yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] drewstiff:
If that was your true intention then I am willing to take back my comments as I said I would do. I believed it was obvious from the conversation that this only happened at 90%+ and so your comment sounded very facetious to me at the time. I thought you were trying to say something along the lines of "well that's stupid because you can still overcharge it at 89%!", and so I just thought "chill the hell out - it's not my doing, I was only trying to help". Text isn't the best way to get across the intended intonation I guess.

It's no excuse but I was just finishing work after a $h1t day and I think I must have been more than a little riled! And reading back now, it does seem a little harsh regardless of how your comment sounded to me at that moment...

Can we agree to move on, and I'll stop being a d*ck and everyone can talk about the kernel? :o
[Nexus One Android Development] intersectRaven:
Btw, are those of you having incompatibilities with the camera using the Desire camera mod?
[Nexus One Android Development] Docmjldds:
Yes. Mine installed via Kitchen Baked build
[Nexus One Android Development] Docmjldds:
Posting a new reply intentionally. Phone threw multiple FC's. Android Process I believe . Also it phantom dialed a contact (my wife's phone as I was watching the FC's popping up) Going back to last .33 version CFS 925 again.

Edit:2.6.33.3_AVS-925mV_CFS_20100508_2206.zip reflashed and everything back to normal.
[Nexus One Android Development] hah2110:
Back on 4/29_1009 800 and getting the best battery life. I've beat the crap out of my phone today and from 8am-5pm, still got 72% left. That is bad@$$. I may try the 925 version of 4/29 since that day somehow hits the sweet spot for me.
[Nexus One Android Development] x986123:
Still getting random reboots with the newest kernel RC7. No idea whats up.
[Nexus One Android Development] Imperial.mack:
Did u wipe both caches in recovery after you flashed? That mayb the prob...
[Nexus One Android Development] x986123:
Yes, I did wipe both.

*Update: Flashed newest one, with the audio fix, and wiped cache and Dalvik-Cache again, this time no reboot, have been using 10 minutes so far.
[Nexus One Android Development] mtw4991:
LMAO...hilarious Dictionary, too f*#king funny!!! Maybe we should all just chill out and ignore haha's posts until he decides to grow up and quit spamming the threads. Kinda like "ignore it and maybe it'll go away", lol. Plus, you're gonna give yourself high blood pressure;)
[Nexus One Android Development] x986123:
This is really, a test kernel. You have to expect problems. Get retail kernels if you want minimum issues.

By the the way, IntersectRaven, thanks for the latest one with the audio fix! No skipping!
[Nexus One Android Development] schahr01:
I realized this myself as well. The Apr-29 800mv (.33.3, pre loop unrolling, old toolchain) is fine for me and I get great battery life and comparable linpack scores (6.8 on average). I am going to stick with this for now and continue to watch this thread. have tested the .34 rc6 and most of the 925mv CFS ones (tried 1 BFS - a no-go) released in early May but honestly I don't think the new bells and whistles warrants it yet. This is by no means an attempt to undermine the great work Raven is doing.

I want to start using the this phone for what it is, a great smart phone :)
[Nexus One Android Development] timothydonohue:
i can confirm that the rc7 released last night has music skipping. i'll have to wait to try the new one, but not sure i want to, if there is an issue with unmounting usb

switching back to 4-29, 925
[Nexus One Android Development] solidmac:
Had some time today being a bit frustrated with my shaky E or 3G(H) connection on campus, i decided to up my voltage by switching from the 800mV Kernel to the 900mV Kernel. All i have to say is that I am VERY shocked at the difference it makes on the signal strength, it went from -71dBm to -53dBm. Tomorrow i go back to campus and i will give you my thoughts on how my connection has improved or not.
[Nexus One Android Development] intersectRaven:
I can't pinpoint the USB remounting problem yet. I believe it will be resolved as I apply driver fixes from the .33 branch to the .34 branch. Just be patient for awhile. :)
[Nexus One Android Development] SimFox3:
I'm also one of the few people that gets more battery life with a 800 kernel as compared to a 925, no matter if it's .33 or .34. Also, I don't see any drop in signal strength.
[Nexus One Android Development] seanowns:
Music is fixed on updated .34 kernel. I did see problem before too.
[Nexus One Android Development] Ownatik:
I can't tell exactly when it started but it's pretty close to the .34 kernels. I'm having a hard time waking up from sleep. the whole phone is frozen for a good 10-20 seconds and wifi drops, then reconnect, then the phone is usable again. ANyone else experiencing this?
[Nexus One Android Development] x986123:
Yea, When i press the power button, lights turn on, but screen is black. All I have to do is just press it again.
[Nexus One Android Development] Ownatik:
After testing, every time the screen sleeps for a couple minutes my wifi is down when I open it back. Apart to that everything's been running perfect as usual. Good work intersectRaven.

