yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] MaxiJavi:
I have gone back to the TEST ...

I get better battery life in standby from that kernel than in any kernel that came after.

With the next release I'll retest, but for now I need something that I know works well :-)
[Nexus One Android Development] intersectRaven:
Minor update uploaded again! This should improve battery life somewhat by a tiny bit. :)
[Nexus One Android Development] tsouza:
Worse battery life ever

Ever since this TEST release my battery life is awful, it's like ~10% drain per hour (mostly in standby).

I've gone back to 0613_2053, which is much better...
[Nexus One Android Development] Gilg@mesh:
is this the latest 800mV BFS kernel?

2.6.34_AVS-800mV_BFS_20100619_0016.zip
[Nexus One Android Development] hah2110:
Yes, I believe so. I just tried the latest 800 CFS and think it is holding up well.
[Nexus One Android Development] sir*mez:
Yes this update is a beast! I'm on 70% and 7h 30m. Minor update great battery! Keep up the great work!
[Nexus One Android Development] intersectRaven:
Update!

20100619_11XX_.34:

- updated with latest Android Experimental repository commits

- includes all minor updates from before

Here're the links:

20100619_11XX_.34:

BFS:

925mV -> http://www.mediafire.com/?zdmtjwtndxc

800mV -> http://www.mediafire.com/?lkwczwy2ktn

CFS:

925mV -> http://www.mediafire.com/?z3zjwudo5my

800mV -> http://www.mediafire.com/?gdk454md2fy
[Nexus One Android Development] THATTON:
This is the fastest intersect raven kernel i have ever seen and i've been flashing these things since the beginning!!! All i can say is wow! Battery life is fantastic(as long as it is on par with the one "minor update" from before) and speed is unreal!!!! Thank you sir!
[Nexus One Android Development] sir*mez:
I thought you were bs'ing. But this kernel like you said is fast. Hopefully its not a performance over battery. I will be testing this, I was happy with the battery life on last minor update. So I hope the battery stays the same as before.
[Nexus One Android Development] intersectRaven:
Minor update was uploaded again. I just updated the scheduler to its .35 version. :p
[Nexus One Android Development] watercool:
ok, i'll try my luck here again, probably it is not an IR issue:

I have 2 Nexus one, both have exactly the same rom (installed from the same zip file), the same apps, the same configuration (apart from the gmail adress) and the same kernel version.

One is fine, the other one has sometimes touch issues. Touch issues mean:

when you push for example the "e" button on the keyboard, the "y" or "x" button is pushed, pushing the "x" button does nothing or closes the windows. I am quite sure it is not the keyboard, and i am sure it is not the rom version cause this happend with different roms.

Might it be possible it's the kernel?

Locking the screen and and unlocking solves the problem.

thx.
[Nexus One Android Development] Gilg@mesh:
13xx is latest?
[Nexus One Android Development] intersectRaven:
Latest yes. :)
[Nexus One Android Development] hah2110:
Re: [.33.5 & .34]intersectRaven's Kernel (Hybrid AVS *Stable*) 06/19/2010 11:48am

I don't get it. Battery is phenomenal until I leave the phone overnight. I just lost 30% in 6 hours.

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One Android Development] THATTON:
Then just charge it overnight and not worry about it. :confused:
[Nexus One Android Development] hotweiss:
It could be a bad app that is causing this. Download OS Monitor to see what app could possibly be causing this.
[Nexus One Android Development] hah2110:
I have it but it only goes back like 3 minutes... Or am I missing something?
[Nexus One Android Development] r34p3rex:
I've been playing with the various 800/925 bfs/cfs kernels for a while now.. which gives the best battery life? :D I haven't been recording my battery life after testing each kernel

I read somewhere that the 800mv may actually give less battery life than the 925 since the radio gets less power and thus works with a weaker signal. Is this true?
[Nexus One Android Development] watercool:
Re: [.33.5 & .34]intersectRaven's Kernel (Hybrid AVS *Stable*) 06/19/2010 11:48am

