yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] theBlackEnd:
In short: nope. All these Lollipop ROMs are really similar atm, adding LS themes to SlimLP would be really unfair and would mean getting a copy of LS as result.

Also, I'm trying to keep this closer to official SlimLP as possible. Good new is that SlimLP officially added RRO themes support. If everything goes well, next build will have full RRO support.

Fix for this is in latest pages of the thread. Anyway, I will rename drm dirs myself in next build. This fixed all Google Play Services FC for me.

Camera works here. I'm on stock kernel, though. Could be a SELinux policy conflict with bsmitty's kernel (?)

I guess lag is due to Google Play Services, but I'm not sure. Does it happen with data/wifi turned off? I had a similar problem on KitKat, too.

What do you mean by "not able to finish phone calls" ?

----

Thank you all for your patience and feedbacks.

I'm sorry for the late reply, I'm really busy with finals. I still have three exams this month .-.

Anyway, I've got a build with a different kernel toolchain, I can't test it as I have a different eMMC chip, though.

I'm not sure this will fix the problem as I've used the same toolchain for builds #4 to 7v2, so I'm not going to upload new build/boot.img here, but I've got a few other ideas.

If anybody wants to help with tests, PM me or post bellow. Thank you in advance.

PS: [MENTION=4608636]bsmitty83[/MENTION], may I ask you which toolchain are you using? If I remember correctly, you're still on 4.7.x, right?
[Samsung Galaxy Nexus] sergialess:
First of all, thank you for your effort and prompt response.

When you are doing a call and you finish talking, you usually click the "phone" icon to end the phone call. Ok... that button wasn't responding to the click. It's like if the UI was blocked or something, and I was not able to end the call (stupid situation, btw).
[Samsung Galaxy Nexus] bsmitty83:
Saber Mod 4.9 is what I've been using . 4.8 is the troublemaker for kernels , always has been for whatever reason.
[Samsung Galaxy Nexus] theBlackEnd:
Thank you.

Meh, I've been using Linaro 4.9.3 since build #2. Result: #2, #3, #7, #7v2 are not booting on VYL00M.

MWisBest and Ziyan had to push O0 to drivers/mmc/quirks.c to fix boot on that chip, but seems that's not working here.

Anyway, good to know, I made a build with SM toolchain this morning, maybe it's worth a try.
[Samsung Galaxy Nexus] Nautilus74:
On my VYL00M GNEX your last build starts if I flash smitty's kernel, in f2fs too....

The great problem is that remains continuous errors of play services
[Samsung Galaxy Nexus] theBlackEnd:
New build is up. Changelog Build 7v2 >> 8:

- Workaround for Google Play Services FC. You need to wipe /system before updating;

- Revert Dark Material UI;

- Added full RRO Themes support;

- Minor changes;

This looks like the smoothest build so far to me.

Edit: This build boots on devices with VYL00M eMMC chip.
[Samsung Galaxy Nexus] Rd. Vortex:
Latest build boots on VYL00M even with the included kernel. Thanks!
[Samsung Galaxy Nexus] sergialess:
Yesterday I was a bit dissappointed on my phone's behavior, but today, with the new build and the smittyl r9 I've changed my mind.

- It feels definitively snappier!.

- Camera working great!.

- I can end phone calls.

- No Google Play Services errors.

- Boots OK with the stock kernel.

Hell yeah, this is becoming interesting!!!.
[Samsung Galaxy Nexus] karofus:
.

in the last build "8" is there any changes on the camera and torch? At the last build before "7" my camera and torch working perfect, but after instaling apps like viber, skype , google drive and docs , and Google Camera , the torch and camera apps start crashing after a day... i'm with stock kernel. Do i doing something wrong?
[Samsung Galaxy Nexus] pilotn:
Everything is smooth and fast for the moment.

