yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Meandi51:
Well, started yesterday but ended in Gnex not recognized in fastboot mode.

The Samsung driver seem to be proper installed, as adb works.

Once in bootloader cant talk to the phone anymore.

Aborted due to less time yesterday, but will proceed later today.

EDIT: It was driver issue.

Strange, did a lot devices before as Nexus 5x and several Samsung.

Anyway, now its done and hey, this Rom (yes 6.0, latest release) is superb.

It feels even much smoother than stock before.

Thanks again for your precious hint.
[Samsung Galaxy Nexus] phaleg:
Awesome, enjoy the best android device ever made!
[Samsung Galaxy Nexus] Castro27:
Im using the Full_auto kernel but it's still not working. Should I use the beta one?

EDIT: Nevermind, its working
[Samsung Galaxy Nexus] theBlackEnd:
Test Build 4 is up. I'm sorrry for all these troubles with kernel.

Changelog:

- Audio is now working properly and so is video recording, you won't need an external kernel;

- Kernel is now built with GCC 4.9.3 [12.14] Optimized for Cortex A9;

- Merged lastest MWisBest's changes to camera, I guess it should be a bit more stable now;

More:

VLC and MX Player do play videos (even with HW decoding enabled).
[Samsung Galaxy Nexus] smartAgent47:
Is camera recording without those green glitches when we play the video or it has still those glitches ??

And torch toggle working ??

Thanks and salute :good::good:
[Samsung Galaxy Nexus] xaifer:
With this build can I format system, cache and data in f2fs?
[Samsung Galaxy Nexus] theBlackEnd:
There's still a small green band on the left of recorded videos. Torch tile is not working yet.

Nope, I have to add f2f support in device tree and fs fallback in system/core. I've already cherry-picked all commits needed to another branch of our kernel.

Well, it looks like system/core already supports fallback. If so, I just have to re-build kernel and re-add a few lines (that I discarded two days ago -_-) to device tree.

--

However, since converting /system to f2f brings no gain in performances, I'll probably add f2f support just for cache and data.
[Samsung Galaxy Nexus] xaifer:
OK I hope that full support be ready as soon as possible

PS i have bugged chip and f2fs save my maguro. With system in ext4 lag everytime

Sorry for my english
[Samsung Galaxy Nexus] Castro27:
Did anyone else lost root?
[Samsung Galaxy Nexus] zzpianoman:
I don't even see how it would be possible to have /system as f2fs, considering the fact that many of us are having problems fitting everything onto an ext4 formatted partition. Only way it would ever work is if the ROM was fully deodexed and even then you'd be cutting it pretty close.
[Samsung Galaxy Nexus] rjshrjndrn:
Where is advanced powerboot and status bar data monitor settings.

Slimkat 9.0
[Samsung Galaxy Nexus] Airlibik:
I'm not able to download slim lp gapps...the link in the op is empty...

I found 2 external link to get it

http://104.237.50.75/Gapps/Lollipop/

http://104.236.22.120/index.php?device=gapps/lollipop
[Samsung Galaxy Nexus] theBlackEnd:
I'm using SuperSU atm, I don't know if that's due to SlimROM's supersuser or just to something I'm missing, I'm really busy with school and finals these days and I had to fix kernel first.

Thank you for pointing this out. :) I know f2f formatted system reduces available space but I didn't think about that to be honest.

Advanced powerboot: Settings > Security > Advanced powerboot

Status bar data monitor: I never used it, anyway, according to this it has been removed.

You're welcome.

I don't know why they removed all SlimLP gapps ._.'

Where did you find those links? I don't think they're official.

Use PA gapps instead until repopulate download page.

---

Anybody with VYL00M eMMC chip could report if TB #4 boots on your device? Thank you in advance.
[Samsung Galaxy Nexus] Airlibik:
Well I took this gapps from slim lp thread for nexus 5 here in xda and I think they are official I used them and they worked as they should.