For some reason every phone respond in an other way to different kernels so you have to try. With the 800 my phone switches constantly between 3g and e.
[Nexus One Android Development] wildmonks:
+1

Mine switches back and forth in certain locations on 800, which results in more battery drain.
[Nexus One Android Development] intersectRaven:
Posted another minor update. This one disables the FAIR_SCHEDULER option to increase performance. (contributed by damentz) :)

Btw, minor updates can be found on both MediaFire and my MyHangoutOnline repository. :)
[Nexus One Android Development] THATTON:
For which scheduler? Ondemand, Conservative or both?
[Nexus One Android Development] intersectRaven:
It's not for the governor. It's for the CFS scheduler. According to damentz, CFS should perform better than BFS with this. I'm inclined to believe him since my Quadrant scores are now consistently better now. :)
[Nexus One Android Development] rjhay22:
Nice... trying it out now. Thanks.
[Nexus One Android Development] spr33:
I'd love it if people would describe how they're getting their excellent battery life:

- What CPU governor they're using

- What SetCPU profiles they're using (+ speed/oc/uc info)

- Whether they're leaving data/wi-fi enabled

- What kind of apps they have running

- Whether they're leaving sync enabled

- What ROM they're using

- What *exact* kernel they're using
[Nexus One Android Development] intersectRaven:
I'll humour you on this one since I'm bored...

- conservative

- none

- wifi set to turn off when suspended UNLESS plugged-in

- runtime, I think only advanced task manager, setcpu and battery graph on the background

- yup

- FroYo FRF50 before, FRF72 now

- mine? (duh...well 925mV CFS if you want specifics)

:p
[Nexus One Android Development] nurre:
Switching between articles in newsrob seem considerably slower for me. There might be a quite big performance/latency tradeoff disabling fair scheduling.
[Nexus One Android Development] spr33:
Humour away. I just managed to get my battery to drop 10% every ~1h 20minutes under my usual conditions thanks to you. (Checking email/twitter/browsing/texting/sync/data enabled). Currently at 70% after 4h 12minutes. This is about 3x better than I was getting before changing kernels/SetCPU profiles.

Sure, it's all good and well putting out an 'energy efficient' kernel but if there isn't any guidance to go with it it's almost useless. Sharing information benefits the community.
[Nexus One Android Development] sir*mez:
Every phone is different. This is like a hah2110 question. You have to find out what works for you, you'll have to go and run some tests.
[Nexus One Android Development] hah2110:
Ouch! I asked questions to see what was happening with the masses. But I can tell you from 1st hand experience, not every kernel works the same for everyone.
[Nexus One Android Development] mtw4991:
ROFLMAO:D;)...sorry, hah, I couldn't help myself! we only pick on the folks we like, otherwise they are ignored:eek:
[Nexus One Android Development] rjhay22:
Lies! Just kidding. Back to lurking... *whistles*
[Nexus One Android Development] thelucster:
I can't remember whether I've yet said thanks, so here goes again: Thanks for your great work and keeping this so up to date! :D
[Nexus One Android Development] Contivity:
can I run this after flashing MCR r17 or r18?
[Nexus One Android Development] lorloff:
Yes, just make sure you're running the .34 version.
[Nexus One Android Development] wildmonks:
FAIR_SCHEDULER observation

Hey IR, just wanted to share my observations with the FAIR_SCHEDULER disabled. Indeed I saw a consistent increase in benchmark scores with it disabled. But I noticed that the launcher (launcherpro) became noticiably laggy when swiping between homescreens. Its subtle change that I did not see until I upgraded to FRF72.

It could be just my imagination and I maybe the only one seeing this but I swear its there haha. Its also something that I can see in your kernels too (between your 20100620 and 20100619 CFS).
[Nexus One Android Development] intersectRaven:
Minor update posted again! Changes include resync with both Android Experimental and Cyanogen's repositories. For details, look in my GitHub. :)
[Nexus One Android Development] r34p3rex:
Awesome, testing it out now :D
[Nexus One Android Development] intersectRaven:
Yung iba lang dito eh yung AVS saka yung non-AVS di overclocked. :)

