yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Sveke:
Just download gsam battery monitor. Open it. Run your phone like normal for a few hours without charging it. Go into the app again, click on app usage, see whats abnormally high, click on it, see what sub processes are running and trouble shoot from there.
[Samsung Galaxy Nexus] shawnaye:
Hmm, Xylon, FNV, RBJ, Xenon, SlimBean, AOKP.

Perhaps time for me to flash stock and try. I didn't blame the ROM, cause it's kernel dependent isn't it wi-fi?
[Samsung Galaxy Nexus] F_T_B:
I have a ton of Google apps, Facebook, SkyDrive, Dropbox, Twitter, Exchange account and LinkedIn, all syncing in the background. It's normal, it's not an issue. I'm wondering why you take it I need to troubleshoot something, it's like we speak entirely different languages here.
[Samsung Galaxy Nexus] lesp4ul:
I didn't mean to gank his mod, i just don't remember where i got it. Now you mentioned vonVideo (credit to him) and your analysis is right but I still use this, my volume never above 75% to avoid artifacts. Cheers :)
[Samsung Galaxy Nexus] F_T_B:
In your case of Wi-Fi disconnecting while sleeping it can be a ROM issue or app issue, as I never had any problem with Franco's kernel in the past.

My first advice is to look at cellular data consumption and see just how much is actually registered. Please do that first.

Then if there is serious cellular data consumption (more than a few KB) you can install the ROM and not install any apps afterwards. See how it works out for you when you let it sleep.

Tell you what. Try RasbeanJelly because that's what I run. If you encounter any issue afterwards with Wi-Fi disconnecting let me know.
[Samsung Galaxy Nexus] Sveke:
No, you stated that unlocking the boot loader is the culprit for high android op system readings, you wrote it 3 pages ago about halfway down. That is not a correct statement, so we speak the same language.
[Samsung Galaxy Nexus] Angelakaro:
Yes,i know that too many syncing apps reduce battery life and,since i have a lot of apps and accounts working in background (if not,it makes no sense to have a powerful smartphone), i do not pretend an impressive battery life. However,as i stated before,my idle drain is great,1/2% max per hour,so apps do not interfer too much with my battery life and they do not wake up my phone. Maybe the only reason is the unlocked bootloader,cause the issue appears only if my phone is modded.

EDIT: another thing is that if i'm not connected to any network (data or wi-fi) android system do not eat battery life. Using a app,many times ago,i noticed that the apps that eats battery (concerning android system) is Key Chain. Can it be a Google fault?
[Samsung Galaxy Nexus] osm0sis:
I lock and unlock the bootloader with BootUnlocker all the time, so it's not the actual state that matters, it's the wiped data when you do it via fastboot that F_T_B and I were talking about before. More precisely it's likely just Android syncing your settings and apps again from your Google account after a factory reset, and redoing all the system settings, account syncing, etc.
[Samsung Galaxy Nexus] shawnaye:
http://xdaforums.com/showthread.php?t=2027859&page=3

found the thread, dudes with stock facing issues as well. haha.
[Samsung Galaxy Nexus] F_T_B:
I only wrote about the chain of events to explain the process. I'm not an idiot to assume that unlocking the bootloader immediately causes a spike in Android System usage, it's just the butterfly effect. Read through it again.

---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------

You my man get it. Thank you.

---------- Post added at 06:54 PM ---------- Previous post was at 06:51 PM ----------

Then yeah, I can't really explain it. I always try to find the most likely logical outcome, but who knows maybe it's just a bug somewhere affecting a limited number of usage scenarios.

With the factory images, using the bootloader, radio, system, userdata and boot files it never happened to me. Nor did it happen when running CyanogenMod 10.1, AOKP with Android 4.2 base, RasbeanJelly. I also ran Franco's kernel and Trinity and never, ever had I had this issue of Wi-Fi disconnecting.

The only cellular data usage I see is immediately after installing Android, right before connecting Wi-Fi. Android uses a few KB then and that's it.
[Samsung Galaxy Nexus] duduzinho15:
When I get a reboot how can i see THE error in last kmsg?
[Samsung Galaxy Nexus] joaquinf:
Ok i've reinstalled the game just to see for myself because i've never had any issues with shadowgun on franco's kernels. All i can say is that the game runs liquid smooth on my phone, my setup is as described on my signature but it is pretty much the stock configuration but the max freq is bumped to 1.3.

