yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Yeah it sounds like WIFI PM_Fast and the "Wi-Fi Optimization" options do the opposite thing, so maybe some conflict there once you added PM back in, even though nobody has PM enabled. :good:

I haven't had an SOD since I tweaked my voltages earlier, but they're pretty randomly timed, so we'll see.
[Samsung Galaxy Nexus] joaquinf:
Read this

---------- Post added at 05:21 PM ---------- Previous post was at 05:16 PM ----------

thanks for the info. I have the wifi_pm disabled on fku and wifi optimization ticked on settings and i can't get to trigger the SOD nor a single reboot. So far r325 is running great and batt life is even better than r318.

Let's see if i can make it panic, i'll keep trying and report back if i have any interesting finding

:)
[Samsung Galaxy Nexus] franciscofranco:
Ok r326 is up, wifi_pm is goners. Let me know if you can trigger a SoD.
[Samsung Galaxy Nexus] Vangelis13:
On it. You want "wi-fi optimization" in the settings left on I guess?
[Samsung Galaxy Nexus] Craxx:
I am on it. "wi-fi optimization" in the settings is on.

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] franciscofranco:
On or off, works for me. Mine is always off, never had a problem.
[Samsung Galaxy Nexus] Vangelis13:
K, trying with "on".
[Samsung Galaxy Nexus] Khrushy:
Ok, testing 326 now. Wi-fi optimisation left to on.
[Samsung Galaxy Nexus] :
Thanks for the link, just flashed 325.

Question: I am used to Trinity kernel colors. How can I setup the Franco app to achieve Trinity based colors?

Thanks again!
[Samsung Galaxy Nexus] bat0nas:
Same here!

Few times in few hours!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
try this setup:

Color multipliers:

135; 135; 200

RGB gamma:

-4; 0; 4

Trinity contrast interface:

-24 (i leave mine at -15)

OMAP:

1.0
[Samsung Galaxy Nexus] Puzzlegirl:
Thanks Franco, just flashed r326 after 3 SoDs today. Wifi optimisation on. Onwards and upwards :)
[Samsung Galaxy Nexus] Astug:
I'm hoping you guys just missed my post, so quoting myself here.
[Samsung Galaxy Nexus] franciscofranco:
Sorry, but I have no clue.
[Samsung Galaxy Nexus] The Gingerbread Man:
Hi Franco seems I'm late to the party here had 11 pages to catch up on...

Since 325 and latest app update I've had WiFi pm mode enabled and also WiFi optimisation enabled in advanced WiFi settings so I'm not sure if that's the culprit of these sods. I'm using smart reflex for my all my voltages except 192mhz @ 735 MV. I flashed 325 using the app to restore 325.IMG if that makes any odds?

No sod here, litterally no issues what so ever on 325 for my normal usage.

Sent from my Galaxy Nexus

---------- Post added at 11:19 PM ---------- Previous post was at 11:17 PM ----------

Try signing out of your Google account, reboot and sign in again. I dorm think this is kernel related though matey

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] KJW979:
Running r326,so far so good, haven't been able to replicate any SOD. All stock settings.
[Samsung Galaxy Nexus] :
Thanks man though settings look pretty good!

How is battery life with default voltages etc. Just now flashed 326.

Thanks for all of your help!
[Samsung Galaxy Nexus] mikiept:
Well, that seems to be an issue with that particular ROM, because I had that issue to. Try changing the ROM ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Just my CPU 192mhz at 735, rest all at smart relflex calibrated values

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RayGarden:
first SOD on #325 was at the moment i connect my Gnex on Power Adapter and Switched Screen off. Both Powerbutton ands PGM didn't respond anymore.

* Wifi Optimization was Checked - On

* Wifi_pm - i don't know. what is that and where to find it????

Now testing #326
[Samsung Galaxy Nexus] TinyFeather:
Sound control missing on r326?

Doesn't show up in Franco app :(

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] The Gingerbread Man:
In Francos marvelous app

