yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dracon6ai:
Got Gmail, Yahoo, Google currents, Google+, talk, drive, plus some more I can't remember on constant sync (over 165 apps). On 4g 80% of the time, auto brightness, Wi-Fi and GPS always on. Google Now enabled with everything enabled (with Maps keeping my location updated) and I still get 2+ hrs screen per charge with r295 stock settings. Got 3 1/2hrs yesterday by being on Wi-Fi most of the day. All with 14-15 hours off charge before it dies, stock Verizon battery.

With that said, quit worrying about trying to hit the magic 4 hour mark and just enjoy a awesome phone turned badass by Franco. :D

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] yellowdie:
*Sigh* Do you remember what happened last time I tried to replicate on your "issues?" Exactly. That was 50 pages ago. And now we have r295 because of it! lol So I'll mess with mine (take off my precious scripts) and see what I can break, I mean fix. :)
[Samsung Galaxy Nexus] amf100:
Ah, I see. I just use titanium to convert the system apps to user apps, but I use Autostarts to control the event (not just start up on boot, but all events) behavior for both system and user apps.
[Samsung Galaxy Nexus] yellowdie:
*Facepalm* I just uninstalled the app,

then

went looking for the /data/data/com.franco.Kernel folder.... lol *Noob* :eek:

---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------

Well the third and fourth one sounds like Franco's got a delay in there. That would make sense. Also, did you use Recovery or Autoflash? I wanna replicate the same.
[Samsung Galaxy Nexus] franciscofranco:
I promise I will take a look, might be something in the function I wrote to read stuff from files. As usual it sticks for me on all my devices.
[Samsung Galaxy Nexus] franciscofranco:
I dont control the order of my app boot service, its normal that it doesnt fire off in the exact second that the device boots.
[Samsung Galaxy Nexus] yellowdie:
Cool, good to know. Like Trickster has the "delay on boot" deal, I thought maybe you set something like that for the new stuff. :)

I just uninstalled the app and everything. Wiped caches and fixed permissions. Phone's rebooting now and I'll install the app and see if I can replicate. :)

Edit: Franco, when you first made your app, did you intentionally name it FKU? lol :p
[Samsung Galaxy Nexus] 5pace:
Oh my god, the kernel is so awesome! I am using the stock settings (the settings which come with r295).

Just a small feature request, to Francois:

Is it possible to export all the costumizations / settings made / altered by the users to SDCARD, in the kernel updater app? So that users could share their settings here. It would really be handy to have that feature as users could attach their exported file in here so that the people on the other end could download and import the settings into their phones. :)

EDIT: Sorry is this feature was suggested already.
[Samsung Galaxy Nexus] TEK112:
You could always use titanium to backup app data and use the built in send function to send it.
[Samsung Galaxy Nexus] osm0sis:
Yeah, I get that, but it's weird that it would show the stock kernel values, and THEN revert to your kernel defaults; or alternately show my saved ones and then revert. It'd make sense if it initially showed your kernel defaults (6/7/6/3) and then took 15 sec to switch to my saved settings (I tried 5/5/5/2 just to test), but not the other way around. So it's pretty bizarre. Thanks for looking into it. :)

I tried both at different times. Autoflash first, to no avail, and then tried the recovery flashable zip (minus sdcard binary like I usually do) since I knew franco has a simple cleaner.sh script in there which I was hoping might help. Also no dice.
[Samsung Galaxy Nexus] franciscofranco:
I have a better plan in the works. You'll see when its ready.
[Samsung Galaxy Nexus] 5pace:
I just want it to be handy. The user on the other end just takes the config file exported by another user and places in the root of SDCARD and imports it, as simple as that. Titanium is much of hassle as it includes placing the backups in '/sdcard/TitaniumBackup/' and then refreshing the whole app. It will be awesome if is integrated in the francos app itself. :)

Looking forward for them!

And yeah just a random question:

Are you on any kind of IRC channel / network, francois? If yes, please share!
[Samsung Galaxy Nexus] teriemer:
Follow the link in my signature. There you'll see the explaination ;)

My CPU freq. min is 729 MHz and max is 1228 MHz (I'm testing 729 for battery right now). But dude mann - I tell it's fast a snappy with these settings...
[Samsung Galaxy Nexus] yellowdie:
Yeah, mine showed the 10/5/6/2 defaults for the first few seconds, then changed to the new defaults of 6/7/6/3. Franco, you said the app doesn't have a delay, but when do r295's settings kick in? I'm guessing a few seconds after boot. Did the old kernel apply settings before boot somehow? Os, were you setting your stuff with init.d? Try setting the gov settings with a 30 sleep to leap frog the kernel settings.

I just changed the settings in the app and rebooted and they didn't stick on boot. Then I slapped myself, changed the settings again, checked the bloody box that says "set gov controls on boot" and it stuck after rebooting. Go flippin' figure. :p:silly: But then after a few seconds, it went back to r295's settings. So it sounds like the kernel itself may have some type of delay built in that's overriding the app's settings. But like you said, the min_sample_time is the setting I applied in the app, but the delay and load and timer settings went back to 6/7 and 3.

Franco, you said you didn't have a delay, but maybe a delay in the app is what it needs? Or less delay in the kernel itself (if you can change that).
[Samsung Galaxy Nexus] DigiK:
Settings to Franco Cloud, perhaps? :D

R295 utterly rocks, Franco. Any possibility of adding SIO scheduler to the kernel and separate screen on and off mins in the app? 192 is great for screen off but I do detect a bit of lag on user input compared to 384.
[Samsung Galaxy Nexus] osm0sis:
No, the only things I've ever set with init.d are color settings and my stable selective UVing. So the CPU and Governor stuff has always just been in the app for me. :eek:
[Samsung Galaxy Nexus] yellowdie:
That makes sense. Like I said, my app settings didn't stick either (except for the min_sample_time).
[Samsung Galaxy Nexus] swarm871:
My first 4 hours of screen on since i have the nexus.... Thank you francooooo!!!
[Samsung Galaxy Nexus] burner07:
i have a problem with incoming calls: when i get a call with my headset pluged in and i remove them and answer i get a very low volume in the earpice...
[Samsung Galaxy Nexus] shreddintyres:
toggle either mute or speaker phone and it corrects itself.
[Samsung Galaxy Nexus] lsv-1:
My phone just crashed in the middle of a phone call, I'm using r295 192-1.3GHz fsync off, ondemand - deadline 384MHz max screen off, logging off. I do not know how to get the kmsg or whatever is called, how can determine what happened?

Sent from my Nexus Prime JB 4.1.2
[Samsung Galaxy Nexus] TheKeeperOfPie:
Don't use 384 screen off. 729 minimum. When you're in a call, the screen can turn off and 384 isn't enough to keep the call going .
[Samsung Galaxy Nexus] fredryk:
Never had a call turn off on 384 screen off, and I've read about a lot of people using 384 on here. Can anyone else confirm this?
[Samsung Galaxy Nexus] michaelmotes:
I've experienced unstable behavior with less 729 screen off. Apps will crash, phone lags when re-awaking.

You can get kmsg by running these command in a terminal app:

su

cat /proc/last_kmsg > /sdcard/last_kmsg.txt

Do that the first time you boot after the crash.
[Samsung Galaxy Nexus] cpom1:
Thanks franco. Looking forward to it :)
[Samsung Galaxy Nexus] lizaSB:
I just wanted to drop a note and say thanks for all your hard work Franco! I'm currently using Minco v5 and R295 and this is easily the fastest, most stable and battery sipping combination I have ever had on my GNex -- and yesterday was my first full day using Minco along with the first charge cycle of 295!

