yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] waylo:
Ahh, finally found the right thread for this. Having identical symptoms like the users posting above.

I was actually using Wildmonks' kernels, which are of course completely based on this kernel. Happened using 2.6.34 and 34.1 versions of 800mv BFS and CFS, as well as 925 CFS. The first group I was using was based on 7/1/10 build.

SetCPU is set from 245 to 998 while awake. The only profile I have is a "screen off" 245min ?500 or so max. Unclear if this has an effect on what the touchscreen does when attempting to wake up.

I finally changed over to Pershoot's kernels for now, where I haven't had this happen (only been a few days though). I'm on 5.0.8, and I had thought it was only on that ROM, but it's interesting to see that it's also happening on some Froyo.

Pretty sure I did not have wifi or BT on when these freezes occurred.
[Nexus One Android Development] Pochemuchka1977:
To all who has unresponsive screen problem. Several days ago I have opened a bug on CM project and today I got the response for this bug:

Comment 2 by steve.kondik, Today (1 minute ago)

Your SD card is dying. See the mmc0 errors in the dmesg? Time for a new one :)

So it looks like this is an issue with SD card. In order to be sure, AFTER you have your phone stucked, connect it to the PC and enter the adb shell and run the command cat /proc/kmsg | grep 'mmc'.

If you see the lines with mmc0 errors - this might be your issue as well.

Of course I would also like to ask intersectR to check whether this issue could be caused by his kernel?
[Nexus One Android Development] mindfrost82:
It still has to be kernel related because it doesn't happen on a stock kernel or on pershoot's kernels. It seems to be AVS related IMO.

I have apps installed on my SD card and everything has been working fine except for this issue. Hopefully IR can offer some insight to this.
[Nexus One Android Development] S_Dot:
Wifi doesnt work on 2.6.35_AVS-925mV_CFS_20100713_1042 ?
[Nexus One Android Development] bewA:
try pushing the wifi driver seperately.

instructions are on post 1 if not search the thread ;)
[Nexus One Android Development] JonInAtl:
Working fine for me
[Nexus One Android Development] waylo:
Took a look at your bug report...

(Here for everyone else:

http://code.google.com/p/cyanogenmo...ty Version Model Owner Summary Stars Modified

Not entirely sure that's the whole explanation for all of us (like some of the other posters, have not had it happen on other kernels)... but so far, you're the only one smart enough to actually have the log files to prove it! :)

If it happens to me on pershoot's kernel, I'll definitely try to get the adb shell command running on it.
[Nexus One Android Development] Nighthound:
You can use OSMonitor (free app on Market).

Go to Options, under the Message section, choose dmesg in View Log. Then in Filter (dmesg), enable filtering, type "batt" for Tag Filter, and select None or Information for Filter Log.

Now exit Options, click on the Message tab, and you'll see all the battery info. Open the menu and you can export the log to a text file.
[Nexus One Android Development] Pochemuchka1977:
Thanks :)

I saw this problem several times doing scenario I have explained in the bug. And this is the only way I managed to reproduce the error, but not always (and this is the most important part here :-) ) And I suspect that we all have the same issue. The only way to be sure is OP to check the log files and might be he will find the problem ...
[Nexus One Android Development] nellyspageli:
anyone try a 800mv kernel with the new korean radio? sounds like potential to me. im trying it right now
[Nexus One Android Development] zyonee:
I'm using the 800mv BFS with the new radio. Seems to work just as well as before (meaning it's OK). I can't decide whether the 800 or 925 uses more battery. Maybe it's true that 925 has better reception due to the voltage being fed to the radio, but I experienced my phone heating up during normal (not excessive) use with it. Went back to 800.
[Nexus One Android Development] wbknox:
bluetooth not working in new kernel

2.6.35_AVS-925mV_CFS_20100716_1410.zip can someone confirm thatfor me?
[Nexus One Android Development] intersectRaven:
Yes. It's a side-effect of the FM integration. Use the older kernel temporarily while I try and fix it.
[Nexus One Android Development] S_Dot:
DId you fix it? What happened to the changelogs?

