[TESTING] XDAndroid GBX0C 2.3.7 Build

[arrrghhh]

Originally Posted by mck2528

Well I added the 3.2.1 kernel that was compiled today. I just left the original zimage that came with the bundle and and left the kernel with its 3.2.1 name and everything boots just fine. I've read the directions from the incremental updates page you linked me to but whenever I delete the old zImage and add the new one that came with the update the boot dies in linux.

Dude. The zImage is the kernel. So swapping the modules does nothing, except break things like wifi.

Either you're replacing the kernel incorrectly, or you're not on the new HaRET/startups. Please ensure you're using everything from the first post.

Again, if you can't replace kernels just stick to the bundled stuff. Perhaps you should get comfy with FRX07.1 before trying a build that's still in testing? Just a thought.

Originally Posted by boneskid1

I tried the new bundle and it is the same as the old one. Not just file names i understood that it is all the same. What file are you pointing me towards? Cause the one on the post is not what you say it is.
Im not trying to be snappy im just a bit confused.
Thanks,
Boneskid1

Like I said, filename doesn't update. Here, I'll take a screenshot to show you what the hell I mean.



That was taken straight off of files.xdandroid.com - do you see what I mean!?! I only kept the same filename because these builds are in testing. Sorry, I'm not going to version these builds if there's just regressions being fixed... Seriously. There's no point in saving 5 different test builds because the first 4 all had something silly missing...

Originally Posted by Sc/ant864

I got Droid Explorer to finally finish installing and while USB debugging is checked in development, phone is charging, installed the USB drivers for SDK, I still cannot connect. Droid Explorer isn't showing the device and the phone does not display the debugging icon in the notification bar. Could it be because I don't have/know which drivers are needed for Windows?

Hrm. I wonder if the problem is GB+.27. There's a bug, specifically with this GB+.27 setup where USB doesn't notify properly. I know this might be a pain for you, but can you try to use adb in FRX07.1, then try this build again? rel_path= and different folders on a big SD will save you some headache here .

I'm honestly not sure what else would be holding it up. I don't get any USB notifications in the bar either, but despite this adb still works great....

So get comfy with adb first, then try it on this build. Sorry for the pain...

Originally Posted by eyeb

I did notice that the phone's battery indicator (i know this isn't accurate or anything) but it seems to be stuck or likes to say it is around 90% even more than it did before. I just don't see the battery level dropping as much as it should. Again I know this is an old issue, and I'm charging phone to repeat it. Just saying it's what I observed, so I'm not sure if something in this update touched on it. If not, then it's no biggie since you already know about it.

If you want logs, how should I do this? I get how to get the logs, but should i just randomly use phone to run down battery?

This isn't a bug at all. No need for logs.