yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ncandy:
For those who want ZMod with FA R18: don't flash all at once (rom + gapps + kernel).

I did a clean flash 5/18 ZMod + gapps, wait until boot completed, then flash FA R18. It booted without any problem.

P/s: I used no debug FA and I thought that my maguro has a VLYOOM chip (not tested yet).
[Samsung Galaxy Nexus] akhi24nick:
I didnt have that issue in previous versions, just encountered since R17 i guess. Therefore posted it. Plus I thing CAB issue was fixed I guess.
[Samsung Galaxy Nexus] Punkiderma:
Also here, nodebug is stuck at Android logo on zmod
[Samsung Galaxy Nexus] BfstMtn:
I haven't tried R18 b/c people seem to be having problems. I do have that chip and had problems w/ main R17...
[Samsung Galaxy Nexus] bsmitty83:
For those having issues with boot ,

anybody want to try a test kernel for me ?

if it dosent work a dirty flash of the rom will reset the boot.img

I'm hopeful this kernel will solve the issue
[Samsung Galaxy Nexus] Fenix46:
smitty using GCC 4.9? because of old chip there a bug with this GCC
[Samsung Galaxy Nexus] BfstMtn:
It boots! :)
[Samsung Galaxy Nexus] Punkiderma:
Boots fine here!
[Samsung Galaxy Nexus] bsmitty83:
ha ! freaking knew it lol . It was an fstab mount flag called formattable , that is needed on my nexus 6 on the latest android release ( 5.1.1_r5 ? LMY47X )

anyways , I'll update the op shortly

Thanks guys for testing :good:
[Samsung Galaxy Nexus] bsmitty83:
Ok I reuploaded the fixed kernel's , they have the same title as the old ones so I advise deleting the old copies you have before re-downloading . hopefuly now they will work for everyone :p
[Samsung Galaxy Nexus] rambhanushali20:
Debug version dont work... And No debug version just booted... On Zmod 18/5
[Samsung Galaxy Nexus] BfstMtn:
R18 still won't boot past Google logo...
[Samsung Galaxy Nexus] bsmitty83:
I just tried it after reading this , and it booted for me . If one boots , the other should as well , there isn't enough of a difference between the two to have one work and one not work .

Does it just sit on the google screen ? does it make it to the boot animation ? im confused as to why this would be happening
[Samsung Galaxy Nexus] bsmitty83:
try this one out I guess , I changed the only thing I could think of that is different between the two that MIGHT affect boot for some
[Samsung Galaxy Nexus] BfstMtn:
Yeah, it just hangs at the Google logo then reboots over and over. No android boot animation. Just tried R18-NoDebug and it boots fine.

---------- Post added at 02:35 PM ---------- Previous post was at 02:18 PM ----------

[MENTION=4608636]bsmitty83[/MENTION], TestBoot-2 doesn't boot, unfortunately. Same: Doesn't get past Google logo.
[Samsung Galaxy Nexus] giudech:
now it boots!!

the second fixed copy of FA R18 NoDebug works fine for me :good: :highfive:

thanks man :good:
[Samsung Galaxy Nexus] venni:
The reuploaded R18-NoDebug boots fine. R18 and TestBoot-2 both bootloop at the Google logo.
[Samsung Galaxy Nexus] bsmitty83:
ok heres test no 3 for anybody that wants to try it
[Samsung Galaxy Nexus] bamtan2:
I am your humble servant ;)

Same problem here. The nodebug one I installed a few days ago works fine. I flashed this new one using the "zip" command in Flashify. I didn't wipe cache or do anything else. Is there something obvious we might be missing? I'm using TWRP 2.8.6.0.

It sits at the Google logo for a while and then reboots. Now it's sitting there slightly warm and getting warmer, not rebooting. It's trying very hard to turn on ;) I will now go back to R17 nodebug.
[Samsung Galaxy Nexus] bsmitty83:
Idk I'm at a loss as to why the nodebug version works and the regular version won't boot . its baffling to me . I must not be able to see some small detail I'm missing or something but I swear the regular version should be working , thanks for testing , I'll keep at it until I figure it out . what's really strange is that the regular version boots on my phone , I've tried it a few times , so I myself have no idea what's going on . frustrating to say the least though