After 1.25 days on battery, I've still got 5% battery left and I've used 3.25 hours of screen and about 1 hour of music playback through Spotify. I normally play several hours of music in a day, so this usage pattern isn't entirely normal; however, it is seriously impressive nonetheless. I'm confident that I could pretty much play 6 hours of music, in addition to normal browsing habits (1-2 hours screen) and still have charge left at the end of the night. In other words, you've given me the freedom to abuse my phone's battery and data plan :victory: I guess I'll find out soon enough though!

I'm not sure how you keep improving something that's already amazing, but you do!
[Samsung Galaxy Nexus] bigfnjoe96:
Outside of a radio dump, is there anything I can do for a weak signal when I'm @ work.

It's the biggest cause of drain for me.

Thanks

Sent from my Galaxy Nexus running Milestone 6
[Samsung Galaxy Nexus] nuwan32:
I've been using 384 screen off for about a week now and got 0 problems with heavy usage. It might be your roms fault
[Samsung Galaxy Nexus] SUTHRNFRIED:
I find that hard to believe its the ROMs fault IMO.
[Samsung Galaxy Nexus] 15israellai:
Just slept for 7+ hours and dropped from 92 to 67. guess I have some bull**** apparent running in addition to titanium.

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] Shadow-Nexus:
If you're using AOKP or CNA you might experience more lagginess and unstableness than in CM or PA
[Samsung Galaxy Nexus] franciscofranco:
osmosis and yellowdie can you both send me an email please.
[Samsung Galaxy Nexus] yellowdie:
Done. =)
[Samsung Galaxy Nexus] BigBake88:
Something tells me Franco is cooking us up something...:good:
[Samsung Galaxy Nexus] osm0sis:
Sent. Thanks!

*rubs hands together* :D
[Samsung Galaxy Nexus] franciscofranco:
Not this time, just trying to find out what happened with the boot service on the app...again :)
[Samsung Galaxy Nexus] Raijin:
This means, with Franco's Kernel, CM is more stable than AOKP? How much compared with stock?

Sorry for off-topic.
[Samsung Galaxy Nexus] jltorrente:
I used yellow's post and no luck, nothing works for me to get decent battery life.

I'm kinda sad, I keep seeing all those awesome stats and no matter what I do, I'm stuck with sucky battery life
[Samsung Galaxy Nexus] chickentuna:
Not one bit of a problem on CNA, Stock and CM. Not sure about AOKP but I've read that the latest aokp build is a little buggy. Was using franco 295 on aokp build 4 a few days ago and i have no lags or bugs(except for a few known aokp bugs).

My setup on franco 295 is all default except that I have undedclocked to 1036 and undervolted 192 to 690mV

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Shadow-Nexus:
It seems that have to many wake locks

Look for the problem that is causing this with better battery stats and correct it

It helps to use WiFi more than 3g too
[Samsung Galaxy Nexus] Leegalaxy:
My battery life is real good with r295
[Samsung Galaxy Nexus] cpom1:
Looks like Franco fixed the app. Thanks man. :D

Also for those running interactive can you post your governor control settings?

Also Franco on the next kernel update, can you make it so the sampling rate min when using on demand can be set 15000? Sorry if I'm being a noob.

sent from my Nexus Prime
[Samsung Galaxy Nexus] Dr Byte:
From the look of your own screendumps, it spent 4 of the 8 hours awake. Playing music?

Powermanager Service (ie, running Apps) had the phone awake for 1h 18m.

The first dump shows lots of apps' alarms waking the phone

Wifi activity kept it awake for 34m (possibly overlapping the above)

You were out of coverage/poor coverage for 6h (72.5%!)

The phone was "awake" for 4 hours, and half of that time with the screen on.

It only spent 4 hours (half the time) in "deep sleep"

The display was on for over two hours (that in itself is 50% of the battery)

It's no wonder it burned through the battery.

Any two of those would be bad news.

(Those of us who get <1% per hour spend 95% or more in Deep Sleep.)

Try

- logging out of Latitude/G+/disabling Google location

