yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] momomok:
on my N1, all TEST kernels are fine except the first one.

it was super laggy...
[Nexus One Android Development] Treatcon:
Running new test 4 kernel set for 2 hours with no problems at all. Nice!!

Will monitor logs for abnormalities.
[Nexus One Android Development] Combatbob:
Only issue i am having is the track ball wake is WAY delayed, have to mash it like 5 times. This is with smartass, if i go to ondemand all is well.

I used smartass fine before these test ones. Almost like my phone sleeps way to deeply. ;-)
[Nexus One Android Development] intersectRaven:
This is an expected behavior when smartass sleeps at 128Mhz. I could replicate it but I can't pinpoint why exactly this happens. Anyways, I tried to address this before with the latest non-TEST kernel but it seems to cause more problems than it solved. :)
[Nexus One Android Development] intersectRaven:
Seems no problems are being reported with the latest TEST kernel. I'll release it as stable next time then. :) Now I just have to wait to get enough funds to get a next generation device with a Scorpion processor. :p
[Nexus One Android Development] superg81:
That just made my day. I'm assuming you're referring to sensation. I picked one up and love it.
[Nexus One Android Development] intersectRaven:
Maybe yes, maybe no. Depends on when I get the funds...or whether I get it at all. :p
[Nexus One Android Development] sir*mez:
Yea I'm jumping ship to the sensation. I just confirmed that for my birthday coming up, a sensation will be given to me as a gift. Then I can use my upgrade whenever the next Nexus comes out. So where ever you go I'll see you there. But I'll still be here playing with my n1 since there no root for the sensation yet.
[Nexus One Android Development] gieja:
With the combination of latest fits built + test4 kernel (avs/cfs) and everything on ext4 my ringer volume is getting very quiet after a couple of hours. Wifing cache and dalvik-cache helps, but not for a long lime :(
[Nexus One Android Development] intersectRaven:
I don't think that's kernel related. :cool:
[Nexus One Android Development] gieja:
Moved back to stock kernel. Testing...

On stock kernel i don't have problems with sound.
[Nexus One Android Development] wbknox:
kernel test 4 when phone plugin(ac) screen work fine unplug (dc) screen will not come on had to remove battery twice.
[Nexus One Android Development] intersectRaven:
Have you tried holding the power button for a few seconds? Sometimes it just takes a while. :)
[Nexus One Android Development] wbknox:
yes i did that, also tried pressing power button between 5 an 10 times. went back to kernel 2.6.38.8_AVS-CM7_CFS_20110713_1002.zip
[Nexus One Android Development] harmohn:
Tried TEST 4 AVS kernel after doing my usual nand backup, wipe cache/dalvik cache & lost all gmail account settings on my device. Not sure what happened there ...grr.

Restored from backup to TEST 3 kernel setup. :/
[Nexus One Android Development] operron:
Same thing just happened to me yesterday, but with latest "stable" kernel from 7/13/2011.

I've flashed the latest cm nigthly (134) and just afterwards without rebooting ir's kernel (this is the procedure I used to follow for ages now) and did lost my gmail accounts. Well, I believe I did lost all the Google related settings: gmail, market account, etc...
[Nexus One Android Development] k3vink3vin:
Can you check your /system partition's free space?
[Nexus One Android Development] temasek:
Use Amon recovery or cwm2.

