yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MaLiXs:
im really tired my screen goes off ( without press power button) While setting an alarm with stock clock app like an sod i cant use my phone except if i pull the battery ( or reboot via adb)

im relly tired .. i got the same issue on stock kernel ... i dont know what to do now
[Samsung Galaxy Nexus] franciscofranco:
Because you probably have Location service enabled, I dunno, its your device, you have to find out for yourself.

And what makes you think we can fix something thats triggable on the stock kernel? No one knows wtf Google did. 4.2.2 comes in January, so we have to wait.
[Samsung Galaxy Nexus] whitedragonz83:
What ROM? That is likely the problem.
[Samsung Galaxy Nexus] JBNex:
On 4.2.1 r 348 the 192 and 384 voltages are too low. I get constant reboots with it on minimum.
[Samsung Galaxy Nexus] osm0sis:
Just got a screen-off SOD (notification light still flashing) with r348. ****ing Google.. 4.2.2 better fix it.
[Samsung Galaxy Nexus] aimcr7:
I even lowering it to 725 and no SOD or reboot. But in franco kernel i usually get reboot after initial boot but after the reboot everything is normal and stable as rock.
[Samsung Galaxy Nexus] The Gingerbread Man:
Will this be set on boot? And enter this in to terminal?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] MaLiXs:
i just ask it here if someone have an idea to reduce the number of those thing that i dont know the name
[Samsung Galaxy Nexus] BigBake88:
What is this 4.2.2 you speak of? :eek: 348 running great so far, Franco. No issues and very smooth.
[Samsung Galaxy Nexus] Khrushy:
It's the (currently) mythical update Google will release in the future which will fix all the stuff they broke in 4.2/4.2.1
[Samsung Galaxy Nexus] malaroth:
Damn dude.... the only time I know I'm gonna get SOD is if I'm plugged in and downloading NFSMW yet again because I flashed a new version and it's a protected app

JBSourcery 4.0 + r348 Franco FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] alfiemenace:
ROM control in AOKP ;)

Stock ROM, custom user.
[Samsung Galaxy Nexus] franciscofranco:
Its not mythical, I already know they are going to release it since last week. Cant tell how I got the info, but it came from Google.
[Samsung Galaxy Nexus] franciscofranco:
No set on boot, and yes.
[Samsung Galaxy Nexus] malaroth:
The question is... is it worth anticipating? Or will it be a disappointment? But thanks for the confirmation Franco

JBSourcery 4.0 + r348 Franco FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] The Gingerbread Man:
OK so since I tried roughly an hour ago really it's hard to tell any difference. I have been reading xda, a Google play magazine and messing about on apex launcher. When I entered the command I didn't get any out put after hitting enter

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
Let's just call it one of the perks of the new job :p
[Samsung Galaxy Nexus] bradm23:
So weird that they would take so long to fix a pretty big issue with the sod's people been having. I personally haven't had any but seems like it is a common issue.

Also is it true that 512 is now stock GPU? If so i find it ironic that Collins Cross was so against it when u asked him awhile back. If it I'd true it is funny how the android community influences the mainline updates
[Samsung Galaxy Nexus] The Gingerbread Man:
Impressive no?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] smileyanz:
I've been more then happy with 342 345 and 348. I'm no expert but I found 342 faster but 345 and 8 seem so smooth and now since 8 has been running for a few days on balance its been great on battery as well. Won't come off this until I hear the WOW factor!!! So does anyone know about this next rom roadrunner apparently coming out in summer !!!
[Samsung Galaxy Nexus] malaroth:
Mine won't count cuz I plugged it in for about ten mins at work but....here it is anyway

JBSourcery 4.0 + r348 Franco FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] franciscofranco:
4.2.2 is not only for fixing sods, theres a bunch of crap that needs fixing. I hope Google makes up for its word about 4.2.2!

512 is default. Dunno about Colin Cross, I haven't met him. I would like to though.
[Samsung Galaxy Nexus] The Gingerbread Man:
I just can't get over the fact today I'm at nearly 3 hours screen on and 40% battery left! I didn't even charge to 100% was (about 98%). All I did was turn off Google now and stop maps from reporting my location. I'm using cfq and 192mhz @750mv and added what ever that tweak was Franco added earlier for cfq, all the rest stock values except my colour set by init.d and Francos app

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thegtfusion:
For people with overheating issues when charging ( while you use it) , i found the cause. Take a franco kernel and a trinitt kernel to compare. Both kernels stock settings.

-franco kernel voltages are much higher than the trinity defaults, so that explains the higher temperature of the phone for me..

