Related
I just flashed CyanogenMod 5.0.2 for the first time last night, according to the instructions on the wiki. Before that, I was using the N1 with Google's OTA update and had 4 full 3G bars at work.
After flashing CM, I noticed that at home, the phone dropped to EDGE. I didn't mind that much, and drove to work, and at work the phone was still on EDGE. I had to reboot for it to use HSDPA.
Has anyone else seen this kind of behavior where the phone gets stuck on EDGE even though it gets in an area that T-Mobile lists as "best 3G coverage"? This seems like a regression in CyanogenMod vs. the stock ROM.
PS: I can duplicate the signal drop while holding the bottom of the phone with my hand.
There have been many reports of this issue in the bay area. It's probably a network issue.
maybe you should start a poll.
I have this problem. I thought I solved it by going to network operators, but my when i lose H(3G) and it goes to E it wont go back... i too am in the bay area.
Remaining stuck on EDGE with CyanogenMod only
FettsVett said:
There have been many reports of this issue in the bay area. It's probably a network issue.
Click to expand...
Click to collapse
Connectivity issues aside, in the same Bay Area, with the stock ROM, the Nexus One would go back to 3G when 3G was available. Now, with CyanogenMod 5.0.2, once it switches to EDGE, it seems to stay on EDGE until you reboot (or maybe until you toggle plane/flight mode, I haven't tried that).
I've added a poll at badnewswrx's suggestion.
It's not just the Bay Area. It happens to me in the San Fernando Valley as well. I don't think it's specific to this release of CM 5.0.2, I think it occurred on my stock N1 before I ever rooted it. Either way, it occurred in beta 4 and 5 as well.
i wonder which side the problem is happening. Tmo or Google/HTC, or maybe CM5.0.2?
I would guess Tmo, the rom was running fine with great 3g or H coverage. not any better than stock for me though. Im thinking we will have to force the 3g until something clears up
badnewswrx said:
i wonder which side the problem is happening. Tmo or Google/HTC, or maybe CM5.0.2?
I would guess Tmo, the rom was running fine with great 3g or H coverage. not any better than stock for me though. Im thinking we will have to force the 3g until something clears up
Click to expand...
Click to collapse
With my stock ROM, I did not have this problem. The OTA update didn't improve the 3G/EDGE flip issue for me, but the phone wouldn't be stuck on EDGE.
UPDATE: With CM5.0.2, I got one case this morning where the phone remained stuck on EDGE even though it was in an area (at my workplace) where it had HSDPA all the time before flashing CM. This evening, it switched among EDGE an HSDPA, and now it's on EDGE, even though I'm at home, in an area with maximum T-Mobile 3G coverage.
Nasty hard to reproduce issue.
hmmm.....
H now...........
speed test at 1030, in an area where i had no H lets see how long this holds up
3 mins later drop to E
I only had this problem with the ERE27 radio. Never had it with stock, and don't have it with the newest one.
Hope we can figure out what the issue is, manually switching to force 2G and back to 3G as a workaround is quite annoying.
dandv said:
With my stock ROM, I did not have this problem. The OTA update didn't improve the 3G/EDGE flip issue for me, but the phone wouldn't be stuck on EDGE.
UPDATE: With CM5.0.2, I got one case this morning where the phone remained stuck on EDGE even though it was in an area (at my workplace) where it had HSDPA all the time before flashing CM. This evening, it switched among EDGE an HSDPA, and now it's on EDGE, even though I'm at home, in an area with maximum T-Mobile 3G coverage.
Nasty hard to reproduce issue.
Click to expand...
Click to collapse
For me its quite easy to reproduce.
- Force phone in 3G
- Make a call (data disconnects)
- After the call it goes into 2G and gets stuck there until I reboot the phone or force 3G again with *#*#4636#*#*
Here are the screen shots and the scenario
Rebooted the phone had 2G already, never went to H
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then Forced 3G
As you can see I do have a strong 3G signal here but stuck on EDGE/2G
Just came across something, After I had forced 3g, I received a call, I noticed that my H symbol was still on, so i decided to go on the browser, and it did! I went to 3 different pages, they were bookmarked.
I thought tmobile didnt have talk and data simultaneuosly (lol). Anyway my phone is still on H, seems pretty decent bars, if i notice a drop into E which will happen sooner or later, then ill let you know if it goes back into it.
just thought i should share, btw, am i late knowing about the talk and data thing???
Is there a reason why I only get 2G right after reboot in a 3G area?
This is bothering the hell out of me.
Since my last post earlier today, I have dropped to e once. I'm on h now and even forced into e and back out and it selected h by itself. I hope it stays like this. I haven't done anything to fix the problem so to me its looking like a tmo service issue.
T-Mobile morons have no idea what I am talking about. Talked to 4 different people and even at their highest tier support.
I am about to smash this piece of **** against the wall so Asurion can send me a new one since they won't send one unless its broken.
badnewswrx said:
just thought i should share, btw, am i late knowing about the talk and data thing???
Click to expand...
Click to collapse
3G supports simultaneous voice and data; 2G does not.
Stuck on EDGE again
It just happened again - the phone was on EDGE. I toggled airplane mode and now it's on HSDPA. Obviously, I haven't moved it, and I'm in an area which T-Mboile claims to have maximum coverage.
Signal strength: -87 dBm 15 asu
This has has nothing to do with Cyanogen's rom. It's T-mob. to confirm, I changed my sim to my G1 and the same thing happens. I was in test mode and the phone dropped from UMTS to GPRS. I was in a call when this happened. I see the exact same thing on my N1.
erikku said:
This has has nothing to do with Cyanogen's rom. It's T-mob. to confirm, I changed my sim to my G1 and the same thing happens. I was in test mode and the phone dropped from UMTS to GPRS. I was in a call when this happened. I see the exact same thing on my N1.
Click to expand...
Click to collapse
Never said it was Cyanogen related issue.
With all the 4G Toggle issues, runaway errors related to it in aLogcat and having to reboot so it didn't eat up battery I decided as of today I would come up with something else.
Started using the phone to make a one-click shortcut to 4G..Hell with any 4G toggles.
Long click on desktop
..Click Shortcuts
..Click Activities
..Scroll down to Settings..Halfway down or so you will see 4G settings
..Click 4G settings
..Click Ok
You now have your own phone made shortcut to phones 4G settings with no need for any toggle. I am using LP Pro. This will also tell me if it was toggle or problem is within framework/phone. Enjoy.
devnulldroid said:
With all the 4G Toggle issues, runaway errors related to it in aLogcat and having to reboot so it didn't eat up battery I decided as of today I would come up with something else.
Started using the phone to make a one-click shortcut to 4G..Hell with any 4G toggles.
Long click on desktop
..Click Shortcuts
..Click Activities
..Scroll down to Settings..Halfway down or so you will see 4G settings
..Click 4G settings
..Click Ok
You now have your own phone made shortcut to phones 4G settings with no need for any toggle. I am using LP Pro. This will also tell me if it was toggle or problem is within framework/phone. Enjoy.
Click to expand...
Click to collapse
I dont have ACTIVITIES.. ONLY Settings and there is nothing for 4G. Any ideas?
UPDATE: This method did not work either..Hot Boot or Reboot is what it takes to actually shut off 4G...hmmmmm somethings definitely wrong with this picture.
I dont have 4G in my area so I wonder if those who can connect to 4G have the same runaway errors in aLogcat after they shut 4G off..regardless of what they use to shutoff..Toggle or manual method.
if you have sense you need BETTER CUT to do this...
BUT does this fix the issue with using a shortcut instead of the widget? I honestly do not see this error when I look in the logs...
devnulldroid said:
UPDATE: This method did not work either..Hot Boot or Reboot is what it takes to actually shut off 4G...hmmmmm somethings definitely wrong with this picture.
I dont have 4G in my area so I wonder if those who can connect to 4G have the same runaway errors in aLogcat after they shut 4G off..regardless of what they use to shutoff..Toggle or manual method.
Click to expand...
Click to collapse
I am in a 4G area and this works great for me. I followed the steps in the first post and added the icon to my homescreen. I was able to start and stop 4g without any issues.
What issues did u experience i am not following from your comments?
Thanks.
I found out this problem has been Reported to Google by many and there is an open ticket with medium priority.
Experienced runaway error messages in aLogcat when 4G is turned on either intentionally or accidentally, then turned back off at any point, the following messages continue to repeat at about 2 second intervals. The only cure seems to be shutting the phone off and then back on, but this shouldn't be required every time someone uses 4G
Errors..over and over..and over........
I/Wimax ( ***): <DC> Try to establish a connection to DC server.
E/Wimax ( ***): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'
Took me the longest to figure out that this is what was killing my battery. I just go into settings and turn it on when I need it now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rocking cm6... so I can ignore the issue for a while. loving the speed and smoothness.
Sent from my PC36100 using Tapatalk
dang you are absolutly correct..no wonder this drains the battery faster. Hmm any work arounds?
I used tasker to make a 4g toggle. Works with no problems.
his idea for a free toggle works...but the issue is what is happening in the background after your disable 4g. The wimax continues searching for a signal over and over after disabling the 4g service causing a battery drain.
I haven't experienced this, my 4g seems to shut off properly when I use the widget. At least I don't experience excessive battery drain. How do I check this. Maybe it is the rom you are using causing the problem. I'm running Sprint Lovers.
I honestly didn't notice this before this thread because I don't turn off 4g anymore. Most parts of sa I go to have 4g so I just leave it on. Interesting though and something for me to mess with.
Stroid01 said:
his idea for a free toggle works...but the issue is what is happening in the background after your disable 4g. The wimax continues searching for a signal over and over after disabling the 4g service causing a battery drain.
Click to expand...
Click to collapse
Whats even worse..I tried to even use Airplane mode and it didnt stop it...
You must Reboot (hot or full) or turn off the phone or the radio will keep going while on the plane.
cruise350 said:
I haven't experienced this, my 4g seems to shut off properly when I use the widget. At least I don't experience excessive battery drain. How do I check this. Maybe it is the rom you are using causing the problem. I'm running Sprint Lovers.
Click to expand...
Click to collapse
download alogcat from marketplace and view the log after installing it you will see what devnulldroid posted on page 1 of this thread
cruise350 said:
I haven't experienced this, my 4g seems to shut off properly when I use the widget. At least I don't experience excessive battery drain. How do I check this. Maybe it is the rom you are using causing the problem. I'm running Sprint Lovers.
Click to expand...
Click to collapse
Use aLogcat or any other free log app and turn on 4G and then turn it off.
Once it says its off watch the logs live, I filter to errors only, and you will see
E/Wimax ( ***): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused' over and over.
quocamole posted a great screenshot of what I am talking about on page 1.
devnulldroid said:
UPDATE: This method did not work either..Hot Boot or Reboot is what it takes to actually shut off 4G...hmmmmm somethings definitely wrong with this picture.
I dont have 4G in my area so I wonder if those who can connect to 4G have the same runaway errors in aLogcat after they shut 4G off..regardless of what they use to shutoff..Toggle or manual method.
Click to expand...
Click to collapse
I have had this issue as well and recently stopped using the 4g toggle. I was actually thinking of making this type of shortcut over the weekend.
I have not used alogcat, but I was able to figure out I had the 4g issue. cpu at 100% and system process suspend running.
at first I had the 4g toggle off and just rebooted my phone. this didn't seem to stop the issue. I went into settings - wireless & networks - mobile data always on - toggled this on and off a couple of times and it seemed to kill the process.
I have since stopped using the toggle and haven't gotten the issue to come back.
I live and work in San Francisco. I get 4g at work and no 4g at home. when I turn off 4g while getting coverage I didn't seem to get the issue, but if I left 4g on and drove home and then turned it off I would have this issue.
lately I haven't been using 4g and just switched to a different rom, so I don't know.
I have also unchecked network notifications within the 4g settings (needs to be done while connected to 4g or 4g on). not sure if this has helped any, but it was on by default on fresh 3.4. it is off by default on calkulins evio 1.6.2 rom.
hot reboot makes you lose 4g. I just do a real reboot and its fine.
tim
any kind of 4g widget turns on 4g when rebooted.
only workaround so far that i know if is to not have any 4g widgets on the home screens and to reboot after using 4g.
quocamole said:
any kind of 4g widget turns on 4g when rebooted.
only workaround so far that i know if is to not have any 4g widgets on the home screens and to reboot after using 4g.
Click to expand...
Click to collapse
Doesn't matter. I have found with no widgets..simply turning it on manually..and then off again the 4G radio or software that operates it still tries connecting and throws runaway errors.
Anybody have any suggestions for remedying the following two issues? Or is anybody else experiencing them?
1) First, and most importantly, my Gmail and Google Talk notifications are delayed on wifi when my screen is off. When I'm actively using the phone and my screen is on, there is no delay. Typical delay when screen is off is 3-5 minutes. However, I've seen delays as long as 20 minutes. Strange thing is, the delay kicks in literally the second I turn my screen off. For instance, I can be sitting and using the phone, turn it off, and then one second later send myself a Gtalk message, and the message won't come in for 3-5 minutes.
If I turn my screen on during this "delay period," all of the notifications immediately show up. So it's almost like the phone is going into some reduced wifi sensitivity mode the instant I turn the screen off.
For the record, my wife's Galaxy Nexus always gets Gmail and Gtalk notifications instantly when on wifi (yes, including the same wifi network that is giving me problems).
The only fix I've attempted so far is setting my phone's wifi to 2.4 ghz only, which did not seem to change anything. I already have the phone's wifi set to "Always" on. I do not have any power saving features turned on (no juice defender, no smart actions, etc.).
Router is an Apple Airport Express (as part of a Time Capsule). Update: I've now also tried an Actiontec router, and I get exactly the same delays. So it does not seem to be specific to Airport.
2) Second, I'm getting tiny, random wakelocks. I'll explain with three screenshots from different phones:
The below screenshot is from my wife's Galaxy Nexus. You can see that generally, when the screen is off, the phone is asleep. There are a few times when the phone is awake and the screen is off -- that's when the phone is streaming music.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The below screenshot is my HTC One S, which is setup exactly the same as my Razr M. Same widgets, syncing the same accounts, etc etc. Identical. Again, you can see that when the screen is off, the phone is almost always asleep.
The final screenshot is my Razr M. It's easy to see that the Razr M has tons of tiny wakelocks that neither of the other phones have.
I've tried to solve the wakelock problem by disabling location services, disabling 4g LTE, and disabling light flow. None seemed to have any effect. And again, the Razr M is setup identically to my One S, which does not experience the wakelocks.
Now, the wakelocks do not seem to be negatively affecting battery life, so I can deal with them. I just find it a little bit disturbing. Any suggestions for getting phone wake time to mirror screen on time?
Thanks.
Just to update the delayed notifications on wifi issue.
I've now tried it connected to my Apple Airport, an Actiontec router, and I even tried it connected to wifi using my HTC One S as a hotspot. So that's 3 different routers I've tried. I've tried WPA2 encryption and no encryption at all. I've turned off "mobile data" on the Razr M while connected to wifi in case there was some sort of interference going on. And yes, I even factory reset the Razr M and tried all of the above on a completely fresh M that had absolutely nothing installed to it or done to it other than adding my Gmail account. Despite all of this, my Gtalk and Gmail messages are still delayed by 3-5 minutes on average when I'm connected to wifi, and sometimes much longer.
Not sure what else I could even try on this particular unit. I'm going to take it to Best Buy and exchange it today (fingers crossed they don't give me any trouble). Hopefully I've just got a bad unit and the replacement will receive my messages on wifi in a more timely manner. Delayed receipt of messages on wifi was a major problem on HTC One series phones... I'm pretty sad to see it here, too.
I keep calling some of my contacts over VoLTE and first it'll drop LTE to 3g and try to complete the call. It rings and rings, then goes to voicemail and the other person doesn't even hear the phone ring on their end.
Anyone else with this issue? Doesn't happen every time but quite often. I'm running Stock rooted.
Ascertion said:
I keep calling some of my contacts over VoLTE and first it'll drop LTE to 3g and try to complete the call. It rings and rings, then goes to voicemail and the other person doesn't even hear the phone ring on their end.
Anyone else with this issue? Doesn't happen every time but quite often. I'm running Stock rooted.
Click to expand...
Click to collapse
I have T-Mobile, and as far as I can tell my VoLTE works. I haven't verified that it doesn't drop at some point during the call, but I haven't had any problems calling people, and when I look at the beginning of the call, and after the call is over, I usually have the VoLTE icon still in my status bar.
Both seem to work for me
I have TMobile as well and have 0 issues. Are you on 4.5.4?
Maybe it's just my area. Happened again today. I just noticed it happens when I call cell phones. When I call land lines it works fine.
works great when apn is set correctly ;D
Clownfish44 said:
works great when apn is set correctly ;D
Click to expand...
Click to collapse
This is what I have.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just to check the basics... You have it turned on, right?
Ascertion said:
Maybe it's just my area. Happened again today. I just noticed it happens when I call cell phones. When I call land lines it works fine.
Click to expand...
Click to collapse
I thought VoLTE was only supposed to work from Tmobile phone to Tmobile phone. So basically 2 phones on the same carrier network. I remember when that first came out as a thing it didn't work from say a Tmobile customer to a Verizon customer so it didn't work from a cell phone to a normal landline originally.
and to the OP's point... mine works fine as I can also tell by the HD symbol on the dialer screen. VoLTE is HD calling.
@Elnrik
I don't even See this option
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
moritz31 said:
@Elnrik
I don't even See this option
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
Click to expand...
Click to collapse
That is odd. I set up my phone without the Sim in it, used it for a while, then put in the Sim and installed the T-Mobile app. After that I had those options.
Maybe a factory reset and try the setup again?
Eric214 said:
I thought VoLTE was only supposed to work from Tmobile phone to Tmobile phone. So basically 2 phones on the same carrier network. I remember when that first came out as a thing it didn't work from say a Tmobile customer to a Verizon customer so it didn't work from a cell phone to a normal landline originally.
and to the OP's point... mine works fine as I can also tell by the HD symbol on the dialer screen. VoLTE is HD calling.
Click to expand...
Click to collapse
Yes, VoLTE is toggled on. It works for landlines, but not when I call other mobile numbers. It's really weird for me. The mobile numbers I'm calling are also on T-Mobile. If they call me, the phone stays on VoLTE, it's only when I call out.
Ascertion said:
Yes, VoLTE is toggled on. It works for landlines, but not when I call other mobile numbers. It's really weird for me. The mobile numbers I'm calling are also on T-Mobile. If they call me, the phone stays on VoLTE, it's only when I call out.
Click to expand...
Click to collapse
Hmmm, that's really odd. I would say a call into support would be your next move. Maybe it's faulty hardware!?
Currently downloading and its not a security path its changes . To super slow motion camera etc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Galaxy Note8 (SM-N950U)
Build Number : N950USQU5CRIA
Android version : Oreo(Android 8.0.0)
Release Date : 2018-10-10
Security patch level : 2018-09-01
· A new Camera function has been added(AR Emoji, SUPER SLOW-MOTION)
· The security of your device has been improved.
October security patch now available
anybody update to october fix and still retain hotspot hack?
SayWhat10 said:
anybody update to october fix and still retain hotspot hack?
Click to expand...
Click to collapse
Yes, it works.
Anybody have issues with their screen after update? I have dead spots on the screen that don't respond to my finger but work with the stylus. For example if I open the keyboard the y H and b don't respond to my finger.
urvi1 said:
Anybody have issues with their screen after update? I have dead spots on the screen that don't respond to my finger but work with the stylus. For example if I open the keyboard the y H and b don't respond to my finger.
Click to expand...
Click to collapse
I've been on crid update for almost 3 weeks and there's nothing wrong with my h key or y key at all I think you better warranty replace your screen before it's too late.
madmangunradio said:
Yes, it works.
Click to expand...
Click to collapse
Thanks
I updated and didn't even have to go back in and add DUN. It retained during the update
Finally got the official Pie update ??
Got the Pie update, lost LTE - update profile, update prl no go.
Also watching 3-minutes after reboot not getting a cell connection - anyone else?
Working fine for me..........................not able to get hotspot mod working anymore.
Sprint offers free hot spots now,so this isn't really needed anymore
Sent from my iPad using Tapatalk
Just spent an hour on with Sprint tech in OK, they have no idea what's happening for me (I see LTE, it drops to 0 bars then disappeared, I have 3G, it drops to nothing, I get "emergency calls only")
Things done
Cleared cache from recovery
popped the SIM out and put it back in
Updated profile/PRL
Reactivated on the network using ##72something#
Had network technicians check the tower to make sure there wasn't just a coincidence.
Forced LTE/CDMA as under automatic it will not connect to 3G
They're advising me to factory reset at this point, I'm betting there's some data in there munged... you know, look at all the phones I ever rooted and the one that I don't gives me the problem.
Looks at how many apps I'm going to have to put the password back in because they're garbage... silently cries...
##72786#
mildlydisturbed said:
Just spent an hour on with Sprint tech in OK, they have no idea what's happening for me (I see LTE, it drops to 0 bars then disappeared, I have 3G, it drops to nothing, I get "emergency calls only")
Things done
Cleared cache from recovery
popped the SIM out and put it back in
Updated profile/PRL
Reactivated on the network using ##72something#
Had network technicians check the tower to make sure there wasn't just a coincidence.
Forced LTE/CDMA as under automatic it will not connect to 3G
They're advising me to factory reset at this point, I'm betting there's some data in there munged... you know, look at all the phones I ever rooted and the one that I don't gives me the problem.
Looks at how many apps I'm going to have to put the password back in because they're garbage... silently cries...
Click to expand...
Click to collapse
Yup, that's what they had me dial. It ran some white screen app for about 5 minutes then rebooted, re-registered on Sprint, same issues shortly after.
ycats said:
##72786#
Click to expand...
Click to collapse
Updated yesterday, other than loosing access to the Google Play Store for a few hours, everything is working fine (so far)
what I noticed so far is that the OS consumes more RAM and there are processes that unintentionally close, Google assistant take a little more time to launch and same with the keyboard.
This new update sucks, anyway to roll it back?
Everything keeps on crashing.
I deleted or moved a few GB of data off the internal storage and still get the no space error.
whatsapp crashing
google play crashing
this is horrible
So no one has any idea? How can I fix this problem?
Hard reset