yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bigbiceps:
amazing battery life!! better than trinity :)

i had issues with trinity with android os consuming all my battery juice,

now that i have franco, nothin can stop my gnex!!

thanks frankie :) :good:
[Samsung Galaxy Nexus] prembox:
Revert to R348 until the issue is sorted out...

---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------

Yes, WiFi drivers are always part of the Kernel.....but there would myriad reasons while you could be getting low WiFi signals...if only you elaborate a bit more on the problem...
[Samsung Galaxy Nexus] allgsmnetwork:
Flashed zip 355 no error :good: thanks francisco.franco :)
[Samsung Galaxy Nexus] franciscofranco:
r356:

* More stability fixes - reverted all interactive patches to match r348 state

* Add static volume boost to headphones - now we have respectable sound!

Thanks for all the testing in the latest versions, I'll contact Todd Poynor (Google kernel engineer) and try to see what was causing the slowdowns etc
[Samsung Galaxy Nexus] shawnaye:
I'm sorry franco. Does that mean that got the interactive gov, everything is the same as it was in r348?

Meaning that the only difference from r348 and r356 is the volume boost?
[Samsung Galaxy Nexus] franciscofranco:
Interactive is the same as on r348.

No, I changed some other things not worth mentioning here.
[Samsung Galaxy Nexus] razvanultra:
I am using a Linksys E3200. After the update from 4.1.1 the problem remains. The connection has a 65Mbps link immediatly after connecting, but right away drops down to 5Mbps and become unuseful. I've tried another type of router, from Dlink825 with the same result. As I want to mention, I had no problems with other phones (LG with Android 2.3.4) in the same positions.

I'll try another kernel version. thanks
[Samsung Galaxy Nexus] allgsmnetwork:
Twice has restarted the 356 but I have changed the governor as osm0sis hs in 1036 and ipf to 729 will be for this? UV as always - 50 mV
[Samsung Galaxy Nexus] franciscofranco:
Stock Wi-Fi drivers here, 0 changes.
[Samsung Galaxy Nexus] haxor:
So many test build and nightly till Christmas due to slow down.....really appreciate Franco hard work !
[Samsung Galaxy Nexus] prembox:
As far as I know all other Kernels use the same ....i.e. Stock WiFi drivers... Did you check your Router's security type and changes it to something else??.
[Samsung Galaxy Nexus] allgsmnetwork:
another reboot this time I left governor normal UV happens when I go back to 348 for now sorry for your work :(
[Samsung Galaxy Nexus] llevo3:
bro, I don't understand you anything, but I'm sure Jesus knows
[Samsung Galaxy Nexus] shawnaye:
Think he means that 356 has rebooted twice after he changed his settings according to osm0sis config.

Your English could be improved too :D

"bro I don't understand anything you say, but I'm sure Jesus knows."
[Samsung Galaxy Nexus] AndyGnex:
At least his is comprehensible.

Well anyway, im guessing he copied osmosis' settings without actually testing what voltages are stable for his phone

delivered by FedEx
[Samsung Galaxy Nexus] llevo3:
you got me :D
[Samsung Galaxy Nexus] haxor:
* Add static volume boost to headphones - now we have respectable sound!

Its just patch or I have to enable it from f.Ku ?
[Samsung Galaxy Nexus] Phoenix Wright:
I think I understand what the jesus guy said, since I'm Italian too :P

He said that it reboots with -50 mV undervolt and osm0sis's kernel settings. I can vouch to that, unfortunately... and without any undervolt at all.

Here's the init.d script I used:

#!/system/bin/sh

# File System Mounts for I/O performance
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nodev,data=writeback,barrier=0 -t auto /system
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /data
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /cache

echo "cfq" > /sys/block/mmcblk0/queue/scheduler
echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle
echo 0 > /sys/block/mmcblk0/queue/iosched/back_seek_max
echo 0 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty
echo 0 > /sys/module/sync/parameters/fsync_enabled
echo 1536000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 729600 > /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq
echo 1350000000 1350000000 1950000000 > /sys/class/misc/colorcontrol/multiplier
echo 0 0 0 > /sys/class/misc/colorcontrol/v1_offset
echo -24 > /sys/module/panel_s6e8aa0/parameters/contrast
echo "westwood" > /proc/sys/net/ipv4/tcp_congestion_control

And I added just one thing to the ramdisk in init.tuna.rc:

write /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq 1036800

The phone just keeps rebooting, after some minutes of usage. I tried reverting the few changes Franco made to the ramdisk between r348 and r356 but no dice. Also, r348 doesn't reboot with r356's ramdisk.

Here's the last_kmsg.
[Samsung Galaxy Nexus] allgsmnetwork:
For me better 348 i tested all latest kernel...348 max stability,max benchmark point,battery,and other why change?

Sent my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] haxor:
r357 coming soon....bcoz r356 also having reboot issue :(
[Samsung Galaxy Nexus] allgsmnetwork:
Are the initials of hispeed_freq (hs) and (ibf) input_boost_freq the governor in franco.kernel updter :)
[Samsung Galaxy Nexus] llevo3:
lol it was just a joke
[Samsung Galaxy Nexus] djdeeles:
awasome sound! thanks franco i've never had any sods with this kernel except 355
[Samsung Galaxy Nexus] The Gingerbread Man:
The perfect xmas gift I've been waiting for this, thanks so much just can't wait to get off work to try it :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] haxor:
The static sound boost is default activated to headphone or we have to activate it ?
[Samsung Galaxy Nexus] MaLiXs:
I hope this boost will not mess up with xlouder

