Set up phone without encryption? - HTC One A9

Got my 32gb unlocked A9 a few days ago. Wondering, without modifying anything (unlocking bootloader, custom recovery, rooting, ect) is it possible to run this phone without encryption? My 3rd Gen Moto G feels faster than this. I find the general lag, and sometimes even freezing, a nuisance (especially during read/write), and have no need for the encryption. Is there an option somewhere to disable it? Maybe some different steps during factory setup (i.e. opting out of pin/fingerprint)? I'd like to have the phone decrypted, but would still like to use the fingerprint to wake/unlock the phone.
My phone is on the latest firmware, and I've already tried a factory reset, this is why I'm assuming the performance hit is the encryption.
Example of one of the stutters I notice is going between the home screen and the recents screen. Anyone else get this? Maybe something got screwy during the 20 (/s) firmware updates when I got it?
Edit: Also thought I'd mention that I'm also getting random reboots.

rouyal said:
Got my 32gb unlocked A9 a few days ago. Wondering, without modifying anything (unlocking bootloader, custom recovery, rooting, ect) is it possible to run this phone without encryption? My 3rd Gen Moto G feels faster than this. I find the general lag, and sometimes even freezing, a nuisance (especially during read/write), and have no need for the encryption. Is there an option somewhere to disable it? Maybe some different steps during factory setup (i.e. opting out of pin/fingerprint)? I'd like to have the phone decrypted, but would still like to use the fingerprint to wake/unlock the phone.
My phone is on the latest firmware, and I've already tried a factory reset, this is why I'm assuming the performance hit is the encryption.
Example of one of the stutters I notice is going between the home screen and the recents screen. Anyone else get this? Maybe something got screwy during the 20 (/s) firmware updates when I got it?
Edit: Also thought I'd mention that I'm also getting random reboots.
Click to expand...
Click to collapse
AFAIK it is not possible without TWRP. I have reflashed the whole system and tried if it stays decrypted without setting up fingerprint, but it does not.
I have had some lags as you described, it got better with usage, there are some micro lags, but I got used to it. It is smooth in general. I have also had one reboot in the first few days, but not ever since. Give it a little time.
Sent from my HTC One A9 using XDA Free mobile app

I downloaded the 1.7gb file from HTC and used that to reflash(?) the phone. I can tell some things are different in the UI than when it went through the chain of updates, and seems faster too. Might be placebo. I'm still waiting to see if I get a reboot. Reboots were happening about every 12 hrs.

rouyal said:
I downloaded the 1.7gb file from HTC and used that to reflash(?) the phone. I can tell some things are different in the UI than when it went through the chain of updates, and seems faster too. Might be placebo. I'm still waiting to see if I get a reboot. Reboots were happening about every 12 hrs.
Click to expand...
Click to collapse
Yeah, I did the same too. I felt the phone became more laggy, after updating OTA, so I thought reinstalling the latest firmware might be the best idea. I'm not saying it is perfect, as it is not, multitasking can be really sh*tty sometimes (I have the 2Gb version though), but it is usable, and generally fast and smooth.

Related

[Q] what is the lag thats getting fixed

