yashsingh1/xdaforums huggingface dataset:
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
I havent used wifi at all today, unplugged at around 6:30, it's 3:45 now and I'm at 63%, but from around 9:50 to 11:45 and then from 12:20 to 2:20 I had airplane mode enabled since the time without a signal was at 70%, very low signal area. So it seems like for only 4 hours or maybe 5~ of non airplane mode time I should be at above 63%. I only had wifi on for a half an hour today. I'm considering going back to stock for a few days just to see the battery life comparison, and then nandroiding back to CM6.1. I always end up going back to AOSP-based roms in the end. I don't have a data plan on my phone at the moment, getting it today I'm pretty sure, so could all of the blue be from the phone continuously trying to access a website? But other people said they have the same issue and I'm assuming that they have data plans, so that can't be too much related. Hmm.

I also checked cpu usage and such like you suggested, there were a lot of things listed but all but two of them were too small to even have a bar. The two that did have a bar visible were minuscule to put it lightly, so that can't be an issue. Battery use in the about phone area always has cell standby at the top, normally between 40 and 80%. It would seem like there is way too much cell communication going on, moreso than normal. Cell standby stays at the top in even high signal areas, so it's not the signal levels. Kind of stumped here.
[myTouch 3G Slide Q&A, Help & Troubleshooting] KCRic:
Well if the cell is in standby then it's linked to a tower and awaiting activity. Every now and then it 'checks in'. If it's doing that too often then that could seriously drain the battery. You're right though, I'd just switch back. Trouble shooting the exact issue wouldn't be worth the time. Maybe try flashing it again later, could have just been a corrupt download that didn't flash properly.
[myTouch 3G Slide Q&A, Help & Troubleshooting] NJAZ:
After conditioning my battery religiously (full to empty with every charge cycle) I am back up to about 15 to 16 hours from full battery to system shut down which is way better than the 10-12 hours I was getting when I first loaded RC2. CR_OTA ROM gave me up to 24-30 hours off of one charge with the exact CPU/2g/3g/wi-fi "routine" as I am using with RC2. Tracked battery usage with System Panel app and RC2 has a steady and even drain pattern ... an even diagonal line down the graph (100% to 0%). Cell standby uses a ridiculous 40% of the battery from full charge! On the stock ROM System Panel app shows plateaus throughout the day when the phone screen is off/sleeping where battery use is virtually non-existent. I'm going to load RC3 today and track the cell standby and battery usage. This time I am not going to use setCPU and just let the ROM run as the CM team designed it to be used and see if anything has changed. I tried this with RC2 and the battery still trended absolutely evenly from 100% to 0%. I can live with a 16 hour battery cycle for the CM ROM because it is very smooth and never has a glitch. The stock ROM is smooth as well but it has some buggy behaviors that I just cannot stand for and it does not run the latest GAPPS.
[myTouch 3G Slide Q&A, Help & Troubleshooting] Sinsst:
I've noticed i have exacly the same problem(was actually gonna post it when i found this thread)

Needless to say that on eclair my battery lasted ~48 hours constantly, not its drained in max 24...
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
The highest I have EVER gotten was 24 hours, and that was on a cm6.1 nightly build, pre RC2. I loaded cr_mod and experienced a HUGE drain. I had airplane mode on, just to test, and it dropped 7% in an hour, in AIRPLANE mode, with no screen on time. I went into spare parts and looked at the usage, and sure enough, "running" was at the top, with 99% of the time spent without sleeping. This has never happened before though, so I can probably attribute that to my modifications. I deleted a few apk's and de-odexed it before I flashed it, and I have a feeling something I did corrupted something else, so I'll flash plain old cr_mod and see where that leaves me. I should probably get back into the habit of full charge/drain every cycle. I used to do that until my battery started lasting longer than I was awake for, so I always had to plug it in at around 15 to 30%. I'll run some more "trials" and see what's going on.