Envoyé depuis mon Galaxy nexus avec XDA premium
[Samsung Galaxy Nexus] djdeeles:
@amit.meena05 its activated.
[Samsung Galaxy Nexus] numb_:
Flashed r356, rebooted, opened the app drawer and got a SOD..

This is my last_kmsg..
[Samsung Galaxy Nexus] eriksengh:
First of all thank you Franco for making our GN´s what they really should be from factory. Amazing transformation with your kernel vs stock :)

I have one small problem with your app. My OC settings never get stored, also if i try to change my download path i get this error: "This directory does not exist you have to create it first..." even if i try to use the standard: /mnt/sdcard/

I suspect these problems could relate to each other?

Running latest app and kernel 13.

I´m currently on Bigxie´s Build 9 witch i believe is already rooted. Cleared data, cache and dalvik before installing rom, so that should not be it.

Hope someone has got an answer to this.

Thanks

Geir Helge
[Samsung Galaxy Nexus] Vangelis13:
Try uninstalling and / or clearing the app cache?
[Samsung Galaxy Nexus] DJTaurus:
I also have stronger wifi signal with 13...

Sent from my blazing fast Galaxy Nexus!
[Samsung Galaxy Nexus] eriksengh:
Just did and still no go.

But thanks anyway :)
[Samsung Galaxy Nexus] slg60:
GPU Overclock @ 384 in Nightly 13?
[Samsung Galaxy Nexus] Juno-First:
Is it ok use this kernal with the aokp rom, thanks.
[Samsung Galaxy Nexus] zephiK:
Yes, it's compatible with any 4.0.3 ROM. And it's kernel not kernal.
[Samsung Galaxy Nexus] gn00my:
No deep sleep
[Samsung Galaxy Nexus] bradm23:
Looks like you have an app not playing nice. I get deep sleep and didn't even wipe anything, just a #12 flash over
[Samsung Galaxy Nexus] zephiK:
Deep sleeps for me. It's most likely a bad app.
[Samsung Galaxy Nexus] gn00my:
No nothing .Will look further
[Samsung Galaxy Nexus] zephiK:
try looking in partial wakelocks... not kernel
[Samsung Galaxy Nexus] jetrii:
I have the same issue. What ROM are you running?
[Samsung Galaxy Nexus] gn00my:
Also nothing wierd
[Samsung Galaxy Nexus] kecinzer:
Yes, I also think that lag is because autobrightness. But I using this feature :(. Can you Franco look at it?
[Samsung Galaxy Nexus] esoomenona:
I had this problem as well. I dropped the /mnt and just went with /sdcard/xxx
[Samsung Galaxy Nexus] gn00my:
Using Manhattan rom
[Samsung Galaxy Nexus] gn00my:
Never mind, is there now. Just took some time i geuss
[Samsung Galaxy Nexus] franciscofranco:
Not kernel issue as far as I know, auto-brightness **** is handled in the rom. I can't fix everything lol
[Samsung Galaxy Nexus] deezid:
Nice 3D improvement!

Slowdowns in Hot Pursuit and Riptide are gone :)
[Samsung Galaxy Nexus] shawnaye:
think he had an inactive screen.
[Samsung Galaxy Nexus] AndyGnex:
Probably got it confused with a freeze..or sudden reboot. :D

