Should I upgrade P6210 from 4.1.2 to Cyanogenmod 13.0? - Samsung Galaxy Tab Plus

Background: I bought the Galaxy Tab 7.0 Plus P-6210 more than 3 years ago. Originally, it had 3.2 and was always re-booting and losing connections. About 2 years ago, I was able to upgrade to 4.1.2 by flashing a UK stock version. It has been very stable and reliable. Lately, i have had difficulties connecting to certain websites and have been told that my OS is too old. Also, some apps can only work with the newer OS. So I am thinking about updating to Cyanomodgen 13.0, but I am very concerned about all the possible problems. I still use this Tab a lot for Yahoo emails and web-browsing.
Can any P-6210 owners advise me about all the pros and cons with updating this particular Tab from 4.1.2 to CM 13.0?

Never mind. I decided to just bite the bullet and flashed the CM 13.0 with the help of my son.
We had to do it a few times to get it to work. The stock gapps was too big and i kept getting an error 70. I switched to the pico gapps which flashed but after rebooting, i kept getting a pop up saying i had lost play services. I found that i had to wipe and to flash the rom and gapps at the same step instead of two separate steps to get it to work.

I used the CM 13.0 rom for a couple of days. It is usable, but glitchy. It was fun to play around with the new features. But once the novelty wore off, i found the lagginess and occassional force closes and reboots to be annoying. I could have lived with it if i had to. I decided to restore the 4.1.2 backup, mostly just to see if i could do it. It was like a breath of fresh air.
EDIT: I decided not to both with the unofficial kitkat or lollipop roms and just focus on any custom marshmallow roms. They are all located at the XDA Galaxy Tab 7.7 forum.

i flash on p6200 latest daniel's cm13 of 29/7/2016, it is a bit laggy, but major bug are screen mirroring not working and swipe on aosp keyboard not working...
Can i resolve those?

re p6200
I tried loads of the different ROMs here, mainly from daniel_hk, massive kudos to him, from kitkat, lollipop and higher, Carbon ROM, Slimkat, OMNI (which I love) etc, but all of them are rather unstable and the CPU seems to overheat all the time.
I also keep reverting to the 4.1.2 firmware, which to this day works fantastically and stably with dozens of the apps I use daily working fine.
I love my galaxy tab plus
---------- Post added at 21:06 ---------- Previous post was at 20:58 ----------
PS recently a friend gave his old fitness watch with a heart rate monitor, but neither my tablet or phone could communicate with it. I tried the newer android, the app installed but it still didn't work. Turned out the bluetooth was also too outdated.
In the end I bought the cheapest smartphone I could find for 30 US dollars, which had bluetooth 4.0 and Lollipop, and it works fine with the bracelet.
So, I suppose there's no point in upgrading to higher android anyway as the hardware can't keep up the higher demands.

Related

CM 10.1 (JB 4.2) on my Cappy = awesome

Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse
daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yeah Factory reset is recommended. And its Working great. I must ask you to consider updating to 4.2, 10.1 nightly build. Its literally flawless...
Sent from my SGH-I897
cm10.1 really cool. Waiting for slim android 4.2
Several days ago I did the upgrade to 10.1 from 10 without the factory reset - no problems, but wipe the caches). You need to clear the clock data first and do the upgrade from the boot screen (not the update screen in about phone). Do a backup just in case you have problems.
for further info go to :donandroid.com/how-to-update-cm10-to-cm10-1-with-cwm-recovery-581
ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
+1
Sent From the Land of Defrag
if you do Erase SD Card, does it erase internal storage instead?
I tried the stable version of CM10, and it seemed to work great except for one thing. I could connect to my employer's Exchange server at all. I tried all kinds of things and it just couldn't connect. I took it to the IT guys and they fiddled with it for a while and couldn't get it to work either. A little quality time with Google told me that JB has a bug that sometimes makes it impossible to connect to corporate exchange accounts. I ended up switching to CM9. Do you know whether CM10.1 fixes that? If so I think I'll give it a try.
ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
Slim 4.2.1 has been available in beta for a week or two now... I've not encountered any problems with beta 2 so far.
http://forum.xda-developers.com/showthread.php?t=2060386
falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!
thank quá hay :
theoctagon said:
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!
Click to expand...
Click to collapse
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?
CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897
laughingT said:
CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897
Click to expand...
Click to collapse
So for a stable fast ROM, you would suggest CM 10.0 over AOCP or some of the other 4.1.2 "final" version ROMs like SlimBean?
depends on your personal preference I suppose. you need to get to CM9 at least, preferably 10.0, to flash slim bean, right? So, if it runs well on 10.0, then you could go slim bean
you wrote that you just want the basics, nothing fancy. so, yes, CM10.
Sent from my SGH-I897
daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yes, I did. And I didn't really have any problems with Semaphore, it just seemed a little laggy.
RichMD said:
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?
Click to expand...
Click to collapse
I would highly recommend Sephhi's [ROM][4.2.1]Captivating (Xperia Themed)
It is CM10 based and is stripped down to run smooth.
http://forum.xda-developers.com/showthread.php?t=2057574
Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?
BELbX said:
Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?
Click to expand...
Click to collapse
Try hellybean 4.2. Hellybean came a long way from when i used it a while back! It's a much smaller and light weight package as compared to the xperia one. Barely any issues. Boot times and first boot are quick. Over clocking is fun again too. I thought it was oc'd at first for being smooth. It's so smooth and stable. One or two things, but nothing compared to others. I like the xperia one but it's heavier with more to be worked. It's running better then aokp 4.1 with semaphore.
Sent from my SGH-I897 using xda app-developers app
3g Problem
I just flashed 4.2.1 AoCP 5 and lost my 3G. Anyone know what's up?

