yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] JAY28W:
Easy-peasy to install the app and overlays. Did so and my screens are just like Natakranta's.

Thanks Robbie and everyone else concerning this. Looking forward to having some fun with it.

jay
[ONE Original Android Development] JaylanPHNX:
Until they change how it all works. Lol! They're working on a way to apply whole themes in a friendlier manner that also lets the themers put them on the Play Store. I won't be complaining when that happens.

It's baconnn!
[ONE Original Android Development] skeamznz:
Without reboot would be great. I also think this could be far Superior over theme engine more possibilities. Can't wait to see where it goes.
[ONE Original Android Development] soliditalstud:
Hardware buttons stay lit after locking screen
[ONE Original Android Development] RobbieL811:
I must have forgotten a commit. I will post another build in a few.

Sent from my 1+1
[ONE Original Android Development] soliditalstud:
Trying the newest build from this evening and will follow up

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

Sorry one more thing or maybe I just missed something. But wasn't there an option before for the advanced reboot menu?
[ONE Original Android Development] anishz:
No there was no advanced reboot menu.
[ONE Original Android Development] soliditalstud:
OK so the newest build from tonight fixed the button issue.

Thanks

Looks like I got it mixed up with the slimsaber rom.

Is there any thing coming for remapping or adding options for the hardware buttons?
[ONE Original Android Development] RobbieL811:
Yes. There definitely is an advanced reboot setting. It's in Settings > Security. You can enable it there.
[ONE Original Android Development] anishz:
Oops :o, thanks for letting me know, generally have always seen it in Developer options, so never checked in security. Thanks, XDA thanks limit is up.
[ONE Original Android Development] RobbieL811:
As long as I can remember in Slim, it has been in Security settings. Anyways, glad I could help you!
[ONE Original Android Development] RobbieL811:
Ok guys. Another new build up. Tons of changes. I can't list them. Sorry. Lots of Bluetooth changes. Test BT for me.

ROM Server 1

ROM Server 2

GAPPS Server 1

GAPPS Server 2

SuperSU

Also, I have pushed some RRO themes to here:

RRO Themes
[ONE Original Android Development] primo14z:
hopefully this doesn't sound mean :D

but men i can't have 1 day without flashing my phone :D

thanks for the updates tho , GJ :D
[ONE Original Android Development] S1ay3r666:
Instructions working great!

It was my fault flashed it the first time but now all is running great.
[ONE Original Android Development] RobbieL811:
I only posted 2 or 3 builds. Do you have any idea how many I flashed??? Probably about 20 lol. Sorry about so many posted in one day. Just a lot going on w/ RRO and a bunch of commits from CM.

Sent from my 1+1
[ONE Original Android Development] Zeus20:
Don't ever say sorry!!! Your trying to make the best rom possible and as a flasher and a follower of your work. I'm happy to see that it is always being worked and changed for the greater good. I think I speak for everyone and and say we are sorry for not showing more support money wise. For your donation bin.
[ONE Original Android Development] wozn:
Heck mate post as many as you like, who cares that the wife says I'm always playing with my phone and not the kids. I enjoy slim more then the kids anyway
[ONE Original Android Development] cavlovic:
Robbie, I asked somewhere before, but you must have missed it. What is main difderence betwrmeen this ROM and your other Sabermod CM12 ROM, other than the fact second is based on CM12 sources? Which one would you suggest?

Sent from my A0001
[ONE Original Android Development] RobbieL811:
Well, I need to get better at picking release builds. I just get excited when new stuff gets pushed & I feel like I HAVE to do a build lol. I know it can get aggravating to flash & get everything set up and look at the thread & there's another build already lol. But hey you crack Flasher's ain't gotta flash EVERY build lol. I do though lol. ???

You better take that shi* back right now lol or in gonna tell your old Lady on you lol!!!

Man, it's hard for me to tell you that. Both are really stable builds & run really fast. It's really not a decision for me to make as to which one you should flash. I normally run Slim as my DD. My CM builds definitely have more features, but I am just a Slim guy. And w/ all the testing and all, it's just easier for me to keep Slim as my DD. Flash both & let me know what you think.

Sent from my 1+1
[ONE Original Android Development] wozn:
More invites

https://account.oneplus.net/invite/claim/GLZQ-MP4A-SPYI-2WNR

https://account.oneplus.net/invite/claim/GLQV-DBRA-TGT8-GHMG

https://account.oneplus.net/invite/claim/GLJS-BGKA-PRFN-H7QJ

