yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Gr8gorilla:
You can enable swap when you do the menu-config. It is disabled in most kernels because it uses your sd card for the swap so it can slow you down. Anyway it is either enabled under general or on the first page of the menu-config. I would guess that the answer is no.

Compcache is similar but it compresses the information in ram and decompresses it, (if my memory is working right) and also creates a sort of virtual memory. This is also usually disabled because of the high ram of the nexus. It is just not needed.
[Nexus One Android Development] kromem:
I was on King's Desire yesterday and from 9am to 6pm with moderate use (w/o BT and Wi-Fi on) I went down to only 76%, with about 1% drain per hour idle.

With Cyanogen 5.0.6 and latest IR kernel, I was seeing it drop much quicker. Finally took a look at my logcat and saw the Weather Widgets Pro kept popping in for a forecast update despite not being set for that. Removed it and killed the process, and seeing much improved drain so far, and a much clearer logcat.

What's weird is that the process didn't take up very much of the "what's draining your battery" display.

I get why hah2110 is being persistent - his results vary wildly from what others are reporting. I was in the same boat, but knew it wasn't my battery as desire was lasting amazingly well.

Kernels aren't everything.

P.S. Anyone else notice that the "display" in battery status on Stock/Cyanogen appears to be a much more significant drain than on Sense, despite overall drain being similar? But on Sense, Wi-Fi and BT seem to dran much more. I've found this very weird going between the two - I wish it would show absolute figures instead of relative percentages.
[Nexus One Android Development] sir*mez:
Swap/Compcache is not needed on the Nexus one. Have you read around lately?

Edit: Just read Gr8Gorilla's post up above. That basically clears up my reason why we don't need this.
[Nexus One Android Development] rp1783:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/20/2010 10:33pm

Anybody anybody?
[Nexus One Android Development] rjhay22:
Bro, scroll a few pages back.
[Nexus One Android Development] rp1783:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/20/2010 10:33pm

Maybe I'm an idiot. I'm on the xda app. I'm not seeing it.
[Nexus One Android Development] dictionary:
You'll just lose wifi, as you need to push that file over later.
[Nexus One Android Development] rp1783:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/20/2010 10:33pm

Thanks so much.
[Nexus One Android Development] cjacks519:
Also using the same kernel which I flashed last night (20100419_2044, CM 5.0.6). Previously used Pershoot's latest kernel. IR's kernel seems to be one of, if not the best kernel for me on battery life and stability.

Off the charger this morning at 5AM with 100%. My usage is almost identical to Jack_R1. Only difference is I never killed any task and I sent/received about 50 to 60 sms. By the time I got back home around 4PM (11hrs since unplugging from charger), I still had 72% battery! :D

With Pershoot's latest kernel I would normally be at roughly 50-55% with the exact same usage. How much of this difference could be the OC?

Great work IntersectRaven! But do me a huge favor and stop creating these damn things cuz I can't stop flashing them...lol ;) Just kidding. Keep it going!

P.S. There has to be some sort of class, or rehab, or something for people like myself who can't stop flashing stuff on their phone. :p
[Nexus One Android Development] Markdental:
Flashing the newest AVS from 4/20. Will report back...
[Nexus One Android Development] cjacks519:
Definitely let me know how that goes. I'm about to pull the trigger on the 4/20 myself even though the 4/19 is giving me the best performance to date.
[Nexus One Android Development] Markdental:
it has been very stable so far. As for battery's life, will need to give it some time.
[Nexus One Android Development] intersectRaven:
Woah! I just logged in at work and what do I find? A ton of discussion on battery life, spam and the like! Anyways, battery usage CAN and WILL vary between users. If you're in doubt, try a bunch of different kernels for a few days and compare battery life! Don't rely on people saying I lost .000001% in 1 minute or something since even if the setup's the same, the hardware and other factors aren't. Anyways, let's bring back this discussion to the stability and overall feedback with the kernel shall we? :cool:
[Nexus One Android Development] dictionary:
Will you release an OC kernel as well, even experimental? Flashing the latest version now. 2044 was great for me.
[Nexus One Android Development] slyydrr:
Quick question regarding the kernel! :)

