yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] damanrico:
For me SU 2.2 doesn't set setcpu at boot. You're right that it takes about 1 minute before SU to become active (and also load my widgets).

BUT, SU 2.2 doesn't actually set your settings once it becomes active. You can really see that if you use Autokiller. Every reboot you need to select your profile again. Also, setcpu will not overclock UNTIL you actually start setcpu, then it will apply your settings.

Using SU 2.1 it does remember the Autokiller profile, and setcpu does set your settings at boot, without it needing to be manually started by the user.
[Nexus One Android Development] whoisthedrizzle:
That's probably autokiller... I honestly don't have issues with setting at boot even though it takes a minute. If I have the setcpu widget - no chance it will set the clock @ 1113 vs 998 after a reboot, without the widget it appear to holds my boot settings fine (verified by going into multiple apps like quadrant and viewing system info before opening setcpu after reboot and looking at the device info page - always at 1113 max)
[Nexus One Android Development] whoisthedrizzle:
Yeah, I mean I'm by no means an expert or any kind of pro-coder but I'm rather convinced most people's issues with ADW are actually for the large part because of the broken SU. To be honest, I'm really not sure how people stayed on RC1 for so long without reverting or flashing something else or updating SU, and the only thing I can think of is they much not be using many, or any root-only apps, because it isn't just setcpu it's titanium, meta-mortph, adfree, etc etc. From my perspective that's a pretty broken build (even taking into account it's in development).

Did you revert to the last nightly or are you still trying out RC2? I'm debating giving it one more shot maybe with the non system ADW to see if there's any improvement. That's about the only thing I haven't tried.
[Nexus One Android Development] wildmonks:
I'm giving RC2 at least a full day but yah, I'm starting to move towards reverting. As the day goes on, it feels more sluggish and from what I'm reading in other threads, there might be a memory leak somewhere in this build. The last nightly I was on (07232010) has been a more pleasant experience.
[Nexus One Android Development] andrewv88:
still the tethering doesn't work after your's new kernel
[Nexus One Android Development] pakraider:
I think there may be other WiFi issues beyond just that fix. My router's MAC starts with 00, but I still get the WiFi problem (it doesn't honor the 'never' sleep setting) regardless of the new kernel or any ROM I put on. Very frustrating, as I'm not sure where the problem really lies (hardware, ROM, kernel, etc.)

There's an app by an xda member with some workarounds, but unfortunately that doesn't solve it for my phone either.
[Nexus One Android Development] whoisthedrizzle:
Yeah. Interestingly enough I flashed back to a nightly for a while, then back to RC2 and I've been using it bare and stock for an hour or so, only installing root explorer and os monitor. My CPU is completely locked @ 883 Mhz/userspace and rarely drops to 245 or even fluctuates. No kernel will default to 998/ondemand for me anymore with RC2. A.W. tweeted something about a memory leak in ADW earlier. IMO, functionality should come before theming support, but oh well. Hello sweet nandroid...
[Nexus One Android Development] wildmonks:
Sorry for not specifically pointing this out but when I said the MAC address starting with 00, I meant the phone's MAC address, not the router.

I've read up on the thread with the app that doesn't work for you (yet). It would seem there's a deeper cause to this problem. I agree, this can be frustrating since there seems to be no rhyme or reason as to the cause and why it only affects some phones.

I can tell you that the there has been continual updates by the broadcom people for the wifi driver so perhaps in the near future this will be resolve for all affected devices.

Edit: I do have the old source code for the Wi-Fi driver. If you like, I can try to use that source in the latest .35-rc6, compile the kernel and see if that makes any difference at all for you. There's a chance that the old source for the Wi-Fi doesn't cause this issue for you.

Curious, does downgrading Superuser to 2.1 resolve this problem. I can't seem to replicate this problem on RC2.

Sorry to hear that flashing my kernels did not solve your tethering problem. In an effort to try and replicate your problem I installed cm6-rc1 (without kernel updating) and tried to Wi-Fi tether my computer to the phone. Surprise to see that my computer won't connect to the phone. I then deleted the Wi-Fi profile on the computer ("Android AP" in my case) and tried to reconnect to the phone and it was successful. I then flashed a new kernel and verified Wi-Fi tethering is still working.

Try deleting the Wi-Fi profile on your computer or whatever device your trying to tether to the phone with and see if that solves your problem.