Only issue for now is that I can't use SuperSU, tried playstore installation and zip via recovery in with same result: bootloop.
[Samsung Galaxy Nexus] Nautilus74:
SuperSU 2.45 works fine here.....
[Samsung Galaxy Nexus] pilotn:
The same I'm trying to use...
[Samsung Galaxy Nexus] renz427:
Is it EXT4/F2fs supported. sorry I'm noob at this. how can I install this via cwm recovery?
[Samsung Galaxy Nexus] renz427:
How did you make it work sir? 'cause mine here have also that supersu problem :(
[Samsung Galaxy Nexus] Nautilus74:
I have not done anything in particular ....

The only thing I can say is that I left off the integrated superuser (from developer options)

and flashed SuperSU from recovery as the last thing!
[Samsung Galaxy Nexus] Koplinjp:
I too flashed SuperSU 2.45 like you did, but apps that need root... nothing... I did not even get the pop up question from SuperSU to "allow" or "deny".

One more thing... I installed full gaps with this rom. I installed avast and i wanted to install rooted Anti-Thief but it tells me that there is not enough space in system partition. Is this because i need SuperSU to work properly? Does anyone tried this?
[Samsung Galaxy Nexus] Nautilus74:
nope, it's because you've used gapps perhaps too large....
[Samsung Galaxy Nexus] eternal70:
A little bit off topic, can you guys use RRO ? I got errors on Layers app and i read in the g+ forum it's rom related
[Samsung Galaxy Nexus] theBlackEnd:
Nope, you're just out of space in /system partition. Try using smaller gapps package. Unfortunately our device has small system partition and ROM cannot be shrunk any more.

Meh, Layers app is working fine here, I've successfully installed a overlay. Which errors are you talking about?

---

Anybody else experiencing bootloops after flashing SuperSU?

Could you be provide more details [dirty\clean flash, built-in superuser, order of flashing - i.e. ROM, gapps, kernel (?), su] and attach a logcat?
[Samsung Galaxy Nexus] eternal70:
[MENTION=5773568]theBlackEnd[/MENTION] this. Hmm, maybe im was wrong, what folder did you put the apk ?
[Samsung Galaxy Nexus] theBlackEnd:
Oh, lol. THAT error. I totally forgot about it, I'm sorry.

Looks like Layers app doesn't like refresh button being pressed. I put all apks in that folder (../Other Overlays) and had to restart the app to reload the overlays list.

There are many users reporting this bug on different ROMs and devices, so I guess it's app related.
[Samsung Galaxy Nexus] ashish__s:
No audio with R9 - FML

I'm into bsmittys kernels so I flashed R9 - FML and everything is great except no audio coming through. not in notifications. not in google play music. are we supposed to use R9 CM? is there something i'm missing?

thanks for the great work!

edit - flashing R9-CM brought back audio. does it matter whether we use CM or FML?
[Samsung Galaxy Nexus] bsmitty83:
FML kernel is for fml , cm kernel works for the rest as all the other ROMs use ziyans repos . once a new fml build is released it will change , as MW synced his ROMs audio with cm's , so I will only have to make one kernel .
[Samsung Galaxy Nexus] ashish__s:
understood! thanks for your help and work! :)
[Samsung Galaxy Nexus] zieruchan:
Bro, Recent apps is laggy. I think cm already fix this

And headset button isn't working
[Samsung Galaxy Nexus] ruben2000de:
Wow. I came from FML and switched to SlimLP#8

