yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Natakranta:
Bad news for Dan.

Not compatible on Slim-bacon-5.0.1.alpha.0.7-UNOFFICIAL-20141206-0718 with Slim_mini_gapps.BETA.5.0.x.build.0.x-415

I clean flashed it yesterday as second secondary ROM :)

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] chikimonke:
But the other app you suggested does show as compatible? Because I get the incompatibility for both.
[ONE Original Android Development] dankoman:
Yay.

I'll make the smali hacks more aggressive and do another gapps today.
[ONE Original Android Development] Natakranta:
Sorry for not being specific. I updated my previous post.

Both incompatible in SlimLP clean flashed.

Both compatible in SlimSaber LP dirty flashed.

Slim_mini_gapps.BETA.5.0.x.build.0.x-415

used in both cases.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] chikimonke:
Thanks Dan! Any idea if we're going to have to clear data on Play Services and all that crap, or should we be able to just flash and go?
[ONE Original Android Development] carpdeeem:
I'm still on SlimKat, but would a 3rd party app like this work on SlimLP until double tap is reintegrated? I use it on my tablet and it works (reasonably) well enough...

https://play.google.com/store/apps/details?id=net.maicas.android.wsleep
[ONE Original Android Development] dankoman:
Probz have to clear play store, services, and framework data, and remove/re-add google account.
[ONE Original Android Development] martinoff:
Thank you [MENTION=1277872]dankoman[/MENTION] downloading 416
[ONE Original Android Development] bundys:
Screen not waking up on call

Have been out of cell range for a couple of days, but now that I'm back home, have noticed three calls today where the screen didn't wake up when receiving a call. Anyone else seeing this? I'm on 5.0.1A0.7.
[ONE Original Android Development] chikimonke:
Yup, I've been noticing that as well. Do you have "Settings>Display>Prevent accidental wake-up" set to on? I do, I'm wondering if that's some how related.

Edit, Just tried it out, that setting is the culprit. If you get a call while there's something in the Prox sensor's range, the screen won't turn on, even after you remove it from your pocket (or in my test case, remove my finger from the sensor) If the phone is just sitting on the desk, the screen wakes up just fine with that setting set. If you turn that setting off, the screen wakes up as expected as well. [MENTION=4911350]RobbieL811[/MENTION] , I think there needs to be something added to that feature that if a call is incoming, but the proximity sensor is active (phone in pocket) then keep the screen off, but if the call is still incoming and the phone is removed from the pocket, turn the screen on. Hope that made sense.
[ONE Original Android Development] bundys:
Yup, confirmed.
[ONE Original Android Development] f100cleveland:
[MENTION=4790322]kufikugel[/MENTION] [MENTION=4911350]RobbieL811[/MENTION] Is it a known issue that voicemail notifications don't show up on the statusbar? I just checked mine and I had 3 that I didn't know about from yesterday and I had that issue last week too. Oh yeah, this is on SlimLP.

Thanks
[ONE Original Android Development] jdavis7882:
[MENTION=2875820]f100cleveland[/MENTION] that issue is not exclusive to slim it's on any 5.0 rom. I'm sure the devs are aware of it and a fix is in the works..
[ONE Original Android Development] RobbieL811:
I'm glad that you chimed in w/ this. I just spent from the time that he posted til now searching for commits. Lol. Thanks!!! Are you sure of this???
[ONE Original Android Development] jdavis7882:
Only an observation from using every lollipop build on XDA lol. As far as a commit there may be one out there but I'd assume it would've been merged by now. Good luck on that search!
[ONE Original Android Development] geowolf1000:
Deleted
[ONE Original Android Development] RobbieL811:
We don't have any ambient light feature.

Sent from my 1+1
[ONE Original Android Development] MyDarkThrone:
Ignore everything you read out there. I used CM11S for almost 2 weeks and the ROM is stable. I had no problem either FC or anything, I did not have a single problem. I just do not feel fast enough for my taste. I love the speed above all else, for that reason I kicked my S4 and buy a Nexus and I put the two more fast for me LiquidS and Slim.

For me, stability is important but so is speed. I understand delays in Galaxy Young, but not in a terminal like this.

The theme engine is welcome but not essential. But now that I have bought I would use it in my favorite ROM. If tomorrow SLIM launch a compatible theme engine would be perfect, but if not then I would welcome with open arms just because they expand enough customization possibilities. Because let's be honest and realistic today TheRealDark is nothing new, almost all ROMS offer DarkUI and anyone can download blackened Gapps.