I played for about 30 minutes on different maps (both deadmatch and zone control) and i couldn't reproduce the lags or choppiness you were talking about. Nothing, zero, nada, no lags. The game runs just fine on every scenario. Coud you please provide more info about how to trigger the slowdowns? which rom are you using? does your device gets too hot when playing? playing time? does this happens even on the first game with while the phone is "cool"?.

I hope it helps

EDIT: make sure that under options > Display graphic details are set to low. That's the default value for our phone, anything up is for tegra 3 and/or powerful cup/gpu
[Samsung Galaxy Nexus] osm0sis:
After the reboot copy /proc/last_kmsg to your sdcard or pull it to your computer. Open the file. The last line tells you the basic reason for the reboot and then you generally compare that to what was happening at the end of the log right before it happened.

Nice work! Thanks for that! And ahh It's got its own detail setting built-in? That's easy then.
[Samsung Galaxy Nexus] joaquinf:
Yes! unlike NFS:WM you don't have to do any apk mod to make it work . Graphics can be tweaked from inside the game, the way it should always be.

If the game still lags on low graphic details then is something on his end. Even my old HTC Sensation can run this game smoothly with a less powerful CPU/GPU, less RAM and running ICS. My guess is that the autodetect function has set up the graphics to a higher level and he isn't aware of that.

Let's see

EDIT: this is how the options screen should like inside the game
[Samsung Galaxy Nexus] sergini:
This is not kernel related, sorry for that:

osm0sis I tried to put your init.d script, color settings and It's not working, even with permissions set. My question is, I'm using trickster, should I be using franco to make it work?
[Samsung Galaxy Nexus] enel_:
Wow, I didn't check the thread for few hours and boom there are 826382 new posts:D

To answer the question before, I didn't change anything about WiFi optimization.

F_T_B as far I can see we run the same setup rasbeanjelly + 361, but I got the issue you don't, very strange.

Reading xda I found it's not ROM or kernel related more device related because it happens on every ROM on these devices.

Something strange happened to my minutes ago, I changed the scheduler to ROW and every time, just every time I unlocked my phone, I got WiFi drops. Changed back to deadline, my WiFi drops are really really rare. I really have no idea if this can or is related...
[Samsung Galaxy Nexus] osm0sis:
Nah init.d is built into the franco.Kernel boot sequence itself, independent of any app. Checklist time ;):

1) downloaded the script from my post, not just copy-pasted.

2) when editing the script you need to have left the LF (linefeed) characters intact and only have edited the numbers. all quotes and semicolons should still be where I had them.

3) renamed the script to 900colorsettings

4) script is in /system/etc/init.d/

5a) from Android Terminal: chmod -R 755 /system/etc/init.d

5b) alternately just make sure rwxr-xr-x permissions are set to both the /system/etc/init.d directory and every file inside.

6) BusyBox Smart Installed to /system/xbin/

That's all I've ever done, and I'm on stock ROM which doesn't even have init.d built in; the only reason it works is franco's ramdisk, so you should be able to get it working too. Hope this helped! :good::)
[Samsung Galaxy Nexus] F_T_B:
Actually right now I run Trinity. But I ran R358 or the last one before the 360 series as well as 361 for a while. Admittedly I did not check on 361, but everything was fine before.
[Samsung Galaxy Nexus] J-Hop2o6:
You sure that's Celcuius? If so that's insane! Because 80C = 176F!!! So I doubt you mean 80C. The highest temp I got on my phone was 122F (50C) and that's when I was doing heavy stuff (heavy games, benchmarks, high radio usage) with my phone. So I don't believe your "80C" story.

Try not using WPS? I don't see the point of WPS. I have it on my WiFi router but don't use it because I don't see how its different from the regular method.

That doesn't sound right. Do what osm0sis said and check your wakelocks via BBS app.

That sounds about normal. I get 0-1%/hr. when its sleep/idle.
[Samsung Galaxy Nexus] nodstuff:
80c is quite possible under heavy load, it shouldn't get that high because throttling starts at 70c but it's still possible, I've had my phone shut off at 110c with throttling turned off.

Maybe he has his phone overclocked to maybe 1.5/1.6 GHz, that wouldn't be long getting to 80c.
[Samsung Galaxy Nexus] Klisman:
I just installed a custom kernel for the first time on my GN.

I am using the r361

I noticed that the franco kernel's highest cpu speed is 1229 (default). Is it bellow the stock google speed, right?

And it seems to me that the screen resolution is 720*1184 against 720*1280. Am I right?

Could you explain me why? I searched, but it is really difficult to find out that information in 4000 pages....
[Samsung Galaxy Nexus] osm0sis:
1.2GHz is roughly, if not exactly the same as Google's stock default max CPU freq.

