yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] VictorLapin:
[MENTION=4217156]SnZ[/MENTION] your log is very clean actually.

There are the key strings of it. If you have some dev skills, you can easily investigate it yourself. Otherwise... as [MENTION=2033478]Yank555[/MENTION] said, fixes for 4.4.4 are very unlikely to happen.
[Nexus 5 Original Android Development] SlimFatso:
Is SlimPIE implemented ? It's the only thing that's keeping me on lollipop
[Nexus 5 Original Android Development] Yank555:
Sure, been in for quite a while already :

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.

EDIT : Sorry, I misread your post, nope not yet implementes in Slim6 !
[Nexus 5 Original Android Development] malek_anas_97:
When the phone reboots and powers on before connecting to wifi the time is always missed up, after it connects to wifi its back to normal and then the usual timeservice force close

And i keep getting error messages from what's app telling me that my time is incorrect

Is this because I'm in airplane mode ?

And will unticking the automatic time and date switch in the settings do any thing to solve this ?
[Nexus 5 Original Android Development] Yank555:
Nope, that's due to rtc not being updated correctly, TimeService fc should be linked to that. I need to find time to look into this, but not easy atm to find time :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] Vogie:
Gapps for 5.1.1?!

Nexus 5
[Nexus 5 Original Android Development] pianistaPL:
www.opengapps.org
[Nexus 5 Original Android Development] Yank555:
Official Slim gapps : http://xdaforums.com/showthread.php?t=2792842

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] Yank555:
Just not merged in yet.

But as I said, if you want it, just use my private build which has had that in for ages.

The difference between the DM build :

Slim-hammerhead-5.1.1.beta.0.8-UNOFFICIAL-20150926-1141.zip (plain SlimLP source)

and my private build (which I run as daily on my daily device) :

Slim-hammerhead-5.1.1.beta.0.8-UNOFFICIAL-20150926-1607.zip

is this changelog :

- Statusbar network traffic indicator

- SuperSU settings integration

- Remove AOSP system update

- European time servers for gps (Yank555.lu)

- Adblocking hosts file

- Layers : RRO Type 2.1 support (reverted type 2 and redone 2.1)

- Layers : Exposing Settings backgrounds for more theming options, while not impacted stock

- Layers : Add the ability to color dashboard title independently

- Suppress sound on volume rocker wake

- Use 20dpi steps also for high resolution devices (Yank555.lu)

- Hide AlarmClock Icon in StatusBar (Marek Walczak)

- Slim global menu (fusionjack)

- add Lockscreen rotation switch (Yank555.lu)

- updated kernel to m-preview-2 Google sources (Yank555.lu)

- CellularTile: Long-click triggers detail view instead

- ResolverActivity: reduce elevation to make it flat

- Fix the cell standby mobile radio active issue

- RRO: idmap: fix sorting of overlays.list

- kernel-config: only run kernel-config script if kernel is Yank555.lu (no more need to delete the file if you run a custom kernel !)

There is no objective reason to be "afraid" of using that ROM if you "dare" using the DM build ;)

JP.
[Nexus 5 Original Android Development] panni:
Damn, I flashed the "wrong" ROM then, didn't pay attention to the DM detail :(
[Nexus 5 Original Android Development] TJKV:
Got quite a shock to see the lock symbol against the old thread in my CP, all sorts of explanations running in my head, from mods locking it temporarily to fix the ghost "New Post" appearances in the CP, to a full blown SlimPocalypse O.O

But good to see it's something more innocuous than I had imagined :p

Will definitely miss the old one, lots of fond memories over there for the past two years :)
[Nexus 5 Original Android Development] Mikulec:
Yea, I am especially missing the old chaps (Tylog, Juba, Kufikugel, ...). But to see also the bright side, we have "new" faces here (well, not really new) who are keeping the work going.
[Nexus 5 Original Android Development] theesotericone:
Everyone will eventually migrate over here. Well, everyone that still has the device that is. It's hard to imagine the old thread made it almost two years and two android versions. In the tech world that's basically legendary status. I'm sure [MENTION=2033478]Yank555[/MENTION] realizes he's filling some big shoes. With his past track record on XDA and with Slim specifically, I'm sure this thread will be every bit as good. Now, we better get some off topic started to make him feel at home.:cool:
[Nexus 5 Original Android Development] paradoxiumwind:
Working fine except I get "unfortunately, Clock has stopped" when the rom boots up - I load the clock app and I see the background for it but then it closes and gives the same error. Is it just me?

