yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] cam30era:
FWIW: AT&T Next plan.

No subsidized phones

. 3 smart phone lines and one flip phone line. Unlimited voice and text. 10gb/month. $150. And this is not a promotional offer.

I'd suggest you might want to look at the AT&T website and price out the Next plan yourself.
[ONE Original Android Development] nhshah7:
@

Then definitely look into the next plans. You don't have to buy a phone through them to sign up, they're just excluding and separating the cost of subsidizing a phone through contracts so you could save $20-30 per line per month! (And yeah I expected you'd have bought your devices outright hahah)

On topic: last build seems solid, nothing sticks out to me and no lag or random reboots. Also have noticed that on hotspot, it doesn't update and tell me when devices are connected (just says no devices connected). I can get you a log if you want later. Can't wait for the new build!
[ONE Original Android Development] RobbieL811:
Thanks for the tips on the AT&T stuff guys. I guess it's time that I call them and re evaluate my service plan! Sounds like I might be paying too much!!! On another note, I have the new alpha ready to test w/ the new msm_mpdecision, in a little different implementation this time! Test the crap out of it and let me know how it works. I think we might have a winner this time. [MENTION=3685904]ak[/MENTION] is using the same code in his kernel and he is reporting good things to me!!!! Anyways, here it is!!!

ROM - Server 1

ROM - Server 2

GAPPS - Server 1

GAPPS - Server 2 - Look for new GAPPS update tonight on both servers. Danko told me he is doing some gapps work tonight.

SuperSU - http://104.237.50.75/SuperSU/
[ONE Original Android Development] nhshah7:
No need for clean flash? (I always wipe system cache and dalvik)
[ONE Original Android Development] RobbieL811:
Wiping system, dalvik, and cache should be fine.
[ONE Original Android Development] Natakranta:
Dirt flashed over Jan.07 build with Slim mini gaps Jan.13 and SuperSU 2.44.

Ready and set up for tomorrow. I'll give it a spin and report in the evening.

I don't have any karnel tweaking app. If I leave it on default as flashed, will it be running the new things you added to karnel?

Or do I have to turn this msm_mpdecision on?

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] RobbieL811:
I THINK that I have it set up to be enabled by default. I would advise you to check on that though.
[ONE Original Android Development] Natakranta:
OK, I'll install Synapse. Which UKM do you use? Official UKM_v3.6.1.zip ?

Or ak's UKM_v3.6.1.1_Special_Ed.zip ?

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] RobbieL811:
I use the one that's on my server.

http://104.237.50.75/
[ONE Original Android Development] Natakranta:
OK, that's official by apb_axel

Thanks for quick reply!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] RobbieL811:
No problem.
[ONE Original Android Development] Natakranta:
I've just flashed ukm and installed Synapse.

That's default setting - see screen shot.

MPDecision on top is ticked

Intelliplug is disabled

MSM MPDecision is ticked

Is it how you want it to be tested?

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] RobbieL811:
Something is wrong w/ what you've got going on there. You shouldn't have mpdecision on the top. Hang on and I'll post a pic for you. That selection should not even be there. You didn't flash another kernel did you?
[ONE Original Android Development] Natakranta:
No. All stock.

I'll untick MPDecision on top then.

I doubt that it's being secondary on multiROM can have anything to do with it? I mean me having this option when it shouldn't be there?

Or is it because of dirty flash? I can't wipe system in secondary ROM, only cache and dalvik.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] RobbieL811:
What's up guys. Here's a new build. I think it fixes the color issue. Also, let me know if the battery life is any better.

ROM - Slim-bacon-5.1.1.beta.0.1-UNOFFICIAL-20150714-0743

GAPPS - Slim_mini_gapps.BETA.5.1.build.0.x-20150709
[ONE Original Android Development] indian84:
You the man...

