Related
This morning (2011may27-0700 PST [pacific]), I received my 1st ever update from T-Mobile for my Galaxy S 4G. It told me "Congratulations," you have an update! or something like that, then told me I wouldn't be able to use the phone for 10min, I said OK, it rebooted into a white screen, applied an update (with progress bar), and said "Update is Failed", and rebooted. Upon reboot, I have a "low on space" notification and it stays up there in the menu bar, above. I don't have any extra apps, and don't know what to do.
Can someone walk me through finding where the space is suddenly used up? I'm really going to need some hand-holding on this. Thanks
Can someone tell me how to apply the update? If I go to "Settings" -> "Software update", it says "no firmware". As far as PC's go, I use Linux, btw
Has this update worked for others? What does it update you to? 2.3.x ?
Wrong Section mate, you might want to try out the Galaxy S 4g forums, i highly doubt anyone with a vibrant got an update for the Galaxy S 4g.
-Cheers
crud! thanks! Will repost
Hi,
I found firmware that looks very promising to work on my tablet. It boots, kinda. I mean, when I flashed it it did a bunch of formatting messages and now when I try to turn on the tablet it shows the logo. Sometimes it goes to the "lock screen" other times it just shuts off instantly. It doesn't seem to take my touches as inputs when I try to unlock the tablet. However, it does appear to have the right resolution for my tablet as all the visual stuff is laid out neatly and fits on the screen.
So, since I cannot find the right firmware (I have searched for 3 days straight now - even reached out to manufacturers - still no luck), I'm wondering if someone out there can modify this firmware so it will work with my tablet?!
My tablet model is S750L and uses Rockchip 292x. Supports Android 4.1.1
Link to firmware (For model TAB R76.2): This site wont let me give the link. So, go to GoClever.com click on "Support" and then "Software Update." Look in "TABLET" for R76.2. See where it says "update file?" Click on the blue icon that says. "ZIP" all the way at the right.
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
I have to same issue that just happened and same as the screenshot.
Same issue...
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
mikeinstlouis said:
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
Click to expand...
Click to collapse
Latest update have little bugs
Sent from my Nexus 5 using Tapatalk
I am also having this issue on my Galaxy S4.
---------- Post added at 02:56 PM ---------- Previous post was at 02:46 PM ----------
mrneoz81 said:
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
Click to expand...
Click to collapse
One way I found that I can close it is by opening the menu that has active apps, then going to RAM, next turn the phone on its side (<--- yes do that), then hit clear memory a few times. And done its gone.
Thanks! That worked on my Sprint S4! (restarting phone has also worked for me, but this is easier.)
After holding down Home button to open the menu that has active apps, the options were still covered by the text to speak box. So I had to FIRST turn phone on its side to make visible the pie chart icon on bottom left, THEN then going to RAM tab and hiting clear memory a few times. When I turned it back to portait orientation, the text to speak box was gone. Thanks!
This has been happening to me all day long. so frustrating. I am also not the tech savy one in the house and hubby is not around. So thanks for the quick answer to get rid of it until he can uninstall the new update. Thanks
What is the pie chart menu option? What is the RAM tab? And will just be a little easier for Google to fix this? Lol
same problem here
Galaxy S6, same problem, started last night (September 24, 2015) . I do know that some updates were performed last night, not sure what. How do I uninstall the update? Which one is it? Help! I use voice typing constantly, and my phone is a brick when this thing locks up. It covers all my buttons. "Restart" doesn't clear it, I have to totally power off and back on. Right now, I have disable my voice key on my keyboard so that I don't accidentally touch it while waiting for solution.
Me too - just started today after some updates yesterday.
Same here....has anyone responded with a fix yet??
THANKS!
Glad it's not just me and my Note 3, but where does google get off sending out this kind of crap? It's enough to drive me to a windows phone.
Having the same issue only way I can get ride of it is to turn off my phone
same issue on moto droid mini; have to turn off phone too! poor QA google!!!!!
Me too. Galaxy S4. Have to shut the phone down and restart it to resolve the issue.
Piece of crap
Note 4 same problem started on the 24th
Same issue, Note 4
Same issue, Samsung Note 4.
Yep me too Verizon Galaxy s6
Sent from my SM-G920V using Tapatalk
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
its nokia that pushed the update they did not make the rom right
Same here I told nokia about it and they told me to wait for a bug fix. I told them I wanted to downgrade since your firmware bug broke my phone.
Just wait for a bug fix? So use a Phone that cant make calls right?
So payed a guy to unlock my boot loader to try to flash a rom so i can just make the phone usable.
I spend about 6 hours try to get the rom to work. With little to no luck I was able to get into twrp a few times.
So ya Im in the same boat. I just got this phone back 3 weeks ago from a rma due to a bad chargeing port. Now Im forced to pay some one to unlock the boot loader and try to get a custom rom Just to be able to call
If I cant get the rom working Im going to have to go spend like $200 on a new phone today just sucks
fisterkev said:
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
Click to expand...
Click to collapse
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
gumbyx84 said:
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
Click to expand...
Click to collapse
I haven't. Just using whatever over the air OS Nokia pushes to the phone.
yes I did pay to unlock the boot loader I used linage from the rom section
it has all the bugs of the stock rom. Cant call out or with out the loud noise bug and no voip apps work
I did get the Android 9 based rom to work. it has a few bugs but its usable.
I more or less gave up im looking at a iphone now.
I spend 20 hours or more trying to get this phone to work
first the usb port goes out and I cant charge.
2 weeks after having the phone back I got a magnetic cable so the usb port would not brake any more cable. That was like $20
After 2 weeks android 10 more or less bricks the phone (a phone that cant make calls)
Then I have to spend like $15 to pay the poor guy to unlock my boot-loader (he did a great job)
I spend a lot more time loading the linage android 10 rom for it to have the same bugs ( in no way is it the devs fault im sure he did not know).
... can unlock your bootloader for a small fee.
I would say all android 10 based rom will have those kind of problems. I can only confirm it on the android 10 linage one
When I flash twrp most of the time the twrp would just freeze if booting form the phone.
I had no problem loading it with fastboot works evey time. So I would only use it install the rom and just boot it when you need it. I would not suggesting flashing it to recovery as it only worked some of the time for me.
Hope all that info helps
QUOTE=gumbyx84;81261583]Have you guys modified the phone in any way like unlocking the bootloader or rooting?[/QUOTE]
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
The calling problem goes in and out. Some times it works some times it dose not. Facebook message outgoing calls the mic will not work, Same with google voice.
if i make calls with out google voice it works 1/2 the time. all the people have the same problem
https://community.phones.nokia.com/discussion/54374/android-10-after-update-on-nokia-7-1
diggeryo said:
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Click to expand...
Click to collapse
How to fix the phone call problems
To everyone having calling issues (distortion / squealing, or other people can't hear them), try this: Turn off Voice over LTE. You go to Settings -> Wireless and Networks -> Mobile Networks -> VoLTE, and turn that setting off. This fixed the problem for all 3 Nokia 7.1 phones in our family, when nothing else seemed to work.
Turning off VoLTE and wifi calling works, but VoLTE is important in my area with TMobile. Without it, too many dropped and missed calls. I actually downgraded from an Xperia XZ1 just to get VoLTE, now this happens.
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
Click to expand...
Click to collapse
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Thank you so much for sharing! Works like a charm
Unfortunately denying microphone for the Google app did not work for me. I also noticed no one can hear me when making videos calls (Hangouts, Duo, Facebook messenger).
I then decided to factory reset, but did not help. Both VoLTE and video calling still not working.
Anyone else with video calling mic issues?
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
Click to expand...
Click to collapse
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Confirm this recipe works for my TA-1085. Thanks much.
I solved my random voice problems (others can't hear me on Duo video call, duplex voice on the other side etc.) with the voice match assistant workaround until hopefully gets fixed in a next update. Don't know for sure if the thing is only on Nokia's side or Google app's as well on Android 10, since disabling Hey Google solves all issues
Will have to try/catch on future google app updates as well to find out
Sly_North said:
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
Click to expand...
Click to collapse
Under "Voice Match" I don't see any "Access With Voice Match" setting. What I do see is "Hey Google," which says "Access your Assistant any time you say "Hey Google" when your screen is on." Perhaps this is what your mean?
I tried this solution and it works, too. I think it also has the advantage of not completely shutting down Assistant's access to the microphone. Just waking up Assistant by voice. Much less of a price. Thanks!
Has anyone heard anything about a real fix for this issue? I've gotten two Android updates since the upgrade to Android 10, but this issue has not been fixed yet.
After extensive talks and inside info on Nokia's community forums, seems like a Maintenance update (MR) is on the way for May, which they say fixes -among others- both voice bugs. That is, the echo on calls plus sound distortion in some games (e..g Monument Valley 2 for me)
Cross your fingers everyone for a quick release and confirmation of the fixes!
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
dbal said:
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
Click to expand...
Click to collapse
Yes, they seem to have fixed the voice call problems with Whatapp, Wechat, Hangouts and etc since the Android 10 update.
BE2026
The stock oxygen OS has a text message bug that apparently isnt fixed yet, so i thought id try a different rom.
I unlocked the bootloader, worked great.
Then i flashed TWRP and it worked great.
I then proceeded to try and flash DerpFest and when the ADB sideload (ACCORDING TO THE DIRECTIONS) was done, it is suppose to reboot into the new os. but I get nothing.
So Ive tried, a bunch of stuff. I tried using orangefox and it doesnt support SD cards and the sideload option just crashes. So then i try TWRP recovery instead of billies recovery and when i select the image to install in TWRP, and then 'swipe to flash' TWRP instantly resets. and nothing happens.
So then i tried the MSMdownloader tool and it will not recognize the phone at all. all adv and fastboot commands work great.
Can someone help me?
I tried switch A or B, and flashing both,
I tried to go back to stock and i cant even get that to work.
Help meh please, i just bought this phone and now i cant even use it
I also cannot get the MSMdownloader to work. it shows my phone on the list in EDL mode. but com port is empty. device id is empty. all the fields are empty and it just says waiting on device. nothing happens.
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
arda99 said:
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
everyone comes up as it should in the device manager. sad face....
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
SomeRandomGuy said:
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
Click to expand...
Click to collapse
OH wow it did. Thank you, the documentation for that side of MSMd is vague. So after trying like 3 different "qualcomm" drivers I finally got it to work! As in the stock android 10 is loaded and the phone is no longer bricked. However, when I try the same methods again to actually put a custom rom on this phone the same thing is still happening.
No matter what OS i try to flash, no matter what mode or slot, or what recovery 'program' i use like twrp or orange FOX, nothing seems to actually boot into an OS. it just loops into Fastbook.
Can anyone help me? I dont want to use oxygenOS
I had a somewhat similar experience in loading custom ROMs, and simply took to de-bloating the stock image (emphasis on de-google-services, de-OnePlusSpyware, and de-auto-OTA). Still not really happy, compiling AOSP source now to try to swap out some of the system APKs that annoy me for customized ones. If there are only a few things that sour you to OOS, maybe I (or others) can help cure those? Debloat and replace...
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
So the main reason for me not wanting to use Oxygen OS is because when initally setting up the phone, everything works great. for about 2 or 3 days. then for what ever reason i cannot receive text messages. If I factory reset the phone, or put my simcard into another telephone all of them come rushing in.
In the event of me factory reseting my phone, ill get text messages from 3 or 4 days ago.
and it always works. as soon as my friend is texting me and i dont recieve it, i just factory reset then boom its there.
I tried everything, different SMS apps, update this, android 11 that. it always did it to me, like clockwork. like the phone installs an update and breaks text messages. I tried contacting oneplus customer support but that shhit is a joke. they told me they are aware of multiple isolated incidents about this and that the only thing to do left is to send it in. I JUST BOUGHT THIS THINg, im not about to send my device away, right after paying for it. I paid you guys $400 just to NOT have a telephone for 8-16 weeks?
SomeRandomGuy said:
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
Click to expand...
Click to collapse
See thats the thing, Ive never gotten another room, to boot. at all. no splash screen, no bootlogo nothing. it always just goes back to fastboot. it never tries to boot an OS. i follow these billie instructions and nothing happens. its the same result. I have tried all the different versions in this forum. from pixel experience to derpfest. all work great, untill the very last step where they say side load rom/flash and then reboot. your new os should be booting! and it doesnt.
Wow, that's a new one for me. I wish I knew more about the internals (slowly learning) to help troubleshoot. I would GUESS that if you can change phones (e.g. you said you can put the sim in a new phone, and get a backup of messages delivered), that it isn't so much that the phone is dropping them as it is not getting them in the first place.
With no guarantees- this is a SWAG- have you checked your APN settings? Most definitely, these come through as part of a new registration (duh), and consequently can get messed up for $diety knows why later... but at least you may be able to get a known-good set of settings (post reset, post registration) to compare to after terrorists strike and you are no longer getting messages. It should be easy to add a new APN with the "right" settings and manually select it.
If it is something like that, odds are an alternative ROM would just do the same thing; I assume there's some kind of handshake standard for initialization of the carrier network. I'm on TMo and happy to share my settings, if it helps....?
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
arda99 said:
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
Click to expand...
Click to collapse
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
agentruley said:
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
Click to expand...
Click to collapse
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
I had to go through the setup process again. First time the DF just didn't catch. I read ADB sideload can be broken as **** sometimes.
arda99 said:
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
Click to expand...
Click to collapse
Sadly this has nothing to do with my problem. Installing newer/ using older versions do not change the behavior.
The phone breaks as soon as I go back to the "Google Assisnt" -Setting up your phone for the first time- wizard and instead of selecting "Remind me tomorrow" i select next, and then the following screen says "Installing updates" and then the telephone will no longer recieve text messages. Does anyone have any help?
Oneplus customer service is terrible and they told me to buy another device.
This is the last phone i will ever purchase from them