yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Yank555:
And that is exactly not normal ;)

Just try to flash SuperSU zip right after the ROM before first boot on new ROM.

Also, skip clearing anything, there's no need really, all you'll do is loose a lot of time for app optimization on first boot. If it needs to be done, it will be, without clearing anything.

I just :

1) boot recovery

2) flash ROM

3) flash gapps - I know I could skip this, but it's a no fuss thing and the habit of an old man ;)

4) flash SuperSU

5) boot system

TWRP allows to queue zips, so it's no big deal to go about doing this.

Never had a glitch with SuperSU.

JP.
[Nexus 6  Original Android Development] PerfectSlayer:
Good to know! I still wipe cache and dalvik cache when I upgrade the rom :silly:
[Nexus 6  Original Android Development] panni:
I'm on 0.7 on my hammerhead now, and it's running great.

I've noticed one huge problem, though: I'm using a speedcam app (called Blitzer.de Premium), which allows me to hear speedcam warnings in my car's multimedia system using Bluetooth HFP. Since my clean 0.7 install the volume of the HFP sound is ridiculously low and I can't change that (tried several apps, resetting the connection, cranking the car's radio up etc). Calls via Bluetooth are working normally.
[Nexus 6  Original Android Development] Yank555:
You're on shamu thread --> Hammerhead is here ;)

Maybe the build you are on use the other blobs ?

Have you tested latest 0.8 I posted a few days ago over there ?

JP.
[Nexus 6  Original Android Development] panni:
Nope, I was on short vacation and Ding, there was a new build out. Finally got everything working on my clean 0.7. I've been posting here because it felt the most active, sorry.

I'm using the hammerhead build. Have there been any changes in terms of BT/HFP since before 0.7?

I'll try a dirty flash to 0.8 if you think that may change anything.

Thank you. I'll switch over to the hammerhead thread.
[Nexus 6  Original Android Development] Emilius:
Is it layers fully working with latest SlimLP? tnx
[Nexus 6  Original Android Development] damngood98:
download Yank's personal builds that he posts, and yes, layers works great on it...he's been posting a straight slim build now too though (no cherry picking, just from source) so make sure you grab the right one
[Nexus 6  Original Android Development] Galaxysm:
Does this ROM have theme engine or rro??
[Nexus 6  Original Android Development] G1-evolve:
Nav bar keeps dissappearing upon each boot (until I go in settings disable and renable it).. Also happens randomly upon using the ROM. Other than that so far its pretty good.
[Nexus 6  Original Android Development] Yank555:
Yes, my builds include Layers (RRO) 2.1.

This is very odd, never had that happen on any of the 4 Nexus I have the ROM running ?

Can you give us more details of your setup ?

JP.
[Nexus 6  Original Android Development] damngood98:
there's a post right above yours by a very intelligent man who was just speaking of such things :p

um...no idea...if your current build wasn't clean flashed it may be a good time to give that a try...otherwise cat + log = better help :D ...oh, btw, assuming you're not using expanded mode settings? nav bar is set to on?
[Nexus 6  Original Android Development] Khizar:
Are you using xposed? Or more specifically GB module? That causes this issue..
[Nexus 6  Original Android Development] :
Yes this is an Xposed problem. Seen it before. If you have GravityBox then disable any navbar stuff.
[Nexus 6  Original Android Development] drharder:
Just want to say awesome rom. Sleeping like a baby. Great work!
[Nexus 6  Original Android Development] jcrompton:
SlimPIE

From an everyday usage perspective ... do most of you guys that use SlimPIE just completely disable the NavBar? Or do somehow use both in combination?

I guess having the NavBar always present can be convenient but at the expense of screen real estate
[Nexus 6  Original Android Development] franatic08:
SlimPie, navbar disabeled.

I trigger it from the right and bottom. Only wish SlimPie "responded" as well and as fast as LMT. Somehow it feels sluggish for me.
[Nexus 6  Original Android Development] :
SlimPIE with NavBar completely disabled. I use GMD Gesture Control to navigate so I actually use even SlimPIE very seldom. This setup works absolutely perfectly for me :)
[Nexus 6  Original Android Development] drharder:
SlimPie, navbar disabled. I like the extra space. I also use Nova Launcher Prime an have gestures setup to toggle the dock and notification bar. This way I get maximum screen.
[Nexus 6  Original Android Development] danarama:
SlimPIE bottom only, no Navbar. Nova prime, just 1 button to app drawer on dock.. Use glove box with swipe gesture for everything else
[Nexus 6  Original Android Development] beren:
Hi there...

