Database Develop

[ROM][4.3.1][JLS36I]SlimBean -T959 [Build 2][+WEEKLIES]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
Notification drawer Shortcuts
Full hardware key rebinding!
Keyboard rotation
SlimCenter
Check out our full feature list here
Changelog
Find our latest Changelog go here
Chat with the slim team and other slim users
IRC: #slimusers @freenode
New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
More interested in development and compiling? Check out our development channel. #slimdev
Check out our forum if you're looking for a place to talk all day long about SlimROMs FORUM
Google+ [link]
Twitter [link]
Facebook [Link]
Installation instructions
For Most Users
Please keep in mind if a special instruction is needed it will be noted in the Changelog
Download the latest build from [here]
Addons ( if you don't have it already) from [here]
!Recommended! Full wipe, and manual format /system
Flash ROM and the addons you want, reboot
FAQ
Check out out FAQ before posting! Keeps more common questions answered in one place!
Help us out!
If you want to help us by translating slim to your language check out Crowdin.net and submite your translations.
Or consider a donation.
Thanks!
You can find the full list of credits here
Source
Please visit here for the rom source code.
Kernel source can be found here

Right now only Weekly is available

It's really a good rom.
But I'm facing a problem. The internal SD Card writing speed is only about 4MB/S
Is there anyone else facing this problem?
Will changing the default kernel help solving this?
Thanks

IDK but have you downloaded semaphore manager apk to ramp it up. Default is 512K but you can bump it up to 2048K within the app.

what aint working here?? Im sorry i ask but its important for me as i use this as a daily phone..

I tried this rom out shortly - I love PAC but I needed the extra ram. It was snappy, but it had some pretty big problems. First off I was getting battery drain and CPU maxing out when GPS was on, unlike Pac. Secondly (worst of all, which made me have to flash back), I kept finding the phone completely dead. I kept checking my BatteryStats and everything was more or less OK, so I was confused. Then on a day when I was using my phone more, I caught it rebooting into recovery mode randomly, with the screen on the whole time, so that must have been what was going on. It happened often enough that it was too unreliable for me to continue using. Maybe I'll try the stable when it's out, because it was pretty smooth. Please work on these two issues and you'll have a great rom!

So thanks for the completely useless post give me damn logs. Anyways you guys can consider this device EoL. I have 0 intentions to update sgs1 to 4.4
Sent from my Nexus 4 using Tapatalk 4

prbassplayer said:
So thanks for the completely useless post give me damn logs. Anyways you guys can consider this device EoL. I have 0 intentions to update sgs1 to 4.4
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
If you don't want to maintain the sgs1 phones would you have any objections to unofficial builds?
Sent from my Nexus 4

After I drop it nope lol
Sent from my Nexus 4 using Tapatalk 4

prbassplayer said:
So thanks for the completely useless post give me damn logs. Anyways you guys can consider this device EoL. I have 0 intentions to update sgs1 to 4.4
Click to expand...
Click to collapse
I never understood all the whining & complaining ... esp. when you consider 2.1, 2.2, 2.3, 4.0, 4.1, 4.2, 4.3 ... the evolution to "butter" smoothness on these ancient phones has been spectacular. SB & PRB are at the forefront of that. I know people (with other phone types) who don't even get to use anything past Gingerbread (due to stability and lack of official support). Just look at all the roms left for dead on CM's nightly page.
Thanks to the tremendous efforts of PRB, jrongi1, DT, FE, stratosk, and others (inc. their testers) ... it's been an absolute pleasure to continue using this phone. Definitely showing its age spec-wise, but the latest 4.3 builds have been silky silky smooth. SB 4.3 v1.4 was great for me, and I just noticed the new weekly was posted.
So, damn ... just wanted to say "THANK YOU" to PRB for all the work put into maintaining this device. Whether EoL happens or not for SB's Vibrant fate, I'm stoked that at least jrongi1 is willing to carry the flag. PRB, man, seriously, thanks brother for all you do. Ignore the whiners 'cuz that stuff is unfortunately inevitable in this massive XDA expanse.

Rom problem it's effing random and logs don't show much...
Sent from my Nexus 4 using Tapatalk 4

BrianXP7 said:
I'm wondering if this might be an issue with the kernel or not but I've been getting quite a few soft (dirty) reboots. (I'm using GearKernel 1.0.9v2sv, by the way.) When I perform any action relating to file management (installing/uninstalling APKs, moving apps to SD card, enabling USB mass storage, etc.) it goes into a soft reboot. It might be because of the scheduler (sioplus) GearKernel might be using or that I'm overclocking up to 1200 MHz. I'm asking if this might be an issue with the ROM itself or if it occurs on any other ROM. I'll pull you a logcat when I experiment a bit more ...
Click to expand...
Click to collapse
I haven't had much luck with GearKernel on Slim. The one freak time I was able to use it (without losing IMEI) was flashing 1.0.8sv right after restoring an SB 7.8 nandroid. It was actually the smoothest kernel I've used at stock speeds (ondemand, sioplus) ... but terribly unstable at 1200-1400 Mhz. When OC'd, the phone would inevitably soft reboot, as you mentioned. Mackay Kernel 0.335 was more stable on SB 7.8 (than GearKernel), and it would allow gaming at 1400 MHz. However, Mackay also would eventually soft reboot at 1200-1400 MHz (tho it lasted a bit longer than GearKernel) ... and then would end up losing IMEI at random times. Even Semaphore would soft reboot at 1200 Live OC, though it would last much longer than either GearKernel of Mackay. Mackay's 1400 MHz is the fastest I've ever experienced on my Vibe ... but the fun only lasts until the next soft reboot. Lol. :crying:
I've tried GearKernel 1.0.9v2sv on 7.8, 8.0, and 4.3 v1.4 ... but I'd lose IMEI/APN/Baseband every fricken time I flashed that thing. No method would ever bring the damn thing back - ie. pull SIM / reboot / reinsert SIM, wipe init.d, and even manually restoring a backed up efs folder.
I've got a smooth 4.3 v1.6 running now, so I'm not even gonna touch it. Semaphore runs very smooth on 1.6. Maybe bring up the issue in Alberto's thread. He may have more insight for you. Good luck.

yosup said:
I haven't had much luck with GearKernel on Slim. The one freak time I was able to use it (without losing IMEI) was flashing 1.0.8sv right after restoring an SB 7.8 nandroid. It was actually the smoothest kernel I've used at stock speeds (ondemand, sioplus) ... but terribly unstable at 1200-1400 Mhz. When OC'd, the phone would inevitably soft reboot, as you mentioned. Mackay Kernel 0.335 was more stable on SB 7.8 (than GearKernel), and it would allow gaming at 1400 MHz. However, Mackay also would eventually soft reboot at 1200-1400 MHz (tho it lasted a bit longer than GearKernel) ... and then would end up losing IMEI at random times. Even Semaphore would soft reboot at 1200 Live OC, though it would last much longer than either GearKernel of Mackay. Mackay's 1400 MHz is the fastest I've ever experienced on my Vibe ... but the fun only lasts until the next soft reboot. Lol. :crying:
I've tried GearKernel 1.0.9v2sv on 7.8, 8.0, and 4.3 v1.4 ... but I'd lose IMEI/APN/Baseband every fricken time I flashed that thing. No method would ever bring the damn thing back - ie. pull SIM / reboot / reinsert SIM, wipe init.d, and even manually restoring a backed up efs folder.
I've got a smooth 4.3 v1.6 running now, so I'm not even gonna touch it. Semaphore runs very smooth on 1.6. Maybe bring up the issue in Alberto's thread. He may have more insight for you. Good luck.
Click to expand...
Click to collapse
It soft rebooted because your device can't handle that high of an oc. For example some people can not over clock at all some can hit 1.2ghz a few can hit 1.4-1.7
Sent from my SGH-T959 using xda app-developers app

prbassplayer said:
So thanks for the completely useless post give me damn logs. Anyways you guys can consider this device EoL. I have 0 intentions to update sgs1 to 4.4
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I don't appreciate the hostile reply. The rom was unstable enough that I just flashed back before I got any logs, and I figured any issue that severe would have already cropped up. I hope I didn't seem ungrateful about your work, just stating the fact, that right now for me it was too unstable to run. I understand that it's a nightly, and I was just testing it out.
Anyway, it's a moot point because it sounds like you're not going to maintain it anyway, so I'm not sure why you'd even be asking for logs.

Fact? Fact is runs fine on my captivate, or as fine as it can on it. Without logs it's just wasting keystrokes. I asked for logs because I'm still maintaining it. I said I won't be for next aosp version. Guys it's impossible to say how a rom/kernel set ups react on each separate device so if crap breaks and you actually want to help the community provide explicit instructions how to reproduce any problem with logs and screenshots if applicable. Else man don't bother.
Cheers
Sent from my Nexus 4 using Tapatalk 4

@prbassplayer thank you for your hard work on maintaining our phone and keeping it alive for so long. I am sad to hear that you won't be maintaining it for the next major update. Is that a for sure thing, or is it just a likely thing depending on how our phone continues to run?
Sent from my SGH-T959 using Tapatalk 4

Cooptx said:
@prbassplayer thank you for your hard work on maintaining our phone and keeping it alive for so long. I am sad to hear that you won't be maintaining it for the next major update. Is that a for sure thing, or is it just a likely thing depending on how our phone continues to run?
Sent from my SGH-T959 using Tapatalk 4
Click to expand...
Click to collapse
Its already lagfest (yes it is use a newer phone and you will see the difference), doubt a new aosp version will help. And time man. I'm maintaining 3 SGS1 devices, Skyrocket, Hercules, 3 t0lte devices and I spend a lot of time working on mako kernel as its the device I actually own and use as dd.
BrianXP7 said:
So, the latest weekly build was a huge improvement over the first. No more soft reboots! (It could be GearKernel's problem. I'm not so sure.) Everything works great and performance is balanced quite nicely. The only issue I have is the back button often doesn't quit a running app but it works with going back a "page". The other capacitive keys are fine, though. I usually resort to using the Home button to quit instead.
Click to expand...
Click to collapse
Grab a bug report quickly after it happening. I have no clue why this is happening. are you sure you set the kill app feature to back button (or hold back)?\

BrianXP7 said:
No, I'm using the default hardware key configuration. How do I take a bug report? Logs?
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Then I don't understand the problem?

BrianXP7 said:
I think it involves the launcher lagging to be launched when I attempt to quit an app. I tried keeping it in memory but it didn't help much.
EDIT: It seems one of the users also reported the issue in PAC-ROM.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Flash a different kernel like cyancore
Sent from my SGH-T959 using xda app-developers app

BrianXP7 said:
I think it involves the launcher lagging to be launched when I attempt to quit an app. I tried keeping it in memory but it didn't help much.
EDIT: It seems one of the users also reported the issue in PAC-ROM.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Get the semaphore manager from play store as slim uses the kernel it can help with some of the lag. But as prb said the Vibrant is not a speedy device as much as I use my N4 it can seem like forever doing things on the Vibrant.
cannondaleV2000 said:
Flash a different kernel like cyancore
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Sent from my Nexus 4

For modders Only bug rooms STOP

I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.

Serial67 said:
I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.
Click to expand...
Click to collapse
Haha, there are so many angles i can take on this.
I and the other 4x developers and users don't owe you ANYTHING, dont like our roms? dont use them, Simple. It amazes me some people are so entitled...

Go and make some Roms by yourself we'll see how good they would be .
For your information bringing roms to device in long chain of more people than just our devs
Sent from my LG-P880 using Tapatalk

Serial67 said:
I know that... TL;DR
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app

ectoplasma22 said:
Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't worry ecto, we are talking about it in the italian forum where this kind of discussion began.. And we are composing it saying exactly what you're saying right here..hope that it'll stop as a great mistake, and to go on..
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

one word, ridiculous

We should change abit this letter and sent it to the LG dev-update department so they can ask @Demetris @laufer @adam @Ectoplasma @JoinTheRealms @SnXo (and many other talented and good people) for help next time they decide to push or even make any software for any LG phone.I know.this guyment to say official software not custom one so i am just correcting his type mistake.
Послато са LG-P880 уз помоћ Тапатока

whoa, easy there, mate...
First of all, I haven't seen an unstable ROM on our phones up till now. I am personally using CM (unofficial) and SlimKat as my daily drivers, and both are rock stable. The only bugs I have personally encountered are the camera (which is extremely hard to properly fix) and the broken reboot into recovery on Slim. And that's it.
All ROMs you find on xda are made for free, you don't need to pay anything, which means you also can't demand anything. Bringing a ROM to a device can take several hours (disregarding the time the pure download of the sourcecode takes), as every ROM needs its special treatment.
Furthermore, do you have any idea how long the pure compile process takes? On my new machine (which I upgraded for development only) needs ~75min for a clean build. Before that, my lappy was working over 8 hours for a clean build...
Saying we devs wouldn't maintain our ROMs isn't really nice, nor what XDA stands for. We do our best to provide you with the best/fully functional stuff, but there are things we can't fix/improve simply because we don't experience these issues. As an example, I am debugging my kernel ATM, and @FunkyRasta and I both run the kernel, however, FunkyRasta is experiencing lags, that I never experienced. So without his reports, I wouldn't even know about that until someone else might encounter it after the release.
@Serial67, nobody forces you to use "unstable" ROMs, but please don't just complain, but rather give some helpful feedback (logs) to help solve the issues. If you're not willing to provide such info (you don't have to), please don't complain.
Thread closed.

please help in my decision

I am about to pick up a nexus 6 and was seeing a lot of issues with the battery life. Does cm12 extend it or is it the same as stock? 2-4 hours aint that long. Im a huge fan of nexus but if it doesnt pass a decent amount of batt life im leaning towards a note 4 edge. Please guys some info. Thanks

podagee said:
I am about to pick up a nexus 6 and was seeing a lot of issues with the battery life. Does cm12 extend it or is it the same as stock? 2-4 hours aint that long. Im a huge fan of nexus but if it doesnt pass a decent amount of batt life im leaning towards a note 4 edge. Please guys some info. Thanks
Click to expand...
Click to collapse
I get a full day out of it. Averaging about 5-6 hours screen on time. I'm running a custom aosp ROM with custom kernel and my own settings. Runs amazing. My wife has the note 4 which is also an awesome phone. I'd say battery life is comparable. That really depends on who's using the phone though. But if you like to go custom with you're device then I would go with the nexus.

Depends how you use it honestly. I have seen 4-7 hours of on screen time. Depending. There are a lot of variables
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Google N6 on VZ

toknitup420 said:
I get a full day out of it. Averaging about 5-6 hours screen on time. I'm running a custom aosp ROM with custom kernel and my own settings. Runs amazing. My wife has the note 4 which is also an awesome phone. I'd say battery life is comparable. That really depends on who's using the phone though. But if you like to go custom with you're device then I would go with the nexus.
Click to expand...
Click to collapse
Im a rom freak and miss the hell outta flashing. Stuck with the flex right now. Yeah as soon as i get it im going with cm12. 5-6 hours is decent enough for.me.
Thanks man

podagee said:
Im a rom freak and miss the hell outta flashing. Stuck with the flex right now. Yeah as soon as i get it im going with cm12. 5-6 hours is decent enough for.me.
Thanks man
Click to expand...
Click to collapse
I would wait until cm12.1 comes out. Alot of people are getting bricked devices since Android updated too 5.1....Benzo rom which is based off of cm12 is running great in 5.1
Bricked :http://forum.xda-developers.com/showthread.php?t=3059518

jiv101 said:
I would wait until cm12.1 comes out. Alot of people are getting bricked devices since Android updated too 5.1....Benzo rom which is based off of cm12 is running great in 5.1
Click to expand...
Click to collapse
Probably bricked because new to flashing. Ibe flashed a bunch of phones,even flashed them to other.companies,stopped doing that though,so,not too worried about that. I just really really miss vanilla android,especially cyanogenmod

Cyanogen is out Alpha. CyanogenMod 12.1 ROM for Nexus 6! (Alpha): https://youtu.be/D4JE27mo600
I have flashed two or three roms on 5 .1. I don't think I've ever bricked a phone in five years. The Nexus 6 doesn't have a locked bootloader people are just not paying attention.
Benzo and Chroma currently offer more than CyanogenMod does.
Sent from my Google N6 on VZ

Oh ok I was just saying, didn't know your past history. 700 dollar paper weight is no good

Well, i was at sprint earlier doing a transfer and almost had my nexus 6,but, guess what? I gotta go in again later today,because, someone is using my identity in Maryland and has racked up a nice bill. Im in Hawaii so i just think thats crazy. Good thing Sprint and I have all the information for that dumb ass. So we will see if i get it today

podagee said:
Probably bricked because new to flashing
Click to expand...
Click to collapse
Incorrect. "Bricked" due to CM deciding they wanted to try and modify the bootloader during flash of nightlies. Bootloader cannot be downgraded so cleaners found themselves in a qhsusb_bulk mode. Its not a brick though because it is now recoverable, though initially it wasn't.
podagee said:
I just really really miss vanilla android,especially cyanogenmod
Click to expand...
Click to collapse
I think we have different ideas of vanilla
If android was icecream, cm would be vanilla chocolate fudge.

rootSU said:
I think we have different ideas of vanilla
If android was icecream, cm would be vanilla chocolate fudge.
Click to expand...
Click to collapse
Don't forget with nuts. Lots of nuts. Especially with CM
Sent from my Google N6 on VZ

podagee said:
I am about to pick up a nexus 6 and was seeing a lot of issues with the battery life. Does cm12 extend it or is it the same as stock? 2-4 hours aint that long. Im a huge fan of nexus but if it doesnt pass a decent amount of batt life im leaning towards a note 4 edge. Please guys some info. Thanks
Click to expand...
Click to collapse
My first day with the device where I was playing with all the settings, testing out the cam, and using the phone to make a few calls, text, listen to music at the gym, etc....i was at like 54% battery at the end of the day. So battery seems just fine. I charge every night so this should easily last you a day unless you are watching movies and talking on the phone for many hours.

i just got home with my N6 and am so stoked right now. time to root and rom it.

podagee said:
i just got home with my N6 and am so stoked right now. time to root and rom it.
Click to expand...
Click to collapse
Good choice, I always had Samsung and htc devices in the past.
I'm not going back to them anytime soon
Battery life is good enough for me at about 5 to 6 hours of screen on time. If you need more juice, just pull out that turbo charger and charge it quickly.
I do miss my zerolemon 10000mah battery I had on my note 3 tho
The phone itself is very fast and the fact that temaseks cm12 rom is also available for this device made me jump the ship (always used his roms on my note 3)
Have fun

My first couple of days, battery wasn't that great. I think once all my apps installed and everything finished syncing and settling it, my battery has been great. I have averaged about 12-14 hours with 5+ hours SOT. that's on par with my note 3 so I'm happy with it and its snappy as hell. I could t tell a difference after decrypting, so not sure if there is a benefit to doing that anymore. Heard google patched the way encryption works on 5.1

Sammath said:
Good choice, I always had Samsung and htc devices in the past.
I'm not going back to them anytime soon
Battery life is good enough for me at about 5 to 6 hours of screen on time. If you need more juice, just pull out that turbo charger and charge it quickly.
I do miss my zerolemon 10000mah battery I had on my note 3 tho
The phone itself is very fast and the fact that temaseks cm12 rom is also available for this device made me jump the ship (always used his roms on my note 3)
Have fun
Click to expand...
Click to collapse
Was going to download temasek but, i got a question for you. I had no luck flashing cm12 and lollipop dream roms. I am on 5.0 rooted unlocked and twrp 2.8.6.0 installed. My question is will temasek flash with my 5.0 baseband or do i need to update ota then redo everything else then flash temasek?

I used Temasek on the old baseband. I updated it to the 5.1 bootloader later on and it worked for me. Had no problems on the 5.0 bootloader tho.
Keep in mind that temaseks cm12 is encrypted so if you're unencrypted already you will lose all your stuff again since it will force encryption again

Sammath said:
I used Temasek on the old baseband. I updated it to the 5.1 bootloader later on and it worked for me. Had no problems on the 5.0 bootloader tho.
Keep in mind that temaseks cm12 is encrypted so if you're unencrypted already you will lose all your stuff again since it will force encryption again
Click to expand...
Click to collapse
Not too sure on encryption....never touched that part so im guessingbim still encrypted??? Will try out temasek this morningbwhen i get off of work 6am hawaii time. Thanks bro

i just updated to LMY47I. and going to try and flash some stuff...

Nexus 6 - Stock, AOSP, CM and Blends

OK so I know everybody had different experiences but I thought I'd share mine and see what others are experiencing .....
Currently running Multirom
Primary -- Android N
Secondaries Tried -- Pure Nexus, Stock Lite, UberStock, and couple others
The N ROM is just a bit buggy and although there are apparently work arounds I can't get many apps to work. Fairly fluid but not "snappy".
Stock Lite has interestingly been the most steady but requires Cat mod to get the bare minimum Moss that I like.
Weirdly enough despite Pure Nexus being so popular, it and a few other AOSP builds have just not been as reliable. I just got a phone call on PN and the screen wouldn't come on until several power button pushes.
UberStock was snappy but it just irritates me to not have a text percentage battery.
The CM builds of various authors usually have their bugs.
Any thoughts? Or share experiences ..... Not necessarily of a specific ROM but more of thoughts Stock, vs AOSP, vs CM etc
Certainly don't want to insult any developers .... Their shared work is appreciated

jcrompton said:
OK so I know everybody had different experiences but I thought I'd share mine and see what others are experiencing .....
Currently running Multirom
Primary -- Android N
Secondaries Tried -- Pure Nexus, Stock Lite, UberStock, and couple others
The N ROM is just a bit buggy and although there are apparently work arounds I can't get many apps to work. Fairly fluid but not "snappy".
Stock Lite has interestingly been the most steady but requires Cat mod to get the bare minimum Moss that I like.
Weirdly enough despite Pure Nexus being so popular, it and a few other AOSP builds have just not been as reliable. I just got a phone call on PN and the screen wouldn't come on until several power button pushes.
UberStock was snappy but it just irritates me to not have a text percentage battery.
The CM builds of various authors usually have their bugs.
Any thoughts? Or share experiences ..... Not necessarily of a specific ROM but more of thoughts Stock, vs AOSP, vs CM etc
Certainly don't want to insult any developers .... Their shared work is appreciated
Click to expand...
Click to collapse
running pure nexus myself. generally, I like staying with aosp builds. but, user experience can be heavily effected by whatever the user installs or mods. like your power button issue, that can happen because of an app, a theme, or a mod. not because the ROM doesn't like it, but becauseany apps, themes, or mods are not made by professionals, but by amateurs.
stock, I usually am on for the first hour to a max of a couple days after getting a nexus. then its usually an aosp build. CM, or CM based ROMs I stay very far away from. I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.

stock+xposed+gravity box and other modules? you don't really need custom roms anymore, having said that I prefer aosp, cm not even once

sgloki77 said:
stock+xposed+gravity box and other modules? you don't really need custom roms anymore, having said that I prefer aosp, cm not even once
Click to expand...
Click to collapse
Do you ever have or feel like xposed slows things down .....? It's been a while since I've tried
simms22 said:
running pure nexus myself. generally, I like staying with aosp builds. but, user experience can be heavily effected by whatever the user installs or mods. like your power button issue, that can happen because of an app, a theme, or a mod. not because the ROM doesn't like it, but becauseany apps, themes, or mods are not made by professionals, but by amateurs.
stock, I usually am on for the first hour to a max of a couple days after getting a nexus. then its usually an aosp build. CM, or CM based ROMs I stay very far away from. I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
Click to expand...
Click to collapse
Thanks

have all these modules working on pure nexus, snappy as usual
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk

Since the introduction of Lollipop, I really haven't felt the need to flash a custom ROM.
Stock ROM has always worked great for me, I use root for a few things like Greenify and Xposed, but I stopped using those as well.
On my N6:
Stock ROM - Best so far. Sometimes I don't even use root. Excellent battery life, no bugs and great performance.
PureNexus - Great ROM, however the CMTE version was a bit buggy when I used it. No disrespect to the devs, they're doing an excellent job.
CyanogenMod - My second choice, always. Nightly builds are stable in most ways, I'm using one right now and it's working great with a custom theme and a few mods installed.
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
simms22 said:
I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
Click to expand...
Click to collapse
Can you elaborate a bit on this?
Everything seems the same to me.

I got my Nexus last year. I ran several kind of custom roms. Most of them dont last longer then a few hours. The one i am using the most and always go back to is Lite Rom. It has everything that i need and is stable, good battery life and just works. Sometimes i feel like the builders just try to put too many things into the rom and it can be confusing. I like to keep it simple and clean.

@murtaza02: I'm not @simms22, but I can provide some insight here. Back before Android hit version 4, Cyanogenmod was "king of custom ROMs". They were on the cutting edge, with lots of features that simply weren't available in Google's stock Android. This was done not for money, but out of love of Android. A few years ago they incorporated and now offer a commercial alternative to Android. Afterward they pretty much stopped innovating, especially after the Focal fiasco.
Cyanogenmod strayed from its roots, looking to get paid money rather than respect.

Strephon Alkhalikoi said:
@murtaza02: I'm not @simms22, but I can provide some insight here. Back before Android hit version 4, Cyanogenmod was "king of custom ROMs". They were on the cutting edge, with lots of features that simply weren't available in Google's stock Android. This was done not for money, but out of love of Android. A few years ago they incorporated and now offer a commercial alternative to Android. Afterward they pretty much stopped innovating, especially after the Focal fiasco.
Cyanogenmod strayed from its roots, looking to get paid money rather than respect.
Click to expand...
Click to collapse
Yes I recall during the time that this was going on there were several very heated discussions that took place here on XDA. The bottom line though 4 those of us not in the know basically I just noticed that cm ROMs definitely changed

Once they incorporated is when the innovation stopped, as that is when they changed focus away from what brought them to the attention of everyone in the Android community. Instead of making a "better" Android, they settled for simply making Android. The Focal fiasco cost them, in that they lost many of their freelance developers, and lost a lot of respect from the community at large.
To this day I don't put Cyanogenmod on my devices, because Cyanogenmod left the building a long time ago.

To be honest I stopped using CM and CM based roms years ago. While it has a little o do with their business model it was mostly due to the fact that there are bugs that have been around for years that were never fixed. Then they merge in code without testing it which has been known to cause huge issues.
I prefer roms built from AOSP which there are very few. I also never go for what is popular. To be honest to many people are sheep and follow the crowd. (yes even in android) I prefer to try some out and make up my own mind. And then I stick with it.

Honestly, I ditched Cyanogenmod because they stopped being innovative. It goes hand in hand with them incorporating, because the profit motive overrides everything else. Profit first, last, and always.

Which Oreo ROM to pick? (And why?)

With the recent influx of Oreo ROMs I was wondering just what people are using now and why?
I personally am still on AICP 12.1 Nougat, simply because I use my phone a lot and found it to be quite stable and very battery friendly.
But as a enthusiast I can't lose that itch that is telling me to finally upgrade my Mix to Oreo...
So, tell me about your experiences and why you made the choice you made.

MrColdbird said:
With the recent influx of Oreo ROMs I was wondering just what people are using now and why?
I personally am still on AICP 12.1 Nougat, simply because I use my phone a lot and found it to be quite stable and very battery friendly.
But as a enthusiast I can't lose that itch that is telling me to finally upgrade my Mix to Oreo...
So, tell me about your experiences and why you made the choice you made.
Click to expand...
Click to collapse
I was on Oreo builds but ended up returning to AOSiP Nougat. Been on it for 2 weeks, feels comfortable and stable and etc. First tried AICP 12.1 but a visual glitch occurred due to using RTL layout. Not even a single issue on AOSiP that I'd call it a deal breaker. Cheers.
Sent from my Xiaomi Mi Mix using XDA Labs

Konstantine34 said:
I was on Oreo builds but ended up returning to AOSiP Nougat. Been on it for 2 weeks, feels comfortable and stable and etc. First tried AICP 12.1 but a visual glitch occurred due to using RTL layout. Not even a single issue on AOSiP that I'd call it a deal breaker. Cheers.
Click to expand...
Click to collapse
What made you go back? Did you perceive any deal-breaking issues?
The only thing that really irks me on AICP 12.1 Nougat is that it (randomly) black screens on me after 2-3 days of continuous use.
My hopes are that with my next move I can finally leave that bug behind.
I obviously don't want to invite additional bugs however...

MrColdbird said:
What made you go back? Did you perceive any deal-breaking issues?
The only thing that really irks me on AICP 12.1 Nougat is that it (randomly) black screens on me after 2-3 days of continuous use.
My hopes are that with my next move I can finally leave that bug behind.
I obviously don't want to invite additional bugs however...
Click to expand...
Click to collapse
Sorry, missed the why part. On Oreo roms, there are issues like Mobile network stand-by drainage which is always draining more amperes than the rest(while using the mobile data connection). And the proximity issues, one has got an almost working proximity sensor but at the same time breaks the in-call sound when you switch between speaker-earphone and the other one has no proximity sensor which sometimes become irritating. One of these is becoming a deal breaker after sometime.
Beside, there is no black screen issue on AOSiP for two weeks of usage, but I was and am using Floppy kernel RC 1.2(Google toolchain one) for the whole time. Take a look at the Up time in the screenshot, there is not even a reboot or freeze. You may want to give it a go.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Xiaomi Mi Mix using XDA Labs

After taking the time and checking all (I kid you not) Oreo ROMs out there I have finally settled down on Pixel Experience for now.
It's less feature packed than the other ROMs (given it's pure AOSP focus) but as such it's the only one I've found without "broken" features, glitched settings menus, etc.
So far everything seems to work, sans the proximity sensor, which is more or less the same completeness of functionality my previous Nougat ROM had.
I was forced to rely on Magisk and Xposed to get my beloved Pie Controls back up and running however (as all app-based implementations out there suck so far).
I'll take my time with this ROM now and report back after a week or so of active use. That should give me enough time to test everything out properly.

MrColdbird said:
After taking the time and checking all (I kid you not) Oreo ROMs out there I have finally settled down on Pixel Experience for now.
It's less feature packed than the other ROMs (given it's pure AOSP focus) but as such it's the only one I've found without "broken" features, glitched settings menus, etc.
So far everything seems to work, sans the proximity sensor, which is more or less the same completeness of functionality my previous Nougat ROM had.
I was forced to rely on Magisk and Xposed to get my beloved Pie Controls back up and running however (as all app-based implementations out there suck so far).
I'll take my time with this ROM now and report back after a week or so of active use. That should give me enough time to test everything out properly.
Click to expand...
Click to collapse
It's been a week now and I've been pleasantly surprised except for two things:
Battery life isn't quite up to par to what I had on AICP, which is a shame because I've gotten so damn used to the thing lasting me three days.
Now I need to recharge every second day.
Still better than most smartphones but I know we can get more out of this and I'm looking forward to new builds of the ROM addressing this.
The second thing is mostly a personal thing and some people will be totally unaffected by this.
Namely, the lack of built in Pie Controls...
I've come to enjoy the huge screen estate that is the Mi Mix and I just hate wasting space with a navbar.
This is where Pie Controls usually step in, but with Pixel Experience I'm forced to "add those in" via a combination of Magisk and systemless Xposed + Gravity Box.
This ends up double irking me as I prefer to run ROMs clean instead of hacking them up to add things which in my opinion should have been part of the basic bundle.
And... I guess as a optional third issue: Yes, the proximity sensor doesn't work on it but... I'm not really missing it.

MrColdbird said:
It's been a week now and I've been pleasantly surprised except for two things:
Battery life isn't quite up to par to what I had on AICP, which is a shame because I've gotten so damn used to the thing lasting me three days.
Now I need to recharge every second day.
Still better than most smartphones but I know we can get more out of this and I'm looking forward to new builds of the ROM addressing this.
The second thing is mostly a personal thing and some people will be totally unaffected by this.
Namely, the lack of built in Pie Controls...
I've come to enjoy the huge screen estate that is the Mi Mix and I just hate wasting space with a navbar.
This is where Pie Controls usually step in, but with Pixel Experience I'm forced to "add those in" via a combination of Magisk and systemless Xposed + Gravity Box.
This ends up double irking me as I prefer to run ROMs clean instead of hacking them up to add things which in my opinion should have been part of the basic bundle.
And... I guess as a optional third issue: Yes, the proximity sensor doesn't work on it but... I'm not really missing it.
Click to expand...
Click to collapse
Thanks. I have been wanting to switch to Oreo myself but wasn't sure which one was a stable option. I am on Nougat RR and it's running flawlessly. Your review definitely helps. I will wait a little more before making a switch.

psychedelicNerd said:
Thanks. I have been wanting to switch to Oreo myself but wasn't sure which one was a stable option. I am on Nougat RR and it's running flawlessly. Your review definitely helps. I will wait a little more before making a switch.
Click to expand...
Click to collapse
I've found this ROM to be very pleasant to use, even now. I'm sure you'll enjoy it.
If I had to add anything to my previous summary it is that at times the phone will heat up quite a lot.
I haven't found out what triggers it yet and it's seemingly random and as such I can't guarantee that the blame actually lies with the ROM or an app of mine.

MrColdbird said:
I've found this ROM to be very pleasant to use, even now. I'm sure you'll enjoy it.
If I had to add anything to my previous summary it is that at times the phone will heat up quite a lot.
I haven't found out what triggers it yet and it's seemingly random and as such I can't guarantee that the blame actually lies with the ROM or an app of mine.
Click to expand...
Click to collapse
Maybe the current governor profile for your kernel is ineffective. See if you can put a custom kernel and then play around with the governor or CPU settings (if you are unsure on this, do not risk it)
I had a similar issue when I first started using RR. Someone pointed me to use the AKT Profiles apk and select one of the governors. My phone went from being toasty all times to a cool cucumber. Further updates to RR fixed the issue.
Hope this helps.

I’ve been running RR Oreo for months with no major issues. The general responsiveness seems faster than Nougat, though it's difficult to judge, and although the battery life appears to drop faster, I get the feeling that this is more to do with a change in the way the remaining battery life is measured rather than a higher drain rate i.e. nougat used to stay high longer then drop quickly when approaching empty, oreo seems to drop more evenly maybe even slowing down towards empty.
I'm looking forward to trying LOS when it comes of age, but for now, RR gets two thumbs up.
Slàinte
mmidders

I've come to the same conclusion about battery life in the new Oreo based ROMs.