Develop Bugs

Slow Android 2.1

I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Are there any ways that I can actually speed this thing up?
Ive used ATK and thats about it. Im out of ideas here.
Also: 1) Is there anyway to fix the backlight issue when coming out of sleep mode? (It stays at minimum brightness)
2) Is there anyway to transfer winmo contacts to XD?

howeasy said:
I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Click to expand...
Click to collapse
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.

You could try overclocking but it should be pretty speedy already. Is this your first build of Android? Have you deleted data.img and let it remake it. Try formatting your sd card.

ben_duder said:
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.
Click to expand...
Click to collapse
That is indeed the build i'm currently using.
The official XDAndroid build of 2.1 would give me the endless fireworks screen even and updated zImage.
If there's a version that will work on my Fuze then please link me to it as I have been unable to track it down.
But regardless, I've been working on trying to get it to run faster, Ive had moderate luck using ATK but thats about it.
Im baffled as to why its running this slow.
Also, using the 2.0.1 build caused the phone not to send SMS messages, hence the reason I came looking for a new build and came across the Sense one.

Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Here's proof (if you want it) that it's normal for it to take ages to load on first boot.

ben_duder said:
Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Click to expand...
Click to collapse
Indeed I did. It simply played the Nexus one boot animation for a while, froze for around 5 seconds, and then went back and played the nexus one animation from the beginning.
The sense build im using works in all aspects other than the fact I would prefer the normal Android layout, I want it to run smoothly, and I want a more constantly updated version.
I used the Fuze startup text with and without the overclocking script thrown in.
I'd be more than willing to go at it again if its worth the shot.

I really recommend having another go: XDAndroid is exactly what you're looking for with regards to the lack of Sense and the frequent updates. There's no hardware-related reason why it shouldn't work on your Fuze, so delete everything from the build that's already on there, get the right startup.txt and give it a go

Thanks for the positive reinforcement!
If you could possibly directly link me to the 2.1 build you'd personally recommend that would be appreciated.
Ive been trying a build for the RAPH800 that was linked to in your sig and its giving me to the same problem I described earlier.
I have the RAPH110, as you know, but the RAPH800 build was the closest thing I could track down.

Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.

ben_duder said:
Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.
Click to expand...
Click to collapse
Oopsy! I had a hard time tracking that down.
Im using the one labeled "03.05.10 | 2.1 builds". Is that correct?
It also says it already has the lastest zImage that should work so do I need to go update that?
I swear, if there was a super mega +rep button i'd press it.
You're what support forums are all about <3
(3:42PM: Just calibrated touch screen)

Yep, that's the one I'm trying. I've had some experience with the 2.0.1 but I've never actually used this build before, so it's possible there's something missing that I don't know about.
Haha thanks, although there are much nicer and more knowledgeable people on here than me

Well you're the one putting forth the effort to help a guy in need, so I truly do appreciate it.
I'm still getting the constant Nexus one boot animation sadly enough.
Maybe I'll go test out the 2.0.1 build and see if I can get that one to work, but like I said earlier, I had SMS issues with that one.
EDIT: I was able to get the 2.0.1 build working with SMS after zImage and etc..
Going to test sound and whatnot now and come back with another edit to verify.
I would still like the 2.1 build though but this might have to suffice.

Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation

ben_duder said:
Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation
Click to expand...
Click to collapse
AWESOME!
Mind uploading whatever it is you did and tell me what I have to do to get the same result?
Sorry, Im still pretty new to this whole thing.

I won't upload it, but just check your startup.txt and there should be two lines of text that look like they should be separated. Press return just before the second, save it and delete your data.img file. Then run HaRET again and it should work fine.

You have to try this build - it's brilliant.

Well I suppose I'll have to give that a shot.
I found and edited the lines and also threw in the overclocking script.
After deleting the data.img Im giving it one last shot now.
If that doesnt seem to work then I'll just deal with the 2.0.1 build until I find a way to get this to work.
EDIT: anddddd, no such luck.
Guess I'm left to stick with 2.0.1 for now, it was running pretty fast as well.
So if anyone reading this gets 2.1 working please feel free to post.
Is there a way to get Android on the phone itself rather than SD? I'd love to ditch Winmo and save some battery life here.