EDIT - Just flashed and the Yellowish tint is still there.. :(
[ONE Original Android Development] samaritan16:
Going to flash it now [MENTION=4911350]RobbieL811[/MENTION]

Will share my experience soon!
[ONE Original Android Development] paras33:
i never had any yellowish issue ... just came on this rom tody after hearing about it from many ppl.... just flashed latest build and it was working fine until i disabled ambient display and very first time my screen got yellow tint.... n it has stayed like that since then..
[ONE Original Android Development] samaritan16:
I dont think the yellow tint is there anymore.. At least from my initial view.. At times the mind plays games!! I hope I'm not wrong here.. Will confirm tomorrow again when I see it in the day time! Also will get back on battery (esp overnight drain)

---------- Post added at 10:44 PM ---------- Previous post was at 10:18 PM ----------

@robbiel811

I definitely dont think there is a yellow tint now.... But did get a random reboot.. Will let it to use for a day or two..
[ONE Original Android Development] paras33:
im having phone off in idle state.. had to hold power key.. came from exodus clean flash

any firmware or spl instrctions needed plz tell?
[ONE Original Android Development] indian84:
You are either bluffing or you have two phones. Because you posted same thing in SlimSaber thread...
[ONE Original Android Development] kantjer:
Lol, my thoughts exactly
[ONE Original Android Development] paras33:
oh sorry my bad... posted in slim saber rom thread by mistake... even i was wondering whr did my post go.... can you help me with this problem... phone is on but screen doesnt wake up ...had to force reboot to use it

---------- Post added at 12:41 AM ---------- Previous post was at 12:39 AM ----------

thx for reply guys...sorry to bother
[ONE Original Android Development] indian84:
I haven't faced anything like this. Did you undervolt?
[ONE Original Android Development] Chris.C:
I am having an issue with mobile data turning off when my Wi-Fi is turned off.

Both switches are on , I do not have data usage limits activated and my my mobile usage is way below my plan. I have reset my apns.

I have tried turning on safe mode to take out rouge apps but still the same

It is as if the ROM has turned it off mobile data the in non wi-fi mode

I am on the latest build, guess will have to wipe and reflash.
[ONE Original Android Development] RobbieL811:
Mobile data is supposed to be disabled when WiFi is enabled. That's how it's supposed to work. Why do you want mobile data enabled when you have wifi enabled? You want to use WiFi, not mobile data.
[ONE Original Android Development] abhibnl:
Do you mean both WiFi and Mobile Data switches are ON? If that's so then obviously wifi will connect(if you are in a access point's range).

Well Robbie in his first line he mentioned that "mobile data turning off when wifi is off" so that seems like his issue. But in the very next line he mentioned "both switches are on". That actually is not making sense to me.

Sent from OnePlus One
[ONE Original Android Development] therahmaniac:
I suppose what he mentions is if You have both wifi and mobile data enabled, if wifi is connected, Only Wifi will be implicitly made use of (Effectively disabling mobile data rather than a visible disabling on the mobile data settings ).

---------- Post added at 12:13 AM ---------- Previous post was at 12:07 AM ----------

Hey Robbie! Is there any contexts where the ROM changes the min, max frequency of the CPU other than reboot. ? I use Tasker to change governors and set frequencies. Setting of CPU min frequency doesn't work for cores other than the first core (core0) mostly. Occasionally it gets changed in more cores but after a while i see them to get back to '1267MHz'.? Any thoughts?

Thanks for the awesome ROM man!
[ONE Original Android Development] Chris.C:
The issue is with WiFi off even though mobile data is switched on the system will not allow me to connect to the Internet etc.

I have fixed the issue by toggling through LTE, 3 and 2g. while not on WiFi and I now have a connection in mobile data.

Sorry for the confusion something got out of whack
[ONE Original Android Development] inffy:
Huge Wakelock from Phone/RILJ on the newest build.
[ONE Original Android Development] paras33:
ok guys i managed to get rom working fine by flashing firmware but yellow tint is still there...

also main problem is double tap to wake is not working normally...it wakes with tap only when there is notificaion else only double tap to sleep works n i had to use hardware key.. i re checked under settings but no solution i can find
[ONE Original Android Development] Rd. Vortex:
I was getting the same couple of builds back when on WiFi. Disabling mobile data solved the problem for me. Never happened while I was on mobile data only though.
[ONE Original Android Development] deltatux:
I've been getting quite nasty drains since the July 4th build... Thought there's an app that's been eating the battery but it's been Android OS doing so... Phone fails to go to deep sleep half the time even though it's idling most of the time...

This screenshot is taken from the July 4th build. The battery drain was worse on the July 12th build. On the right side, it's the screenshot that I just took. Deep sleep is slightly better but the CPU still fails to sleep and that it prefers full speed too much...

deltatux
[ONE Original Android Development] ~KV:
[MENTION=4911350]RobbieL811[/MENTION] What's the difference between SlimLP and SlimSaber?