---------- Post added at 07:38 PM ---------- Previous post was at 07:28 PM ----------

@Robbie worth me building a saber build of the stock slim? Are their enough advantages, for the pain of me pulling out hair setting it up. I kinda half set up it on my always-on box then lost interest I few months back. I have fond memories of you saber slim kat
[ONE Original Android Development] RobbieL811:
What is always on box? Idk. That's up to you. I don't think any huge gains would be seen. And fusionjack already does a Sabermod build. That's why I quit doing mine.

Sent from my 1+1
[ONE Original Android Development] Wongher:
great work

This Rom is super fast, great job.

many thanks to [MENTION=4911350]RobbieL811[/MENTION]
[ONE Original Android Development] RobbieL811:
Eh, give me a donation when you can. It does help me w/ my server costs w/ community donations but I don't want anyone giving me anything unless you think I deserve it!

Sent from my 1+1
[ONE Original Android Development] wozn:
Haha just a small headless i5 box I use for torrents, nas backups etc that's always on mostly doing nothing. Need to find more jobs for it to do. Yeah I've tried FJs but I always come back to stock as I just don't use the extras he adds. Nice work though and very committed.

Anyway if sabermod ain't worth it I'm not bothered. Thanks
[ONE Original Android Development] RobbieL811:
I mean hell, if you want a stock Sabermod build to try, that's enough reason to do a build of it isn't it? I have already fixed up the kernel to compile w/ Sabermod 4.9. And compiling ROM side w/ Sabermod 4.8 is MUCH easier than in KK! All you need to do is point it to the Sabermod TC that you wanna use and compile. Up to you if you wanna try it. If you want, I can do a build of it for you to see if you would like it...

Sent from my 1+1
[ONE Original Android Development] S1ay3r666:
Yeah maybe you can build one with sabermod, that would be great.
[ONE Original Android Development] JAY28W:
[MENTION=4911350]RobbieL811[/MENTION]... loaded and then tested this update with BT this morning on the way to work. Connected quickly, stayed strong and quality seems to be good.

Also, did not know if it was recommended or not, but I unloaded all the RRO layers/themes before dirty flashing this update, just to be on the safe side. Will apply some of the new RRO themes later.

jay
[ONE Original Android Development] RobbieL811:
So BT audio in the car was working good!?!? That is awesome news! It wasn't working before was it??? Doesn't matter about layers. Clean flash will reset them. You just have to re enable them after first boot.
[ONE Original Android Development] JAY28W:
Yeah, it was working before, sure. Frankly I've not noticed any difficulties in BT for a long time...I think the last difficulties I've had with BT date maybe back to KK days.
[ONE Original Android Development] RobbieL811:
Ok. I had a report that in car audio BT wasn't working. Glad to see that it is.

Sent from my 1+1
[ONE Original Android Development] JaylanPHNX:
Speaking of audio, there's a bug still present that's been there from the beginning, where if you're listening to music and get a notification or any change in audio focus (navigation does it a lot), the volume goes down like it's supposed to, but when it comes back up, it gets much louder than it was. Like ridiculously loud. If you hit a volume key, it will return to normal levels. It's strange when you hit volume up and it gets quieter because it was artificially that damn loud. This happens with Google Play Music. I haven't tested with any other music players. It doesn't seem to matter if it's over Bluetooth or headphone jack.

It's baconnn!
[ONE Original Android Development] RobbieL811:
Test w/ MusicFX. I think I have it built into the ROM. I think the app name is "Music".
[ONE Original Android Development] dharmabm:
I had that same issue yesterday, had to run to my Bose BT speakers before they blew. Since I'm using multirom I didn't report it but since someone else had the issue I can confirm.
[ONE Original Android Development] cam30era:
[MENTION=4911350]RobbieL811[/MENTION],

Just a quick question to make sure I've got this right: I'm currently running 0122 build with your dark UI, and it's flawless. If we wish to have the latest updates, we'll need to flash the last 0125 build from yesterday and apply the RRO overlay?

Thanks for your great ROM, again.
[ONE Original Android Development] tygern8r:
That was me with the BT car issue. It had worked without issues on my Note 2, but when I got my OPO it would sync and I could use it to make calls, but the contacts wouldn't load. That's when I dropped CM11 and found your SlimLP, but I had the same issue. Then out of the blue on Sunday, my contacts suddenly showed up in the car. I made some calls and everything was great.