- Disable wifi/cell tower location (this eats a lot of power on my phone) but leave GPS on.

- Use a less congested Wifi network SSID

- Set the polling interval for your apps (especially the TV app) MUCH longer! 16 times per hour? REALLY?

- Posting the "partial wakelocks" screen from BBS next time :)
[Samsung Galaxy Nexus] klobkelosh:
I'm running the latest Franco kernel app on r295 on toro and the tcp congestion settings are no longer in the app. I've tried clearing app settings and reinstalling the app and no settings. Not sure what's going on, but thought I would pass it along for consideration.
[Samsung Galaxy Nexus] osm0sis:
f.KU 7.1.3 just rolled out on the Play Store, is that the one you're using? Try downgrading to M6 in the app, do the TCP settings show up again?
[Samsung Galaxy Nexus] klobkelosh:
Yup, I had installed 7.1.3. I downgraded to m6 as suggested but still no tcp settings. I also tried rolling back to a titanium backup of the kernel app and still no tcp settings. Odd. I've been auto flashing the kernels, gonna try a recovery install and see if the cache cleaner triggers things properly.

Odd. Thanks for responding osmosis.
[Samsung Galaxy Nexus] osm0sis:
Odd indeed. Well we just ruled out the kernel itself being the problem, and your TiBU restore ruled out the app. Are you running any init.d scripts or other kernel control apps? It could also just be some random derp of your ROM, though I don't understand how.

Hmm. Maybe uninstall the app, reboot to clear all the remaining settings in the sysfs and then restore the old backup from TiBU. That way you're sure you're doing so over a clean slate.
[Samsung Galaxy Nexus] klobkelosh:
No init.d scripts at all. No other kernel apps. I'm running bugless beast, so petty f'n close to stock.

Uninstalled app, rebooted, restored app version 6.9.3 from tibu....no tcp settings. Hmph.

Guess the next time I have a hankering to install a new Rom I'll see if it shows up in the settings. I was worried that it was a toro problem, since all development is tested on maguro.
[Samsung Galaxy Nexus] osm0sis:
6.9.3 might be too far back. Try uninstalling the app, reboot to clear all the remaining settings in the sysfs, clear cache+dalvik and then install from Play Store.
[Samsung Galaxy Nexus] klobkelosh:
No dice. Thanks for your help osmosis. I'm going to bed...maybe someone else had the same problem and will chime tomorrow.
[Samsung Galaxy Nexus] teriemer:
Check my signature + follow link to understand ;) That setting seriously kicks azz :good:

Battery is surprisingly good too, the performance considered. I have no lags what so ever and it's blazzing fast constantly. So far I got 1d 13h and 31% left with 2:02 hours screen on.

Max freq 1228

Min freq 729
[Samsung Galaxy Nexus] trailblazerz11:
Been endurance testing with 192mhz at 730mV. Seems stable so far 51 hours.

Really loving balance of battery life and performance on kernel. Surprise how long it spends at 192 and no lag. Maybe stutter playing music though.
[Samsung Galaxy Nexus] black_sith:
May I ask you which system apps do you deinstall?

Thx

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] venividivici87:
Here too... 192@775mV, I'm a quite careful on UV, but I've noticed stuttering playing music.

So set up max screen of and min_sample_time

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Schneewitzchen:
Hey franco,

got problems with your app v7.1.3. There are no settings which stick for me after reboot!

Tried with Milestone6 and v295! I uninstalled your app, busybox and supersu. After that i rebooted, wiped cache and dalvik, fixed permissions. Installed supersu, busy box and your app again!

I don't know what i've been doing wrong. If i remember it right i got no problems two or three app releases back.
[Samsung Galaxy Nexus] The Gingerbread Man:
Last night I think I might of had a sod, I undervolted 192 to 700mv and shortly after I got an email. The screen would not wake up but the notification led still kept flashing white as normal. So I take this is the sleep of death? Back to 725mv and all is working as normal again.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] punkeroso:
Someone managed to make init.d work on stock 4.1.2 JB (with franco kernel obviously)?

