What are you all's observations on the operation, stability, reliability and or issues with the new 3.0 release? Does is also solve the modem flashing issues present in 2.8.7.0?
http://forum.xda-developers.com/oneplus-one/general/twrp-3-0-0-tried-test-feedback-t3309543
Related
Hi,
After flashing a few ROM/Kernel combinations on my dad's I9023, eventually running into problems every time, we're now tired of having to attend to the phone and just need something stable and self-sustaining, but still better than the stock offering, if possible. Reliability is the main concern, followed by performance, followed by features and easy upgradability to the next Android version (or the custom ROM's equivalent), but battery life is low priority.
Thanks in advance for any suggestion.
knzo strawberry
rasbeanjelly
flo's stock 4.1.2
The closer to stock, the safer.
Strawberry is a good candidate.
Thanks for your replies. So far, Strawberry does look like the best option. Questions:
1. Does it keep up with Android updates?
2. Once it's flashed, will updating it to the latest version require wiping user data every time?
3. Which kernel should I use with it?
Glaux said:
Thanks for your replies. So far, Strawberry does look like the best option. Questions:
1. Does it keep up with Android updates?
2. Once it's flashed, will updating it to the latest version require wiping user data every time?
3. Which kernel should I use with it?
Click to expand...
Click to collapse
1. Your question is strange. Does it get updated? Yes. Keep up with Android updates? As in cross version (GB/ICS/JB)? Probably won't. But that doesn't mean crap, because CM7/9/10 are all different and flashing from one to the other without wiping is just bad omen. So in the end, it doesn't matter if your favorite ROM moves from one version of Android to the other. You want something new? Find a new ROM. There's only very few roms that went from ICS to JB without notable changes and none as far as I'm aware that went from GB to ICS to JB.
If you mean incremental updates (say, Jellybean gets updated) then yes, most ROM cookers update their roms.
2. No
3. Included kernel
I did mean incremental updates, thanks.
Glaux said:
I did mean incremental updates, thanks.
Click to expand...
Click to collapse
Alright. Then yes, most roms available here are update incrementally by their developpers. Usually popularity brings constant updates, too.
You want true "flash and forget" for your dad, Flash factory from Google. If your Dad doesn't care if it is custom or stock, just flash factory and move on. All custom Rom's and kernels come with issues. Google's bugs are solved by Google and send the update via OTA so Dad can do it himself.
https://developers.google.com/android/nexus/images
Use this guide
http://forum.xda-developers.com/showthread.php?t=1785672
I've never had any issues with RasBeanjelly. So saying that all roms have issues and bugs is a bit weird.
Flash RasBeanjelly and trinity or bedalus kernel (check for stable one) and forget all about it as it is incredibly stable!
Sent from my Nexus S
Well I recently gave slim a run and noticed it has the ota update option, so that may be an option.
I dont know if its my phone or what but I haven't had any luck with AOSP ROMS on this phone. It seems like there's always some sort of bug that just kills it. I flashed a CM10.2 rom that felt like speed of lightning but was bugging out. I tried ecilpse and some others but all were to buggy for me. I recently tried to flash liquid cause I wanted to run something else other than touchwiz but it ruined my phone and now I cant flash custom ROMS(i have a help thread up..feel free).. Anyone else having bad luck on these AOSP ROMS
Not what you want to hear, but I'm having no issues with flashing new ROMs. I'm only using LiquidSmooth and waiting/hoping for a 'complete' 4.3 version, but again, no problems with flashing to a new ROM. I have been running LS2.9 (4.2.2) for several weeks and on Sunday flashed up to LS2.10 (4.3) but went back to 2.9 because when I mirror my phone on my AppRadio3, it doesn't auto-rotate my screen to landscape, so I have a portrait orientation of my phone on the radio display, which makes it so small as to be unusable.
I don't recall what method I used to root my phone, but I'm using TWRP 2.6.3 to perform a) a clean wipe every time (Factory Reset + System), then b) install the new ROM, and c) a final reboot back in to recovery and flash the latest gapps image. Does it take a little longer to follow this process? Sure, but it's a reliable process that means I don't have issues afterwards to mess with, so the extra time spent on the front end is worth it to me.
I've had moderate success with the AOSP ROMS. Each one seems to have it's own small bugs, but the AOSP ROMs that I've tried didn't have anything that ruined functionality. Been running Dirty Unicorn ROM for the past couple days and it is really solid. Haven't noticed any issues at all with it yet.
It's got to be your downloads or install process. Do you check MD5? If no then start. Remember just wipe data for each install. Updater-script in ROM zip wipes system for you. Cache resides in data. Do NOT restore system data using TiBu. Other than that I don't know what else to tell ya bud :/
Sent from my SCH-I535 using Tapatalk
Haven;t had any trouble with AOSP flashes, but many of the ROMs or maybe most have some bugs. All the so called AOSP ROMs are built off the same base, CM10. None of them support all the hardware and software features that Tocuhwiz supports. I find the custom TW ROMs far superior in features and as good or better in speed as well.
Make sure you are flashing a compatible Kernel when you switch between CM based ROMs and TW based
I've got a rooted XT926 with unlocked bootloader. I've flashed plenty of custom ROMs on the phone including ones running 4.1, 4.2 and 4.3. I'm gradually moving back to earlier stock-based ROMs because, while the extra features are cool, I grew tired of random main functions that didn't work properly and my battery life was getting progressively worse.
Now I'd like to know for sure I'm running the stock kernel. How do I determine this? My kernel version is 3.0.31-g101ca72. The date of "Thu May 30 18:22:06 CDT 2013" also appears in this subheading of Settings/About Phone.
If I'm not running the stock kernel, where do I find it? I've done plenty of searching but can't seem to find a downloadable stock kernel that I could simply flash from TWRP recovery. Most of the posts of this nature are about unrooting and restoring stock. I don't want to do that. I want my phone to remain rooted but I'd like to know that I'm either on the stock kernel or can find it and flash it.
Not really sure how to check, but if you fastbooted back to stock you have the stock kernel. If you found a stock based ROM and flashed via recovery, unless stated otherwise in the post it should have the stock kernel. And have you tried arrrghhh's kernel? It works really well. It's for all msm8960 (or whatever msm we are) devices so it will work as long as you download the stock version.
Sent from my MB886 using Tapatalk
What would be the point of using arrrghhh's kernel with a stock rom? Or, what does his kernel do differently than the stock one?
At the moment I'm running RageHD 2.3, a straight-forward stock-based ROM running 4.1.2. It's doing pretty much what I want -- everything works, smooth and solid, better battery life than I was getting with 4.2.2 and 4.3 ROMs and improved signal strength. Still, I read from time to time that custom ROMs tend to give improved functionality and lessened bloat but that they also shorten battery life, sometimes substantially. To test this myself I need to know that either I'm on a stock kernel now or that I can find and flash a stock kernel.
Hello everyone,
I'm really enjoying these kitkat based roms for the Atrix 2, however I'm having issues loading JBX 3.0 (2/27/14) on roms like liquid smooth and nexus experience. Without the custom kernel, phone boots up fine and everything works. However, the phone does not seem to recognize sim card and has no mobile network with JBX installed. I have tried unticking the 10% battery mod and I believe it's called the xposed framework in different configurations nothing works. Additionally, I have the same issue when I attempt to boot this newer version of jbx over the older version integrated into Gummy. Any help with this issue would be greatly appreciated!
Most custom ROMs already have this done but if you're stuck on a stock build this little ditty will definitely improve the performance of your phone ...
https://www.yahoo.com/tech/secret-settings-android-phone-feel-twice-fast-152712638.html