Cheers ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] malaroth:
That's awesome man... my phone is always on.... maybe it's a placebo effect in my head but USB fast charge seems faster with the uv numbers I ganked from osm0sis. On another thought.... trickster mod has the zram toggle but I thought I remembered that it was disabled in Franco... am I mistaken? Is it worth it?

JBSourcery 4.0 + r348 Franco FTW. Keep the Magic alive!

---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------

I'll take the higher temp since the safety valve is on versus the total lack of compatibility on my hardware with Trinity. But glad it works for you ;)

JBSourcery 4.0 + r348 Franco FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] The Gingerbread Man:
Does trinity not use smart reflex or is it something you don't use? I'd of thought if trinity does use smart reflex then the voltage would be calibrated to the same values being device specific.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] malaroth:
You mean you don't already know what's in it Franco? ....there you go trying to fool us that you're a mere mortal again... I'm on to you now

JBSourcery 4.0 + r348 Franco FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] nikulogical:
512 is default for Franco.... Not on the stock kernel..lol

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] kCelsius:
Idk about you guys but ever since upgrading to to 4.2 from 4.1, waking and locking the phone has become a bit slow and there's definitely some choppiness in the UI that wasn't there in 4.1...Hope this 4.2.2 will fix whatever they broke so that it'll be as smooth as 4.1 was.
[Samsung Galaxy Nexus] The Gingerbread Man:
I find 4.2 to be very smooth, the only thing which pisses me off daily is the music widget in the lock screen, how it will repeatably flash between the album art and a black square and appear to be spazzing. That and the constant reminder to not turn up your headphones to loud (it should have 'do not show again' box). I guess iv been lucky not having sods and repeated random reboots. Overall I like it, only thing I miss from 4.1 is the volume boost for my headphones, so as you can see 3 of my points being media based that my music is important to me :)

@ franco

I don't know about the other guys here but I'd be happy to have the bugged volume boost back and happily switch calls to loud speaker and back to get in call volume correct as I use my music more than calls. I hope you may consider adding it back as it was even though I know it's bugged until you get time to fix it Franco which I know and understandably may be some time as we now take 2nd priority what with the n4 being 1st now you have one. And your new job and stuff and I know your pushed for time as things are. I don't know how you would feel about some vote perhaps and we are all aware that it's not working 'as it should' :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kCelsius:
One thing that's just really annoyed me is that when I lock my phone and try to immediately unlock it, the screen doesn't immediately turn back on...there's like a 2-3 second stutter before it turns on - not sure if this is just a problem for me or a 4.2 thing.
[Samsung Galaxy Nexus] bradm23:
I could be wrong but I think stock android GPU is now 512.
[Samsung Galaxy Nexus] shreddintyres:
this is actually a bug with the recent maps update. i had the issue as well, uninstall and reinstall from the play store (do not restore from titanium or youll run into the same issue)

This morning when i took my phone off the charger i was down to 70% in under 2 hours which is not normal at all eventually tracked it down to something in maps being borked, better battery stats showed no use, but for some reason it was eating 80+ % of battery and app info was telling me gps had been on for 15 minutes.

hope this solves your issue

- Cheers
[Samsung Galaxy Nexus] The Gingerbread Man:
Francos default is 512mhz vs googles 307mhz

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khrushy:
Somewhat common bug. If maps updates you need to open the app and close the "what's new" announcement. Until you do, maps stays awake in the background and phone never sleeps.
[Samsung Galaxy Nexus] modifii:
Just experienced first SoD on stock 4.2.1 with r348 on 192/1228mhz rest all stock settings. No voltage changes at all. Interactive/cfq. Wifi was on while it went into SoD.

Drained almost 10% battery while SoD took place.
[Samsung Galaxy Nexus] gianton:
R348 is rock stable here and very smooth with interactive/cfq/westwood. Running osm0sis UV settings with 192/1536MHz max screen off 537MHz on AOKP Roman 1218 build. Lost 1% in 8h overnight on airmode.

Thanks again Franco!
[Samsung Galaxy Nexus] newbcake:
Can you guys please explain what you mean by Osmosis?
[Samsung Galaxy Nexus] osm0sis:
That would be me. ;)
[Samsung Galaxy Nexus] TransX2:
Yeah, me too.
[Samsung Galaxy Nexus] gianton:
Check here.

