yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] temasek:
Not sure abt iphone but many have.lower class sd card. Even my class 6 card speed tested was below par. Sad: (

Anyway most of us the recordings are directly written to sd card and not internal. So sd card does affect.
[Nexus One Android Development] redstar3894:
Yep, that was it.... I re-pushed the bcm4329.ko module and that seemed to do the trick.... thanks :)

I thought it might have had something to do with the weird i2c errors I noticed in the dmesg, but I guess not....

Sorry about the false alarm.... :p
[Nexus One Android Development] intersectRaven:
HAVS updated again! Nothing major, just a rebase to latest cyan commits which are just minor. Go to my MediaFire folder for links! :)
[Nexus One Android Development] houzuoguo:
Latest one is very stable . good work Raven
[Nexus One Android Development] MicroMod777:
IR, here's the error I and others are getting for Google Goggles:
[Nexus One Android Development] intersectRaven:
I'm not seeing it on my setup. I think it's a ROM problem if it can't mount the IPv6 from the module. I use CM nightly and it's fine so I won't address it in the kernel. Building it in would make it bigger which is what I'm trying to avoid. :o
[Nexus One Android Development] MicroMod777:
Yea, thats what I read why other dev's left it out of the kernel because of size. I think the 2.10 base ROM's have this problem because other bases have had it working, as you did. I'd change base but its the only base that supports all my other hybrid Cyanogen apps. Guess well just have to live without Goggles unless you make one bigger custom kernel once to experiment with and see how it goes. :)
[Nexus One Android Development] jameztcc:
Flashed latest CM-BFS-HAV on nexus one, on cm 6.1 rc1, having problem watching YouTube app (latest).

The video is very delayed and laggy. Tried performance, interactive and ondemand gov at various frequently until max, same issues. Does not happen on pershoot or cm kernel.
[Nexus One Android Development] zitseng:
Works okay for me. Google goggles too. I'm loving this kernel.
[Nexus One Android Development] intersectRaven:
BFS doesn't work very well when you have too many background apps. Maybe that's the problem? :confused:
[Nexus One Android Development] jameztcc:
Thanks for the tips, shall try to terminate background apps and try again.

In your opinion, should we use bfs or cfs, as android allows us to just put apps to background and 'multitask'?
[Nexus One Android Development] intersectRaven:
If you have many background apps that require lots of CPU time, I'd go with CFS. If your focus in on one run application performance, go with BFS. :)
[Nexus One Android Development] jameztcc:
Thanks! Guess I stay with BFS, not running a multi user server on phone ;p rather have the focus app run at best performance and batt life (at idle) if possible.
[Nexus One Android Development] houzuoguo:
Hi Raven

after I've been running your latest kernel (1030_0804), I think it is very stable, would you please make a kernel with lower voltage? (like few months ago you had 800mV version of kernel)

Thanks a lot!
[Nexus One Android Development] intersectRaven:
First of all anything lower than 950mV would lower the signal quality. If you still want one, please specify what voltage you want and I'll try to release something. (just don't expect it to be included in my regular releases) :)
[Nexus One Android Development] houzuoguo:
wow that's very kind of you :D thanks a lot.

How long does it take to compile kernel?

could you make a 800mV version and a 850mV version please?
[Nexus One Android Development] intersectRaven:
BFS or CFS? I'm just in a good mood today and not doing anything since my external HD just crashed on me taking all my previous anime with it. :p
[Nexus One Android Development] Cpt.Curry:
hey IR, great kernels been using them on cm6.1 and getting quadrant score of 1800, real sweet, just wondering which CFS-CM kernel would you recommend for the best battery life, been playing around with, and can't seem to find really good battery life, I used to have great battery life with 1025-with the latest entry from the op, but when I got to rc1 the batt life dropped dramatically. THanks :D
[Nexus One Android Development] houzuoguo:
thank you so much :D BFS and no audio-boost please
[Nexus One Android Development] intersectRaven:
One last question...CM or non-CM?
[Nexus One Android Development] houzuoguo:
Cm please :p thanks a lot!
[Nexus One Android Development] intersectRaven:
Here:

http://www.mediafire.com/?ms6yphi8rj48dba :)
[Nexus One Android Development] houzuoguo:
thank you so much Raven :)
[Nexus One Android Development] jameztcc:
Just for fun of it flashed this and can't last a minute of use 2x, just auto rebooted. Guess 800 not for me.
[Nexus One Android Development] houzuoguo:
actually I just had similar problem.. I have SetCPU on demand, up to 960mhz, and my phone freezes ~

thanks anyway :)
[Nexus One Android Development] intersectRaven:
That's too bad. If it worked at 960Mhz I would've released an 875 for you to test the effect on signal but now I don't think your N1's CPU can handle even that voltage. :(
[Nexus One Android Development] jameztcc:
Don't mind me asking, any diff between this kernel and pershoot's?
[Nexus One Android Development] redstar3894:
Interesting idea, merging in the OOM killer rewrite from 2.6.36... don't get me wrong, it seems to be working VERY well so far with the latest kernel, but wouldn't that potentially conflict with Android's native internal memory killer?

IIRC, there are some android specific calls in the original 2.6.35 OOM killer, which presumably would invoke the Android native task killer at certain points... correct me if I'm wrong here, but wouldn't the new OOM killer cause conflicts between the two?

Another observation: I've noticed that the available (free) memory seems to be considerably lower during normal use than it was prior to this merge... what I've observed so far is that it tends to hover roughly around ~15mb free, even dropping down to ~4mb at some times, when before it was usually ~50-90mb higher, it scared me for a minute since I'd never seen it get this low, but everything seems to be running as smoothly as ever :D....again, just an observation, I trust the Linux kernel to have much better memory management skills than I would... :p

That being said, the latest kernel is running very well, the OOM killer rewrite seems to have helped in many small areas, I guess time will tell what real impact it has... :cool:
[Nexus One Android Development] houzuoguo:
going to try new kernel now :D

does anyone know how to prevent android from killing background programs?

I constantly getting more than 150MB of memory and my background programs constantly get killed :(

I tried auto task killer, set everything to 0 but still background programs got killed~~

thanks!

by the way Raven, is your kernel 950mV right? Could you please release a 925mV version? I yesterday tried WM's 925mV kernel and the voltage seems quite stable :p

thanks a lot!
[Nexus One Android Development] intersectRaven:
It should be fine. I did spot the android task killer and didn't remove it from the code. Just made sure that the patches are applied properly. Also had it running for quite some time before I merged it into my standard so there should be no problem. :p
[Nexus One Android Development] redstar3894:
It's been running very stable here as well, no problems as of yet... ;) it seems to be running more smoothly, and I'm not sure about the battery life yet since my girlfriend has been playing angry birds all night on the nexus... :p

Any plans for merging in commits from cyanogen's new 2.6.35-msm-exp tree? It looked like he was doing more fooling around with memory management and stuff like that, could be interesting.... :p

Anyway, just a thought, :D
[Nexus One Android Development] intersectRaven:
Yeah. I'm particularly interested in the power enhancement from HTC. I just don't have time to merge and test so can't do it right now. :(
[Nexus One Android Development] m00moo:
Cant seem to find any havs in your mediafire folder? Ty
[Nexus One Android Development] zitseng:
I'm particularly interested in that too :) The merge is a little to complicated for me to manage on my own :P
[Nexus One Android Development] redstar3894:
I have some time today before work, I'll try and get a test kernel or two built with some of the new commits and let you know how things seem to be running.... ;)

The power management stuff does indeed look intriguing...
[Nexus One Android Development] _Opiate_:
I guess I got lucky...mine boots that test kernel and runs just fine on "on demand" or "interactive".
[Nexus One Android Development] redstar3894:
Okay, managed to get some of the changes merged in... it booted and seems to be running quite well *so far* :rolleyes:

I tried wifi, camera, flashlight, most stuff seems to be working as expected...again, so far...;)

I have the updated source up on github if anyone is curious...

https://github.com/redstar3894/ppckernel/commits/mahimahi-2.6.35

I rebased off of IR's kernel before I started working, and the YAFFS2 is from the latest commits off their site...

I'm running eViL's NXsense desire port 1.22.1, the kernel is using the CFS scheduler...

Otherwise, that's about it... IR, I'll email you the update.zip if you're interested, and I can provide a logcat I took on the first boot as well as a couple dmesg outputs... :cool:

I don't want to hijack the thread any more than I already have, so I won't publicly post the update.zip without IR's permission... ;)

This is the commit in question: https://github.com/redstar3894/ppckernel/commit/c6a9f8bf0e49b9d036a7c2a7d4d2bef40e66fd7f
[Nexus One Android Development] intersectRaven:
HAVS Kernel updated!!! :)
[Nexus One Android Development] zitseng:
Cool! Noticed you've a new branch based off cm-kernel-exp. I've been trying the latter and pretty happy with it. Just only missed HAVS. Now we've got the best of both worlds :)
[Nexus One Android Development] xzr3b0rnzx:
hm...the new CM 800mv CFS kernel is stable ???
[Nexus One Android Development] intersectRaven:
Depends if your N1 can take it. It's stable for me but I have received reports that it was unstable for others so I'm not providing the full link. :)
[Nexus One Android Development] mrluker:
I want to know the difference between AVS-CM and AVS

