LeeDroid HD V3.x.x-Port-Rx FAQ
last updated: 2011-Oct-29 [DISCONTINUED]
If you wish to use the data in this FAQ in any way, you are free to do so without any need for links \ attribution, except for people mentioned in the FAQ itself - please mention them where applicable.
ROM version described: 3.3.3-Port-R5
Contents
1. What's all that geeky stuff about A2SD+ \ Data++?
1.1. What is the difference between A2SD+ and Data++ versions of LeeDrOiD V3.x.x Bravo GB?
1.2. I installed Data++ version and have a xx GB ext partition. Why isn't my internal memory same size, i.e. xx GB?
1.3. I do not have enough memory for my apps!!!
1.4. What else do I have to keep in mind if I want to use the Data++ version?
1.5. I have Data++, but my internal memory is only ~287 mb, not 1Gb <substitute your value> of the sd-ext partition. What's wrong?
1.6. Is my Data++ working?
1.7. Is there a data2ext version of LeeDroid 3.3.x?
1.8. How do I check where my dalvik cache is?
2. What do I have to do before I can flash the ROM?
2.1. What is required to flash this ROM?
2.2. I want to S-OFF, how do I do that?
2.3. I have to flash a different hboot, how do I do it?
2.4. I'm not sure which hboot I have, how do I learn that?
2.5. Can I change the hboot without reflashing the rom?
2.6. How do I partition my SD card correctly?
2.7. Do I have to have S-OFF to install this ROM?
2.8. I have radio other than recommended by Lee (32.56.00.32U_5.17.05.08). Do I have to flash the recommended radio?
3. Flashing guide
4. Troubleshooting ROM installation
4.1. It won't flash the rom!
4.2. I'm stuck on first boot!
4.3. I downloaded the data version and its flashing now and says now flashing leedroid... a2sd+ ?!?!
5. Troubleshooting other problems
5.1. I'm getting multiple Force Close all the time
5.2. I'm getting Force Close on Calendar, both widget and the actual app
5.3. Weather info on sense keeps disappearing after sleep mode, is there any fix for that?
5.4. Videos distorted if made in portrait orientation
5.5. Battery life miserable
5.6. Large apps such as Sygic Aura Drive disappearing after reboot
5.7. ADfree is not working
5.8. How to disable CRT TV on-off animations?
5.9. Is it possible to change the shortcuts on the Sense 3.0 lockscreen?
5.10. Where can I get the default Ginger2.3 keyboard? Call me crazy but I like it more than the Sense one
5.11. When using Spare Parts, and I want to check the Battery History I get a force close error, anybody else?
5.12. Music not loud enough when using headphones.
5.13. Using Sense Camera app causes screen brightneess to go to 100%
5.14. I've bought a larger SD card, now I don't know how to painlessly upgrade from the old card without loosing the system...
5.15. I've switched to this rom from another one, and there's not enough space to restore my apps with Titanium Backup!
5.16. AC charger is recognized as a USB charger and therefore charges the phone very slowly.
5.17. Messages appear claiming that SU-binary is outdated but you can't update it.
5.18. Camera app quits suddenly and\or switches screen brightness to maximum.
5.19. Can't get to bootloader...
6. Mods
6.1. What mods are available?
6.2. How to flash the Sense 3.0 pack?
6.3. Is there anything I should know before flashing the mods?
6.4. How about themes?
7. Troubleshooting modding problems
7.1. I've flashed Sense 3.0 Pack and it's screwed up!
7.2. How to add\remove\change ringtones, alarms and notification sounds?
7.3. How to remove \ change the bootsound \ bootanimation?
7.4. I've flashed Sense 3.0 pack, and I guess I don't really like it and want to get rid of it - how to?
8. Customizing guide
8.1. Kitchen customizations
8.2. Adding notification panel widgets
8.3. Sense skins and themes
9. Downloads
1. What's all that geeky stuff about A2SD+ \ Data++?
1.1. What is the difference between A2SD+ and Data++ versions of LeeDrOiD V3.x.x Bravo GB?
With Desire's stock ROM, little ROM is available for user apps as the \data partition is very small (147 MB).
With A2SD+ ROM, somewhat more is available, as dalvik cache and apps are moved to sd-ext. However, some data is still written to the \data partition, so no matter what, the "Internal memory" will decrease.
Data++ version gives you yet more internal memory for app installation than A2SD+ version, however, it is a little trickier to both flash and customize. As it does not move dalvik cache to SD, unlike A2SD+, dalvik cache still occupies a considerable amount of internal storage. This makes the system marginally quicker than A2SD+, at the expense of available internal memory and placing a cap on the total volume of installable apps (which is still considerably higher than in the A2SD+ version). Furthermore, it can be moved to sd-ext as well, freeing more memory still (see subsection "Things to know if using Data++" below, item 5).
To actually free more memory for user apps, data++ version moves a number of system files from \system partition to sd-ext. This in turn allows to redistribute the partitions of the phone memory:
- system partition is reduced to 145 Mb at the expense of files moved to sd-ext and\or deleted
- cache partition, originally 40 Mb and empty most of the time, is reduced to 5mb
- data partition (the one shown as "internal memory" and available for your user apps\dalvik) is increased at the expense of the two mentioned above to 287 Mb, which is 140 Mb larger than stock.
This partitioning is determined by the hboot you use. So, in order to enjoy the benefits of data++, you will have to flash the required hboot first, which is Bravo CM7 r2.
Another difference between A2SD+ and Data++ is that you DO NOT have to have S-OFF for A2SD+ but YOU HAVE TO HAVE S-OFF for Data++.
1.2. I installed Data++ version and have an xx Gb ext partition. Why isn't my internal memory same size, i.e. xx Gb?
Data++ is NOT the same as Data2Ext. Data2Ext (same as Data2SD) will increase the size of "internal memory" as percieved by your system to the size of your sd-ext (it may also require two ext partitions instead of one depending on implementation). Data++ will NOT increase your internal memory to the size of sd-ext; it will only free some NAND memory by moving some system files to sd-ext and re-allocating the freed space to \data by using oxygen hboot.
1.3. I do not have enough memory for my apps!!!
If you're using A2SD+:
- If you have dalvik on nand (which is default for latest builds of this rom), move it to sd using respective patch listed in this FAQ. This will result in marginal (or noticable, if your card is slow and\or your luck runs out) performance degradation.
- If you need more space or want to leave dalvik in nand for better performance, switch to data++ version of this ROM.
If you're using Data++:
- If you have dalvik in nand (which is default in last builds), move it to sd using respective patch listed in this FAQ. This will result in marginal (or noticable, if your card is slow and\or your luck runs out) performance degradation.
- If you still need more space, either try increasing the size of your ext partition, or switch to a different ROM offering data2sd capability.
1.4. What else do I have to keep in mind if I want to use the Data++ version?
1. As cache partition has been reduced to 5 mb in data++ version-compatible hboot:
- a ramdisk is used instead of it for caching downloads from the market. However, RAM is not used when not needed, so you should not worry about your RAM being squandered.
- to update the radio, you have to use fastboot ('fastboot flash radio radio.img'. Radio.img is to be extracted from the radio update.zip beforehand) or update radio using stock hboot prior to flashing modified hboot. I guess you can also use Android Flasher, which is basically a GUI for ADB flashing commands, though I've not tried it myself.
2. Since location of some system files has changed in data++ relative to stock ROM (i.e. they were moved to sd), flashing UOT kitchen mods and themes can be tricky. More on this below in the respective section.
3. Having sd-ext on sdcard may negatively affect the read\write performance of the fat32 partition (this one goes for A2SD+ as well, though).
4. Even if you install data++ version, which has dalvik in internal memory, you can move dalvik cache to sd-ext to free space for your apps at the cost of a small performance decrease using the dalvik2ext patch.
6. If you want to go back from Data++ rom to a2sd+\stock rom, be it by flashing or restoring a nandroid, you will have to flash stock hboot first!
1.5. I have Data++, but my internal memory is only 287 mb, not 1Gb <substitute your value> of the sd-ext partition. What's wrong?
You've clearly missed item 1.2 of this FAQ. Please scroll up and read it.
1.6. How do I tell if my Data++ is installed correctly and working?
If the phone boots, that means sd-ext is working all right.
You can also use free market app Quick Sytem Info to check if it shows you A2SD storage. It should obviously be non-zero but equal to the size of your sd-ext partition.
You can also see in the same program the Internal memory size. Total should be 287 mb, if it is not so, you're on the wrong hboot. See item 2.3 of this FAQ to learn how.
1.7. is there a data2ext version of LeeDroid 3.3.x?
No. If you need a lot of space, try the data++ ROM with dalvik-cache on ext. It should be faster and more stable than data2ext.
1.8. How do I check where my dalvik cache is?
- You may use DiskUsage and let it show /data
- You may use RootExplorer
- You may use ADB, with the command: adb shell ls -la /data
If it's a directory then it is on data. If it is a symlink then it's where the symlink points to.
<back>
2. What do I have to do before I can flash the ROM?
2.1. What is required to flash this ROM?
a. General requirements
- Rooted HTC Desire
- SD card partitioned into two partitions - FAT32 and EXT3 (EXT4 supported, but if you are going to flash mods later on you may have to mount it manually for some of them)
- hboot 0.93.x - I suppose it's same as with LeeDroid 3.0.x, where some have reported successfully flashing with older hboots, but it usually took multiple attempts, so it's easier to S-OFF
- fully charged battery, just in case, and a USB connector to plug it in in case you're not sure if you can turn it off prior to getting advice
- It is always better to flash critical stuff (like hboot) using a notebook or UPS-connected PC for obvious reasons
b. Requirements specific to Data++
- S-OFF
- Bravo CM7 r2 hboot downloaded and ready to flash (Bravo CM7 r1 is NOT compatible!)
- Stock hboot in case you want to go back
2.2. I want to S-OFF, how do I do that?
A video guide on rooting, S-offing and partitioning is available in this wonderful video tutorial thread.
Obtaining S-OFF is also described here: http://alpharev.nl/ OR in detail http://forum.xda-developers.com/showthread.php?t=805811
Brief explanation (sapienti sat): download S-OFF CD http://alpharev.nl/alpharev.iso, burn it and reboot (or mount it as bootcd in a virtual machine and reboot it), connect rooted HTC Desire, cross your fingers and follow instructions. If unsuccessful, try several times, if still unsuccessful, use a different USB port (preferably one on the motherboard, not the front panel, if you're using a desktop and not a notebook) and try several times, if still unsuccessful, try a different computer.
Can be done in a VM such as VMWare as well.
Another way is to use the newer Revolutionary tool.
A brief how-to is here.
2.3. I have to flash a different hboot, how do I do it?
Flashing hboot is described here:
- http://alpharev.nl/
- http://forum.xda-developers.com/showpost.php?p=14259861&postcount=3683
- http://androidtricks.net/fastboot-custom-hboot-partition-table-htc-desire-52
- http://forum.xda-developers.com/showpost.php?p=15646202&postcount=6730
All necessary files can be found in the last section.
2.4. I'm not sure which hboot I have, how do I learn that?
- by internal memory size: your internal memory should read 287 Mb if yoou're on Bravo CM7 r2
- by hboot name: Turn off your phone and hold volume down button and power button at same time. This will open a fastboot after couple seconds. See the top line where it says s-off, and in pink it should say "AlphaRev" and hboot name, e.g. "AlphaRev CM7 r2". Hboot version is couple lines below top.
If you see S-ON instead of S-OFF, you'll have to btain S-OFF first to be able to flash a different hboot.
2.5. Can I change the hboot without reflashing the rom?
If you've flashed Data++ version of this rom on a stock hboot, you can try changing hboot without reflashing the rom by means of nandroid backup.
Of course, it works only if your system\ and data\ are same or smaller than those of the new hboot, otherwise unpacking the nandroid will fail as you run out of space. Data++ rom installed on stock hboot is exactly such a case:
- Make a nandroid backup
- Flash Bravo CM7 r2 hboot
- Restore backup
Should work. But in any case, make sure you back up all the necessary stuff to PC, just to be safe.
If it doesn't work, you can always either
- flash the rom anew
- give up, flash old hboot and restore nandroid
2.6. How do I partition my SD card correctly?
To partition your card, you can use:
- GPARTED (linux software for partitioning, can be run on any PC using a live-cd, site: http://gparted.sourceforge.net/livecd.php, how-to)
- any other reasonably advanced partitioning program (such as Acronis Disk Director)
- minitool partition wizard (freeware windows partitioning program, site: http://www.partitionwizard.com/download.html)
- your recovery
- ROM Manager app
This list is ordered in terms of success probability:
- GPARTED is the surest way to make good partitioning, although it is not noob-friendly and requires you to use a live-cd if you're using a non-linux OS such as windows, which means (a) rebooting to use it and (b) knowing how to enable booting with CD if it's disabled in your BIOS
- any other reasonably advanced partitioning programs cost money, so if you don't have 'em already, no point in buying them
- minitool partition wizard is windows-native and user-friendly, although marginally not as dependable as the two above options. Had never any problem with it, though
- recovery is another way to partition your card, but you are more limited as to available partition sizes and the probability of errors is higher.
- ROM Manager can also partition cards, but the probability of errors is higher than with recovery
Keep in mind:
- both partitions should be primary (see below on how to check)
- FAT32 should go first, EXT3\4 should go second (EXT4 claimed to be supported, not tested by author of this post)
- if partitioning via recovery\ROM manager, specify swap size as zero
- do not label the partitions
- reasonable size range for ext partition is 1-2gb
- if you are not experienced in partitioning, back up your sd card data (if you need it), for there are many ways to lose it when partitioning and only a few not to. You can just copy your sdcard data to a folder, then copy it back to fat32 partition if necessary.
- method of partitioning should be irrelevant, however, best results seem to be obtained by using GPARTED \ minitool partition wizard. Gparted is the surest way, but least convenient; minitool Partition Wizard is very easy to use and requires no reboots.
2.7. How to check if my partitions are primary and in correct order?
Simply put, you can do that by using programs used for partitioning listed above.
If you partitioned using ROM manager \ Recovery, your partitions should be primary, because the writers of that software are not saboteurs. So you need to check it only if you partitioned the disk yourself using partitioning software and are no longer sure if you did it right (one can always forget).
If you're using Windows, it's very easy:
If you don't have a card reader or do not want to open your desire to get the card out of it:
1. Connect phone to PC with USB and boot into recovery
2. Enter USB-MS mode and wait for the PC to see your flash card
If you have a card reader and don't mind opening it to get the card out:
1. Open Desire, remove card
2. Connect card reader to your PC, stick the card into it, wait for the PC to see it, and then...
...if you have minitool Partition Wizard, you can:
3. Launch it
4. Find your card in the list of disks
6. See partition types in the rightmost column, and partition order in the list under the card and graphically in the bottom half of the window
...if you have acronis Disk Director, you can:
3. Launch it
4. Find your flash card
5. In the top half, partition types are specified
6. In the bottom half, you can check the color of the partition against the legend (primary is yellow), and see if the order of partitions is correct
...if you have not the above software, you can go with Windows Disk Management:
3. In windows, press WinKey+R to get the Run dialog
4. Type dikmgmt.msc and hit ENTER
5. Wait for it to initialize, locate your flash card in the bottom half of the screen, using scroll bar if necessary
6. It should show two partitions, xx.xxGB FAT32 / Healthy (Primary Partition) and x.xxGB / Healthy (Primary Partition)
7. When done, close the window
...if you're masochistic enough for command prompt, you can:
3. In windows, press WinKey+R to get the Run dialog
4. Type DISKPART, wait for a prompt to appear (it could take some time)
5. type LIST and hit ENTER
6. It will show you a bunch of disks that are on your system. You have to find in the list the one which is your flash card (by the size) and mark its number.
7. Type SELECT DISK <disk number here> and hit ENTER
8. Type LIST PARTITION and hit ENTER
9. It will show you partitions, their order and their types
10. After you're done, just close the windows with the mouse
2.7. Do I have to have S-OFF to install this ROM?
Since you've obviously missed the "2.1. What is required to flash this ROM?" section of this FAQ, suggest you scroll up and read it thoroughly.
2.8. I have radio other than recommended by Lee (32.56.00.32U_5.17.05.08). Do I have to flash the recommended radio?
Actually, not. The rom will work with any radio. The best (but a very tedious) approach would be to flash a multitude of radios in succession and see which one is best for your combination of device\rom\cell provider\geographical features
This would take a lot of time and effort, and you would still not be sure which radio is really better as the differences are in most cases subtle. E.g. some people reported troubles with gmail sync on standard radio, which were resolved by flashing a different one; at the same time, however, other people live fine with recommended radio and have no gmail problems whatsoever. Get my drift?
Basically, if you're more or less satisfied with your battery life (i.e. it lives at least a day long with moderate to active use), GPS, cell module (no phone dropouts, reasonable signal power), you're good with your current radio. If not, look for a better one.
One more thing: you can flash the radio any time you want, it is not a necessary step for flashing this rom.
<back>
3. Flashing guide
Legend:
[optional]: this step is up to you
[data++]: this step pertains only to a data++ installation, so if you're installing data++, follow it; if you're installing A2SD+, ignore it.
0. [optional] Read this whole FAQ including troubleshooting sections to avoid pitfalls and prepare for eventualities
1. [optional] Make a Titanium backup of apps
2. [optional] Make a Nandroid backup
3. [optional] Copy both backups (titanium and nandroid) to a PC for ultimate safety
4. Have the following files on your SD card in the root folder:
- Lee's ROM
- [optional] radio if you update it from sd
- [optional] any other zips you may want to flash (kitchen and other mods mod)
- [optional] hboot files (Bravo stock and Bravo CM7 r2) if you want to install hboot using the PBIMG way (for unbranded phones)
5. [optional] Flash recommended radio (32.56.00.32U_5.17.05.08), reboot to old rom to check in Settings\About phone\Software Information\Baseband version. If you don't know whether you need to update your radio or not - see section 2.8.
6. Make sure you have an EXT3\EXT4 partition as described in the Requirments section above
7. [data++] Flash Bravo CM7r2 hboot (via PBIMG if your phone is unbranded, or by ADB, or Android flasher, see item 2.3 of this FAQ for links to how-to's)
8. Perform a full wipe if you're coming from another ROM (including LeeDroid 3.0.x). If updating from most prior sub-versions of this rom e.g. 3.3.x, wiping is optional, and you can reflash again with wiping if you have problems.
9. Flash rom.zip
10. Reboot and wait for the ROM to boot, which may take quite some time (up to 10-15-20 minutes is a safe bet; if you worry your battery will run low, nothing keeps you from connecting the charger)
11. If everything is OK, reboot back to recovery and flash optional mods if you have them. Suggest flashing them only after having booted the ROM, and not flashing several mods consecutively, as this may result in bugs.
12. If you have problems flashing the rom \ first-booting, read the following section on troubleshooting.
13. [optional] restore Titanium backup if you have one. Make sure you do not restore any red items. To totally make sure, I suggest restoring only user apps+data, and set up system settings by hand. Do NOT restore contacts if coming from other ROMs (including LeeDroid 3.0.x), but sync them using Google, HTC Sync, and\or other tools.
<back>
4. Troubleshooting ROM installation
4.1. It won't flash the rom!
1. Attempt to flash modified ROM without toggling signature verification to disabled
If you modified your ROM.zip file, you have to toggle signature verification off; e.g in Amon-Ra it's in the menu Other\Toggle Signature Verification.
2. Corrupt ROM file
- You may want to check MD5 signature for the rom file just in case (see link to software to check MD5 code in the Downloads section of this FAQ)
- If you modified the rom.zip - make sure you did it without extracting stuff with consequent recompressing; make sure you haven't deleted anything not meant to be deleted
- If you tried integrating kitchen mods into rom.zip file - try flashing a vanilla rom, this way you'll determine the cause (maybe you modified rom.zip incorrectly, corrupting it)
4.2. I'm stuck on first boot!
Usually, failing to flash\boot the rom has the following causes:
1. Incorrect card partitioning - perhaps number one among other reasons.
To check for it, reboot to recovery (if you can't reboot by key combination, pull the battery). Try mounting sd-ext in recovery.
If it fails, this is indeed a problem.
Solutions:
- delete sd-ext partition in any partition manager such as Gparted \ minitool Partition Wizard and recreate it again, then try reinstalling rom by repeating steps starting with step 10 of the above flashing guide.
- if above fails, repartitioning the whole card (fat32 backup may be necessary if you have needed data on it), then try reinstalling rom by repeating steps starting with step 10 of the above flashing guide.
- if all above fails, ask the gurus such as anderl78 or rom-author, and don't forget to press the THANKS button once they have solved your problem
2. hboot - rom incompatibility, such as:
- flashing data++ rom on a device which is S-ON and\or has stock hboot (Solution: if so, S-OFF your device and flash correct hboot)
- flashing data++ rom with Bravo CM7 r1 hboot (Solution: flash Bravo CM7 r2 hboot)
- flashing a2sd+ rom on Bravo CM7 r2 hboot (Solution: flash stock hboot)
- flashing rom on old hboot (<0.93): may take several tries, though I'd suggest S-OFFing as an easier alternative
3. Corrupt ROM file
- You may want to check MD5 signature for the rom file just in case (see link to software to check MD5 code in the Downloads section of this FAQ)
- If you modified the rom.zip - make sure you did it without extracting stuff with consequent recompressing; make sure you haven't deleted anything not meant to be deleted
- If you tried integrating kitchen mods into rom.zip file - try flashing a vanilla rom, this way you'll determine the cause (maybe you modified rom.zip incorrectly, corrupting it)
4. Unrooted phone
Solution: Learn to RTFM and root your phone
You can read up here: http://forum.xda-developers.com/showthread.php?t=696189
5. Other causes
If your problem does not fall under the above list, ask the gurus such as anderl78 or ROM-author in the MAIN THREAD, and don't forget to press the THANKS button once they have solved your problem
4.4. I downloaded the data version and its flashing now and says now flashing leedroid... a2sd+ ?!?!
The text label was not updated, ignore it.
<back>
5. Troubleshooting other problems
5.1. I'm getting multiple Force Close all the time
If you've used Titanium backup to restore stuff, that's the most likely reason. DO NOT restore system apps and\or their data, do not restore contacts from Titanium.
Solutions:
- Reflash the ROM, and restore only user apps+data OR
- Clear data for the Contacts app and sync contacts using google or third-party backup apps; if you're still getting ".htccontacts" FC's, also clear Mail service data. Thank doggydog for the tip!
Actually, the really bad thing is restoring TB made in previouos version of LeeDroid (e.g TB made under LeeDroid 3.0.x) on the new versions of LeeDroid (e.g. on LeeDroid 3.3.3). I assume that restoring TB made under 3.3.3 on same version 3.3.3 would run flawlessly.
However, even within one fork different versions of the rom may include different versions of some system programs, and restoring old TB backups completely in such cases (i.e. restoring a full TB backup of 3.3.3 on the next build e.g. 3.3.4) might lead to errors and instability.
- The safest thing is to back up and restore only user apps. It is the only way for restoring TB backups from older LeeDroid ROM forks such as LeeDroid 2.5\3.0.x.
Pros: no potential for screwing up your system
Cons: you'll have to manually re-configure any system apps after reflash, you'll have to restore contacts you had via sync \ separate back up e.g. vcard file
- The second best is to restore full TB backup only on the ROM of the same fork (i.e. restoring a 3.3.3 on the next build e.g. 3.3.4), with a nandroid made prior to that.
Pros: if restoring Tb screws up your system, you can restore from nandroid and restore "user apps only", see above
Cons: it takes time and you have to have space for a nandroid backup on your sd card, but hey, what d'ya want? Safety takes effort.
5.2. I'm getting Force Close on Calendar, both widget and the actual app
Wipe dalvik cache in recovery, then go into settings, manage applications and delete again data and cache of the calendar app.
5.3. Weather info on sense keeps disappearing after sleep mode, is there any fix for that?
Go to settings > Applications > Manage applications > All. Find the weather application and "Clear Data".
5.4. Videos distorted if made in portrait orientation
Common problem for HD ports. Not yet resolved.
I've seen people say (not tried myself yet) that playing the portrait video back in any non-Sense player will not show the problem. So most likely it is not the incorrect aspect ratio \ resolution problem, but sense-camcorder-vs-sense-player problem.
Or you could look in the Market for a camera replacement, such as https://market.android.com/details?id=rubberbigpepper.lgCamera
If the aspect ration is still screwed, you could adjust the aspect ratio in you PC player if you're using anything sensible like KMP or VLC or GOM Player. You could even repach the video stream in an MKV via MKVtoolnix, changing AR once and for all, though it gets a bit geeky there.
5.5. Battery life miserable
- Disable HTC Hub (an HTC app to simplify downloading wallpapers and ringtones, read "crapware"): start HTC-hub, menu, settings, disable sync of HTC sense and HTC hub. It should not be working if you haven't registered there, but if not still give it a try.
- If this hasn't helped, look for power-hungry apps you may have installed. Most users are very satisfied with battery performance under this ROM since version 3.3.3 R5.
- If you're using Sense 3.0 pack but can live without it, get rid of it. How? Not sure, but maybe flashing the rom on top might get rid of it - but not sure. I really do wonder though why people don't care to make a nandroid prior to installing Sense 3.0 pack...
5.6. Large apps such as Sygic Aura Drive disappearing after reboot
Result of failed zipaligning.
Solution 1 (preferable): Download and flash patch from this post. See this thread for more info.
Solution 2: If you have Root Explorer or QTADB go to system/etc/init.d and delete 97zipalign or something similar, reboot, reinstall those apps again, and you should be ok.
5.7. ADfree is not working
Solution 1:
Try this patch by anderl78, then start adfree update.
Solution 2:
With R5 there is a symlink in /system/etc
/system/etc/hosts -> /data/etc/hosts
The directory /data/etc did not exist, so no hosts file for adfree to write to.
I just created /data/etc and made a new blank hosts file in it.
adfree was able to update and now seems to be working OK
Solution 3:
Restore Adfree from titanium backup if you have one
Solution 3:
Remove it and install one from the market.
5.8. How to disable CRT TV on-off animations?
Install Spare Parts app from the market, set ANIMATION SPEED to FAST.
5.9. Is it possible to change the shortcuts on the Sense 3.0 lockscreen?
Yes, Customize / Lockscreen / Parameters / shortcuts
5.10. Where can I get the default Ginger2.3 keyboard? Call me crazy but I like it more than the Sense one
At the Market.
Call me crazy, but Swype beats any keyboard hands down, though!
5.11. When using Spare Parts, and I want to check the Battery History I get a force close error, anybody else?
Spare Parts is known to cause this error when running under GB.
To see battery history, you can use other apps, such as "Betterbatterystats".
5.12. Music not loud enough when using headphones.
Serch the market for "Equalizer" which may solve your problem.
5.13. Using Sense Camera app causes screen brightneess to go to 100%
No known fix at the moment, you could try using an alternative camera such as mentioned above in this section; most likely, this should resolve the problem. Otherwise, wait for further ROM updates where this issue would be fixed.
5.14. I've bought a larger SD card, now I don't know how to painlessly upgrade from the old card without loosing the system...
1. Make a nandroid backup of your system in recovery
2. Make the partitions (gparted best but less convenient way, minitool Partition Wizard is a sane alternative) on the new card as described in 2.6 of this FAQ
3. Copy all files from FAT32 partition of the OLD card to the FAT32 partition of the NEW card
4. Put the new card in the phone
5. Boot into recovery
6. Restore the nandroid you have made
5.15. I've switched to this rom from another one, and there's not enough space to restore my apps with Titanium Backup!
The latest builds of this rom have dalvik cached on nand (internal memory) by default for better performance. Dalvik cache grows with the number of apps installed, and thereby limits the number of apps you can install.
If this limit is too small for you, you can flash the dalvik2ext patch from the section "6. Mods and fixes" below, moving dalvik cache to sd-ext and thereby removing any limits to the number of apps installable at the expense of a slight performance degradation.
If your middle name is Thomas and you don't trust anyone and still believe that "App2sd script is not working", take a look at your \system\sd folder (which is actually sd-ext) in any reasonably advance file manager such as Root Explorer, and you'll see if all your apps are really there.
There also are apps like "App2sd" which apparently move your apps to sd (didn't try it so can't say where to exactly, fat32 or sd-ext) in a more complete fashion then the script, but the space savings are still small, so I wouldn't suggest using these apps to anyone. You'll save more by moving dalvik to sd-ext (around 100 mb).
Lastly, having so many apps is just a perverse form of hoarding. I have never seen anybody really needing all that stuff, myself included. I have 160 apps on installed on LeeDroid 3.0.8, and frankly, I can easily part with at least half of that number should the need arise. Just check which apps you haven't used for over three months - and uninstall them. Same goes for apps which you don't remember what they are.
5.16. AC charger is recognized as a USB charger and therefore charges the phone very slowly.
Several people had this problem. For most of them, flashing the latest version of snq's kernel helped.
Alternative solution is also kernel-related - flash Tristan's kernel.
5.17. Messages appear claiming that SU-binary is outdated but you can't update it.
Try this fix.
5.18. Camera app quits suddenly and\or switches screen brightness to maximum.
Try this fix from anderl78.
5.19. Can't get to bootloader...
There are two ways:
1. Power down device completely:
- by holding power button and tapping "power off" in the menu OR
- by pulling the battery and replacing it (less desirable)
Then, hold down VolDown and Power until you get to the bootloader
2. By rebooting to bootloader:
- by holding power button and tapping "restart" in the menu, then choosing "Bootloader" and tapping OK
What may be preventing you from getting there is Fast boot.
Check: Settings\Power\Fast boot should be unchecked.
<back>
6. Mods
6.1. What mods are there?
Mods in the OP of the ROM
- Sense 3.0 pack: parts of Sense 3.0 adapted to Desire. Currently: SMS app, Lockscreen, Notification settings tab, and maybe something else.
- RTL Language support - A2SD++ / Data++
- Enable AdHoc Networking
- Remove Transparency - Both builds (Removes transparent app drawer & pulldown)
Remove FlyIn Animations - A2SD++ / Data++
Mods by anderl78
- Autobrightness patch: Tweaks the autobrightness-settings of the ROM - you can choose between 3 versions; see this post for the version which takes advantage of the latest kernels' "0" light level setting.
- dalvik2ext, dalvik2nand: Moves dalvik-cache to sd-ext or nand
- Disable Key Backlight: disables the backlight oft the hardware keys, good for those who use Desire a lot in darkness, e.g. for reading
- Sense 2.1 Black ClockWidget
- Sense 3.0 Black ClockWidget
- No transparency mod for Sense 3.0 pack
- Trackpad to wake and unlock for Sense 2.1
- Trackpad to wake and unlock for the Sense 3.0
- Notification Pulldown Window MOD - disable recent apps and / or quick settings
- Hardware key remapping mods
- Flashable vdd levels script for latest kernals + explanation (undervolt)
- Rosie (sense launcher) automatic rotation mod (experimental)
- No-Sense patch (removes sense and its widgets)
- AdFree not working fix
- "SU-binary is outdated" fix
- Camera fix (fixed camera app suddenly quitting, display brightness switching to max, jpeg quality)
- Database defrag mod (frees a bit internal memory, speeds up operation a bit, slows down boot a bit)
You can find them in his separate thread: http://forum.xda-developers.com/showthread.php?t=1222351
This post is updated periodically, but there's a chance you'll find anderl's thread more up-to-date.
Do not forget to click the THANKS button on his thread, he's spent a bunch of time and effort to make everyone's life a lot easier!
Mods by himeshladva
- Stock Sense 3.0 lockring courtesy of himeshladva
Mods by punky.mtp
- Dark black lockring (preview) (look for Russe_Ring(Sense3.0-V4-Bravo-AutoExt).zip).
Lots of goodies there, by the way, so look around!
- Ad-hoc patch, HTC Trace keyboard, Wi-Fi n patch can also be found on punky.mtp's site.
Mods by mastersjef
- Disable provider/time/date on Sense3 Lockscreen
6.2. How to flash the Sense 3.0 pack?
- Make sure you have booted at least once after having flashed the rom
- Make sure your Sense 3.0 pack version is correct for your rom - Data++ or A2SD+
- Put Sense 3.0 pack .zip on your sd card, reboot to recovery
- Make a nandroid backup, if you like to be safe - copy it to PC! Lots of people are asking later on "How do I remove Sense 3.0???"...
- Manually mount sd-ext in recovery
- Wipe dalvik cache and cache in recovery
- Flash the Sense 3.0 pack
- Restart
- If you encounter problems, check item 7.1 on this FAQ.
6.3. Is there anything I should know before flashing the mods?
Yes, a few points:
1. Always nandroid prior to flashing mods. Also a good idea to have fresh nandroids and titanium backup copied to you PC just in case.
2. Mods modify various system files:
- some, like Disable key backlight, modify files not usually changed by other mods
- others, like Autobrightness mod, UOT kitchen mods, Notification Pulldown mod, all change system files which are often changed by other mods.
What that means is that it's absolutely of no consequence whether you flash Disable key backlight mod before of after you flash any other mod.
On the other hand, you have to check which files are modified by other mods, because flashing one mod that modifies file "x" and then another one that does the same will remove any effects of all but last mods that change this file.
E.g. if you flash a UOT kitchen mod with your icons over the Autobrightness mod, autobrightness mod will be gone as system files will be replaced by stock ones from the UOT with only the icons (and whatever else changes you made in the kitchen) available.
Conversely, if you have installed a UOT mod, and an Autobrightness mod after it, you will have Autobrightness mod working, but your UOT modification will be gone.
To combine the two, you'll have to first apply the Autobrightness mod (same with any non-UOT mod that changes files changed by UOT), then take the files for the UOT and upload them to the kitchen for modifications. This way the Kitchen will modify files already modded by Autobrightness (in our example), and when you flash the resulting UOT mod it will be actually the UOT+Autobrightness mod combined.
Files modified by mods (not a complete list, you can always check by looking inside the mods's zip file):
- framework-res.apk: modified by Autobrightness mod, UOT kitchen mods
- SystemUi.apk: modified by Notification pulldown mod, UOT kitchen mods
- HtcLockScreen.apk: modified by Trackpad to wake and unlock,
- fusion.apk: Lockring mods (dark ring mod, original sense lockscreen ring mod)
- Idlescreen_base.apk: Lockring mods (dark ring mod, original sense lockscreen ring mod, and obviously mastesrjef's modified Idlescreen_base.apk removing the time, date, and cell provider name from lockscreen).
Another example: if you want to have LeeDroid 3.3.x with Sense 3, a dark ring, Autobrightness, TP2wake&unlock, no recent apps in notification, and custom icons from UOT, the sequence would be:
0. Disable Hardware key brighntess - no matter when you flash it, can as well start with it
1. Autobrightness mod (framework modified)
2. Notification pulldown to disable recent apps (SystemUI modified)
3. Sense 3.0 Pack - not so important when you flash it, but it has to be flashed before the TP2wake&unlock \ Lockring mod
4. TP2wake&unlock for Sense 3.0
5. Now take your framework-res.apk and SystemUI.apk and upload them to the kitchen to cook your own mod. The resulting mod will contain changes from Autobrightness mod and notification pulldown mod along with UOT icons and whatever else you changed there. Flash it.
For another illustration of incompatibility of various mods and solution to that, check out posts 41 to 43 of this FAQ.
6.4. How about themes?
Check out item "8.3. Sense skins and themes" of this FAQ.
<back>
7. Troubleshooting modding problems
7.1. I've flashed Sense 3.0 Pack and it's screwed up!
If you've flashed Sense 3.0 Pack and can't see the difference, or it is not working correctly, then:
- if your sd-ext is ext4, try mounting sd-ext in recovery prior to flashing the add-on
- check if you've flashed the correct version, i.e. there are two different packs for A2SD+ and for Data++ rom versions
- don't forget to wipe dalvik cache and cache prior to flashing the Sense 3 add-on
- some Desire phones have a somewhat smaller system\ partition (PVT4 Desires). They therefore do not have enough space for Sense 3.0 stuff (~4236 Kb). To resolve the problem, manually delete unnecessary files such as wallpapers, books, widgets, apps, that you do not need and are not critical for the system. You can do that either in rom.zip prior to flashing or on the installed rom with Root Explorer or a similar app. First method is much more convenient.
I'd try killing:
LeeDrOiD_HD_V3.3.3_GB-Port-R5-Data.zip\system\etc\slideshow\*.*
LeeDrOiD_HD_V3.3.3_GB-Port-R5-Data.zip\system\customize\resource\[all wallpaper jpegs you don't need, small jpegs are also ok]
If you're on A2SD+, also kill sample books (on Data++ they're on sd-ext, not so on A2SD+ where they remain on system\ taking 2.2 Mb).
LeeDrOiD_HD_V3.3.3_GB-Port-R5-A2SD.zip\system\etc\*.epub
You will have to toggle signature verification to OFF in recovery prior to flashing the modified rom.zip, or it won't flash.
7.2. How to add\remove\change ringtones, alarms and notification sounds?
Prior to flashing ROM, go to the following folders in the zip file:
A2SD+: LeeDrOiD_HD_V3.3.3_GB-Port-R5-A2SD.zip\system\media\audio\
Data++: LeeDrOiD_HD_V3.3.3_GB-Port-R5-Data.zip\sd-ext\media_s\audio\
In respective subfolders, add\remove necessary files. For Data++, they are on sd-ext, so size is not a big concern. In A2SD+, adding about 45 Mb of ringtones will make rom non-flashable as they reside on the system partition, so be moderate
Do not unpack the archive - just do it using del key to delete, mouse to drag-and-drop files into the folders using your archive program sych as WinZip, WinRAR, 7Zip, or Total Commander with an archive-reading plugin.
You will have to toggle signature verification to OFF in recovery prior to flashing the modified rom.zip, or it won't flash.
If you've already flashed, go to the following folder on your device in Root Explorer or similar program:
A2SD+: system\media\audio\
Data++: system\sd\media\audio\
There, use your file manager (should have root access) to add \ delete files in respective folders.
I guess there also exist apps to do this, but if you already have a set of files for notifications, ringtones, and alarms like I do, this way is easier and faster.
7.3. How to remove \ change the bootsound \ bootanimation?
One way is to remove\change it in the rom.zip prior to flashing.
You can find it here, along with bootanimation:
LeeDrOiD_HD_V3.3.3_GB-Port-R5-Data.zip\data\local\android_audio.mp3
Just remove it in the rom.zip prior to flashing or substitute for that of your preference.
You will have to toggle signature verification to OFF in recovery prior to flashing the modified rom.zip, or it won't flash.
If you've already installed, you can use root explorer or similar app to remove\change it, should also be in data\local, I guess - can't say for sure as I've always removed it prior to flashing.
7.4. I've flashed Sense 3.0 pack, and I guess I don't really like it and want to get rid of it - how to?
There are two ways:
1. If you're a pro than you should have a nandroid backup made just prior to flashing Sense 3.0 pack, so you can use it.
2. If you forgot to make the backup or even worse, didn't even think of it - or if you have one, but it took you too long to realise you hate Sense 3.0 stuff and the system's been changed a lot enough for you to dislike the idea of restoring the nandroid, you can flash anderl78's trackpad 2 unlock mod, which will bring back the Sense 3.0 lockscreen (not sure about the other stuff, but it's usually the lockscreen that people find annoying). As a side effect, you will have the trackpad wake\unlock feature.
Update: the weather app will remain Sense 3.0 and will work if you push REfresh button in it, but may not autoupdate and the desktop widget will most likely not function. So a nandroid restore \ rom reflash appears to be optimal if you use the weather app\widget.
<back>
8. Customizing guide
Various mods are not covered here, look for them in the "6. Mods and fixes" Section
8.1. Kitchen customizations
I'll provide more infor here once I have processed it.
To customize your phone by changing the appearance of top bar icons, notification panel, fonts, battery icon and the like you can use the UOT kitchen: http://uot.dakra.lt/kitchen/.
Just cook the file you need as described here http://forum.xda-developers.com/showthread.php?t=990829, then flash it from recovery.
However, there is a number of points to keep in mind while doing that.
1. Always a good thing to make a nandroid backup - it would be a pity if while trying to change a look of an icon or two you screw up a perfectly working setup, right?
2. Customizing stuff in UOT kitchen if you have installed some mods can revert some stuff to original, unless you upload the customized files to be altered by the kitchen manually.
3. Likewise, Installing some mods may revert UOT kitchen customizations to original. The only easy solution is to apply mods first, then upload files to the kitchen and customize them.
A2SD+ customization
In the HD port (unlike the LeeDroid 3.0.x GB), some system apps are moved to "sd-ext/app_s", so customizations made in the UOT may not apply completely.
You will have to modify the script accordingly, as described in his post here.
If he's helped you, give him a THANKS, btw.
Data++ customization
Now if you have installed data++ version, things may be somewhat complicated. This is due to the fact that in the data++ version, some system files are partially on sd-ext:
/system/app goes to /sd-ext/app_s
/system/framework goes to /sd-ext/framework_s
/system/media goes to /sd-ext/media_s
/system/fonts goes to /sd-ext/fonts_s
You can actually check it yourself by opening the rom.zip file.
As the files which are changed by the kitchen mod you have cooked are usually among the ones relocated, the mod has to be a little different from the standard.
There are several ways to do this:
1. When cooking the mod in the kitchen, set the "Kitchen\File Upload\Flashing for Data++ ROM option" to ON.
This worked for most users.
2. [OR] edit cooked file manually, replacing file paths as described below:
Open the theme's zip file (e.g. one from UOT) and edit \META-INF\com\google\android\updater-script file, changing paths of files that had been moved to sd-ext in the data++ rom. After that you can flash it from recovery as usual, having toggled signature verification to Disbled.
For instance:
Original script (for LeeDroid 3.0.6, could be different with 3.x.x data++, but enought to get the picture, and you can always figure out the paths and which of them to alter from the UOT mod.zip and rom.zip) was like this:
ui_print("Applying UOT framework");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("framework", "/system/framework");
package_extract_dir("app", "/system/app");
run_program("/sbin/busybox", "umount", "/system");
With the data++ version of 3.0.6 I used the following lines (could ALSO be different with 3.x.x data++):
ui_print("Applying UOT framework");
run_program("/sbin/busybox", "mount", "/sd-ext");
package_extract_dir("framework", "/sd-ext/framework_s");
package_extract_dir("app", "/sd-ext/app_s");
run_program("/sbin/busybox", "umount", "/sd-ext");
So it's the "spot 10 differences" game. Just check the data++ rom.zip for files moved to sd-ext, then check what files are changed in the theme\mod zip, and alter the update script accordingly. Remember not to extract files and recompress them, but rather to open the archive and edit the script from the archive.
Furthermore, the kitchen has the DATA++ option somewhere, and it should work - you can give it a try.
3. [OR] integrate the cooked file into rom.zip. To do this:
1) Browse through your cooked mod and see what modded files are in there. Usually its SystemUI.apk and framework-res.apk.
2) Extract these files to any folder.
3) Now open you rom.zip using WinRAR, 7ZIP, Total Commander with an archive-browsing plugin or any other decent software.
4) Locate the files you found in (1) and replace them by dragging the files extracted in (2) over them. E.g.:
You have extracted from the kitchen mod.zip:
framework-res.apk from the app\ folder
SystemUI.apk from the framework\ folder
to some temporary folder on your pc.
In data++ rom.zip, you'll most likely find
framework-res.apk in rom.zip\sd-ext\framework_s\
SystemUI.apk in rom.zip\sd-ext\app_s\
So, for each instance, you drag the respective file from temporary folder to the archive, and confirm if the program you're using asks if you want to replace the files. In any case, ignore the META-INF\ folder.
The resulting modified rom.zip should be flashed with Signature Verification toggled to Disabled in recovery, as we have modified it.
Troubleshooting
Check if you have selected the right source files in the kitchen. In the UOT kitchen, on the FILE UPLOAD tab, under the heading "Select your rom from kitchen's list, or upload your own files", make sure you use "Kitchen's list", and select "LeeDrOiD HD 3.3.3 R5 Desire ROM" from the dropdown, or whatever version is closer to yours. Alternatively, you can upload the actual files from the rom.zip.
If it still isn't working, then, most likely, you have incorrectly followed the above guide. With all due respect, go to the main thread and bug people there - they will be very amused by yet another repetition of the "how do I flash the UOT kitchen mod on data++" topic... but will help you anyhow, as they are indeed nearly saints.
8.2 Adding notification panel widgets
The question of how to add widgets into the notification panel seems to appear every now and then in the main thread. There are many ways to do that. However, not all of them are easy\are easily customizable as the way I am describing below.
I solved it for myself by using the free Widgetsoid app.
It allows to make any number of highly customizable widgets, and can also place any of them in the notification bar.
The way to setup is first:
1. Install widgetsoid
2. Run it from the apps menu for initial settings:
ADVANCED tab:
- Flash led setting is METHOD 2
- Select desirable Brightness levels if you're going to use it (suggest using Seekbar first to get the hang of which levels are good for you, then using custom levels to set them up)
- I'd suggest setting "Widget focusable" to OFF, haptic feedback to ON
- Service in backgroud ON
NOTIFICATION tab:
- Hide notification icon to ON
- Open popup to OFF
Other settings you can change to your taste.
Then, to create your widget:
- Create a widget on your desktop, i usually use Widgetsoid Switcher 4x1 widget
- On network, Screen, Sound, Other, Shortcut tabs -- select which widgets are needed
- by clicking on a specific widget item in the preview you can move it to any place you want
- Go to theme tab, set it up to look as you want
- go to advanced tab, suggest following settings:
-- Modifiable - YES, you can turn it off later after you're sure you got what you wanted
-- Modifiable icon - up to you, I set it to off. What it does is show a small icon in top right corener which you can click to bring up widget editing screen; it works the same way without the icon, so it looks cleaner. It affects only the widgets placed on desktop, it won't be visible\usable in the notification panel widget
-- Notification - ON if you want to see the widget in the notification bar - so you want it ON
-- Widget invisible - as you want. If you check it, widget won't take place on your desktop, it'll only be visible in Notifications panel. Can't undo that later, so decide on the spot. You can always make another widget, though, if you later want to have one on the desktop and had made the previous one invisible.
-- Click Apply tab
It will ask you if you want to edit global prefs - no need to do that, so answer NO. The widget should appear in notification panel.
Some notes things:
- depending on notification panel style (transparent\white\other) you may want to change the color of your widget's icons so they are clearly visible (Widgetsoid app\Notification tab\Choose icon color). In transparent panel of 3.0.6-r2 it doesn't seem to work; as I remember, it worked with a white panel.
- In some cases, you may get a popup with the widget after you tap a widget item in notification panel after initial setup. If that happens, got to widgetsoid app, go to Notification tab, check state of "Open Popup" checkbox. If ON, set to off. If OFF but you still get the popup, check it to ON, then set it back to OFF, this solves the issue. It appears, you'll have to do that each time you add a widget to notification panel.
- If you made your widget visible only in notification panel and want to edit it, you can go to Widgetsoid app, go to Widgets tab, select widget you want to edit, tap the pencil button, edit as needed, tap apply tab.
- If you choose the widget to be Invisible on your dektop when you set it up initially, there is no way to uncheck this option if later you change your mind and want to see it on you dektop as well as in the notification panel. The only way you can do that is by recreating the widget.
- You can put more than one widget panel in the notification panel.
- If you use task killers (why would you want to?), make sure widgetsoid service is on the exceptions list.
VOILA, LeeDroid GB3.x.x with a notification tab switches in an easily customizable way!
PS you can watch it, if I am not mistaken, starting with 14:00 of the official widgetsoid video guide.
8.3. Sense skins and themes
See this post for a link to an XDA thread dedicated to skins and themes for Sense 2.1 (and yes, it should be 2.1 since Sense 3.0 is not Sense 3.0 per se but only bits and pieces of it).
Can't give any how-tos here as have no experience in skinning\themeing sense and no desire to acquire such.
If anybody can't figure stuff out, ask in relevant threads (and send me a link to answers that worked so I can post them here). Same goes for people who know how-to - PM me and I'll add your walkthroughs to this FAQ.
<back>
9. Downloads
ROM links
ROM itself: see the this post
Recommended radio 32.56.00.32U_5.17.05.08, MD5 03cd7972412bec4b4ed6f2699e4c9af0
S-OFF links
Site: http://alpharev.nl/
Live-CD used to S-OFF, MD5 3ca4c4803fe1eb309c980420788ad3f
Feel free to donate to Alpharev using the "Donate" button on their site!
HBOOT links
Site: http://alpharev.nl/
Bravo CM7 r2 on Alpharev's site:
- fastboot flashing, MD5 0be8c68b41f3ab6dda4f772d6de50760
- PB99IMG flashing
Stock hboot:
- fastboot flashing, MD5 7bd5234711364880de1fa982dcf3a2d6
- PB99IMG flashing
Tools
Software to check MD5
GPARTED - linux software for partitioning, also can be run on any PC using a boot-cd, site: http://gparted.sourceforge.net/livecd.php
MiniTool Partition Wizard - freeware windows partitioning program, site: http://www.partitionwizard.com/download.html
Mods
For mod download links see section "6. Mods and fixes"
<back>
_____
DISCLAIMER: whatever you do, you do on your own initiative and the results of your actions are your responsibility.
Rhethoric question: why in the world are there no <SPOILER> tags on this forum?
Wow! Your FAQ-thread's are nearly unbelievable! Respect!
Sent from my HTC Desire using XDA App
anderl78 said:
Wow! Your FAQ-thread's are nearly unbelievable! Respect!
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
It's been easier since I could build on the 3.0.x FAQ.
Hope not too many mistakes\omissions here, please correct if you see any!
Also propose adding a link to this FAQ to your mod-list instead of the old faq link, as it has superceded it.
s300pmu1 said:
It's been easier since I could build on the 3.0.x FAQ.
Hope not too many mistakes\omissions here, please correct if you see any!
Also propose adding a link to this FAQ to your mod-list instead of the old faq link, as it has superceded it.
Click to expand...
Click to collapse
Hello!
as written, really good work! Added your FAQ in the addon-thread and in my signature ;-)
Woooo, really nice work, i love this faq
added in my signature too
thank you
Added your FAQ in the addon-thread and in my signature
Click to expand...
Click to collapse
added in my signature too
Click to expand...
Click to collapse
1. Fiat lux!
2. Manus manum lavat
Hi,
first off all you have made a very good FAQ. But I still have one question.
Do I need to S-OFF my Desire, because the phone says in the bootloader menu that I allready have H-Boot 0.93.0001?
I want to install the A2SD++ Version. Will it work without S-Off my Phone?
My Desire is PVT4, rooted, AmonRa v2.0.1 Recovery, 16GB CAT4 SD Card with a 2GB EXT4 Partition.
Thank you for your help.
Best Regards
Volker
===Volker=== said:
Hi,
first off all you have made a very good FAQ. But I still have one question.
Do I need to S-OFF my Desire, because the phone says in the bootloader menu that I allready have H-Boot 0.93.0001?
I want to install the A2SD++ Version. Will it work without S-Off my Phone?
My Desire is PVT4, rooted, AmonRa v2.0.1 Recovery, 16GB CAT4 SD Card with a 2GB EXT4 Partition.
Thank you for your help.
Best Regards
Volker
Click to expand...
Click to collapse
Hello! S-off is not required for the a2sd+ Rom.
Sent from my HTC Desire using XDA App
Hi,
first of all congratulations for this great FAQ.
But please add the following finding:
I have tried to apply an UOT mod to my A2SD+ version (see my sig).
But it doesn't apply completely.
The reason is (mainly known from the DATA++ version) the target for the 'app' modifications. In the A2SD+ version it is the same as in the DATA++ version 'sd-ext/app_s'.
So I modified the well known original UOT-script to the following
Code:
ui_print("Applying UOT framework");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("framework", "/system/framework");
run_program("/sbin/busybox", "umount", "/system");
run_program("/sbin/busybox", "mount", "/sd-ext");
package_extract_dir("app", "/sd-ext/app_s");
run_program("/sbin/busybox", "umount", "/sd-ext");
ui_print("Applying UOT bootanimation");
run_program("/sbin/busybox", "mount", "/data");
package_extract_dir("data", "/data");
run_program("/sbin/busybox", "umount", "/data");
And then flashed the UOT-mod successfully.
Cheers
Dirk
Hi,
I flashed the rom yesterday and it works perfect. One little thing I noticed.
I had to flash the "Move Dalvik to Sd.zip" file before the first boot otherwise the phone got stuck on the bootscreen.
I thought the dalvik cache get moved automaticly during the install of the rom?
===Volker=== said:
Hi,
I flashed the rom yesterday and it works perfect. One little thing I noticed.
I had to flash the "Move Dalvik to Sd.zip" file before the first boot otherwise the phone got stuck on the bootscreen.
I thought the dalvik cache get moved automaticly during the install of the rom?
Click to expand...
Click to collapse
What rom version have you flashed? Data++?
In Data++ dalvik is on nand by default, don't know about A2SD+.
If you're on Data++ but haven't flashed CM7 r2 hboot prior to flashing the rom and are therefore on stock hboot, you may not have enought internal memory for dalvik-cache to form and hence bootloop.
RSVP.
So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
If you plan to do this available to any android device, the file size will be so big that it will become useless. Every phone has different apk, and not only that, but those apk are different in different version of os. For example, CM9 framework should not work on google release. Worst, older CM9 framework might not work on newer CM9 and newer framework might not work on older. Also, one of the cause of bootloop that i have been experiencing since i have my GNexus is data corruption of apps. The only way i had was to wipe data. I dont think there is a way to know if your app are corrupted with script. I also seen a lot of strange problem on SGS II like the kernel being erased. Well, in this case this package would be useless. So i guess that having this package would be awesome, but wont happen. My best advice is that you could create a universal guide on how to recover from bootloop/fc/hang with the minimum of impact on the phone. This is just my opinion tho.
Sent from my Galaxy Nexus using xda premium
You could add using flags in the updates filename, see some roms or themes for the lg optimus 2x for more information. It uses sed. For example, "update-wc-wd.zip" would wipe /data and /cache.
You could also merge these features in a customized clockwork mod recovery, the up side would be that you could automatically make a backup of the last flashed full ROM's systemui etc. this would also allow usage of the touch screen/volume keys to choose an repair option. You could even allow users to backup specific applications along with their data, and let users restore it later on after a fresh flash. I have some basic knowledge in modifying the recovery so I might help you out a little if you're interested.
chadouming said:
If you plan to do this available to any android device, the file size will be so big that it will become useless. Every phone has different apk, and not only that, but those apk are different in different version of os. For example, CM9 framework should not work on google release. Worst, older CM9 framework might not work on newer CM9 and newer framework might not work on older. Also, one of the cause of bootloop that i have been experiencing since i have my GNexus is data corruption of apps. The only way i had was to wipe data. I dont think there is a way to know if your app are corrupted with script. I also seen a lot of strange problem on SGS II like the kernel being erased. Well, in this case this package would be useless. So i guess that having this package would be awesome, but wont happen. My best advice is that you could create a universal guide on how to recover from bootloop/fc/hang with the minimum of impact on the phone. This is just my opinion tho.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I told it already, the "custom" folder is not filled. It will be kept empty. The user can put a file, which ofcourse is the file of the device he/she have or want to get repaired. All he has to do is copy and paste the file from the working zip( zip file of his currently installed rom, that encounter the problem) of his rom to the custom folder inside the rescue.zip.
And the things that are common will be scripts, but those too will contains device specific mound points, paths, etc. I think that will be common( ie, the working of script, once the mound is done). Am i right?
So all i have to figure out is mount points, paths etc.. i got a couple of them, about 15 or so. And pls help me to find the rest.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
a good idea to add is a file system chech like windows systems has. By installing a rom the installer should first check for bad sectors and mem blocks before installing the rom. After all blocks and sectors are scanned and the bad ones marked as "bad or corrupt" it should run something like defrag and place the bad blocks at the end of the file table. When all is done .. then the true rom install should start.
This will prevent heaps of problems since the curent installs just write over a bad block or sector creating the most weird problems. A fault checker/repair will take away a lot of strange forced closes and othere software/hardware failures.
Most phones wont last that long so that bad blocks or sectors can occure. But for the flashing junkies among us its a serious problem what can occure. I guess after 1000 or more installs bad sectors or blocks will occure and not all are being able to be repaired
Sent from my Galaxy Nexus using XDA App
Mikevhl said:
You could add using flags in the updates filename, see some roms or themes for the lg optimus 2x for more information. It uses sed. For example, "update-wc-wd.zip" would wipe /data and /cache.
You could also merge these features in a customized clockwork mod recovery, the up side would be that you could automatically make a backup of the last flashed full ROM's systemui etc. this would also allow usage of the touch screen/volume keys to choose an repair option. You could even allow users to backup specific applications along with their data, and let users restore it later on after a fresh flash. I have some basic knowledge in modifying the recovery so I might help you out a little if you're interested.
Click to expand...
Click to collapse
I am totaly newbee to lg. I have experience with htc, few samsung, etc. So can u pm me the details? Also is it usable to create recovery? I think a zip file with selectable options is more friendly. The thing is building a recovery wont make it universal( or atleast common for a couple of devices) and we will have to port them for each and every device. Thats the problem.
But any way i want ur help in building it. Can u pm me an example for mounding script in lg devices? And any thing that may become useful. Thank you.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
wilwilwel said:
a good idea to add is a file system chech like windows systems has. By installing a rom the installer should first check for bad sectors and mem blocks before installing the rom. After all blocks and sectors are scanned and the bad ones marked as "bad or corrupt" it should run something like defrag and place the bad blocks at the end of the file table. When all is done .. then the true rom install should start.
This will prevent heaps of problems since the curent installs just write over a bad block or sector creating the most weird problems. A fault checker/repair will take away a lot of strange forced closes and othere software/hardware failures.
Most phones wont last that long so that bad blocks or sectors can occure. But for the flashing junkies among us its a serious problem what can occure. I guess after 1000 or more installs bad sectors or blocks will occure and not all are being able to be repaired
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Pls pm me the idea how to make the checking script. Or links that have info in this. Thank u in figuring out such a prob. I am unaware of that.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
showlyshah said:
I am totaly newbee to lg. I have experience with htc, few samsung, etc. So can u pm me the details? Also is it usable to create recovery? I think a zip file with selectable options is more friendly. The thing is building a recovery wont make it universal( or atleast common for a couple of devices) and we will have to port them for each and every device. Thats the problem.
But any way i want ur help in building it. Can u pm me an example for mounding script in lg devices? And any thing that may become useful. Thank you.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
Click to expand...
Click to collapse
I'll send this as a PM as well, but people might learn from this. I am not talking about any specific mount points for LG phones, I just pointed out that there are some roms which use sed to check the filename of its update.zip and do tasks according to that, you need to have one line in your updater script to run the script which detects what to do. That way a user of a Galaxy Nexus would rename it to update-maguro.zip and it would know to use mount points for the maguro, while if the exact same update.zip was to be named update-p990.zip, it would know to use the mount points for the LG optimus 2x. This way you could easily keep the zip up to date for any device, because they all use the same update.zip
About the recovery, you would need to build it for every phone once, but you could make one change to the recovery source and easily compile the recovery for all phones which are capable of running CWM. I believe this method to be more user friendly, as a recovery image has support for actually choosing what you want to do, instead of having to rename the file. A recovery image also has a better way of communicating with the user. Where a update.zip can only say "Hey, I had an error and I'm quitting now, I won't give you any details what the problem was because that's just how update.zips roll", a recovery image would be able to give more advanced outputs, like "An error occurred when trying to mount /data." And then give you the option to either try again, manually fix it by using a computer with adb, or quitting.
But that's just my personal opinion. The recovery would be way harder to make, but I was the original porter of CM6, CM7 and HTC Sense to the xperia mini pro and mini back in the days. I also made a custom recovery and roms for the HTC desire Z, maintain a CWM port for the HTC Chacha which I don't even own and have used the LG optimus 2x before. (currently a maguro owner) but I'm trying to say that I've been experimenting a lot with different phones and know what the possibilities of Android are. you could even make a live Android build, tailored for recovering your phone, which is ran by an update.zip! How cool is that? That would be VERY device specific though..
let me know what you think is the best way to do this. I was thinking of making a mobile time machine app for some time so it's good I saw this thread.