I'm using 2.6.35_AVS-925mV_CFS_20100713_1042 phone running real hot
[Nexus One Android Development] intersectRaven:
There are no changelogs. The .35 are still experimental which is why I haven't posted them here yet.
[Nexus One Android Development] S_Dot:
BT fixed on this ? 2.6.35_AVS-800mV_CFS_20100716_1411.zip
[Nexus One Android Development] myakove:
BT still not working on 2.6.35_AVS-925mV_BFS_20100717_1525
[Nexus One Android Development] intersectRaven:
I see. It looks like I'll have to withdraw FM support for the regular .35 kernels until I (or someone else) can get BT working again. I can't really test BT since I'm using Desire in which BT doesn't work. :o
[Nexus One Android Development] Zoide_:
I see that there are 2.6.35 kernels from today that have FM in the name and some that don't.

Will Bluetooth work on those which don't say FM? For example: 2.6.35_AVS-925mV_BFS_20100717_2035.zip
[Nexus One Android Development] intersectRaven:
Yes. Bluetooth *should* work on those without FM. I can't test it for sure since I'm on Desire but since the complaints only started when I integrated FM, I'm pretty sure that's the problem. :p
[Nexus One Android Development] S_Dot:
Whats the last .34.1 and .33.5 kernels you've done with everything working?
[Nexus One Android Development] intersectRaven:
I don't know if the .33.5 is still in my MediaFire folder. As for the .34, the last one should be the one I posted in the OP. :)
[Nexus One Android Development] S_Dot:
Thanks, is it okay to use 2.6.35_AVS-800mV_CFS_20100717_2024.zip off your MF folder
[Nexus One Android Development] intersectRaven:
It should be fine. I've been using .35 ever since Google released a bootable source base. :)
[Nexus One Android Development] waylo:
Do you recall which of the last kernels may have been functioning properly without the touchscreen issue? You mention sometime within the last 2 months. Would love to try out an old version if it doesn't have the aforementioned issue.
[Nexus One Android Development] myakove:
Is 2.6.35_AVS-925mV_BFS_20100719_1409 include the audio boost?
[Nexus One Android Development] ultra99:
I'm a bit confused. I want to install the .34 but which one?

BFS:

925mV

800mV

CFS:

925mV

800mV
[Nexus One Android Development] watercool:
Your choice. 925 cfs will work quite sure, bfs 800... You have to try.

Cfs is stable, bfs more experimental but work for most

925 is stable, 800 have some people 3g issues
[Nexus One Android Development] Bidshelf:
Which version of this Kernel are rocked solid to use everyday without FC, reboot or other issues?
[Nexus One Android Development] bewA:
I've never had any problems whatsoever with iR's kernels. So just choose the latest 925 CFS one for starters :) and then if you want to try the BFS or or 800mv ones then go for it :)
[Nexus One Android Development] Bidshelf:
HotSpot working well on this .35 kernel?

I got limited connection (no internet) in windows 7 before connected.
[Nexus One Android Development] ChronoReverse:
[edit]

Oops, I was running the latest wildmonks version of .35 AVS. I swap between these kernels too much lol.

[/edit]
[Nexus One Android Development] brian6685:
Can anyone tell me what the AVS-X's are? Also, which kernel's, in your opinion, give the best battery life on froyo?
[Nexus One Android Development] bewA:
They are early alpha versions of the fm radio kernel. They were probably a little buggy :)

Sent from my Nexus One
[Nexus One Android Development] intersectRaven:
.35 release (non-FM version) Released! :D
[Nexus One Android Development] waylo:
Do you recommend .35 for CM 508?
[Nexus One Android Development] intersectRaven:
Nope. For FroYo based ROMs only. :)
[Nexus One Android Development] Pochemuchka1977:
Hi,

I have just installed the latest .35 kernel (0208) and I can't quite understand the strange behavior of AVS. Check the portion of the kmsg file:

<6>[ 167.724822] AVS setting V to 950 mV @998 MHz