Hmm not sure what you mean about the resolution, are you maybe forgetting that part of the 1280 needs to go to the navbar in most circumstances?
[Samsung Galaxy Nexus] F_T_B:
Franco's kernel only runs at 28MHz higher than stock. Stock is 1.2GHz.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -> 4.2 | r300 -> 4.1

Edit nm thinking bytes

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] calinoii:
Unfortunately it's true:(

I had my phone overclocked to 1.3 only.

No dubt I have serious issues with my chip...
[Samsung Galaxy Nexus] malaroth:
BTW thanks for that eMMC chip checker osm0sis... found out mine is 11/2011 so not in the bad batches.

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] osm0sis:
Nice. Thanks to whoever posted it in here in the first place or I wouldn't have remembered it to repost. ;)

Glad you're all good!
[Samsung Galaxy Nexus] malaroth:
I've been waiting to possibly get my stepbrothers laptop, been a year since I had my computer and I can't get terminal emulator to work very well so having issues pushing 900colorsettings to initi.d:'(

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] peikojose:
I am not getting good battery life with 361... It was better with 358 or 348... I was getting usually 12-14h idle time and 3:30 screen on time..

Today I got this :(

I hope it was me... I don't know how to read well partial and kernel wake locks with BBS.

Best regards
[Samsung Galaxy Nexus] mrm43:
For your information I too have the same battery scenario as his. When I go to sleep I turn off wifi sync and data. I too have a blank space when I sleep. The phone does not wake or nothing and it looses only about 3% battery overnight. Deep sleep is very good. He was just peacefully showing his stats and you flamed him. Let's be good to each other here.
[Samsung Galaxy Nexus] F_T_B:
You're right, there is really no point in arguing over it. To each his own.
[Samsung Galaxy Nexus] malaroth:
I'm a dolt. But I've been so since before 18

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] The Gingerbread Man:
Guys sorry for off topic but I'm in need of advice here http://xdaforums.com/showthread.php?t=2086226 I really think my phone is messed up, details on thread

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Klisman:
Does anyone have problems paying NFS most wanted with r 361?

I was able to run the game using the stock kernel, but with 361 it seems that the game is running at 0,5x speed
[Samsung Galaxy Nexus] whitedragonz83:
Search this thread. It is an issue with the game detecting Franco's ramdisk changes as though the nexus has specs like the S3 or something. There is a fix I believe if you search here.
[Samsung Galaxy Nexus] joaquinf:
Have you tried this?http://xdaforums.com/showthread.php?t=1845993
[Samsung Galaxy Nexus] Klisman:
No, I did not try it yet, but it worked in stock, it should work using the franco kernel as well.

We just need to find where the issues lies.

I also have the NOVA 3 installed and no problem at all using r361
[Samsung Galaxy Nexus] joaquinf:
Due to the crappy coding used on the game, it adjusts the graphics quality according to some parameters present in the kernel like max cpu freq and gpu freq. Using franco kernel the game adjust the graphics to the max level hence the lag, on other kernels woks fine (like stock) but on franco the phone is detected like is a powerful beast :rolleyes:

Try the patch I've linked it works great
[Samsung Galaxy Nexus] neo-X:
...but the phone is a powerful beast with Franco :D
[Samsung Galaxy Nexus] grotesque02:
I'm on 361, but I have better battery with 348, is just me?
[Samsung Galaxy Nexus] Klisman:
Sorry, I didnt have gotten it. Thank you for the explanation!
[Samsung Galaxy Nexus] ChazzMatt:
Franco download server seems to be down? Can't access any of the repository of kernels. Google can't even access cached copy.

______

Wait! back up.
[Samsung Galaxy Nexus] michi_1983:
Doesn't seem to be a server issue, works fine from here.
[Samsung Galaxy Nexus] malaroth:
I don't know what I'm doing differently but I have 0 problems with NFS:MW.

Hope you're having a badass time at CES Franco!

JBSourcery 4.2 + Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] ijama:
Working great r361 plus AOKP rom..yeah keep the magic alive..and as for gaming..i dunn have any probs..nfs.mw run smooth, sg.deadzone perfect,dead trigger and dungeon hunter 3.everythings great..default setting..franco kernel absolutely thumbs up

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] marcusva79:
This has been the best I have had. I haven't charged my phone nor USB synced so I have no idea what that increase is. But damn 8 hrs and at 63% battery. Keep it up Franco
[Samsung Galaxy Nexus] marcusva79:
I have no clue why it wouldn't let me post. But here it is. Sorry for the double post.
[Samsung Galaxy Nexus] J-Hop2o6:
I always have my phone using 1.5GHz (even my last phone, G2/DZ). But seriously, past 60C sounds like a Nuclear Meltdown for a phone, lol. Like I said, even with doing heavy stuff on my phone, I don't pass 50C. Guess i'm just lucky? lol