Yup been missing since 4.2 its not yet implemented

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] duduzinho15:
Without sound control is bad :S because my earphone is low :(
[Samsung Galaxy Nexus] The Gingerbread Man:
Try 160, 135, 180 , 0,0,0 trinity and omap unset

Sent from my Galaxy Nexus

---------- Post added at 11:40 PM ---------- Previous post was at 11:39 PM ----------

Then you play with eq

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] duduzinho15:
This equalizer isn't good, i prefer the Increase of the sound control!!
[Samsung Galaxy Nexus] osm0sis:
Sounds like you flashed one of the old broken zips from before r325? Those are exactly the errors we were seeing associated with the broken sdcard binary. See here, and flash the stock binary I attached.
[Samsung Galaxy Nexus] franciscofranco:
Yeah thats a typical kernel crap.

No sound control yet, sorry.
[Samsung Galaxy Nexus] osm0sis:
Franco, I see you enabled SR for the 1420MHz step - it gets calibrated to 1230mV. Could that also be causing issues for people? I was messing with it just now and got an SOD with r326. Completely unresponsive so no chance for USB Debugging.
[Samsung Galaxy Nexus] franciscofranco:
I did? I don't remember messing with that. I'll re-check...

EDIT: 1420MHz is not being calibrated just checked on my device.
[Samsung Galaxy Nexus] osm0sis:
Yeah it's definitely something weird going on with 1420MHz, shows as calibrated to 1230mV and even when I lower it below 1230mV (I usually keep it at 1225mV) it still displays as 1230mV.

Edit: Whoa. Completely froze up again after a reboot, still at 1225mV which always worked before... now the One Time Setup came up.. so my system settings data is gone. Fun! :p
[Samsung Galaxy Nexus] The Gingerbread Man:
Then invest in some decent headphones I spend £60 on my klipsch s4a and a further £20 on comply tx 100 tips and to me that eq is perfect, granted without the volume boost its a little queit than what I'd like so your choices are 1 wait till volume is reintroduced or get a half decent set of headphones till then and reep greater rewards when sound boost is back :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Thats not funny. Mine is not being calibrated. You had fsync off didn't you?
[Samsung Galaxy Nexus] osm0sis:
Fsync on actually. Turned it back on when people started reporting SODs.

Yup now 1420 is not being calibrated here anymore either. That was really weird, wish I'd taken a screenshot. Some kind of random derp.

I notice 1804 is still apparently being SR calibrated too. No matter what you set it to it gets calibrated to 1410mV.
[Samsung Galaxy Nexus] ahqball:
Sorry for the noob question, but what's a "sod"?
[Samsung Galaxy Nexus] The Gingerbread Man:
Essh with f sync on that doesn't sound at all good. I wonder though if your voltage settings were not working if some other settings got messed up too like f sync perhaps?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Guys flash r327 please, I'm pretty sure I found the culprit.
[Samsung Galaxy Nexus] The Gingerbread Man:
Sleep Of Death

Phone screen won't wake up, voltages dropped too low is main cause. Need to pull battery to reboot to gain access to screen again. Be careful with voltages before you hit the set on boot button :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Bl4ck3urn:
Screen of Death
[Samsung Galaxy Nexus] drmxmyt:
whooooaaa:highfive:
[Samsung Galaxy Nexus] franciscofranco:
1410mV is the maximum voltage allowed from the smartreflex voltage headers, so if one wants more than that it needs to be set up manually in the sysfs entries (using a script or an app). Its working as intended. I just went through all my freqs and they are all working properly.
[Samsung Galaxy Nexus] yellowdie:
GAH!! :eek: I need to learn to read everything before flashing kernels. I was behind a bunch, so I was reading to catch up, saw r325, flashed it. Then saw r326, flashed it, and now I am flashing r327. All in a matter of like 15 mins. haha. :silly:
[Samsung Galaxy Nexus] marshy73:
Thanks!

Just fyi with 326, flashed in the morning,

Within an hour, had system freeze (need battery pull) and a random reboot. Wifi wasn't on.

Now on 327 with wifi most part of the day.