Anyway I want to thank you for your work porting here my favorite Rom I didn't expected that it should work so good I really love it :) the only two things that I notice (and they are rly not important) are that the boot animation is sluggish and at first install the system says that we are using a tablet :) performance instead are awesome I've hit almost 19.000 on benchmark with bsmitty kernel and nephilim settings keep up the good work !
[Samsung Galaxy Nexus] Airlibik:
I had not tried camera yet and I must say that it didn't work neither stock camera nor 3rd camera app...when you open camera screeen become black.
[Samsung Galaxy Nexus] ducnknd:
Nice Rom

I like this ROM. But my GNex very often is turnned off cellular network :(.
[Samsung Galaxy Nexus] aliesz:
is this rom stable enough for daily use?
[Samsung Galaxy Nexus] theBlackEnd:
I just made a factory reset to check that. Camera is working fine here. Try cleaning cache and using PA gapps.

I'm uploading SlimLP official gapps (439, mini). Use this package until they fix downloads in official. Check post #1 in ~10 minutes for download link.

What do you mean?

If you don't mind issues in first post, yeah, it's pretty stable.
[Samsung Galaxy Nexus] Airlibik:
well I made a clean install with the new gapps in the op and camera now works:good:
[Samsung Galaxy Nexus] Pjodor:
I must say that this LP rom works best on my phone right now, thanks hope to see more updates :)

Skickat från min Galaxy Nexus via Tapatalk
[Samsung Galaxy Nexus] aliesz:
I can't download from the OP link :(
[Samsung Galaxy Nexus] Airlibik:
Someone is having trouble with calls chronology? I don't understand why but some number I call become unknow after some minutes in the chronology is someone else expecting this?
[Samsung Galaxy Nexus] theBlackEnd:
Thank you for your feedback. I really appreciate it :)

Meh, sometimes AndroidFileHost goes down. It's working fine now.

Just checked this. I can't replicate that bug. Can anybody else confirm?

-----------------------------

Test Build 5 is up now :)

Short changelog this time, but it's worth a flash (ehehehe)

Changelog:

- Torch tile is now working fine. If it doesn't for you, please, wipe cache and try again.

- ScreenRecord should be fixed. I haven't tested it, though.

- Video playback works fine on stock gallery apps

Many thanks to Cyanogen guys and to [MENTION=3457922]stargo[/MENTION] :)

Updated Gapps: http://104.237.50.75/Gapps/Lollipop/

These are official from SlimROM.

PS: I still need somebody to confirm that TestBuilds #4 and #5 boot on maguros with VYL00M eMMC chip. Nobody is complaining so I guess #4 was, but I want to be sure before removing this from Known Issues.

You can check your eMMC chip by typing from shell:

adb shell cat /sys/class/block/mmcblk0/device/name
[Samsung Galaxy Nexus] aliesz:
for me it occurs every time ,:crying: may you upload files on another download center?:rolleyes:
[Samsung Galaxy Nexus] Tolazace:
I have maguro with VYL00M eMMC chip and last build #5 boot and works great :D Video in 1080p don't lagg, torch work, camera take a picture and recording 1080p without lag. Recent apps laggy. I have little bug with lock becouse when I press Power button the screen blink :P Great minimalistic Lollipop Rom :D

Sorry For English
[Samsung Galaxy Nexus] seriousia:
Video records without any green(?) lines?
[Samsung Galaxy Nexus] Tolazace:
With green lines but is very smooth :)
[Samsung Galaxy Nexus] theBlackEnd:
I've uploaded TB#5 here on XDA. Check the download section of this thread :)

Thank you very much :)

Yup. There's still a green line on the left of the video.
[Samsung Galaxy Nexus] aliesz:
I tried the latest build on my maguro which has vyl00m emmc chip and yes it works for me too, with slimlp beta full gapps its boot takes long time( about 16 min) but there was not any problem except the known issues remained, also There is still some phonic glitches.
[Samsung Galaxy Nexus] Nautilus74:
Little OT:

With any Lollipop rom, on stock Browser, i have only local bookmarks....