Wait.... 110C!!!!! Now that is a straight up lie! Pics or GTFO! lol
[Samsung Galaxy Nexus] morfic:
His numbers sound plausible, we've all "been there, done that."

CPU thermal shutdown temps for most cpus is in the 100C+ range.

N4 thermal throttling stock *does not* start until 60C, runs great up to 80C though, just like krait in sgs3.

Going through the past few pages looks like a lot of people have no idea about cpu temperature ranges.
[Samsung Galaxy Nexus] J-Hop2o6:
I know PC CPU can get up pretty high, but they have fans. It just sounds crazy with a fanless tiny SoC/CPU getting past 80C w/o having it totally crapping out. When my phone went up to 122F (50C) it was pretty hot. I can't imagine 70C+ and I don't want to try it lol.
[Samsung Galaxy Nexus] morfic:
You forgot the cpus reach the temp, the fans just mean they have to put more energy into reaching those temps.

70C is 70C if passive or active cooling.

And yes, your SoC cools by spreading the heat over the other materials.

And when i referred to the 100C+ for most cpus, i meant SoCs.

People wouldn't OC if there was no headroom/no safety.

Think about that.

Just trying to keep people from freaking should they see 60C or 70C, not advocating to reach that.
[Samsung Galaxy Nexus] J-Hop2o6:
I OC to 1.5GHz and I never had it go above 50C with heavy usage. 70C+ is strange, but 100C+ in a phone is insane to me, lol.
[Samsung Galaxy Nexus] Fenvarien:
The new ROW scheduler performs quite good IMO. Is this patch "row: Add support for urgent request handling" already included?

https://patchwork.kernel.org/patch/1862311/

GNex with franco.Kernel r361 / CM10.1
[Samsung Galaxy Nexus] osm0sis:
Look at the thermal throttle toggle in f.Ku. You'll see the hardware safety cutoff is at 110 degrees C for the GN, and that thermal throttling usually begins around 70 degrees. I've never seen my device past 65 after a charge and with heavy usage but that doesn't mean it's not in the range of normal to have it meet the throttling point. Anything much higher than that shouldn't really occur unless the throttle is disabled though.

I hope you saw the guy who was upset about 33 degrees C. So ridiculous. ;)
[Samsung Galaxy Nexus] neo-X:
Flashed r361. Been running for two days now and no SOD's. Was getting SOD's previously but I think that was because of 192 min.

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] g virus:
I'm in the same boat. Flashed r361 over 348, always with stock kernel settings. When screen off battery consumption it's about the same, but when I'm using the phone it wastes more battery then r348. This extra fluidity comes with a price of little more juice :)

Franco, I ask you if in the future releases you could enable SmartReflex, and ignore/don't support the problems of undervolting noobs, to see if battery life goes to r348 standards.

Keep up the good work, and enjoy CES!
[Samsung Galaxy Nexus] :
This R361 is a very annoying problem that happened before with other versions of the kernel of the franc. Before if you changed the color green, the green screen and all would be to restart the device. In this latest version, if you change the color blue, the screen just stays with multiple color bands, and back home screen. :mad:
[Samsung Galaxy Nexus] osm0sis:
The -1 green rgb gamma thing has been there since Ezekeel wrote it. Seeing as Ezekeel himself hasn't fixed it, I think we can assume it's just a limitation of the interface. To correct it you don't need to reboot though, just move the green gamma back to 0. Anyway, I can't reproduce this blue issue you're talking about, not with rgb gamma or multiplier. Perhaps you could describe it a bit better? Or better yet, take a picture?

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

On another topic, I'm at 23h 15m, 3h screen on and 25% left on battery. And if I can do that on Stock ROM, autobrightness, wifi and sync enabled, there's nothing wrong with battery life in r361. Quite the opposite. Looks like it'll be one of the best cycles I've ever had. If I stayed screen on until it dies I'm on track to reach 4h, which I've only done at 1d+ maybe once or twice before. 1750mAh battery of course.
[Samsung Galaxy Nexus] shawnaye:
You're still on deadline right my friend?