I am a new N6 user, bought only 5 days ago and coming from a slimmedLP oneplus one wanted to try on n6 before jumping on MM.

Obviously slim is great on N6...just I am noticing some frame drops that sound strange in a powerful device like neuxs6, I didn't see this while on stock rom.

Is this related to encryption as I readed?

Inviato dal mio Oneplus One utilizzando Tapatalk
[Nexus 6  Original Android Development] danarama:
Framedrops? Please describe.
[Nexus 6  Original Android Development] beren:
I mean that the very smooth animation in the ui sometimes is not so smooth... The frame rate goes a little down for a moment, barely noticeable.

Can't even call it lag... And I am talking about the Ui not in app or games

Inviato dal mio Oneplus One utilizzando Tapatalk
[Nexus 6  Original Android Development] Rd. Vortex:
Personally I'm also coming from a OnePlus One (mine died). I haven't noticed any significant frame drops. What's strange though, is that despite the specs being basically the same on the both devices, I sometimes get random freezing/hanging as if the device is running out of RAM. I find this quite odd considering how powerful the device should be and it definitely shouldn't be running out of RAM. Don't recall same happening on OnePlus One when I had SlimLP or Exodus on it.

I have had encryption disabled since the day I switched to SlimLP.

Also on completely another matter: Does anyone else get random sleep of death? I've now twice encountered a situation in which the phone is completely dead and screen won't turn on until I reboot by holding power. First time when this happened my phone was ringing but I couldn't answer since there was no way to turn the screen on.
[Nexus 6  Original Android Development] Yank555:
2 things come to mind, one being the 'prevent accidental wakeup', or the unstable current issue on shamu.

If you go through the Google logo, I think the latter can be the case. Been running into that myself, but no idea what to do about it. Moto's attempt by limiting cores online and capping cpufreq didn't help at all on my end.

Worst, on poweroff there is no kernel log left to look at :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] Rd. Vortex:
So, could disabling prevent accidental wakeup possibly solve the issue? I do have to completely boot the phone though so that it goes all the way to the Google logo.
[Nexus 6  Original Android Development] Yank555:
The prevent accidental wakeup will cause the display to not turn on as long as your proximity sensor is triggered, that's it's whole point. This can be good, but you need to aware of it. If for example you hold your device in landscape, you'll trigger the sensor, and your screen won't turn on, neither on a phone call, nor motion detection, nor notification, nor power button press. That is intended behaviour. Just test it bht turning the display off, putting a finger on the proxy and with the other hand hit the power button, the device will stay switched off if this option is enabled.

Now if your device just turns off (as in powers off) and you need to restart it (Google logo), that's likely the 'instable current' hardware issue. I'm running into this occasionally myself on my device, but I just can't RMA it and not have it for weeks, so I live with that.

In m-preview kernel moto tried to limit CPU to 2 cores and cap cpu max. freq to 2GHz whenever instable current is supposed to be detected, but this didn't help at all one mine, hence I disabled that again, so at least we keep full CPU performance all the time.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] hotyys:
It is possible to disable non-intrusive incoming call notification? I can't seem to find an option to turn it off.
[Nexus 6  Original Android Development] Yank555:
Yup. It's in the dialer app settings -> call settings :

JP.

Sent from my Note 3 running Yank555.lu SlimLP 5.1.1.
[Nexus 6  Original Android Development] hotyys:
Thank you!
[Nexus 6  Original Android Development] CrashTestDroid:
Ok guys, something bad happened between 9.27 and 10.03 builds. Just flashed the 10.03 build by [MENTION=2033478]Yank555[/MENTION] and on bootup got the cyanogen style retina searing 'Optimizing apps' screen, and now LiveDisplay doesn't work either. Last I checked the borked Live Display was localized to CM-based roms? Anybody got a workaround or fix handy cuz i am not near a computer...
[Nexus 6  Original Android Development] Yank555:
LiveDisplay works fine on my end, just tested.

What exactly is the 'cyanogen style retina searing' ?

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] beren:
i wasn't comparing oneplus with n6 smoothness, just stock n6 with slimlp n6...