Without going any further,there are themes like DarkMTRL that do the same that TRD.

And PLEASE I not want that all you understand this like something bad. [emoji120][emoji120][emoji120][emoji120][emoji120]

I only want talk about like always go more further. OK?
[ONE Original Android Development] drakester09:
Is nothing new now, but all other roms pretty much got 'their' dark mode from Slim's TRDS implementation.
[ONE Original Android Development] MyDarkThrone:
Yes. I know. But if others look to you to match you. Because you can not look to others in order to re-take the lead?

---------- Post added at 07:51 PM ---------- Previous post was at 07:33 PM ----------

And do not misunderstand me. I love the TRD. The first day I saw him I fell madly in love with him. If you look closely my avatar you will see right away that I love the black and white.
[ONE Original Android Development] RukusX7:
The thing each and every last one of you need to understand is that slimroms have been here since at least the i9000 days. Have a look at their offered previous features in other roms. Have a look at their design model. Think of where they want to be and where they will go. This is literally one of the most amazing popular devices of the year that is literally meant to have a custom ROM.

Look, think, put it all together. Be patient.
[ONE Original Android Development] MyDarkThrone:
If we were not patients would not have a OnePlus[emoji16]

Here we are seeing day by day the evolution.
[ONE Original Android Development] DespairFactor:
Why is the default governor interactive and not slim?

EDIT: Nevermind, I see why.
[ONE Original Android Development] wp7chris:
Stop lying to yourself cm11s is cluttered with force closes, crashes, and lags making an unusable rom.
[ONE Original Android Development] RukusX7:
Go make a bug report there. This is the slimkat thread.
[ONE Original Android Development] MyDarkThrone:
What!? Oh man if you have these problems you should start thinking about selling your OnePlus because this defective
[ONE Original Android Development] DespairFactor:
Are you sure you even have this phone? There are nearly no bugs on CM11S, slimkat is just a lot smoother on the device.
[ONE Original Android Development] chikimonke:
Sorry guys, my comment about CM11 before was not meant to start a flame war on CM. What CM has done for the custom ROM community can not be stated enough. That said, nobody is perfect, not even Slim. Keep in mind that the beauty of Android and phones like the 1+1 is the ability to choose what best fits your needs and wants. No one is wrong or dumb or delusional for wanting to use a certain ROM, just different. Now let's get back on track.
[ONE Original Android Development] MyDarkThrone:
No problem on my part. Also it's always nice to discuss with people here on these issues. Not with everyone you can talk about ROMS and phones. What would we be without this kind of exchange of views?
[ONE Original Android Development] RukusX7:
I really enjoy Slim. I like how minimalistic it is. It sends a message to me that the slim team has carefully chosen what goes into their ROM. Although I admit this is quite biased, as I prefer to be more minimalistic.

---------- Post added at 07:18 PM ---------- Previous post was at 07:11 PM ----------

In your slim governor, I noticed that any frequency parameters you could set, are set to 300000. ie: optimal_freq, sync_freq...

Why was this chosen? I've been trying to understand the most about governors as I can.
[ONE Original Android Development] DespairFactor:
I believe its to ensure that it runs at the lowest frequency possible when more processing power is not required.

[MENTION=3478918]rukusx7[/MENTION] are you using it? Do you notice your phone not deep sleeping when using the slim governor?

EDIT: Nevermind, it is sleeping, just took a little longer than interactive to sleep.
[ONE Original Android Development] playya:
Question - I know we mentioned this before but I am having issues with bluetooth and my Car audio. It seems stock works fine as I nandroid back to check it out and did not have a chance to take a bug report. OP can you tell me if bluetooth on AOSP is different than on CM since it seems to be evident on all AOSP roms for me.

Also if anyone else has this issue let me know as well. I have a Honda and bluetooth is built in.

Thanks in advance
[ONE Original Android Development] latenightchameleon:
I'm using mine in my toyota with no problems, what issue exactly are you having?
[ONE Original Android Development] playya:
its a 2013 honda and it FC's after it connects and tries to sync the phonebook. If I do get the FC's to stop when I make a phone call its choppy on the other end and most cant hear me at all. Tested it with stock rom and like I said stock rom works fine...
[ONE Original Android Development] kufikugel:
Strange. Works fine here as well. Can you take a bug report please of it?