The latest 4/20 release says: still the "hack" version since I can't seem to get it stable with the "clean" version

What is the "hack" referring to? I know the 4/19 release mentions it finally being true AVS but not knowing if it would be stable for everyone. Did the 4/20 release revert back to the 4/18 implementation?

Also, any way to determine what the current voltage being sent to the CPU is?

I just flashed the 4/20 build and it seemed to boot on first boot. I was expecting it to do a series of rolling restarts per something I read. This is the reason for me asking what the "hack" is. Thanks!
[Nexus One Android Development] intersectRaven:
Unfortunately, I really hate overclocking so I won't release that. If you want overclocking, go to Ivan's kernel since he's also doing AVS with his OC kernels. :p
[Nexus One Android Development] intersectRaven:
The "hack" pertains to the way by which I'm setting the voltage to the CPU. It uses a very "dirty" way of directly writing the voltage to the regulator instead of following the "clean" way of going through the regulator framework. The problem is going through the regulator framework seems to be what is causing the instability with AVS. As for a way to determine what the current voltage being sent to the CPU is, I don't know of any way unless I enable even more debug outputs which could already be detrimental in trying to read the kernel logs. :)
[Nexus One Android Development] bonkasnucca:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/20/2010 10:33pm

I saw someone mention that its not just the kernel that matters nd I just wanted to second that...making use of the profiles on setcpu has also helped me save a lot of battery.. when the screen is off I have clocked it down to 500 something nd around the same for Wen the battery is below 35% also using different governors for the scaling in certain situations helps..my point is wen using a great kernel like this tweaking setcpu properly can help u get every last drop out of it

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] slyydrr:
Okay, that's what I thought. Would there be any increase in battery life if the 4/19 release runs stably on a device in comparison to the battery life of the 4/20 release?

I'm just curious if the "clean" way is better on battery, essentially.

Also, thanks for you great work and your quick response. You sir, have earned a beer!
[Nexus One Android Development] intersectRaven:
I'm curious about it as well since there seems to be plenty of checks with using the regulator framework than by writing it directly. Right now though I can't get the regulator framework to work stably with AVS. :confused:
[Nexus One Android Development] adam18488:
been following this thread for a while now but i couldnt resist the urge any more so i flashed ur latest kernel. no problems so far...even though its been 15 minutes.

going to bed now but will post back first impressions after a day of use tmrw!!

nice work btw:cool:
[Nexus One Android Development] slyydrr:
Hmmm, I'd try to help if I could but I fear that this may be way over my head :( I haven't done any kernel-related coding and haven't touched C in quite some time. I've been engrossed in Java for the past few years.
[Nexus One Android Development] minooch:
could be wrong, but i thought the version you just downloaded is 1 version older than the current - would you like me to upload my boot.img anyway?

Just let me know
[Nexus One Android Development] rp1783:
No, thanks I'm home now. I actually have been switching between these kernels and kmobs daily. I think kmobs is working out for me best right now. Not to say that intersectRaven isn't doing amazing work. I have a feeling this is going to just keep getting better.
[Nexus One Android Development] minooch:
intersectRaven,

Cheers for your work, your latest version seem to be very stable (has been a few hours), it also fixes my problems with wifi that the previous version had (at least for me).

PS: before anyone asks, yes i checked the proxy settings & i pushed the correct bcm4329.ko. It would actually connect, but no data would transfer.

edit: I forgot to add, my phone also seems to be a little bit faster.

Cheers,

Minooch
[Nexus One Android Development] rp1783:
http://xdaforums.com/showthread.php?t=634587

This is the one I've been using, cause I don't really feel I need an overclocked kernel.
[Nexus One Android Development] crabnebula:
Happy to report that wifi is now working for me too. With the 0419 version over CyanogenMod 5.0.6 I was getting the reboot loop with a hidden SSID. That seems to be fixed. Thanks!

However I'm having another issue. I installed the latest wifi tether (pre10) and although everything seems fine on the Nexus, my laptop won't connect to it. Windows says that the network is taking longer than usual to respond. Perhaps completely unrelated...
[Nexus One Android Development] intersectRaven:
Just read this. I like! :p
[Nexus One Android Development] Wysie:
Do you use Twitter by the way? :) Also, have you considered adding what pershoot adds in for his "xtra" kernel? I don't play much games, but from what I read in the thread the "xtra" seems to really help with 3D games :)!
[Nexus One Android Development] intersectRaven:
You mean the msm 3d driver? I already have it in if that's what you mean. :)