S3 constantly crashing

Hello,
I bought a VZW Galaxy S3 at the end of May. I left Touch Whiz on it for about a week before I couldn't stand the look of it any more, It also started freezing and I would have to hold the power button down to reboot it. This would happen 2-3 times a day so I decided to go with a custom rom. I had rooted and installed custom roms on my Nexus 7 several times before so I felt comfortable doing it on my S3. I was able to root it and unlock the bootlader and I installd TWRP as my custom recovery. I flashed the AOKP rom and was using that for several weeks. Initially it worked great and crashed maybe once a day but I figured that was normal for a custom rom. After a few weeks it started to crash more and more. I finally ended up restoring the phone from an AOKP backup I had made the first day. That seemed to help a bit. After it started to get worse again I switched to SlimBean. This one was the worst. It worked good for a few days then crashed constantly. Finally, after getting extremely frustrated I flashed CM 10.1.2 I decided to go with one of the Milestones to be on the safe side. This was working great until now. It constantly freezes and crashes. Also, many of the apps crash. I am just wondering if this is an issue with how I unlocked and rooted it or if this is an issue with my phone? I have also noticed I have terrible reception with any rom even stock. What roms would you guys recommend as a very stable one? I know CM is supposed to be. Any help would be greatly appreciated. Sorry for the long post I wanted to make sure I included enough information.
Thanks.

Best ROM for running kids' games?

Hi everyone,
Simply put, what's the best ROM to use specifically for a 7 year old who wants to play games like the Lego games, Minecraft PE, and that awful bloons TD battles?
Everything was fine until my child's p5113 updated itself automatically to 4.2.2. Immediately after, it became unstable, frequently crashing and rebooting itself. Oddly, my other, identical p5113 used by my other child had no issues with the 4.2.2 update. Maybe a bad download flash? After some months of hearing complaints of the tablet freezing/rebooting in the middle of my kid's games, I decided to flash a custom ROM and get rid of all the bloat.
I used a May build of Omnirom which was much more stable, but I grabbed it at a time when it was having issues with disabling the keyboard (it assumed a hardware keyboard was present). So after every reboot I had to go into settings and fix it, not useful for a 7 year old child. But we made do through spring and summer until things started getting unstable again.
I installed Slimkat yesterday, and it looks beautiful, but the LEGO Speedorz game installs but dies right before the racing action starts. Bloons battles downloads but gives an error during installation. Sigh.
Cyanogenmod gives the same problems with the games, as does the latest Omnirom.
I don't care at all about fancy stuff, I just want something basic t hat actually works for my kid's games. I've installed several ROMs over the past day... several wouldn't even boot. I'm tempted to get an account at SAMMOBILE to get the stock firmware and flash that, but stock is so bloaty I imagine that's a source of problems.
I suspect I may have an actual board problem with the tablet, but before selling this one for parts and buying a new one, I'd like to exhaust all possibilities. Any ideas?
Thanks in advance!
Marc
My daughter has Stock 4.1.1 (P5113UECLK7) rooted with the Next kernel and it seems to be ok. She runs a Ton of games daily with Minecraft being number 1. I have the file but am unable to upload it here so I would have to send it thru an email link. I have various others as well....Pure Vanilla 4.2.2, Brolees 4.2.2 and Shakatus newest Zapblaster v2.3 which is 4.2.2 Thats a really zippy ROM and he just updated it for the last time so its pretty new and very good. You can get that one on xda but I believe that all the lenks are down for the rest I mentioned. But I do have them just in case.
CSP III said:
My daughter has Stock 4.1.1 (P5113UECLK7) rooted with the Next kernel and it seems to be ok. She runs a Ton of games daily with Minecraft being number 1. I have the file but am unable to upload it here so I would have to send it thru an email link. I have various others as well....Pure Vanilla 4.2.2, Brolees 4.2.2 and Shakatus newest Zapblaster v2.3 which is 4.2.2 Thats a really zippy ROM and he just updated it for the last time so its pretty new and very good. You can get that one on xda but I believe that all the lenks are down for the rest I mentioned. But I do have them just in case.
Click to expand...
Click to collapse
Excellent. Thanks. If you could PM me a link to Pure Vanilla that would be great. I was looking for that one yesterday and the links were dead. :crying: The Shakatu mostly stock/rooted one didn't boot for me for some reason. But Ripper ROM based on it seems to be working well. Would love pure vanilla as a backup. I will also look into the zapblaster one.
Thanks so much for replying!
Marc
Sammobile and samsung-updates both have that file. Sammobile doesn't send me any emails even though I have an account so that isn't really a problem. The accounts are free. If you root it, you can remove the extra system apps. You could also flash the next kernel for some extra speed and overclock.
jrc2
Sent from my T-Mobile S2 using Tapatalk