Shame... I can't understand how it's not working now. All I did was edit the startup.txt, delete my data.img and try again, then wait for ages while everything loaded. If you're not sure if you've edited your startup right you can try using the one that works for you with 2.0.1.
As for not having to use the SD, that would require NAND flashing, which has some way to go before we can use it on our Touch Pros to replace Windows Mobile. There's a thread about it here. There are dual-booting and light WM ROMs designed for XDAndroid users, however.

In case you don't believe me
Sent from my AOSP on XDANDROID MSM using the XDA mobile application powered by Tapatalk

Did you happen to update the zImage or anything or did you just copy and paste and throw in the startup?

Desire build for Kaiser (SENSE)

Here is a desire build I have been tinkering around with for a long while. There are several several issues still in need of work so I am going to leave it to the community to help me out.
I failed to mention this is a full NAND install
I will get some screen shots up as soon as I can get time.
Much faster and much more responsive in my opinion than the legend / hero / mytouch builds
Here it is in a nutshell
- I am not a hardcore developer I have just been using existing files and putting something together that works most optimal. This build has a lot of polymod, and mssmison mixed.
- Hardware keyboard does not work correctly while using Rosie, disable Touch Input to correct this issue. Also speeds up system somewhat.
- clock.sh is in /system/bin use at your own risk It is only there for those that wish to use it is not enabled at boot. Modify sysinit.rc for this
- Disable vibrate on ring and quiet when phone is moved helps with incoming calls
- This build will leave approximately 37mb of free space for data, I do store apps on SD but it is a little unorthodox maybe someone can do better than me. I create an app folder on sdcard and symlink to it. I do not recommend this but I will be upgrading soon and could careless about damaging my cards they are old.
- Livewallpapers are questionable I don't use them or like them If they dont work and you want them then you are welcome to work on their developement.
- Bluetooth not working Help Please
- Wifi not working Help Please
- Widgets may need influenced to work just go to applications / manage applications / Find HTC Sense and Force stop and Clear Data if widgets do not load on boot.
- First boot takes an extreme amount of time.
- CompCache is disabled use it if you will I find that it causes stability issues try to keep the mem size down to 28 or less if you use it.
- Media folder is not built into this system it is included in the download just add it to your sdcard should look like this /sdcard/media
ONCE AGAIN I AM NOT A DEVELOPER I WILL WORK ON WHAT IS OUTSTANDING AS I GET TIME. I MAY OR MAY NOT MAINTAIN THIS BUILD IF YOU HAVE A FIX FOR ISSUES PLEASE PM ME I WILL UPDATE FIRST POST TO REFLECT THE FIX AND BY WHO.
DOWNLOAD
USE ONE OF THE 320x480 NBH FILES FOR YOUR KAISER

Why you name it Desire build.. android on desire looks differently

Michga said:
Why you name it Desire build.. android on desire looks differently
Click to expand...
Click to collapse
This is an old build, mssmison put it out as a sdcard install on the vogue a long time ago before the legend builds were put out. I kept hold of it and tweaked it to work on my kaisers nand. That is why it looks much different than the most recent builds

Post it in the vogue forum. They get more attention so easier chance of a wifi/bluetooth update.

kallt_kaffe can probably help you with the wifi.

Dukenukemx said:
kallt_kaffe can probably help you with the wifi.
Click to expand...
Click to collapse
Try this (NOT TESTED!). I actually think just putting the correct wlan.ko in /system/lib/modules might be all it takes but I included the usual stuff just in case.

does anyone have a mirror for this build. I would like to try it out

Does anyone have market problem. I can't even enter the market, it just kick me out

crackeyes said:
does anyone have a mirror for this build. I would like to try it out
Click to expand...
Click to collapse
It should download for you I just checked it to make sure it was still validwhat issue are you having