As yellowdie said a new thread with your settings would be great for people not searching in the "wild".
[Samsung Galaxy Nexus] osm0sis:
A whole thread for just my settings? Nah. Not my style. I might try to find a way to add some links to my settings and other things I've done in my sig tomorrow, but I'm having a hard time trying to figure a way that wouldn't mess up the good simplicity of it. The PM warning already annoys me but it became a necessary addition once I got nominated for RC. Even before that I was getting way too many "troubleshoot me" PMs. :p
[Samsung Galaxy Nexus] allgsmnetwork:
My gnexus with 345 6 hours only 1% on line 192 / 1420 and 1 hour with active LCD remains 78 % :thumbup:

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] newbcake:
So do your settings give a 'beastly' battery?
[Samsung Galaxy Nexus] osm0sis:
More like balanced with a lean toward smoother user experience. :)
[Samsung Galaxy Nexus] allgsmnetwork:
consumed 7% more but I do not understand why the LCD consumes 60% :confused:
[Samsung Galaxy Nexus] franciscofranco:
Because you're using your device?
[Samsung Galaxy Nexus] Pro4Eva:
Lol

Sent From My Paranoid Android Nexus
[Samsung Galaxy Nexus] osm0sis:
back_seek_penalty doesn't seem to accept anything less than 1.

Either way, these seem to improve it a little. But I'm still finding deadline just a hair smoother across several apps and games.
[Samsung Galaxy Nexus] sajty:
I have one question, maybe proposal (please, don't kill because of that, just asking :)). Nobody is missing some governor with hotplugging? For example sakuractive (I found it most stable across many kernels). Maybe somebody already asked this question and was rejected, so please...
[Samsung Galaxy Nexus] allgsmnetwork:
has happened other times then slowly descends consumption continues but now, I clean the cache and davlik?, or use cwm-franco.Kernel-Emergency.SettingsReset.zip? ( great work ) hours I saw a screenshot that also consumes 60% rather 61 maybe it is normal ...
[Samsung Galaxy Nexus] marcocsh:
Hi all,

With r348, I have to set screen off min frequency to 729MHz in order to remove the glitches/skips when listening to FLACs.

In the past release (r300 for example) I don't need such a high frequency to keep the music smooth.

My set up is:

Max/min CPU: 1536/384

Governor: interactive

Governor control: 60000/65/45000/15000, 1036/729

SR enabled with no UV

ROM is JB sourcery 4.1

Player is poweramp with highest buffer and thread priority.

Any clue what the problem maybe?
[Samsung Galaxy Nexus] lippol94:
I have applied them without any problem. Don't know..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shawnaye:
I'm not sure if this is a rom or kernel related issue.

So when using my phone, I'll get horrible lags. I'm quite sure it has to do with memory management.

It's so bad that when I type. The letters slowly appear 1 by 1 every second.

Everything gets better once I hit the clear all on my recent apps list.

BTW I'm on the latest xylon.

Is anyone else facing this? Or can think of a fix for this? It's like my apps aren't closing in the background even though the ram SHOULD be running out.
[Samsung Galaxy Nexus] Khrushy:
Aaaaand back to deadline. The minor gain in launcher/browser smoothness isn't, to me, worth the delays when switching between large tasks.
[Samsung Galaxy Nexus] Khizar:
i was getting lag on all kernels on xylon v12, franco is the only one that doesnt lag
[Samsung Galaxy Nexus] shawnaye:
mine isn't lag per say, like i said, everything is smooth when i clear app my apps.
[Samsung Galaxy Nexus] TheQuarterMile:
Does using the usb fast charge option affect the phone or battery health in any way?
[Samsung Galaxy Nexus] sajty:
Phone not, but it can destroy your USB jack.
[Samsung Galaxy Nexus] TheQuarterMile:
How so?
[Samsung Galaxy Nexus] calinoii:
Is there any chance that my phone doesn't support franco's kernel? I have some terrible lags after using it for couple hours after a clean rom flashing...same with lean kernel and stock kernel...i have like many little freezes,on other kernels I don't have this problem:-/ what could it be?
[Samsung Galaxy Nexus] sajty:
Because you force your USB to handle bigger voltage,so you can simply destroy it.I dont use USB fast charge,never,i like my computer :).
[Samsung Galaxy Nexus] Kurre:
AFAIK, voltages will remain intact, only current is affected by fast charge. But those current levels are inside the current range specified to USB ports so it isn't a problem. Even some pc device plugged to the USB port could draw more power from it..

feel free to correct me if you need to, couldn't check the facts atm.. :)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] Redneck Trash:
It's not going to damage your phone or the USB port its plugged into. As long as your phone isn't getting excessively hot when charging it shouldn't damage your battery. I use fast charging with my 5V/2.1A external battery pack and haven't blow anything up. Haven't blown up a USB port either. My phone still has its original battery.