This Build has great Performance(and a few great Slim Features), even with Stock-kernel. (will try smitty's next days.)

Huge thanks for That Rom ;-*
[Samsung Galaxy Nexus] sergialess:
Same here. Stock kernel is working great. Great battery life and performance. I know SmittyL is a powerful, full-featured kernel, and I'll stick with it when I get bored of the stock xDDDD.
[Samsung Galaxy Nexus] hubik.j:
Did you wipe or just dirty flashed? Are you using f2fs? I am considering the switch as well. Please post feedback as well once you try bsmitty83's kenrel. I would appreciate the same from [MENTION=4815527]sergialess[/MENTION]
[Samsung Galaxy Nexus] sergialess:
[MENTION=4623343]hubik.j[/MENTION]:

I have /cache and /data in F2FS.

Rom and stock kernel worked out of the box.

First time I wiped cache, system and data.

Using latest slim gapps (smallest one).

I'm talking about Build #8 exclusively.
[Samsung Galaxy Nexus] Nautilus74:
your emmc chips?
[Samsung Galaxy Nexus] sergialess:
VYL00M

01/2012

fw rev.: 0x25
[Samsung Galaxy Nexus] Nautilus74:
strange.... my gnex (same mem chips) doesn't want start......

I had to use smitty's kernel with modified fstab....
[Samsung Galaxy Nexus] sergialess:
Sad to hear that...

That also happened to me before #7.2. I had to flash a modified version of SmityL. Since #7.2, it is booting ok with the stock kernel.

My recovery is TWRP 2.8.0.0 (with f2fs support).
[Samsung Galaxy Nexus] phaleg:
Looking forward to install on my wife's nexus ^^

is it a bad sign that I don't read updates on this project recently?
[Samsung Galaxy Nexus] theBlackEnd:
In short, I've got a final on Thursday (second part of mathematical analysis - I don't know if that's a real subject in english).

Also, I've been trying to use a slightly updated domx on my free time, but that will take some time to get it working.

Torch, video decoding and camera (? I've not even tested last build .-.) are broken atm.

"Is this worth it?" Who knows, I hope so. At least I'm learning something about our device\domx.

Anyway, I think I will revert to old domx to build B#9. I've got a few fixes (recents lag, ...) and a few ideas\commits to push and test.
[Samsung Galaxy Nexus] fearlessaryan:
All the Best for ur Exam. :o
[Samsung Galaxy Nexus] phaleg:
What is exactly domx?
[Samsung Galaxy Nexus] Reptilez_DK:
Very nice ROM ! Oh why did I wait so long before trying this. ;)

Do you have a local_manifest file, you would care to share ?

Never mind. :)
[Samsung Galaxy Nexus] theBlackEnd:
DOMX is the software interface to our hardware multimedia capabilities. Check this for more.

If you still need it PM me.

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

Here we go, Build #9 is up.

Changelog:

- Switch from JEMalloc to DLMalloc (memory allocation);

- Built-in ART now includes changes needed by XPosed (*);

- Recents lag fix;

- Some fixes here and there;

- Synced up with SlimROMs repos (improvements, updates to translations\built-in apps, ...);

Xposed is NOT included in this ROM.

(*) This means you can safely remove these files from xposed-arm-*.zip

- system/bin/dex2oat
- system/bin/oatdump
- system/bin/patchoat
- system/lib/libart-compiler.so
- system/lib/libart-disassembler.so
- system/lib/libart.so
- system/lib/libsigchain.so

I'm not going to threat bootloops or whatever as bugs if you haven't removed these files from Xposed zip before flashing it, since Rovo89 is compiling ART from official source and a few commits that are included in our ART are missing.

EDIT: I've uploaded a ready-to-flash package for this ROM. Check download section.

Please, report if multitasking handles better. It looks similar to KK to me now.
[Samsung Galaxy Nexus] alboz83:
Thanks for new build, green line in video recorder are still there? I want to left Kitkat for Lollipop, but i need a full and always working video/camera
[Samsung Galaxy Nexus] ashish__s:
stuck on white Google text screen :/

tried dirty flashing from build 8 and got stuck in white Google text screen.

decided to try and clean flash but still stuck at white Google text screen.

what should i do?

--edit--

hubik.j's idea fixed it. thank you very much kind person!

--edit2--

- adb shell cat /sys/class/block/mmcblk0/device/name command spits out "VYL00M"

- can't upload kmsg because new member - link: https://drive.google.com/file/d/0BxEtYACls7xCLUUxNGtuTzMxam8/view?usp=sharing

hope that helps!
[Samsung Galaxy Nexus] hubik.j:
Last time there was this problem, it was kernel related. You can try flashing bsmitty's kernel and see if it resolves the problem.

If you want to help theBlackEnd with development of this ROM, then do this before flashing the bsmitty's kernel:

adb shell cat /sys/class/block/mmcblk0/device/name

This shows you the eMMC chip version.

