Database Users

Found EASY gps fix

so as many of us here i had the gps problem, and i started to not care anymore. The other day after i flashed Trigger 3.2, i also flashed some useful apps like SGS tool, spare parts etc. As i was going over those apps, i went to SGS tools, and noticed GPS fix all the way at the bottom. I decided to give it a try but didnt think it would work. I clicked and then select north-america.... and apply.
And surprisingly my GPS has been working perfectly fine since then.
So those of you who still have gps problem, try that
Hope this help

Djapatos said:
so as many of us here i had the gps problem, and i started to not care anymore. The other day after i flashed Trigger 3.2, i also flashed some useful apps like SGS tool, spare parts etc. As i was going over those apps, i went to SGS tools, and noticed GPS fix all the way at the bottom. I decided to give it a try but didnt think it would work. I clicked and then select north-america.... and apply.
And surprisingly my GPS has been working perfectly fine since then.
So those of you who still have gps problem, try that
Hope this help
Click to expand...
Click to collapse
This has been posted before, it works for some people and it doesn't for others. Just like every other GPS fix out there. Not trying to be rude and I'm sure everyone appreciates you trying to help, but duplicate threads just create clutter. Once again I am not trying to be rude so please do not take it that way.

flashing the S.gps is the easiest way as I know

This is kind of random, but did anyone notice that the latest Kies update fixes/helps GPS?
With KA6, I have to manually set GPS mode to MS-Based and change the supl settings before I get a quick lock. With KB5, it works very well right out of the box. No configuration needed.

ooooohhhh
mugenfiji0327 said:
This has been posted before, it works for some people and it doesn't for others. Just like every other GPS fix out there. Not trying to be rude and I'm sure everyone appreciates you trying to help, but duplicate threads just create clutter. Once again I am not trying to be rude so please do not take it that way.
Click to expand...
Click to collapse
ooops i didnt know, wel anyways that works for me

[Q] Searching For Gps problem. HELP!!

I have seen multiple threads on this subject for every other phone but none for the Nexus. Ever since i updated to CM 7.0.2 my gps hasnt worked properly. It locks in on my position and others in latitude very quickly, but if i try to use navigation it stays stuck on searching for gps. When i attempted to use the app gps status to check out the problem, it keeps loading and never finds any satellites. I posted in a g2 thread and the response i got back was this:
"You need to find out what partition on your phone the radio/gps cache is stored. Wipe it. That is the same type of idea of what we are doing here. Hopefully that helps get ya going in the right direction. I would also recommend trying to back it up first if you can. I'm also sure some dev with the know how could write a very easy script for you so that you can't mess it up. But it would obviously have to be someone familiar with the nexus setup. Good luck!"
can anybody help???

I wish I could ban people for this.
WARNING - DO *NOT* POST QUESTIONS IN THIS FORUM - only tips/info/etc.

dont kill me man my bad. really need the help tho. ill try this question in the correct forum as well.

[Q&A] [ROM][AOSP] Google Edition S4/ Pure Nexus Edition[SAFESTRAP] Oct 4th.14

Q&A for [ROM][AOSP] Google Edition S4/ Pure Nexus Edition[SAFESTRAP] Oct 4th.14
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:

Thanks Joe! And a question.
First off, I want to thank Joe for all his hard work! Ever since I upgraded from the S3 to the S4 I have been missing CM for their lack of bloatware more than anything else. Found this just over a week ago, installed it and haven't looked back at TouchWiz ever since!!! Everything works great but I have a small issue I am hoping someone can help me with, I have tried using GravityBox and a separate Xposed module to have a different picture on the lock screen but all I ever get is a black background. If anyone has any ideas I would love to hear them. Thanks again Joe for all your hard work and I am sad to hear you will be moving on. Was hoping to see some of that Lollipop goodness but I understand that hobbies can only take so much of your time. Good luck with your S5 work!