thanks
[Nexus One Android Development] myakove:
Just flash the BFS CM new kernel and in the "about" it say CFS.
[Nexus One Android Development] ilos:
CM is for CyanogenMod rom
[Nexus One Android Development] houzuoguo:
Hey Raven :D

thanks a lot and well done,

I'm now using your 35.8 kernel (normal voltage one) and it works very well.

and my nexus one perhaps isn't able to handle 800mV :p
[Nexus One Android Development] sir*mez:
I'm back on your kernel great work! Damn 800mv didn't work on my nexus. But either or its good to be back!
[Nexus One Android Development] intersectRaven:
Really? Hmmm...maybe something wrong with my maker script...or maybe I just did the configuration wrong...I'll see to it once I get home...forgot to put my configs and the improved maker into my dropbox...should've just made a soft link for them... :p
[Nexus One Android Development] MicroMod777:
Yea, I tried it too on Enom's 2.13.2 ROM and it would freeze on boot. Maybe 900mV next try? :)
[Nexus One Android Development] adx_x:
11/07 kernel:

"goggles won't work in your non-standard system configuration (kernel is missing ipv6 support)."
[Nexus One Android Development] redstar3894:
+1 on the new branch, helps me out a bit... :D

Okay, so my build of your mainline kernel with the HTC power management code has been running VERY stable for the last couple days, haven't noticed any substantial improvement in battery life, but then again, perhaps the ROM needs to be coded to take advantage of the new features...:confused:

I also tried a test build with the tiny preempt rcu changes merged in, seems to make CFS seem very smooth, almost indistinguishable from a BFS powered kernel, and that didn't seem to have a huge effect on battery life... so I would recommend that for inclusion... :cool:

I put both test kernels (with power management and the second one with tiny-preempt-rcu) through some heavy use the last two days (went on a road trip) and they both performed very well, very stable, no real problems to report.

I'll have to try building one with the kineto gan (wifi calling) module and see if the whole wifi calling thing works... been waiting for that ever since I ditched my crackberry for the N1.... :p

And per some requests I've gotten, I'll try building one with IPv6 built in (for googles support) and see how much that enlarges the kernel binary, but like IR said previously, I would recommend/prefer that it be built as a module, if the ROM isn't loading it, AFAIK then maybe there could be a way to modify the init scripts so that the module is autoloaded on boot, but I'm not too familiar with that side of android hacking... :rolleyes:

I don't have too much time this week, but please let me know if you (IR) or anyone else needs anything tested, I'm more than happy to whip up a test build or two if I have time... :D
[Nexus One Android Development] zitseng:
Yup, I'm very pleased with CFS + CONFIG_TINY_PREEMPT_RCU too.

Re HTC power management: I think we're squeezing the last few ounces of battery out of the ROM that any further improvements will be hard to measure. :) But it's good to know that at least theoretically it has got to be better than before.

Another thing to try is the cpufreq interactive governor. I have this feeling that it's slicker too, although hard to quantify objectively.
[Nexus One Android Development] zitseng:
Btw, I looked at the AVS kernel messages and noted that with the latest kernel (2.6.35.8_AVS-CM_CFS_20101107_2050.zip), I don't see any message about AVS settings for 998MHz. For example, messages like below:

AVS setting V to 1225 mV @960 MHz

There are many other frequencies in the log, just not 998MHz. But checking /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq does show the CPU running at 998MHz now and then, so I know the CPU did really ramp up to 998MHz.

Wonder why the lack of AVS messages about 998MHz?
[Nexus One Android Development] intersectRaven:
This should happen if AVS isn't ramping the voltage for that frequency. :)

