Issue with incoming calls - OnePlus 3T Questions & Answers

After upgrading (dirty flashed) to OxygenOS 5.0.5 & OxygenOS 5.0.6 from Nougat (OxygenOS 4.5.1), in the incoming calls screen doesn't appear the toggle to pick up the phone , just the caller name and number, I have to slide down the notifications bar to be able of picking up the call. Do you know how to solve this?

Factory reset - major Android upgrades require that to avoid issues

Many thanks for your answer but I'd prefer to find the root cause of the issue.

spaniard said:
Many thanks for your answer but I'd prefer to find the root cause of the issue.
Click to expand...
Click to collapse
The root cause is that you dirty flashed.
Seriously, if you have random bugs after dirty flash, the most likely solution is to clean flash or wipe data.

spaniard said:
Many thanks for your answer but I'd prefer to find the root cause of the issue.
Click to expand...
Click to collapse
The root cause is the incompatibility between major upgrades and doing such upgrade very often introduces weird bugs.
This probably wouldn't be the cause if upgraded like from Android 8.0 to 8.0.1 (just an example), but not 7 to 8.
Every manufacturer, if asked for support, will ask you to reset your device to default and check if problem persists.

Thanks guys, I know that and I think that this is the most probable solution, anyway as I'm too lazy for clean flashing will keeep researching a more direct solution. Next step: trying a new dialer.

spaniard said:
Thanks guys, I know that and I think that this is the most probable solution, anyway as I'm too lazy for clean flashing will keeep researching a more direct solution. Next step: trying a new dialer.
Click to expand...
Click to collapse
That's a temp solution till u start having other problems too.
U know what's the problem, so sooner or later u shall proceed with factory reset.
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
That's a temp solution till u start having other problems too.
U know what's the problem, so sooner or later u shall proceed with factory reset.
Click to expand...
Click to collapse
Will try to wait until Pie

spaniard said:
I'm too lazy for clean flashing will keeep researching a more direct solution. Next step: trying a new dialer.
Click to expand...
Click to collapse
My opinion, the clean flash is the more direct solution. Tinkering with things like a new dialer is indirect. You may even be causing more problems than you solve. The problem is conflicting user data. The stock dialer app works just fine.
With a dirty flash, I always say "hope for the best, prepare for the worst". Meaning, you can try to dirty flash (as it is quite convenient). But be prepared to wipe or clean flash if you run into any issues with the dirty flash (which you are).

Well, the issue was caused by an old call recording Magisk module, restored latest nandroid backup, deleted the module and dirty flashed again 5.0.6 an everything looks working nice again .

Related

Anyone still having SMS issues?

I've tried everything now, but I'm still not receiving SMS messages until I reboot... then I'll get a couple that I may have missed, and then nothing again.
I can now only assume that if it is software related, its down to Magisk or root.
I've tried RR 5.8.3 official ROM and it happens (that's when it started), I've also tried ExperienceOS... both of those also tried with their Kernel and Bluspark.
I'm now on OnePlus3t_Oxygen28 (stock?) with the kernel that comes with that (have also tried Bluespark).
I'm *still* not receiving - and problems sending I think now - SMS. I know there was previously a VOLte issue, but would have thought this was sorted in Custom ROMS, and I can see no option within them to turn off VOLte (or select it)
Does anyone have any software suggestions... or know a ROM/Kernel that DEFINATELY sorts this issue? I've requested a new SIM from Vodafone but I do think there is something within the software somewhere that is causing the problem.
Suggestions welcome. Failing that its bin the 3t and go back to the HTC10 as I need SMS.
Are you by any chance using Root Call Blocker?
Do you dirty flash a lot? Have you ever done a data format? when you go into advanced on TWRP and wipe your data you should also format too. Trust me it helps when installing new roms especially lineage. I would say update to the latest 4.1.6 or OB8 then do both of those things and go with whatever rom you want. I used to miss SMS as well but this fixed my issue a few months back with OB6.

Missing product code