Will observe.

Thanks!
[Samsung Galaxy Nexus] thegtfusion:
Hey yellow! What are the best settings for the interactive governer? Hispeed freq and input boost? At what do i need to set it? Im running 1305/384.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khrushy:
Flashing 327 now.

No issues with 326 in the whole 2 hours I had it running :P
[Samsung Galaxy Nexus] osm0sis:
Ah okay, good to know. I was just mentioning since 1405mV is a crash and 1410mV is "stable", so personally I'd want it around 1425, or the 1450 you have it set at (for apparently no reason :p). Trying r327 now. What was the issue?
[Samsung Galaxy Nexus] Savant:
Yeah Franco is on fire and glad he wants the users happy. It means a lot because most devs don't care and we all know he's a busy man.
[Samsung Galaxy Nexus] yellowdie:
Franco's stock is the best. It's what we narrowed everything down to a few weeks ago. :):D:laugh::good:
[Samsung Galaxy Nexus] galakanokis:
Should we be able to download/install kernel zips through the app yet or are these just tests kernels in zip form? I see them on the site but I get an error message about no 4.2 kernels available when I try the app.

Completely fresh install of ROM and kernel as well. Haven't come across useful posts in the thread but I will bump up to 327 in light of the SODs.

Sorry if I missed the info.
[Samsung Galaxy Nexus] GCbard:
Is this hard on the phones software that the kernels are all now 512 mhz gpu?
[Samsung Galaxy Nexus] Savant:
No its not. The difference isn't really apparent unless your playing a game.
[Samsung Galaxy Nexus] GCbard:
Thanks. I meant hard on the hardware.
[Samsung Galaxy Nexus] KJW979:
Just installed 327,also had no problem with 326 for short time was using. Have noticed on 327 & 326 when first boot up wifi won't connect, have to turn off then back on for it to connect.
[Samsung Galaxy Nexus] numb_:
Just flashed r327 and after some minutes of browsering I got a reboot..

All the settings are defaults.. Here is my last kmsg.. http://db.tt/jJlQBgjz
[Samsung Galaxy Nexus] aimcr7:
Just flashed r327, first boot had freeze but after reboot everything seems normal, fast as usual.

Wifi hotspot still doesnt work, tried using open and wpa2.

Does all 4.2 kernel clocked at 512 max gpu?
[Samsung Galaxy Nexus] wolf911:
No, not till he ready to release it stable, he talked about this earlier.
[Samsung Galaxy Nexus] allbass:
This works on stock 4.2 ROM?
[Samsung Galaxy Nexus] malaroth:
Is screen freeze same as sod? I had multiple instances where I had music playing in the background and it kept playing but screen was unresponsive, not even turning off just stuck but I could "receive" messages or calls even though I couldn't trigger an answer response due to unresponsive screen. Battery pull. Both pa 299.1 and 325 and mmuzzy 4.2 325 release. I'll sit in the background till eagle flys (edit) back to update sourcery so I know my way around the rom.

Sourcerized, Milestoned6, just missing the Cheetos and Redbull. http://teamsourcery.com/Images/teambanner.png FTW Keep the Magic alive!!
[Samsung Galaxy Nexus] Phoenix Wright:
Don't know about the sods but the wifi tethering issue and the logcat spamming are still there...

---------- Post added at 02:54 AM ---------- Previous post was at 02:54 AM ----------

Yeah, that's what a sod is...
[Samsung Galaxy Nexus] malaroth:
Thanks bro.... I feel naked till my fiancée brings my computers back and I can hook up for adb... I swear I AM wearing pants though

Sourcerized, Milestoned6, just missing the Cheetos and Redbull. http://teamsourcery.com/Images/teambanner.png FTW Keep the Magic alive!!
[Samsung Galaxy Nexus] simms22:
screen on, that's not a sod. sod = SLEEP of death.
[Samsung Galaxy Nexus] :
Flashed 327 no issues so far. Was running 325 and 326 earlier today, also with no issues. What was causing the SOD's for you guys?