EDIT: By the way, my sleep policy is set to "Never".
[Nexus One Android Development] dictionary:
Agreed. 2.6.33_AVS-925mV_20100429_1010.zip and 2.6.33_AVS-925mV_CFS_20100504_1327.zip yield the absolute best results for me. I'll keep bouncing around between the latest and one of those two to keep testing. rc7 has been solid for me so far though. Video plays, as does music. No issues. Signal strength is great. Only problem I'm having (which isn't a huge deal), is that the wifi doesn't automatically reconnect when I come back home. rc7 seemed to also cure my usb mount/unmount issues as well. I'm using 2.6.34-rc7_AVS-925mV_CFS_20100510_2223.zip with 5.0.7 Nightly Build as of 5-10. It's newer than the Test build that is out. I wonder if this is the reason for my added stability?

I take that last bit back, lol. Just had another unmount issue, which can only be sorted by a reboot. Hmm. Looks like I'll just be using USB from recovery for the time being.
[Nexus One Android Development] christiankk:
Seconded. The kernels past 0429 have had worse performance for me.
[Nexus One Android Development] seanowns:
Confirm some sleep/wake issues.

My screen would turn on, but i could not unlock it. It did allow me to properly reboot.
[Nexus One Android Development] bskim23:
I'm also getting some excessive battery drain with the 925. I lost 6% in 45 min while I was taking a nap. Don't have any service bouncing issues in my room either
[Nexus One Android Development] phunghoang24:
my phone use 70% battery 20h do nothing. [.33.3 & ,34-rc7] intersectRaven newest!
[Nexus One Android Development] phreaker18:
Ok Dude i have to agree with u here on battery life ... this kernel has hit the sweet spot for me too ... so i would believe and hope that u wont be testing any more kernels in the near future ...

well hope is eternal !! :D
[Nexus One Android Development] bunjeeeee:
I lost 60% in 4hs with the last build of 34-rc7@925mV!

Now back on .33.3 4/29 @925mV, i get the best results with it.

Just a question, after reflashing is it necessary to wipe cache?
[Nexus One Android Development] drewstiff:
Hmmm... I don't seem to be getting particularly great battery life on the 925mV compared to the 800mV I was using previously... but the signal strength seems to be noticably better.

I guess this means I have a decision to make...:confused:
[Nexus One Android Development] phunghoang24:
my battery is bad , 70% in 5h (now 27%) not fullday. newest kernel
[Nexus One Android Development] timothydonohue:
maybe you are wearing it down by checking it all the time, lol. turn off all the background stuff. i know that with background data on, my phone burns through battery lickity split, but it can go well over a day if i have that turned off
[Nexus One Android Development] hah2110:
Haha - Only other thing I tried was the 925 version of 4/29. I'm going back to 800 now. This 925 did yield better results than any other 925, but not as good as the 800 on standby. It may have been the same for loss during usage though.

+1 on 4/29. It is weird because after that, raven said he made a tweak to improve battery life which most agreed helped [or so I thought].

+1 on the 800 being better. Have you tried changing to the GSM PRL deal talked about in the other thread?

I'm also going to try my Seidio extended battery now that I know the 800 4/29 kernel works great as the Seidio 1600 was yielding worse results than stock.
[Nexus One Android Development] Ownatik:
Seidio 1600 will yield worse results than stock battery no matter what.
[Nexus One Android Development] bunjeeeee:
Is it necessary wipe data cache after flashing kernel?
[Nexus One Android Development] bewA:
I would do the cache's and battery stats.

I dont know if its required but for me its good practice and just a few extra clicks :)
[Nexus One Android Development] schahr01:
I may be going a little overboard but I usually wait for 100% batt then install a new kernel, reboot into recovery and clear dalvik, cache, batt stats and start testing.
[Nexus One Android Development] phunghoang24:
there is proplem about push mail.

my Email incoming delay 5 minutes .

( Email local company)
[Nexus One Android Development] bt1980:
0429 kernels

I see many people have posted that 0429 kernels are yielding the best battery life; but I would also like to mention that 0429 happens to be the most stable for me.

