yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] intersectRaven:
We may really have deviated from each other's AVS code. Our respective githubs haven't been updated so I can't really tell where we're at. I'll try redoing it from the non-AVS version using my previous github commit.

*Rebase successful...recompiling now...

**Uploading now...can't really test it on my N1 since I don't experience the problem...

Here's the rebase:

http://www.mediafire.com/?2mtj2vmnydj
[Nexus One Android Development] christiankk:
the 0409 version has been running stable on my n1 for 16 hours now :cool:

thanks for your hard work buddy!
[Nexus One Android Development] die-hard:
Hi man this is last version?

What is different betwen this and avs in first page?
[Nexus One Android Development] intersectRaven:
Good to hear! I might rework it though based on the 0403 version as it seems to be stable for some. I'll slowly readd the AVS edits to find out which is the most stable combination.

This version is a rollback of all AVS edits I made to the 0403 one which seems most stable for some. If the one on the first page works for you, you can ignore this one for the time being. Although I would appreciate testers. ;)
[Nexus One Android Development] persiansown:
To intersectRaven and Ivan:

Hey guys, great work on these kernels. I've been looking to drop the resting voltage lower on my kernel as well (but without AVS). Rather than doing the same research twice, I was wondering what voltages you guys found most stable on the resting frequency.

Thanks for any input!
[Nexus One Android Development] intersectRaven:
I haven't released the XUV mod yet so you'll have to ask Ivan. I have no problems with 800 though in my personal tests but it wildly depends on the CPU. (I'm lucky I guess...) :p
[Nexus One Android Development] Pochemuchka1977:
Well, I saw the error only once until I reached the home screen.

<6>[ 87.879730] do_imprecise_ext: ADFSR = 0x00000004

<6>[ 87.879943] do_imprecise_ext: DFSR = 0x00000436

<6>[ 87.880035] do_imprecise_ext: ACTLR = 0x000c0037

<6>[ 87.880187] do_imprecise_ext: EFSR = 0x00000004

<6>[ 87.880279] do_imprecise_ext: L2SR = 0x00010000

<6>[ 87.880401] do_imprecise_ext: L2CR0 = 0xc0050f0f

<6>[ 87.880554] do_imprecise_ext: L2CPUESR = 0x00001020

<6>[ 87.880645] do_imprecise_ext: L2CPUCR = 0x000000e0

<6>[ 87.880828] do_imprecise_ext: SPESR = 0x00000000

<6>[ 87.880920] do_imprecise_ext: SPCR = 0x0000000f

<6>[ 87.881011] do_imprecise_ext: DMACHSR = 0x00000001

<6>[ 87.881195] do_imprecise_ext: DMACHESR = 0x00000000

<6>[ 87.881286] do_imprecise_ext: DMACHCR = 0x0000000f

<6>[ 87.881469] do_imprecise_ext: TCSR_SPARE2 = 0x0000a037

<1>[ 87.881561] Unhandled fault: imprecise external abort (0x436) at 0x4183702

c

So far running fine :D, I will check the log after running some more applications.

Having more errors:

<6>[ 193.816894] do_imprecise_ext: ADFSR = 0x00000004

<6>[ 193.817016] do_imprecise_ext: DFSR = 0x00000416

<6>[ 193.817108] do_imprecise_ext: ACTLR = 0x000c0037

<6>[ 193.817260] do_imprecise_ext: EFSR = 0x00000004

<6>[ 193.817382] do_imprecise_ext: L2SR = 0x00010000

<6>[ 193.817535] do_imprecise_ext: L2CR0 = 0xc0050f0f

<6>[ 193.817626] do_imprecise_ext: L2CPUESR = 0x00001020

<6>[ 193.817718] do_imprecise_ext: L2CPUCR = 0x000000e0

<6>[ 193.817901] do_imprecise_ext: SPESR = 0x00000000

<6>[ 193.817993] do_imprecise_ext: SPCR = 0x0000000f

<6>[ 193.818176] do_imprecise_ext: DMACHSR = 0x00000001

<6>[ 193.818267] do_imprecise_ext: DMACHESR = 0x00000000

<6>[ 193.818450] do_imprecise_ext: DMACHCR = 0x0000000f

<6>[ 193.818542] do_imprecise_ext: TCSR_SPARE2 = 0x0000a037

<1>[ 193.818634] Unhandled fault: imprecise external abort (0x416) at 0x4858a00

0

It seems to run very slow, Linpack gives about 2.3 MFlops instead of usual 6.9-7.0
[Nexus One Android Development] persiansown:
Alright thanks, I wish I could play with AVS... I just don't have the time anymore.. :(
[Nexus One Android Development] intersectRaven:
As long as you don't experience any reboots or FCs I think I'll count this rebase as a success! Anyways, your Linpack result is odd. I'm running the rebase (except I have my minimum voltage at 800) and I'm having consistent > 7 results...usually 7.132...can you check SetCPU if the powersave governor or something is set to slow down your CPU?

*It seems I really did something wrong somewhere since I now don't see an error with how the CPU sleeps (not suspend). It now sleeps successfully.

**I'm beginning to think this is better...this is the first time I actually saw the POKE CHARGER message while the phone is suspended...I'll update the front page...
[Nexus One Android Development] Pochemuchka1977:
SetCPU shows that scaling ondemand is enabled and running at 998MHz

- Long Benchmark gives me a 2484ms

- Linpack gives 2.5 MFlops

Checked the same with Ivan's AVS kernel - SetCPU shows the same (scaling ondemand and running at 998MHz)

- Long Benchmark gives 1094ms

- Linpack gives 6.69 MFLOPS

On your non-AVS kernel Linpack gives about 7.1 MFLOPS
[Nexus One Android Development] TFJ4:
A fully working phone powered off for 9 hours won't get you 100% battery.... therefore something is wrong or it's BS
[Nexus One Android Development] Realtyem:
alright hah, i'll bite. Give us a comprehensive list of your phone. Any hardware modifications you are using, EXACTLY which kernel build you are running, how you are installing your kernel, which ROM you use(and any mods done to it), every single app you have installed(even the ones you don't think are running or contributing to your battery life), if you use setCpu then all the profiles you have set up. Everything. Tell us about ALL of it. Even your daily usage pattern over the last 48 hours including the little bits like when you plugged it in and how often you've rebooted. I'm off to dinner soon so take your time and we'll pick it apart when you are done. If there's something there, i'm sure we'll find it.
[Nexus One Android Development] Breece:
Well I dont think anyone says you are lying, BUT a cellphone simply needs power... And lets say the cellphone used 0,6% in 9 hours which equals to roughly 9mha...so that is 1mha in one hour...

