Database Users

Bluetooth Headset w/Media & Phone enabled.

I have been searching for an answer to this for two weeks with no success. I apologize in advance if the question has already been answered… I couldn't find it.
On Sprint's Hero, when setting up a headset (in my case the car radio BT adapter) one can enable both Phone and Media. Supposedly, this should allow a user to listen to tunes/podcasts/Sprint Nav and be able to use the phone when needed through the BT. Unfortunately, it doesn't work this way.
If I'm listening to something on the phone and wish to place a call, I will enter the contact and start the call. The phone responds by pausing the audio program I'm listening to as it should, but I get NO AUDIO from the phone! Nothing! The call is placed and the recipient hears nothing also!
Now; If I'm listening to something and a call comes in, again, as would be expected, the audio program gets paused and the phone rings through the BT. Unfortunately, there is no auto-answer in Android 1.5 (grrr!), so I reach over and press the Answer button. Lo and behold, it answers! but over the phone's speaker and mike instead of the BT!
They refused to accept that it was a problem with the phone at Sprint. Is this fixable? Can I look forward to it working in Android 2.1? Is there anyone else experiencing this problem?

As far as I have read/heard its a known issue that I think one of the roms here may have corrected. I will look around and see if I can find the thread, its been more than a month since I read it. Maybe MoDaCo but again, I will have to track it down.
EDIT:
Personally I wouldn't look towards anything in android 2.1, sprints release could be as far as 6 months away.

I'm currently using MoDaCo's UNOFFICIAL v1.3 ROM. I've tried this with his 1.1 and UNOFFICIAL 1.2 as well. I've also tried Fresh's ROMs without success.

Las_Vegas said:
I'm currently using MoDaCo's UNOFFICIAL v1.3 ROM. I've tried this with his 1.1 and UNOFFICIAL 1.2 as well. I've also tried Fresh's ROMs without success.
Click to expand...
Click to collapse
So maybe no one fixed lol

Poor in-call audio quality

