i know in the FAQ's it says that data on cdma is flacky on this build. however i cant even get data to work. i tried changing the line "force_cdma=1" to "force_cdma=0" and nothing happens..i have the lates rooft,image, and modules..what am i doing wrong..gb does seem more snappier,which i like.
im wondering for the people that are using it, about how many hours of battery are you guys getting?
i know in the FAQ's it says that data on cdma is flacky on this build. however i cant even get data to work. i tried changing the line "force_cdma=1" to "force_cdma=0" and nothing happens..i have the lates rooft,image, and modules..what am i doing wrong..gb does seem more snappier,which i like.
im wondering for the people that are using it, about how many hours of battery are you guys getting?
thnx.
My battery life is on-par with FroYo, but I haven't done a detailed side-by-side comparison.
Also, this build is ancient. Perhaps try on the stock rootfs and kernel that comes with this build? At this point, the stuff on the autobuild might not play nicely with this build because it's so much newer... I haven't run this version of GB in ages.
AFAIK it's still on 'fake GSM mode' for CDMA, hence the need for force_cdma=1. I don't know why you would change that to 0, that would indicate you're running in GSM mode...
I doubt you even have an APN menu... Maybe. Damn, just been too long.
Is your provider Sprint? It should "just work" with Sprint, but some providers require more setup to get going.
My battery life is on-par with FroYo, but I haven't done a detailed side-by-side comparison.
Also, this build is ancient. Perhaps try on the stock rootfs and kernel that comes with this build? At this point, the stuff on the autobuild might not play nicely with this build because it's so much newer... I haven't run this version of GB in ages.
AFAIK it's still on 'fake GSM mode' for CDMA, hence the need for force_cdma=1. I don't know why you would change that to 0, that would indicate you're running in GSM mode...
I doubt you even have an APN menu... Maybe. Damn, just been too long.
Is your provider Sprint? It should "just work" with Sprint, but some providers require more setup to get going.
i know its an ancient build,but i just want to try a different build and see if i get more battery out of it.the frx7.1 is awsome but the battery is a killer for me :/(i still use it everyday though ..)
i just change the data number to 0 to see if that would work,which it didnt,since using the "1" didnt work. yeah im using sprint as my provider.
it does have an apn menu on it,takes a bit of time to load,but it is there..
this is a great build, i prefer it to froyo 100%.. but for some reason on my 300/ tilt 2 after about 15 mins it wont wake up anymore. light stays orange and no response from any button. ive formatted my sd card and redone the install 3 times now. i wonder if it could be because im using my ts calibration file from the old froyo install? im lost i dont want to switch back to froyo since this runs so much smoother but im missing everyones call/txt as its frozen in my pocket and its getting irritating lol. awesome build though, i rly hope i can figure it out. suggestions?
this is a great build, i prefer it to froyo 100%.. but for some reason on my 300/ tilt 2 after about 15 mins it wont wake up anymore. light stays orange and no response from any button. ive formatted my sd card and redone the install 3 times now. i wonder if it could be because im using my ts calibration file from the old froyo install? im lost i dont want to switch back to froyo since this runs so much smoother but im missing everyones call/txt as its frozen in my pocket and its getting irritating lol. awesome build though, i rly hope i can figure it out. suggestions?
This build is ancient... really hoping to get something out soon. We're trying to sort out how we want to do the next release...
You on the newest rootfs/kernel? That would be the first place to start. ts-calibration is build-agnostic.
This build also predates hyc's RIL work. There was a TON of improvements in that department, especially related to SoD's.
Also, boot Android with WinMo in airplane mode. Always seems to help things along, but I don't think that'll fix this problem.
The Following User Says Thank You to arrrghhh For This Useful Post: [ Click to Expand ]
wow thank you for the quick response! so i updated the root/kernel about an hour ago and so far no lockup! it was doing it about every 10-15 mins before so i think that may have been the solution. if it fails again ill let u know, or just use froyo until a new GB is released.
thanks again for the help, everyone here is so helpful and knowledgeable it really makes me feel guilty im too broke to donate.. (4 kids, 2 cars lol). anyways keep up the awesome work and ill be holding my breath for a new GB release!
It's under very active development, and my guess is, a release will happen sooner rather than later.
Having said that, you can always build the source that is in the gingerbread branch of the gitorious xdandroid repo -> most updates have been pushed and are available for public consumption, just not yet served on a platter.
The Following 2 Users Say Thank You to detule For This Useful Post: [ Click to Expand ]
It's under very active development, and a release will happen sooner rather than later.
Having said that, you can always build the source that is in the gingerbread branch of the gitorious xdandroid repo -> all updates have been pushed and are available for public consumption, just not yet served on a platter.
New GB build is in testing, but there's a lot of things to test before release. Especially with the new acoustic code.
The Following User Says Thank You to arrrghhh For This Useful Post: [ Click to Expand ]
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?