I got a Nexus 7 2013 (32GB wifi) off of reddit.com/r/hardwareswap for $80, and absolutely love it.
Naturally I applied the 5.0 OTA update, rooted it, and installed ClockworkMod Touch first chance I got.
Frustrated by not being able to apply the 5.0.2, I realized that Cyanogenmod 12 was based on 5.0.2 (or at least the latest nightly was) so I figured that was the best way to get the newest version, and would make updating easy after that (cyanogenmod's update tool works great, much easier than flashing updates individually, or hoping a stock ota update will play nice with your custom recovery)
After that my nexus 7 was almost perfect, but I had to get the stock boot animation back because it's way cooler than CM12's.
Finally, I REALLY wanted the ability to double tap the screen to wake it. This is something that I've gotten so used to on my Xperia Z3, and there was a nice way to do it that required Xposed framework, which doesn't work on ART, so that is out. It seems that getting a custom kernel that will play nice with the TouchControl root app is the only way I've been able to find that will let you do the double tap to wake thing.
Anyway I flashed the lastest Franco Kernel and it totally jacked up my Nexus. I had anticipated that and made a backup, and restored to that backup, but that didn't fix the problem and now it just bootloops the splash screen, although I can get into recovery and the bootloader.
So now, I figure I can either try flashing the original CM12 kernel over the broken franco kernel, or I can just re-flash the ROM and start from scratch. I'd really rather not do that, but I may have to. I can't get into the filesystem or get adb to find the device because of drivers, so I'm not sure which will be more of a headache: figuring out getting drivers to work in recovery/bootloader, or setting up android from scratch.
I just realized that it might be easiest to do a factory reset THEN restore from the backup, so I'll give that a try.
All of this got me thinking, is CM12 better than stock Lolipop 5.0.2? I just flashed it for easy updates and to get to the latest version, but what is everyone elses experiences between the two?
Also I'd love to hear of other ways to get the double tap to wake on Lolipop that might not involved flashing custom Kernels. Though I think I might give the ElementalX Kernel a shot, and it looks like that one won't break everything.
Franco's L kernel works with CM12, but if you have problems, just reflash the CM zip. Nothing else required.
I wouldn't use CM12 atm unless you like to test drive stuff, it's too early in development you can encounter quite a few bugs.
ElementalX kernel has the double tap to wake and a few other features. The only issue which is minor IMO is that is you update to the newest nightly you'll go back to CM kernel, and have to flash the ElementalX again. There may be a way around this, but I've only been on that kernel for a couple days now and haven't really looked in to a solution.
---------- Post added at 09:50 AM ---------- Previous post was at 09:41 AM ----------
k3lcior said:
I wouldn't use CM12 atm unless you like to test drive stuff, it's too early in development you can encounter quite a few bugs.
Click to expand...
Click to collapse
I can't say that I have encountered any real bugs, it seems very stable. Early on there seemed to be a battery drain and data connection seemed exceptionally slow at times, these may have been just due to my setup. I haven't had any of those problems for the last two weeks or so. Have you used it? If not why would you discourage someone when you have no personal experience?
Related
As the title says, I am running gedeROM 1.55 for the past year, since I experimented with a couple ROM's and settled on this one. For the most part its been a decent daily driver but have found it a little 'sluggish' lately and it annoys me. The lack of deep sleep keeps me always scrambling to keep it charged and ready to go so I don't find it dead when I want to use it.
Of course in the process I am using an older version of FFF and TWRP, so I know an update of them would be necessary.
A couple questions, looking for opinions:
1. Is it possible to just use KFU and update FFF and TWRP without disturbing everything else? I'd like to get them up to date.
2. After reading for 2 hours or more I am unclear on the limitations of 10.1 JB and wonder if I should be changing to JB at all?
3. Are the 10.1 ROM's a better option than I am running for speed and reliability? If so, any shining star amongst them?
I know asking for opinions will bore most people to death reading this, but I need some guidance from those that have been active and keeping up with ROM dev on this unit while I left mine alone and got behind.
Thanks in advance.
This might help you:
1. Look on the first post of this thread. Theres a flashable zip for FFF1.4 (Just flash in TWRP)
2. Here is Ichigo's flashable zip for TWRP 2.5.0 (Just flash in TWRP) https://www.dropbox.com/s/b4idirzkmgvnm07/TWRP-Blaze-2.5.0.0.zip
Those will not disturb anything else.
And try This ROM first and see if you like 4.2.2. This is the OFFICIAL cyanogenmod 10.1. To me its by far the best in terms of stability and speed. Make sure you wipe everything BUT /sdcard in TWRP before you flash!
Moving to a recent JB ROM will be a good move compared to gede because not only will you have better battery life but you'll have almost another year of improvements made to the Kindle since then.
Thanks for the info.... I'm gonna give this a shot I think. Not much to lose, nothing mission-critical on my tablet anyway
I'll post back once it's done!
Thanks again.
Bozz5384
It seems to have gone well, thanks for all the info. Updated FFF, TWRP, and now on CM 10.1 ... I did the 5/20 nightly, wasn't sure which one to do -- seems pretty bug free at this point.
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
TooG435 said:
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
Click to expand...
Click to collapse
I think something like 6.0.4 the latest CWMR. ( you can build with http://builder.clockworkmod.com/ , Existing Device option doesnt work)
It charges in latest TWRP, you can see "+" char when on charge next to the battery level.
Stock uses recovery for official upgrade, and factory reset. We have only offline charge issue, but recovery has no effect on it. Offline charger works with a limitation. I wouldnt bother you with the explanation, since you said you would like to use stock ICS.
You can backup efs in rooted rom without recovery. You can always flash recovery with odin phone in download mode.
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
TooG435 said:
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
Click to expand...
Click to collapse
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
bubor said:
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
Click to expand...
Click to collapse
My only real requirement in a phone is that it be reliable - I don't want to have to pop out batteries or have no audio on calls if I get stranded in the middle of nowhere. At this point, my phone is still in the mail - got a used one from a friend, but it hasn't arrived, so I haven't had much ability to experiment yet.
My Android experience is exclusively with a Transformer TF101, which had 4.0.4 ICS stock and is currently running Katkiss JB 4.2.2_226 (Katkiss 4.3 isn't stable enough for me yet, was getting daily crashes last time I tried). All of the phone components are new to me - and the Glide seems to have a more fragmented recovery scene than the TF101, which is pretty much TWRP or nothin'
Thanks again for your help!
Hi,
I'm about to buy a LG G Pad 8.3 and plan to root it and flash CM11 right away. I've read in a few places that there is a brightness issue with custom ROM's but haven't seen a clear way to avoid it or fix it (other than perhaps flashing stock reflashing CM?). I've also seen various posts suggesting fixes to this in the latest CM builds and also a custom kernel that could be used (AIC?). So which, CM build should I use (official, infected) and can anyone please explain how to avoid the low brightness issue?
Thankyou!
thegrantonstarcause said:
Hi,
I'm about to buy a LG G Pad 8.3 and plan to root it and flash CM11 right away. I've read in a few places that there is a brightness issue with custom ROM's but haven't seen a clear way to avoid it or fix it (other than perhaps flashing stock reflashing CM?). I've also seen various posts suggesting fixes to this in the latest CM builds and also a custom kernel that could be used (AIC?). So which, CM build should I use (official, infected) and can anyone please explain how to avoid the low brightness issue?
Thankyou!
Click to expand...
Click to collapse
Use whatever CM build you want. I don't know much about the other fix, I assume you mean when infected said he committed some change that is ROM side.
The other method is to pick whatever CM version you want(or other ROM for that matter). Use the AIC kernel installer and select custom ROM's when prompted. Then if you were on Stock LG 4.4.2 before you flashed CM you pick the 4.4.2 ROM, and if you were on Stock LG 4.2.2 before you flashed you pick the 4.2.2 ROM. 4.4.2 and 4.2.2 have nothing to do with CM version only which Stock LG ROM you started with.
Ok thanks
Sent from my Nexus 10 using XDA Premium HD app
thegrantonstarcause said:
Hi,
I'm about to buy a LG G Pad 8.3 and plan to root it and flash CM11 right away. I've read in a few places that there is a brightness issue with custom ROM's but haven't seen a clear way to avoid it or fix it (other than perhaps flashing stock reflashing CM?). I've also seen various posts suggesting fixes to this in the latest CM builds and also a custom kernel that could be used (AIC?). So which, CM build should I use (official, infected) and can anyone please explain how to avoid the low brightness issue?
Thankyou!
Click to expand...
Click to collapse
I think you are referring to a dimness issue when going to a custom rom from stock 4.4.2. Its related to the custom recovery not supporting soem changes to the partition or directory structure made by the LG update. Just make sure to update TWRP to 2.7.0.1 before flashing your custom rom.
Any rom will due. I'd advise sticking with the M-releases so you can get some stability and be able to do a monthly dirty flash. I've heard good things about infected's CM build.
ruibing said:
I think you are referring to a dimness issue when going to a custom rom from stock 4.4.2. Its related to the custom recovery not supporting soem changes to the partition or directory structure made by the LG update. Just make sure to update TWRP to 2.7.0.1 before flashing your custom rom.
Any rom will due. I'd advise sticking with the M-releases so you can get some stability and be able to do a monthly dirty flash. I've heard good things about infected's CM build.
Click to expand...
Click to collapse
Ok I'll risk this question (I thought that I knew the answer)....
Brightness
I was on Stock 4.4.2. I had rooted the Pad and then ensured that the version of TWRP installed is 4.4.2-v500-TWRP_2.7.0.1-recovery.zip.
So I should be fine when installing Infected's build of the Slimkat ROM as it also is built on 4.4.2 and yet I can't see a thing when it first boots.
The screen is way too dim. Eventually when I work blind to get it to finish its set up the screen is still very dim. Booting back into recovery it is fine and bright. A reboot and it is really nice and bright for about ten seconds and then it will reduce a small amount but placing into standby and then back on again and it is perfect.
It will remain perfect until I need to reboot it and then it will dim slightly until I place it into standby and then back on again and then it is absolutely perfect.
So what am I missing with the version of TWRP I have installed over that of the stock 4.4.2 UK OTA ROM and using any custom ROM based on 4.4.2...?
Thanks
vimesUK said:
Ok I'll risk this question (I thought that I knew the answer)....
Brightness
I was on Stock 4.4.2. I had rooted the Pad and then ensured that the version of TWRP installed is 4.4.2-v500-TWRP_2.7.0.1-recovery.zip.
So I should be fine when installing Infected's build of the Slimkat ROM as it also is built on 4.4.2 and yet I can't see a thing when it first boots.
The screen is way too dim. Eventually when I work blind to get it to finish its set up the screen is still very dim. Booting back into recovery it is fine and bright. A reboot and it is really nice and bright for about ten seconds and then it will reduce a small amount but placing into standby and then back on again and it is perfect.
It will remain perfect until I need to reboot it and then it will dim slightly until I place it into standby and then back on again and then it is absolutely perfect.
So what am I missing with the version of TWRP I have installed over that of the stock 4.4.2 UK OTA ROM and using any custom ROM based on 4.4.2...?
Thanks
Click to expand...
Click to collapse
From what I can understand, TWRP 2.7.0.1 should have fixed that startup dimness issue (reference: http://forum.xda-developers.com/showpost.php?p=52019098&postcount=343).
Otherwise, you can try flashing back to 4.2 stock rom before flashing to a custom rom (reference: http://forum.xda-developers.com/showpost.php?p=52564158&postcount=360).
ruibing said:
From what I can understand, TWRP 2.7.0.1 should have fixed that startup dimness issue (reference: http://forum.xda-developers.com/showpost.php?p=52019098&postcount=343).
Otherwise, you can try flashing back to 4.2 stock rom before flashing to a custom rom (reference: http://forum.xda-developers.com/showpost.php?p=52564158&postcount=360).
Click to expand...
Click to collapse
Thanks
I understood that as well but now get the impression that other influences could be a contributory cause. In the thread of Infected's SlimKat's ROM he had noted some build issues which could well have caused that, as others had noted it, and so compiled another build. One other who had noted it had flashed back to 4.2 and used 2.7.0.0 of TWRP and yet still got the issue.
vimesUK said:
Thanks
I understood that as well but now get the impression that other influences could be a contributory cause. In the thread of Infected's SlimKat's ROM he had noted some build issues which could well have caused that, as others had noted it, and so compiled another build. One other who had noted it had flashed back to 4.2 and used 2.7.0.0 of TWRP and yet still got the issue.
Click to expand...
Click to collapse
I was fighting a dimness issue on the latest Mahdi last weekend and went back to stock rooted because of it. Something definitely has changed since I took the 4.4.2 stock update from LG. I did not try going all the way back to 4.2 as an alternative. I do know that the issue is worked around in the TWRP with 2.7.0.1, however once I boot into Mahdi everything is very dim until I change the brightness slider.
In addition when I would change the brightness slider (in mahdi) the rate at which the screen would change was dramatically different from previously. Something in the 4.4.2 update has changed the way brightness works on the V500. I'm wondering if it is related to the fix that made the 7 led lights go away for so many (including me) on 4.4.2. I can say that it was annoying enough for me to revert to stock and simply run stock and rooted again...
I also noticed, with two or three different custom ROMs that supposedly had the brightness fix in there (AICP and Infected's CM nightly from the 21st) they both booted up with the backlight basically off. When scrolling the brightness meter, only the last 5th or so was usable, and approximately equivalent to the whole meter in stock. I went back to stock for that and other reasons, but I may try it again soon, especially if someone has a suggestion... I am leery of trying to go to 4.2.2 since I had such bad luck flashing LRS and could only get recovery 2.7.0.1 working properly.
I don't really like to draw comfort from other peoples issues as noted but I'm kinda glad that at least the methodology I was applying when I installed these custom ROM's was ok. Also the version of TWRP was applicable for the version of KK being used, to go with the bootloader, I guess.
What is being described since my last comment is typical also of what I'm seeing.
I'm tempted to just go back to stock KK, at least the full and complete range of brightness control works without issue.
I ended up biting the bullet, and found a TWRP 2.6.3.2 recovery that worked properly, though it is still incredibly dim brightness-wise. But now I was able to install LRS G Pad, which is stock based so it doesn't have the brightness issues... but hey, at least it's a custom ROM, right?
IBJamon said:
I ended up biting the bullet, and found a TWRP 2.6.3.2 recovery that worked properly, though it is still incredibly dim brightness-wise. But now I was able to install LRS G Pad, which is stock based so it doesn't have the brightness issues... but hey, at least it's a custom ROM, right?
Click to expand...
Click to collapse
No, it is not in custom ROM section, but a stock based that give the speed of AOSP into stock-like ROM, so it is the best choice for every device out there, plus, you can install some kernels that's made for stock...
Sent from my LG-V500 using Tapatalk
i got the same problem but i found a way to fix it,sort of.When my rom its booting the backlight is low,i installed the lux brightness app,i press the power button one time and the tablet sleeps,when it comes back i got full backlight.It stays full until reboot,in fact i will never do a reboot.Try that maybe fix your problem
Fix that
I found a fix for that,let the ROM boot and then press the brightness setting to full,press the power button to go to sleep and then press to wake up,that work for me,I can use any custom rom
I flashed the LRX21P factory image onto my Nexus 7 2013 yesterday and to be honest I'm really quite disappointed with the performance. Most of the material design animations seem to be running slowly or dropping frames, scrolling is jittery and even the performance of many of my games (the ones that still work, anyway) is much worse than before.
I've seen comments elsewhere with other people having the same experiences, just wanted to get a feel for how common this is and if there is anything that can be done to fix it.
Did you wipe data? Old data cannot remain or it will ruin performance.
madbat99 said:
Did you wipe data? Old data cannot remain or it will ruin performance.
Click to expand...
Click to collapse
I used the script included with the factory image. Unfortunately my Nexus 7 won't even boot right now, so I'm going to restore it from my Kitkat backup and not muck about with it again.
You really need to do a fresh install when upgrading to a major new version of an OS. Trying to keep your old data and settings is a recipe for disaster.
On my Nexus 7 2013 at first time it was running laggy, but now, after few reboots it's running OK, but I think it can be faster.
a lot of people have same problem
Reboot and install clean master. Maybe fix it
It is slightly laggy but not a deal breaker
I used the Stock Factory Image to upgrade, and it gave me absolutely no issues at all..
I did a COMPLETE WIPE, then installed the image via Wugfresh's NRT Program/Tookit and played with it for about a week.. It broke a few of my apps.. So I decided to go back to Carbon's Nightlies 4.4.4.. I won't go back to Lollipop until a decent Custom rom is released with Xposed modules... I did not notice a performance boost or anything different other than a complete interface change.. I had to download a beta copy of Titanium Backup to restore the Data of my apps so I could at least restore a few things.... Lollipop isn't ready for prime time, stick to your latest version of Kitkat..
Zaphodspeaks said:
I used the Stock Factory Image to upgrade, and it gave me absolutely no issues at all..
I did a COMPLETE WIPE, then installed the image via Wugfresh's NRT Program/Tookit and played with it for about a week.. It broke a few of my apps.. So I decided to go back to Carbon's Nightlies 4.4.4.. I won't go back to Lollipop until a decent Custom rom is released with Xposed modules... I did not notice a performance boost or anything different other than a complete interface change.. I had to download a beta copy of Titanium Backup to restore the Data of my apps so I could at least restore a few things.... Lollipop isn't ready for prime time, stick to your latest version of Kitkat..
Click to expand...
Click to collapse
Xposed doesn't work on art. And there is waaay more than a ui change. There are security enhancements that I have been waiting for. Even though one of my favorite apps isn't updated to work yet (dish anywhere) I can't go back, lol. Onward to the 21st century!!
madbat99 said:
Xposed doesn't work on art. And there is waaay more than a ui change. There are security enhancements that I have been waiting for. Even though one of my favorite apps isn't updated to work yet (dish anywhere) I can't go back, lol. Onward to the 21st century!!
Click to expand...
Click to collapse
I know Xposed doesn't work on ART, hence why I downgraded to my trusty Carbon 4.4.4 where its tried and true..
The developer of Xposed doesn't even know if he will port Xposed over to Lollipop, although I have confidence that he will eventually.. I never liked the Stock version of any version of Android.. But because its open source, or at least up until now, there will always be someone out there with a CM port, or Carbon.. ETC..
Lollipop broke a lot of my apps.. Thats because some developers haven't caught up.. I like Lollipop, but I hate the middle pull down menu.. other than that, it's fantastic.. Battery life really good, smooth and gave me not a single issue while I used it for just over a week... But I missed some of my games.. and favorite apps.. Then I temporarily downgraded to 4.4.4.. Until the 3rd party developers can polish this amazing rom..
Mine lagged after flashing as well. I just reflashed and now its a smooth as ever. Stock kernel
I'm quite happy back on Kitkat. Since Google appear to have pulled the OTA update I can't see a reason to rush to upgrade right now and I probably shouldn't have been so impatient.
Interesting to see the poll is almost neck and neck too.
I was worried after seeing some of these comments, but I flashed Lollipop last night and my tablet is running great!!
timrock said:
Mine lagged after flashing as well. I just reflashed and now its a smooth as ever. Stock kernel
Click to expand...
Click to collapse
Absolutely great advice for any issues after a rom flash. If you are fastboot flashing rather than taking an OTA, it's so easy to just reflash the system. If needed, reflash all components.
I'm currently using the latest version of ResurrectionRemix and it's a bit too unstable for me so I'd like to go back to something stock-ish. I'm currently on CQB2, so should I do anything more than flash CQC1 and then MODest? (I'm going to do a clean flash.)
Also, I've had a lot of trouble getting anything GearVR-related to work ever since I first started flashing custom roms on this phone. (Even after completely reverting to unrooted/locked stock more than once.) Is there anything I can do to get that functionality back?
princeendo said:
I'm currently using the latest version of ResurrectionRemix and it's a bit too unstable for me so I'd like to go back to something stock-ish. I'm currently on CQB2, so should I do anything more than flash CQC1 and then MODest? (I'm going to do a clean flash.)
Also, I've had a lot of trouble getting anything GearVR-related to work ever since I first started flashing custom roms on this phone. (Even after completely reverting to unrooted/locked stock more than once.) Is there anything I can do to get that functionality back?
Click to expand...
Click to collapse
I was looking at RR, myself. I'm glad I came across your post. Thank you. With to hsbadr's other 7.1 ROMs, it looked as if you needed to flash a special version of TWRP, but not with RR. Did you do this by accident? It doesn't appear that RR needs this. I wouldn't know for sure, not would I know if flashing this special version of TWRP would cause the instabilities you speak of.
I'm on the second most latest version of MODest (v6). There were problems with v7. First, the wifi didn't work, and that got fixed with an update (v7.1). I believe there's another issue with it, regarding a method to unlock your phone. It wouldn't affect me, since I use a PIN. Read the thread on it, maybe just glance through the last couple of pages.
Anyway, I THINK all you need to do, is flash CQC1 in Odin, then the ROM in TWRP, which includes a kernel. He's also got a separate post for the kernel, as well. Not sure why. Since I'm on MODest, I don't need it.
I'm waiting until everything is ironed out to upgrade to v7.x. v6 is running just fine, for me, but I'm a glutton for punishment and upgrading my phone, going through the backup and restore process over and over again.