When you are stuck on the Google logo and adb is working then reboot the device:

adb reboot

When adb works again:

adb pull proc/last_kmsg

This way you get the kernel log - post it here.
[Samsung Galaxy Nexus] big_zein:
Hi, my gnex also get stuck on the Google logo and i'm trying hubik.j recommendation.

Here's my result.

D:\Master\NRT\data>adb shell cat /sys/class/block/mmcblk0/device/name
VYL00M

D:\Master\NRT\data>

I cant find another way to post my log since char limit are 30.000, and i cant upload any attachment because i'm a new member...

here's my log on my dropbox folder

bit.ly/1zW33re

there are 2 files because i tried it 2 times

Hope it helps.

Flashing another kernel like full auto does fix this problem.
[Samsung Galaxy Nexus] hubik.j:
VYL00M is known to cause issues (I have the same). The larger last_kmsg file without the underscore at the end is the correct one. theBlackEnd will have to look into it as I am not a developer.
[Samsung Galaxy Nexus] ashish__s:
unable to install apps

Error

"App_name" could not be downloaded due to an error. (942)

I have installed build 9 of slimLP and Slim mini gapps with bsmitty kernel. Thank you for your help!
[Samsung Galaxy Nexus] hubik.j:
Try to force stop and clear cache for these apps: Google Play Services, Google Play Store, Google Services Framework

If it does not help, try to reflash gapps and wipe cache in recovery.
[Samsung Galaxy Nexus] ashish__s:
both methods failed :/ i'm getting the same error
[T-Mobile Galaxy Note 4 Android Development] turilo:
yep

Here is the csc/Data fix that I've created to get these international roms Network to work on our devices. Thought I share for those wanting to test or port any Roms yourself. This will give you the N910W8 LTE icon rather then Tmobiles. Edit the build prop to acquire your desired LTE icon. Enjoy, as I think I'm done on Porting anything else, no time as I need to take care of my son but will keep Xnote updated as it comes from original dev [MENTION=4443870]soloilmeglio[/MENTION] and [MENTION=4937312]xentrix[/MENTION]

https://mega.co.nz/#!mYA0TZAa!NVYLzK8ZoiMxRXWlu5dDeMZGCOOnZX40lwjfZEQUFe4
[T-Mobile Galaxy Note 4 Android Development] Rob the plumber:
I'm probably an idiot, but where do i download it here?

Thanks for your work!
[T-Mobile Galaxy Note 4 Android Development] JodyBreeze901:
Try to view the page in Landscape mode......the download button may appear then.
[T-Mobile Galaxy Note 4 Android Development] turilo:
View it in desktop mode then hit the download arrow. Not sure why my link opens up that way I'll try and fix it
[T-Mobile Galaxy Note 4 Android Development] mrimage:
+1 cant find dl button
[T-Mobile Galaxy Note 4 Android Development] Nvrenough:
whats the gmail fix dudes :(
[T-Mobile Galaxy Note 4 Android Development] mgbotoe:
Oo a second port. Welcome welcome ^.^
[T-Mobile Galaxy Note 4 Android Development] turilo:
Go in dolphin settings and change android to desktop and reload or reopen link
[T-Mobile Galaxy Note 4 Android Development] Rob the plumber:
Thanks guys.
[T-Mobile Galaxy Note 4 Android Development] Speed72584:
Download google drive for download
[T-Mobile Galaxy Note 4 Android Development] willjohnson:
Awesome. Thanks for releasing this. Good work. :)
[T-Mobile Galaxy Note 4 Android Development] turilo:
Keep me posted if any issues :)
[T-Mobile Galaxy Note 4 Android Development] Nvrenough:
Can't get Gmail to sync other then that awesomeness
[T-Mobile Galaxy Note 4 Android Development] Misterjunky:
re: congratulations

Congratulations on your new thread and the excellent port of the x-note rom.

This x-note rom in my personal opinion has more extra additional features

and options than any other Note 4 rom I have ever found or flashed so far.

The best part is that all the extra additional options & features

it has are all working properly (unlike xposed - wanam).