* The difference of this kernel is in the AVS and that the non-AVS version is not overclocked. :p
[Nexus One Android Development] intersectRaven:
I see...it seems you just received a greeting from AVS back there! :p
[Nexus One Android Development] bobdude5:
i love your kernels..great on battery :) and its nice to see a new one ever day (i love flashing my phone) lol
[Nexus One Android Development] intersectRaven:
Thanks! I love seeing compilation messages and to always have the latest version which is why I started this. Also, it doesn't hurt exercising my programming muscles! :p
[Nexus One Android Development] britoso:
happy to report that '2.6.33_AVS_20100410_1809.zip' works flawlessly on CM5.0.6-N1-test2
[Nexus One Android Development] rjhay22:
Testing 1000mv on Enoms ROM. Ill report back on the outcome.

Edit: 1000mV seemed stable and working... Trying out the 850mV now...
[Nexus One Android Development] www1:
I can't use AVS kernel.

I try different way but nothing.

I only use it with cyanogen 5.0.5.3 now with 5.0.6test2 always reboot.

:(

I have try to wipe cache, wipe dalvik but nothing.

This kernel seem doesen't work on my N1.

Any suggestion for try to use it?

When I flash It reboot or stop on boot. Anytime It's start but after a few second it frezee
[Nexus One Android Development] RieGo:
freezes or reboots only occur while booting or right after boot is done, when entering my PIN. but it seems to be gone now. debug info is a good idea
[Nexus One Android Development] intersectRaven:
Unfortunately, right now it really is random as to whether or not AVS works or not. It could work after a few reboots, an hour of reboots or no reboots at all! I recommend just sticking with non-AVS for now until AVS has been "stabilized". You could also try Ivan's since our modifications already diverged at some point. :)
[Nexus One Android Development] www1:
I have try Ivan kernel already but with no luck.

Now I retry to flash and to reboot N1 I hope to have more lucky.

:p
[Nexus One Android Development] die-hard:
Raven, after a few reboot and freez my N1 work fine with your kernel 850.

In the afternoon i'll try to install 800mv ;)

I hope it work fine
[Nexus One Android Development] vipermo:
Re: [Kernel - .33]intersectRaven's Kernel (with several tweaks) 04/11/2010 09:08am

well i flash the kernal works great but every time i put the wifi fix over it puts my phone in a loop anyone else had this?

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] intersectRaven:
Are you trying to connect to a WiFi that has a hidden SSID? It is a known issue with the wifi driver revert by cyan. :confused:
[Nexus One Android Development] die-hard:
I have freeze problem when i reboot my device and it is connect to usb cable or in recharge mode.

Anyone have this problem?

I work on 850MV kernel

