yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rabhw:
I know ASUS has something like this for their motherboards. It's a piece of software that ups the voltage incrementally, each time running a benchmark to confirm stability. At each new step, I'm assuming it updates a file on the hard drive that contains the last functional frequency / voltage.

Upon system crash / reboot, it detects that there was a crash and reverts to the last known working frequency cached on the hard drive.

Simple enough in concept, probably not that easy in execution :)
[Samsung Galaxy Nexus] loudaccord:
Those are some smart mo-fos! I don't see why that couldn't be done with the Ghz also... some people can run 1.42Ghz others can't even pull off 1.35.
[Samsung Galaxy Nexus] rommel500:
I am trying to buy the app on the market and I am getting this error -

We're sorry. This seller is currently unable to accept orders. Please try again later or contact Google Checkout support.

Anybody else seen this?
[Samsung Galaxy Nexus] franciscofranco:
Yes, don't worry, Google is just doing some standard procedure verifying who I am etc :) will be sorted soon.
[Samsung Galaxy Nexus] rommel500:
Ahh ok thank you for the response, Do you know if this will be sorted today?
[Samsung Galaxy Nexus] franciscofranco:
I can't say, it doesn't depend from me ;)
[Samsung Galaxy Nexus] Shetlander:
Would this be a setting in the overclock screen of your app. If so I think it would be a good idea to give the option so it can be tested to death and see if the setting does infact work or if it is a placebo effect.
[Samsung Galaxy Nexus] franciscofranco:
Yes, that's something I'm gonna work on tomorrow, definitely.
[Samsung Galaxy Nexus] slg60:
Can you give me the Settings for this Score?

I never come to this!

My CPU is @ 1350 with Nightly 12 and With governor interactive I come to max 6200 and with conservative I get maximum 6550. What makes the difference?

Tolerances?
[Samsung Galaxy Nexus] yohinomura:
Bro, try to change to performance governor. See if it helps.
[Samsung Galaxy Nexus] bradm23:
Anyone having issues with trial extreme 2 force closing?
[Samsung Galaxy Nexus] :
Hi,

Brake my own score :D :

Running at 350Mhz-1.35Ghz/Ondemand/No reboot:

Second bench after reboot/Same settings...

Battey drain...In normal use (for me,i've posted my battery drain a few pages ago) about one day (a bit more),with multiple benchs... (half a day :D).

In any case great and best kernel for Gnex,no issues :)

All is perfect...Expect a little OC to 1.42Ghz...I know it is not expected :rolleyes: (ok LOL)

Always the best kernel i tested :eek:

One thing,as i understand and read,no GPU overclock with this nightly #12,no difference in benchs,ok,but no one has noticed a kinf of lag just in transition (animation) ?

If in your app could have the choice to overclock the GPU it would be great (like mentioned a few pages above)!!!Or via Sysf...

A few beers for you: 0VN22346W1812871S :D for the best work for ours Gnex :cool:

Do not drink too much :D :D :D :eek: :cool: :)
[Samsung Galaxy Nexus] rosswaa:
It wont let me buy the updater app!! Says your not able to accept at the moment??
[Samsung Galaxy Nexus] zephiK:
Read previous page,
[Samsung Galaxy Nexus] DJ "suMo*:
Yo franco, can we get that 525MHz slot from faux? Loving the app.

Sent from my GN
[Samsung Galaxy Nexus] -Phazenine-:
Is this kernel safe for Eagles Blood? Best recommended Cpu settings?
[Samsung Galaxy Nexus] Deus_eps_machina:
Why can't I buy the updater app from the market? It claims its not compatible?
[Samsung Galaxy Nexus] gundamboy:
aww man, the kernel stops paulobrien's ir9 update from booting. :(
[Samsung Galaxy Nexus] MarcLandis:
Did you select the 4.0.3 compability in the kitchen options?

Marc
[Samsung Galaxy Nexus] rafi300:
This kernel has drastically improved screen on performance and stand by time. Attached are pictures.