EDIT : just to be sure , I factory reset my device , re-flashed Zmod , booted , rebooted to recovery , flashed R18 regular , and it booted 1st time , it sat on the google logo for about 15 seconds like always and booted right up . I feel like I'm chasing my tail on this one
[Samsung Galaxy Nexus] rambhanushali20:
It never cross Google logo... Keeps on restarting...
[Samsung Galaxy Nexus] siealex:
Latest r18 no debug ? ? fine. But why no 1036 MHz? I always set this as max, but here I see only 920 and 1200.
[Samsung Galaxy Nexus] bsmitty83:
mind trying this kernel for me ? I'm using a previous kernel config . It booted fine for me , but I need to make sure it works for all
[Samsung Galaxy Nexus] siealex:
This build booted up fine. But Trickster sees it as a completely different kernel.
[Samsung Galaxy Nexus] bsmitty83:
What does it show ? This is what my phone reads
[Samsung Galaxy Nexus] siealex:
It shows different kernel settings, especially governors.
[Samsung Galaxy Nexus] rambhanushali20:
Tried the test 5 kernel...Booted fine in 1st time..!

Congo..!

But i find some lags in zmod latest with this...

Can u provide with some settings..?

Btw I am using Nephilims settings.
[Samsung Galaxy Nexus] siealex:
Not only lags, but constant 50..70% CPU load at 1200 MHz regardless of running apps.
[Samsung Galaxy Nexus] Punkiderma:
Same here, R17 was blazing fast, R18 sometimes lags a lot, tried different governors but it doesn't change.

I think R17 was the only release that for me worked well on Zmod
[Samsung Galaxy Nexus] Djalaal:
I've noticed a bug of sort I think. Using R17 on ZMod. It's regarding bluetooth.

I'm using the Sixaxis Controller tool to connect my PS3 controller to my phone via bluetooth. It works when I'm on ZMod's stock kernel, but gets buggy when using R17. All else is the same (clean flash).

What I'm experiencing is the following 3 things:

First bug is that the controller becomes unresponsive for about 10 seconds every minute. It does not disconnect, as the channel 1 light remains on.

Second bug is that the Sixaxis app keeps repeating 2 lines over and over:

Client 1 battery status: Full

Client 1 battery status: Critical

This stops in the 10 second the controller becomes unresponsive like I described above.

