yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] garuhhh:
I tried going back to stock kernel, to see whether it's really a kernel issue or ROM issue. But since I'm the only one reporting this, it seems its more likely ROM issue. But for the limited time I was using all stock, didn't really seem to notice this happening.

I'm using stock ROM, but flashed it without wiping.
[Samsung Galaxy Nexus] franciscofranco:
Without logs theres nothing I can do to help you.
[Samsung Galaxy Nexus] xolanir:
Have you tried to clean flash the ROM and kernel and see if that fixes the issue? Also if you can, download catlog from the play store and try to get a log so that Franco can see what's happening ion the background.

Edit: btw my deep sleep issues have resolved. Thx for all the help I was given and the support! I'm digging the kernel Franco and hope to see more awesome stuff come to it once the 4.2 settles and all the bugs get ironed out by Google. :cool:
[Samsung Galaxy Nexus] franciscofranco:
Just pushed a maintenance release of the test kernel:

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/boot-r315.img
[Samsung Galaxy Nexus] Hungry Man:
Maintenance release?
[Samsung Galaxy Nexus] exmatproton:
Thanks! Was impressed by the stability of 313. Also the battery life was nice!!!
[Samsung Galaxy Nexus] franciscofranco:
Yes mostly fixes and some changes I left behind in r313.
[Samsung Galaxy Nexus] Hungry Man:
I see, thanks.
[Samsung Galaxy Nexus] frost866:
Does this one work on 4.1.2?
[Samsung Galaxy Nexus] Khizar:
gonna test this... been using r313 and its great

---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------

its for 4.2
[Samsung Galaxy Nexus] franciscofranco:
No...
[Samsung Galaxy Nexus] sleepsus:
I noticed a lot of people are experiencing random soft reboots, it's a community known bug, don't know if Google has acknowledged it yet.

Here's a nice article with a list of bugs found in the wild:

http://www.androidpolice.com/2012/1...major-issues-plaguing-googles-newest-release/
[Samsung Galaxy Nexus] garuhhh:
thanks xolanir for the Catlog tip, I'll do my logs, and try r315.
[Samsung Galaxy Nexus] rmcsc:
You see, the thing is that Franco doesn't like or want flashable zips in this thread. Making a bad flashable zip can screw a phone up badly, something that's simply not associated with Francisco's work. :)

You do remember Francisco asked us this about 1800 pages ago, right? :p

What? Missing, too many, too few, too loud...? Need more info to be able to help.

Yes. It's been discussed in the past, I don't know, 100 pages or so?

4.2, buddy. The only magic number that matters at the moment.

That's the Red Bull talking. :p

Thing is that you and everyone else who hasn't and doesn't care about reading ask the same thing over and over. After the fifth person you get tired.

Buddy, this attitude is earning you nothing, so settle down.

If you insist.

In the meantime, you could go around the internet reading about how to do everything you have questions about. It's always helpful learning some more.

Weird, this. I've not had one reboot, so I guess I can't vouch for his experience but... just weird.

This. A million times this.

It's not yet an officially available kernel, buddy. It's still under heavy testing. You'll see it's available when the thread name changes. ;)

You trickster, you. Reminds me of... r200, was it? The first changelog-less one.

Nope! Only testing for 4.2 at the moment. Sorry!
[Samsung Galaxy Nexus] Khizar:
its pretty simple.. but if you dont know how or are too lazy you could use the toolkit to flash it...
[Samsung Galaxy Nexus] franciscofranco:
Well if I don't post .zips there is a reason. I really don't care if people don't know what a boot.img is or how to flash it, the ones that know how to use it will provide me the best and most truthful feedback...but you know that already ;)

Well now everyone can use 512MHz GPU after I stopped it from calibrating it further down theres no point in having 2 different builds.
[Samsung Galaxy Nexus] IgnorantNerd:
Hey guys has anybody had this problem before? It happened when I tried to update Franco's app.
[Samsung Galaxy Nexus] The Gingerbread Man:
Sneaky hahaha at least that makes less work on your end! Is there anything in particular you need testing in 315?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] --__LoRiS__--:
Franco if you want and tell me what to do, I'd be happy to translate your application into Italian, thanks for your work!
[Samsung Galaxy Nexus] franciscofranco:
No, just use it normally.
[Samsung Galaxy Nexus] The Gingerbread Man:
So far as I can tell all is well except those couple of things which I've mentioned over last few days like TCP algorithm, io scheduler and blx settings not sticking or making any effect changing their values. I did a like more trouble shooting to eliminate busybox by trying v 1.19.4, 1.20.0, 1.20.1 & 1.20.2. The only other thing that seems a little of is in the core voltage being labelled core 0 - 2 but I expect that was intentional for the 512gpu test on 313 :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
do you get lag when answering a call?
[Samsung Galaxy Nexus] Phoenix Wright:
r315 turns off the adb usb connection when the phone goes to sleep... seems to be a kernel problem, I tried to use the stock ramdisk and the problem is still there... reverting to 313 (I'm an heavy adb user XD)
[Samsung Galaxy Nexus] franciscofranco:
That a bug in the app, just finishing more bug fixing to push it, don't bother with the busyboxes lol.

The Core labeling will stay like that.
[Samsung Galaxy Nexus] Khizar:
adb works fine for me..even when phone goes to sleep
[Samsung Galaxy Nexus] franciscofranco:
Yep, sorry bout that, you can re-download r315 :)
[Samsung Galaxy Nexus] marshy73:
Happened to me while i was on 313. I flashed back 4.2 with default kernel, wiped caches and fix permissions. Solved. Not sure if it's specifically related to 313 or not.
[Samsung Galaxy Nexus] Khizar:
hmm.. so that is confirmed bug? how come adb works for me when the phone goes to sleep?
[Samsung Galaxy Nexus] The Gingerbread Man:
Nope I litterally just had a call and didn't seem to see any lag at all. Do you mean lag as in the answering animation or transition to the call?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
both..the animation is really choopy and it takes around 3-4 secs for the call to come through
[Samsung Galaxy Nexus] The Gingerbread Man:
Hmm I dunno, like I say was fine for me just now. I dought it has anything to do with caches but perhaps just a simple reboot might help to clear out any **** in the memory or ram. I would suggest at least 1 reboot per 48 hours personally

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Ok 8.0.5 pushed, time to sleep:

8.0.5

* Improvements to Power Modes handling system which should fix reported FC's when trying to use a PM after it was created

* Fix Kernel Settings bug where no option would be set

* Improve Color Control code

* Improve Frequencies activity handling system

* Improve Kernel Backup/Restore activity handling system which also fixes a bug after creating the image

* Some polishes here and there

Thanks for all the reports! Sorry for the spam of updates but this is my only free time after work.
[Samsung Galaxy Nexus] Khizar:
yeah i reboot at-least once a day

Edit- i dont have the lag any more..weird but its gone now
[Samsung Galaxy Nexus] Raijin:
Sorry? Why, for all the hard work you do for us, and in your little free time? Do not say it again. :)
[Samsung Galaxy Nexus] The Gingerbread Man:
App update fixed kernel custom settings bugs, select power mode caused force close, bug report sent through Google play

Sent from my Galaxy Nexus

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

This +1. Its nice to see Franco is indeed an actual person with feelings etc not a build bot sent from 2120 to save us with his kerneIs and like the off topic bits to add some conversation and its not all so serious all the time :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rmcsc:
He's a guy sent to us from [date withheld, although I know it] to save us with his kernels.
[Samsung Galaxy Nexus] gianton:
It happened to me too, I unistalled the app and reinstalled it from Play store.
[Samsung Galaxy Nexus] arq7203:
When that happened to me, I had to revert to stock kernel and then reinstall the app.
[Samsung Galaxy Nexus] yellowdie:
I get the FCs when opening Power Modes as well. But I don't know about your second post. I still think Franco's "I need to sleep." posts are just BS to throw us off and make us think he's actually a human. :eek:
[Samsung Galaxy Nexus] bboran:
how can i flash the r315? is there a possibility to flash it without using adb push?
[Samsung Galaxy Nexus] osm0sis:
Man... If I get a N4, gonna need a case from day one.

http://www.neowin.net/news/google-nexus-4-drop-test-fun-or-frightening

I remember in one of the first reviews they managed to crack the back just having it fall off his kitchen table by mistake. Not sure why they made the back glass.. The new iPhone moved away from glass backs again for this very reason.

---------- Post added at 10:00 AM ---------- Previous post was at 09:56 AM ----------

You'd use fastboot flash not adb push. Anyway you don't need to either way. Just download it to your sdcard and move it to the kernel_backups/ directory then go into f.KU's Kernel backup/restore page and you'll see it there. Tap it and 'restore' to flash.
[Samsung Galaxy Nexus] Khizar:
no there is only the img file available which you have to flash via fastboot
[Samsung Galaxy Nexus] bboran:
How can i do this? Can you give me instructions ?
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Yeah. I got a Seidio Surface on the same day I ordered the GNex. If I could afford 2 phones, then I'd forgo the case...but I can't.

RF
[Samsung Galaxy Nexus] osm0sis:
No, you'd have to flash it with fastboot if franco wasn't ****ing awesome and didn't give us an interface in the app to do it with. But he is ****ing awesome so check my last post. ;)

---------- Post added at 10:25 AM ---------- Previous post was at 10:25 AM ----------

GN is a little sturdier than glass though. :p Mine took a few drops before I got a case, just scuffed the edges of the chassis.

I wonder if the tempered glass SP guys will make ones for both sides. :laugh:
[Samsung Galaxy Nexus] eng.stk:
You merged zram, me likes :cool:
[Samsung Galaxy Nexus] osm0sis:
Holy ****! NO! DO NOT **** around with the zips any more. the sdcard binary in them will break your 4.2 system, and I'll refuse to troubleshoot your dumb asses. Can you guys read this? Am I a goddamn ghost over here?
[Samsung Galaxy Nexus] Khizar:
lol i never knew.. btw does this also save your kernel settings when you back up and then restore after flashing a different rom?
[Samsung Galaxy Nexus] chickentuna:
anyone here who have problems with USB fastcharge on the latest r315? It seems that whenever you disable/enable it, you need to reboot in order for the changes to apply
[Samsung Galaxy Nexus] Khizar:
the way osm0sis posted is pretty simple.. i think that way is better for new users
[Samsung Galaxy Nexus] copi:
oops.. really? i've already done that. hahaha. and is running along with bixie. ok sorry, i'll look on ur post then
[Samsung Galaxy Nexus] osm0sis:
Nah it just takes a backup image of your currently running kernel. Settings backup/restore is on the slate for a future f.KU version.

Yup pages of discussion about that when we first started trying f.K on 4.2, and a few pages back a guy posted a zip with the 4.2 test kernel and sdcard binary still in it and messed up a few people so we had to have a mod come scrub the thread. :)
[Samsung Galaxy Nexus] ambuj:
Thanks Osmosis
[Samsung Galaxy Nexus] Phoenix Wright:
The problem is still there... I tried to redownload the img even with a different browser, but no dice... sorry for annoying you :)

---------- Post added at 04:51 PM ---------- Previous post was at 04:34 PM ----------

I accidentally deleted my backup of r313 and it's no longer on the server... if anyone has it I'll be grateful to them
[Samsung Galaxy Nexus] 11768:
How can I remove Android/Linux internal lowmemorykiller? I want to try use a third party app to manage my RAM as I want to keep certain app like (Phone, Messaging, etc) alive at all time.

Any idea guys?
[Samsung Galaxy Nexus] joaquinf:
Here

---------- Post added at 11:23 AM ---------- Previous post was at 11:10 AM ----------

I just downloaded a new copy of r315 and adb is indeed getting killed when phone goes to sleep, not necessary screen off but deep sleep.

When in deep sleep state adb devices doesn't show the phone being attached
[Samsung Galaxy Nexus] elnovio:
Here you go:

http://db.tt/jKvdOuLm

Edit: hm. Simultanous...
[Samsung Galaxy Nexus] osm0sis:
That's weird.. If I recall correctly from before, the phone wouldn't deep sleep when plugged in? Maybe that's the problem now. It's not supposed to.
[Samsung Galaxy Nexus] joaquinf:
It could be. Are you facing the same issue?

EDIT: not only it kills adb but media storage is killed as well :(
[Samsung Galaxy Nexus] franciscofranco:
I didn't, it was a left over from something I was doing at work...
[Samsung Galaxy Nexus] osm0sis:
I don't tend to go the USB Debugging route, if I'm using adb it's usually through CWM; so I don't know! What are you doing that you're leaving your phone plugged in with adb?
[Samsung Galaxy Nexus] joaquinf:
I was checking the logcat while booting, i was trying to figure out some strange reboots i'm experimenting if i check "disable content adaptive brigntess on fku. However, this deep sleep issue is also happening for the media storage. If i left the phone untouched while plugged in it will unmount as a media device for no reason
[Samsung Galaxy Nexus] franciscofranco:
Maybe I forgot to remove something from work - by the time I realized I was working in the same branch that this kernel I already did some changes and I might've borked something. I'll check it out later today. BTW adb is not being killed on my device.
[Samsung Galaxy Nexus] The Gingerbread Man:
A work around for now but is in developer options enable 'keep awake while charging' this keeps the screen on whilst you charge unless you manually do it. Very helpful for reading in bed :)

You are correct, deep sleep can't happen during charging

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] llevo3:
Flawless on AOSP 4.2 KALO v5.1 :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Kurre:
Any experiece about zen i/o, anyone? Or has Franco made any experiences with it? Dunno if that one is already well-known friend/foe, but anyway :) By search I didn't find anything useful in this thread, but most probably someone can enlighten me :p

Somewhere I read that it's comparable to the FIOPS scheduler in terms of performance (dunno if read or write).

Well, I think that Franco has his hands full with 4.2 issues, so these io schedulers etc things are quite background stuff atm and I can't complain :D

This was discussed some time ago..and I even posted screenshot after a night with charger plugged in (I think it was this thread). And deep sleep time was 7-8hours, so I'd say that it shouldn't prevent deep sleeping :)

edit: Link to my earlier post
[Samsung Galaxy Nexus] joaquinf:
Just reverted back to r313 for testing sake and adb/media storage was working flawless again. In r315 it just happens when the screen is off, around 15 or 20 secs after it goes off. Best way to try it is to do adb logcat and then turn off your screen and you'll see the logcat is stopped after some time. Is like if the service is restarted, very weird.

EDIT: after leaving the device with the screen off for about 3 minutes after adb got killed it came back by itself

EDIT: aaaaaaand down again

Here is the last part:

EDIT3: Here is another full log in case you want to take a look
[Samsung Galaxy Nexus] llevo3:
if USB debugging is ON, while charging as soon as the phone goes into deep sleep, keeps connecting and disconnecting from PC #r315
[Samsung Galaxy Nexus] thedirtchamber:
Hi guys. I'm posting this in case someone else has a similar issue as I did. I also posted on the AOKP rom thread, I thought it was a rom issue, but it turns out it's a kernel issue. Here's the post:

"Guys, does anyone have problems with Bluetooth in this ROM? I'm not really sure it's a ROM issue, but maybe someone has a clue about it: I'm using the Nexus with my car's bluetooth, everything is fine, except now I can only access the phone directory. Before (I am not sure when this problem started, so I can't associate it with something I installed/flashed on my phone) I was able to access the Call list too (there are 2 options when I press the car's BT button, Telephone directory and Call list). I tried pairing again, the phone asks if I give permission to the car to access my call list and contacts, I hit OK, but it won't work, I only have the directory option... And it's really annoying to browse all the contacts instead of accessing the recent/missed calls or dialed numbers...

If it helps, I'm using franco's kernel, latest nightly. Thanks."

I flashed Milestone 1 and everything was back to normal, so there's something about the nightly version (300). I hope this helps someone. :)
[Samsung Galaxy Nexus] gianton:
I noticed that too.
[Samsung Galaxy Nexus] franciscofranco:
I know.
[Samsung Galaxy Nexus] timbck2:
F. Ku app 8.0.5 has fixed the problem I was having where the TCP congestion avoidance setting wouldn't set to anything except cubic; I can now set westwood again.
[Samsung Galaxy Nexus] IgnorantNerd:
Flashed back to stock and it worked. Thanks!
[Samsung Galaxy Nexus] bat0nas:
Is franco kernel supported in stock and rooted (supersu) android 4.2 (installed from takju images)?

Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gianton:
Yes you need to flash r315 version, search Franco's post to download it.
[Samsung Galaxy Nexus] Cobra78:
After a test with another kernel i can confirm: with r313 (didn't tested r315 yet) proximity sensors aren't working right, on call the screen goes off but immediatly it turn back on; obviously with another kernel this thing dosen't happen.

Sorry for my bad english!
[Samsung Galaxy Nexus] nikulogical:
Haven't tried the new one but r313 has been pretty stable and good with battery with the PA 4.2 alpha. Great stuff.

Sent from my PARANOID ANDROID
[Samsung Galaxy Nexus] Fenvarien:
+1

Scheduler and TCP settings are working again, thanks for your fast update Franco! :)

GNex with franco.Kernel / MiNCO ROM
[Samsung Galaxy Nexus] bigfnjoe96:
Anyone getting force closes when they try to access the frequencies tap with Franco App via r313/315.?
[Samsung Galaxy Nexus] yellowdie:
Some FCs are fixed in 8.0.6. Should be out soon. :)
[Samsung Galaxy Nexus] bigfnjoe96:
BTW thanks for all your testing & help in this thread. It's been very helpful for a novice like me
[Samsung Galaxy Nexus] grognaz:
found an other problem with the app, when i save color profiles then the blue value get the same value as the red one was set to.
[Samsung Galaxy Nexus] dehein:
No I meant it had flaws. I wanted to report that and than I saw that a new update with good translation was already there. I anyways. I have to read some pages...
[Samsung Galaxy Nexus] RevengeFNF:
Hey Franco, what about Portuguese Language in your app? :p
[Samsung Galaxy Nexus] dyepnoodle:
can someone please share the r315 cant find it. is there a flashable zip for this?

edit.

nevermind found the .img file. :)
[Samsung Galaxy Nexus] zephiK:
no flashable zip. flash it via fastboot or kernel restore it within franco app
[Samsung Galaxy Nexus] joeb3786:
out of curiousity, what are others able to UV the 384mhz step to? On r313, SR was calibrating 384mhz to 920mv, while 537mhz was hardcoded to 900mv. I UV'ed 384mhz to 850 and 875 but got reboots on both, so I decided to run with 537 min. Still using this on r315 as SR had both steps at 900mv. Loving the battery life and performance with this setup though. Used to have 192 step at 775 on pre-4.2 kernels with great luck but it was just too slow for my liking.
[Samsung Galaxy Nexus] The Gingerbread Man:
If you didn't know 8.0.6 is up now. All is good and working as it should and harmony returns to the world :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Whoa, if anyone here doesn't already have franco.Kernel updater app, now is your chance!

Reduced price for Black Friday for the next 7 days!!

Or at least "the next 7 days" from whenever Franco started that promotion. :p

---------- Post added at 08:09 PM ---------- Previous post was at 08:04 PM ----------

Interesting. Your silicon is not as strong as some it would seem. :(

I've got 192MHz@725mV and 384@775mV... I agree about 192MHz being too sluggish, made scrolling in stock browser feel jittery, I'm running 384MHz min now quite happily. I run 1536 max but my device seems to handle all the way up to 1.8GHz quite well.

Just finished completely UVing this morning actually. Now that franco took away 1228MHz I only had 3 left that I was letting SR calibrate, so I figured why not. Here's what I ended up with as stable, going down by 25mV steps, for my voltage profile (type "cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table" in Terminal Emulator):

1804mhz: 1425 mV

1728mhz: 1375 mV

1612mhz: 1325 mV

1536mhz: 1275 mV

1420mhz: 1225 mV

1305mhz: 1175 mV

1036mhz: 1050 mV

729mhz: 925 mV

537mhz: 825 mV

384mhz: 775 mV

192mhz: 725 mV
[Samsung Galaxy Nexus] Hungry Man:
My voltages:

192: 710

384: 775

537: 790

728: 905

1036: 1075

1305: 1150

1420: 1190

1536: 1330

1612: 1340

Anyone undervolted their 155mhz core slot? I can go ridiculously low.
[Samsung Galaxy Nexus] F_T_B:
Sorry if I ask a silly question, but how is 315 compared to 313? I want to install one, and can't make up my mind on which.

Only one way to find out... 315 it is.
[Samsung Galaxy Nexus] joeb3786:
dang... my phone sucks! one more thing wrong with the vzn nexus ;). I even got a reboot on my first boot on 315 before I set 537 as min. maybe I have some testing to do.
[Samsung Galaxy Nexus] osm0sis:
If I recall correctly you shouldn't undervolt Core too much.. since, though it might seem to be working well, weird things start happening like signal drops, Wi-Fi drops and 512GPU artifacts. That's why franco stopped letting SR handle Core.
[Samsung Galaxy Nexus] nuwan32:
It really varies and my phone is a beast, here's my values

384 = 700 mV

537 = 725 mV

729 = 750 mV

1036 = 850 mV

And these are perfectly stable for me, whereas for my friend's nexus you would have to add 200 mV for each step to be stable.
[Samsung Galaxy Nexus] rmcsc:
Yes.
[Samsung Galaxy Nexus] franciscofranco:
Thats something I'm trying to get courage for ;) Soon I promise.
[Samsung Galaxy Nexus] osm0sis:
Haha holy smokes! Your phone IS a beast. Do I remember you had 192 down at like 625mV too? Just insanity. :):highfive:
[Samsung Galaxy Nexus] Hungry Man:
Haven't had any issues personally. I have 512mhz down to 1050, the step below at 950, and below that it seems I can just keep lowering without issue, not sure if it's a bug or what but until I get down to 90mv it works.
[Samsung Galaxy Nexus] osm0sis:
Cool. I'll have to see if I can find the guts to try UVing core one of these days. Probably helps with heat a lot. Getting 155MHz step down to 90mV does sound a little crazy though.
[Samsung Galaxy Nexus] nuwan32:
675 actually :p but I found the 25 mV wasn't worth the loss in performance so I use 384 as min
[Samsung Galaxy Nexus] Leegalaxy:
-Off topic-

I've ordered an N4 and have avoided watching the drop test videos because I was scared to watch. I'm actually relieved to see that it still worked after. Is expecting it to turn into powdered glass flakes and disappear completely:rolleyes:
[Samsung Galaxy Nexus] gummie:
w/c was the latest Milestone6 or r300 for JB 4.1.2?

EDIT: nvm I found it. It was r300 was latest.
[Samsung Galaxy Nexus] gianton:
Do you leave SR on?