Sent from Google's flagship device, Galaxy Nexus using xda premium
[Samsung Galaxy Nexus] sileniusmike:
The updater app shows latest nightly as r300. I'm running 4.2.

Can you update it?
[Samsung Galaxy Nexus] kuronosan:
I tried 328 on my vzw gnex and it doesn't boot past the Franco animation.
[Samsung Galaxy Nexus] franciscofranco:
I'll update it when its finished, I have a real work now, less time to code the app, only after I leave the job.
[Samsung Galaxy Nexus] timbck2:
r328 is only for 4.2... Are you by chance running 4.1.x?
[Samsung Galaxy Nexus] thisguy23:
Franco the Zen kernel just got tethering on 4.2. Not sure how, but maybe you can see from his git.
[Samsung Galaxy Nexus] MaLiXs:
I would like to know if there have widjet like cpu temps and speeder with your toolbox?
[Samsung Galaxy Nexus] Savant:
He reverted the kernel drivers so they are not using the 3.4 ones anymore.
[Samsung Galaxy Nexus] Tommy_FIN:
Idle drain is awesome with 328! Only 4% in 12 hours. Also no sod's or lags. Running smooth.

Settings:

537-1305

interactive (1036 hispeed_freq, 729 input_boost_freq)

537 screen off max
[Samsung Galaxy Nexus] syncopy:
Yes, it does. But, if you install PGM and get SODs, get rid of PGM and test.
[Samsung Galaxy Nexus] kuronosan:
No.
[Samsung Galaxy Nexus] akash3656:
Then it's about the same as your temperatures. At day, outdoors it can go up to 38 haha. Now I recall, yes this phone does stop charging for me if its plugged in on a hot afternoon with heavy usage (such as flash videos or games).

With normal usage such as phone calls, continuous whatsapp texting, and music playback, the phone charges fine.

I recall the battery reporting "Not charging" before with Franco kernel during the early 4.1.1 days (July/August?), but not anymore.

Then again, I don't use a case. Not even a screen protector. I guess this reduces the amount of heat trapped within the phone.

And yes, this phone doesn't charge up the battery even when its plugged in IF the battery is a above a certain temperature. I think the limit is about ~50°C

It's a safety feature.
[Samsung Galaxy Nexus] isaacraja:
Data connectivity problem

Hi,

I know there are some issues with Wifi tethering in r328. But any one experiencing data connectivity problem (edge/ hspa).

It connects sometimes when the wifi is on, but sometimes it don't. This could be related to kernel? Any have ideas on how to debug?

Thanks
[Samsung Galaxy Nexus] franciscofranco:
I know. That will be fixed tomorrow with a new kernel release.

App v8.1 is also almost ready with 4.2 support. Its in testing phase at the moment
[Samsung Galaxy Nexus] 5nickers:
Will the Galaxy Nexus get the 3.4 kernel as the nexus 4 already has?
[Samsung Galaxy Nexus] gianton:
Great news mate, r328 on AOKP Nov 27th build running rock stable with excellent battery life.

Are you going to use the old WiFi drivers with WEP support? I miss that, as most public routers use the WEP security.
[Samsung Galaxy Nexus] gummie:
Oh so that's why I cant connect when I'm at Malls or public hotspots. Yep this definitely must be implemented as not all people just sit or lie down couches and hug pillows :laugh:
[Samsung Galaxy Nexus] joaquinf:
Ok i'm gonna post this here because i want to hear some feedback and what do you guys think:

Yesterday I experienced a weird issue with the latest rasbeanjelly build. I've had the same weirdness before (just in 4.2 ROMs) but it was gone for a couple of 4.2 builds, now is back.