By the way, I normally I don't use the built in tethering function and instead use this tethering app since offers data usage and speed tracking, supports reducing the Wi-Fi power output in an effort to save on battery drain, and has bluetooth tethering support. You can grab it here if you want to try it. (I use version 2.0.1 since that version offers the Wi-Fi power output settings)
[Nexus One Android Development] pakraider:
ah. well my phone's WiFi MAC address starts with 00 too :) Yeah, I'm hopeful that sooner or later we'll see a fix across-the-board for the problem. If you could compile that test kernel, I'd be much appreciative! Sending a few orange juices your way. :)
[Nexus One Android Development] whoisthedrizzle:
YEah. Actually I kinda screwed that post up apparently...

What I had also intended to say was that on RC2 SU 2.2.2 + SetCPU widget were displaying the proper min/max but, was defaulting to 833/userspace, and at this point I was convinced it was actually setcpu and not su, but with 2.2.2 it will always boot up @ 883/userspace - with or without the active widget, using 2.1 it saved the proper min/max upon reboots.

I had initially thought that 2.2.2 was working with everything because it was displaying the proper value min/max - it just wan't moving from 883Mhz which I even verified through other apps that just read the cpu state/freq. Clean install of RC2 without any changes whatsoever, and it's stuck at 883/userspace which apparently is the bootclock.

Just reflashed RC2 and SU 2.1 over RC2 w/ SU 2.2.2 and instantly started setting the right frequency, which would not reset initially. I'm going to try a complete wipe w/ RC2 and 2.1 and see how that goes. Again.
[Nexus One Android Development] wildmonks:
Whoa wait, hold off on the O.J.! (haha). Wait and see if this works. I don't know if it will even compile, or if the old driver will introduce other bugs.. boy.. that would be bad...... :(
[Nexus One Android Development] wildmonks:
If indeed using the old 2.1 solves all aspect of your specific problem then it would seem so many of the user reported issue with rc2 can be resolved by fixing SU 2.2.2. (That and the VM heap size thing).
[Nexus One Android Development] whoisthedrizzle:
So first boot on SU 2.1 - I installed System Panel - checked min/max clocks - good. Then installed OS monitor - checked min/max clocks - good but still stuck on 883/userspace. Then installed setcpu to triple confirm this. Didn't touch min/max, simply selected userspace and set on boot, and rebooted. Upon boot immediately checked clock frequencies and governor and both had stuck. Last night I was using your 925 CFS, today just 100% stock and the same **** happened,
[Nexus One Android Development] whoisthedrizzle:
I also noticed that even though all kernels show the full min/max when @ 883/userspace on boot (with SU 2.2.2.), this only happens for me on RC2. Latest two nightlies will both stay @ 998/on demand.

On a side note the latest BFS was smoking last night for the short amount of time i had a stable device :p
[Nexus One Android Development] wildmonks:
Wow, crazy that it gets stuck like that. I don't know enough about rom development to even guess why that's happening... :confused: I think its time to give up on RC2 and stick to what works.
[Nexus One Android Development] wildmonks:
Sorry it took so long but I got so many compiling errors as I was trying to make it .35 friendly. I have my doubts about this working at all since I just read some post that this problem has been present for some as far back as the G1 and HTC Magic phones.

http://code.google.com/p/android/issues/detail?id=6406

2.6.35-rc6_AVS-925mV_CFS_1113Mhz_OldWiFi_072610.zip