Stay away from cwm3.
[Nexus One Android Development] operron:
I use AmonRA since ages... Never been convinced by cwm !
[Nexus One Android Development] bimasakti85:
Kernel test 4 is running smooth...
[Nexus One Android Development] wbknox:
ir are you compiling a new kernel (3.0)
[Nexus One Android Development] intersectRaven:
Nope. Tried multiple times and I thought I got it right once but it still didn't work so I've given up trying to do it. Hopefully someone better can make a base. :(
[Nexus One Android Development] solidmac:
Is USB tethering broken for anyone with the latest test version? everytime i tether the phone freezes and reboots If i try again(after reboot) it works...
[Nexus One Android Development] intersectRaven:
AVS Kernels updated! :D

*stop reporting about the data corruption issue as I doubt it's kernel related since it isn't consistently replicate-able even on same kernel releases.
[Nexus One Android Development] bimasakti85:
+1 for you IR

Sent from my Nexus One
[Nexus One Android Development] harmohn:
Yep, my experience exactly!
[Nexus One Android Development] scotte9999:
But correlation sometimes does mean causation

That's the problem with intermittent bugs. I really only want to note a "me too" for the corruption issue though. Using a Pershoot kernel (or the Pershoot version delivered in CM7) I don't see corruption. With an IR kernel, about every 10th reboot *something* gets corrupted.
[Nexus One Android Development] Werewolf123:
I guess here is some problem with new release - PowerAMP not working any more and crushed constantly Returned to 0713 and it is OK

Edited: it was something with the nightly CM7 140, sorry..
[Nexus One Android Development] DonDizzurp:
things ive noticed since the new kernel (7/24)

- tonnnnnnn of FCs

- random syncing even though i have all syncing off

- autobrightness doesnt work anymore

- there was something else but i cant remember it.. so its probably not too important
[Nexus One Android Development] Treatcon:
I have none of those problems. The kernel works flawless for me.
[Nexus One Android Development] schizophrenia:
fortunately same here.

so far no problem at all
[Nexus One Android Development] phewizzo:
I have no problems with this kernel, very good performance and battery life, thanks IR.
[Nexus One Android Development] noisemonkey:
Ask good here. Think it's safe to say data corruption issues are to do with clockwork mod three
[Nexus One Android Development] solidmac:
Corruption issues can also be related to system storage space. Try to have a minimum of about 7mb available to avoid any issues, anything under that and you start having data corruption issues.
[Nexus One Android Development] rickh925:
I have had that problem since CM 6 and have just given up on USB tethering sometime over the last 6 months. I'll try it again tomorrow at work and see if anything has changed.

Sent from my Nexus One
[Nexus One Android Development] XIPRELAY2010:
@intersectRaven

First kickass rom !

Can you get fm transmit working on this one ?

@phewizzo love the sig! :P
[Nexus One Android Development] phewizzo:
Haha Thanks
[Nexus One Android Development] wbknox:
new kernel is wright. no problems found.
[Nexus One Android Development] intersectRaven:
Thanks!

;)
[Nexus One Android Development] wbknox:
what's the word on kernel 3.0?
[Nexus One Android Development] intersectRaven:
I'm not actually working on this since I'm on another project right now which I think will please many people if ever I get it to work. Anyways, cyanogen is already working on it although he's gotten sidetracked by 2.3.5 I think so maybe it'll take a bit longer to finish. :)
[Nexus One Android Development] momomok:
Any good place to learn something about kernel building stuff? Love to help, but know nothing... :P
[Nexus One Android Development] intersectRaven:
Depends on what you want to learn and also the proficiency level you have with the C language. :)
[Nexus One Android Development] momomok:
Damn. I know absolutely nothing about C language :o
[Nexus One Android Development] pen²:
Hey all, IR's power supply is broken and needs to be replaced. If you think about a donation, it would be a great idea to send one now.
[Nexus One Android Development] temasek:
US $10 donated to my respected N1 kernel developer.

Confirmation number: 78785620KH9xxxxxx

For others who can afford, pls help IR out.....

Many thanks. :)
[Nexus One Android Development] pen²:
As his great kernel saved me from buying a second battery: 0AN89037999999999, another 10 coming
[Nexus One Android Development] Treatcon:
$15.00

Confirmation number: IRKNOWSHEGOTIT

:cool:
[Nexus One Android Development] intersectRaven:
I'd like to thank all of you who donated but please don't post those here. Aside from being out-of-topic, it might be usable by people with evil intent. (I'm not sure though since I think the confirmation number is not publicly exposed or something) Again, thanks for the support. :)
[Nexus One Android Development] RogerPodacter:
There's a foolproof step by step guide on cyanogen wiki page for compiling the kernel. Even if you don't know C its a valuable experience, afterwards you can practice making small simple kernel changes to see what happens and how it works.
[Nexus One Android Development] momomok:
Good suggestion. Will definitely try it this weekend! :D

Just sent mine. Can't reach my own PC until night.

Not much, but hope it helps :)
[Nexus One Android Development] intersectRaven:
Every little bit helps. :) Anyways, it's getting close to target so I may be able to restore my PC by tomorrow if ever...well, hopefully at least... :p
[Nexus One Android Development] momomok:
invest on a better PSU. It's worth it. :)
[Nexus One Android Development] donchele:
Probably this is a stupid question, but, since I'm a crackflasher, is there a way to avoid flashing this kernel every time I flash a nightlie or a gigglebread?
[Nexus One Android Development] ultra99:
then just don't flash this kernel?
[Nexus One Android Development] donchele:
Whoa! what a genius!

For the rest of you, is there a way to make this kernel permanent?
[Nexus One Android Development] temasek:
Cm rom comes with its own kernel so when u flash a cm nightly, your existing kernel will definitely be overwritten.

So no short cut available. Flash any custom kernel after u flash a new cm nightly if u do wish to have a custom kernel.
[Nexus One Android Development] donchele:
Bad to hear! :P

