Does anyone experience this? *see attached*
I tried flashing different Roms from different countries but it is still present.
Cherry Mobile One (H940)
Currently on LMY47I
lazydreamr said:
Does anyone experience this? *see attached*
I tried flashing different Roms from different countries but it is still present.
Cherry Mobile One (H940)
Currently on LMY47I
Click to expand...
Click to collapse
i have similar issue for me looks like hardware related
lazydreamr said:
Does anyone experience this? *see attached*
I tried flashing different Roms from different countries but it is still present.
Cherry Mobile One (H940)
Currently on LMY47I
Click to expand...
Click to collapse
No problem with stock roms,even Official Lollipop has no issues, only CM builds have problem, I found this issue when using dish aligning apps, in Satellite Director Elevation is remains stuck at random reading.But everyting works fine with stock lollipop and kitkat.
Related
Hi,
I just wanted to create a centralized thread for all the discussion surrounding the work of fixing the softkeys.
Many users are reporting, including myself, about the softkeys not working properly after some time on the ICS roms.
My 25 cents:
Is it a kernel issue? ROM issue? I have tried multiple ROMs but none have fixed the issue.
Multiple kernels tried too, to no avail. I suspect it is a software issue though. It's as if the buttons go into some state of sleep mode in the software, and after a few minutes come back for a few milliseconds. Just my thoughts into it.
-
Sergio
After facing the issue, i smartflashed gingerbread, there also softkeys not worked.
It is a kernel issue for sure. Worked great on GB, but I think they messed up the driver in ICS. Have you tried my blue kernel already? Dont know if I fixed it there, but it is worth a try. Or compile your own kernel, but use the GB Softkey files. Should work just fine with some mods here and there
Sent from my XT1052 using XDA Free mobile app
Has anyone successfully fixed this issue?
I am facing the same problem after flashing ICS on my OB.
i fixed it by replacing the digitizer, i had to order 2 cause the first arrived with the same problem.
Maybe
hackerse7en said:
i fixed it by replacing the digitizer, i had to order 2 cause the first arrived with the same problem.
Click to expand...
Click to collapse
I don't know about that though, mine works excellent through the CM key test. Just fails in the OS. And I can't use the kernel by Nooby, I'm on Nameless KK. But before that I tried IZS, GB, 2.1, etc to no avail.
I'm gonna research this and try and fix it in the Aeroi Kernel
I am facing frequent network 4G/3G issues on my Nexus 6. Data goes off for 30 minutes to 1 hr or more around 4-5 times a day.
Tried clearing google connectivity data , unistalling connectivity services updates, and so on but still the problem pops up frequently. any possible solution ?
The problem is not with the carrier since this doesn't happen on my Xpeia Z3.
I am running 7.0 stock rooted
Build NBD90Z
kernel : 3.10.40-gede039c
BB : MDM 9625_104670.31.05.42R
smithinsundar said:
I am facing frequent network 4G/3G issues on my Nexus 6. Data goes off for 30 minutes to 1 hr or more around 4-5 times a day.
Tried clearing google connectivity data , unistalling connectivity services updates, and so on but still the problem pops up frequently. any possible solution ?
The problem is not with the carrier since this doesn't happen on my Xpeia Z3.
I am running 7.0 stock rooted
Build NBD90Z
kernel : 3.10.40-gede039c
BB : MDM 9625_104670.31.05.42R
Click to expand...
Click to collapse
Hi. I cleared my Cache Partition and golden since then.
Was experiencing something like you described...though different periodic.....as well as bluetooth and Wifi hotspot issues.
Have same Build as you on my Nexus 6.
Luck
smithinsundar said:
I am facing frequent network 4G/3G issues on my Nexus 6. Data goes off for 30 minutes to 1 hr or more around 4-5 times a day.
Tried clearing google connectivity data , unistalling connectivity services updates, and so on but still the problem pops up frequently. any possible solution ?
The problem is not with the carrier since this doesn't happen on my Xpeia Z3.
I am running 7.0 stock rooted
Build NBD90Z
kernel : 3.10.40-gede039c
BB : MDM 9625_104670.31.05.42R
Click to expand...
Click to collapse
There have been several noted issues with the 05.42 Radio you are using. If you flash an older radio your issues will be resolved. There are fastboot flashable radios and also TWRP flashable radios. Choose whichever suits your needs. You can also flash several different radio's to find which one gives you the best connection. Hope this helps.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
There have been several noted issues with the 05.42 Radio you are using. If you flash an older radio your issues will be resolved. There are fastboot flashable radios and also TWRP flashable radios. Choose whichever suits your needs. You can also flash several different radio's to find which one gives you the best connection. Hope this helps.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks buddy. I have been searching for flashable radio . I ended up finding 5.42 only for Nougat. Will android 6.0 radio work on nougat ?
Sent from my D6633 using XDA-Developers mobile app
smithinsundar said:
Thanks buddy. I have been searching for flashable radio . I ended up finding 5.42 only for Nougat. Will android 6.0 radio work on nougat ?
Sent from my D6633 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, you can flash any radio for the Nexus 6 no matter what version of Android it came from. You can flash any 6.0 or 6.0.1 radio or even a Lollipop radio. I've been using the 02.101 radio at home near Dallas, Texas and since I own a trucking company I am on the road all the time I keep every TWRP flashable radio on my USB OTG drive in case I am in an area where my service starts to suck I can switch radios instantly. Here is the link to @Q9Nap's thread with all the available radios for download.
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
Sent from my Nexus 6 using XDA-Developers mobile app
I'm on stock ROM 5.1 build LPA23 12-39.7 and I'm having wifi issues. It happens at random times, even at home not being able to see the wifi access points at all, even if the SSID's are broadcasting. I saw some threads stating moto x has that issue. Any way to fix it and is there a stable 5.1.1 ROM available? I see there is a 7.0 but it has camera issues
Anybody?
sam008 said:
I'm on stock ROM 5.1 build LPA23 12-39.7 and I'm having wifi issues. It happens at random times, even at home not being able to see the wifi access points at all, even if the SSID's are broadcasting. I saw some threads stating moto x has that issue. Any way to fix it and is there a stable 5.1.1 ROM available? I see there is a 7.0 but it has camera issues
Click to expand...
Click to collapse
Hey bro, i too have this samee issue
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.
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.