I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom. so I decided to go back to stock. I noticed when I went to download mode the
"carrier id" is now blank whereas it was PAK before it was gone, also I went to settings it displayed XTC/XTC/ .
I did backup my efs
How do I restore my original product code?
Please help
Excuse me, off topic, but what font are you using?
winol said:
Excuse me, off topic, but what font are you using?
Click to expand...
Click to collapse
I'm using Googlesans
upbeatwrench said:
I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom. so I decided to go back to stock. I noticed when I went to download mode the
"carrier id" is now blank whereas it was PAK before it was gone, also I went to settings it displayed XTC/XTC/ .
I did backup my efs
How do I restore my original product code?
Please help
Click to expand...
Click to collapse
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
_alexndr said:
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
Click to expand...
Click to collapse
also, after flashing stock firmware, I had the data erased (didn't used the HOME_CSC), after I enable developer options, OEM Unlock is already there and the option is ticked
_alexndr said:
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
Click to expand...
Click to collapse
I have later more studied and found this code is in bootloader and strongly believe this specifically happens when you flash BL and modem with TWRP instead of odin. I request users to check this. Though this seems purely a cosmetic glitch and yet haven't found any ill effect practically.
dr.ketan said:
I have later more studied and found this code is in bootloader and strongly believe this specifically happens when you flash BL and modem with TWRP instead of odin. I request users to check this. Though this seems purely a cosmetic glitch and yet haven't found any ill effect practically.
Click to expand...
Click to collapse
Is this because of some ROMs with such options to update BL/CP before installing the rom may have cause the issue?
upbeatwrench said:
Is this because of some ROMs with such options to update BL/CP before installing the rom may have cause the issue?
Click to expand...
Click to collapse
This is what is my speculation, if someone don't have this issue and flash BL and Modem with TWRP and if he/she get this error, we can confirm it.
But this code is simply a cosmetic and I haven't seen any issue related to this.
upbeatwrench said:
I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom [...]
Click to expand...
Click to collapse
BTW: Side note - my ROM is NOT sluggish but you just experienced latest Magisk's issue after clean install. More info you will find in similar S8's thread (post #280):
https://forum.xda-developers.com/showthread.php?p=77657344&postcount=280
... I just forgot to put same info in N8 thread
dr.ketan said:
This is what is my speculation, if someone don't have this issue and flash BL and Modem with TWRP and if he/she get this error, we can confirm it.
But this code is simply a cosmetic and I haven't seen any issue related to this.
Click to expand...
Click to collapse
I see, if that's the case, I did tick those options cause I thought it would be better to update BL/CP
anyways, I thought missing the product code or the 3rd csc was a huge problem because as I was installing different roms after I lost it and reinstall the stock FW, there was a lot of lag and every rom that I install, I did wipe/format data,cache before installing a new one.
Another one problem I encountered was everytime I download root explorer app and try to modify some cscfeatures, the SystemUI stops, sometimes even after a few minutes after it restarted, the SystemUI stops.
anyway, I thought these problems was related to the product code being missing, but it's all good now, everything is working just fine :good:
I have had this problem for ages, over 6 months, had flashed a number of roms and different country stock files before I noticed it had changed.
I had not used Dev-Base at the point of realising the change though.
I have never had any issues in functionality despite this. Not seeing anyone else with it, I assumed Samsung maybe updated something for unlocked phones.
_alexndr said:
BTW: Side note - my ROM is NOT sluggish but you just experienced latest Magisk's issue after clean install. More info you will find in similar S8's thread (post #280):
https://forum.xda-developers.com/showthread.php?p=77657344&postcount=280
... I just forgot to put same info in N8 thread
Click to expand...
Click to collapse
Yup, sorry about that, I thought it was only yours,
thanks for letting me know that Magisk was responsible for that extreme lag
upbeatwrench said:
I see, if that's the case, I did tick those options cause I thought it would be better to update BL/CP
anyways, I thought missing the product code or the 3rd csc was a huge problem because as I was installing different roms after I lost it and reinstall the stock FW, there was a lot of lag and every rom that I install, I did wipe/format data,cache before installing a new one.
Another one problem I encountered was everytime I download root explorer app and try to modify some cscfeatures, the SystemUI stops, sometimes even after a few minutes after it restarted, the SystemUI stops.
anyway, I thought these problems was related to the product code being missing, but it's all good now, everything is working just fine :good:
Click to expand...
Click to collapse
Nope, None of such issue is related to missing code.
this error I have on my N8 and I remember once I had flashed BL and modem via TWRP , though at that time I have no idea otherwise I can confirm it. I have made small tool to restore missing code too but never shared (Nor I am using) because t requires to patch on every boot. So my suggestion is just forget it.

[SOLVED] How to fix the TW Oreo battery calibration issue.

so for some reason upgrading to oreo really messes up the battery calibration for me. at first, everything will be fine, but after a few reboots and using the phone, the battery percentage is everywhere. I'll plug my phone to charge and the percentage will rise as if it were seconds. I love oreo to bits, and I prefer it over nougat obviously. I used Odin to flash a stock rom, and still it's happening. anyone know what we can do to fix this? I know others here have the same problem.
EDIT (09/03/2019):
some people have mentioned ways to try and fix the problem, so I decided to make this a thread to try and find a solution to the calibration issue.
How can I participate?
You can participate by (briefly):
*submitting a solution you have found
*submitting an idea that may potentially work
*testing the fixes or ideas submitted
What else?
*solutions that are submitted are to be tested and confirmed if they work or not.
*ideas can also be tested, but at your own risk. make sure to make a backup of your current rom and storage if you don't want to lose anything.
*also submit what model you have (unless this applies only to the G610F model - we cant tell).
we can do this. I am tired of android nougat (android N doesn't have this issue).
EDIT (14/04/2019)
so, now that our phone actually recieved OneUi, theres no point for this thread android Pie doesn't have this problem, which is fantastic. thanks for those who contributed!
ill keep this thread around in case there are some bois out there who still prefer oreo for whatever odd reason.
but honestly tho, oneui is perfect.
PEACE!!
EDIT 13/05/2019
SOLVED!! (FINALLY)
right now im running oreosama rom, with no issues, no problems at all - i have (accidentally) found the solution to this battery problem!
the solution is very simple - download a stock oreo rom from sammobile or updato, and then flash its bootloader with odin. the battery calibration issue occurs cause the bootloader is still based on nougat. that issue goes away once you upgrade.
there you go folks - happy oreo flashing!!
lor3tz said:
so for some reason upgrading to oreo really messes up the battery calibration for me. at first, everything will be fine, but after a few reboots and using the phone, the battery percentage is everywhere. I'll plug my phone to charge and the percentage will rise as if it were seconds. I love oreo to bits, and I prefer it over nougat obviously. I used Odin to flash a stock rom, and still it's happening. anyone know what we can do to fix this? I know others here have the same problem.
Click to expand...
Click to collapse
I have the same problem after an OTA update.
officially from samsung?
Try to use Battery Calibration app on CHPlay of SuperThomasLab, read instruction and follow that, i am in TW Oreo and my battery is OK although it stills rarely mess up
I have this problem and I don't know why. I have Android 8.1 official
I had the same problem but .. its gone after flashing oreosama rom and in other TW roms that supports USSD CODES (including the stock) I used *#0228# and it worked everything was ok
Can you give more details?
AhmedKhamis67 said:
I had the same problem but .. its gone after flashing oreosama rom and in other TW roms that supports USSD CODES (including the stock) I used *#0228# and it worked everything was ok
Click to expand...
Click to collapse
i could give this a try. im desperate to get my phone fixed lol.
AhmedKhamis67 said:
I had the same problem but .. its gone after flashing oreosama rom and in other TW roms that supports USSD CODES (including the stock) I used *#0228# and it worked everything was ok
Click to expand...
Click to collapse
so I updated the post. anyways, I tried your idea. I downloaded oreosama and used the ussd code. I thought everything was fixed, then suddenly it gave the usual problems. so your solution did not really work. is there any way we could like port the nougat battery files over to oreo?
If you try to delete battery.bin?
Maybe it would help you.
Drain to 0% and charge your phone to 100%. While plugged in, dial *#0228# and press 'Quick Start'. It would be better if you are on stock ROM. Do it 1 or 2 times and you are good to go. Works like charm for me.
do i dial the ussd code once the phone has reached 100%? how do i know if theres a battery calibration issue?
Beytullah61 said:
If you try to delete battery.bin?
Maybe it would help you.
Click to expand...
Click to collapse
somebody test this
lor3tz said:
somebody test this
Click to expand...
Click to collapse
It worked on my phone.
I think you need to replace the battery with new one
Before doing make sure battery is at 100%
1. Go to root/data/system.
2. Delete all the files which have a name that starts with battery.
3. Delete the Dropbox folder.
4. Reboot to TWRP.
5. Go to Wipe -> Advanced Wipe. Choose dalvik and cache partitions and then wipe them.
6. Reboot and check.
For TWRP and root users ..
op post edit~
guys, ive finally fixed the problem. check the OP to see how!
Help, all of your methods are not work on my phone. My phone is charged too quickly to 100% and after restart the battery is draining to 10%.
did you upgrade the bootloader to Oreo?
lor3tz said:
did you upgrade the bootloader to Oreo?
Click to expand...
Click to collapse
Yeah.

[Help] Unable to use custom ROMs on brand new 3T (touch non responsive once woken)

So about 3 weeks ago my 2 year old 3T just stopped working out of nowhere. I debated on whether to upgrade for over a week, but eventually decided to replace it with the same, just to have the familiar ROM, & not to have to learn anything new or mess with anything else, since I'm going through a lot of personal stuff right now. Anyway, I got the phone over a week ago and I've tried everything since then to get it running something beside OOS to no avail. Every single time it goes to sleep in another ROM, once I wake it up, touch is no longer responsive. I can't for the life of me figure out why. I have tried so many different things, in so many different ways. I know it might sound ridiculous but at this point I'm just in tears... I really need a functional phone, and I never would have bought another OP3T if I knew I'd be stuck with OOS....
The process I went through as soon as I got it:
Unfortunately I don't remember the version of OOS that it came with
- Unlock bootloader
- Flash TWRP (twrp-3.0.4-1 due to a thread I came across and was confused by)
- Wipe everything
- Flash recommended firmware for my ROM (posted in the ROM's thread)
- Flash my favorite ROM (Unofficial RR)
- Flash Magisk
- Boot, everything seems fine, screen goes off, turn it back on, unable to use touchscreen anymore.
I then used the unbrick tool, and tried again. Same problem. Used unbrick tool, unlocked bootloader, this time tried to flash this unofficial Lineage . Booted. It went to sleep. Woke up. Touchscreen nonfunctional.
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS. I go through the entire process again, this time flashing TWRP 3.2.1.0, it's the same thing. I've tried going up to open beta and then flashing my roms. I've tried flashing the rom without firmware, without magisk. With gapps. Without gapps. I always format and wipe everything. I also tried this on the off chance it might work.... I have seriously done the process every way imaginable, over twenty times since I got the phone last week.... nothing ever works. I also just tried Cyanogenmod, but it wouldn't flash at all.
I don't know what to do anymore. I just want to have a phone that I don't hate. At this point, I am too tired and I've got too much going on to figure this out on my own anymore. I would be grateful to pay someone at this point just to help me get this working honestly.... so if there's anyone out there who knows how to fix this, please let me know
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Mizart said:
It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess).
Click to expand...
Click to collapse
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
SpaceOctopus said:
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS.
Click to expand...
Click to collapse
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Mizart said:
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Click to expand...
Click to collapse
Brand new from ebay. Sealed in the box.
I did try flashing a more recent version of resurrection remix, but it failed. Any recommendations?
redpoint73 said:
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case. Thank you.
hhp_211 said:
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Click to expand...
Click to collapse
I did try that TWRP eventually. No change. I would probably have switched to pie a while ago, except one small thing. There's an xposed module I'm really attached to, and as far as I'm aware, xposed isn't available on pie? Or at least that's what I've heard/read. It's the xprivacy lua module that lets you control every type of data an app has access to. I think I've tried looking for an alternative and there aren't any, either. :'( You know, sometimes it's just that one small thing... lol
However, I did try to install the most recent version of RR yesterday, and it failed flashing. Don't know why. I'm going to try again after flashing the firmware. Maybe it'll work this time.
Anyway, I'm also going to try what you all have recommended and see what happens. Hopefully something happens. Thank you much for your help
Ok, well, this time it let me install Resurrection Remix latest version. It may not be exactly what I wanted, but it's pretty goddamn close, and it sure as hell isn't OOS! lol
Thanks for your help everyone! I really appreciate it. I do still really wish I knew wtf was happening honestly with it not properly running nougat ROM's, but hey, this works for me. It won't make me want to toss it in a dumpster and set it on fire every time I pick it up. :laugh: :laugh: :laugh:
Maybe I can get someone to figure it out in the future or something, I don't know. I sure wish someone would convert that xprivacy module to work with Magisk though! I'm surprised nobody has even made an alternative or an app or anything like it really.
SpaceOctopus said:
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case.
Click to expand...
Click to collapse
I think the unbrick tool does flash the full OOS. But honestly not 100% sure, as I have never actually had to use the unbrick tool (knock on wood!). Which is one reason I decided to pose that as a question.
In any case, if the unbrick did flash an old OOS, best to replace with newer version (or at least the firmware). Updated firmware typically plays better with the current custom ROMs. And old firmware is often a culprit when random bugs occur after flashing a custom ROM. So again, flashing firmware and/or the full update zip (which also flashes the firmware) is best practice in such cases. And if you are in any doubt about the OOS version or corresponding firmware that was installed, it probably doesn't hurt to flash again.

Revert from Android 10 to Android 9 - All stock

Hi,
I am done with the android 10 update as it is full of bugs and I do not have any wifi.
is there a smart easy to go back to latest stock android 9 ?
bootloader is locked
meisterlampe2000 said:
Hi,
I am done with the android 10 update as it is full of bugs and I do not have any wifi.
is there a smart easy to go back to latest stock android 9 ?
bootloader is locked
Click to expand...
Click to collapse
Second update is 100% clean of any bugs. Maybe factory reset Is you still have problems
Baron60 said:
Second update is 100% clean of any bugs. Maybe factory reset Is you still have problems
Click to expand...
Click to collapse
What errors were fixed?
mh, i cannot connect to any wifi network, even the open without password,cypher...
That is still the case in the Jan Update, will try the factory reset now.
meisterlampe2000 said:
mh, i cannot connect to any wifi network, even the open without password,cypher...
That is still the case in the Jan Update, will try the factory reset now.
Click to expand...
Click to collapse
hi.
u want connect with share internet with Bluetooth
very easily
****oonn said:
hi.
u want connect with share internet with Bluetooth
very easily
Click to expand...
Click to collapse
sure, thanks. But what i really want is a working operating system
Baron60 said:
Second update is 100% clean of any bugs. Maybe factory reset Is you still have problems
Click to expand...
Click to collapse
Ok, dude, stop misleading people. Maybe it is 100% bugfree for you. Which I doubt, unless you do have device personalization services installed as a system app and can use 5 GHz hotspot; both of these problems present in mine and my wife's phone, who upgraded today, thus not coming from 13 jan upgrade. Or maybe it doesn't have any bugs that bother you, but it's enough to go quickly through the the various threads to see that you're wrong in claiming that's 100% clean of bugs.
Hey i just wiped the phone (factory reset) and now WiFi is working fine again. So definitely a SW migration bug, to those who suffer the same (wifi not connecting at all), you may have to do that or wait for a proper fix (Jan 2020 patch did not solve for me).
Thx!
hugohenry16 said:
What errors were fixed?
Click to expand...
Click to collapse
Slow WiFi fixed. UI glitches with gestures and other UI things fixed. Too early to tell but battery seems slightly better
Baron60 said:
Second update is 100% clean of any bugs. Maybe factory reset Is you still have problems
Click to expand...
Click to collapse
No, you shouldn't do a factory reset unless you want an annoying banner at the Settings page

Categories

Resources