When I manually reboot my phone and i let it boot completely without touching it at all (i.e: hold down power button, reboot, phone turns off then on again, slight vibration and google splashscreen then android boot animation, here it comes the lockscreen and a couple of secs later the screen turns off) everything is normal but, 10 seconds later the phone reboots itself unless i unlock the phone within the first 5 seconds while the lockscreen is still shown and the screen on. If i don't touch the phone it will keep "bootlooping". <-- this is something we all know for a couple of days back (disabling/enabling CAB isn't working anymore as a valid fix)

To add some weirdness to the recipe, after getting out of that reboot trance the initial setup screen is shown :eek: i have to go through, select the language, type the owner name and then "the setup is complete". For some apps, like whatsapp, app data and preferences is gone and back to default :( i really don't think this is a kernel issue because of the last part where the UI is all f***d up.

Any clue? my setup is as described in my signature, no UV
[Samsung Galaxy Nexus] Khrushy:
The boot looping sounds like Context Adaptive Brightness bug. If you have CAB disabled in the FKU app then it causes those bootloops. (I can replicate them too by disabling that check box on my system)

The needing to re-setup each time I have no idea about - that's a new one to me.

---------- Post added at 12:57 PM ---------- Previous post was at 12:55 PM ----------

Sorry I meant "I can replicate that bug by ENABLING that check box on my system" (setting CAB to disabled)
[Samsung Galaxy Nexus] joaquinf:
Thanks i've tried that and it was working before 4.2.1 now isn't working, however, for me it worked the other way around, disabling cab (checkbox checked) caused bootloops and if i unticked it everything was fine :eek:
[Samsung Galaxy Nexus] ChazzMatt:
So they can steal your personal information. The only people who use WEP on routers are the ignorant and criminally-minded. Think about it. :rolleyes:

WEP has been cracked -- it's NO protection -- for this entire century, a dozen years now. Even 12 year olds have no problem downloading apps that will crack a WEP router in seconds/a few minutes. Then, they just wait for you to connect. It's common knowledge, just like knowing Lindsay Lohan will be arrested again. :D

I understand many people will gladly take convenience over security. But there's a very urgent valid reason the new drivers don't support WEP.
[Samsung Galaxy Nexus] The Gingerbread Man:
Bump your min voltage up by 25mv from what ever smart reflex is calibrating for you and also make sure f sync is enabled

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
That's what happened to me when we first started testing the r32x builds! I was like "holy **** it just wiped my system settings" and franco said "that's not funny". No joke though, it took a couple other apps with it just like you say. I never tied it down to unlocking the lockscreen or anything like that though. And the craziest part was fsync was on.

Happened to me again late the other night with r328 because my battery was super low and one of my chargers is from an older phone and likely didn't have the amperage to keep the phone running through a boot. Anyway once I got a bit of a charge into it and put it on my better charger it booted up just fine; but again, I had to redo the "one time init" setup, and redo my Disabled system apps and other system settings, even though fsync was enabled. A little disconcerting.
[Samsung Galaxy Nexus] suxLV2:
CM 10.1

Boot-loop on GNex running CM 10.1 (4.2) @ r328
[Samsung Galaxy Nexus] gummie:
That maybe be a valid argument but still... Nah! I my self is a danger to WEP security as well :p so I guess this is a good measure for further security though, I might as well live with this new driver :laugh: Just use my 3G instead when on public.

EDIT: Tomorrow going to nearby Mall and ask management to upgrade WiFi security (not for security though but so I just could connect with it LOL)
[Samsung Galaxy Nexus] osm0sis:
As much as we might like it to be true, there is no "urgent valid reason." There is no overarching scheme to push the Wi-Fi world forward here; it's just a bug. WEP works in the 3.4 drivers on the N4 where they came from. The reason they don't work for us is because they got broken in the porting process, nothing more, nothing less.
[Samsung Galaxy Nexus] SahilC:
Hey, can anyone recommend a good 'close to stock' rom?
[Samsung Galaxy Nexus] Khizar:
bigxies 4.2.1 aosp
[Samsung Galaxy Nexus] gummie:
Try PA 2.99.5 plus you have addon features you might like.
[Samsung Galaxy Nexus] Khizar:
how exactly is that "close to stock"? lol
[Samsung Galaxy Nexus] osm0sis:
Well at least it's based on AOSP now. ;)
[Samsung Galaxy Nexus] whitedragonz83:
Cataclysm http://xdaforums.com/showthread.php?t=1995801
[Samsung Galaxy Nexus] tetrakinitis:
RasBeanJelly

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] Khizar:
lol thats true and its pretty good but comparing pa to stock is like insulting pa
[Samsung Galaxy Nexus] SahilC:
Looool.