I'm completely loving ROW now just cause it makes chrome fly for me. :victory:
[Samsung Galaxy Nexus] 1Speed:
New kernel is awesome, thanks franco!

Battery life for me is around 15% better than the previous kernel. Will post stats when I get a chance.
[Samsung Galaxy Nexus] GManLynx:
I'm sorry if this is a stupid question, but I can't find the colorcontrol on your app, I'm running nightly 13 and updated to the last est version for your app. I've used before...

Edit:

I mean to control the navigation buttons

Jk found it. Its in settings
[Samsung Galaxy Nexus] jan-willem3:
ro_explorer you dont got any problems with init.d scripts? Since I am also using this kernel and bigxie's build. And I got problems with it, they dont get executed.
[Samsung Galaxy Nexus] apratomo:
Yes, sir I'm aware of that, the name implies. But the problem is I was connected then unplugged then restarted my phone. Should it still there? If yes then, moving on :-)
[Samsung Galaxy Nexus] franciscofranco:
Dunno. I don't know if those stats get saved and persist through reboots.

Anyway I reverted a bunch of omap patches before I went to sleep yesterday, enabled wifi and I only dropped 1% in 7 hours, so I guess that "extra" battery consumption should be now fixed.
[Samsung Galaxy Nexus] ro_explorer:
I had issues with #12 ... I don't know yet with #13 .. I did not rebooted the gadget yet. I'll check his and report back ... give me few minutes :)
[Samsung Galaxy Nexus] kimboinatl:
Running 13 right now. So far so good. I can't comment on battery life yet since it's only been a day.
[Samsung Galaxy Nexus] jan-willem3:
I didnt really had issues with battery life lost 1% in three hour with mobile data on. One hour driving around and turned the screen on and off for lets say 30 sec.

However this wasnt enabled:

ARM CPU Topology enabled again - you'll notice an init.d script called schedmc that enables the power saving technique offered by that interface. For more information Google it up, I did the same

Because I dont have working init.d at the moment.
[Samsung Galaxy Nexus] Thracks:
Hey, Franco, I understand your app was supposed to be available on androidpit? I'd really like to purchase. Has that happened yet? :)
[Samsung Galaxy Nexus] franciscofranco:
Well I don't understand the init.d issue. I installed AOKP 19 last night just to be sure and I have my init.d working.

I contacted them yesterday night and got an answer today that they are looking into it. Just gotta wait.
[Samsung Galaxy Nexus] festermania:
Ho in using this great kernel but i font understend why in used up i fine everytime google maps.

I kill this up but automaticaly it re start agains..

Its norma o i ha ve ab issue?
[Samsung Galaxy Nexus] sishgupta:
Phone just rebooted.

Is there a way to get logcats to persist past reboots?
[Samsung Galaxy Nexus] Vangelis13:
Use titanium backup to freeze it.

---------- Post added at 06:23 PM ---------- Previous post was at 06:18 PM ----------

Get the file from /proc/last_kmsg (faux had advised in his thread, I take no credit)

Though, I couldn't find it on my phone just now when I looked.. :confused: EDIT: I guess if I didn't have a reboot there won't be a last_kmsg..? dooooh
[Samsung Galaxy Nexus] festermania:
I hope thats its possible find a solution less aggressive
[Samsung Galaxy Nexus] sishgupta:
Doesn't that only work if I am the one doing the rebooting? I don't think TB freeze is gonna help if the phone randomly reboots.
[Samsung Galaxy Nexus] bradm23:
Please excuse my noob question however I am a little confused what an init.d script is. Is this something our phones use that we don't have to activate, or do we have to do something in order to activate it?
[Samsung Galaxy Nexus] trismegistos:
If the kernel supports init.d the scripts in the init.d folder are executed on startup automatically.
[Samsung Galaxy Nexus] Vangelis13:
Huh? The freezing comment was for the other lad with the maps issue..
[Samsung Galaxy Nexus] Vangelis13:
Freezing (not deleting / uninstalling) is not aggressive at all.
[Samsung Galaxy Nexus] toonlight:
I think the wifi changes need testing. I just upgraded from nightly #12 and my wifi signal seems significantly worse (0-1 bars instead of 2-3 bars). I'll need to use it more to be sure, though.
[Samsung Galaxy Nexus] osm0sis:
Yes sir. ROW felt too choppy in games and Currents for me, and in general use I find deadline virtually the same or a hair smoother. So 1305 max + deadline right now and my whole phone is flying. Westwood and all else defaults. We'll see what happens with M7 but these might be my new daily driver settings. :)