So total noob question. What exactly is the lag thats being fixed? Is there a specific lag or is it more of a general slowness of the phone?
Thanks!!
Some apps open slow. Some people notice lag in booting the phone. Mainly overall feel i guess. Like you said.
docflower said:
So total noob question. What exactly is the lag thats being fixed? Is there a specific lag or is it more of a general slowness of the phone?
Thanks!!
Click to expand...
Click to collapse
The lag that is being referred to is a lag caused by samsung's property rfs file system that samsung put on this phone. As far as I can tell there is a flaw in data write where the rfs file system can pause for as much as second - and when you get multiple process waiting in line to write data it causes a very noticeable lag in the phone as it will come to almost a standstill.
If you don't nice anything don;t worry about it....LOL
I see more issues caused by lag fixing than those who don't bother with them...especially when loading new ROMS A slight hesitation now and then doesn't bother me.....Perfection is not the goal.
I've found I don't need a lagfix for Cog's 2.2 beta 5.6.
I get a hiccup every once in a while but otherwise everything seems to run fine. And it's still a billion times faster than my old iPhone so I'm happy either way. (I had to wait to do EVERYTHING on that POS)
http://capfaq.com/w/Lagfix
dayv said:
The lag that is being referred to is a lag caused by samsung's property rfs file system that samsung put on this phone. As far as I can tell there is a flaw in data write where the rfs file system can pause for as much as second - and when you get multiple process waiting in line to write data it causes a very noticeable lag in the phone as it will come to almost a standstill.
Click to expand...
Click to collapse
Exactly how do this happen ? Can this be replicated on this phone so everyone can see it ? I have seen and experienced wake up lag on Androids that have non stock roms..and also the damnable phone dialer lag as well with my Hero..but have yet had this problem with my Captivate....So.. what does one have to do to see it on the Captivate? Your saying the file system that is causing this correct...I don't believe it is the same thing other Android phones are experiencing and what has been called LAG to honest with you..if it were then everyone that had this phone would be complaining about it. Sometimes I had to swipe 4 or 5 times to unlock my Hero..or having tried to dial a number only to have 5 or 6 extra numbers punched in because of the LAG..
I think what you seeing and what is being described here as LAG isn't really the LAG of most Android based phones are having..What I think is being described is just a slight hesitation of certain applications being opened and closed..This is normal for any computer depending on what and how large the program is.The file system used with these may indeed cause this but it is nothing as compared to a phone that really Lags. Boot lag is something entirely different..and as far as I can tell can be caused by what is loaded on the phone and not really the phone itself, unless the phone isn't really wiping any residual data before applying a new rom and thus causing conflicts on booting.
If this wasn't the case..then every Galaxy phone would do this..complete stock or one that has been customized. I may be totally wrong..but I don't think I am..
Mac
The problem isn't on other Android phones because other Android phones don't use RFS. RFS is a Samsung thing.
And just about every person does complain about the lag... how severe it is depends on how heavy of a user you are so a few uber-light users might not notice it so much.
Me? I notice things like occasionally 10-30 seconds after returning to my home screen for my icons to appear, hesitation in keyboard entry causing massive typos and repeated keypresses, unresponsiveness of home keys only to have it suddenly register all queued presses, etc.
I acknowledge the problem but unfortunately a lot of the "lag fix" hacks cause more harm than good.
Mac11700 said:
Exactly how do this happen ? Can this be replicated on this phone so everyone can see it ? I have seen and experienced wake up lag on Androids that have non stock roms..and also the damnable phone dialer lag as well with my Hero..but have yet had this problem with my Captivate....So.. what does one have to do to see it on the Captivate? Your saying the file system that is causing this correct...I don't believe it is the same thing other Android phones are experiencing and what has been called LAG to honest with you..if it were then everyone that had this phone would be complaining about it. Sometimes I had to swipe 4 or 5 times to unlock my Hero..or having tried to dial a number only to have 5 or 6 extra numbers punched in because of the LAG..
I think what you seeing and what is being described here as LAG isn't really the LAG of most Android based phones are having..What I think is being described is just a slight hesitation of certain applications being opened and closed..This is normal for any computer depending on what and how large the program is.The file system used with these may indeed cause this but it is nothing as compared to a phone that really Lags. Boot lag is something entirely different..and as far as I can tell can be caused by what is loaded on the phone and not really the phone itself, unless the phone isn't really wiping any residual data before applying a new rom and thus causing conflicts on booting.
If this wasn't the case..then every Galaxy phone would do this..complete stock or one that has been customized. I may be totally wrong..but I don't think I am..
Mac
Click to expand...
Click to collapse
I did not say that I ever saw this lag myself - I was just answering the question as to what was being fixed in the lag fixes - and the rfs file system hang that happens at the sync on close at the end of a write is what these guys are attempting to address with these lag fixes.
I am not even using a lagfix as the current custom rom I am running is running just fine without one.
Here this thread gives more in depth description and explanation of the rfs lag
http://forum.xda-developers.com/showthread.php?t=799931
i feel the lag is caused by touchwiz and exaggerated by the file system. i never noticed a complete lack of lag with a lagfix. things got slightly less choppy but i think there is a big placebo effect around here. in eclair my phone was still laggy with any and all lagfix's that i tried including voodoo.
the leaked froyo doesn't lag too much but doesn't update the wallpaper on wakeup if you are running live walpapers so you get a black background ocasionally. applying the z4mod lagfix to froyo makes a difference in bootup and wakeup but is not totally necessary. actually there is a big potential for problems and forgetting to remove a lagfix before flashing will turn into a headache really fast.
The video in the below thread gives a clear enough demonstration of the effect. A lag in opening emails, or marking email unread, that is at least around 2 seconds every time and 5 seconds at one point. After a lagfix is installed, it consistently takes well under one second to perform the same operations.
As I understand it, lagfixes either re-partition the file system entirely with a new file system, or create a large cache so that data can be accessed quickly without as much interaction with the filesystem.
http://forum.xda-developers.com/showthread.php?p=8638406#post8638406
TheYar said:
The video in the below thread gives a clear enough demonstration of the effect. A lag in opening emails, or marking email unread, that is at least around 2 seconds every time and 5 seconds at one point. After a lagfix is installed, it consistently takes well under one second to perform the same operations.
As I understand it, lagfixes either re-partition the file system entirely with a new file system, or create a large cache so that data can be accessed quickly without as much interaction with the filesystem.
http://forum.xda-developers.com/showthread.php?p=8638406#post8638406
Click to expand...
Click to collapse
While the video does indeed show lag in opening everything with that custom rom..where is the video showing the same issue with that phone prior to any modifications using the stock rom..? I'm not talking about one that has been rooted and re flashed..I am talking about one straight out of the box... If it took that long just to boot up with cog..then there really is something wrong. From a dead stop with the battery out to being fully up and running..takes less than 45 seconds with mine running staright from the box stock. Either I don't understand everything( big possibility) or something is either wrong with that phone with that rom installed on it.
I'm not trying to say this isn't Lag on the video..it clearly shows it..but I do question why a fair comparison isn't being shown..As much as I hate to say it..it looks like the biggest amount of issues I have seen here is from folks who have rooted and flashed new roms. BTW..my email opens as fast as the fixed one does as well. I am sure someone does have these issues (perhaps not to this degree) on a unaltered phone..but I also think it is exactly what I said earlier too..that some of it is normal..but some want everything instantaneously...and I don't believe that will happen for sometime.
I do understand what folks do here and why..I'm not totally dumb when it comes to rooting and flashing...but to me and the way I am seeing it..something somewhere isn't being taken into account here with how this rom is acting. I know a lot went into developing it..but..in all honesty to my eyes it looks like it isn't fully optimized yet,even with what has been done with it so-far.Of course I have absolutely no way of knowing what that phone did when it was totally stock either...but with out a true side bt side comparison video of the same phone..nor will anyone else. Also..I don't blame folks who want something different..Hell..if folks didn't try to make changes..nothing new would ever get developed,but sometimes trying to fix something that works fine,is cutting off your nose to spite your face too..
To me..instead of trying to replace the file system with something different..why not try to make a rom using it..? The phones are spec'd to use it..so use it..optimize it..and see if most all of these "issues" go away..Maybe easier said than done..I don't know..but that's how I look at it.
Mac
The stock email is not the one shown in the video, it is touchdown which many use to sync their corporate email accounts as the stock program is inadequate or not compatible.
If you have not noticed the lag then you don't need a lagfix. Data intensive operations do exploit the flaws in the rfs system however and many experience better performance after installing one.
As for startup time, lagfix really has nothing to do with this. Regardless of setup, the phone will boot only slightly faster with one.
Sent telepathically using vulcan mind meld app.
For what its worth. I remember showing my coworker my lagfixed 2.1 and we compared to his stock, and did a side by side on browser, email and a couple of other apps. It was a big enough impression that he immediately installed oclf.
Sent from my SAMSUNG-SGH-I897 using XDA App
govgeek said:
For what its worth. I remember showing my coworker my lagfixed 2.1 and we compared to his stock, and did a side by side on browser, email and a couple of other apps. It was a big enough impression that he immediately installed oclf.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Well..that make me wonder if all of these issues are a QC issue from Samsung..I do know I had to go through 7 different phones(all new not refurbs) for the wife last week we we signed up wit AT&T...
I guess I'll wait till the official non beta release of 2.2 is out before I start changing mine.This will give me a better understanding on how everything is right now..as opposed to flashing a different rom,and see if the phone starts acting up.
Thanks
Mac
Mac11700 said:
As much as I hate to say it..it looks like the biggest amount of issues I have seen here is from folks who have rooted and flashed new roms.
Click to expand...
Click to collapse
While I am rooted now (reluctantly, due to some things that I need to run that require it), my lag predates that as I only rooted recently. Lag of 10 seconds at a time is not uncommon... whether it's a freeze while using the keyboard, trying to pull down the notification bar, trying to switch apps, trying to use the "Home" key, or waiting for the home screen icons to re-appear. I've counted delays as long as 30 seconds at times.
If lagfixes weren't so dirty and unsafe, I'd be their biggest proponent.

