yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Yank555:
Well ... you gotta ask Google this, they seem to not know this LOL

But lollipop is a full word, when Slimpop would be Slim's take on (lolli)pop :D

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.2a kernel.
[Nexus 5 Original Android Development] TJKV:
I'm not sure either, whether he was answering you or was saying there's no need for a discussion about the name :p

But either way there is actually no need for you to flash the multi-dpi add-on when you are using SlimLP builds :)
[Nexus 5 Original Android Development] VictorLapin:
I can't say that I pay attention to it, but you may be right.
[Nexus 5 Original Android Development] coolek33:
It's under your question so yes, it's a answer. I don't like quoting post right before mine.
[Nexus 5 Original Android Development] dokie80:
Works fine with me.
[Nexus 5 Original Android Development] perrocaliente:
Everybody is offended by everything these days. But whatever I'm not making the decisions so it is what it is.
[Nexus 5 Original Android Development] JaylanPHNX:
It's not a matter of being offended, it's a choice the team made to keep the name family friendly. People put Slim on their kids' tablets. You'd be hard pressed to find a joke too dirty for my sensibilities, but I don't think I'd put something called f**kROM on my young nephew's phone.

Perhaps this should be the last we hear about this subject. It was beat to death when lollipop first debuted, and we're about to move on to marshmallow.

From my SlimTab Pro 8.4
[Nexus 5 Original Android Development] Chitown021:
Bring on SlimMM :)
[Nexus 5 Original Android Development] perrocaliente:
I have a lot I could say about it but it's not important like you said. Here's to hoping marshmallow actually fixes some crap instead of just adding new features to the same crap.
[Nexus 5 Original Android Development] ( V ):
admit it, it does have a zing to it ;)
[Nexus 5 Original Android Development] bitubo:
hi, thanks for this great rom :)

it is possible to add a speed monitor of the network ? like the rom purity ?
[Nexus 5 Original Android Development] coolek33:
Try one from builders collective if you want it so badly.
[Nexus 5 Original Android Development] a g bell:
http://xdaforums.com/showthread.php?t=3182504

[ROM]★ Twisted Android Project ★ SaberMod | Layers | LYZ28J | Tweaks★ [Official] or try this one
[Nexus 5 Original Android Development] dokie80:
How many hours you guys get on SlimLP?

Mine is worse than stock, less than 10 hours, and I am on wifi most of the time.

Did i miss something ?
[Nexus 5 Original Android Development] NovaSlim:
depend on how much screen time, mine typically exceed 15 hours, more so if I use the screen less than 2 hours.
[Nexus 5 Original Android Development] dokie80:
I use it for work, so definitely more than 2 hrs, but I expect slimLP to have greater battery life than stock.

BTW, if u use supersu app, should I disable superuser option on developer setting? I ask this on Q&A thread, not sure if anyone still follow the thread :p
[Nexus 5 Original Android Development] TJKV:
I get great battery life on SlimLP, let's say around 18-24 hours with 3-3.5 hours of screen on time. Nothing too heavy though, mostly comm apps and calls, about an hour of 3G browsing tops.

Edit: Wanted to add that I got my battery replaced with a new one around 4 months ago, so if your battery is really old then it may just be that.

I had never realised that one needs to subscribe to the q&a portion of threads separately O.O Subscribed now, thanks :p
[Nexus 5 Original Android Development] dokie80:
thanks.... i ll see for couple more days..

yesterday is the first time on slimLP that I use cellular data for most of the day, and surprised to see that at 2pm (unplugged at 8am), left with 20% battery.

I use the phone for IMs, emails, SMS, and 1-3 calls.

attached is today's stats, with wifi connection most of the time, and i've disabled livedisplay. screen time is almost 2 hours.

I really dont want to start a debate about battery life betweens roms, but any tips to conserve battery on slimLP are welcomed, what settings to turn off etc. (especially hidden settings or settings that are not available on stock). I really need it to survive at least 12 hrs on cellular with active use.

here's what i did in hope to increase battery life:

- headsup notifications - off

- livedisplay - off

- ambient display off

- dashclock - uninstalled

thanks
[Nexus 5 Original Android Development] TJKV:
Those ROM features you mentioned hardly matter to a discussion of battery life. Any ROM that is decently made (IE no egregious mistakes in code that may, for example, keep your CPU at max frequency constantly) will give you good battery life. Similarly this applies to any user app one may install. Badly coded apps or apps specifically designed to require lots of processing power will kill your battery.