Combining FRX03 with Neopeek FRG83.R5 with working Bluetooth ?

Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
-------------------------------------
----------------
EDIT:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !

d0nate110 said:
Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
Click to expand...
Click to collapse
1) as far as I understand Neopeek uses large parts of Xdandroid projects, starting from the kernels/rootfs. This is not hidden/secret, so he and xda devs may know each other pretty well.
Therefore I can't understand how he can have bluetooth working and Xdandroid not.
then ...
2) maybe he shares branches of code and patches with our devs, but while our devs decided that the code to make bluetooth working is still too buggy, he could have decided to shoot it in for good. In fact reading comments on the thread you posted you will see that at the end the people crying for not-working BT are a lot ...

I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.

I just installed it, on a blank 2Gb I had spare.
At start it's quite a pain in the arse ...
cmdline was a little different, I just set correct keyboard.
But I immediately put the latest kernel (24.11.2010). Both in installer and main.
Much faster than Xdandroid. Much faster at boot, much snappier in launcher etc., but this may be related also to the age (of the FAT32 file system) of the other SD I use for Xdandroid. Will format it and see what happens swapping.
But then, when it went to sleep it just crashed.
I tampered with the startup, added pmsleepmode=2, this worked, tried =1 and works quite well.
As I expected, BT doesn't work on my RHOD100.
This neopeek build comes nearly all from xdandroid, so it seems it's not as up to date.
But while that guy takes most of development from XDA, he must work a lot on tweaks, therefore XDA should take something back ...
I'll try cleaning the other SD and check what happens.

Installed on extra card. Rhodium 400 . It is fast. Boots quicker. The initial setup screens are very friendly. Power off and other buttons work more like winmo. Bluetooth will not turn on. Phone works. Data does not work. Have to use WiFi for data. USB while in Android does work (sweet). Key board backlighting not working. I am going to reinstall with bluetooth enabled initially in winmo.

Neopeek SuperFroyo Repack into system.ext2
arrrghhh said:
I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.
Click to expand...
Click to collapse
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !

reinstalled Bluetooth not working. Rhodium 400
Only things that could make improvements to XDA android are Speaker phone is working. USB in android does work. Buttons function as they should. It works with SIM card installed. Speed. Boots faster. Screen adjusts to right profile on start lockscreen.USB headset works without line in startup.
Still not working
Data does work but have to manually set APN. Headset does not work ( Does work with line in Startup and calling during boot). Problems with the market downloading.
Does work tethering. pretty much everything
One nice thing is they have a seperate install folder so if your system is corrupted you just reinstall with file manager in winmo. It reformats the ext2 partition on the card. I assume the sizing of partition is in place of the sizing the data.img file on the card.
Being open source borrowing a few items should not be considered crossing a line.

d0nate110 said:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !
Click to expand...
Click to collapse
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..

First Full Day Of Testing
[ACL] said:
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..
Click to expand...
Click to collapse
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.

d0nate110 said:
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.
Click to expand...
Click to collapse
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him

too buggy things would work then stop working. I could plug in a usb headset have it work in a call or music unplug it then plug it back in and it does not work. Many other things like that. Same with the 3.5 jack trick it would work sometimes then sometimes not. If u left it stock it works great and is very fast. Diamond users were happy. I have a diamond that I will try it on sometime next week, but it is not good for rhodium. It did something to the usb on my Rhodium in winmo would not work so gave me a chance to jack in energy rom like that so far.

[ACL] said:
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him
Click to expand...
Click to collapse
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?

Sorry about that
sad0felix said:
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
First of all I AM NOT Donate - I'm donatello written with numbers
I don't want any donations and hate money
Second I apologize, but I can't implement FRG83.R5 to use without formating my SD-card thats why I use a SuperFroyo. The member DmK75 gave me this link to system.ext2 file with SuperFroyo release in it...
I try though to repack FRG83.R5 also in system.ext2 file later... I just don't have the know-how yet...

sad0felix said:
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.

[ACL] said:
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.
Click to expand...
Click to collapse
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!

