yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] eternal70:
As i expected. Maybe anyone who can't boot through the google logo can confirm your chip type ?
[Samsung Galaxy Nexus] rohitchouhan07:
I confirm..
[Samsung Galaxy Nexus] mowto:
i confirm the emmc chip...VYL00M
[Samsung Galaxy Nexus] bsmitty83:
well , I'm not sure why this bug is now affecting my builds , I don't recall it ever being an issue before . so it's new to me .

If anybody with a VYL00M based memory chip wants to test a kernel for me , it's posted here .

Again even with a good boot it will take more than a minute on the google logo . I added the mmc workaround for this test kernel , no idea if it works thats why i need a tester lol

and for those already using r21 , hope its doing well .....
[Samsung Galaxy Nexus] christianpeso:
I do not have the aforementioned emmc that supposedly has issues. R21 boots and runs fine for me. Thank You! Actually better than R20 which was super unstable and laggy for me. This is much better. It does seem to be missing the 1400000 speed step. At least it is not showing up in the latest version of Trickstermod. I liked that speed as it was the highest speed I can go without the phone crashing on me. Anything above 1500000 crashed. Anyway to add that back?
[Samsung Galaxy Nexus] dalvear88:
For me, I was able to get booted with the original R21, but for some reason it murdered my camera all together, not even 3rd party apps work. I'm on the last FML from 3/11 (the FML in this thread doesn't boot for me)

If I install FML without the Kernel then I have camera no problem.
[Samsung Galaxy Nexus] handofdark:
stuck on google screen . waited for 5 minutes. latest zmod
[Samsung Galaxy Nexus] massoudsh:
Me too, stuck on google logo even with test version of R21. My phone have VYL00M eMMC chip & run latest euphoria rom.
[Samsung Galaxy Nexus] eternal70:
Yeah i have camera problem too. Now it shows can't connect to camera. Also playing youtube make the device to freeze.

Im trying to get the log
[Samsung Galaxy Nexus] bsmitty83:
I noticed it a well , I'm not yet sure of the cause , I made no changes to video or RAM allocation , or anything , so I suspect its some derp on my part somewhere in my config or setup . something I'm missing .

think i just fixed it ............hold tight
[Samsung Galaxy Nexus] mowto:
It stucks on google logo even with the latetst kernel patched for VYL00M.
[Samsung Galaxy Nexus] bsmitty83:
Ok , so I fixed the insanely long boot times , and camera crashes . Turns out it was related to input boost so I removed it

Hopefully this will aslo fix the boot issue for those who cant get it to boot .

I freed up 8mb of ram also , should be 760 total now .

the kernel is in the downloads section replacing the old R21
[Samsung Galaxy Nexus] massoudsh:
I am very sorry [MENTION=4608636]bsmitty83[/MENTION], tested R21.1 and it stucks on google logo again...
[Samsung Galaxy Nexus] siealex:
No luck, stuck forever at Google logo and constantly heating.

PS, I can connect via ADB, but I can do nothing: no /system/bin/sh or other errors.
[Samsung Galaxy Nexus] mowto:
Same here, 10 minutes at google logo.
[Samsung Galaxy Nexus] bsmitty83:
OK cool , Im not sure what to do to get the kernel to boot on the touchy emmc , I'll keep putting out test kernels for those that cant boot .
[Samsung Galaxy Nexus] mowto:
It boots on my nexus
[Samsung Galaxy Nexus] bsmitty83:
Awesome , I finally know what it is then . hopefully I can get another person to confirm .
[Samsung Galaxy Nexus] dalvear88:
I was able to boot the original R21, and now the R21.1 is practically perfect. Everything runs smooth and camera is back.
[Samsung Galaxy Nexus] massoudsh:
I confirm that, last test version boot fine for me finally and I'm very happy, thanks very much man!!
[Samsung Galaxy Nexus] bsmitty83:
Thanks for testing guys
[Samsung Galaxy Nexus] bsmitty83:
I added the test kernel to the downloads section , R21.1 should now boot for everyone
[Samsung Galaxy Nexus] madhavs:
why App RAM usage always showing 0.00Bytes I tried on both Euphoria And Chroma ROMs but with stock kernel of those individual ROMs everything OK