delivered by FedEx
[Samsung Galaxy Nexus] Khizar:
dont wanna be rude but..do you have any idea what a SOD is? SOD aka Sleep Of Death is when after the phone goes to sleep you try to wake it but it doesnt wake up and then you have to do a battery pull
[Samsung Galaxy Nexus] sajty:
You are right.Only Chuck Norris can have SoD while screen on.
[Samsung Galaxy Nexus] AndyGnex:
:eek: we have Chuck Norris as an XDA member?! :eek:

delivered by FedEx
[Samsung Galaxy Nexus] le_prof:
Still running 355 on stock 4.2.1 and running great so far. Will stick with it until I encounter any problems... Thanks Franco. And Happy Holidays to all!
[Samsung Galaxy Nexus] lesp4ul:
Close enough but...
[Samsung Galaxy Nexus] Langduscher:
Lots of SoDs, freezes and random reboots on r356... not able to post ksmgs sorry.

It's worse than last few builds. Going to clear fKu app data & cache and try again.
[Samsung Galaxy Nexus] joeyfong:
which schedule are u guys using?
[Samsung Galaxy Nexus] marshy73:
Been on r356 the moment it was released.

Been nearly 6hrs of heavy use as of this post.

So far no issues for me. r356 feels just like r348.

If the cause of all these issues were due to the new Google patches that Franco built-in from r350. Then r356 should not have these problems since Franco has removed these patches altogether.

Anyways, going to zzzz land now. Will wake to see if anything happens with r356.
[Samsung Galaxy Nexus] allgsmnetwork:
The 356 does not support UV and restart :(
[Samsung Galaxy Nexus] :
I think the changelogs are not as complete as they could be.
[Samsung Galaxy Nexus] X1iser:
last_kmsg with 356 after reboot :good:
[Samsung Galaxy Nexus] allgsmnetwork:
Without UV reboots?

---------- Post added at 05:45 PM ---------- Previous post was at 05:26 PM ----------

Have the UV or voltages stock?
[Samsung Galaxy Nexus] Angelakaro:
Sorry cause i'm late,but i'm still on r350 without any issue. Going to post again if there are troubles

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] Charmacas:
348 worked nice but had some lags when switching or opening apps.

With 356 these works much better. ;)
[Samsung Galaxy Nexus] bradm23:
Just wanted to report that 355 is by far the best battery and smoothest I've ever seen. It has been running great minus one slow down i experienced last night which was very strange. I have never seen anything like that before. During the slow down i was getting screen tears also. Hopefully Franco will find out that the bug was caused by something weird in 350 and not the Google patches because i noticed a big difference. I'm running osmosis settings as a reference point
[Samsung Galaxy Nexus] miqz:
using r356 with xylon 14-1 for 1 hour..so far no SOD or freeze like previous version..

using standard voltages

