yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] mildlydisturbed:
66 hours

I'm beginning to suspect something is not getting cleared in the kernel. Today had it reboot at roughly 3 days uptime. This seems to be what's happening - works for 3 days and then reboots. Twice on the charger twice off the charger. 1 time with a phone call coming in (or perhaps they hit immediately after it rebooted) and 3 times without.

I mean, a reboot every 3 days is not bothering me (just reporting this for your benefit), but I sort of feel like the kernel gets sloppy on day 3. Perhaps a memory leak? Cleanup routine needed?

My phone's been off the charger ~29 hours

4.3.2 CFS NOHAVS NOSUV SBC

1.77 pri/nv

Sprintlovers

If there's anything I can run to monitor the kernel let me know and I will put it on and let you know in 2 days if anything is up.
[EVO 4G Android Development] kahluachno:
i've tried two kernels so far:

Netarchy Toastmod - 4.3.2-cfs-nosbc-havs-more

Netarchy-toastmod - 4.3.1-cfs-sbc-havs-more

when my phone is charging, some apps (i.e. dolphin browser, google maps, live scores) close unexpectedly during use. when it's not plugged in charging, the apps run fine. does that mean the kernel is incompatible with my phone? or is something else thats likely causing the crashing?

using retail charger, on myn rls5, hardware 0003
[EVO 4G Android Development] mildlydisturbed:
try a HAVS LESS, SUV, then NOHAVS NOSUV

I had a lot of weirdness go on with HAVS MORE daily, next to none with NOHAVS NOSUV. I also found I had better battery life with NOHAVS than I did with HAVS, but your mileage may vary
[EVO 4G Android Development] live2ride96:
+1. Every phone is different and mine does NOT play well with havs either.

Sent from my MikFroyo'd, custom Chogardjr'd Evo, plain and simple.
[EVO 4G Android Development] xHausx:
4.3.2 cfs-havs-more-nosbc and everything looks good, no random reboots. The first night I flashed it got stuck on the splash screen when coming back up but that was also the last time I was able to use that battery so I don't know if there was any connection there.

A dalvik wipe was all it needed for my phone to come back but the battery is still a paperweight.
[EVO 4G Android Development] Phillysphinest1:
Ive been waiting since yesterday to post this up. 16+ hrs unplugged is ****in great!!!!!!!!!!!! I'm estatic!!!!
[EVO 4G Android Development] diomark:
Anyone having issues with Bluetooth remote controls (avrcp) not working under 432 cfs less aggressive?

-mark
[EVO 4G Android Development] youngkalico:
what rom & kernel are u useing
[EVO 4G Android Development] live2ride96:
I don't know about that particular kernel as I'm using 4.3.1, but to start, I'd try un-pairing and then re-pairing your bt device.

Sent from my MikFroyo'd, custom Chogardjr'd Evo, plain and simple.
[EVO 4G Android Development] :
I hear you, this is the best thing ever for battery life!

Using 4.3.2 SBC MORE HAVS naked on Myn's RLS5 on my 004.

I love this:

Sent from my RLS5 Warmed EVO, fast & furious!!!
[EVO 4G Android Development] percboy:
Want to try that kernel as I `m losing about 18-20 % over night on RLS5 4.3.2 nosbc more havs.

Any problems with using a SBC kernel these days?

Need to adhere to special charging methods?

Thanks
[EVO 4G Android Development] :
Just to clarify, did your phone slept at all? Sound to me you have a wakelock issue, afaik that drop is not normal...

As for sbc, as long as you understand the risks, for me the benefits are far too great to ignore, just let it charge overnight and enjoy

Hope this helps ;)

Sent from my RLS5 Warmed EVO, fast & furious!!!
[EVO 4G Android Development] percboy:
Doesn't seem like any wake problems:

Up time: 18 hours

Awake time: 3 hours

Im assuming the "risks" you are referring to on the SBC is not using the phone while on charger. Also, you leave it on charger (trickle) everynight? That the advantage of a SBC kernel?

Thanks.
[EVO 4G Android Development] :
Ok, what about your pri? If youre in 1.90 that could be the reason for your drop, downgrade to 1.77 and check again.

And yes I leave it on trickle all night long, so far zero issues...

Sent from my RLS5 Warmed EVO, fast & furious!!!
[EVO 4G Android Development] wiicked26:
what are the risks excatly.. im kinda new to this whole thing
[EVO 4G Android Development] :
Well, there was an issue of batteries exploding due to the way trickle charge was implemented, but nothing was proven as far as I know, basically youre changing the way the battery hold the charge, sorry I can't explain it more detailed, but checkout ms's kernel thread for more info, all I know is that it works, have been using sbc for a month now and if my battery dies, I have 2 more to spare.

Sorry I can't post the link but I'm on xda app, cannot link it.

Take care

Sent from my RLS5 Warmed EVO, fast & furious!!!
[EVO 4G Android Development] wiicked26:
Gracias!!

so what other kernel would you recomend/ have tried that does not have the trickle charing for a semi medium to heavy user.
[EVO 4G Android Development] spork27:
I'm not new to Android or too rooting, but I am new to new kernels. And I've been reading up enough to know that is a newb question, so I apologize. I just wanted to verify that if I'm using netarchy 4.3.2 and I chose the More Aggressive HAV I shouldn't be using something like CPUTuner or SetCPU, correct? I'm supposed to just let the kernel take care of all that stuff, right?
[EVO 4G Android Development] Apo11on:
Custom kernels unlock the frequency modes, they do not set them. So yes, you're correct - you need to use a tool like SetCPU to overclock and set power profiles the way you like, unless you know how to do it manually.
[EVO 4G Android Development] chotabk:
correct. use the NOHAVS version if you want to use setcpu profiles.
[EVO 4G Android Development] netarchy:
Actually you're quite free to use setcpu with both. HAVS deals specifically with undervolting, not clock speed. Setcpu deals specifically with clock speed, not under/over-volting.

If you want to overclock, you have to use something like setcpu/oc widget (or a manual echo via shell which isn't particularly friendly) anyway.

The only real thing about setcpu that is debated over is the option to use profiles to define speeds in various situations (such as a screen off profile). Some people swear by them, others swear they do more harm than good. Even more debated is whether or not the profiles are bad on HAVS vs NoHAVS ;D

Personally I've not noticed an issue with using profiles on HAVS, but ofc your mileage may vary.
[EVO 4G Android Development] mildlydisturbed:
A few people using one custom kernel with SBC managed to fry batteries. Don't remember what kernel it was, but you can go to goodandevo.net and look a couple of weeks back about the debate and someone will point you to a page of 6 or so blown batteries.

AFAIK the failure rate on SBC and the failure rate of EVO batteries was not correlated. And I don't know what sort of increase it was.

If you're worried about potential battery bricking, don't install an SBC for a while. I'm at maybe 6 weeks with no issues, but your mileage may vary. It's nice to have that extra couple of hours, but generally I don't need it as with Netarchy's kernels I already have about a full 24 hour run on a stock battery.

Also with Net's stuff you can ease on over there as you feel more comfortable... step into the hot tub with

4.3.2 NOSBC CFS NOHAVS NOSUV (probably safest starter)

Have a glass of wine and perhaps slip off that NOSUV and go to a SUV

Feeling comfy? Ease on in further to the hot tub of kernel swapping with 4.3.2 NOSBC CFS HAVS LESS

If that works for you for a couple of days go to HAVS more

Swap it up to BFS and SBC if you ever feel like it. I liked BFS better but was having an issue with it and 4.3.2 so I went back to CFS.

Keep a few kernels on the phone and a nandroid backup and just swap as you want to try... pretty soon you'll be a kernel ho.
[EVO 4G Android Development] adrian2pm:
Can you get more out of SBC?
[EVO 4G Android Development] mildlydisturbed:
I get about 2 more hours battery and a much faster charge.

Your milage may vary
[EVO 4G Android Development] adrian2pm:
When should you UN plug when charging? The lowest mine went was 6ma
[EVO 4G Android Development] adrian2pm:
Net can we overclock byediting the maxCPU frequency with textpad does it work that way?
[EVO 4G Android Development] mildlydisturbed:
I unplug when I wake up Phone goes on when I go to sleep and off when I'm heading to work. Then it's off the charger all day. I don't pay any attention to it... sometime between 5 & 8 hours on a USB charger a night has been steadily increasing battery estimated life (by juiceplotter) for the past 3 weeks.

Looking at juiceplotter it appears that it's done a couple of hours before I wake up.
[EVO 4G Android Development] SpydaPig:
I'm really impressed with the battery life i've gotten with 4.3.2 cfs nosbc havs more. This is the first time i've ever gotten 5 hours of awake time. This was my results from a moderate to heavy use throughout the day. For me the unplugged time I could care less about its the awake time that really matters for me. I probably would have gotten about another hour of awake time if I didn't spend most of my time on youtube lol..This is definitely my kernel i'll be sticking with. Performance is also fantastic with this kernel, everything is running smooth and snappy and also everything works fine, haven't had any issues with reboots or anything of that nature. Thanks Net
[EVO 4G Android Development] adrian2pm:
Finally found the right kernel thanks a bunch net.

That's with stock battery. Amazing!
[EVO 4G Android Development] frifox:
I think it's safe to call v4.3.2 a stable build. Been running the CFS Less HAVS variant for few weeks now and it's still rock solid and performance has not degraded not one bit. Other kernels that I experienced problems with would usually start tripping out by now =P the battery life isn't the best I've seen with your kernels so far but it's still very acceptable compared to stock. I can easily get through the day.

PS: battery monitor says that while sleeping the phone is drawing about 100mA to 110mA. On one of your older kernels (don't remember which one exactly) phone would sleep at 60mA to 80mA with which then Evo would last at least 2 days before dying (but performance was quite unstable so maybe that was the tradeoff)
[EVO 4G Android Development] philly0128:
Unless I missed this hiding in the thread somewhere is anyone having a issue with 2.6.32.25 4.21 cfs havs more smartass where sometimes when your phone rings, it will not sure you whos calling until the call ends or if the # of the person shows up, it's hard to answer the call?

I'm running Fresh 3.5.1 both myself and myself are having this issue

2 of my coworkers who have newer evo's w/ stock rom, all I did was change the kernal and setcpu and they're complaining of the same issue.

I thought maybe it was because I had the setcpu off set to powersave @ 128, but when I changed it. it doesn't seem to do anything

if this has been talked about already.. sorry for another post on it. I'm hoping I don't have to leave this kernal, tonight I will try switching to maybe less havs.
[EVO 4G Android Development] strongsteve:
I am wanting to use 4.3.2 no havs, no sbc, no uv and would like to change the max cpu freq to 1113 permanently without using SetCPU or other software. Can I just edit some file or create an init script? How can I do this? Thanks in advance..

Nevermind.. got it..

#!/system/bin/sh

echo "1113600" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[EVO 4G Android Development] BuddaBelly:
I found out how long I could go on a charge by accident. My charger had came unplugged from the wall so i missed two charging cycles. I have just the stock battery.
[EVO 4G Android Development] minieod:
you can use collins_ph battery mod
[EVO 4G Android Development] robbyhousley:
So what do you do to get that kind of life? I use cfs more havs and the best I got was about 15 hours. Way better than stock, but no where near 2 days lol
[EVO 4G Android Development] live2ride96:
Not use your phone, that's what.

Sent from my MikFroyo'd, custom Chogardjr'd Evo, plain and simple.
[EVO 4G Android Development] SpydaPig:
Lol, I was about to say the same thing.
[EVO 4G Android Development] BuddaBelly:
Yeah the picks I took tell the tale. The only thing I do is check email and visit this site with a call

or two an hour. But even then I thought two days was pretty crazy.
[EVO 4G Android Development] Product F(RED):
4.3.2 more aggressive gives me the best battery life and performance ever with my 2600 mAh battery. No SetCPU either. On average, after about 9-10 hours, I'm still around 65-70% with medium usage.
[EVO 4G Android Development] live2ride96:
And that's the key is to find a means to get battery life that you're happy with. I bought extra batteries on ebay (legit oem ones) and between the 16-18 hours I get plus the possibility of am extra battery on hand, I'm perfectly happy. One person's medium usage is another person's heavy usage,etc. Kernels make a difference, but typically not night and day difference as far as I've seen.

Sent from my MikFroyo'd, custom Chogardjr'd Evo, plain and simple.
[EVO 4G Android Development] brol1k:
Mind posting a link to that?

Tapatalk'd on Evo
[EVO 4G Android Development] gpz1100:
brol1k, if you're referring to a link to the kernel in the post above, did you consider looking at the first page of this thread? :rolleyes:

If you're referring to the battery, please disregard this reply.
[EVO 4G Android Development] mildlydisturbed:
100% System usage

Hey Net, got a little bit of a hint on the 100% CPU usage issues I've told you about before.

Mine

Evo / Sprintlovers / hw 003 / 1.77 pri and nv

4.3.2 cfs sbc nohavs nosuv - lasts roughly 3 days and then 100% CPU usage

Hers

Evo / stock / hw 003 / 1.9? OTA pri and NV

Whatever the latest stock OTA kernel is

So roughly 3 days after my last 100% CPU usage I was having dinner with my wife who has a stock unrooted Evo with no similar software. My CPU pegged at 100% with android OS showing as 100%. I took her phone because I was trying to look something up and surprise - her phone was nearly unresponsive. I opened task killer on hers and OS monitor on mine and looked around. Her phone came back from the near dead and went back to being normal without any cajoling, mine stayed at 100% until I finally rebooted it.

So, other than that this kernel does not come back from the near dead, it seems to be doing the same thing the OTA does
[EVO 4G Android Development] stricklerjosh:
What's the difference really between the 4.3.1 and 4.3.2? I'm using 4.3.1 right now on Koni's elite rom and seems to be working pretty well.
[EVO 4G Android Development] gpz1100:
Conversion to this kernel

For several weeks now, I've been running the combination in my sig (evio 1.77 with ziggy's 1/15/2011 kernel) - along with some custom tweaks to the conservative governor settings and -100mV static undervolt.

Battery life has been very good, along with reasonably good stability except in one area. Accessing the internet (stock browser) immediately after a reboot would cause the device to reboot. It would get about 10-15% loading the page, stall, then reboot. This wasn't a huge deal, but bothersome as I like things to be as close to 100% stable as possible.

In trouble shooting, I attempted the -50mV as well as the no undervolting scripts thinking that during the time immediately after booting there are background tasks going on and lack of voltage is leading to cpu instability. Neither corrected the issue.

I didn't try the ziggy 1/21 kernel, but decided to give this one another try. After recovering an earlier backup, installed 4.3.2 cfs havs more (no sbc). The browser/reboot issue was gone. However, I did run into some strange issues following a subsequent reboot.

That is, the kernel is installed and phone booted. Use the phone for a few minutes, then do a normal reboot. After this reboot, the phone gets locked at the htc logo (not boot animation). This is a hard lockup requiring a battery pull to regain any control. In fact, until the dalvik cache was wiped, I could not boot back into the system.

So, I restored the backup again, reloaded the kernel, but this time, instead of doing a reboot, I did a power down. Few seconds later,powered back up into recovery and wiped dalvik cache, rebooted. Since doing this, no more hard lockups on reboot.

My guess (net you can clarify) is that somethings are changed after that first boot into the OS after the kernel is installed. In certain cases, this either corrupts the dalvik cache, or something else get corrupted, so that until the cache is cleared, any reboot or powerdown/restart without wiping it causes the hard lock.

I don't think it's governor related at all since the system is not even getting to the boot animation, but locking at the initial htc logo. Same for cpu voltage. This is happening right after that single vibration on reboot/power on.

Ultimately, it may be an artifact of the previous kernel even though dalvik cache was wiped prior to install.

Finally, some questions. Ziggy's kernel made use of static undervolting as defined in one of the vdd files generated by the boot script. You can't have havs and static at the same time, so something in the boot sequence defines that. Where is this defined, and how can I view the havs voltage table?

I notice that scripts in the /etc/init.d folder are executed as my sleep profile and governor tweaks are still functional. However, the undervolting script is smart enough to not engage - likely due to this line in the script

"if [ -e /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels ]; then

".

A different script also moves the dalvik cache to the /data partition. I wonder if that's the cause of the initial lockup after switching to this kernel..

Thoughts?
[EVO 4G Android Development] mildlydisturbed:
FYI Net - Interesting

Just dropping feedback in case it helps, had decided to try the 4.3.2 CFS MORE HAVS SBC. Had been running NOHAVS NOSUV SBC up until yesterday and other than it went to 100% cpu usage every 3 days had been fine.

Ran about 14 hours on the new kernel, noticed the CPU was at 100%, chose to shutdown and reboot and it came up and locked at the android loading screen. I did the standard boot into recovery clear cache/dalvik and after the longest boot ever was at a pc3600 setup screen and having issues.

Poked around a bit, looked like all the settings were gone and the rom was having issues, decided to revert back to my nandroid backup which worked fine.

I figure it was probably the more havs causing issues with the rom reading data, but it was an interesting crash. And since it also had been prefaced by the 100% cpu usage in android OS I'm pondering if they're connected in some sort of IO bottleneck / failure sort of way.

Anyhow, back to the old and no harm for me at the moment...

Oh yeah, the rom dev said the occasional need to wipe the dalvik on reboots looked like it was kernel related and not rom related and mentioned I should mention it to you.

Evo HW 003

Sprintlovers 1/26, pri 1.77
[EVO 4G Android Development] mildlydisturbed:
I and a few other people have the same exact issue on Sprintlovers currently
[EVO 4G Android Development] kenlperry:
FYI.. I'm also running the latest version of Sprint Lovers ROM, on HW 003, with PRI/NV 1.77. I currently run the 4.3.2 CFS SBC HAVS MORE kernel and I haven't had any issues. Right now my phone has been powered on for 96 hours, 19 minutes, and 47 seconds. I've had pretty amazing battery life lately with this kernel, 31 hours between charges over this past weekend(which included playing music while at the gym, texting, emailing, receiving twitter texts, making phone calls, taking pics and video, and copying pics and video to my PC wirelessly). No reboot issues and no lockups. Previously I ran the 4.3.2 CFS HAVS NOSBC, the 4.3.1 version, and the 4.1.9, and I didn't have any issues with those either. I guess it just depends on the phone in question.
[EVO 4G Android Development] kenlperry:
Also, just for comparisons sake, I actually had the lockup after reboot issue with the Sprint Lovers ROM when I had the stock kernel. It would do it almost every time I did a reboot and I'd have to pull the battery to get it to boot. I re-installed the Standalone without wiping anything and the problem cleared up. And I never had it happen again, even with any of netarchy's kernels(I've tried about 5 of them). I've never had that reboot issue again.... knock on wood!
[EVO 4G Android Development] stricklerjosh:
4.3.1 cfs havs no sbc is working great for me on koni's elite rom. Got over 24 hours on moderate use. Thanks net for the great kernel.

Koni's elite is where its at!
[EVO 4G Android Development] SpydaPig:
How did you go about doing that by changing the max freq? Did you use terminal or just change it through root explorer?
[EVO 4G Android Development] gpz1100:
Just create a file in the /etc/init.d folder

call it something like 01overclock

For the contents, paste the code above

#!/system/bin/sh
echo "1113600" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

I believe the numeric part is necessary for the filename as it sets up the order in which init files are processed [?].
[EVO 4G Android Development] SpydaPig:
Alright i'll try that. But another question is can I just edit the freq number in /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq through root explorer? or is it just the same thing as making a file in the /etc/init.d folder?
[EVO 4G Android Development] gpz1100:
NO NEED TO QUOTE IF RESPONDING TO A POST DIRECTLY ABOVE!!!

Assuming you have nothing that modified that file, you can edit it directly. However, before moving forward, i'd check the contents of your init.d folder to make sure there are no scripts in there currently that modify the cpu settings. On that note, if there are no scripts, you would also need to check to make sure the file is retained between reboots.
[EVO 4G Android Development] SpydaPig:
Thanks gpz, i really appreciate the help. Sorry for the noobish questions, I've never tried changing it manually but I'll do it your way by making a new folder in the /etc/init.d/ folder. Last question though so if I want to revert back to 998 freq do I just delete the folder and what checks should I make in the persmissions?
[EVO 4G Android Development] gpz1100:
You're making a new file, not folder within the init.d folder.

Looking at other script samples, no permission changes are made. Thus, I don't think there are any additional permissions being set on the files other than whatever gets set by default at creation. And yes, deleting it should revert back to default.
[EVO 4G Android Development] SpydaPig:
alright I just made the file and it worked, thanks for all the help gpz. I didn't know it was that easy lol..
[EVO 4G Android Development] adrian2pm:
whats the difference between changing it manually than creating this file?
[EVO 4G Android Development] gpz1100:
I believe there are certain files within the file system that are not retained between reboots. I don't know if this is one of them or not. If it's not, then you'd need something the equivalent of an autoexec.bat (thus the init.d folder) to recreate it after each reboot.

Also, it's more convenient, and is probably convention to have anything that changes the operating environment located in one place than scattered throughout the file system. 6 Months later when a chance is necessary, you only have to remember to look in the init.d folder at the boot scripts than try to remember where all the individual files are at.
[EVO 4G Android Development] SpydaPig:
Oh yeah I forgot to mention I did have to make changes in the permission because it wasn't reading it at first. I had to check the execute checkboxes.
[EVO 4G Android Development] blkcamarozr28:
Notes for Revision 4.3.2

- SD card read ahead fixed, higher class SD cards should

have an easier time reaching their potential speeds

Is this the same SDCard tweak that is in the forums? Where readahead is set to 128?