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!
Hi I upgraded to a new CM10 nightly several weeks ago and then did not use my prime for several weeks I turned it on today and the above message keeps popping up I searched and it seemed to be a cm10 issue so I changed to a different rom (baked black bean 6) but no change and to top it off I can't even access the play store to try a different keyboard app so I really need help to solve the stupid message problem.
Keyboard has stopped working
fastfibre said:
Hi I upgraded to a new CM10 nightly several weeks ago and then did not use my prime for several weeks I turned it on today and the above message keeps popping up I searched and it seemed to be a cm10 issue so I changed to a different rom (baked black bean 6) but no change and to top it off I can't even access the play store to try a different keyboard app so I really need help to solve the stupid message problem.
Click to expand...
Click to collapse
I am having the same problem. I downloaded the latest PACMAN rom and noticed the battery would not charge past 40%. I figured it was a rom bug, so I reset to factory, installed the stable version of cm 10 and gapps, and now I cant use anything because the keyboard has stopped working message keeps popping up and wont let me text or download anything from the play store. Can anyone help us with this??
Hey guys!
I've already posted my problem in the Nexus 4 Q/A-Forum.. till now without help. Well i thought that maybe here is a good place to get help, too!
So whats my problem.. Yesterday i flashed a new update of Xylon-Rom (clean flash) on my Nexus 4. Installed and restored all Apps. Usually I use Swiftkey 4 as keyboard, so I set up everything like all the times before. The last times everything works fine, but this time not. I set up SK as my standard keyboard and began to write. After a while I wanted to write again, but suddenly there was the AOSP keyboard. Changed back to SK. But after some moments it happend again. So everytime when there is a text input AOSP appears.. I change back to SK then, but after turning screen on some minutes later AOSP again.
As it would be not enough, the same thing is happening since yesterday on my gf phone (HTC One S, also rooted with Carbon Rom). Like on my phone, it never happenend before.
What I've done till now? Erased App-Data of both keyboards, disabled AOSP keyboard. Everything without success.
Dont know why it happens now... I often flash other Roms, Updates etc and I use Swiftkey for a long time. Restoring with Titanium works everytime. And this time i haven't done any other thing on Restoring.
I hope u understand my problem (my english isn't the best ) and anyone could help me!?
Thanks so far.
Cls
Tried to freeze the AOSP in Titanium -> no effect
Set Swiftkey as System-App -> no effect
:X
I was encountering this with swipe keyboard previously, and my solution was to use swiftkey.
Sent from my Nexus 7 using Tapatalk 4 Beta
same thing
im suffering from this problem too.. no solution yet :3
Hi everyone!
I installed CM on my mothers phone some while back (+gapps). Seemingly she used the automatic update function yesterday and since then the mobile will not start up properly (start-screen stays even after a night). She tried taking out the battery and starting it afterwards. I'm about 2000km away for the next two weeks. Any suggestions what she could try, or what I could try once I'm back?
Thanks!
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.