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

[Reefermattness]

Originally Posted by defiantone

I'm enjoying the overclocked foyer 2.2. I only wish that google maps would show the map. GPS comes on but the map is blank.

Youre using satellite view, and the reason it has a blank image is because you are out off the coast of africa somewhere!! Switch back to regular view, or zoom out about 15-20 times and you will see whats going on. If you get a lock in WinMo first, or make it so your screen doesnt shut off for 10 minutes or so you will eventually get a fix for your real location, and not for the party us XDA users are having with google buzz out in the ocean.

[2phonejones]

whooooooooooooo this is awesome now i know why there so much talk about android. super fast and i still have win mo on the side! annnd i have more bars when in a basement then i did on windows mobile wow! but i still havent got my data working on sprint but wifi works! and the marketplace on android blows windows out of the water! litterally.

[kern417]

Thought I'd add in my 2 cents

Finally tried it out and its working great. text a few people, downloaded email and twitter all worked fine. battery meter was visibly jumpy but i wasnt worried about it dying since i had just charged it before, but it was definitely bouncing up and down. the battery ran very warm, i tried disabling a lot of the apps i had because i didnt realize almost everything is set to auto refresh every few minutes so hopefully the next time i try it out it will be cooler, but i had to switch back to WinMo for a while so my hand could cool down/:

basically this works fine for me, the only other thing i would like to see is a working camera application, i mostly use my phone for sms, internet, and twitter, so bluetooth and things of the sort dont affect me. Also an accurate battery meter would be nice but i'm pretty used to my phone that i can guess when its going to die before hand. Sometimes i couldnt get the on screen keyboard to pop up and i really tried not to open the hard keyboard as much since the G-Sensor seemed buggy

Main reason i switched was due to the realization that i could run Android 2.1 with Sense, i always saw people running 1.6 and really am not attracted to that build. this sense build is beautiful though, may try out 2.2 next.

Overall i give it a 7.5-8.0 rating. if battery and camera were working i would give it a solid 9, the bugginess i can deal with. But that's just me.

Again thanks for all your work to the developers. Trying out things like this makes me really appreciate my phone and the online communities

[Reefermattness]

Originally Posted by kern417

Main reason i switched was due to the realization that i could run Android 2.1 with Sense, i always saw people running 1.6 and really am not attracted to that build. this sense build is beautiful though, may try out 2.2 next.

Overall i give it a 7.5-8.0 rating. if battery and camera were working i would give it a solid 9, the bugginess i can deal with. But that's just me.

Again thanks for all your work to the developers. Trying out things like this makes me really appreciate my phone and the online communities

Wait until you try 2.2, you wont care about sense anymore. LOL

Sense is my least favorite, and the most buggy of all the builds. I personally give it around a 4-5 rating, and consider it more of a novelty build, than a day to day user. I guess Ive been using sense back when it was called Manilla3d, so its nothing new to me, but it almost takes away from Android, and REALLY slows it down. Almost makes you feel back like you are running laggy WM again. Just an example, Sense build when in normal use has about 40mb free ram. Use ATK to "Kill all tasks" in the Sense build and you are lucky if you have around 60mb free ram. Do the same with 2.1 or 2.2 w/o SenseUI, youre at about 70-80mb free ram during use and after ATK you have close to 100-110mb free.

[YnYng]

is anybody else getting massive battery drain from reefermatts froyo cab version? I removed the overclock and put the sleep mode to 1 instead of 2, an put the line about the proximity sensor (Enable Proximity Sensor - board-htcrhodium-proximity.on=1 Enable Wake on Proximity Sensor - board-htcrhodium-proximity.wake=1) could these be the issue? I am barely getting 6 hours with minimal usage.

[jpriset]

Originally Posted by demonlordoftheround

Wirelessly posted (Mozilla/5.0 (Linux; U; Android 2.1-update1; en-us; AOSP on XDANDROID MSM Build/ECLAIR) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17)

I couldn't get it to boot. Maybe 767MHz is too much for my Rhodium.

Same here. I lowered it to 650000 and it booted no problem.

[Ragster]

787000 is as high as I always go, its 767 MHz

[aldamon]

Originally Posted by YnYng

is anybody else getting massive battery drain from reefermatts froyo cab version?

Yes, but it runs so well I just plug it in.

[urbanmartyr]

Weird scenario-

This is my first time trying android on my sprint CDMA TP2. I just installed the latest build [Froyo]. Currently I'm in Singapore for the summer and I am using a GSM SIM card on a local singapore carrier (SingTel).

I can boot into android but can't get any connectivity from the phone network or from Wifi (even though I have WAP at home). I tried the force cdma option and without it.

Does anyone have advice as to how to get this cab to work correctly if you're on a CDMA TP2, but using a GSM SIM card?

I checked the threads a couple of times, but am unclear as to what to do. Thanks

[one80oneday]

Originally Posted by jpriset

Same here. I lowered it to 650000 and it booted no problem.

Originally Posted by demonlordoftheround

I couldn't get it to boot. Maybe 767MHz is too much for my Rhodium.

Originally Posted by Ragster

787000 is as high as I always go, its 767 MHz

I've been able to boot at 824 MHz with no problems