Related
Hey all,
Wanted to post CM7 here for everyone to enjoy.
Neopeek has been working hard to get this build up and running, he's been doing great work!
Neopeek's Original Post - if you wish to see Neopeek's original post about the CM7 topic.
Also, since now I am using his new ClockWordMod method - CWM Recovery thread
As is stated in the title, this is mainly for devs/testers. Lots of things are broken, and there will be frequent updates.
There are two methods to using this build:
1) ClockWorkMod (requires 3 separate ext2 partitions)
2) Loop'd system.ext2 image (like XDAndroid) [In progress]
The benefit of #1 is a dedicated system/data partition, and *partial* USB mass storage support.
The benefit of #2 is, it's easier .
I still have to work to get #2 up, but I wanted to post #1 ASAP. Lots of work to flesh out the post to, be patient!
I've been holding off on releasing this CWM version of CM7, because I'm still having a lot of bugs with it. Still needs quite a bit of work, but it's getting late for me tonight - I am going to release it, let me know if you guys make improvements, I'd love to incorporate them!
Main issues seem to be related to my durn CDMA device. Need to break into some logs to see what's goin on, it may be a little while! I think GSM folk will be fine. Let me know!
Downloads
Download #1
How-to
Method #1 (ClockWorkMod)
****WARNING****
If you setup dedicated partitions using this method, normal XDAndroid builds will think that you want to use dedicated partitions. I had to modify the init to get it to work correctly (I basically broke the partition detection in the init). It's not pretty, but I don't know of a better way to resolve that issue - let me know what ideas you guys have!
Setup:
You will need to create three (3) ext2 partitions on your SD card. This is not extremely simple, but by no means impossible .
If you're using Windows, I like the Mini Partition Tool. If you're in Linux, I usually use gparted.
This takes a little bit of planning - but in total, I would say you need a minimum of 450mb of space for all three ext2 partitions. So work out how much free space is left (if you want a bigger data partiton, or system partition account for it!) and make that the first partition - FAT32. Make sure all the partitions are "primary", not "logical"! See the partition layout below:
1 - FAT32 Primary (remainder of card)
2 - ext2 Primary (at least 150mb, system partition)
3 - ext2 Primary (at least 250mb, data partition - I wouldn't go over 1gb here)
4 - ext2 Primary (at least 50mb, cache partition)
Don't worry about putting anything in these ext2 partitions, everything is populated by Android and CWM. The FAT32 partition is used to kick off Android, while system, data and cache are all ext2 partitions. Reason for this is, hopefully if things go haywire we can blast out cache, not data . Also, it should be easier to update using this method than previously.
Extract the file. Look at the folder it created (npkboot). Copy the entire npkboot folder to the root of your SD (for now this is required - the init assumes there's a /sdcard/npkboot/tmp folder). There will also be an update.zip, in this case update-cm-7.0.0-neopeek.zip. Put this at the root of your SD card (this makes finding it in the menu much easier!)
Copy the appropriate startup.txt from the STARTUPS folder.
Find haret.exe in th npkboot folder. Run it, and watch the boot process carefully! It will ask you to hold the vol down button to enter recovery, and you have 10 seconds to do so.
Assuming you manage to do this correctly (I had some trouble at first ) you should see an icon like a hat. Wait for the menu.
Buttons:
End key - back (back button seems to do this as well...)
Send key - enter
Vol up - up
Vol down - down (menu button seems to do this as well...)
If this is the first install, go to "install zip from sdcard". Then "choose zip from sdcard" This will install the system image to the system partition from the update.zip.
If you need to wipe the data partition, you can do that under "mounts and storage". You shouldn't need to do this unless you're going from gb -> froyo or visa-versa. Froyo -> froyo should 'just work', as always YMMV.
There are A LOT of options in replimenu. The only ones I have used are install, format /data, /system or /cache and Reboot. According to Neopeek, there are several things that should not be used:
Neopeek said:
* Don't use "factory wipe" in CWM (you have been warned )
* Don't use "format sdcard" unless you know what you do (you have been warned )
* Don't use "partition sdcard" unless you know what you do (you have been warned )
Click to expand...
Click to collapse
Once you've installed Android, go back to the main menu and "reboot system now" There are some bugs, for example "reboot recovery" and "power off" all just reboot the phone to WinMo.
Boot haret again, but this time don't hold the vol down to enter recovery - boot as normal!
#2: Much simpler method, similar to XDAndroid builds.
Extract the file to your desktop. Go into the CM7 folder, look for the STARTUPS folder - grab the appropriate startup.txt, move it to where haret.exe is.
Copy everything in the CM7 folder to the root of your SD card - if you want to run it from a folder, create a rel_path=CM7 statement in your startup.txt after the set cmdline (if you want a different folder, change the CM7.)
Grab the ts-calibration file attached to this post (for RHOD), or go to this post for a list of ts-calib's. You can also create your own on boot, but may have to revert to an older kernel to do so.
Run haret.exe!
****Not Working****
CDMA seems broken - still! I did some testing with hyc's RIL and it's still busted, so there's something in the system image messing with it - Airplane mode was checked, and I could not uncheck it.
In addition, phone.apk seems like a forceclosefest. Neopeek did point this out in his original thread...
Mobile data - broken (Fixed soon)
Wifi - broken (Fixed soon)
System needs optimization for RHOD - was originally build with DIAM in mind - so it's a little slow.
Failed wakes seem pretty bad - sometimes it is quite difficult to wake the phone.
Boot animation seems to be not present - I'm looking into fixing it, probably graphics libs if anything that's broke it.
Dev Content
This new method should be great for anyone who wants to make their own updates - you can easily peek into the system image and make changes at will, then just install the new system image! You can even rolll updates instead of an entire system image if you wish.
The script language in ClockWorkMod is called "Edify", see this thread to learn about the syntax. This is related to the META-INF folder you see in the update zip.
There's a few differences in the rootfs', the main being the init. There's also some additional files it looks like neopeek added for Recovery specifically.
This is amazing work. Props to all involved.
Does anyone have any feedback on this build?
arrrghhh said:
Long story short, you need a ext2 partition and a fat32 partition - ext2 needs to be between 400-600mb, fat32 can just take the remainder of the card's space.
Click to expand...
Click to collapse
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
PM message
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Sorry, I need access to a Linux box to do the 'easy' build... I will when I get home tonight from work, promise .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
You can make it as big as you want I guess... I'm not sure how neopeek sets up the data partition to be honest, I'd have to ask him.
Edit - in lieu of the post below, I adjusted the first post to say it needs to be at least 400mb .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
I have 700 mb and is working well,you can use as much as you want
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
I wonder if CDMA data is working with this...that is my biggest issue with GB right now...
HELICOPTER88 said:
I have 700 mb and is working well,you can use as much as you want
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
Click to expand...
Click to collapse
yeah easy for you to say, that sounds complicated.
I will wait for the other one.
Do you know the ETA?
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
Still need to upload, sorry!
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
I was looking at that too when extracted the files and didn't see what you are also missing.
Sorry about the confusion guys, I probably shouldn't have put the download link up before I was done .
I just fixed it, so #1 is good to go! I'll get #2 up later, thanks.
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
(...solved...)
it's necessary create a swap partition?
What works in this build?
fishingmedic said:
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
Click to expand...
Click to collapse
The rootfs is more or less collapsed in these.
Kernels are straight from XDAndroid repo.
OC is the same, startup.txt is fairly similar .
Quincux said:
it's necessary create a swap partition?
What works in this build?
Click to expand...
Click to collapse
Swap is not necessary.
Most things that work in XDAndroid work in here. Lots of other things are broken here tho .
Okay, downloaded and installed without problems.
First impressions:
Absolutely great build in terms of response!
No delays in menus, etc.
Also, this looks like the first build that may have little or no clock delay, so no need for clocksync !!! (to be confirmed since I did not use it very long, die to issues below)
However...
1) No WIFI
2) No Mobile data (2G/3G)
3) camera not working (could be just blackstone)
- maybe other issues, decided to wait for more feedback before continuing, without market access there's little point...
Device: Blackstone
Kernel: extensive testing with provided one (1276), later switched to 1277, to fix audiostuttering, no wifi or mobile data in either...
As a reference, used many NeoPeek / XDAndroid builds, generally got WIFI/Mobile data working until now...
Love to hear if someone else (blackstone?) got WIFI/2G/3G working...
Oh, well, as I understood, this was an early "developer" release, still plenty of room for improvements!
Cheers,
Robbert
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
FroyoB Hercules V4 Final
This ROM is based on tiad8 new rom - thanks tiad8.
Changes:
changed back to old fonts!!!
add new launcher 2.3.3.
add new market.
changed phone - thanks to cytown from XDA.
changed theme.
some bug-fixing...
What works:
* SuperUser
* WiFi
* GPS
* 3G Network
* GPS
* Phone (new)
* SMS
* Good Battery Life
* camera
* camcorder
* new market
* youtube
How to install:
A. Download:
V1: http://www.multiupload.com/ZSOG83Q1K7
V2: http://froyob.blogspot.com/2011/07/froyob-hercules-v2-final-release.html
V3: http://froyob.blogspot.com/2011/07/froyob-hercules-v3-first-beta-release.html
V4: http://froyob.blogspot.com/2011/07/froyob-hercules-v4-final_18.html
B. Before install :
1. Format your SDCARD make 4 Partition with recommended size:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 300MB )
3rd partition: EXT2 (data / 300MB)
4th partition: EXT2 (cache / 300MB)
Be sure make all 4 partition primary
2. extract and copy folder npkboot to root of sdcard and put in kernel that you like (I use kernel 1295 on my Raphael and it very good).
3. copy FroyoB_Hercules.zip in to root of sdcard.
C. Install:
1. run Haret, and wait when it will be asked to press "Volume Down" shortly (!!important!! shortly) to launch
ClockworkMod Recovery or any other key to usually continue booting into Android.
Press volume Down and wait for menu Recovery.
2. In menu recovery choose "install zip from sd-card" choose zip from sdcard and select "FroyoB_Hercules_V2_final.zip"
Confirm installation . after installation finish, Confirm installation then back to main menu (press ok key) and
choose: reboot system now.
3. Run HARET again and boot into Android.
when you report a bug please do it in this format:
1. my device is:
2. I'm using kernel:
3. I'm using Ver:
4. What CWM Ver:
5. the problem is:
thanks
Nebarkay
anyone tested this?
im coming from HD2, and wondering why you need all the 4 diffrent partitions? which program do you recommend to do this?
can you post any screenshots? would like to see before i go ahead an try
loni90 said:
anyone tested this?
im coming from HD2, and wondering why you need all the 4 diffrent partitions? which program do you recommend to do this?
can you post any screenshots? would like to see before i go ahead an try
Click to expand...
Click to collapse
The four partitions are laid out..
"1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 300MB )
3rd partition: EXT2 (data / 300MB)
4th partition: EXT2 (cache / 300MB)"
However, cache is not necessary - especially not 300mb. I think neopeek recommended 50mb, but I don't think it's necessary at all.
Other builds in this section of the forum require only one FAT32 partition. This is because the data & system are just loop mounted.
For creating partitions I recommend this:
MiniTool Partition Wizard Home Edition
http://www.partitionwizard.com/free-partition-manager.html
it's free and very useful
loni90 said:
anyone tested this?
im coming from HD2, and wondering why you need all the 4 diffrent partitions? which program do you recommend to do this?
can you post any screenshots? would like to see before i go ahead an try
Click to expand...
Click to collapse
EASEUS Partition Master Home Edition for Windows is the fastest tool I've used. Haven't had any problems.
You need the partitions on your SD card because this ROM is in CWM format and will install to those EXT2 partitions (/system, /data, /cache). The order must be:
1. FAT32 (FAT32)
2. /system (EXT2)
3. /data (EXT2)
4. /cache (EXT2)
BE SURE TO REMOVE THE "/" WHEN NAMING THE PARTITIONS!! (I.E. "system", not "/system")
maff1989 said:
EASEUS Partition Master Home Edition for Windows is the fastest tool I've used. Haven't had any problems.
You need the partitions on your SD card because this ROM is in CWM format and will install to those EXT2 partitions (/system, /data, /cache). The order must be:
1. FAT32 (FAT32)
2. /system (EXT2)
3. /data (EXT2)
4. /cache (EXT2)
BE SURE TO REMOVE THE "/" WHEN NAMING THE PARTITIONS!! (I.E. "system", not "/system")
Click to expand...
Click to collapse
EASEUS is fantastic, I forgot it did ext2 as well. I use it to resize NTFS partitions all the time!
Can anyone confirm it working on Sprint TP2? and what does and does not work?
Thanks guys!
I installed on a Sprint TP2 last night but haven't really had a chance to drive it full throttle. Did try turning on BT unsucessfully. Getting longer life than FRX06 so far. Usually I have to charge before my 8 hour shift is done. Today I was able to go 11 hours with moderate use and still had 68% showing on the meter when I had a reboot to windows while trying to update an app. We'll see how it goes the next few days now that all of my apps are installed thanks to TB.
i keep on getting an issue with no signal. I did all the steps successfully but when it loads i get no signal. and then on reboot i get signal. I rebooted once again and now i have no signal what so ever. am i missing a step?
been using this for a couple of days...
device: at&t tilt 2
kernel: wistilt2
testing period: 3 days
battery: one full day... charge all night
signal... weak at times
system speed: awefully slow... worse then looped
3d: not terrible not great.. to be expected
conclusion: not for me.. too slow.. spotty signal... not the best battery life.. have seen better...
ok, now i know.
but i want to fix android to my lil´brothers TP2, and wondering what ROM i should use? which one is the most stable, and complete - and closest to stock? any good HTC sense roms?
loni90 said:
ok, now i know.
but i want to fix android to my lil´brothers TP2, and wondering what ROM i should use? which one is the most stable, and complete - and closest to stock? any good HTC sense roms?
Click to expand...
Click to collapse
Closest to stock and Sense do not go together. Sense is an abomination, horrid UI for Android. I don't get why it made WinMo so great but Android so horrid.
I recommend FRX06 myself, 07 is going to be out soon (promise!)
loni90 said:
ok, now i know.
but i want to fix android to my lil´brothers TP2, and wondering what ROM i should use? which one is the most stable, and complete - and closest to stock? any good HTC sense roms?
Click to expand...
Click to collapse
i have a really nice version of gingerbread that i am modifying... i will send you a zip if you want to try...
Trekfan422991 said:
i have a really nice version of gingerbread that i am modifying... i will send you a zip if you want to try...
Click to expand...
Click to collapse
I would very much love to give ur gingerbread build a try, so if u could please send me a zip as well. Thanks
villa15 said:
I would very much love to give ur gingerbread build a try, so if u could please send me a zip as well. Thanks
Click to expand...
Click to collapse
Actually I'm having one small problem... the android marketplace is only displaying like a few hundred apps...
I need to do some more research to find out why... so if you want me to fix it first or there are quite a few alternative marketplaces u can install... one I use on it right now is called--- 1 mobile market...
If you don't care I will send u the zip to try... it has gapps...
Just pm your email address
sooo, been testing this for a few days on my Rhod100... and have to say it pretty much sucks...
signal drops to 0 quite often, i get random reboots when trying to call someone / in call / when hanging up, apps that use the inet connection force close when i lose data connectivity (meebo, xda, gmail), the font is _horrible_ (yes i know, fontchanger is included, but it doesnt work the way one would expect it to)
to sum it up, it's like a F1 car without a steering wheel.. fast, fun for the first minute, but completely useless
going back to FRX06 looped and finally deleting NP from my favs
edit : forgot to mention the new audio code isnt integrated, so you cant use the new .39 kernel, but thats just the icing on the ****cake
Trekfan422991 said:
i have a really nice version of gingerbread that i am modifying... i will send you a zip if you want to try...
Click to expand...
Click to collapse
I would like to get it too. Thanks!
thanks for this rom
but when I started haret.exe file and press Run botton, I saw this message:
that default.txt doesn't found
what's problem?
bahaa87 said:
thanks for this rom
but when I started haret.exe file and press Run botton, I saw this message:
that default.txt doesn't found
what's problem?
Click to expand...
Click to collapse
You have to choose your startup.txt according to your device,there should be a folder called startup,check inside for your device and copy it where there's haret.exe
Thank you I tried the ROM on 1 / 7 is good and where some of the problems
I will work on this
FroyoB Hercules V4 Final
This ROM is based on tiad8 new rom - thanks tiad8.
Changes:
changed back to old fonts!!!
add new launcher 2.3.3.
add new market.
changed phone - thanks to cytown from XDA.
changed theme.
some bug-fixing...
What works:
* SuperUser
* WiFi
* GPS
* 3G Network
* GPS
* Phone (new)
* SMS
* Good Battery Life
* camera
* camcorder
* new market
* youtube
How to install:
A. Download:
V1: http://www.multiupload.com/ZSOG83Q1K7
V2: http://froyob.blogspot.com/2011/07/froyob-hercules-v2-final-release.html
V3: http://froyob.blogspot.com/2011/07/froyob-hercules-v3-first-beta-release.html
V4: http://froyob.blogspot.com/2011/07/froyob-hercules-v4-final_18.html
B. Before install :
1. Format your SDCARD make 4 Partition with recommended size:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 300MB )
3rd partition: EXT2 (data / 300MB)
4th partition: EXT2 (cache / 300MB)
Be sure make all 4 partition primary
2. extract and copy folder npkboot to root of sdcard and put in kernel that you like (I use kernel 1295 on my Raphael and it very good).
3. copy FroyoB_Hercules.zip in to root of sdcard.
C. Install:
1. run Haret, and wait when it will be asked to press "Volume Down" shortly (!!important!! shortly) to launch
ClockworkMod Recovery or any other key to usually continue booting into Android.
Press volume Down and wait for menu Recovery.
2. In menu recovery choose "install zip from sd-card" choose zip from sdcard and select "FroyoB_Hercules_V2_final.zip"
Confirm installation . after installation finish, Confirm installation then back to main menu (press ok key) and
choose: reboot system now.
3. Run HARET again and boot into Android.
when you report a bug please do it in this format:
1. my device is:
2. I'm using kernel:
3. I'm using Ver:
4. What CWM Ver:
5. the problem is:
thanks
Nebarkay
Problem SD card formating
Hello,
I try format SD card a and create partition but still not function.
What program have I use for formating and creating partition?
Thanks
MagorX said:
Hello,
I try format SD card a and create partition but still not function.
What program have I use for formating and creating partition?
Thanks
Click to expand...
Click to collapse
On Linux - fdisk, gparted.
On Windoze... don't know many options other than some "Mini Partition Tool"... Win doesn't like to read Lin partitions. At all.
To the OP - perhaps you should provide some guidance here. It's very different from how XDAndroid builds are done, with one giant partition and looped mounts.... much easier for newbies to handle .
MagorX said:
Hello,
I try format SD card a and create partition but still not function.
What program have I use for formating and creating partition?
Thanks
Click to expand...
Click to collapse
Here is a guide for you:
http://froyob.blogspot.com/2011/06/how-to-install-froyob-hercules-v2-on.html
Does the camera work?
Cellulario said:
Does the camera work?
Click to expand...
Click to collapse
yes. photo and video.
dude,
ive just installed it. i parttitioned my mass memory with ubuntu and it worked like a charm. its probably the fastest build ive ever used. working camera, and good battery life too! one problem tho, whenever i try to enable wifi, it says error. why is that?
Hello,
on my Raph100 all work fine (BT, USB, camera, ecc..), only problem are crazy led on capacitative button.
Kernel 1333
Pixel_ubuntu said:
Hello,
on my Raph100 all work fine (BT, USB, camera, ecc..), only problem are crazy led on capacitative button.
Kernel 1333
Click to expand...
Click to collapse
That "crazy led" represents sleep.
There's an APK called LEDEffects.apk. This will allow you to customize how this LED is treated. In XDAndroid builds it's in AndroidApps/Other IIRC.
"1. run Haret, and wait when it will be asked to press "Volume Down" shortly (!!important!! shortly) to launch
ClockworkMod Recovery or any other key to usually continue booting into Android.
"
I need run haret in folder npkboot ?? i run this e no asked for Volume Down!
**resolved**
Other question, dont have market?
Anyone with screenshots?
Anyone with screenshots?
This ROM is really nice!
I have a question for npkboot ROM's. After I run the installation from npkroom directory the installation starts and I can complet it without any problem. If I want to move the content on mpkboot directory into the root directory of my sdcard in order to make the OS start at booting, should I copy all the content of the directory npkboot into /sdcard/? in this case, should I keep two copies of all files one in /npkboot/ and one in /sdcard/? I hope I was clear enough. To make it short, what file sould I keep or/and moove to make this rom start with Gen.Y boot application?
Second question, how could I make the font bigger! It's too small for me
How did you resolved the Volumn Down issue.
fabioaz said:
"1. run Haret, and wait when it will be asked to press "Volume Down" shortly (!!important!! shortly) to launch
ClockworkMod Recovery or any other key to usually continue booting into Android.
"
I need run haret in folder npkboot ?? i run this e no asked for Volume Down!
**resolved**
Other question, dont have market?
Click to expand...
Click to collapse
Maybe you haven't copired npkboot into sdcard, you will have something like /sdcard/npkboot/ and from there run Haret. Rows will start scrolling down, at a certain point the screen will be cleared and only one line will appear on top saying to press "volume down"
Nope I have have the same. I downloaded the V2. Unzip and put npkboot at the root of sdcard. My location is /sdcard/npkboot/ . So is this correct or I have to keep everything inside the npkboot to /sdcard/
Looking it carefully I am getting this error. Currently only 1 or 2 FATs are supported, Not 255
What does this mean.
Can anyone help me out?
Problems Resolve Thanks
arrrghhh said:
That "crazy led" represents sleep.
There's an APK called LEDEffects.apk. This will allow you to customize how this LED is treated. In XDAndroid builds it's in AndroidApps/Other IIRC.
Click to expand...
Click to collapse
Thanks arrrghhh, LEDeffects partial solved the problem, my problem is like this:
http://forum.xda-developers.com/showthread.php?t=669796
Pixel_ubuntu said:
Thanks arrrghhh, LEDeffects partial solved the problem, my problem is like this:
http://forum.xda-developers.com/showthread.php?t=669796
Click to expand...
Click to collapse
Ah, yea there's no good fix for that. Android/Linux doesn't handle the capacitive panel so well... When I had my RAPH, I remember if you touch from the very outside of the panel/button and ensure the button lights up before you press it - this usually ensures that the button you're pressing is actually picked up.
I've heard of the panel going completely dim, and never responding to touch input. Like I said, that damned panel is not so well supported. Not sure what's wrong with it, other than it's a bad design from the start. I'm sure Linux could handle it better tho... Devs welcome .
Cellulario said:
This ROM is really nice!
I have a question for npkboot ROM's. After I run the installation from npkroom directory the installation starts and I can complet it without any problem. If I want to move the content on mpkboot directory into the root directory of my sdcard in order to make the OS start at booting, should I copy all the content of the directory npkboot into /sdcard/? in this case, should I keep two copies of all files one in /npkboot/ and one in /sdcard/? I hope I was clear enough. To make it short, what file sould I keep or/and moove to make this rom start with Gen.Y boot application?
Second question, how could I make the font bigger! It's too small for me
Click to expand...
Click to collapse
As for your first question, Neopeek butchered the rootfs pretty bad so you can't move the folder. Just tell Gen.Y to use the npkboot folder (there's registry settings for Gen.Y...)
As for your second question, lcd.density? Not sure.
Hi
I have rooted my phone with unrevoked, s-off'ed with alpha rev 1.8, partitioned 1gb of my 4 gb card to ext 3 and installed Gingerbread F1 V3 Ap2SD ENG.
On first load of the rom i can see that my SD card FAT 32 storage has been reduced but the only other memory internal memory which was at 147mb when i first booted the rom.
All apps are installing to the internal memory by default with only the option of moving to the SD FAT 32 partition. and there is no option to move to the sd ext3 part as there is no option - so I have lost 1gb off my sd card.
What have i done wrong?
on a 2nd note i appear to have a call delay when answering the phone my radio version is 32.49.00.32U_5.11.05.27 - do i need to update this ? will it solve the problem ? my carrier is vodafone UK.
appreciate the help
ararararar... Sorry had to do something.
This has been explained SO many times by me included. The way a2sd works is by symlinking the folder containing the apps(/data/app) to you ext-partition.
You cannot see this partition listed in the system info, as the partition is not supposed to be there. The system have no way of knowing that you are using an ext-partition, as it just installs apps to /data/app, however as it's symlinked to ext, they are actually being placed in sd-ext/app.
This means that you will only see you internal memory, but it still works. Your apps will just take up less space on internal, as the apk file is placed on the ext-partition. They will still take up some space for data and dalvik cache.
edit: bonus info. Install "quick system info" or "titanium backup" from the market to see the size of your ext-partition in those apps.
edit2: and if i did not make my self clear. The partition-size info in the system settings is not supposed to be a partition manager. It's written to be userfriendly, and it only provides the regular user with the partitions they should care about(/data and /sd-card). If you want a detailed view of all your partition(and there is more than a few) go get root explorer. It'll let you play around with all the partitions mounted.(you won't have access to recovery, bootloader and so on from here)
Ok thanks. I'm new to this and there's so much info to take in
With regards to the radio is there a simple way of flashing as I have alpha rev installed the method via recovery wont work. I see alot of people talking about doing this through a terminal but I could not find a comprehensive guide for this like the xda root guide. Thanks.
Darren
Sent from my HTC Desire using XDA App
Well i take it that your cache partition is too small(this is why people using alpharev cm hboot cannot use recovery for this). In that case you have already flashed another hboot(using "fastboot flash hboot hboot.img") if you haven't done this, you cache-partition should not be too small, and the recovery method should be able to do this just fine. If you have done this, use the same command to flash the radio eg "fastboot flash radio radio.img"
Either way it is very unlikely to fix your call delay(read: it won't fix your problem, as it's got nothing to do with the radio). It's a problem caused by some incompatibility between the htc libs and GB. It's quite common on GB roms apparently. Wait for HTC to release the real GB update, and we might very well be able to solve this problem.
dazzr123 said:
Ok thanks. I'm new to this and there's so much info to take in
With regards to the radio is there a simple way of flashing as I have alpha rev installed the method via recovery wont work. I see alot of people talking about doing this through a terminal but I could not find a comprehensive guide for this like the xda root guide. Thanks.
Darren
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Install android sdk:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Copy the downloaded radio.img to e.g. partition C: on your computer (if you downloaded a zip, extract the radio.img from there). Check the md5sum!!!
Boot your into fastboot mode (start it with pressed back and power button) and connect your phone to your computer.
Now open command prompt on your computer and type
Code:
fastboot devices
It should list your device now. If it does, type
Code:
fastboot flash radio C:\radio.img
(in case your radio.img was copied to C: ).
Now, observe the computer and be patient TOUCH NOTHING!!
The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
Watch the little indicator at the top of your phone screen.
Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
Then, and only then, reboot your phone.
Click to expand...
Click to collapse
A nice guide about adb/fastboot can you find here:
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
Flashing radio is a risky thing. Because if there something is wrong, your phone won't be more than a paperweight.