Also some times Free RAM values showing in Minus values

I am On Latest kernel
[Samsung Galaxy Nexus] jcpowell:
For those of us that your original booted fine is there any point in using your test build?
[Samsung Galaxy Nexus] christianpeso:
If you would like faster boot times and 8MB more RAM to use, I would say yes. :D
[Samsung Galaxy Nexus] siealex:
The latest build boots fine. Testing...

PS. It is much smoother than R20.
[Samsung Galaxy Nexus] siealex:
After several reboots it stopped at Google logo...
[Samsung Galaxy Nexus] eternal70:
Anyone have video playback issues ? Camera works here but videos in instagram and line just black and only playing the audio. Chroma here
[Samsung Galaxy Nexus] Fenvarien:
Latest kernel build 21.1 works very smooth and stable here. Thanks for the new version!
[Samsung Galaxy Nexus] giudech:
after a clean flash of Dreams and F.A 21.1

also on my phone I have some problems with the monitoring of the ram usage,

everything else seems to work well anyway,

thanks for all your efforts :good:
[Samsung Galaxy Nexus] siealex:
Build 21.1 gives random reboots two or three times per day. WTF?
[Samsung Galaxy Nexus] bsmitty83:
No idea bro , I'm not a mind reader , you give me nothing to go on , no logcat , no last_kmsg . I just don't understand how after all this time , I still get messages like this . logcat or GTFO
[Samsung Galaxy Nexus] siealex:
How to get logcat of a reboot if all logs are cleared on boot?
[Samsung Galaxy Nexus] eternal70:
[MENTION=4608636]bsmitty83[/MENTION] Oh yes, regarding the playback issues, here's the log. OMX is failing

https://drive.google.com/file/d/0B7SqITe__f5KU0drRTlQVTNqd2c/edit?usp=docslist_api
[Samsung Galaxy Nexus] osm0sis:
last_kmsg specifically is for this purpose. Not seeing any reboots on my device, mostly defaults but cranked GPU up to 512 and CPU max up to 1350.
[Samsung Galaxy Nexus] siealex:
Random reboot with screen off...
[Samsung Galaxy Nexus] nikodr:
Overclocked to 1650, applied nephelim settings all good. And much more free ram 760.no reboots. :)
[Samsung Galaxy Nexus] siealex:
Logcat in my previous post did not catch the reboot, I replaced the file.
[Samsung Galaxy Nexus] massoudsh:
If anyone feel R21 with interactive governor is little lagy use trickster app and go to governor control, then change default value to the below and enjoy:
[Samsung Galaxy Nexus] bsmitty83:
You setting SElinux enforcing ? I'm just comparing your kmesg , and normally i see a line that says ">SELinux: Starting in permissive mode" , but its not there . Also there is no stacktrace , no kernel OOPS , nothing that points to the kernel being responsible for the reboot. Sorry I cant help more but anything else would be just a guess on my part . I'm always very critical of how the build works on my own device , I usually have a good feeling for how stable a version is . Like for example , on DirtyV I really hacked up zram to get it to work , but this time I took alot more time and knowledge into it and I didnt have to force anything to build .

I'll keep an eye out for any strange behaviour or reboots on my own phone . I've been using it as a music player at work with BT headphones and have no issues , hell the usual screen off music stutter is gone too
[Samsung Galaxy Nexus] siealex:
Can it be improper undervolting? I've set all MPU voltages 100 mV lower than stock (this configuration worked perfectly on 4.4!) and minimum calibrated MPU voltage to 775 mV.

PS, I do not change anything related to SElinux. Can Xposed change its mode?

PPS, I saw a large empty space (at least 30 minutes) on the battery usage graph before this reboot. What's this?
[Samsung Galaxy Nexus] bsmitty83:
Yes I'm sure it could be voltage related. selinux is probably fine , if anything xposed would force it permissive I would think.