Third bug is that occasionally (maybe once a minute) some button is pressed. It is not just one kind of button either. I use the PPSSPP to check this (free). It is located in Settings > Controls > Control Mapping > Test Analogues. I can say this though, it is usually the case that both analogue sticks move to the left bottom most corner for a split second (even though I didn't touch them). Sometimes moves to the right top corner too.

I'd appreciate it if you could look into this, even though this is something very few people use, and might not be very high on your priority list.

If you need any logs at all, I can provide them.
[Samsung Galaxy Nexus] sergialess:
Back to R17, and good. I don't know why R18 makes ZMod a bit more laggy.
[Samsung Galaxy Nexus] erk1725:
R18 in downloads tab working great on FML

Thanks [MENTION=4608636]bsmitty83[/MENTION]!!
[Samsung Galaxy Nexus] Rushead:
Hey [MENTION=4608636]bsmitty83[/MENTION], is there a way to disable radio altogether? [MENTION=2513714]CondemnedSoul[/MENTION] made a flashable zip for the Dinc2 years ago for those who are using wifi only.
[Samsung Galaxy Nexus] bsmitty83:
I remember , and I'm sure there is a similar way to do so . I noticed with a toro ROM on toro phone with no sim , you need to keeonit in airplane mode to get deepsleep. But if you flash a maguro ROM it deepsleeps on its own . it pretty much disables cell service . I'll look into it if I get some time
[Samsung Galaxy Nexus] PainFly23:
I wonder if this could be the same thing that's causing Bluetooth audio to be buggy for me. Try a few older versions to see if that fixes it. Bluetooth audio is buggy for me on R15 but totally fine on R14.1. Hopefully if we find out when the bug was introduced it will also help pin down the problem.
[Samsung Galaxy Nexus] ramosroger:
For all u having problems with latest full auto, does the screen turn black after Google logo? If it does just wait, its still booting but the latest kernel has a glitch that causes no boot animation. I wouldve never noticed if it weren't for some hardware glitch that causes the top and bottom pixels to be brighter on my gnex
[Samsung Galaxy Nexus] siealex:
No, it tries to reboot and sticks at Google logo.
[Samsung Galaxy Nexus] Driver007:
it stuck's at android logo and I can wait forever :D but it boots whit Full_Auto_TestBoot-5.zip
[Samsung Galaxy Nexus] siealex:
Yesterday I've installed GravityBox and this kernel (r18 nodebug) simultaneously, now I often have significant lags when opening apps (up to 1 minute). Is it kernel or is it GravityBox?
[Samsung Galaxy Nexus] osm0sis:
Only you can tell us that. Uninstall one or the other and troubleshoot yourself.
[Samsung Galaxy Nexus] Djalaal:
I'm guessing kernel because I'm on R17 with gravity box, and I don't experience such lags. You on F2FS?
[Samsung Galaxy Nexus] siealex:
No, ext4. R17 does not ? ? on my ?.
[Samsung Galaxy Nexus] bsmitty83:
Its possible that garbage collection and discard are too much together , for the next build I'll have garbage collection off , just discard . also I added flush merge flag back to fstab which should help .

Ive been running this kernel on Zmod and its butter smooth . 21k in antutu fwiw , no lags at all . I keep min screen on at 500mhz , overclock to 1.5ghz .

EDIT : I added R19 , no kernel side changes , but added the mount options to the fstab as mentioned above .
[Samsung Galaxy Nexus] rambhanushali20:
The thing i noticed after flashing r18 testboot 5....

it worked almost fine with few lags and when i tried to return to zmod rom kernel... or any other kernel or version of your kernel.. i got bootloop.. the only thing solved it was flashing testboot 5 again....

i think dirty flash of a rom would have solved it...
[MENTION=1533050]bsmitty[/MENTION]
[Samsung Galaxy Nexus] siealex:
R18 is very laggy... I switched to LuckyK v1.9 and have no lags at all.
[Samsung Galaxy Nexus] bsmitty83:
cool glad you found something that works for you ......
[Samsung Galaxy Nexus] bsmitty83:
I added a updated homemade FML build to the downloads section , its a build for all variants of the gnex , a clean flash is recommended .

EDIT : you may need to flash a different kernel to get it to boot , I couldnt get the stock kernel to boot , but I flashed R19 and it booted fine
[Samsung Galaxy Nexus] aditya.jazzmaster:
[MENTION=4608636]bsmitty83[/MENTION]

What is difference between NoDebug and the original one?

Thanks
[Samsung Galaxy Nexus] bsmitty83:
the nodebugging version is slimmed down a little bit , I removed some of the debugging options in the kernel , logcat still works , dmesg will not
[Samsung Galaxy Nexus] zieruchan:
[MENTION=4608636]bsmitty83[/MENTION] : What's new with R19 ?

Currently I'm using R18 and there is a bug, I can't receive file on bluetooth, unfortunately I'm on nodebug version
[Samsung Galaxy Nexus] Tolazace:
On maguro with old chip FML_tuna won't boot :/ I have bootloop on bootanimation.
[Samsung Galaxy Nexus] bsmitty83:
Flash a different kernel , the stock kernel won't boot . R19 boots fine .
[Samsung Galaxy Nexus] bsmitty83:
Only difference is the fstab Mount options
[Samsung Galaxy Nexus] bsmitty83:
I'll reupload a new FML with my kernel included as soon as it finishes building ........
[Samsung Galaxy Nexus] pkgnex:
Sorry to bother... but which android version or build number is the unofficial FML build - e.g. 5.1.0 or 5.1.1?

Thanks!
[Samsung Galaxy Nexus] bsmitty83:
5.1.1
[Samsung Galaxy Nexus] siealex:
R19 nodebug is as laggy as r18.
[Samsung Galaxy Nexus] pkgnex:
Thanks!

I'll probably give it a whirl later today or when you post the build with kernel included.

I've noticed that the 5.1.0 to 5.1.1 upgrade saved my son's Grouper from being a total lag disaster, so I'm hoping I have better luck with it on my Toro than I have with past FML builds.
[Samsung Galaxy Nexus] bsmitty83:
Its reuploaded
[Samsung Galaxy Nexus] bsmitty83:
I dunno what to tell you , my device is lag free .
[Samsung Galaxy Nexus] siealex:
I'll try to clean flash it tomorrow, today I flashed it over r18.
[Samsung Galaxy Nexus] zzpianoman:
Check for corrupt media files on your /sdcard. If you have any videos recorded before the green lines fix, consider moving them off of the device or just deleting them altogether.

Also, if on the off-chance you ever expanded a tarball of a /system partition to a folder on the /sdcard, (I used to do this quite frequently) considering removing this, or at the very least, the ringtones from the /media folder. Come to think of it, I'd get rid of any external ringtones/notification sounds as I believe this can lead to problems with lag.

Just my two-cents on the whole issue. Lag can come from anywhere - even the most unexpected places. I doubt it is a kernel issue.
[Samsung Galaxy Nexus] siealex:
I had one video file taken with ZMOD 10-05 build.

Why almost no lags on LuckyK even on 1036 MHz?
[Samsung Galaxy Nexus] sergialess:
Promising rom and kernel!!

Just the green lines bug... ;)
[Samsung Galaxy Nexus] pkgnex:
Thanks again, bsmitty83!

