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
Related
I have searched via various keywords for days and have not found an answer to my problem yet. I have only run across one other post (on another forum) that describes exactly my issue and they are asking the exact same question I have with no response.
I am using the AT&T Samsung Galaxy S3. I have downloaded CM 10.0.0 stable d2att on several occasions (different computers even), verified the md5, and installed on my phone. I have used CWM, CWM Touch, and TWRP to install hoping it was an issue there. Regardless of what I have done, I have the same issue addressed below:
I make or receive a phone call. No problems answering a phone call when it comes in. However when I hang up, the screen immediately goes back to sleep (which seems to be normal for the Nexus after researching). However, if I press the power button after the call is ended, the screen does not turn on at all. The hardware buttons (menu and back) do light up however and they remain lit. Regardless of what I do my phone stays stuck in this mode unless I hold the power button for about 10 seconds or so and force it to reboot, at which point it operates normal with no issues until my next phone call.
Has anyone experienced this issue and if so did you find a way to resolve it that does not require rebooting the phone? Right now this is the only thing keeping me from using the ROM as my daily driver.
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
xBeerdroiDx said:
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
Click to expand...
Click to collapse
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
aybarrap1 said:
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
Click to expand...
Click to collapse
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
xBeerdroiDx said:
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
Click to expand...
Click to collapse
I actually downloaded the camera/gallery apk for 4.2 as well as the keyboard. Already installed and running. Prefer both over the 4.1.2 versions installed on AOKP and CM10. Thanks for the info.
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!
[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Q&A for [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
kbfirebreather said:
Anyone having problems with torch on the beta build? Not turning on LED for me, and keeps force closing.
Click to expand...
Click to collapse
I'm having issues with it as well. Sometimes it sits there thinking it works, other times it waits a few seconds and then crashes. It worked for a day...not sure what I did past that to break it.
Is there anyway to overclock the latest update? I know I can't install a new kernel with this ROM.
Also, any option for Volume Rocker unlock? I'm new to this ROM, coming from CM. I kinda rely on that option, since my power button is kinda on the fritz.
Fml 4.4.4 beta
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
vicious01 said:
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
Click to expand...
Click to collapse
Which gapps package are you using? I'm using the modular mini. Try another clean flash (sorry) and use a different package than you are now.
aaa
nothing
I've tried a lot of KitKat ROMs, but each one with a lot of issues. So I came back to the 4.3, it surprised me for his stability (1 year with bugged ROM make you feel that your phone sucks more than it actually does [no, it doesn't, I love it!]) and I decided to don't try your FML. Now I can't wait for Lollipop, and even if I haven't tried your ROM, I trust in it and I think it will be the best choice. Good work and thanks!
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
Samsung Galaxy Nexus FML Lollipop
Hello. I hope this is the right place to post this. I have less than 10 posts so I have to post here...
I've tried to install your FML rom (the lollipop beta) on my Samsung Galaxy Nexus, but I seem to be having the same issue that coleburns is having. Namely, I flashed the rom from recovery, but when I reboot the phone, it shows the Google splash screen and then keep rebooting over and over again.
I understand that the first boot is supposed to take some time, but I've left it for over an hour and it still won't boot into the OS. Is there a step I'm missing?
I'm using the custom version of TWRP that you linked to in the first post. I also formatted all the partitions to ext4. Before flashing the rom, I performed the factory reset from recovery and also cleared the /system folder.
I've managed to load on the KitKat version of your ROM just fine...I can't work out what I'm doing wrong!
Anyway, if you need some logs or something to help debug the issue, let me know. Or, if I'm doing something wrong, could you please let me know? I'm very keen to try Lollipop!
Thanks.
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
lollipop build 2
Haven't seen anybody ask... In your changelog for lollipop you said the rom takes a VERY LENGTHY FLASH TIME. Are we looking at 5 minutes or more?
edit: VERY LONG... over 5 minutes for me
This is the best rom ever!
When you said, "These builds are very early! They aren't daily-driver-stable, but they are progressing extremely fast." I was expecting junk, then I tried it. I was a big fan of your kit kat rom as well but once I tried this android l rom I fell in love. I have used this all day and it is extremly stable. The only bug I have to report that isnt even a need is the app drawer is the app drawer animation is very laggy. I tried enableing 2d gpu acceleration just in case that had something to do with it but it still didnt help. Any suggestions would be great. Oh and yes I have tried closing other apps, multitasking is no issue with this rom, the memory management is great. I thank you so much for such a great rom, keep up the amazing work.
Installing TWRP Problem
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Mondos said:
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Click to expand...
Click to collapse
Download the file in the OP for FML (twrp 2.7.1). Flash with Flashify. Reboot to recovery.
Don't worry too much about it not working. It's fully working for me but it's pretty slow when you actually need to use it. If you get it going it will pick up the pace, but it's far from usable, being in an app for longer than a minute and touching the home screen button will freeze it up for 10 seconds before it takes you to an empty screen that takes another few seconds to load all the apps and widgets back in. I'd wait for a newer release.
Feedback
Hello i have tried the older version and it was great but i really need my camera so i went back to 4.4 but i appreciate you so much thanks !
Please fix the camera asap and i will definitely install this rom ! and i tried to install the new version but it said Error Binary something in TWRP recovery what can i do thanks!
Q
Is the camera fixed yet?
Notification Light
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
TheIbanez97 said:
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
Click to expand...
Click to collapse
I don't think so.
I found that the miscellaneous section of the battery stats was taking up most of the battery usage. I don't have any apps installed other than the stock standard.
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?
Hi everyone.
I'm a bit confusing after reading a lot of threads in LG G3 about bumping... I've tried to make my mind, but can't understand properly how that works, coming to a LG G3 from a Nexus 4 (who has suddenly died after a fall), and a couple of Samsung tablets, where I had just to install a custom recovery to flash new roms/kernels, root, nandroid, etc.
Is this different in LG phones?
I've saw a thread with a bumped TWRP, and another one that seems to give instructions to install usual TWRP. There are roms/kernels that seem to be bumped an other ones that say nothing about that...
Can't be just flashed a recovery on a rooted phone and then used to flash anything else?
Bumped TWRP admits just bumped rom/kernels?
Usual TWRP admits bumped rom/kernels or just non-bumped ones?
Which are the advantages/risks of using a bumped or not TWRP?
I'm really lost about all that that seems to be just LG related...
And another set of questions (that will be more a question of preferences, though...):
I like to have my phone set to my taste. I can see 3 options. I would like to know, not so much which one is better (each one will say the option he's using, as logical), but which are the advantages/risks/problems with any of them in this concrete phone:
a) Using stock (rooted, with a custom kernel -which one?-, and with the xposed LG G3 set of options).
b) An AOSP derived ROM (non CM... there are few, it seems), with quick circle module, and any camera that improves AOSP one. And a kernel if that improves the one in the ROM
c) A CM based ROM (seem to be more of that) with same additions.
After some reading, I see many people complaining that the nice camera in this phone is only working fine in stock. But I don't know if that's really so much worse as to stick on stock, even if xposed enables a lot of customization... When I want serious photos, I use my DSLR... so I just want the camera to behave nice, and do a good work when I'm just doing occasional photo. But I don't want a nearly broken camera, of course...
On the other side, AOSP based ROM's seem to be, not only more clean and customizable, but better in battery management (and less overheating). But some people says CM based ones are no so much so... Don't know what to think about that.
And I'm not sure how the quick circle mod is working on AOSP or CM ROMs (I have an original case, so, it would be nice to use it...)
Sorry for so many questions, but I have the feeling that LG is a bit "another world" from Nexus (freedom......) or Samsung, where everything is like just flash and go...
And thanks everyone reading this!
:good::good::good:
Hi,
It is not that complicated.
First part. Root the phone and then install TWRP. There are few threads about how to do it.
Second part. Stock based roms work fine. AOSP based roms are smoother but camera quality and battery performance are worse. Depends on what you need.
Regards
Sent from my phone
So, bumping question is nothing to think about? That's good news, then is just setting TWRP and done, like any other device. Thanks for that!
from SM-T520
nachordez said:
So, bumping question is nothing to think about? That's good news, then is just setting TWRP and done, like any other device. Thanks for that!
from SM-T520
Click to expand...
Click to collapse
Yes, for the most part, as all of the custom/aftermarket recovery images and ROMs are already 'bumped', and 'bumping', in the context of LG smartphone and tablets, is simply appending a signature key to make sure that the bootloader gives the custom recovery/ROM package the approval to be installed.
You ONLY need to 'bump' an image if the image you want to install has not been signed, which is rare as like I said, almost all of the custom recovery/ROM images are 'bumped', and if you do come across a situation that requires you to 'bump' an image, there's an offline tool that works on Microsoft Windows that is simply called 'Bump!!!', which can sign, or 'bump' an unsigned image and it only takes a few seconds to do that as it is easy to do.
As for setting up your LG device, in the case of the LG G3, root your phone first - rooting an LG device on the stock Lollipop ROM can be done with this script:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
After you have rooted your phone, Install AutoRec for your LG device and remember to choose the version that matches your phone model number (e.g. LG G3 D855) - this will Install the TeamWin Recovery Project recovery image onto your phone.
Once that is done, you can now choose a ROM that you want to install - most ROMs obviously come in flashable ZIP form, so pick your poison and Install via recovery mode - most people love the certain blue poison that is Cyanogenmod but others may try CloudyG3, which is an LG ROM-based custom ROM - like ypsmav said, it depends what features you are after the most - if you prioritise unlimited tethering and Miracast over other features, choose CyanogenMod or any other AOSP-based custom ROM, or if you prioritise camera quality and vendor-exclusive features over other features, then choose Cloudy ROM or any other vendor-based custom ROM.
Have fun!
Thanks for your time and counsels, @aha360 and @ypsmav
Now, I know what we are talking about
:good:
from Nexus 4
I'm still unable to update from TWRP 2.8.6.0 to anything newer - I have an Lg G3 F400K on Android 5.0, stock rooted. I was able to use AutoRec to flash TWRP 2.8.6.0, but then flashing 3.0.2.0 gives me the 'secure boot' error when trying to boot into recovery. I've tried:
1) flashing through TWRP
2) Rashr
3) Flashify
Any further ideas? Will it work if I change roms? Is it related to the SD card? (I saw something on this thread which I didn't quite understand)