Related
How often do you guys make a backup up?
I used to do it very rarely. Then it became every Sunday.
Now I'm doing it everytime I install a new app, or make a mod to the phone... I do one almost daily, and sometimes up to 5 times a day!
And I don't even change ROMs after that!
Is that bad? How often should I do it?
How often do you guys go it?
-------------------------------
Sent from my HTC Desire S
I usually only make one when changing/updating ROMs. Then I only keep it till the next ROM change or a completely different ROM, for example I keep the original Sense nandroid and I have the last ILWT CM7 nandroid I made when switching to ICS, but, usually delete between ROM updates.
Sent from my Quattro'd HTC Desire Z using xda premium
i do Nandroid backup once or twice every week...
- backup before update ROM or change to other ROM
- backup before i update kernel
- backup after i update alot of apps on that day
I do it only before changing/upgrading roms... in the first case i keep it for two/three of them in the eventuality to go back for a more stable one... only the last good one in case of upgrade.
I backup every saturday and keep backups of all my fave roms set up and ready to go.
Sent from my GT-I9100
I do it every time I mod Rom or change the Rom...
It's not harmful taking nandroid backups
"Ever wondered why??"
olyloh6696 said:
I do one almost daily, and sometimes up to 5 times a day!
Is that bad? How often should I do it?
How often do you guys do it?
Click to expand...
Click to collapse
Careful there, you might end up blind.
iR¡[email protected]!* via Tapatalk
I just do mine every time I mode my ROM.
iridaki said:
Careful there, you might end up blind.
iR¡[email protected]!* via Tapatalk
Click to expand...
Click to collapse
Hahaha
I guess the way I phrased it was a came out wrong if you read it in a different context
-------------------------------
Sent from my HTC Desire S
olyloh6696 said:
Hahaha
I guess the way I phrased it was a came out wrong if you read it in a different context
Click to expand...
Click to collapse
Indeed! Funniest "misunderstanding" since the "How to take a dump" thread someone made asking how to take a... screenshot!
That made my day, so thanks!
Jokes aside, I find Titanium sufficient to backup apps and data and I only do nandroid backups when I edit system files. That way, if something goes wrong, I go to recovery -> Advanced Restore -> /system so my phone comes back to normal and my data are intact. So 5 nandroids a day will do no harm but no good either, imho.
iridaki said:
Indeed! Funniest "misunderstanding" since the "How to take a dump" thread someone made asking how to take a... screenshot!
That made my day, so thanks!
Jokes aside, I find Titanium sufficient to backup apps and data and I only do nandroid backups when I edit system files. That way, if something goes wrong, I go to recovery -> Advanced Restore -> /system so my phone comes back to normal and my data are intact. So 5 nandroids a day will do no harm but no good either, imho.
Click to expand...
Click to collapse
Ok thanks!
I'm gonma try to cut down the NAND backup now
Its a bad habit
I just made a few changes to my Launcher, and I'm feeling tempted to just to a NANDroid backup now
Must resist..
-------------------------------
Sent from my HTC Desire S
I make a backup everytime i root. So i backup the stock rooted rom then flash away. Also make sure u dont swap sd cards or u will get a md5 mismatch
sent from an HTC sensation on CM7 alpha #10
If you do it that often there's a good chance that one day you include the problem that screws up your install in your Nandroid, making it worthless to go back to. If you're flashing/modding a lot i'd suggest having one known stable backup which you keep as a fall-back, and then another that you replace as often as you like.
DirkGently said:
If you do it that often there's a good chance that one day you include the problem that screws up your install in your Nandroid, making it worthless to go back to. If you're flashing/modding a lot i'd suggest having one known stable backup which you keep as a fall-back, and then another that you replace as often as you like.
Click to expand...
Click to collapse
Good point! I see your logic.
Thanks for that!
-------------------------------
Sent from my HTC Desire S
Never do those. Only backed up my efs folder.
Sent from my Nexus S using Tapatalk
So, I understand the process of it.. but not really as to why.
Are you able to install anything N4 you want? Roms, kernels, etc? Or is it just the N4 converted roms from the dev section?
Is everything working? I've read mixed reports.
Thanks,
Nicholas
xsaqzw said:
So, I understand the process of it.. but not really as to why.
Are you able to install anything N4 you want? Roms, kernels, etc? Or is it just the N4 converted roms from the dev section?
Is everything working? I've read mixed reports.
Thanks,
Nicholas
Click to expand...
Click to collapse
The lgog and the nexus 4 are fairly similar phones. The reason we can't run nexus 4 ROMs is because some differences in the partitioning. Flashing the modified tot for the conversion converts your partition layout to that of a nexus 4 and installs the stock nexus 4 rom with an unlocked bootloader.You are supposed to be able to use nexus 4 ROMs and kernels. I've flashed like a 3 different nexus 4 ROMs
The problems that you might run into are with lte but that is fixable.
There is a fix for capacitive keys , nfc , and the external SD card which I were originally not working. The fix is a ROM so if you want all those things working you have to use it or properly patch another ROM with some of its files. There is also a flash able zip that but it is only compatible with certain ROMs.
The only "issue" in not having the full internal SD storage. You only have 8gb in comparison to 16gb but having large external SD should help storage wise.
However, apparently the conversion breaks the camera for the jelly bean stock port from the lg e973http://forum.xda-developers.com/sho...an LG-E973/1/5/0 CANADA / ATT / INTERNATIONAL. Camera works fine on every other stock based ROM when you convert back but apparently not on the jellybean port. It has not been proved but it has many claims supporting it. My camera does not work and I have converted.
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
The lgog and the nexus 4 are fairly similar phones. The reason we can't run nexus 4 ROMs is because some differences in the partitioning. Flashing the modified tot for the conversion converts your partition layout to that of a nexus 4 and installs the stock nexus 4 rom with an unlocked bootloader.You are supposed to be able to use nexus 4 ROMs and kernels. I've flashed like a 3 different nexus 4 ROMs
The problems that you might run into are with lte but that is fixable.
There is a fix for capacitive keys , nfc , and the external SD card which I were originally not working. The fix is a ROM so if you want all those things working you have to use it or properly patch another ROM with some of its files. There is also a flash able zip that but it is only compatible with certain ROMs.
The only "issue" in not having the full internal SD storage. You only have 8gb in comparison to 16gb but having large external SD should help storage wise.
However, apparently the conversion breaks the camera for the jelly bean stock port from the lg e973http://forum.xda-developers.com/sho...an LG-E973/1/5/0 CANADA / ATT / INTERNATIONAL. Camera works fine on every other stock based ROM when you convert back but apparently not on the jellybean port. It has not been proved but it has many claims supporting it. My camera does not work and I have converted.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Dr0!d thanks for explanation. I have a question. Ever time I come back to stock I get an encryption error. What am I doing wrong?
Sent from my Xoom using xda app-developers app
jimi_pooh said:
Dr0!d thanks for explanation. I have a question. Ever time I come back to stock I get an encryption error. What am I doing wrong?
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
I got that error once. lgpnst doesn't really wipe partitions correctly before flashing ROMs. NownI wipe all of my partitions in recovery and then fastboot -w in command prompt before flashing back to stock . A data and cache is probably all that's needed but the flashing process takes a minute and I haven't had time to try it out. I think there is also something you can do at the encryption screen . it says like reset phone or something I think I've read that if you keep hitting it it will reset your phone or something idk sorry.
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
I got that error once. lgpnst doesn't really wipe partitions correctly before flashing ROMs. NownI wipe all of my partitions in recovery and then fastboot -w in command prompt before flashing back to stock . A data and cache is probably all that's needed but the flashing process takes a minute and I haven't had time to try it out. I think there is also something you can do at the encryption screen . it says like reset phone or something I think I've read that if you keep hitting it it will reset your phone or something idk sorry.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Dude thanks a bunch. I'm going to try wiping like u suggested
Sent from my Xoom using xda app-developers app
jimi_pooh said:
Dude thanks a bunch. I'm going to try wiping like u suggested
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
That's what did the trick for me when I came back. Good luck
Sent from my Nocturnal'd Optimus G
Dr0!dFreek said:
I got that error once. lgpnst doesn't really wipe partitions correctly before flashing ROMs. NownI wipe all of my partitions in recovery and then fastboot -w in command prompt before flashing back to stock . A data and cache is probably all that's needed but the flashing process takes a minute and I haven't had time to try it out. I think there is also something you can do at the encryption screen . it says like reset phone or something I think I've read that if you keep hitting it it will reset your phone or something idk sorry.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
I tend to go back and forth doing the N4 conversion and back to At&t stock. I get this fail to encryption screen,some times after I LGNPST back to stock. Pressing the "reset phone" repeatedly never does anything for me. What i've been doing is when this happens is, I'll shut the phone down and press the Vol down and HOLD first and then hold the power button. It will bring you to some kind of factory recovery where it says "HARD RESET MODE" Just press the power button to confirm the reset and it essentially just wipes the phone and brings it back to stock.
Hope that helps!
Dr0!dFreek said:
The lgog and the nexus 4 are fairly similar phones. The reason we can't run nexus 4 ROMs is because some differences in the partitioning. Flashing the modified tot for the conversion converts your partition layout to that of a nexus 4 and installs the stock nexus 4 rom with an unlocked bootloader.You are supposed to be able to use nexus 4 ROMs and kernels. I've flashed like a 3 different nexus 4 ROMs
The problems that you might run into are with lte but that is fixable.
There is a fix for capacitive keys , nfc , and the external SD card which I were originally not working. The fix is a ROM so if you want all those things working you have to use it or properly patch another ROM with some of its files. There is also a flash able zip that but it is only compatible with certain ROMs.
The only "issue" in not having the full internal SD storage. You only have 8gb in comparison to 16gb but having large external SD should help storage wise.
However, apparently the conversion breaks the camera for the jelly bean stock port from the lg e973http://forum.xda-developers.com/sho...an LG-E973/1/5/0 CANADA / ATT / INTERNATIONAL. Camera works fine on every other stock based ROM when you convert back but apparently not on the jellybean port. It has not been proved but it has many claims supporting it. My camera does not work and I have converted.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Thanks so much man!
Are there going to be any AOSP roms coming out native for the LGOG soon? If so, I'll hold off on the conversion. But if not, then I think I'll go ahead and do the conversion and flash Ginsex or one of the other JB ports. Are the cameras working on this if you flash the fix?
Nicholas
xsaqzw said:
Thanks so much man!
Are there going to be any AOSP roms coming out native for the LGOG soon? If so, I'll hold off on the conversion. But if not, then I think I'll go ahead and do the conversion and flash Ginsex or one of the other JB ports. Are the cameras working on this if you flash the fix?
Nicholas
Click to expand...
Click to collapse
Yes there are a couple of people working on aosp ROMs right now just give them a little more time
Sent from my LG-E970 using xda premium
I know some people are against the conversion as such, but I think in the long run, this will be the only benefit of this phone - I'm expecting LG to do its thing where they don't provide any updates once their newer phones come out.
And here comes the nexus4 conversion - we'll be able to advance our phones thanks to the actual updates for nexus4 that google and the community will provide. Probably we'll lose LTE at some point when the modems will no longer be compatible with newer android versions.
My previous phone, the captivate was in a similar scenario - slightly different from the international galaxy s, but the devs worked out a set of patches to be applied against the galaxy s roms to make them work on the captivate and the captivate has long lived since, becoming one of first phones to get cm10.1 nightlies and enjoying more than a few 4.2.1 roms. It's definitely slowing down, it's been more than 2 and half years since the phone launched and people have moved on to newer devices.
So if it wasn't for the nexus4 conversion, I wouldn't have jumped on the lgog for my upgrade - the phone shipped with ICS, might get a 4.1 update eventually, but I don't expect LG to follow up with further stock updates after 4.1.
I know there is speak of AOSP roms coming to the LGOG, and I'm really thankful for the all the devs who work bringing these, and hoping we'll even see official cm10.1/cm11 then probably we won't need the conversion at all, but if it doesn't happen, or devs give up on the lgog the conversion will be the only path to newest android.
I still dont understand why any dev is working on anything other than perfecting the n4 conversion. Doing anything else seems like a huge waste of effort and time to me. A perfectly functioning n4 conversion = this phone will be in the game for years and years. Anything else just means everyone is sol when the developers for this specific phone jump ship.. that will never happen with the n4 conversion.
There is also the odd (cant put my finger on it) veil of secrecy with this phone that i never bumped into before. So much info no one knows because its just simply not shared in any way.
whiteguypl said:
I still dont understand why any dev is working on anything other than perfecting the n4 conversion. Doing anything else seems like a huge waste of effort and time to me. A perfectly functioning n4 conversion = this phone will be in the game for years and years. Anything else just means everyone is sol when the developers for this specific phone jump ship.. that will never happen with the n4 conversion.
There is also the odd (cant put my finger on it) veil of secrecy with this phone that i never bumped into before. So much info no one knows because its just simply not shared in any way.
Click to expand...
Click to collapse
While I personally don't really agree with the first comment (I feel as though stock LG development has its place and there are dangers to the conversion), I definitely agree with the secrecy, on my old inspire I knew just about everything the devs were working on, what was and wasn't working, as well as which problems they were facing. With the LGOG I feel like I'm in the dark quite often.
Sent from my "Canadian" LG-E970
whiteguypl said:
I still dont understand why any dev is working on anything other than perfecting the n4 conversion. Doing anything else seems like a huge waste of effort and time to me. A perfectly functioning n4 conversion = this phone will be in the game for years and years. Anything else just means everyone is sol when the developers for this specific phone jump ship.. that will never happen with the n4 conversion.
There is also the odd (cant put my finger on it) veil of secrecy with this phone that i never bumped into before. So much info no one knows because its just simply not shared in any way.
Click to expand...
Click to collapse
This phone is already essentially a N4. We are working on methods of porting the nexus 4 kernel to our phone that do not require any modifications, so we will always be able to run anything the n4 can run anyway. Basically, there will be a longer wait because this is harder to do, but it will be better in the long run, as we fully understand what is going on.
Accept that the problem still stands with a ported kernel doesnt it? You guys leave and we need a new kernel and are s.o.l. . Also please dont take what im saying as any kind of insult, its not. Just looking to understand better.
Though i guess the same could be said for a perfected conversion is something in that needed changing.
There is now a fix for jelly bean rons after converting back to stock
http://forum.xda-developers.com/showthread.php?t=2146816
[FIX][Re-stock after N4][E970] Camera Fix for JB !!!ALPHA!!!
Sent from my LG-E970 using xda premium
whiteguypl said:
Accept that the problem still stands with a ported kernel doesnt it? You guys leave and we need a new kernel and are s.o.l. . Also please dont take what im saying as any kind of insult, its not. Just looking to understand better.
Though i guess the same could be said for a perfected conversion is something in that needed changing.
Click to expand...
Click to collapse
Of course both would need kernel changes to make everything work 100%. Either way, someone would need to fix things. Fixing the kernel to boot with full stock may take more work, but I would consider something that does not require modifying the non "normal" partitions of the phone to make work better than something that modifies the base bootloader of the phone.
whiteguypl said:
I still dont understand why any dev is working on anything other than perfecting the n4 conversion. Doing anything else seems like a huge waste of effort and time to me. A perfectly functioning n4 conversion = this phone will be in the game for years and years. Anything else just means everyone is sol when the developers for this specific phone jump ship.. that will never happen with the n4 conversion.
There is also the odd (cant put my finger on it) veil of secrecy with this phone that i never bumped into before. So much info no one knows because its just simply not shared in any way.
Click to expand...
Click to collapse
You're so right about the veil of secrecy!
C2fifield said:
While I personally don't really agree with the first comment (I feel as though stock LG development has its place and there are dangers to the conversion), I definitely agree with the secrecy, on my old inspire I knew just about everything the devs were working on, what was and wasn't working, as well as which problems they were facing. With the LGOG I feel like I'm in the dark quite often.
Sent from my "Canadian" LG-E970
Click to expand...
Click to collapse
HA! thank you! i HATE this stupid secrecy thing that alot of people in this community have. i have also never experienced anything like it. it really keeps things from expanding. people in here know that they run the risk of damaging their phone anytime they flash anything. the reason these people are keeping things secret is because they think that "dumb people will brick their phone". i have personally been running a solution to running n4 roms/aosp stuff without having to do any conversion for multiple weeks without any harm to my phone. i have a completely working cm-10.1 rom with full internal (16gb), full access to external, cap buttons, led lights, LTE, etc. everything works but i was told by members of team codefire that if i release it then i am an effing moron.
sk8erwitskil said:
HA! thank you! i HATE this stupid secrecy thing that alot of people in this community have. i have also never experienced anything like it. it really keeps things from expanding. people in here know that they run the risk of damaging their phone anytime they flash anything. the reason these people are keeping things secret is because they think that "dumb people will brick their phone". i have personally been running a solution to running n4 roms/aosp stuff without having to do any conversion for multiple weeks without any harm to my phone. i have a completely working cm-10.1 rom with full internal (16gb), full access to external, cap buttons, led lights, LTE, etc. everything works but i was told by members of team codefire that if i release it then i am an effing moron.
Click to expand...
Click to collapse
Who cares what team codefire thinks just keep doing what you are doing and thanks for everything can't wait to try something out. If you need more/any tester just let me know I have best buy insurance so not worried about bricking.
Sent from my LG-E970 using xda premium
sk8erwitskil said:
HA! thank you! i HATE this stupid secrecy thing that alot of people in this community have. i have also never experienced anything like it. it really keeps things from expanding. people in here know that they run the risk of damaging their phone anytime they flash anything. the reason these people are keeping things secret is because they think that "dumb people will brick their phone". i have personally been running a solution to running n4 roms/aosp stuff without having to do any conversion for multiple weeks without any harm to my phone. i have a completely working cm-10.1 rom with full internal (16gb), full access to external, cap buttons, led lights, LTE, etc. everything works but i was told by members of team codefire that if i release it then i am an effing moron.
Click to expand...
Click to collapse
I'd like to just chime in and say 1) one person said you'd be an effin moron and he is far from the whole of team codefire. His words and actions don't represent the team as a whole, and his words were uncalled for. He could have said things in a nicer way. 2) The cm-10.1 you have relies on a testing version of freegee that was developed, but since abadonded. The reason it was abadonded was quickly we discovered that it bricked sprint radios. We had 4 people, including myself, loose radio. Thus this new freegee method was dropped.
We are instead working with 3.4 lge kernel source. I've also narrowed down what I believe the issue is on mako kernel not booting stock, to be the lge power management vs caf/mako power management. We'd probably have lge 3.4 working by now, but all of us, sk8 included jumped on using mako kernel once it was discovered about this slightly different freegee method. However like I said, after we bricked 4 radios on sprint, we didn't expand the testing any further and stopped.
Hi there.
Following @Tijmen's advice, this thread is for those who have damaged screens (specifically the black lines). There are reports that a reboot triggers this issue. @autoprime had his G2 (never flashed recovery, kernel or ROM) get the black lines after rebooting into Stock Recovery when he was only using ADB with the phone hot.
My device:
Model: LG G2 D805
Current ROM: CloudyStock 2.3 (flashed after the screen panel replacement through RMA)
Panel: $ su -c 'cat /proc/cmdline' -> mdss_dsi_g2_lgd_cmd -> LGD Panel
Damage: Permanent Vertical Black Lines on the right side (borrowed screenshot; even in recovery)
External Links: Reddit 01, Reddit 02
From #[email protected] (irrelevant lines have been removed):
<gitanO0|vs980> hey all, long time since i've been on here
<gitanO0|vs980> anyone experience top to bottm vertical black lines on the right side of their screen after flashing rom?
<gitanO0|vs980> persists through boot and seen in recovery
<gitanO0|vs980> i've seen some other folks have this issue after flashing rom but not seen any solutions
<gitanO0|vs980> right after the flash of the rom, the lg boot screen came on and went all inverted and fading... I booted back to recovery and flashed nandroid and now have these perma lines on the right 1/8" or so of screen
<@autoprime> wat rom? PA?
<gitanO0|vs980> no carbon
<gitanO0|vs980> one of the devs made some 24a bootstack changes for some of the repos
<@autoprime> if it persists thru recovery it might be perm damage
<gitanO0|vs980> yeah, that's what I figurered
<gitanO0|vs980> might have to go the send it back route. any good "back to stock, unrooted" guides out there?
<gitanO0|vs980> autoprime, is there anything I can test or look at to verify if it's permanent?
<@autoprime> if its in recovery its most liekly perm
<@autoprime> if it was rom only then its fixable
<gitanO0|vs980> right
Click to expand...
Click to collapse
IMPORTANT - MUST READ IRC TEXT BELOW IN RED!:
<@autoprime> wah... i has lines on mah g2
<@autoprime> RMA
< Compass_Linux> no worries. the'll be present in the
< Compass_Linux> G3 if LG does it right.
< chachin> lol
< Compass_Linux> i wouldn't cheer to soon when this is fixed though. some regressions come with a vengeance.
< Compass_Linux> s/to/too
<@NookieBot> Compass_Linux meant: "i wouldn't cheer too soon when this is fixed though. some regressions come with a vengeance."
<@autoprime> i wasnt even flashing custom rom
<@autoprime> so its not the roms lol
<@autoprime> wasnt using twrp either
<@autoprime> was messing with adb and stock partitions
<@autoprime> reboot into stock recovery... stock recovery has lines.
< Compass_Linux> autoprime: you serious? :|
<@autoprime> Compass_Linux yup :/
<@autoprime> suxxxxxx
* Compass_Linux needs a hammer for his G2. And quick!
<@autoprime> i think its heat. mine was getting really hot in adb
< Compass_Linux> autoprime: can i add your txt to the OP?
< Compass_Linux> damn LG...
<@autoprime> ok
<@autoprime> 100% stock
<@autoprime> :/
<@autoprime> so based on how mine went down.. its not related to rom/kernel flashing :/
< Compass_Linux> cr*p
< Compass_Linux> i'll update the OP.
<+savoca> autoprime: your g2 just got lines one morning?
<+savoca> autoprime: apperently its a possible defect as well.
<+savoca> however pa's kgsl sh*t bumps the probability by like 200%
<@autoprime> today.. lines on right side
<+Khaytsus> autoprime: So your device has lines now? geez
<@autoprime> Khaytsus indeed
<+Khaytsus> Has anyone positively identified this happening on a device that's always been stock?
< Compass_Linux> Khaytsus: yes, just happened to autoprime right now.
<@autoprime> my g2 was 2nd batch
<+Khaytsus> Has anyone positively identified this happening on a device that's _always_ been stock?
<@autoprime> :/
<+Khaytsus> autoprime: Yours hasn't always been stock, right?
<@autoprime> of course it has :|
<+Khaytsus> really??
<@autoprime> this is public record
<@autoprime> :X
<+Khaytsus> My point being nobody really knows what the failure cause is yet.
<+Khaytsus> But nobody has had it happen on a device that's _always_ been stock that I'm aware of.
<@autoprime> Khaytsus i wanna say heat. but idk
<@autoprime> mine has been getting hot the past few days
<@autoprime> never had issue before
<@autoprime> then was using adb and got hot again.. rebooted into stock recovery.. lines
Click to expand...
Click to collapse
How I saw it happen:
After twrp flashed the files mentioned above, the phone rebooted to a black screen with a vertical non uniform white band in the middle, which rapidly expanded sideways until the screen suddenly went entirely black (that's the moment the screen was damaged), vibrated and turned off. When turned on, permanent vertical black lines on the right side of the screen in recovery, in ParanoidAndroid etc. Flashed a stock D805 ROM, problem persists.
What has been confirmed about the origin(s) of this issue:
@dr87 was kind to clarify this issue here, here, here and here.
@houstonn has some information here and here.
This issue in numbers of LG G2's affected is very low. What is increasing until now are the number of different ROMs affected.
*** Unconfirmed Information (updated 28/07/2014) ***:
It was previously thought that Custom ROMs/Kernel were the cause of this problem, and that Stock ROMs/Kernels were safe to use. This is no longer the case due to @autoprime's experience. I removed the safe and unsafe ROMs list because of this and the Black Lines Survey. The possible reason (and I'm speculating here) Custom ROMs are more prone to this is that modifications done to them or their Kernels accentuated the problem that the phone already has but haven't yet appeared (not all devices due to the still small number of complaints). With the information we have now, it indicates that a hardware failure related to heat is to blame, and using a Custom ROM/Kernel can make the failure appear more quickly than if you keep completely at Stock. In @autoprime's case the simple use of ADB then reboot into Stock Recovery with the phone hot triggered the black lines. And since people are asking what is safe to flash and whatnot, there is unfortunately no answer as of yet.
My device is back from RMA (Return Merchandise Authorization). The panel has been replaced, and after flashing (recovery and ROM) no black lines.
@dr87 has a very interesting post here. He has also built a custom twrp with thermal control. If you use this and it corrupts your /cache partition, do this.
@chillstep1998 has a post about an app that can somehow remove (in his case all of them) the black lines. I'm not sure how it works but if you do chose to use it (if you have no warranty for example), remember that your results will likely vary from others experience.
Which Panel do I have? LGD or JDI?:
Here. Thanks go to @autoprime.
When was my G2 manufactured?:
Here. Thanks go to @jdk2. Once you input the URL, check the generated page source code (you might not have to do it; I did) and read this.
Here is another (and better) way to check the same information. Thanks go to @razrzxcvbnm.
I'll leave both methods just in case one or the other "disappears".
Hints:
@RusherDude has an interesting theory. If the conditions he mentions match yours, please confirm and elaborate the best you can in the thread. Thanks!
In the meantime (considering no permanent way to avoid the black lines):
You're crazy about Custom ROMs as I am and still have some months warranty for your device. I had my screen panel replaced under warranty and it's working fine for now. If I get the black lines again I can take it for repair, as long as I'm under warranty. Once my warranty expires, I'm on my own;
You're crazy about Custom ROMs as I am and no warranty for your device. You fall into two situations basically. Repair the screen now for around USD$80 (parts only), or live with this situation and flash to your hearts content. Repairing the screen hopefully fixes the problem permanently.
Black Lines Survey:
User @NicoC72 created a Black Lines Survey, Graph and Spreadsheet. Thanks!
Contact:
You can find me and lots of nice people in the #lg-g2 IRC Channel at irc.freenode.net (go to Freenode for instructions on how to connect)
To see if I'm away, use /whois Compass_Linux.
Compass.
RIP screens :/
did you try a return to stock method to check if issue survives that?
bachera said:
did you try a return to stock method to check if issue survives that?
Click to expand...
Click to collapse
Few people have reported using tot and kdz, and the issue stayed.
Sent from my Vs980 running Mahdi 2.5
http://forum.xda-developers.com/showthread.php?p=52969597
so after going to stock and using the dialer code ( update firmware) it stayed after a reboot? Dr's suggestions might be handy. I dont have the issue but listing all avenues walked to solve might help.
Is there not a disclosure in every op.. To flash at ur own risk.. I have ran many of houstonns roms and i highly doubt that a rom can cause this.. Closing houstonns thread is little to much dont u think... 4 or 5 out of 1000s of people who flashed this rom. Come on! Bullsheit
Sent from my LG-D800 using XDA Free mobile app
I agree, I've seen this issue pop up in multiple rom threads. It's not just PA. It happened to me after a flash of slimKAT a while back. I don't think it's software related. I think it's faulty hardware that's causing the issue. Quite honestly, I think that while backing up and flashing a new rom in recovery, the device gets hot and stresses the hardware.
I think that houstonn is getting crucified unfairly on this.
bachera said:
did you try a return to stock method to check if issue survives that?
Click to expand...
Click to collapse
Yes, no success.
Thanks for mentioning. I've updated the OP.
Compass.
bachera said:
http://forum.xda-developers.com/showthread.php?p=52969597
so after going to stock and using the dialer code ( update firmware) it stayed after a reboot? Dr's suggestions might be handy. I dont have the issue but listing all avenues walked to solve might help.
Click to expand...
Click to collapse
Doing the Touch Firmware Upgrade also fails, unless you mean something else. Thanks.
Compass.
bps119 said:
I agree, I've seen this issue pop up in multiple rom threads. It's not just PA. It happened to me after a flash of slimKAT a while back. I don't think it's software related. I think it's faulty hardware that's causing the issue. Quite honestly, I think that while backing up and flashing a new rom in recovery, the device gets hot and stresses the hardware.
I think that houstonn is getting crucified unfairly on this.
Click to expand...
Click to collapse
You need to share that this happened to u on another rom with the monitor that closed his thread
Sent from my LG-D800 using XDA Free mobile app
iamtha1 said:
Is there not a disclosure in every op.. To flash at ur own risk.. I have ran many of houstonns roms and i highly doubt that a rom can cause this.. Closing houstonns thread is little to much dont u think... 4 or 5 out of 1000s of people who flashed this rom. Come on! Bullsheit
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think closing houstonn's thread is too much. Moderation has tried to contact him to no avail.
As for the 4 or 5 people out of 1000's, those are the ones that have been reported in XDA. If you leave this issue unresolved, you can expect an increase in those numbers.
And so far the damage is permanent.
I mentioned the warranty/liability in my Post 01. If I knew I could damage my hardware permanently like this, I wouldn't have upgraded P.A. and might have changed ROMs (back to stock maybe).
bps119 said:
I agree, I've seen this issue pop up in multiple rom threads. It's not just PA. It happened to me after a flash of slimKAT a while back. I don't think it's software related. I think it's faulty hardware that's causing the issue. Quite honestly, I think that while backing up and flashing a new rom in recovery, the device gets hot and stresses the hardware.
I think that houstonn is getting crucified unfairly on this.
Click to expand...
Click to collapse
It could indeed be a hardware issue, but that doesn't exempt the fact that P.A. (and other ROMs apparently) is triggering this.
Compass.
On the Mahdi thread I saw the ROM author say he avoids commits that change the panel driver code, or something to that effect, and that's why his ROM hasn't had that issue. Have there been reports on his ROM too? Now I'm scared to flash anything.
Compass Linux said:
I don't think closing houstonn's thread is too much. Moderation has tried to contact him to no avail.
As for the 4 or 5 people out of 1000's, those are the ones that have been reported in XDA. If you leave this issue unresolved, you can expect an increase in those numbers.
And so far the damage is permanent.
I mentioned the warranty/liability in my Post 01. If I knew I could damage my hardware permanently like this, I wouldn't have upgraded P.A. and might have changed ROMs (back to stock maybe).
It could indeed be a hardware issue, but that doesn't exempt the fact that P.A. (and other ROMs apparently) is triggering this.
Compass.
Click to expand...
Click to collapse
Dude every dev warns u that flashing roms can damage ur phone.. Come on... Stick to stock if u cant handLe damaging u phone
Sent from my LG-D800 using XDA Free mobile app
I'd like to remind people that flashing a tot or kdz only replaces 12 partitions out of the total 39 partitions on the device.
Partition list here - http://pastebin.com/S5XtQtW3
I can't confirm anything but it seems no one has backed up all partitions and restored them after running into this issue.
so it's still not 100% that it's permanent damage(although it very well could be).
tot/kdz is made to get you booting.. not fix all the things. I have a zip I made to automate the backup of a lot of these partitions... of course you can always do it manually too.
http://forum.xda-developers.com/showthread.php?t=2451390
tbh.. I'm not sure what each and every partition does.. or if it can be shared between users. Example: modemst1 and modemst2 is your EFS and is unique to your phone only.
Only common thing I see between everyone with issues is they all used a custom recovery... maybe we shouldn't use those either
autoprime said:
I'd like to remind people that flashing a tot or kdz only replaces 12 partitions out of the total 39 partitions on the device.
Partition list here - http://pastebin.com/S5XtQtW3
I can't confirm anything.. but it seems no one has backed up all partitions and restored them after running into this issue.. so it's still not 100% that it's permanent damage.
tot/kdz is made to get you booting.. not fix all the things. I have a zip I made to automate the backup of a lot of these partitions... of course you can always do it manually too.
http://forum.xda-developers.com/showthread.php?t=2451390
tbh.. I'm not sure what each and every partition does.. or if it can be shared between users. Example: modemst1 and modemst2 is your EFS and is unique to your phone only.
Only common thing I see between everyone with issues is they all used a custom recovery... maybe we shouldn't use those either
Click to expand...
Click to collapse
Thank u prime!
Sent from my LG-D800 using XDA Free mobile app
iamtha1 said:
You need to share that this happened to u on another rom with the monitor that closed his thread
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Done
iamtha1 said:
Dude every dev warns u that flashing roms can damage ur phone.. Come on... Stick to stock if u cant handLe damaging u phone
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I assumed the risk of flashing a Custom ROM, as I've mentioned before.
Again, this doesn't exempt the people responsible for the Custom ROM. I'm not seeking damages against them or anything. The only thing I asked for was to remove the P.A. ROMs from when this issue began. And I don't think that's too much to ask for.
Compass.
Compass Linux said:
I assumed the risk of flashing a Custom ROM, as I've mentioned before.
Again, this doesn't exempt the people responsible for the Custom ROM. I'm not seeking damages against them or anything. The only thing I asked for was to remove the P.A. ROMs from when this issue began. And I don't think that's too much to ask for.
Compass.
Click to expand...
Click to collapse
Because u had a problem with pa... Everyone else including myself know cannot run it.. I have ran every beta he has released with no problems what so ever! Now a rom that i love may be in jeopardy of being gone.... Thanx for ur help buddy but it wasnt needed!!
Sent from my LG-D800 using XDA Free mobile app
Flashes on VS980 no problem. You guys had me worried for a minute. Hopefully they fix the issue across all devices. It's a great ROM.
iamtha1 said:
Because u had a problem with pa... Everyone else including myself know cannot run it.. I have ran every beta he has released with no problems what so ever! Now a rom that i love may be in jeopardy of being gone.... Thanx for ur help buddy but it wasnt needed!!
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Not only me, if you read the OP. And not only on Paranoid Android either.
I can private message you the Paranoid Android official webpage, where you can download. I cannot post the link here.
You have to contact houstonn to see if it will continue to be developed. I have no influence on the matter, as you suggested the contrary.
I also like Paranoid Android, but this problem cannot persist. It has even spread to other ROMs.
Compass.
Hello,
After a year or so after buying a SGS III, I started experiencing slowdowns. Six months later I installed Android 4.3 as it was available with OTA. I run official ROM, nothing fancy. Now, I experience serious performance slowdowns during new screens loading, switching applications, any action in fact can be slow; when I listen to music (standard player) sometimes I get 10 cuts in a song.
I have like 60 apps installed. My average RAM load is 750 MB / 831 MB.
I have never reset to Factory defaults. I just tried deleting all my text msgs to improve loading, it dit not change anything.
I imagine the current services load is too heavy for a pretty old phone. Is this the reason for huge performance slowdowns (sometimes 5 secs delays)?
I also fear the development of the Samsung layer is pretty bad. When you take into account, the poor dev capabilities Samsung demonstrated with Kies, or with PC interface (I struggle uploading files to the device, it gets deconnected all the time). I think Samsung is good at electronics, but bad at software; this would be a personal "feeling". I aslo experienced huge performance drops with SGS1.
What do you think of the reasons for performance issues with SGSIII ?
You are on unmodified stock, that is the reason.
boomboomer said:
You are on unmodified stock, that is the reason.
Click to expand...
Click to collapse
No troll please, it s too easy
one more thing
There is one more think I wanted to add: I wonder if Samsung does not use "programmed obsolescence" (don't know if it is the correct term)...
No, I wasn't trolling. Unmodified stock has over sixty processes and services running all the time while most users only need four or five.
Over time and use the system will slow even further as firmware updates and third party apps interfere.
The phone hardware is well up to running 4.3, just not sixty things at once.
Your first step is to backup your personal data then factory reset and format the internal storage. This will improve things immediately but until you switch to a custom firmware, even one with a stock base, you will not solve the problem.
Even on stock firmware you can disable 80% of the junk Samsung installed.
Very honest opinion.. Just flash your phone with Cyanogen or another custom ROM.. This should be the best bet for you!
You should get KitKat 4.4.4 as of now.
Sent from my GT-I9300 using XDA Free mobile app
boomboomer said:
No, I wasn't trolling. Unmodified stock has over sixty processes and services running all the time while most users only need four or five.
Over time and use the system will slow even further as firmware updates and third party apps interfere.
The phone hardware is well up to running 4.3, just not sixty things at once.
Your first step is to backup your personal data then factory reset and format the internal storage. This will improve things immediately but until you switch to a custom firmware, even one with a stock base, you will not solve the problem.
Even on stock firmware you can disable 80% of the junk Samsung installed.
Click to expand...
Click to collapse
Thanks for your explanations, they are helpful.
I experienced huge performance drops one year or so after installing Darky ROM on my SGS1; I had to switch back to stock ROM. That's why I'm not eager to try the "custom ROM experience" again; it takes too much time.
I still have two questions to you, you seem to know well this Android subject:
1. Does the factory reset changes the ROM installed, or just wipes the user data?
2. How do I disable some stock services? Is there a good app? (I could not find anything useful by forum search)
AOSP Custom rom is for the enthusiast only, as they all come with drawbacks like shorter battery life or hardware issues. Custom rom based on stock is suitable for daily use, as they are just debloated.
Factory reset only wipes user data.
App manager, click on the service or app then disable button. Caution that some are essential to things you might need, search and read here on xda for guides on what is pure bloat.
Bro! I'm using the same phone. Had loads of problems with Samsung's TouchWiz. Your phone is absolutely fine. Use Cyanogen CM11 it is way better. I have been using Cyanogen for almost 6-7 months and honestly I have had problems but XDA is always full of solutions.
Go to "get.cm" and use the automatic installer to install cyanogen into your phone without you having to do anything such as rooting and flashing.. Cyanogen Installer does it automatically for you. If you are not satisfied you can always manually install cm
" https://www.google.co.in/url?sa=t&source=web&rct=j&ei=AiF_VOnCFNO3uQSw1YEY&url=http://m.ibtimes.co.in/how-install-cyanogenmod-android-4-4-4-kitkat-cm11-m9-custom-rom-samsung-galaxy-s3-i9300-tutorial-606129&ved=0CBoQFjAA&usg=AFQjCNHiKLLDngZKWM8lvfSa15QTXRRzdA&sig2=VZslZMxWssAwAyjfm0F8WQ"
Which is of course free of cost!! You just need 4 things
1. Samsung GS3 i9300
2. USB
3. A PC
4. INTERNET
Check out my Setup
https://plus.google.com/102584932386482931948/posts/VuXyAnPJMtM
Sent from my GT-I9300 using XDA Free mobile app
Thanks for the hints. I found this thread witch can be helpful: http://forum.xda-developers.com/galaxy-s2/themes-apps/applications-safe-to-remove-t1069924
I think I will use Titanium Back Up App to remove unused services. Crap, I'll have to root the phone! I ll wait till I get a new phone, I'm looking for a good LTE-A no QHD (just FullHD) candidate.
Returning to the thread point, does all brands have this kind of performance problems or are there some more stock optimized phones? I'm hesitating getting away from Samsung, even if the OLED screen are really great (excepted the color saturated ones like the Alpha's). I was told HTC was more optimizing its layer, but I don't know if it is really true...
ROOTING your phone will unlock endless possibilities!
Regarding HTC, their flagship devices are very good.. Always first with updates right after google launches for their nexus devices very good sound and faster than other same priced smart phones.
Even Nexus devices are really a great deal giving you stock android with great performance and .01% lag.
Samsung is a more feature based smart phone with over used RAM and disabling the system apps causes the system to crash every now and then. I too love Samsung devices but prefer to use the stock android or even a custom ROM instead of TouchWiz.
Sent from my GT-I9300 using XDA Free mobile app
boomboomer said:
AOSP Custom rom is for the enthusiast only, as they all come with drawbacks like shorter battery life or hardware issues. Custom rom based on stock is suitable for daily use, as they are just debloated.
Factory reset only wipes user data.
App manager, click on the service or app then disable button. Caution that some are essential to things you might need, search and read here on xda for guides on what is pure bloat.
Click to expand...
Click to collapse
Eventually, I rooted my phone, as it has no more warranty anyway. I've unistalled some forced system apps, frozen some RAM resilient apps/services. Now I have an average of 200 MB free RAM and the screens loading in TouchWiz are fast as at the beginning
So, thanks to your help, I can answer my own question about performance loss: too many resilient services for a 1GB RAM phone; it's about time I get a new phone
I hesitated to root the phone because I will give it to my girlfriend and she is the type of user clicking on every OK button when she gets a dialog. How she said she will not take the phone because I tinkered with it! Ah women ...
Hi guys,
I'm sorry cause asking this, especially cause this question has been asked manytimes and I have read several subjects too, but I didn't strict answer I'm looking for.
I recently bought nexus 9 (WiFi only model) 16gigs,
I unlocked bootloader, I rooted the device and now I want to debloat it.
I'm in dilema weither I should just have it rooted and debloated on 7.1.1. android, or should I use some of the custom roms around.
I'm aiming to use tablet mainly for gaming. I have servral games I'd like to play listed:
Marvel Future Fight
DC Legends
Star Wars Galaxy Heroes
Star Wars Force arena
and few others but i take it that if those can run fine, all others would too.
Also can someone point me to a safelist of application that can be removed if answer to first question is to just leave it rooted and debloat.
Thank you a lot for help.
Cheers.
IrethTassartir said:
Hi guys,
I'm sorry cause asking this, especially cause this question has been asked manytimes and I have read several subjects too, but I didn't strict answer I'm looking for.
I recently bought nexus 9 (WiFi only model) 16gigs,
I unlocked bootloader, I rooted the device and now I want to debloat it.
I'm in dilema weither I should just have it rooted and debloated on 7.1.1. android, or should I use some of the custom roms around.
I'm aiming to use tablet mainly for gaming. I have servral games I'd like to play listed:
Marvel Future Fight
DC Legends
Star Wars Galaxy Heroes
Star Wars Force arena
and few others but i take it that if those can run fine, all others would too.
Also can someone point me to a safelist of application that can be removed if answer to first question is to just leave it rooted and debloat.
Thank you a lot for help.
Cheers.
Click to expand...
Click to collapse
For the best performance, install a custom ROM. As for debloat, ... It's a Nexus, what bloat?
But if you want minimal, I would say flash slimrom and the smallest gapps package that fits your needs. Or go gapps free and use micro g instead.
Performance on stock is pretty bad (really bad), but a custom ROM will fix it for the n9. When I say bad on stock, I mean opening more than 1 tab in chrome, it has to reload the page every time switching between the two. Same with having a couple apps open.
Fortunately, most of the ROMs out there take care of all that.
madbat99 said:
For the best performance, install a custom ROM. As for debloat, ... It's a Nexus, what bloat?
But if you want minimal, I would say flash slimrom and the smallest gapps package that fits your needs. Or go gapps free and use micro g instead.
Performance on stock is pretty bad (really bad), but a custom ROM will fix it for the n9. When I say bad on stock, I mean opening more than 1 tab in chrome, it has to reload the page every time switching between the two. Same with having a couple apps open.
Fortunately, most of the ROMs out there take care of all that.
Click to expand...
Click to collapse
I'm on latest Android 6 stock, unencrypted and Fire Ice kernel. its running fine and if use the chrome that comes with the stock and don't update it, it will run fine.
How would someone find official roms? I used pure nexus rom thinking that is official but i guess i was wrong. I not to big on roms knowing. They all looks the same to me I just care to be able to uninstall builtin apps i don't use and that everything works fine.
This one i use now had a problem common with nexus 9, white blocks and anoying skrechy sound, but i read somehwere it is fixed by unhoking battery, cleaning pins and putting it back together. I tried it and I didn't have problems since then. I drained battery to 2% no problem, before it was impossible. I have no idea was it ROM issue or what.
IrethTassartir said:
How would someone find official roms? I used pure nexus rom thinking that is official but i guess i was wrong. I not to big on roms knowing. They all looks the same to me I just care to be able to uninstall builtin apps i don't use and that everything works fine.
This one i use now had a problem common with nexus 9, white blocks and anoying skrechy sound, but i read somehwere it is fixed by unhoking battery, cleaning pins and putting it back together. I tried it and I didn't have problems since then. I drained battery to 2% no problem, before it was impossible. I have no idea was it ROM issue or what.
Click to expand...
Click to collapse
That's a common hardware issue for n9, not a ROM issue.
madbat99 said:
That's a common hardware issue for n9, not a ROM issue.
Click to expand...
Click to collapse
But it's safe to say that it's fixed now. Everyone was talkin about disconnecting battery, and clean a bit and connecting again.
it seems such a easy troll solution to this "very anoying and hard problem that even HTC didn't solve", and i did it and it really did the job (knock on a wood ). I've been draining battery to the end for 3 days now, nothing ever like that happend ever again. before it wasn't even a day when i didn't experienced that problem.
IrethTassartir said:
But it's safe to say that it's fixed now. Everyone was talkin about disconnecting battery, and clean a bit and connecting again.
it seems such a easy troll solution to this "very anoying and hard problem that even HTC didn't solve", and i did it and it really did the job (knock on a wood ). I've been draining battery to the end for 3 days now, nothing ever like that happend ever again. before it wasn't even a day when i didn't experienced that problem.
Click to expand...
Click to collapse
Good to hear. That usually is the fix for that.
Please, just to confirm, is this "image-volantis-n9f27l" official ROM or it's custom ROM?
I also use this bootloader : "bootloader-flounder-3.50.0.0143" since other ones didn't work for me.
I was with support trying to solve issue of Device restarting every time I install new app or update app, and while trying to clear cache partition, it gone to my device not wanting to boot. so i had to factory reset, and it still won't start android in full. so i have to reflash ROM. I guess.
I'm kinda lost now cause i don't know what to do.
As said i just want for my device to be rooted so i can delete all apps i don't need and change launcher (deleting existing one - well i don't know if it's smart or not. i figure why having two launcers when i will use only one).
And i want to play games and use apps without it failing on me all the time.