Then I saw all the RRO stuff so I flashed 20150125-1025 last night. This morning on the way to work I kept getting the "bluetooth has stopped working" popup on the phone and the car kept saying it couldn't pair with the phone. So I'll flash the 20150125-2223 and see what happens.

Thanks again for all your work!
[ONE Original Android Development] RobbieL811:
Well, there is a lot of BT stuff being pushed right now, so we'll see.
[ONE Original Android Development] evronetwork:
Hi there, found a bug :D

How to do it(maybe it was one of it's kind and won't happen again? ..who knows). I've wiped everything, flashed rom, flashed gapps(slim gapps are recommended), flashed SU

Then booted, phone connected to usb port(pc), I've tried to remove usb debugging, phone froze... and rebooted :D

EDIT: Not a coincidence, it happens EVERY time. Connect phone enable usb debugging instant freeze/reboot, same as disabling it (maybe it's a know issue but I though I could mention it)

EDIT2: it might be an accidental issue as EFS lost after flashing. Putted nandroid backup still efs losted, no pin number asked, no cell signal(but I was prepared), I fastboot efs backup back.. I'll try tommorow again to see if this happens and update accordingly

EDIT3: Just flashed again, now it doesn't even boot(stuck at Slim logo), this isn't gonna work for me..
[ONE Original Android Development] soliditalstud:
I was getting disconnect/reconnect issues and FC Bluetooth so I cleared cache and disabled Music app and using Google play works well but still getting that issue when music comes back after notification and gets loud with static. Other issue is every 15-30sec I get a music skip
[ONE Original Android Development] JaylanPHNX:
I'll reflash and try maybe Wednesday when I have time. I always use Viper4Android. It happened back when I was using slimsaber, too. Anyone else get this? Try with navigation.

It's baconnn!
[ONE Original Android Development] tygern8r:
I flashed the 20150125-2223, went to lunch and the phone and car synched up immediately, contacts and everything. Made a couple calls, everything seems to be working great!
[ONE Original Android Development] RobbieL811:
Lol. So it's working for some and not for some. Jesus this is gonna be a pain! I can already tell!
[ONE Original Android Development] ralpheboyo:
Can feel the pain already.... Can I just remind everyone to test without restoring anything.... Blank. Pure Robbie build inc wipe data.....

1+1 Ultra~SlimLP
[ONE Original Android Development] ak:
@ralpheboyo

do you have merged latest rro v2 into your build?
[ONE Original Android Development] 530farm:
Is slim planning on adding the ability to change the H/W buttons?
[ONE Original Android Development] ralpheboyo:
Been migrating my build environment to another storage..... Should have it done in next build.... Just kicked off the build 30 non ago....

Oh on that note....why the hell you not in the hangouts grp....????

Well you are now....whether you like it or not.....lol....

1+1 Ultra~SlimLP
[ONE Original Android Development] JaylanPHNX:
Eventually, yes.

From my SlimTab Pro 8.4
[ONE Original Android Development] nhshah7:
I'm on the 0122 build (dark UI) and have had NO issues with BT.

I haven't had this with any music or nav stuff. I use spotify iheartradio and pandora. BT and headphone jack and phone speaker. I'm not on V4A, but using the builtin audio fx thingy.

No disconnect/reconnect issues here (0122 build, flashing newest now). The contacts have always worked for me over BT on LP, as someone else reported was problematic. I DO have the music skipping/beeping issue occasionally depending on what I'm listening to with iheartradio and spotify.
[ONE Original Android Development] anishz:
Went to Cm based roms just to see whats new[Keep doing it from time to time] and all have boat-load of features, but i clean flashed from cm12 26/01 nightly to them. The thing is none of them managed to get my wifi working, which was really strange.

Even Vanir has the same problem for me on the latest builds, and Liquidsmooth which is apparently based on AOSP but still has wifi issue.

But just now flashed back to slim and everything's fine, [Camera is f!@#$d, but i use modded camera anyways] wifi connected fine. Why is that? :confused:
[ONE Original Android Development] elchmartin:
seems to work just fine :)

flashed last night and did a little testing (calls, BT, Wifi, RootApps) .... cant se any flaw until now.

also flashed cm11s camera, works,

adaway is blocking some hosts, also looking good.

here's my path:

-latest Phils touch

-clean wipe from philz

-installed latest bacon firmware

-installed SlimLP zip

-installed normal slim gapps

-installed superSU zip in philz

-rebooted

done!

