Hello all,
Last week, I broke my oneplus one's screen so I decided to try and revive an old oneplus X.
A month ago, this device was still running the latest available OxygenOS but I played around with the device at the time and decided to install Lineage 14.1. I used the following versions of TWRP and LineageOS:
- LineageOS-14.1 20181110-nightly-onyx-signed (was no longer available on the official LineageOS site)
- TWRP version 3.3.1-0-onyx
After installing LineageOS 14.1, I noticed that there were some glitches when using the phone and the UI would lagg very hard sometimes. Since my Oneplus One was still working fine at the time, I decided to not troubleshoot this any further and put the device away.
Unfortunately, last week I dropped my Oneplus One and broke its screen, so I immediately tried to fix the Oneplus X again. I figured this might have been an issue with the LineageOS 14.1 ROM so I browsed this forum for an android 9 build and found the builds by YumeMichi and by psychem.
First, I booted into TWRP and performed an advanced wipe with every option selected.
Then, I installed Yume's build using the latest version of the ROM and Yume's version of TWRP: "twrp-3.2.3-20190127-onyx".
This booted fine and looked very promising at first, however the glitching/lagging returned after a few hours of use.
Then I cleared everything again and tried psychem's version (11.08.2019 build, without MicroG). I did not change the TWRP version (still using Yume's TWRP). This would not boot but I solved that by flashing Yume's build again and then dirty flashing psychem's build on top of it. That worked fine, untill after a few hours, the lagging and glitching returned.
The past week I've been playing with the power settings and trying to find someone with a similar issue on google. No luck, unfortunately.
The, on 22/08, I noticed psychem released a new build (22.08.2019). I installed that one and at the same time enabled the option "Force use of GPU for 2D rendering" in the developer options. That seemed to do the trick. I was able to use the device for 2 days without any issues, until the glitching happened again yesterday evening.
Today I installed the 23.08.2019 build but that did not solve the issue unfortunately.
To clarify what I mean by glitching/lagging: the phone seems to work fine for 90% of the time. Everything works, the device is performing smoothly and the battely lasts more than a day, awesome.
But sometimes, the screen starts glitching, the interface is extremely laggy and the phone might even randomly reboot. This phone will then be glitchy/laggy andis unusable for an hour. Rebooting does not help, clearing caches does not help, ... The wierd thing is, the same behaviour is also present within the TWRP interface at that moment (so not only once android has booted), as you can see in this video I made. It as also present during the boot phase. But, after a certain amount of time (usually 20-60 minutes), all is fine again and the phone works perfectly.
Is there any change this is not a hardware issue and I might be able to save this phone? The only reason why I think this might not be a hardware issue is because the phone runs fine 90% of the time.
Thanks in advance!
latest build is the 23.08 build.
Try this Nougat RR 5.8.5, works great for me, no lags at all.
https://androidfilehost.com/?fid=6006931924117938132
psychem said:
latest build is the 23.08 build.
Click to expand...
Click to collapse
Thank you. I installed this one, however that did not solve the issue.
I am inclined to believe this might not be related to the ROM at all, since all the LineageOS 14.1 ROM and Yume's ROM also had the same issue and also the issue is present in the TWRP interface and during the boot cycle too.
Is there any driver/firmware/software/... that might be causing this instead of a hardware issue?
My experience with what you are describing leads me to believe one of three things may be causing this. Double tap to sleep on lockscreen enabled, Gboard and Chrome.
Try this, enable software button and disable hardware buttons and see if this resolved your issue. If so ... Toggling software buttons from time to time helps.
AOKP is the only rom this does not happen as well as OOS of course.
BuzzBradA said:
My experience with what you are describing leads me to believe one of three things may be causing this. Double tap to sleep on lockscreen enabled, Gboard and Chrome.
Try this, enable software button and disable hardware buttons and see if this resolved your issue. If so ... Toggling software buttons from time to time helps.
AOKP is the only rom this does not happen as well as OOS of course.
Click to expand...
Click to collapse
Thanks for the suggestions! I do not have Chrome and Gboard installed so that should be fine, but I have disabled the double tap to sleep/double tap to wake option yesterday. Since then I've not experienced any more glitching/lagging. If it returns I will disable the HW buttons and use on-screen buttons and report back.
Unfortunately, none of these options worked. The glitching and lagging is still there and is becoming more frequent.
Any chance I'm missing something?
acidiz said:
Unfortunately, none of these options worked. The glitching and lagging is still there and is becoming more frequent.
Any chance I'm missing something?
Click to expand...
Click to collapse
To put your mind at ease, try OOS and see if it occurs. Then you'll know for sure.
Edit: just saw your video, never seen that before.
Related
Last night I updated my g tablet to the most recent VEGAn ROM 5.1. I wiped all the data from my device via clockwork, wiped the Dalvik cache and repartitioned the internal memory as well. The install went smooth and everything is running great except for the fact that I now have no audio coming from my speakers. Turning the volume all the way up does nothing. I tried reinstalling the ROM but the issue repeats itself. Anyone have the same problem? Or, anyone have an idea how to fix this? Thanks.
Sound works fine here. I did have to take it out of silent mode.
bartonhen said:
Last night I updated my g tablet to the most recent VEGAn ROM 5.1. I wiped all the data from my device via clockwork, wiped the Dalvik cache and repartitioned the internal memory as well. The install went smooth and everything is running great except for the fact that I now have no audio coming from my speakers. Turning the volume all the way up does nothing. I tried reinstalling the ROM but the issue repeats itself. Anyone have the same problem? Or, anyone have an idea how to fix this? Thanks.
Click to expand...
Click to collapse
Sound fine here too. Volume rocker ONLY sets Media Volume in this ROM. Go to Settings->Sound->Volume and manually set volumes up, see if it fixes.
Thanks for the responses guys(or girls...one never knows). Silent mode is definitely turned off and I have also tried to address the issue by going into the volume settings. I have turned everything all the way up but I still get nothing. I'm gonna restore it to beta 4 and see what's up and then try and reflash 5 again. Wish I knew what was going on but thanks for the input.
Just reflashed to beta 4 and audio worked perfectly. I then reinstalled beta 5.1 and the audio disappeared again. Am I the only one?
bartonhen said:
Just reflashed to beta 4 and audio worked perfectly. I then reinstalled beta 5.1 and the audio disappeared again. Am I the only one?
Click to expand...
Click to collapse
I am actually still using beta 5, not beta 5.1, so not sure if something changed when Gojimi updated it this morning?
A quick suggestion - can you try first backing up everything in Clockwork Mod, then wiping user data and see if it makes a difference (i.e. if audio is still screwed up on a fresh install of beta 5.1).
Sound is fine for me in 5.1. All he changed was the G sensor stuff...
Backed it up, wiped user data, did a fresh install and still nothing. Maybe it is specific to my device(although I could not understand for the life of me why). Sad...I am loving VEGAn especially this newest update. I guess I will just wait for the next release to see what happens.
bartonhen said:
Backed it up, wiped user data, did a fresh install and still nothing. Maybe it is specific to my device(although I could not understand for the life of me why). Sad...I am loving VEGAn especially this newest update. I guess I will just wait for the next release to see what happens.
Click to expand...
Click to collapse
If it works in Beta 4, but not 5 maybe download the file again. Besides the G sensor stuff in 5.1 I think Gojimi also uploaded a new file to fix some boot.img size problem. Can't hurt to try the latest if you haven't already...
Did you try the headphone trick? (insert headphone plug into port, then unplug) That was an early issue that was resolved, but maybe it's making a reappearance.
I'm not on 5.1 yet, working on that today.
(btw, when I first read the title, I thought you were trying to do surround sound off your GTab!)
Brilliant! I've spent hours flashing and reflashing trying to get this thing to work and all I needed to do was plug in some headphones and then unplug them! I wish I would have found this out sooner so I wouldn't have wasted everyone's time. Thank You!
P.S.- Yeah I could see how there could be some confusion about title to this post...ha, I'll have to clarify more next time.
bartonhen said:
Brilliant! I've spent hours flashing and reflashing trying to get this thing to work and all I needed to do was plug in some headphones and then unplug them! I wish I would have found this out sooner so I wouldn't have wasted everyone's time. Thank You!
P.S.- Yeah I could see how there could be some confusion about title to this post...ha, I'll have to clarify more next time.
Click to expand...
Click to collapse
Only thing is you should not have to do that anymore. I bet you still have fragments of old roms hanging out. I do not have to do the headphone trick anymore and I am using 5.1. Haven't had to use that trick for a while now.
Whenever I flash something new I always do a factory reset, and a cache wipe. Every now and then I will use Nvflash to restore all the way back to brand new out of the box status. Too much of the old is getting mixed up with the new in a lot of cases causing lots of people to have weird issues that really don't exist.
Makes it hard for a developer to really know what is working and what is broken..
I just installed beta 5.1 and no audio issues, yet. Did you do a data wipe? Maybe there's something in /data causing the issue, that's my only guess.
Data wipes between mods and major updates is always recommended. I know it's a PITN but it can reduce the number of weird issues. I use Titanium Backup religiously.
I have never had to do it before with any older ROMS. I have only been using VEGAn ROMS since beta 3 came out. I also have been doing factory resets, wiping the cache, and repartitioning the sdcard consistently between installs. I might need to use Nvflash just to be safe and install a totally clean version.
bartonhen said:
I have never had to do it before with any older ROMS. I have only been using VEGAn ROMS since beta 3 came out. I also have been doing factory resets, wiping the cache, and repartitioning the sdcard consistently between installs. I might need to use Nvflash just to be safe and get it to stock.
Click to expand...
Click to collapse
I think the framework changed between beta 4 and beta 5. Different stuff. Maybe that's why you have been fortunate until now...
I got No sound too. Plugging in headset makes sound work On headet but when unplugged my sound is gone again. was working perfect on Beta 4.
Just flashed to Vegan Beta5 2 hours ago. My audio is working fine. Playing "Hall of the Mountain King" atm from speakers.
I update Vegan-tab 5.1 and the sound was working, i watched couple of movies, and today evening no sound, tried in setup and no sound.
I was turning sound off/on from the screen unlock, window, by swipe down the speaker icon. Now i have no sound.
I don't know what i did to make the sound goaway.
Update: now i got the sound back, don't know how i got back since i did all the tricks said in this forum.
1. did the settings->volume-> changed all 3 volume increase.
2. reboot may times.
don;t remember the order. so don't know which one cleared it.
So far I have not run into the no sound problem with b5.1. I sure hope it doesn't crop up because I leave today for a week long trip.
Last night i had installed FRING and Yahoo Instant Messenger, with the Voice/video add-on. And my media volume was muted, couldn't get it to go up. Even when going into setting, and increasing it, it wouldn't increase. I uninstalled those programs and it started working again after a reboot. Running VEGAN 5.2.
Hi all,
Firstly can I say thankyou to all of you at these forums, I've been a lurker for a while, waiting for my Prime to arrive, and I'm very grateful for all your insights!
I have now recieved it and seem to avoided most of the well-documented problems on here, but seem to have managed a new one (at least i couldn't find a similar one through searching).
So I updated the Prime with the new firmware and it all seemed to go well. After a while the notification popped up to do the camera firmware (as I had been expecting from these threads). I set it going, and after a short while it said it was complete. The next time I powered on however, the notification to update the camera firmware was back, so I did it again (thinking it must be additional one). But it keeps doing the same thing - saying it's successful, only to re-appear after a re-start.
My current versions are
Build - 8.8.3.33 (which i know is what it should be)
Camera - 0xFFFFFFFF (which I know is wrong!)
Anyone else had a similar problem? Or any ideas?
I have no idea if it's possible, but I am also wondering whether this is what's causing my auto-rotate not to work. Just to confirm, I have the auto-rotate set on, and the gyroscope doesn't seem to be working for anything else (tried it on riptide demo)
Any ideas would be greatly appreciated!
you should try reflashing .33 from the ASUS hosted file...i think there are a few threads about where to get it.
tdrussell said:
you should try reflashing .33 from the ASUS hosted file...i think there are a few threads about where to get it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1429067
Mine is completely borked. After installing ICS I got a notification for a camera firmware update. The update failed several times, and now when I launch the camera app it says it won't work without updated firmware...
EDIT: I rebooted and as soon as it started up it bugged me to install the camera update again. I made sure the screen stayed on while it updated this time and things seem to have worked out. Camera is working just fine!
Dear All,
The case of my phone is quite peculiar because there are several very serious problems, that combine together and make it impossible to use.
> The main problem is the lag. Still after i flashed the CM 13 and i am using the last Boeffla Kernel it lags so bad that i can't use it properly. Sometime to launch an app takes 5/6 seconds. This isn't changed even with different configuration for the Kernel.
The problem connected with the lag is that it takes ages to launch the apps, specially the gapps. It takes ages to launch chrome or maps or gmail. usually after are being launched they work, but apps like chrome are difficult to use on multiple tabs for instance. In general the multitasking is very slow.
>Another problem is that after the screen is locked it it takes at least 3 seconds to to being reactivated, same timing with every phisical button that wake the device up.
>The last problem is that the connection, either 3g or any other, sometimes is present sometimes is not, but it doesn't depend on the area, for instance sometimes works in my room sometimes not.
Is there someone who can help me to find a solution for these problems?
@Volkert Gage:
If everything run fine before CM13, do a clean flash without GCrap and custom kernel - perhaps you fished the wrong GApps.
If there were problems before, go back to firmware to repair.
rp158 said:
@Volkert Gage:
If everything run fine before CM13, do a clean flash without GCrap and custom kernel - perhaps you fished the wrong GApps.
If there were problems before, go back to firmware to repair.
Click to expand...
Click to collapse
thank you for your adivice rp158,
The fact is that these kind of problems (except for the connection) are not new for the phone, i always had it, even with the original firmware.
Before the upgrade to CM 13 i tryed to sort it with the original firmware but nothing worked.
Anyway, can i ask you what gapps pack do you reckon might work better on the phone?
@Volkert Gage: I recommend strongly to flash latest firmware +factory reset. You can't expect any stable LP or MM, if Sammy JB struggles.
@rp158 i'll try to do so then, thank you.
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
If this happens on a stock rom, it is probably a hardware issue.
audit13 said:
If this happens on a stock rom, it is probably a hardware issue.
Click to expand...
Click to collapse
Thank you for your reply, but this does not happen on the stock rom.
It's definitely good that this doesn't happen in stock.
Sounds like a incompatibility between the phone and rom. Have you tried earlier or later versions of lineage?
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
I can also confirm this on the latest lineageos nightly update to date. It's as if phone is on standby/sleep and no way to wake it up without rebooting the phone by holding down the power button until phone restarts. I don't need to go into recovery like OP. Anyone else?
Are we the only ones experiencing this issue? Any help would be appreciated.
Gizmotech said:
Are we the only ones experiencing this issue? Any help would be appreciated.
Click to expand...
Click to collapse
You got a reply in the other thread where you posted about it:
minealex2244 said:
I'm feeling bad for you guys. Everyone should get the same beautiful LOS experience.
Thank you @Gizmotech for the last_kmsg. I think that you removed the battery to be able to reboot your phone. If you received a notification (sometimes you will receive it but it will freeze before letting you know that you got a notification) then the kernel will freeze. If the kernel is freezing it's because of root or a failed attempt to remove root (even if it said that it was a successful removal). It's very simple: you get a notification and it freezes. Maybe it will give a sound and the LED light maybe not. What's sure is that the kernel will freeze. Lastest SuperSU has this issue fixed. If you want it working then dirty flash latest build again. Tell me if the issue was fixed and avoid root until that time. After you'll tell me the results you can flash latest SuperSU and tell me again what happened. Do not remove root. This is always a dangerous thing.
Click to expand...
Click to collapse
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Providing the last_kmsg will help Simon to find a solution. If you only complain about this issue then it won't be solved. Next time make sure to include last_kmsg.
---------- Post added at 19:49 ---------- Previous post was at 19:45 ----------
shivadow said:
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
Click to expand...
Click to collapse
Really? Do you know what beta means? I'm sure that you don't. Beta means that it is not really stable (80% or less of the things are working) while stable means that 95% of the things are working. This explains why LOS 14.1 for S6 was considered stable: because everything was working. Also that issues are already listed in the forums.
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. st the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Same problem with last lineage version. Are you found solution ?
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
cRaZy-bisCuiT said:
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
Click to expand...
Click to collapse
The problem is the rom or kernel. It happens to all custom roms and kernels on the s3. No-one has found the source of the problem.
Everything custom is beta even if it is considered stable. Beta means "not final". Unless you see a rom with "final" on it then you'll encounter issues at some point.
The only truly final product if you want root is stock rom rooted. If you flash a kernel you'll get the same problem.
I've been seeking help over most big android forums, and I can't seem to get anymore help other than that, and it's utterly annoying.
So I got a redmi 5 plus over in my country which is Malaysia, and it has a unlocked bootloader, and the box that came with it is in Chinese, so I can only assume it's a imported device. And it's fine in the few weeks, after 3 weeks, my screen started to lose control. I can see the screen showing the image, but I can't make any touches on the device and it won't respond, and the only way to fix this is by locking the screen and unlocking it again. And it won't permanently solve the problem as well. It still occurs randomly between uses, and sometimes it just loses control with everything flashing on screen (emulated touches I assume), and I can't control it until I lock the screen and unlock it again. And I've tried disassembled it and reconnecting the screen ribbon cable and it still occurs. Any method of fixing it for good, it's been messing with my gameplay or normal usage and it's really annoying. Thanks for any help in advance.
What MIUI version are you on? My problems were fixed with the versions released this March.
sigma392 said:
What MIUI version are you on? My problems were fixed with the versions released this March.
Click to expand...
Click to collapse
I'm on 9.2.6.0 NGMIEK, but I can't go any further than that due to software issues.
YenChen Je said:
I'm on 9.2.6.0 NGMIEK, but I can't go any further than that due to software issues.
Click to expand...
Click to collapse
Try flashing the latest firmware files for the stable version of MIUI. There may be problems in your firmware partition.
sigma392 said:
Try flashing the latest firmware files for the stable version of MIUI. There may be problems in your firmware partition.
Click to expand...
Click to collapse
I' m currently stucked on a chinese global firmware, and I have to wait 250 hours before unlocking, so yeah.. and any more newer firmware on global will kill my phone..
My fone liked yours
When i use stock chine it does not happen... After i unlocked & used miui eu, sometime same yours...but i update always ( eu weekly) almost this phenomena sometime happen....
I think this problem is connection to rom it does not compatible with hardware
It happens to me also on global rom 9.2.3.0 NEGMIEK when turning off memory optimization on developer options. The issue goes away after putting it back to middle.
Touch display problem
I was fixing this problem with turn off the background and notifications of facebook lite app
in my country a lot of people facing this problem same
(me too)
I am on latest Rom 9.6.2.0 but have the same issue in MEI7
MI Redmi 5 Plus Touch not working issue
I am experiencing the same issue with my MI Redmi Note 5 Plus with MIUI Version: 9.6.2.0 (NEGMIFD) - Stable version.
I have checked the apps and removed unnecessary apps to make sure this is not because of the any app installed.
Please suggest me what can I do to fix this issue?
Thanks.
mirza_arslan_baig said:
I am experiencing the same issue with my MI Redmi Note 5 Plus with MIUI Version: 9.6.2.0 (NEGMIFD) - Stable version.
I have checked the apps and removed unnecessary apps to make sure this is not because of the any app installed.
Please suggest me what can I do to fix this issue?
Thanks.
Click to expand...
Click to collapse
The touch screen may not be completely unresponsive but may be slightly unresponsive or too responsive. To calibrate the touch screen, follow the following steps.
Dail *#*#64663#*#* in the phone application
Tap touch sensor
Long press the menu button
Tap touch calibration
Follow on screen instructions to calibrate the screen
Source: https://www.ifixit.com/Wiki/Xiaomi_Redmi_Note_Troubleshooting#Section_Incorrect_Touch_Sensitivity
Same problem! I have official Miui Global Stable. Please help!
Is there already a fix for this issue or people who already managed to fix it? I myself encountered this issue too on last weekend. On MIUI Global 9.2 | Stable 9.2.6.0.0(NEGMIEK) too.
Same problem
I have same problem on miui global 9.6.2.0 stable and the navigation bar not working any solution
YenChen Je said:
I've been seeking help over most big android forums, and I can't seem to get anymore help other than that, and it's utterly annoying.
So I got a redmi 5 plus over in my country which is Malaysia, and it has a unlocked bootloader, and the box that came with it is in Chinese, so I can only assume it's a imported device. And it's fine in the few weeks, after 3 weeks, my screen started to lose control. I can see the screen showing the image, but I can't make any touches on the device and it won't respond, and the only way to fix this is by locking the screen and unlocking it again. And it won't permanently solve the problem as well. It still occurs randomly between uses, and sometimes it just loses control with everything flashing on screen (emulated touches I assume), and I can't control it until I lock the screen and unlock it again. And I've tried disassembled it and reconnecting the screen ribbon cable and it still occurs. Any method of fixing it for good, it's been messing with my gameplay or normal usage and it's really annoying. Thanks for any help in advance.
Click to expand...
Click to collapse
warranty
I have the same problem and its now frequently happening. It pisses me off, specially when Im in a Moba Game..
Anyone fixes this issue? please share
Went further from inital stable stock rom (nougat) until stable 9.6.5 (oreo), same touchsreen issue still exist
Like @cyrusextra said, it affected to mobile gaming experience. I'm a FPS gamer and this problem is totally messed up
Any fix?
Any solution to this problem?