Shutdowns since KitKat

Unrooted, locked RAZR Maxx HD. The only thing not entirely typical about my phone is that I'm in Germany at present, running it on a no -Verizon SIM. Since I updated, I seem to be getting restarts every day or two. Screen blacks out and the phone is unresponsive for a minute or two, then it fires up again. Doesn't quite act like a complete reboot, since I don't get the "Unlock PIN" screen that I do when I boot. But I get the message that the PIN is from an unknown source, and then it works fine. At first I thought that maybe the trouble was from Greenify, which I installed shortly after the update, but uninstalling it didn't help. Any thoughts?
Did you did a Factory Data Reset (FDR)? I know they are a pain since it wipes everything out, but it definitely cures a lot of ills after a major OTA like this one. I'm not saying it cures all issues, but it definitely cures a lot of issues like what you have described.
iBolski said:
Did you did a Factory Data Reset (FDR)? I know they are a pain since it wipes everything out, but it definitely cures a lot of ills after a major OTA like this one. I'm not saying it cures all issues, but it definitely cures a lot of issues like what you have described.
Click to expand...
Click to collapse
Yeah, I was afraid that would be the response. Not afraid in that I don't think it might be right; was just hoping for something easier. That's more than I can take on here; I'll be back in the States for a week next week and might have time for it then. So obviously the answer is no; I cleared the cache, but that's it.
dimdem said:
Yeah, I was afraid that would be the response. Not afraid in that I don't think it might be right; was just hoping for something easier. That's more than I can take on here; I'll be back in the States for a week next week and might have time for it then. So obviously the answer is no; I cleared the cache, but that's it.
Click to expand...
Click to collapse
Yeah, I know. A lot of people hate to hear it, but considering we went from JB to KitKat, that's a pretty big architectural jump. Usually, when things like this happen (GB to ICS, ICS to JB, and now JB to KK), it usually is best to wipe your phone clean and start over from scratch. Definitely resolves a lot of issues like this.
Now, the only other thing I can think of is your SIM card. Since it's non-Verizon, I don't know if that could be the issue. It could be the SIM is bad. You never know.
It will be interesting to see if a return to the states and using a Verizon SIM cures your ills? If so, then I definitely point it to the SIM card and then possibly, a FDR isn't needed.
Hello All,
Does the Factory Data Reset remove all installed apps from phone?
Regards
Rafal
rafjak said:
Hello All,
Does the Factory Data Reset remove all installed apps from phone?
Regards
Rafal
Click to expand...
Click to collapse
Yes. It wipes all installed apps as well as settings, contacts, text messages, etc. It effectively resets the phone back to factory defaults (no Google accounts registered, all email accounts removed, contacts, text messages, etc).
Now, if you've modified it (removed system apps), it will NOT restore those. It can only reset/wipe settings as well as messages, emails, etc, installed apps.
Does Fatory Reset help anybody for constantly rebooting?
Regards
Rafal
dimdem said:
Unrooted, locked RAZR Maxx HD. The only thing not entirely typical about my phone is that I'm in Germany at present, running it on a no -Verizon SIM. Since I updated, I seem to be getting restarts every day or two. Screen blacks out and the phone is unresponsive for a minute or two, then it fires up again. Doesn't quite act like a complete reboot, since I don't get the "Unlock PIN" screen that I do when I boot. But I get the message that the PIN is from an unknown source, and then it works fine. At first I thought that maybe the trouble was from Greenify, which I installed shortly after the update, but uninstalling it didn't help. Any thoughts?
Click to expand...
Click to collapse
I'm getting this in the UK. It is apparently a problem with the Fast Dormancy Monitor on European GSM networks, after the 4.4.2 update
According to a Motorola forum, they are aware of the problem.
Unfortunately the only possible fix I have seen involves rooting the phone then editing the build props file to disable the fast dormancy monitor process
I guess a question many would have here is why arent you rooted and unlocked.......
droidrazr7 said:
I'm getting this in the UK. It is apparently a problem with the Fast Dormancy Monitor on European GSM networks, after the 4.4.2 update
According to a Motorola forum, they are aware of the problem.
Unfortunately the only possible fix I have seen involves rooting the phone then editing the build props file to disable the fast dormancy monitor process
Click to expand...
Click to collapse
Interesting. I came back to report that the problem cleared up once I was back in the U.S. I guess this explains why.
Possibly this:
https://forums.motorola.com/posts/9573b20d40?page=5
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
cmh714 said:
I guess a question many would have here is why arent you rooted and unlocked.......
Click to expand...
Click to collapse
Well, I am now. The last time that I had checked, it hadn't been possible, and I hadn't followed the more recent surprise developments. Now that I've done it I don't plan to take advantage of it, since the phone works fine for me as it, but it's good to have the security for down the road. But thanks for alerting me to the possibility.

