Touch stops working. - Galaxy S 5 Q&A, Help & Troubleshooting

Okay, so... I'm a noob at this. Apologizing up first if I somehow did something wrong or not properly.
Issue:
I have a Verizon Samsung Galaxy S5. About a year ago I managed to get root access and boot LineageOS on my device, and it was working just fine. 2 months ago I decided to try out resurrection remix oreo. It also worked fine... but then I decided to upgrade the rom... Instead of upgrading (by flashing the new build) I went into recovery (TWRP) did an advance wipe and wiped the entire system, data, cache etc... and just loaded the rom like new with Gapps and Magisk.
For some reason TWRP doesnt work well with Aroma Gapps... and I often like to customize what Gapps get installed. It took me a while to figure out how to make a gapps config file and where to put it.
So after booting the new os everything seemed to work fine. Except! Whenever someone called me, my touchscreen would not respond... I couldnt answer calls or even end them. I had to wait till the call ended so I could use the phone again. So I tried clearing the Phone app's data and see if that would help. (It didnt)
I decided to wipe my device again, do a factory reset. So I booted into recovery only to find my touch screen wasnt working again! I pushed the power button to turn off the screen and turn it on back again and my touch worked. (This was strange)...
So I went ahead and cleared everything again, this time I decided to downgrade and go back to LineageOS 14.1. and now..... it's worse.
The touchscreen goes on and off when it feels like it. It doesnt happen with just calls anymore.
The touchscreen would work but the navigation buttons (Recent apps and back button) seem to work.
and then there are times where the touchscreen would work but the navigation buttons wouldnt work.
sometimes both wont work.
I also get a bootloop issue.
The Samsung Galaxy S5 Powered by Android boot up screen usually loops for a good while and then youd get the Lineage os boot animation. Sometimes it comes on as normal.
I know you guys may need a logcat. So ive grabbed one. I'm not sure how to attach because I dont see any option to and apparently after 10 post, only then I can post links.
I also tried flashing a new Kernel but that didnt help...
Again I'm apologizing if i did anything wrong or improper. If you need anything else, I'll be willing to provide more.
Thank you!!!
Link to Logcat:
nofile.io/f/sEA03NPv8rx/2018-06-26-17-47-11.txt
I also used GAPPS Super package with a config file for custom gapps installation.
Link to my GAPPS config file:
nofile.io/f/qONXoDoewuX/open_gapps_log.txt
nofile.io/f/hodHOtCFaTH/open_gapps_debug_logs.tar.gz
nofile.io/f/35qUphmpxOZ/.gapps-config
EDIT: Ive noticed whenever my nav buttons dont work, the recent apps button is lit but very slightly, the back button doesnt light up at all.

hyp3rvybe said:
Okay, so... I'm a noob at this. Apologizing up first if I somehow did something wrong or not properly.....
Click to expand...
Click to collapse
I'm just going to suggest something...
Have you tried the following?
1) Go to Developer options...
2) Then the Drawing Section (or Rendering Section)...
3) Locate and Disable/Turn Off the "Hardware Overlays".
It looks like many Samsung Devices experience this issue (or similar) and is, unfortunately, misdiagnosed as a hardware issue (though it can be Hardware Related).
Sometimes, without any "rhyme to reason", the device can get a bit confused between the use of Hardware or Software settings and acts like its in a "Panic" like state bouncing between the two.
The above steps just manually tells the device to use GPU for all/any screen adjustments.
There's no guarantee that this will work but, I've seen it work for most individuals who has/have/had experienced the same/similar issue.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Apparently it was already off... I tried turning it on. Will use it during the day and see what's up. Also I remember whilst the logcat was running. If I tapped the screen it would show something like "pause audio"... I'll grab some screenshots later.
And as for touching the navigation buttons. It shows Google input method anytime I touch the buttons. I'll grab some screenshots to show specifically. Have to head to work