Also, do you guys roll with Fsync off or on, just curious.

Thanks!
[Samsung Galaxy Nexus] syncopy:
Yes, it does. Flash away!

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/
[Samsung Galaxy Nexus] kyokeun1234:
No sod at all since 315. I have f sync on and also Wi-Fi high performance on... I am using stock deodexed ROM...
[Samsung Galaxy Nexus] simacai:
Hi guys.A strange issue. My screen still active but truned off during a call. I'm on r327, this happens on r315, too. Paranoid ROM. Is this related to kernel or the ROM?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Weird something is still wrong with r327 seeing those last_kmsg logs. I'll do a fresh config compile, maybe I borked something by accident.
[Samsung Galaxy Nexus] momomok:
it is a PGM issue
[Samsung Galaxy Nexus] asder00:
I finally tried to change stock kernel and I must say GREAT result :D (r326)

The only thing that drive me crazy is the color calibration. Any setting seems better than the one before and I can't really find a setting that goes fine. I just wanna ask u if u can tell me the default franco kernel settings for color? (Or maybe also the reccommended one!)

Thx!!!
[Samsung Galaxy Nexus] kyokeun1234:
I personally like trinity kernel colors. But that's because I like everything with high contrast and nice blue color.

All gammas are 0

Contrast is -24

Multipliers:

Red and Green: 135

Blue: 214
[Samsung Galaxy Nexus] simacai:
THANKS a lot, man!

So I should turn PGM off and wait for it to update...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] whitedragonz83:
It seems I can under volt almost every speed about 50 mV lower then SR. Am I saving that much? Or is there a reason I shouldn't do this?
[Samsung Galaxy Nexus] Khrushy:
If you're stable then you're fine, and you'll see some small but appreciable battery gains. If you find you're unstable at all, then it's probably those voltages :P
[Samsung Galaxy Nexus] aimcr7:
Wow you really really fast mate, take your time. No SOD or freeze for me so far, pretty stable.
[Samsung Galaxy Nexus] momomok:
Yup

that's what I did now

*sigh*

get used to slide to wake, now looks like a idiot to slide and try to unlock but nothing happens... :(
[Samsung Galaxy Nexus] franciscofranco:
Ok r328 is up, compiled with a fresh config, should be OK now.
[Samsung Galaxy Nexus] :
Thanks man, just flashed.

Cheers!
[Samsung Galaxy Nexus] harmohn:
No reboot on r328 this time when stress testing. Good job :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] simacai:
Bootloop several times and boot failed once after flashing or restore to r328...

Flashed back to r327 so I can report.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] b1337:
constant reboots after upgrading from 327>328 phone got super hot as well

no reboots on 3 versions prior
[Samsung Galaxy Nexus] drmxmyt:
i just flashed r328, and it seems fsync is off. is it supposed to be like this?
[Samsung Galaxy Nexus] reflexr:
No reboots or sod here.

Using the latest 328.IMG

Settings are on stock

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] joaquinf:
So far 328 is running great here. No sod or issues whatsoever. Everything is snappy, fast, fluid and i don't have reboots or overheating problems.

Thanks Francisco for your work
[Samsung Galaxy Nexus] shawnaye:
Constant reboots after flashing to r328.

Flashed via app img.

Rebooted at least 8 times before I could press restore r326 in time.

R326 working fine for me as of now.

No sods YET
[Samsung Galaxy Nexus] klobkelosh:
Wifi tether still broken on r328. Testing all else now...
[Samsung Galaxy Nexus] aimcr7:
Using flashable zip r328 got sod in first boot when trying to decrease voltage, but no more sod after that sod, running 5 minutes so far no problem
[Samsung Galaxy Nexus] franciscofranco:
Something is fishy here.
[Samsung Galaxy Nexus] shawnaye:
I don't even got time to grab any logcat haha.
[Samsung Galaxy Nexus] galakanokis:
Sorry, all I saw was he was not going to release zips until he was happy with a stable version. Zips heave been released so I thought there mighty be something else up. Must have missed the post about skipping the app.