Does anyone have a recommendation on GAPPs for the unofficial FML ROM? What have the first few people that flashed this ROM used - any issues?

Thx in advance...
[Samsung Galaxy Nexus] bsmitty83:
I use the 5.1 FML gapps in the FML thread . check the downloads section
[Samsung Galaxy Nexus] bamtan2:
I installed the regular R19 and the system booted successfully. I guess you fixed that problem!

I noticed further settings changes. TCP changed to cubic. CPU governor settings changed (the speeds and their break points). I would rather read the changelog than ask you to explain every change ;)
[Samsung Galaxy Nexus] Younex:
Mine too (almost). At least I know that the kernel improves performances and lags are not related to it, more likely to the old eMMC or the nearly saturated storage space...
[Samsung Galaxy Nexus] siealex:
Regular R19 boots up fine, testing... It seems the regular version has much less lags than the nodebug one.
[Samsung Galaxy Nexus] sergialess:
It doesn't make too much sense. In theory "nodebug" means that the kernel isn't wasting time dumping logs, right?.

So, what's the difference between one and another?
[Samsung Galaxy Nexus] XXN:
Bluetooth problems

Hey [MENTION=4608636]bsmitty83[/MENTION] I had problems with my bluetooth headset since R15, for some reason the music stops and become choppy sound impossible of keeping listening.. Any Ideas of what happen or how to fix it? :confused:

PS: Sorry for my english, hope you can understand me..
[Samsung Galaxy Nexus] bsmitty83:
I have not been able to fix it , but yes I am aware of that bug . I'll keep trying to fix it .
[Samsung Galaxy Nexus] CondemnedSoul:
Use a terminal window and type

su

radiooptions 1

This does work still on my nexus, however, for one reason or another which I haven't looked into because I have been pretty busy with other things I'm working on, it does not work as an init.d script nor as a script run on boot with script manager or rom toolbox pro. Doing those methods you'll see it disable the service and put an x over the signal bars but then it starts searching again after about 15 seconds. If you disable it with the radiooptions command in terminal emulator however, it will stick until you reboot. Since I only use my nexus for music and other things only on Wi-Fi and I rarely reboot it for anything, it hasn't been a bother to me to disable the radio manually with the commands. :cool::beer:
[Samsung Galaxy Nexus] bsmitty83:
Yes , I noticed that now , but i don't have a sim card in so I don't see activity at all on the icon, i thought the script worked . glad to see you around buddy [emoji106]
[Samsung Galaxy Nexus] CondemnedSoul:
Doesn't on mine anyway.... I'm around some ;) lol just been inactive for a while especially on development. Been trying my creativity elsewhere and working on something I've always wanted to do instead lol. We'll see how that goes in time. :sly::thumbup:
[Samsung Galaxy Nexus] Rushead:
Woohoo! I successfully awakened the man! (too boastful?)