Yes. I think I'll be trying Linaro's stock.
[Samsung Galaxy Nexus] joaquinf:
Humm yep i forgot to mention that some system settings like sound (notifications, vibration) were messed up and disabled apps were active again and hidden apps were visible on the drawer (like cerberus, poweramp license, haxsync wizard) i've cleared fku data and i'm pretty sure it has something to do with color control. I'm trying to trigger the reboots again with no luck
[Samsung Galaxy Nexus] osm0sis:
Ah yes, I forgot about those hidden ones, yeah, license keys and whatnot. So perhaps that helps narrow it down. Launcher is what's having its data wiped?

I've been running CAB enabled for a month now, and all my color settings are done via init.d during boot, so I really don't think that could be it... :confused:

It's LIKE a voltage instability, but it doesn't occur under any normal conditions including performance governor for any of the freqs and gaming. For me the couple times it's happened they've just been a random **** where the screen freezes, goes bright purple then reboots.
[Samsung Galaxy Nexus] joaquinf:
I've re-done my color settings after a fku app data wipe and everything is exactly the same way as it was when i was having those nasty reboots and i now can't manage to trigger anything. This is my 12th reboot and nothing has happened ... nothing. Only thing different is that i had disabled logger and events logging now they are enabled, could be it?

EDIT: now testing fsync off; logger off; events logging off ... let's see how it goes

EDIT2: third reboot and nothing, everything is stable after a manual reboot with the same config i had when facing those reboot issues ... somehow clearing fku data fixed the issue temporarily

EDIT3: CAB is unticked (enabled) and nothing
[Samsung Galaxy Nexus] osm0sis:
Nah I just honestly think it doesn't have anything to do with f.Ku, I think it's a random kernel edge case that will hopefully get worked out as franco goes through and tries out fixes for Google's terrible coding in JB 4.2.
[Samsung Galaxy Nexus] joaquinf:
Indeed, random ****. I couldn't replicate the issue anymore. The strange thing is that data loss in the launcher and system/settings app :confused:

EDIT: funny thing is that i'm kinda frustrated because now i don't have those reboots :p
[Samsung Galaxy Nexus] navyguy:
Mmuzzy 4.2 AOSP. It is very stable and he is very active in support of his ROM.
[Samsung Galaxy Nexus] klobkelosh:
+1 for Mmuzzy's ROM. Also Mwalt2.
[Samsung Galaxy Nexus] kyokeun1234:
My data drops randomly with this kernel. Using 4.2.1 deodexed stock ROM. Sorry if it already has been discussed. If you need anything, just tell me. Just rebooted.

Edit: I am using stock setting with minimum frequency of 500 and max screen off of 700
[Samsung Galaxy Nexus] navyguy:
The fix is coming.
[Samsung Galaxy Nexus] timbck2:
Affinity Series if you're ok with 4.1.1 (they'll eventually release a 4.2.1 build, but it's taking a while). XenonHD if you want 4.2.1 now.
[Samsung Galaxy Nexus] supernova_00:
Franco and Minooch's rom, MiNCO! http://xdaforums.com/showthread.php?t=1790532
[Samsung Galaxy Nexus] dratif:
Believe it or not...jumped from a score of 6800 to this....blended xenonHD rc2 with franco r328...thanks to both developers :)
[Samsung Galaxy Nexus] shawnaye:
Believe it or not! We don't care about benchmarks!

