yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] SimFox3:
MTW,

I added your step to the HTC rep's procedure:

Recalibrate the Battery - Nexus One - Power - HTC

1.) Please connect the phone to the charger with the phone powered on, and allow the phone to charge until the notification LED is green, indicating the device is fully charged.

2.) Disconnect the phone from the charger, and power it off.

3.) Reconnect the phone to the charger with the phone powered off, and allow the phone to charge until the notification LED is green.

4.) Disconnect the phone from the charger and power it on.

5.) Once the phone is powered completely on, power it off again and reconnect it to the charger until the notification LED is green.

6.) Disconnect the phone, power it on into RECOVERY, Wipe Battery Information, and power it off.

7.) Reconnect the phone, charge for 30 minutes, even if the notification LED is green.

8.) Disconnect the phone, power it on, and use it.

Is this correct?
[Nexus One Android Development] mtw4991:
Yep that's what I did although I must admit I left it on for about 60 minutes but don't think it made much diff
[Nexus One Android Development] wildmonks:
Update for both .34 and .35:

2.6.34 kernels

Changes since kernel date 070110:

-Lots of commits added from IR's latest source (2010-07-05 & 2010-07-07)

-Version changed to 2.6.34.1 (Latest stable release)

2.6.34.1_AVS-800mV_CFS_1113Mhz_070810.zip

2.6.34.1_AVS-925mV_CFS_1113Mhz_070810.zip

2.6.34.1_AVS-800mV_BFS_1113Mhz_070810.zip

2.6.34.1_AVS-925mV_BFS_1113Mhz_070810.zip

No Audio Boost versions can be found here.

2.6.35 kernels

Changes since kernel date 070510:

-Tons of commits added from IR's latest source (2010-07-06, 2010-07-07 & 2010-07-08)

2.6.35-rc4_AVS-800mV_CFS_1113Mhz_070810.zip

2.6.35-rc4_AVS-925mV_CFS_1113Mhz_070810.zip

2.6.35-rc4_AVS-800mV_BFS_1113Mhz_070810.zip

2.6.35-rc4_AVS-925mV_BFS_1113Mhz_070810.zip

No Audio Boost versions can be found here.
[Nexus One Android Development] waylo:
Oh no, it's an update! =)

Do I get greedy and flash? Or am I content with 7/1/10??

For now, the opposite of good is perfect...

Trying to sift through all the updates on the commit history... wish I understood half of it =P
[Nexus One Android Development] wildmonks:
Its a whole bunch load of changes, but interestingly, I have not found any obvious difference in performance or battery life. I say go ahead and stay with what works. But if you do update, do a nandroid backup ;)
[Nexus One Android Development] SimFox3:
Running 7/8 - 800-CFS-No-Audio. I'll report findings and battery burn rate tomorrow morning.
[Nexus One Android Development] Autinhyeu:
Edit: mistake... sorry :D
[Nexus One Android Development] fitsnugly:
:D 7/8 on CM6 nightly
[Nexus One Android Development] harmohn:
7/8 925 BFS on CM6 nightly 7/9 ;)

Sent from my Nexus One
[Nexus One Android Development] fitsnugly:
Showoff ;)
[Nexus One Android Development] wildmonks:
Whoa... This makes me want to try the cm6 nightly builds :eek:
[Nexus One Android Development] fitsnugly:
Ran it again just for fun and popped an 1805 ;)
[Nexus One Android Development] notxel21:
Since we seem to be having a friendly pissing contest I'll post. ;) :D

Running 2.6.35-rc4_AVS-925mV_BFS_1113Mhz_070810 on

CM Nightly cm_passion-07092010-013513 :cool:
[Nexus One Android Development] wildmonks:
I think I just pooped a little when I saw this...
[Nexus One Android Development] fitsnugly:
Made your socks wet did ya?
[Nexus One Android Development] yvyv:
I have to admit this Kernel 2.6.35-rc4_AVS-925mV_CFS_1113Mhz_070810.zip is wicked, Fast, smooth "AWESOME"

