yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] intersectRaven:
Hmmm...I love smartass so maybe I'll get it in. :)
[Nexus One Android Development] momomok:
Thanks!

Love to see smartass vs SavagedZen :D
[Nexus One Android Development] Timdor:
Did you ever get this fixed?

From a quick glance, it looks to me like you're in a ****ty area for signal. Your cell standby shouldn't be that high.

If it's not fixed, I'd recommend hopping on WiFi and seeing if that helps. That, or just turn on airplane mode to determine if it's a rogue app that's eating the battery or if it has something to do with the signal on the device.
[Nexus One Android Development] Timdor:
This was a double post, sorry! :o
[Nexus One Android Development] schizophrenia:
unfortnately I have not yet picked up what is the cause of the battery problem yet

but I am now in another country roaming and I cannot get on any data/wifi

and after 12 hours, of not much using (the phone ringed once, no phone calls)

the result is:

80% left

Cell standby: 28%

Phone idle: 26%

Display: 24%

Maps: 18% (likely latitude)

Android OS: 3%

What do you think?
[Nexus One Android Development] momomok:
The savagenmod governor is great!

My N1 runs more smoothly than running in smartass. :P
[Nexus One Android Development] bimasakti85:
Whats the difference between smartass and savagedzen?

Sent from my Nexus One
[Nexus One Android Development] www1:
Finally I have AVS kernel working

I have made this

*please note the instructions...push the wifi driver BEFORE rebooting for flashing zImage...if your wifi is turned on when you reboot before you pushed the wifi driver for the kernel, there is a chance that you will go into a bootloop due to the incompatible wifi driver!

And now I can use with kernel AVS with cyanogen 5.0.6 test2

The version I use is 1000v but If this is stable I can try to use version with loss voltage.
[Nexus One Android Development] flojho01:
Thanks intersectRaven for your kernel.

I use the 800mV kernel with the conservative mode in Setcpu and it work perfect!
[Nexus One Android Development] r8zer:
im so unhappy, i tried your 800mV but unfortunatly kept rebooting to padlock screen, i have to use 850mv Nooooooooooooooooooooooo!! LOL, those 50mv's are gonna kill me, but on serious note ULTRA cool, working great on 850mv, on cm 5.0.6 test 3.

great work!!
[Nexus One Android Development] www1:
I have made some test And now my Avs kernel working good.

Now version 925.

Tomorrow I wrote the exactly metod for install kernel for have it to work on your n1.

Whis this method Avs kernel working in anti n1 I have try.

In first my n1 can't use avs kernel.
[Nexus One Android Development] rjhay22:
Your latest update actually made 850 stable for me... Rebooted a few times and it still works, before I cant even get 1 reboot out of it... Makes me wonder now if my phone isnt really taking the 850mV and below setting or maybe if you tweak just right, might work for me. Now testing the 825/800.

EDIT: 3:15PM - Flashed 825, stable so far.... after an hour I'm gonna push my luck and go for 800...
[Nexus One Android Development] intersectRaven:
Good luck to your tests! :)
[Nexus One Android Development] rabhw:
850 seems like my lucky number to get it to boot. Hopefully it stays stable with regular use. For reference, what were the min voltages for your avs and avs_xtra versions when you were doing those if you don't mind telling?
[Nexus One Android Development] sir*mez:
First time trying this out. I couldn't get anything lower than 875 to boot. 875 has been good so far. Further testing, let see if this beats 20hrs.+ that I got from kmobs kernel.
[Nexus One Android Development] rjhay22:
Thanks man, so yah, 825mV is the lowest I can go. 800mV wont let me go pass the X-Lock Screen... But thats an upgrade from the 875mV :)
[Nexus One Android Development] intersectRaven:
Just to clear things up, what kernel are you using? Yesterday morning's or evening? :)
[Nexus One Android Development] intersectRaven:
Back then I just stuck with the default minimum and maximum voltages of AVS which were 1000 - 1250. I then readjusted the maximum voltage to what our scorpion CPUs are set at stock which was 1275. :)
[Nexus One Android Development] rjhay22:
The most recent one, I could only go 875mV prior to that.
[Nexus One Android Development] intersectRaven:
Odd...the only change that had was the commits made by cyan...oh well...it's AVS' quirks... :p
[Nexus One Android Development] rjhay22:
Yes, that's why I don't understand, and I'm using Enoms ROM too if that makes a difference. But whatever got tweaked it surely is to my favor. Harhar!
[Nexus One Android Development] apacheo:
Just a question - is this available / is anyone able to drop the latest 825 mv kernel into a flashable boot.img or update.zip? I am away from my computer and I've flashed the latest cm5 test 3, and the standard kernel is going to kill my battery before I can get to a charger.. :/