btw...talking about encryption, that i don't need, turning it off will wipe my storage? and what about he incoming andorid M, will this force encryption again w/out a custom kernel?

thanks for answering a noob :)
[Nexus 6  Original Android Development] Smallsmx3:
Encryption is here to stay.... Yes it will force it when 6.0 arrives. You should give it a whirl. It was definitely over exaggerated. It doesn't effect performance one bit
[Nexus 6  Original Android Development] CrashTestDroid:
Weird, I can only see Live Display working for the first 15 seconds or so and then it visibly goes back to daylight setting. It's manually set to "Night mode" because auto wasn't doing anything at night.

Retina searing "Optimizing Apps..." screen is the one at ending of the boot sequence before the lockscreen is shown. It happens if you wipe dalvik in TWRP or flash a new rom. I've never seen that happen on Slim before.
[Nexus 6  Original Android Development] Yank555:
Do you change this right after boot ? Could be the kernel config script setting display to calibrated 6500k ... maybe try changing LiveDisplay after 2-3 mins after boot. If it sticks until reboot, I know what to do ;)

This will happen each time there is a change in frameworks base repo, that's totally normal to happen with change coming to the ROM ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] Yank555:
ROM Testbuild

Those of you using stock MMS app and having issues, can you test it in this build ?

Josue took a go and stock MMS app should be working now.

Download Link

Thanx for reporting back if it's fine on your end !

JP.
[Nexus 6  Original Android Development] danarama:
I'm not sure what is going on for me. I've flashed pretty much every update since Beta 0.1, but none of them seem as smooth when I'm gaming. I use the same kernel and settings as always (and tried the kernel that comes with the ROM too) but it's always the same. I'll play the game for a while (Modern Combat 4 online to be precise) and after a little while of playing, it get's jerky and I lose the precision I need.

I usually stay on a new build for 2 days, then I get annoyed and restore back to 0.1 every time.

Does anyone else ever see this sort of thing?
[Nexus 6  Original Android Development] Yank555:
ROM Update

Maintenance update to SlimLP beta 0.9

Slim-shamu-5.1.1.beta.0.9-UNOFFICIAL-20151008-2220.zip

- repo sync Thu 8. Octobre 18:15 CET 2015

- (hammerhead) fix zswap not activated to a SELinux issue (Yank555.lu)

- fix stock mms app (prbassplayer) - there may be some issues left, but SMS/MMS work on my end

- mobile data tile back to more stock behaviour (Yank555.lu)​

Download Link AFH

Download Link D-H

Full changelog & my BC OP Link

JP.
[Nexus 6  Original Android Development] x111:
with this update, "xposed-v74-sdk22-arm-by-romracer-20150911" doesn't work.

after flashing it, got frozen boot for at least 10 min with overheat.

with "Slim-shamu-5.1.1.beta.0.8-UNOFFICIAL-20150927-2313" everything is working.
[Nexus 6  Original Android Development] rrrrrrredbelly:
Same here. Wiped system/cache before installing rom, gapps, etc. Rom booted up fine. Back to recovery and flashed xposed zip and was stuck in slim logo. Restored twrp backup.

Thanks
[Nexus 6  Original Android Development] __NBH__:
There is a v75 of xposed have you tried that?
[Nexus 6  Original Android Development] x111:
"Slim-shamu-5.1.1.beta.0.9-UNOFFICIAL-20151008-2220.zip"

with

"xposed-v75-sdk22-arm.zip"

everything is working fine.

...
[Nexus 6  Original Android Development] PerfectSlayer:
Hi [MENTION=2033478]Yank555[/MENTION]

In your previous maintenance update (0.8), my shamu become back slow.. Camera is slow, lockscreen too and global responsiveness is bad. :(

Have you changed something in camera fix? Thanks!

P.S. I'll test 0.9 as soon as I could ;)

Envoyé de mon Nexus 6 en utilisant Tapatalk
[Nexus 6  Original Android Development] Yank555:
Negative. no changes there ...

Check CPU freqs and GPU freqs, just in case...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] PerfectSlayer:
Thanks I'll do it. What are the expected default value of your kernel? Or where can I find it?

Envoyé de mon Nexus 6 en utilisant Tapatalk
[Nexus 6  Original Android Development] Yank555:
JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] PerfectSlayer:
My GPU frequency is only 300Mhz. I never use app or script to change it. Why?

