Related
http://forum.xda-developers.com/showthread.php?t=1590170[/
What makes this application?
Check for new rom available (works)
Show list of kernel which can be downloaded, download it and reboot to recovery (works)
Show list of plugin which can be downloaded, download it and reboot to recovery (works)
Show list of themes which can be downloaded, download it and reboot to recovery (works)
Check md5 for download file (works)
Check new rom on startup (works)
check new rom every hours (works)
android version >= 3.0
Create your custom tab with name and icon
Link for download
Android > 3
https://play.google.com/store/apps/d...usoft.UpdateMe
Android > 2
https://play.google.com/store/apps/d...teMeSmartphone
Direct link
http://dl.dropbox.com/u/3681387/UpdateMe.apk
http://dl.dropbox.com/u/3681387/UpdateMeSmartphone.apk
How to configure
The program is easily to configure.
in your rom you need only a file named update_me.xml in the system folder.
The file must be like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<RomConfig>
<RomName>Name rom</RomName>
<RomVersion>0.1.0</RomVersion>
<RomCheckUrl>http://www.me.com/update_me_ckeck.xml</RomCheckUrl>
<RomElemUrl>http://www.me.com/update_me_parts</RomElemUrl>
<CheckMD5>0</CheckMD5>
<RebootRecovery>0</RebootRecovery>
</RomConfig>
and 2 other file must to be placed online:
- a file with rom info for check new rom availability
- a file with element for rom.
ATTENTION
When the rom is update, the new rom MUST contains a modified update_me.xml with new version,otherwise the app show always the message "new rom available"
an example config is available here
http://dl.dropbox.com/u/3681387/config_example.zip
the pack of available icon for tabs can download here
http://dl.dropbox.com/u/3681387/icons.zip
in the pack icon named icon_0.png is the number 0 of the config ;D
Supported file host
direct download file host
public folder on dropbox, box.net, etc
goo.im
xdafileserver.nl
androidfilehost.com
How check md5 work
if check md5 is enabled for a file, the program check for a file name with the same name of file plus .md5sum like: app.zip and app.zip.md5sum
with contains md5 plus filename.
if the host is goo.im the md5 is read directly from page
Donate
if you like my work, donate me a beer!!!!
i have create a new app on the market for donate 3 €.
https://play.google.com/store/apps/d...pdateMe.donate
for now it don't allow new feature but in the future i'll add some feature only for donate user.
Extra
Also i have create a new site for the project
http://win.acquariusoft.com
for registered user is possible upload your xml file for public access without limitation of time, in the future more stuff ;D
for now registration is now available on the site, so if you want an account send me a pm with username, password and email.
Donator (tnx to all)
krarvind
TamCore
core720
barikke74
pglmro
pcrao.n
jeff
TRothe
jensmeyer1URL]
Yours?
here is the easy how to for those interested
Original post here
http://forum.xda-developers.com/showthread.php?t=1590170
Original post here
http://dl.dropbox.com/u/3681387/UpdateMeSmartphone.apk
for those that like to add this to their Rom its easy all you do is add the update_me.xml file to your system folder.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<RomConfig>
<RomName>Name rom</RomName>
<RomVersion>0.1.0</RomVersion>
<RomCheckUrl>http://www.me.com/update_me_ckeck.xml</RomCheckUrl>
<RomElemUrl>http://www.me.com/common_update_me.xml</RomElemUrl>
<RomElemUrl>http://www.me.com/transformer_update_me_parts.xml</RomElemUrl>
<RebootType>1</RebootType><!-- 0 no install,1 install on cwm, 2 install openrecoveryscript -->
<FilterName>transformer</FilterName> <!-- Filter for element,if you don't need not insert-->
</RomConfig>
then the file
update_me_ckeck.xm you edit and add it to your files location
Code:
<?xml version="1.0" encoding="UTF-8"?>
<Version>
<Code>1.0.0</Code>
<Desc>First version of this rom</Desc>
<Url>http://www.xdafileserver.nl/TF101/CM9%20by%20ricardopvz/Normal/29%20Mar/update-cm-9.0.0-RC0-tf101-KANG-29Mar-signed.zip</Url>
<HomepageUrl>http://www.google.com</HomepageUrl>
<DonateUrl>http://www.donate.com</DonateUrl>
<CheckMD5>1</CheckMD5>
<MD5Url>http://aaa.md5sum</MD5Url> <!-- url where download the md5 of file, delete tag if don't use -->
<MD5>12345678901234567890123456789012</MD5> <!-- the md5 of file, delete tag if don't use -->
<RebootRecovery>1</RebootRecovery>
</Version>
Lastly do the same for update_me_parts.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<Elements>
<Tab>
<Name>App mod</Name><!-- name of tag -->
<IconNum>0</IconNum><!-- the icon -->
<Element>
<Name>Big rom 1</Name><!-- element name -->
<Desc>Theme1</Desc><!-- element description -->
<Url>http://aaa.zip</Url> <!-- the direct link -->
<Version>1.0.0</Version> <!-- version ( only in format x.x.x not v x.x.x) -->
<CheckMD5>0</CheckMD5><!-- check for md5 1=true 0=false -->
<MD5Url>http://aaa.md5sum</MD5Url> <!-- url where download the md5 of file, delete tag if don't use -->
<MD5>12345678901234567890123456789012</MD5> <!-- the md5 of file, delete tag if don't use -->
<RebootRecovery>0</RebootRecovery><!-- reboot on recovery after download the file 1=true 0=false -->
<Wipe>0</Wipe><!-- show a message for inform that full wipe is raccomandate, and if auto install on recovery, auto full wipe -->
<Dest>/system/app/</Dest><!-- move on directory leave blank or delete for no move -->
<DestChmod>0755</DestChmod> <!-- Chmod value for dest. Default is 0644 -->
<LaunchApp>0</LaunchApp><!-- launche the application after donwloaded 1=true 0=false -->
<Filter>transformer</Filter> <!--Filter for decide if element is show for this rom,if you don't need not insert this line-->
<ThumbnailUrl>http://www.vikispot.com/z/images/vikispot/android-w.png</ThumbnailUrl> <!-- Url for little image see on the left of element,if you don't need not insert this line -->
<ImageUrl>http://eeepc901.altervista.org/blog/wp-content/uploads/2010/04/android-64.png</ImageUrl> <!-- Image show when click on gallery icon in the element,if you don't need not insert this line -->
<ImageUrl>http://www.androidquery.com/z/images/androidquery/github.png</ImageUrl><!-- More then one image ;D,if you don't need not insert this line -->
</Element>
</Tab>
<Tab>
<Name>App mod2</Name>
<IconNum>2</IconNum>
<Element>
<Name>Applicazione 2</Name>
<Desc>Theme1</Desc>
<Url>http://aaa.zip</Url>
<Version>1.0.0</Version>
<CheckMD5>0</CheckMD5>
<RebootRecovery>0</RebootRecovery>
<LaunchApp>0</LaunchApp>
</Element>
<Element>
<Name>Applicazione 3</Name>
<Desc>Install</Desc>
<Url>http://aaa.zip</Url>
<Version>1.0.0</Version>
<CheckMD5>0</CheckMD5>
<RebootRecovery>0</RebootRecovery>
<LaunchApp>1</LaunchApp>
</Element>
</Tab>
<Kernels>
<Kernel>
<Name>Guevor</Name>
<Desc>Gueveor test 4 kernel no md5 no recovery</Desc>
<Url>http://goo.im/apps/Indirect/Nook_tablet/NookUnrooter.apk</Url>
<Version>1.0.0</Version>
<CheckMD5>0</CheckMD5>
<RebootRecovery>0</RebootRecovery>
</Kernel>
<Kernel>
<Name>Stock</Name>
<Desc>Kernel stock della rom a</Desc>
<Url>http://goo.im/apps/longcat/E4GT_Stock_GPSConfig_Signed-Naerok.zip</Url>
<Version>1.0.0</Version>
<CheckMD5>1</CheckMD5>
<RebootRecovery>1</RebootRecovery>
</Kernel>
<Kernel>
<Name>Test sourceforge</Name>
<Desc>Test</Desc>
<Url>http://sourceforge.net/projects/microzip/files/src.7z/download</Url>
<Version>1.0.0</Version>
<CheckMD5>0</CheckMD5>
<RebootRecovery>0</RebootRecovery>
</Kernel>
<Kernel>
<Name>Test sourceforge Big rom</Name>
<Desc>Test</Desc>
<Url>http://sourceforge.net/projects/fastdontlie/files/Sweet%20Child%20of%20Mine%20v3.5.zip/download</Url>
<Version>1.0.0</Version>
<CheckMD5>0</CheckMD5>
<RebootRecovery>0</RebootRecovery>
</Kernel>
</Kernels>
<Plugins>
<Plugin>
<Name>Plug1</Name>
<Desc>Plug1</Desc>
<Url>http://goo.im/apps/Indirect/Nook_tablet/NookUnrooter.apk</Url>
<Version>1.0.0</Version>
<CheckMD5>1</CheckMD5>
<RebootRecovery>1</RebootRecovery>
</Plugin>
<Plugin>
<Name>Plug2</Name>
<Desc>Plug2</Desc>
<Url>http://www.xdafileserver.nl/Home/ASUS/Asus%20Transformer%20(TF101)/ROMS/Megatron/Gapps/gapps-ics-20120317-signed.zip</Url>
<Version>1.0.0</Version>
<CheckMD5>1</CheckMD5>
<RebootRecovery>1</RebootRecovery>
</Plugin>
</Plugins>
<Themes>
<Theme>
<Name>Theme1</Name>
<Desc>Theme1</Desc>
<Url>http://www.xdafileserver.nl/Home/TF101/CM9%20by%20ricardopvz/Normal/29%20Mar/update-cm-9.0.0-RC0-tf101-KANG-29Mar-signed.zip/Kernel/Guevor/test4/guevor-test4.zip</Url>
<Version>1.0.0</Version>
<CheckMD5>1</CheckMD5>
<RebootRecovery>1</RebootRecovery>
</Theme>
<Theme>
<Name>Theme2</Name>
<Desc>Theme2</Desc>
<Url>http://www.xdafileserver.nl/Home/TF101/CM9%20by%20ricardopvz/Kernel/Stock/Stock_Kernel.zip</Url>
<Version>1.0.0</Version>
<CheckMD5>1</CheckMD5>
<RebootRecovery>1</RebootRecovery>
</Theme>
</Themes>
<Apps>
<App>
<Name>Applicazione 1</Name>
<Desc>Theme1</Desc>
<Url>http://dl.dropbox.com/u/3681387/UpdateMe_1_0_3_beta1.apk</Url>
<Version>1.0.0</Version>
<CheckMD5>0</CheckMD5>
<RebootRecovery>0</RebootRecovery>
</App>
<App>
<Name>App2</Name>
<Desc>Theme2</Desc>
<Url>http://dl.dropbox.com/u/3681387/UpdateMeSmartphone_beta3.apk</Url>
<Version>1.0.0</Version>
<CheckMD5>1</CheckMD5>
<RebootRecovery>0</RebootRecovery>
</App>
</Apps>
</Elements>
no its not i have a modified version with a fullly kitchen app.
myApp called Drive Thru is much different, my program rips rom from phone and intigrates into a gui kitchen then cooks the rom with full modded themed and editing all aspespects of the creation and then flashes it . i call it Drive Thru
It is working on for linux, windows and mac.. still has 23 bugs but so far its almost ready for release...
I will move this to General and lock
Cheers
Is there any way to update an existing XDA user account, such as change user e-mail address, or change or add an im'age? I've made several attempts, but haven't been able to find the method for accomplishing this.
This recovery is CWM for the One SV. It is fully working and has no problems. All variants are supported below
K2_CL (Boost Mobile) -> Boost Download
K2_PLC_CL (Cricket) -> Cricket Download
K2_UL (EU LTE) -> EU LTE Download
K2_U (EU NON-LTE) -> EU Non-LTE Download
Sources:
Boost Mobile Source
Cricket Source
EU LTE Source
EU Non-LTE Source
To build these recoveries on your own, simply follow the directions below:
Clone the CyanogenMod repo. See their wiki at http://wiki.cyanogenmod.org
create a local_manifests file by issuing the command `mkdir -p .repo/local_manifests/` then `gedit .repo/local_manifests/k2.xml`
inside this new document place the following lines
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/htc/msm8960-common" name="CyanogenMod/android_device_htc_msm8960-common" />
<project path="device/htc/s4-common" name="CyanogenMod/android_device_htc_s4-common" />
<project path="device/htc/k2_cl" name="SimonSickle/android_device_htc_k2_cl" revision="cwm" />
<project path="vendor/htc/k2_cl" name="SimonSickle/android_vendor_htc_k2_cl" revision="jellybean" />
<project path="device/htc/k2_plc_cl" name="SimonSickle/android_device_htc_k2_plc_cl" revision="cwm" />
<project path="vendor/htc/k2_plc_cl" name="SimonSickle/android_vendor_htc_k2_plc_cl" revision="jellybean" />
<project path="device/htc/k2_ul" name="SimonSickle/android_device_htc_k2_ul" revision="cwm" />
<project path="vendor/htc/k2_ul" name="SimonSickle/android_vendor_htc_k2_ul" revision="jellybean" />
<project path="device/htc/k2_u" name="SimonSickle/android_device_htc_k2_u" revision="cwm" />
<project path="vendor/htc/k2_u" name="SimonSickle/android_vendor_htc_k2_u" revision="jellybean" />
<project path="kernel/htc/k2" name="SickleKernels/android_kernel_htc_k2" revision="htc_3.4" />
</manifest>
now run `repo sync` and wait for this to finish. It will take a long time
With any luck, you now have the source. Your computer should already be set up to build so just do the following commands
. build/envsetup.sh
now you will want to lunch the right device (see the download section as a guide)
lunch cm_k2_cl-userdebug
and finally the make command is as follows
make -j5 recoveryimage
at the end you will see a welcoming path to your new recovery. Flash it in fastboot or with dd and enjoy!
simonsimons34 said:
This recovery is CWM for the One SV. It is fully working and has no weird glitchy screen like it had before.
Download for BOOST MOBILE here -> http://downloads.codefi.re/simon/k2cl/CWMrecovery.img
Source at http://github.com/SimonSickle/android_device_htc_k2_cl/tree/cwm
I have applied for official status with Koush. Until he accepts it, enjoy this perfect build
Click to expand...
Click to collapse
Works great Simon! Thanks.
simonsimons34 said:
This recovery is CWM for the One SV. It is fully working and has no weird glitchy screen like it had before.
Download for BOOST MOBILE here -> http://downloads.codefi.re/simon/k2cl/CWMrecovery.img
Source at http://github.com/SimonSickle/android_device_htc_k2_cl/tree/cwm
I have applied for official status with Koush. Until he accepts it, enjoy this perfect build
Click to expand...
Click to collapse
Hi;
The recovery file is not there. Can you reload it?
Sorry Simon, recovery doesn't boot.
Neither the k2u nor the k2ul.
k2u -> boots constantly into android, not recovery.
k2ul -> hangs on splash screen.
bkcokota's cwm works totally fine, but it has the framework bug.
This bug fixed and we have a stable CWM. But i know, devs do not work on others build.
I am going to do twrp then. Once those are confirmed booting ill use the TWRP folder and remove anything non twrp from them
PS- The issue with his build is a lack of source (problem one), the partitions are different (two), the devices have different code names which messes with the flashing of source built roms (problem three) and its not ready for 4.3 (4)
Updated 9/21/13
Sent from my C525c using Tapatalk 4
All of the links are dead. Where else can I get info for the Boost c525c?
Hi i have tested a lot of OTA apps and configs and they are very annoying until i stop thinking for a moment and I find a solution for having true OTAS updates and not depending from other users just like Nexus Devices OTAS.
Ok we started:
First of all we need to download Android Bundle with contains SDK and Eclipse
Here it is:
http://developer.android.com/sdk/index.html?hl=sk#download
After it is download and installed.
You are going to download my fixed source for supporting from Android 4.1.2 to 4.4.2.
https://github.com/werty100/OpenDelta
And Click on:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Them open Eclipse...
Go to file/Import:
Next and locate were is the download source
Then Finish...
Wait until it is import....
Go to res folder, values and open config.xml:
Here are the important values for making work your OTA in your phone.
Code:
<!-- Property to read for ROM version -->
<string name="property_version">ro.delta.version</string>
<!-- Property to read for device identifier -->
<string name="property_device">ro.delta.device</string>
This should be put in build.prop:
Ex:
ro.delta.version=1.0.2
ro.delta.device=i9000
You can modificated all values but you should modificate this ones:
Code:
<!-- URL base to find .delta files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_delta">https://delta.omnirom.org/nightlies/%s/</string>
<!-- URL base to find .update and .sign files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_update">http://delta.omnirom.org/nightlies/%s/</string>
<!-- URL base to find the full zip files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_full">http://dl.omnirom.org/%s/</string>
Indicates where to find the ZIP for your phone...
Also you can modificate all UI and values....
After the essentials modifications you will need to compile APK:
Go here and click on selected item..
You will need to create your own KeyStores
Rellenate also this:
https://dl.dropboxusercontent.com/u/26870831/rellenate.png
Them just put destination and click finish:
After all of this you have to modificate the Settings.apk of your rom:
Decompile with the script/tool you like more and go to:
In res/values:
String.xml
Add this:
Code:
<string name="system_update_settings_list_item_title">System updates</string>
<string name="system_update_settings_list_item_summary" />
Paste it near baseband_version string kernel_version string etc...
Then go to public and paste this near device_info_settings:
Code:
<public type="string" name="system_update_settings_list_item_title" id="0x7f0c06d7" />
<public type="string" name="system_update_settings_list_item_summary" id="0x7f0c06d8" />
Then go to xml/device_info_settings.xml:
And copy this in the firs lines after:
Code:
<?xml version="1.0" encoding="utf-8"?>
<PreferenceScreen android:title="@string/about_settings"
xmlns:android="http://schemas.android.com/apk/res/android">
Paste this:
Code:
<PreferenceScreen android:title="@string/system_update_settings_list_item_title" android:key="system_update_settings" android:summary="@string/system_update_settings_list_item_summary">
<intent android:action="android.settings.SYSTEM_UPDATE_SETTINGS" />
</PreferenceScreen>
<PreferenceScreen android:title="@string/additional_system_update_settings_list_item_title" android:key="additional_system_update_settings">
<intent android:targetPackage="@string/additional_system_update" android:action="android.intent.action.MAIN" android:targetClass="@string/additional_system_update_menu" />
</PreferenceScreen>
After Compiling Settings.apk you will have full OTAS
Tomorrow More
Today more
Publish on HTCMania haha
Update New settings for OTA
Just a quick question:
Code:
[B] <!-- URL base to find .delta files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_delta">https://delta.omnirom.org/nightlies/%s/</string>
<!-- URL base to find .update and .sign files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_update"http://delta.omnirom.org/nightlies/%s/</string>[/B]
<!-- URL base to find the full zip files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_full">http://dl.omnirom.org/%s/</string>
If we want to configure it to our directory, what should we inclue on .delta files & .update and .sing files?
With this OTA guide will I have to boot into recovery to flash a OTA?
You can't use this for any other ROM because we don't know what we should had on .delta & .update & .sign files
Howdy! Some general stuff:
You should credit original developer of OpenDelta (that's Chainfire @ OmniROM)
Proper way to make own, patched version is Pulling the original repository (easiest way is using "Pull" button on GitHub there: https://github.com/omnirom/android_packages_apps_OpenDelta) and then patching it - this way you preserve all the commits history (and credits to original authors)
_MarcoMarinho_ said:
You can't use this for any other ROM because we don't know what we should had on .delta & .update & .sign files
Click to expand...
Click to collapse
There we got with an example:
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.sign
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.update
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.delta
.delta file is JSON
.sign is binary signature
.delta is binary delta data
...and
GUESS WHAT! There's an opensource stuff to generate ALL of the above.
Completely! Automagically!
https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-4.4/server/
Rebellos said:
Howdy! Some general stuff:
You should credit original developer of OpenDelta (that's Chainfire @ OmniROM)
Proper way to make own, patched version is Pulling the original repository (easiest way is using "Pull" button on GitHub there: https://github.com/omnirom/android_packages_apps_OpenDelta) and then patching it - this way you preserve all the commits history (and credits to original authors)
There we got with an example:
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.sign
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.update
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.delta
.delta file is JSON
.sign is binary signature
.delta is binary delta data
...and
GUESS WHAT! There's an opensource stuff to generate ALL of the above.
Completely! Automagically!
https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-4.4/server/
Click to expand...
Click to collapse
Thanks so much :highfive:
So I just need to modify few things, generate ALL stuff and then upload it to my server right?
Yup. Looks like. I'm not really experienced with OpenDelta but knowing Chainfire it's all easy to work with.
Post for subscription
when it comes to these stuff (git with coding and xml and OH MY GOD!) i am a total noob.
i still don't know how do i generate these files. I understand .zip is the whole ROM, but i have no idea how i can make .update .sign and .delta and what should i put in them and all.
hehe, to me, all i see is three beautiful files here https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-4.4/server/ which i know nothing about how i can use them to get the files.
i guess i'll wait for the "tomorrow more"
@_MarcoMarinho_ you can find on the github readme how to generate the Delta files.
Server-side
To create the delta files on the server, you need several things, some of which can be found in the server directory. The main thing is the opendelta.sh script. It contains a configuration section which you can edit with the correct file locations on your own system. Quite likely you will need to create a wrapper script that pulls in your previous release and your current release, and pushes out the created delta files.
The script depends on xdelta3, zipadjust and minsignapk.
For the builds on your server, make a copy of the jni directory - do not compile inside jni because you may mess up the build of libopendelta.
xdelta3 can be built in (the copy of) jni/xdelta3-3.0.7 by calling ./configure and make.
zipadjust can be built in (the copy of) jni by calling:
gcc -o zipadjust zipadjust.c zipadjust_run.c -lz
dedelta (not used by the script, but maybe helpful when debugging) can be built in (the copy of) jni by calling:
gcc -o dedelta xdelta3-3.0.7/xdelta3.c delta.c delta_run.c
minsignapk Java source is in the server directory, as well as a prebuilt minsignapk.jar file that should work on most systems.
Click to expand...
Click to collapse
If you are however to lazy to set up all that stuff check my script on github you can find here:
https://github.com/Myself5/CarbonDelta_server_software/
(I used it for my unofficials and when we tested CarbonDelta (which is based on OpenDelta))
Check the readme on how to install it and use it.
Myself5 said:
@_MarcoMarinho_ you can find on the github readme how to generate the Delta files.
If you are however to lazy to set up all that stuff check my script on github you can find here:
https://github.com/Myself5/CarbonDelta_server_software/
(I used it for my unofficials and when we tested CarbonDelta (which is based on OpenDelta))
Check the readme on how to install it and use it.
Click to expand...
Click to collapse
Thank, thanks so much, now I understand
-----
When I should put your repo? inside pakcages/apps?
_MarcoMarinho_ said:
Thank, thanks so much, now I understand
-----
When I should put your repo? inside pakcages/apps?
Click to expand...
Click to collapse
In any folder where you want it. It must not be inside your Roms Sourcecode. To create the delta update and sign files just follow the readme
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<!-- Output some debug strings -->
<item type="bool" name="debug_output">false</item>
<!-- Property to read for ROM version -->
<string name="property_version">ro.euclidean.version</string>
<!-- Property to read for device identifier -->
<string name="property_device">ro.euclidean.device</string>
<!-- %s is expanded to property_version value. .zip, .delta, .update, .sign extensions added when needed -->
<string name="filename_base">euclidean_%s</string>
<!-- Path deltas are stored, relative to sdcard root -->
<string name="path_base">EuclideanDelta</string>
<!-- URL base to find .delta files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_delta">http://euclideanrom.grn.cc/downloads/%s/delta/</string>
<!-- URL base to find .update and .sign files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_update">http://euclideanrom.grn.cc/downloads/%s/delta/</string>
<!-- URL base to find the full zip files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_full">http://euclideanrom.grn.cc/downloads/%s/</string>
This is my setup.
I can't figure it out why I don't receive the updates
@werty100 will this work for lollipop?
gcng said:
@werty100 will this work for lollipop?
Click to expand...
Click to collapse
You need the new app source code.
Hey guys. I want add support OTA in my builds. I'm fully understand what need to be changed on client side and how generate *.delta and *.update files, but what i need for server side?
Just place files at some path, and somehow mystical way the application will find it.. or need some json script, which protocol need to use, how app retrieve list of files/information from server...
Thanks in advance.
ElArchibald said:
Hey guys. I want add support OTA in my builds. I'm fully understand what need to be changed on client side and how generate *.delta and *.update files, but what i need for server side?
Just place files at some path, and somehow mystical way the application will find it.. or need some json script, which protocol need to use, how app retrieve list of files/information from server...
Thanks in advance.
Click to expand...
Click to collapse
just add them to web server.
Hello, I'm trying to build cm 13 caf rom myself (i have never done it before) and I'm following this guide. I have done everything to the step "download the source code" from https://github.com/CyanogenMod/android.git. Now I should "Prepare the device-specific code", but the guide is for hammerhead CM (non-caf) and, if I'm right, I should add some local_manifests but I have no idea of how to do this. (in fact if I type $ breakfast hammerheadcaf it starts downloading and then it says
** Don't have a product spec for: 'cm_hammerheadcaf'
** Do you have the right repo manifest?)
Can anyone explain it to me, please?
Hello apon97!
You can search the CAF thread a bit - a lot of question regarding building CyanogenMod for hammerheadcaf have been already covered there. However, the thread is huge and searching it is a pain in the b*tt sometimes so I'll try to help you here.
You have to know the following:
Downloading the source code will 'only' download the default projects. This usually takes a few hours to download depending on your internet connection. However, to build for a specific device (hammerheadcaf in this case) you also have to get two more things: It's dependencies (device- and kernel-tree) and the vendor proprietary files - usually simplified as 'blobs'.
So after you've downloaded the source code you don't have any local manifests. A simple 'breakfast hammerheadcaf' will look for cm.dependencies in the device-tree and automagically add these to your default local manifest (called 'roomservice.xml').
The proprietary stuff has to be manually added to the local manifest. Just open up /SOURCE/.repo/local_manifests.xml and you should see that the kernel and device tree is already there (because you breakfasted...). Now add another line for the blobs. These can be found on TheMuppets: github.com/TheMuppets/proprietary_vendor_lge
So your local manifest 'roomservice.xml' should look something similar to this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_hammerheadcaf" path="device/lge/hammerheadcaf" remote="github" />
<project name="CyanogenMod/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" revision="cm-13.0-caf" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>
PS: myfluxi updated the proprietary files for hammerheadcaf on his personal GitHub. You're free to use this project instead if you want to be up-to-date. However, he says that we don't need necessarily up-to-date blobs. Then the last project would look like this:
Code:
<project name="myfluxi/proprietary_vendor_lge" path="vendor/lge" remote="github" />
Now you have everything set up and ready to build CM13 CAF for the Nexus 5!
You don't have to go through this everytime you want to build. Next time just use
'repo sync'
'source build/envsetup.sh'
Optionally 'make clean' or 'make clobber' <- This will delete stuff from previous builds. Doing a clean build will take longer...
and finally...
'brunch hammerheadcaf'
Much fun building!
Everything looks clear. Yes, I have searched your thread but couldn't find the answer (maybe I could have tried a little more). I hope I will not have to bother you anymore
Thank for such a complete answer and for everything you do for our Nexus 5
Yeah I know, the thread is a bit messy but I can't do anything about it
Don't hesitate to ask if you need a bit more help
Hello, My fingerprint sensor is not working with any official or custom firmware other than renegade v1.1. Even renegade v2.0 does not work, does anyone have any hints at what might be happening? Thanks.
Solution
After a long time trying to find a solution to the fingerprint / pin code error I found: Just create a new user and switch to it and everything will be solved.
Edit
Secondary user have limitation (privileges) so is not a solution but somehow the pin password fingerprint works like a charm on Secondary user, the problem persists...
I think I found the cause of the error in rom renegade 1.1 the XML file of the primary user found in the path /data/system/user/0.xml, looks like this:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<user id="0" serialNumber="0" flags="19" created="0" lastLoggedIn="1497859689448">
<name>Zeki Melo</name>
<restrictions />
</user>
In stock firmware (which does not work pin nor password is this way:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<user id="0" serialNumber="0" flags="19" created="0" lastLoggedIn="1497859689448">
<name>Zeki Melo</name>
<restrictions />
<device_restriction_polices /> (something like that)
</user>
I think there has to be with the security policy of Google / Samsung, does anyone know if you have how to disable this security policy in Android or take off this code ( <device_restriction_polices />) from the primary user?