Related
Hello,
this is my first attempt to Android build for HD2, i'm not a dev, i only made this build for my personal purpose and i thought to share it with this community.
Before some specs i wanna thanks some people:
-XDA-Developers
-DFT Forum
-Cotulla and bepe for MAGLDR link
-RaiderX303 for ClockWorkMod link
-M-Deejay for Kernel link
-Gauner1986
-Taknarosh for Bootanimation link
-Rafpigna for his fonts link
-EStrong Inc. for Es-Esplorer link
and......
all guys at #HTC-linux, DarkStone, Markinus, Projection, Bauner, Tytung, White-Energy and many other, give me a call if i missed you
REQUIREMENTS:
Hardspl 2.08
MAGLDR 1.11 (follow my sig for 1.12)
ClockWorkMod
SPECS:
Based on Desire Sense 2.29.405.5 with all stock apps.
Kernel by M-Deejay 10.3
Data and Apps to EXT 2/3/4
GoogleMaps 5.0 Included
Es-FileExplorer included
Custom Fonts (ty to Rafpigna)
Custom BootAnimation (ty to Taknarosh)
No Sound on boot
Battery with %
Properly rooted
Quadrant score 1700-1800 @ 998
Quadrant score 2000-2200 @ 1536
Battery at sleep 4-6 ma
Code:
[CENTER][B]INSTRUCTIONS:[/B][/CENTER]
[B]1. back-up your SD Card files and folder
2. Copy the file inside "Copy to SD Card Root"and "Copy to SD Card" folder to your main root SD Card
3. Boot you phone while hold and press "power" button till MAGLDR menu will appear.
4. Choose n.5 voice, "USB Flasher"
5. Plug in your USB cable to your phone and PC till when "wait USB...USB" will appear
6. Run "DAF.exe" from ClockWorkMode, your phone will go to reboot, press and hold power button to enter MAGLDR menu
again.
7. From MAGLDR menu, choose "Boot AD SD"
8. Now you are in ClockWorkMode (CWR) menu.
9. Choose "advanced"->"Partition SD Card" and grab the EXT size of your choice, i suggest to don't go over 2048.
10. Set Swap Size to 0
11. Now you have an EXT3 partition in your SD card, you should be good to go but if you want an EXT4 partiton, you
need to :
11A. Boot into any Linux Live Distro build (Ubuntu 10.10 is what i have) and format your sd card.
11B. Search in XDA-Developers forum for a Tutorial (don't remember yet the link lol)
12. From CWM menu choose "install zip from SD card"-->"Choose zip from sdcard"--> next find "DR Desire HD2 V.0.1 and press the green button till the process will end and then reboot your phone.[/B]
-----------------------------------------------------------------------------
Testes on my phone with daily use and it works fine.
TMOUS users : untested.
VoiceInCall fix, inside.
My Radio is 2.10.50.28_2
-----------------------------------------------------------------------------
DOWNLOAD.
happy flash.....and be kind
ChangeLog:
Code:
V.0.1
Initial Release
UPDATES:
(copy your choice .zip to your SD card, reboot to CWM and apply .zip from menu)
Gauner Kernel : Download No Overclock but less power consummation and more stable (smartass Gov)
MDeejay 10.4 : Download
Congratulations on your first build, will download and test tomorrow
Downloading...
I'll report back soon.
yay nice to see another android dev on the scene, welcome
please another mirror for downloading...i cant download it -.-
Hi,
Thank you so much. This is the best nand sense rom that i have come across so far. I love that you decided to bundle Data2EXT with Stock Desire.
Aside from some wakeup lag (bearable), I haven't been able to find any problems.
Keep up the good work.
Thanks
Mostly, i dont have lag on power, though it seems to be a common Sense build issue, anyway i did put some kernel updates on post #3.
I used all the day my build with SetCpu @ 1190 without problem and lags and battery is fine, worth a try .
Check in first post what radio i'm using, maybe changing it can help.
smakazmi said:
Hi,
Thank you so much. This is the best nand sense rom that i have come across so far. I love that you decided to bundle Data2EXT with Stock Desire.
Aside from some wakeup lag (bearable), I haven't been able to find any problems.
Keep up the good work.
Click to expand...
Click to collapse
Looks good, tempted to download as the build I'm using at the moment doesn't work with MDJ S10.3.
Maybe, you could include a stock framework and stock fonts for stock lovers?
No problem......i will make an update with both stock fonts and framework.
shadiku said:
Looks good, tempted to download as the build I'm using at the moment doesn't work with MDJ S10.3.
Maybe, you could include a stock framework and stock fonts for stock lovers?
Click to expand...
Click to collapse
build looks nice - this is my second nand flash both desire based.
The first worked perfectly and then i installed yours so i could get the sd memory but now im finding that alot of the apps that previously worked no longer do and i have also lost contacts.
The previous build was lightning fast whereas this seems to have a slight lag.
Do you think i have done something wrong? And should i download those 2 updates
Which build you was using?
Looking at your reply i suppose that you was using a non Data2Ext build, so it is normal:
_ Loosing App and Data if not a previous backup with Titanium backup,Mybackup,...
_A little lag, because Data are on SD card.
perfectknight75 said:
build looks nice - this is my second nand flash both desire based.
The first worked perfectly and then i installed yours so i could get the sd memory but now im finding that alot of the apps that previously worked no longer do and i have also lost contacts.
The previous build was lightning fast whereas this seems to have a slight lag.
Do you think i have done something wrong? And should i download those 2 updates
Click to expand...
Click to collapse
No, it wasnt a d2ext build (DFT's Desire build)
I guess you are right and i should expect lag etc
Am i right to assume that the apps that i find that arent working are doing so because they dont support a2sd? or should they 'believe' that they are on the rom?
I find that a large number of them, when i try to load them, just flash up the screen asking me to force close them.
Basic apps that should always run like Lookout security (worked previously) but only works intermittently now and i keep having to register apps such as the Android Market.
Also i cant seem to save contacts.
I dont know if there are apps that doesn't support a2sd but i just gave a try to Lookout Security and it does work as expected and i also can save contacts without any problem.
My guess is that you have something wrong with your SD card partition, read again the Readme.txt for "how to" partition it and before flash again the build, give a wipe from Clockworkmod menu.
perfectknight75 said:
No, it wasnt a d2ext build (DFT's Desire build)
I guess you are right and i should expect lag etc
Am i right to assume that the apps that i find that arent working are doing so because they dont support a2sd? or should they 'believe' that they are on the rom?
I find that a large number of them, when i try to load them, just flash up the screen asking me to force close them.
Basic apps that should always run like Lookout security (worked previously) but only works intermittently now and i keep having to register apps such as the Android Market.
Also i cant seem to save contacts.
Click to expand...
Click to collapse
yeah i think that's what i will do.
Although i followed all the steps - im sure i must have gone wrong somewhere.
I was also finding that some of the games dont save my progress.
I'll let you know how i get on.
Thanks for your help
thanks for this rom seems to be the best desire rom,only one thing can you increase usb transfer speed?Markinus has done this with his rom,thanks again
Thanks
Anyway USB transfer it is already patched, though i've seen that it is slow while using Multi Mount SD card.apk, can't go over 2,00 mb/s.
kgian2007 said:
thanks for this rom seems to be the best desire rom,only one thing can you increase usb transfer speed?Markinus has done this with his rom,thanks again
Click to expand...
Click to collapse
this version is awesome! thanks
Hi,
Sorry to join that late but I was conviced that the desire HD had the closest hardware to the HD2.
Now knowing it is not would you be king to provide a working link ?
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
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.
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.
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
nlooooo said:
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
Click to expand...
Click to collapse
Why? No.
If you can live with slower perfomance, active the stock a2sd again with answers: y, y ,y
vBurak said:
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
Click to expand...
Click to collapse
I had exactly the same problem. At first I chose during flashing the option "Regular a2sdext" as it seems good to me. However, nothing has changed, it was not working for me at all. Then I reflashed again with "Stock a2sd" and after booting I went to terminal and activated it. I tried it with several combinations (in some of them I got the message "Insufficcient storage available" and I only had like 5 apps installed...). At the end I finally made it work with the combination that is recommended by Sandvold - Y N Y. After that I have been installing several apps and my internal memory does not go down almost at all :good:... I will see later, but for now, this is the best set up for me....
I had this problem
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I have been testing 0.18 for a few hours now. Your phone issues should be resolved except you will encounter a new issue. You will lose superuser privilliges, to restore this, you have to install a zip of superuser through recovery.
My comments on Sandvold ICS 0.18
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
CzarD said:
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
Click to expand...
Click to collapse
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
skubko said:
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
Click to expand...
Click to collapse
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
CzarD said:
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
Click to expand...
Click to collapse
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
UserMatty said:
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
Click to expand...
Click to collapse
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
skubko said:
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
Click to expand...
Click to collapse
I did a full wipe again, and everything went back to perfect working order. Thanks man
CzarD said:
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
I did a full wipe again, and everything went back to perfect working order. Thanks man
Click to expand...
Click to collapse
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
It's not okay, minitool doesn't do that correctly. Use 4ext recovery to partition your sd card.
Sent from my HTC Desire using Flashes and Thunders
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
just to add - I have Amon RA Recovery and I partitioned my SD card by that, it was also working without any problems everytime I did it...
@CzarD - I am glad to hear that the wipe helped you...
You should try out the Amarullz or INT2SD from the Aroma installer. I have INT2SD and I have 1,3G of free space (2G EXT partition)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
As I know, swap in linux is somewhat like virtual memory in Windows.
Will be launched when the system is in low memory.
That's exactly everything I know
I'm now Using Revolutionary CWM v4.0.1.4, stock HBOOT, S-OFF
And just follow your way to full wipe then install the system again(stock a2sd)
I still can't get the root access. thus, I can't activate a2sd in terminal
PS: with Beta 0.18
But Beta 0.17.1 currently work!