Edit: clearing the clock app cache/data fixed it

Edit2: No way to hide the clock from the nav bar? I feel like every time a new rom update comes out we go two steps back.. this stuff should be standard in the stock google roms now, right??? I mean c'mon
[Nexus 5 Original Android Development] Yank555:
I suppose we are talking about the statusbar ?

If so, I'd suggest you have a look at :

Settings --> Interface --> Statusbar --> Clock & Date :

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 5 Original Android Development] DrunkFuX666:
I think it's time to flash Slim again... Loved it... But just not had the time or patience to reinstall everything from scratch...

Long Live the Slim...

Sent from my Nexus 5
[Nexus 5 Original Android Development] lightingcloud:
[MENTION=2033478]Yank555[/MENTION] I'm wondering if there's a problem with IO speed or with rendering? Sometimes the phone become incredibly laggy and I have no idea why...

True, I didn't do a "full clean install" (as in flash stock first then root etc), but I did wipe system and data first...

Maybe your custom build is better in that sense?
[Nexus 5 Original Android Development] formicae:
The only place I notice lag is the dialer, big delays when selecting a contact, viewing details, and when tapping the call button itself. Present after clean flashes of 0.5 and 0.8 betas, but I didn't use the dialer until I had reinstalled a few apps, so I can't rule out something else misbehaving unless someone else confirms it's slow for them.
[Nexus 5 Original Android Development] dokie80:
[Hammerhead][ROM-AOSP][2015/SEP/27] SlimLP 5.1.1 beta 0.8

I had this lag too. I suspect the cpu governor and scheduler, so I change it to interactive+noop. Much better now, but consume more battery.

[MENTION=1885761]formicae[/MENTION] And my dialer app is also kinda lag. Not sure that everything should run smooth, I can live with the 1-2s delay for some apps,as long as not all. :P
[Nexus 5 Original Android Development] Yank555:
That is very odd, I never noticed anything thelike ...

Do you use any kernel apps ? If so, try not to (freeze them) to check cpu freqs are not turned upside down.

Also, which kernel are you 3 using, stock ?

Cause I'm wondering how interactive would be so much different than yankactive (it's really just a tad cooled down) and noop vs. fiops should actually not be an improvement.

JP.
[Nexus 5 Original Android Development] Mikulec:
Well, I am getting really bad lags, they are so big that the phone becomes unresponsive for more than 30 seconds. This is after clean flash of your latest personal build. Tried to change the kernel to ElementalX and it didnt help. I am going to flash tonight different rom (probably latest M preview) and see if that is the rom or some app is causing it.
[Nexus 5 Original Android Development] Yank555:
Oh :( When did this actually start happening ? My HH has always been snappy so far, bur since it's not my daily anymore, I can't test it as extensively as I used to or as I do for shamu.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 5 Original Android Development] Mikulec:
Probably last 2 builds, therefore I have tried clean flash the last to try to solve it this way. But it didnt help. I am forced to flash something else and test if it happens also on other roms.
[Nexus 5 Original Android Development] Yank555:
Thanx. Keep me posted how it turns out...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 5 Original Android Development] lutanica:
I have experienced the same thing. But it seems that one of my widgets (analog clock) caused much of the lags.. After removing that, it became my much better..
[Nexus 5 Original Android Development] Mikulec:
I have them mostly in multitasking, switching quickly between tasks, browser and youtube and others
[Nexus 5 Original Android Development] VictorLapin:
Actually the dialer is really less snappy than other apps. No bad lags here though.

Tapatalked from Slim Nexus 5
[Nexus 5 Original Android Development] Yank555:
Compiling a testbuild (kernel) ... only worth trying if you run my kernel...

Will post when I'm back home ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 5 Original Android Development] Mackie Messer:
Installed Slim6. Looks good and feels pretty fast. Found only two things:

1. Keyboard: Gesture typing (slide) doesn't work.

2. Clock: Crashs when I try to open world clock.

---------- Post added at 11:17 PM ---------- Previous post was at 10:44 PM ----------

Where are the USB-Options? Can't find anything.