How I resolve it?
[Samsung Galaxy Nexus] Pjodor:
If I want to try bsmittys kernel, do I use asop or cm version with this rom?
[Samsung Galaxy Nexus] massoudsh:
deleted...
[Samsung Galaxy Nexus] theBlackEnd:
I've tested FML version and it works fine, I can't say about CM. I guess audio should stop working.
[Samsung Galaxy Nexus] massoudsh:
oh sorry....you are right. excuse me.:o
[Samsung Galaxy Nexus] dr_kalel:
Rom is smooth but recent app still lag
[Samsung Galaxy Nexus] theBlackEnd:
Give a try to last build, it looks smoother to me.

Test build 6 is Up now. Changelog:

- F2FS support has been added (data and cache), report if it works, please. I'm still on ext4.

- New open-source bin to get camera calibration file (thanks to Ziyan), non-PIE support has been disabled;

- Built with SaberMod 4.8.5 [01.15]. C++11, -O3 and strict aliasing have been enabled (thanks to MWisBest);

- Synced up with official repos;

- Minor changes;
[Samsung Galaxy Nexus] smartAgent47:
I installed the TB6 build.

It works gud but google play services error is frequent !!

Hope it fixes in the next build
[Samsung Galaxy Nexus] aliesz:
I think if you update google play services and other google apps it will be solved.
[Samsung Galaxy Nexus] dr_kalel:
I can't send any sms over 160 words. Please fix it
[Samsung Galaxy Nexus] pilotn:
Good job, dirty flash over SlimKat 9 official and everything seems perfect, great!

I don't use it as daily phone and don't have any sim inside, but for all I tested till now there is no problem using this Rom.

Thanks again, good Rom and great support
[Samsung Galaxy Nexus] Castro27:
Everything is running great except for some camera crashes, sometimes on the app itself and others while using torch. Anyway, my question is: did anyone manage to get trusted faces working? Here it crashes everytime it calls the camera
[Samsung Galaxy Nexus] pilotn:
All my apps are updated but I still have the same problem
[Samsung Galaxy Nexus] Castro27:
This is probably due to the modified DPI. I think the only way to fix this is to use the default 320 DPI.
[Samsung Galaxy Nexus] pilotn:
I'm having this problem with 320 DPI
[Samsung Galaxy Nexus] theBlackEnd:
Can you attach a logcat of the error? I'll look into this as soon as I can. I'm still busy with school and finals .-.

Thanks for testing. No surprise, thought. SlimROM gapps are multi-DPI compatible, but that was worth a try.

Since every Lollipop ROM is affected by this I assume that is an issue due to play services itself.

If anybody wants to give this a try and report if it works that would be of help.

Edit: Gapps have been updated by dankoman, I'll try them this evening, I guess.

Edit 2: Is F2FS working fine, guys?
[Samsung Galaxy Nexus] Pjodor:
Play service fc for me just after I have rebooted the phone. Have three or four fc's and efter that it works with no problem. Hadn't tested Netflix and streaming from Google play though.
[Samsung Galaxy Nexus] DelsaZaraki:
I've a little issue after the latest update, with tb6 i've no root acces even if it says that i've the root. For example titanium backup or trickster mod doesn't work because they can't have root acces. What can i do to fix this?
[Samsung Galaxy Nexus] Airlibik:
have you enabled root to apps and adb from developer option?
[Samsung Galaxy Nexus] alboz83:
I tried slimlp and confirm that root don't work. I flashed Supersu

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] DelsaZaraki:
yes i've enabled it in developer option, but now i think that maybe the rom doesn't allow root access. So i'll just wait for other update :) :)
[Samsung Galaxy Nexus] Airlibik:
install super su zip from recovery and everything will work.
[Samsung Galaxy Nexus] DelsaZaraki:
I've unrooted and rooted again and now it works
[Samsung Galaxy Nexus] pilotn:
Lp Gapps from slimteam are back
[Samsung Galaxy Nexus] theBlackEnd:
New build is up. Changelog:

TB 6 >> Build 7:

- Enabled F2FS kernel support;

- Switched from SELinux Permissive to Enforcing (thanks to [MENTION=4986658]freshgiammi[/MENTION]);

- Darkened UI a bit (Dark Material) [boot to reduce screen burn-in, notifications, settings, powermenu...] (thanks to [MENTION=2095315]ezio84[/MENTION]);

- Added RRO Themes support (needs testing);