Also, on an unrelated note, I love the stock rom, I always love the sense UI, but I hate HTC_IME compared to the froyo Latin_IME, is there any way at all I could port the froyo Latin_IME to the eclair stock rom?

Edit: also, I flashed dumfuq's OC kernel over cr_mod, could that have been the culprit to the battery drain?
[myTouch 3G Slide Q&A, Help & Troubleshooting] KCRic:
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.

Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.

NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
Actually, by process of elimination, the kernel was the issue. I remember hearing about there being a bug in the older dumfuq kernels with something idle being null, I really don't remember but it had something to do with sleeping. I flashed pure CR_mod and then 3.5 dumfuq and I experienced the same issue where it wouldn't sleep. I flashed 4.0, but I think it's too soon to determine whether or not the same issue with sleep is occurring.

I tried doing what you said with LatinIME.apk, I even imported the lib file from /system/lib on CM6.1, but the it was nowhere to be found in the system when I booted. It wasn't under keyboard settings, and HTC_IME was gone. I figured it was an incompatibility between froyo and eclair, since the stock sense rom is eclair and the LatinIME.apk is from a froyo ROM. Do I have to something more than just adb push the apk and lib file? I also tried installing it with a file manager, and no surprise, problem parsing the package. It's a system apk so I didnt expect it to be able to install via a file manager. Do I have to use adb install instead of adb push? I'm wondering if htc IME is so wired into the system that it won't work that way. What if I rename LatinIME.apk to htcime.apk or whatever the name of HTCime is and see if that works, because the system may be is treating that as the stock android keyboard, rather than a third party one, because it is labeled touch input in settings, just like LatinIME in aosp roms.

I'll experiment some more I guess

edit: Nevermind, 4.0 is draining as well, albeit less rapidly. Ah well. I guess I'll have to go back to CM6.1 if I want to do overclock. Shame, I love sense so much.

ANOTHER edit: nevermind, you were right, it isn't the kernel at all. It happens when I turn wifi off. I'm assuming that's because I don't have a data plan so it's continually retrying a server that it can't access. I don't know why it didn't do this on the stock HTC kernel, but I'm pretty sure it's the issue. If I turn wifi AND mobile data connection off, it stays at normal drain as well. Well, I'm at 11% and my battery app is estimating roughly 1 hour and 20 minutes remaining, so I don't know if that's GOOD, but I'll give it a good full charge tonight and run it tomorrow. I hopefully will have data activated tomorrow so I can really test it.
[myTouch 3G Slide Q&A, Help & Troubleshooting] Markus214:
Hey guys new to the slide forum but not new to the site. I come from the G1 thread and we had the similar problem. How is your battery life on a 2.1 ROM? I have my phone rooted with a Sense ROM and it has 2.2 and i do see a bad battery drain as well. I remember froyo ROMs battery life may not be the greatest yet. I remember that was always a big problem over there and it looks like it still hurts here. Have you tried setcpu settings?
[myTouch 3G Slide Q&A, Help & Troubleshooting] Sinsst:
Maybe this information will help, i forgot to mention last time i posted that i'm not using a HTC device, i'm using Samsung Galaxy S, and there are more ppl with this problem on our forum aswell, so maybe someone can use this information correctly, i mean, it's either a program that's doing this or some strange freaky froyo process that not everybody has? or idk..
[myTouch 3G Slide Q&A, Help & Troubleshooting] KCRic:
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.

As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.

As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.