*Forgot to mention my twitter account is the same as my username here. :)
[Nexus One Android Development] xCALLmeKING:
I've been trying out different kernels over the past few days. Sorry if this has been asked already...I am just curious if this can be installed via recovery > update.zip. Thanks in advance.
[Nexus One Android Development] intersectRaven:
No it cannot. This requires fastboot. I am considering it but I don't know how to create an update.zip. :confused:
[Nexus One Android Development] xCALLmeKING:
Thanks for the quick response, I guess i'll take the plunge and try via adb / fastboot. Just a little nervous about straying from what's familiar to me, but did manage to install Amon_RA's recovery via fastboot.
[Nexus One Android Development] rp1783:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/20/2010 10:33pm

I can probably help you out. Won't be til late tomorrow though.
[Nexus One Android Development] pershoot:
This is assuming your using Windows (XP/2000/2K3/Vista/7):

1. unpack this http://www.relentlessaddictions.com/Androidstuff/signing.zip to tools directory within your sdk folder.

2. run autosign.bat and go number by number

From Linux:

3. unpack this: http://android-dls.com/files/linux/split_bootimg.zip

4. take a boot.img from let's say, cyanogenmod rom

5. ./split_bootimg.pl boot.img

6. If you would like to modify anything in the ramdisk:

mkdir my_ramdisk

cd my_ramdisk

gzip -dc ../boot.img-ramdisk.gz | cpio -i

To pack back together:

cd ..

mkbootfs ./ramdisk | gzip > my_ramdisk.gz

Note: you can find mkbootfs in AOSP: out/host/linux-x86/bin

7. use mkbootimg (found within AOSP: out/host/linux-x86/bin (assuming your using an x86 linux host)) to create a nexus image, contained of your zImage and a ramdisk:

mkbootimg --base 20000000 --cmdline 'no_console_suspend=1 console=null' --kernel arch/arm/boot/zImage --ramdisk boot.img-ramdisk.gz -o my_bootable_file.img

From Windows:

8. take one of my bootable recovery update.zips (http://droidbasement.com/db-blog/?p=161)

9. replace your my_bootable_file.img with the boot.img found within the .zip

10. replace your modules folder and wifi module in the modules folder

11. feel free to amend the update-script found within META-INF\com\google\android (you can use this as a reference: http://xdaforums.com/showthread.php?t=641223)

12. if you setup autosigning correctly, you can now right click the .zip -> sign.

Note: on windows 7, the right click gets damaged, so to speak, if you reassign the extension after autosigning, so just open up a command prompt and: java testsign my_recovery_update.zip

13. your all done.

To sign updates in Linux:

Follow this: http://xdaforums.com/showpost.php?p=4155081&postcount=1

-pershoot
[Nexus One Android Development] intersectRaven:
Ooooh...thanks for compiling it all in one post! I already found how to do it but only partially and haven't had the time to search around for the missing options. :p
[Nexus One Android Development] christiankk:
latest and greatest kernel works like a charm for me! cheers :D
[Nexus One Android Development] S_Dot:
Anyone using this kernel on Cyanogen latest? How is the battery life???
[Nexus One Android Development] bewA:
I'm liking this kernel :)

The main reason why i tried this one over others was that I wasn't bothered about any of the OC stuff, I just want to improve battery life :)

It's improved over my iPhone 3GS which i'm happy about anyway :)

Battery life is a little improved, i've got my setcpu governor set to conservative now.

however I have dropped 4% in an hour and 40mins of that was me driving to work with the phone in my pocket.

Is there a way I can double check this is working?

I notice some people outputting their logcat.

I've not had any reboots at all in the last 2-3days of me running this kernel :)
[Nexus One Android Development] rjhay22:
Wahaha! It works well on Cyans ROM too :-p It actually lasts a whole day now with moderate use.
[Nexus One Android Development] wildmonks:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/20/2010 10:33pm

Raven, just wanted to thank you for updating your github. I'm now enjoying what appears to be a stable AVS @ 800mV with OC. Great work raven :D
[Nexus One Android Development] intersectRaven:
Updated!

- same file as last version except it's now in update.zip format (flashable from recovery...thanks pershoot!!!) :D

Here's the link:

http://www.mediafire.com/?qmmjtmtzymv
[Nexus One Android Development] Docmjldds:
Guess I be the first to try, with my issues of charging. Initial boot took a little long, but so far no problems and am charging :D
[Nexus One Android Development] jblazea50:
Raven, is the kernel from 20100420_2217 your latest one?

i see you made an update.zip, but that's the same kernel as from April 20 at 2217?

thanks
[Nexus One Android Development] intersectRaven:
Yes, they're the same. The April 21'st version is just a repack to update.zip format. :)
[Nexus One Android Development] die-hard:
pls continue to put zimage and .ko, because with .zip my desire camera not work
[Nexus One Android Development] myplague:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/21/2010 09:47pm