If this doesn't work, I'm real sorry to have wasted your time.. :(

And I'd be more then happy to give back your donation :o

Oh, for those that are curious, I took the code from here.
[Nexus One Android Development] pakraider:
You're probably the most humble dev ever! How can you even think that you somehow have wasted our time? No matter what, your work and dedication has made my N1 experience vastly better and I'm sure I speak for everyone in saying that. Will try this kernel and let you know.

And you can drink the O.J.. if this kernel works, you might just get a bonus... we'll call it Tang? ;)
[Nexus One Android Development] damanrico:
There it is, I'm finally getting a 1 Mbps connection to my wifi using the 1707 CFS 1190 kernel.

So it seems like it's not related to the latest kernels. Although it took me 5-6 days to get it using the 1707 kernel, while I did get it after a few hours on the latest kernels. I guess that was just back luck. Going to the latest kernel now, since nothing holds me back now.
[Nexus One Android Development] overground:
Thanks!

Just wanted to drop a note and say thanks for all your efforts. Been using your kernels almost since the beginning. Got #101 Linpack for all devices using the "mega-oc" kernel...not really stable, but fun nonetheless. You respond to everyone in a timely manner and are never condescending. Keep up the great work...it is appreciated.
[Nexus One Android Development] skorpioneMM:
With the latest 1190 Mhz CFS kernel and for 4 days ago, i dont have any drop downs and any issues, i'm very happy with this kernel, i am using the SuperFroyo 2.4 ROM By Super@tmel and SetCPU in interactive mode and well, i am getting 47-48 MFLOPS constantly and i am in the 8 place off Top 10 in Nexus One category with 49.212 MFLOPS :D:D

Greetings!
[Nexus One Android Development] damanrico:
Wait, what am I missing here? SuperFroyo is only for the G1, right?
[Nexus One Android Development] pakraider:
No go with the test kernel either with the WiFi issue.. But obviously it seems like a stubborn problem that's been around for a while. Guess I'll cross my fingers for Gingerbread to patch it up. :) Thanks for the help, I'm back to your trusted rc6 800mV kernel. :)
[Nexus One Android Development] overground:
I'm thinking not with those kind of numbers.
[Nexus One Android Development] damanrico:
Yeh, can't find it for the N1 though. So don't know what he's talking about.
[Nexus One Android Development] skorpioneMM:
Nop, from 20 days ago, Super@tmel has starting to make ROMS for Nexus One, today he released a new version, SuperFroyo 2.6 and I go to try now :D.

You can find Super@tmel ROMS for your Nexus One here:

http://www.htcmania.com/forumdisplay.php?f=207

Greetings!
[Nexus One Android Development] wildmonks:
Thank you everyone for your feedback, both the good and especially the bad, and all your kind words. And special thanks to IR for posting his code on guthub.

It really puts a smile to my face to read this after experiencing a tough day work :o.

Happy to hear that the latest kernels are mostly working for everyone, and I will always strive to do my best. I also enjoy answering questions and discussions because I often learn something new and cool from them.

Again, thank you everyone!
[Nexus One Android Development] wildmonks:
It was a really long shoot but no harm trying :)

Yah, let's hope advancemenst to the wifi will happen often and soon.
[Nexus One Android Development] skorpioneMM:
Thanks to you, for your great and hard work, the latest 1190 Mhz kernel are awesome for me!!

In your next release, i donate to you again, i really apreciate your good work.

Greetings!
[Nexus One Android Development] ChronoReverse:
Flashed the 925mV CFS rc6 072410 kernel yesterday and so far it's running beautifully! Set at 245/1075 interactive governor.

Incidentally, a rom was released for our n1's with FM radio support! Do you think it would be a lot of trouble to make this kernel work with that rom?
[Nexus One Android Development] Amritttt:
i have installed a 2.6.34.1_AVS-925mV_BFS_1113Mhz_070810 and i want to install 2.6.34.1_AVS-925mV_BFS_1113Mhz_072210 so do i have to reinstall the rom and install it or is there a another way? and sorry if this has been asked before
[Nexus One Android Development] wildmonks:
I have been keeping an eye on intersectRaven's amazing work in enabling FM radio support. Unfortunately at this time, the code to enable FM radio will disable bluetooth and so this is the reason why I haven't included it yet. I do believe soon this will get perfected and that is when I will include it.

I can't really help out with the development of the FM radio support at this time as don't have the desire rom installed (I don't really like the desire interface :rolleyes:)

Edit: But it doesn't mean I won't make you, your own custom kernel with FM radio support. Tell me which kernel you like the best and I'll remake it with FM support ;)

You do not need to reinstall the rom. All you have to do is flash a new kernel again. This also applies to any of the other developer's kernels :)

I do recommend you make a nandroid backup just in case something goes wrong or you want to go back to your previous setup.
[Nexus One Android Development] ChronoReverse:
@wildmonks

You are a very kind person. I thank you for your offer but I actually only wanted the information you just provided =)

I will look forward to when the FM code is completed.
[Nexus One Android Development] wildmonks:
Heh thanks for the compliment :o. I too am looking foward to providing FM support for you all (without compromise).

And feel free to send any more questions my way (same goes to everyone out there). :D
[Nexus One Android Development] Amritttt:
You do not need to reinstall the rom. All you have to do is flash a new kernel again. This also applies to any of the other developer's kernels :)