salpsuc said:
First off, I want to thank Joe for all his hard work! Ever since I upgraded from the S3 to the S4 I have been missing CM for their lack of bloatware more than anything else. Found this just over a week ago, installed it and haven't looked back at TouchWiz ever since!!! Everything works great but I have a small issue I am hoping someone can help me with, I have tried using GravityBox and a separate Xposed module to have a different picture on the lock screen but all I ever get is a black background. If anyone has any ideas I would love to hear them. Thanks again Joe for all your hard work and I am sad to hear you will be moving on. Was hoping to see some of that Lollipop goodness but I understand that hobbies can only take so much of your time. Good luck with your S5 work!
Click to expand...
Click to collapse
Which rom are you using right now? I heard there's an issue with GB while on the gpe version. You might have to do a nandroid backup and try out pure nexus as others users reported GB working with no issue for them. And sometimes after applied a tweak, you must restart your phone to take affect.

salpsuc said:
First off, I want to thank Joe for all his hard work! Ever since I upgraded from the S3 to the S4 I have been missing CM for their lack of bloatware more than anything else. Found this just over a week ago, installed it and haven't looked back at TouchWiz ever since!!! Everything works great but I have a small issue I am hoping someone can help me with, I have tried using GravityBox and a separate Xposed module to have a different picture on the lock screen but all I ever get is a black background. If anyone has any ideas I would love to hear them. Thanks again Joe for all your hard work and I am sad to hear you will be moving on. Was hoping to see some of that Lollipop goodness but I understand that hobbies can only take so much of your time. Good luck with your S5 work!
Click to expand...
Click to collapse
In gravity box switch background mode from overlay to underlay. That's what worked for me.

Google Wallet
Has anyone gotten Google Wallet to work? When i setup tap to pay, it says its not the default, but in phone setting, its thr only option. Anyone know how to fix it?
-Todd

How to Pure Nexus on SGH-1337M
Hello,
I have the SGH-I337M with bootloader I337MUMUAMDJ and with TWRP recovery, I'd like to install this Pure Nexus but I don't know what to chose when it comes to the modules.
Has anyone installed this or can anyone provide me some advice?
Thanks,

OMG I am LOVING the Pure Nexus rom on my S4!!!!! I just want to say that this was my first Android experience and was going to be my last until I stumbled upon xdadevelopers and this ROM a few days ago. I originally switched from an iPhone (which was hard enough) but when I got my brand new S4 I couldn't believe how slow and laggy it was, thanks to ATT apps and touchwiz, my phone with all these great specs could barely keep up with MMS messages and was lagging just scrolling thru my contact list!!??! :/
So anyways, I was ready to move back to the Apple side of the world before I decided to give this ROM a try and after installing the Pure Nexus rom all i can say is... WOW!!! I think i'm finally falling in love with this device 1.5 years later. This is exactly how the S4 should be stock from all carriers!! Pure, clean, fast and functional!! very impressed! Awesome work Joe!!

[ROM] Pure Nexus for SGH-I337M
Arilou said:
Hello,
I have the SGH-I337M with bootloader I337MUMUAMDJ and with TWRP recovery, I'd like to install this Pure Nexus but I don't know what to chose when it comes to the modules.
Has anyone installed this or can anyone provide me some advice?
Thanks,
Click to expand...
Click to collapse
I believe I was in the wrong forums, I found GOOGLE EDITION 4.4.4 by Danvdh, Kryten2k35 & Ktoonsez and I believe it is meant for SGH-I337M so I'll give it a try.

Also, I did have one question, is there any work around yet for being able to connect this to a PC via USB and being able to transfer files? Again, I'm on ATT NC1 using the Pure Nexus Rom.
Any help would be appreciated, thanks!

thatwasntnice said:
Also, I did have one question, is there any work around yet for being able to connect this to a PC via USB and being able to transfer files? Again, I'm on ATT NC1 using the Pure Nexus Rom.
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
No. Look into airdroid or the app in the OP. There will be no work around unless our bootloader gets unlocked, from what I understand it's a kernel problem and there's no real way to fix it without flashing a kernel

Rhymey said:
No. Look into airdroid or the app in the OP. There will be no work around unless our bootloader gets unlocked, from what I understand it's a kernel problem and there's no real way to fix it without flashing a kernel
Click to expand...
Click to collapse
Airdroid is really good, thanks Rhymey!
I couldn't get Multi Mount SD-card lite to work though, even after checking off MTP fix... like it shows up in my file explorer as a drive but everytime I click it, it says "please insert disk"... not sure why?

thatwasntnice said:
Airdroid is really good, thanks Rhymey!
I couldn't get Multi Mount SD-card lite to work though, even after checking off MTP fix... like it shows up in my file explorer as a drive but everytime I click it, it says "please insert disk"... not sure why?
Click to expand...
Click to collapse
no idea there, i just use airdroid haha