for someone changing ROMs frequently, i definitely like the NFC-initiated profile copy-thing in lollipop. cant get any easier (using my n7)
[ONE Original Android Development] ak:
Good ... Thanks a lot .... For your testing report.

Sent from my A0001
[ONE Original Android Development] evronetwork:
I did a full wipe,

Flashed SlimLP zip

Flash the small slim gapps

and the supersu zip

..quite a few bugs in the first seconds, lost cell signal etc, had to revert to 44S nandroid backup+restore efs files. Tried to flash again, stuck at boot logo(S logo)

(but now that I remember the firmware update was important in order to move from 4.4.x to 5.0.x ..but no one mention it :P.. care to share a link -> yes I'm lazy, cmon it's morning here :p)

P.S. If there's a link to previous(4.4.x) and to newer(5.0.x compatible) it would be lovely as I might not like it and I'm pretty sure I've read somewhere you can run stock CM11s with newer firmware(gives you all sorts of problems) -thx
[ONE Original Android Development] anishz:
Firmware for CM12 new: https://mega.co.nz/#!KVN0URZB!ICHUMdBMtvK2lGmbkw8eOW2b3vkioULNwtPeVulRyEA

Firmware to go back to CM11: https://www.androidfilehost.com/?fid=95897840722647804

Credits to Tobitege for the files, thank him, you will find him everywhere on these forums. :p:D
[ONE Original Android Development] Hzu:
Any chance we would be seeing a CM equivalent of Protected Apps on SlimLP?

Loving this ROM so far, it's really amazing. I wish I had discovered this ROM earlier.
[ONE Original Android Development] simarilon:
Hm, I wonder if there is a newer firmware for LP out? The date from your link is 2015_01_23 (31,1MB),

the date from the firmware on RobbieL811 server page is 2015_01_16 (32,5MB) they have also different size.

Thank you for you help

Best regards
[ONE Original Android Development] primo14z:
i am using the new one :)

and it works fine, no difficulties whatsoever
[ONE Original Android Development] cam30era:
FWIW: I believe that Omni is the only OPO ROM that is AOSP based...
[ONE Original Android Development] NuLLV01D:
All ROMs are CAF-AOSP based in case of OPO. no Pure AOSP stuff is available
[ONE Original Android Development] chikimonke:
Is there a thread where this new firmware is discussed? Can't seem to find mention of it.
[ONE Original Android Development] anishz:
Frankly i don't remember which thread i got this from, but its from user tobitege [been using his firmware packages for sometime], either Temasek/Blisspop/Euphoria/Tuga. You will have to search a bit.
[ONE Original Android Development] chikimonke:
Alright, thanks. Usually things like new firmware get talked about everywhere after they are released, especially in the firmware thread. [MENTION=4877142]tobitege[/MENTION] just curious where you posted the firmware initially. Don't like to just randomly flash things like firmware without seeing what others are experiencing with it first. (like the sensor issues before we knew 100% that you needed a rom with specific commits for everything to work properly) Thanks
[ONE Original Android Development] dharmabm:
The only place I have seen both those files is on [MENTION=453962]fusio[/MENTION]jack's sabermod here http://xdaforums.com/showthread.php?p=55040333 but I am too lazy to check datestamps to see if they are most recent
[ONE Original Android Development] tygern8r:
Seems like BT worked fine for the majority of people, even on the stock CM11S. I appear to be in the minority and most of the troubleshooting methods I found were in Nexus forums where BT and cars seemed to be a much larger issue. There's a guy in OPO forums with the same year and model car as mine and his OPO worked just fine out of the box.

I'm running :

TWRP 2.8.4.1

bacon_firmware_update_2015_01_16

had the Alpha modem, but it would constantly drop cell signal, so I flashed 44S

Robbies 20150125-2223

mini gapps beta 5.0 20150122

SuperSU 2.45

overlay_frank11_darker

and everything seems to be working fine, although I haven't had a chance to try streaming any music yet. I'll do that at the office today.
[ONE Original Android Development] niko2931:
Okay guys, I've got a question.. How come using the stock keyboard with svipe doesn't work on my native language (danish) but works on english?
[ONE Original Android Development] kantjer:
Probably because there is no Danish dictionary in the stock keyboard.
[ONE Original Android Development] niko2931:
But how can i add it?

On Temasek/katinatez cm12 rom it works, without me having to do anything?
[ONE Original Android Development] kantjer:
try this http://xdaforums.com/showpost.php?p=58202934&postcount=3656
[ONE Original Android Development] niko2931:
Thank you!