---------- Post added at 11:22 PM ---------- Previous post was at 11:17 PM ----------

OK, I found it in the notification bar, not in the settings.
[Nexus 5 Original Android Development] Phazmos:
Try dev options
[Nexus 5 Original Android Development] kamild_:
Hey, how's SlimLP? How many functions are already implemented compared to Slimkat? Is it stable enough for daily usage? Asking because I'm missing all those functions from SlimKat and I'd love to use them on Lollipop :D
[Nexus 5 Original Android Development] oxidising:
I've been using it daily for months now, it's great. Going to try out the Marshmallow release today, see how that goes.
[Nexus 5 Original Android Development] oxidising:
Is the DPI different in 6.0 for a reason or am I safe to change it? What DPI is used in the Lollipop build?
[Nexus 5 Original Android Development] Mackie Messer:
Slim6 is like stock. I changed it with textdroider_dpi. No problems.
[Nexus 5 Original Android Development] oxidising:
What DPI does SlimLP use?
[Nexus 5 Original Android Development] BlueDevil™:
480
[Nexus 5 Original Android Development] theesotericone:
Nope. SlimLP uses 400. 480 is stock density.

This is pulled from the build.prop of the last DM build for SlimLP.

ro.slim.lcd_density=400
[Nexus 5 Original Android Development] malek_anas_97:
The title says "NOV/29 slim6" and i don't see any post about a new build is it just the xda app acting weird or there's something that I'm missing ? ?
[Nexus 5 Original Android Development] Yank555:
Nah app is fine ... I was about to upload, when I noticed I still had not added the kernel config script ... and well ... let's say ... simple things can sometimes grow complicated :D