Well and yes the BT stack is very different. Aosp ones is way more basic and more important more universal across all devices and usually more stable. At least this is our experience with it. Or do you mean the difference code wise?
[ONE Original Android Development] playya:
No that's what I meant. Yeah it sux that every AOSP ROM I try gives me that error and the ROM I wanna run keeps FC on me. You got it I will try and get a bug report for you.
[ONE Original Android Development] sshinde555:
Hey can any body confirm whether the Wakelock blocking through Privacy Gaurd as Keep wake off is working for any one. as twice clean install the device is not able to sleep due to IBM lotus traveler app, has to use exposed module to block it,

Please somebody confirm the same, even i try to off the location service of google map through Privacy Gaurd & restart the device but the device is able to report the exact location of mine..................
[ONE Original Android Development] bundys:
Is there any reason why we don't have a separate thread for the 5.0 stuff? Some comments are starting to get confusing in regard as to which build they are referring to - and this is a 4.4 thread after all.
[ONE Original Android Development] RobbieL811:
This is the thread. Figure it out for now. A little reading never hurt. It will be a little confusing for the next few weeks I admit, but I don't think another thread is necessary right now. It's not that hard for me to decypher. And the title will be changed when we officially switch to LP nightlies.
[ONE Original Android Development] lemonspeakers:
Can't wait for an official release of SLIM-POP
[ONE Original Android Development] martinoff:
Never will be one as SlimPop doesn't exit :P

Sent from my super dupah futurephone
[ONE Original Android Development] chikimonke:
SlimLP
[ONE Original Android Development] RobbieL811:
I don't know how everyone thinks that is the name??? Lol.
[ONE Original Android Development] chikimonke:
KitKat:SlimKat as Lollipop:SlimPop It was the natural assumption, but Slim threw us a curve ball. Some said SlimPop had not too good meanings in some language/s but never heard an actual explanation. Either way, in a month we'll all just be referring to it as Slim anyway.
[ONE Original Android Development] indian84:
I guess SlimPop means Slims*x or something similar in German. Remember Tylog saying..
[ONE Original Android Development] ptr_hamilton:
There was an explanation. In the beginnings of slimroms the used to call their roms this way. I remember SlimICS - not SlimSandwich :D - and yes I think the language issue also pushed the decision a bit.
[ONE Original Android Development] chikimonke:
But wasn't it SlimBean? [emoji4]
[ONE Original Android Development] tracerit:
(slimkat question) are the navigation button icons changeable?
[ONE Original Android Development] inffy:
Yes
[ONE Original Android Development] Nibb31:
Yes.

I can't live without that feature (with the target ring slide used as a quick launcher), so I'm using SlimKat until that feature is ported over to SlimLP.
[ONE Original Android Development] tracerit:
nice clock font, what font are you using?
[ONE Original Android Development] indian84:
Exact reason I am back to SlimKat. I tried really hard for a day to get used to capacitive buttons and the AOSP softkeys. Got fedup and flashed SlimKat back..

Kufi was in the thread couple of days ago and he confirmed that he is working on it. Won't be long I guess.
[ONE Original Android Development] Nibb31:
Lato. It's the one used by the stock CM11S Hexo theme.
[ONE Original Android Development] ralpheboyo:
Did a build this morning... Tapatalk now FC when opening.... Just a heads up...
[ONE Original Android Development] ptr_hamilton:
Yes it was, that was the first time they changed the naming. Don't know why. But before they had it like now
[ONE Original Android Development] wozn:
Loaded up the newest slimsaber build 1209 to test the email fix. Still crashes on opening any emails while in combined view. Clean flash with latest slim gapps. Did you need a new logcat? if so find attached. Thamks agian to the Slim team!
[ONE Original Android Development] Natakranta:
I've just got an email:

But now - no invite needed, till stock lasts:

https://oneplus.net/

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] ralpheboyo:
Player pro FC.....

(Clean install)
[ONE Original Android Development] fireforhire:
Seeing the same thing on newest weekly.
[ONE Original Android Development] JaylanPHNX:
Hammerhead got a new alpha (.8) today with lockscreen shortcuts. Can anyone hear the bacon sizzling?