Glad to see/hear from you, bro. Thanks for your help, and hope all is well. Peace and damnation. [emoji14]
[Samsung Galaxy Nexus] CondemnedSoul:
At least you didn't awaken the demon :eek::eek: lol

All is well here bro :thumbup: .... Been on the G3 forums some lately but not working on anything. I was working on a rom but decided to put most of my free time into moving forward with writing my first novel instead :sly: ..... The divorce is finally over.... That was ugly lol.... Real ugly and still is :banghead: .... But I've moved out of state.... Ok, well actually.... Across the country lol.... I'm happy here though so that's good and I don't have her crazy family stalking me here :D

Peace??? That 5h!t5 for hippies homie :beer: lol.
[Samsung Galaxy Nexus] Punkiderma:
R19 on zmod is FAST. Incredibly smooth, like never before
[Samsung Galaxy Nexus] siealex:
R19 worked fine for several hours, then started lagging again. Trying LuckyK for at least one day...
[Samsung Galaxy Nexus] erk1725:
Im not trying to post any bug reports for the unofficial FML ROM@bsmitty83 was so nice to build for us, Im just curious if any toro users are getting 4g on their device? I flashed this last night, and up til now, Im still only getting 3g :(

Just wanted to know if anyone had the same issue and if they fixed it o not, before I restore my backup

Thanks
[Samsung Galaxy Nexus] nikodr:
Does zram crash now? I plan to use r18 or r19 on paranoid android 5.0 beta two that [MENTION=6140342]Fenix46[/MENTION] compiled for maguro. I just want to test it and see hiw it goes for this pa beta rom. Lucky kernel seems to work goid till now. But on zmod i was always on latest btsmitty kernel

---------- Post added at 02:19 PM ---------- Previous post was at 01:42 PM ----------

Reason i am asking is that i want to beta test this rom,and to be sure that any crashes or such are only from the rom and not the kernel.I remember i had some crashes on zmod latest with r16 when zram was on.
[Samsung Galaxy Nexus] rambhanushali20:
How can I download PA rom..?
[Samsung Galaxy Nexus] bsmitty83:
I havent had any issues with zram on but my phone isnt used very much at all anymore . I heard some users were getting reboots when an incoming call was received with zram on , but in my experience with my phone just sitting here , Ive yet to get a reboot from zram being on .
[Samsung Galaxy Nexus] bsmitty83:
I'm not sure , I dont have active service on the gnex anymore . I simply synced up FML's repo and compiled , I made no changes at all besides the kernel . did you check your network settings to make sure LTE is on ?
[Samsung Galaxy Nexus] erk1725:
Yes, the setting wont stick for 4g/lte it always goes back to 3G....Ive rebooted a lot, its weird tho, because in the status bar, during initial setup from a clean flash it showed 4g, but hasn't shown it since

its ok, just thought I would ask....thank you:good:
[Samsung Galaxy Nexus] osm0sis:
Knowing where the crashes come from is what stock kernel is for.. ;)
[Samsung Galaxy Nexus] nikodr:
well i am on paranoid android beta and install r19 i tried to apply nephelim settings all ok,but i dont know about the governor it used to have dyninteractive but on r19 it is gone should i use zeninteractive?which on is the same as dynamic interactive?
[Samsung Galaxy Nexus] bsmitty83:
if you feel like trying this kernel out for me to fix the Bluetooth issue , I'm trying to figure out what could be causing it . the only thing I can think of is swtiching to GPADC driver from MADC .

