Hey guys,
For 2 weeks now I got a laggy Keyboard. It's not always laggy, but often, it just doesn't recognize my input when I type a letter, and then it feels really slow.
I tried different, Roms and Keyboards and also Stock, Problem still there (wasn't before! Had the same Roms tried before the problem already) Disabled Encryption and Selinux is permissive. Also Tried save Boot. I usually clean flash and use ROM, Gapps, Magisk, + "Disable Encryption" zip.
It occurs before and after optimizing (disabling stuff etc)
I kinda think it could be a Hardware problem.
Maybe someone has an idea.
Cheers
Bottom right the glass is a little broken, maybe that's the reason? Maybe it got worse or so and now it's giving some input all time? Although I checked a display test and only my hands did visible input.
"SOLUTION"
I think I improved it by using "Partial "Screen repair". Also ""Touchscreen Repair" seems to be a good app that helps for smoother
Related
Hey guys,
I've been having some keyboard issues for a while now and it's really starting to bug me. I'm currently on BAMF 2.1, but I've used various iterations of BAMF and I was even experiencing the same problem on CM7. Whenever I install a new ROM I do a complete wipe 3x and lately I haven't even been restoring data on my apps.
When typing, certain letters just don't work. It's really odd. I can sit there and tap tap tap away, and it may take like 6 taps to get a letter to work. At first I thought it was my screen, but I experience NO issues with the screen anywhere else but typing. The fact that what letters don't work often change (both in landscape AND portrait) also makes me think that it's not the screen.
I'm currently using Smart Keyboard Pro with a DX skin (had a DX before this and loved the keyboard), but I've even switched to the market version of the GB keyboard and experienced the same problem.
Edit: I forgot to mention that it doesn't always happen. I could go half a day with no issues, but then it pops up and it's pretty persistent.
Does anyone have any ideas? It's really starting to become a problem.
I have experienced maybe something similar. Since I flashed gingerbread ( my keyboard sometimes locks up. There's usually a delay of 3 seconds before it picks up. I'm using swift but it has happened on swype and the stock keyboard.
Happens to me, exact same problem but it also happened on my inc so I'm not too worried lol it IS annoying but doesn't last for an extended amount of time
Sent from my ThunderBolt using XDA Premium App
Ugh, this is still happening to me and still being a pain in my ass
Flashed neutrino 2.9 this morning and it is AWESOME! It was my first time ever flashing anything onto my phone, and everything worked out great! There are only 2 things I am wondering about...
First off, am I able to get swype set as my input method? I realize it's a pretty stripped down rom and swype has most likely been removed to cut down on size or increase efficiency etc. I've tried installing the swype beta, and managed to get the installer installed (yeah it's kind of an odd system, you download and install the installer to install swype) but for whatever reason when I type in the user/pass to get the actual swype installed, it just sits there forever and doesn't do anything. I've also just tried restoring swype with titanium backup from the backup I did on my stock rom, but it just starts a force-close loop until I set the input method back to the regular keyboard.
Secondly, and this is extremely minor, when I set up the fingerprint unlock there doesn't seem to be any backup unlock system for it. In the stock rom as we all know there is a pin that you can set to unlock as an alternative to swiping your finger on the reader. Maybe I'm just paranoid, but it would be a bit of a pain in the ass if I was to drop my phone and a rock smashed the fingerprint sensor, or my index fingers got chopped off in some freak accident haha.
All input greatly appreciated! Apologies if this is in the wrong forum, didn't seem quite appropriate to be posting over in the development section for something like this though.
*EDIT*
Swype problem solved. Looks like there was something wrong with the swype beta installer. After force closing it and opening it again it worked just fine, and swype is now installed and working (so far) perfectly!
So... Sort of a bump, but I ran into a new problem today.
For some reason when charging my phone, it only charges to 92%. I had it plugged in for about 12-13 hours, and it just seemed to stop charging. I pulled the battery, rebooted the phone, plugged it back in, etc. Didn't seem to do anything.
Anybody run into this one and know of a solution?
Tried this already?
Worked like a charm! Thanks.
was the fingerprint pin bypass every addressed?
i just started using 2.91gt+ and i won't enable the fingerprint lock with out a bypass pin...
i'm a marine engineer so my hands are constantly in and out of oil, fuel and fast orange so i've had days where on the stock rom it wouldn't even recognize i swiped my finger over it at all
I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.
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.
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.