I know that BFS and HelixLauncher were supposed to have issues and that using a WLAN with a hidden SSID was supposed to cause reboots; but for kernels after 0429, I am pretty sure that even with CFS and WLAN with broadcasting SSID I experienced very occasional FCs, random reboots while connected to or toggling WLAN, and gradual performance degradations over time until rebooting. This happened with or without HelixLauncher (using CM-5.0.6).

Should also mention I'm using Paul's Desire Camera, in case that makes a difference, stability wise.

While I currently cannot definitively say whether 800 or 925 gave me better results, I do get better reception with 925 (both 3G and with WiFi I can see more networks from the same place with 925). I have designated 0429-925mV-CFS as my preferred stable kernel to fall back to.

What I have noticed with the kernels newer than 0429 is that they boot up faster, and initially (for the first few hours) are a lot snappier and responsive.

Lastly, just want to say that these are observations and by no means complaints. Everybody here really appreciates all the hard work you put into the kernel and for the most part we are here to try out the very bleeding edge of kernel development.

Cheers! Thanks again IntersectRaven :)
[Nexus One Android Development] Docmjldds:
Agreed on Seidio.

Just tried 2.6.34-rc7_AVS-925mV_CFS_20100511_1504.zip, dated today in Mediafire folder but not mentioned yet in change log. USB mount still broken as well as Desire Video camera. Yes, I pushed ko followed by wipe both cache files then flashed zimage and tried booting up twice to verify. Will run basic testing now.

Edit: Battery has dropped 6 points in last 15 min. with phone on standby. These RC7's really like to eat up battery. I can confirm initially extremely short boot times. (30 seconds from boot animation to desktop). Very snappy scrolling.

I agree. Been returning to this same one after testing latest RC7's. Will wait for fixes regarding excessive battery drain, as well as working with Desire Video Camera.
[Nexus One Android Development] dirk411:
Can you believe it?

2.6.33.3_AVS-925mV_CFS_20100805_2206.zip

I've found the one for me. Thanks, intersectR :D

33hrs. / 45% remaining...
[Nexus One Android Development] Bay Harbor Butcher:
But you are under 2G signal..it eats less battery than 3G/hsdpa,Anyway..very good results..
[Nexus One Android Development] dirk411:
How much more of a difference would it be? 10-15%? Would that not still be very good results? :o

Shame on T-Mobile for not having 3G in Mississippi, USA
[Nexus One Android Development] schahr01:
Or it could be an AT&T SIM in the original T-Mobile 3g band unlocked phone - Like me.

OT - Debating on whether or not I will get the AT&T version. Anyone know if the bluish/purple tint issue is gone? I get a sneaking suspicion that Google may stop selling the phones directly soon given the relatively epic fail.
[Nexus One Android Development] hah2110:
What is the logic behind Seidio being worse? The mAh is higher? Wouldn't it be better if conditioned right?

You ARE getting SUPERB battery life but it is a little better because of 2G. What is your usage like? I was at 19% after 36 hours with what I consider moderate usage.
[Nexus One Android Development] Docmjldds:
<<What is the logic behind Seidio being worse? The mAh is higher? Wouldn't it be better if conditioned right?

In theory, yes. I have owned this since they first announced it for sale. I have tried every method known regarding battery conditioning. It simply does NOT yield same as stock battery. Seidio offered me RMA exchange a while back. I never sent it in, since many users reported same issues. I basically just use it as backup when on trips. Stock battery runs cooler also. Guess you can infer increased temp=poorer battery times as a reason.
[Nexus One Android Development] Chahk:
Actually, I read an article that said 3G was using less power than EDGE when under load. Stand by power is still lower with 2G though.
[Nexus One Android Development] hah2110:
Correct. I read this too. Guess it depends on usage?
[Nexus One Android Development] schahr01:
The article in question is a sticky in the General section, "[Guide] Everything you wanted to know about Li-Ion batteries but were afraid to ask!"

The theory here I guess is that 3g is faster than EDGE, which leads to completing the required network task faster. The radio goes to sleep after completion sooner. The same argument was used to recommend wifi over 3g.
[Nexus One Android Development] L10nH34Rt:
Latest kernel is giving me screen issues. When it wakes touch doesn't work and I can't make it sleep, the button only dims the screen. Reverting to older kernel to see if that fixes it.
[Nexus One Android Development] hah2110:
Hmmm... Weird. On the Seidio now. It seems to be running good. How much does a 20 minute conversation straight drain everyone's battery? This is weird. In my Battery Graph, I see:

11:18am - 89%

11:23am - 88%

11:28am - 88%

11:33am - 59% (I threw in the Seidio here which obviously wasn't charged and plugged it in)

12:33pm - 73%

12:38pm - 100% (how did it charge up so fast?)

I is confused!
[Nexus One Android Development] b1337:
save it for YOUR battery thread bro, what does this have to do with ravens kernel?
[Nexus One Android Development] sir*mez:
You is always confused!!
[Nexus One Android Development] Johnex:
Im having screen issues too with the latest .34 :)
[Nexus One Android Development] hah2110:
The 20 minute convo definitely involves his kernel.
[Nexus One Android Development] sir*mez:
Not when you involved a different battery that's not stock!! Obviously its foreign to the phone therefore not kernel related!
[Nexus One Android Development] b1337:
yep specially when u started your own thread about that pile of a battery..
[Nexus One Android Development] cchhk:
After mounting the SD card through USB, cannot turn off the storage mode even unplug the USB. (on 20100510_2222_.34-rc7)
[Nexus One Android Development] L10nH34Rt:
Had to pull battery thrice today to be able to make a call. Reverting back to previous rc kernel (the one without the driver updates) fixed it for me :)

Raven plz investigate :D
[Nexus One Android Development] izmar:
Moving back to 800mv 0429... Latest gave me sub par results.

edit -

did a test and im getting 1 more bar with 925mv. We'll see how the battery holds up compared to the 800mv.

How have your experiences been between the two? Noticeable difference in battery life?
[Nexus One Android Development] 2000impreza:
I've been switching between the two for the last few days and haven't noticed any real difference in battery life between 800 and 925. I'll probably stick to the 925 versions from now on.
[Nexus One Android Development] x986123:
Latest 1504 kernel restarts by itself randomly. The only one working for me right now is 2223.
[Nexus One Android Development] snavid972:
im using 800 429 kernal, my phone starts to heat up at 89f is this normal i mean i do check my phone like almost every 5 to 10 min lol i love it cant help it......one other things what do you recommend setcpu profiles at to save battery life????
[Nexus One Android Development] Docmjldds:
USB mounting is known issue. Another common issue appears to be users with Desire camera having video issues related to Desire and RC7. Most users are reverting back to .33 versions. (Whichever they felt worked best for them. Most seem to like 4/29 posted 925 versions. Consensus seems to be 925 versions yield improved phone reception (more bars or more H vs Edge) I would wait for more news from Raven. I personally get great results with last posted 925mv CFS dated 5/08 as shown in my sig.

Anyone here feel free to jump in if my consensus seems at odds
[Nexus One Android Development] Nighthound:
Just to address this question which was lost amongst the bit of flaming that followed, this is actually implemented in Google's code some time during the upgrade from 2.6.29 to 2.6.32 (as far as I can recall, can't remember exactly when). There was a hardware battery charging circuitry that was not enabled in the initial release of the Nexus One, but was subsequently enabled in the update. What the circuitry did was to switch off charging at the hardware level when the battery is near max capacity so that the battery does not overcharge. The charging circuit is enabled again when the battery charge drops below 90%. So it is not purely a Cyanogen mod, but should be on all N1s now.

The problem that the people using CM test mods at that time was that after reverting from the test 2.6.32 kernels to the 2.6.29 kernels, the old kernel was not aware of the need to switch on the charging circuit, and so people could not recharge their batteries again! :)

Edit: oops I meant 2.6.29 and 2.6.32... fingers were dyslexic =p

Read this thread: http://xdaforums.com/showthread.php?t=649770

A quick summary is that the OEM battery from HTC has better performance even though it has a lower rating that the Seidio battery. Remember, the ratings are put there by the battery manufacturers, not independently certified by a third-party.
[Nexus One Android Development] hah2110:
Oh, I've read that. However, I have run a logcat on my device at 100% and it rated 1576mAh which is why I'm so confused.
[Nexus One Android Development] sir*mez:
Congratulations you managed to get confused again!! :eek:
[Nexus One Android Development] schahr01:
Great info - Thanks.
[Nexus One Android Development] dictionary:
Re: [.33.3 & .34-rc7]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/10/2010 10:39pm