From my SlimTab Pro 8.4
[ONE Original Android Development] chikimonke:
Those are good and all, but did you see what [MENTION=4911350]RobbieL811[/MENTION] was working on last night? This, this, this and this.

Here's hoping a new build is coming soon with these baked in :D
[ONE Original Android Development] ralpheboyo:
[MENTION=4790322]kufikugel[/MENTION] ....could yo pls take a look...?? device soft booting left and right....:(
[ONE Original Android Development] JaylanPHNX:
Oh god, yes! I need those like crack.

From my SlimTab Pro 8.4
[ONE Original Android Development] pippoaacc:
Anyone else has to trigger the recents two times to get the last activities shown?
[ONE Original Android Development] chikimonke:
SlimKat or SlimLP. On SlimLP, no, I do not.
[ONE Original Android Development] pippoaacc:
Slimkat. First time i see the apps that were there when I opened the panel the previous time, next time I find the apps at the moment.
[ONE Original Android Development] Sir_gpm:
Is possible to disable the capacitive keys?
[ONE Original Android Development] shadeofgrey:
With a flashable zip that's floating around this thread, yes. You'll have to just disable the key backlights after flashing it. It was posted a few pages back.
[ONE Original Android Development] Sir_gpm:
Use that zip but now my power button does not work.
[ONE Original Android Development] chikimonke:
Are you on KK or LP? I believe that zip is only for KK, not sure what it would do on LP.
[ONE Original Android Development] shadeofgrey:
I forgot to ask that as well.. I had used that zip on an earlier version of lollipop, but not slimLP. I'm not sure whether it would work.
[ONE Original Android Development] ralpheboyo:
Crapatalk... Cough... Mean Tapatalk is working as of today.... So friggin strange... Music is a hit or miss... Sometimes it works... Sometimes it doesn't... When it doesn't work (player pro) will open... Press play... Nothing happens... Cant close/exit... After some time.. Message comes up.. Wait / close / Yada Yada Yada.... Once you choose the app will close... And after a few minutes a soft reboot will happen... (all that should be in the logcat... I hope... Lol)...

(I attached logcat in the original post)...
[ONE Original Android Development] Natakranta:
If you only attach it ;P

Edit

About the music bug, see the screen I made today.

I haven't had a chance to test it yet. I'm back on primary SlimSaberKat, battery life is way better than on LP

Edit 2

And who forgets to attach...

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] Andrew025:
I think it's a Tapatalk issue, as it suddenly started FCing on me and I'm on a few week old Slimkat.
[ONE Original Android Development] shadeofgrey:
They added ads...or is that just for me?
[ONE Original Android Development] indian84:
That's what Ad Block is for. :P
[ONE Original Android Development] Andrew025:
I'm using adaway.
[ONE Original Android Development] Vonnegut:
A few pages ago, i posted a very simple zip for KK. The other 2 zips are made for LP and they both remaps both the hardware and the capacitives button....and they takes away the WAKE command to power button too.
[ONE Original Android Development] shadeofgrey:
Well yeah, but I was just thinking that could have been a cause for Tapatalk crashing? :)
[ONE Original Android Development] inffy:
I am trying to build SlimLP build for oneplus. I just never get it to build the actual zip and the building just stops/crashes.

my local_manifest looks like:

I need to use the caf branch for the bacon right?

so I did

repo init -u git://github.com/SlimRoms/platform_manifest.git -b lp5.0-caf

and

repo sync

then I issued: breakfast bacon and brunch bacon

Am I missing something here or doing something wrong?
[ONE Original Android Development] ralpheboyo:
click on Sig Pic to take you the SBC thread...you can also post there...

In short the steps are correct...however your proprietary files does not look 100% (once again see OP of SBC thread...has most common proprietary for devices)

Its also a good idea to pastebin your WHOLE output from the terminal so we can help....

Welcome to the building club....:highfive:
[ONE Original Android Development] chikimonke:
Hi [MENTION=4790322]kufikugel[/MENTION] and [MENTION=4911350]RobbieL811[/MENTION] Did something get removed by accident from SlimLP? I swear I was able to make my phone not vibrate for calling and notifications not too long ago, now I can only turn it off for phone calls. I have Tasker set up to make my phone silent when connected to my pebble, as there's no reason for the phone to make noise or vibrate, I get to the notification on my wrist. And even within tasker now, the option to toggle notification vibration says it's not available on my phone. I'm positive Tasker was able to do this on earlier versions of SlimLP. Ringer vibration disables and enables no problem, sound enables and disables no problem, but I get notification vibration no matter what I try.