ps. Not a noob, and know full well what these kernels involve - just don't have access to a machine I can fastboot from to flash the zImage :-/
[Nexus One Android Development] intersectRaven:
I'm definitely considering it. Unfortunately, I can't figure out the instructions to do so. :p Plus I've been quite busy recently which limits the time I could spend learning it. :o
[Nexus One Android Development] paulk_:
Would it be possible to set the maximum voltage for the AVS to something that has been tested to be working, such as pershoot or persiansown's values? That way, when the CPU is being fully utilized when surfing the web or playing a game, it'll still be undervolted?

Then again I could be wrong and it could be undervolted already.
[Nexus One Android Development] apacheo:
It's not particularly tricky, but (not having done it for a little while) I can't remember all the things you need.

Basically you need to extract a boot.img from a Cyanogenmod build, extract the ramdisk from that boot img, combine that ramdisk with the desired kernel using mkbootimg --base 0x20000000, and then that boot.img can be flashed onto the device from a command line (on the phone, without adb/fastboot).

But if you aren't confident doing it, then yeah, not worthwhile, because it can easily brick a phone such that it can only be repaired with fastboot anyway :P

(I'll just wait til I get home :))
[Nexus One Android Development] apacheo:
Actually, no I wont.

I'll do a nandroid backup of the current CM build with your kernel which will, amongst other things, create a boot.img.

Then I'll flash over CM5.0.6 test 3, and then just re-flash the boot img.

Sweeeet :)
[Nexus One Android Development] intersectRaven:
Hmmm...that certainly is do-able...I'll think about it. Thanks for the input! :)

I admire your resourcefulness. :cool:
[Nexus One Android Development] momomok:
I read from somewhere that savag is some sort of tweaked smartass.

Source:

http://ch33ky.site11.com/kernels/governors.txt
[Nexus One Android Development] Mayday_XL:
Smartass and savagedzen runs not smooth on my N1, only 460 Mhz.
[Nexus One Android Development] schizophrenia:
Anyone has any problem playing youtube on HD using the Youtube app? I can't play HD anymore using the app as the video stops on the first frame or skipping frames like crazy but the sounds is fine. It has nothing to do with the connection as I made sure it buffers everything already before I played the clip. I am on IR and CM7. Anyone has a clue what I should check? Thanks
[Nexus One Android Development] momomok:
Only 460 MHz? Can't it be increased further?
[Nexus One Android Development] Ertavarez:
i have problem with this kernel and Darktremor Apps2SD, taking random reboot and sometimes won't boot
[Nexus One Android Development] temasek:
No issue here.

I'm on latest IR kernel with DT A2SD datasd enabled on EXT4 with my self compiled CM7 Kang Rom.
[Nexus One Android Development] cr0wnest:
Works fine for me on CM7 nightly #94. Im on 128mhz minimum and 1136mhz maximum. Perhaps it has something to do with your setcpu profiles?
[Nexus One Android Development] Ertavarez:
Why takes so long to start the system with this kernel?:confused::confused:
[Nexus One Android Development] temasek:
Huh? Mine was fast.

I had just wiped due to testing of CWM3.2.0.1 which corrupted my EXT4 partition. So I tested the IR kernel w/o DT and was super fast. Then I flashed my DT script and restored my apps. It is still fast.
[Nexus One Android Development] sir*mez:
I don't know what your trying to say but you need to give more information other than just blindly complain about what you have done to your phone. I've been running IR kernel since the beginning and never had any problems. Please provide a logcat or a kmsg atleast to see what the issue is! Without that its a guessing game, like I can say, "oh its the speaker causing your system to be slow". Don't make it harder for the dev as its already hard enough for them.
[Nexus One Android Development] Treatcon:
If you're running Smartass or SavagedZen you should disable SetCPU profiles, from what I've been reading anyway.

New kernel is awesome!! Been using SavagedZen now for about 8 hours and it's amazingly fast and fluid. ZERO problems thus far!! Love it, thanks IR!!
[Nexus One Android Development] slavag:
New kernel on #89 CM cause all data lost after switched to savagedzen.

Did nand restore to revert to working system.

Also after switched to savagedzen is very hard to wake up the phone.

Very long system start.
[Nexus One Android Development] Mayday_XL:
Ok, thanks.
[Nexus One Android Development] slavag:
Tried again new kernel with the #95 build of CM,

got very strange behavior, I lost every settings, including system, security settings and data.