[Q] Cyanogenmod 11-M9 crashy as hell on Hammerhead?

Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
starslab said:
Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
Click to expand...
Click to collapse
Try without encryption. It's hardly useful and only causes issues on Android.
Lethargy said:
Try without encryption. It's hardly useful and only causes issues on Android.
Click to expand...
Click to collapse
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
starslab said:
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
Click to expand...
Click to collapse
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Lethargy said:
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Click to expand...
Click to collapse
CyanogenMod has Privacy Guard, which is another feature I'm using, mostly with the aforementioned WhatsApp!, which has a list of permissions longer than my arm. I don't like it, but I need it for work.
I'll grant that the custom Recovery and ROM may slightly weaken the encryption (specifically an attacker could alter the ROM from Recovery), but even so having the encryption makes the phone a million times more resistant to data theft and tampering than not having it. It's worth noting that tweaking the ROM is the _worst_ an attacker could do. If I suspected such a thing had happened I could re-unlock the bootloader (which would wipe my data), and re-flash a known good Recovery and ROM. I'd lose my data, but even if the attacker had dumped the partition they still wouldn't have my key, and my data would still be private.
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
its more then likely the encryption. Disable it, re-flash and see what happens
No encryption. Wiped and trimmed the phone yesterday, now 4 crashes.
Try another ROM, see if it crashes. If it still does, flash factory images and see if it still does.
If so, RMA.
Nothing but trouble for me since upgrading to m9. I have been using the various M builds since March with no problems. M8 was fine. No device encryption for me. I tried turning it on and instead got stuck redoing the whole phone.
Now I get frequent crashing. I switched to the most recent nightly yesterday. Apps stopped crashing. However the os itself still crashes. Several times the screen wouldn't turn on after removing it from my pocket. The light was blinking so it definitely didn't just turn off. It also has stayed black after a few (but not all) phone calls. I've had to hard reset every time to recover.
Thinking about reverting to m8 backup. Willing to give it a few more nightie and see if it works out.
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Got it from the OTA update. Unfortunately I'm not experienced enough to know how to debug it or use proper logs. It could be that its an app I'm using combined with the most recent update...
Im using M9 snapshot too and i have not had 1 problem its been excellent
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
+1. I installed another kernel (Chaos) for that reason and it's way faster.
OP: Maybe a bad flash? I would download M8 latest stable snapshot, and do OTA upgrade to M9. That's how I got mine.
C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
Thanks for the suggestion. I actually have been using elemental and forgot to install it after the OTA. Will put that on now and see if it helps.
starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
simms22 said:
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
Click to expand...
Click to collapse
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Sent from Tapatalk on Nexus 5
last four hours have been fine since adding elemental. Hopefully works in the long run. 8/18 nightly.
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Click to expand...
Click to collapse
What roms do you think are more stable than CM at this time?
trobbs said:
What roms do you think are more stable than CM at this time?
Click to expand...
Click to collapse
Just about any