Rather it's the processor and the display that take up most of the juice. Reduce the brightness to the lowest usable level and reduce performance in favour of better battery longevity (since the things you said you do with the phone aren't all that cpu/gpu intensive).

How does one reduce performance? Play with the kernel, specifically governors, hotplugging, frequencies etc. One good place to start is [MENTION=2033478]Yank555[/MENTION]'s kernel with his personal settings (You'll see how to set those when you flash his kernel). You should find a link to his kernel in his XDA signature.
[Nexus 5 Original Android Development] dokie80:
Thanks. I try to change cpu governor and scheduler, and downclock max cpu, and see if it give signifant gain on battery.

From stats, I can see the phone run at max cpu clock most of the time (60%).

At first I flashed Franco kernel and stuck on boot :D

Lucky I have rom's zip on phone. Phew! Lesson learned. Should've read first :p
[Nexus 5 Original Android Development] coolek33:
Ahh battery life discussion. I think it's pointless cause everyone is using its device differently.

But here's mine on elementalx :p
[Nexus 5 Original Android Development] Phazmos:
[MENTION=1944312]Dokie[/MENTION]BO

Use privacy guard to disable location and keep awake in Google play services and any other Google play xxxxxxx you see
[Nexus 5 Original Android Development] perrocaliente:
The WORST user of battery in terms of apps is Google. That will use more battery than just about anything else. If you can turn off location history and disable Google now it will increase your standby time a lot. I have tested this and it greatly reduces how much your phone is awake when you're not using it.

---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------

You really only need it for services and the Google search app. However now you're gonna lose out on a lot of functionality with that method.

---------- Post added at 08:23 AM ---------- Previous post was at 08:22 AM ----------
[Nexus 5 Original Android Development] perrocaliente:
You really only need it for services and the Google search app. However now you're gonna lose out on a lot of functionality with that method.
[Nexus 5 Original Android Development] dokie80:
really appreciate the replies... I'm using smart lock, so turning off location is not an option.. location history already off. I'll see privacy guard..

but today i m seeing better stats after changing cpu setting ;)
[Nexus 5 Original Android Development] dokie80:
Great battery for today

Btw. About root app. Should I disable root option in developer options if I use supersu app installed from play?

Thanks
[Nexus 5 Original Android Development] JaylanPHNX:
If you're using superSU, it doesn't matter what you set the built-in superuser to. I leave it on in case something goes wrong with superSU (like the backup script not working on a dirty flash).

From my SlimTab Pro 8.4
[Nexus 5 Original Android Development] badrsj:
Very interested in this ROM. Does any one have a double tap 2 wake solution or is that baked into this ROM? Thanks
[Nexus 5 Original Android Development] SunamY:
Using slim of [MENTION=2033478]Yank555[/MENTION] since a few hours. It's so awesome... It's fast as hell and unbelievable solid. Battery is really great with latest hell's core kernel. Awesome work Slim team and [MENTION=2033478]Yank555[/MENTION]

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] NHNXDA:
Using the latest release, the lock screen lag is back for me & I wiped cache, dalvik, system etc, anyone else got the same issues?
[Nexus 5 Original Android Development] dokie80:
I assume double tap screen to wake use alot of battery. No, It is not built in the rom.

I use proximity sensor to wake screen with 3rd party app.
[Nexus 5 Original Android Development] DigitalUnderground:
Left the N5 for the Moto X, than G3, than S6....... Come back to my N5 and check my old favorite thread and first thing I see is the same thing I saw when I left... Smh some people.

Agree that was beat to death, and it was time to move on about a year ago.

Anyway... Who's building for Slim nowadays... Are Kufi, Juba, bassplayer, and Robbie still at it?
[Nexus 5 Original Android Development] physwizz:
Yes. Let's move on to "marshslim" :)

Or perhaps "SlimMM" would be better to follow "SlimLP"
[Nexus 5 Original Android Development] hooliganx:
and how's your battery? compared to a dt2w in kernel.

n5twisted.08.18layeredslim.gapps.08.20

blu_spark.r14rd.2.26v4a.2.3.4twrp2.8.7.1

-----------------------------------------
[Nexus 5 Original Android Development] dokie80:
what is dt2w?

attached my battery stats, with no game played.

but I change the cpu governor to interactive, and scheduler to cfq, and downclock max cpu to 1,7ghz.
[Nexus 5 Original Android Development] AquilaDroid:
Double Tap to Wake - uses 2-3 percent of battery per hour.
[Nexus 5 Original Android Development] Phazmos:
Slimellow

Maybe with 2 ms though