(Mostly) Happy Samsung Galaxy Note 3 SM-N900 Exynos User

Hi
I'm new to XDA, but have used the site for years for various reasons and never found the need to post. I am posting some threads to get my count up in order to participate in the development for my phone, the aforementioned Exynos Note 3.
I picked up my N900 used off of eBay for $180 with free shipping. The previous user had kept it in great shape; no scratches on the screen, and with only a couple of dings on the metal edges. I was running the stock Kit Kat ROM when I got it, but for obvious reasons, I wished to upgrade. After careful examination of the Exynos Development section for N900's, I chose the "Dr Ketan" Lollipop L24 ROM. I found this ROM to have a lot of features, almost too many for my purposes. I also found that when it was first installed it ran very smoothly, but gradually (as I added my apps) began to slow down, and I never quite figured out why. I used L24 for about 6 months, reinstalling it once or twice along the way without too many problems. However, the lag became unbearable after I picked up an old used iPhone 5 running iOS 9.3.0. By comparison, the iPhone with it's fraction of the total CPU and RAM of the Note 3 was as smooth as silk. I had to find a new ROM for my N3.
Once again, back to the XDA Exynos N900 section. I liked the progress on CM12 and CM13, but they both appeared too buggy for an everyday driver. After I read that SlimLP was giving people the highest benchmarks of any Note 3 Exynos ROM, I tried it. Installation was a breeze; wiped everything, flashed the ROM zip and then the SlimLP GApps. Right off of the bat, I could tell this ROM was a dramatic improvement over L24. Everything ran more smoothly. The added features of 5.1.1 were the icing on the cake...
I've had SlimLP installed on my N3 for a few days now, and everything is better about my N3; it runs the way I expect an 8 core, 3GB pocket PC to run. I have had only a few problems with it. For some reason, one of my reminder apps refuses to display notifications and run alarms. I use this app each day and I am trying to figure out why it's not working, with limited success. I am going to switch to a different type of reminder app and see if that helps. Other than that, everything seems great.
Thanks to everyone at XDA for their time and effort in preserving the community for continuing development on these handsets that the manufacturers have abandoned.
really? I want to try too. SlimLP right?
Leang Vannak said:
really? I want to try too. SlimLP right?
Click to expand...
Click to collapse
That's correct.
http://forum.xda-developers.com/gal...nos-android-development/rom-12-04-15-t3263881

Custom ROMs... Are they still worth it?