Looks like last kernel has some problems, before that every IR kernel worked like a charm.
[Nexus One Android Development] lolobabes:
wow this latest kernel seems even smoother and faster than the one 2 days ago, lets see what savagedzen can do, proud of you intersect! go PINOY! ahihihihi
[Nexus One Android Development] jameztcc:
Fast, smooth and stable on latest avs kernel and Savagezen. Only thing slow is my 'broadband' provider ;p that can't keep up with phone ;p
[Nexus One Android Development] Babydollll:
The newest AVS kernel seems to be running fine. 128mhz min 1036mhz max SavagedZen and I'm running a kang compiled by Temasek based off of one of the recent nightlies

(Cyanogenmod 7.1.0 RCO N1 KANG) thank you.
[Nexus One Android Development] cr0wnest:
Yup I completely removed all my profiles except the high temperature one (i want that as a fail safe since I'm overclocked) and when the battery is less than 30% and 15% (for emergencies in case I ever leave home without my spare battery)
[Nexus One Android Development] Mayday_XL:
No difference when i deactivate SetCPU. :confused:
[Nexus One Android Development] navahoo:
S-zen kernel kinda laggy for me too. But smartass working without probs. But someone may explain me the difference between those two governers and the ondemand?
[Nexus One Android Development] pen²:
Savagedzen seems to take too long to shift up, scrolling in the app drawer is a bit laggy if set from 128 to 998. Smartass seems to be better for me...
[Nexus One Android Development] bimasakti85:
+1

It's laggy with savagedzen.smartass is better for me.

Sent from my Nexus One
[Nexus One Android Development] intersectRaven:
I like smartass better too. SavagedZen seems to prefer staying at lower frequencies. :)
[Nexus One Android Development] momomok:
Governors are fun to play with.

I still prefer SavagenZen to smartass. :P

It seems to consume less battery when I am actually using the device.

I just hope there is a revolution in battery technology.

Sick of worrying about battery left of my favourite device...
[Nexus One Android Development] temasek:
I prefer........IR kernel and whatever that comes with it.