- Some Updates to RIL [long text sending fix, ...];

- Brought back some audio changes to the kernel. Following MWisBest, this will allow bsmitty83 to build just a version of his kernel. Use CM version until he uploads a new build;

- Added pngquant PNG compression to lower ROM zip size;

- Synced up with official, minor changes;

Keep using SuperSU guys, I still can't get built-in Superuser working. :silly:
[Samsung Galaxy Nexus] alboz83:
Thanks, i love Slim rom and now i'm running on your slimkat 4.4.4. I tried SlimLP and i can say that is very fast, more then cm12 and fml. But i'm waiting to a full fix for camera. The good thing in the SlimLP is that the 1080p record are smooth, while in cm12 not.
[Samsung Galaxy Nexus] netreign:
how fix this... google play services has stopped. cant play video on youtube... on Facebook... hw+ not work
[Samsung Galaxy Nexus] theBlackEnd:
Fix for Google Play Services crashes is in previous page of this thread. :rolleyes:

YouTube, Facebook and HW decoding work fine here. If video decoding stops working after google play services crash you just have to restart your app.
[Samsung Galaxy Nexus] Rd. Vortex:
Is anyone else having problems with build 7 not booting at all? When I try to boot the phone it simply gets stuck on the Google logo and does nothing else. I dirty flashed over build 6 which would start just fine.
[Samsung Galaxy Nexus] phaleg:
Can you install or move apps to external SD with that?
[Samsung Galaxy Nexus] zzpianoman:
Galaxy Nexus does not have external SD card.
[Samsung Galaxy Nexus] hubik.j:
I have the same issue. Clean flash with f2fs /data and /cache. Everything wiped including the internal storage. Build #7, normal Slim gapps, supersu.

Edit: I waited 30 minutes stuck on the Google logo. I had to pull out the battery to reboot.
[Samsung Galaxy Nexus] phaleg:
Sorry, I misposted... I am following SlimLP for me (note3) and for my wife (Maguro) :D
[Samsung Galaxy Nexus] hubik.j:
I solved the problem with stuck boot on Google logo. I just flashed the bsmitty83 LP kernel (cm version) and it works now. Otherwise same setup as I wrote before, just the kernel on top of that.
[Samsung Galaxy Nexus] theBlackEnd:
Are you on f2fs?

Was Test build 6 working for you?

What's your eMMC chip guys?

Could somebody pull a kmsg log?
[Samsung Galaxy Nexus] Rd. Vortex:
I'm using ext4 and my eMMC is VYL00M. If I flash bsmitty83's Lollipop CM kernel then build 7 boots just fine just like it did for hubik.j.
[Samsung Galaxy Nexus] hubik.j:
Build 7 is my first. I was a Slim virgin :D

VYL00M

Log is zipped and attached (It was too big).
[Samsung Galaxy Nexus] hubik.j:
I just want to clarify what is my current status:

After flashing bsmitty83's LP CM kernel, I was able to get past the Google logo. It booted into setup wizard after about 10 minutes. But during the setup, there is a lot of pop-ups about various services stopping (not only Google Play services), the screen blacks out, everything crashes. Up to a point, where it is no longer possible to click on OK on the pop-ups and the phone just freezes. I had to pull the battery to reboot multiple times, until I was able to get through "most" of the setup. But still no luck with completing the setup and booting to the launcher.
[Samsung Galaxy Nexus] pilotn:
I don't know if is this Rom or is a lollipop feature..... Multitasking is almost impossible, if I put an app in background using home button then I try to reopen, I understand that app has been closed. Even nova launcher reload almost every time I go back to desktop. There is more or less 150mb of memory free, but the behaviour is always the same... Any idea?
[Samsung Galaxy Nexus] hubik.j:
Another minor problem that you might want to look into is this:

When I flash the ROM in recovery, there is the huge ASCII-art Slim logo. And then:

"Format and Mount System. Mount Data..."

"unmount of /system failed; no such volume"

"Symlinks and permissions..."

...

"script succeeded: result was [/system]"