I have been a flashaholic for some time, probably the Eclair days, but I really question if it's worth it now days.
Most Lollipop and newer ROMs, except for Nexus devices, seem to have some kind of issues... If not immediately, then over time. While at the same time factory ROMs get better, partially because the base code is better and because many manufacturers are getting better at it.
And now, some features are being blocked just by unlocking of bootloader, even if you're otherwise stock, like Android Pay and others like Pok�©mon Go.
I find all I really do now on custom roms is some interface tweaks... Change the battery icon, add a clear all button to recents, and add arrows to the navigation bar, all minor stuff. Otherwise things like Nova Launcher, SwiftKey, and GSAM largely don't even require root anymore much less a custom ROM. Part of it used to be for battery life, but now, at least on modern Moto devices, most custom roms struggle just to match the battery life of stock.
I've tried every rom for this device I can find, here and other places, and they all seem to have a variety of things that fail, from minor annoyances to major services broken like GPS, or they fail over time.
My question for discussion is it still worth it, and why do you ROM or even root anymore?
I used to run a variety CM ROM's on Samsung Galaxy & Note devices. Starting with the Galaxy S2 Skyrocket and then every decent device Samsung released until the bootloaders stopped getting cracked.
There was always something that just didn't work right and I'd have random crashes.
But for me it was semi-worth it. I like to tinker and customize a lot.
Fast forward to the last thirteen months with my first non-Samsung since. A Motorola Moto X Pure.
Best damn phone I've ever had.
And there is CM available, but I quickly discovered AOSP ROM's like Dirty Unicorn and Broken OS.
Both these ROM's are FULL of customization not found in Xposed modules, and both ROM's have been 100% reliable.
I may have had one lockup in the last 13 months. And everything from GPS to Bluetooth, etc. have all worked perfectly.
So for me, yes... custom ROM's are more than worth it once you find the right ROM. My phone is heavily customized to my needs and super reliable.
The only thing lacking with MotoX was kernel development. Which I guess is where you start losing some reliability.
But it's also where I'm hoping the Pixel will get some good development and I'm looking forward to it. :good:
Non-rooted stock MM has been going great for me lately. Lots of great built in features like Moto actions, etc. I play Pokemon while walking on my breaks at work, and the last few updates forced my hand to go back to stock. I was (am) also a flashoholic, and it was mainly to have custom features and better performance on outdated and mfg abandoned phones. It was also a must for my Kindle Fire. I really don't see myself going away from stock MM (soon to be Nougat) on my MXPE at this point. I still flash ROMs on my G2 and Note 3 though, but barely use them outside the house.
CZ Eddie said:
I used to run a variety CM ROM's on Samsung Galaxy & Note devices. Starting with the Galaxy S2 Skyrocket and then every decent device Samsung released until the bootloaders stopped getting cracked.
There was always something that just didn't work right and I'd have random crashes.
But for me it was semi-worth it. I like to tinker and customize a lot.
Fast forward to the last thirteen months with my first non-Samsung since. A Motorola Moto X Pure.
Best damn phone I've ever had.
And there is CM available, but I quickly discovered AOSP ROM's like Dirty Unicorn and Broken OS.
Both these ROM's are FULL of customization not found in Xposed modules, and both ROM's have been 100% reliable.
I may have had one lockup in the last 13 months. And everything from GPS to Bluetooth, etc. have all worked perfectly.
So for me, yes... custom ROM's are more than worth it once you find the right ROM. My phone is heavily customized to my needs and super reliable.
The only thing lacking with MotoX was kernel development. Which I guess is where you start losing some reliability.
But it's also where I'm hoping the Pixel will get some good development and I'm looking forward to it. :good:
Click to expand...
Click to collapse
Hmm... I have been on that "rom that shan't be named on XDA" for a while now. After a month started suffering SoD randomly and Play Services has stopped issues. DU 10.6 couldn't maintain GPS lock, but 10.5 was fine, seemed to effect only a handful of devices, lucky me.
Anyway, thanks for your input.
acejavelin said:
Hmm... I have been on that "rom that shan't be named on XDA" for a while now. After a month started suffering SoD randomly and Play Services has stopped issues. DU 10.6 couldn't maintain GPS lock, but 10.5 was fine, seemed to effect only a handful of devices, lucky me.
Anyway, thanks for your input.
Click to expand...
Click to collapse
I also have been a avid user of the "rom that shan't be named on XDA" for many months now with no real issues. By chance have you tried a fresh install again. The latest release was back in late August a 4.9.1 version that made corrections to some issues on the 4.9 release.
Jimi Mack said:
I also have been a avid user of the "rom that shan't be named on XDA" for many months now with no real issues. By chance have you tried a fresh install again. The latest release was back in late August a 4.9.1 version that made corrections to some issues on the 4.9 release.
Click to expand...
Click to collapse
Not yet... I have been on 4.9.1 already, and have been working with the devs a bit on it but seems mostly isolated to my device.
acejavelin said:
Not yet... I have been on 4.9.1 already, and have been working with the devs a bit on it but seems mostly isolated to my device.
Click to expand...
Click to collapse
If anything try a fresh install and see if your issues were only from maybe a bad original install. If they show up again then I would say they are isolated to your device.
Jimi Mack said:
If anything try a fresh install and see if your issues were only from maybe a bad original install. If they show up again then I would say they are isolated to your device.
Click to expand...
Click to collapse
I'm out of town for the weekend, in a rather rural area, so maybe will try tomorrow evening.
LMT pie, adaway, naptime, and general tweaking are the only reasons I root on a phone this close to stock android.
I didn't run custom ROMs on this phone until about August of this year. That was when battery life on aicp started to get comparable with stock for me. I can get most of the features I want from gravitybox, but I prefer them baked into the ROM. Xposed always seems a little problematic even when you don't install janky modules. I really like the notification led; missed that when I got this phone. I know we're supposed to use moto display, but I think that makes more sense on amoled than a great big LCD. Never had good luck with lightflow or the led enabler apps, but the custom roms work great. I really like slim recents too. I haven't found any modules that work to put KitKat like recents on M ROMs.
TruPureXMM + GravityBox
Loved my MXP so much I bought one for my mom who was hating her iPhone5. Kept it stock (for obvious reasons), so I have a good baseline to compare to my MXP running TruPureXMM + GravityBox. I've tried a bunch of ROMS for this phone but I always come back to TruPureXMM + GravityBox. Oh, and Tasker.
There is no way in hell I would go back to stock.
I used Cyanogenmod on my HTC Incredible and Verizon Galaxy Nexus. Didn't root or ROM for a while due to using the stock ROM on the 2nd generation Verizon Moto X 2014 and stock Android on the Nexus 5X and 6P. But, I had the itch to unlock the bootloader on my Moto X Pure, due to curiousity, and because it's likely that we will only see one more Nougat update. I tried CM13, but I was getting UI freeze ups and slowdowns on multiple builds, so I tried Dirty Unicorns 10.6, and that has been working fine. I may return to the stock ROM after the Nougat update, but in the meantime, I'm happy experimenting with different ROMs on the Pure.
I'd be cool with stock- as long as I could debloat it.
And it was updated fairly quickly.
Stock for this phone is great. Better than most. Only issue really is Moto is so far behind on security updates. They are on what, May I believe? CM13 is Oct.
Sent from my XT1575 using XDA-Developers mobile app
Stock here, never a issue. With Nougat in the horizon, a custom ROM is a big NO for me.
Enviado desde mi XT1575 mediante Tapatalk
I would say TruPureX with a few mods is a very solid and stable way to go. I myself am on TurboROM which has ceased current development, but have ZERO issues. AICP's MM build is the most feature filled and works flawlessly aside from one issue I don't have on other ROMs, where my bank app only shows black when using the camera to deposit checks, making AICP unusable for me, but highly recommended for others to try as that's the absolute only issue I could find after a week full of testing (Kind of what I do as a hobby is push ROMs to their limits to find the issues.)
So in short: TruPureXMM, TurboROM, AICP - are all great choices without the negatives associated with many custom ROMs.
Pretty sure we are all here to push the ROMs to he limits lol?
Sent from my XT1575 using XDA-Developers mobile app
Speaking of custom ROMs, I just searched android file host for Clark and there are new 7.0 builds of zephyros, pure nexus, aosp, and cos.
I'm in a limited data area so I haven't downloaded or tried them out yet.
jason2678 said:
Speaking of custom ROMs, I just searched android file host for Clark and there are new 7.0 builds of zephyros, pure nexus, aosp, and cos.
I'm in a limited data area so I haven't downloaded or tried them out yet.
Click to expand...
Click to collapse
Running the latest Zephyr after trying AICP and CM14. Uses substratum and SuperSU. Camera recording isn't working with snapdragon camera (FC), google camera (records but doesn't save). Had an android.phone FC but replaced with google phone/contacts and no problems so far. Still need to test speakerphone and bluetooth, but assuming those work as well as 6.0.1 I'm pretty impressed by Birdman.
Any roms that anyone can recommend? CM13 and OrionOS both have very bad stuttering after some time of use. Has anyone tried Pure Nexus or Slim6? Just need a good daily driver that can handle games without heating up so hot, and handle most social apps great...
jason2678 said:
Speaking of custom ROMs, I just searched android file host for Clark and there are new 7.0 builds of zephyros, pure nexus, aosp, and cos.
Click to expand...
Click to collapse
Seriously? We've got like one and a half here.

Categories

Resources