<6>[ 167.824951] AVS setting V to 925 mV @245 MHz

<6>[ 169.957031] AVS setting V to 950 mV @998 MHz

<6>[ 170.197265] AVS setting V to 925 mV @245 MHz

<6>[ 174.961914] AVS setting V to 950 mV @998 MHz

<6>[ 175.042022] AVS setting V to 925 mV @245 MHz

<6>[ 179.966796] AVS setting V to 950 mV @998 MHz

<6>[ 180.066925] AVS setting V to 925 mV @245 MHz

<6>[ 190.727233] AVS setting V to 1225 mV @998 MHz

<6>[ 190.968383] AVS setting V to 925 mV @245 MHz

<6>[ 190.987518] AVS setting V to 1225 mV @998 MHz

<6>[ 191.007873] AVS setting V to 1200 mV @844 MHz

<6>[ 191.027496] AVS setting V to 1025 mV @499 MHz

<6>[ 191.035644] batt: 60%, 3889 mV, 315 mA (250 avg), 31.7 C, 814 mAh

<6>[ 191.047546] AVS setting V to 1000 mV @460 MHz

<6>[ 191.077606] AVS setting V to 1225 mV @998 MHz

<6>[ 191.137603] AVS setting V to 1150 mV @768 MHz

<6>[ 191.157775] AVS setting V to 1225 mV @998 MHz

<6>[ 191.217773] AVS setting V to 925 mV @245 MHz

<6>[ 191.918426] AVS setting V to 1225 mV @998 MHz

<6>[ 191.938446] AVS setting V to 950 mV @384 MHz

<6>[ 191.958465] AVS setting V to 925 mV @245 MHz

<6>[ 196.002410] AVS setting V to 950 mV @998 MHz

<6>[ 196.232635] AVS setting V to 925 mV @245 MHz

<6>[ 201.047424] AVS setting V to 1225 mV @998 MHz

<6>[ 201.297607] AVS setting V to 925 mV @245 MHz

Somehow, after AVS successfully set the voltage of 950mV for 998MHz, it jumps to much higher voltage of 1225 mV @998 MHz and then back to 950 mV @998 MHz and up again to 1225 mV @998 MHz.

After couple of minutes, the behavior is totally stocked - no AVS at all:

<6>[ 371.593780] AVS setting V to 925 mV @245 MHz

<6>[ 372.174285] AVS setting V to 1225 mV @998 MHz

<6>[ 372.364532] AVS setting V to 925 mV @245 MHz

<6>[ 376.258270] AVS setting V to 1225 mV @998 MHz

<6>[ 376.278320] AVS setting V to 1000 mV @460 MHz

<6>[ 376.298309] AVS setting V to 925 mV @245 MHz

<6>[ 381.273132] AVS setting V to 1225 mV @998 MHz

<6>[ 381.313232] AVS setting V to 1125 mV @691 MHz

<6>[ 381.333190] AVS setting V to 925 mV @245 MHz

I am running on CM6-RC2 and set the governor to ondemand in init.d scripts because of the bug that RC2 in running on userspace by default

IntersectR, do you have any clue what might be the reason for that ?
[Nexus One Android Development] intersectRaven:
That's fine. Sometimes the CPU clocks itself to 998 without doing anything tough which is why it settles at the lower voltage. When it does something which causes it to sweat a bit, it will complain and raise the voltage. :)
[Nexus One Android Development] wbknox:
do it make a difference if you do adb push or update.zip?
[Nexus One Android Development] vegetaleb:
Any improvements in battery life?

