Related
I couldn't find anything anywhere online about this OTA that I got yesterday on my US996, no record of it ever existing. So I asked LG about it and this was their response. I haven't applied the update yet, but will update this post if I notice anything other than what LG stated. I will hold off for a while on installing it so if enough people want me to capture and share the OTA then I will.
https://www.youtube.com/watch?v=KsD3pGv5cv8
From what I see all I've noticed is the Nov 6 security patch which means blueborne and krack are fixed among other exploits, ARB is still 0 so can be rolled back if wanted for some reason. Cool that it adds rcs support, not that my carrier has support anyway
was there a point for a video? simple screenshot of the conversation would have sufficed
updated, and i can't use my sim card anymore, the phone detected sim card but no signal at all, got some extra buttons in dailer.
ttnduy said:
updated, and i can't use my sim card anymore, the phone detected sim card but no signal at all, got some extra buttons in dailer.
Click to expand...
Click to collapse
As I mentioned in another thread, after I installed the update, it listed "unknown version" for baseband and wouldn't connect to Verizon for a few minutes. Then the baseband version showed correctly and it connected.
Since baseband is a wholly separate CPU and OS, it's not clear what it was updating in the background, but it fixed itself eventually.
alexandero11 said:
I couldn't find anything anywhere online about this OTA that I got yesterday on my US996, no record of it ever existing. So I asked LG about it and this was their response. I haven't applied the update yet, but will update this post if I notice anything other than what LG stated. I will hold off for a while on installing it so if enough people want me to capture and share the OTA then I will.
https://www.youtube.com/watch?v=KsD3pGv5cv8
Click to expand...
Click to collapse
Obviously LG thinks that we don't need to know the details, just that LG has improved the usability and functionality of the phone, that's all we need to know. /s
From what I can tell, it's the same build of android, NRD90M, as before the update. So probably only has google supplied security patches.
As long as LG gives us US996 Unlocked users an Oreo update early next year, I'm OK with them not doing much with the original 7.0 firmware... but definitely security updates more than once per year would have been nice.
The "slower than" or "completely missing" compared to major carriers updates up until this one, has definitely been a disappointment since the factory unlocked version of the phone should be the easiest to get updates pushed out for.
On Tmobile, 5G was working fine but after the April Android update 5G no longer works. LTE works fine but if you try to force 5G on, it actually only shows 3G active. Was working fine before the Android update. Anyone else seeing this? Tmobile only?
xenokc said:
On Tmobile, 5G was working fine but after the April Android update 5G no longer works. LTE works fine but if you try to force 5G on, it actually only shows 3G active. Was working fine before the Android update. Anyone else seeing this? Tmobile only?
Click to expand...
Click to collapse
Same issue here (had a crappy phone laying around, reason for the trade in). I tested it and in my area I have only Band 66 and shows 5G but no data. LTE works fine, my LG V60 has no problem with 5G. After the update I noticed this, factory reset and everything I have tried hasn't resolved anything. Most people might haven't noticed because they might be on LTE, haven't updated or possibly other 5G Bands work fine.
xenokc said:
On Tmobile, 5G was working fine but after the April Android update 5G no longer works. LTE works fine but if you try to force 5G on, it actually only shows 3G active. Was working fine before the Android update. Anyone else seeing this? Tmobile only?
Click to expand...
Click to collapse
Keep updating until it's broke vs update only when it's broke.
At least wait a few months to update to hear if any horror stories come out.
If I have a fast, stable platform that fulfills its mission I let it be. Security is almost never an issue on Android unless you do stupid things and no update will save you from that.
I'm still running Pie on my Note 10+, zero issues.
blackhawk said:
Keep updating until it's broke vs update only when it's broke.
At least wait a few months to update to hear if any horror stories come out.
If I have a fast, stable platform that fulfills its mission I let it be. Security is almost never an issue on Android unless you do stupid things and no update will save you from that.
I'm still running Pie on my Note 10+, zero iss
Click to expand...
Click to collapse
blackhawk said:
Keep updating until it's broke vs update only when it's broke.
At least wait a few months to update to hear if any horror stories come out.
If I have a fast, stable platform that fulfills its mission I let it be. Security is almost never an issue on Android unless you do stupid things and no update will save you from that.
I'm still running Pie on my Note 10+, zero issues.
Click to expand...
Click to collapse
The update was to fix some issues with calls ( which many were having, not sure if all, I did). In the process broke other things. I never update right away, but in this case was needed. Probably there's a bug with automatically selecting bands. There's never an update without bugs. I find updates scarier than flashing ROMS.
Derfomiundz Ivy said:
The update was to fix some issues with calls ( which many were having, not sure if all, I did). In the process broke other things. I never update right away, but in this case was needed. Probably there's a bug with automatically selecting bands. There's never an update without bugs. I find updates scarier than flashing ROMS.
Click to expand...
Click to collapse
Most times you can find work arounds for issues but they take time. Once found, no firmware solution needed.
You always get new issues that need work on a new OS plus the inevitable learning curve.
Time/effort vs benefits; the payoff better be worth it and unfortunately many times it isn't.
After over a year on Pie maintenance is almost effortless and second nature. It's very stable and predictable so malware is easy to quickly spot if it inadvertently works it's way in.
Not knowing what to expect from an OS opens you to all sorts of new dangers as well as wasting huge amounts of time.
Updates can also bring very unwanted features and lockouts that can't easily if at all rolled back
blackhawk said:
Most times you can find work arounds for issues but they take time. Once found, no firmware solution needed.
You always get new issues that need work on a new OS plus the inevitable learning curve.
Time/effort vs benefits; the payoff better be worth it and unfortunately many times it isn't.
After over a year on Pie maintenance is almost effortless and second nature. It's very stable and predictable so malware is easy to quickly spot if it inadvertently works it's way in.
Not knowing what to expect from an OS opens you to all sorts of new dangers as well as wasting huge amounts of time.
Updates can also bring very unwanted features and lockouts that can't easily if at all rolled back
Click to expand...
Click to collapse
At least I have way above average knowledge, but still is a horrible experience for normal consumers. Returning products, contacting the company for repairs. Both points are valid and differences of opinion. Still, it's possible the update was just fine and it's just the network and the new device. I don't care much about malware, that's up mostly about how someone use their devices. Funny story, I never used Android 9, I went from a device with Android 8 to 10 and 11. Also a reminder to people that aside from the main device is always good to have backup devices. We all know, they don't.
Derfomiundz Ivy said:
At least I have way above average knowledge, but still is a horrible experience for normal consumers. Returning products, contacting the company for repairs. Both points are valid and differences of opinion. Still, it's possible the update was just fine and it's just the network and the new device. I don't care much about malware, that's up mostly about how someone use their devices. Funny story, I never used Android 9, I went from a device with Android 8 to 10 and 11. Also a reminder to people that aside from the main device is always good to have backup devices. We all know, they don't.
Click to expand...
Click to collapse
Yeah they are little heart attacks
Those not technologically interested/adaptive will suffer like pigs, ☠guarenteed☠
I went from Kitkat to Pie, talk about future shock.
However I quickly learned to navigate it and plunged straight into settings and customizing it.
Double tap on/off, Good Lock Apps/One Handed Operation +, Galaxy store custom themes/icon packs, hell yeah.
Not bad for a none rooted phone
Optimizing it was a nightmare but only persistent prevails It was a hot running bandwidth/battery hog and it took close to a year to complete tone it down and dial it in.
Many failed experiments and 2 boot loop forced factory resets latter it's a very stable, fast platform that gets good battery life and fulfills its mission. It's drop dead gorgeous and hella fun to use even after 1.5+ years.
Malware is almost always the operators fault. I had one script jpeg that trashed the download folder files a bit but I tagged right away. Had a trojan preloader (came through the browser) that got in but was detected/deleted before it could go to town.
So far in 7 years no malware forced reloads. Not bad considering most of that time has been on systems deliberately not updated.
Data loss? Bah-ha-ha-ha listening to Don't fear the Reaper, BOC
Android's rarely crash... until they do☠☠
Have a T Mobile A32 5G (SM-A326U) with the lastest update.
Baseband version A326USQU1AUD4
Kernel Version 4.14186-21188749
Build number RP1A-200720.012.A326USQU1AUD4
KNOX 3.7API level 33
5G download speed 15-20 Mbps
4G LTE download speed 45-65 Mbps
I suspect the 5G issue may be related to your local transmission tower(s). Perhaps T Mobile has just released another update to fix the 5G connection problem.
Just got May update and still no 5G on Tmobile. 5G worked fine before getting the last update. Any suggestions?
xenokc said:
Just got May update and still no 5G on Tmobile. 5G worked fine before getting the last update. Any suggestions?
Click to expand...
Click to collapse
If your phone has the same software spec revision as mine, then the problem is probably coming from your T Mobile tower. Again, I get 5G, but the speed is slower than 4G LTE. I can manually switch between 5G and 4G LTE. I disabled KNOX, but I doubt that was the root cause for the lack of 5G connectivity.
I've tried in several parts of town that are known to have Tmobile 5G. Maybe its this particular phone. Will take to a TMO store.
xenokc said:
I've tried in several parts of town that are known to have Tmobile 5G. Maybe its this particular phone. Will take to a TMO K
Click to expand...
Click to collapse
The key is the software update number. My area is full of users, so I only get about fifteen M of throughput. Went to a poor neighborhood, and the 5G speed hits 390 Mbps. This phone does not allow the user to lock in to a particular T Mobile band.
furballi said:
The key is the software update number. My area is full of users, so I only get about fifteen M of throughput. Went to a poor neighborhood, and the 5G speed hits 390 Mbps. This phone does not allow the user to lock in to a particular T Mobile band.
Click to expand...
Click to collapse
Yes it does permit on dialer go *#2263# and banc lock lol phone supports 3xCA
financeledger said:
Yes it does permit on dialer go *#2263# and banc lock lol phone supports 3xCA
Click to expand...
Click to collapse
Thanks. Still slower 5G speed at some locations. 4G LTE is best for me, but that may change next year.
I just got an update on my motog stylus and haven't heard or seen anything about it. Was wondering if anyone knew about,
RPRS31.Q1-56-9-7 this is the updated version of my phone now. Any word or advise would be GREATLY APPRECIATED!! Is it just the security thing or just moving to Api 31?
My security Update is June 1, 2021.
JYrocks247 said:
I just got an update on my motog stylus and haven't heard or seen anything about it. Was wondering if anyone knew about,
RPRS31.Q1-56-9-7 this is the updated version of my phone now. Any word or advise would be GREATLY APPRECIATED!! Is it just the security thing or just moving to Api 31?
Click to expand...
Click to collapse
I just received the update as well. I'm installing now, going to re-root with magisk after update reboot.
I am currently looking at the a 21.40MB update called, rprs31.q1-56-9-7, that says 0 of 6, and supposedly includes Android security patches from August 1, 2021. I currently have it paused at 0% and is waiting for WiFi, despite having an unlimited data package, because I don't trust that it is what it claims. What network are you on? I am on Metro by TMobile. I googled the update version and first hit back was a verizon.com link, that apparently means this is their update, and if so, why the hell is it trying to force it's was onto my phone. (Backstory about my paranoia and anger, the past 6 weeks of my life have been nearly entirely consumed by phone crap, and 10 devices, including one Chromebook, and 9 phones, 3 of which I purchased brand new during this time, have all been infected with some sort of remote spyware hack, and I cannot get rid of the thing and have yet to be able to use any devices that doesn't quickly show signs it is also infected. It's a ****ing nightmare.) But yeah, I know my phone is hacked, and I have that on mine, and I am not a member of the provider that is claiming to be responsible for the update, so I'm disallowing it. If I were you I would freak the **** out right about now and see if you can remove it. Trust me that you don't want to end up where I'm at. Good luck.
It's been out for a while now. Did everyone else get it already?
MacGuy2006 said:
It's been out for a while now. Did everyone else get it already?
Click to expand...
Click to collapse
The updates are available at Full OTA Images, so if you haven't yet received a notification to update, you can simply sideload it.
Pretty sure those of us with TMo are "de-prioritized", for the interim, for some reason that's not terribly public (I can see why TMo wouldn't want it to be, obviously). There's a discussion on AndroidCentral, but nothing really meaningful, just a bunch of me-too responses, and a handful of those with other carriers, who got the notification the first week of Jan.
I'm speculating on some of that thread, because I don't know how the carrier interop works in terms of un-branded devices, really, but I do wonder about the mechanism in this regard, if anyone knows?
This is odd because I was able to get the January update on the 5th on a T-Mobile MVNO Boost mobile? If it is blocked by T-Mobile wouldn't that affect the MVNO as well? Maybe I got it before it was pulled?
pgrey2 said:
Pretty sure those of us with TMo are "de-prioritized", for the interim, for some reason that's not terribly public (I can see why TMo wouldn't want it to be, obviously). There's a discussion on AndroidCentral, but nothing really meaningful, just a bunch of me-too responses, and a handful of those with other carriers, who got the notification the first week of Jan.
I'm speculating on some of that thread, because I don't know how the carrier interop works in terms of un-branded devices, really, but I do wonder about the mechanism in this regard, if anyone knows?
Click to expand...
Click to collapse
I am on Google Fi...
Although I was considering switching to T-Mobile, as I went on an extended vacation in Europe and after two and a half months Google cut off my service without warning, claiming that it is only for those living in the US (which I do) and that I can only reactive once back in the US. I was left with no data and no map live services in a strange city, and no way to call hotels, so I have been looking for alternatives that provide better service and better customer service.
Google-Fi was great at the beginning, but like most things Google, it gets worse as time goes by. They censor Search and YouTube, I guess why not censor where and how long you travel...
MacGuy2006 said:
I am on Google Fi...
Although I was considering switching to T-Mobile, as I went on an extended vacation in Europe and after two and a half months Google cut off my service without warning, claiming that it is only for those living in the US (which I do) and that I can only reactive once back in the US. I was left with no date and no map services in a strange city, so I have been looking for alternatives that provide better service and better customer service.
Google-Fi was great at the beginning, but like most things Google, they it gets worse as time goes by. They censor Search and YouTube, I guess why not censor where and how long you travel...
Click to expand...
Click to collapse
I learned this lesson the hard way and learned that, when traveling internationally and need maps/gps, to download an app that can be downloaded with current info and used offline; gps doesn't need data to work, just to download data for the maps...
But hopefully T-Mobile gets it figured out soon! It's weird that usually carriers are on top of things when it comes to the update releases tailored to them; Verizon had its own version a couple months back. I'm pretty certain that, once T-Mobile has things figured out, Google will have to publish/host a T-Mobile factory images on its developers site as well...
Just FYI -- I manually installed the January update since I am rooted and use Pixel Flasher anyways and it is easy.
Now I wish I hadn't -- cellular seems much more flakey (using LTE instead of 5G on TMobile and connections timing out) and there is a pretty massive BT issue where the phone no longer connects to several cars (Toyota, Subaru, Kia and others are mentioned). I can no longer connect it to my 2011 Subaru, so first time in 12 years I have not had bluetooth audio in the car.
Kinda sucks...
I would sit this one out....
MetroWestMA said:
Just FYI -- I manually installed the January update since I am rooted and use Pixel Flasher anyways and it is easy.
Now I wish I hadn't -- cellular seems much more flakey (using LTE instead of 5G on TMobile and connections timing out) and there is a pretty massive BT issue where the phone no longer connects to several cars (Toyota, Subaru, Kia and others are mentioned). I can no longer connect it to my 2011 Subaru, so first time in 12 years I have not had bluetooth audio in the car.
Kinda sucks...
I would sit this one out....
Click to expand...
Click to collapse
Except I'm on T-Mob and have none of those problems
HipKat said:
Except I'm on T-Mob and have none of those problems
Click to expand...
Click to collapse
Google Pixel owners seeing Bluetooth and Android Auto issues following January update
The January 2023 update for Google Pixel phones appears to be causing issues with Bluetooth and Android Auto in cars.
9to5google.com
https://www.reddit.com/r/GooglePixel/comments/1045k5g
It's not just me and my car and I tried everything - it won't connect...
MetroWestMA said:
Google Pixel owners seeing Bluetooth and Android Auto issues following January update
The January 2023 update for Google Pixel phones appears to be causing issues with Bluetooth and Android Auto in cars.
9to5google.com
https://www.reddit.com/r/GooglePixel/comments/1045k5g
It's not just me and my car and I tried everything - it won't connect...
Click to expand...
Click to collapse
Must be certain models of Audio units/drivers. I can connect to my Work Van - 2021 Dodge Pro-master and my buddies truck, 2014 GMC Sierra with no problems
MetroWestMA said:
Google Pixel owners seeing Bluetooth and Android Auto issues following January update
The January 2023 update for Google Pixel phones appears to be causing issues with Bluetooth and Android Auto in cars.
9to5google.com
https://www.reddit.com/r/GooglePixel/comments/1045k5g
It's not just me and my car and I tried everything - it won't connect...
Click to expand...
Click to collapse
VAG and Hyundai issue maybe? January update here, connects to my 2022 C-Class no issue for audio, calls and wireless Android Auto.
MetroWestMA said:
Google Pixel owners seeing Bluetooth and Android Auto issues following January update
The January 2023 update for Google Pixel phones appears to be causing issues with Bluetooth and Android Auto in cars.
9to5google.com
https://www.reddit.com/r/GooglePixel/comments/1045k5g
It's not just me and my car and I tried everything - it won't connect...
Click to expand...
Click to collapse
No issue with my January update paired to Mazda HU.
But then i won't argue that some users might indeed have issues.
T-Mo is trying to do something new and fancy with the way they allow/force users to connect to their network. This is the MAIN reason they are delaying the update. Personally I do not care about the Bluetooth issue but as for LTE/5G connections...they MUST work 24/7! So I would say the best bet is to wait until whatever is broken gets fixed. YMMV
MetroWestMA said:
Google Pixel owners seeing Bluetooth and Android Auto issues following January update
The January 2023 update for Google Pixel phones appears to be causing issues with Bluetooth and Android Auto in cars.
9to5google.com
https://www.reddit.com/r/GooglePixel/comments/1045k5g
It's not just me and my car and I tried everything - it won't connect...
Click to expand...
Click to collapse
The "ok google" not doing anything issue is not limited to the Jan update. I am on the December update (on T-mo), and the "ok google" doesn't work - the hardware button on my steering wheel works, so I'm using that for now.
Wow. This is crazy. Remote execution vulnerabilities that don't even require user interaction, just your phone number. Google says to either turn off both VoLTE and WiFi Calling or update to March update. Pixel 6 series is screwed until Google gets their update out.
Definitely not a good look for Samsung!
Google: Turn off VoLTE, Wi-Fi calling due to severe Exynos modem vulnerabilities on Pixel 6, more
Google found severe vulnerabilities with Exynos modems used on the Pixel 6 and Samsung phones that warrant disabling VoLTE & Wi-Fi calling...
9to5google.com
funny and crazy
I understand the concern but how many people in the world even know about, or how to actually execute any of these exploits AND has your phone number AND you have the type of phone for it to even work? YMMV
jaseman said:
I understand the concern but how many people in the world even know about, or how to actually execute any of these exploits AND has your phone number AND you have the type of phone for it to even work? YMMV
Click to expand...
Click to collapse
If a threat actor wants to exploit this, they just have to start running numbers until they hit matches. It would be pretty trivial because they don't need anything else but for you to have an affected device that has VoLTE or wifi calling enabled. There is a pretty long list of affected devices from both Samsung and Google, including many midrange devices that have a much higher market share, so the potential attack surface is quite high. The oldest chipset on the list, the Exynos 850 (Samsung updated the list since the article was published to add more affected chipsets including this one), is from 2020, and the newest, the Shannon 5300, is the modem in the Pixel 7 series. This exploit covers close to 3 years worth of Samsung phones, that's a crazy amount of vulnerable devices.
If you don't believe there are groups sophisticated enough to pull off these attacks en masse, you haven't been paying attention to all of the breaches over these last years. Something like this would be a dream come true for them because there's no indication you've been breached and exploits like this can be used to disable system updates so it never gets patched. Lets also not forget that many people don't even bother to keep their devices up to date to begin with. My partner's phone is probably a year behind on updates and he leaves his Windows desktop sitting there with the update icon until it forces him to actually do it.
jaseman said:
I understand the concern but how many people in the world even know about, or how to actually execute any of these exploits AND has your phone number AND you have the type of phone for it to even work? YMMV
Click to expand...
Click to collapse
This is what I often wonder. How bad are all these DOOMSDAY vulnerabilities. I think most are overblown. Possible, but over-hyped.
EtherealRemnant said:
If a threat actor wants to exploit this, they just have to start running numbers until they hit matches. It would be pretty trivial because they don't need anything else but for you to have an affected device that has VoLTE or wifi calling enabled. There is a pretty long list of affected devices from both Samsung and Google, including many midrange devices that have a much higher market share, so the potential attack surface is quite high. The oldest chipset on the list, the Exynos 850 (Samsung updated the list since the article was published to add more affected chipsets including this one), is from 2020, and the newest, the Shannon 5300, is the modem in the Pixel 7 series. This exploit covers close to 3 years worth of Samsung phones, that's a crazy amount of vulnerable devices.
If you don't believe there are groups sophisticated enough to pull off these attacks en masse, you haven't been paying attention to all of the breaches over these last years. Something like this would be a dream come true for them because there's no indication you've been breached and exploits like this can be used to disable system updates so it never gets patched. Lets also not forget that many people don't even bother to keep their devices up to date to begin with. My partner's phone is probably a year behind on updates and he leaves his Windows desktop sitting there with the update icon until it forces him to actually do it.
Click to expand...
Click to collapse
"all of the breaches over these last years"
Are these breaches happening on individual cell phones or on company enterprise computers? I know of nobody that has ever had a breach on their cell phone unless they are accessing very shady web sites themselves. YMMV
jaseman said:
"all of the breaches over these last years"
Are these breaches happening on individual cell phones or on company enterprise computers? I know of nobody that has ever had a breach on their cell phone unless they are accessing very shady web sites themselves. YMMV
Click to expand...
Click to collapse
I was talking about the sophisticated corporate breaches. That takes much more work than this would really. Having millions of vulnerable devices out there, you can bet they're going to start working on this ASAP. Being able to remotely take over a device with just a phone number is a pipe dream for hackers. Getting in at the baseband level... Yikes.
It's bad enough that recent Pixel 7 builds have completely broken wifi calling and n25.
Samsung and Google treat the modem and /vendor like a playground and afterthought.
Have to run the DP1 modem on DP2 for it to work properly. Now I probably have to use the QPR3 or DP2 modem depending on what the bootloader allows or accept the risk.
LLStarks said:
It's bad enough that recent Pixel 7 builds have completely broken wifi calling and n25.
Samsung and Google treat the modem and /vendor like a playground and afterthought.
Have to run the DP1 modem on DP2 for it to work properly. Now I probably have to use the QPR3 or DP2 modem depending on what the bootloader allows or accept the risk.
Click to expand...
Click to collapse
I honestly love that Google doesn't just use Samsung's modems but does extensive security tests on them via fuzzing etc. to find these kinds of exploits before others do (NSA, etc.)
kudos to project zero for finding these
what is n25?
and honestly:
"playground and afterthought", really? what is your argument here. that's just flaming and bull****.
Dj_Fex said:
I honestly love that Google doesn't just use Samsung's modems but does extensive security tests on them via fuzzing etc. to find these kinds of exploits before others do (NSA, etc.)
kudos to project zero for finding these
what is n25?
and honestly:
"playground and afterthought", really? what is your argument here. that's just flaming and bull****.
Click to expand...
Click to collapse
Throughout the Pixel 7's life, the phone has regressed in its phone capabilities.
Recent updates break wifi calling and it's very easy to replicate. It also disabled the n25 5G frequency band for T-Mobile users. It effectively breaks 3CA carrier aggregation for some people with bad spectrum allocations. Until a few months ago, updates had also disabled the ability for a call to use VoNR and be made completely over 5G. I've had to do countless mods and firmware mixes to fix these.
It's a playground because I see the regressions build by build. I've had to raise bug reports for most of them. There is no quality control and these changes are rarely mentioned in release notes.
Sucks, but that stuff will get fixed eventually. it's not one of those issues many people actually notice and most people don't rely on both of these features.
and I think Europe doesn't deploy n25. so less people to report bugs like these. Bugs happen. Google didn't build the baseband. I don't wanna tell you don't blame them, but rather: live with it and don't mark the phone as unusable.
I get it you want to blow some steam
The only two things I experienced so far:
sometimes (very rarely) the screen starts flickering/going black a bit. (not always waking up instantly staying black for some time) like it doesn't get enough power. it might only happen when the battery is close to 0 percent and you then start charging the phone. not sure, it goes away most of the time. (maybe it was fixed by Joe). the other bug is more annoying to me personally: the recents screen breaks every now and then, but a restart fixes that.
broken means: it doesn't list recent apps I opened, but only the ones I used some time ago, opening the activities therefore fails because they were closed by now. I can close all of them but opening the recents screen the same closed activities reappear again.
it's annoying because it breaks my workflow. I can't switch back and forth between apps by swiping the bottom bar of the screen. it just sends me to the home screen since the (wrong) "last" activity was closed already.
jaseman said:
"all of the breaches over these last years"
Are these breaches happening on individual cell phones or on company enterprise computers? I know of nobody that has ever had a breach on their cell phone unless they are accessing very shady web sites themselves. YMMV
Click to expand...
Click to collapse
Sophisticated attackers go for anything, the wannacry ransomware was based on Eternalblue which used a vulnerability in smb1 and this caused major problems for organizations.
A vulnerability was found in IOS and to the researcher's surprise websites were sending out this code before the exploit was made public, this video from about 5 minutes in describes it quite well.
Modem is fixed in March update for P7(P)
Look at CVE 24033
for people running custom roms: do they need to flash basebands themselves or can the custom roms do this with their android security patches nowadays? (asking for a friend with a Pixel 6a. Yes, I know the Pixel 6a wasn't patched, yet ^^)
Dj_Fex said:
and most people don't rely on both of these features.
Click to expand...
Click to collapse
Seeing how many countries are in the process of getting rid of 2G and 3G, without one of those features enabled, you can't make calls.
danmaman said:
Modem is fixed in March update for P7(P)
Look at CVE 24033
Click to expand...
Click to collapse
I said this in the first post when I was warning people to update to the March update.
Im still running the November update from when I first bought the phone... Rooted and bootloader unlocked TMobile variant, can anybody link me the steps for updating? Unsure if I can jump from November straight to this version?
jake.99x3 said:
Im still running the November update from when I first bought the phone... Rooted and bootloader unlocked TMobile variant, can anybody link me the steps for updating? Unsure if I can jump from November straight to this version?
Click to expand...
Click to collapse
You can by dirty flashing the March security patch.
EtherealRemnant said:
Seeing how many countries are in the process of getting rid of 2G and 3G, without one of those features enabled, you can't make calls.
Click to expand...
Click to collapse
Is VoNR the same as VoLTE now? I can take calls just fine. Telekom in Germany has no 3G left and I disabled 2G in the settings and calls work just fine. Just no "HD" for whatever reason. Telekom is an eSIM. "HD" calls work for my other regular Nano Sim though.
So yeah as I said: no calls in 5G is also no deal breaker right now.
edit: I disabled the nano sim and I disabled wifi calling. and calls over lte+ on my Telekom esim still work.
Not_Purgatory said:
You can by dirty flashing the March security patch.
Click to expand...
Click to collapse
Did anyone upload a zip on here? I'm fairly certain (from past phones) that OTAs fail once you unlock the Bootloader.
the Telekom sim is definitely using VoLTE. If I disable VoLTE in the settings I can't take calls unless I enable 2G again.
Now I have to find out why HD voice doesn't work
If VoLTE doesn't work for you, then it might not have been allowed for/activated by your carrier for the Pixel 7 devices.
Maybe call your ISP and ask them.
Dj_Fex said:
Is VoNR the same as VoLTE now? I can take calls just fine. Telekom in Germany has no 3G left and I disabled 2G in the settings and calls work just fine. Just no "HD" for whatever reason. Telekom is an eSIM. "HD" calls work for my other regular Nano Sim though.
So yeah as I said: no calls in 5G is also no deal breaker right now.
edit: I disabled the nano sim and I disabled wifi calling. and calls over lte+ on my Telekom esim still work.
Did anyone upload a zip on here? I'm fairly certain (from past phones) that OTAs fail once you unlock the Bootloader.
Click to expand...
Click to collapse
Use the official Pixel Web based flashing tool