With this rom there is hardly any need for xposed and wanam.

I just got done flashing it and it's working just fine... I did have to download

and install the "com.google.android.gms-6.5.99 Google service" apk which

you suggested to do to get the gmail working and it works just fine now.

Hopefully you will be updating this x-note port with even more additional

mods, themes and other goodies in the near future.

What I would love to see is for some themer to make a theme for this x-note

port which is not simply inverse or different shades of black or dark screens.

The kind of theme I am waiting for is something similar to the theme which BoBCatRoM

has developed for the Note 3 phones in the international development forum.

Here is the link to his theme thread in the note 3 international forum in case

someone wants to check it out:

http://xdaforums.com/showthread.php?t=2535240

Have a great day, and congratulations again on your new thread.
[T-Mobile Galaxy Note 4 Android Development] Nvrenough:
Great stuff got it working wonderful
[T-Mobile Galaxy Note 4 Android Development] mgbotoe:
i think the only permission he has is to port, not to use as base

There's quite a difference between the two
[T-Mobile Galaxy Note 4 Android Development] Tiffany84:
Great job turilo
[T-Mobile Galaxy Note 4 Android Development] mocsab:
Awesome - THANKS!
[T-Mobile Galaxy Note 4 Android Development] ejdavis:
Thanks
[AT&T Samsung Galaxy S 5] harry_seaward:
My girlfriend has an AT&T Galaxy S5. She's on Android version 4.4.2 (baseband version G900AUCU2AND3, build number KOT49H.G900AUCU2AND3). She's rooted with towelroot.

She's very keen on updating to Lollipop. The reason for this is that she's a very avid photographer and takes many shots on her phone. She is REALLY interested in trying out the RAW image processing.