Major OS/touch screen freezing - Unroot, return device, etc.?

Got a new OP7 Pro. Nice hardware for sure. I unlocked boot loader, installed TWRP recovery, Magisk, but using standard factory ROM/kernel (OOS 9.5.8). I am experiencing severe screen freeze issues. It is like all touch inputs are ignored or screen is frozen for up to 10 seconds at a time. The phone is pretty well unusable as this gets in to a loop of unfreezing perhaps for a few seconds or a minute but then right back to frozen. Crazy...
Some times I can go an hour or so with out it happening but once it sets in it seems to recur frequently . Rebooting helps as does wiping dalvik/cache, but it always seems to come back. Does not appear to happen when booting to safe mode, which leads me to believe it is an incompatible app but the app would have to be doing some crazy stuff to screw up the entire phone/screen/touch input this much. Just can't find the trigger or a fix.
I've got many options. All my (relatively Android noob) buddies (some are very good programmers though) insist I should unroot and remove TWRP and get back completely to stock. I could try those sequentially. I can also return the phone and replace it since it is brand new. Oneplus suggested this rather than providing any help or real tech support.
I've googled around a lot and have found some (appears to be infrequent) folks who ocassionally loose touch access in a corner of the OP7 Pro screen. Neither this nor the "ghost touch" are the same as my issue.
Hoping to get some good advice here from some Android gurus. Thanks in advance.
Bump, no one??
swamp2 said:
Bump, no one??
Click to expand...
Click to collapse
Update the firmware.
dynospectrum said:
Update the firmware.
Click to expand...
Click to collapse
Thanks, but just random tech support advice? Or do you have a reason to believe there is something particularly relevant in the 9.5.10 release?
9.5.7 or 9.5.8 had random screen touch issues Anna .10 hot fixes more bugs that they introduced to .9
If I were you, I'd update and get on the current firmware. I'd also backup all your data on the phone and do a factory reset after the updated then if it still is having issues return it for hardware defect. It makes no difference to do this as you have to perform the data wipe before returning it anyway.
Eric214 said:
9.5.7 or 9.5.8 had random screen touch issues Anna .10 hot fixes more bugs that they introduced to .9
If I were you, I'd update and get on the current firmware. I'd also backup all your data on the phone and do a factory reset after the updated then if it still is having issues return it for hardware defect. It makes no difference to do this as you have to perform the data wipe before returning it anyway.
Click to expand...
Click to collapse
Thanks, things are looking free of this issue so far on .10!
Issue is back, greatly improved but back. This phone is driving me nuts. Must be incompatible with some app...
Removed root, removed twrp, locked boot loader and clean flashed 9.5.10. Screen freezing completely gone for around 24 hours. Also have only installed essential apps. Sure would like both TWRP and Magisk back, but undecided. I seem to be the only person with this particular problem... Additional advice appreciated.
I'm getting the same problem even on .10 version.
I had to unroot and lock the bootloader again.
I thought I'm the only one who is facing this issue.
Any more updates on this? Was it an app causing it?
I have OnePlus 7 Pro for a few weeks already, but I started use 7 Pro as my primary device from last weekend and since that time I have experienced the identical problem.
Renovate ROM, stock kernel, xposed
shank19 said:
I'm getting the same problem even on .10 version.
I had to unroot and lock the bootloader again.
I thought I'm the only one who is facing this issue.
Click to expand...
Click to collapse
Wow, I'm not alone! Can't decide if I want to do a warranty return and try an entirely new phone. We just can't be the only folks with TWRP and Magisk on this device. It seems like a software problem but odd that more are not experiencing. I'm hesitant to even try Magisk for fear of a long difficult full wipe without a good TWRP backup.
Edit: I should have done better testing but pretty sure unroot by full Magisk removal did not fix the issue.
Honestly if it's not a hardware defect the one thing I think that it could be is accidental touches. Are you using a case on your phone? Does it get any better if you lay your phone flat and only touch the screen with your finger?
When I first got my s9+ which was my first curved screen phone I had this same issue and thought it was hardware related, but when put a case on it the issue completely stopped and I realized I had been touching the curved screen with my palm while holding the phone.
I don't really see how unlocking the bootloader, magisk, or twrp could be responsible as I haven't had any issues with any of them, but you could try custom kernels or roms if you want to try everything before you return the phone, but I think that would be really grasping as straws.
It could be a Magisk module as I've had issues where installing and deleting the modules cause me to have random reboots even with all the modules uninstalled, id try wiping data, and flashing fresh oos 9.5.10 to both slots.
I just uploaded a video of that issue, sorry for the quality (Xiaomi Mi A2 Lite).
Weird issue. Glad I'm not seeing it on my International 9.5.19.
This is definitely not an issue you're going to resolve by just installing a few apps and waiting to see if they affect the performance. I am interested to see what the logcats (actually, logs in general) say at the moment the phone freezes. If anyone can provide these it would be a great insight for sure.
Unroot, lock bootloader, wipe, factory 9.5.10, problem completely gone. Good and bad, prefer root...
I've only encountered this issue while using Facebook messenger.
I tried to deactivate xposed and magisk modules but the problem persisted - it seems it just started to appear less frequently but not fixed.
I am on the Havoc ROM for more than two days and touch screen issue is gone.
Chrono Leggionaire said:
I tried to deactivate xposed and magisk modules but the problem persisted - it seems it just started to appear less frequently but not fixed.
I am on the Havoc ROM for more than two days and touch screen issue is gone.
Click to expand...
Click to collapse
Strange, one common denominator is an unlocked bootloader. Do you also have TWRP?