I created the folder and wrote this simple script:

#!/system/bin/sh
echo "it works" > /storage/sdcard0/test.txt

but isn't working.

I also gave 755 permissions to file and folder.

In the meantime, I'm testing r295 with 192 min freq at 700mV!!
[Samsung Galaxy Nexus] franciscofranco:
Thats odd. Are you waiting a few seconds after boot before opening the app? Yellowdie, osmosis and minooch tested the app and they all said the boot service was working correctly. I tested on 4 devices and it worked fine. No one reported problems with that either so far.
[Samsung Galaxy Nexus] Schneewitzchen:
Sorry only wanted to report that there is a bug on my phone. This was the first reboot after installing MincoV5 1 day after i was released. Within this time the only change i do was updating your app and write an init.d script to set 750mV for 192 slot.

Yeah i boot the phone then it stay's about 30 seconds on lockscreen until screen times out. Then unlock with pin, wait until screen gets off after 30 seconds another time. Then i open the app and no settings sticks, it's like when i install a new kernel, all settings won't stick not even cpu or governor.

I will make a nandroid now and install mincov5 on factory reset. Then i will report back if this helped for me or not.
[Samsung Galaxy Nexus] franciscofranco:
Very weird. Did you try removing that init.d script? Might be conflicting somehow I dunno.
[Samsung Galaxy Nexus] ChazzMatt:
Titanium Backup has busybox already, doesn't it? or does the Titanium Backup busybox only work with Titanium Backup? And he doesn't have a busybox installed for the rest of his system?

http://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-user-guide.html
[Samsung Galaxy Nexus] yellowdie:
I will get back to you on that. It's a long list.

Mine SODs at 700 as well. I like 730mV. :)

I would try the actual Busybox app and make sure that you have 1.20.2 installed to /xbin (not /bin). That's likely the problem.
[Samsung Galaxy Nexus] teriemer:
Confirmed - I lost my gov. settings too...
[Samsung Galaxy Nexus] klobkelosh:
Thank you master! Now it works. I feel so noob.
[Samsung Galaxy Nexus] kmjo29:
Install busybox
[Samsung Galaxy Nexus] franciscofranco:
Thats not the app, its something else I borked in the kernel init.
[Samsung Galaxy Nexus] Steve46xda:
Hi guys! Do you suggest to stay on m6 or flash lastest 295 nightly? I'm on minco v5.

What app do you use to undervolt? Is it better stay on smart reflex or find the optimal undervolt settings?

Can someone post a rock solid undervolt config for every frequency?

What value did you set as screen off frequency?

I know that are many answers, but I very would like to know how to optimize at best my phone?!
[Samsung Galaxy Nexus] androidkid311:
I was on lastest nightly and had 2 random reboots so went back to milestone 6 :)
[Samsung Galaxy Nexus] Schneewitzchen:
yep first thing was to remove the script...

Now i'm on a fresh mincov5 and got the same problem that the settings wont stick...dunno why!
[Samsung Galaxy Nexus] yellowdie:
Settings not sticking are a known issue and should be fixed in the next nightly. :)
[Samsung Galaxy Nexus] chickentuna:
1. Flash r295 you wouldn't regret it

2. Use franco app. Trickster mod is good too(I use it)

3. Do not bother under volting, franco has set the voltage to the optimal settings where he thinks the phone would be stable. Afterall the boss knows what's best:D. Right now we are testing 192mhz as min frequency under volted at 725mv(mine is 690mv). Screen off max is default 729.

We are getting quite good results in terms of performance, stability and battery life with the current config. r295 is just awesome
[Samsung Galaxy Nexus] shr33kant:
+1 to sio, I used to use that on my s2 and its a nice scheduler :).

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Schneewitzchen:
ok so this is kernel related? or kernel and app 7.1.3 related? its happening also on M6
[Samsung Galaxy Nexus] ajm786:
Someone already reported this earlier, but there was no resolution; with 295, I'm getting popping and clicking on audio, especially apparent when viewing YouTube HD videos. I've downgraded back to 290; I will test later tonight.

