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.
Related
Hey all,
Wanted to post CM7 here for everyone to enjoy.
Neopeek has been working hard to get this build up and running, he's been doing great work!
Neopeek's Original Post - if you wish to see Neopeek's original post about the CM7 topic.
Also, since now I am using his new ClockWordMod method - CWM Recovery thread
As is stated in the title, this is mainly for devs/testers. Lots of things are broken, and there will be frequent updates.
There are two methods to using this build:
1) ClockWorkMod (requires 3 separate ext2 partitions)
2) Loop'd system.ext2 image (like XDAndroid) [In progress]
The benefit of #1 is a dedicated system/data partition, and *partial* USB mass storage support.
The benefit of #2 is, it's easier .
I still have to work to get #2 up, but I wanted to post #1 ASAP. Lots of work to flesh out the post to, be patient!
I've been holding off on releasing this CWM version of CM7, because I'm still having a lot of bugs with it. Still needs quite a bit of work, but it's getting late for me tonight - I am going to release it, let me know if you guys make improvements, I'd love to incorporate them!
Main issues seem to be related to my durn CDMA device. Need to break into some logs to see what's goin on, it may be a little while! I think GSM folk will be fine. Let me know!
Downloads
Download #1
How-to
Method #1 (ClockWorkMod)
****WARNING****
If you setup dedicated partitions using this method, normal XDAndroid builds will think that you want to use dedicated partitions. I had to modify the init to get it to work correctly (I basically broke the partition detection in the init). It's not pretty, but I don't know of a better way to resolve that issue - let me know what ideas you guys have!
Setup:
You will need to create three (3) ext2 partitions on your SD card. This is not extremely simple, but by no means impossible .
If you're using Windows, I like the Mini Partition Tool. If you're in Linux, I usually use gparted.
This takes a little bit of planning - but in total, I would say you need a minimum of 450mb of space for all three ext2 partitions. So work out how much free space is left (if you want a bigger data partiton, or system partition account for it!) and make that the first partition - FAT32. Make sure all the partitions are "primary", not "logical"! See the partition layout below:
1 - FAT32 Primary (remainder of card)
2 - ext2 Primary (at least 150mb, system partition)
3 - ext2 Primary (at least 250mb, data partition - I wouldn't go over 1gb here)
4 - ext2 Primary (at least 50mb, cache partition)
Don't worry about putting anything in these ext2 partitions, everything is populated by Android and CWM. The FAT32 partition is used to kick off Android, while system, data and cache are all ext2 partitions. Reason for this is, hopefully if things go haywire we can blast out cache, not data . Also, it should be easier to update using this method than previously.
Extract the file. Look at the folder it created (npkboot). Copy the entire npkboot folder to the root of your SD (for now this is required - the init assumes there's a /sdcard/npkboot/tmp folder). There will also be an update.zip, in this case update-cm-7.0.0-neopeek.zip. Put this at the root of your SD card (this makes finding it in the menu much easier!)
Copy the appropriate startup.txt from the STARTUPS folder.
Find haret.exe in th npkboot folder. Run it, and watch the boot process carefully! It will ask you to hold the vol down button to enter recovery, and you have 10 seconds to do so.
Assuming you manage to do this correctly (I had some trouble at first ) you should see an icon like a hat. Wait for the menu.
Buttons:
End key - back (back button seems to do this as well...)
Send key - enter
Vol up - up
Vol down - down (menu button seems to do this as well...)
If this is the first install, go to "install zip from sdcard". Then "choose zip from sdcard" This will install the system image to the system partition from the update.zip.
If you need to wipe the data partition, you can do that under "mounts and storage". You shouldn't need to do this unless you're going from gb -> froyo or visa-versa. Froyo -> froyo should 'just work', as always YMMV.
There are A LOT of options in replimenu. The only ones I have used are install, format /data, /system or /cache and Reboot. According to Neopeek, there are several things that should not be used:
Neopeek said:
* Don't use "factory wipe" in CWM (you have been warned )
* Don't use "format sdcard" unless you know what you do (you have been warned )
* Don't use "partition sdcard" unless you know what you do (you have been warned )
Click to expand...
Click to collapse
Once you've installed Android, go back to the main menu and "reboot system now" There are some bugs, for example "reboot recovery" and "power off" all just reboot the phone to WinMo.
Boot haret again, but this time don't hold the vol down to enter recovery - boot as normal!
#2: Much simpler method, similar to XDAndroid builds.
Extract the file to your desktop. Go into the CM7 folder, look for the STARTUPS folder - grab the appropriate startup.txt, move it to where haret.exe is.
Copy everything in the CM7 folder to the root of your SD card - if you want to run it from a folder, create a rel_path=CM7 statement in your startup.txt after the set cmdline (if you want a different folder, change the CM7.)
Grab the ts-calibration file attached to this post (for RHOD), or go to this post for a list of ts-calib's. You can also create your own on boot, but may have to revert to an older kernel to do so.
Run haret.exe!
****Not Working****
CDMA seems broken - still! I did some testing with hyc's RIL and it's still busted, so there's something in the system image messing with it - Airplane mode was checked, and I could not uncheck it.
In addition, phone.apk seems like a forceclosefest. Neopeek did point this out in his original thread...
Mobile data - broken (Fixed soon)
Wifi - broken (Fixed soon)
System needs optimization for RHOD - was originally build with DIAM in mind - so it's a little slow.
Failed wakes seem pretty bad - sometimes it is quite difficult to wake the phone.
Boot animation seems to be not present - I'm looking into fixing it, probably graphics libs if anything that's broke it.
Dev Content
This new method should be great for anyone who wants to make their own updates - you can easily peek into the system image and make changes at will, then just install the new system image! You can even rolll updates instead of an entire system image if you wish.
The script language in ClockWorkMod is called "Edify", see this thread to learn about the syntax. This is related to the META-INF folder you see in the update zip.
There's a few differences in the rootfs', the main being the init. There's also some additional files it looks like neopeek added for Recovery specifically.
This is amazing work. Props to all involved.
Does anyone have any feedback on this build?
arrrghhh said:
Long story short, you need a ext2 partition and a fat32 partition - ext2 needs to be between 400-600mb, fat32 can just take the remainder of the card's space.
Click to expand...
Click to collapse
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
PM message
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Sorry, I need access to a Linux box to do the 'easy' build... I will when I get home tonight from work, promise .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
You can make it as big as you want I guess... I'm not sure how neopeek sets up the data partition to be honest, I'd have to ask him.
Edit - in lieu of the post below, I adjusted the first post to say it needs to be at least 400mb .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
I have 700 mb and is working well,you can use as much as you want
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
I wonder if CDMA data is working with this...that is my biggest issue with GB right now...
HELICOPTER88 said:
I have 700 mb and is working well,you can use as much as you want
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
Click to expand...
Click to collapse
yeah easy for you to say, that sounds complicated.
I will wait for the other one.
Do you know the ETA?
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
Still need to upload, sorry!
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
I was looking at that too when extracted the files and didn't see what you are also missing.
Sorry about the confusion guys, I probably shouldn't have put the download link up before I was done .
I just fixed it, so #1 is good to go! I'll get #2 up later, thanks.
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
(...solved...)
it's necessary create a swap partition?
What works in this build?
fishingmedic said:
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
Click to expand...
Click to collapse
The rootfs is more or less collapsed in these.
Kernels are straight from XDAndroid repo.
OC is the same, startup.txt is fairly similar .
Quincux said:
it's necessary create a swap partition?
What works in this build?
Click to expand...
Click to collapse
Swap is not necessary.
Most things that work in XDAndroid work in here. Lots of other things are broken here tho .
Okay, downloaded and installed without problems.
First impressions:
Absolutely great build in terms of response!
No delays in menus, etc.
Also, this looks like the first build that may have little or no clock delay, so no need for clocksync !!! (to be confirmed since I did not use it very long, die to issues below)
However...
1) No WIFI
2) No Mobile data (2G/3G)
3) camera not working (could be just blackstone)
- maybe other issues, decided to wait for more feedback before continuing, without market access there's little point...
Device: Blackstone
Kernel: extensive testing with provided one (1276), later switched to 1277, to fix audiostuttering, no wifi or mobile data in either...
As a reference, used many NeoPeek / XDAndroid builds, generally got WIFI/Mobile data working until now...
Love to hear if someone else (blackstone?) got WIFI/2G/3G working...
Oh, well, as I understood, this was an early "developer" release, still plenty of room for improvements!
Cheers,
Robbert
This is a summary of most useful and repeated info in main thread about ROM LeeDrOiD V3.0.x GB | Android 2.3.3.
Updated until April 23.
I've been reading most of the "ROM LeeDrOiD V3.0.x GB | Android 2.3.3" main thread , but have not installed it myself. Not in a beta testing mood. So decided to help instead by compiling what seems to be a FAQ, derived from that thread - so that the main thread needn't be polluted by always the same questions.
This is not meant to be complete. If an answer isn't clear enough, it's because more info is out there, either on Google, XDA or e.g. on http://leedroid.com/bravo-wiki/
All credit goes to Leedroid, and the experts answering on the main thread. I'm just compiling info - hopefully to slow down the rate of always-the-same posts in the main thread.
NOTE: do not use this thread to ask new questions. Only to debate the correctness of the FAQ.
* if you report a problem/success, make sure to mention your version of: HBOOT, recovery, S-OFF/ON, PVT (1-4) (if PVT4 also erasesize), did you wipe before flash, what was your previous ROM, etc, ...
* best way to install LeeDroid 3.x A2SD+ ROM:
- optionally backup all your apps with data (e.g. Titanium)
- optionally backup all your contacts, sms, apn's, etc (whatever is not saved in the cloud) - various apps out there.
- optionally nandroid backup (recommended for an easy way back if it fails)
- make sure to have HBOOT 0.93x
- flash new recommended radio (32.56.00.32U_5.17.05.08), reboot to previous rom. Check radio version in Setting / About Phone
- set up your SD card with a (1st) primary partition FAT-32 and (2nd) primary EXT partition (512MB-2GB)
- from recovery: wipe all partitions (data, app, cache, dalvik) (except if coming from earlier Leedroid 3.x)
- flash the "Convert sdext to EXT3" zip (unless you know exactly why you don't want to - e.g. if you want to keep EXT4).
- flash the LeeDroid ROM
- reboot, wait, could take 5-20 minutes
- enjoy.
* ROM is only partially multi-lingual (system language). (is based on a leaked test ROM directly from HTC, many languages incomplete. Can't be fixed)
http://forum.xda-developers.com/showpost.php?p=12968676&postcount=341
* IMPORTANT: so far, nobody with HBOOT 0.75 or 0.80 has reported success. It always hangs on boot. Solution: get HBOOT 0.93x.
Option 1) flash latest RUU (you will need to re-root also then). E.g. http://forum.xda-developers.com/showpost.php?p=13056537&postcount=1457
Option 2) Get it via AlphaRev S-OFF
* If you are S-OFF (alpharev.nl), make sure to have the default "stock" partition table sizes (Bravo Stock 250M/40M/147M).
* partitions of your SD card: (1st) primary partition FAT-32 and (2nd) primary EXT partition (the EXT partition should be 512MB-2GB; for most users, 512MB-1GB is plenty enough). Experts highly recommend Gparted (use align to MiB option; this is a Linux application, but easily used from a boot CD/USB for Windows users). (You may want to research this issue if you're new to it, is out of scope for this FAQ). Esp. if you didn't use Gparted, it's highly recommended to use the "Convert sdext to EXT3" zip -> will align the partition for faster read/writes.
* many people reporting ROM failing to boot/flash, fixed it by running the "Convert sdext to EXT3" zip. This will align & format in your EXT partition.
* Which recoveries work? So far, no special comments. CWM 2.5.x or AmonRa 2.0.0/2.0.1 seems ok. For some, flashing with recovery CMW 3.0.0.5 leads to boot hang, but others say it works.
* Several programs force close (e.g. angry birds ) when run from SD. Fix: move app to phone (Settings / Application Manager). Note that on an A2SD+ ROM, having the "app on phone" really means that app is on the EXT of the SD, so that's exactly what you want! ("App on SD card" as used in the Settings / Application Manager is an inferior method of saving data space)
* Gingerbread - Handcent: no LED. Known problem. Works with Green LED, not with Blue LED (in Handcent settings). Some say this can also be worked around with GO SMS and/or Led me know - search main thread for more.
http://forum.xda-developers.com/showthread.php?p=13000559#post13000559
* Menu (button) to wake is problematic. This feature was added in LeeDroid 3.0.2. Only works for a short time after the screen lock. Lee's working on it.
* for some apps, restoring from Titanium *INCLUDING app's data* will lead to app FC. if so, delete app's data via Settings/Applications
* Adobe Flash Player / iplayer (BBC UK) problems? Redownload Flash Player from Market. Some say "it worked but only until the next boot!"
http://forum.xda-developers.com/showthread.php?p=12986992#post12986992
http://forum.xda-developers.com/showpost.php?p=12986547&postcount=752
http://forum.xda-developers.com/showthread.php?p=13005362#post13005362
http://forum.xda-developers.com/showthread.php?p=13005263#post13005263
* Some people had problem until they wiped (write zeroes) the EXT partition from Partition Wizard, and reformatted (no need to touch the FAT32). Probably easier fixed with the EXT3 zip.
http://forum.xda-developers.com/showthread.php?p=13003478#post13003478
* Some say "Swype needs to be switched on after every reboot"
* (sibere/droidzone's) Data2SD flashable zips DO NOT work on LeeDroid 3.
* EXT4 does not work with the leaked ROM (HTC). EXT4 support was added in LeeDroid 3.0.2. However, many have said that EXT4 is readable but can still not be used as A2SD partition with 3.0.2..
3.0.3 should bring improved EXT4 support - waiting for user reports!
* Compass is broken (doesn't point in right direction). (one user report that it works with older Radio)
* Visually it's almost identical to Froyo Sense, because it's still the same Sense version (some say 1.9) from Desire stock Froyo (with a few feature (text copying?) as in Desire HD Sense). Supposedly the Gingerbread improvements are under the hood (better memory management, speed, battery). Nobody knows whether future real/leaked ROMs from HTC will include a later Sense version (as in Desire HD or S)
* Gingerbread contains new feature "fast boot" which resembles hibernate... if enabled, you can't go into recovery on boot with the usual key presses...
(1) Try Settings > Applications > Turn off Fast Boot. (2) Or use ROM manager's (included with LeeDroid 3.x) "reboot to recovery" feature. (3) Or use Restart and hit vol- the moment screen goes black.
* Data++ can be made to work... but requires editing ROM before flashing. See main thread post by anderl78*
* Do I need to wipe? Some users say it works without (when coming from Leedroid 2.4) - if you feel adventurous, try yourself, but if problem, go back and wipe. (and report). This depends on how "different" your current ROM is.
Specific to 3.0.3
- see changelog on 1st post in main thread.
- No wipe required from 3.0.2
- No locale modifications yet, we will need a new WWE build from HTC
- no change on the menu/trackpad to wake...
- Many report that upgrade/uninstall of app via Market leads to soft reset. (but that install of new apps works). ==> update: there's a specific patch for that in main thread OP.
- compass still pointing in the wrong direction
good overview,well done mate!
i seem to be one of the few lucky individuals who was able to flash 3.0.2 without any problems whatsoever
Nice piece of work, thanks for that!
Could you add one other point? You DONOT need to disable fastboot to get back to recovery. ROMANAGER is pre installed, just open it up and select boot to recovery.
really useful thread mate!
Not sure if this is just mine or not, but when downloading apps from Market, it says "starting download" throughout the whole time it is downloading it whereas it used to show the progress of it..
Well done mate. Worth mentioning that reinstall flash works only until reboot on s-on phones,as you need to be s-off to edit system folder.
Reboot to recovery, either use Rom manager or normal restart and as soon as all light go out just hold -vol button.
Market downloads but doesn't do anything else-SOLUTION: clear market data/cashe
Sent from my HTC Desire using XDA App
Success
100% working, no fc's or problems flashing ROM (small problem with wake from menu/trackball commonly reported). Flashed newest radio before flashing ROM, came from LeeDroid 2.4
Read some people with old HBoot are going back to newest stock RUU to get 0.93, making life a little easier by starting from square one and then going through the procedure of root and s-off.
SD formatted Ext3 using GParted (it's a great tool)
Excellent thread, lots of waste of space questions in the main thread!
AmonRa 2.0.1 | PVT4 40000 S-Off | HBoot 0.93.1000 | Radio 5.17.05.08 | LeeDroid 3.0.2 (A2SD) | HTC Desire A8181
Siresmokalot said:
good overview,well done mate!
i seem to be one of the few lucky individuals who was able to flash 3.0.2 without any problems whatsoever
Click to expand...
Click to collapse
I second that, I came from ReflexTsense HD 1.8, as I only use EXT3 I didn’t have any of the problems I too can confirm the menu > track pad wake only works for a brief period but everything else is SOLID.
If your coming from a custom ROM I suggest you use MyBackUp Root to back up and restore all data (sms, contacts, settings, etc etc) and apps as I installed LeeDrOid 3.0.2 then downloaded a file manager, installed MyBackUp Root and I have been up and running with no FC’S. I do miss the features of a Desire HD ROM as it allows you to install some awesome Sense skins and just because of Sense 2.1 on HD ROMS, I am tempted to go back.
Thanks again for the FAQ dude.
himeshladva said:
Not sure if this is just mine or not, but when downloading apps from Market, it says "starting download" throughout the whole time it is downloading it whereas it used to show the progress of it..
Click to expand...
Click to collapse
Mine also have this same problem..don't know to resolve.
Nice work!
Desire hardkey backlight
Thank you for the comprehensive FAQ.
1. Could you please advise if there's a mod or some other solution (prefereably non-battery-intensive) to turn off hardkey backlight on htc desire with Leedroid 3.x?
I tried "LED's hack" app but it pops up "superuser access granted" all the time + mentions that it can be battery-intensive. Maybe there's an alternative way, a patch of some sort, or a terminal command?
2. Lee says that LED backlight was tweaked. Still not good enough for many night users - too bright; is there a way to add led backlight custom level tweak functionality seen in CM?
3. Mainpage says "smartass\interactive governors used, selectable by SetCPU". Anybody happens to know what CPU governors \ values are used in screen off state? I assume smartass is on by default for screen on.
csyrix said:
Mine also have this same problem..don't know to resolve.
Click to expand...
Click to collapse
What about reading 2 post above yours? THAT is lazy mate.
Can I suggest that you ask people to format and partition their card using G-Parted via Linux/Ubnuntu boot CD - I think this is a better method than using the zip align and I'm guessing the reason that many people didn't have issues was that they originally partitioned their card via this method in the first place.
It worked for me when zip align didn't, I tried re-partitioning using AMON RA 2.0.1 and zip align and no joy.
Nice thread. Was certainly getting messy in the main thread.
fred_be9300 said:
many people reporting ROM failing to boot/flash, have HBOOT 0.75 or 0.80. Usually fixed by doing AlphaRev HBOOT flash / S-OFF.
Click to expand...
Click to collapse
Wanted to mention that instaling stock RUU from HTC site will give you 0.93, for those not wanting to S-Off. You'll have to re-root, but no big issue.
fred_be9300 said:
* When using "fast boot" feature, you can't reboot into recovery. Either disable fastboot, or use the pre-installed ROM Manager: open it up and select boot to recovery. (I have seen some other suggestions, but forgot what they were)
Click to expand...
Click to collapse
The other one was to select Restart and hit vol- the moment screen goes black...
Seems to be 100% working here, save for the few glitches mentioned like Menu wake-up etc. I am 0.93 and S-On...all good
tinky1 said:
Market downloads but doesn't do anything else-SOLUTION: clear market data/cashe
Click to expand...
Click to collapse
I think you have misunderstood what I was saying..
Whilst a new app is currently downloading and you go to the "My Apps" list, it will constantly say "Starting download" as opposed to showing the progress of the download. Once the download has been completed the app does still install..
I've tried clearing data/cache but it doesn't change it.
Easy recovery - restart phone and hold volume down once screen goes off
Guys, for new issues is better to put it in leedroid main thread where more experts see it. This thread is to collect and summarize known info. And to feedback on FAQ.
I will update OP tonight or latest tomorrow eve
Ps: Thx for feedback and suggestions to improve
Sent from my HTC Desire using XDA App
My apologies then. I had this issue with stock ROM, factory restore fixed it for me. Google stuck download market issue,there will be a solution. I don't think its ROM related.
himeshladva said:
I think you have misunderstood what I was saying..
Whilst a new app is currently downloading and you go to the "My Apps" list, it will constantly say "Starting download" as opposed to showing the progress of the download. Once the download has been completed the app does still install..
I've tried clearing data/cache but it doesn't change it.
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA App
does this rom have compatibility with htcsense.com ?
^^^^No.
From the latter post it looks like people who don't have any problems flashing this rom are on hboot 0.93 and amonra 2.0.0/2.0.1 or older cwm 2.5.xxxx recovery, regardless of s-on or s-off.
Sent from my HTC Desire using XDA App
last updated: 2011-Oct-29 [DISCONTINUED]
ROM version described: 3.0.8
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.
I'd like to thank Lee for the wonderful ROM, fred_be9300 for the initial FAQ, and anderl78 for... lots of help.
Also thanks to alpharev and others who are quoted or otherwise mentioned on this page.
Thread management
[DISCONTINUED]
======
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 90-100mb 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
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. There are currently several hboots that are compatible with LeeDroid Bravo GB. However, to obtain the maximum benefit you have to flash Oxygen hboot (revision 1), second best is Oxygen-r2. More details on flashing \ updating can be found in the respective section.
You can get an overview of different ROM variants looking at the picture Bravo ROM allocation.jpg by clicking the preview at the end of this post. The picture may be not very precise and perhaps even partially erroneous, but it will give you a graphical overview and it is correct in general.
Last point: data++ is NOT the same as Data2Ext. Simplified explanation: Data2Ext will increase the size of "internal memory" as percieved by your system to the size of your sd-ext (it may also usually require two ext partitions instead of one, etc, etc). 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.
Things to know if using Data++:
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.
2. Since location of some system files has changed in data++ relative to stock ROM, 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. There are two most suitable hboots for data++: oxygen r1 and oxygen r2. The difference between them is that r1 has a 90mb system partition while r2 has a 100mb one. As LeeDroid Bravo GB 3.0.7 has a system partition exceeding 90mb, you have two options:
- prudent option for people who have hands.sys and head.sys drivers installed on their system:
-- use oxygen r1, as it leaves more space in data partition hence more space for your apps
-- modify LeeDroid Bravo GB rom.zip in any of the below ways to reduce the size of \system folder:
--- open the rom.zip in either WinRAR, 7ZIP, Total Commander with an archive-reading plugin will also work, other methods have not been mentioned but might also work; do NOT unpack rom.zip, just open it
--- remove bootanimation (rom.zip\resource\customize\bootanimation.zip) and boot sound (should be somewhere near it) by pressing the del key inside the chosen app (WinRAR\7ZIP\TC)
--- and\or remove unnecessary stuff like wallpapers and jpegs and whatever you believe is ok from rom.zip\system\customize\resource
--- copy the modified rom.zip to sd card for flashing, keeping in mind you will have to turn off signature verification (as we've changed the rom.zip and the embedded signature is now no good) in the recovery prior to flashing (e.g in Amon-Ra it's Other\Toggle Signature Verification)
- strange option for people who are lazy and\or do not have hands.sys and head.sys drivers installed (what would they be doing flashing hboots and roms then is another question, particularly data++ roms):
-- use oxygen r2, as it has a 100mb system partition and no modification have to be made to rom.zip prior to flashing - but your data partition will be about 10mb smaller than with oxygen r1
5. 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. To learn more, see post by anderl78: http://forum.xda-developers.com/showpost.php?p=14297694&postcount=4751
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!
2. Requirments for flashing (i.e. before you flash, you need)
a. General requirements
- Rooted HTC Desire
- SD card partitioned into two partitions - FAT32 and EXT3 (EXT4 supported, haven't tried it but people confirm it works)
- hboot 0.93.x - some have reported successfully flashing with older hboots, but it usually took multiple attempts, so it's easier to S-OFF
- Desire should be fully charged, just in case
- It is always better to flash critical stuff using a notebook or UPS-connected PC for obvious reasons
To partition your card, you can use:
- your recovery
- ROM Manager app
- 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)
- any other reasonably advanced partitioning program (such as Acronis Disk Director)
Keep in mind:
- both partitions should be primary (how to check if your partition is primary?)
- 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.
- the last, but NOT the least: method of partitioning should be irrelevant, however, best results seem to be obtained by using GPARTED \ minitools partition wizard. Gparted is the surest way, but least convenient; minitool Partition Wizard is very easy to use and requires no reboots.
b. Requirements specific to Data++
- S-OFF
- Oxygen hboot downloaded and ready to flash
- Stock hboot in case you want to go back
Obtaining S-OFF is 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), connect rooted HTC Desire, cross your fingers and follow instructions.
Flashing hboot is described here: http://alpharev.nl/ OR http://androidtricks.net/fastboot-custom-hboot-partition-table-htc-desire-52 OR http://forum.xda-developers.com/showpost.php?p=14259861&postcount=3683 OR read this post by anderl78 with detailed instructions of flashing it via fastboot.
Flashing hboot via PBIMG is in my opinion easier and is the only way I ever tried. Flashing via fastboot requires having ADB installed.
All necessary files can be found in the last section: "7. One-stop download reference".
3. Flashing guide
1. Make a Titanium backup of apps (optional but reasonable)
2. Make a Nandroid backup
3. Copy both backups (titanium and nandroid) to a PC for ultimate safety (optional but reasonable)
4. Have the following files on your SD card in the root folder:
- Lee's ROM (make sure to have modified the updater script if it's 3.0.8.2 Data++)
- Ext3 alignment patch
- [optional] radio if you update it from sd
- [optional] any other zips you may want to flash (kitchen mods, backlight mod)
- [optional] hboot files (stock and chosen oxygen) if you want to install Data++ using the PBIMG way
5. 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
6. Make sure you have an EXT3 partition as described in the Requirments section above (EXT4 claimed to be supported, not tested by author of this post)
7. [data++] Flash necessary oxygen hboot (r1 or r2) if you are flashing the data++ version
8. [optional but highly recommended] Perform a full wipe (can usually be omitted if updating from most prior sub-versions of this rom e.g. 3.0.x where x<8 but better to do this, you do have titanium backup anyhow). Still, you can always try flashing without wiping, and if it doesn't work or works but is buggy, you can reflash again with wiping.
9. [data++] Toggle signature verification to off if you are using oxygen-r1 hboot and have modified the rom.zip to reduce system partition
10. Flash rom.zip
11. Reboot and wait for the ROM to first-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)
12. If everything is OK, reboot back to recovery and flash optional mods if you have them (you can flash them right after flashing rom.zip prior to first-booting, but if the rom fails to boot it will be hard to determine the reason - maybe it's the rom, maybe it's the mod - so easier to flash after first-boot)
13. If you have problems flashing the rom \ first-booting, read the following section.
14. [optional] restore Titanium backup if you have one, but make sure you do not restore any red items. To totally make sure, you can choose to restore only user apps+data, and set up system settings by hand, if you like to be on the safe side.
Note: DO NOT flash EXT3 Alignment Patch as described on Lee's official page (step 3 of his flashing guide). With all due respect to Lee, flashing this patch has resulted in non-mountable sd-ext partition for many users. So do not flash it unless the rom won't start, as described in the following section.
The ext3 aligtnment patch has the following purpose, however, ROM works fine for virtually all who go without it and the opposite is not true. So the guidelines are:
- if it works without it, don't flash it;
- if it doesn't work without it, try flashing it
- if you you've flashed it first and the rom doesn't boot, use any partitioning software to delete the ext partition, then re-create it and flash without the alignment patch.
4. Troubleshooting ROM installation
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:
- flash EXT3 Alignment Patch (http://leedroid.ftp.rshost.eu/Bravo_Addons/alignment-ext3.zip), then try reinstalling rom by repeating steps starting with step 10 of the above flashing guide.
- 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 mod-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 unmodified data++ rom with oxygen-r1 hboot (Solution: either modify rom or flash oxygen-r2 hboot)
- flashing a2sd+ rom on oxygen 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
- If flashing 3.0.8.2 Data++, modify the updater script as described here
- You may want to check MD5 signature for the rom file just in case
- If you have modified data++ rom to use oxygen-r1 hboot - 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. Attempt to flash modified ROM without toggling signature verification to disabled
If you have modified your ROM, you have to toggle signature verification off; e.g in Amon-Ra it's in the menu Other\Toggle Signature Verification.
6. 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 THANK button once they have solved your problem
5. Customizing guide
5.1. Kitchen customization - battery icon, etc.
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.
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, with the data++ version of 3.0.6 I used the following lines (could be different with 3.0.7 official data++, but enought to get the picture, and you can always figure out the paths and which of them to alter from rom.zip):
Code:
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");
whereas original was like this:
Code:
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");
So it's the "spot 10 differences" game. Just check the official 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.
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 3.0.7 A2SD, ROM" from the dropdown. 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.
5.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 at http://www.youtube.com/watch?v=6pyf7U1cByI
6. Troubleshooting other issues:
There's not much issues I know of with this rom, unlike the HD ports. They may be user-specific, but I'm listing them here just in case.
- Lockscreen not appearing on power-on, i.e. after on button is pressed, phone starts direct to desktop.
Problem surfaced after several months of use. Fixed by reboot.
- When I want to select which calendars to be synced, I can only select [x] of my [x+n] calendars.
Fixed by clearing all data in the Settings>Applications section from processes containing the word Calendar.
7. One-stop download reference:
ROM links
ROM itself: see middle of this post
EXT 3 Alignment patch
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
HBOOT links
Site: http://alpharev.nl/
Bravo oxygen r1 (with 90mb system partition, alpharev took it down after releasing r2 for some reason):
- fastboot flashing: link courtesy of anderl78, OR backup link to same file, MD5 0ac1bd252276a7e81c24d601569746e1 (if you use the second link and want to check MD5, unpack .img first, then check MD5)
- PB99IMG flashing, MD5 4f19784ae373fbfd8c2e5de6d32696a0
Bravo oxygen r2 (with 100mb system partition):
- fastboot flashing, MD5 532e39f7b0e8cf9aff07d4556fe6d841
- PB99IMG flashing
Stock hboot:
- fastboot flashing, MD5 7bd5234711364880de1fa982dcf3a2d6
- PB99IMG flashing
Mods and fixes
- All mods courtesy of anderl78, so if you like them, I'd suggest pushing a THANKS button on the respective post by anderl78
- Nandroid prior to flashing is a reasonable policy
- Some mods may require toggling signature verification to "disabled" prior to flashing
Hardkey backlight always off (good for those who like to read at night), backup link
Bluetooth autoconnect
No-sense patches for A2SD+ and Data++ versions: for LD3.0.7 and for LD3.0.8
Camera tweak (media_profiles updated, reducing jpeg compression)
Unlimited browser tabs tweak
3G\EDGE\MMS not working:
- reset your APN to default (goto Settings\Wireless and Networks\Mobile networks\Access Point Names\ press MENU key on your device, choose RESET TO DEFAULT)
- if unsuccessful, enter APN details manually (your operator should know) OR see this post for how-to on importing a large APN preset list
Black HTC Home widget (flip-clock+weather), works for 3.0.x and 2.5.0
Various performance improvements
Autobrightness tweak for 3.0.8
Juwe11's Ramscript for Leedroid
Leedroid 3.0.8.2 data++ updater-script fix
Database defrag mod (frees internal memory, speeds up operation a bit, slows down boot a bit)
Tools
[url="http://www.paehl.de/cms/fastmd5_deutsch]Software to check MD5[/url]
GPARTED - linux software for partitioning, also can be run on any PC using a boot-cd
- site: http://gparted.sourceforge.net/livecd.php
- how-to: http://www.youtube.com/watch?v=sVK-tJe8pXE
MiniTool Partition Wizard - freeware windows partitioning program, site: http://www.partitionwizard.com/download.html
DISCLAIMER: whatever you do, you do on your own initiative and the results of your actions are your responsibility.
Hello s300pmu1!
respect, very good FAQ-Thread!
oxygen_r1 hboot (bravo_alphaspl-oxygen.img) http://db.tt/eNlzMrS
md5: 0ac1bd252276a7e81c24d601569746e1
hi,
indeed very well done.
I would suggest that this thread url is pasted to the OP Lee's thread. would be easer for everyone's as an howTO
awesome thread .. resolves most of the issues that crop up related to data++
Thx a lot. Seems to be complete and clear !!!
hi,
Is there a easy way to check if my sd-ext3 is set as primary? Im using Win7 and i try booting into Gpart via a usb drive, but it doesnt seem to detect my sd.
My sd-ext3 have been partitioned using RA when i flashed LeeDroid 2.4.0.
kobezt08 said:
hi,
Is there a easy way to check if my sd-ext3 is set as primary? Im using Win7 and i try booting into Gpart via a usb drive, but it doesnt seem to detect my sd.
My sd-ext3 have been partitioned using RA when i flashed LeeDroid 2.4.0.
Click to expand...
Click to collapse
Firtsly, 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
THEN:
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 and their types
10. After you're done, just close the windows with the mouse
ALTERNATIVELY, for the GUI-minded:
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.
OR, 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, at least in version 10)
s300pmu1 said:
Firtsly, 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
THEN:
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 and their types
10. After you're done, just close the windows with the mouse
ALTERNATIVELY, for the GUI-minded:
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.
OR, 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, at least in version 10)
Click to expand...
Click to collapse
Thank you so much for the detailed stepped.
I tried using the the steps with DiskPart as well as Disk Mgmt. But I can only see one primary partition on my 8GB SD, that is the FAT32 Primary with around 6GB+ size. I could not see the ext partition which I have partitioned to be 1GB.
Does this mean my ext3 is not primary? or Win7 just cant detect ext3 since it suppose to be for Linux?
Does this mean my ext3 is not primary? or Win7 just cant detect ext3 since it suppose to be for Linux?
Click to expand...
Click to collapse
It means, most likely, that something is wrong.
Win7 can detect sd-ext, though it will not be able to work with it.
Still, it will display the ext partition in both diskpart and diskmgmt.msc, and also show if it is primary.
How did you connect the flash card to your PC?
If you just connect your booted Desire to PC in "Disk Drive" mode, it will never show the sd-ext partition. You have to do it as described, from recovery or by using a card reader.
If you still can not see the sd-ext partition (BTW, what size is your card?), try partitioning it using recommended software (you can start with minitools partition wizard as it is much easier than Gparted and yields the same results).
first, I'm sorry I can't post my question in the main thread (not enough
posts ).
Question :
i have Leedroid 3.0.7 A2SD+ installed, everything seems fine, but I can see my internal storage free space going down and down (now only 5 mb) and at the same time the SD card (A2SD ext3 partition) still has 284 Mb free.
Anyone knows where the problem could be ?
Anyone knows where the problem could be ?
Click to expand...
Click to collapse
Yup. See the first post of this thread:
However, some data is still written to the \data partition, so no matter what, the "Internal memory" will decrease.
Click to expand...
Click to collapse
To get more memory, you will have to use Data++ version.
Or somehow integrate data2ext which will give you even more space (which is, however, rather complicated, and I assume, less stable).
s300pmu1 said:
Yup. See the first post of this thread:
To get more memory, you will have to use Data++ version.
Or somehow integrate data2ext which will give you even more space (which is, however, rather complicated, and I assume, less stable).
Click to expand...
Click to collapse
Hey guys,
Everybody just keeps saying that, but there must be a limit to data accumulation, isn't?
Even with data++, if it is just normal to lose 5mb each day without new installs or updates, well...
I'd address this question to anderl78\lee.
They are better equipped to answer it ^)
Just don't forget that apps do store data (e.g. gmail stores incoming mails somewhere, and this somewhere is most likely the \data partition).
TomLeeDesire said:
Even with data++, if it is just normal to lose 5mb each day without new installs or updates, well...
Click to expand...
Click to collapse
What, you're losing 5 MB of internal memory EACH DAY? That's insane! I'm about to switch from A2SD to DATA++ because my internal memory is dangerously low but should I now?
I'd address this question to anderl78\lee.
They are better equipped to answer it ^)
Just don't forget that apps do store data (e.g. gmail stores incoming mails somewhere, and this somewhere is most likely the \data partition).
Click to expand...
Click to collapse
Hello! I looked into the Rom configuration but could not find a problem that would cause this space consumption. Apps are saved in sd-ext, app-data is saved in nand Memory (internal).
Dalvik-cache is on ext or internal, depends in the Rom, is ok too.
In data++ is a little error, app-private (buyed apps) is not on sd-ext, its completely on internal memory. To change this, flash my dalvik2nand.zip ;-) (see link in OP) - perhaps its that? But this is only in data++ and not in a2SD+ ROM... I don't think this is the reason...
I looked into the space available here on my phone for a few days now, and I have to say nearly no space is gone... 116mb free to 115mb free in 3 days... Absolutely ok what I think. (data++ with the above dalvik2nand "extension" )
I think, the described problem is related to some apps, which are storing a lot of data in internal memory. If somebody have this problem, I recommend to see into "manage applications" sorted by needed space, or use "diskusage" from market to look, what app(s) are causing this.
One other thing I have seen is Titanium backup. After a flash I restored my apps with tb as usual. I wondered why some apps last so long to restore and suddenly i got a low space warning message. Looked into the apps and see for example xda-app using 90MB for data! Wiped all, restored nothing with tb, installed all from market and the problem is gone...
I hope this helps somebody... ;-)
Sent from my HTC Desire using XDA App
Ghisy said:
What, you're losing 5 MB of internal memory EACH DAY? That's insane! I'm about to switch from A2SD to DATA++ because my internal memory is dangerously low but should I now?
Click to expand...
Click to collapse
See my post above, you could use data++ without fear! ;-)
Sent from my HTC Desire using XDA App
Ghisy said:
What, you're losing 5 MB of internal memory EACH DAY? That's insane! I'm about to switch from A2SD to DATA++ because my internal memory is dangerously low but should I now?
Click to expand...
Click to collapse
Hey don't panic.
I am a happy data++ user.
Those 5mb were just a way to speak about this subject coming back every time.
I just can't stop installing and uninstalling apps so I have no real number to give you.
I also use a cache cleaner that frees some internal every day.
I just thought there would be a max data an app can store that would avoid explosion...
Thanks for your replies guys. I went ahead and updated to DATA++. I've checked apps sizes in the "manage applications" menu and they don't seem out of the ordinary.
I guess that's what you get when you have 130+ apps installed!
anderl78 said:
See my post above, you could use data++ without fear! ;-)
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
It may be something wrong with the A2SD version.. When I was using that I was constantly losing memory, I switched to the data++ version and no longer have the problem.. the memory always stays the same (give or take a few mb for app caches etc..).
Something seems weird with the A2SD version for sure.. (well that's what I think anyway lol)
himeshladva said:
It may be something wrong with the A2SD version.. When I was using that I was constantly losing memory, I switched to the data++ version and no longer have the problem.. the memory always stays the same (give or take a few mb for app caches etc..).
Something seems weird with the A2SD version for sure.. (well that's what I think anyway lol)
Click to expand...
Click to collapse
I can't believe it, cause a2sd+ Rom and data ++ Rom are using the same a2sd-script, the difference is, in easy words, only that the dalvik-cache is not moved to sd-ext in data ++ Rom. But I'm not the Rom-cook, perhaps I'm totaly wrong... I have only looked a bit into scripts and a few other things perhaps related to this - I'm not a real expert in this... Let's see, if lee provide us with more infos and perhaps a solution in his next build!
Sent from my HTC Desire using XDA App
4EXT Recovery Classic v2.2.7 RC5 | STAY @EXT4 | Convert FS | Rom -> Backupname | ..
{
"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"
}
Quick note about themes:
Available themes as of Oct/18:
Themes by [URL="https://forum.xda-developers.com/member.php?u="]GuestK00388[/URL]
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
New option: check and optionally repair the file system on your sdcard (fat32)
Removed duplicate format cache option inside the format menu (wipe cache does the same)
When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
Added new size option (128mb) to the partitioning menu per request
Parted is no longer used to format fat32 in the partition menu-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
4EXT Recovery themes should now stay when formatting /system or flashing new roms
New option: format /sdcard fat32
New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
Size for recovery greatly reduced
New 4EXT Recovery Control Features
Please see www.4ext.net for more.
Fix permissions
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
As an example, the following would be possible to do in just one session: Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Features: Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!
not all features may be relevant for all devices
Displays additional information:
Identifies your current rom and displays its name
Current filesystems on your partitions
Free space remaining of all of your volumes
Current battery charge level
Backup | Restore:
Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
Tar backups (can be switched on or off)
Complete CWMR5 compatibility
All Backups you create will be named after your currently installed Rom for easier identification.
Never unwillingly get "downgraded" to EXT3 again
Always restores backups using the file systems you HAD on your partitions at the time of creation!-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.
You can manually change any existing Backup to ext4 or ext3-> so that after a restore, all partitions and up with the file system you wanted!
Advanced Backup: backup only a single partition
Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:
When you wipe or format it will always use the same file system you currently have.-> but you can change that
When you format ext4 it will always create an aligned file system
Correctly identifies unformatted sd-ext partitions-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu
Filesystem check and repair option in advanced menu
Partitioning:
Alignment check of your partitions
Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
(RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:
Integrated md5sum checking option
Themes:
Customize all colours used throughout recovery
Use your own icons, background images, progress bars.. more to come.
Assign different backgrounds to different menu categories (version >= 2.1.2)
Create a flashable zip for others to flash your theme.
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Less "No's" in confirmation dialogues
Changed Advanced Restore: first select what you want to restore, then select the backup-> Useful for restoring from "Advanced Backups"
4ext.prop:
Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
Change all settings conveniently with 4EXT Recovery Control
Many more options to come
Share your settings / themes by packing your config into a flashable theme
Other stuff:
USB Storage Autostart (must be switched on)
Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)-> you could even partition your sdcard from your PC while connected via USB
Switch haptic feedback on/off
You don't need to reboot recovery if you transferred a file to show up in the install menu.-> This bug affected only some users with either CWMR or previous versions of 4EXT.
Button backlights (Desire S, Desire HD and Incredible S only)
Download:
All downloads are now available through 4EXT Recovery Updater. It's free, no ads, no tracking, no nothing, don't worry
.. and of course via 4EXT Recovery Control
This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
It also notifies you when there are any new critical bugs found
Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control
Free version: Recovery Updater
Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
Flash as many zip files you want in one go
Automatically calculate and display the md5sums of all zip files you are going to flash
Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
Optionally, but highly not recommended:If md5sums don't match but you REALLY NEED that backup BADLY, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup to "forcefully" restore it!
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
As an example, the following is possible to do in just one session: Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Much, much more! See www.4ext.net
Recovery theming
Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
Change all colours with live preview and a nice colour picker.
Working great on my dinc2 this is the one thing i missed since switching from the inspire and now i have it back. Thanks max!
Sent from my Incredible 2 using xda premium
oxlong27 said:
Working great on my dinc2 this is the one thing i missed since switching from the inspire and now i have it back. Thanks max!
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Thank you very much for that!
And for jumping into the cold water for me
If it booted up fine it's alright and I can remove the warning. Everything else is just like on the IS.
---------- Post added at 01:09 AM ---------- Previous post was at 12:48 AM ----------
Added 2.1.1 Final, but that version is really old.
I'd try the latest first. It has been extensively tested and issues if any should only be minor.
Yep everything i tried is working as it should. Havent tested the formatting yet but im sure its fine everything else works. And as far as trying something thats untested, well thats what xda is about, if you dont get a soft brick here and there your not having any fun. But yes this works fine thanks again
Sent from my Incredible 2 using xda premium
I gave it a go and seems to be working just as it should. Was jealous of this recovery on the Incredible S forums because it let you create EXT4 file structures and now its here. Thanks!
Quick question, what's the advantage with EXT 4? I have heard that it's faster, but then several others say it's a waste of time. I do like this layout a lot more aswell.. The backgrounds are an awesome idea! Great job with this
Sent from my Incredible 2 using XDA App
You should add this to ROM manager.
jonathon2011 said:
Quick question, what's the advantage with EXT 4? I have heard that it's faster, but then several others say it's a waste of time. I do like this layout a lot more aswell.. The backgrounds are an awesome idea! Great job with this
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
Thank you very much
Yes, theoretically it's faster.. depending on usage it can be much faster.
On a phone the difference is less than on a computer though.
Deleting larger files is definitely much faster, also formatting.
Most newer mobiles get shipped with ext4 file system instead of ext3.
It's difficult to answer your question
You should try it out and check if you feel the phone is faster
shoman24v said:
You should add this to ROM manager.
Click to expand...
Click to collapse
I really can't imagine that I had a chance or that it would be possible
Also obviously I would like ppl to use my app.. it was a lot of work.
And yeah, also if it is the free version!
It's a big advantage for me as the developer and I hope for the users too.
That way I can send you news about critical bugs found in a new release (which happened with rc1 for example), I can make sure you get to see at least the Changelog when you install a new version and since it's just a button press, the chance is greatly increased that you also take a look at any known issues.
There are times when I release many updates in a short time. This really comes in handy.
At the moment there is only the preview, but I will release the free version today or tomorrow
Downloaded this morning and gave it a run. I like this recovery a lot.
I ended up making a backup, and then converted my file system to Ext 4 on data and Cache (system already is.)
This is a very nicely done recovery, I like that it is easy to navigate, and has a few more options when doing wipes.
The app is nice to.
Thanks for sharing this!!
PacerguyDon said:
Downloaded this morning and gave it a run. I like this recovery a lot.
I ended up making a backup, and then converted my file system to Ext 4 on data and Cache (system already is.)
This is a very nicely done recovery, I like that it is easy to navigate, and has a few more options when doing wipes.
The app is nice to.
Thanks for sharing this!!
Click to expand...
Click to collapse
Thank you very much
BTW Free version of the app is finally up
madmaxx82 said:
Thank you very much
BTW Free version of the app is finally up
Click to expand...
Click to collapse
I went ahead and bought the market version. Excellent job, Ive been waiting for a recovery like this.
I would have to say I like this recovery a lot. I like having the partion information and battery level in recovery. Also the option to convert partions is a plus. Already tried it on a couple different roms and currently running them all as ext4.
Great job and keep up the good work
Sent from my Incredible 2 using XDA App
After converting everything to ext4 cant get wifi tether to work anyone else have this issue? Boots 100 times faster though on cm7
edit fixed by updating to the latest nightly
Great recovery, got the market version. Super smooth on a few roms here.
Anyone with a sense rom should go without saying but make sure the kernel supports ext4. Drellisdees kernel does well
This Recovery looks great, I'll try it soon. A couple questions...
1. It replaces Clockworkmod 5.0.2.0?
2. Has anyone actually done any benchmarks to see if Ext4 is faster than whatever is on the stock phone?
I use Ext4 on my Ubunutu Linux box and I understand it improves performance and adds journaling, but is it actually faster on a phone. It would be cool to see boot times, application install and launch times, task switching, etc. So often people say even minor updates to ROMs are "much faster" and it's nonsense.
Thank you all very much
regarding ext4: yes it will be faster, but how much depends on usage and it's really difficult to say on a phone. But certainly it won't be slower.
Also since newer phones seem to ship with ext4 it might indicate something
Yes, when you flash any other recovery it replaces the previously installed one.
ph1nn said:
This Recovery looks great, I'll try it soon. A couple questions...
1. It replaces Clockworkmod 5.0.2.0?
2. Has anyone actually done any benchmarks to see if Ext4 is faster than whatever is on the stock phone?
I use Ext4 on my Ubunutu Linux box and I understand it improves performance and adds journaling, but is it actually faster on a phone. It would be cool to see boot times, application install and launch times, task switching, etc. So often people say even minor updates to ROMs are "much faster" and it's nonsense.
Click to expand...
Click to collapse
Well as far as benchmarks I haven't dug in too deeply. Unfortunately with quadrant file systems tend to fool it anyway but I haven't gotten linpack or similar
The biggest advantage I see are the same things that we both likely saw when linux changed to ext4 (ubuntu fan here too ) that being, things involving large amounts of data being moved at once have the biggest improvement. Obviously there are more instances of that on a computer than a phone . Boot times, it knocked a few seconds off my boot time on cm7 which is not slow to boot by any means already. I think it would be even more drastic with something as big as a sense 3.0 rom..everything else I don't know that its particularly faster after everything settles down but is most definitely not slower and is just as snappy as before. It does seem to be a bit quicker in terms of settling down more quickly after a reboot (not laggy for as long) and everything getting precached etc.
Just want to tell everyone, that there is a new known issue with tar backups!
It can happen if you have enabled tar backups that superuser stops working after you restored a tar backup.
To anyone not familiar with this: it is disabled by default! So don't worry if you didn't enable that setting!
I have updated known issues and also sent a notice about that.
To work around this, you can flash your rom again (no wipe needed) and it will be ok.
Nonetheless please deactivate tar backups for now.
It doesn't happen for everyone and always.
Difficult to track it down and I couldn't reproduce it on my device yet.
It is or was also known to happen with CWMR5 which introduced tar backups.
Maybe it's solved in the newest version I don't know however I have seen a lot of posts regarding that.
I'm working on this.
If someone runs into this problem, please send me a pm or a report telling me which version of superuser and which rom he was running.
Thank you very much and sorry about that.
Anyone entering the app gets a one time notice about it.
I've been using the tar backups since installing 4EXT last week. No problems on my end, but since I really don't need the tar backups anymore, I'll go ahead and disable that option and go with the default format.
Thanks for letting us know Madmaxx. And thanks again for the great recovery!!
Thank you
New versions of recovery and 4EXT Recovery Control.
Big changes
Hi,
First i will say thanks for the great rom, i will try it asap (a little bit more stable)
i read about this rom in the topic since it was started .
i have some Questions, it will be my first "clean" Android (without Sense)
There should be a installer after first start of the rom after flash? Where can i found more information about the things i can chose?
Evervolv toolbox, is that an addtional Settings Dialog with more Options or still a app which can be used as "standalone"
(sorry for the bad english)
When you install it you will get some options to choose a launcher and a2sd-script.
On first start you won't get the app to set your g-acc and so on, you'll have to do that in the system settings.
And the Evervolv-Toolbox are additional settings the this rom it's not a standalone app.
Hope this helps
grtz
Please note that Sandvold ICS v. 0.4.2.1 has some stability problems at the moment. Many people experience "black screen of death", device fails to turn on screen after a period of inactivity, battery has to be removed to reboot. I found that raising the minimum CPU speed from 245mhz to 384mhz completely removes this problem. With this small tweak the rom is great! You *should* be able to change this setting with Evervolv toolbox, sadly it does not work. For some reason the toolbox runs with insufficient rights to tweak cpu speed, I did my own scripts to set cpu speed from the console instead.
cheers
/Stig
stig_dk said:
Please note that Sandvold ICS v. 0.4.2.1 has some stability problems at the moment. Many people experience "black screen of death", device fails to turn on screen after a period of inactivity, battery has to be removed to reboot. I found that raising the minimum CPU speed from 245mhz to 384mhz completely removes this problem. With this small tweak the rom is great! You *should* be able to change this setting with Evervolv toolbox, sadly it does not work. For some reason the toolbox runs with insufficient rights to tweak cpu speed, I did my own scripts to set cpu speed from the console instead.
cheers
/Stig
Click to expand...
Click to collapse
Black-screen-issues can be solved by flashing MIUI-kernel:
http://www.miui-au.com/wp-content/plugins/download-monitor/download.php?id=166
Hi! I use ICS since beta 0.3.9 and I'm now updated to 0.4.4
This release seem very stable now. Just remember that the camera preview doesn't work. Also, you might have some problem with MMS.
App space problem
Hello - some help for a newbie please (well Desire newbie)...
I did try reading though Sandvolds thread, and I have tried to remedy, but I don't seem to get much further ....
I am running an ICS beta on my tablet, so I thought it would be interesting to try it on my Desire too. On the tablet there is more memory, so I have never experienced space problems with apps.
I rooted the Desire OK - and flashed 0.4.2.1 ... ran fairly smoothly, but hit space problems when trying to load up some of my favourite apps. I have a 16gb sd card. I downloaded apps2sd from the market - and moved some of the apps. However still not able to update some system apps from the market due to insufficient space (even though there appears to be enough).
Reading the other thread, I have gathered some/little understanding... and so before flashing 0.4.4 I reformatted my SD card from recovery choosing the largest ext4 that I could.
I was then ready to go to try 0.4.4.
On trying the Amarullz script and Nova launcher - I was having lots of lag after boot and I kept getting prompted to enter PIN number and reboot the phone. (I had done a factory wipe and cleared Dalvik after flashing the ROM).
I then reflashed choose Apex launcher, stock Kernal and data2sd option.
I wiped after flashing, did a few waits and reboots - as others recommended this.
Now seems to run quite smoothly, I have added back a bunch of apps via Titanium Backup ... but I don't see any apps 'automatically' being moved to sd card. I have moved as many as I can manually.
But I can also see that I am going to run out of space again soon ....
If I look in the settings at storage I see...
Internal storage - Apps 104MB Available 26.86MB
SD Card - Apps 239MB
Am I doing anything wrong?
Looloup said:
Hello - some help for a newbie please (well Desire newbie)...
I did try reading though Sandvolds thread, and I have tried to remedy, but I don't seem to get much further ....
I am running an ICS beta on my tablet, so I thought it would be interesting to try it on my Desire too. On the tablet there is more memory, so I have never experienced space problems with apps.
I rooted the Desire OK - and flashed 0.4.2.1 ... ran fairly smoothly, but hit space problems when trying to load up some of my favourite apps. I have a 16gb sd card. I downloaded apps2sd from the market - and moved some of the apps. However still not able to update some system apps from the market due to insufficient space (even though there appears to be enough).
Reading the other thread, I have gathered some/little understanding... and so before flashing 0.4.4 I reformatted my SD card from recovery choosing the largest ext4 that I could.
I was then ready to go to try 0.4.4.
On trying the Amarullz script and Nova launcher - I was having lots of lag after boot and I kept getting prompted to enter PIN number and reboot the phone. (I had done a factory wipe and cleared Dalvik after flashing the ROM).
I then reflashed choose Apex launcher, stock Kernal and data2sd option.
I wiped after flashing, did a few waits and reboots - as others recommended this.
Now seems to run quite smoothly, I have added back a bunch of apps via Titanium Backup ... but I don't see any apps 'automatically' being moved to sd card. I have moved as many as I can manually.
But I can also see that I am going to run out of space again soon ....
If I look in the settings at storage I see...
Internal storage - Apps 104MB Available 26.86MB
SD Card - Apps 239MB
Am I doing anything wrong?
Click to expand...
Click to collapse
1). www.revolutionary.io use this
2). www.alpharev.com download cm7r2.img
3). flash the hboot
Code:
fastboot flash hboot hboot.img
4). re-flash 4.4 and choose stock a2sd
5. enable a2sd
Code:
su
a2sd install
#choose settings#
Thanks for quick response..... I have a fee more questions....
I originally rooted my Desire via revolutionary .... do I need to do it again?
I guess I then flash the zip file.
The fastboot command - can I do this from the terminal app?
hi,
fastboot command and adb must be running from computer.
you need to instal sdk android sdk android
if you run revolutionary, u don t need to do once again but to flash an hboot you must be Soffed.
dunno if revolutionary does the job... i used alpharev to do son gain S-offed and able to flash hboot from fastboot command.
I saw the option to install agps in the installer but i chose gps. How can i add the agps when i already installed the rom? Because getting gps fix in navigation is taking way to long, so long that i abort it while trying
Getting closer
@bortak
1. Done OK
2. Done OK
3. Done OK
4. Done ... BUT ... no Gapps, no Terminal app ... not much really not even a keyboard (even after 2 reboots)
- The link to Gapps for CM7r2 no longer works
5. Unable to try this as no Terminal app ... and I can't get ADB working on my PC.
where have my apps gone?
So I can't get cm7r2 to work, so I reflashed hboot back to standard, I then reflashed 0.4.4 choosing stock a2sd. I installed a2sd via terminal and moved cache too. After reboot I installed a bunch of apps .... and eventually ran out of space - as if apps not being moved.
I then rebooted, and all of the apps except the paid apps have gone. I installed a couple of apps from the. Market and they have also gone after reboot.
I turned a2sd off, then I was able to keep apps over a reboot ..... but I would like to get a2sd working.
Any ideas?
For now I am manually moving apps to SD card.
Sorry for this question...
Your 3G, Wifi is working.. My wifi, 3G is not working..
3g (once APN set up) and wifi both working well
Looloup said:
@bortak
1. Done OK
2. Done OK
3. Done OK
4. Done ... BUT ... no Gapps, no Terminal app ... not much really not even a keyboard (even after 2 reboots)
- The link to Gapps for CM7r2 no longer works
5. Unable to try this as no Terminal app ... and I can't get ADB working on my PC.
Click to expand...
Click to collapse
Did you do a wipe after flashing the rom? I had a similar problem when doing that. CWM Recovery also deletes the sd-ext partition, and as on cm7r2 there are also system apps on sd-ext, they are gone.
With the included a2sd apps should be moved to sd-ext automatically. It is not shown on the phone.
How big is your ext4 partition? And did you create it with CWM Recovery? If so, try recreating with gPartEd.
muellersmattes said:
Did you do a wipe after flashing the rom? I had a similar problem when doing that. CWM Recovery also deletes the sd-ext partition, and as on cm7r2 there are also system apps on sd-ext, they are gone.
With the included a2sd apps should be moved to sd-ext automatically. It is not shown on the phone.
How big is your ext4 partition? And did you create it with CWM Recovery? If so, try recreating with gPartEd.
Click to expand...
Click to collapse
This.
10chars
I created the extra partition via CWM recovery - maybe too large as I made it 4gb.
I wiped the device and Dalvik cache after flashing the ROM.
I then set a2sd via terminal and allowed reboot.
I then downloaded apps (or restored via Titanium)
Eventually ran out of space when downloading apps - so they were not being moved.
Apps run OK.
When I did a normal reboot - the apps 'disappeared '.
Reading Bortaks debug guide the only thing I can see that looks relevant is to try reformatting the SC card with 2 primary partitions.
Read what i wrote? Do the following:
1) Recreate the partitions on your sdcard using GParted
2) Do a full wipe BEFORE flashing.
3) Re-flash the rom and select stock a2sd
4) Do NOT wipe again
4) Reboot, start Terminal emulator, set up a2sd
5) See if apps stay
On my first try I selected stock A2SD and set it up as explained using the terminal. (using a 2GB ext3 partition, placed after FAT32)
I rebooted and everything seemed fine, and I installed several apps. After a while, though, I got the "insufficient storage" error whenever I tried to install something. In the application manager the internal memory available had a large negative value.
I then wiped everything, reformated the 2GB ext3 partition to ext4, using "Minitool parition wizard" and reinstalled the Sandvold ICS ROM with Amarullz. Everything seems fine, and it shows 2GB internal memory. However, I've noticed that the ROM gets more unstable the more apps I install (it shows 500MB installed apps now, after removing around 50MB)...
Most of the time what happens is that system apps start crashing (Google Music, Dialler, Contacts, etc.) out of nowhere. After a while normal apps crash on execution as well. Google music is useless, as it crashes after a few songs and brings down the whole phone. Other music apps don't have this problem.
Am I doing anything wrong with the way I set up Amarullz? Should I retry stock A2SD with ext4?
I'm using stock HBOOT, Nova launcher and stock kernel.
Got there ..... but.....
After repartitioning my SD card for the third time ... I finally have this working.
Thanks to all for help/advice ..... but (isn't there always a but) ....
Downloads from the Market/Play are extremely slow maybe 5+ times the same apps took before .... I have tried on different WiFi connections - still the same.
Is this a consequence of the write speed of my SD card (it is only class 4) ... I did see a post in another thread where a class 4 wasn't recommended, but this was refuted by others using a class 4 card.
Otherwise all apps seem to be running OK, with no real loss of performance.
I guess once I have finally loaded up on all the apps I want, the Play updates will be more infrequent and less of an issue.