Lenovo TB-X705f P10 tablet random crashes lockups

As the title says, There is no rhyme or reason. open an app crash to home screen. try again tablet reboots. Works fine for days then constant reboots and crashes. Love the tablet but when major apps like facebook. twitter, youtube, just starts crashing and rebooting the tablet something must be wrong. I did just reset the Cache and will see if that helps. I was thinking about rooting and looking for a custom rom. Found the guide for rooting but am not sure if there is a custom rom for this yet.
Anyone else with this tablet experiencing this? I still have a month and a half left on warranty service. Should I attempt to try and get Lenovo to authorize a send to repair or is it not worth the hassle?
Thanks in advance for any help.
You are not the only one as I have the same tablet and therefore have the same problems. It seems like Lenovo is done supporting this hardware. The only way to get around these problems is to install custom firmware.
[GUIDE] Unlock/Root Lenovo Smart Tab P10 (TB-X705F) by Chaser42
This guide will show you how to unlock the bootloader and root Android 9.0 (Pie) with Magisk on the Lenovo Smart Tab P10 (TB-X705F). This guide is written for Lenovo Smart Tab P10 (TB-X705F). However, it can also be used for the Smart Tab P10...
forum.xda-developers.com
Teutonicc said:
As the title says, There is no rhyme or reason. open an app crash to home screen. try again tablet reboots. Works fine for days then constant reboots and crashes. Love the tablet but when major apps like facebook. twitter, youtube, just starts crashing and rebooting the tablet something must be wrong. I did just reset the Cache and will see if that helps. I was thinking about rooting and looking for a custom rom. Found the guide for rooting but am not sure if there is a custom rom for this yet.
Anyone else with this tablet experiencing this? I still have a month and a half left on warranty service. Should I attempt to try and get Lenovo to authorize a send to repair or is it not worth the hassle?
Thanks in advance for any help.
Click to expand...
Click to collapse
I have exactly the same problem, although for me it never really works fine for days, at most it last for one hour, then it just crashes for no reason or patron and it makes a sound (it is not a sound of a normal restart, not digital, but it sounds like disconecting a computer from the power supply, like a hardware matter) anyway, did it work for you? I still have one month on warranty service, but It was bought in Finland and now I am currently in Peru, I fear that I wont be able to fulfill my warranty rights.
I will try the solution our friend Bwildered01 suggest us. Good luck and thank you so much!
I just stumbled across this thread...
I have had two of these tablets since 2019 and for the most part they've been great. I use them a LOT and I would say 90% of the time they behave. Sure, every now and again something wonky happens and I have to reboot. However, I think that's true of every computer type device I've ever used.
I don't know if it's a Lenovo thing or a Android Pie thing, but sometimes memory management ****s the bed. Chrome and a few other background processes will slow it down to a crawl. I use a system monitor when this happens and I kill greedy apps that are eating up resources even though I thought I had closed them. That seems to make the tablet happy again.
Are you guys using the latest firmware? Right now you should be at Android 9 with the most recent OTA update from November. The current version is: TB-X705F_S210164_201119_R0W
Chaser
Chaser42 said:
I just stumbled across this thread...
I have had two of these tablets since 2019 and for the most part they've been great. I use them a LOT and I would say 90% of the time they behave. Sure, every now and again something wonky happens and I have to reboot. However, I think that's true of every computer type device I've ever used.
I don't know if it's a Lenovo thing or a Android Pie thing, but sometimes memory management ****s the bed. Chrome and a few other background processes will slow it down to a crawl. I use a system monitor when this happens and I kill greedy apps that are eating up resources even though I thought I had closed them. That seems to make the tablet happy again.
Are you guys using the latest firmware? Right now you should be at Android 9 with the most recent OTA update from November. The current version is: TB-X705F_S210164_201119_R0W
Chaser
Click to expand...
Click to collapse
Latest firmware. used the lenovo diagnosing prorgram. factory reset. reset cache. still just random reboots. When it is running it is a very good tablet.

Categories

Resources