yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
So it's only franco.Kernel, Lean Kernel and Stock kernel? Yeah that's weird. Which ones DO work?
[Samsung Galaxy Nexus] calinoii:
I'm using faux's kernel for over a mont now and it works greate,not even a freeze, and i'm satisfied,I tried trinity too and no freezes,but i liked faux more.But you know...I want franco's
[Samsung Galaxy Nexus] Bonvaz:
Guys I remember that with old version of franco kernel if I flashed it from recovery the i had to flash sd original binaries or something like that.. Do I have to do it also now? Not using franco from ages..
[Samsung Galaxy Nexus] osm0sis:
Well that's really peculiar. I'd try flashing stock again using fastboot. I'd fastboot oem lock, then fastboot oem unlock to wipe, then flash the entire image set as in efrant's thread just to make sure it all gets wiped. But unfortunately, like I said, if stock kernel doesn't work over a fresh fastboot flash of Google's factory image on your device there's still something very wrong, and it's likely wrong with the device itself.

Nah, the sdcard binary issue has been resolved since Franco started rolling non-test JB4.2 builds. It doesn't replace the stock binary anymore. You're good to go. :good:
[Samsung Galaxy Nexus] Kurre:
This kind of post doesn't help anyone actually..and I said that "feel free to correct me", so...? ;)

I'm pleased to stand corrected if facts are brought to the table with some proofs...that isn't a problem to me :)

season greetings to you also :D

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] calinoii:
I wiped everythng,but I still did a backup of some pics and mp3's,is this ok? I think it's not doing anything wrong. Could this be because of takju/yakju thing ? Btw could i have a Verizon model? I bought it from Vodafone Romania,it was unlocked and the latest android version was 4.1.1 a month ago,when i first flashed a custom rom :-/ not even 4.1.2 .I saw that this is the latest OTA for Verizon.
[Samsung Galaxy Nexus] neverhappy:
Gnex random mac address

Strange issue here:

So it has been a year since I purchased my GNEX CDMA LTE. During that time I have loaded many ROMs and most all of Franco's nightlies.

I recently began using the JBSourcery ROM. I did not use the Franco kernel at first, just to see how the package ran out of the chute. When I came into work this week I could not access my work network via the wifi. I noticed my MAC address had changed on my device. How could this be?? Well it did. Yes, my workplace has MAC access list lookup(I know, pretty barbaric). I then noticed the phone randomly changing the MAC on each reboot of the phone. Needless to say, my IT was not too happy with me asking to have the access list adjusted each time. I decided not to ask again until I could figure out why this was happening http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=23330

I then read that Franco and other Devs appear to have taken measures to try to eliminate this randomization. So, I loaded nightly 384 and now the random mac assignment has stopped. The problem is, while the random MAC has stopped, it has locked on the last occurrence of random MAC assignment. So for a year, I had the factory MAC starting with 2c:44:01 and now I have a MAC starting with 00:90:4c.

I'm looking for a way to get back to my factory issued MAC. One that does not require me to have a degree in Software Eng. Any Ideas?
[Samsung Galaxy Nexus] iNeedICS:
Hmm did u flash the maguro version instead of the one that's for the cdma?

Also have u tried restoring a nandroid? Maybe you can get your original Mac add?

Sent from my iPhone smashing GNex
[Samsung Galaxy Nexus] osm0sis:
Pretty sure what you said was correct too, Kurre. :)

Backing up to your PC doesn't matter, but if you've properly wiped your phone completely then sdcard should get wiped too. I'm suggesting this so that you can know you're completely starting from scratch. So, follow the instructions in my last post and that will ensure you've got a completely clean slate, then use the latest Google Factory Image for your device like I suggested, then you can see if you get the OTA immediately or you can flash it yourself. Do all this before you put any apps on, and don't let it put any apps on and see if you still have the issue with a completely stock setup. Anyway we're definitely off topic here, so start a thread over in Q&A if this doesn't resolve your problems. ;)
[Samsung Galaxy Nexus] whitedragonz83:
If Franco implemented it the same as Morfic (Trinity Kernel) it will not change anymore.

http://xdaforums.com/showpost.php?p=28866239&postcount=11656