thanks fransisco for make a good kernel on holiday..
[Samsung Galaxy Nexus] shreddintyres:
No offense but you clearly have no idea what you are doing when you are undervolting. Forget undervolting let SR do its job or undervolt correctly according to the numerous guides out there on XDA and otherwise. If you wish to continue complaining about UV reboots etc, you need to start pulling logcats and last_kmsg's so you and others can discern if the cause of the problem is a bad UV by you or because of the kernel itself, ive been running 356 since release and have had no slowdowns, no SOD, and nothing otherwise to report other than another awesome job by Franco. My only changes to kernel settings are increase from 1228 to 1305 max, and change tcp algorithm from cubic to westwood. everything else is as the kernel ships.

Please either learn more and determine whether or not your original uv settings were stable in the first place by Undervolting properly (on your own) or stop commenting about UV and let SR do its job

- Cheers
[Samsung Galaxy Nexus] alexdemonumber3:
Did you try disabling SR? I did that and I'm getting crazy good results. R356 seems amazingly battery efficient
[Samsung Galaxy Nexus] Fenvarien:
Using r356 with UV since release without a single reboot or SOD. Perfectly stable and smooth :)

GNex with franco.Kernel r356 / CM10.1
[Samsung Galaxy Nexus] MizzouBrent:
No issues for me on 356 either. I haven't touched any settings at all since flashing except for I changed the color a little.
[Samsung Galaxy Nexus] OtavioMalzone:
How to enable hotplug at fk APP??
[Samsung Galaxy Nexus] bradm23:
Lol. Just use interactive gov and it will hot plug itself
[Samsung Galaxy Nexus] OtavioMalzone:
Op says that flu can enable hot plug.. I think that interactiveX hotplugs, Interactive not....
[Samsung Galaxy Nexus] sk8oldschool74:
Why do people post pictures when a charge has obviously taken place???
[Samsung Galaxy Nexus] bradm23:
I'm guessing that is very old. When francos app was first released it was only one of very few functions it could do. Since then the app has came a long way but it no longer controls hot plugging
[Samsung Galaxy Nexus] Tito2007:
Went from everything OK settings on r348 to r356 and my music would stop playing from instantly to around 5 seconds. I didn't change any settings ..pretty sure its the static volume feature.
[Samsung Galaxy Nexus] franciscofranco:
I can't reproduce that, heard music for over 1hour no stops...

Anyway I don't understand the problems users been having... please stop undervolting and let Smartreflex do its job.
[Samsung Galaxy Nexus] ChosSimbaOne:
Chuck Norris is not a member of xda, Chuck Norris allows xda to exist :P
[Samsung Galaxy Nexus] Tito2007:
thanks for responding .. was that hour using and auxiliary port??? I went to r355 and everything is OK again.. I changed NO settings whatsoever ..just flashed the image using your app. I'll try r356 again later. Thanks again
[Samsung Galaxy Nexus] timbck2:
Why do people post battery life pics at all? It seems ridiculous to me.
[Samsung Galaxy Nexus] jcmm11:
But but but undervolting is kewl and let's us get into all sorts of trouble we don't understand! :confused: Much more fun that way :p :eek: :rolleyes: :D
[Samsung Galaxy Nexus] osm0sis:
I guess because "pics or it didn't happen" ;)
[Samsung Galaxy Nexus] confyzone:
This is my first ever custom kernel aside from what comes with the roms and I have gotta say I love it
[Samsung Galaxy Nexus] _chanstar_:
I had reboots on r356. I didn't have any issues on the previous builds. Not too familiar with logcats yet but I'll try to post next time if the issue re-occurs.

The only difference I did this time compared to the last builds were:

1) Left CPU to set on boot checked. [192MHz-1.5GHz]

2) Auto-flashed the Kernel from FKU after downloading the zip.