It probably tries to unmount something, that is already unmounted. I think it does not affect the flashing.
[Samsung Galaxy Nexus] theBlackEnd:
Thank you. That log is of your KK ROM, though.

That's quite strange, I never had such problem, also, nobody reported it before. I'll wipe data once I fix boot to test, but I guess you forgot to wipe cache or just installed an old gapps package.

Once I fix boot for maguros with VYL00M chip I'll upload build 7v2, with tuned low memory killer values. Let me know, please.

That's ok, it doesn't affect flash result. However, I'll fix that.

---

Boot on VYL00M maguros:

Well, some of the latest updates (to the distro) broke #pragma GCC support in my build machine, this something breaks the fix to the fix (LOL!) to eMMC, which leads to bootloop.

I have to get that working to build Build#7v2. If Build #7 doesn't boot use bsmitty's CM kernel or test build 6.
[Samsung Galaxy Nexus] Pjodor:
Anyone know what the star is in the notification? Never seen it before, I had a circle with a line before also that I have never seen either.
[Samsung Galaxy Nexus] hubik.j:
I am not an Android developer nor a Linux expert, but how can it be from KK? I am coming from KK, but I wiped everything, including the internal storage. And it was also wiped by the change to f2fs.

I already wrote about all the wiping and I am sure I use the correct gapps. I settled on mini version:

http://www.slimroms.net/index.php/d...-mini-gapps-beta-5-0-x-build-0-x-20150131-459

---------- Post added at 03:01 PM ---------- Previous post was at 02:59 PM ----------

Priority mode: http://fieldguide.gizmodo.com/16-things-you-can-do-in-android-lollipop-that-you-could-1659628014 Third item.
[Samsung Galaxy Nexus] theBlackEnd:
That's just priority notifications. Check this.

Well, I guess you booted your device more than once since bootloop. according to the date reported in the log, you've pulled that log during bootloop.

My bad, I thought you'd pulled that log after a reboot, so that adb command was meant to get kmesg PRIOR to reboot.

Linux version 3.0.101-omnirom-g9aa418f (deadmetaler@dedmetaler-System-Product-Name) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Jan 21 10:29:53 MSK 2015

That's the second line of that log. For sure, that's not related to SlimLP.
[Samsung Galaxy Nexus] hubik.j:
I did try to boot. Then you wanted the kmsg, so I booted to recovery and used the adb command you provided. But it did not give me any log. So I rebooted the recovery and it worked finally. Just tell me the exact steps I should do, including reboots and boots. I suggest:

Wipe everything, set /data and /cache to f2fs

Reboot recovery

Upload ROM, Gapps, SuperSU, Kernel over MTP

Flash ROM, Gapps, SuperSU, Kernel

And now what? Wipe Cache again? Try to boot? Or just reboot recovery and get kmsg? Or no reboot at all and get kmsg?
[Samsung Galaxy Nexus] theBlackEnd:
That's right, but you don't need to wipe cache twice. Flash -> Boot -> Bootloop (?) -> Recovery -> Pull. You could also try to get kmsg log during bootloop (adb shell su -c dmesg > dmesg.log), but that won't work if adb is not started on device-side.

However, I think I found what is not working. Thanks anyway :)

Edit: Factory reset instead of full wipe should be a better choice.

Also, flashing a working kernel won't let you pull a log of the non working one.
[Samsung Galaxy Nexus] hubik.j:
So I tried it and it was like this: Flash -> Boot -> Crash&Freeze during Setup Wizard -> Pull Battery -> Recovery -> cat last_kmsg

And this is what I received:

cat: can't open '/proc/last_kmsg': No such file or directory

So I tried to reboot recovery and cat last_kmsg again and I received log which contains the line you did not like the first time...
[Samsung Galaxy Nexus] bsmitty83:
Your pulling the kmsg from the recovery kernel . when you pull the battery you wipe out the last kmsg from the ROM , the only way to get it is if the system reboots on its own. If you pull the battery or otherwise power off the device , there will be no last kmsg
[Samsung Galaxy Nexus] hubik.j:
But how do I get to recovery to be able to use adb to read the kmsg? Even if it would reboot, it would not go to recovery on its own. :confused:
[Samsung Galaxy Nexus] bsmitty83:
You don't , you let the phone reboot , when the ROM starts back up , you adb pull proc/last_kmsg . if you enter recovery , you will get the kmsg from the boot up to recovery , which you don't want . so forget about recovery and pull it from the ROM
[Samsung Galaxy Nexus] hubik.j:
Update on my progress with kmsg:

I used your helpful guidance and now I finally understand it quite well. I tried to use the "stock" kernel which is in the ROM. I found out, that adb is somewhat working when it is stuck on the Google logo - the device is listed with "adb devices" and I am able to pull the last_kmsg. The issue is, that the phone will not restart on its own, so the last_kmsg still contains log from the recovery.

Unfortunately I am not able to read the current log with "adb shell su -c dmesg > dmesg.log" because I get "- exec '/system/bin/sh' failed: No such file or directory (2) -". Any suggestions?
[Samsung Galaxy Nexus] frickinjerms:
Perhaps try

adb reboot

then when you get back to adb working again, try to pull that last_kmsg?
[Samsung Galaxy Nexus] hubik.j:
I already installed another ROM - I needed the phone... Maybe Rd. Vortex can try it? He has the same issue.
[Samsung Galaxy Nexus] theBlackEnd:
Thank you all, guys ^^

----

Build 7v2 is up and brings a few fixes to build 7.

Changelog: 7 => 7v2

- Built-in Superuser is now working;

- SettingsUI themed Dark Material, too;

- Tuned Low Memory Killer values. Thanks to Ziyan;

If you have VYL00M eMMC chip, please, report if v2 boots on your device. If it doesn't, use bsmitty's CM kernel or revert to TB6.

You can check your eMMC chip by typing from shell:

adb shell cat /sys/class/block/mmcblk0/device/name
[Samsung Galaxy Nexus] alboz83:
Thanks, i was with build 7 but i change the rom an hour ago because i had a Google Play Services FC and it was a bit slow. Now i wait a feedback for 7v2 :)
[Samsung Galaxy Nexus] Rd. Vortex:
Still not booting with VYL00M. Attached last_kmsg. Not sure if it's done correctly though since I've never had to pull kmsg from any device. Tried to boot -> got stuck -> adb reboot recovery -> then took kmsg.
[Samsung Galaxy Nexus] zieruchan:
What ? I'm using the same chip like you, even on v7 1st build. It's working fine no problem.

Maybe because I'm using bsmity kernel.

For developer : Can we get full black theme like liquidsmooth LP, because the only reason I like slimrom is The Real Dark Slim :)
[Samsung Galaxy Nexus] hubik.j:
That is the reason.
[Samsung Galaxy Nexus] Pjodor:
How can I see if I have vyl00m or not?
[Samsung Galaxy Nexus] xxSAKISxx:
sorry mate but you read the thread at all? Your answer is 6 posts above yours.
[Samsung Galaxy Nexus] alboz83:
Google Play Services work well in the last build? FC or not?
[Samsung Galaxy Nexus] hubik.j:
http://wiki.cyanogenmod.org/w/EMMC_Bugs#How_do_I_check_my_device.27s_eMMC_details.3F
[Samsung Galaxy Nexus] yatskanich.sasha:
Galaxy Nexus. BUILD_7v2 not booting, is freezing on google logo

Maybe i doing something wrong?

my steps:

1 wipe data/factory reset

2 wipe cache partition

3 mounts and storage -> format system

3 advanced -> wipe dalvik cache
[Samsung Galaxy Nexus] Nautilus74:
BUILD_7v2 on my VYL00M gnex don't boot in f2fs (CACHE & DATA) if I leave internal kernel.....

....but it works if I flash one of bSmitty's kernels! :) (anykernel version)
[Samsung Galaxy Nexus] sergialess:
Same here, 7v2 does not boot with my VYL00M.

Experiences with v7.2 + SmittyL R8:

- Faster than other LP roms.

- Camera not working for me on this buid/combo.

- Not able to finish phone calls :S

- Constant google play services errors.

- Absurd lag sometimes (ART?).

Looking forward Android 5.1 and better memory management...

Thanks.