See where I am getting at? The Nokia 1661 has a standby time of about two weeks with 720mha and it uses MORE than double what your N1 used?

Well leave your N1 on for a straight two months because thats what you should get :)
[Nexus One Android Development] hah2110:
You guys are misunderstanding. It isn't STILL getting that battery life. Now I am getting the ~1%/hour when not being used at all. My point was that PLENTY of people have documented cases where their phone doesn't budge from 100% for a little while. One guy a few pages back had Cardio Trainer going for an hour and it was still 100%. It doesn't make sense that the phone could go for that long at 100%, but then decrease at 1% an hour afterwards.
[Nexus One Android Development] kamasi36:
Not unusual if you are on edge network. Have had phone on for a few hours on one of his kernals the old 800 one and it stayed at 100 percent for almost 3hours. This was on edge though not 3g. Also the usage was text coming in and emails or whatever the phone was doing on its own.
[Nexus One Android Development] ieatacid:
The device is consuming power, therefore it can't sustain 100% battery for such a duration -- the battery level was being reported incorrectly.
[Nexus One Android Development] intersectRaven:
Test Update!

20100519_085X_.34:

- test fix for power problems

20100519_085X_.34:

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

800mV -> http://www.mediafire.com/?i1bku22z3oq
[Nexus One Android Development] hah2110:
9 hours at 100% on WiFi/2G

While I agree. Something isn't making sense here. Lets pull all things constant for a minute here and pretend Raven had one kernel and everyone's phone operated the same. Lets say under usage, everyone's device consumed 2%/hour and everyone used the device the same. The phone would go for 50 hours and, if the battery meters were correct, it would properly report until 2% (when it would properly turn off).

Now, my phone ran 100% for 9 hours and has been properly discharging since after the 9 hours was up. I'm now at 72% and it has been nearly 24 hours and I have had moderate usage (lots of text and e-mails and about 40 minutes of phone calls with 8 market updates). I'm going to continue to let this discharge until it dies (unless I have to charge it preparing to be away from a power source). Now, if the phone magically dies at 10% or 15% or 20%, your theories will be right, and it wasn't really at 140x or 139x mAh for as long as all of the measurements reported. However, if it goes until the regular threshold (probably <4%), then maybe the battery meter is inaccurate BUT, the battery usage was still phenomenal. Maybe then in other scenarios when the phone gets down to critical point, it isn't really critically low, and the meter is inaccurate.