Another problem: my device reboot when i start SetCPU :(

After first reboot battery go 100% to 98% ;(
[Nexus One Android Development] Pochemuchka1977:
Is there are any debug messages in kernel regarding AVS?

And is there any way to know for sure that device enters the sleep state without errors?
[Nexus One Android Development] vipermo:
No mate i cant get my phone back i have to restore it its very strange cos the kernel works great only when i replace the .ko file to get wifi working after reboot just gets stuck on the animation X bit.. could it be cos im replacing the the .ko file using root explorer ?

many thanks
[Nexus One Android Development] intersectRaven:
Right now, the debug information only appears when there is a really bad failure with AVS. I plan to enable a few more AVS debugging messages in the next release. :)
[Nexus One Android Development] intersectRaven:
I am unfamiliar with root explorer so I can't really say. It could be a reason though since an incompatible bcm4329.ko file could make the kernel restart when it tries to load it. :confused:
[Nexus One Android Development] LunatikBunnie:
AVS hates me no matter which UV i choose =( random reboots and FC and even freezes. and i'm ALWAYS on conservative governor in SetCPU. I'm back to using the non-AVS that you have now(it seems to work for me at the MEAN TIME, will report abnormalities if i come across them). Ivan's Kernel seem to work flawlessly as well(non-avs, of course)
[Nexus One Android Development] vipermo:
worked with the other ones u have done very strange..

ok big ask is there any chance of a update.zip file?

thanks :)
[Nexus One Android Development] mtw4991:
Froyo just dropped in the AOSP according to Cyanogen's tweet!
[Nexus One Android Development] Pochemuchka1977:
Hey,

I am running CM 5.0.8 with your latest kernel (2.6.34_AVS-925mV_CFS_20100620_0948.zip) and today my phone got stacked and the touch screen stopped to respond. The power button was working, but that's all

The only thing I could do is to reboot the device with trackball + volume down + power

From the /proc/last_kmg I saw the following:

[ 4024.156982] mmc0: Data timeout

[ 4024.740936] batt: 91%, 4060 mV, -123 mA (-156 avg), 29.6 C, 1238 mAh

[ 4026.206909] mmc0: Data timeout

[ 4027.488159] AVS setting V to 1225 mV @998 MHz

[ 4027.578277] AVS setting V to 925 mV @245 MHz

[ 4028.256439] mmc0: Data timeout

[ 4028.272521] mahimahi_ts_power: power 1

[ 4028.275268] dhdsdio_htclk: HT Avail request error: -35

[ 4030.031066] AVS setting V to 1225 mV @998 MHz

[ 4030.080627] AVS setting V to 1150 mV @768 MHz

[ 4030.120666] AVS setting V to 1225 mV @998 MHz

[ 4030.241973] AVS setting V to 950 mV @384 MHz

[ 4030.291015] AVS setting V to 925 mV @245 MHz

[ 4030.310302] mmc0: Data timeout

[ 4030.417816] keyboard reset

[ 4030.532928] AVS setting V to 1225 mV @998 MHz

[ 4030.555908] save exit: isCheckpointed 1

[ 4030.557373] Restarting system.

[ 4030.557495]

[ 4030.557739] Restarting Linux version 2.6.34-CFS-intersectR (root@raven-lx) (gcc version 4.4.1 (0xlab) ) #1 PREEMPT Sun Jun 20 09:48:24 PHT 2010

[ 4030.557739]

[ 4030.581329] wds: 0022 @ ff

[ 4030.581329] qmi: wds: DISCONNECTED

The full log can be found at Full last_kmg

Any suggestion what might be the problem ? Is it ROM or kernel ?
[Nexus One Android Development] intersectRaven:
I'm currently reworking everything from the latest kernel so maybe this will be solved afterwards. I think it's just a lousy merge or something. :)
[Nexus One Android Development] intersectRaven:
Update!

20100624_23XX_.34:

- reworked the entire source from original Android Experimental branch while cherry-picking select commits from Cyanogen's repository

Here're the links:

20100624_23XX_.34:

BFS:

925mV -> http://www.mediafire.com/?mlm5bmmzmm4

800mV -> http://www.mediafire.com/?dtyzt5nyeej

CFS:

925mV -> http://www.mediafire.com/?kzoz31lnumj

800mV -> http://www.mediafire.com/?gjxy3zmqfiw
[Nexus One Android Development] G0belet:
Flashing ;)
[Nexus One Android Development] GIKE:
flashed new cfs 800 mV.

Thanks!
[Nexus One Android Development] phewizzo:
flashing :)
[Nexus One Android Development] mtw4991:
@IR, do these blend with Froyo 83?
[Nexus One Android Development] TheMorpheus:
From the first post:
[Nexus One Android Development] watercool:
short answer: yes
[Nexus One Android Development] mtw4991:
Duh, I do read OP's before asking and there wasn't an "update" that specifically said the kernel had been optimized to include the brand new Froyo FRF83. I knew it would work, but was asking if it had incorporated the new source code, i.e. "blended". Sorry if I wasn't clear:eek:
[Nexus One Android Development] Chahk:
Just ran across this thread in G1 Development forum. I was wondering if this method is compatible with Nexus Ones. Or is it something specific to the G1's drivers?
[Nexus One Android Development] www1:
@Intersectr