Maybe there will be an update soon (it's midnight here now), or maybe there won't :silly:

JP.

Edit : Sorry, I'll call it a day, it's past 1am, work tomorrow, no update for now :(
[Nexus 5 Original Android Development] tehtrk:
System becomes unresponsive

Hello, firstly, I want to say thank you for maintaining slim in the nexus 5. It's been my favorite for years (since slim bean).

Running 5.1.1 beta 12, I have noticed occasionally that the foreground app on my phone will occasionally become unresponsive, sometimes for minutes at a time, and sometimes resulting in a reboot. It is sometimes an app, and sometimes the system ui.

I have been trying to reproduce the behavior today so I could get a logcat snippet to attach, but I have been unsuccessful. Are there any known issues which could result in the behavior I described? I know it is a bit vague, but I have the time to look into this finally and I would appreciate any input on this.

I have tried wiping data, as well as reflashing after factory reset.
[Nexus 5 Original Android Development] Yank555:
From what I gathered it mostly will happen after longer uptime ... ram would run full, which causes the lag.

Can't say I ran into this on HH, but i don't use is as daily, so I'm not really likely to run into this myself...

Atm I'm trying to get Slim6 to run my kernel config script, but new SELinux is not really being friendly with me on this :(

JP.
[Nexus 5 Original Android Development] preusstang:
Unfortunately my brother and I are both seeing this on a daily basis. At least two reboots a day to keep running smoothly. There must be a leak somewhere..
[Nexus 5 Original Android Development] Yank555:
Have you tested a different kernel, does that make a difference ?

Just looking to know if I'd need to look into ROM or kernel...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] lightingcloud:
I guess it's the same problem I had? I "solved" it with elementalX. It's not completely solved, since the phone sometimes still have some heavy lags, but at least it doesn't freeze completely anymore. I still have to do a reboot every 36 hrs or so, but it's still better that with stock kernel.

Oh, and since I stopped using Fleksy, the lags aren't so heavy.
[Nexus 5 Original Android Development] Yank555:
Everything would still keep hinting towards zswap being a potential issue ... But I already made a non zswap kernel and even a full stock kernel, and it made no difference ...

Well no difference as in it would behave as elementalX, but that's not "good enough" to be a solution for me. So I guess that somewhere there must be sth wrong on the ROM side, but that would be another universe to look at :(

Atm I'll be pretty much away from my keyboard, likely won't get much Android time until mid decembre... and how it will be over the xmass days is yet another story ;)

JP.
[Nexus 5 Original Android Development] Dodgexander:
Once you have the time adding support to multi rom might be an idea for people testing out. I tried to install via multi rom but it failed.
[Nexus 5 Original Android Development] preusstang:
I'll try this over the next few days. Btw, we're running your personal builds if that matters.

EDIT: Also curious if anyone else is having GPS lock issues. Both of our phones are refusing to get locks and when they do, they're lost after a couple seconds. I've tried clearing cache etc. and using the GPS Status and Fix app.
[Nexus 5 Original Android Development] lightingcloud:
My GPS is fine, the compass sometimes is stuck pointing south but that's not ROM related AFAIK, it's a general n5 problem. Sorry :( maybe satellites above you are misbehaving?
[Nexus 5 Original Android Development] bonedriven:
I am sorry to ask this. But is this the official slimrom ? It seemed slimrom had disbanded some while ago?
[Nexus 5 Original Android Development] TJKV:
Definitely official. Was never disbanded, just went on a semi-vacation so they could revamp the backend, including forming an official company for Slim.

This is just a new thread as the old one was getting quite long, and the OP wasn't around anymore. [MENTION=2033478]Yank555[/MENTION] is the maintainer now, and he has the first post here at his disposal.
[Nexus 5 Original Android Development] VictorLapin:
Disbanded? Never! Resistance is futile! :D:D
[Nexus 5 Original Android Development] jugoslavpetrovic:
I'm new to this thread.

Just need some clarifying, a bit confused. Would like to try MM build but CAF got me confused. I cant really say what CAF twrp has that aosp twrp doesn't but I was sure that if the rom is CAF it needed twrpcaf or it could be flashed by some modification in .zip.

So, SlimRom MM is CAF rom, right? And, it can be flashed with regular TWRP?

What about custom kernels, are those need to be CAF as I assume?

Also, Bootloader+Radio, cuz one guy asked for dirty flashing from LP which I really doubt would go right, especially when it comes to bootloader and radio of course?

One more thing ;) are You the creator of Yankactive, Yankdemand ...?
[Nexus 5 Original Android Development] Yank555:
It already has multi-rom support, has had for quite a bit, but if you are talking Slim6, there's sth multi-rom needs to change because MM ROMs do a verify after flash, and that makes it fail to flash as second ROM.

There is a hack to just not do the verify, but Slim will not use it, Slim6 is MM and will stick to MM way of things, so Multi-ROM should adapt.

You can also apply the hack manually by removing the verify line in the update-script in the ROM zip prior to flashing it.

And I believe someone also said he could install it as primary fine and then move it to secondary.

Maybe someone with actual multi-rom knowledge can chime in, I may be repeating wrong stuff here, this is all based on hear-say, I am yet to test multi-rom :angel:

JP.
[Nexus 5 Original Android Development] Yank555:
That is very odd ... can you give the DM version a go see it that helps ? I use European time servers in my personal builds ... maybe that's the issue ?

JP.
[Nexus 5 Original Android Development] Yank555:
I don't quite get what the difference would be, a recovery is just flashing a ZIP file that contains (mostly) binary images, so basically all it does is a dd to a few devices ...

I still use a pretty old twrp (nothing CAF mentioned) that is easy 18 months old on my HH, never failed me.

But then again, I'm willing to learn more about the difference, so if someone knows more, please help us out ;)

I've been using the MM BL/radio for both LP and MM.

Regarding Yankxxx govs, yes, but well there's nothing much there, they are just slightly tuned stock governors, I've simply changed the default values of the tunables to make them a tad more battery friendly while trying to not lose snappiness. I only added them separately so I could switch from stock to my settings for that governor more easily ;)

JP.
[Nexus 5 Original Android Development] Dodgexander:
Thanks, it's a shame it doesn't just work out the box like most other roms do. I remember trying stock mm builds in multi rom when they started to appear and many didn't work. Recently though every other release seems to just work.

I'm not sure if this is because they all change the script or use the same mod but it would help a lot for people willing to try slim mm if multi rom did just work.

As far as the development of multi rom itself goes it doesn't look very promising. No update to modded twrp since June and latest release note states support for m preview only. I've seen people since in the multi rom thread for the nexus 5 also having to mod the script for some roms to install.

Shame, because if neither update to work with one another then slim miss out more users testing and reporting bugs[emoji10]
[Nexus 5 Original Android Development] Yank555:
Agree ... but on the other hand, Android is leading the way, and we ought to follow and not build more and more hacks over time to keep old stuff working.