Side note, I'm really not a fan of how Google has setup sounds and notifications, it's actually rather confusing now as to what notification you will and won't be getting.
[ONE Original Android Development] indian84:
+1
[ONE Original Android Development] K Rich:
I <3 Slimkat
[ONE Original Android Development] fusionjack:
that is the audio issue that our device has. it can be triggered from some third party music players or games. once it hits, you need to reboot so that any other actions that use audio is working again. otherwise you'll always get ANR dialog or fc.

it is easy to notice when this issue is hit with touch sound. if you enable it, you won't hear touch sound when you click app in home screen.

so far only poweramp is free from this issue.
[ONE Original Android Development] inffy:
nevermind :)
[ONE Original Android Development] ralpheboyo:
Super stuff [MENTION=1228651]fusionjack[/MENTION] thxs! just in case also hammering playerpro with bug reports ;)....
[ONE Original Android Development] fusionjack:
it's our side issue. as i read, it's qcom thing.

google music is also broken...but streaming with bt seems fine. someone or [MENTION=2495716]chikimonke[/MENTION] has reported it. can't remember who...
[ONE Original Android Development] RobbieL811:
Also, it is not affecting only our device. The problem is on some other devices as well.
[ONE Original Android Development] Ankru:
Our device with your cm build is working fine with Google music and Video playback.

---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------

[MENTION=4911350]RobbieL811[/MENTION]
[ONE Original Android Development] RobbieL811:
I know. It's a Slim problem.

Sent from my 1+1
[ONE Original Android Development] Ankru:
I switched for a try to cm, because your slim build 0.7 had much random reboots. Hopefully next build is more stable. Will wait so long.[emoji4]
[ONE Original Android Development] RobbieL811:
I'm not sure what you're talking about Lol. I haven't gotten 1 random reboot on L so far. Reboot wise, all of my LP builds have been stable. At least for me anyways.

Sent from my 1+1
[ONE Original Android Development] Ankru:
O.k. then i have to do an absulutely clean one.
[ONE Original Android Development] kantjer:
Running Slim LP now for about 2 week, not a single RR
[ONE Original Android Development] Ankru:
I have played once with kernel settings. I think thats my fault.
[ONE Original Android Development] RobbieL811:
I like the festive avatar kantjer. Lol. Same for me w/ the random reboots. Prey much CM kernel w/ Intelliplug & a few other little things like that.

Sent from my 1+1
[ONE Original Android Development] kantjer:
That was a great hit last year on the Slim S4 threat, a lot of users pimped there avatar then. So why not try to make it popular on the OP thread as well :D
[ONE Original Android Development] fusionjack:
i thought cm also has this problem and i just wait till cm fixes it...:eek:

now i'm starting to worry :(
[ONE Original Android Development] kantjer:
Don't loose any sleep over it ;)
[ONE Original Android Development] Ankru:
Actually i try Robbies cm and there it is fine with Google music.
[ONE Original Android Development] fusionjack:
if i commit something that it shouldn't to my github, then you know what happens :p

did you use google music with headset, bt or speaker?

[MENTION=4911350]RobbieL811[/MENTION]: do you know which other devices that have this audio issue? perhaps we could know the link between them...
[ONE Original Android Development] kantjer:
Yea, I loose sleep over it, trying to figure why the build erros out and what I did wrong :D
[ONE Original Android Development] chikimonke:
Yup, it was me. Haven't experienced the issue once with BT. I don't think streaming vs local is a factor though. When I try to use headphones at work, streaming or local will work for a little bit, but it always cuts out eventually.
[ONE Original Android Development] inffy:
Same here. I even did a new build today morning and still my OPO does random reboot and very often.

It's strange because everyone else are having a rock solid build.

I need to test with my brand new Nexus6 today
[ONE Original Android Development] Ankru:
With headset and speaker- both stop after 2 seconds musicplay and freeze google music app.

---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------

Many of my reboots were related to the usage of camera, gallery and sometimes during sleep.
[ONE Original Android Development] pippoaacc:
Sorry if I repost, but noone has experienced a decrease in fps with heavy 3d games in comparison to cm11s due to the fact that filters are enabled that are not so in cm11s? Raising the dpi does not help.