Now I try original kernel on my N1 and I don't have any touch issues.

I have not to lock and unlock phone for fix this issues.

I have see that the original kernel in SETCPU only use ondemand, userspace, performance and not the other optimizations.

Can we think that the touch issues can be caused by this optimizations?

Thanks

www1
[Nexus One Android Development] seraphimserapis:
I would love to see a Kernel with Framebuffer-Console like here:

http://sven.killig.de/android/console.html

Is there any way to get this to work on our N1?
[Nexus One Android Development] Wysie:
Yup, seeing that too with the latest kernel, LauncherPro seems laggy now.
[Nexus One Android Development] watercool:
some numbers from here if someone is interested.

Running Modaco r19 with latest IR CFS 925. Charged to 100%, rebooted and wiped my battery stats, put phone to sleep. Using conservative govenor(!)

Running: System Monitor, Tasker (Location Check every 10 Minutes)

Synch: Facebook and Newsrob every 4 hours, Twitter every 15 Minutes

Lost 9% battery in 9,5h. I think that's ok.

ADW Launcher feels a bit laggier too when switching between screens, but not sure if this is kernel related or Rom or something else (or maybe the cons. gov.).
[Nexus One Android Development] G0belet:
I had the same power button unresponsive problem. I saw my trackball flashing so I went to see the notification, and couldn't power the screen up. This is with the latest kernel. This is not the first time this happened, too.
[Nexus One Android Development] Royan:
Hmm... maybe it's just me being stupid, but which kernel is most suitable for CM 5.0.8 which is a 2.1 rom that uses froyo radio?

brgds

Royan
[Nexus One Android Development] pzumk:
.34 kernel.

I'm using the latest 925mV CFS .34 Kernel with CM 5.0.8, launcher pro and desire cam, works great
[Nexus One Android Development] Royan:
Thanks xPatriicK I'll give it a try :)

brgds

Royan
[Nexus One Android Development] intersectRaven:
A minor update has been uploaded to my MediaFire folder. This update includes tweaks for the CFQ scheduler, the ondemand governor and the writeback algorithm. As usual, details can be seen on my GitHub commits. :)

***Btw, this may be my last update for awhile since I'll see if the .35 branch made by Google can be made to work. I'll resume maintenance of this branch afterwards. Also, the .33 branch will be dropped since the FroYo source has been released and it's only a matter of time before the ROM cooks release for it. :)
[Nexus One Android Development] eViL D::
Thanks bro, resyncing as I type.
[Nexus One Android Development] intersectRaven:
I'm having trouble pinpointing the reason as to why .35 has errors so I'm posting it here: http://rapidshare.com/files/402943886/2.6.35-rc3_AVS-925mV_CFS_20100626_2048.zip.html

Anyways, here are the errors I've encountered. If ever anyone has any idea as to why please PM me. :confused:

1.) adb shell's cat and ls commands throw a not found error. The same happens when cat or ls is run on the phone's terminal app (not recovery).

2.) SetCPU hangs when trying to open

3.) WiFi can't get an IP address

:confused:
[Nexus One Android Development] wbknox:
Can you check your new link for CFS 925 cannot download .
[Nexus One Android Development] wbknox:
Can you fix your link 2.6.34_AVS-925mV_CFS_20100626_1031.zip can't download.
[Nexus One Android Development] intersectRaven:
I could download it just fine. :confused:
[Nexus One Android Development] intersectRaven:
Minor update has been posted for .34 again! Changes include a newer YAFFS driver and change from SLUB to SLAB memory allocator since while figuring out how to get .35 running, I found that it was the one causing the weird problems. :)
[Nexus One Android Development] dessanct:
Getting 1% drain an hour with the newest minor update! 245 Max in setcpu when in standby..