I am surprised you didn't have this issue occur sooner since every reboot should have changed your MAC address (without using a custom kernel). Maybe someone else can help find a way to "pick" your MAC address, but I wanted to provide this information above at least.
[Samsung Galaxy Nexus] calinoii:
http://xdaforums.com/showthread.php?t=2055260 this is my thread,and I have some others with the same problem,but thisis the latest,no one could help me this far.I already did what you suggested me...I`m sure I did the clean wipes,just installed gapps and nothing else...when it was getting little hot the freezes were starting too,I think i did all I could,many people in this forums adviced me and still nothing,maybe franco's the only one who can help me with this...
[Samsung Galaxy Nexus] neverhappy:
JBSourcery V4.1 - LTE - Official Release

---------- Post added at 02:04 PM ---------- Previous post was at 01:55 PM ----------

Must admit, I have used the Franco kernel 99.95% of the time. Got a few beers in me, went out and cheated on Franco and Got a STD: :eek:
[Samsung Galaxy Nexus] malaroth:
Sourcery 4.1 is a version number. It's a 4.2.1 based rom. However I've had zero problems so check your apps

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

---------- Post added at 04:28 PM ---------- Previous post was at 04:22 PM ----------

No... version 4.0 starts the 4.2.1 source. There's just already been major additions of the classic ultra themeable sweetness that is the sourcery rom hence the change in sourcery build numbers

JBSourcery 4.1 + r348 Franco FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] bigjohns97:
I'm on JBS4.1 myself and switched over to franco kernel last night and had a SoD today at work.

not doing any special overclocking or undervolting, is this common?
[Samsung Galaxy Nexus] malaroth:
Some silicon just does that unless you can pinpoint an app or process. I've been using Franco since I rooted to the first jellybean. Mine only has one point where I get SOD.

JBSourcery 4.1 + r348 Franco osm0sis UV settings FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] bradm23:
With any 4.2+, yes it is a common Google issue
[Samsung Galaxy Nexus] timbck2:
My battery has been draining very quickly the past couple of days... There's a process called "vbus-tuna_otg" that seems to be pulling a lot of juice (see attachment) according to BetterBatteryStats. I upgraded a couple of days ago to StickMount Pro, which is the only thing I can think of related to OTG. I haven't had an OTG adapter attached, however. Any ideas?
[Samsung Galaxy Nexus] osm0sis:
I'd definitely uninstall StickMount and its corresponding Pro key and see if that resolves it. If so, then I'd report it to Chainfire. ;)
[Samsung Galaxy Nexus] marcocsh:
OK I tried reverting back to r345 and it is better now. But still very little glitch persists when using poweramp to play FLACs. I will live with it however.:o
[Samsung Galaxy Nexus] Khrushy:
New AOKP nightly with OTG enabled? Could also be a bug in the OTG seeing as it hasn't been officially merged yet.
[Samsung Galaxy Nexus] grotesque02:
Is better keep fsync enabled?

Can occurs serious problems if I disabled?
[Samsung Galaxy Nexus] timbck2:
I'll do that. :D

No I'm running XenonHD (AOSP).
[Samsung Galaxy Nexus] timbck2:
That doesn't seem to be the problem. I uninstalled StickMount, fully charged my phone (to 96%), then unplugged it and it's already down to 89% basically sitting idle for 30 minutes (besides tapping out this post). I don't really know how to interpret the stats from BBC, so I've attached a screen shot (I don't even know if this is the right screen to diagnose the problem). I turned off GPS earlier today because it was spending a lot of time trying to lock. Thanks in advance for any help you can provide.
[Samsung Galaxy Nexus] osm0sis:
That's not the right screen. Those are all normal. Show us partial and alarms. Also you should update BBS. :)

Not sure what to tell you. Maybe reboot first then try again? Dirty flash your ROM, or failing that fully wipe and reflash? The usual s**t really. ;)
[Samsung Galaxy Nexus] alexdemonumber3:
Can anyone tell me why I can't get deep sleep on r348 with android 4.2.1 on a sprint gnex?

sent from my galaxy nexus

hit that thanks button if I helped you
[Samsung Galaxy Nexus] shreddintyres:
with out any additional information, no, you need to provide at the very least, rom, kernel settings, and log cats, better battery stats screens would also be helpful.
[Samsung Galaxy Nexus] malaroth:
If you could do an in depth post as to required information to solve even basic problems that'd be great osm0sis. 500 word minimum please....and your TPS reports are behind schedule. Kindly amend them as well :P thanks for taking your time to help us man. I appreciate it

JBSourcery 4.1 + r348 Franco osm0sis UV settings FTW. Keep the Magic alive!