So, I will have to flash this every time! :P

Great! :P thanx temasek!
[Nexus One Android Development] solidmac:
Is this kernel compatible with the battery utility ?
[Nexus One Android Development] temasek:
Yes ........
[Nexus One Android Development] intersectRaven:
AVS Kernels were released earlier. Can anyone with an SDXC MMC test and forward their kmsg so I can see if the modifications I made took any effect? :D
[Nexus One Android Development] momomok:
I am not using SDXC card, just to report that the latest kernel works just fine :)
[Nexus One Android Development] momomok:
My N1 just got rebooted, last_kmsg:

http://pastebin.com/2tUdhEcu
[Nexus One Android Development] intersectRaven:
I think that log is from recovery since the kernel version string indicates itself as being from koush. :)
[Nexus One Android Development] momomok:
Oops. How can I get the correct last_kmsg after a soft reboot?

Usually the device will reboot when I am at work, so I can't use a PC to capture it...

Any method to obtain the last_kmsg :confused:
[Nexus One Android Development] ch33kybutt:
Did it reboot all the way back to X (usually kernel panic) or to boot animation (usually ROM problem)?
[Nexus One Android Development] momomok:
Reboot to boot animation only :p

So, ROM issue?
[Nexus One Android Development] ch33kybutt:
Most likely, that's why you couldn't get a valid last_kmsg
[Nexus One Android Development] momomok:
Is there anything that I can do to help getting rid of it on the ROM? A logcat?
[Nexus One Android Development] intersectRaven:
If you're soft-rebooting and this is the last_kmsg, then my kernel isn't installed. :)
[Nexus One Android Development] momomok:
Just got a hard reset 15 mins ago.

Will upload the log as soon as I am home.

EDITED:

here's the last_kmsg:

http://pastebin.com/C0Md5U9Q
[Nexus One Android Development] Serious_Beans:
I don't see a BFS version of the kernel. Where is it located?
[Nexus One Android Development] wind0zer:
I *think* over the past months CFS was adopted in favor of BFS because it works better with AVS.

Is it just me or 2.6.38.8_CAVS-CM7_CFS_20110804_1510.zip is much better on the battery than 2.6.38.8_CAVS-CM7_CFS_20110724_2036.zip?
[Nexus One Android Development] Serious_Beans:
Okay, thanks, that's too bad I always use BFS, oh well, can't get picky with a great kernel like this.
[Nexus One Android Development] intersectRaven:
Since there isn't much development in the kernel front, I could make a custom BFS if you want. Just specify the version of CFS you want with BFS instead. Also, don't expect any support. :p

*Also, new experimental AVS kernels uploaded. Please inform me if you notice any performance increase. :)
[Nexus One Android Development] puttytatko:
Could you give a changelog too...???
[Nexus One Android Development] Serious_Beans:
Difference between AVS/CAVS? Which one is better? Suppose I use BFS which one would be better and I'm using CAVS-CM7-CFS20110804

Would BFS be unstable? If it's not too much trouble then sure :) and no worries, I don't expect support lol.

Also should there be a notable performance increase? Quadrant wise or just regular use.

Is it just the AVS or the CAVS one as well? Sorry for so many questions, I've been googling but I don't have a good understanding of it yet, and I'm newish to Nexus One.
[Nexus One Android Development] harmohn:
I'm convinced I can see an appreciable increase in general responsiveness with the newer experimental kernels.

Cheers IR :)
[Nexus One Android Development] momomok:
Just tried the experimental kernel

and my N1 got stuck at the X logo

reverted to the previous build and everything is alright...
[Nexus One Android Development] intersectRaven:
From what I hear, due to the recent (then) changes made to CFS, they're actually at par with BFS which is why BFS was abandoned in favor of CFS. Also, BFS is a tad bit unstable since it doesn't play well with the android scheduling mechanism. ;)
[Nexus One Android Development] intersectRaven:
Can you give a kmsg?
[Nexus One Android Development] momomok:
Sure.

But how?
[Nexus One Android Development] intersectRaven:
While it boots the moment it reboots hold the volume down key to go to bootloader then go to recovery after which give me the last_kmsg. :)
[Nexus One Android Development] momomok:
Miracles happened!

Upon re-flashing your kernel, everything works beautifully :)
[Nexus One Android Development] Treatcon:
Use root explorer to extract that file from the /proc folder

or

adb shell cat /proc/last_kmsg > lastkmsg.log
[Nexus One Android Development] intersectRaven:
Your issues seem to be AVS related so I cannot help you next time. Seems it's a hit or miss for your N1 when flashing AVS. :p Anyways, good to hear you managed to get it up now. I hope it stays up long. :)
[Nexus One Android Development] Serious_Beans:
Well alright then, if CFS is up to par guess there is no need for BFS, thanks anyway! Great kernel!
[Nexus One Android Development] pen²:
I had no luck with avs kernel from 8/8 and fits build from 8/8. Tried flashing ir kernel twice, first time I was stuck at X, then flashed ir kernel again. This time it booted but then I got a series of Launcher Pro FCs. (not just one, after one FC there came the next)
[Nexus One Android Development] momomok:
is the tweak in the latest release the same as the 0804 non-public kernel :confused:
[Nexus One Android Development] intersectRaven:
No. This one adds the MTD buffer tweak. :)
[Nexus One Android Development] momomok:
Great. That means increased speed, right? :D
[Nexus One Android Development] intersectRaven:
I don't know. There's no way to actually test the internal storage speed so I can't tell. :p
[Nexus One Android Development] phewizzo:
Nice kernel IR, I dont know if its placebo but my phone is running much snappier with the update, but I am on InteractiveX kernel seems to give me better battery life then Smartass.
[Nexus One Android Development] Mayday_XL:
Good kernel in combination with

http://xdaforums.com/showthread.php?t=1199472 :D
[Nexus One Android Development] noisemonkey:
Weirdly my home and search buttons have died since installing the latest kernel
[Nexus One Android Development] Serious_Beans:
Wipe everything and fix permissions.
[Nexus One Android Development] ac251404:
Just wondering if anyone has experienced any issues with the network stack in 2.6.38.*

I was having some issues with the android-xbmcremote app and continually dropping connections. I also noticed some strange network behavior in other apps but wrote it off to being poorly coded (epsn score widget, buzz time playmaker trivia for BW3's). I started debugging android-xbmcremote myself and really could not track down any issues in the source and the buggy behavior was extremely sporadic and difficult or impossible to consistently reproduce.

I was just curious since I really like this kernel but having a running remote is a must for me right now.

For the curious... I can't post a link, but the android-xbmcremote issue tracker issue is #493 for the original report on this and some of my investigations.
[Nexus One Android Development] bassmadrigal:
Are you running a nightly of CM7? I think any of them after build #143 have been having sporadic wifi dropouts. It seems like it is not honoring the dhcp lease time from the router and it is trying to get a new lease every few minutes.
[Nexus One Android Development] yermet:
I had that problem with my Linksys and I fixed it installing the nightly-157 (last one when I upgraded it). Now it respects the lease time :)
[Nexus One Android Development] ac251404:
sorry forgot that important detail... I am running CM7 nightly since about #138 or so. This has been an issue the whole time. Currently on nightly #158 and the issue is present with IR kernel, but not with the stock kernel of the nightly (2.6.37).

So as of 2 nights ago, CM7-158 with IR kernel - sporadic wifi behavior, CM7-158 stock kernel - expected behavior.

It's not a huge issue for me, and probably difficult to nail down. Just wanted to get some feedback to see if it is specific to me or something I'm doing.

Also: phone is N1 and router is linksys WRT54G with DD-WRT firmware. My roommate has a HTC thunderbolt running CM7 stock kernel with no problems also.
[Nexus One Android Development] bassmadrigal:
I am running the same router with the same firmware, and I didn't have any issues with wifi until I got into the 2.3.5 nightlies (using both stock and IR kernels). One thing to possibly check is the DHCP Lease Time. I know someone else somehow had theirs set to 2 minutes. The default is 1 day.
[Nexus One Android Development] momomok:
2 hard reboots today :(

http://pastebin.com/qaFhFrsa

http://pastebin.com/B8XZ0aHy
[Nexus One Android Development] momomok:
Just got another hard reboot

Here's the last_kmsg:

http://pastebin.com/9FN9n70i
[Nexus One Android Development] intersectRaven:
Seems an error with your MMC. :)
[Nexus One Android Development] momomok:
Hmmm... MMC = my SD card?
[Nexus One Android Development] intersectRaven:
Yeah... :)
[Nexus One Android Development] momomok:
Alright. Let me check the SD card using HDtune or something similar tonight...

I also saw something about bad block ing yaffs.... does that mean there is some bad /dead blocks in the internal memory?
[Nexus One Android Development] matti537:
After one day of running the latest kernel I also started getting sporadic reboots.

CM Nightly 07-132011.

No issues with my sdcard to my knowledge.
[Nexus One Android Development] momomok:
Wiped davik cache and cache yesterday and it seems ok....

I got a hard reboot 15 minutes ago