Thank you..
[Nexus One Android Development] notxel21:
So after you wipe yourself are you going to try a CM nightly build? :confused: :D
[Nexus One Android Development] flak0:
1731 on Quadrant with 28% battery

just ran quadrant again. I'm blown away. why is this different than pershoots?

posted from my nexus.
[Nexus One Android Development] watercool:
Froyo:

.800 was booting for me but quit every benchmark to the homescreen after a few seconds

.925 reboots constantly after a few seconds

:(

edit: hm, ok, seems to work without OC
[Nexus One Android Development] big_adventure:
Absolutely beautiful kernel.

I'm using the .34 BFS 800mv. It has been completely stable since loading it about 20 hours ago. Everything I have tried has worked - though I do not use Goggles often and almost never mount the SDCard as a disk. The interface as is completely smooth as ever (and noticably smoother, to me, than IR's, though that, too, was nice). Battery use overnight was nearly nothing - I charged it to 100% around 8PM, and, after a little chat, a few emails and a few SMS, I had 86% this morning at 7:15AM. That is probably the best I've EVER seen on this phone. I could not use AVS on 2.1 / CM, because it always caused frequent reboots, but that seems to be a thing of the past with .34 on FroYo. wiFi and WiFi tether both (still) work flawlessly.

I just turned 910 in Benchmark Pi (my high - faster than the 944 best I turned on Pershoots OV - and #105 on all devices).

I don't seem to turn Linpack as well - I was turning 42-43 on Pershoot's, with a high of 44.011, and I seem to see 37-38 with a high of 40.23 on this one.

Quadrant (I never used it with stock, IR's or Pershoots) just turned 1727 with SetCPU on "Ondemand".

This is with no special service stops or starts - the phone has been running since I pushed the kernel, has done browsing, calling, SMS and GTalk, played a couple of games, sat there while I both read and sync'd NewsRob, Sync to Google, Facebook and Twitter are all running, Y5 has WiFi shutdown here, 3G is connected and working, I even received a notification during (or maybe just before or after) the Quadrant test.
[Nexus One Android Development] wildmonks:
Hmm.. Sorta looks like your phone doesn't respond well to overclocking. Have you tried clearing out your cache before or after you flashed? Have you tried out the Pershoot's OC kernels? If you have no problems with his kernels then I guess your phone doesn't like AVS+OC together... :(

I'm glad it's working out well for you :).

Yah, I too have similar results with my benchmarks with some actually lower then what others have been getting. I think irishrally had it right when he said it's not only the kernel that determine one's results.

But what probably matters more is one's user experience with their phone. And from what you described, you seem to be one happy user ;)
[Nexus One Android Development] t0ol:
same. cant OC.. went back to pershoot
[Nexus One Android Development] watercool:
i don't really need OC, i am happy with 1000 mhz and this kernel should give me a better battery.

I'll try the pershoot just because i am curious if i have a bad cpu or not :(

@ to0l, may you please give me a link if you find a kernel that works with oc?

and a noob question:

with AVS the 800mV is the minimum voltage.. what is maximum and what is default for nexus one @ stock kernel?

@pershoot: http://droidbasement.com/db-blog/ one of these froyo kernels?
[Nexus One Android Development] RinTinTigger:
just want to keep guys remembered, who "partly" initiated this kernel ^^

It was ME!!

^^
[Nexus One Android Development] gn00my:
omg ! thanks , i´m blind now :D
[Nexus One Android Development] fitsnugly:
OK tried out the .34 925 BFS version... SetCPU short benchmark is regularly getting high 190's, low 200's results... with pershoot's I was gettin high 240's, low 250's...

Interesting....
[Nexus One Android Development] t0ol:
pershoot`s latest .34 for froyo works fine for me with OC..

http://xdaforums.com/showthread.php?t=633238
[Nexus One Android Development] paratox:
WTF?! i`m also blind!^^

ot:

witch wifi module is used in the .34 kernels?

i`m not able to get above 52 Mbps. doesn`t look like draft-n. sometimes it drops to 19 Mbps for no reason.

edit: forget it! after doing a wlan speed test the link speed increased to 72 Mbps. looks like the new wifi module is used.
[Nexus One Android Development] irishrally:
You must have some sweet internet service to pull speeds like that.
[Nexus One Android Development] paratox:
link speed is the output of the wifi information when you dial *#*#4636#*#*

it`s the link speed between phone and router.

my ISP speed is "only" 50 Mbit. ;)
[Nexus One Android Development] irishrally:
Only 50Mbit? Man life's tough.
[Nexus One Android Development] mtw4991:
Mediafire seems down at the moment. Anyone got a mirror or repos. for the 925 BFS OC?
[Nexus One Android Development] wildmonks:
Hastly created mirror for you. I'll update the first post with this link too.

http://drop.io/wildmonks
[Nexus One Android Development] wildmonks:
The max is currently set at 1275mV for these kernels, which if I'm not mistaken is also the same for the stock kernel (just took a quick look on the official Android source site).

BTW: It looks like 1050mV is the min on the stock kernels.

I think I just barfed a little, Lol

Just to confirm, yah its using the updated wifi code.
[Nexus One Android Development] mtw4991:
Thanks for the mirror. Flashing now, will report later.
[Nexus One Android Development] chowlala:
Wow. I must say... I'm very impressed. XD

PS EDIT: I ran the above Quadrant test on the 925v BFS.

Just wanted to ask a few newbie questions, what's the primary difference between BFS and CFS? In lay man terms please, been reading and searching and it's very technical. Lol.
[Nexus One Android Development] darkjedi:
Wow, how the heck did you get that? I'm getting barely 1500 using the same kernel.
[Nexus One Android Development] wildmonks:
Hellz to the yeah!

I was going to wait until they made a release candidate but not anymore! ;)

Your welcome :o
[Nexus One Android Development] notxel21:
Schweet!! :D It gets better nightly!! :eek:

I'm loving your kernel as you can tell I'm sure! Thanks! :cool:
[Nexus One Android Development] crimsondr:
This convinced me to try this kernel. Didn't get the results I wanted. So you ended up convincing me to flash cm nightly build! It's great!
[Nexus One Android Development] wildmonks:
Sweet! I get to join the +1800 club! :D

Rom: CM6 Nightly (cm_passion-07092010-013513.zip)

Kernel: 2.6.35-rc4_AVS-925mV_BFS_1113Mhz_070810

Took me 5 or 6 runs before I finally broke 1800.
[Nexus One Android Development] mtw4991:
lol, wildmonks is awesome on its own. This was pre-CM6 Alpha, just stock FRF85B with wildmonks kernel.

Gonna try the 0709 nightly and latest Wildmonks kernel:-)

I wish the iDont was part of the graph also!
[Nexus One Android Development] mtw4991:
Nice, now calibrate your battery, lmao:D:eek: Btw, did you wipe data (not yourself) before you flashed the nightly or your kernel?
[Nexus One Android Development] harmohn:
Hehe, the combination is just sick! :)
[Nexus One Android Development] wildmonks:
Yes I did, both me and the phone. :p

(data/cache/Dalvik)

Still in the process of putting all my apps back and theme.

I see I don't have to mod for the text colors. Very cool :)
[Nexus One Android Development] mtw4991:
umm, interesting. I wiped cache/dalvik, then flashed CM nightly then booted right back into recovery and flashed your latest. I did not wipe data as I didn't want to have to put all my apps back, lol. That might be why my Quadrant is only topping out at 1775?? Neocore otoh was 30.7 and Linpack was still around 41-42 tops. That's maxed out at 1113 performance.

Any ideas? should I rewipe and reflash?
[Nexus One Android Development] wildmonks:
I was only able to get +1800 before I install back all my apps. I haven't been able to since. I'm also experiencing launcherpro FC with this nightly after I placed all the widgets that I use on the homescreen (even with the stock kernel). I think I'll probably go back to alpha 1 after I'm done testing and wait for a more stable cm6 release.

Edit: I lowered launcherpro's memory usage and that fixed the FC.

Edit 2: I changed the VM heap size to 24m and now all is well. I was able to return launcherpro's memory usage to high. No FC and its nice and smooth. Guess I'll be staying on this nightly :)
[Nexus One Android Development] waylo:
I'd been having great luck with the .34 800mv/BFS kernel for a few days. Then yesterday and today, I think I started having some of the mentioned low voltage problems. This afternoon, after a rapid slew of notifications, I was unable to get the phone to unlock as the touchscreen was totally unresponsive and the trackball was extremely sluggish. Too sluggish to do a reboot from the powerbutton menu.

I did a battery pull but ended up in a "7-vibrate" boot freeze (phone vibrates 7 times when the battery gets put in and doesn't respond at all afterwards--cannot boot at all). Finally discovered you can leave the battery out for a while (? to fully discharge the phone) and it will restart okay.

Trying the 800mv .34.1 CFS now. Let's see what happens.

Don't plan on 6.0 for now, so I can't join in on all the fun you guys are having with .35!
[Nexus One Android Development] SimFox3:
WildMonks,

How did you increase the VM heap size? I don't see no -Xmx option =P
[Nexus One Android Development] wildmonks:
Good luck with the 800mV CFS! Hopefully that will work for yah, otherwise you'll have to move on to the 925mV kernels. Also thanks for reporting your "7-vibrate" boot freeze. If any others encounter that, they will know to leave out the battery longer so it will restart normally.

Oh, in the nightly build they added the ability to change the VM heap size directly from the settings menu. You'll find it if you go to settings --> CyanogenMod settings --> Performance settings --> VM heap size

Interestingly, the default its set to 32m but launcherpro seems to have a problem at the setting. Lowering it to 24m fixes the previously mentioned problem for me.
[Nexus One Android Development] big_adventure:
Odd, I'm using the 709 with 32M heap, and LauncherPro sings sweetly. :-) Ah, maybe it's something in the kernel? I'm on the CM6 kernel (for now, until I flash another of course...)
[Nexus One Android Development] wildmonks:
I only get this problem when I loaded LauncherPro up with all my widgets and I use A LOT of widgets (heh) and i like to set my LauncherPro to high memory usage profile. As I stated before, I got the same problem with the default kernel. I haven't tried the latest nightly though. It may have been fixed there.
[Nexus One Android Development] rumil86:
For me LauncherPRO crashed a lot when in its setting I had "Keep in memory" checked. After disabling it, it's stable with 32MB heap size.
[Nexus One Android Development] dictionary:
Doesn't matter the kernel for me, or the launcher. Both adw and LP produce the FC. I also had a ton of Widgets. It happened when switching orientation from landscape to portrait on a page/screen with a lot of Widgets, then scrolling back and forth. This is with any memory usage profile, with heap at 32. Never thought to lower it. I ended up just dropping to two screens and using powerstrip
[Nexus One Android Development] wildmonks:
Uh.. weird.. so I just put back to 32M (to do what rumil86 suggested) and its still silky smooth with no FCs. I reciently updated to the latest LauncherPro, maybe that fixed it or maybe it was switching the VM heap size back and forth? :confused:

Whatever... its all working fine now, that's what matters :D
[Nexus One Android Development] wildmonks:
Dropping back to just two screens and using powerstrip would annoy the hell out of me... Fiddle with the VM heap size, see if it fixes the problem. Certainly this has been a weird bug for me to deal with.
[Nexus One Android Development] pzumk:
CyanogenMod 6.0.0 nightly with .35 925mV BFS 1113MHz Kernel

(unfortunatly it didnt hide shootme, wth)

How did you get 1800+ ?! O_o
[Nexus One Android Development] harmohn:
Run it 3+ times ;)

Sent from my Nexus One
[Nexus One Android Development] wildmonks:
I did the following:

-I restarted the phone

-Waited for it to finish loading

-Set to 1113MHz performance

-Task killed everything (Big Killer)

-Ran Quadrant 5 or 6 times till I got a "high" score.

-Press the home button, ran ShootMe, press Hide

-Press the home button and returned to Quadrant

-Took my screen shot

I was lucky to get +1800, usually only get upper 1700. I believe a backgrounded app that reloaded or even the launcher is stealing precious cpu time away from Quadrant :rolleyes:

This kinda tells me that quadrant numbers doesn't mean a whole lot if it can be skewed that much but I guess its fun to brag about. ;)
[Nexus One Android Development] pzumk:
Did it the same way but not multiple times.

now

1st: 1500

2nd: 1758

3rd: 1752

;)
[Nexus One Android Development] wildmonks:
There yah go, much better ;)
[Nexus One Android Development] pzumk:
Yeah thanks ;)

btw did you mess around with the overclocking? I know pershoot or persiansown or someone find out the "highest" clock rate to run stable but did you try even higher?

I'd like to know how the phone acts with 1.2 or 1.3GHz
[Nexus One Android Development] wildmonks:
I tried 1152MHz for a little bit and got some better benchmark numbers but the phone got pretty hot, very quickly.:eek: I determined it was unsafe and never made a 1152MHz kernel again.
[Nexus One Android Development] pzumk:
lolwut

the temperature difference is THAT big between 1113 and 1152?

you know anyone who tried 1.2GHz yet?
[Nexus One Android Development] wildmonks:
Nope. Not publicly anyway.

It really starts getting dangerous at those upper speeds as it requires the overvolt of 1325mV or more which is above the rated specs of the voltage regulator. If you don't damage the cpu at those speeds, you may damage the voltage regulator instead.
[Nexus One Android Development] mtw4991:
was playing around last night and got an 1836, my highest, lol
[Nexus One Android Development] flak0:
Thanks WildMonks

@Wildmonks I just wanted to say thank you for your hard work and dedication. I would love to learn how to compile kernels. I just got a brand new i7 desktop and i'm ready. anyways I wanted to share with you and the communtiy my results for runnin your Kernel and only completing steps 1-3 for battery bump. I also have attached an screenshot of my reply to hack-a-days ridiculous article on Android. I can't stand fan-boys. Anyways heres the screenies. Thanks again man.

By the way for those who would like to know my SetCPU settings:

This is with WIFI and SYNC on
[Nexus One Android Development] Kepster:
SetCPU

Sorry for being an ignoramus guys, but can i use setCPU to overclock my N1? Thanks heaps! This kernel looks interesting, been using persiansown. want to try this one.
[Nexus One Android Development] flak0:
Yes you can. This is a great Kernel. Just slide the slider in SetCPU to your desired clock speed and tick on boot. Thats it.
[Nexus One Android Development] Kepster:
Thanks for the quick reply dude! Will try this on CM6 RC1.

Thanks again!
[Nexus One Android Development] wildmonks:
Just finished reading the hackaday article and wow, its full of miss information and slander against the android platform. :mad:

Your gonna love it when you start compiling! You'll learn so much about the platform and get to make custom kernels that fit your needs/wants. If you have any questions or run into any trouble when you start compiling, let me know, I'll be glad to help yah out ;).

BTW, awesome core i7!! I bet if I had that, it would reduce my compile time in half. That last release I did with 16 kernels took forever...
[Nexus One Android Development] flak0:
Let me know if you need any help.
[Nexus One Android Development] pakraider:
All working great here on CM6 RC1, great work!

For the 925mV kernel, does AVS still kick in on 1075, or does it stick to static voltage whenever it over clocks (or is it static only at 1113)?
[Nexus One Android Development] rodigezstyle:
u think about create a 1.2 Ghz Kernel ? source is up...
[Nexus One Android Development] athost:
http://xdaforums.com/showpost.php?p=7135152&postcount=608
[Nexus One Android Development] damanrico:
While we're talking about speeds above 1113 mhz, let me ask a quick question as well: Why can the Desire handle much higher clockspeeds than the Nexus One? Isn't the hardware almost 100% the same?
[Nexus One Android Development] wildmonks:
@1075mhz your still using AVS. Static is only at 1113mhz (1275mV)

I will not do 1.2ghz as at that speed it would require a voltage beyond 1300mV. Not only do I not feel comfortable overvolting the regulator but I would also have to bypass voltage safety limits in the code. I'm sure there's a good reason why they set the max volt limit to 1300. Sorry... :(

I am open to the idea of 1152mhz as that speed only needs 1300mV to be stable. But it can get uncomfortably hot...

It can? I wasn't aware of this... I know the EVO can overclock beyond 1.2ghz with no problems as it is using a newer qualcomm processor.
[Nexus One Android Development] damanrico:
I've seen kernels that are doing 1113-1267, and I think I even saw kernels with 13xx mhz. I wonder if those are also in danger of doing serious damage to the device as you have been talking about, or that the Desire can handle more.

I'll never use a kernel that can do damage to my device, so I'm happy being @ 1113 mhz (although I've been setting it to max 1036 for AVS usage), but it just made me wonder why the Desire has such kernels.

Oh another question: Is there any noticeable difference in voltage between max 1036 and 1075 mhz? You said 1075 also still uses AVS. So I'm wondering if setting the max to 1075 will result in the same battery saving.
[Nexus One Android Development] wildmonks:
Hmm.. not sure why.. I would be concern using those high mhz kernels for the desire.

I have set both 1036 and 1075 mhz to have their AVS voltage max out at 1250mV but AVS will often set a lower mV automagically whenever it can :)
[Nexus One Android Development] damanrico:
Okay cool, so the battery usage should be the same? Btw, thanks for answering all questions so fast and with great detail.
[Nexus One Android Development] wildmonks:
Battery drain can also be a component of how fast and hard the cpu works and not just how much voltage is feed. But yah, it would be a very, very small difference between 1036 and 1075 mhz.

No problem about answering the questions. I try my best to give a complete answer whenever I can ;)
[Nexus One Android Development] mrmarshall428:
Juice defender

Wildmonks, do you use juice defender the app from the market that lets you set profiles to save battery? Don't know if I'm wasting my time using it!
[Nexus One Android Development] xda890:
Does this kernel have the tun/tap module compiled and included?

Edit: Seems like it doesn't... Any chance for including this?

BTJ
[Nexus One Android Development] wildmonks:
I never did play around with juice defender. I'm actually pretty satisfied with the battery life I have now.

Its currently compiled into the kernel rather then making it a module (so no tun.ko) This was a setting that was carried over from IR's kernel. But I was never able to see if VPN works (don't have a VPN to connect to).
[Nexus One Android Development] wildmonks:
I did a quick test to see if I can access a tun0 device and it looks like I can. I don't know about actually connecting to a vpn server but the tun device is present.

openvpn --dev tun0
Sun Jul 11 15:16:25 2010 OpenVPN 2.1.1 i686-pc-linux-gnu [SSL] [LZO2] [EPOLL] built on Jul 10 2010
Sun Jul 11 15:16:25 2010 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Sun Jul 11 15:16:25 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Sun Jul 11 15:16:25 2010 ******* WARNING *******: all encryption and authentication features disabled -- all data will be tunnelled as cleartext
Sun Jul 11 15:16:25 2010 TUN/TAP device tun0 opened
Sun Jul 11 15:16:25 2010 UDPv4 link local (bound): [undef]:1194
Sun Jul 11 15:16:25 2010 UDPv4 link remote: [undef]
[Nexus One Android Development] xda890:
Aaaah... great... Will test this tomorrow... :)

BTJ
[Nexus One Android Development] wildmonks:
Coolzors ;)
[Nexus One Android Development] fitsnugly:
Woot. CM6-RC1 is badass. and only 28.7C temp when I ran that :)
[Nexus One Android Development] wildmonks:
Nice, you get to join the +1800 club ;)