I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
[myTouch 3G Slide Q&A, Help & Troubleshooting] KCRic:
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
Yeah that'd be cool. It must have something to do with that, since it's the cell radio sucking battery.
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
I flashed 6.1.0 stable, battery drain seems to be slightly less. I'm still at around 5 or 10% below where I was at this time on stock, with 9.5 hours off the charger, current level 57%. Although, I did use airplane mode for almost 2 hours, so really I'm like 10 or 20% below where I should be. I just can't figure it out, cell standby is at like 80% usage in this ROM. It's ridiculous, is it the polling intervals or something? How can it be so much less battery efficient than stock? :confused:
[myTouch 3G Slide Q&A, Help & Troubleshooting] NJAZ:
I flashed 6.1 RC2 with a low battery and had trouble with battery life. TMO's service was acting very strange for a couple of weeks and my cell standby was consuming a lot of juice. Flashed 6.1 RC3 with a well conditioned full battery. At first I used no setCPU just to see how things would go ... 11 hours from full battery to empty. Added setCPU to RC3 and got 27+ hours out of a full charge. Either TMO fixed it's towers or RC3 was better with cell standby because my network usage was not cranking overtime like it had been. Finally, I flashed 6.1 stable with setCPU and I average around 22 to 24 hours on one charge.

One observsation - when I first flashed RC2 I was really into my phone again. I was constantly tweaking it and flipping through options, testing apps, digging new Gapps, etc. ... bottom line I was just using my device waaaaay more than usual and I think that played a huge role in my (supposed) poor battery performance. All seems to be well with 6.1 stable.
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
I think it did improve after RC2. I still think it's kernel related, however. Just for the hell of it, I tried flashing dumfuq 4.0 over cm6.1, redundant, I figured, but not like I had anything to lose. I was speculating about how maybe there was a modification in the cm kernel that was changed AFTER dumfuq posted his 4.0 kernel. I thought this because flashing 4.0 over stock 2.1 hugely INcreased battery life. And actually, I think I was right. I am getting decent battery life. Not quite as good as stock 2.1, but it's worth it for the theming, 2.3 keyboard, and general customizable nature, as well as speed of course. Display is above cell standby and display was only been on for like 20 minutes out of several hours. It still gulps the battery in low signal areas, which is unfortunate since for 6.5 hours mon-fri I am in school, where there must be lead paint or something because I have horrible signal. So I just turn airplane mode on, like android suggests, fixes that issue. In moderate-high signal areas battery life is great, at least 15 hours. Cyanogen must've modified his kernel and it affected the battery life.

So for anyone having the issue, I suggest flashing dumfuq 4.0 over their ROM, it more or less fixed my issue.
[myTouch 3G Slide Q&A, Help & Troubleshooting] Digitaldreamer7:
3 hours off the charger and my "voice" used 35% of my batt, with a 13m 6s talk time..
[myTouch 3G Slide Q&A, Help & Troubleshooting] KCRic:
Can some one with this issue post a logcat so we can sort this out? If possible, MusicMan, maybe we can get it up in the OP when one gets posted?
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
Yeah, no problem

Unfortunately I am still lacking a usb cable. But what is a logcat going to tell us anyway? It's a long term issue that can't be seen while the phone is charging off of a usb cable. Logcats are incredibly useful for crashes soft reboots and bootloops and all of that, but that's because it's a specific issue, one thing that caused a crash or an event. How are we going to track battery drain using logcat?
[myTouch 3G Slide Q&A, Help & Troubleshooting] KCRic:
I may be thinking of the wrong thing but shouldn't the logcat show us processes and what they're doing? Like when a process calls up the radio and for how long?
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
Yeah it probably would. I found another source of drain after I flashed dumfuq 4.0 over cm6.1, occasionally something will glitch and keep the system wakelocked, and I generally notice it after a few percentage points of battery are lost in 5 minutes, and a reboot fixes it. When I go to partial wake usage it's always either google voice, android system, or music.

The only thing about the logcat is that to collect enough data to actually make a conclusion you would need a LONGGGG logcat.

EDIT: As for the partial wake glitching, it's google voice that's doing it mainly. Music partial wakelock is supposed to do that when it's playing music. The google voice bar was over half of partial wake usage, my phone spent 2.5 hours without sleeping, while the screen was on for 40 minutes. I just force stop google voice when it happens.
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
This google voice wakelock issue is starting to annoy me, anyone else having the issue/have a solution? Thanks!