---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------

Plus...make sure you tick the "include deep sleep" box on whatever. CPU monitor you're using

JBSourcery 4.1 + r348 Franco osm0sis UV settings FTW. Keep the Magic alive!

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

Plus...make sure you tick the "include deep sleep" box on whatever. CPU monitor you're using

JBSourcery 4.1 + r348 Franco osm0sis UV settings FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] alexdemonumber3:
Alright its the AreYouJellin ROM which is 4.2.1 and Franco r348 with stock settings. Logcat is not physically possible to get ATM, but my brother just flashed it over the ROM and deep sleep is just not working.

sent from my galaxy nexus

hit that thanks button if I helped you
[Samsung Galaxy Nexus] yodanutz01:
i'm i the only one who is having very bad battery life with 348? i used bigxie stock, deodexed rom, and my battery was very bad...
[Samsung Galaxy Nexus] gaich:
In Poweramp I found the solution - check "direct volume control" in settings-sound-additional and you`ll not see this reminder anymore.:cowboy:

---------- Post added at 08:40 AM ---------- Previous post was at 08:37 AM ----------

I am running the third or the fourth circle, it seems to me that the problem is still present...
[Samsung Galaxy Nexus] Khizar:
i am using r348 with osm0sis settings and am getting pretty good battery lfie
[Samsung Galaxy Nexus] bajsmumsaren:
You could try r345 instead and see if you notice any difference, I'm getting awesome battery life with that one.
[Samsung Galaxy Nexus] The Gingerbread Man:
Ah I use Google play music so that won't work for me as no such option exists, glad you fixed it it though!

As for battery drain, I'm finding 348 to give the best battery iv ever seen. I would blame funky roms if your having issues. Yesterday again I went over 3 hours screen in and some 16 - 18 hours off charger. I'm on stock 4.2.1 rom, using cfq and under clocked to 192 @ 750mv and Max speed 1228 using smart reflex. All I did was turn off Google now and turn off location reporting in maps and it makes all the difference. The rest are stock settings.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gaich:
Yes, I think it is rom`s fault. Will test on Minco when it`s ready...
[Samsung Galaxy Nexus] The Gingerbread Man:
Even stock rom isn't that bad, apart from a couple of minor things like those spazzy music widgets I said about other wise its OK :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] allgsmnetwork:
I tested yesterday and today r348 for me 345 better performance and battery we will see during the day...

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] gaich:
Oh, no, after reboot it came back...:crying:
[Samsung Galaxy Nexus] Murrzeak:
Guys, can you explain why I can't boot after installing the latest stable release atop of CM10.1 (latest nightly)? The auto-flash from the Franco's app did download the kernel and tried to flash it, but the system booted with the stock CM kernel somehow. So I flashed it myself from recovery and couldn't pass the Google logo. I've cleaned dalvik and cache, but no luck. Sorry if it's a nube issue..
[Samsung Galaxy Nexus] gianton:
R348 on AOKP Roman 1218 build. 384/1536MHz max screen off 537MHz interactive/cfq/westwood with osm0sis UV settings.

Great work Franco!

View attachment 1581185 View attachment 1581187 View attachment 1581188 View attachment 1581189
[Samsung Galaxy Nexus] Khizar:
i dont think this kernel changes roms boot animation or at-least it never changed it for me.. as for being stuck at boot logo, did you wipe FKU data before flashing the kernel? if i didnt do that i got issues sometimes...
[Samsung Galaxy Nexus] The Gingerbread Man:
I would say it's probably a ram disk issue, I did think franco make it compatible with cm unless they changed something else their end again. You'll need to either stay with their stock kernel or change rom

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] smileyanz:
Yeah I done the same by taking that advice and can't believe the dif it makes. Really is bang on the mark. And I download and mess around a lot on it. I can see a stable surfacing shortly. Franco rules!!!
[Samsung Galaxy Nexus] Murrzeak:
Nope, I didn't..

Right. That's not cool. :(
[Samsung Galaxy Nexus] The Gingerbread Man:
I suspect m7 might drop with minco v6 but I won't bet on it in case I'm wrong ;)

Sent from my Galaxy Nexus

---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------

Well I'd suggest changing roms personally but its your choice

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
might wanna clear the apps data and then flash the kernel again... i am not a expert on kernels but it doesnt hurt to try.. if it still gets stuck then it is most likely a rom issue
[Samsung Galaxy Nexus] The Gingerbread Man:
He's stuck at boot animation so I dought app data would make any difference as it should actually boot then reboot once f.k.u gets su permission. Its either rom or ram disk or just generally cm being a pita as they like to be :rolleyes::p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
yeah i was actually getting stuck on boot animation with one of the franco kernels and clearing app data fixed it.. so my advice comes from experience ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
I see, my advice to all would be unset any set on boot options you have when updating the app or kernel just in case and that help eliminate some potential issues

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Follow the emergency zip link in my sig. It wipes f.Ku settings among other things. Might help the guy.
[Samsung Galaxy Nexus] Khizar:
agreed.. that does cause issues, i learned the hard way lol

---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------

hey thanks for posting that zip bro..
[Samsung Galaxy Nexus] The Gingerbread Man:
Hopefully Franco can add some kind of mandatory download for that from the app with an update

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Yeah he said he'd put it in the OP awhile back, and I think that would be good enough. But you know how he is with keeping the OP updated. ;):p
[Samsung Galaxy Nexus] Murrzeak:
Hm...I think I found the solution :)) Somehow the free version on Franco's Updater offered me a Milestone 4 kernel which can't be used with 4.2.1 ... I should've checked this thread beforehand. Sorry guys, the nightly r348 booted up nicely.
[Samsung Galaxy Nexus] osm0sis:
Hah, there you go! When in doubt, read the thread title. :p
[Samsung Galaxy Nexus] Paragon_X:
I can hit around 3 sometimes, mainly a bit over 2 however it's a combination of wifi and 3g. Usually half n half... how about yourself? Are you dedicated wifi or 3g? I'm running AOKP 12/18 now.

---------- Post added at 10:28 AM ---------- Previous post was at 10:21 AM ----------

Same here mate but much less than 348. It's a shame because Google Music seems to eliminate any skipping but the sound doesn't equal anything anywhere near Poweramp. I'm using the Noozxoide EIZO-rewire and it's bumpin!
[Samsung Galaxy Nexus] The Gingerbread Man:
I use WiFi at home, my parents and gf's parents but at work I don't have access to WiFi

That's my stats for so far today

I always keep WiFi turned on

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] neverhappy:
Follow-up for anyone that cares:

So I ended up diving into my random mac address issue this morning. Found and followed this process: http://xdaforums.com/showpost.php?p=28939877&postcount=46

Had to revisit my limited adb skills. The fix works and now my factory mac is back and not changing on reboots. Not sure what caused this, but it looks like many others have had this happen as well. Hopefully this does not creep back in at some point, but for now, all's good.
[Samsung Galaxy Nexus] The Gingerbread Man:
Direct mandatory download from the app would be best

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] allgsmnetwork:
very the best 348

Really good the battery with the franco kernel 348 with the settings posted in the signature by osm0sis undervolt + 25 all mhz only CPU down values ​​then being calibrated even better I did everything, google+, facebook, benchmarks, web browsing, vodafone speedtest with 3.5 mega down and 2.5 up, and yet the remaining 30%, I would say very good better than this' always to 1536 mHz...:good:

I also added the Undervolt in IVA and CORE ;) no reboot,no problem :good:

CPU voltege:

1804mhz: 1450 mV

1728mhz: 1400 mV

1612mhz: 1350 mV

1536mhz: 1300 mV

1420mhz: 1250 mV

1305mhz: 1200 mV

1228mhz: 1150 mV

1036mhz: 1075 mV

729mhz: 950 mV

537mhz: 850 mV

384mhz: 800 mV

192mhz: 750 mV

IVA Voltage:

(mhz (mV)

133	900

266	1100

332	1275

430	1350

Core voltage:

(mhz) (mV)

153	875

384	1025

512	1100
[Samsung Galaxy Nexus] vigan_ks:
View attachment 1581909
[Samsung Galaxy Nexus] Pumpino:
I switched from stock to Cataclysm yesterday and decided to flash Franco's r348 several hours later. One of the benefits of switching from stock to Cataclysm was that wifi would no longer switch off when the phone went to sleep. However, since flashing r348, wifi is switching off again. Is this typical? Is there a way of sticking with Franco's kernel and having wifi remain on? Otherwise I'll have to switch back to Cataclysm's stock kernel. Thanks.
[Samsung Galaxy Nexus] Paragon_X:
Well I'm assuming you've check under the wifi options that you can keep it on when the phone goes to sleep? Quite honestly I've never heard of that being a problem relating to a kernel, the option is present on stock or modded roms.
[Samsung Galaxy Nexus] F_T_B:
I feel like I have to intervene here -- Wi-Fi powers down when the screen is off because you enabled a setting (or it is like that by default). That's an option with every ROM that i used so far.

Check out Wi-Fi -- Advanced and see if "Keep Wi-Fi during sleep" is set to "Always".
[Samsung Galaxy Nexus] Pumpino:
Yes, it's on the default setting which is to stay on during sleep. Since switching back to Cataclysm's stock kernel, the issue has resolved itself, so it looks like a kernel issue.
[Samsung Galaxy Nexus] allgsmnetwork:
but use it only for phone calls?impossible can you show the exact values​​, wifi, screen on time, online or airplane mode so 'it's not clear how you use it :rolleyes:
[Samsung Galaxy Nexus] F_T_B:
I find it hard to believe that the stock ROM doesn't keep the Wi-Fi on during sleep if enabled. And I also struggle to see how this is a kernel issue.
[Samsung Galaxy Nexus] Pumpino:
Wi-fi turning off during sleep was a recognised bug in stock 4.2.1.

I'm simply reporting my observsations - wi-fi stays on with Cataclysm's included kernel but not once I've flashed Franco's kernel. Whether or not it "should" do that is irrelevant to me. I'm looking for a solution. :)
[Samsung Galaxy Nexus] mariosraptor:
Sorry first of all for what i will say.

I have disabled the loggers in Franco app. So i won't post log.

I left my phone in airplane mode to charge for hours and when picked it up it was on SoD. Last time i saw phone was at 97% .

After SoD i pulled battery and when i turned it on again was at 92%.

I will re-enable logs in event this happens again

Cfq, min screen off 384, interactive, max cpu 1305 stock voltages. R348 on Purity v2.

Thanks.

edit. i can only provide bug report since uptime cause when i try fr las kmsg i get Unable to open log device '/dev/log/main': No such file or directory
[Samsung Galaxy Nexus] osm0sis:
No problem with that on franco with stock ROM here. Wifi stays on just fine.
[Samsung Galaxy Nexus] -star-:
The only weird WiFi behavior I could recognize is that the status bar icons turn from blue to grey and back to blue again after I unlock the phone.
[Samsung Galaxy Nexus] F_T_B:
Right. Nor with any lightly modded ROMs. Something is going on there...
[Samsung Galaxy Nexus] mikeandjaimie:
Actually a few things can cause the issue with wifi dropping, and saying that it can only be the one thing or he's wrong just makes you look ignorant imho.

Try checking to disable the option for wifi optimization under advanced wifi settings in your ROM, i've also seem this behavior from the avoid poor connections option in the same area. Also, which has fixed this problem for many in the past, is checking wifi pm fast on, in francos app. This gives the wifi a bit more juice and helps keep the connection alive. In order for me to get my wifi working as it was pre 4.2 I had to do all 3.
[Samsung Galaxy Nexus] marjaN_:
which rom should i use with this kernel? :)
[Samsung Galaxy Nexus] dannejanne:
Anyone.

Tapatalked
[Samsung Galaxy Nexus] BigBake88:
I'm running Rasbean Jelly with 348 and it's great!

---------- Post added at 07:57 PM ---------- Previous post was at 07:51 PM ----------

I have noticed this as well. I am running RBJ with 348 and it happens sometimes. It loses connection after an extended period of time and when you turn the screen on the wifi symbol will come back and then go from grey to blue. Unchecking WiFi optimization helped some. I saw this on Tiny's kernel as well so I think it is more related to the OS rather than FK...
[Samsung Galaxy Nexus] Pumpino:
Thanks for believing me. The above suggestion not only resolved the issue when using wireless with Franco's kernel under Cataclysm, but also resolved the issue when using stock 4.2.1. Since this was the main reason I decided to try a custom ROM, I've restored the backup of stock I took prior to flashing, and it's working well. Funny how trying Franco's kernel has led to a solution to my wireless issues.
[Samsung Galaxy Nexus] jeetS:
Minco v6. Wait a few hours it will be released
[Samsung Galaxy Nexus] allgsmnetwork:
test 348 finish very the best all kernel of franco also 345 is good :cool:
[Samsung Galaxy Nexus] allgsmnetwork:
test 348 with antutu incredible...:cool: