yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Knolly:
General question for everyone. I'm currently running Kang maguro milestone 3, and have ran only Kang milestones with Franco's kernel for the last month or so. At least 2 or 3 times a day something will crash and a window will pop up to let me email a bug report of the crash, although it doesn't fill in a recipient. I've looked at the crash jargon but am not that knowledgeable about Android, so I'm wondering, is it likely that this is the kernel or the firmware? Or is there a way I can check specifically from the crash data?

Many many thanks to Franco for all of his hard work either way!
[Samsung Galaxy Nexus] nicandris:
it can be several things. next time it crashes note the app that crashes and post it. or a screenshot etc. also you can upload your crash report in pastebin so we can take a look. 99% it's not kernel related. usually it's some app or wrong gapps files
[Samsung Galaxy Nexus] pmicho:
Running same rom and Franco 16.1... no such problem. Maybe a rogue app on your phone.
[Samsung Galaxy Nexus] marc.tulley:
Thats why there is the 'Disable bugmailer' option in AOKP :)

although 2-3 times a day is a lot. I'd reflash and gradually reinstall everything to try and highlight the culprit although a reflash may likely solve it. I used to have this but only 3-4 times EVER and with old flashes. Nothing in weeks now.
[Samsung Galaxy Nexus] Francois88:
Franco, what's your thoughts on the xda article about undervolting/deep idle/etc. that basically says most of these features do not help the battery ? I wonder if this applies to your kernel and the GNexus or if the article's conclusions are limited to the Nexus S

http://www.xda-developers.com/andro...ry-study-brings-about-surprising-conclusions/
[Samsung Galaxy Nexus] ceo.mtcl:
For some reason I'm unable to go past beyond the 5500 mark in Antutu. Not that I care too much about these benchmarks, but I was able to go up to 7000 with Francos13.1

Screen shot from 16.1

Screen shot from 13.1:

Any ideas?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nikulogical:
Having the same issue as you. I'm thinking its the nova launcher causing this problem.
[Samsung Galaxy Nexus] johno168:
Disable bug mailer in general ui
[Samsung Galaxy Nexus] loudaccord:
look at your ram on each of the screen shots. Either reboot then run the test again or use a task killer then run bench.
[Samsung Galaxy Nexus] ceo.mtcl:
I did use task killer to kill all the applications.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] loudaccord:
your ram is almost 1/2 of what your first bench was. Reboot then run it again.

I'm on 16.1, I'll run the test now.

my ram was similar to the ram you had on #13. I did a reboot then ran the benchmark. Also, make sure your phone is cool, if it's warm, it may throttle the CPU.
[Samsung Galaxy Nexus] MarcLandis:
The RAM in antutu is not related to free memory. It is the IO speed.

Marc
[Samsung Galaxy Nexus] loudaccord:
I'm curious why it goes up so much (or down) when you kill all apps just before running the bench?

Not being sarcastic, just wondering if there is a way to optimize it so that doesn't effect it as much.
[Samsung Galaxy Nexus] franciscofranco:
Thanks everyone for the feedback through the day. I've been really busy today so later at night I'm going to have some free time to look at some of the bugs that have been reported.
[Samsung Galaxy Nexus] danielvc:
Haven't had a single issue with wifi today on 16.1, but I'll need some more time if the 'problem' is really gone.
[Samsung Galaxy Nexus] homer2320776:
I just purchased the franco.Kernel Updater app and I cannot get my settings to stick either.

The Kernel settings, either Hotplug Mod or Dynamic Hotplug will stay between reboots but anything in the OC/UV reverts back to 700/1000 and francoGazelle no matter what I choose.

I have Set at Boot checked and have tried everything that I know to do.

I'm running 4.0.4, this may be the issue, with stock ROM and recovery.

Currently running Franco Kernel 16.1

Thanks.
[Samsung Galaxy Nexus] poopooface:
Thank you very much Francisco, I really appreciate the work you put in on this! I flashed back to 15.2 and then back to 15-test4 and all seems to be working now, but it's awesome how tireless you are in coming up with badass new versions :)

If there is any sort of log I can provide re. the issue of CPUs bumping up to 1GHz every few seconds, let me know and I could probably flash again and send.
[Samsung Galaxy Nexus] tempera:
Where do we enter the commands for hotplug etc..? Command prompt on the phone or adb?
[Samsung Galaxy Nexus] MarcLandis:
Both is possible

Marc
[Samsung Galaxy Nexus] tempera:
I get an error saying "permission denied" using command prompt?
[Samsung Galaxy Nexus] MarcLandis:
Make sure you mount /system as read/write

Marc
[Samsung Galaxy Nexus] franciscofranco:
Nah its ok. If the issue didn't happen on test4 then I know exactly what I'm gonna do for #16.2 to replicate that ;)
[Samsung Galaxy Nexus] Nebucatnetzer:
Ah I nearly forgot it.

I finished my test with #16 and 350 to 1200 Mhz.

I know you said you wouldn't support it and so on but I hadn't had

a single SoD with #16 thought you should know it.

However I had the idea that it might be because the 2nd core was frequently ramped up again so I'll test again if you've fixed this one.
[Samsung Galaxy Nexus] poopooface:
Okay, thanks! I am waiting with baited breath for 16.2 and I'll get back to you with any observations I can pull out of my phone, which I think is probably smarter than my brain.
[Samsung Galaxy Nexus] tempera:
How can i do that? Cant see no option. Im using terminal emulator.
[Samsung Galaxy Nexus] stesmi:
mount -o remount,rw /system

<do whatever you want to do>

mount -o remount,ro /system

Another way, although I haven't tried it myself, but it should work I guess is :

Install ES File Explorer. Go into settings, enable ROOT and click "mount system rw". Then open the terminal and do whatever you want to, then back into ES File Explorer and remove the checkbox.

// Stefan
[Samsung Galaxy Nexus] yyz71:
I just installed this new rom Ir11 Beta 1 IMM30B / 4.0.4: MoDaCo Custom ROM for Galaxy Nexus,and running this kernel 16.1 and so far so good ;) very smooth thank for your hard work and time :D
[Samsung Galaxy Nexus] atsavlis:
Also just installed 4.0.4. First visible "fixes" from good ol Google is the Android OS keeping the system awake... Phone has only been running with rom for about 2 hours, but as you can see, Android OS has dropped from about 23% in 4.0.3 to 10% in 4.0.4....

Hopefully this can add that little extra to our kick ass kernel!
[Samsung Galaxy Nexus] funnyclub:
Will this Kernel work with Android Revolution HD 2.1.5 ROM?
[Samsung Galaxy Nexus] loudaccord:
no

10char
[Samsung Galaxy Nexus] funnyclub:
Ah ok tnx :(
[Samsung Galaxy Nexus] 2dorr:
I just got a reboot, when I wanted to bring down the notification bar, it was blocked half down, everything freeze and then reboot. I am on Dynamic Hotplug with 700 MHz Min cpu and francoTurtle governor. Kernel 16.1. I had that once with an older version of the kernel.
[Samsung Galaxy Nexus] jhericurls:
With all due respect to Mike, there are better ROMs available, than REV.

The OS bug doesn't affect battery life, it just showed the wrong % for Android OS.
[Samsung Galaxy Nexus] hasnol143:
I also got a reboot (twice), I was downloading a torrent, i left my phone plugged in while it downloads, I'm running dynamic hot plug, 700-1000, turtle. I turned off dynamic hotplug and still no luck, everytime my screen is about to shut off, my reboots instead.
[Samsung Galaxy Nexus] nikulogical:
So what's the general consensus, the regular hot plug is working perfectly and makes the device more efficient but the dynamic hot plug is still buggy and experimental?
[Samsung Galaxy Nexus] franciscofranco:
I need more information about that, dmesg log and logcat. Without that I cant do ****.
[Samsung Galaxy Nexus] opensourcefan:
Is there any chance that a kernel, not particularly this one could effect the proximity sensor. Mine is on the fritz. It has improved very slightly with flashing AOKP 22 and 16.1 but have no idea why. It was poor on M3 with 15.2, 14.2 and 13.1. Any ideas...

EDIT: NM, upgraded my Bootloader and it fixed it.
[Samsung Galaxy Nexus] franciscofranco:
They serve different purposes and have different implementations. But dynamic hotplug is pretty experimental and I think not every phone likes it the same way. Im already running 16.2 but I still need to do more ajustments on how and when the checks for cpu1 online/offline are made, and that is going to be my fun for the night =)
[Samsung Galaxy Nexus] homer2320776:
There seems to be a bug in the current version of franco.Kernel updater. If you've never used the program or are coming in from a fresh install, no matter what you set in the OC/UV part of the application will not set on reboot, regardless of if you've ticked the Set at boot box.

The only way to fix this, until Franco changes the program, is to manually use a program such as Root Explorer or ES File Explorer and browse to:

/system/etc

and create a folder called init.d

Apparently with the latest version of the app, it can no longer create this folder in the system directory. It may also be that I'm running 4.0.4 but this is a fix for it nonetheless.

After the folder is created you can go back into the franco updater and untick and retick the set at boot and it will create the necessary file in the init.d for the OC/UV to stick on boot.

EDIT: While the program will now add the 13overclock file to the init.d file, after reboot if you check the values that are presented inside franco updater, they are back to default while the 13overclock file still has the settings that were saved before the restart. If I use CPU Spy I can see that the frequency ranges that I've selected are in use but the second I load back up franco Updater the defaults are loaded back into memory, ignoring the 13overclock file.
[Samsung Galaxy Nexus] franciscofranco:
Now that's some interesting feedback, I didn't know about that at all. I will fix it tonight, thanks.
[Samsung Galaxy Nexus] crecsky:
Update: changing the group update interval made no difference. At home my wifi kicked me off saying it was still connected. Anyone have any idea what settings to use for the router that don't include static IP addresses and that don't require Mac blocking/allowing.
[Samsung Galaxy Nexus] drawde40599:
smooth

AOPK build 22 and kernel 16.1 - gazelle CPU 700/1350 running flawless!!!! battery cool 2!!
[Samsung Galaxy Nexus] nrgaway:
Suggestion. In your app, have a button a noob can press that will email you dmesg and logcat. Be sure to set a subject of kernel, etc when you send to yourself so you can easily filter :)

This should help with debugging, especially for users who would find it difficult to navigate shell commands or are unsure of which GUI app is the best suited for the purpose.
[Samsung Galaxy Nexus] franciscofranco:
That's a good idea as well, thank you!
[Samsung Galaxy Nexus] Vangelis13:
You ^^^^ there;

Holy fck.. Would you like a pizza & a beer with that..? :-)

Please (if you now have to post it here & not at the betterbatterystats thread..) post a document as attachment and not the raw data like that!

(P.S. It's endless on xda app, though the web version makes it look ok..)
[Samsung Galaxy Nexus] chardd23:
my Gnex slept too deep :( i cant wake it up without removing the battery. what do i do?
[Samsung Galaxy Nexus] jwood:
After reading all the messages about 16.1 I think I am going to stay on 16 for now.. Running smooth and less then 10% drain with screen on per hour and amazing screen off battery drain.. Less then 1% per hour.. If it ain't broke don't fix it...
[Samsung Galaxy Nexus] sishgupta:
On 16.1 my mipi_link kernel wake lock is really giving me issues.

Just got a 3hour wake lock for that of 6 hours uptime and 50 min screen on.

Not sure if its something I'm doing or what.

I have dynamic hotplug on.
[Samsung Galaxy Nexus] Cutting-TM:
350 MHz? Undervolted? Give us more information. Governor, CPU speed, hot plug etc.
[Samsung Galaxy Nexus] franciscofranco:
#3.1.1 franco.Kernel updater app

* Set on boot option for CPU settings should now work

* Dynamic hotplug and Hotplug mod not possible to select at the same time

* Add "Turn on CPU1" option. This is specially good when users change from francoTurtle and dynamic hotplug to another governor because it will make sure both cores are active and running
[Samsung Galaxy Nexus] homer2320776:
I just tested the new updater and it's doing the same to me. I'm beginning to think something is wrong with my init.d, it's like the scripts aren't being executed on boot. Everything I have it pretty much stock except root and franco.kernel.

I have busybox installed and all the scripts in the init.d directory have execute permissions.

What am I missing here?
[Samsung Galaxy Nexus] nicandris:
can you connect via adb shell and post an

ls -l
[Samsung Galaxy Nexus] homer2320776:
System Tuner (terminal) ======================= > ls -l (su) =======================

drwxr-xr-x root root

02-09 01:30 acct drwxrwx--x system cache

02-09 01:31 cache

root

-rwxr-x--- root

12-31 19:00 charger dr-x------ root root

02-09 01:30 config lrwxrwxrwx root root

02-09 01:30 d -> /sys/kernel/debug drwxrwx--x system system

02-09 01:32 data

root

-rw-r--r-- root

12-31 19:00 default.prop drwxr-xr-x root root

02-09 01:31 dev lrwxrwxrwx root root

02-09 01:30 etc -> /system/etc drwxrwxr-x radio radio

12-31 19:00 factory

root

-rwxr-x--- root

12-31 19:00 init -rwxr-x--- root root

12-31 19:00 init.goldfish.rc -rwxr-x--- root root

12-31 19:00 init.omap4pandaboard.rc -rwxr-x--- root root

12-31 19:00 init.rc

root

-rwxr-x--- root

12-31 19:00 init.tuna.rc -rwxr-x--- root root

12-31 19:00 init.tuna.usb.rc drwxrwxr-x root system

02-09 01:30 mnt dr-xr-xr-x root root

12-31 19:00 proc

root

-rw-r--r-- root

12-31 19:00 ramdisk.gz drwxr-xr-x root root

12-31 19:00 res drwx------ root root

02-07 12:11 root drwxr-x--- root root

12-31 19:00 sbin

root

lrwxrwxrwx root

02-09 01:30 sdcard -> /mnt/sdcard drwxr-xr-x root root

02-09 01:30 sys drwxr-xr-x root root

02-09 01:10 system -rw-r--r-- root root

12-31 19:00 ueventd.goldfish.rc

root

-rw-r--r-- root

12-31 19:00 ueventd.rc -rw-r--r-- root root

12-31 19:00 ueventd.tuna.rc lrwxrwxrwx root root

02-09 01:30 vendor -> /system/vendor > (su) =======================

Sorry for the crappy paste job, this is directly from a terminal on the phone itself. It's almost 2 am here and I was rushing to get something posted before bed. I'll post the adb output tomorrow though. Thanks for the help though.
[Samsung Galaxy Nexus] flolep:
:-( I think I reported too quickly...

16.1 flashed, I had another SOD this night... With the same parameters as before... I really thought it was finally stable with 350mhz frequency and dynamic hotplug but I must admit that it isn't...

So I go back to 700 - 1200 range until another build comes and I could try again.

Thanks for your hard work, Francisco.

P. S. Indeed, wifi random disconnections are a thing of the past, it seems to be more stable than before.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Mehrsau:
Noob Question: Can I install this Kernel also on 4.0.2. Stock?
[Samsung Galaxy Nexus] nicandris:
nop nop and nop 4.0.3 only (maybe 4.0.4 also)
[Samsung Galaxy Nexus] zack80:
I do not know if the cause of my trouble comes from the franco kernel 16.1 or of the millestone 3 rom but I noticed during a prolonged sleep there is a concern for freeze clocks. The clock on the lockscreen, the office and that of the taskbar displays a different time ..
[Samsung Galaxy Nexus] johno168:
nope its m3 aokp bug, a reboot fixed it. Having had it since.
[Samsung Galaxy Nexus] zack80:
thank you for the quick response, hoping that after a reboot the bug does not continue.
[Samsung Galaxy Nexus] johno168:
Glad to help! Let me know if its gone after a reboot!
[Samsung Galaxy Nexus] K.D.M.:
You are saying that he can't flash this kernel because he is on 4.0.2??

This kernel will change your version to 4.0.3 you don't have to be on 4.0.3 to be able to flash this kernel.
[Samsung Galaxy Nexus] qsec:
You have really misunderstood something here. This kernel is for 4.0.3 and it seems to function on 4.0.4 as nicandris says. But it does NOT work with 4.0.2 roms.

The kernel does not change you rom build to 4.0.3.
[Samsung Galaxy Nexus] Fihlvein:
I find that "turn CPU 1 online" a bit confusing. What exactly does it do and how it is benefical over normal behavior?

Sent from Galaxy Nexus, typos expected
[Samsung Galaxy Nexus] johno168:
Umm correct me if I wrong but I'm pretty sure you HAVE to be on a 4.0.3 rom to flash this kernel.
[Samsung Galaxy Nexus] danielvc:
Oh my, you really give the wrong advice here.
[Samsung Galaxy Nexus] minipaolo:
omg... facepalm
[Samsung Galaxy Nexus] StuMcBill:
............................................________........................

....................................,.-‘”...................``~.,..................

.............................,.-”...................................“-.,............

.........................,/...............................................”:,........

.....................,?......................................................\,.....

.................../...........................................................,}....

................./......................................................,:`^`..}....

.............../...................................................,:”........./.....

..............?.....__.........................................:`.........../.....

............./__.(.....“~-,_..............................,:`........../........

.........../(_....”~,_........“~,_....................,:`........_/...........

..........{.._$;_......”=,_.......“-,_.......,.-~-,},.~”;/....}...........

...........((.....*~_.......”=-._......“;,,./`..../”............../............

...,,,___.\`~,......“~.,....................`.....}............../.............

............(....`=-,,.......`........................(......;_,,-”...............

............/.`~,......`-...............................\....../\...................

.............\`~.*-,.....................................|,./.....\,__...........

,,_..........}.>-._\...................................|..............`=~-,....

.....`=~-,_\_......`\,.................................\........................

...................`=~-,,.\,...............................\.......................

................................`:,,...........................`\..............__..

.....................................`=-,...................,%`>--==``.......

........................................_\..........._,-%.......`\...............

...................................,<`.._|_,-&``................`\..............
[Samsung Galaxy Nexus] sotoskawasaki:
Well instead of giving facepalms you could try and explain the situation.

Kernels are compiled for a specific Android version. This Kernel is for Android 4.0.3. Therefore it will NOT work with Android 4.0.2! A kernel does NOT update your Android version. This is the job of the different roms. Now as for 4.0.4 I dont know, since there isnt any official source code release from Google.
[Samsung Galaxy Nexus] jhericurls:
I've stopped using Dynamic Hotplug and switch back to normal Hotplug. Dynamic was giving me quite bad idle time. 100% charge before I went to bed, woke up to 89% after 8 hours.
[Samsung Galaxy Nexus] minipaolo:
I did the same for the same reason, but I'm still having that issue with the old hotplug.

It looks like this 16.1 isn't running as it should on my phone.
[Samsung Galaxy Nexus] Elganja:
as did I.. phone feels a ton better now too. I felt with dynamic hot plug the phone was a bit more laggy overall
[Samsung Galaxy Nexus] manu_up:
Hi can you give me the instructions to do so. Can I just open terminal emulator and input these commands? Thank you very much.
[Samsung Galaxy Nexus] kodath:
Hey guys, I just have a quick question.

When I was on #16, I was using francoTurtle (700 and 1000)

Now when I updated to #16.1 it defaults on francoGazelle, but it's still set to 700 and 1000.

So question is, do I need to set it to 700 and 1200? Or 700 and 1350?

Thanks!
[Samsung Galaxy Nexus] nic85:
Still 700-1000

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] jhericurls:
I switched it back using Francos app.

https://market.android.com/details?id=com.franco.kernel&hl=en
[Samsung Galaxy Nexus] franciscofranco:
Both options are there for that reason, to give the user the power and control over the device. The dynamic hotplug is a nice idea in the paper, but Im not sure if its benefitial enough to spend much more hours into it. I will give another go today because yesterday I wasnt very successful.
[Samsung Galaxy Nexus] franciscofranco:
That is to make sure your cpu1 is online in case you change governors from turtle +dyn hotplug.
[Samsung Galaxy Nexus] khenderick:
I just flashed 16.1 and purchased the app, but it seems like the setting "Scaling governor" is not being saved/restored properly; After a reboot, its back at "francoGazelle". However, settings like "Hotplug Mod" are restored correctly.
[Samsung Galaxy Nexus] delvirtud:
My name is....and I am a kernel flash junky.

I keep trying everyone else's kernel, well, just because. As someone else has already stated, I always come back to Franco's. I haven't gotten the best battery life out of any of them, but I know it is my fault because of the particular apps/radios (enabled) that I run. Bottom line, this is the butteriest kernel I have seen. My UI is like ice and it is a very fast experience. Even though 16.1 is nice, it seems 15.2 for me seems to be the speediest.

Trying GummyNex after having tried AOKP and KANG CM9. Like it so far, but performance-wise they are all comparable as long as I use this Kernel.

/cheers

del
[Samsung Galaxy Nexus] sangio89:
Does this work with 4.0.4?
[Samsung Galaxy Nexus] qsec:
If you are running aokp look under performance settings and untick set at boot.
[Samsung Galaxy Nexus] StuMcBill:
I am running it on 4.0.4 (MoDaCo GSM Edition).

Not 100% sure if it will work ok on LTE, I imagine it will, but do a Nandroid just in case?
[Samsung Galaxy Nexus] blackdub370:
franco ... I have to say that version 13.1 works better than later version ... gta3 with the 16.1 version works with lag, however with 13.1 does not give me any lag ... I feel the same with the screen transitions, I tried to reinstall rom, kernel, wipes and still fails to do something ...

ROM: Milestone 3

Radio: xxkl1

IML74K

Max CPU: 1350MHz Min: 700MHZ Governor: Interactive in 13.1 / Interactive or franco.Gazelle in 16.1
[Samsung Galaxy Nexus] khenderick:
I use Manhattan IC112 and in the "Manhattan settings" there is nothing "set at boot".

Below the contents of the init.d director, if this might help debugging this issue.

root@android:/ # ls /system/etc/init.d
ls /system/etc/init.d
12gammaoffset
13overclock
89hotplug_enabled
root@android:/ #

root@android:/ # cat /system/etc/init.d/12gammaoffset
cat /system/etc/init.d/12gammaoffset
#!/system/bin/sh

echo -4 0 5 > /sys/class/misc/colorcontrol/v1_offsets
root@android:/ # cat /system/etc/init.d/13overclock
cat /system/etc/init.d/13overclock
echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo francoTurtle > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
root@android:/ # cat /system/etc/init.d/89hotplug_enabled
cat /system/etc/init.d/89hotplug_enabled
busybox echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled
root@android:/ #
[Samsung Galaxy Nexus] Stretlow:
Same.............
[Samsung Galaxy Nexus] sangio89:
it's ok im a gsm too :D