With the latest .34 I losed 20% in 10 minutes playing solitaire :(

When the N1 is sleeping the battery is good but once the screen lights up...

And yes I know it's normal ,and yes with non-froyo intersect kernels when using 2.1 roms it was 1% every 2 minutes while now it's 2% per minute :eek:

I hope the .35 is better
[Nexus One Android Development] intersectRaven:
You're more sure that it will work when you do an adb push. Some ROMs seem to fail with the module copy part when using the update.zip method. :)
[Nexus One Android Development] uoY_redruM:
Is there any way to tell if it did not work correctly (I'd assume looking at the "about phone").

I've done all of my radio flashes via update.zip and its always worked for me (I'm using wildmonks 1190 and since I'm overclocking to 1190, I know it has to be working :p)
[Nexus One Android Development] sirtrini:
Bluetooth Seems to Be Broken in the 3 of the latest releases

intersectRaven - thanks for all your hard work - its appreciated!

On your last 3 releases of so in your Mediafire folder - Bluetooth seems to be broken.

Bluetooth seems to start up, but when you go into Settings, Wireless & netowrk settings, Bluetooth settings you'll see that scan for devices does not work, nor any of your Bluetooth devices in the list below (they are missing).

The last release that seemed to have Bluetooth working properly is 2.6.35_AVS-925mV_CFS_20100719_1354.zip.

Can you take a look?

Thanks!
[Nexus One Android Development] EarthsiegeTA:
Bluetooth is broken in the releases with the FM radio support. The latest one should work fine.
[Nexus One Android Development] nurre:
Been having issues lately, I've had touchscreen die on me twice lately (think when switching networks, I usually had 2g only. Grabbed Toggle2G and since then I've had some issues. Disabled Toggle2G but left 3g enabled and had another lock up).

Flashed the latest kernel, and had a reboot with usb tethering.
[Nexus One Android Development] tltester:
A little question (I've browsed a thread for about 30min and didn't find an answer): does this kernel include a latest broadcom WIFI driver fix (for non-00-starting mac devices)?

Thanks.
[Nexus One Android Development] Bidshelf:
It is possible add to kernel the option of 720p that Cyanogen released for 2.6.34 kernel?
[Nexus One Android Development] flipper203:
I'd like to test one of your kernel but I don't know wich one to pick!!! can someone help me?
[Nexus One Android Development] RieGo:
I also had a touchscreen die today.

And I had this already several times..

what does it come from?
[Nexus One Android Development] dessanct:
With the newest 8/02 kernel my battery life seems to be very bad.. 20% gone in 2 hours with just moderate texting!
[Nexus One Android Development] waylo:
A few of us have had this problem. Which kernel are you using?

See:

http://code.google.com/p/cyanogenmo...ty Version Model Owner Summary Stars Modified

http://xdaforums.com/showthread.php?p=7331410#post7331410

Post 3726 onward:

http://xdaforums.com/showthread.php?t=653598&page=373

In short, I believe in some cases it's due to the undervolting modifications. In my own logs, the phone was unable to access the sdcard when at the lower voltages, leading for some reason to a loss of touch screen function. The error in the logs is: "mmc0: Data timeout"

I had this occur to me repeatedly using another kernel which are based on IR's kernels here (Wildmonk's overclocked kernels). Funny enough, it has not occurred to me using IR's last 34.1 kernel, so it may be due to some subsequent changes made to the kernel.