New HAVS kernel released!

- added WiFi fix for WiFi calling (please tell me if you notice any significant power consumption so I can roll this back)
[Nexus One Android Development] Werewolf123:
Dear intersectRaven! What happened to NO AUDIO BOOST versions? My speaker on phone screaming like a crazy when I unplugging BT headset (Samsung). And I noticed that the

minimum

speaker volume is

increased
[Nexus One Android Development] iDance°-->ra1n:
cfs or bfs??
[Nexus One Android Development] intersectRaven:
Woops...forgot about that one... :p
[Nexus One Android Development] muchbt:
Yes! 800MV one works on my n1.:p

EDIT: but unstable for me,rebooted after a few minutes.
[Nexus One Android Development] alvinistic:
Tried the 11/08 bfs and experienced random lock ups which caused FC :(.

EDIT: The cfs version has big performance boost on homescreen though. Thanks, Raven!
[Nexus One Android Development] iDance°-->ra1n:
what is the best, CFS or BFS?
[Nexus One Android Development] alvinistic:
Read post #2 :)
[Nexus One Android Development] u3819013:
800mV unstable (random reboot)

but 825mV works for me. :D
[Nexus One Android Development] RieGo:
sry, i mean when i reboot the phone makes a few freezes and reboots before it's ready to use. but that's a problem on every avs-kernel i tried...
[Nexus One Android Development] bt1980:
aha

Got brave enough to try AVS again and I got 850 working with CyanogenMod 5.0.6-test2. So fast, so nice :)
[Nexus One Android Development] rjhay22:
Thats a common issue, a few people has reported the same :) I've tried them all and was able to run all of em as well, but after a reboot it goes to boot loop :(

Im on Enom's ROM and the battery life on this is AWESOME! (as long as I dont reboot I be fine i guess) lol.
[Nexus One Android Development] lore2486:
just tried the 825 its working stable for me, the 800 didnt boot at all

my only problem now is that the wifi dosent stay connected?? any one else experiencing something like this?
[Nexus One Android Development] rjhay22:
Try pushing the wifi module again.
[Nexus One Android Development] TurnandBurn0:
CPU Voltage Display

I have added the 850 kernel to my N1 and wanted to find a way to be able to view what voltage the cpu is drawing in real-time. Is anyone aware of how to do this? Thanks
[Nexus One Android Development] myplague:
You can use the terminal or just use OSMonitor from the market.
[Nexus One Android Development] lore2486:
adb shell cat /proc/kmsg :)
[Nexus One Android Development] lore2486:
tried that didnt work any other sugestion? it connects but after 5 min it disconects itself
[Nexus One Android Development] LunatikBunnie:
Good job raven! I finally found an AVS version my phone actually boots into :D

The 925mV and 1000mV, currently on 925, will report abnormalities again :3
[Nexus One Android Development] overground:
The 800 gives me random reboots. So far, 825 behaving swimmingly. :)
[Nexus One Android Development] rjhay22:
Hmm that is unlikely, since you can connect for a few mins, sounds like your wifi connection is the culprit. reboot? and hope it wont bootloop :P then try 850mV. Least thats what I would do. :)
[Nexus One Android Development] rjhay22:
+1 OSMonitor works great :)
[Nexus One Android Development] jblazea50:
No go on the 800 or the 825. 825was working but now just keeps on rebooting and can't use it at all. Going to get back in the 850 as I know that works well on my phone.
[Nexus One Android Development] Nick_Hrh:
rebooting with 850. 875 works fine so far.
[Nexus One Android Development] overground:
One thing that has been bothering me, the governor, most times, does not like to scale using conservative. It just sticks at whatever it was at before the switch. Once in a while, conservative will actually scale. Ondemand scales fine every time. This is using SetCPU.

EDIT: Still no problems with the 825 for me.:D
[Nexus One Android Development] hah2110:
800 seemed okay for me although Touchdown FCed (never happened before). I was able to reboot fine, and then it rebooted by itself so I'm moving to 825. Here was my log from 800, is this fluctuation normal?
[Nexus One Android Development] christiankk:
seems you have something running in the background.
[Nexus One Android Development] hah2110:
What could the culprit be? Anyway to see what it is?