End of story :p
[Nexus One Android Development] evcz:
My phone is no longer able to run ir kernels... Basically everything FC randomly and corrupts /data/ content :(

On cm7 nightly default kernel runs ok...

Is my phone now requiring something more then just 925mv? :(
[Nexus One Android Development] SheridanJohn:
I had the same problem with FCing/corruption. Reverted via nandroid to older IR kernel and everything is fine...
[Nexus One Android Development] evcz:
I think I've started seeing this kind of problems with recents .8

previous .7 didn't had big troubles (except "wonkyness" certain times when using the smartass or the interactive governor)

I made no major change so I cannot find a path or refer to something specific as problematic.

the only certain this is that it's basically currupting everything on data... wipe google accounts, wipe twitter, wipe messages, keyboard crashing and so on...

this does not necessarily happens as soon as I boot it... yesterday it lasted 12hours befora going mad...

At this point I start having some relief: maybe it's not the voltage too low :D
[Nexus One Android Development] bimasakti85:
Happened to me once,after changing from tiamat kernel+vipermod undervolt extreme. So I fully wipe with temasek script,and its working smooth now. And I still use vipermod,but not the extreme mode because of randomly reboot.

Sent from my Nexus One
[Nexus One Android Development] bimasakti85:
Did you use DT A2SD? I think its related. Perhaps running a2sd repair will help this.

Sent from my Nexus One
[Nexus One Android Development] evcz:
never ever used app2sd :(

I always do a full format of /system and /cache before installing a new nightly/kernel.

I admit I didn't do a clean data as the problem get fixed by reverting back to another kernel or restoring an old nandroid backup if the /data/ corruption is "strong"

for example: this morning I was no more able to open gtalk and twitter, additionally google map and navigation were wiped from the phone..

left the phone charging the whole night (wifi disable, data disabled)

phone ringed two times (incoming sms), this morning woke up, unlocked the screen, tried to open the messages app and it FC... then re-tried and all the messages where gone... (lost those two... they weren't yet been uploaded to gmail using smsbackup+...)

anyhow after that navigation disappeared and any icon i would click 90% of the time would give me a FC and would basically mess up its data :(
[Nexus One Android Development] makelegs:
Check /system memory. Weird stuff like that happens when it gets really low, and these new builds take up much more /system space than did cm6. And even if you clear /system clutter, it returns after each flash..... Rinse & repeat

YMMV, tho... ;)
[Nexus One Android Development] evcz:
system was fine, 13mb free :(

redstar's 38.7 was working fine, tried 38.8 and got the phone messed up too :(

now formatted everything (boot, data and sdcard too) and will try a nandroid restore from older backup

//edit

decided to do a fullwipe with factory reset... will not restore the nandroid... hope this will sort everything out :/
[Nexus One Android Development] pen²:
I had the same problem. Couldn't even restore nandroid backup due to strange errors during restore. Did a full wipe by temaseks format zip (amon ra full wipe was not sufficient), after that i could restore the nandroid backup.
[Nexus One Android Development] Mayday_XL:
I have no problems with the latest kernel.
[Nexus One Android Development] evcz:
everything's fine here too with the latest kernels after a fullwipe...

restoring old nandroid backups (clockwork 3 recovery here) was failing as it kept resulting in a currupted system... something was really badly messed up :D
[Nexus One Android Development] temasek:
Time to downgrade your CWM3 to CWM2 or use Amon_RA Recovery
[Nexus One Android Development] sir*mez:
That was the problem Clockwork recovery 3+. It had nothing to do with IR kernel.
[Nexus One Android Development] pen²:
However, my problems with not being able to restore the backup were not related to cwm. I have always used amon ra... So the data corruption and possible corruption of system were somehow related to the kernel.
[Nexus One Android Development] SheridanJohn:
Regarding restore problem: I learnt that AmonRa won't restore if battery is below 30%. Only visible in log, on screen it only says "restore failed". Let me sweat heavily until I found out ;)
[Nexus One Android Development] makelegs:
Hmmm.... I think you may have just made sense of a predicament I ran into, not too long ago.

I freaking wiped b/c of it......DOH!!!
[Nexus One Android Development] lolobabes:
first flash of 38.8 deleted my contacts and messages. after flashing i set the governor on cm settings then i decided to reboot after boot contacts and messages were gone.... I am not sure though if it was bec of the kernel but now no problems anyway. ahihihihi
[Nexus One Android Development] mezmer1ze:
There's probably problem with SavagedZen governor, when my phone sleeps for some time and I get suddenly a phone call, I can't hear anyone on the other side or he can't hear me, it varies from a call lol. To fix it, I need to hang up and call back. Otherwise this governor has been great on my battery life.
[Nexus One Android Development] lolobabes:
so far so good hear, ahihihihi
[Nexus One Android Development] harmohn:
I'm REALLY enjoying the InteractiveX governor - thanks for including it IR :D
[Nexus One Android Development] intersectRaven:
Well, I found it with SavagedZen governor so I included it. If ever you know of other governors to include just give a shout here. :)
[Nexus One Android Development] ch33kybutt:
Find the following i2c bus errors in dmesg...

<6>[ 8.783477] msm_i2c_probe
<6>[ 8.783752] msm_i2c_probe: clk_ctl 35d, 100000 Hz
<3>[ 10.762481] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 10.762695] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 10.762817] msm_i2c msm_i2c.0: Error during data xfer 48 (-110)
<4>[ 10.763122] msm_i2c msm_i2c.0: Still the bus master, status a700, intf 0
<4>[ 10.763244] msm_i2c msm_i2c.0: i2c_scl: 1, i2c_sda: 1
<6>[ 10.763549] msm_i2c msm_i2c.0: Bus busy cleared after 1 clock cycles, status d0, intf 300
<3>[ 12.748413] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 12.748626] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 12.748748] msm_i2c msm_i2c.0: Error during data xfer 48 (-110)
<4>[ 12.749023] msm_i2c msm_i2c.0: Still the bus master, status a700, intf 0
<4>[ 12.749176] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<6>[ 12.749481] msm_i2c msm_i2c.0: Bus busy cleared after 1 clock cycles, status d0, intf 300
<3>[ 13.463348] msm_i2c msm_i2c.0: error, status 43c8
<3>[ 13.463470] msm_i2c msm_i2c.0: Error during data xfer 40 (-5)
<3>[ 14.207733] msm_i2c msm_i2c.0: error, status 43c8
<3>[ 14.207946] msm_i2c msm_i2c.0: Error during data xfer 18 (-5)
<3>[ 14.208648] msm_i2c msm_i2c.0: error, status 43c8
<3>[ 14.208770] msm_i2c msm_i2c.0: Error during data xfer 18 (-5)
<3>[ 14.209472] msm_i2c msm_i2c.0: error, status 43c8
<3>[ 14.209686] msm_i2c msm_i2c.0: Error during data xfer 18 (-5)
<3>[ 14.210388] msm_i2c msm_i2c.0: error, status 43c8
<3>[ 14.210510] msm_i2c msm_i2c.0: Error during data xfer 18 (-5)
<3>[ 14.211212] msm_i2c msm_i2c.0: error, status 43c8
<3>[ 14.211425] msm_i2c msm_i2c.0: Error during data xfer 18 (-5)
<3>[ 14.212127] msm_i2c msm_i2c.0: error, status 43c8
<3>[ 14.212249] msm_i2c msm_i2c.0: Error during data xfer 18 (-5)

