[CAB] GSM&CDMA Project Android Port and Startup Utility [01/23] FRX04 Reference!

[bteljuice]

So i searched and searched, and all I could find is this which is a theme of swype on the current keyboard [THEME]Android Swype Skin - HTC_IME like || WVGA & HVGA - xda-developers

All others searches led to NO swype for rhodium. So can anyone guide me to the proper place.

[smoke_007]

Hi all,

First, thank you tons to all the developers for all the work you do! Love Android!

Question and my info:
I'm currently running [MJG]Rhod.2.2Froyo.092610 reference build. I deleted my data.img and started over fresh.

When the phone first boots up it's lighting fast. My problem happens after the phone has been sleeping in my pocket for a while. I'll wake up the phone and it will be extremely slow. So much so that it's practically unusable. If I restart the phone, boot to Windows Mobile, restart Android, it's fast again until it's slept for a while. Then it's slow again.

Killing everything with a task manager program does not speed it up. That's why I even tried deleting my data.img file and starting over. I don't get lock ups, so I don't think it's from over clocking, but maybe. The 9-16-10 reference build did this for me also and it wasn't overclocked by default.

Any thoughts or things to try any one?

I might try and switch back to Blazn build now that it's updated. Blazn build killed my phone battery quickly even in just sleep/stand by, so I thought I'd try Reference build and see if battery lasted longer...

Thanks,
Smoke_007

[123sit]

Originally Posted by bteljuice

So i searched and searched, and all I could find is this which is a theme of swype on the current keyboard [THEME]Android Swype Skin - HTC_IME like || WVGA & HVGA - xda-developers

All others searches led to NO swype for rhodium. So can anyone guide me to the proper place.

Check your PM

[twobeaglesjtj]

Originally Posted by smoke_007

Hi all,

First, thank you tons to all the developers for all the work you do! Love Android!

Question and my info:
I'm currently running [MJG]Rhod.2.2Froyo.092610 reference build. I deleted my data.img and started over fresh.

When the phone first boots up it's lighting fast. My problem happens after the phone has been sleeping in my pocket for a while. I'll wake up the phone and it will be extremely slow. So much so that it's practically unusable. If I restart the phone, boot to Windows Mobile, restart Android, it's fast again until it's slept for a while. Then it's slow again.

Killing everything with a task manager program does not speed it up. That's why I even tried deleting my data.img file and starting over. I don't get lock ups, so I don't think it's from over clocking, but maybe. The 9-16-10 reference build did this for me also and it wasn't overclocked by default.

Any thoughts or things to try any one?

I might try and switch back to Blazn build now that it's updated. Blazn build killed my phone battery quickly even in just sleep/stand by, so I thought I'd try Reference build and see if battery lasted longer...

Thanks,
Smoke_007

I have the same issue on the 9/26 Blazn, I thought it was just me.........Any suggestions guys??? Thanks

[ThrottleAbuse]

Originally Posted by ThrottleAbuse

To upgrade from the Aug 30 build to the latest one can you simply replace the zimage and rootfs.img file in the andboot folder? It looks like you need to change the startup.txt file to allow the 3D hardware also. Is this the best way to upgrade the latest build or should I be doing something else. Just trying to upgrade without losing anything in the current build. Thanks.

I did give this a try. Not sure if that is the best or proper way to update the kernel. Phone seems to be running fine and I can run neocore at 18.1 fps. When I look in settings and phone info it says I am on kernal build # 20100813.141358 Does this make any sense? The one I downloaded and renamed was 20100926_001914 I saw there is an update utility in the project android program on WinMo. Does this update you to the latest build or is it better to install the cab? Thanks.

[arrrghhh]

Originally Posted by ThrottleAbuse

I did give this a try. Not sure if that is the best or proper way to update the kernel. Phone seems to be running fine and I can run neocore at 18.1 fps. When I look in settings and phone info it says I am on kernal build # 20100813.141358 Does this make any sense? The one I downloaded and renamed was 20100926_001914 I saw there is an update utility in the project android program on WinMo. Does this update you to the latest build or is it better to install the cab? Thanks.

To update the kernel you just download the new package, extract the zImage and modules to where you run Android, and make sure the zImage is named "zImage" - unless you adjust your startup.txt. The modules file need not be renamed.

The update utility you speak of is nice, but to my knowledge it does not work correctly & corrupts the startup.txt if you use it... So until the dev updates it, don't use it. Same goes for the cab, as I believe the cab creates a shortcut to this utility.

[ThrottleAbuse]

Originally Posted by arrrghhh

To update the kernel you just download the new package, extract the zImage and modules to where you run Android, and make sure the zImage is named "zImage" - unless you adjust your startup.txt. The modules file need not be renamed.

The update utility you speak of is nice, but to my knowledge it does not work correctly & corrupts the startup.txt if you use it... So until the dev updates it, don't use it. Same goes for the cab, as I believe the cab creates a shortcut to this utility.

Ok. Does this do the same thing as installing the latest Blazin Build? Sorry I am pretty new to the Android side of things.

[demonlordoftheround]

Originally Posted by ThrottleAbuse

Does this update you to the latest build or is it better to install the cab? Thanks.

Don't use the Update Utility for modules/zimage updates. Doesn't work and will bork your setup.

[sp4rtan5]

Originally Posted by MrPib

Geez, man, you shouldn't have to take this crap. Demand a full refund!

Originally Posted by MrPib

Geez, man, you shouldn't have to take this crap. Demand a full refund!

Can you believe this? Waiting for months and months for this port to get done.and this is what we get?a half working port that's barely runs? What do those dev drink or smoke before they try to port this over?I mean really!geeezzzzzz! I doubt they under stand how we the testers have other more important things to do rather than testing these half botched ports. Someone needs to kick them in their behind and slapp them a few times across their foreheads. If this port ain't done by the end of this week, there I'd going to be hell to pay.WHO'S WITH ME!!¡!!??? Enough is enough! And Im dead serious! Enough already! I swear by god I will go on a hunger strike if we all dont get this done ASAP. done joking. if going on a hunger strike dont get this done then we in ppcgeeks will boycott xda.

[ooxteme]

Originally Posted by sp4rtan5

Can you believe this? Waiting for months and months for this port to get done.and this is what we get?a half working port that's barely runs? What do those dev drink or smoke before they try to port this over?I mean really!geeezzzzzz! I doubt they under stand how we the testers have other more important things to do rather than testing these half botched ports. Someone needs to kick them in their behind and slapp them a few times across their foreheads. If this port ain't done by the end of this week, there I'd going to be hell to pay.WHO'S WITH ME!!¡!!??? Enough is enough! And Im dead serious! Enough already! I swear by god I will go on a hunger strike if we all dont get this done ASAP. done joking. if going on a hunger strike dont get this done then we in ppcgeeks will boycott xda.

I hope this is a joke....