I do recommend you make a nandroid backup just in case something goes wrong or you want to go back to your previous setup.[/QUOTE]

so i can flash any kernel i want nice thanks a lot
[Nexus One Android Development] wildmonks:
so i can flash any kernel i want nice thanks a lot

Well, any Nexus kernel. Don't go flashing kernels that are made for G1, Magic, etc, but I'm sure you already know this ;)
[Nexus One Android Development] knightnz:
He's obviously basing it off the current CM source judging by the presence of the lockscreen music controls, and even though my Spanish is pretty poor, I'm not seeing any attribution to Cyanogen or Koush etc. for any of their work. Could be another King Klick job. You need an account to see anything on there. Possibly just using the same kernel source as well as the current pershoot-based kernel in CM6 supports the same 1113600Mhz speed.

Feel free to correct me though, Google translate is blocked at the office ;)

Had the WiFi tethering going on my N1 for a couple of days straight to my iPod Touch so I can play "Words with friends" against a mate in Australia, I did have the odd sleep issue but overall it behaved pretty well, most of the issue was probably the iPod as it's got iOS4 on it which is a complete pile of Sh*t.
[Nexus One Android Development] mathieulh:
I have tested the 1190mhz kernel on the lastest cyanogen nightly a bit doing some extensive benchmarks (I got up to 46+Mflops in linpack) and it seems fairly stable on my phone, I haven't noticed any kind of issue with it, I wont use 1190mhz as a daily setting obviously, I went back to 1075mhz on interactive scaling now. I believe that those having issues with 800mv kernels (which is not my case) are the most likely to have issues on 1190mhz@1300mv though.
[Nexus One Android Development] wildmonks:
Thanks for your feedback! Ah, you bring up a good point as I have some minor issues with 800mV (cellular reception) and I can't use 1190MHz at all...
[Nexus One Android Development] mathieulh:
wildmonks when did you purchase your nexus one ? I bought a vodaphone version about 4 weeks ago or so, I believe that the first batches are more likely to have issues than the later ones because they are probably using more recent snapdragon processors batches as well
[Nexus One Android Development] wildmonks:
I bought mine in late early Feburary, I believe only a month after it was first released so yah, mine is from an early batch... :(
[Nexus One Android Development] mathieulh:
It's likely that earlier snapdragon cpus require require more power to work at a specific frequency than the newer ones would (considering how many 1ghz snapdragons have been produced for various devices over the last few months the production and chips themselves are bound to have been optimized thus more cpus produced with less defects. I would not be surprised if the lastest batches could clock as high as 1.5ghz though that would likely require to go passed the 1300mv which I would not advise.
[Nexus One Android Development] skorpioneMM:
The interactive mode don't work for me and for another people, when i put the SetCPU in interactive mode, all correctly, i can sende SMS, MMS, calls etc... but i found an issue with this mode when you are navigating in the browser.

After a few minutes navigating in some pages, my phone freezes and i need pull the battery and restart the phone.

More people are having this issue, i read this in the CM Nightly's post.

This issue occurs in any frequency off the CPU (998, 1057, 1113...) but only in interactive mode, i tested this issue for a lot off days and im 100 % sure that this are an issue with the interactive mode.

Greetings
[Nexus One Android Development] mathieulh:
Odd, interactive mode works great here.
[Nexus One Android Development] whoisthedrizzle:
Is there a way of determining the manufacture date?

Nexus One didn't exactly sell like hot cakes... As far as I know the ATT/TMO versions have identical hardware as far as the cpu is concerned. The Incredible got a 8260 - which has a higher capacity and can go to 1.5Ghz. The teardowns that were done shortly after release found the chips to be made ~ 10/2009. My bootloader is marker 12/19/2009 (no clue if thats relevant to hardware) but either way ~3 months from manufacture->my hands is really, really quick. 8260 devices have only been out for like 4-6 weeks. The only thing I can find with my googlefu about N1 w/ 8260 is a preliminary datasheet from late march listed as N1-SPRINT (from pdadb.net). The EVO prelim specsheet is from early April and are more or less the same short of a few specs and the TFT LCD. Looks like sprint's N1 became the EVO4G. Anway, rambling aside - an N1 bought in March was probably made in late 2009, same as one bought on day of launch.

Edit: Easy way to find out is just pull up the sysinfo and look at the specs
[Nexus One Android Development] skorpioneMM:
Are you sure?? You tested navigating about 30 minutes in various pages in the default browser?

I am sure if you do this, your phone freezing.

Certainly, what kernel and ROM are you using???

P.D.: I have this issue with the CM Nightly's ROMS and 1190 Mhz CFS kernel.
[Nexus One Android Development] wildmonks:
After just flashing the latest nightly, I gave this a try and I was able to freeze up the phone. I did a hard reboot (hold down power, vol down, and trackball at the same time) and toggled VM heap size. (Change to 24M, reboot, change to 32M, reboot. this is my way of fixing the the VM bug).

Now, as hard as I try, I can't get it to freeze anymore. Maybe this is just luck (probably) or maybe it has to do with the latest kernel I'm testing for release (unlikely) but it seems to be fixed. I'll continue to keep an eye on this issue.

BTW, I was able to get a dmseg log of the freeze and it said there was a kernel panic relating to the keyboard. But yah.. I haven't been able to reproduce this yet since I toggled the VM.

[ 1190.799865] capella_cm3602_ioctl cmd 1
[ 1190.802612] capella_cm3602_ioctl cmd 1
[ 1195.857818] batt: 94%, 4045 mV, -412 mA (-408 avg), 28.7 C, 1278 mAh
[ 1220.677886] keyboard reset
[ 1240.584381] Kernel panic - not syncing: keyboard reset failed, 1
[ 1240.584594] Rebooting in 5 seconds..
[ 1245.559936] Restarting Linux version 2.6.35-rc6-925mV-CFS-OC-Monks-TEST-072910 (root@monks-desktop) (gcc version 4.4.0 (GCC) ) #3 PREEMPT Thu Jul 29 09:43:46 PDT 2010
[ 1245.559936]

Also if you want to know what keyboard I was using during the freeze, it was SwiftKey Beta and I'm still using it now.
[Nexus One Android Development] skorpioneMM:
Yeah thanks for try this, yesterday, i try this a lot off times and the conclusion are that seems a issue with the CM6 ROMS an interactive mode, because i try freeze my phone with ondemand profile and my phone never freezes.

Now im testing interactive mode with the latest Rod ROM and at the moment, i can't get freeze my N1 :)

Now, I will continue testing this and later I will test your VM solution with the latest CM6 Nightly.

Thank you for answering and testing this, I already thought it was my N1 problem.

Greetings!
[Nexus One Android Development] wildmonks:
Ah ok, like you said its probably a CM6 issue if its not happening on Rod's rom. Thank you for reporting this, I probably would not have known about it otherwise :)
[Nexus One Android Development] skorpioneMM:
Ok after 20 minutes stressing my phone with the browser and after 2 or 3 messages off "Browser not responding. Waiting or close" my N1 has freezed with the Rod 3.5 ROM in interactive mode.

When i am in ondemand, performance etc.. i strees my N1 a lot with the browser, and this not happening.

If you notice, when you boot your phone in interactive mode and after a few minutes off stressing your phone, if you go to the Linpack aplication begins to make a stranger every time you test, the "Running" message dont appear and seems to be frozen every time you test.
[Nexus One Android Development] Kepster:
Hi! wondering if this kernel works with the current ENOM Froyo ROM? Cuz i tried the latest pershoot kernel and it makes my N1 reboot several times a day. I also use SETCPU on demand currently.

Also wondering which one to use CFS or BFS.. probably go with CFS.

Thanks!
[Nexus One Android Development] wildmonks:
Let hope CM6 moves towards being solid and stable in the near future and that future updates will be made to this very new interactive governor.

I haven't tested personally Enomther's rom but I believe he said it best about the use of custom kernels with his roms and using my kernels is no different.

That said there's been a number of reports that it works with Enom's rom but there are also reports of it having a higher battery drain then his stock kernels. My guess would be that AVS is interfering with battery optimizations he has made to his rom.

I think pershoot is very very close to fixing the FC/reboots on Enom's rom so you might want to wait till then (I think tonight he's going to release it)

If you do decide to use my kernel, then yes I recommend first using 925mV CFS.
[Nexus One Android Development] mathieulh:
I am on lastest nightly with CFS 1190 kernel on interactive mode and no freeze so far (and I use the browser a lot)