I'll set it to 600mhz as you and hope it'll help. Thanks!

Envoyé de mon Nexus 6 en utilisant Tapatalk
[Nexus 6  Original Android Development] Yank555:
This sometimes happens, it will get stuck at some freq. lower than stock 600.

I set it to 600 in the kernel config script after boot, that does the trick 99% of the time...

When it get stuck it mostly happens when app optimising takes place on first boot after rom flash.

Had no time to dig into why this happens so far :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] PerfectSlayer:
Good to know! No problem if it's a known issue and there it a workaround ;)

Envoyé de mon Nexus 6 en utilisant Tapatalk
[Nexus 6  Original Android Development] Yank555:
Anyone running into issues when using the camera from within apps (like to take a pic from within messenger to send it ?

My phone tends to become unresponsive for quite a bit, like 1-2 mimutes...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] Andromendous:
Working fine here. Im using hells core tho
[Nexus 6  Original Android Development] Yank555:
Wellit used to work, and there's been no kernel change lately...

Hmm ... always sth ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] DroidIt!:
+1 Juba's gonna be busy I think...Kufi's pushing for COS :)
[Nexus 6  Original Android Development] letmedanz:
I concur.

Had to flash Elemental X to get it to boot...
[Nexus 6  Original Android Development] TONY206:
I had the same issue. Didn't try another kernel yet.
[Nexus 6  Original Android Development] renny083:
If you do not get past boot and for the other's who posted before this post with same issue[MENTION=3192189]TONY206[/MENTION] this is exactly what I did....

1.)First I wiped system along with factory reset, cache.... 3 times just to be sure.

2.)Next then flashed SlimLP Rom latest v.8,

3.)Next then flashed Sensei v R19 kernel(Found HERE)

4.)Last then flashed latest gapps I used Slim_mini_gapps.BETA.5.0.x.build.0.x-424.zip

Mine booted up fine running perfectly hope this helps.
[Nexus 6  Original Android Development] DroidIt!:
Did you guys try wiping cache/dalvic after flashing? Don't know if it'll make a difference or not, but RobbieL (1+ slim dude) said to not wipe after flashing and before booting or you may not boot. Kind of a shot in the dark, but an idea :)
[Nexus 6  Original Android Development] Smallsmx3:
Davlik doesn't exist on this device
[Nexus 6  Original Android Development] JaylanPHNX:
When you wipe dalvik in recovery, you're really wiping runtime cache. It was just always labeled dalvik cache before ART and the recoveries haven't really changed the labeling yet. At least that's my understanding.

From my SlimTab Pro 8.4
[Nexus 6  Original Android Development] bikeryder007:
Whoa, Slim totally saved me today at work. I am a health insurance agent working on a December 15th deadline. We are signing up people on new plans right and left trying to get them all in. After lunch today, our cable internet went down. Nothing worked. We had people lining up in the office and no way to sign them up, as it is all done online. I never use the tether feature on my phone, but I grabbed it in a panic, set up the hotspot, tethered it to my laptop, and signed them all up on lte. It worked perfect, and saved me a ton of time and headaches. Thanks. :good:
[Nexus 6  Original Android Development] aoaleman:
Wow! Awesome!
[Nexus 6  Original Android Development] kufikugel:
So I see here are all my n5 guys :D

Well will subscribe this thread hehe
[Nexus 6  Original Android Development] TONY206:
Flashing lean kernel worked just fine now.
[Nexus 6  Original Android Development] flipmoder7:
Google camera is now fc on hdr+, even the the "motorola" edit in build prop. Camera was working on alpha build 7.
[Nexus 6  Original Android Development] freebee269:
flashed the .8 today and i have that mms issue. i can send sms fine but receiving an mms doesnt work. the download tried to go but it just fails. and yes i'm on lte setting and yes my apn settings are right for at&t.
[Nexus 6  Original Android Development] Rauch:
The legend still exists. ?
[Nexus 6  Original Android Development] ocbrewing:
Did you reboot after the build.prop change? I had the fc, then changed my build prop and it's working fine.
[Nexus 6  Original Android Development] apascual89:
That happens with the Google messenger app, right? Can you check if works fine when you set the default to the aosp messaging app that's included with the rom?
[Nexus 6  Original Android Development] kufikugel:
Of course......I will survive forever :p