Are both essentially the same?:confused:
[ONE Original Android Development] inffy:
Pretty much. SlimSaber uses different toolchain (UberTC) and has some modifications
[ONE Original Android Development] bundys:
Same as the other guy who posted above, huge phone/rilj wakelock but on the 0709 build. Goibg to try the 0714 build and see if it continues.
[ONE Original Android Development] JaylanPHNX:
SlimSaber uses some CM bits, like their telephony and heads-up and a few other things. It also has Layers support. Robbie's Slim is the official Slim.

From my SlimTab Pro 8.4
[ONE Original Android Development] Android-Andi:
Maybe you need to stop mpdecision first, make changes and start mpdecision?

Maybe try an app like Kernel Adiutor instead.

[MENTION=4911350]RobbieL811[/MENTION] do we need something like https://github.com/CandyDevices/device_samsung_p3100/commit/939f865a1008fd0e3c16988b6835b0a463f5168f ?
[ONE Original Android Development] therahmaniac:
I see kernel adiutor to use a replacement called 'MSM MPDecision' hotplug. I do not find a way to just disable the Qualcomm hotplug(Am i missing something?). Also please correct me if am wrong, do hotplugs govern the min and max frequencies or Cores online and current frequencies? Because in my case i think the indivdual core frequencies settle down to frequencies that dont match with the ones i attempt to apply, even with kernel adiutor.
[ONE Original Android Development] Android-Andi:
You can disable it, there's a slider in the tab.

I haven't read and played much with it, but afaik msm mpdecision is a Qualcomm kernel feature which changes the frequency and online/offline cores intelligent depending on the usage.

If you disable it you should be able to define fixed values and used cores. But i am not sure if it makes sense.
[ONE Original Android Development] therahmaniac:
I thought may be the slider is disable using the replacement(EffectivelyMeaning either use Qualcomm's or the MSM hotplug). And no, even after disabling (using the slider on kernel adiutor), the min freq of cores 1,2,3 settle at 1267 mhz.
[ONE Original Android Development] dharmabm:
Hey everyone!

I have finally taken the full leap to 5.1, was waiting for a bit until the kinks were worked out, and 5.0 was just working for me.

Anyway I am very impressed, but am having 2 small issues.

The first may just be me losing my mind, but I swear the alarm isn't working properly. I haven't been able to replicate it but the first morning I was using the latest build, clean flash and I snoozed the alarm @5:45am, then woke up at 8. When I looked at the alarm notification it said it was snoozing until 20 minutes after on the next day! Anyone else notice any issues?

The other problem is a bit more severe, and very puzzling. I don't use google services but sync my contacts with my owncloud server via davdroid. It appears to be syncing properly as I can watch all of my contacts appear in the phonebook, then gradually all but a few disappear! There are no errors on the server or in the logcat, the last message the logcat shows is

[ 07-15 17:28:12.752 29639:30879 I/davdroid.SyncManager ]

Removing non-dirty resources that are not present remotely anymore

This is very strange as I can add a contact to the phone and it stays and syncs with the server fine.

I thought I recalled Robbie saying something a few builds ago about an issue with contacts, but for some reason I cannot find that post. I don't believe that issue is the problem but I thought i would try the steps he outlined to clear the local phonebook cache. I have tried going into airplane mode and manually deleting all contacts and then syncing again but the issue persists.

Any ideas?
[ONE Original Android Development] MBurns2:
I believe that slimlp use bricked hotplug instead of MP decision. Pls correct me if i'm wrong

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] nhshah7:
That issue was just with how the contacts are sorted. Nothing like this. Sorry dude, not sure what's going on with you.
[ONE Original Android Development] k3vink3vin:
Thanks, disabling off mobile data seems to have helped with the drain I have been having when WiFi is connected.

RILJ wake time seems to have reduced drastically, though com.android.phone still wakes a lot.
[ONE Original Android Development] RobbieL811:
Ok guys/gals. I have a new build here for OPO. LOTS of changes made. Kernel changes, device changes and also changes in the blobs. I think that wifi is going to work much better now. Also, hopefully it will take care of the battery drain problems that we have been having. And also for those of you that use the nav bar, I have added in commits from [MENTION=2033478]Yank555[/MENTION] and [MENTION=1277872]dankoman[/MENTION] that add CM's nav ring and a new feature by dankoman that is called SlimDim. Dims the nav bar keys. I hope yall enjoy. Let me know if things are better or worse w/ the battery and wifi, or if any other problems have popped up. Thanks.