Basically, IF my phone continues to go as long as it should on this scale, something IS wrong with the battery reporting but it is in our favor (meaning we can get more battery life than we think).
[Nexus One Android Development] dnsmo:
still having the usb unmount issue with the latest 2.6.34 avs 925mv cfs 20100517

again in 20100519 testing update also having issue unmount
[Nexus One Android Development] intersectRaven:
That won't be fixed in the near future. The power consumption is a more pressing issue right now together with the touchscreen unresponsiveness problem when left idle for some time. These two should be fixed by the Test Update release. :)
[Nexus One Android Development] dnsmo:
thanks for the quick reply but its annoying to have to reboot the phone everytime I mount the usb :(
[Nexus One Android Development] intersectRaven:
Someone mentioned a market app that allows you to remount the sd card. :)
[Nexus One Android Development] D200P13:
i am on the same version as you (2.6.34 avs 925mv cfs 20100517) and the mount/unmount is working fine for me.
[Nexus One Android Development] dnsmo:
do you remember the name of it?
[Nexus One Android Development] D200P13:
yea i get the 1% per hour on cyans default but we will see tonight :)
[Nexus One Android Development] D200P13:
ahh never mind i cant remount the usb after i did a reboot. weird because it worked fine before.
[Nexus One Android Development] Docmjldds:
It was called USB switcher and I don't think it will be a fix, since I posted this as a workaround when Raven first posted the initial .34 release and at the same time posted .33 release and I mistakenly reported that the market app would work as a temp fix. I did not realize I had installed the .33.

That said, termana's build1 .34 release uses wavelocks, instead of suspend blockers which does not have the USB mount bug. You can always try that and see how it works out. This is working for basically every ROM I have tested, from CM5.0.6 and Pauls A19 and A22 Desire.

http://xdaforums.com/showthread.php?t=670040

Edit: did not mean to mention Desire ROMs since MountUSB is a market app that Paul included in the files
[Nexus One Android Development] intersectRaven:
It seems that Opportunistic Suspend is a long ways off. The official android repositories have been updated to 2.6.34 but using wakelocks only. I'll be reverting to this for my future .34 releases. :)
[Nexus One Android Development] D200P13:
what is Opportunistic Suspend and got an idea as of when you will be reverting?
[Nexus One Android Development] Realtyem:
official android repositories? does that mean that froyo is out?
[Nexus One Android Development] mdubs:
grrr...

Camera is still closing on me after about 10~15 seconds of video.

Using the Desire cam. This is most likely the issue. Still a crazy fast kernel that worked flawlessly in every other area of note.

Thanks for the hard work raven.
[Nexus One Android Development] myplague:
the test file you released is using wakelocks?
[Nexus One Android Development] D200P13:
what happens if i dont turn off the wifi? my first time doing this i didnt turn it off and wifi still works.
[Nexus One Android Development] intersectRaven:
FUTURE releases. :p
[Nexus One Android Development] intersectRaven:
I will be releasing BFS and CFS and 800mV and 925mV versions for 2.6.34 and 2.6.33 in a while. :)
[Nexus One Android Development] paulk_:
Sweet! Hopefully using wakelocks will help with battery saving..
[Nexus One Android Development] Docmjldds:
+1 on this, since Termana .34build 1 wavelocks has no issues with battery consumption increases or Desire Video camera closing down
[Nexus One Android Development] intersectRaven:
.33.4 Update!

20100519_17XX:

- updated BFS version to v0.318

20100519_17XX:

BFS:

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

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

CFS:

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

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

*.34 is delayed since I'm having corruption issues with the source from official... :confused:
[Nexus One Android Development] kiowa79:
Latest .34

I confirm the mount USB issue, is very annoying having to reboot every time I pass files to my N1.

And another two:

Market downloads new app versions sometimes, others doesn't

Multitouch zoom works oddly in default browser
[Nexus One Android Development] hotweiss:
I have been using this kernel all day now. Best kernel yet.
[Nexus One Android Development] Vandam500:
Which one are you using?
[Nexus One Android Development] WebghostDK:
Why do we need like a billion kernels? More ROM's pls.
[Nexus One Android Development] hah2110:
FYI drained as normal last night with ~1%/hour. I am going to continue letting this go but IF it doesn't die until 2%ish, it means I'm right and we can all get better battery life then Google/HTC is letting us.
[Nexus One Android Development] RussianSolja:
Which one you using? I'm looking for the best one to work with xkings ROM. :-)
[Nexus One Android Development] bewA:
What was the last 33.3 update?
[Nexus One Android Development] Docmjldds:
+1 too. FYI, Termana's build1 using wavelocks .34 kernel started to use more battery after a couple of days. Not sure why, but idle time was using 2%/hr or a bit more, compared to the 1%/hr or less using the current Raven .33
[Nexus One Android Development] Docmjldds:
Originally Posted by intersectRaven View Post