Slimmellow

Yeah, that's the ticket
[Nexus 5 Original Android Development] DroidIt!:
Flar2 (ElementalX) has it down to about .4% an hour. ;)

Slimlow? SliMarsh? SlimArs?

---------- Post added at 08:13 AM ---------- Previous post was at 08:11 AM ----------

Ohhhh! I have a mascot! Absolutely perfect! :)

---------- Post added at 08:14 AM ---------- Previous post was at 08:13 AM ----------

Ohhhh! I have a mascot! Absolutely perfect! :)
[Nexus 5 Original Android Development] amphi66:
He needs a bit of a diet for the "Slim" participation, tho!
[Nexus 5 Original Android Development] dokie80:
So, ElementalX works on SlimLP?
[Nexus 5 Original Android Development] DroidIt!:
Yessir. Really well actually. ;)
[Nexus 5 Original Android Development] dokie80:
Mind telling me how to install it?

I ve read the thread, mentioning about installing it via aroma installer is recommended, is this aroma is built in the ROM? Or a 3rd party app to be installed? Or I just flashed the zip file via twrp?
[Nexus 5 Original Android Development] DroidIt!:
Yeah sure :) You just click the download link in the op, pick the most recent L kernel and download the aroma installer version. Just go into recovery and flash. When you select to flash it aroma will open up and let you select what options you want for your install. I've found it's pretty much just best to stay with the defaults that flar has preselected. His preselected values are a pretty good balance between performance and battery savings. You can always tweak, but I'd just start out with the defaults to get a good baseline.
[Nexus 5 Original Android Development] physwizz:
True dat
[Nexus 5 Original Android Development] Renton91:
Is the Prevent accidental wake up working now?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] t0mas_:
it doesn't for me
[Nexus 5 Original Android Development] prbassplayer:
So in the process of debugging the slow wakeup can people suffering from the problem do me a favor. Go to Settings/Interface/Quick Settings/ and turn off "Disable on Lockscreen". After that reboot to recovery wipe cache and dalvik and boot normally and use. Report back if problem still exists, is better or is solved.

Cheers
[Nexus 5 Original Android Development] Mikulec:
If by slow wakeup you mean the lag, then I have this option always on and get the lags.
[Nexus 5 Original Android Development] TJKV:
Same as [MENTION=653788]Mikulec[/MENTION] above.

Further, entirely disabling the lockscreen via Settings->Security->Screen Lock->None leads to the home screen/foreground app lagging on screen on :p

([MENTION=1277872]dankoman[/MENTION] too)
[Nexus 5 Original Android Development] prbassplayer:
I meant off, fixed original post

Sent from my SlimRoms powered Galaxy Tab Pro 8.4
[Nexus 5 Original Android Development] zymphad:
I do not have that option.
[Nexus 5 Original Android Development] Mikulec:
Ok, this is probably the only option I didnt try in the proccess of investigating the lags. And unfortunately I am not on Slim now, so I cant test it.
[Nexus 5 Original Android Development] Fastrite:
My normal setting is to have this setting switched off and only occasionally get the lags (sometimes more than a week apart). I can confirm [MENTION=4148153]TJKV[/MENTION]'s comment that the lag occurs on the homescreen or foreground app when the lock screen is disabled.
[Nexus 5 Original Android Development] zymphad:
How? Setting isn't there.

Wasn't there when I used Robbie's 8/16 build and not there with Yank's 8/25.
[Nexus 5 Original Android Development] wangdaning:
SlimMM

---------- Post added at 08:44 AM ---------- Previous post was at 08:41 AM ----------

It is there for me on Robbie's 8/16 build. It is the last one in the QS options under interface, you have to scroll down.
[Nexus 5 Original Android Development] zymphad:
That was embarrassing, found it.