Sent from my T-Mobile myTouch 3G Slide
[myTouch 3G Slide Q&A, Help & Troubleshooting] KCRic:
No issue with GV but I noticed 'dialer' was running the most and preventing it from sleeping. Do you have GV set to make all calls? Maybe dialer is the issue and if GV is set to make all calls then it's in partial wakelock all the time because it's tied to the dialers' process.
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
No I have it set to make no calls. Dialer isn't even visible on the list I don't think. I just rebooted, so it cleared the wakelock data.

Earlier today I was particularly annoyed because not only did I see that my phone had spent the last 2 hours not sleeping because of google voice, but I rebooted to fix the issue, like it normally does, then the same thing happened except it was UID 10000 with the lock.

That has happened before too. It's always either UID 10000 or google voice. I googled android UID 10000, didn't find anything too specific. Is it calendar storage? I'm wondering if these are still issues from me flashing a kernel over cyanogenmod, which already has an overclock kernel.
[myTouch 3G Slide Q&A, Help & Troubleshooting] KCRic:
You might try not flashing it and see how it goes. Any reason you flashing the kernel?

I'm not a pro at linux so I'm not sure what UID 10000 is, I know UID 0 is root so UID 10000 has to be either user or system and calendar *I think* would fall under user depending on what it's doing. It just depends on who or what 'user' is calling or using the process.

EDIT: Got it!! This should help.

AID_ROOT: 0 [traditional unix root user]

AID_SYSTEM: 1000 [system server]

AID_RADIO: 1001 [telephony subsystem, RIL]

AID_BLUETOOTH: 1002 [bluetooth subsystem]

AID_GRAPHICS: 1003 [graphics devices]

AID_INPUT: 1004 [input devices]

AID_AUDIO: 1005 [audio devices]

AID_CAMERA: 1006 [camera devices]

AID_LOG: 1007 [log devices]

AID_COMPASS: 1008 [compass device]

AID_MOUNT: 1009 [mountd socket]

AID_WIFI: 1010 [wifi subsystem]

AID_ADB: 1011 [android debug bridge (adbd)]

AID_INSTALL: 1012 [group for installing packages]

AID_MEDIA: 1013 [mediaserver process]

AID_DHCP: 1014 [dhcp client]

AID_SHELL: 2000 [adb and debug shell user]

AID_CACHE : 2001 [cache access]

AID_DIAG: 2002 [access to diagnostic resources]

**The 3000 series are intended for use as supplemental group id's only.

**They indicate special Android capabilities that the kernel is aware of.

AID_NET_BT_ADMIN: 3001 [bluetooth: create any socket]

AID_NET_BT: 3002 [bluetooth: create sco, rfcomm or l2cap sockets]

AID_INET: 3003 [can create AF_INET and AF_INET6 sockets]

AID_NET_RAW: 3004 [can create raw INET sockets]

AID_MISC: 9998 [access to misc storage]

AID_NOBODY: 9999

AID_APP: 10000 [first app user]

root - AID_ROOT

system - AID_SYSTEM

radio - AID_RADIO

bluetooth - AID_BLUETOOTH

graphics - AID_GRAPHICS

input - AID_INPUT

audio - AID_AUDIO

camera - AID_CAMERA

log - AID_LOG

compass - AID_COMPASS

mount - AID_MOUNT

wifi - AID_WIFI

dhcp - AID_DHCP

adb - AID_ADB

install - AID_INSTALL

media - AID_MEDIA

shell - AID_SHELL

cache - AID_CACHE

diag - AID_DIAG

net_bt_admin - AID_NET_BT_ADMIN

net_bt - AID_NET_BT

inet - AID_INET

net_raw - AID_NET_RAW

misc - AID_MISC

nobody - AID_NOBODY

