Related
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?
The latest nightlies can't be flashed automaticaly. You have to manualy install them from the opendelta folder.
How come ?
Sent from my Find 5 using XDA Premium 4 mobile app
There was one in the last few days that I had to manually flash, but todays OTA went fine. What recovery are you using, and have you installed SELinuxModeChanger and have you set it to permissive?
Both nightlies from the 21st and the 22nd have the problem, and i'm using twrp.
But i'm not asking for a way around the issue, i'm just asking why it's happening all of sudden...
Sent from my Find 5 using XDA Premium 4 mobile app
I am also facing this issue. It's because of the ZIP Verification.(using latest TWRP by the way) Flashing manuelly without ZIP verification works just fine. Also tried to deactivate ZIP verification in settings oft TWRP, but when i try to update through opendelta it's automaticly reactivated...
Before the nightly oft the 20th everything went fine.
Gesendet von meinem Nexus 4 mit Tapatalk
Just disable secure mode in the open delta settings.
Gesendet von meinem Nexus 5
Did that allready. Changes nothing. Goes to TWRP and cancells because of ZIP verification failure. Then I have to install it manually
Gesendet von meinem Nexus 4 mit Tapatalk
Yes, I have the same problem as described by Destroyer706, on mint with twrp 2.6.3.0 on FOTA ...
Hey guys, I'm new to the ROM. Trying to download and flash the 26th nightlie but whenever I flash it says failed and says "zip verification failure" or something along those lines. I'm using TWRP if that matters and even unselected secure in settings for open delta. Could some one please help me out?
Also I was wondering if anyone has had their lock screen freeze on them at all? I've noticed on 4.4 ROMs for my vzw gs4 sometimes my lock screen will freeze and I'll have to do a battery pull. Though I noticed is far less on OmniRom than CM or Gummy.
You just need to install the update manually. The update file is in the /sdcard/opendelta/ folder. Choose the ZIP to install and then uncheck the "ZIP verification" box. It should flash straight away.
The lockscreen freeze must be device specific. So better ask directly in the thread of your device, to get faster help.
BTW i switched to Philz touch recovery and the opendelta updates are working again. I prefer cwm anyway, so no more Problem for me
Gesendet von meinem Nexus 4 mit Tapatalk
open delta is downloading the entire file and not only the delta... or did i missed some settings ???? :silly:
doctor_droid said:
open delta is downloading the entire file and not only the delta... or did i missed some settings ???? :silly:
Click to expand...
Click to collapse
My open delta file has over 300 Mb, entire newest rom from today is still 189 Mb... and TWRP can't flash it... thanks god I've made backup before... :silly:
New changes have been committed, disabling the signature verification if secure mode is not enabled. We're still not quite sure why some TWRP builds derp on it, though. This specific issue should stop annoying you the on the 27th --> 28th update.
OpenDelta auto update fails everytime
Hi Guys,
I've been having problems with OpenDelta since day one, even with latest updates. Everyday when update check is automaticaly launched it simply get stuck at about 9% or 11% of the process. I need to reboot my I9100 and manually check updates to get them. Also if I don't reboot OpenDelta consumes the batery.
Anyone having this issue?
By the way, I'm still reading documentation but I was planing to start participating. But I'm getting old and my Java skills are a little rusty so before throwing code lines like a crazy I prefer finish reading the available documentation. Also it's my first incursion with Android programing.
Anyway, for the moment I'm just trying to set a development enviroment on Windows and reading gerrit docs and preparing for download the code. Any guidance on setting windows enviroment will be much appreciated
My idea is to add stop / resume / restart functions to OpenDelta and setting to enable / disable auto update.
keep your screen from timing out while doing the OTA update.
bleggy said:
keep your screen from timing out while doing the OTA update.
Click to expand...
Click to collapse
Can't do that, unless I set the screen to never timeout. But It usually launches the auto updates while I'm sleeping. Manually checking the updates work fine, even when screen timeouts.
Osmodiar said:
...
Anyone having this issue?
...
My idea is to add stop / resume / restart functions to OpenDelta and setting to enable / disable auto update.
Click to expand...
Click to collapse
The issue is the sdcard fuse daemon getting stuck, not OpenDelta - that's just a symptom. It (occasionally) happens on all i9100-family devices, including the Note 1.
You can already en/disable updates by setting the networks it updates on to none (from the actionbar menu).
As for stop/resume/restart, it may be useful but under normal operation (not one of these problematic devices like the i9100) it updates while you aren't using the device, so these buttons would not see much use - if any at all. As it currently is, the process is frozen when this problem happens, and a proper restart would require forcefully killing the entire process through a secondary process - something you really don't want to do.
If you want to help out, spend time on figuring out what the actual problem is in the sdcard fuse daemon - that will actually solve a host of problems instead of just fighting symptoms. So far we already know putting the fuse daemon in debug logging mode makes the issue disappear (or at least, we haven't been able to replicate the issue in debug mode), probably due to the forced synchronisation of outputting to the log.
Chainfire said:
The issue is the sdcard fuse daemon getting stuck, not OpenDelta - that's just a symptom. It (occasionally) happens on all i9100-family devices, including the Note 1.
You can already en/disable updates by setting the networks it updates on to none (from the actionbar menu).
As for stop/resume/restart, it may be useful but under normal operation (not one of these problematic devices like the i9100) it updates while you aren't using the device, so these buttons would not see much use - if any at all. As it currently is, the process is frozen when this problem happens, and a proper restart would require forcefully killing the entire process through a secondary process - something you really don't want to do.
If you want to help out, spend time on figuring out what the actual problem is in the sdcard fuse daemon - that will actually solve a host of problems instead of just fighting symptoms. So far we already know putting the fuse daemon in debug logging mode makes the issue disappear (or at least, we haven't been able to replicate the issue in debug mode), probably due to the forced synchronisation of outputting to the log.
Click to expand...
Click to collapse
Thanks for the explanation, will read a little bit about sdcard fuse deamon. But as these are my first steps with Android development I think first need to learn some other things in order to provide any useful solution.
Destroyer706 said:
You just need to install the update manually. The update file is in the /sdcard/opendelta/ folder. Choose the ZIP to install and then uncheck the "ZIP verification" box. It should flash straight away.
The lockscreen freeze must be device specific. So better ask directly in the thread of your device, to get faster help.
BTW i switched to Philz touch recovery and the opendelta updates are working again. I prefer cwm anyway, so no more Problem for me
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
That's the problem I'm facing though. When I manually try to flash it it always says "failed" and won't flash the update.
Osmodiar said:
Can't do that, unless I set the screen to never timeout. But It usually launches the auto updates while I'm sleeping. Manually checking the updates work fine, even when screen timeouts.
Click to expand...
Click to collapse
yeah, turn off auto updates (uncheck all under network) until this fixed & when updating, keep screen on.
Nwwolf1 said:
That's the problem I'm facing though. When I manually try to flash it it always says "failed" and won't flash the update.
Click to expand...
Click to collapse
The same here with a Samsung i9300, had to install CWM to be able to flash updates. On the other hand excluding the problem auto update issue mentioned before, once the update gets downloaded TWRP update works perfect on my i9100.
I have followed the guide to flash the unlocked firmware and root my S7 Edge (http://forum.xda-developers.com/ver...de-flashing-sm-935u-firmware-verizon-t3415145) and all has been working well this weekend. This morning my phone gives me a persistent popup notification about a service provider update and "my device will restart to configure features supported by new sim card." The only option is to press ok and allow it to reboot. I cannot use my phone while this notification is active, and I am unable to kill it in any way. When the phone reboots to recovery, the configuration fails with "dm-verity verification failed". I then reboot system or power off and the endless cycle continues.
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
I wasn't getting any notifications however i did have some strange behavior going on and rebooted only to get the dm-verity verification failed and was no longer able to boot it would just sit at the Samsung splash screen I then had to factory reset re-post and re-setup everything, hopefully your experience won't need that since you are still able to boot!
Sent from my SM-G935U using Tapatalk
Thank you for the response, it's always nice to know someone has had similar problems. Looks like I will have to try reflashing the firmware. After your re-setup, did you do anything to prevent the issue from reoccurring?
Everything is again in working order. If anyone finds this and has the same problem, after flashing the Verizon fixes the phone is identified (in the about device setting) as the SM-G935V version again and is set to download updates automatically. I unchecked this option and I hope this should prevent it from happening again.
Not really wasn't sure exactly what happened the first time but thankfully (knock on wood) ??? it hasn't happened again.
Sent from my SM-G935V using Tapatalk
mine did it too. had to reinstall the whole thing.
drmatthews1 said:
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
Click to expand...
Click to collapse
shawnten said:
mine did it too. had to reinstall the whole thing.
Click to expand...
Click to collapse
I encountered this issue today and found a solution:
http://forum.xda-developers.com/galaxy-s7/help/whats-package-service-provider-update-t3425169
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Dameon87 said:
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Click to expand...
Click to collapse
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
thedrizzle said:
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
Click to expand...
Click to collapse
This has been my experience, as well as a few others. I'm not 100% sure it's that setting in particular, but I am 100% sure that it is caused by a setting in xTouchWiz. I had the issue once before, and it was a clean install save for xTouchwiz and me running through all the options. Since then, I've limited the choices in xTouchwiz and have not experienced the issue since. When I have some time I'll run through it and see if I can replicate the behavior again, since I'm working on a ROM.
There is a simple fix...
I agree, XtouchWiz drops a bomb when installed and it will cripple your phone. I never played with DVFS, I personally though it was the disable TIMA that set it off. An easy fix for anyone who stumbled on this. Power off your phone, remove the sim card, power up your phone, freeze a service called AutoPreconfig, power down and insert sim, good to go.
More info http://forum.xda-developers.com/gal...ge-service-provider-update-t3425169?nocache=1
Shout out to Wired4Fun for this easy fix.
Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!
I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.
whoiswes said:
I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.
Click to expand...
Click to collapse
thanks for the reply. i did a clean flash. didnt work.
i flashed the boostack, rebooted back to recovery, flashed the rom and gapps, wiped cache and rebooted. it boots fine. but then i still dont have auto rotate. seems like the drivers werent installed or something
Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?
MiMtnBiker said:
Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?
Click to expand...
Click to collapse
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end
crazynitro said:
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end
Click to expand...
Click to collapse
Check the md5 on your download to make sure it is not bad Install twrp 3.0.4.0 you could also move everything you want to keep to a sdcard so you can do a total wipe. Now install rom and gapps only and check to see how everything works before adding root or apps.
crazynitro said:
Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!
Click to expand...
Click to collapse
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.
lkiefer said:
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.
Click to expand...
Click to collapse
I lost my phone so i currently have another one. i can t remember what i did to fix it though
crazynitro said:
I lost my phone so i currently have another one. i can t remember what i did to fix it though
Click to expand...
Click to collapse
That's a drag. Thanks for the quick response though.
Hello, I also have an issue with the accelerometer (and by consequence the auto rotate function).
I am on full stock Nougat B09 (no root) and the issue was also present on B06.
Rebooting the device solve the issue, and factory reset does not make this bug disappear.
That being said, I think I located the root cause.
The magnetometer seems to be never working, even after a reboot. When an app wants to use the magnetometer (like Google map, or the compass), it make the accelerometer crash....
Anyone else having this issue ?
Does you magnetometer works flawlessly ?
Thanks.
@arachneon,
Hi, you can change it in the tools---compass, and in that compass you can waggle the phone in the way of "8", if all that cannot fixed you can also seek help in the nearby ZTE after sales service repair center. Thanks!
hey,
is there any one experiencing incoming call issue , from other end if someone calls rings from their side but on phone there is no ring is coming and that calls goes to voicemail
I get that sometimes but only when my phone has been locked for a long time. Feels like calls don't come in because of some doze setting.
Have you find any workaround? i tried to dissable magisk and xposed then also its exist so it not doze issue right ?
alwynjoshy said:
Have you find any workaround? i tried to dissable magisk and xposed then also its exist so it not doze issue right ?
Click to expand...
Click to collapse
Unfortunately I haven't found any solution. It still happens to me sometimes when my phone is locked for a while.
Now i. Am using non treble AeX rom, its okay still now no issues
Try change "preferred network type" to Global. Doing that solved the issue for me.
Some dirty flash updates can cause those issues. I have 2 backups, and one of them is creating this issue. Selecting Global as @christoophat proposed didn't fixed the issue in the failing backup. It actually was always configured as Global. Encryption has nothing to do. Clean flash worked fine. You all having this issue can test it by doing a TWRP backup of your data partition, wipe dalvik/cache/data and reboot. You don't need to go through all the google setup just skip all and test your incoming call.
Oki said:
Some dirty flash updates can cause those issues. I have 2 backups, and one of them is creating this issue. Selecting Global as @christoophat proposed didn't fixed the issue in the failing backup. It actually was always configured as Global. Encryption has nothing to do. Clean flash worked fine. You all having this issue can test it by doing a TWRP backup of your data partition, wipe dalvik/cache/data and reboot. You don't need to go through all the google setup just skip all and test your incoming call.
Click to expand...
Click to collapse
Since I never dirty flash, never even do backups, not sure why you think that here.
And no, my phone (until the latest clean install of LOS 07/23 build I did last night) has never been set as Global default before on this phone, but either LTE/GSM or just LTE
I just tell you what worked on my phone, up to you to try or not. :highfive:
christoophat said:
Since I never dirty flash, never even do backups, not sure why you think that here.
And no, my phone (until the latest clean install of LOS 07/23 build I did last night) has never been set as Global default before on this phone, but either LTE/GSMA or just LTE
I just tell you what worked on my phone, up to you to try or not. :highfive:
Click to expand...
Click to collapse
Sorry @christoophat, I wasn't answering you since you hav already found your fix. As you, I was adding info to bring some light to the issue, thinking on the other members still having the issue. I was asking them to try other things so we all could figure out all the possible causes of this behavior. I am in T-Mobile USA and I don't have the issue. I had to recover an old backup to reproduce the issue.
I am also on TMo USA too.