Sorry i thought i had made a search.. Sorry..
[ONE Original Android Development] tobitege:
The firmware I have in my sig is the one from CM-12 official nightly dated Jan 23, all 8 firmware files, incl. updated "logo.bin". I packaged it and flashed it myself. :)
[ONE Original Android Development] chikimonke:
Cool, thanks. I take it that means you've been keeping track of the nightlies then, and updating when you see something different? I only ask, because there have been 4 more nightlies since you made that zip :)

Edit: Never mind, I jsut hashed out the files myself, and all the files are the same. You should post your file in the Modem thread or start your own if you plan to keep this up to date. Just a thought. Thanks again.
[ONE Original Android Development] tobitege:
[MENTION=2495716]chikimonke[/MENTION]: I do follow the nightlies, yes, and would update my sig accordingly. ;)
[ONE Original Android Development] chikimonke:
So I just flashed it and noticed that the initial boot splash has a bigger 1+ logo, but when the "powered by android" portion goes away, you can still see the top of the "powered by". It's like a black box is overlayed on that part of the screen, but the placement is off. Did you notice this?
[ONE Original Android Development] tobitege:
Yes, but I can't say who botched that job. :D That came with the new "logo.bin" on 23rd. Maybe they either did a bad job in hiding it or just needed to get the filesize down (for whatever reason).
[ONE Original Android Development] MrSpaceman:
Network indicator

Everything seems to be running fine.

However, my network indicator doesn't seem to show H+ when appropriate.

Am I missing something?
[ONE Original Android Development] bobby_sucker:
I mentioned that 2 days ago in Hangouts. But no one paid attention as usual

Flash 16th firmware and you'll get it back normal
[ONE Original Android Development] elchmartin:
sooo today was a good day.

all worked fine until i left work and headed home.

while listening to music through my BT headset i recieved a call. pickup and the call itself were just fine. music coming back up after the call, first 5 seconds playback were OK, then all i heard was some kind of gaussian noise :confused:

pause/unpause google play music app solved it ... i wonder if this is some BT issue or and issue with gie play music app and SlimLP?

and by the way is there any kernel i should try?

still pretty happy with SlimLP so far!

cheers!!
[ONE Original Android Development] fatboyinlycra:
[MENTION=4911350]RobbieL811[/MENTION] I've just flashed your build of 25th Jan coming from the Jan 22 build and noticed the battery icon choices have disappeared. Is this right?
[ONE Original Android Development] chikimonke:
Yes, there were bugs in the code that they couldn't figure out, so they've been removed for the time being. That said, Griff was asking what people's preferences were for battery icon styles in the builder Hangout, so I don't think they will be gone for long. If you had the text option turned on in the previous build, the text will still show up in the battery icon after flashing the latest build. If you want to get rid of it, you have to flash back to the old build, disable the text, then flash the new build again.
[ONE Original Android Development] probiewankenobi:
[MENTION=4966414]fatboyinlycra[/MENTION] yes, was necessary to implement correctly RRO v2. Can't be more specific, sorry but I assure you have done nothing wrong lol

Sent from a bacon flavored lollipop.
[ONE Original Android Development] RobbieL811:
Good news guys! [MENTION=2033478]Yank555[/MENTION] has helped me w/ the battery commits, and I have managed to get them back into the build and working properly w/ RRO. Coded properly lol. I will try to post a new build w/ them back in here in a little while.
[ONE Original Android Development] tygern8r:
Well, I realized that not being able to wake up the screen during a phone call was because I flashed the 44S modem. This was causing too many problems (not being able to switch to speakerphone, hang up, conference call, blah blah) so I wiped everything (just for fun), started fresh and clean, but this time I stuck with the Alpha modem. Same issue, dropping cell signal every 12 seconds or so then locking back on. Under Settings > More > Mobile Networks > Access Point Names I switched to T-Mobile US LTE. It locked on and has stayed locked on. Sweet.
[ONE Original Android Development] evronetwork:
Firmware for CM11 is same as CM11s? :confused: (cm11s and cm11 are different as s is a specialized ver for 1+1 but thats not what I'm asking)
[ONE Original Android Development] apatal:
I think firmwares for the two versions are interchangeable as long as they're both KitKat. I've always updated firmware from new nightlies as this usually comes with some sort of fix or another from the hardware sources for the device.
[ONE Original Android Development] indian84:
The firmware includes radio and other files like boot animation. They are samebfor CM11S and CM11...