I'd just like to know if she can update and keep root. So if anyone could help me out here or point me in the right direction since I don't know my way around this forum, that would be fantastic. Thank you very much.
[AT&T Samsung Galaxy S 5] Nucleartx:
Once we get a leak or the actual release, we won't know what Lollipop will have in store for the Dev's root wise. Everything now is speculative though the International version(G900F) has had good success with root and Lollipop.
[AT&T Samsung Galaxy S 5] harry_seaward:
I'm sorry, I just saw something after a quick Google that led to believe there *was* a release. So you're saying as of now, there's no Lollipop on G900, root or not?
[AT&T Samsung Galaxy S 5] Nucleartx:
The g900f, which is the over seas version, has had a limited release with lollipop. AT&T version, G900A, does not have lollipop yet.
[AT&T Samsung Galaxy S 5] cstayton:
No AT&T release as of yet, and even when (IF) it does drop and IF root is obtainable it is a longshot whether or not we will have SafeStrap or any other type of custom recovery :(:(
[T-Mobile, Samsung Galaxy SIII] V@no:
Hello.

I'm trying root a T999L model. I've followed instructions from [HOWTO] [ROOT] No Tripping Flash Counter [Tmobile / Wind / Mobilicity / Videotron]

The installation seems to went well, SuperSU is installed and some of the root functions work, BusyBox installs fine too, however I'm unable mount / as RW via RootExplorer and also unable activate root explorer in ES Explorer (/system mounts RW just fine though)

On top of that TWRP 2.8.1.0 unable to mount any partitions at all.

I've tried several times reinstall stock roms, root, etc nothing seems to help.

Any suggestions?

Thank you.

P.S.

and I just learned that IMEI on label doesn't match IMEI in about->status... how bad am I screwed now?
[T-Mobile, Samsung Galaxy SIII] canodroid15:
Do you have data & cell service? If so your good on imei, what ROM are you running, did you flash a kernel?
[T-Mobile, Samsung Galaxy SIII] V@no:
Yes, I do have service.

Running all stock MK4/NC1

No custom kernel

All started after the phone failed to get unlocked with www.fastgsm.com (first tried USB method, it failed, then tried alternative via IMEI, it also failed, and then I learned that IMEI I gave them was the one from status screen not from label, perhaps that's the reason)

In the process of attempting unlock the phone I've tried flash an 4.1.2 baseband as suggested by fastgsm.com suppport, after flashing it the status would show unknown baseband. So reflashing stock images fixed that.
[T-Mobile, Samsung Galaxy SIII] canodroid15:
OK have you disabled Knox?
[T-Mobile, Samsung Galaxy SIII] V@no:
My understanding root66 disables it. But anyhow, SuperSU didn't prompt about knox either, so I'd assume it's disabled.
[T-Mobile, Samsung Galaxy SIII] canodroid15:
You may need to flash an insecure kernel, also I used titanium backup to freeze everything in system that said Knox in it, if that doesn't work you could just flash cm11 or any ROM for that matter and your problem will cease, if you want a stock rooted ROM with init'd & bisybox no Knox im sure I could find a link for you
[T-Mobile, Samsung Galaxy SIII] V@no:
Well, that's the problem I can't flash anything because TWRP doesn't work (it can't mount any partitions, including sdcard)
[T-Mobile, Samsung Galaxy SIII] canodroid15:
Try cwm just not 6.0.4.7 any other 6.0.4.3 & up is good. You're not the only one having this problem with twrp. After you flash a ROM with cwm you can go back to twrp & the mount problem should be gone, my PC is down so I'm on my phone, hence why it takes a min 4 me to reply. I don't have the t999l but I'm familiar with it I have d2att sgh-i747. I use tmo ROMs on my phone so I know a little bout t999 yours is 3g only I believe, isn't it?

---------- Post added at 01:28 AM ---------- Previous post was at 01:20 AM ----------

Also b4 going any further, you should do a nvdata backup thru terminal emulator its easy to do :

Open terminal

Type su hit enter

Then type reboot nvbackup

Phone will reboot & your imei & baseband will be backed up!

If you ever lose it open terminal

Type su hit enter

Type reboot nvrestore

It will save your life man really
[Fire TV General] Neo3D:
I've been having audio sync issues with quite a few of my files, I'd guess about 20% of them. The funny thing is that it wasn't the huge 30gb+ MKV files that were giving me trouble...which is what you'd guess. I have a lot of files and it was hard to tell which one was having issues and why.

I searched on here and http://forum.kodi.tv/ and found a solution.

I'm posting it here to save future users time if they experience the same issue. And to contribute back as others have been very helpful to me.

All you have to do is TURN OFF all hardware acceleration features:

SYSTEM > VIDEO > ACCELERATION > DECODING METHOD SOFTWARE

SYSTEM > VIDEO > ACCELERATION > Allow multi threaded software decoding > ENABLE

This solution works great for me! YMMV.

If it works for you, then please post. If it doesn't, then please post.

I hope the hardware acceleration bugs are worked out by the time the public version of Kodi is released.
[HTC Desire 510] karmasblade:
I rooted my new Desire 510 today and I want to change the DPI. I did some googling and couldn't find how to get S-Off on the Desire 510. It says S-ON when I go into fastboot. Anyone know how to get S-Off?
[HTC Desire 510] huggs:
You have to flash a kernel for your carrier with write protection removed. Look in Desire 510/Android Develooment for the kernel that matches your carrier, download it, back up your stock kernel (boot img) or download your stock kernel from one of the threads in Desire 510 Android Development, flash the write protection removed kernel using ADB or Flashify (look for it in the Play Store), change your DPI, and then flash your stock kernel back if you so choose. Done!
[HTC Desire 510] karmasblade:
Thanks for your input. My carrier is Telus, the Canadian variant. I'm not sure if using the Sprint/Virgin kernel will mess up my phone, or any other kernel for that matter. I asked the same question in that thread and I got a reply saying it will be fine, I'm not quite sure that is correct though. Any thoughts?
[HTC Desire 510] jdmedeiros:
It will, DO NOT DO IT. Sprint is CDMA, Telus is GSM. There is a better way. DO you have this file: 0PCVIMG_A11_UL_K44_DESIRE_SENSE60_AIO_TELUS_WWE_1.11.661.1_Radio_1.101.1372.19.0725_10.22.4205.00L_release_391960_combined_signed_2_4.zip ?