Someone needs to pick up multi-rom if it's not to die...

I see your point, but I tend to agree with Slim's view on sticking with progress of the base code.

It's a choice of principle rather than a technical issue...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.4 kernel.
[Nexus 5 Original Android Development] shimatta8:
Hi guys can you guide me on how to upgrade from slimkat to slimlp?

so do i flash In this order?

twrp > then bootloader> SlimLP >Gapps >Kernel>Supersu?

If im to flash baseband and radio when should i flash it?

Can i dirty flash?

Thanks
[Nexus 5 Original Android Development] TJKV:
That order is correct. Would be most convenient to flash the bootloader and radio images together, don't you think? Flash bootloader, do a 'fastboot reboot-bootloader', and flash the radio image.

You should not dirty flash. Wipe data, system, and cache. In fact, the 'best' way to upgrade is to flash the full LP stock image, boot up once, and then flash TWRP, SlimLP, Gapps, Kernel, and SuperSU. Doing that wipes every partition on the phone, so backup your /sdcard partition to a PC.
[Nexus 5 Original Android Development] lightingcloud:
Google Play Service just notified me about the Android 6.0.1 update and asked me if I want to download it.

I'm on last SlimKat available.

WTH? I was considering going to stock for a while, but...

What should I do? Would this brick my device? Wipe everything I have on it?
[Nexus 5 Original Android Development] TJKV:
Don't even think about accepting that OTA update :P

Typically OTA update mechanisms are disabled on custom ROMs, but sometimes it sneaks in anyway. Through Google Play Services I suspect. If you want and you are capable, you can snoop around the services available in that app and disable the ones relevant to OTAs.
[Nexus 5 Original Android Development] lightingcloud:
I'm not, sadly, which means that the notice will stay there I guess. :'D untill I decide to actually update :P I'd do a clean flash, actually, but it's a pain to back up all the SD content. And I read that the -w option doesn't always work...
[Nexus 5 Original Android Development] preusstang:
I installed elemental x on both our devices Sun. night and so far neither us have had lock-ups or slow downs. It must be the kernel. Thanks for the suggestion.
[Nexus 5 Original Android Development] pkelly517:
SlimKat? I admire your devotion.

You can accept the OTA, but it will most likely fail. An OTA will only patch the device. As your /system isn't what's expected, you should just get a nice, polite error message.

You have a Nexus. You have to work very, very hard to brick it.

If you are taking a poll, like every single member in the Nexus G+ community apparently feels is required (/rant), I'd bump up to marshmallow. Doze does wonders for idle (on desk) time. Material Design is nice. Layers are wonderful. It's TRDS on steroids. Real Dark. Almost Dark. Green highlights. Pink highlights. Transparent screens. It just goes on and on.

There are custom ROMs that have many of the SlimKat features. You could try one until Slim gets up to speed. PureNexus is my current choice. I won't link in this thread, but it's easy enough to find.

Good luck, and Happy Holidays!
[Nexus 5 Original Android Development] TJKV:
Oh right, I should have specified what happens if he accepts the OTA. It will download the entire huge file, fail to flash, and proceed to redownload and fail again. This repeats until it has sucked up all his data limit (if any). Happened to a friend of mine on SlimKat for mako when Lollipop came out. Used up his 2GB allowance on 3G, and once that got over the carrier charged a fixed rate per MB that wiped out his remaining prepaid balance. All of this in one night :eek:
[Nexus 5 Original Android Development] lightingcloud:
Woah.

Thank you very much guys :) and yes, I did mean SlimLP actually. XD
[Nexus 5 Original Android Development] tehtrk:
I have been running elemental X for the last 2 days and I noticed it today when I was running google navigation with Pandora in the background. Pandora continued to play music, but the interface became unresponsive when I switched to it.. I ended up having to kill it and reopen it. Sadly, since I was on the road, I wasn't able to grab a logcat. At least I know one way to reproduce it though, so I may still be able to get some helpful logs.

Before installing elemental x, my workaround was to limit background processes to 2 or 3 under developer settings. This seemed to help to some degree, but I don't know if it was foolproof. Didn't test well enough, it was just a shot in the dark based on previous input on swap that I read in this thread.