It happened to me on both 800mv and 925mv versions of the OC'ed kernel, so I thought my Nexus was just unable to deal with lower voltages. But the 800mv 34.1 listed in my signature has worked great so far, basically the past 2 weeks.
[Nexus One Android Development] intersectRaven:
All kernels are pulled effective immediately. AVS wasn't working. :(
[Nexus One Android Development] martin0285:
Terrible news :(
[Nexus One Android Development] intersectRaven:
I prefer not making it too easy as a form of barrier for entry. It's better that the user is familiar with the adb and fastboot commands to make sure that he/she really knows what he/she is doing. :)
[Nexus One Android Development] vipermo:
pushed file with adb rebooted flashed Kernel now in that booting loop again lol this is cracking me up haha
[Nexus One Android Development] seanowns:
850 seems solid for me.

I tried 800 earlier, and noticed a reboot so went back to 925 at the time. 850 hasnt had a single freeze or reboot yet.

Guess I know my limits.
[Nexus One Android Development] intersectRaven:
:(

:cool:
[Nexus One Android Development] DebauchedSloth:
Working great at 850 here. Very solid. Nice!
[Nexus One Android Development] dictionary:
850 working great here
[Nexus One Android Development] intersectRaven:
Currently uploading a new version with extra AVS debugging messages. Now you will be able to see what voltage AVS is setting your CPU at. :D
[Nexus One Android Development] intersectRaven:
Updated!

20100411_2113:

Non-AVS:

http://www.mediafire.com/?tgmmuzgmmum

AVS (850mV):

http://www.mediafire.com/?ghgjtdzgzro

AVS (925mV):

http://www.mediafire.com/?mm0tnynti4o

AVS (1000mV):

http://www.mediafire.com/?dwmmyfmyykj
[Nexus One Android Development] Pochemuchka1977:
What does it mean "AVS setting V to 1200 mV @20" - setting voltage of 1200mV to what ?

What is a frequency of the processor ?
[Nexus One Android Development] christiankk:
intersect: is there a step between 850 mV and 925 mV?

cheers
[Nexus One Android Development] intersectRaven:
20 is 998 Mhz so what you're seeing is your N1 is using 1200mV at 998 Mhz. :)
[Nexus One Android Development] intersectRaven:
What do you mean? Are you asking for the voltage steps? If so, then AVS uses a step voltage of 25 mV to adjust. :)
[Nexus One Android Development] christiankk:
yeah - i was kinda hoping that my n1 could work with 875 mV ;):D

I was thinking that maybe 925 isn't the lowest possible stable, given that many seems to have good success with the 850 mV kernel. :)
[Nexus One Android Development] intersectRaven:
I'll try to compile one tomorrow. It's already quite late today and I still have to get up early to go to work since it's a Monday and it's always difficult going to the city during Mondays. :)
[Nexus One Android Development] Ivan Dimkovic:
Most likely, the "minimum stable zone" lies somewhere between 0.925v and 0.8v for the majority of N1 CPUs

It is only a matter of convenience - if kernel developer was to offer all of those, he would have to build:

- 800mv

- 825mv

- 850mv

- 875mv

- 900mv

- 925mv

Total 6 kernels :)

The best option would be to make this user configurable - but the problem is going to be that at this early stage of booting when AVS is configured, you don't have access to the file systems (e.g. to read build.prop or smth)
[Nexus One Android Development] christiankk:
sure! no problem!:)
[Nexus One Android Development] intersectRaven:
Yeah. It's just too early to access a file in order to set it. Anyways, I already developed a system that compiles everything for me so its ok. :) By the way, have you updated anything else for AVS? Your github has been inactive lately but I gather from your thread that you've gotten quite a bit of modifications lately. My modifications had to be rolledback since I seem to have broken something. :p
[Nexus One Android Development] christiankk:
Sure, that I fully understand. I didn't exactly know where 925mV came from and thus I thought it would interesting to try and search for the lower bound - right now it seems that a most have no problems with 925mV, so the bound can be lower.

I, however, fully understand that the guy who has to compile all these kernels have a life besides making custom kernels - and I thus fully understands if a decision is made not to go lower than 925mV. :)
[Nexus One Android Development] lore2486:
I am using the 850mv one but my phone still consumes a lot of battery im down to 82% in les than an hour and runs@27° to 32° usually any idea why ?
[Nexus One Android Development] exelinguy:
How can I see the debug message to see the status of my battery?
[Nexus One Android Development] waylo:
Ouch. How far back are you finding this bug? Weeks, months? Looks like no kernels at all are listed on the first post.
[Nexus One Android Development] MrKongeniality:
Integrate FM too?

with all the goodies you pack so nicely and faster than many ...why is it that u r not adding FM support with all that meat u pack in?

it would be nice that u pack ur FM support feature with all these!! it will be one hell of a kernel!!!!
[Nexus One Android Development] intersectRaven:
Current FM support breaks bluetooth support so I can't add it in the mainline. As for those who asked how far this has been present, all versions of AVS are affected. It seems as if the reason why it's been stable is because IT WASN'T SETTING VOLTAGES!!! :o
[Nexus One Android Development] THATTON:
Well, I for one still think that they ****IN' ROCK!!!!!!!!!!!!! You make kernels like nobody else man and hopefully you can get this straightened out.
[Nexus One Android Development] shorza:
^^^