Still running 325 with WiFi pm on and no reboots. Working fine so far.
[Samsung Galaxy Nexus] RoscoeDpG:
and we know u will catch it :fingers-crossed:
[Samsung Galaxy Nexus] franciscofranco:
Im completely clueless at the moment.
[Samsung Galaxy Nexus] Khrushy:
Errr, so do you need more people testing 328? I note a lot of "Instant SOD" posts that make me think I should avoid it :P

Still on 327 here, with no problems so far. Wifi Optimisation on, most kernel settings at default.
[Samsung Galaxy Nexus] Edrill:
Have the exact same problem after flashing the same way. Tried clearing Dalvik and Cache, but still had the reboots. Back on r327 and all is back to normal now!
[Samsung Galaxy Nexus] osm0sis:
Everything here was good since r327 - No more weirdness with 1420MHz not liking 1225mV and no SODs for what short time I was using it. The weird system data wipe I experienced earlier made me want to properly format data and restore my TiBU user app backups then set up system apps again from scratch to make sure everything was good; so I did. On r328 now, no weird issues like everyone is talking about with reboots. We'll see how it goes.

Those with Wi-Fi tethering problems, try disabling Wi-Fi Optimization under Wi-Fi Advanced system settings, see if it makes a difference.
[Samsung Galaxy Nexus] mohaimed:
What is the changelog from v325? I have not faced any problem in 325 Do i still need to update?
[Samsung Galaxy Nexus] D3VI0US:
The weirdest thing just happened to me .. i flashed the r325 through fastboot no problem and the phone started no problem so i left the room for 10 mins and i came back to find the X bootanimation and usually since that ****ty 4.2 update it's normal to see this kind of behavior every once and while but the difference here that it was a bootloop so i tried to roll back to r318 and it didn't work flash the stock kernel back still didn't work .. so i went to fastboot update image-xxx but still nothing and it didn't work until i did clear data and restored old backup i had ... from how i see things i guess the kernel got something to do with one of the apps but how come and i tried 2 different kernel ? ... so guys any idea what might cause this?

also how to reboot a nexus phone when it's stuck on black screen or bootloop without removing the battery

because a phone like Nexus 4 got no removable battery and for samsung phone for example you can press power button for almost 6 sec and it will reboot so how to do this on a Nexus device
[Samsung Galaxy Nexus] osm0sis:
Borked system file would do it, though franco.Kernel should not in any way be causing that, especially when flashed from fastboot. Unfortunately the Galaxy Nexus missed the boat for holding power to reboot. The Nexus 7, 4 and 10 all work that way, and a lot of Samsung devices do too, but not the GN. I guess it's more likely included on the Nexus devices without removable batteries. :p

I would update. Franco definitely fixed a couple things from what I've observed with my own device. Generally, newer = more fixes = profit!
[Samsung Galaxy Nexus] rmcsc:
I had the first SoD I've ever had on this phone running r325. Maybe.
[Samsung Galaxy Nexus] Khrushy:
Being the good little kernel flashing monkey that I am I went ahead and flashed 328 anyway. No problems so far. Fsync On in fku. Wifi Optimisation on in settings.

Cheers~
[Samsung Galaxy Nexus] D3VI0US:
Yep but that only happen when i flashed the r328 and before that the phone was working no problem

as for the power button thing i don't know why in the hell Samsung dropped that feature instead of taking the battery out that is really silly
[Samsung Galaxy Nexus] jesfreak:
Whats the difference between .img and .zip? Wich one is better and why the change from zip to img?? <---- NOOB
[Samsung Galaxy Nexus] kyokeun1234:
IMG, you have to flash via fastboot using your computer or Franco kernel's built in kernel restore

Zip, you just flash from the recovery

There's no difference in performance or anything, just a personal preference.
[Samsung Galaxy Nexus] alexdemonumber3:
all is well here on r328. underclocked to 1036 and undervolted heavily. phone is running cool and no problems whatsoever.
[Samsung Galaxy Nexus] franciscofranco:
r328 seems completely fine to me right now to be honest.
[Samsung Galaxy Nexus] garuhhh:
Tethering still would not turn on, whether wifi optimization is On or OFF. I've attached logcat, if it's helpful.