So heres a kernel with the latter driver . give it a shot and see how BT works .
[Samsung Galaxy Nexus] hubik.j:
Color multipliers in Synapse

[MENTION=4608636]bsmitty83[/MENTION]

I am on R19 nodebug and color multipliers in Synapse do not show up. Instead for all three of them, it shows:

SSeekBar has failed:
java.lang.NumberFormatException: Invalid int:
"2858644864"

Kernel Adiutor can set the multipliers just fine, but it misses a lot of other stuff. Can you look into it please? My screen is ugly green without it. Thanks.
[Samsung Galaxy Nexus] erk1725:
I believe you just need to uninstall any kernel settings apps other than synapse, and clear data and cache for synapse and immediately reboot, and it should show the values and let you adjust them:good:
[Samsung Galaxy Nexus] PainFly23:
Tested with Bluetooth audio and it didn't fix the problem for me, but I didn't test any other Bluetooth functions. It seems like whatever broke it happened between R14.1 and R15...
[Samsung Galaxy Nexus] hubik.j:
Reboot fixed it. Thanks!
[Samsung Galaxy Nexus] bsmitty83:
mind trying this one out for Bluetooth ?

What puzzlez me is I cant seem to figure out what changed between those two versions that would affect BT .

This test kernel probably wont fix the problem , but there is a chance

EDIT : after a LOT of logcats , I fixed it . I'll post a test kernel that works shortly ........
[Samsung Galaxy Nexus] bsmitty83:
OK Here's a test kernel with what should be fully working BT . I successfully transfered files from my laptop to my Gnex via BT , when I couldn't previously . So hopefully the crazy audio problems are fixed as well . I dont have a pair of BT headphones on hand ATM to test audio

So if someone could kindly confirm I can move on with this ..........lol
[Samsung Galaxy Nexus] lileoja:
A probar se ha dicho

Enviado desde mi Galaxy Nexus KitKat 4.4
[Samsung Galaxy Nexus] PainFly23:
Nice job, Bluetooth seems to be back in working order for me!
[Samsung Galaxy Nexus] aditya.jazzmaster:
After using this kernel for 2 days, I got lag and after view minutes it will smooth again, and continuously like that. It will be normal after rebooting.

PS: I use greenify.
[Samsung Galaxy Nexus] siealex:
+1. But I have such lags in 2..3 hours after rebooting.
[Samsung Galaxy Nexus] sergialess:
R19 and no lag with zmod. Not the smoothest experience, but used as daily driver. Thanks devs!

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] XXN:
It Works!

yep... you really do it! congratulations and thanks for your amazing work! :victory:
[Samsung Galaxy Nexus] aditya.jazzmaster:
[MENTION=1097461]siealex[/MENTION] after using for 3 days I got same problem like you, so any solution?

And what version of lucky kernel you used?

[MENTION=4815527]sergialess[/MENTION] can you share your kernel setting parameter? I still use standard value just change color value.

Thanks.
[Samsung Galaxy Nexus] siealex:
R19 regular, other versions don't start at all. All settings are standard except all MPU voltages are 100 mV lower and max frequency 1350 MHz.
[Samsung Galaxy Nexus] sergialess:
Default r19 settings, 1350 max, CAB on, Fsync off.

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] jguerdat:
I guess I just have weird hardware. Recent kernels are unreliable (reboots, etc.) for me and the unofficial FML does the same thing, kernel or not. Complete wipes help not at all. I have to use the 3/11 FML build plain to make things work. Toro here. Clues?
[Samsung Galaxy Nexus] siealex:
Galaxy Nexus has at least TWO (if not three) completely different hardware revisions. And the difference is not only the emmc chip. Try to install the official 4.1.1 image on a phone made after August 2012 - it will be bricked.
[Samsung Galaxy Nexus] klingklang76:
I have a maguro running Zmod pretty smoothly. I tried to flash kernel R19 (wiping system partition) and suddenly things got very sluggish, so I went back to stock kernel. I guess this kernel is not for everybody just yet, but keep on your much appreciated work, I'll be following future updates, thanks :)