ROM - Slim-bacon-5.1.1.beta.0.2-UNOFFICIAL-20150717-1505

GAPPS - Slim_mini_gapps.BETA.5.1.build.0.x-20150716
[ONE Original Android Development] djha53k:
Is SuperSU included or has to be installed in TWRP separatelly?

Thanks.
[ONE Original Android Development] :
You don't need that on this ROM.
[ONE Original Android Development] djha53k:
Question is not if I need or not, but is it included in the ROM?
[ONE Original Android Development] samaritan16:
Thanks for the build [MENTION=4911350]RobbieL811[/MENTION]

Flashed it now. Quick suggestion, the quick setting bar overlays the display.. Meaning while some other app is on the background, the notifications are shaded by the extended quick settings bar when pulled down.. Seems some minor issue.. Definitely not a major one for me for now.. Have a look at it and if it is there, maybe for next build!

---------- Post added at 07:40 PM ---------- Previous post was at 07:31 PM ----------

Edit: The problem was there only in 400 DPI... With 480 all is well :)
[ONE Original Android Development] beren:
flashed last build, seems good so far (10 minutes)

first time i am using built in root, and this app (http://xdaforums.com/android/apps-games/widget-toggle-network-type-5-0-xda-t2945406) seems can't work properely (says to check root)

anyone having same problem?

edit: btw is there any place to check which apps are allowed to get root?
[ONE Original Android Development] RobbieL811:
No, SuperSU isn't included. We include open source root and it works perfectly. I've never had a single problem with it.

Idk what you are talking about.
[ONE Original Android Development] RobbieL811:
I think that this might be an app problem.
[ONE Original Android Development] kantjer:
LOL, that app needs SuperSU to work ;)

From the apps OP

Requirements: On Android 5.0 and later, when SELinux is set to enforcing: a superuser app with support for a SELinux context parameter (-cn). Currently, only SuperSU supports this parameter
[ONE Original Android Development] djha53k:
Ohh, thank you.

I have one app which crash on you ROM and appl supp stated "it is because SuperSU is installed".

I did clean install of ROM, no GAPPS, no SuperSU...

Can you provided me a link to that root, so I can fwd it to appl supp?

Thank you.
[ONE Original Android Development] RobbieL811:
I'm not sure of what you are asking?
[ONE Original Android Development] djha53k:
URL link to "open source root"

Thanks
[ONE Original Android Development] RobbieL811:
I don't understand. There is no URL link. Are you asking how to enable root in the ROM??? If so, go to developer settings and enable it there. The switch for it is near to the top of the list.
[ONE Original Android Development] beren:
Oh thank you... Missed that part...

Inviato dal mio Oneplus One utilizzando Tapatalk
[ONE Original Android Development] rogi19:
Doesnt slimlp have layers theme engine?
[ONE Original Android Development] chikimonke:
Not the most recent 2.x updates. It only sort of supports 1.x. If you want Slim and Layer support, you need to run Slim Saber.
[ONE Original Android Development] samaritan16:
[MENTION=4911350]RobbieL811[/MENTION]

The issue is like this: While setting up the rom and downloading/updating apps, the notifications come on the top of the phone.. When I swipe it down (along with quick settings) normally I can bring the notifications down and kill all or choose to click on what i need.. While doing this, I noticed that at 400 dpi settings, and pulling the screen down to bring notifications of app dowloading, the quick settings sort of extends.. meaning quick settings and the first most notification merge and half first notification is visible while quick settings end (basically the opaque screen) fills the other half of where the actual app notification must be.. I hope i've explained this better.. The issue isnt there on 480 dpi though..

Btw, lost 6% battery overnight with wifi/data off.. Dont know if it is considered normal, but I can swear that some May/June builds of slim never drained a dime of the battery overnight.. Max loss used to be 2% with wifi/data turned off..
[ONE Original Android Development] Chris.C:
I run at 400dpi and don't have the issue you are having with the quick settings extending. I have 17 quick settings in 4x4 rows then 1
[ONE Original Android Development] JaylanPHNX:
Try going back to 400 and see if it's still there. Sometimes, if there's been changes in the dpi system, changing it then changing back is necessary.