There is an app that I saw that was used to see an app and it's UID so you can figure what's running all the time. Activity Express Task Manager, also one I've used for a while is CPU watchdog (I think that's the name) that will alert you if a process goes crazy.
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
I tried flashing the other kernel out of a pure hunch, because it had improved my battery life on stock. I thought that maybe cyanogen had modified his kernel source and dumfuq hadn't synced yet, so I'd give it a whirl. I got better battery life, but not as good as stock. Cell standby usage went down a bit, but not as much as with stock. I did try flashing cyanogenmod 6.1.1, since it was just released, without the dumfuq kernel flashed over it, same drain issue, worse than before, same google voice wakelock issue. Even google voice was worse. Not even restarting it worked, I had to use titanium to freeze it because my phone hadn't been sleeping at all since boot. I ordered a usb cable, should be here soon, then I can help out with ADB stuff, see if we can figure this out. For now, I can't tolerate the battery life, I'm going back to my own little modified spin on cr_mod until I can really try to crack down on the CM drain issue, if it is even possible with my limited knowledge of that kind of dev-level stuff.

Also, on an unrelated topic, the market wouldn't work on cyanogenmod 6.1.1 after I flashed it. When I accepted the terms, it just force closed and wouldn't run after that. I was using a different zip though, not yours. Still, odd that it worked on 6.1.0 and not 6.1.1.
[myTouch 3G Slide Q&A, Help & Troubleshooting] archie53:
Market isn't working for me either on 6.1.1, I know unrelated but letting you know your not the only one.
[myTouch 3G Slide Q&A, Help & Troubleshooting] KCRic:
Sounds good, it'll be great to figure this out. On the unrelated note, I tried the new market, no force closes but I can't get anything to install (not new) but after the DL finished (shows on the notfication bat - market still says 'starting DL') I went to the download folder and there was nothing there, which sucks because I can't manually install it, must be downloading somewhere else - maybe temp. in the cache??..
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
It could be cached. I have a feeling it's downloading to the internal memory, not the sd card. Must be a new thing. Maybe I could try uploading that market 2.2.7 that I mentioned in my other thread and seeing if that works. Either way we are kind of getting off topic haha :rolleyes:
[myTouch 3G Slide Q&A, Help & Troubleshooting] MusicMan374:
The latest version of cyanogenmod fixes battery life, just so you guys know

Sent from my T-Mobile myTouch 3G Slide
[Vibrant General] nlghthawck:
Let's see if I have better luck getting a reply here :-/ I was running into problems with my vibrant I'm using a custom rom Vibrant_AOSPish_JK2_v1.1 I'm loving the rom but for some strange reason! I was able to transfer 900 songs to my phone's internal memory, all of a sudden an error popped out and it wouldn't let me transfer anymore, I thought well maybe there's a 900 limit so I removed them all and tried again and still it wouldn't let me. I then went and formated the vibrant's internal drive and my phone isn't malfunctioning or anything but all my 14 gigs I had are gone! now I only have 2 gigs I don't know what I did...
[Vibrant General] dcontrol:
How'd you format the internal drive?
[Vibrant General] nomadrider123:
sounds like you should flash back to a older rom then try a factory reset
[Vibrant General] nlghthawck:
well...

I went on the start bar clicked on computer and my phone was plugged in into my usb and mounted... I right clicked on the phone internal memory " Not the one that has Avatar " as that's the external SD card, After I right clicked I chose Format.. it formated it and only left me with 2 gigs and my other 14 gigs are missing.
[Vibrant General] nlghthawck:
yay :)

Ok so I RE-Formated Again and now it sees all my gigs!! thanks anyways guys :)
[Vibrant General] Telanis:
Never format from Windows. If you want to wipe the filesystem and start over, learn to use Odin.
[Vibrant General] secularhuman:
Similar problem here, cant transfer files

Suddenly I cant copy files to or from the SDs to my computer without errors during the copy. Ive tried SD_fix.zip but it aborts during installation.

Secular
[Vibrant General] ColorNapkin:
I had this error with my first 2.2 flash but what I did to solve it was format the phone's SD card using the option through the phone itself. It wipes the card but I backed it up before I did that.

My problem was that I couldn't copy files TO the card but I could copy files from the card and I could create files on the card itself using the right click > new context menus. Weird, but formatting it fixed it for me.