Running r328, no SODs so far, and it works fine on me with the 15mins or so of playing with it.

EDIT: did not touch any of the kernel settings, everything is stock (freq, voltages, governors, etc.)
[Samsung Galaxy Nexus] franciscofranco:
I know tethering doesn't work.
[Samsung Galaxy Nexus] kecinzer:
This is very strange. When I read those posts, I'm afraid to flash new version :). Now I'm on #325 and no problems so far.

I think I'll try 328 - some people says good, some sods. I'm lost :D
[Samsung Galaxy Nexus] alexdemonumber3:
haha I'm with franco, r328 is just fine. I think it may just be noob-user error lol
[Samsung Galaxy Nexus] osm0sis:
No SODs reported for r328 yet. One guy who was UVing too far is all. Not sure what's up with those getting weird bootloops. I know I've had zero problems with that here on any of Franco's JB 4.2 versions, all the way back to r301.
[Samsung Galaxy Nexus] jcmm11:
I'm back on 327, which is working fine. 328 initially gave me an SOD. After I got through that it went into bootloop mode on me. Pulled battery, booted into recovery, flashed back to 327. No issues so far (early times on this version though). Never had these issues before.

Default governor and freqs.

Mmuzzy ROM on toro. No mods added.
[Samsung Galaxy Nexus] osm0sis:
Spoke too soon.. :laugh::(

@jcmm11: When you say SOD do you actually mean your phone booted up, went to sleep and wouldn't wake up (ie. a SOD, by definition)? Or was it just a freeze + reboot? I feel like people are starting to confuse any old freeze for a SOD.
[Samsung Galaxy Nexus] wolf911:
r328 for about an hour now, no SOD, seems smooth for me on jelly belly v10.2 - wifi opt on
[Samsung Galaxy Nexus] beren28:
On 328 phone would boot and run fit about 90 seconds. Then the screen would flag blue, a click, and a reboot. Referred to a backup for now so I can go To bed and trust my alarm.
[Samsung Galaxy Nexus] Khizar:
do you mean r328?

---------- Post added at 11:19 AM ---------- Previous post was at 11:19 AM ----------

No SOD on r328 but i am getting random reboots, so flashed r327
[Samsung Galaxy Nexus] osm0sis:
Those with issues: get it to a bootable state, clear data+cache on franco.Kernel updater app, then flash r328 again. Might just be something whacky there, as the 90 second delay might indicate (ie. f.Ku bootservice restores whatever is making things crazy then kaboom).
[Samsung Galaxy Nexus] Khizar:
i flashed the zip..
[Samsung Galaxy Nexus] osm0sis:
Yeah, zip or not shouldn't make a difference now. Try what I said, please. If it works we could be on to something. :)
[Samsung Galaxy Nexus] windsor:
Im in stock, and always runin just fine with 318, 325, 326, 327, and 328 with wifi_pm on/off, fsync on/off, 384-1305 mhz, undervolts -100/speed.
[Samsung Galaxy Nexus] Khizar:
ok i will try and report back
[Samsung Galaxy Nexus] Booker-T:
I use interactive governor, does it have default lower frequency setting when screen off like SetCpu profile function?

Besides, is hotplug enable on default?
[Samsung Galaxy Nexus] samizad:
Quick answer: Yes. http://xdaforums.com/showthread.php?t=843406

No. Hotplug is off by default.
[Samsung Galaxy Nexus] jameslfc5:
Get stickmount off the market, it's awesome! :)
[Samsung Galaxy Nexus] balders27:
NFC no longer works on latest build? Any ideas on a fix
[Samsung Galaxy Nexus] DynamicRam:
in OLED blue decays faster than Red and Green , Red is the slowest to decay

so

i think

increasing the gamma of blue is not a good idea

2 0 -5 seems good