here's the last_kmsg: (pretty long :D)

http://pastebin.com/4MiQKhFW
[Nexus One Android Development] intersectRaven:
That one may be AVS related. :p
[Nexus One Android Development] momomok:
AVS related? I don't understand...
[Nexus One Android Development] intersectRaven:
Your N1 can't handle the voltage so it makes incorrect calculations thus making the N1 crash. :(
[Nexus One Android Development] momomok:
Hmmm... it's like undervolting in PC

, right?

Needs a lot of trials to find out the lowest stable value...
[Nexus One Android Development] Realtyem:
new project

Been loving this kernel for a long time, but I would like to see some new directions. IR have you ever considered looking into other Tcp Congestion Control plugins for the kernel? Android comes with RENO and CUBIC which is great.....if you are on a landline lol. Here's what I was reading http://en.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm

thought you might be interested. Thanks for all your hard work.:D
[Nexus One Android Development] intersectRaven:
Currently we're already using Yeah-TCP as the TCP congestion protocol. I don't know if there's any merit in switching to the others as they seem to be older. :confused:
[Nexus One Android Development] Realtyem:
True that. Not sure exactly where but somehow I missed a kernel flashing. Figures the one time I would actually look into it and I'm looking at the wrong kernel LOL. Anywho, yeah I see yeah and vegas now. Has either of them been benchmarked that you know of?
[Nexus One Android Development] evcz:
I think I'm having the same issue :(

How can we handle that?

Is there a not-undervolted version available? :(

Thank you
[Nexus One Android Development] Realtyem:
So IR, whatcha doing? Don't suppose you'd be kind enough to build cifs modules for us, please please please :D
[Nexus One Android Development] Realtyem:
Nevermind, I found them. Not sure why they didn't load /shrug
[Nexus One Android Development] intersectRaven:
That's what CAVS is for. :)
[Nexus One Android Development] houzuoguo:
Hey IR :D are you gonna get Nexus Prime?
[Nexus One Android Development] intersectRaven:
Depends on the specs. :)
[Nexus One Android Development] intersectRaven:
Found a really huge as in facepalm huge mistake in AVS. It wasn't working ever since the 20110713_10XX version!!! Sorry about that!!! It was just functioning like SVS. :(
[Nexus One Android Development] intersectRaven:
AVS Kernels updated!

- fixed it to actually work

*please expect those who had instabilities before the version I mentioned which started the mistake to restore those instabilities :p
[Nexus One Android Development] zyr3x:
Thx. Good job
[Nexus One Android Development] ~semsem~:
Waiting for kernel 3 :) hopefully it will not be a long time
[Nexus One Android Development] yermet:
Yeah!!1

Thanx a lot man!
[Nexus One Android Development] n0w4y:
Tried again your great kernel, but sadly my nexus is still sleeping to deep :(

needs a lot of trackball hits to wake up.

everything else works smoothest ;)
[Nexus One Android Development] intersectRaven:
That's a problem with 128 Mhz. Don't use that as the lowest frequency if it bothers you too much. :)
[Nexus One Android Development] evcz:
Mine keep force closing apps, I suppose it's due to higher voltage required by my CPU ( in the past it was able to handle low voltages without troubles but I use and stress it a lot)

(Everything as default: "on demand" and stock frequencies)

What do you suggest in such cases?

(Cm7 nightly kernel works fine)

Thank you
[Nexus One Android Development] cpm:
I get the same, apps FCing etc.

However if I use Tiamat kernel Smartass 128Mhz works fine.
[Nexus One Android Development] temasek:
Latest IR Kernel stable. Didn't realise AVS wasn't kicked in. Prior to update was using 0808 IR build.
[Nexus One Android Development] intersectRaven:
If in the past you meant the versions beginning with what I posted earlier, then AVS hasn't kicked in then which causes your false stability. Now that AVS is up again, you should adjust voltages to be more acceptable for your N1. :)

AVS...AVS...AVS...adjust your voltages... :)
[Nexus One Android Development] cpm:
Will try it again so :)
[Nexus One Android Development] houzuoguo:
im using ondemand and lowest frequency at 128mhz... no any problem so far ^_^
[Nexus One Android Development] evcz:
Thanks

Ok, will try to change the voltages soon (gotta found out how to do that :P) :)
[Nexus One Android Development] intersectRaven:
I think someone wrote a utility for that already. I've been meaning to write an app for it but I'm still learning how and even if I do learn how it might take some time as I'm notorious with my programming iterations. :p
[Nexus One Android Development] harmohn:
Try using vipermod script:

http://vipermod.tiamat-dev.com/