I'm not really running any custom settings; minimum CPU is 384 and I am not undervolting.
[Samsung Galaxy Nexus] gianton:
Same problem here too, settings not sticking on CNA 3.8.0 and r295 384.

Using TricksterMod app instead and settings stick OK after a reboot.
[Samsung Galaxy Nexus] haxor:
Franco why milestone 6 not having duel booting feature ? Have you heard about siyah kernel its on www.gokhanmoral.com
[Samsung Galaxy Nexus] BigBake88:
Look what I found when I searched the thread! ;)
[Samsung Galaxy Nexus] Tarun95:
192 MHz is giving me micro lags. Anyone else ?
[Samsung Galaxy Nexus] chickentuna:
kernel related
[Samsung Galaxy Nexus] punkeroso:
Here, when swiping in the menu.
[Samsung Galaxy Nexus] franciscofranco:
Dont you think trickster mod is conflicting with my app? Everything sticks on my device.
[Samsung Galaxy Nexus] tgyberg:
r295 is still rock'n for me. No wakelocks at all last night and just a straight line across for battery! Awesome sauce! :good:
[Samsung Galaxy Nexus] sk8oldschool74:
Are you running stock 295 or did you tweek it?
[Samsung Galaxy Nexus] tgyberg:
All stock settings and clocked at 1228. Almost the exact same the night before at 1536!
[Samsung Galaxy Nexus] marcocsh:
I have the same problem with r295. The popping and clicking are even more frequent when playing FLAC. The problem persist no matter screen on or off. :silly:

My settings are:

max cpu: 1228

min cpu: 384

max screen off: 729

Governor Control: 6/7/6/3 & hs 729 & ib 1036

I would really appreciate if anyone can point out anything wrong in my settings.:rolleyes:
[Samsung Galaxy Nexus] duduzinho15:
Franco i got some reboots :-$, its here my Last_ksmg can you help me? http://www.4shared.com/file/A2-Qcl1i/last_kmsg_2.html
[Samsung Galaxy Nexus] Hans QC:
How to find cause of laggy phone

Scrolling on my Galaxy Nexus is very laggy (it stutters when pictures appear in a list). And sometimes it takes more than 5 seconds to build the home-screen.

I tried all possible settings in Franco's app (yellowtie's high-octane settings, etc) but nothing helps. About a month ago it ran without any problem and I am not sure if this problem is kernel related.

How can I troubleshoot this? I googled but didn't find anything usefull.

I removed all widgets, ditched lots of applications but it still doesn't feel as snappy as before.

I am running r295 with Minco v5.

Sorry if this is off-topic.
[Samsung Galaxy Nexus] II12yanII:
core

I don't know that much about the governors and I was wondering which one to choose that puts one of the cores to sleep when the screen is off. I'm using the newest build r295
[Samsung Galaxy Nexus] sk8oldschool74:
Franco can I ask you an honest question??? Would you prefer people test your kernels as they are or tweek them? On r290 I noticed I had to restart my launcher a couple times a day and on r295 wifi not quite as strong but they are both smoother other than that...
[Samsung Galaxy Nexus] BigBake88:
Go with the default, interactive, as this is the best optimized governor for jellybean and the system automatically shuts down a core when it is able to do so. No need to force it with a governor. ;)
[Samsung Galaxy Nexus] kosmogon:
Confirm same here!

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] vinmoto:
Leankernel JB 4.5.0 also good
[Samsung Galaxy Nexus] gianton:
I uninstall your app (7.1.3) temporarily and tried TricksterMod app which sticks the settings.

I noticed that deleting the init.d folder, then settings stay with your app.
[Samsung Galaxy Nexus] BigBake88:
Great, go tell IMO :D