.33.4 Update!

20100519_17XX:

- updated BFS version to v0.318

20100519_17XX:

BFS:

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

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

CFS:

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

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

*.34 is delayed since I'm having corruption issues with the source from official...
[Nexus One Android Development] mtw4991:
I'm using 0517_1015 925 CFS 33.4...what is the difference in 0519_17xx 925 CFS? Didn't see a changelog..
[Nexus One Android Development] uberingram:
Because there isn't anything wrong with CM. Unless you're planning on actually contributing.
[Nexus One Android Development] b1337:
[highlight]Mod Edit: You were already warned once by Fallen Spartan about flaming. Temporarily Banned[/highlight]
[Nexus One Android Development] sir*mez:
STFU or contribute!! Make your own and stop *****ing about life!!
[Nexus One Android Development] Chahk:
What's this "we" ****? Speak for yourself there, buddy.
[Nexus One Android Development] D200P13:
i am getting lag/slow response from my nexus after going from the cyan default to this. is this common or a known issue?

how would i go about to switch back to the cyan kernal if i still have issues with this?
[Nexus One Android Development] schahr01:
Reflash the cm506 update.zip ?

Interesting sig - Does it work? Do people really just send you money? ;-)
[Nexus One Android Development] D200P13:
were can i get that update zip?

no hasnt worked yet haha.
[Nexus One Android Development] sir*mez:
Interesting!?!? How did you flash CyanogenMod if you don't know where his update.zip is? I hope you just had a brain fart, lol.
[Nexus One Android Development] D200P13:
i have never done an "update" of cyan. i went from stock to cyan but never updated cyan to cyan.
[Nexus One Android Development] wbknox:
do not use the set cpu widget, the active create lag.
[Nexus One Android Development] D200P13:
never messed with cpu. ill just continue to use it for a while and see what happens. will update maybe tomorrow to the newest version.
[Nexus One Android Development] mtw4991:
getting horrible battery life with latest 0517_1015-925mV CFS kernel. normal 1.2% standby drain overnight when on 3G or WiFi, but switching to Edge much more than usual at work (mainly when coming out of sleep mode) and not picking up calls while on Edge???

Any thoughts guys?
[Nexus One Android Development] whoa718:
Are you using cfs or bfs 800 or 925?
[Nexus One Android Development] hah2110:
Re: [.33.4 & .34]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/17/2010 07:59am

You get 1.2% total loss or per hour?

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] hah2110:
Re: [.33.4 & .34]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/17/2010 07:59am

And I'm still running off that charge!

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] WebghostDK:
Re: [.33.4 & .34]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/17/2010 07:59am

Wait, what? Hold your horses. I was asking you guys a question. Let me put it in another way:

What are the reason for so many kernels? Im having a hard time finding out which one of them i should use and what versions of them i should get.

No need to flame, i obviously just asked it the wrong way.

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] joeld79:
xda moderators=uber *******

* MOD EDIT *

Not this one. Banned for using a sock puppet acount to disrespect other members AND breaking forum rules after being banned as "[URL="http://xdaforums.com/modcp/user.php?do=viewuser&u=2303663"]b1337[/URL]".
[Nexus One Android Development] student.driver:
Sometimes you get the car you want, but you wish you could drop a more powerful, more efficient engine in there. Same-same.
[Nexus One Android Development] schahr01:
The N1 stock kernel and ROM serve their purpose for the general population but we (XDA community, kernel devs, etc) want/demand :) better battery life and more performance. All of the custom kernels here, not just intersectRavens (IR), kick the stock kernels ass. IR's kernel seems to be most active at this time on the stable .33.4 branch as well as the newer .34 (still some kinks to work out).
[Nexus One Android Development] sir*mez:
Try all of them out. Stay with what works! Trial and error. Every kernel has something different to differentiate eachother.
[Nexus One Android Development] hah2110:
Been going since Monday at 11pm, 21% left. I'll be charging up soon.
[Nexus One Android Development] mtw4991:
WOW! 44.75 hours and 21% left...incredible battery life considering the 2 calls and 5 texts you did:eek::D
[Nexus One Android Development] hah2110:
Ugh... Not sure where you got your math:

- About an hour of calls

- Over 125 e-mails received between Exchange and Gmail

- About 10 sent between Exchange and Gmail

- 3-4 app downloads and 8-10 updates

- About 20 minutes of browsing

- About five minutes of UStream broadcasting