Seems to have fixed the lag for me, but that may change later. Will update if the lag returns. I'm on the Beta 0.6 Yank 8/25 build with his kernel.
[Nexus 5 Original Android Development] wangdaning:
double post
[Nexus 5 Original Android Development] AquilaDroid:
Are you and Tapatalk done spamming the thread? (I know you didn't intend to post so many times!) This might be a new record though - 22 reps...
[Nexus 5 Original Android Development] dokie80:
You actually count it?

Btw, u guys talking about MM preview, not SlimLP, right?
[Nexus 5 Original Android Development] TJKV:
Doh, that actually makes sense. Will report back after further testing.
[Nexus 5 Original Android Development] batam:
Using latest Robbie's release I have now a '!' on my network signal.

Flashed LMY48I radio, reboot but no luck.

Seemed to work fine during 2 days then it's having issues now.
[Nexus 5 Original Android Development] Mikulec:
Check if you have correct APNs set in network settings.
[Nexus 5 Original Android Development] Mikulec:
Just tried that and within few hours I got teo lockscreen lags. So turning it off didnt help. :(
[Nexus 5 Original Android Development] prbassplayer:
Yea by itself doesn't fix it. We are working on it, pita bug.

Cheers

Sent from my SlimRoms powered Galaxy Tab Pro 8.4
[Nexus 5 Original Android Development] Mikulec:
Are you on track of the bug or you still dont know what it could be?
[Nexus 5 Original Android Development] prairie-dad:
I hate to be dim, but oh well, I guess I just am...dim or timid

Got my N5 back in early 2014, rooted it immediately, and have been using SlimROMs ever since...weekly after weekly for many months, culminating in the final SlimKat 4.4.4 last December. But now SWMBO has a new little phone, and it came with Lolllipop, so it was time for me to catch up. Yesterday I went to the 5.1.1 factory image, to get the right bootloader and radio, and now I'm ready to leap into SlimLP, where I'm sure I'll be much happier.

I've downloaded TWRP 2.8.7.1 for hammerhead to my Mac, and will rename it twrp.img. I've got SuperSU 2.46, and I've got [MENTION=2095315]ezio84[/MENTION]'s latest build for a ROM (still to be moved to the root of the internal storage.)

Question 1: (small question) What GAPPS?...can I use [MENTION=1277872]dankoman[/MENTION]'s here, and is the mini from 20150729 the latest?

Question 2...the big question: Do I do _this_?:

1) move the SuperSU, ROM and GAPPS .zips to the root of my storage.

2) have the TWRP in the folder with fastboot, adb, etc., binaries

3) reboot into the bootloader (already unlocked)

4) flash recovery

5) reboot...but into what...system or recovery?!

If I reboot into the recovery, can I immediately use TWRP to make a nandroid? (not that I really need one...I haven't done anything much with stock, and it would be easy enough to reinstall it via fastboot if I had to, but still, isn't it a good idea?) And can I do this without having root yet? (I think yes, but just checking.)

If I have then made a nandroid, can I reboot into recovery (no connection to the Mac any longer necessary...) and then flash SlimLP, GAPPS and SuperSU .zips (in that order?)

Or, do I have to flash SuperSU earlier...for example:

1) fastboot flash recovery twrp.img

2) reboot into recovery, make nandroid...then flash the SuperSU

4) reboot into system, that is a now rooted stock 5.1.1

5) reboot into recovery, flash Slim, GAPPS, (and SuperSU again?)

Bear in mind, I haven't rooted the phone since about 18 months ago...I hope I'll be forgiven for wanting to go over all the steps, just to be sure.

Many, many thanks to all...just playing it safe.

p-d
[Nexus 5 Original Android Development] TJKV:
No, use the latest that he has uploaded. 20150820 I believe. And no, there is no need to flash the multi-dpi add on while using it on slimlp. The rom fully handles compatibility between gapps and non-stock dpi now.

The first way is fine, and flashing rom, gapps, supersu in that order is the way to go. But here is what I usually do when going from stock:

1. Fastboot flash recovery

2. Reboot to recovery immediately

3. (Optional nandroid but since you already have factory images on hand, you can skip.)

4. Connect USB to your computer and enable mtp, transfer back your nandroid.

5. Wipe /system /data (and internal storage too) and /cache

6. Transfer rom, gapps, supersu from computer

7. Flash in that order, reboot

8.??

9. Profit!

But to further address your question of whether to reboot to system or recovery after fastboot flashing recovery, here's the deal:

On the nexus 5, one needs to reboot to system immediately after doing 'fastboot oem unlock', without immediately flashing a custom recovery. That's because the phone needs to wipe data after an unlock, but it can do so only on rebooting and only using stock recovery. Replacing stock recovery with twrp before that reboot and data wipe will cause the phone to not boot, as a security measure to prevent access to your data.

After the reboot and wipe, one can head back to bootloader and flash custom recovery. Now we have to head to recovery first rather than booting up the os. The stock os has a stock recovery restoring script that may run and overwrite twrp. Hence boot to recovery, and allow it to erase that script. You will get a prompt to do so.

After these you are free to do as you wish. I'd recommend you check whether you have mtp access from twrp first though.
[Nexus 5 Original Android Development] ezio84:
Don't flash supersu, it's bundled with the Rom ;)

