Re: [TESTING] New Kernel (Battery Status testing!!)
 

ok got it working but unfortunately I get reboots pretty quickly after startup using 9/29 blazn but I'll try the reference build and see if that helps

Re: [TESTING] New Kernel (Battery Status testing!!)
 

if its not working for you, can you get some logs ? dmesg should suffice.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

If it's not even letting you do anything, you'll have to add the dmesg command to your froyo.user.conf so it runs on boot.

Try reference, perhaps with a new data.img. Shouldn't be required, but stranger things have happened.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

This new kernel has definitely improved the battery status tremendously as it matches the windows status within 1-2%. Still have the call issue where I can dial and connect but can not hear anything but this time when I toggle the +/- on volume, it tends to reboot android...........you guys are getting there and I appreciate your hard work but without stable calling, it's tough to use full time...keep it up!!!

Re: [TESTING] New Kernel (Battery Status testing!!)
 

Test 5 is out guys. Looks like it's just testing for shutdown tho... camro also mentioned on IRC to test in call sound. I don't think it was ever an issue for me, seems like it's GSM guys only. So let us know on that. I'll update the first post with the new kernel.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

one issue i am having is, when i try to wake up the phone by pressing end key, it always doesnt wake up. sometimes i have to push it few times for the system to wake up. maybe user error? i dont know

Re: [TESTING] New Kernel (Battery Status testing!!)
 

i have found the top power botton wakes the phone much faster than the right end key....i have almost stopped using the right end key and have been using the top key instead....try it out

Re: [TESTING] New Kernel (Battery Status testing!!)
 

USB plug n play .. is .. gettin' there!

Re: [TESTING] New Kernel (Battery Status testing!!)
 

First Thanks for the hard work Guys. One thing I noticed is when I try to connect to laptop,phone tries to connect as usb mass storage and I can't see any data on sdcard after wards using OI file Manager.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

I have a problem. When i connect to the usb with my phone the battery percentage decreases instead of increases. so before i plug it in in would be at 40 percent but while it is plugged in it decreases to like 20 percent. is anyone else having this problem i am on rhod 400

Re: [TESTING] New Kernel (Battery Status testing!!)
 

Batt code has been committed. I had to modify slightly to reduce the warnings but it shouldn't cause any issues. Glemsom autobuild should pick it up shortly for everyone to fully enjoy.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

congratulations acl thx for all the hard work you devs are the best

Re: [TESTING] New Kernel (Battery Status testing!!)
 

NP. if you see camro or viruscrazy on xda, make sure you thank them for that mathematical mumbo jumbo they got working.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

I was having the exact same problem. Even though batt meter showed charging, the % dropped ... if I was doing nothing with the phone. When I began entering apps, settings, etc. I noticed the meter did a 180 and started to increase. 8-[

Re: [TESTING] New Kernel (Battery Status testing!!)
 

alright so i should just start opening apps and setting and it might start working for me

Re: [TESTING] New Kernel (Battery Status testing!!)
 

if you really wanna see the batt code.

Commit in linux-msm in Linux on Qualcomm's MSM - Gitorious

Re: [TESTING] New Kernel (Battery Status testing!!)
 

so just curious ACL is the battery percentage really close now the it is been commited and what else works now? if you can tell me thx

Re: [TESTING] New Kernel (Battery Status testing!!)
 

Can't guarantee but yeah, that's what worked for me. Sometimes I notice the meter gets stuck at a certain %, 72% and 93% so far.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

alright thx linguini i hit the thx button

Re: [TESTING] New Kernel (Battery Status testing!!)
 

ahh .. well im not the author of the code. I just cleaned it up a bit to commit it. The percent is not 100% accurate and probably wont be for a while. Reason for that is that we are just doing some math based on the values we get back from memory. We dont know if that math is 100% correct so there may be some errors. Some devices have it easier than others. Rhod happens to be one of those weird ones so others (topaz/blac/diam/raph) may report better numbers.

This code is just battery. no usb, no leds. That still yet to be cleaned up/approved.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

alright thx for the info

Re: [TESTING] New Kernel (Battery Status testing!!)
 

Thanks for this kernel.

I have installed Test5 and I noticed a couple of things. The plug-n-play detection of the phone on USB is almost perfect, aside from the fact that I don't have any drivers for CDC Abstract Control Model (ACM) and CDC ACM Data.

Also my WIFI turns on, but when it starts scanning for a network it turns off. Do you know what may be going on?

Thanks,
-.Drynaps

Re: [TESTING] New Kernel (Battery Status testing!!)
 

That is because your phone is probably auto-mounting your SD card. I use Dual Mount SD, that way the card is accessible both within android and from the computer at the same time.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

Thanks. I will try that.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

Those are just for ADB. The Android SDK has the drivers and tools if you want to set that up.

Re: [TESTING] New Kernel (Battery Status testing!!)
 

I do have the android sdk, but it does not seem to be able to find any drivers for those two items. Can you point me to the right folder?

Thanks!

Re: [TESTING] New Kernel (Battery Status testing!!)
 

If you use the SDK manager, it is an option you have to check to download. It will be located under android-sdk-windows\usb_driver

Another option is to grab Droid Explorer which I believe will take care of it for you. Droid Explorer

Re: [TESTING] New Kernel (Battery Status testing!!)
 

I must have misunderstood you originally.

I have all that, and it works fine for ADB connectivity. Droid Explorer works fine, but I still have those two items hanging without any connectivity. Are those items the ones that are used for USB Tethering? Based on the research I have done, it seems like they may be the drivers that make it act as a modem in order to be able to send to it AT commands.

Re: [TESTING] CONCLUDED! (For the time being...)
 

First of all, thank you so much for your great job. The battery meter is improved substantially and I truly appreciate your efforts to help us out.

I have been experiencing a problem with this new kernel though. I can not get my data (3G or 2G) connection work. If I use the old kernel, it is working fine but not with this new one. My device is Touch Pro Rach800 with Sprint. Any help will be greatly appreciated.

Re: [TESTING] CONCLUDED! (For the time being...)
 

A) This is the TP2 section.

B) You shouldn't be running this code anymore... notice that it says testing has concluded? Please use a kernel from the autobuild service.

Re: [TESTING] CONCLUDED! (For the time being...)
 

Except for the data connection issue, everything else worked perfect on Touch pro as well. Great job. Thanks anyway... I tried. :)

Re: [TESTING] CONCLUDED! (For the time being...)
 

I guess I'm missing something... the code's been committed to git, so just grab the newest...

Re: [TESTING] CONCLUDED! (For the time being...)
 

Has the USB code been committed as well? That worked awesome with this kernel, but not with the autobuild ones.

Thanks!

Re: [TESTING] CONCLUDED! (For the time being...)
 

Nope. It's much easier to commit little pieces at a time - as I'm sure you've seen, there's usually some regression with this device or that device because we try & support all MSM devices.

So they commit this piece & that piece. Once camro fixes the most recent things broken, which seem like it's happening soon... Then we can move onto further testing USB. It didn't work flawlessly for me, and they want it to at least test well for most before they commit it to git.