yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Treatcon:
Same here.
[Nexus One Android Development] erikclaw:
Luckily I had TB and nandroid back up or it would have been a long day.
[Nexus One Android Development] sietepasosalsol:
Maybe full wipe before flashing will fix it..
[Nexus One Android Development] intersectRaven:
I think I know the problem. Can anyone see a PMEM error in logcat before it restarts?
[Nexus One Android Development] Arrqh:
Here's what I see when I go to voice search...

Logcat: http://pastebin.com/xSFtCumm

kmsg: http://pastebin.com/cnxQb5vd
[Nexus One Android Development] intersectRaven:
AVS Kernels updated with the Voice Search fix! :)
[Nexus One Android Development] Arrqh:
Works fine over here now! :)
[Nexus One Android Development] intersectRaven:
Good to hear. Now that that's over, I can go back to my next kernel attempt. :)
[Nexus One Android Development] kgp700:
working perfactly a2sd+ and voice recorder!!

thanks:)

please update 7/7/2011 kernel source on your github
[Nexus One Android Development] momomok:
The latest update is working good. Thanks!

Any big surprise in the next build? :P
[Nexus One Android Development] erikclaw:
I just flashed latest, and no problems. Don't know what happened earlier.
[Nexus One Android Development] intersectRaven:
If I posted it here it wouldn't be a surprise right? :p
[Nexus One Android Development] momomok:
Nice point... but my PM inbox is always open :P
[Nexus One Android Development] pen²:
Got strange results with latest AVS Kernel (7/7/2011, CM7, Normal Boost).

I am using fit's build from 07062011, and I don't have haptic feedback for the buttons.

After I flashed latest IR Kernel, everything seemed fine, but when I put my phone into the car dock (triggering Car Mode, Bluetooth connection to hands free, etc), it rebooted. After this reboot (not sure if it was there before), I had haptic feedback and when I pressed the "power" buitton, there was no audio profile, no flight mode, no profile chooser, just restart, shutdown and (I believe) screenshot.

Due to these weird things, I restored my nandroid backup :|
[Nexus One Android Development] ch33kybutt:
Next time weird things happen, get logcat and dmesg first, then nandroid. Then we can help to un-weirdify.
[Nexus One Android Development] pen²:
Yup, I know - forgot to get a logcat but was in a hurry to go to work and wanted to check some mails, so there was too little time.

I just thought I could at least share the observations I remember - maybe it is at least any help...
[Nexus One Android Development] momomok:
Mind sharing how to do this?

Hook it up and key in command in ADB shell?
[Nexus One Android Development] ch33kybutt:
http://wiki.cyanogenmod.com/wiki/Logcat

For kernel/driver messages, just replace "logcat" with "dmesg". Or if it's there, pull /proc/last_kmsg

And don't paste the logfiles here directly (those using XDA app or Tapatalk won't appreciate getting scroll-thumb), but use http://pastebin.com and post the links here.
[Nexus One Android Development] pen²:
For logcat, you can use apps like "alogcat", too. Most of them allow sending the log by mail so you can view and edit the log on your computer
[Nexus One Android Development] momomok:
I know alogcat. But how to grab the log if my device keeps rebooting?
[Nexus One Android Development] wind0zer:
FYI I was on kernel 2.6.38.8_AVS-CM7_CFS_20110706_0918.zip yesterday and my phone rebooted when I pressed "Listen" button after launching Soundhound app. Then I repeated the same mistake like 4-5 times after each reboot. : P Didn't get a logcat.

Anyway good to know it's fixed. Such strange issues! ; )
[Nexus One Android Development] wbknox:
can someone check out the new kernel 2.6.38.8_AVS-CM7_CFS_20110710_2105.zip,gave a blue screen also

would sleep and would not wake up.
[Nexus One Android Development] intersectRaven:
That version is unstable which is why I didn't announce it. Would've deleted it earlier if it wasn't too late in the evening already. :p
[Nexus One Android Development] wbknox:
ok kewl i was late to the party.
[Nexus One Android Development] lojden:
Hm, it works fine for me :)
[Nexus One Android Development] intersectRaven:
That's odd. The changes in there almost always assure a kernel oops. :/
[Nexus One Android Development] intersectRaven:
Updated with Ivan's compiler optimization idea. :)
[Nexus One Android Development] d.cortez:
forgive my redundant question, but, does the 20100329_2221 release include the volume modifications from rotohammer (e.g., release 20100328_1953)? you know how we are: always wanting to try/use the latest release seeking the optimum, ulitimate, spectacular device performance that somehow always evades us! :) thanks!!
[Nexus One Android Development] intersectRaven:
I understand your concern. That's the primary reason why I started compiling my own kernel...to always have the latest! :p As to your question, it has the volume modifications but based on pershoot's values. :)
[Nexus One Android Development] h11g:
used your kernel and i have to say i love it~! In-Call volume is awesome now. The phone seems to be running at a lower temperature now. And while charging the phone it doesn't heat up so badly. My only wish is for the phone's speaker volume to be louder.
[Nexus One Android Development] sir*mez:
liking this kernel, so far. will test for the day and see what i get for powersave.
[Nexus One Android Development] h11g:
Do we need to install setcpu to enable the powersave function?
[Nexus One Android Development] d.cortez:
ok, thanks. if i recall, his values are somewhat lower than rotohoammer's so i'll stick with what i have.
[Nexus One Android Development] Gilg@mesh:
my wifi doesn't work with this kernel, I have flashed the zimage and pushed the 4329.ko but still can't turn on wifi...
[Nexus One Android Development] www1:
try to repush wifi.

In first i can't mount it but after all works perfect by repushing it
[Nexus One Android Development] Gilg@mesh:
hmm, I don't understand "adb remount" I have use the recovery to push the file, but maybe thats wrong? and I have also used zip file to flash the .ko file (before), but I don't understand "adb remount" and then push it... :/
[Nexus One Android Development] fabioccoelho:
The steps:

1º adb remount

2º adb push bcm4329.ko /system/lib/modules

3º adb reboot bootloader

4º fastboot flash zimage zImage

5º fastboot reboot

Enjoy ;)
[Nexus One Android Development] Noel3903:
YEah so im at work the next 12 hours and was wanting to put this badboy on my cm rom, but i cannot install drivers on work comp to do so =(...i know soso sad =(... so if anyone with sparetime could upload a ...update.zip to this badboy i can DL it strait to my phone...Cheers..ps if not no worries its just 12 hours =( soso sad lol
[Nexus One Android Development] intersectRaven:
Don't be in recovery when you push the file. I don't know why but it just doesn't work when done while in recovery. :)
[Nexus One Android Development] britoso:
Did you test this scientifically, or just what you feel ?
[Nexus One Android Development] evidenc3:
This is likely because in recovery only a couple filesystems are mounted. You can push in recovery you just need to do 'mount /system' or 'mount -a' before you push. I play it safe and umount also before reboot, but you should be fine either way.

Also someone is bound to ask, compared to persiansown's underclocked kernel, what is the difference here? He uses kmobs for volatge also so that should match, but you have the volume hack and also some mods that made the kern a bit bigger but hopefully faster? His also mentions 'This kernel has my button fix (capacitive buttons can now be pressed more accurately)'. Sharing that or have a similar patch by chance? Just being bold and trying to get a best of everything kernel as I like the additional features of yours :) Keep up the good work.

Edit: Also just saw Ivan's Diet kernel heh.. your two are pretty similar?
[Nexus One Android Development] intersectRaven:
None taken! ;) Anyways, its hard to find out why this is so. Use what works so I say! :)

I see. Thanks for the heads up! :D Ivan I think didn't modify the default power governor while mine defaults it to conservative. Also, his has the ondemand governor while I stripped it off mine. I don't think my .32 kernel has the button fix since it's taken straight from AOSP sources (unless someone points me to the modified file! :p) but I'm not sure about the .33 although if Cyan already integrated it on his kernel source it should be present here as well. :)
[Nexus One Android Development] intersectRaven:
Updated! ;)
[Nexus One Android Development] zitseng:
When in recovery, the usual /system is not mounted as /system, so anything you push actually ends up in the wrong place.
[Nexus One Android Development] intersectRaven:
Final update for awhile! (unless I get really bored or something new is committed on cyan's or android repositories) :P
[Nexus One Android Development] britoso:
If youre bored how about creating a boot.img for me with one line modified in '/init.rc' :)

export ANDROID_BOOTLOGO 0

Just guessing (and hoping) I can view the console logs scroll past as it boots.
[Nexus One Android Development] apacheo:
Having a cap on voltage would be pretty cool. What would be even better is if these settings were dynamically changeable by writing a value to the proc filesystem... e.g. /proc/minvoltage and /proc/maxvoltage ... but that's getting into fairly advanced kernel tinkering ;)

My workaround worked perfectly - got the (second most recent) 825mv kernel on CM5.0.6test3 and its a beautiful thing :D
[Nexus One Android Development] intersectRaven:
Good for you! :)
[Nexus One Android Development] paulk_:
Just thought that since most of the battery drain will come from actual usage of the phone, and usage of the phone means that AVS will probably scale the voltage up to max, having a cap on that max should save quite a bit of power.

This could a point where non-AVS actually has an advantage over AVS due to it using less voltage while the user is using the phone for intensive tasks.

Think some people have reported instabilities with non-AVS kernels such as pershoot's though..
[Nexus One Android Development] intersectRaven:
I'll just set it to the max voltage as defined in my non-AVS kernels. This should be fine since those are from kmobs. :)
[Nexus One Android Development] hah2110:
I hate to say it... But I am seeing a slight improvement using the Diet UV AVS kernel. I wonder how much difference will be made if you [Intersect] try and help with non-standby usage. I see huge gains using AVS (both your kernel and the Diet) in standby, but just picking up the phone to make a call could drain 5% in <10 minutes which is what really bites.
[Nexus One Android Development] paulk_:
That sounds great! Perhaps you could release test copies with different maximum voltages to let people test for you, in order to get the maximum possible benefits with the least amount of time spent testing for you :P
[Nexus One Android Development] intersectRaven:
Hmmm...but if I do that, I'll have to release too many kernels... even with my automation script that seems too many to manage for my MediaFire folder. :p
[Nexus One Android Development] paulk_:
True, though I think eventually if you have any time on your hands, people who can use the AVS 800 might benefit from an even lower maximum.

Eagerly awaiting your new capped AVS kernels!
[Nexus One Android Development] intersectRaven:
Currently compiling AVS with maximum voltage capped at 1225 which is the maximum for my non-AVS ones with the exception of the 1000mV one which will retain its default 1275 max. I'll try and upload after lunch. ;)
[Nexus One Android Development] paulk_:
Sweet! I just came back from lunch lol
[Nexus One Android Development] lore2486:
lol i was just about to ask you to make something liek this, can you make a 850mv capped at maybe 950 or 1000 (what ever the UV kernels run)?

edit: just read a couple of post back and realize you are gonna do something similar :D
[Nexus One Android Development] paulk_:
Hmm.. Do you mean that you're capping the voltage at 1225 for all CPU speeds? If I'm not wrong the voltage for non-AVS is usually capped at different levels for different CPU speeds
[Nexus One Android Development] intersectRaven:
Yes it is but it's not actually a cap. With non-AVS, the voltage is specified for the voltage so there is no adjustment. Here we're just going to have AVS top at 1225 for all speeds IF the CPU demands it. It should undervolt automatically for the lower clock speeds. :)
[Nexus One Android Development] S_Dot:
Can someone teach me how to install this, and what this about wifi not working? anyone?
[Nexus One Android Development] britoso:
On CM 5.0.6 N1 test3, got a reboot with the 850 so I'm back on 875. (4/14/10 10am kernel)
[Nexus One Android Development] paulk_:
Wouldn't it be better, battery wise, if the voltages for CPU speeds all followed the non-AVS version?

Sorry if I sound like I'm hounding you lol
[Nexus One Android Development] paulk_:
Installation instructions are on the first page.

If the wifi isn't working it's probably because someone didn't push the bcm4329.ko properly.
[Nexus One Android Development] intersectRaven:
From my understanding of AVS, it does initially follow the SVS (Static Voltage Scaling). Only when the CPU complains about the voltage does AVS make the adjustments to the voltage being delivered. :)

*Hmmm...now that I think of it, it should be possible. I'll try to look at it when I get home. Work is quite busy at the moment unlike last week. :)
[Nexus One Android Development] intersectRaven:
I have finished uploading the AVS kernels that have the maximum voltage set at 1225. You can find them on my MediaFire folder. :)
[Nexus One Android Development] paulk_:
Ouch I know the feeling, was frantically fixing all the bugs to meet the deadline this morning. Hope your workload lessens!
[Nexus One Android Development] momomok:
Just tried the latest kernel. My N1 would stuck at the X logo.

Have to revert back to the previous build.

I will try it again tonight after work, and if that fails again, I will grab the last_kmsg to help debugging. :)
[Nexus One Android Development] intersectRaven:
Ok. Should be an AVS quirk since the changes I made don't affect that phase of the bootup. :)
[Nexus One Android Development] wbknox:
boot ok works fine so far.
[Nexus One Android Development] intersectRaven:
Good to hear. I'm thinking of applying what I learned in modifying the governor to AVS' algorithm to make it more responsive in adjusting voltages. I'm thinking that maybe the odd occurrences could be minimized if AVS reacts even more quickly. :)
[Nexus One Android Development] fcisco13:
Work your magic bro. great job by the way what governor do you use in your phone?