Ps: ensure you have my latest build from yesterday, it seems to fix the lockscreen lag.
[Nexus 5 Original Android Development] dokie80:
ezio84, can I dirty flash your build over RobbieL811 's? never realize LP has lockscreen lag, seems fine on mine.
[Nexus 5 Original Android Development] ezio84:
Wipe system and caches, it should be enough.
[Nexus 5 Original Android Development] wangdaning:
If you are on stock that is a lot of steps not needed.

If locked bootloader unlock it in fastboot as mentioned

1) fastboot boot twrp image (not needed if you have twrp already)

2）Wipe everything

3) With phone in recovery, on pc "adb push (slimlp version on pc) /sdcard/" "adb push gapps version on pc) /sdcard/"

4) Install slim and gapps in twrp

5) Install twrp if you don't have it (use "adb push (twrp.img on pc) /sdcard/" and then use recovery to install img file)
[Nexus 5 Original Android Development] wangdaning:
Accidentally glued my hands together with super glue after the above post, maybe I am not the best one to give advice :silly:

It might just be that the super glue container was spotty, too cheap, and bound to fail (you get what you paid for). God knows what would happen if kids in the US could get 15 cent tubes of super glue (I know what I would have done) :eek::eek:

PS I am a US citizen living in China and yes it is that cheap for something like that.
[Nexus 5 Original Android Development] Natakranta:
Hi, I couldn't have locked GPS position at all on beta 2.1 and 2.2 even though nobody else had this problem. Clean flashes were not solving the problem. I thought my GPS was broken, but when I restored nandroid of full stock factory image just rooted with SuperSU GPS was working fine. So next thing I did clean flash of beta 2.2(2) and GPS is now working fine on SlimKat. Since then I clean flashed beta 2.3 and GPS still good.

So if SlimKat clean flash doesn't fix it for you, restore/fastboot flash Google factory images and clean flash SlimKat over it.

Good luck!
[Nexus 5 Original Android Development] AndrasLOHF:
You using the headphone jack??? Phone speaker and bluetooth work flawlessly with the ROM but something causes issues with the headphone eq. I'd also try moving it to a system app if the process is getting killed in the middle of playback.
[Nexus 5 Original Android Development] bigbear6708:
Loved slim on my s3... think I'm going to finally get around to flashing on my n5...I just love this phone stock so much!!! How is this baby compared to stock??!
[Nexus 5 Original Android Development] DroidIt!:
My guess would be some sort of previous mod installed that left some junk files. I clean flash every update just to avoid any possible problems. I have seen in the past even after wiping everything, somehow my wallpaper from my last version pops up on a clean install. I don't recall it doing it on the N5, but I have had that before. Thanks for sharing though, good to know what might work/be needed in the future. :good:
[Nexus 5 Original Android Development] Natakranta:
My exact thoughts. There must have been some leftovers from between flashes of different custom ROMs, some survival scripts or something that were resisting data+cache wipe and even manual system format in CWM.

So my advice is, if your phone starts playing funky despite clean flashes, restore full stock Google factory image and start from scratch.

---------- Post added at 04:57 PM ---------- Previous post was at 04:45 PM ----------

Stock? I didn't even think about stock since first SlimKat alpha. Last time I restored stock nandroid I noticed it's missing hell lot of a features which I so much get used to on SlimKat that I started to take them for granted. Make a nandroid and flash. You will not regret it even a second.

Did I mention additional hour of SOT? On stock (with my pattern of usage) I was getting 3+h SOT, really struggling to reach 4h. On SlimKat, after one day (ROM settles?) I'm getting 5h SOT with the same pattern of usage. I will not get into details because I don't want to start battery life discussion in development thread.

It's great and it's just getting better with every weekly release.
[Nexus 5 Original Android Development] Aggarwaldhruv:
Not working with phone speaker at all.. And also .. Stop working if pushed to system app
[Nexus 5 Original Android Development] bigbear6708:
Thanks for that! I fear I will miss the Google dialer...lol. Going to flash tonight, granted I stop puking!! Lol
[Nexus 5 Original Android Development] AndrasLOHF:
I'd try uninstalling the drivers and app, reboot, install the app as a system app(either push it to system manually and match permissions or install as user app and convert with Titanium), reinstall drivers and reboot. I've installed the app dozens of times on Slim with all the awesome updates we get and the only issue I've had is sporadic with headphones.
[Nexus 5 Original Android Development] Aggarwaldhruv:
Tried what u said .. But not working .. Everything is fine but it is not processing