Our benchmarks are if you're using your phone. And something ***** up. Post a logcat!
[Samsung Galaxy Nexus] franciscofranco:
I also just started having SoDs as well out of the blue. I really doubt its my kernel, stock also has the same problem.
[Samsung Galaxy Nexus] jcmm11:
Muzzy is great, as long as you're on Verizon.
[Samsung Galaxy Nexus] simms22:
as we have guessed, its something in googles source. but the issue is, cant find what it is. it took a long time before i got my first 4.2 sod too, and the gnex is my main phone :(
[Samsung Galaxy Nexus] osm0sis:
Has everyone getting SODs tried turning off the new Wifi optimization to see if it makes a difference?
[Samsung Galaxy Nexus] simms22:
yes, with and without. i only get them when plugged in, once every 2-4 days or so. but there are some that get them very frequently. and they seem to occur in clusters.
[Samsung Galaxy Nexus] luisqcosta:
Franco, no sod's or reboots on stock. On the other hand with 328 he he he not working here (reliably I mean).

Keep up the good work.

Grande abraço!
[Samsung Galaxy Nexus] osm0sis:
So odd.. I only got SODs before r318. Testing at first with r32x I got those weird bootloops resulting in wiped launcher settings (even though fsync was on), but those seem resolved with r328 except for when I had severely lowbat the other night and was plugged in to my crappier charger while it was trying to boot from off.
[Samsung Galaxy Nexus] yellowdie:
Simms, one of the things we toyed with was having both the new wifi optimization on and wifi_pm enabled at the same time. They seem to be opposite / mutually exclusive. Thoughts? :)
[Samsung Galaxy Nexus] franciscofranco:
Yeah its lame. I have two GN, havent tried it with the other one but might be good to see whats up.
[Samsung Galaxy Nexus] simms22:
i dont know if they interfere with each other. but honestly, i just dont know. i dont use wifi_pm ever, and i rarely use wifi on the gnex. on my seven, they dont seem to interfere with each other.
[Samsung Galaxy Nexus] KJW979:
Haven't had an SoD since r325,then it was only once, no bootloops either. Running 328 stock values other than max/min of 1536/384, fsync on. Currently using latest Eclipse 4.2.1 rom.
[Samsung Galaxy Nexus] simms22:
another set of eyes looking into it definitely wont hurt. what bugs me is that these sods dont seem like any of the other sods that we have encountered before, since the device is fully awake when it happens, just the screen wont turn on. everything else functions as it should. notifications come in, sound can be adjusted up or down, even pop up notifications happen(we just cant see them behind the dark screen).
[Samsung Galaxy Nexus] osm0sis:
What about something wrong with the screen voltage? Also, though it might be an unrelated additional issue, when I got the freezes/bootloops the screen locked up and went bright and purple, making me wonder if something was pushing extra voltage into it.
[Samsung Galaxy Nexus] yellowdie:
My wife has been getting SODs lately and she's on 4.1.2 Rasbean. But she also dropped her Gnex in the toilet on Thanksgiving, so I don't think it's kernel related! Lol! :)

I'm on r328 with no SODs/reboots yet. :D
[Samsung Galaxy Nexus] Leegalaxy:
Since I installed Bigxie's AOSP 4.2 ROM and now his deodexed 4.2.1 ROM I've only been lurking this thread. I've been waiting until Franco feels the Kernel is ready to be loaded into the app (ready for prime time if you will).

That said, I've not experienced any SODs or freezes with this so-called stock-ish ROM. And battery life has been pretty good.

While 4.2 and 4.2.1 are considered incremental updates, I really think there have been a lot of changes in the background that must be causing all of these issues.