The previous builds, I had all set on boot options unchecked and manually flashed the zip through recovery.
[Samsung Galaxy Nexus] whitedragonz83:
Flashed r356, adjusted voltages as I usually have done, decided to uncheck 'set to boot' options and just go pure Franco-stock goodness. Upon rebooting my phone it froze and rebooted again 10-20 seconds into loading the lock screen. Here is my kmsg. Hope it is useful.
[Samsung Galaxy Nexus] allgsmnetwork:
I always leave SR osm0sis active as I said I would use it to 1536 mhz and UV values ​​are the same I used with 342.345 and 348 since I tested the kernel 350,355 and 356 with the same UV values ​​I had reboots do not understand. .. maybe you have to change the UV values ​​... I have to test better ... I do not offend friend :)
[Samsung Galaxy Nexus] osm0sis:
MPU Watchdog reset. No real reason why other than something went wonky so it rebooted.

r356 has been excellent so far, though I notice one odd thing; not so much an issue as a point of interest, but one of my voltages became borderline all of a sudden with r356 where in previous versions it had been stable. It was my 1036 MHz (also set as hsf) voltage of 1050. Got two freeze+reboots with it, so I bumped it up to 1075mV and not a problem since. Odd that a voltage could suddenly become borderline.

Anyway, managed to grab a complete set of logs (alogcat + kmsg) during my last slowdown on r355 before updating. Maybe you can forward them to Todd. They seem like great examples of this HSI and CPBOOT stuff that always coincides with a signal drop and the slowdown.
[Samsung Galaxy Nexus] Phoenix Wright:
I didn't undervolt... I posted my config here (everything via init.d). Hope it can be fixed...
[Samsung Galaxy Nexus] timbck2:
Yeah but who cares if it "happens" or not? (Well obviously a lot of people do, but I'm not one of them.)
[Samsung Galaxy Nexus] splus:
Had a freeze and then reboot as well on r356 while using GMaps, just 5 min after flashing it. Haven't had reboot with any previous kernels versions.

No UV, interactive 384-1305 MHz.

How do you attach last kmsg from Tapatalk?? I'm on the phone...
[Samsung Galaxy Nexus] osm0sis:
For reboots we'd want the /proc/last_kmsg file copied from after the reboot occurred. :good:

Like I suggested a few pages back to someone using Tapatalk, try uploading it to cloud storage and then link it. Might be simplest.
[Samsung Galaxy Nexus] franciscofranco:
I don't know whats up with the voltages, I don't change any voltage thing since r320 or something.

I'm one step further into removing stupid undervolting interface, smartreflex does better job than any of us will ever do and I'm growing tired of reboots etc.
[Samsung Galaxy Nexus] bradm23:
Flashed back to 342. Everything in 350+ was giving me slow down and freezing, 348 seems a little slow compared to 342, so that's the reason i choose 342 over 348.

355 was soooooooo smooth, i have never witnessed anything so smooth on my gnex. Really hope Franco / Google can figure out those interactive patches!
[Samsung Galaxy Nexus] osm0sis:
Like I said, not so much an issue as a random point of interest that it could suddenly become borderline where it wasn't before. As for removing it altogether, I'd be all for that if SR was just a bit more aggressive, and was able to handle lower and higher freqs more effectively (or at all). :);)

Have you tried r356? Working great here and I haven't seen anybody report any real problems with it; only positive feedback.
[Samsung Galaxy Nexus] franciscofranco:
Maybe I'll just re-do everything from scratch again, something's very strange with 4.2.
[Samsung Galaxy Nexus] osm0sis:
Agreed. Google just shat it out so they could release manta with multiuser.
[Samsung Galaxy Nexus] razvanultra:
Almost I solved the problem, it's was an issue from the router signal, an interference who came from an electrical outlet from the wall. Also switched to channel 13 for best link speed. Thankyou for your patience.
[Samsung Galaxy Nexus] Angelakaro:
Sh**,after great smoothness and stability me too experienced lags with r350. Don't wanna try 351/354/355 unless franco will rework google patches,sorry. Here is my last kmsg

http://db.tt/k8ypiElo