EDIT - Just ended all apps and processes... Doesn't seem like there is a difference in fluctuation... What could it be?

EDIT again - On standby, no apps running... It fluctuates between 850, 825 and 1050... Completely skips the 900s. What is it doing?
[Nexus One Android Development] Werewolf123:
Have I hope to get it?
[Nexus One Android Development] nakedwarrior:
I have the new Evil 1.26 ROM and wanted to know what is the best IR kernel for it. I have the kernel that came with it so far. What is everyone using?
[Nexus One Android Development] niftydl:
Non-CM camera fix

Those of us with non-CM stock FRG83 roms would really appreciate it if you could find some kind of fix (or a workaround) that includes the WiFi calling modules and a working camera ;)

WiFi calling link: http://xdaforums.com/showthread.php?t=807116

I am using Geo411m's FRG83: http://xdaforums.com/showthread.php?t=714184

*fingers crossed*
[Nexus One Android Development] houzuoguo:
Hi Raven :)

I use to undervolt my laptop CPU working voltage and that results in significant less heat and less power consumption, so I'm wondering, is it OK to do so to Nexus One's CPU?

My old laptop has 1.225V normal CPU working voltage, and I undervolt it down to 1.1V and got nearly same performance as using 1.225V.

thanks!
[Nexus One Android Development] intersectRaven:
No audio boost versions uploaded. :)
[Nexus One Android Development] zitseng:
Use the HAVS kernels? Already adaptively undervolts :)
[Nexus One Android Development] Werewolf123:
Many thanks!
[Nexus One Android Development] houzuoguo:
thanks :) yes I'm using HAVS kernel now.

What's normal highest voltage to feed Nexus One's CPU? That's what I'm wondering, because since 1.225 volts is very stable at maximum frequency, is it possible to lower the voltage to gain more power saving at high frequency?
[Nexus One Android Development] zitseng:
Hi... in principle, AVS is supposed to get hardware hints about what is the right voltage needed by the CPU based on current operating conditions. If you look at /proc/kmsg, you should see AVS doing its work to undervolt the CPU. AVS operates within a certain voltage range, defined in a table, for each CPU frequency.

If you're asking to further lower the voltage... you could change the values in the table. You'd have to recompile the kernel though.

My Nexus One seems to be very happy running between 825mv (245MHz) to 1200mV (998MHz).
[Nexus One Android Development] houzuoguo:
i see, thanks mate
[Nexus One Android Development] redstar3894:
At least in my experience, 1200mV is good for an upper vdd limit for a non-OC kernel, and if you're going to OC frequencies, then between 1225 and 1275 is a good bet... IIRC Wildmonks set his to go up to 1300mV (I think that's technically overvolting...but whatever... :p) and it was pretty stable up to 1225MHz

Lowering the voltage can only get you so far... and it seems to be a mixed bag at that... zitseng is one of the lucky few who has no problems running voltages lower than 900mV... whereas my nexus will tolerate the lower voltages with no immediate problems, but tends to exhibit random quirks when running at said voltages.... so tread cautiously here... ;)

AFAIK the generally accepted logic from kmobs (the guy who pretty much invented UV on the nexus) is that 950mV is about as low as you can go and still have optimal functioning... some may be able to go lower, but 950mV is a good starting point...

As stated above, AVS will handle most of the undervolting... it sets the voltage to the lowest possible value in the table for that respective frequency...if that voltage isn't stable, it ups the voltage by 25mV and tries to set it again... so AVS will usually do a pretty good job of handling the undervolting on a daily basis... :cool:
[Nexus One Android Development] alvinistic:
I am experiencing random lockups with the 11/08 CFS too. Applications are randomly in hang state and there is no other choice but to force close. I even have wiped everything. Using it on CM 6.1 RC1.

Any tips from those who found it stable? Perhaps I got something wrong.

Thanks.
[Nexus One Android Development] mezmer1ze:
I had no problems with 800 mV SVS kernels that you made like 5 months ago so I may give a try to an AVS one and see how it goes :p

Anyway doesn't the low voltage for AVS affect signal strength?
[Nexus One Android Development] zitseng:
I think there was a post some time back that said so, for voltages under 950mV (from IR if I didn't remember wrongly but pardon me if I am mistaken). However, my personal experience testing 950mV vs 825mV could not conclusively find any meaningful difference both in signal strength and achievable download/upload bandwidth.