Good info. I thought it was CyanogenMod. Cool stuff
[Nexus One Android Development] dnsmo:
i am having freezing and/or reboot problem with the latest .34r7 firmware, also sometime enabling the wifi will freeze or force reboot the phone. hope this issue will be addressed soon. thanks for the good work!!! love this mod
[Nexus One Android Development] x986123:
Do you have Desire ROM? Because I have it, and I get freezing/rebooting, and I haven't noticed anyone else getting this. The 2223 925v is the only RC7 working great for me. Try it?
[Nexus One Android Development] dnsmo:
i am using CM 5.0.6 and IRs kernel
[Nexus One Android Development] Nighthound:
Typo in my earlier post, should've been 2.6.29 and 2.6.32, but I guess you guys get the drift. :)

Actually there's a bunch of gremlins that secretly goes into his house every night and swaps his phone for a different N1.
[Nexus One Android Development] x986123:
Actually, every time he gets good battery life, I jack his phone and swap mine.
[Nexus One Android Development] phunghoang24:
I can't push mail with newest version . i think because wifi and 3G/H ...

i test wireless there is a proplem . i comand : ping xx.xx.xx.xx -t , if screen on -> ok ,screen off : request time out : 80% .
[Nexus One Android Development] Docmjldds:
+1. I will add that I too was flamed over questioning this problem. In my case, my N1 had decided that it would NOT turn on charging when for example, I would be at 92%, and plug it in before going to sleep. If I would leave it alone till next day, at times it would have dropped to the 70's and STILL not be charging. The later Kernels here seemed to have stopped this behavior for me, so charging would commence correctly when below 90% as it should. Again, sorry for adding to thread drift, but felt it was needed to be said here, and it is of some concern regarding charging and battery times etc.
[Nexus One Android Development] Nighthound:
I hacked together a quick boot animation for an Android BSOD... something just for laughs :)

http://xdaforums.com/showthread.php?p=6420446
[Nexus One Android Development] L10nH34Rt:
Happened with previous .34 kernel. Reverting back to latest .33 kernel to see if that fixes it, or my phone has a hardware problem... :(
[Nexus One Android Development] Docmjldds:
Hilarious. Will install your script later on.

Edit: Script works perfectly. Black Splash on white screen full screen really nice.
[Nexus One Android Development] ratson:
with all the kernels i recently used i had a strange issue: it looked i have 3G/H connection but actually no data could be transfered. i first thought this issue is network related, but now i see that this is somehow related to my N1. i have tryed cm 5.0.6, cm 5.0.7-T1, a few kernels (.3 .4 OC/nonOC 800, 925mV) and i got it on every build. do you face same thing? it recovers itself, sometimes a restart also helps but not always.

i see nothing in logcat which would be related to this...
[Nexus One Android Development] mtw4991:
Went back to 0429_1009 800mV kernel...might try the 925mV version later just to compare:) Seems the most stable, pretty quick and battery life is very good at 15 hrs 55% left with 7 hours overnight sleep and moderate use. That's an average of 3% per hour with 1-1.3% sleep drain.

btw, in my build.prop I have ro.ril.hsxpa=1, not 2 as was standard in CM 5.0.6-N1. Anyone else do the same? Sorry for the drift.
[Nexus One Android Development] hah2110:
Glad I'm not the only one going back. That one works wonders for me.
[Nexus One Android Development] Chahk:
Any chance of a refresh to get it in line with CM 5.0.7 test2?
[Nexus One Android Development] xghostyxjokerx:
im using cyanogen rom 5.0.6 and i just dl the 900v...whats the difference in 800 to 900???
[Nexus One Android Development] b1337:
get in line with what exactly? works just fine with test2
[Nexus One Android Development] Chahk:
Just because it flashed without any problems doesn't mean it actually works as intended. There could have been kernel changes in test2 that you overwrote when you flashed a different kernel that wasn't re-baselined against Cyanogen's latest commits.
[Nexus One Android Development] intersectRaven:
Finally solved that damned touchscreen bug! Will not post yet since I haven't brought my GitHub up-to-date yet on my testing branch. Stay tuned though as I slowly merge the driver updates found on .33 to .34! :D

*Btw, still haven't got a clue as for the USB remount bug. If anyone has any ideas, please message me. :)
[Nexus One Android Development] jblazea50:
Raven, not sure if you are aware of this, but kernel .33.4 is now stable according to this http://www.kernel.org/
[Nexus One Android Development] b1337:
it works as intended if youre that worried stick to cyanogens kernel with test2 or compile your own
[Nexus One Android Development] Chahk:
Nice retort. Btw, here, you've lost some things: .,'.

Seriously though, have there been any changes in test2 that would require another update, or is the latest version (20100510_2222_.34-rc7) up to date with Cyanogen's commits?