Okay so if I touch the screen, log records the entry as
AudioService Stream Muted, Skip Playback.
Anytime I touch the navigation buttons it shows
GoogleInput onFinishInput(): Dummy InputConnection bound
GoogleInput onStartInput(): Dummy InputConnection bound

hyp3rvybe said:
Okay so if I touch the screen, log records the entry as
AudioService Stream Muted, Skip Playback....
Click to expand...
Click to collapse
Your best bet is to post this within the following Q&A thread that's specific to the S5 and Variants.
https://forum.xda-developers.com/showthread.php?t=2700073
Members there should be able to provide some better guidance than I can at this point.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Related

[Q&A] [ROM][4.4.4]VanirAOSP[OFFICIAL][Samsung X Cover 2-GT-S7710]

Q&A for [ROM][4.4.4]VanirAOSP[OFFICIAL][Samsung X Cover 2-GT-S7710]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
hi , installed this rom but i still haven't network connection
Double boot when starting phone
Hello all together.
Yesterday I flashed the latest rom on my skomer.
So far everything runs smooth but I recognized one weird thing.
During boot (doesn't matter if a warm or cold start), the phone boots twice.
Means I see the Pin entry screen and after approx. 15s I see the boot animation again.
It does not matter if I enter the pin or not, it boots a second time at all.
After the second boot everything is OK.
This was a clean flash from theboegls prerooted image with normal pa gapps flashed.
Does anyone have a solution for this issue!
Thanks a lot,
Kubunter
Just installed the new nightly(4.4.4.101014) Everything is running smooth. Just wondering if there is a radio for android 4.4.4 and how do i get it if there is?
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
ManuelBiancolilla said:
hi , installed this rom but i still haven't network connection
Click to expand...
Click to collapse
I read the forum and tried this code and it worked for me.
run this code in your terminal if you cant find terminal get if from playstore using wifi.
adb shell
su
find /efs/|while read s; do chown radio:system $s; done;
find /modemfs/|while read s; do chown radio:system $s; done;
chmod -R 777 /efs/
chmod -R 777 /modemfs/
reboot
After reboot your mobile data should be working
Camera not working
Thank you for your great work, hopefully devs are reading this subthread, too.
It would be nice, if following message would be referred on the first message, since many people have issues with network. I managed only to find all the information by very inconvenient googling:
http://forum.xda-developers.com/showpost.php?p=55354795&postcount=414
This post is the Theboegl's relevant one:
http://forum.xda-developers.com/show...3&postcount=43
After the newest nightly, camera stopped working. I will downgrade, but here are some details:
Model:
GT-S7710
Incremental version:
eng.nuclearmistake_20141012.042853
Running apps:
Nothing extraordinary
Exception class name:
java.lang.NullPointerException
Source file:
PhotoModule.java
Source Method:
initializeFocusManager
Line number:
1997
Start trace:
PhotoModule.java: 1997, 1835, 96 and 234
Cleaned cache+camera data. I was using SIM-card as my memory.
ManuelBiancolilla said:
hi , installed this rom but i still haven't network connection
Click to expand...
Click to collapse
Did you use the right clockworkmod mentioned on the main post? Also your firmware might be too new, therefore flashing this one might help:
http://forum.xda-developers.com/showpost.php?p=40232503&postcount=43]
If I got it right it must be
- install odin and get cwm on pc
- get supersu and cm on your sd card
- reboot in download mode
- flash cwm on phone
- reboot in Recovery
- well i think you can backup already
- root with supersu
- reboot in Recovery
- wipe data/factory
- install
- reboot​
I use 1010114
wifi and camera work here, but sim card seems not to be accepted
good use of hardware buttons after reflashing (this had issues before)
[did not install GApps, but that should not be a problem..?]
tried 10.2 from flxo and had the same problem with SIM
Double Boot
Hello all together,
I have a logcat of the problem, saved at pastebin.
As I´m a new user, I´m not allowed to post a outside link.
Is it possible that I will send someone who is able to post a link a PM?
The second boot happens around 22:44:54 o´clock
Something with a android process seems to be wrong.
Is anyone able to help?
Thanks a lot,
Kubunter
Android Lollipop?
Pushed fix for streaming YouTube should now work next nightly. Downloading source now to build recovery image. Thanks for waiting. I will try to solve the problems we have but I can't guarantee anything due to lack of device. I'm going to discontinue my work for ste devices soon. As long as it builds I will try my best to keep supporting them but fixing problems etc I can no longer continue.
Click to expand...
Click to collapse
@Unjustified Dev, will you made Android 5.0 for xcover 2? (Because you discontinue development)
andrew551 said:
@Unjustified Dev, will you made Android 5.0 for xcover 2? (Because you discontinue development)
Click to expand...
Click to collapse
There are still STE developers and I'm sure this one will get lollipop working if he can't I doubt we will see it , but lollipop might be a large merge and roms might have to rebase or start from scratch porting hardware workarounds and eventually bring back features.
intermittent network signal
Guys please help. I tried this ROM and it looks great but I'm loosing network signal almost every time I'm starting up navigation (Sygic) and I use it a lot. I don't loose it immediately, sometimes after a few minutes, sometimes after 20 min. but the signal triangle finally goes black and doesn't come back after switching off navigation. This makes it unusable to me. I've seen people reporting problems with network signal so I guess it's not the app. issue. Sometimes it looks like I just loose data transfer (it shows no internet) but the signal bar shows that I have network. Some other time I was not moving at all but the signal bar was going up and down from max. to min. within 3 sek. After few minutes it stabilized. Something seems to be wrong with the antenna or modem, whatever is responsible for network signal.
And another thing, that looks to be related, I don't have any arrows and network type sign (2G/3G) showing if I do or don't have internet connection.
There were some posts talking about a fix for network problem by typing some commands somewhere but could someone explain it step by step how to apply it, if it is a working fix.
Thanks!
After a reboot the home button doesn't work until I enter my pin code, which comes like half an hour after boot! How do I fix it and does anyone else have this problem!?
I was about to throw this piece of **** phone away but i gave it a last chance with Vanir. It took me nearly 2 hours to flash the Rom , but i got it working.
First of I want to thank the dev for the work, I realy apreciate it. You managed to make this phone usable again, I hate Samsung so much for this crap Software they used for the Xcover2.
After using Vanir for one week (using not testing), here is what is not working for me:
-maximum volume for every call
-stock photo app crashes
-Location is very inaccurate, my guess is the cell tower fix is working and the GPS is not
-sometimes i cant shut off the phone, it freezes and i have to pull the battery
-phone is sometimes not going to sleep mode, i have to restart it
Everything else is working perfectly, this is thousand times better then the Samsung bull****. Oh, my carrier is Telekom(Germany).
No radio/SIM with GT-7710 XCover 2 on CM11
The forum forces me to open a new thread, apologies.
I gave the Vanir Skomer 4.4.4.101714 nightly a try but my broadband (S7710XXAND2)/IMEI is gone after reboot. Big difference to most reports I've read is that once I return to stock ROM all is fine again. In other words: the SIM was not damaged. Also the chmod/chown and move-files-from-stock trick doesn't improve anything. No idea what else I should try. I'm currently back on stock Android.
This is what I've done:
- Use Odin 3.09 to apply 20140112_cwm-6.0.4.6_skomer_fixed.tar.md5
- Boot into CWM
- Update to CWM 6.0.4.7 via cwm_skomer_test2.zip
- Wipe/Factory + Dalvik reset
- Install vanir_skomer_4.4.4.101714.zip (also tried 20131231_cm_11.0_skomer-ota-eng.flx.zip)
- Install pa_gapps-modular-pico-4.4.4-20141019-signed.zip
- Wipe/Factory + Dalvik reset
+ Copied {efs,modemfs} from stock to vanir (removed vanir's folder contents before)
+ Fixed file perms to 666, folders to 777, owner to radio:system
I couldn't find TWRP for Skomer or a more recent clockwork recovery. Just mentioning this because I've read a post that mentioned recovery is responsible for setting radio related stuff.
Ideas?
Network connection doest work for me to. I like this rom too and like to be it get worked! (Y)
Never mind, fixed my radio issue. See http://forum.xda-developers.com/showpost.php?p=56293409&postcount=37
vanir_skomer_4.4.4.101714
I got that one and currently it's syncing but I have no mobile networks. I'm from Finland and I'd like to know what data I should post to help fix it. (I could recompile and all if I get instructions)
__
Your's Mikko A. Liukkonen
Kiil said:
After the newest nightly, camera stopped working. I will downgrade, but here are some details:]
Click to expand...
Click to collapse
Just wanted to confirm with my Vanir nightly of 101714, my camera app crashes too. No problems with radio or networking though.
Cant call, says my phone is currently airplane mode
hello, just installed the latest (vanir_skomer_4.4.4.102814) and now my phone can't find network and says that airplane mode is on when i try to call. Airplane mode button says it's off and kills the bt and wifi if i turn it on, aka goes to real airplane mode.
Fix for this would be more than welcome.
itsesaatana said:
hello, just installed the latest (vanir_skomer_4.4.4.102814) and now my phone can't find network and says that airplane mode is on when i try to call. Airplane mode button says it's off and kills the bt and wifi if i turn it on, aka goes to real airplane mode.
Fix for this would be more than welcome.
Click to expand...
Click to collapse
What's the latest stock update because we are having incompatible installation due to my kernel being based on older release and blobs
Unjustified Dev said:
What's the latest stock update because we are having incompatible installation due to my kernel being based on older release and blobs
Click to expand...
Click to collapse
What do you mean by stock update?
Edit:
Seems like it's working again, it woke up after an hour. Sorry for the trouble.

[Q&A] CyanogenMod 11.0 for Galaxy S4 LTE-A (GT-I9506)

Q&A for CyanogenMod 11.0 for Galaxy S4 LTE-A (GT-I9506)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
rtc clock not working properly
I cant change rtc clock time, I tried -w and -systohc, but nothing
I have 20141013 installed
---------- Post added at 05:58 PM ---------- Previous post was at 04:58 PM ----------
Dsp manager also not working. When I change sound compression it works, but at next song it sounds normal, like if it wasnt activated.
RTC can't be set directly on all newer Qualcomm devices.
DSP Manager most likely will be changed in CM. Anyway its DSP Manager bug and not ROMs itself. So if you want look through CM JIRA and if there no such bug report. You can report it.
solk2 said:
RTC can't be set directly on all newer Qualcomm devices.
DSP Manager most likely will be changed in CM. Anyway its DSP Manager bug and not ROMs itself. So if you want look through CM JIRA and if there no such bug report. You can report it.
Click to expand...
Click to collapse
Ok, I'll report that. I also noticed that recovery backups dont have rtc time. I did some research on the internet and I found something about newer qualcomm devices have recovery time kept in a file in /data/time. I could check this by reading the file time_log.1.
I did know this coz one day recovery bacckups were changed from 1970 to 2014, but with wrong date, so I think I would have to do a full wipe, format data and system and reinstall the rom, I think this could work. I also read someting in the changelog like rtc showing correct or something like this. Maybe same time is kept coz I dont do wipes while installing a new nightly. I really appreciate your work, I love your rom.
It is set to 2014 in kernel. That what Samsung made in KK opensourced kernel. And dont be surprised if it will be set to 2014 next year. Day, month isn't changed forcefully. So thats why you see such date in recovery. While in normal boot mode time_daemon starts and sets date and time. So wipe don't change anything. These RTC changes related to normal boot mode only. Particularly to time_daemon.
And yes, recoveries like Philz support setting correct date.
Ok, thanks
Is screenshot function working for you?
Sent from my A0001 using XDA Free mobile app
Dialer
First of all, thank you for a great ROM. The only problem I have, is when I am calling someone. The screen just goes black. Is there any trouble with the proximity sensor?
When I take the phone away from my ear the screen is supposed to light up right? Mine doesn't do that...
Thanks!
B
Hi, is screen mirroring working with CM11 nightlies?
Gesendet von meinem GT-I9506 mit Tapatalk
Hi!
I've been having an issue ever since I started using one of the first nightlies of this ROM: After a random time both my WIFI and phone signal icons turn orange and the proces Android OS starts draining my battery together with having no signal at all. Turning off WIFI at that point doesn't seem to work anymore but can be done by putting the phone in airplane modes. When I disable airplane modes and have my WIFI disabled I can browser through my phone network but Android OS still drains the battery. After I reboot everything is back to normal, as long as I leave my WIFI off.
- I've installed various nightlies and have had the same problem on all of them.
- I've done both a firmware update and a factory reset of my wireless router: Linksys E2000.
- I've both enabeld and disabled the Google Location reporting.
The problem still occurs and I can (with a random time) reproduce it. If anyone can help me debug or solve this problem that'd be great!
Assuming you have CWM in use as recovery, enter CWM. Do a format on /system from mounts menu. Then do a factory reset. Install latest nightly from SD and voila. That worked for me a while back.
TonskuDaigle said:
Assuming you have CWM in use as recovery, enter CWM. Do a format on /system from mounts menu. Then do a factory reset. Install latest nightly from SD and voila. That worked for me a while back.
Click to expand...
Click to collapse
I'll give this a try and let you know if it helped. Thanks!
TonskuDaigle said:
Assuming you have CWM in use as recovery, enter CWM. Do a format on /system from mounts menu. Then do a factory reset. Install latest nightly from SD and voila. That worked for me a while back.
Click to expand...
Click to collapse
That did not work. Just got the orange icons again.
I'm open to suggestions.
(It's not exactly a question, but since I have less than 10 posts)
Hi, I've installed the 20141106-NIGHTLY yesterday, everything was working great, I updated to the 20141107-NIGHTLY today and now I don't have notification sounds, vibration and light, most of the audio files I select under Notification Sound are detected as Unknown Ringtone, the battery notification light is not working too, I wiped and restored factor settings through recover and installed the 20141106-NIGHTLY but its still the same, changing the color of the light confirms that the notification light is still working but does not activate wen it should.
Nevermind, I cleaned all my setting and reconfigured, it solved the problem
Hi friends, how can we root this ROM?
Thanks
As other users in the thread about solks2 CM11, I am affected by thebrandom reboot thread. I thought it might help to let you know that those reboot often occur when using waze (while charging the phone in my car). Sorry to post here but I do not have the 10 required posts to reply in the right thread.
---------- Post added at 11:08 PM ---------- Previous post was at 11:02 PM ----------
Hello,
I also have a bug when trying to use google now via bluetooth (stuck on a screen with "initializing" written). I tried several workarounds from the internet but without success. Some suggest that a2dp should be disabled but I didn't find an option to disable it... Anyone managed to make google now work with bluetooth?
I am unable to record videos, anyone else having this issue?
EDIT: I just updated to the latest NIGHTLY, still unable to record videos, in a week or so I'll go on vacation for the holidays and I really need to record some videos, so if someone knows whats wrong please help me, thank you
Revolted5 said:
I am unable to record videos, anyone else having this issue?
EDIT: I just updated to the latest NIGHTLY, still unable to record videos, in a week or so I'll go on vacation for the holidays and I really need to record some videos, so if someone knows whats wrong please help me, thank you
Click to expand...
Click to collapse
I accidentally pushed some wrong commits. Will push fix today.
solk2 said:
I accidentally pushed some wrong commits. Will push fix today.
Click to expand...
Click to collapse
Thank you, you're a life saver
EDIT: Back from work and what do I get? An amazing update, I'm finally able to record videos, thank you very much solk2.

Home button not working at all (tried several fixes)

(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro
Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users
Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....
DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.
faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.
can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english
I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also
i've turned to stock i've updated to oxygen 3.0 bet and the button worked again
i think rooting installing twrp and installing different roms may be the cause of this issue
faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.
pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue
faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.
Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.
Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.
For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?
Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max

Stock / Google Dialer and rebooting when trying to make a call?

I've seen this mentioned in other places before, other threads and in the r/motox subreddit, about how the open GAPPS package apparently flashes the Google Dialer over the stock one, and it doesn't work with the Pure? Which is what causes the reboots whenever I try to make a call or, presumably, get a call, which until now I chalked up to random reboots in CM13.
So I've seen a bunch of posts about it, but none that explain how to actually fix it? Am I doing something wrong from the start?
Bonus question, I've been having radio problems on almost every AOSP rom I flash, either Wifi doesn't work upon booting and it persists in other ROMS or cell service is out (even though LTE data works fine). Is the radio (which I assume is the same as the "modem") included in each ROM package and is replaced every time you flash a new one, or does it persist in some system directory cross-firmware?
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
lafester said:
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
Click to expand...
Click to collapse
Set what as default? Or uninstall what? When I look in the apps list all I see is "phone". Nothing under the name google dialer or anything. It's just confusing, I didn't have this problem on other phones.
Sorry for the double post but I figured instead of making another thread I'll continue asking here, I'm STILL having cell issues, no matter what ROM I flash, stock or AOSP, or any of the radios I can find around the forums, whether it be with the February security update or not, I'm still not getting a connection. In fact once I flashed a new modem, I went from not being able to send texts etc. but able to get LTE data, to getting no connection at all. I'm totally lost, this is the second time it's happened I have no idea what to do. Happens in every single rom.
Last time it was fixed once I flashed from stock (which I had in turn flashed to try to get rid of the problem) to CM13 I think. But it was totally random, I have a feeling it didn't even have anything to do with the ROM itself...
Google searching: "Google Dialer reboots when making a call" >
http://android.stackexchange.com/qu...s-when-making-or-receiving-a-call-nexus-6cm13
https://www.reddit.com/r/cyanogenmo...cm_13_nexus_5_soft_reboots_when_a_phone_call/
Even from Open GApps own FAQ page:
https://github.com/opengapps/openga...boots-when-i-receive-or-make-a-phone-call-why
Thanks, I honestly dunno why I couldn't find that before. At first I wasn't even aware it was actually called the "google dialer" so I was just googling "phone app reboots after flash/root/etc" and obviously it wasn't turning up many results. But the stock rom rooted debloated thread had the instructions at the bottom, now I know. Whoops. Like I said, just really confusing coming from other phones where everything mostly just worked....
The baseband is still perplexing me though, in the bootloader under baseband it says <not found>. I'm keeping on trying to flash different stock roms to see if I get lucky.
EDIT: so I think flashing the modem at the SAME TIME as a new ROM might be the key? I think I saw something about that on some random obscure post and tried it out and bam, it worked like a charm. Anyway hopefully that works again when I flash to something new

Can anybody help me

will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.
Unroot, lock and take it back for repairs? Sorry, not very XDA-style answer.
Edit: are you completely sure that you flashed the right stock ROM for your device?
Try again
Alvaro Luna said:
will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.
Click to expand...
Click to collapse
I have a Retla and received official 9.0. download the 89-2 stock firmware. You can find it here. Use the .bat
File, place inside extracted firmware click & when it restarts you should get a notification to download 89-5.. once it completes the next notification will appear.. that's 116-11 9.0..
mod edit - telegram chat spam removed

Categories

Resources