I use the GPE ROM on safestrap nb1. Does anyone experience random "No Service" problem? It 2as working fine for few weeks and the next morning there is no service but my brother's phone(same att as me, stock) has se4vice. Thankfully i reflashed the rom and it came to normal. Will this recurr?

Adding tiles to drop down menu?
Greetings all,
Is there a way to add more tiles to the menu? Where the Brightness, Settings, Wifi, Network, Battery Life, Airplane Mode, Bluetooth and Location settings are? I'd like to have to customize this a bit if possible.
Thanks!

zodiacs123 said:
Greetings all,
Is there a way to add more tiles to the menu? Where the Brightness, Settings, Wifi, Network, Battery Life, Airplane Mode, Bluetooth and Location settings are? I'd like to have to customize this a bit if possible.
Thanks!
Click to expand...
Click to collapse
You need to install Xposed Installer and GravityBox KK Modules.

Cannot see internal storage
Hello,
After flashing this ROM, I can't see all of my internal storage. Is there an easy fix for this?

Wifi difficulties on Google Play Edition ROMs for I337UCUFNI1
Hello, I followed the instructions for the SafeStrap installation of various Google Play Edition ROMs on my Samsung Galaxy S4, NI1 found here:
http://forum.xda-developers.com/showthread.php?p=53758259#post53758259
I successfully booted into working installations for all of them (Pure Nexus Edition, Google Edition for SafeStrap v1.1, & S4 Google Edition for SafeStrap. The phone could receive 4G LTE, but could not turn on Wifi. It became stuck on "Turning Wifi on..." & never progressed elsewhere. I performed all manner & combinations of hot reboots & full reboots, with no luck.
I also tried flashing different ATT modules.zip from NB1 & NC1, none of which changed anything.
In http://forum.xda-developers.com/galaxy-s4-att/development/rom-google-edition-s4-t2837239/post55466895#post55466895
I also saw that in addition to hot/soft reboots, trying go enter/exit airplane mode may also get wifi back up again. This too failed. I'm utterly confused how hot reboots & this airplane mode fix worked for so many others.
Anyone else had luck with fixing wifi?

Requesting advice/help. I just flashed this rom and have experienced two data drops already within 30 minutes of me using the rom. What should I do to fix this?

also...just tried to install chrome from the play store. When I open chrome my phone immediately vibrates 3 times very quickly, and says "unfortunately chrome has stopped". Ive tried clearing cache/data and uninstalling, neither worked. Did I forget to do something when I flashed this rom? other weird stuff has been happening like I rebooted my phone one time and the wifi wouldn't even turn on and I had to reboot again to get it working.

Every time you cold boot, you need to do a hot reboot to get wifi working.
Sent from my GT-I9505G using XDA Free mobile app

Samfail root success and workarounds

I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.

dirtydodge said:
I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.
Click to expand...
Click to collapse
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:

jcrompton said:
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:
Click to expand...
Click to collapse
Yea i never video or WiFi call (ok maybe have yo WiFi call about 2 or 3 times a year) so losing those two things don't bother me. I've always turned off enhanced lte services since they introduced it simply because it drains more battery plus from what I've googled about it, it don't really pertain to anything i need. I am hopeful though that once people start to use this root method, we'll start to figuring out how to fix everything like normal.

I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method? I mean there are a few fun things to do but not worth a unstable system and 80% battery.

timmy10shoes said:
I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method?
Click to expand...
Click to collapse
Why do you say "it's not really root to begin with"? By doing this method you gain access to root files and to the heart of your phone. SuperSU installs and works, you are able to deodex, theme, modify all as you want if you know what your doing. Sure there are a few issues with it (battery limited to 80%, WiFi calling, and camera) but none of this will get fixed we work on finding out the issue, but root has always brought about some type of issue one way or another in locked bootloader devices. My plan with rooting my phone is to build my rom with the tweaks and mods that i like, run the ad blockers that i like, possibly install xposed (haven't used it in a while). One of the main purposes of root in my opinion is to make your phone the way you like it. I mean you can sit around and wait for someone to make the phone how they like it and then possibly share it with others or you can take the initiative to learn yourself. Not really root to begin with? It's root, just not how it used to be. I hope someone does figure out a different root method that don't render the battery to 80%, i wish i knew how to look for exploits (I'm currently trying to learn) but until then, this is what we have. What are your reasons for believing this is not a real root method?

timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
Click to expand...
Click to collapse
Well that's why I'm still hoping for a different root method they don't have to use leaked files. But i can say that this root method runs a lot smoother than the method we had to use in the S7. This method hasn't been out very long, but is say within the next few months we'll start seeing more development happening . Or at least i hope. I've just recently started making my own roms (i don't release them to anyone being as I'm still learning and can't give a lot of trouble shooting assistance) but it's fun for me to pass the time at work. (I have a real laid back job with nothing to do a lot of times lol)

I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.

timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.
Click to expand...
Click to collapse
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.

I have developed a few roms myself for the Bionic and Razr. Its highly entertaining and I want it myself but there hasn't been true root since the note 3 I believe.
---------- Post added at 04:54 PM ---------- Previous post was at 04:53 PM ----------
dirtydodge said:
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.
Click to expand...
Click to collapse
I use unactivated devices. There is a ton on trial and error so I don't use my daily driver for that.

Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?

Don_Pachuco said:
Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?
Click to expand...
Click to collapse
No roms yet (on AT&T at least that i know of). Not trying to be rude but do you even search, see attached picture. Literally 4 post down from this thread.

I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.

Don_Pachuco said:
I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-note-8/how-to/n950u-odin-5-files-stock-firmware-t3715770

Help!!! Please help!!!!
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear

jforest3026 said:
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear
Click to expand...
Click to collapse
This is a thread for mods done after rooting, post questions about getting rooted in your root thread please.
https://forum.xda-developers.com/ga...nt/root-samfail-galaxy-note8-t3685340/page323

the %80 max battery issue
I've enjoyed a rooted Note 8(sm-n950u) Nougat7.1.1 for over a week via samFAIL method and am quite thankful to the samfail/pwned team for providing it.
The max battery issue is the only drawback as far as I've noticed so far. I have a nice and speedy phone that is devoid of bloating apps, and vendor/carrier garbage.
As far as the max battery issue, I've done some digging and haven't found a cure yet.
I've noticed a couple things.
in /efs/Battery and in /sys/class/power_supply/battery there is a file named batt_capacity_max that has something to do with the max battery limit which is obvious by name of course.
Notes:
1. You can not change the value in /sys/class/power_supply/battery/. You can edit and write the file without any error or sign of failure; But checking the file immediately afterwards, you'll find that the contents did not change.
2. You can change the file in /efs/Battery/, but the contents are reset upon reboot.
3. The file contains only a number.
In my case, batt_capacity_max contains the number 1000 regardless of the charged state. i.e. It is 1000 when the phone if charged to max, and it is 1000 when the phone is nearly drained.
I change the value to see if it has any effect, and it does.
I interpreted the 1000 as binary 8, and changed to number to 1010 (binary 10). Then I charged the phone only to find that I could not charge the phone past 17% eep! This wasn't a problem though as rebooting the phone or returning the file to its original value restored the function to normal(rooted normal, that is..max 80%).
I've also deleted the file, then charged the phone to find that there was no effect.
I then came across a slightly older xda thread charge to 100 snapdragon root(s8 sampwn)
The thread had a great number of contributors and provided a great deal of background info, but the method described therein has become obsolete or does not apply to the Note 8 i believe.
If anyone has discovered anything effective regarding the battery max limit, I hope they will contribute that info here, or at least link to an existing thread that I may have missed.
One thing I would like to understand is what processe(s) are being employed in this battery limit system. Is it merely a sub-function of the SafetyNet, or something else? I've filtered what I believe are the pertinent logs(dmesg and logcat) trying to find reference to batt_capacity_max but have come up empty.
I have't tinkered with this in a couple days, but I plan to get back to it tomorrow. Anyone has ideas or suggestions, please contribute. personally I don't really care wether I "fix" this issue as much as I am using this pursuit to glean a better understanding of the android/samsung subsystems relative to it. .. to fix it, of course, is ideal.

delete

[SOLVED] Weird Phone app behaviour when trying to make a call on custom ROMs GT-I9506

Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.

If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.

DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?

henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?

DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads

Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.