Just saw you requested me for IRC......I will come tomorrow.......3am here and I need to start to learn sleeping early lmao

Night :D
[Nexus 6  Original Android Development] Rauch:
Fair enough :) Word travels quick. I've missed my Deutschbag. :D :D :D :D
[Nexus 6  Original Android Development] aalopez10:
new alpha .8 seem to me density much smaller or am i going blind lol my first nexus dont mind me.
[Nexus 6  Original Android Development] Mrbobrowitz:
Just answering this question, yes MMS doesnt work in the Messenger app, but the AOSP MMS apk that is built into the rom works just fine for sending a receiving messages.
[Nexus 6  Original Android Development] Andromendous:
I have a feeling the great yankavich will figure it out[emoji12]
[Nexus 6  Original Android Development] Yank555:
About camera issues, can you give this test-build a spin ?

Slim-shamu-5.1.1.beta.0.9-UNOFFICIAL-20151013-2109.zip

In certain circumstances I ran into unresponsiveness (as I posted yesterday), seems fine now (but need to test after longer uptime still)...

Thanx, JP.
[Nexus 6  Original Android Development] PerfectSlayer:
Yes, it happens me sometime.

For sure! I'll give it a try today and report few days later. Thanks for your investigation about it :good:
[Nexus 6  Original Android Development] danarama:
No one replied to me, so is it safe to say no one has issues with lag and jerkyness on more intensive games after playing for a while?
[Nexus 6  Original Android Development] JaylanPHNX:
I imagine that's just a natural result of thermal throttling.

From my SlimTab Pro 8.4
[Nexus 6  Original Android Development] Yank555:
I'd tend to agree, but if it's not happening with older builds, it sure is weird...

But I can't (thus didn't) comment as I don't play games on my device...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] danarama:
I'd have thought so too, but I have throttle temp raised and cpu Max has not changed when this happens.. It only throttled when I put power cable in.

I might be wrong, it is happening on 0.1 too, though its less noticeable.
[Nexus 6  Original Android Development] Yank555:
There are apps that can show thermal throttling history, like fauxclock.

Worth having a look when that happens...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] danarama:
It's definitely not throttling. Throttling sets my Max cpu lower but it isn't changing. I check it in elemental.x kernel app.. I can see when it throttles
[Nexus 6  Original Android Development] Yank555:
Throttling can also remove cores and gpu might also get throttled (though now I think about it, I never cared to check if stock kernels/modecision does throttle GPU).

In Intellithermal you can also start by removing cores before lowering max. freq.

Other reason could be memory pressure (memory leak ?).

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] danarama:
These are all things I check. I dont use mpdecision.. Custom hot plug forcing all cores online whilst gaming.

This is the screen I check when playing..

So all that info is available.. I'm really not sure what's doing it...

I'm using an M kernel now to address other issues but not still happens.

Just not sure what's going on anymore.
[Nexus 6  Original Android Development] Yank555:
Weird, looks normal there, 44 is pretty cool ...

Maybe you already said it, but this also happens on other kernels ? Wild guessing here...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] danarama:
Yeah, it was happening with yours too on the later builds (0.6 / 0.8) but not tested on .0.1

Screenshot is from now btw, not gaming. It's usually around 57 when gaming, which is under stock throttle but I set my throttle at 85 anyway.
[Nexus 6  Original Android Development] Yank555:
Wilder guess, can you give the testbuild a spin ?

Kernel is quite different !

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.3a kernel.
[Nexus 6  Original Android Development] danarama:
Will do.. I'll flash it today.
[Nexus 6  Original Android Development] Smallsmx3:
Been searching to no avail. Is 6.0 being worked on mellowslim or squishy slim? slim?
[Nexus 6  Original Android Development] danarama:
I would expect so, though it would be some time before it seems light of day.
[Nexus 6  Original Android Development] Smallsmx3:
So basically when the next version of android is available
[Nexus 6  Original Android Development] :
Well lollipop was out last fall and we had early SlimLP builds in December. I'd hardly call that a year (when M became available) so please don't exaggerate. Also from L to M the changes are much less drastic so it will probably be quicker than last year.
[Nexus 6  Original Android Development] Smallsmx3:
We had 5.0 builds. 5.1 was a disaster with all the different carrier builds. I'm glad that 6.0 brought everything back together. I just feel like sliM will get back to its former glory....