Here's the PPCG thread on NAND boot testing. Not for the faint of heart...

sad0felix said:
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!
Click to expand...
Click to collapse
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.

[ACL] said:
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Click to expand...
Click to collapse
Hep, I am just a curious guy.
One of those many that want to put their nose everywhere, but also one of the few that:
a) most of the times will need to read the guide just once (if guide isn't enough there are FAQs and Google),
b) will follow instructions easily because normally understands what they mean/what they are for
c) will never give it up until success
d) will never come to the forum writing: "I have a phonez, tried to put some android on it, doesn't work HELP1!!1!!1!"
Moreover, my TP2 is just 6 months old, is a gift, I use it for work, so to not void the warranty I didn't even install HardSPL on it.
So do not worry.
I am just curious to read how you can do it.
But will not die if I don't know yet
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.
Click to expand...
Click to collapse
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?

sad0felix said:
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?
Click to expand...
Click to collapse
Not to my knowledge. I guess we should *try* it just to see if there's a big difference... perhaps Neopeek can help us here muhahahahaha!
But I think the theory was the tradeoff would be small - a lot more work for very little reward. However, I would be interested to see if there is a difference, and if it is big or not. At the very least just to know if it's our build or just the ext2 partition that's making it feel snappier.
In addition, AFAIK swap partitions on SD cards should be avoided, unless they have a write-levelling scheme (I believe they only put these in SSD's... I don't think any SD card has this tech because it's typically unnecessary) - I've heard swap partitions can just destroy a normal SD card because of writing and re-writing to the same area of the card many, many times... I mean physically on the card, not just logically in the folder hierarchy.

Just installed it on my diamond Bluetooth does work but it doesnt pair. The screen eventually graduates to the center dividing it in opposite. I thought maybe because I was running the hot version. Repartitioned reinstalled the normal clock version runs for a time then the same. Its no better than XDA

[BUILD] **Complete FroYo Bundle** FRX07.1 - Maintenance Release

FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>​
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.

stinebd's Changelog:​
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse

Layman's Changelog​
(As in, the changelog I wrote )​
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually. See Detule's post on this topic.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup

Caveats:​
BT - works now! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
NOTE: BT must be disabled in WinMo before booting Android or else you'll run into all sorts of odd issues...
WEP on wifi doesn't work. I heard an app called 'wifi-ace' (on the Market) fixes WEP!
If auto-brightness is enabled, the keyboard/button lights will fail at random. See this post for more scant details .

Yay! No more "when is FRX07 coming out?" posts!

highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
And to that effect, I would like to personally apologize to everyone for how long it took. Life has been crazy busy the past couple months. Hopefully we'll get GRX01 out in a more timely manner.

Woooohooooo!!! Thanks to all of the dev's on this, Stine, Hyc, Emwe, Arrrghhh (for putting up with all the BS!), and anyone else involved.

Can't wait to try this out. Thanks to all who contributed =)
highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
Just to get a sense of things, is it too soon for a "when is FRX08 coming out" post?

Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk

bluenote73 said:
Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Ah yea... I need to test this on a RAPH800 I just got my hands on, thanks for reminding me!

Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?

wmg316 said:
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?
Click to expand...
Click to collapse
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...

arrrghhh said:
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...
Click to expand...
Click to collapse
Thank you sir!

Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.

webxplore said:
Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.
Click to expand...
Click to collapse
Figured out...Had a corrupt zimage file. Able to launch now.

After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy

First Impressions
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
EDIT: Figured I'd list what is and isn't working for me. Again, I'm using all the default components like kernel and whatnot on the Tilt2 and have the phone overclocked to 710.400MHz now:
WiFi - Works
Data - Works (most stable I've experienced)
Bluetooth - Works (haven't tried headset)
WiFi HotSpot - Buggy; Turns on, but disabling keeps the notification icon and enabling again causes reboot. Different kernel doesn't fix.
USB Tethering - Works/Turns On (Don't have the driver to test quite yet )
Camera/Camcorder - Works (Camcorder doesn't record sound.. known issue?)
Phone - Works flawlessly
MMS - Incoming/Outgoing Works

maff1989 said:
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
Click to expand...
Click to collapse
+1
Come from FroyoB Hercules v2.
Any possible to run FRX07 on CWM?

FRX07 on cwm is being worked on by Eodun,wich sadly yesterday released FRX06 for cwm

rtrip said:
After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy
Click to expand...
Click to collapse
I would bet that the new audio routing stuff fixes the static problems. It definitely cleaned things up for me. But at this point I think we need a newer kernel in addition to the new audio libraries, the stuff in that audio routing thread is rather out of date at the moment.
I've been running most of this stuff for more than a month without issues. It's definitely going to be a lot more solid than any previous builds...

[ROM][NAND] [No longer being developed] GBX0* + 3.4.41 kernel - update 04/25/13

First I would like to give credit to everyone who has worked on GBX0* in any way. ACL, arrrghhh, detule, and Stinger22 to name a few important faces around here. I do not take credit for 99% of this. It is a modded version of the GBX already published on XDA.
Stinger22 is responsible for building the killer new kernel. I packaged the kernel into a boot.img and collected all the compatible updates into a single installable Zip with lots of tweaks.Stinger22 deserves big thanks for his work here.
There will be limited support for this build. Feel free to ask questions, and even better if you can help answer them. If you know how to fix something that is broken I would love to hear from you. I would be happy to include anything that you can contribute.
Due to the number of people unhappy with the RHOD100s phones and this rom, we do not recommend it for the RHOD100s (not that we ever did as we only have RHOD400s to test with).
New install guide.
Now what you came for:
GBX*
Includes:
GBX 5-8-12 lib update.
Slightly smoother boot animation used.
Build.prop tweaks.
Added a couple of ringtone/media sounds.
Superuser replaced with SuperSU .97
Modded audio.conf file to allow for the streaming of media metadata from apps like Pandora when the advanced menu / car bluetooth mode is enabled in the app. Also this change should allow for more Bluetooth devices to connect to the phone. Does only appear to support AVRCP 1.0, so no metadata without extra app support. However track forward/back/pause will work with some setups.
Added circle battery icons with %s for more precise gauging. Shows in 5% blocks. What you see is +/-3% of what the battery is really reporting. Based off the themes here. It is better than a half filled bar IMHO. It might take a full discharge or two before the battery gague/acl code becomes accurate. The battery also tends to drop quickly in the first 10% and then levels off.
RHOD300 keyboard fix. Credit to Detule
Changed RHOD100 from default keyboard to RHOD100_UK keyboard map.
Fix to ramdisk to resolve error reported during boot.
Fix to bluetooth main.conf to prevent bluetooth media devices from crashing OS. *only included in the 3.4.26.1 and newer full build*
-Still have issues where connecting/disconnecting the sink device can sometimes cause the phone to reboot. Seems sink device dependent. Mostly fixed in 3.4.26.13
Fixed bluetooth typo bug to 3.4.26.1 in 3.4.26.11
Boot animation in 3.4.26.13 credit.
3.4.17 Kernel update:
Including ACL's newer battery code.
More accurate readings from battery gague.
Maybe slightly better sleep battery usage.
Small Bluetooth fix (I find paring to be easier).
Kernel panic fix that may help prevent phone lockup if apps crash.
Many other small patches.
Fixed USB detection issue in 3.4 kernels.
Overclocking still supported. (SetCPU is free to XDA members)
Added a hack supplied by detule to prevent the sd card reader from suspending to prevent unexpected sd card removal errors.
Added a kernel splash screen to cover up some of the rolling text during boot time. Credit.
Sleep works with wifi turned on. - Battery life should improve where wifi prevented sleep before. Wifi tethering will prevent wifi sleep.
Zoom slider bar now works. Acts like a two finger touch moving from the center of the screen. If you tap on the zoom bar it will be just like tapping in the middle of your screen. Something to keep in mind if you get unexpected touches while holding the bottom of your phone. More benefit than a draw back IMHO. Added permission files. Link at bottom for those who just need this (based off of mankineko's work).
3.4.24 Kernel *minor update*
Includes updates from source.
Added code to cause system to reboot rather than hang from a system crash.
3.4.26 Kernel
Reboot function in shutdown menu has been fixed (power off is still broken)
Host file is no longer over written on boot up. This had been preventing ad blocker apps from working correctly.
ACL's panel code has been used. Hopefully this will resolve some issues for the RHOD100 users. We have no way to test, so it is as-is.
Auto brightness has been fixed. You may need to press the power button and force the lcd off, after it has been enabled, before it will take effect.
Device name is no longer reported as 00000000 by ADB. It should show as the serial number.
3.4.35 Kernel
Slight performance tweaks.
Added CrossBreeder mod. Basically helps tethering internet.
Added "Smartassv2" cpu governor. Can be set using apps like SetCPU. Should be slightly better performance, but may come at the cost of battery life.
Added "row" scheduler.
3.4.41 Experimental Rhod400 Kernel.
Shutdown working
Fps limit fixed, plus a slight gpu performance boost (previously was benching about 19fps for both 2d/3d, now I'm getting up to 60fps 2d, 26fps 3d)
Enabled more compiler optimizations. Kernel is slightly larger, but seems to perform a bit better
USB: No need to plug/unplug once before adb works, faster cable connection detection
Other miscellaneous tweaks that may or may not help battery life
Known bugs:
Many of these bugs are found in the 3.X kernels, and so they may be found here too.
MMS does not work out of the box. Add this APN info if you want it.
Google maps newer than 5.9 shows graphic distortions with street names, and other graphic issues sometimes. Waze is a good gps alternative if you want something with more features.
Shutdown and reboot options on the power button menu do not work.
Auto backlight does not work.
8-15-12 RIL update breaks radio (on CDMA for sure/no reports from GSM owners).
SD card unexpected removal errors when the phone wakes from sleep on *some* phones. -try a non SDHC sd card if all other standard troubleshooting fails. I have been able to use a 512mb and 1gb card micro sd card without issue. However all my 4,8,16, and 32gb micro SDHC cards have this issue. Hacked work around as of update 3.4.17.
May have to remove and reinsert USB cable a few times before the phone will recognize it has been plugged into a data port. Also you may need to turn features on/off to get the correct tethering/usb storage/usb debug to work correctly.
No front facing camera support for RHOD100.
Deleting bluetooth.apk may be necessary to get the phone to connect to some Bluetooth devices that have any advanced features.
If Bluetooth is left on and the phone is rebooted/crashes, the unit may bootloop. I have not found a fix other than reloading the Rom from recovery.
This bug seems to effect A2DP and other audio streaming devices the most v.s a bluetooth mono ear piece for calling with. This is a bug I have been able to repro on the GBX*+ 3.3.6 kernel as well. Make backups before using Bluetooth. If you are a CDMA user, you could try the original Ril from inside the GBX+3.x rom. It seemed to cause the reboot loop a little less. However GSM users must have the 5-8 Ril to use this Rom.
Found that this bug seems to be for devices that support multiple profiles. I have a Bluetooth receiver that will use phone and media profiles. If the phone profile is disabled the lock-ups do not happen. This work around will not let you use the phone features, but you can stream media. You need to pair the device. Then long touch it to get a to an options menu. Uncheck the phone profile option to stop the crashes when playing any media.
Sometimes if the phone locks up during the boot animation from this issue, then you reboot once or twice, and leave it alone for a long long time it will sometimes finally finish booting. It is worth a couple of reboots, and a lot of waiting vs reloading the rom. It also seems to help if you plug the phone into the usb on a computer after the boot process has passed the blue screen.
Pandora's internal/advanced bluetooth settings must be turned off, otherwise it may crash the phone on device disconnect.
Bluetooth is not 100% stable, and may crash the phone on connecting or disconnecting devices. During use it is stable.
If the phone crashes while bluetooth is turned on it may boot loop. If this happens connect the phone's usb port to a charger or usb port on a computer. This should cause it to boot correctly on the next time around.
Sprint phones must be activated on the Sprint network in WM before loading Android. Android can not activate everything correctly.
It has been reported that the keymap for the RHOD300 is not correct.
Not an Android bug, but Sprint DNS services are crap. I found good working links not working correctly due to bad dns info. Of course you can use any public dns server you like.
A suggestion for getting your own dns in more easily is this App.
If you tether on Sprint I suggest that you put your own DNS server in under the TCP/IP settings on client device as it will only use sprint's by default. I leaned this the hard way.
RHOD100 WIFI may not reconnect to access point automatically upon waking from sleep. Disable and reconnect to work around.
This Rom was only tested on the Sprint TP2 RHOD400. It will probably work on any that worked with the GBX0* + 3.3.x kernel, but we can't promise it.
Updated RIL from Skysoft here. Not included in any build. 4-16-2013
Full Downloads:
GBX0*+3.4.17 Full.
GBX0*+3.4.24 Full
GBX0*+3.4.26 Full
GBX0*+3.4.26.13 Full *feedback on if Bluetooth is still crashing the phone after a clean rom load would be interesting.*
GBX0*+3.4.35 Full
Kernels:
3.4.26 Kernel update.
3.4.24 Kernel update.
3.4.17 kernel update.
3.4.35 kernel update.
3.4.41 Experimental Rhod400 Kernel.
If you download please hit thanks at the bottom and/or post feedback. I'm curious as to how many people are downloading.
New install guide.
Old install directions for all other NAND roms.
It is assumed that you have unlocked your phone. If not read here and/or here, and/or here.
If you are running the 8-15 ril that was patched, and you are unable to get a cell signal, I would highly suggest that you install the older patch ril file.
If you want to add just the permission files for the zoom bar (and a few other things) rather than downloading the whole thing again here they are. When I did this it broke Zeam. I had to add another launcher, and then switch between the two. That fixed it for me.
As always BACKUP, BACKUP, BACKUP before doing anything. Please use at your own risk.
*Related goodies*
Gapps package.
For those of you who want an ICS facelift, check out the modded Zeam launcher.
Most recent recovery thread. - this recovery creates a md5 error on a backup's restore. Anyone know how to fix it?
ACL's known good recovery.
Good chance you will need to calibrate your touch screen. This thread covers that,and how to make it stick.
I may have found a launcher that is more lightweight than Zeam from what I can tell. I am running Lighting Launcher, and am quite happy. Seems to have an even smaller memory footprint, which is great for phones without much memory.
Swapper2 app. This is an interesting thing I found the other day. It allows you to use your SD card for swap (Virtual ram). I did verify that a 64mb swap file (did not test swap partition) can work on our phones. I would love to hear some feedback from people who might be interested in playing with it. I would suggest a Micro sd card with a high random read/write speed. Here is a guide that is already made if you want to use a swap partition rather than a swap file. It will probably wear out your sd card faster, but sd cards are cheap these days. Also note that SD storage vie USB may not work if you use this mod.
Update.
I got out my 32gb high random speed sd card today, and I whipped up a swap partition according to the guide above. I bumped the swappyness setting to 100. I was in a generous mood, so I lopped off 1gb of space for swap (256mg would have probably been a better choice). I did get a name error when I enabled it, but it seemed to work just fine. The swap space of 1gb showed up by the free command, and the swap space showed use after I ran a few apps. It is a subjective observation, but I think multitasking is a little smoother. I plan on leaving it setup like this for now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did manage to max out the cpu, and crash the system resulting in a reboot. I was running two gps apps, and two music apps, and two or three other apps all at the same time (abit poorly though). It might not have liked having multiple apps access the same resources.
Here is a handy app for rebooting the phone quickly, and entering into recovery.
Possible way to disable the proxmity sensor for people who have bad ones causing a non-waking screen here. Credit.
*Bonus for Sprint RHOD400 TP2 users*
If you are tired of the white HTC splash screen here are two nbh files you can flash just like a rom from the SD card. They should only touch the splash screen. Everything else is left alone. Flash one, or both in any order. These probably work on other Rhod phones, but I have no way to test them. So no screaming if something gets bricked. Based off the work in this thread. Reported not working on RHOD100 by this post. Reported working on RHOD300 here.
If you know of an image (480x800 res) that is even more amazing than these, and you feel it would be a good replacement drop me a link to it. If I love it, it will make it to the first post. Otherwise I might just whip one up special for you for contributing.
Primary
Secondary
As of 3-25-13 I have moved onto the EG4G/SII phone after reading about it and SERO legacy at Howardforums.
I will stop in from time to time, and if I am given a newer kernel I will post it. However I will no longer be using this phone.
So long, and thanks for all the fish.

i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw

Slipdoozy said:
i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw
Click to expand...
Click to collapse
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.

wizardknight said:
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.
Click to expand...
Click to collapse
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:

Slipdoozy said:
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:
Click to expand...
Click to collapse
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.

wizardknight said:
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.
Click to expand...
Click to collapse
im not happy with google selling my info so i refuse to give them any space on my phone lol
i tried the modded zeam all the ways i could think of, before flash, after flash, through adb didnt matter. maybe corrupt apk?
no worries. ill try to redownload it and try it your way with launcher2 first
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.

Slipdoozy said:
i tried the modded zeam all the ways i could maybe corrupt apk. before flash, after flash, through adb didnt matter.
no worries.
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.
Click to expand...
Click to collapse
Be ok with loosing the money. Some people have reported that they didn't get the unlock info, and the dev for that is next to impossible to get to respond.
You might check this thread. Not sure if they got it working.
Most of the credit goes to Stinger22. The man is kicking some serious code butt!
I would try re-downloading the apk. I was able to install it with a adb install. Not sure what else it could be. Did you hold your tongue just right while dancing madly during the install?

Slipdoozy said:
im not happy with google selling my info so i refuse to give them any space on my phone lol.
Click to expand...
Click to collapse
You do realize where Android is coming from... Right? lol
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it... Glad it did not get forgotten!

Zoombar!!
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh

Caldair said:
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh
Click to expand...
Click to collapse
HAHA. I didn't think the zoom bar would be the selling feature of this rom, but I am glad you are happy.

arrrghhh said:
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it.
Click to expand...
Click to collapse
Didn't know who did the base work. - Gave credit in the post.

Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.

CodaHighland said:
Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.
Click to expand...
Click to collapse
Wow. I had no idea that the zoom bar was so popular. Just doing what we can to keep the phone going.

Thank you so much for your hard work (especially fixing zoom bar!!!.)

I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks

karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
Yes, overclocking is supported. This should be the same as 3.3.6. I believe the frequency range you can choose from is 122-825. Download your favorite overclocking app from the market, and have at it. I use quick cpu overclock lite.
*edit. I think we have some new governor options. Link for descriptions.

karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.

Slipdoozy said:
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.
Click to expand...
Click to collapse
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.

wizardknight said:
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.
Click to expand...
Click to collapse
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.

Slipdoozy said:
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.
Click to expand...
Click to collapse
I am assuming that you mean OMGB by ACL's rom. To the best of my knowledge there is no way to port the feature without building your own kernel. It is my understanding that the 3.x kernels (what we use) are not compatible with that rom. OMGB userland is no longer receiving updates, so unless another dev adopts that rom it will never work.
I will take the 1% credit for this rom. I have done behind the scenes, packaging, some Bluetooth mods, and testing stuff. The other 99% goes to everyone (esp Stinger22) who has worked on it before me or with me.
On the phone that the zoom bar is not working, did you download that rom zip before or after 11-3? I didn't change the file names or links with the last update. You might try downloading the perms file at the end of the post, and installing that. Otherwise I would re-download, wipe, and reinstall.
If you are still having trouble let me know, and I will go check the zips to make sure that something didn't get busted in the last round of updates.