Is it possible for you to add your kernel to Rom Manager like Kmobs has done with his latest?
[Nexus One Android Development] Docmjldds:
I can confirm this to. FC after taking pix :(
[Nexus One Android Development] intersectRaven:
Updated!

Hybrid AVS:

http://www.mediafire.com/?zzlwmhnotfw -> ZIP format

http://www.mediafire.com/?kjjjhzyzok3 -> Update.zip format
[Nexus One Android Development] Docmjldds:
Reflashing doesn't fix the FC's :( Guess I run a Nandroid restore unless you can offer alternative
[Nexus One Android Development] intersectRaven:
I believe this is because the update.zip you flashed before replaced the boot.img of your phone with something incompatible with the desire camera. Flash the desire camera boot.img first then flash the zImage on top of it. That should work for you. :)
[Nexus One Android Development] dictionary:
The alternative is probably just flashing the zImage and .ko file manually, like you did before (if you're on a Cyanogen rom at least)

Intersect beat me to it, lol
[Nexus One Android Development] Docmjldds:
Since I used the kitchen Baked ROM which has the camera image built in, I can see using WinRar the camera image file inside of the Kitchen rom, so I assume flashing THAT specific image file is what you mean.
[Nexus One Android Development] Wysie:
LOL at the change log! ;p
[Nexus One Android Development] Docmjldds:
I am on 5.0.5.3-N1 Kitchen Baked and no, just reflashing the original zimage and pushing the ko file didn't fix. I am going to try Raven's last to me.
[Nexus One Android Development] pershoot:
flash your rom + gapps, then flash the camera, then fastboot flash intersects zimage and push the wifi module in place.

youll be set.
[Nexus One Android Development] dictionary:
Since the camera is broken now, you'll have to install the camera again, THEN fastboot flash the zImage and adb push the .ko

This time pershoot beat me to it, lol. frig man.

edit 2
[Nexus One Android Development] Docmjldds:
Yeah. That's what I am doing as I type. Got a sig failure just trying to flash the boot img file inside of the kitchen ROM for the camera. Already installed the Kitchen ROM, so gapps not needed. Camera works fine. Just have to push the ko now and flash zimage and will be back to normal.

Edit...fixed. Thanks :)
[Nexus One Android Development] seanowns:
IntersectRaven:

Now that this is stable any chance you will considering supporting it on Rom Manager? Would make it very easy to stay up to date with your latest material.

Anyways, just a thought. I will totally understand any apprehension.

*update* I see you created update.zip, so this is 1 of the roadblocks! Would love it if you also included that with Rom Manger. Thx
[Nexus One Android Development] Docmjldds:
Update zip method wonked the desire camera on mine as well as one other user, so not sure I would go that route. Just my 2c. Ended up basically reflashing ROM and kernel and all is well. Manually installed a few custom theme stff just now to get back to where I was.
[Nexus One Android Development] dictionary:
Just a FYI, as of now, all of the update.zip/flashAkernelTheEasyway.zip files will break the desire cam. We'll have to see about this when Paul gets back.
[Nexus One Android Development] Docmjldds:
Thanks. I don't mind the old tried and true method. Kind of surprised that an update.zip method would be offered anyways, based on the comments about making it too easy for users just randomly installing files without basic knowledge on what if scenarios, such as what happened :rolleyes:
[Nexus One Android Development] sstang2006:
loving this Kernel. fast charging slow discharging. what else can you ask for. Thanks for a great work.
[Nexus One Android Development] FettsVett:
can someone please post a mirror to the file, I'm unable to successfully download the update.zip from mediafire.
[Nexus One Android Development] sstang2006:
Here you go 2.6.33_AVS-80...37_Update.zip
[Nexus One Android Development] FettsVett:
Many thanks!
[Nexus One Android Development] pzumk:
latest (not the very latest with the nonsense update) AVS kernel is working great so far! No reboot since you released it, everything working fine just like with PsyQ's and Pershoot but I actually didnt notice more batterylife. Will test it until sunday and decide which kernel to use for 2 weeks since I wont be able to install a new kernel during the next 2 weeks.
[Nexus One Android Development] vegetaleb:
I am using the 850mv but I barelly notice a difference with original Enomther kernel in battery use
[Nexus One Android Development] hah2110:
+1..........
[Nexus One Android Development] mtw4991:
Ok, had CM 5.0.6-N1 stable and just added Intersect's kernel with Desire camera manually and I'm having ZERO problems so far with anything. CM's5.0.6 (no wipe using CM Updater) wiped my Desire camera also. I'm kinda a noobie also, so I read the whole thread and this is what I did for those who might be new also and hesitating:

Power off, boot into bootloader, then recovery. Wipe cache & battery stats.

Reboot

Power off, boot into bootloader, then recovery. Flash Desire.zip from SD card

Reboot, check/test Desire camera. Working fine.

Mount SD card, enable USB debugging, open Windows Command prompt

type cd\ then hit enter

type cd\android-sdk-windows\tools then hit enter

type adb devices device should be recoginized and number shown

type adb remount then hit enter and it should say remount succeeded

type adb push 2.6.33_avs-800mv\bcm4329.ko /system/lib/modules hit enter

(it takes a second, but it will read/write? and tell you OKAY twice)

type adb reboot bootloader then hit enter

(wait for phone to boot into the bootloader...android on skateboards)

type fastboot flash zimage 2.6.33_avs-800mv\zImage then hit enter

type fastboot reboot then hit enter

Reboot only took a little longer than normal and everything seems to be working great. No reboots, desire camera is fine. Life is good.

My only concern is that my SetCPU doesn't show anything above 998mhz and I don't know how to enable oc'ing and uv'ing. Where do I go? LMAO. :D I got this great kernel by the horns and don't have a clue what to do with it...:confused: Thanks for the help:o
[Nexus One Android Development] masse1369:
This kernel isn't OC'd...
[Nexus One Android Development] jblazea50:
SetCPU won't show anything above 998mhz because this kernel ISN'T overclocked
[Nexus One Android Development] mtw4991:
Thanks, I wasn't sure of that to be honest, lol. Is the undervolting only done through SetCPU? If so, what are the values for the CPU Governor:

Conservative: ?

Ondemand: ?

Powersave: ?

Userspace: ? (what the heck is this anyway??)

Performance: ?

If SetCPU doesn't change the mV parameters, how do you change them?
[Nexus One Android Development] b1337:
read the OP carefully.......
[Nexus One Android Development] myplague:
Conservative - gradually increases clock speed

ondemand - changes clock speed quick as soon as needed

powersave - runs at 245 only

userspace - ?

performance - runs at max

AVS changes the mV automatically.
[Nexus One Android Development] Docmjldds:
I have to say this is the best battery times for me. I went out jogging today for one hour. Timed with a cardio program using GPS as well as listening to btunes blasting away on my monster turbine ear buds. I usually eat up 12-15% of battery during this particular workout. Today, I used 4% during that time. I am using SetCPU governor set for conservative, and NO profiles. When I leave the phone in sleep mode, it typically drains just slightly over 1%/hr on average. The only caveat is I am using an aftermarket Seidio 1600mAh battery, so in theory I will/should see approx 13-14% increase in times, considering stock battery is 1400mAh.