MEXICO U-17 WC CHAMPIONS!!
[Nexus One Android Development] intersectRaven:
I use smartass which is why that's the focus of this recent improvement. I find that setting the base processing speed to 128Mhz causes it to ramp-up painfully slow so I thought of how to speed it up and make it more responsive. :)
[Nexus One Android Development] momomok:
So... there is something wrong with my settings?
[Nexus One Android Development] intersectRaven:
Nope. Just a quirk. Sometimes it works sometimes throws a tantrum. :D
[Nexus One Android Development] sir*mez:
Smartass gov' is extremely lagging now. It was fine before this update. My settings are smartass 245 to 998 on avs kernel. If I use any other gov' the performance returns.

Edit: Scratch that, all gov's were lagging. I reverted to 070711. Everything is fine now. Damn I want to be part of the cool crowd and have the latest, lol. :-(
[Nexus One Android Development] momomok:
Ha. Let me try it again tonight :)

Hope my luck will improve this time.. :P
[Nexus One Android Development] momomok:
Now working fine. Thanks!

Now trying the IR-enhanced Smartass...
[Nexus One Android Development] intersectRaven:
I've uploaded enhanced AVS test kernels for testing. (hence the TEST) ;)

AVS has been modified with what I learned while modifying the governor:

- realtime threads are now used for trying to change voltages

Hopefully this will increase AVS sensitivity thus increasing stability. :)
[Nexus One Android Development] noisemonkey:
Data corruption problems on the latest one again
[Nexus One Android Development] fcisco13:
Ill start testing now! Thanx IR

MEXICO U-17 WC CHAMPIONS!!
[Nexus One Android Development] fcisco13:
@128 with smartass it takes 2-3 track ball presses to wake phone.

MEXICO U-17 WC CHAMPIONS!!
[Nexus One Android Development] intersectRaven:
I think that's usual for smartass at 128 Mhz since I experienced that before usually when I let my phone sleep. :)
[Nexus One Android Development] sir*mez:
Test and 071311 kernel extremely lag for me. I had to revert to 070711 kernel just to write this cause keyboard wasn't cooperating cause of the lag. Hope to see more feedback from more people cause I want to see if I'm alone.
[Nexus One Android Development] harmohn:
Running TEST 2.6.38.8_AVS-CM7_CFS with CM-nightly-129; absolutely fine for me.
[Nexus One Android Development] momomok:
so now I'm flashing the latest TEST kernel...

and... after a long X logo

it boots! :D

anyway, IR any plan to make SmartAss a bit more responsive?

sometimes it just rise the frequency too slowly...
[Nexus One Android Development] intersectRaven:
Try changing the value in /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_up_speed to 128000. I think this should solve the issue. :)
[Nexus One Android Development] schizophrenia:
i am on the latest version and it feels snappy..
[Nexus One Android Development] momomok:
yup. when i wrote the last post, i was still judging from the old SmartAss

the one in test kernel is awesome :)
[Nexus One Android Development] schizophrenia:
the one i tried is not the test one yet.

is the test one even better?
[Nexus One Android Development] momomok:
Yes. I can feel it being more responsive when the CPU load increases.

Rapid response = fewer lag
[Nexus One Android Development] Booker-T:
Will there be some 1.3Ghz kernel?:)
[Nexus One Android Development] phewizzo:
Test kernel is very snappy!!
[Nexus One Android Development] intersectRaven:
I would like to reiterate that the TEST kernels only improve the AVS code so that hopefully those that have problems running the non-TEST kernels could maybe enable AVS now. :)
[Nexus One Android Development] puttytatko:
The whole AVS code is tweaked or just the smartass governor ??? I use mostly ondemand governor so will that changes affect ondemand???
[Nexus One Android Development] intersectRaven:
The TEST kernels have the smartass modifications with the AVS code tweak. If you use the ondemand governor and use the normal kernels then there's no changes that benefit you. :)
[Nexus One Android Development] sir*mez:
I caught this last_kmsg after my phone froze on the test kernel, I couldn't get the logcat. Hope this is sufficient:

http://pastebin.com/ChQWbVqZ
[Nexus One Android Development] intersectRaven:
I think that's the recovery's kmsg since it uses CFQ and also has no mention of AVS. Maybe you booted into recovery, restarted then took the last_kmsg which would result in the last_kmsg being the kmsg of recovery? :confused:
[Nexus One Android Development] sir*mez:
Doh, lmao, yes I did reboot into recovery twice, please don't ask why!?!?!?!
[Nexus One Android Development] sir*mez:
OK, it happened again. Heres the last_kmsg it wouldnt let me get the logcat, I had to do a 3 button reboot:

http://pastebin.com/xfCCYgW7

Edit:

I tried to change the ramp_up_step with root explorer and the phone hung/froze:

logcat: http://pastebin.com/fpu4Bqjk

last_kmsg: http://pastebin.com/3AHSwkVR
[Nexus One Android Development] intersectRaven:
I see. There's no outright errors though...just that the kernel couldn't sync with the keyboard??? Oh well... :rolleyes:
[Nexus One Android Development] intersectRaven:
I think I solved the sync error. Please get the latest TEST kernel I'm uploading currently. :)
[Nexus One Android Development] momomok:
Opera Mobile always hanged when using the 1st Test Kernel

now it is fine running with 2nd Test Kernel

thanks!
[Nexus One Android Development] Treatcon:
2nd Test Kernel is running pretty smooth. No problems at all so far.
[Nexus One Android Development] sir*mez:
5 times I tried writing this statement on my phone, 5 times I would press backspace because of an error I made and my keyboard would have a mind of its own. It would delete the whole comment on its own. I had to get on my pc just to write this because how unresponsive my keyboard is. Test 2 feels less laggy while browsing the web and swiping through the home screen but still lags a lot while swiping up/down the 3d/4d app drawer.
[Nexus One Android Development] fcisco13:
Mine rebooted twice while plugged in charger and trying to use Netflix and another while plugged and listening to I'd radio + tapatalk, phone feels hot too.. using test 2

MEXICO U-17 WC CHAMPIONS!!
[Nexus One Android Development] intersectRaven:
It's interesting to hear varied results for the test kernels. I'm wondering if some native apps use real-time threads that are competing with the ones I just introduced. sirmez, is the latest non-TEST kernel as laggy for you as well?
[Nexus One Android Development] phewizzo:
Test kernel #2 is still very snappy for me.
[Nexus One Android Development] sir*mez:
Its not as laggy like the first. It is more responsive. But it lags only on certain parts of the UI eg. App drawer. If I change smartass governor to conservative all lag disappears everywhere and my keyboard works normal again.
[Nexus One Android Development] noisemonkey:
Yay no data corruption on test 2. Smart ass and savaged zen are laggy but interactive x on down are fine
[Nexus One Android Development] intersectRaven:
Good to hear. Seems that AVS is improved by the realtime thread while the governor isn't. Will release a 3rd TEST kernel to validate. :)
[Nexus One Android Development] intersectRaven:
3rd TEST kernel uploaded! I restored smartass to use workqueues instead of real-time threads. Hopefully, lag for smartass is back to normal. This would just test then whether AVS stability is increased. :)
[Nexus One Android Development] noisemonkey:
No lag with smart ass but data corruption is back
[Nexus One Android Development] intersectRaven:
I'm really convinced this time that it's not a kernel problem. It's too random that tweaking anything doesn't seem to improve it. Anyways, AVS stability test comments are still go. :)
[Nexus One Android Development] wbknox:
i have not notice any problems with 3rd test smart ass is fast and stable for me.
[Nexus One Android Development] noisemonkey:
I'm only using nightlies so maybe it's something to do with them
[Nexus One Android Development] intersectRaven:
I'm thinking hardware though since I compile my own optimized nightlies and have no problems. Are you using A2SD by chance? It could be that since there have been reports before about data corruption with it. :confused:
[Nexus One Android Development] noisemonkey:
Nah I got rid of that as it was making the phone really unstable
[Nexus One Android Development] sir*mez:
Test 3 has everything back to normal.
[Nexus One Android Development] intersectRaven:
Good to hear. Now I'm only waiting for those who can't flash AVS stably before. :p
[Nexus One Android Development] Treatcon:
Just flashed 2.6.38.8_AVS-CM7_CFS_20110715_0938.zip and my phone boot loops. On the second boot loop the screen turns off with the tv off animation. I have to perform the 3 finger salute to get it to do anything. Didn't catch a log since I'm at work.

Re-flashed 2.6.38.8_AVS-CM7_CFS_20110714_1420.zip and all is back to normal. This kernel set has actually been the best for me so I'll just stay with it for a while :)
[Nexus One Android Development] intersectRaven:
Ok. I'll release a 4th TEST kernel for that. (hopefully this is the last) :)
[Nexus One Android Development] intersectRaven:
I've uploaded the 4th TEST kernel for AVS. Hopefully this is the last. :)
[Nexus One Android Development] sir*mez:
I like test 4 the best out of all of them, so far I haven't found anything wrong.
[Nexus One Android Development] noisemonkey:
All ok on test four avs