Texting regularly with a couple calls and browsing! Love it
[Nexus One Android Development] intersectRaven:
.35-rc3 TEST kernel has been uploaded to my MediaFire folder. :)
[Nexus One Android Development] Gilg@mesh:
I will test it (CFS 800mV), but what are the differences between .35 and .34? and btw is .35 stable? :)
[Nexus One Android Development] GIKE:
ditto.

If it´s stable, maybe will test today :)
[Nexus One Android Development] Gilg@mesh:
stable so far :) but I have not done so much, most of time in standby.. but still it works hehe
[Nexus One Android Development] watercool:
Everything ok so far!
[Nexus One Android Development] BootsSiR:
Running 800 and liking it.
[Nexus One Android Development] Harsh:
installed 2.6.35 CFS 925 seems perfect. but linpack scores seem to be reduced, in 2.6.34 i used to get 40.xxx at best, and avg of 38.122 MFLOPS, but in .35 new kernel i get 36.825 avg with best at 38.593. That seem to be reduced speeds by 2 MFLOPS which was the speed of my OLD HTC MAGIC 2.2 MFLOPS on stock roms. Would like to have same speeds and CPU utilization as 2.6.34 in this new one. Hope we get that in future stable release.

Still Thank You intersectRaven for releasing these kernels so fast and also into almost perfect stable stage.

Extremely happy with all your kernels
[Nexus One Android Development] madj42:
Installed the latest .35 925mv CFS kernel today. Appears to be running pretty well. Thanks!
[Nexus One Android Development] sir*mez:
.35rc3 seems stable. Haven't notice any difference from the original stable .34. I haven't dug into it yet.
[Nexus One Android Development] intersectRaven:
We can't really be sure about the speed since this is still just a release candidate for .35. Anyways, I'll be releasing .35 as well as .34 now. :)
[Nexus One Android Development] zizoty:
Hey intersect, whats the goal of .35 kernel and What are they try to improve?
[Nexus One Android Development] intersectRaven:
Look to this for SOME info:

http://www.h-online.com/open/features/Kernel-Log-Linux-2-6-35-taking-shape-1012850.html
[Nexus One Android Development] Harsh:
this link say it is slower, wow i didnt knew they had all this big discussion about slower speeds of .35. but i m sure they gonna improve it before final stable release, not just rc
[Nexus One Android Development] intersectRaven:
If you'll read further, the speed discussion is still anyone's guess since it's still too far from release. Also, it is said there as well that it is typical for the kernel to be slower at this stage in development and that the kernel developers usually address this in the street release. :)
[Nexus One Android Development] dictionary:
I would unleash my .91 kernel, but I'm under strict orders not to from HTC, as it would ruin all future phone sales, due to its sheer awesomeness
[Nexus One Android Development] mindfrost82:
I was running the kernel from 6/19 (925 CFS) and I, unfortunately, had the dreaded unlock screen freeze where you couldn't touch anything on the screen without a battery pull. I went about a week with that kernel and it didn't happen, then I was at a store and I couldn't unlock it. I haven't seen anyone report it with any kernels around or after 6/19, so I just wanted to say that it happened once to me :(
[Nexus One Android Development] Chahk:
You can tell me, I'm a doctor.
[Nexus One Android Development] vnbuddy2002:
It seems that the volume for .35 is very low. .34 is already low, but .35 is even lower. Can you give it a bit juice.

Regards,

Kenny N
[Nexus One Android Development] intersectRaven:
New .35-rc3 HAVS Kernel has been released. Future test updates will be announced on my Twitter account instead of here. :)
[Nexus One Android Development] dictionary:
Same username on Twitter?

\

Yup, lol. Request sent
[Nexus One Android Development] GIKE:
Request sent too. :)
[Nexus One Android Development] intersectRaven:
Btw, to those who are sending requests for me to add them as followers, please note that if you don't have anything android related in your posts (or you also need to be followed to view your own posts) I will decline your follow request. :)