Just my 2¢ :rolleyes:
[Samsung Galaxy Nexus] franciscofranco:
I think might be something to do with that strange lag when shuting the screen on/off since 4.2.
[Samsung Galaxy Nexus] simms22:
I also think its related, or at least a symptom of the same issue.
[Samsung Galaxy Nexus] jeetS:
I have been running bigxies 4.2 and now 4.2.1 with r318 with zero issues.. I've been hesitant to try 328 with all the issues people have been reporting...
[Samsung Galaxy Nexus] harmohn:
I've got your setup, but with r328 & no issues at all. You could always nandroid backup before you try ;)
[Samsung Galaxy Nexus] akash3656:
I had a SOD on 328 also... Its quite random. People seem to get them when charging. Yes I get them during charging too. However, I also seem to get it when answering a phone call or making a phone call. When it happens when I answer a call, I can't hear what the person at the other end is trying to say.

When I make a phone call and when it derps, my call will be totally silent. I will never hear the operator ringing tone. And I have to battery pull to get it working again.

Once I also had it when I was having my lunch, after my lunch, the phone was shut off. A long press on power button got it to boot.
[Samsung Galaxy Nexus] osm0sis:
r328 isn't the problem though.. it's JB 4.2. :eek:
[Samsung Galaxy Nexus] fatappel:
really impressed with r328 while running along side of 11/30 aoskp 4.2.1. will be perfect once tethering is fixed

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] alexdemonumber3:
I don't know where these SODs are coming from, but I've yet to experience one. Running r328 with Xylon 0082, silky smooth
[Samsung Galaxy Nexus] gianton:
No SODs here on r328 and AOKP for the last 6 days with this combo. Maybe I'm lucky lol.

Battery life is the best so far since I switched to 4.2. Great work Franco!
[Samsung Galaxy Nexus] rmcsc:
I'm sure that lag is related to the new lockscreen.
[Samsung Galaxy Nexus] Savant:
I have tried the app and I haven't had an sod in awhile. The app revert the lockscreen like it used to be and works perfectly .https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.deviceadminkeyguard
[Samsung Galaxy Nexus] Misledz:
Ah yeah, I saw this featured on XDA Portal :P Was wondering about it.

Not sure if the SOD is 4.2 stock related or it appears in other ROM's too, Been using rasbeanjelly since the 29th and 328 and I can't say there's been any SOD, apart from the usual laggyness that's 4.2 oriented, I'd say franco's done pretty sweet on this one.
[Samsung Galaxy Nexus] franciscofranco:
Ok app has been updated to 8.1 with the following changes and should be up as soon as Google updates their servers, as usual.

8.1

* 4.2.x franco.Kernel added for Galaxy Nexus and Nexus 7

* Added XDA thread links to the Menu

* Fixed bugs in Backup&Restore + automatically add kernel version string to the editable text zone

* Reworked Power Modes creation panel

* Added toggle to add 4 Power Modes presets - only for Galaxy Nexus for now, more comes later

* Added CORE and IVA freqs display to the voltages section

* About me links fixed

* Added Turkish translation - thanks Muhammed Occan

* More changes...

New nightly r335 should be available in roughly 20m, just finishing something up.
[Samsung Galaxy Nexus] Khizar:
yup same here.. been using r328 since it was released and no issues
[Samsung Galaxy Nexus] gianton:
Thanks for the updates!
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco your such a genius you are able to post here and update apps and create kernels since before you were born or even a twinkle in your father's eye, 1/1/1970 you posted this according to tapatalk :p looking forwards to the updates and hope you can look into headphone boost soon :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shawnaye:
well i on the other hand can't wait till franco finds his hands on those pesky bugs that those dumbass clowns at google introduced into the 4.2 kernel. to hell with google techs! franco is a one man show! :good::good:
[Samsung Galaxy Nexus] rz32:
Thank you! Changelog for 335?
[Samsung Galaxy Nexus] franciscofranco:
/facepalm... its not even out yet.
[Samsung Galaxy Nexus] bat0nas:
EDIT: I see it will be solved in app update. Please ignore my message.

I have stock 4.2.1 android but Updater app gives me r300 and not r328.

Any ideas?

View attachment 1526457

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Update the app, done.