Related
Is anyone else having an issue like this? My Note 5 is on the latest T-Mobile firmware. I've got something like 40-70 pieces of bloat disabled, and I still get outrageous keyboard and general OS lag. Here's a look at the typing performance of a hangout.
Also here's OS monitors look at my running processes. Any insight?
Thanks for any help.
Anyone else have issues like this?
Yes I was having these issues. It was driving me nuts. I tried debloating, and factory resest, with no succes. After updating arter97 kernel my issues went away. Phone works like it should, no more lag or slugish UI. Are you rooted? What method did you use. I'm rooted, I used TEKHD's method. But he has an older kernel in his instuctions. Here are link to the updated kernel, I used version 11.0 http://forum.xda-developers.com/note5/development/arter97-kernel-galaxy-note-5-t3189907 Hope this help.
whasapening said:
Yes I was having these issues. It was driving me nuts. I tried debloating, and factory resest, with no succes. After updating arter97 kernel my issues went away. Phone works like it should, no more lag or slugish UI. Are you rooted? What method did you use. I'm rooted, I used TEKHD's method. But he has an older kernel in his instuctions. Here are link to the updated kernel, I used version 11.0 http://forum.xda-developers.com/note5/development/arter97-kernel-galaxy-note-5-t3189907 Hope this help.
Click to expand...
Click to collapse
I'm not rooted, as I have the Samsung accidental damage warranty. But dammit I think i might have to. I'm glad at least someone had these issues and I'm not alone.
I get the feeling it's a cpu governer issue or something.
Sent from my SM-N920T using Tapatalk
Anyone else have any suggestions? I've cleaned some more apps and it still seems to be an issue.
Sent from my SM-N920T using Tapatalk
The only solution is Swiftkey as arters kernel will only help and not eliminate it.
Similar Issues with other models
I have had similar issues with my SM-G928F (S6 Edge+) before the latest software update and factory reset that I usually accompany with it, I think there was something wrong with Samsung keyboard on android 5.1.1, but they seem to have fixed it, maybe check options in the keyboard and the phone, maybe turn things like power saving mode off and then on again.
Sent from my rooted G928F (Samsung Galaxy S6 Edge Plus)
I'm having a big trouble with keyboard also.. When I press smiley key it needs up to 1 / 1.5 second to switch to emojis.. It is annoying
Maybe It's up to keyboard? Everything else works fine
Can I re-instal keyboard or put keyboard from S6 or It's the same everywhere
---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------
I just instaled google keyboard and It runs like hell.. so , so fast..
But I like more the stock one.. so any solutions? on my other phone (S6 Edge) never fel this lag.. never
Boot into recovery and wipe the cache partition. Before I rooted, that's how I'd solve my lag problems, which for me were very rare.
Akw6190 said:
Boot into recovery and wipe the cache partition. Before I rooted, that's how I'd solve my lag problems, which for me were very rare.
Click to expand...
Click to collapse
I did It once. Didn't help. Still slow when I want to go emoji page.
Is there a link to download and after instal/unninstal stock samsung keyboard
rankoradza said:
I did It once. Didn't help. Still slow when I want to go emoji page.
Is there a link to download and after instal/unninstal stock samsung keyboard
Click to expand...
Click to collapse
Nope. The Samsung keyboard, like most other system apps, can't be uninstalled unless you're rooted. If you're not rooted, the best you can do is download an alternative.
Akw6190 said:
Boot into recovery and wipe the cache partition. Before I rooted, that's how I'd solve my lag problems, which for me were very rare.
Click to expand...
Click to collapse
I've done this several times to no avail, thanks though.
Sent from my SM-N920T using Tapatalk
whasapening said:
Yes I was having these issues. It was driving me nuts. I tried debloating, and factory resest, with no succes. After updating arter97 kernel my issues went away. Phone works like it should, no more lag or slugish UI. Are you rooted? What method did you use. I'm rooted, I used TEKHD's method. But he has an older kernel in his instuctions. Here are link to the updated kernel, I used version 11.0 http://forum.xda-developers.com/note5/development/arter97-kernel-galaxy-note-5-t3189907 Hope this help.
Click to expand...
Click to collapse
As a follow up to your post, I've now factory reset and the problem is still occurring.
Sent from my SM-N920T using Tapatalk
Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,
You can't use an M kernel on N or vice versa. Won't work.
joseph230 said:
Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,
Click to expand...
Click to collapse
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).
zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
I flashed radio of 7.1.1 over 6.0.1 and it did not cause any issues. This is a proof to what you just said. Kernel is full of bugs and that is hard to fix
Sticking with 6.0.1 for now! Maybe I should get back into using custom roms again!
Thanks.
joseph230 said:
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).
Click to expand...
Click to collapse
Heck 98, XP and 7 were the only good ones. Dont even get me started on 10. I had to go back and revert over 300 PC to windows 7 when the 10 upgrade happed. That was just a nightmare.
What sort of issues are you talking about? Besides the speakerphone echo.
zelendel said:
Your issue is 7.1.1. Android N is full of issues...
Click to expand...
Click to collapse
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.
Lawstorant said:
What sort of issues are you talking about? Besides the speakerphone echo.
Click to expand...
Click to collapse
Wifi and Radio connection drops all the time. Many people seem to experience it!
NLBeev said:
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.
Click to expand...
Click to collapse
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!
joseph230 said:
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!
Click to expand...
Click to collapse
It seems to me that Google changed policy.
Till now the changes made the N6 great again.
No encryption, dark interface when possible.
Aquamail is better than Gmail, Signal is better than G-messenger. Nova launcher is better than G-now launcher.
I replace/disable G-apps and G-services when possible.
No Google Assistant, no Fit, no Pay, no Game, no Hangouts, no Wearable, no G-drive, no G-now.
Runs smoothly, no issues. Excellent battery life. Good to have XDA.
Hi community,
my lovely Note 5 is the best smartphone I've got ever. But since the update from 6.0.1 to Nougat, the problems begun.
The original Samsung Keyboard is crashing while rotating the screen (even I use swiftkey). And sometimes, but often I can play Videos in Facebook, WhatsApp, ... only after rebooting the smartphone. And some litlle more problems. But these two problems are annoying.
I've organized a S5 Mini for the while I'm rooting and installing the custom rom on the Note 5. But I'm looking for a stable rom with no known bugs like battery drain, or similar things ...
Is this possible meanwhile?? I'm not using Knox. I just want a "stable" smartphone ...
Greetings,
kangaroo72
kangaroo72 said:
Hi community,
my lovely Note 5 is the best smartphone I've got ever. But since the update from 6.0.1 to Nougat, the problems begun.
The original Samsung Keyboard is crashing while rotating the screen (even I use swiftkey). And sometimes, but often I can play Videos in Facebook, WhatsApp, ... only after rebooting the smartphone. And some litlle more problems. But these two problems are annoying.
I've organized a S5 Mini for the while I'm rooting and installing the custom rom on the Note 5. But I'm looking for a stable rom with no known bugs like battery drain, or similar things ...
Is this possible meanwhile?? I'm not using Knox. I just want a "stable" smartphone ...
Greetings,
kangaroo72
Click to expand...
Click to collapse
So far to me, dr ketan rom having no bugs or issues on my note 5.. very stable and smooth also battery friendly.
kangaroo72 said:
Hi community,
my lovely Note 5 is the best smartphone I've got ever. But since the update from 6.0.1 to Nougat, the problems begun.
The original Samsung Keyboard is crashing while rotating the screen (even I use swiftkey). And sometimes, but often I can play Videos in Facebook, WhatsApp, ... only after rebooting the smartphone. And some litlle more problems. But these two problems are annoying.
I've organized a S5 Mini for the while I'm rooting and installing the custom rom on the Note 5. But I'm looking for a stable rom with no known bugs like battery drain, or similar things ...
Is this possible meanwhile?? I'm not using Knox. I just want a "stable" smartphone ...
Greetings,
kangaroo72
Click to expand...
Click to collapse
have you tried to perform a full wipe on stock?
im using stock rom, rooted with super su and flashed fuel kernel
so fast very very stable for me
when jumping from major firmware changes, full wipe is always recommended
Yes, I wiped two times... Which model you have? N920c too? Which firmware?
I've tried all nugat rom on 920CD. All original and custom: all have the problem of missing voice notifications: call without ringing, no sound messages, and all other silent notifications. About 90 installations and all are strictly clean. All with that problem. Today I'm back to Android 6.01.
This because nobody can help me in this problem to solve .
Download the latest stock ROM here: https://www.sammobile.com/firmwares/
Use "so far stable Odin3 v3.12.3": http://odindownload.com/download/#.WXLIZmh97Dc
I have been using this method since the first 6.0 update and found no issues at all after the full reset (wiping data & cache)
As of now the most stable version on my Model Number SM-N9208 is PDA N9208XXS3CQF3 and CSC N9208OLB3CQD2
Don't forget to wipe cache and data AFTER you install the ROM. Even if wiping cache is only advisable but wiping data will help you get rid of those bugs from your previous OTA Update.
AND DON'T FORGET TO BACKUP YOUR DATA BEFORE DOING THIS
****** SEARCH IN GOOGLE OR YOUTUBE ON HOW TO PROPERLY USE Odin3 v3.12.3 *******
***** I WON'T HELD RESPONSIBLE IF YOU DO SOMETHING WRONG ON YOUR PHONE SO PROCEED WITH CAUTION BUT THIS METHOD IS THE SAFEST AND LEGAL METHOD *****
The touch delay is present since the release of Marshmallow, Nougat and Oreo ROMs in Titan (not sure about Falcon). There is no escape. It's good to see our 2014 devices with the latest version of the Android, but this error is very annoying and is being ignored. Doesn't matter how good the ROM is. If you using any custom ROM with Android 6.0 and up on titan, i'm sure you have this issue.
So i want to open a discussion about this issue here
If you don't know what i talking about, let's simulate the issue:
Try to write something in stock keyboard of your MM,Nougat or Oreo ROM. Now try pressing a second finger in the screen out of the keyboard and write anything else... You noticed? No?
Try to play a very intensive tap game, like Geometry Dash. Play a bit. Now play with a second finger on screen... You noticed?
Only KitKat and Lollipop Roms are free from this bug.
So, the only workaround for this touch delay is pressing a second finger on screen. Shame.
The questions left: Anyone knows a solution? The cause of this issue? There is no way to fix this?
I tried some custom kernels, no success.
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Metalhead666 said:
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Click to expand...
Click to collapse
Some people say the same on Lenovo Foruns...
Pixx 1001 said:
Some people say the same on Lenovo Foruns...
Click to expand...
Click to collapse
I think it is a kernel related issue rather than the bootloader,like some people said on lenovo foruns.I don't have proper knowledge to fix it,you could try to contact some of our developers,maybe there's still someone interested.
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
HiR3x said:
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
Click to expand...
Click to collapse
Every single ROM above 6.0 that I tested have this problem (Cm,AOKP,AOSP,Lineage,Slim,DU,CypherOS,AEX,CrDroid,RR and many more),with and without custom kernels.
I don't use my Moto G to play games , but some random games from PlayStore (Minigore 2, Bejeweled 2, Samurai II) the touch doesn't work well (or simply doesn't work! You can test all of them if you want). Using a 5.1 ROM, they work normally. It would be nice if the people post more problems about this touch issue happening on apps/games on Moto G Titan. I want to know if the same happens on Moto G Falcon, 4G variants.
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Jimisballjohn said:
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Click to expand...
Click to collapse
Well, I used ViperOs (7.1) as my daily driver at work, school for a good time (6 months I guess)... I liked Nougat Features and I guess I will keep using it, or another Nougat ROM, as they work perfectly for it on Titan.
Looks like titan Pie ROMs have the issue too (Used LineageOS 16 for testing).
It sucks that this still has not been resolved. Happened to me as well on LineageOS 16.
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
LightWard said:
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
Click to expand...
Click to collapse
I would like to test it myself and give a feedback, but sadly, my old Moto G2 had the input of the charger/usb connector broken. If anyone have tested the ROM too, would be good if they give a feedback here.
Hi guys, I've faced some issues in the last 3 weeks. First of all, I was on Stock Pie rooted with magisk. After a random restart my phone went to boot loop and I went back to stock, relocked bootloader and tried to update. First Issue: step 2 of upgrading stock kept failing. Due to this inconvenience I decided to re-unlock bootloader and install a custom rom. The first was the pixel experience, and I was very enthusiastic of it, it was perfect. Suddenly the pe got removed from the site and the release suspended. So I tried 3 custom ROMs 10based, the first was havoc and it didn't work very well for me, presenting various bugs. So I tried Lineage 17.1 and I got a very strange battery drain and issues with system app conflicting with gapps. Now I'm on derpfest, sometimes it's a liiiittle laggy, but still good. BUT my banking app doesn't work and I really need it. So, here is the question: Which rom would you suggest me? I'd like it to have these features:
•Stable for a daily run
•Able to run banking app
•No preinstalled system apps as phone, contacts, etc. (I prefer gapps for this)
•10 based
•Good battery life (nothing exceptional, just like stock)
Instead of a custom rom, I would accept to back stock if there is a way to receive OTA update.
Thank you all for your help and forgive me if I wrote something wrong, I'm from Italy and my English is not so good.
EDIT: I forgot to mention that I didn't install magisk on any of these ROMs.
havoc is bad on my device. crdroid and pe are good, crdroid have excellent and complete language support. i never flashed lineage 17.1, I will try it.Sorry my bad English.
Deep fest
What kind of bugs you had on Havoc? I'm using this since I rooted my phone, over a year ago, and works pretty well. I have done the following settings: formated the Data partition as f2fs, installed Magisk, installed OpenGApps nano, and a moded GCam by Parrot043 (version 7.2.014 because the latest has some bugs).
The problem you're having with your banking apps is not related to the ROM, recently Google has pushed a patch to SafetyNet which detects if you've got an unlocked bootloader, custom ROM or if you're rooted, to address this issue you need to install Magsik and use Magsik hide on you're banking apps, if that didn't work either you're gonna have to install a Magsik module called "MagiskHide Props Config" which will hopefully solve the issue. Remember it's not just you and it's happening for all people with custom ROMs or unlocked bootloaders. Also this is a temporary solution since we don't know how Google is going to enforce the newer patches to SafetyNet.
About ROM suggestion thing, DerpFest is pretty good. I was actually on DerpFest myself but then I reverted to stock since the device was overheating too much. Also give crDroid a go. But untill there's a better workaround for SafetyNet I suggest you to revert to stock.
For help and support regarding DerpFest join the official telegram group : https://t.me/BestRom69
LonelyGlitch said:
The problem you're having with your banking apps is not related to the ROM, recently Google has pushed a patch to SafetyNet which detects if you've got an unlocked bootloader, custom ROM or if you're rooted, to address this issue you need to install Magsik and use Magsik hide on you're banking apps, if that didn't work either you're gonna have to install a Magsik module called "MagiskHide Props Config" which will hopefully solve the issue. Remember it's not just you and it's happening for all people with custom ROMs or unlocked bootloaders. Also this is a temporary solution since we don't know how Google is going to enforce the newer patches to SafetyNet.
About ROM suggestion thing, DerpFest is pretty good. I was actually on DerpFest myself but then I reverted to stock since the device was overheating too much. Also give crDroid a go. But untill there's a better workaround for SafetyNet I suggest you to revert to stock.
For help and support regarding DerpFest join the official telegram group : https://t.me/BestRom69
Click to expand...
Click to collapse
I didn't know about that, so i thought it was a fault related to the rom, my apologies. Well, gave derp fest a try but I didn't enjoy it so much, so I went back to PE when i saw the unofficial topic. Now i'm running magisk to use hide feature on my banking app and everything is working great. Sometimes the settings autoclose, but is not too much annoying. Now I'm thinking to buy a mi note 9 pro max (when it will be released in Italy) and keep my Mi A2 as an emergency phone, so I wish to not having trouble during the waiting. Thank to you and to the other users for giving me help in this thread
Chrees_996 said:
I didn't know about that, so i thought it was a fault related to the rom, my apologies. Well, gave derp fest a try but I didn't enjoy it so much, so I went back to PE when i saw the unofficial topic. Now i'm running magisk to use hide feature on my banking app and everything is working great. Sometimes the settings autoclose, but is not too much annoying. Now I'm thinking to buy a mi note 9 pro max (when it will be released in Italy) and keep my Mi A2 as an emergency phone, so I will to not having trouble during the waiting. Thank to you and to the other users for giving me help in this thread
Click to expand...
Click to collapse
Good luck and have a nice day, also take care, we love Italy and you guys will get through it.
LonelyGlitch said:
Good luck and have a nice day, also take care, we love Italy and you guys will get through it.
Click to expand...
Click to collapse
I really, really thank you for your wish, We'll make it
I begin to be tired of th A2...
I think I will try redmi note 9T