Jumped to 356 which seems fine,going to give better feedback tomorrow

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] The Gingerbread Man:
Big thanks again Franco for headphone volume boost, finally I got to test and its LOUD! Awesome job there you did. I think much more and there would be distortion

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rodnar77:
Tried 355 and 356... No issues yet....

Dude... Seriously take some days off... Unless this is what you like to do on your days off!

Thanks a million....

Enjoy some beers or coffee on me Francisco... Its not a million... But a small token of my appreciation.
[Samsung Galaxy Nexus] _chanstar_:
Any vibration changes? My phone is vibrating longer and harder.

"That's what" - She
[Samsung Galaxy Nexus] CommanderDuplex:
Is it good ? looks deeply interesting !
[Samsung Galaxy Nexus] mikeandjaimie:
+1 your kernels are more than stable and you provide enough customization that we get amazing battery life and beyond butter smooth performance!
[Samsung Galaxy Nexus] osm0sis:
Nope, that's just placebo on your end I think. I know he did add vibration control to the Nexus 4 recently, as well as the f.Ku support to go with it, so maybe he'll add it for us too eventually, who knows? ;)

Yup, only issue is SR has a lower bound of 830mV (can't calibrate any lower), meaning low freqs like 384MHz and 192MHz are forced to use more power than they need, and also doesn't work well on any frequency higher than 1305 MHz due to not being able to calibrate the higher voltages required correctly. If Franco could fix those limitations and make it calibrate a little more aggressively then there would be no need for the UV interface at all, ever, and that would be awesome. :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Nope and dont count on it ever happening here, franco said he didnt want to add it

+1 with the exception a few round here actually know how to do it correctly. People complain of instabilities when they don't know wtf they are doing. I don't think there's a win unless Franco does actually make a download of osmisis' reset file from the app

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Kurre:
IIRC, I asked Franco about that ROW scheduler some time ago (and I bet someone else asked also) and I think that Franco said that he had made some tests with it and it didn't work at all (bootloop or something). So maybe that scheduler just isn't mature enough (if there haven't been any development done afterwards).

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] osm0sis:
He also incorporated the basic concept of ROW (read prioritization) into the patch he wrote for deadline. That's why it's so good now. :good:
[Samsung Galaxy Nexus] Syfer_Fever:
guys something wrong when i flashed the latest nightly r356. my wifi connected but no internet connection, my wifi icon is gray not blue, then i change to another kernel the wifi and the internet is connected again. i tried to flash r355 but still the same
[Samsung Galaxy Nexus] Edgarngg:
I've the same issue with music. Have you found the problem man?
[Samsung Galaxy Nexus] ChazzMatt:
THANK YOU.

And if anyone has a problem while undervolting, we don't want to hear about it. :p

I respect those who want to experiment with undervolting, but THAT is really a separate issue from testing dailies. There's enough stuff that can go wrong, no need to introduce new variables.

A transistor doesn't get enough electricity it's going to fail. And if you are right on the edge, it might work 90% of the time. But that other 10% is FAIL. And then you blame Franco's kernel. NO, it's you. :rolleyes:

(I am in no way talking about osm0sis. If he has a problem undervolting, he doesn't come in here and complain. He knows what he's doing, he makes backups, he knows how to recover, he knows his phone, and he knows his tweaked settings may not be set in stone.)

__________________

EDIT:

see? I wrote the above sentence before reading this from osm0sis:
[Samsung Galaxy Nexus] tobitronics:
Testing 356 now, went from 348
[Samsung Galaxy Nexus] marshy73:
Ok.. Woke after 6hrs of sleep.

r356 still no issues for me.

I've been in r356 for like 12hrs without any problems.
[Samsung Galaxy Nexus] franciscofranco:
No, I haven't, I'm working today.

How can I reproduce that problem? I need more info... what player do you use, what quality is your music (in kbps) etc etc...
[Samsung Galaxy Nexus] alexdemonumber3:
0 issues here also on r356. Its amazingly battery efficient. Franco, merry fawkin Christmas :D