From my SlimTab Pro 8.4
[ONE Original Android Development] bundys:
No luck with battery drain - still high due to phone-interface / rilj (flashed over previous build after clearing caches). If anyone clean flashed this build, can you let us know if it made any difference?
[ONE Original Android Development] RobbieL811:
Why not you be the one that let's us know if it makes any difference. RIL wake lock definitely seems much better for me. Still not right on the battery drain though. Is drain high even with other kernels?
[ONE Original Android Development] bundys:
I was simply asking if anyone who did a clean flash saw any improvement - hence saving myself and a bunch of others the time of doing a clean flash if the new build doesn't solve the issue (which it doesn't).

With the 06-29 build my deep sleep percentage was about 98% if I didn't do much with the phone. With similar usage, the 07-17 build gives me 47% in deep sleep - a huge difference.

Don't know about other kernels, using stock kernel.
[ONE Original Android Development] deltatux:
My drain has been much better with this build, more work to be done but still much better than the huge drain from the 12th. Note that I did not clean flash this. It's an upgrade from the 14th build.

The only issue that I'm having is that when you wake the device from deep sleep and try to unlock the screen by swiping up, it takes a second try to get it to register the command. Previous builds never had this issue. Not sure if this makes a difference but I have Smart Unlock (also called trusted lock) enabled to unlock device without password when my watch is near the device...

Cheers,

deltatux
[ONE Original Android Development] samaritan16:
I did a clean flash and found battery drain levels same as recent previous builds.. No significant improvement [MENTION=4911350]RobbieL811[/MENTION]...
[ONE Original Android Development] JaylanPHNX:
They tracked that down in the Builders Collective thread to the new slim dim feature. Dan made a new commit to disable it on lockscreen, which seems to help.

From my SlimTab Pro 8.4
[ONE Original Android Development] Dimpap28:
I still got the problem with the images that open in apps zoomed-in to the upper left part...
[ONE Original Android Development] shadow47:
Hi. I am using Slimlp for the first time. It's very smooth and 6hrs plus battery backup. Good job. :):thumbup:
[ONE Original Android Development] archer100:
Me too. Did you clean flash? Just curious where that problem came from.
[ONE Original Android Development] Dimpap28:
[MENTION=3851102]archer100[/MENTION] No, but I'm gonna try it and come back with the results.

Edit: Nope, still the problem with the pictures remains.

Second edit: Rebooted after the clean flash and it seems to work properly now...
[ONE Original Android Development] Rd. Vortex:
Thanks for the latest build! Battery life definitely seems to be better compared to previous builds. Like someone else mentioned, lockscreen seems laggy at times.

For me haptic feedback doesn't always work on the capacitive buttons. For example: Sometimes when I press home, I go to home screen as I should but there's not vibration at all. Is anyone else experiencing this? I've had that same issue on copule of previous builds. From what I remember from testing CM12.1 briefly it didn't seem to have the same issue.

Regarding battery life: Does anyone know how much of an impact allowing WiFi scanning to be always on has on battery life? All guides on battery life tell to disable that setting but I'm wondering if someone has actually measured if it has any significant impact. Location accuracy and speed acquiring location are definitely better with constant WiFi scanning enabled.
[ONE Original Android Development] archer100:
I have a noob question, how to use fastboot to flash the 05-15 firmware Robbie posted here: https://androidfilehost.com/?fid=24052804347768997 ?

I tried "fastboot flash zip <filename.zip>" and "fastboot update <filename.zip>", but neither works. I read that the latest twrp does not flash firmware due to encryption, and we have to use fastboot. Needs some help here. Thanks!
[ONE Original Android Development] JaylanPHNX:
I think you have to extract the files from the zip and fastboot the .img's. Something like that. I'm no expert, that's for sure.

From my SlimTab Pro 8.4
[ONE Original Android Development] chikimonke:
[MENTION=2714876]bombadier[/MENTION] posted the proper fastboot commands in the SlimSaber thread a few times. Here's the link to his post.

http://xdaforums.com/showthread.php?p=61935141
[ONE Original Android Development] archer100:
Thanks for the help! Confirm that worked correctly. Baseband successfully updated to 3.0.c6-00241. :good:

I originally flashed the zip file using TWRP, but did not notice that baseband was not updated.