Above errors are also present in kernels from pershoot and savaged-zen.

Wonder if they have any negative effects?
[Nexus One Android Development] intersectRaven:
I don't think it has any negative effects. It's been present ever since the upgrade to the .35 kernel versions. :)
[Nexus One Android Development] phewizzo:
IR any info on the .39 kernels?
[Nexus One Android Development] wind0zer:
2.6.38.8_AVS-CM7_CFS_20110608_2101.zip & cm_passion_full-99.zip is a power SIPPER! : )
[Nexus One Android Development] temasek:
17 hrs on air plane mode with latest IR kernel smartass governor = 95% battery left.

Woot! What can I say.....

Impressive kernel :)
[Nexus One Android Development] puttytatko:
3.0 folder is up on the iR site...!! cant wait to see the new kernel in action...brings a lotta improvements....
[Nexus One Android Development] momomok:
Crossed my fingers, patiently waiting :)

I wonder what's the difference between various kernel versions... :confused:
[Nexus One Android Development] intersectRaven:
I just put that there to test something. I'm not going to release a 3.0 kernel yet. :p
[Nexus One Android Development] schizophrenia:
i dont know why but with the latest kernel my phone occasionally restarts itself. but it is not a reboot as the uptime still goes on.
[Nexus One Android Development] temasek:
That is a soft reboot - I don't encounter that though.
[Nexus One Android Development] phewizzo:
I have a BIG feeling your gonna surprise us with something lol.
[Nexus One Android Development] Arrqh:
I'm still getting random data corruption on 38.8 and I'm not sure why. I cleared out /system before flashing this morning and I have ample space. Using amon_ra recovery. Tried with both a2sd turned off and turned on. I did a complete reformat and reinstall a few days back as well.

Everything seems to go fine after flashing but a few hours later data starts disappearing... call log, contacts, etc. Absolutely no problems if I restore back to a 38.7 nandroid backup. Most people seem to be running the latest kernel fine and I'm not sure how to track down what it is about my setup that is causing this. I'm running my own build of CM7 which lines up with nightly 96.
[Nexus One Android Development] evcz:
Try a data wipe (from the bootloader) I know it's a pain but it fixed all the corruption issues I had :(

(I suspect viber caused some troubles too... It was the first to wipe my contact list...)
[Nexus One Android Development] Arrqh:
I tried that a few days back (full wipe and reflash of everything) and the problem still persisted. I guess I can give it another go...

I did restore everything via Titanium last time so I suppose that it could have brought something other that caused it to happen again... but if that is the case then there's still something specific that's incompatible with the .7 vs. the .8. I'd really like to figure out what it is!
[Nexus One Android Development] temasek:
Make sure your TB is the latest version cuz recent updates of TB corrupts data. So if yours is latest TB now then its ok.
[Nexus One Android Development] lolobabes:
is it required to wipe dalvik cache when flashing a different kernel or a non issue? ty
[Nexus One Android Development] temasek:
Some kernel devs recommend wiping dalvik-cache but I've never wipe dalvik-cache and found no issue.
[Nexus One Android Development] lolobabes:
coz i tried flashing redstars kernel twice and on both instances it deleted all my apps except those came with cm7, good thing i had backup :confused:
[Nexus One Android Development] schizophrenia:
i dont think they "deleted" your apps.

it happened to me using IR kernel too.

there were a few times I flashed IR kernel and it ended up rebooting into a brand new home screen with none of my apps in it.

I flashed back to the previous one and it became normal again.

so it was the Kernel which was buggy and bypassed something.

of course, we reported it and IR fixed and updated his kernel and now everyone is happy.

so basically a kernel cannot delete your apps.
[Nexus One Android Development] Arrqh:
My TB was the latest.

Anyway, I did a full wipe and reflash this morning but without restoring any backups this time. Guess I'll see how that goes today!
[Nexus One Android Development] phewizzo:
Yes IR this kernel is still have the problem of deleting apps after a restart.
[Nexus One Android Development] sir*mez:
No problems here. I have all my apps, I update on nightlies everyday or whenever there is one and apply IR's kernel to it.
[Nexus One Android Development] Arrqh:
I've occasionally having problems still with data corruption. A few days ago my entire /data partition went corrupted during a reboot!

It seems to be connected to the governor... I had a few days of no issues and then all sorts of things started going wrong when I switched to interactiveX. I'm back to ondemand now and everything seems to be peachy again. If anyone else is still having issues, what governors are you using?