Set from my toroplus
[Samsung Galaxy Nexus] TheQuarterMile:
What if I use it with the car charger? It has 750mA output..
[Samsung Galaxy Nexus] sajty:
Maybe you are right,I only read about this feature. Maybe it's safe, but definitely I will not risk it :). And as I wrote, this feature is "risky" only for USB port of computer (maybe ;)).
[Samsung Galaxy Nexus] gianton:
Just had a SOD too, while on a phone call. Last ksmg http://db.tt/ORU9uzTj
[Samsung Galaxy Nexus] sajty:
Which governor?
[Samsung Galaxy Nexus] gianton:
interactive/cfq, I had min CPU at 192MHZ I raised it at 384MHZ.
[Samsung Galaxy Nexus] alfiemenace:
Can anyone point me the emergency services zip for this kernel? :)

Stock ROM, custom user.
[Samsung Galaxy Nexus] gianton:
Check osm0sis posts a few pages back, he posted a flashable zip to clear F.K.U. app data.
[Samsung Galaxy Nexus] skinnypupp:
Don't worry, that person has no clue what they are talking about.
[Samsung Galaxy Nexus] franciscofranco:
Like the user above said, no one is talking about leaving the Android Market, this is just for the users that don't have a credit card and want to buy the app. I already got tons of requests to do this, so now that I had a little bit of time I did it.
[Samsung Galaxy Nexus] kabauterman:
Hey francisco :)

first I need to say it another time: great work here with your Kernel!

I've tested a lot of other Kernels and for my kind of usage yours is the best.

But I have a little question, if I run other Kernels (Apex, minimalistic, Matrix) I have arround 350-400 MB free memory and with your Kernel just arround 300 MB.

What causes the higher amount of used memory with your kernel?

Thanks in advance
[Samsung Galaxy Nexus] bradm23:
I'm a little curious what governors everyone is using. I have been using the kernel "as is" and been having great results.

I did notice that my phone never touches the 920 MHz when in use. It seems to only hit min/Max. Do you think changing to interactive will use the 920 slot more instead of always maxing to 1200?

This kernel absolutely kicks butt, just wish I could figure a way to lower my in use battery usage.

Thanks for all the help, can't wait for 13 :-)
[Samsung Galaxy Nexus] Thracks:
It doesn't hit the 920MHz slot because 700MHz is sufficient to ensure smooth performance with the conservative governor. You'll find that the phone spends most of its time on that slot, which is the best battery life you can have.
[Samsung Galaxy Nexus] fenerbuuh:
Waiting for IT. Thanks both of you.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sluflyer06:
I've averaged over 400MB free with Franco's. I seem to be alot lower now on AOKP18 and nova launcher like 350.
[Samsung Galaxy Nexus] Thracks:
Who cares how much free memory you have? Android's memory manager is specifically designed to use as much as possible, because that allows the fastest possible access to applications and their data. It's not Windows XP any more.
[Samsung Galaxy Nexus] d-iivil:
None of my init.d -scripts works with #12. Flashing faux kernel makes them work, so it must be kernel related?
[Samsung Galaxy Nexus] franciscofranco:
Maybe I screw up something. Will check when Im back home.
[Samsung Galaxy Nexus] versd:
im using the ondemand governor setting. please advise if thats the best one to use? Im after a good balance between performance and battery life. more towards the battery life (until my damn extended unit arrives!!)
[Samsung Galaxy Nexus] aron7awol:
If you need to extend your battery life, I suggest lowering your screen brightness. The governor's impact on battery life will be negligible.
[Samsung Galaxy Nexus] pa.pn2:
Which settings are recommended for the color control?
[Samsung Galaxy Nexus] nikosrs4:
I managed to reproduce the lockscreen lag. Probably, it's not kernel's problem.

The lag is produced by the autobrightness of the phone. If the external brightness is different before locking the phone and after unlocking, the phone lags because it tries to set the brightness of the screen. The same happens(at least in AOKP rom) when changing custom brightness to auto, then the phone immediately lags.

The phone stores the brightness levels and when we unlock it, it tries to set it back with the new external brightness levels.
[Samsung Galaxy Nexus] grinch247:
try here:

http://xdaforums.com/showthread.php?t=1447757
[Samsung Galaxy Nexus] Stretlow:
Genius:cool:
[Samsung Galaxy Nexus] Thracks:
Every phone is different. You'll have to experiment.
[Samsung Galaxy Nexus] nikosrs4:
And that's why Franco doesn't have the problem, because he has it at full brightness all the time :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bebolf:
Just want to point out that init.d is disabled in AOKP build 19:

(http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-build-19-jan-17/)
[Samsung Galaxy Nexus] franciscofranco:
Yes, why decrease brightness? The phone is to be used, not to be minimum at everything. And battery is so good, why not use it like it's meant to be? ;)

Anyway, just coding the UV interface @ app. Looking good so far. It will run independently of SetCPU's UV interface because I'm doing it from scratch, so I'll write a note in the UV panel explaining that.

The app will use Theme.Holo.Light.DarkActionBar for this next version, just to be a little different ;)

ETA for kernel and app = some hours.
[Samsung Galaxy Nexus] zephiK:
It's disabled by "default." Just re-enable it in ROM Control.

Settings -> ROM Control -> Start-up tweaks -> enable
[Samsung Galaxy Nexus] Khrushy:
All this USB fast charge talk is silly. No, you can't damage your phone with it. Your phone, even with fast charge on, will not request more current than it can handle. 1amp at 5v, that's it AFAIK. Even if you get a Nex7 charger, which is rated for 2.2 amps at 5v, it will still only give your Gnex 1amp.

Secondly - No, you can't damage your computer. Your USB won't try and force out more current than it can handle either. If all it can give is 0.5 amps, then that's what it gives. No harm done.
[Samsung Galaxy Nexus] JBNex:
Really? How about setting Max screen frequency to 384
[Samsung Galaxy Nexus] jendrassik:
So you suggest to have it off?
[Samsung Galaxy Nexus] Paragon_X:
Yes. Try and see if you have wakelocks.

---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------

Hey mate I recently came in with the same problem a few pages back. Pretty much same setup but a suggestion was to try another player, Google Music see if it still persists. However with Google Music in my case it seemed okay so what I did was revert back to r345 which didn't skip. So really all I lost was CFQ which I can live without... r345 battery is marginally better, literally by 2% a hour in terms of drain compared to r348.

---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------

Hey mate I recently came in with the same problem a few pages back. Pretty much same setup but a suggestion was to try another player, Google Music see if it still persists. However with Google Music in my case it seemed okay so what I did was revert back to r345 which didn't skip. So really all I lost was CFQ which I can live without... r345 battery is marginally better, literally by 2% a hour in terms of drain compared to r348.
[Samsung Galaxy Nexus] ChazzMatt:
One clue might be that you are on a 4.1 ROM with r348, when the r300 is the highest recommended release for a 4.1 ROM?

Higher than r300 is for 4.2 ROMs.

It's even in the thread title...

[KERNEL][GPL] franco.Kernel-r348 -> 4.2 | r300 -> 4.1 >

Go back to r300 until you get a 4.2 ROM.
[Samsung Galaxy Nexus] tjackbjorn:
Dude I think he means he's on v 4.1 of the rom, which is 4.2.1 :)

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] Paragon_X:
I went back a few pages but couldn't find this tweak you're speaking of. Can you elaborate more?
[Samsung Galaxy Nexus] ChazzMatt:
Oh, well that's confusing. :)

And v 4.0 of the ROM was really 4.1? :silly:
[Samsung Galaxy Nexus] Paragon_X:
No sorry. I missed that part of your post... kinda just skimmed what you wrote. I'm on AOKP 12/06 4.2.1 whatever the latest number is now.
[Samsung Galaxy Nexus] yellowdie:
This:

:):D:laugh::good:
[Samsung Galaxy Nexus] alexdemonumber3:
Installed maddoggin 4.2.1 alongside r348 on my brothers sprint gnex its not deep sleeping. Any basic rules I need to know about the CDMA and sprint model?

sent from my galaxy nexus

hit that thanks button if I helped you
[Samsung Galaxy Nexus] osm0sis:
Yeah they apply fine, as in, there's no error returned. But try cat /sys/block/mmcblk0/queue/iosched/back_seek_penalty you'll see that it's still 1. I can echo 2 out to it and it accepts that, then 1 and it goes back to 1, but echo 0 and it just stays at 1.
[Samsung Galaxy Nexus] calinoii:
Anyone? And how can I ask a question directly tp Franco ?I think he has a busy schedule and will never see my post in this thread unless it's a Christmas miracle
[Samsung Galaxy Nexus] osm0sis:
If it's the same with stock kernel and fastbooted full stock ROM reflash with no apps installed then that leaves hardware unfortunately.

If you have apps installed then I'd say something's going rogue.
[Samsung Galaxy Nexus] calinoii:
But why other kernels work fine ? Yhat's a real dilema