Info in my sig. I was on a previous version of CM (4.2.12.2, iirc) and had no problems. It did run sluggish, but was guessing it was due to my class 2 sd card and using swap/ext/fat32 on it.
I repartitioned my card to all fat32 and loaded 4.2.13 yesterday. It runs much faster, much more responsive than before.
Now, when on a call, it sounds like it's breaking up, like I have bad signal every once in a while. When it would do it, I checked and had 3G and 3-4 bars. I was at my house, where I've never had problems before. This happened both with just the my3g and on a BT headset. Initially I thought it was where I was in the house, but it happened no matter where I went.
I searched and found a thread titled "Background noise" talking about improved call quality. I can't post a link because I'm a no0b, but here's the info, with attached filename Audio-mic-gain-fix.zip:
scheng said:
Is there any way to reduce the background noise of the Magic on the voice call? Will it be improved by updating the latest radio?
Click to expand...
Click to collapse
sombionix said:
You can try this. It has improved my call quality a lot. Follow these instructions using terminal app.
*unzip the files using astro or file manager of your choice*
Open terminal emulator
Type - su (enter)
Type - mount -o remount,rw /dev/block/mtdblock0 /system
Type - mkdir /sdcard/mic
Type - cp /system/etc/* /sdcard/mic
Type - cp /sdcard/download/*.csv /system/etc/ (or whatever directory you unzipped to)
Type - reboot
Click to expand...
Click to collapse
sombionix said:
Are you rooted with a modified ROM? If so, many people have complained about poor call quality, distortion, etc. This file has fixed this problem in many cases. The *'s stand for 'files'. If you call out an * in a command it pulls all files in that directory. However, another example would be *.csv, which would only pull .csv files, or whatever file extension you put after the *. Sorry, hopefully that makes sense.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Since the file is named audio mic gain fix, it seems this is more for the mic gain, not the ear speaker.
Am I having the problem this is intended to fix?
Thx!

If you're having a problem with your ear piece (speaker), I don't think the mic-gain file will help with your situation. The mic-gain file was intended to improve call quality via the microphone. Some users were claiming that the people they were calling said they could hardly hear them or that there was distortion and background noise.
I don't believe there have been any reported issues with the ear piece using any Cyanogen ROMS, but I could be wrong. Sounds more like a hardware issue. One way to test is to downgrade to a previous ROM and see if you still have the issue. If so, more than likely, its a hardware problem.
Good luck!

That's kinda what I figured. I'll continue using it to see if I still have probs. If so, I'll try a different ROM.
thx for the infoz.

This might not help but I had the same problem when updating from 4.2.5 to 4.2.13. It was fine on 4.2.5 and had a little background noise frequently. But once I upgraded to 4.2.13 calls were horrible all the time, the person could barely hear me. I decided to do a warranty exchange and unrooted it. Calls were fine once I was on stock 1.6, still had some background noise but not on all calls.
Got my replacement the next day, rooted straight to 4.2.13 and had no problems cept for the background noises every now and then.
I have a MyTouch3G as well.

Weirdkid said:
This might not help but I had the same problem when updating from 4.2.5 to 4.2.13. It was fine on 4.2.5 and had a little background noise frequently. But once I upgraded to 4.2.13 calls were horrible all the time, the person could barely hear me. I decided to do a warranty exchange and unrooted it. Calls were fine once I was on stock 1.6, still had some background noise but not on all calls.
Got my replacement the next day, rooted straight to 4.2.13 and had no problems cept for the background noises every now and then.
I have a MyTouch3G as well.
Click to expand...
Click to collapse
Maybe I'm misunderstanding, but are you saying that you exchanged your phone to fix your problem? I highly doubt that the Cyanogen ROM you had installed caused a hardware problem. Could have possibly caused a glitch if you didn't install it correctly. However, you should have just wiped everything and tried again. Or, if you were really feeling up to it, started from scratch by unrooting in fastboot with the SAPPIMG.nbh, then rooting again with the recovery image and ROM of your choice.

fwiw, I did a wipe, reformated the sdcard, and a fresh install of CM 4.2.13.
I have a feeling it was just poor reception at the time. I don't talk on the phone that often, but used it today for about 5 mins and it seemed fine. I was riding in a car and background noise was loud (my buddies arguing over steroids & McGwire, lol), but the guy on the other end had no probs hearing me.

Glad to hear you got it fixed.

Sorry, I guess that was out of context. That was @Weirdkid, stating that I didn't do an upgrade like he did. I haven't touched it since yesterday, I wanted to let roll to see how it plays out.

sombionix said:
Maybe I'm misunderstanding, but are you saying that you exchanged your phone to fix your problem? I highly doubt that the Cyanogen ROM you had installed caused a hardware problem. Could have possibly caused a glitch if you didn't install it correctly. However, you should have just wiped everything and tried again. Or, if you were really feeling up to it, started from scratch by unrooting in fastboot with the SAPPIMG.nbh, then rooting again with the recovery image and ROM of your choice.
Click to expand...
Click to collapse
Not quite, I was already getting static every now and then even before root(I thought I could live with it). It was just a little glitch I guess and that pushed me to get an exchange. After the unroot and back to Donut, the glitch with all calls getting low quality was gone but still getting minor static noise every now and then(just like before). Sorry for the confusion.

Okay, so I continued to have poor call quality and 3 calls were dropped. I went back, did a full wipe, no swap/ext, and reloaded CM4.2.13 and had the exact same problems.
I decided to load Dwang's rom and no longer have the problem of dropped calls and/or poor call quality.

cougar694u said:
Okay, so I continued to have poor call quality and 3 calls were dropped. I went back, did a full wipe, no swap/ext, and reloaded CM4.2.13 and had the exact same problems.
I decided to load Dwang's rom and no longer have the problem of dropped calls and/or poor call quality.
Click to expand...
Click to collapse
Yeah, I stopped using Cyan's ROM when the 4.2.10 release came out. Great ROM, just seemed to have increasing issues after 4.2.9. You should try the Super D rom. Fastest and most stable ROM I've run, hands down.
http://forum.xda-developers.com/showthread.php?t=613809

Thanks for the the recommendation, I was looking at that one, but haven't changed my SPL. No reason, just haven't ventured down that road yet.
I've been looking at the 10mb ram hack, searching for pros/cons, but just see people using it and no full explanation of it.
Is there any real benefit to it, and what does it actually do?

cougar694u said:
Thanks for the the recommendation, I was looking at that one, but haven't changed my SPL. No reason, just haven't ventured down that road yet.
I've been looking at the 10mb ram hack, searching for pros/cons, but just see people using it and no full explanation of it.
Is there any real benefit to it, and what does it actually do?
Click to expand...
Click to collapse
Not a problem. Also, if you have a mt3g, you don't need to upgrade your SPL to run the Super D rom. Aside from that, just make sure you have the correct radio, then do a full wipe and flash the ROM.
In regards to the 10mb ram hack, it definitely increases system speed and performance. So that would be your 'pro'. However, the ram hack is created by pulling 10mb of ram that would normally be used for graphical processes, and instead applies it to your operating system. The con would be a decrease in 3d game performance. So, if you play a lot of 3d games, then I wouldn't recommend the 10mb ram hack. If you don't, then use it. Currently, the only Super D rom you can download that doesn't have the ram hack is the 1.6.6 beta, which as of right now is fairly stable. However, If you are considering switching to this rom, just wait a couple days, the developer has announced that he is releasing the 1.7 stable version this week. I'm assuming he will have two separate downloads. One with the ram hack, and one without.

Btw, I didn't see your phone setup before my last post. You DO have the correct radio to run the Super D rom. So, all you have to do is a full wipe and flash the rom.

Nice! I forgot I was reading the page in the Dream/G1 section...I got this one how I like it, so I'll roll with it a few days and keep an eye out for Super D 1.7.

Status/Quality of CM7.2

For a number of reasons, I'm thinking of rooting my Droid R2D2 and installing CM7.2. Given that I'm on 2.3.4 and the hoops required to root it, I would love it if someone could verify that the following features all work on their Droid2 or R2D2 with CM7.2. I haven't been able to find a consolidated list of what does or doesn't work on this particular phone. I'll update this post with reported statuses as people respond for others to use as a reference.
Comments in blue are consolidated feedback from others. Comments in green are my own experiences after taking the plunge.
Phone calls: Yes Confirmed
3G Data: Yes Confirmed
WiFi: Intermittent. Sometimes people have to reboot every time you toggle, but not everyone has this issue I've noticed sometimes when on WiFi I lose all data connectivity. Disabling WiFi sometimes fixes it, but not always. Rebooting seems to do the trick every time though.
GPS: Yes Confirmed
Phone-over-Bluetooth: Yes Confirmed
Stream Audio over Bluetooth: Yes, possible lag entering menus/rotating screen/unlocking due to using power amp Pandora works fine for me
Still Camera: Yes Confirmed
Video Camera: Yes Confirmed
Physical Keyboard: Every key except 'ALT LOCK' Confirmed
Motorola Desktop Dock detection/integration: Yes, though it doesn't seem to remember that I've hit the brightness/dim button between inserts as it used to when on stock.
Motorola Car Dock detection/integration: Yes
SMS/MMS (I use Google Voice for most of my SMS needs, but for sake of completeness):Yes SMS - yes. MMS - haven't tested.
In addition, if you could address the following, that would be great: One of the reasons I want to get rid of the installed firmware is because of a strange problem I have when I stream audio over bluetooth to my car. The problem is: when I'm streaming audio, and only when I'm streaming audio, if I use my car's steering-mounted controls to initiate a phone call, it seems to sever the bluetooth connection with the phone. I have to manually re-connect the car to the phone (not re-pair, just re-connect). When I'm not streaming audio, using the steering wheel-mounted controls don't cause the sever to occur. I use both Pandora and iHeartRadio, and have seen the same problem in both apps. Using the iOS version of the same apps on my work-issued iPhone don't have the problem, so I don't think it is an problem inherent with my car, I think it is an issue with the Android installation. If switching to CM7.2 suffers this same problem as the official 2.3.4, it wouldn't be worth the effort to me to switch. But if it DOES fix the problem ... I might be more forgiving if everything in the above list doesn't work fully. I still suffer the same problem.
Thanks in advance!
Other things I've noticed:
Airplane Mode: I've noticed that trying to trigger Airplane Mode doesn't seem to work properly. When I attempt to trigger it, nothing appears to happen. If I then reboot the phone, I see the airplane icon in the status bar, data doesn't work (as one would expect when in Airplane Mode), but the Bluetooth icon is visible, as if Bluetooth were still turned on. Attempting to turn off Airplane Mode also requires a reboot.
Lock Screen: Initially, changing the settings for the lock screen worked just fine. Now, for some reason, the settings don't seem to "stick" ... I set them, but they have no effect. But, if I then reboot, the settings that I tried to set take effect. So they are being persisted somewhere, somehow ...​Airplane Mode and Lock Screen: Originally I noticed the two above items. I just did a factory reset of the phone (Settings --> Privacy --> Factory data reset), and the problems went away. Airplane Mode seems to work properly, and the Lock Screen settings update as expected, just like when I first installed CM. I didn't do all that much previously, so I can't imagine what broke these the first time, but if I happen to recreate the problem and isolate the cause I'll mention it here.
ADW Launcher: When Cyanogenmod first booted up, I couldn't add, move, or remove anything from the default home screens by long-pressing. The haptic would trigger, so I know it was recognizing the presses. By going through the ADW settings and choosing simply to restart ADW, everything started working fine.
Lock Screen: I love the flexibility and customization it allows. At first though, I thought it wasn't showing the time/date of the next upcoming alarm. Then I realized that by disabling the "show next calendar event" feature, it would show up in the same place that the calendar event was otherwise appearing in.
It's fast!: The phone feels MUCH more responsive than when I was on stock.

Phone calls: Yes
3G Data: Yes
WiFi: Intermittent. I have to reboot every time you toggle, but not everyone has this issue.
GPS: Yes
Phone-over-Bluetooth: Yes
Stream Audio over Bluetooth: Never tried
Still Camera: Yes
Video Camera: Yes
Physical Keyboard: Every key except 'ALT LOCK'
Motorola Media Dock detection/integration: Never tried
Motorola Car Dock detection/integration: Never tried
SMS/MMS (I use Google Voice for most of my SMS needs, but for sake of completeness): Yes. I use both also
jlitowitz said:
In addition, if you could address the following, that would be great: One of the reasons I want to get rid of the installed firmware is because of a strange problem I have when I stream audio over bluetooth to my car. The problem is: when I'm streaming audio, and only when I'm streaming audio, if I use my car's steering-mounted controls to initiate a phone call, it seems to sever the bluetooth connection with the phone. I have to manually re-connect the car to the phone (not re-pair, just re-connect). When I'm not streaming audio, using the steering wheel-mounted controls don't cause the sever to occur. I use both Pandora and iHeartRadio, and have seen the same problem in both apps. Using the iOS version of the same apps on my work-issued iPhone don't have the problem, so I don't think it is an problem inherent with my car, I think it is an issue with the Android installation. If switching to CM7.2 suffers this same problem as the official 2.3.4, it wouldn't be worth the effort to me to switch. But if it DOES fix the problem ... I might be more forgiving if everything in the above list doesn't work fully.
Thanks in advance!
Click to expand...
Click to collapse
Does it do this with your standard music app while playing music off your SD card?
Your logic seems sound enough, but you assume Android is a perfect OS. It might just be the way Pandora and iHeartRadio are designed to handle that situation in the Android operating environment and it might just be a bug across 2.3.4. My suggestion to you would be to try these same exact things with a couple DIFFERENT Android phones (a friend's, the wife's, etc.) to see if that's just how it plays out within the Android OS. Worst case scenario, that's just a problem with the apps themselves and you write an email to them asking for an update with a solution.
Sent from my DROID2 using xda premium

Thanks for the info!
pomeroythomas said:
Does it do this with your standard music app while playing music off your SD card?
Click to expand...
Click to collapse
You know, that's a really good thought that I haven't tried yet.
pomeroythomas said:
Your logic seems sound enough, but you assume Android is a perfect OS. It might just be the way Pandora and iHeartRadio are designed to handle that situation in the Android operating environment and it might just be a bug across 2.3.4. My suggestion to you would be to try these same exact things with a couple DIFFERENT Android phones (a friend's, the wife's, etc.) to see if that's just how it plays out within the Android OS. Worst case scenario, that's just a problem with the apps themselves and you write an email to them asking for an update with a solution.
Click to expand...
Click to collapse
Sadly, everyone that I know is an iPhone fanboy. I'm the only one with an Android-based phone!

I'm also aware that the ROM has baked-in support for Motorola's media and car docks, though I don't own one to tell you how well it works. I assume its the same code, just stolen from source, and I've NEVER seen anyone complaining about it on Gingerbread. Maybe head over to the Droid 2 Accessories part of the forum and see if there are any complaints.
Sent from my fully flashed cricKet Droid 2 on CM7.2 using xda premium

Per your advice, I ran a couple of more tests, and found the following. In addition to severing the bluetooth connection when streaming audio from Pandora or iHeartRadio and using the steering wheel-mounted controls to initiate a phone call, the bluetooth connection also gets severed in the same manner when streaming sound from YouTube.
Interestingly, it does NOT sever the connection when streaming audio from the local media player or through Play Music when streaming over 3G. However, even in this circumstance, if I hit the steering wheel "Mode" button to switch to AM/FM, it severs the bluetooth connection. If I recall from past tests, this also would also sever Pandora/iHeartRadio, though I didn't repeat that this morning.
So ... it's not just Pandora or iHeartRadio, but some of Google's own software, though sometimes only when switching radio modes and not always when placing a call.
Is anyone out there running CM7.2 connected to a car and able to verify whether the same problems plague CM7.2 as stock 2.3.4?

2.3.4 and the hoops required to root it,
Click to expand...
Click to collapse
it's not that difficult, just need a decent pc
download iso file (50mb),
mount image to cd, dvd, or usb drive
reboot pc to drive
run program, read onscreen instructions, takes about 10 mins or less
wipe cache, reboot
done your rooted
just know how to boot to bootloader and recovery, read http://droid.koumakan.jp/wiki/Welcome
written for d2G, but same steps

Stream Audio over Bluetooth: Yes, possible lag (music pausing/skipping for a split second ) entering menus/rotating screen/unlocking but maybe because I am using power amp or the kernel that I am using
Dock: There is a dock menu in settings that looks to be specific to this phone (as in I have not seen it on other cm7.2 phones) so it may work
Edit: FYI I had a fun (hard) time getting from stock (froyo) to CM7.2. I had to flash the stock (gingerbread) before I could get to 7.2 (Someone here provided me the file to flash which I may be able to dig up)

Well, I hooped myself crazy, am rooted and on 2.3.4 - and the CM7.2 install script still honks that I'm not on the right version.
Anyone else seen this one?
(I realize I'm a little late to the game - I just got a D2 off of craigslist...)

rprussell said:
Well, I hooped myself crazy, am rooted and on 2.3.4 - and the CM7.2 install script still honks that I'm not on the right version.
Anyone else seen this one?
(I realize I'm a little late to the game - I just got a D2 off of craigslist...)
Click to expand...
Click to collapse
You may need to tweak the Cyanogenmod installer. See the following post for instructions on how to fix. Copying/pasting the instructions here for reference. This worked for me. I ran CM7.2 for quite a while, but eventually got rid of it due to my R2D2 having WiFi issues under CM7.2 (it would sometimes stop having internet connectivity over WiFi, and the only way to fix the issue was to reboot).
http://rootzwiki.com/topic/29930-ne...2-found-droid2-r2d2/page__st__110#entry849398
GregMoens said:
Look like you're failing the check_kernel script. This was put in place to prevent someone with a Froyo based kernel from flashing a CM version that required the Gingerbread kernel. If you open up the cm-7.2.0-droid2.zip file and look at /system/etc/check_kernel, you'll see that the required kernel version is 2.6.32.9-gca08d89, which matches my Droid2 exactly. I'm assuming your version does not match. That 2.3.4 update must have bumped the kernel version. This new kernel may or may not work with CM7.2.
Couple options I can think of. You could change the required version in the check_kernel script. Or you can blank out that entire file and replace it with:
#!/sbin/sh
exit 0
You could also edit the main update script found under /META-INF/com/google/android/updater-script and delete this line:
assert(run_program("/tmp/check_kernel") == 0);
Just make any of those changes, repackage the zip file, and try flashing that. You could very well get stuck in a bootloop due to the new kernel being incompatible and you may have to SBF back to rooted 2.3.4 and live with that for now. Good luck!

based on that post from GregMoens
I've written more detailed instructions here
[How To] Remove Kernel Check on a Rom
---------- Post added at 11:58 AM ---------- Previous post was at 11:54 AM ----------
I have also removed kernel check from a couple of roms, and posted links in my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs

speakerphone software problem - really low

even though no one seems to suffer from that problem, i must ask again-
the problem is a low volume while talking on the phone using the speaker. THEN AND ONLY THEN.
it's working perfect while playing videos, games or music. there are no complaints from the other side of the conversation. no problem while talking with headphones or w/o other devices. nothing. only on my end.
it's probably not a matter of hardware because a lab switched my speaker with another one's and mine worked perfectly on his and his didn't on mine. (same problem that is)
ALSO, i've already updated twice 7.0.1-->7.1.0-->7.1.1 and no changes.
I've already factory reseted, wiped all, cleared cache and data, and did everything i could think of, but burning the damn thing.
the ONLY conclusion i got to (me and the lab) is that there's a code or other software glitch that limits the volume.
PLEASE THINK OR TRY TO FIGURE THIS PROBLEM OUT

I got a similar problem like you.
The RECEVIER doesn't work while talking on the phone.
But the speaker works perfect.
Weirdly the RECEIVER works perfect when I use the other APPs like Wechat to listen some voice messages.
PLEASE THINK OR TRY TO FIGURE THIS PROBLEM OUT

domuzy said:
even though no one seems to suffer from that problem, i must ask again-
the problem is a low volume while talking on the phone using the speaker. THEN AND ONLY THEN.
it's working perfect while playing videos, games or music. there are no complaints from the other side of the conversation. no problem while talking with headphones or w/o other devices. nothing. only on my end.
it's probably not a matter of hardware because a lab switched my speaker with another one's and mine worked perfectly on his and his didn't on mine. (same problem that is)
ALSO, i've already updated twice 7.0.1-->7.1.0-->7.1.1 and no changes.
I've already factory reseted, wiped all, cleared cache and data, and did everything i could think of, but burning the damn thing.
the ONLY conclusion i got to (me and the lab) is that there's a code or other software glitch that limits the volume.
PLEASE THINK OR TRY TO FIGURE THIS PROBLEM OUT
Click to expand...
Click to collapse
Did you try and run the phone in safe mode to rule out a third party app causing the problem? If that makes no difference you could either do a clean install of the latest Android image or if the phone is under warranty try and contact Google or Huawei for support.

didn't try safe mode. will try now. already contacted huawei, no response yet
jhs39 said:
Did you try and run the phone in safe mode to rule out a third party app causing the problem? If that makes no difference you could either do a clean install of the latest Android image or if the phone is under warranty try and contact Google or Huawei for support.
Click to expand...
Click to collapse
THANK YOU

nooooooooo
jhs39 said:
Did you try and run the phone in safe mode to rule out a third party app causing the problem? If that makes no difference you could either do a clean install of the latest Android image or if the phone is under warranty try and contact Google or Huawei for support.
Click to expand...
Click to collapse
unfortunately, safe mode didn't help, so it's probably not an app that blocks it.
is there a good confirmed link to a guide of a clean install?
my 6p is not rooted, if it matters

[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.