- Over 100 SMS
[Nexus One Android Development] hah2110:
Update - battery meter is definitely inaccurate. I was at 19% and the warning box came up telling me to plug it in because it was at 0% and it just died. OS Monitor reports 83 mAh.
[Nexus One Android Development] mtw4991:
Just a joke dude, just a joke
[Nexus One Android Development] intersectRaven:
Finally got official 2.6.34-test1 to work! The YAFFS2 driver was the culprit! Rolling back to previous version fixed it. :D
[Nexus One Android Development] schahr01:
Does that mean the mount/unmount bug will be fixed in your next .34 build?
[Nexus One Android Development] intersectRaven:
I...honestly don't know... :D...I lost my USB cable so I've been downloading my own test kernels through the net wirelessly. :p
[Nexus One Android Development] schahr01:
You're resourceful :D

I'm sure we'll find out shortly after you release it...
[Nexus One Android Development] intersectRaven:
.34 Update!

20100520_10XX_.34:

- latest .34 kernel using wakelocks from the Official Android Repositories

- with HAVS, KANGMEM, capacitative buttons fix, no audio boost, and BFS (marked)

20100520_1048_.34:

BFS:

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

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

CFS:

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

800mV -> http://www.mediafire.com/?wgtulj2rlg0
[Nexus One Android Development] D200P13:
sexy post. gotta touch put my fingers on this.
[Nexus One Android Development] D200P13:
ok sorry for this noob question but couldnt find it in the search and tons of posts here... what is cfs and bfs?
[Nexus One Android Development] halorin:
Touchscreen fix?
[Nexus One Android Development] gotwake424:
I know that this Kernel undervolts the CPU, is there any risk of damage using this kernel?

Also what one would you recommend?
[Nexus One Android Development] iVisionX01:
No danger, use 925mv for best battery life.
[Nexus One Android Development] arjay88:
what was wrong with audio boost.
[Nexus One Android Development] gotwake424:
Thanks for the quick reply, cause I really don't want to search how do I install it? and will it delete all my user data?

also the difference between BFS and CVS?

sorry just came over from WinMo its a whole different world
[Nexus One Android Development] meric04:
.34 925mv CFS Running with enom 1.8.1 - don't seem to have any USB issues.

So far so good...
[Nexus One Android Development] intersectRaven:
I haven't applied it yet. :p
[Nexus One Android Development] iVisionX01:
Your user data will be safe but I always do a nandroid backup just in case.
[Nexus One Android Development] gotwake424:
Thanks for the tip and im running cyanomod-newest so do I go with CVF or BFS?
[Nexus One Android Development] hah2110:
Wow now juice plotter says 54+ hours remaining from 95%... Jeebus
[Nexus One Android Development] x986123:
Does anyone else have the issue of the phone awaking by itself after pressing the power button? (Using this kernel?) I'm getting this and I am worried it's the phone!
[Nexus One Android Development] iVisionX01:
CFS for stability and BFS if you can run it without problems. I would try BFS first and if it doesn't work too well for you just use CFS. I believe CFS is what android uses normally.
[Nexus One Android Development] iVisionX01:
USB Mounting is working for me in 20100520_10XX_.34

Edit: Can't unmount though xD
[Nexus One Android Development] gotwake424:
You are a life saver, otherwise I would actually have to go look stuff up myself. Now that would suck!

So got my kernel how do I install this bad boy?
[Nexus One Android Development] iVisionX01:
ಠ_ಠ Instructions are in the first post.
[Nexus One Android Development] tsouza:
What is supposed to be fixed with this "capacitive button fix"? Because, at least with me, I still need to hit a very narrow upper part area... or is this fix related to another issue?

Cheers...
[Nexus One Android Development] ElenaAlasea:
Could someone please upload the latest version to another file server again? Mediafire is still blocked here in China :-(
[Nexus One Android Development] redraiderj:
If you cannot get across the GFW you'd better choose other kernel, buddy. intersectRaven posts his kernels so often, nobody want to upload EVERY delivery to another file server.
[Nexus One Android Development] ElenaAlasea:
@redraiderj:

Thanks for the advice, but seriously I asked this only once already around 2-3 weeks ago (and someone actually helped me then). So it's not really like I'm begging for an upload each day...

I understand if you don't (want to) have time to do it but there might be someone who hopefully does so this time as well :-)

The VPN I usually use blocks certain filehosting services (like Rapidshare, which is luckily still allowed here), but unfortunately MediaFire is one of the few that are blocked by both my VPN and the GFW of China.

Of course there are still other solutions, but they either cost money or are slow and error prone.