Idk about the battery graph , I'd guess it could be from the undervolting as well.
[Samsung Galaxy Nexus] siealex:
Empty space on the battery graph means the system was frozen or not booted during this period.
[Samsung Galaxy Nexus] bsmitty83:
But it wasn't , correct ? If so , then too low of voltage from the battery could mess with the battery graph I suppose . I've had graphs that look like that when the CPU locks , and reboots less than a min later , losing 20% or more in battery . so , that's also why I suspect the undervolting . but its just my humble opinion.
[Samsung Galaxy Nexus] girkev:
Nephelims settings - Good point.

The min free settings are obvious.

What I do really miss are the other recent kernel settings for this kernel.

It can't be that all ended with KitKat setup.

Any sources known? I googled a lot without success. Thanks a lot for any hint.

sent from my gnex with Tapatalk

---------- Post added at 12:07 PM ---------- Previous post was at 12:05 PM ----------

That is a good piece of information. Thanks.

sent from my gnex with Tapatalk
[Samsung Galaxy Nexus] siealex:
Using TRIM with this kernel causes almost immediate soft reboot. Anyone confirms?
[Samsung Galaxy Nexus] Fenvarien:
Running trim from the terminal for /data and /cache is working good here.
[Samsung Galaxy Nexus] siealex:
Can't switch off ZRAM. Is it possible?
[Samsung Galaxy Nexus] siealex:
Soft reboot two minutes after running fstrim /data in the terminal.
[Samsung Galaxy Nexus] massoudsh:
Confirm... Trim work for me without any problems.
[Samsung Galaxy Nexus] siealex:
How do you run it? Simply fstrim /data?
[Samsung Galaxy Nexus] bsmitty83:
I hate to say it , but I think your EMMC is starting to go , or there is another hardware issue . I replaced the CPU board in my gnex almost a year ago , it randomly rebooted no matter what I did until one time it wouldn't even power on .

But then again you only seem to have these issues on this kernel , so maybe it's just something between your setup and my kernel that don't work .

Zram swapoff works , I tested it many times lol . Sometimes TricksterMod app will revert the switch to on , even though it really is off , but it corrects itself once you exit the app and reopen it .

I also trimmed /system without issue , I'm on f2fs for the others .
[Samsung Galaxy Nexus] siealex:
It's a SOFT reboot, hardware errors always give a full reboot.

PS. What does "-v" mean?

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

It always reverts this switch to on.
[Samsung Galaxy Nexus] bsmitty83:
If its not hardware then idk what the issue is . the kmesg you post have no stacktraces in them , which it would if the reboot was kernel related .

-v is verbose , to have it output what its doing .

Zram switch stays off . zram is off .
[Samsung Galaxy Nexus] Punkiderma:
I can't reproduce videos anymore using Quickpic. Other apps like VLC works well, but this one shows a black screen without audio (or just with the initial seconds).

I post here because with lucky kernel I've never had this problem, so maybe is a conflict between the app and this kernel.

I attach a log, if you prefer a text log file just let me know! Thanks!

By the way, apart from that for me 21.1 is perfect. Blazing fast, zram gives no problems. I've got just a random freeze+reboot once.

Just for curiosity, why isn't zenteractive the default governor? Do you recommend it in favour of classic interactive?

Thanks a lot!

EDIT: I also have issues when trying to record a video; seems like the first days of lollipop, camera crashes as soon as I touch the recording button

EDIT AGAIN: only default camera app seems to do that, but I've got again the purple line at the bottom of the video

EDIT AGAIN AND AGAIN (sorry!) : after 2 reboots, the problems with playback and recording are gone( just the purple line remained) . No idea about what could be.
[Samsung Galaxy Nexus] siealex:
After a reboot this kernel is very smooth, but then (usually after 10..20 hours) it suddenly starts lagging like hell, e. g. Skype opens 2..3 minutes instead of 15 seconds. Almost all settings are stock, except OOM settings that are very close to Nephilim's. WTF?
[Samsung Galaxy Nexus] trzesickipiotr:
Hi

I had one reboot during a call.

Last_kmsg shows:

Internal error: Oops: 17 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 Not tainted (3.0.101-Full_Auto-ga46f031 #22)
PC is at kmap+0x24/0x68
LR is at kmap+0x24/0x68
pc : [<c0065fec>] lr : [<c0065fec>] psr: 60000013
sp : e6ffbe08 ip : c07b4cf4 fp : e6ffbe1c
r10: d2151780 r9 : c08b2b88 r8 : 00000004
r7 : c08b2c8c r6 : e707241c r5 : 003ae5c5 r4 : ffffffff
r3 : 60000013 r2 : 00000000 r1 : 00000017 r0 : 00000000
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 10c5387d Table: 82f0004a DAC: 00000015

I'm on CM12.1

PT
[Samsung Galaxy Nexus] bsmitty83:
OK thanks , next time it happens , can you grab me the entire last_kmsg ? It has more of the error trace in it .
[Samsung Galaxy Nexus] trzesickipiotr:
I grabbed all the logs after a reboot.

Here is full last_kmsg.

View attachment last_kmsg.log

PT
[Samsung Galaxy Nexus] brandonabandon:
i have this error with a personal build. compiling AOSPA with 4.9. i flashed a few other kernel in the theads and no avail. http://pastebin.com/QjTJNi59 <-logcat or

W/linker ( 1199): libEGL_POWERVR_SGX540_120.so: unused DT entry: type 0xf arg 0x54e
W/linker ( 1199): libIMGegl_SGX540_120.so: unused DT entry: type 0xf arg 0x898
W/linker ( 1199): libsrv_um_SGX540_120.so: unused DT entry: type 0xf arg 0xeb9
D/libEGL ( 1199): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
W/linker ( 1199): libGLESv1_CM_POWERVR_SGX540_120.so: unused DT entry: type 0xf arg 0xd66
W/linker ( 1199): libusc_SGX540_120.so: unused DT entry: type 0xf arg 0x2dc
W/linker ( 1199): libGLESv2_POWERVR_SGX540_120.so: unused DT entry: type 0xf arg 0xe4b
W/linker ( 1199): libGLESv1_CM_POWERVR_SGX540_120.so: unused DT entry: type 0xf arg 0xd66
W/linker ( 1199): libusc_SGX540_120.so: unused DT entry: type 0xf arg 0x2dc
D/libEGL ( 1199): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
W/linker ( 1199): libGLESv2_POWERVR_SGX540_120.so: unused DT entry: type 0xf arg 0xe4b
D/libEGL ( 1199): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
W/linker ( 1199): libpvrANDROID_WSEGL_SGX540_120.so: unused DT entry: type 0xf arg 0x112

--------- beginning of crash
E/AndroidRuntime( 439): *** FATAL EXCEPTION IN SYSTEM PROCESS: MountService#onDaemonConnected
E/AndroidRuntime( 439): java.lang.IllegalArgumentException: Failed to find storage device at /storage/emulated/0
E/AndroidRuntime( 439): at android.os.Environment.isExternalStorageEmulated(Environment.java:791)
E/AndroidRuntime( 439): at android.os.Environment.isExternalStorageEmulated(Environment.java:775)
E/AndroidRuntime( 439): at com.android.server.pm.PackageManagerService.isExternalMediaAvailable(PackageManagerService.java:8555)
E/AndroidRuntime( 439): at com.android.server.pm.PackageManagerService.startCleaningPackages(PackageManagerService.java:8595)
E/AndroidRuntime( 439): at com.android.server.pm.PackageManagerService.updateExternalMediaStatusInner(PackageManagerService.java:13595)
E/AndroidRuntime( 439): at com.android.server.pm.PackageManagerService.scanAvailableAsecs(PackageManagerService.java:13508)
E/AndroidRuntime( 439): at com.android.server.MountService$3.run(MountService.java:864)
I/Process ( 439): Sending signal. PID: 439 SIG: 9

any ideas?
[Samsung Galaxy Nexus] ramosroger:
Maybe try r21 since its the latest and greatest
[Samsung Galaxy Nexus] siealex:
Anyone here experiencing horrible lags and freezes after 1..2 days uptime? I switched back to LuckyK and don't have lags for 4 days...
[Samsung Galaxy Nexus] brandonabandon:
I quoted the post for the error. Regarding all kernels. Hoping some devs are familiar with the error. Thanks for the reply. I flashed r21.1, lucky, and a few personal builds with various toolchains which were tested otherwise.
[Samsung Galaxy Nexus] nikodr:
I am running r21 overclocked to 1.650 is it possible to go for more in the max cpu settings under trickster? I successfuly undervolted it. Would love to know if it is possible to go to 1.8 or more mhz.
[Samsung Galaxy Nexus] christianpeso:
And to piggyback on this, this is the 1st kernel I have used on this phone that has accepted and ran without force closes on the 1.6ghz settings. Dont know how, but it is stable. Great work.

I have since went back to Kit Kat, but I will definitly be back on this kernel sooner or later. Thanks!
[Samsung Galaxy Nexus] nikodr:
Can the kernel developers make 1.7 or 1.8 ghz number available for use on tricksyer? 1650 srrms to be the limit
[Samsung Galaxy Nexus] bsmitty83:
It should be possible if I build a kernel with a higher CPU frequency , I remember JB kernels with a max of 2+GHz , but its simply not worth it . the performance gain vs battery loss and high heat , plus the extreme instability , I've found almost no gain in benchmarks or real world use from 1.5 --> 1.6 GHz .

I've always tried to focus on memory management and handling as I believe this is where the most improvement to user experience can be made on our gnex .

The frequencies are hardcoded into the kernel , so unless a kernel is built with higher frequencies , the max is the max .
[Samsung Galaxy Nexus] Djalaal:
Well, my Nexus (maguro) apparently thought it's about time I switched phones. Today it kicked the bucket. It does not turn on anymore. Has been coming for the last 2 weeks.

Just wanna thank all of the devs for keeping the device alive and kicking all this time [MENTION=4608636]bsmitty83[/MENTION], [MENTION=3390093]MWisBest[/MENTION], [MENTION=2633638]Ziyan[/MENTION], [MENTION=4986658]freshgiammi[/MENTION].

It was a fun ride, and I hope you guys (+community) enjoy your devices for longer.

See ya around.
[Samsung Galaxy Nexus] zzpianoman:
I second this.

Memory management is definitely going to give you much more in the way of performance than simply boosting the CPU clock frequency. I think that is one of the biggest bottlenecks of the Android platform, in general - and it seems as if device manufacturers are simply throwing in more RAM and faster CPUs with more cores rather than focusing on improving and streamlining the OS itself, particularly in the way it handles memory usage.
[Samsung Galaxy Nexus] Christopher8989:
I just tried R21.1 with zzpianoman's 7/11 version and it stuck at Google, won't boot any farther.
[Samsung Galaxy Nexus] zieruchan:
Of course it won't boot, zzpianoman using old ddk(1.8) and fullauto using updated ddk(1.9).

You may need to search before ask it here,
[Samsung Galaxy Nexus] cango123:
From zzpianoman's cm 12.1 thread: "Please note that you can NOT use any other kernels with this ROM!! I have added a number of additional features to the kernel including custom voltage, fast charge, and color adjustment so hopefully that will satisfy enough for the time being. "
[Samsung Galaxy Nexus] zieruchan:
Yes ! We should focus on memory management

Kitkat memory management is really bad than jellybean,

but Lolipop memory management more than bad2x than kitkat
[Samsung Galaxy Nexus] bsmitty83:
Well , each version is more complex , and is really intended for current flagship phones , not years old phones .

I don't have any issues with how lollipop runs on the gnex , for the most part .

Also I'm sure when the next version of android comes out , it will run far better on this phone than 5.1 .I've been using the dev preview on my n6 since it was available , and it is basically a polished version of lollipop.

I really don't think the actual memory management has gotten worse , its really just the operating system has gotten more complex and 1 GB of ram is just barely enough.

But I'll keep working on it as long as my device works
[Samsung Galaxy Nexus] siealex:
On Lollipop I have no multitasking at all, starting e. g. the builtin browser kills all other processes, sometimes including launcher and Llama...
[Samsung Galaxy Nexus] nikodr:
Are there any more ways to increase ram? Now it is 760. Other 1 gigabyte ram devices have same free ram? Would kernel 3.4 help? Is the omap 3.4 kernel project alive? I know aosp got a new maguro.

Reason i am asking is because this kernel and fenix46 are the only ones that seem to be alive in the community of maguro and the only ones that could have 3.4 staitus maybe in the future.
[Samsung Galaxy Nexus] eternal70:
Yea, 3.4 will help so much. We've lost 200mb ram for hardware decoding/encoding but 3.4 will solve this problem. I think the devs is working behind the scene. All we can do is just be patient [emoji5]
[Samsung Galaxy Nexus] nikodr:
So you say that 3.4 would offer more free ram? I never understood why nexus loses so much ram for hardware decoding.
[Samsung Galaxy Nexus] osm0sis:
If I recall correctly, 3.4 allows RAM sharing, so yeah, it'd be a total game changer. :)

Every device reserves RAM for things like that, the problems were more that they didn't factor that in when advertising it as a 1gb RAM device and TI OMAP playing it safe with a carve-out so large we really only have like 768mb.
[Samsung Galaxy Nexus] siealex:
693 Mb on stock kernels.
[Samsung Galaxy Nexus] nikodr:
Thank you for this explanation. How difficult would it be to have ran sharing on galaxy nexus? Is it a feature that can be backported to the kernels we have now? Do you plan to invest any time with btmitty83 to resume tge omap 3.4 project?
[Samsung Galaxy Nexus] osm0sis:
Absolutely not my area of expertise, so I won't have much to do with it. [MENTION=4608636]bsmitty83[/MENTION] can tell you his plans. :good:
[Samsung Galaxy Nexus] Nephilim:
So, just stopping in to say I've finally retired my Gnex from daily use. N6 is the new toy and I thoroughly love it!
[Samsung Galaxy Nexus] sergialess:
:_(_ _

So you and BSmitty are playing with Nexus 6... I'm considering doing it too. Next monday the OnePlus Two is presented. If it convinces me, perhaps I get it. If not, the Nexus 6 is a candidate , although I've read negative comments about the camera, not performing as it should be.

Anyway thanks for your support and your fantastic kernel settings.
[Samsung Galaxy Nexus] Djalaal:
My Gnex retired recently too (without my consent). I now bought a budget phone (zenfone 2 lowest spec version) for half the price I bought my Gnex 3 years ago. So far it's doing great in both multi-tasking (2gb ram) and smoothness. I gotta say this one thing. Looking back at all the trouble I've gone through to try and make the Gnex run decently, it seems like I've been wasting my efforts. I would now recommend anyone with problems to just get an upgrade already. It's just worth it.
[Samsung Galaxy Nexus] eternal70:
That's so true. Without 3.4 i guess gnex wont last any longer because apps are changing very fast and make it more heavy and ram-hungry. I remember in 4.3 when chrome is still smooth in gnex.......
[Samsung Galaxy Nexus] nikodr:
May i recommend something? Now that your nexus is not daily phone since you bettysmitt83 aosp and ziyan are the jedi masters of kernel development could you just do experiments for the kernel 3.4? And you wouldnt feel afraid since you have a n6 :D
[Samsung Galaxy Nexus] Nephilim:
To be honest, I've been playing with the camera a bunch and my photos and video have all come out super crisp and clear. I absolutely recommend this device. My only regret is that I didn't utilize the edge program and get it sooner.

I personally don't build kernels but I have no objection to experimenting with my Gnex now. Mainly I'm just utilizing it as a touchscreen mp3 player at this point.
[Samsung Galaxy Nexus] bsmitty83:
Some people were having issues with the n6 shooting video , it seems the camera will constantly refocus , but I haven't personally seen it . [MENTION=2853378]Nephilim[/MENTION] , you should download the m Dev preview , it's much better than lp , definitely more than stable for everyday use too .

I'm still messing with my gnex , I haven't had a whole lot of free time lately , but I'm still around .

There's a few people working on a 3.4 kernel , I personally don't think I have the skill to make it work , but its still a project I mess with . I've backported or committed many backports from 3.4+ for my lollipop kernel , so I'll probably keep working on it until someone gets a working 3.4 kernel going .