[Q] REALLY Laggy phone after a bit. - Galaxy S6 Q&A, Help & Troubleshooting

I have a S6, stock rom
I did end up rooting it, but not using root for all that much other then removed the charge sound, and a little thing here and there
but for some reason, this phone gets super laggy! I don't know what is wrong. It seems that Snapchat seems to make it worse, but when I don't open it, it still can get laggy. Facebook Chat also seems a little problematic, not 100% sure though.
Any ideas? I know I'm being pretty vague, but i am hopeing that peopel have had some idea.

Just flash back stock ROM via Odin. Below are stock ROMa from Sammobile. Just choose your country.
http://www.sammobile.com/firmwares/database/SM-G920F/

well, wiping out the phone, and starting over fixed it. BUT, this has happend on other phones that I have had also.
idk what to do..

Related

[Q] Samsung Captivate-advice buying used

Hi all,
I'm looking for a Samsung Captivate, and i saw one online for $100, but the phone won't start. From what the seller said, it was rooted, and it'll boot up, but the phone then states something to the effect that "the launcher is not responding". My question is this: I don't have experience with Android phones, but does this sound like something that can be fixed using software methods?
I'm experienced with iPhone jailbreaking and WP7 hacking, so I'm not afraid of the challenge, i just want to know if there's a good chance of reviving the phone (assuming there's no physical/water damage)
Thanks in advance!
Launcher issues are easy to fix, fixed even easier with a factory reset which I assume you will do if the seller hasn't. If it's been factory reset and it's giving those issues....well I can only see that happening if there is a custom ROM loaded.
Either way, if you believe it boots, I would buy it. The launcher is basically your home screen, and if the phone can load that far, that's all software level stuff, easy to fix. I own a captivate and I always liked the phone, but rooted and ROM'd it is SO much better. Hope this helped
Hey, thanks so much for the reply! I'll see about piking it up today and let you know what happens
Sent from my SGH-i917 using XDA Windows Phone 7 App
No problem man, if you need help when you get back with it let me know. I'll be glad to help with whatever
So i got the phone today. The phone was pretty laggy, so i used the Odin3 one click sw to bring it back to stock. It worked, but the phone is still laggy. Wouldn't you think that flashing it back to stock would fix any issues with it? I tried it twice.
Also, when i try to open the applications section, it tells me that "TWLauncher is not responding", even after flashing it. I was thinking about just flashing it to CM7, but i have to get the .zip file onto an sd card so i can flash it from recovery. Do you think this might help? Thanks in advance!
Honestly man, my captivate was just like that (laggy), TWLauncher is the UI launcher, TouchWiz. There are thing's about it liked but mostly I hated it. I would root and ROM the phone with something stable (I run CM7, there is finally an RC for captivate). Also, Odin puts the phone back to 2.1, and there was all kinds of GPS bugs and stuff with it, they have 2.2 stock for it now, which runs a bit better but I still don't like.
Also, try removing the SD Card from the phone, in case it's a ****ty one and causing lag while loading in the beginning. That may not help at all, I'm no expert, but I am a huge nerd and it makes sense to me. Just realize the stock firmware on the phone ruins the experience a bit.
Edit: I didn't notice the CM7 part, just make sure the zip is in your main directory, don't put it on either of the SD cards (internal or external).
So the .zip actually goes onto the phone memory itself? That makes sense. I'm having issues getting my phone to mount and the computer to recognize it. My computer doesn't see it as an external drive. I'd try to go to the settings and change it to mass storage, but the stupid TWLauncher isn't working!
Can you load the android market? Try to get ADWLauncher, the free one. Get that installed, and when you push the home button it should ask you which launcher to use. Choose ADWLauncher, possibly reboot, and try again. Again, I hate TWLauncher, it was the first thing I replaced on my phone.
edit: lol, don't forget to hit "use as default" before you select ADWLauncher.
edit again: Dammit, I'm terrible at this...if you can't get android market open, make sure your phone stays on, go to the android market website, and install it from there. That should work for sure
Ok, so I used Odin3 one click version 2.2 (which has froyo and the JI6 build number. Everything works fine, but I'm not able to get out of airplane mode and get cell signal. the phone says the baseband version is unknown. If i use the Odin3 One click 2.1 (build JF6, the phone is in the same unresponsive state it was when i first got it. It doesn't even take me to the setup when you first launch the phone.
It's really weird. I wonder if there's was a way to flash it back to stock without one click. I'm wondering if the ROM in there is corrupt or something. The reason why i want to get back to Android2.1 is because all the CM7 tutorials say to start from there. So yeah. Any other suggestions?
Oh, i got rid of TWLauncher, and yeah. I hate that thing!
Well...the Odin I used took my phone back to base stock 2.1, after I was already on 2.2, you 2.2 has this sig verification crap and you can't flash anything. So I'm not sure which Odin I have, but it took it to 2.1, I imagine yours should too... This problem may need someone smarter... So make sure the Odin you are using is meant to take you to 2.1, make sure it specifically says it's for captivate. If both of those are verified, odin isn't working for some reason. Did you follow the Odin guide for captivate to make sure you didn't miss anything?
Well, i found a random thread on the CM7 forums that said to try using Odin regular, and flashing the original firmware. So i did that and it worked! The phone was usable again! Only thing was that i didn't have any cell service. So i flashed the CM7 ROM and the baseband was fixed. All is well, and i'm loving my device. Thanks so much for your help!
Woot! Man I'm super glad you got all that working, I had to return a Captivate due to no service...so I'm glad CM7 fixed that for you. Super awesome that it's working, glad I could help bro. Enjoy!

Is my Samsung Infuse DEAD?

Hey, guys. Hoping some of you experts can help me diagnose what's wrong with my Samsung Infuse. I bought it off Craigslist at the end of May, and the guy had the phone with the original screen protector on it, with the original case and all accessories, so I had no reason to believe it had any problems. He told me the phone was already rooted & unlocked, which I wanted since I signed up with Straight Talk. I used it for June & July and had a host of problems, so I put on the CM10 ROM last week to see if it helped. It didn't. Here are the problems I continuously encounter:
1. When going to unlock my phone with a pattern, once in awhile it won't detect my finger-presses. Sometimes nothing shows up at all, sometimes one of the dots will highlight as I pass over it, but it won't draw. Eventually the screen turns off, and I turn it on and try it again. Usually it ends up working.
2. The battery dies much quicker than I expect it should. I tried running JuiceDefender and not running JuiceDefender, and it doesn't seem to make a difference. Even without using my phone much for anything, even with the screen off, the battery will run out before the day is out. It's like if you were driving and had a hole in your tire... seems like some sort of a leak.
3. The cell radio seems flaky. Sometimes I won't get texts on time. A lot of the time I can't access any data, which is very important as I use Google Voice for lots of my texting, so I send a text and it won't go out. Loading web pages or reloading my email shows that it is a data problem.
Those are the primary problems, and I suspect that somehow they are all related. I'm not sure if the Craigslist guy sold me a lemon, or there is some other problem that came up. I've tried multiple ROM's and disabling every app I can think of. Can anyone think of anything that would cause these problems & any way to fix it? Or do I just own a broke phone that I have to throw in the garbage?
Thanks in advance for reading!
a whole slew of problems can lead to a whole slew of possibilities for your issues.
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
the "never fail" here.....READ READ READ. feel confident as to what you are doing and follow steps one at a time. UNDERSTAND steps one at a time.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
i know almost everyone else here is more of a expert than i am, but i do believe that is where they will tell you to start
good luck and be sure and thank the experts
captemo said:
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
Click to expand...
Click to collapse
While I have no idea what you're getting at by your Straight Talk comment, as ST is little more than AT&T service that's sold through a 3rd party at a discounted rate, the fact that he's using ST may be part of his problems, at least in regards to the network issues. I'm also having an unbelievable amount of data issues on ST. ST is having some network problems that are affecting a decent amount of customers who are on their AT&T network.
One thing that the OP may want to try is this: Download DNS Changer from the Play Store, and change your primary and secondary DNS to OpenDNS1 and OpenDNS2. Or try different settings, as there are a bunch that are available. That has made at least some difference with my data connectivity issues.
Based on my own experience, having tried to go to JB directly from GB, is that if it's going to affect your radio, it's likely to completely wipe out your EFS data so you won't have ANY cellular or data networking capabilities. As stated, that's simply based on how it worked out for me, and there could easily be other side-effects that just didn't happen to show up for me.
I agree with returning completely to stock UCLB3, with the GB bootloaders. Then flash Entropy's 4.4.2012 Kernel, which will also install CWM Recovery. I'd personally reccomend Heimdall, as it seems to be somewhat simpler. Detailed information on returning to stock via Heimdall can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=heimdall+uclb3
If you use it, be sure to thank qkster for making it available. He's probably the most helpful person you're likely to find on this forum, especially where us noobs are concerned.
I would take it back to stock and start all over.
Here is a very helpful thread.
http://forum.xda-developers.com/showthread.php?t=1700416
I agree with parrot head. When issues arise go back to stock. That's the best part of our phones. They are damn near impossible to really mess up. Just have to be ware of bootloader flash going wrong. If you got your gb rom from keis your good to go though.
Sent from my SGH-I997 using xda app-developers app
Appreciate the response, guys. I guess it doesn't hurt to try to start from scratch... AGAIN! It just seems like I'm putting an awful lot of hours into putting new ROM's and bootloaders on this phone. Going to be especially frustrating if I go through all the steps and it still doesn't fix my issues, which would mean my phone is broke. Oh well, guess I have little other choice.
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
drnecropolis said:
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
Click to expand...
Click to collapse
Yes, the flashing process isn't that long, it's getting back my phone to all of my customized settings that ends up taking weeks. Home screen icon positioning, logging in to every app, system settings, etc.
Didn't create a backup?
drnecropolis said:
Didn't create a backup?
Click to expand...
Click to collapse
I've always created backups with Titanium Backup, but when I restore the apps, a lot of them ask me to re-login or re-verify myself.
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
veeRob said:
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
Click to expand...
Click to collapse
Are you still using the Trebuchet Launcher that comes built-in to the JB ROM? If so, that may be part of your lag problems. I just use ADW EX launcher. Here's an excerpt from the Paranoid Android JB OP:
******* EVERYONE: If you experience a sudden lag for no reason, IT is due to Trebuchet. GOOD NEWS though... From reading the log cat on my end, there is a very simple fix... Go to settings -Launcher - Homescreen - And Check "Resize any widget" and you are good to go! Instantly fixes the lag problem that a few have been experiencing. I have located the source code that needs to be changed and this will be enabled by default on future builds. ********
Click to expand...
Click to collapse
As far as the GPS goes, I think Samsung just used ****ty receivers in the Infuse. My GPS isn't quite as bad as yours seems to be, but it's nowhere near as accurate or reliable as the GPS chipset in my crummy little Optimus V.

My SK4G Story

Hi all,
I finally decided to add a custom rom to my SK4G. I had retired it for a year or so, not from getting a new phone, but rather my youngest child dropped it in a mud puddle. I had put it in rice and all that good stuff. I was able to get it to turn back on, but it has very very very low battery. So I put it on the charger, and it would briefly show the charging symbol and disappear. So I had assumed that it was totally shot, And while I was disappointed, because I love this phone, it still was not surprising. I mean it was in a mud puddle right. LoL
Well about 2 weeks ago I got bored, and figured what the smudge, I will ticker with it. I figured, I couldnt do any worse to it than what was already done. So I once again tried to see if it would charge. Tried by wall charger, by car charger, and by USB charging. But alas once again nothing. Well my husband also has a SK4G. So I ganked his battery for a little bit, and lo and behold, it worked. Turned on flawlessly, and not one issue in the operating system at all. Well at least as flawlessly as a stock SK4g could get. lol
So I was thinking maybe the charger slot had shorted out for whatever, from it being in the mud puddle. I put the battery from my SK4G in my husbands phone and agin tried all 3 charging methinds, and still nothing. So I pluged my phone in with his battery and it went to charing just fine. Okay so, new battery. Not that bad, but I dont order anything over the net. I hate waiting, I live in a big enough city, I figured I could go to one of the electronic stores and get one.
So I tried 5 different places, no one had a replacement for it, but once gain I was impatient and didnt want to wait. Did some googling and found out Batteries plus carries a replacement for it. Wasnt thrilled by the fact that they charge 2 to 3 times more for it that other places. But whatever, if it got my phone running again, okay. I had my oldest son pick me up one on his way home from work. Gave him the stock battery numbers and all that. He brings it home, and I go to put it in and..................It is not even close to being a compatible replacement for the samsung battery. Went back down there and returned it. Told the sales clerk that their website was completely wrong. Upon looking through their wall of replacement cell batteries, I did find another battery that was a perfect match. Only to have the "Battery Expert" argue with me about it being the right one. Finally got him to stop running his mouth and bought the battery.
I had just recently ended my contract with t-mobile, and wanted to take my SK4G with me to a new carrier. Well in order to do that, I needed to unlock the network. So it was research time. Googled and found XDA. Which from then on has ben invaluable to the process. Found Sidekick 4G Unlocking *Follow Directions Closely written by troby86 and SuperOneClick - Root/Unroot Your Samsung Sidekick 4G by Ayoteddy .Had a few problems with SOC. It kept freezing at step 7. Took me a few to find the reason why ( answer is in the forums here, just took some digging and reading to find. The culprit was the "Exploit setting needed to be set to "psneuter". Changed that and finshed rooting with out any more problems on that part.
Next had to unlock the network, following the above mentioned thread. Tried it 2 or 3 times to no avail. Then it dawned on me that I hadnt rebooted after I got it rooted. So rebooted and tried the terminal part of it again. And Bingo! It took the commands or whatever you would like to call them. SK4G was now unlocked. Yay!
SInce I had already been in the forum looking at the unlock and root guides. I decided why not go ahead and put a custom rom on it too. I loved my SK I just loathed the software on it. Constantly freezing while surfing the net or trying to use facebook. I spent a bunch of time browsing the forums, reading the comments on all the roms and trying to decide which rom I wanted to use. I had orginally choose CM6-Merged.
So read the thread on it, and even watched a youtube video by sinesolder. The next task was to chase down all the files I needed to install that, plus the CWM stuff too. I flashed CWM using the app "Root Manager" in the play store. Next was to swap out the "recovery" file. Took a few mins to find it, but did. Placed it in the root of the SDcard along with the update zip. Downloaded Astro file manager from the play store. Went to bottem of list and copied the recovery file, then pasted in system/bin folder. Rebooted, clicked reinstall packages on the stock (blue) recovery screen. But it was a no go. it would not give me the orange CWM. It just ket saying E :file invalid, or some such rubbish. So back to combing the forums again. Had stumbled upon a post some where here, that said something about MNT/SDcard. And sure enough, I copied the recovery file from the MNT/SDcard directory, then pasted in the system/bin. Reboot again, reinstall packages and BAM Orange CWM! But before I flashed my first rom, i wanted to get the red CWM/voodoo recovery. That way I didnt have to worry about mounts while flashing. After much reading again in the forum, I found that the red CWM was already included with the Bali Kernal. Reboot again, then install from SDcard, choose Bali Kernal and installed. Woo Hoo red CWM was up and going. phew.... lol or so I thought. Plugged phone in and put CM6 - Merged on the SD. Back to recovery, wipe factory, wipe cache, wipe dalvik. Then install from SDcard again, chose CM-6 Merged.
This is where I had a bit of a panic. As I was not paying atternion the what Kernal or Baseband the rom was made to run with. So that ended up soft-bricking my phone. But yet again, XDA to the rescue. Searched it out and found the "ODIN to stock" thread. Just had to track down the right TAR and PIT files. I was orginally on KJ2 stock before I did anything, but I could only find the KD1 TAR. No biggie tho, just used the ODIN to stock method and I was back in business again.
Since I am far from having any real knowledge about roms and their internal workings and what-nots. I went about just trying to find roms that would run off of the Bali Kernal and the KD1 baseband. I did find working links to a few of them, not exactly sure how many, but I had serval choices. I went with GingerClone v.2.
Back to reboot, wipe factory, wipe cache, wipe dalvik. Install from SDcard, chose GingerClone and installed. Booted up and everyhting was all hunky dory again. Ran that rom for a few days. And yes it was a really nice rom, and it was faster than stock. It just was quicte what I was looking for.
Back to looking for ROM files, seeing which links were still good and trying to figure out which one I thought would work best for me. Tried TouchMIUIwiz v3, and again very good rom, but still not quite right. Decided to spend a whole day just comparing roms that would work with Bali and KD1. There are only a few roms that are made with KD1. So I wanted to go back to KJ2. I was thinking the only way I could do that was if I wiped again and the hooked up to Kios (or whatever it is called), But no, I found a working like to a KJ2 file. After another set of wiping in recovery, then Flashed the KJ2, then Flashed Nexus CM. Been messing with in for fwe days, and have to say I really really like this one. It has been smooth as glass and quick as a rabbit. I am thinking as long as I dont run into any major problems or bugs with it, this wil be my daily driver.
But I do have a question, since most of you have been here for awhile, and have been able to try out alot of these roms when they were new. Whick rom, in your own opinion, would make web surfing fast and smooth, and also works awesome with facebook? have already rooted and unlocked my husbands SK4G, but he surfs the web and does his facebooking from his SK, and it loves to freeze up and lag out when using both of those things.
Now that I am at the bottom with this, very sorry if my post seemed to long or anything else. Thanks in advance!
That's quite the story there. Crazy to believe it still works.
As for the ROM question, really all of the ROMS for SK4G are outdated. Due to software available. The only ROMS that I would say are up to snuff now are the neXus GB and JB ROMS by RicAndroid. They are chock full of tweaks and scripts. But keep in mind, you're not going to be on the actual newer Android versions. So it may run better, and it may be faster, but only so much.
Hope this helps
Zydrate_blue said:
That's quite the story there. Crazy to believe it still works.
As for the ROM question, really all of the ROMS for SK4G are outdated. Due to software available. The only ROMS that I would say are up to snuff now are the neXus GB and JB ROMS by RicAndroid. They are chock full of tweaks and scripts. But keep in mind, you're not going to be on the actual newer Android versions. So it may run better, and it may be faster, but only so much.
Hope this helps
Click to expand...
Click to collapse
I was pleasantly surprised when it turned out to be just a battery issue.
Thanks for the answer on the roms. I realized that these are older roms now, and its not the most crrrent version of android and all that, and I am totally fine with it. I am just looking for something that is better, smoother and faster than the stock stuff on the phone, for my husband. He still uses his SK4G as well. In fact I dont think I could get him to upgrade to a new smartphone phone/ android device anyways. So I was just looking for something to stop his constant frezzing issue while he is web surfing and things like that. You were very helpful tho, so thanks a bunch.
I agree with Zydrate_Blue; the Nexus JB ROM is about as good as it gets with this phone.
Thanks guys! I will have to d/l and flash it.
CupCakeBombardme said:
Thanks guys! I will have to d/l and flash it.
Click to expand...
Click to collapse
For a smoother internet interface. Get yourself NakedBrowser. They've got a free version that works just lovely. I haven't tried the paid version myself, but if may very well be worth it for someone who uses it a lot!

Bugie new phone

will it seems to be very buggy, first it thinks it is rooted i have been made aware of this because andriod pay wont work . but also its very laggie . app search bar crashes.pauses in screen swaps
you have already posted this
MJPUDS said:
will it seems to be very buggy, first it thinks it is rooted i have been made aware of this because andriod pay wont work . but also its very laggie . app search bar crashes.pauses in screen swaps
Click to expand...
Click to collapse
My thoughts, reflash anew, to start with a clean slate. My phone on Note 8+ ROM, works great. When I have gotten a bug, after some use and new apps, I typically have to go back to un-bugged backup, and better monitor what I put on the phone that causes/caused the bug issue. A little work at times, but worth it,
This phone, for me, is fast, smooth and powerful.
I'm wondering if the person you purchased it from, thought it was buggy for them, and could not figure out how to solve that, so sold it?

It is possible to unlock and root the H990N! :)

I am now running stock Android 8 with ezV2020 kernel for the DS version. Boot loader unlocked and Rooted.
As far as I can see, it is pretty stable. It was a long and tough process, but having already done the LG F800K it just took some hours to do the LG H990N and not days as the former did to break free.
So... just wanted to tell you guys, and let you know, it is possible. Both Sims are working, screen working, seems smooth and stable and all that.
Well, it was a lot of hoops, but I did think it might be possible - and it was and is.
Used my experience from the F800K on this little guy, and it seemed to have payed off, even if I had forgotten a lot of things or had to gather my thoughts on it.
But what a fight... But there you go.
Although it seems like it might be locked on the 4G, and I wanna have it run 3G as the radiation is much much much smaller compared to 4G. Like it is amazing to see the difference between the 2, one being nearly always in the Green by the testing instrument and the other nearly always in the Red. Just utter terrible. But I a have an app that should work that out, or maybe it just need a code and adjustment. dunno what they done to this. But should be workable. There was this code with putting the mobile number into it that got you into a menu... But I found an application for my new used LG mobile that could do the trick which name alludes me... but wait a minute and I will get it. That will most likely be my first try to fix the issue. 4G Switcher is the name of the app and it should be all clean and free!
Dearly regards
- Darkijah
Update... the good news first.
The H990N is running very smooth with the A8 Rooted with the DS kernel of ezV2020... The bad news... the Rotation and Camera does not work.
Not sure if this was something that happened after I installed Lineage 17.1 A10 and then stored it or if it was a problem before that. I just don't know. It looked like it did fine for me, and yet... apparently some issues. I tried to install a foreign kernel like I had done before, but TWRP would not flash it because the kernel file was foreign to the system. Which is odd as I flashed the mobile with the F800K kernel to get it working first hand, ezV2020 1.0 if I recall correct.
Maybe fastboot or something could installed it, adb whatever - still confused by it all...
Lineage by the way was somewhat horrible, and when I found out the sound from the Phone Jack was utter horrible I quickly turned around back to A8 stock. Although now witnessing these issues. I don't know if those issues where there before or not - or if it was something coming after the restoration from Lineage. A lot of factors can make issues.
But the mobile overall, works with network and it does run very smooth compared to my F800K, at least I seem to feel a difference here. One is slower to react, and the other is just butter smooth.
Not sure if I should toy more around with the stuff... I still have my new mobile incoming at some point when they change the broken screen. Getting a little sick and tired of the Android nonsense everywhere, which is literally is, everywhere. Issues, and looking for work arounds and what not, it is never ending.
Rooting should be as easy as pushing a button - and in my opinion should be default out of the box. No user should need to tinker and toy around with there expensive device to get things in order - the criminal companies purposely working against the users on so many levels. Highjacked the whole thing and filling it up with nonsense in the name of security or what not.
To early to say, but I might have found a fix. That took hours and hours... And still at it. But I have the Camera working and the rotation and it seems to still be running smooth. So... Hopefully no more issues, but I will further test it and try some things. It seems this issue is in all H990N20h stock Roms - I have one left to try out. I just tried a DS stock Rom and after installing the kernel and all, doing all the steps I am now into the system, need more testing if everything works, but... Well the Kernel ezV2020 is DS and now the system is DS, also known as Global if I recall. The TWRP is H990 another dual variant. There are absolutely some options to do, but they only allow 2 images being downloaded from the site and it takes a lot of time trying things out, installing it and making it work in the first place. Hours and hours wasted on this :/
But... just wanted to make an update for you guys Found a solution it seems - although there might come up new issues, usual do with Android, but hopefully it everything works!
You have to use the old version of TWRP to fix the lock issue if you get a screen like that. Very annoying, but the oldest version I have breaks it, and then you can install another higher version thereafter. Wipe out the data, and I have wiped out all else except system, not sure if it is needed overall... But in any case, that is my observations for now. I have used TWRP versions before 3.3.0 to unlock this locking issue.
Another issue is that if you go into the system it seems to delete TWRP, so... There are all these steps to do to make it work, *Sigh*.
H990N20f_00_OPEN_HK_DS_OP_1214 - camera and rotation not working.kdz
H990N20h_00_OPEN_HK_DS_OP_0225 - camera and rotation not working.kdz
H990ds20b_00_OPEN_AU_DS_OP_1108 - Newest DS version and working.kdz
H990N20d_00_OPEN_HK_DS_OP_0920 - Oldest H990N A8 but working.kdz
Here are my data so far.
I don't get it, Android is a madhouse. So after having tried things to get the Camera and the rotation to work in the stock A8, kernels and all... Then now installing the newest that did not work. Now it work all of the sudden. Makes zero sense and typical Android. I thought it might work and just for lunacy of it all I tried to install it to verify it still did not work - and now all of the sudden things that did not work, works even if I did the exact same things. It is an utter madhouse. And just typical Android...
After trying different kernels and what not... Downloading another version that did not work, downloading another and another variant of the DS... Then trying the DS that worked, then trying the oldest of the H990N working, and then trying the Newest of the H990N, and now working...
So once again I seemingly wasted hours and hours on something that now just works... Like this is something that happens all the time working with Android I have found out.
The only thing I can conclude by this, is that the installation of the DS in Partioning DL with boot and recovery unchecked, 4 unchecked in total. Must have done something to it, so it could apparently work for the other main images. At least, that's the best I can do, although I don't see why it would be related to fixing it, but it works now with the main and newest H990N image...
I wonder if my old backups would work with camera and rotation if I installed them... but... I'm not so sure I wanna try... But then again... If so, it would make zero sense. In any case I am now making a backup of the one I know 100% to work with camera and rotation H990N. Then I can always try to restore my old backups and see if the problem is there.
First older backup with the camera and rotation not working, restoring crashed the system now before being restored. *Sigh* Trying the first backup that also had the camera and rotation issue.
Well... At least I got it working, it seems. So, so far so good I guess...
My oldest backup got restored, and the Camera and rotation now works... Seems far out, but it is android so not a big surprize I guess. Faulty by design.
Anyway I will try to restore my second backup again and hope for the best... It must have been the H990DS Rom that fixed something while installing it, although have no idea why, and can make no sense of it.
Got my second backup up restored this time... The Camera and Rotation works... Like... I just don't know what could change here. But it started out working when I installed the H990ds stock so I guess it must have something to do with that, beside that I have no idea.
Seems the sickness went away from one mobile and planted itself on the other... I feel more and more that Satans minions are doing these things... Whatever the case, now my daily working mobile is having Camera problems all of the sudden... This is insane, 2 mobiles which should have nothing to do with each other, one mobile having a camera issue, and solving itself all of the sudden, and now the other mobile is infected... Like, just, just give me a break...
You gotta be kidding me, it now also have the turn issue!... This is utter insanity... Like seriously.... *Sigh* What is going on here.
Thinking seriously that a hammer can fix everything!
I downloaded US996 now that US996 is used so much for the F800 mobiles variants, well my F800K did absolutely not like that, I tried it twice and got nothing. It changes partitions apparently - It never loaded up in the system at all.
Anyway, so knowing that the H990DS stock seemed to have fixed the screen issue and rotation issue on my H990N version, I installed that on the F800K and the system worked, and with camera and rotation, although you need a lower version of TWRP to get through the security nonsense as seems to be standard. Well, the H990DS version worked on the F800K and I wonder if it might be a better choice overall to use for it. But it did look pretty good and no Korean nonsense text. Well... I am now restoring my backup of my former system with the sickness that I made before all this, and see if it has fixed it like it did with my H990N. Need to restore +50 GB because of TWRP programming nonsense and then we will see if the Camera and rotation has sorted itself out.
Interesting if it fixes both variant phones... And maybe then it might be better just to use that version on both phones, not sure...
If it sorts it out at least, I think we have a good indication that the DS version H990ds20b_00_OPEN_AU_DS_OP_1108 is a cure for this sickness, it seems.
The F800K seemed to become more sick and skype did not work and it was terrible slow to respond :/ And then of cause the camera and the rotation did not work either. Not sure what is up with that sadly. Not sure what the overall issue is. Maybe I need to keep to the older versions of TWRP or... Dunno...
But I might try the DS version on both systems, if it fixes the 2 main issues, it might not ever come on it. Maybe... Or maybe it just fixes it overall after having been installed, no idea.
I wonder if twrp-3.2.3-0-h990 might also be used on the F800K - if the US996 is not so compatible with the phone, maybe the TWRP is not so compatible either... And the H990 should be close to the DS and H990N version as far as I know...
Restoration failed.... ohh no.... hmmm - might be that the H990DS is different in regards of partitions I wonder...
I will try again and if it fails again, I will install the right stock image and see if it wanna change some partitions and thereby show if there is anything different which might break the beta full partitioning backup. The foolish nonsense of backing up a lot of empty space. Utter insane, but overall Android is insanity.
I feel that the TWRP programmers are lead by Satan, some of these choices that is found is just outrageous. But if you wipe out the competition you can rule over it all, the same with Magisk if there is no competition then it is easy for them to stir the boat. If programs takes the lead and crush everybody else, then they can begin to play tyrants and promote insanity.
Anyway, most likely will get another fail with the backup, partitioning being different in size or something. As TWRP forces this bull**** on the users, and many other things. But can't complain about it, then the blotting pen comes by here on the forum. Censorship, as always, nothing new these Satanic days of hating Truth.
Anyway, I will fix the F800K image and then restore things, that should do it. Then again, it might be better to jump on that DS image overall... *Sigh*
And see if I can get my data with me... Usually also makes issues, because programmers makes it near impossible for users to easily do what they wanna do.
We can't have to much freedom you see...
58 GB's... insanity and waste of time. Programmers love to put that bull**** on us, Android is faulty by design and the programmers outrageous following blindly along pushing more garbage - oh how I wish the Linux Pine or Librem phones had been closer to running as a daily. I would not be on this Android jail bull****, and insanity land of wasting my time with things which should have taken 1 second to fix without breaking anything and yet ends up taking months. Sick sick sick.
Android seem nothing related to Linux, no freedom, no nothing. Just Tyrant companies and programmers, ads all over and other filth. Well the progress is 42 GB and going, getting close to the breaking point I guess.
XDA is full of ads as well, same as all the website with any android stuff - ugly and disgusting filth. Because no website can be run without any ads, apparently...
Yup the restoration failed... but if the partitioning is different then it is no surprise when TWRP programmers program like drunkards full of demons.
Hopefully will soon have figure this out so I can wipe out windows 10 and get on linux... but using LGUP which is running on windows. Don't think there is a Linux version as far as I know. Okay system installed, although it did not give me any warnings of changing the partitioning... I wonder... If it will now restore my backup and if not... then I am in trouble. As this was my main phone... I should have copied everything from the internal to the Micro SD card before doing this.
Should have taken my precautions as Android never seem to do what is expected of it. Always new wacky loony things incoming from all sides. A backup should work but don't expect it too.... Because, Bull****.
Insanity: doing the same thing over and over again and expecting different results. Albert Einstein
I guess he never tried Android...
The error restoration in TWRP could also be related to the version of TWRP, dunno I might have used the old version. Can't remember, but have to take that into consideration as well... As it did not seem to do anything with any partitioning when I ran the H990N stock image.
In any case the H990N stock image is loaded this time - I will restore it with the old TWRP, and if that fails again try a newer version of TWRP and redo it again again again...
So many factors play in, and downgrading for this and upgrading for that. Because... that's Android.
Well, it restored it although with some errors, but not the overall error. Something about some folders it could not enter, which I have seen before. I don't think it is a problem but... I will just test out the Camera and rotation and then go back and restore it with the newest version of TWRP that I have working and see if I get the same issues. The BIG moment... Have it worked? Rotation works... next... Camera works!
Whatever seems to be the issue the H990ds20b_00_OPEN_AU_DS_OP_1108.kdz takes care of it and one can just return to the former stock version or restore the backup.
And I do wonder if I should just install the H990ds20b version on both mobiles really... Seems to be able to run on both variants of the LG that I have.

Categories

Resources