Related
I turned on my tablet the other night and on the screen was a system dialog box that said a new security profile (or something like that) was applied. It gave a number of the build but I can't remember what it was. I thought by clicking OK I would get some more info, but that was it. I checked for updates and there was nothing. I got no other information.
Anyone else see anything like this? I guess it's possible it was linked to some app I have installed. But the popup window definitely looked like a system framework box.
Edit: I guess I did find on the Security tab in the settings that it is set to Automatically install new security policies. So that would make sense, just wondering what might be included in this update?
I'm pretty sure that would be the same security profile updated to version 013 message that I saw as well. If I am to guess, we can thank Samsung Knox for that message.
<synicism>
Thank you samsung for applying a security profile update that I can't see the details of to a device I don't want Knox installed on in the first place.
</synicism>
<rant>
Wish they would put as much effort into getting an update released that fixes bluetooth keyboards. Or how about functional support for BT 4.0, like it suggests on the box? Yes, you can pass the buck to Google on that one, to which I reply, why was this tablet released on 4.3 when these bugs were known?
I generally love this tablet, but the defunct bluetooth combined with screen mirroring related reboots and the Knox warranty crap really has me waiting for someone else to release a non-crippled 10.1 high dpi tablet with an active digitizer so there is some incentive for Samsung to get its act together. Toshiba isn't even worth mention.
</end rant>
dpersuhn said:
I'm pretty sure that would be the same security profile updated to version 013 message that I saw as well. If I am to guess, we can thank Samsung Knox for that message.
<synicism>
Thank you samsung for applying a security profile update that I can't see the details of to a device I don't want Knox installed on in the first place.
</synicism>
<rant>
Wish they would put as much effort into getting an update released that fixes bluetooth keyboards. Or how about functional support for BT 4.0, like it suggests on the box? Yes, you can pass the buck to Google on that one, to which I reply, why was this tablet released on 4.3 when these bugs were known?
I generally love this tablet, but the defunct bluetooth combined with screen mirroring related reboots and the Knox warranty crap really has me waiting for someone else to release a non-crippled 10.1 high dpi tablet with an active digitizer so there is some incentive for Samsung to get its act together. Toshiba isn't even worth mention.
</end rant>
Click to expand...
Click to collapse
This message?
What's the harm? It's updating something already in place that you can't evaluate so why be up in arms about an update that you can't see to evaluate either? Samsung updates a bunch of stuff passively so it's kind of a trust exercise. Since passively doing bad things to people's s/w and h/w without their consent is a sure way for a publically held company to make the front pages of the news (in a financially damaging way) I'm trusting them until given a reason I shouldn't. Do you know what Google's changed security policy enforcement wise when they roll out updates to Android?
BT keyboard usage isn't broken. You need to disable the on-screen keyboard the first time you pair it. From then on the on-screen keyboard's automatically disabled when the BT keyboard is connected.
KNOX is benign when not in use with the exception of the warranty flag that detects the use of unknown ROMs being loaded on the device. I use KNOX on my N3 and N10.1-14 and like it. I also haven't had a single issue related to it.
And it's here to stay.
http://www.infoworld.com/d/mobile-t...-move-blackberry-users-android-and-ios-230343
Go do a little homework on android 4.3 and bluetooth keyboard issues, then I'll be glad to talk about constant disconnects, key repeats, etc. The note 2014 is even worse than other 4.3 tabs in the bluetooth dept. I have gone through 4 BT keyboards so far and each has disconnect and/or key repeat issues in a major way. This is in no way related to disabling the soft keyboard.
Like I said, it starts with google and some will lay the blame there and hold samsung harmless. I guess I have a higher expectation of quality control and since I bought a samsung product and have no direct relationship with google. Samsung selected this version of android for installation, so I think it is very reasonable to hold them accountable for the functional state of the resulting device.
As for Knox, I'd love it for managing enterprise devices as an MDM platform, but there is a reason MDM software has to be INSTALLED on other platforms. It's intrusive by its very nature. I'm not using this device in a corporate environment, it's my personal tablet. As such, knowing that Samsung has the reigns on a corporate MDM tool that wasn't advertised, I had no say in adding or removing, and also provides no visibility into what they consider an appropriate security policy, isn't exactly inspiring trust. You can trust them all you want, I don't see them as being any better than Apple at this point.
My ultimate point is simple. Samsung is wasting resources reinventing the MDM wheel and forcing it on everyone (whether they want it or not) while there are numerous functional issues with this tablet that aren't being addressed. I see that as a questionable ranking of priorities. If they're worried about device security, how about starting by keeping up with updates to The base android install.
---------- Post added at 02:53 PM ---------- Previous post was at 02:46 PM ----------
Also worth mentioning is the complete lack of release notes that go along with the system updates. Think about that for a minute. How do I, as a user, ever know from one update to the next what issues have been addressed, what functional changes have been made, or what areas might have been modified so I can make an educated decision regarding if/when to update?
Samsung has proven that they can and will remove things from one version to the next as they see fit. Why can't they actually tell people what to expect by putting out proper release notes like any respectable software developer would be expected to do? Samsung lacks the skill or capability to do what developers of $2 apps in the play store are capable of? Surely you jest...
Hello everybody,
I hope to bump into someone with the same issue.
I got a ZE551ML 32GB, installed Shazam app, restored my taglist, wanted to restore Spotify connection, but I can't see "Connect to Spotify" option in settings.
It just shows "Connect to Rdio" - it doesn't check for the apps to be installed, so it shows that even if i don't have Rdio app on my phone.
I'm a Spotify Premium user, I was loving this feature on my previous Nexus 5, so it's a bit annoying.
Since I love this phone, I suggested it to some friends who bought it as well: all of them have the same issue.
This is still happening, since the day I bought my phone.
I opened a ticket to Shazam, they checked for the version of the phone (I live in Italy, phone is official WW version with 2yrs Italian warranty), checked for SIM card provider (I had two SIM cards, both from italian providers, H3G and TIM), checked for the latest version both of app and firmware. Nothing to do, "it should just work" they said.
I sent an e-mail to Asus support, but they replied they can't cover third party issues.
I replied that's not true, because on many new firmware's release notes, you can easily find something like "improved/fixed 3rd party app compatibility/issues", like for WW_2.18.40.12 release notes, where you can find "8. Fixed 3rd party app issue.".
I was hoping this was referring to my ticket, but no luck.
Opened a thread in official Asus forum, just one user replied having the same issue, but no replies from Asus.
It's bit old nowadays, but nothing has changed since then, even with latest updates both of app and firmware.
Since nothing changed even after latest OTA WW_2.20.40.63 and latest Shazam upgrade to 5.9.0-150904, I finally decided to go Cyanogen.
After flashing CM12.1, big suprise: installed Shazam app and... nothing has changed!
It just keeps showing "Connect to Rdio" but not "Connect to Spotify".
I can't figure out on which side the issue is.
Sorry for not posting sources but I'm not allowed yet to post links.
Thanks for reading.
Hi Soleinvisibile.
I'm in France and I'm having exactly the same problem. It seems like the problem just doesn't exist since I can't barely find any clue about this. It's quite incredible...
It's no big deal but it's quite annoying, this feature was the reason I used Shazam. It really seems to affect only Asus Zenfones so I just don't understand what is going on...
I know it won't help, but you're not alone! We can try to keep in touch here if any info comes out. Thanks for your attention. Bye.
Hi Cheumeuneu,
Thank you so much for your reply!
My post was quite verbose and I thought to shorten it, I guess its lenght wouldn't help to let the issue come out, as evidenced by zero replies since.
Anyway same for me, the feature was the reason I've been using Shazam, it's pretty annoying and even worse considering the lack of clues about it.
To me, the weirdest thing is that the issue is persistent across stock and custom ROM.
Did you root and flash or kept it stock?
Bye,
Enrico
Mates,
I don't know if the Kevo/Kwikset app folks are dumb, lazy or if there is some fee they have to pay to support new phones, but hear my tale of woe, with a happy ending (a minstrel on a mandolin is playing in the background as you read this).
I put Kevo locks everywhere when they first came out with android support. When they work, it is one less key I have to carry, one more thing my everpresent phone can do. They were announced as partners for the Gear S2 which, as we all know, is bull. The tech writers who said it worked were clearly Samsung lapdogs.
The Kevo website says that the app won't work on the Galaxy S7 edge but it did. Right from the start, right out of the gate. Then T-Mobile rolled out a patch last week and it stopped. Nothing. Bupkus. Google Play says the app is not supported by my device.
A little bit of searching led to the actual newest Kevo apk. I downloaded it, deleted the old app, installed it and voila! Back in business. The new version supports remote open and close, which I haven't checked yet- I bought an upgraded lock but it isn't installed.
So, there you have it. I have no idea why Kevo/Kwikset/Unikey didn't test with the newest phones, why they don't know it works or whatever. Their developers are much more interested in supporting iOS and the sheeple that use it, but it will work for us too!
where did you find the latest? i looked for almost 2 hours and the best i could come up with was the 0.99 beta in the google groups. had to sideload an app that lets you change your device to trick Play into letting you install it.
Googled Android kevo apk, found version 1.2.57.2p everywhere. I presumed that was the latest since it has the remote buttons on it.
yeah i saw those results as well, but none of the apk downloaders worked for me. several even said their 'device' was incompatible, which was the same problem i was having.
I'm in the same boat. I have an S7 Edge and while kevo still works with just the proximity and tap lock to open...I've never been able to get the tap to unlock/lock work. Even on my moto360 (gen1) kevo force closes non stop. Another problem I had was my old S5 was on Lollipop and it worked, but then Tmo rolled out the update to MM and now it doesn't even see the lock. I've had multiple emails to Kevo and the only thing I get is that "We're sorry, we have no plans to support MM".
If you got anything to help out with Kevo working on Marshmallow, then I'd appreciate it as well!
I might be a little late on the the subject but I had the Kevo app since the beginning from my Note 4 on KK all the way up to My Note 5 on MM. I rarely use my Moto 360 (1) to open the door but this time I did and the watch went haywire and kept showing a notification indicating that the app is no longer working. So I decided to uninstall the Kevo app and then proceeded to sync the watch and phone, stopping the annoying notification. When I went to the app store to reinstall I found the "phone not compatible"..
Well, decided to sideload to have the Kevo app to look and work the same way I had it before.. after several attempts I figured it out. 1st sideload the Kevo 0.9.58p apk, sign in, then sideload the updated version 1.2.57.2p and it will finally look and feel like the updated one on Lollipop. Sefar is right, why the devs were so lazy in checking for compatibility is beyond me but it works.!!
Sent from my SAMSUNG-SM-N920A using Tapatalk
Anyone else have the issue with enabling chat features in Messages? I'm not sure if it is a carrier issue or an issue with Messages or the device? I've tried contacting my carrier and getting them to reset my RCS profile, but apparently they are having "issues" with doing this. I have read that others have had this issue and replacing the sim card has fixed it. I tried doing that yesterday to no avail. I get the attached message and then nothing ever happens. I've tried clearing cache and data for Messages, trying again, rebooting, etc. No go. This was a feature I really wanted to get enabled on this device. My carrier (Rogers) does offer RCS messaging, but this simply is not working or not provisioning with the carrier server.
Since no one ever responded here and the carrier still hasn't come up with a fix, here is what I did to enable chat features and get past that "excuse the wait..." screen:
Restarted the device
Go to settings-apps-android messages and then force stop
Launch Google Play and uninstall messages
Then go back to Google Play and install latest version again
Chat features are then enabled. Not that it's that big of a deal because if the people you are texting don't have a phone that supports RCS and even if they do, if they don't have chat features turned on, then it still won't work. It was simply bugging me because the option was there and I couldn't get it enabled.
I am with rogers and have same issue. How do you uninstall messages? It only uninstall its update. Do you root to uninstall complete messages app?
I'm also with Rogers, and this is the solution that worked for me. I found it on the Rogers Community forums.
You have to disable the app called Carrier Services, now setup RCS through the Messages app.
Then you can reenable Carrier Services.
I also rebooted, but I don't know if that's necessary. I hope this helps.
zeeshee said:
I am with rogers and have same issue. How do you uninstall messages? It only uninstall its update. Do you root to uninstall complete messages app?
Click to expand...
Click to collapse
If you force stop it, you can uninstall. It may only uninstall the updates, but it does uninstall after you finally get it to force stop. I had to try force stop a couple of times.
RPAusCan said:
You have to disable the app called Carrier Services, now setup RCS through the Messages app.
Then you can reenable Carrier Services.
Click to expand...
Click to collapse
I didn't have to do this portion. When I went into Messages after doing my steps, chat features were automatically enabled.
What was really funny is Rogers kept sending me emails telling me they were "working on a fix but hadn't found one yet." When I got another email yesterday stating this from them, I chatted with tech support and told them I had fixed it myself so they could stop sending me emails about them working on it. Then I get an email from them stating that "they had fixed my issue..." LOL. Sure, sure you did.
I can't honestly say this was the cause, but my issues didn't happen until I updated to the January Security Patch. I'll try these steps tonight to see if I can get them re-enabled.
TheIgster said:
Since no one ever responded here and the carrier still hasn't come up with a fix, here is what I did to enable chat features and get past that "excuse the wait..." screen:
Restarted the device
Go to settings-apps-android messages and then force stop
Launch Google Play and uninstall messages
Then go back to Google Play and install latest version again
Chat features are then enabled. Not that it's that big of a deal because if the people you are texting don't have a phone that supports RCS and even if they do, if they don't have chat features turned on, then it still won't work. It was simply bugging me because the option was there and I couldn't get it enabled.
Click to expand...
Click to collapse
Does Rogers sell the Pixel 3 in their stores? I'm curious because I have purchased my Pixel 3 from Google and I'm using it on a carrier (T-Mobile) who doesn't sell the P3, but is starting to support RCS. However, their version of RCS support appears to only be enabled through a carrier supplied software update to T-Mobile branded phones. I'm afraid I'll never be able to use RCS on the ONE phone that comes with RCS support out of the box.
But if you were able to get RCS support without Rogers selling the phone, then there may still be hope for me someday!
PuffDaddy_d said:
Does Rogers sell the Pixel 3 in their stores? I'm curious because I have purchased my Pixel 3 from Google and I'm using it on a carrier (T-Mobile) who doesn't sell the P3, but is starting to support RCS. However, their version of RCS support appears to only be enabled through a carrier supplied software update to T-Mobile branded phones. I'm afraid I'll never be able to use RCS on the ONE phone that comes with RCS support out of the box.
But if you were able to get RCS support without Rogers selling the phone, then there may still be hope for me someday!
Click to expand...
Click to collapse
Yup. Both the Pixel 3 and Pixel 3 XL in their stores, online,etc.
If anyone's RCS won't work after clicking "yes, I'm in", just disable carrier services, go back to messages and opt in again. Once working, enable carrier services.
Chat features work in Messages App by Google LLC for me nearly everywhere now:
- Huawei AL10 P9 running Emui 8 Oreo on Telekom network in Hungary on WiFi (no Data subscription)
- Samsung Note 4 N910V LineageOS 16.0 Pie on Telekom network in Hungary on WiFi and Data
- Samsung Note 4 N910V LineageOS 16.0 Pie on GoogleFi roaming in Hungary on WiFi (cannot get LTE Network/Data connected to any tower)
- new device Google Pixel 2 XL Android Q on GoogleFi roaming in Hungary (will test in July)
On my home MikroTik router WiFi, where I run a domain and webserver, i forward port 80/443 to the webserver.
This is the only WiFi network, where I cannot use chat features for unknown reasons.
QUESTION: WHAT PORT(S) DOES RCS / CHAT FEATURES USE ON A WIFI NETWORK FOR COMMUNICATION TO OTHER PARTY AND THE PROVIDER SERVER (IN CASE OF FILE TRANSFER)
Google Fi support and Telekom HU Support dont understand the simple question or they resist to answer me, by replying constantly with the copy/paste of troubleshooting guides that I read all already. Either those are bot replies, or Google started to employ Level 1 people that are forced to reply automatic text. Telekom HU Support always was a big pain in the ass.
did you every figure it out?
Did you ever get this figured out? I've put my router in full DMZ and I still can't get RCS chat features to work on my home WiFi … but They USED TO WORK until a month or two ago... not sure when, It was my wife who noticed. tred 4 phones on 3 carriers, non work. many businesses have notices on the front doors too because it's killing employee's batteries while they work all day. Google refuses to answer.
ant0nwax said:
Chat features work in Messages App by Google LLC for me nearly everywhere now:
- Huawei AL10 P9 running Emui 8 Oreo on Telekom network in Hungary on WiFi (no Data subscription)
- Samsung Note 4 N910V LineageOS 16.0 Pie on Telekom network in Hungary on WiFi and Data
- Samsung Note 4 N910V LineageOS 16.0 Pie on GoogleFi roaming in Hungary on WiFi (cannot get LTE Network/Data connected to any tower)
- new device Google Pixel 2 XL Android Q on GoogleFi roaming in Hungary (will test in July)
On my home MikroTik router WiFi, where I run a domain and webserver, i forward port 80/443 to the webserver.
This is the only WiFi network, where I cannot use chat features for unknown reasons.
QUESTION: WHAT PORT(S) DOES RCS / CHAT FEATURES USE ON A WIFI NETWORK FOR COMMUNICATION TO OTHER PARTY AND THE PROVIDER SERVER (IN CASE OF FILE TRANSFER)
Google Fi support and Telekom HU Support dont understand the simple question or they resist to answer me, by replying constantly with the copy/paste of troubleshooting guides that I read all already. Either those are bot replies, or Google started to employ Level 1 people that are forced to reply automatic text. Telekom HU Support always was a big pain in the ass.
Click to expand...
Click to collapse
ptv83 said:
Did you ever get this figured out? I've put my router in full DMZ and I still can't get RCS chat features to work on my home WiFi … but They USED TO WORK until a month or two ago... not sure when, It was my wife who noticed. tred 4 phones on 3 carriers, non work. many businesses have notices on the front doors too because it's killing employee's batteries while they work all day. Google refuses to answer.
Click to expand...
Click to collapse
I never succeeded yet
I assume (as a RCS novice) support has no idea what RCS is and Google has support agents that have also no idea and the people who developed this left the company or got kicked out...
I also think that my webserver port 80 and 443 causes this, I will try disabling the forward cause my webserver died waiting for replacement unit
ant0nwax said:
I also think that my webserver port 80 and 443 causes this, I will try disabling the forward cause my webserver died waiting for replacement unit
Click to expand...
Click to collapse
I changed the forwarding to not forward ports 80 and 443 to a dedicated IP, still did not help
the router behind my mikrotik router and its wifi is capable of getting a status Connected
the mikrotik router itself and its wifi cannot get beyond Connecting...
I wonder if that might have to do something with IPv6?
Hi. After resetting the phone to factory settings, I can not turn on the chat features, the message configures is displayed, after a few attempts the message "confirm your number" appears, after three attempts the message "limit exceeded try again tomorrow" and so on overnight trying. There is a solution to this problem?
g323 said:
There is a solution to this problem?
Click to expand...
Click to collapse
Hi,
Do you have Data activated during setup? Could help.
Good luck...
Sébastien.
Yes, I have, matches have been with this for a month and I even turned off the chat for 8 days as I write in google help, but it did not work. of course, cleaning the data did nothing
Kind of bummed, ahh well.
Now that that is unrooting and relocking is out of the way... have to say I am sad about this one. I was excited for it, spent HOURS getting it all setup. You all know the deal, lol.
Ran into two issues that I found that apparently showed up with OnePlus' implementation of Android 12 and persist even still... all this time later.
1. The Display Timeout option is not properly (normally) exposed to things like Tasker
2. Call redirection (for things like Google Voice) is broken
I recognize that these are probably issues that 90% of people don't notice/care about, but they're also extremely well documented and reported in all of the normal OnePlus places. I find it bonkers that after all this time, those issues still exist. I use Google Voice to make calls as needed for business when I am on the move without exposing my personal number (and to avoid carrying two devices). I made a number of calls before realizing that it was not working properly (since it's not obvious).
Coupled with some of the little Pixel things I was fine giving up... eh. Just feel sour about long time bugs like that.
Maybe I will try the OnePlus 12 next year. For now, the OnePlus 11 goes back to Amazon.
Just a little rant into the void.
I can't believe they still haven't fixed call redirection. That's been an issue since Android 12 on the OP9. It was so annoying I just switched Google Voice to prefer wifi/mobile data and used the dialer in the app to work around it.
EtherealRemnant said:
I can't believe they still haven't fixed call redirection. That's been an issue since Android 12 on the OP9. It was so annoying I just switched Google Voice to prefer wifi/mobile data and used the dialer in the app to work around it.
Click to expand...
Click to collapse
Yeah... I could work around that... yes, it would be annoying when I am getting in the car to remember to have to get out of the parking lot (off wifi) before making the call... but it would end up ok. Then sometimes (hit or miss in my experience) the call would get messed up when I arrive somewhere and connect to wifi again during the call).
And I could work around the Display Timeout issue using different apps and such.
And workaround this and that, etc. But it's just BS to me. Like... fix these old bugs that you create in your build that don't exist in Android/every other build. Admittedly, I was really annoyed at the several calls I made where I had no idea the wrong number was being shown on the receivers ID. Soured the whole thing for me.
dmarden said:
Yeah... I could work around that... yes, it would be annoying when I am getting in the car to remember to have to get out of the parking lot (off wifi) before making the call... but it would end up ok. Then sometimes (hit or miss in my experience) the call would get messed up when I arrive somewhere and connect to wifi again during the call).
And I could work around the Display Timeout issue using different apps and such.
And workaround this and that, etc. But it's just BS to me. Like... fix these old bugs that you create in your build that don't exist in Android/every other build. Admittedly, I was really annoyed at the several calls I made where I had no idea the wrong number was being shown on the receivers ID. Soured the whole thing for me.
Click to expand...
Click to collapse
Totally agreed. I dumped my OnePlus 9 for the Pixel 7 Pro and chose the S23 Ultra over the much cheaper OnePlus 11 because of my software experience with the 9.
EtherealRemnant said:
Totally agreed. I dumped my OnePlus 9 for the Pixel 7 Pro and chose the S23 Ultra over the much cheaper OnePlus 11 because of my software experience with the 9.
Click to expand...
Click to collapse
I would love to try the S23 Ultra, but from what I've read... the hoops to unlock and root are just a pain. Getting an import model, etc etc.
I root for many fewer reasons than I once did... but I still have reasons to do it. Someday.
dmarden said:
I would love to try the S23 Ultra, but from what I've read... the hoops to unlock and root are just a pain. Getting an import model, etc etc.
I root for many fewer reasons than I once did... but I still have reasons to do it. Someday.
Click to expand...
Click to collapse
Yeah I kept my Pixel for my rooting needs (really just for Network Signal Guru) and haven't missed it at all on the S23U. There's no way I'll ever import a phone with all the compatibility issues AT&T and Verizon have with them plus they never have n71 for T-Mobile either.
EtherealRemnant said:
Yeah I kept my Pixel for my rooting needs (really just for Network Signal Guru) and haven't missed it at all on the S23U. There's no way I'll ever import a phone with all the compatibility issues AT&T and Verizon have with them plus they never have n71 for T-Mobile either.
Click to expand...
Click to collapse
Every year I think more and more about it. At this point I am using root for 4 apps and only 2 of them matter.
1. Adguard - So I can nicely adblock without using VPN style blocking.
2. Swift Backup because I actually find myself regularly wanting to roll back or recover.
The other two are Tasker, but that's mostly just for self granting permissions, and my file explorer that I can easily live without.
dmarden said:
Every year I think more and more about it. At this point I am using root for 4 apps and only 2 of them matter.
1. Adguard - So I can nicely adblock without using VPN style blocking.
2. Swift Backup because I actually find myself regularly wanting to roll back or recover.
The other two are Tasker, but that's mostly just for self granting permissions, and my file explorer that I can easily live without.
Click to expand...
Click to collapse
I switched to Brave so I don't need an ad blocker (ads in apps don't bother me, just the nonsense that happens in the browser, and in fact I get free service from Boost for watching ads anyway) and I started noticing problems with backups that included app data so I just switched to Google Backup. I will say though, Shizuku is supported by Swift Backup. You can back up and restore everything except the app data without root using Shizuku.
EtherealRemnant said:
I switched to Brave so I don't need an ad blocker (ads in apps don't bother me, just the nonsense that happens in the browser, and in fact I get free service from Boost for watching ads anyway) and I started noticing problems with backups that included app data so I just switched to Google Backup. I will say though, Shizuku is supported by Swift Backup. You can back up and restore everything except the app data without root using Shizuku.
Click to expand...
Click to collapse
Yeah, I have needed that app data a number of times... for better or worse, I guess.
I'm selling my OnePlus 11. The software is beyond frustrating and the simple tweaks one can do with Developer Options and ADB are either locked out on this phone or revert to defaults upon reboot. Clearly, OnePlus doesn't listen to their fan base outside of China. The development potential was what drove me to buy this, but it has been a complete disappointment. The lack of wireless charging has also proven to be an inconvenience and I don't trust the longevity of the charging port.
It looks like if you want a Snapdragon 8 Gen 2 running clean versions of Android, Motorola and Sony are the way to go.