+1

I just want to show my support. I don't post on xda often, but i frequent this thread all the time to download and read about your kernels. I'm sure i'm not the only one.

Good luck fixing the problems.
[Nexus One Android Development] waylo:
Wow. So no AVS kernel ever was truly giving adaptive voltage?

That seems so strange because I've been getting amazing battery life out of this last 34.1 kernel you released!

I'm hanging onto it until told otherwise! :)

Lots of respect for everything you've tried to provide to the android community.
[Nexus One Android Development] ardatdat:
+ 1 !!

Show my support also!

I like your kernel and it is a perfect match with my nexus one.

Good luck fixing the problems.
[Nexus One Android Development] SimFox3:
intersecRaven, could you please share a little more detail in why AVS is not working? Is it because of the mmc errors, or is this related to something else?

In either case, you've done some amazing kernels. Thanks.
[Nexus One Android Development] intersectRaven:
It's because of something else. Ivan brought to my attention that a variable was not being initialized which will cause the setting of voltages to not go through to the regulator. I've uploaded a new kernel with FM support (breaks bluetooth) to test the new AVS stability. 925mV for now... :)
[Nexus One Android Development] r34p3rex:
Keep up the good work :D I could only dream of understanding what you do :p
[Nexus One Android Development] knightnz:
Hmm, I've been underclocking my N1 to 883Mhz for a while and it's been giving me great battery life, probably due more to the low speed than the low voltage by the sound of it :)

Cheers for looking into it IR!
[Nexus One Android Development] ardatdat:
Report to IntersectRaven:

Just try the 2.6.35-FM_AVS-925mV_CFS_20100805_1137.zip in my nexus one with ROM: FRF91 Stock, Deodexed, rooted, busybox, battery %... (Geo411m)

- Boot loop + Hang on booting

For your information please, I have been using every previous version of your kernel and they are smooth and fast :) . However, just flash the newest kernel of 20100805_1137, and I experience boot loop and boot hang when startup. Thanks.

*** Yes, same situation as the following member (SimFox3), I can boot to see the wallpaper and the phone restart as soon as I start to move around.
[Nexus One Android Development] SimFox3:
The new kernel was initially boot looping. Then after a couple restarts, I was able to login, but the phone restarted as soon as I started playing with the phone.

I'm still hopeful though =)
[Nexus One Android Development] intersectRaven:
Sounds familiar. Well, at least now we know that AVS "works". :p

*Posted an updated one btw...
[Nexus One Android Development] SimFox3:
Lol btw I'm still on the first build and the phone hasn't restarted again. Stable so far. I'll try the second build and report.
[Nexus One Android Development] bewA:
Just going to download now :)
[Nexus One Android Development] GIKE:
do you plan to add 720p video recording support?

I'm using the new enomther rom, and wish to continue using your kernel :)
[Nexus One Android Development] intersectRaven:
If ever we can stabilize AVS I'll look into it. :)
[Nexus One Android Development] Ivan Dimkovic:
Would be very interesting if someone has pre-release device with Chromium OS based on Qualcomm QSD 8250 CPU...

Because it appears that AVS is in the Code Aurora repository is there for very long time - I would be expecting that it really works, otherwise they would disable it.

With Nexus One Android kernels, AVS triggers instability as soon as voltages are really set (the problem with stable AVS was that it was not really setting voltages at all)

That could be due to two reasons:

a) We are still missing something that is needed for AVS to work

or

b) Qualcomm QSD 8250 in our Nexus One phones is not supporting AVS (unlikely, I think)

Code Aurora kernel is using slightly different TPS 65023 PMIC regulator code - maybe, just maybe, porting it to Nexus One kernel would make AVS work. I'll try it and let you know if it works.