Hello everyone. First of all, lurking on xda has been / is a substantial and rewarding part of my life for the past couple of years, so I just want to say thanks to the whole underground development community, nexus 5 and beyond, from device to device you guys and ladies make it interesting and worthwhile.
I work for a tiny Sprint MVNO and part of my job for the last year or so has been doing minor customizations to the stock nexus 5 rom and then flashing units (i use flashfire / fastboot) for distribution to customers. Also providing level 2 tech support to those same folks.
I've flashed thousands of D820(s) and have had many dozens of these devices either for my own personal use, or on extended loan while I investigate issues or arrive at best practices. I obviously haven't tried every goddamn rom, this device has an embarrassment of riches with regard to underground devops and support, but I've definitely hit more than the highlights.
Of course I've followed along with the exodus to Android 7, in theory. It's just never worked for me. Of course, it would have been a hard sell to convince my employers to bundle a non-google aftermarket ROM, and there would have been the issues of compensation for the devs. I flirted with compiling from AOSP myself, but always returned to the safety and security of stock, and on my personal devices I'm fond of PureNexus 6.0.1 or AICP.
Look, I gave that whole preamble not to bore anyone, but to hopefully avoid anyone wasting their time suggesting, for instance that I clean flash vs. dirty, or flash the radio from MMB30Z, or something basic along those lines. Trust me, I've even tried starting with a device out of a sealed box, unlock, then the radio/bootloader, then TWRP, then rom+gapps alone;
I've tried AOSiP, AICP, Lineage, OCTO, DarkROM, .... what else, I don't know, I've made maybe 25 attempts over recent months to get a working usable daily, but what ALWAYS, ALWAYS, ALWAYS ends up happening is the radio starts cycling off it's provision, scanning for extended periods, locks onto LTE for a while, then back on, then back off. It makes for a useless mobile device. It's fine for a wifi-only device tasked with being, say, a webcam or a controller for ambient house lighting, but in a case like that i stick with the lightest possible footprint (being Kitkat)
On 6.0.1 an issue like this might be resolved with the carrier menu updates, or *#*#INFO#*#* fidgeting, but those don't seem to help on Nougat, the times locked onto the carrier get further and farther between.
My involvement with this device is arcing down, but I still have a bunch of them, and I just thought I'd toss it out there: Nougat never works long term with sprint for me. Ever.
Related
So I recently made the plunge and rooted my Nexus S. It was well worth the trouble. But maybe not for the reason most people might think.
Obviously, my aim was to try out different ROMs and get more power/battery life/functionality out of my phone. I agree on the functionality, but I have great doubts about the other two.
For the last week I've been testing Cynogenmod against Inf1nity against NSCollab and the results have been poor on most accounts.
Improved battery life:
Absolutely no way. My battery life has never been worse. No matter what I try, the battery drain is pretty bad. Not helped by the fact that in all three ROMs there are serious bugs which means auto-syncing even though it's switched off and constant notifications, even though they are all switched off. And that's just on the surface. System processes are going berserk on all three ROMs for no good reason at all.
Improved speed:
If there is, it's a bloody small one. In my opinion, it's quite the opposite. Maybe there's a performance improvement in certain areas, like gaming or audio. But in general the phone was prone to sluggish behaviour, no matter what settings were selected. Only Infinity felt snappy. In all cases you have to remove whatever non-stock launcher was on there and switch off many things.
The only thing you get from all of them is more functionality. But to be honest, I'm back on the stock 2.3.4, rooted and flashed the kernel and my phone is the snappiest it's ever been and so is the battery life. And there was no ROM in sight to get it there.
I'm new to this, so if I have been testing the wrong ROMs then please do point me in the right direction. If not, I'm just going to stick to my rooted phone and customize the parts I want when I have a need for it.
For some reason there is often a disparity between the experience that one individual has with a ROM, and that which another person may have. Even on the same make/model device and the same ROM, peoples 'luck' may be completely different. Perhaps it's the interaction of ROM + Apps installed, configuration, usage, variations at the silicon level...sheer luck...? Who knows?
My device hates Stock ROMs but excells with CM7, whereas others with the same device often have the opposite experience. That's why we're lucky to have a diverse dev culture and usually many options available to us. You just have to find one that fits.
Well, I'm not giving up, that's for sure The Nexus S compatible ROMs seem to be quite new, so I'm hoping future versions will show improvement.
In the meanwhile I have to applaud the community spirit and the work some people put in this. Just a pity it's not translating into results on my phone quite yet. I hope to see a real lean and fast ROM run on my phone soon.
PSA: *This will be crossposted in xda HTC One X and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
....and by old, I mean, this thing has got to be 6 or 7 years old, now. I lost the charger for a few years, so I didn't use it.
Now, I found the charger, the tablet seems to be charging (I've yet to ascertain if it will hold that charge, but, whatever). I have use for it, to use the HDMI output to connect to a TV, and just generally use around the house for browsing, games, etc.
My problem is that there seems to be absolutely zero support for this thing. The manufacturer hasn't released a single update; I'm stuck on some bastardization of Gingerbread 2.3. I can't find any custom ROMs that support the device. I have no clue what tablet it's a clone of or anything. There was only one result on the forums here, from 2011, and with no responses (unless I missed something).
I don't expect to have the latest-and-greatest, but am curious what may be available out there. I have flashed custom ROMs on phones before, so, am not altogether unfamiliar. And a YouTube video (from 2011/12) had a product rep at some convention who said they are all rooted, so, that's one less headache.
Any help would be much appreciated, even if it's simply to direct me to resources where I can discover what my upgrade options are, at least to find out what version of Android I can use and tools for building my own custom ROM (yes I know it's time-consuming, I probably would just deal w/ Gingerbread at that point).
Thank you!!
Yes, yes, it's possible to love a phone. Heck, you sleep next to it, don't you? Rate this thread to indicate your love for the Xiaomi Redmi 5A, all things considered. A higher rating indicates that the Xiaomi Redmi 5A is an incredible phone that you enjoy tremendously. You love it.
Then, drop a comment if you have anything to add!
There and Back Again a Phone/ROM odessy
From the spec sheet the Redmi 5A is nothing to write home about. I was looking for a cheap phone at the time, having a nasty surprise bill which had to be paid. So my Sony Xperia had to go. :crying:
I had the device for a while and did my usual (rooted ROM, stay on stock, try XDA ROMS, get tired of the bugs/lagging, return to stock.
I have to say that while there is a plethora of content for miui and an enthusiatic user base, going back to a stock ROM was less than straightforward. Perhaps it is a symptom of being a China/India company first and foremost. I've started to sympathise with people who have english as a second language....
My road back to stock had a number of speed bumps. I had used a pie rom and after trying an incompatible kernel, the phone was soft-bricked. No problem for an experience ROM junkie right? Well the first stock rom was via fastboot which took the usual wrangling to get on Windows. After a day I realised the camera was not working. Nothing would fix it. I wanted at least Oreo and found what I thought was the solution, but turned out to require "developer permissions". Download the QI messaging app (or whatever it was) and request a developer account. Sadly it kept reverting to Chinese so I could not use it. Did I mention that the phone requires you to enter your MI account after re-flashing. I nearly had lost the password and after failing the challenge questions, they said "we'll get back to you in 3 business days(!). Fortunately I found the right credentials in my browser cache.
After flashing stock Oreo data stopped working completely. I then had to flash an update to the baseband and now happily all is well.
Android Pie is nice and I miss some aspects of it, however the stock ROM is faster and unlocks better with my Mi Band 3. So it looks like I'll stay on Rooted stock for the time being. Plus I do enjoy messing with the different themes :laugh:
Good device for the price! Very nice to test your nerves when you brick it!
As many fellows here on the forum, I just can't stay much time on stock ROM. It's fun to discover the features and bugs of those jewels the devs bring to us.
This Redmi 5A was very chalenging to get back to work after a wrong kernel flash. The soft brick needed to disassemble the device to make USB get recognized, and it make me go back to windows for a while to solve it (it lacks supported Linux tools to do the fastboot flash).
The stock is a very good ROM itself, but as it's stucked in 7.1 (the dev version is Oreo and can be used as daily driver as well).
It was my first cheap and all chinese phone bought from a chinese e-commerce site and it still is a very good user experience.
The themes in the store are very fun play with too. :laugh:
It's love
Back in mid 2018 I bought this phone as a back-up for my Galaxy S8. It was my first Xiaomi phone. For the price (€85) I did not expect much, but I was very surprised! Especially the screen quality is very good for this price, nice colors and good contrast. Because I liked it so much I have replaced my S8 with a Xiaomi Mi 9T as my main phone in mid 2019! Now the Redmi 5A is being used to control smarthome stuff and to experiment with. Even in 2020 as i am writing this mini-review I still like it a lot, and it is still up to date with a LineageOS 17.1 (Android 10) ROM, and it works flawlessly. Also the latest official Global and EU MIUI roms work smoothly, although Android isn't updated past 8.1 on those ROMS. This is one of the few budget phones I used that just 'work'. No annoying bugs or lags, just a phone that does everyday tasks as it should, even in 2020!
Hi
I am on OOS 10.0.11.GM21BA with Magisk and TWRP and I want to update to Android 11 11.0.3.1.GM21BA.
However, I saw that there are mentions of stuck devices after updating and the need for patched boot.img and what not.
Until now I used following method to update:
Disable Magisk Modules
Download newest TWRP to SD
Download Full OTA from OP servers to SD
Flash OTA via local update in system settings
Flash A/B retention script with Magisk
Install Magisk to inactive slot
Reboot
Is this method still a valid way of updating? Do I need some extra steps for the update to Android 11?
I would wait... major reported issues even on Pixel phones.
If your current OS is fast, stable and fulfilling it's mission, let it be.
You have nothing to gain.
Running on Android 11 the OnePlus ranks second to Samsung in having severe aggressive background app killing issues. The full implementation of scoped storage in R will devour cpu cycles like a kid eats candy.
The endless popups asking permission to do everything will give you a new pastime.
I can likely coexist with Q... but R is for reject.
Thanks for the informations @blackhawk !
I was actually hoping that I had waited long enough by now for the initial issues to be gone. I actually want to update because of security patches in the first place, which we can't get on Q anymore, at least with stock OOS.
Also, I have multiple friends that updated (just stock phones) and didn't have any major problems, in regards to background killing of apps too, which I would definitely go crazy over if I had to experience that again.
Do you have any further insight to the update process posted?
Nightmare[ITA] said:
Thanks for the informations @blackhawk !
I was actually hoping that I had waited long enough by now for the initial issues to be gone. I actually want to update because of security patches in the first place, which we can't get on Q anymore, at least with stock OOS.
Also, I have multiple friends that updated (just stock phones) and didn't have any major problems, in regards to background killing of apps too, which I would definitely go crazy over if I had to experience that again.
Do you have any further insight to the update process posted?
Click to expand...
Click to collapse
Can't help you on the update process.
I don't think R will ever be fixed. So much so that I bought another N10+ because both Google Android and Samsung have been dropping the ball so badly I'm stepping back for 2-3 years.
The fact that the N10+ is still a good viable choice today shows how poorly Samsung has done particularly in 2021.
I wouldn't even think twice about not getting security updates. Unless you do something stupid*, malware simply isn't an issue on Android 9 and up. Q has all of the worst vulnerabilities patched anyway. Don't buy into the Gookill security hype.
Been running unpatched Pie N10+ for close to 2 years with over a year on the current load. No malware forced reloads ever, and no malware in over a year. Redundantly backup all critical data and be ready to reload if needed. Really a reload be less trouble than trying to implement R.
Watch what you download, keep email in the cloud, watch over the download folder for anomalies and you'll be fine.
*no saving dumb bunnies...
blackhawk said:
Can't help you on the update process.
I don't think R will ever be fixed. So much so that I bought another N10+ because both Google Android and Samsung have been dropping the ball so badly I'm stepping back for 2-3 years.
The fact that the N10+ is still a good viable choice today shows how poorly Samsung has done particularly in 2021.
I wouldn't even think twice about not getting security updates. Unless you do something stupid*, malware simply isn't an issue on Android 9 and up. Q has all of the worst vulnerabilities patched anyway. Don't buy into the Gookill security hype.
Been running unpatched Pie N10+ for close to 2 years with over a year on the current load. No malware forced reloads ever, and no malware in over a year. Redundantly backup all critical data and be ready to reload if needed. Really a reload be less trouble than trying to implement R.
Watch what you download, keep email in the cloud, watch over the download folder for anomalies and you'll be fine.
*no saving dumb bunnies...
Click to expand...
Click to collapse
Sorry for the delayed response, it was actually not because I updated haha.
Well I can't really say much about R, since i haven't had personal day to day experience, and that's where the little things play a key role which can ruin your experience.
When it comes to the security part, I must say we have a different view on that topic. Unfortunately, you don't always have to be the reason for getting pwned, as there are vulnerability that are out of your ability to do something against it unless the system itself gets patched. The amount of those grows considerable faster once it's not updated anymore as the researchers know that there won't be any patch comming against it. Many of the vulnerability get searched on those system on purpose, especially if a big part of the users are still on that OS version. It becomes more lucrative for them then searching vulnerabilities on R and seeing it getting patched 4 weeks later.
Take RackTooth (which we currently don't know how it really works and how it can be fixed) for example, you are basically screwed once it gets out in the wild, if your device it not supported by the manufacturer anymore. That's also a reason why customs ROM are still so important and the manufacturer giving us the ability to unlock out bootloaders so we can continue to safely use our devices once they don't want to support it anymore.
I will probably be switching to Samsung too after my current device as I don't like where OnePlus is headed, especially with the Oppo codebase merge and them giving up on devices so fast.
It's been 2 years and they still haven't fixed the f*cking call on speaker mic problem, nor the audio quality when making a call with Galaxy Buds+! It is really ridiculous. Kinda regret making 10 people in my surroundings get OnePlus phones....
It feels like Samsung is the only real option left, which is sad to see.
Nightmare[ITA] said:
Sorry for the delayed response, it was actually not because I updated haha.
Well I can't really say much about R, since i haven't had personal day to day experience, and that's where the little things play a key role which can ruin your experience.
When it comes to the security part, I must say we have a different view on that topic. Unfortunately, you don't always have to be the reason for getting pwned, as there are vulnerability that are out of your ability to do something against it unless the system itself gets patched. The amount of those grows considerable faster once it's not updated anymore as the researchers know that there won't be any patch comming against it. Many of the vulnerability get searched on those system on purpose, especially if a big part of the users are still on that OS version. It becomes more lucrative for them then searching vulnerabilities on R and seeing it getting patched 4 weeks later.
Take RackTooth (which we currently don't know how it really works and how it can be fixed) for example, you are basically screwed once it gets out in the wild, if your device it not supported by the manufacturer anymore. That's also a reason why customs ROM are still so important and the manufacturer giving us the ability to unlock out bootloaders so we can continue to safely use our devices once they don't want to support it anymore.
I will probably be switching to Samsung too after my current device as I don't like where OnePlus is headed, especially with the Oppo codebase merge and them giving up on devices so fast.
It's been 2 years and they still haven't fixed the f*cking call on speaker mic problem, nor the audio quality when making a call with Galaxy Buds+! It is really ridiculous. Kinda regret making 10 people in my surroundings get OnePlus phones....
It feels like Samsung is the only real option left, which is sad to see.
Click to expand...
Click to collapse
There are security vulnerabilities, simply be aware of them and do what you to mitigate them.
After over a year of zero updates though I know the actual threat level is low. Updates are far more likely to cripple the phone than malware.
Most victims pawn themselves, one way or another. The other common inept screw up of those infected is failure to promptly address abnormal behaviors.
Malware needs to be resolved immediately and the phone shutdown until it is. Trojan preloaders count on a person's lack of wherewithal and failure to act promptly. If I got nailed now, at the worst I be reloaded and 99% fully operational in about 2 hours. 6 if I lost the SD card data.
So what? My data, security, everything is redundant, replaceable, resetable.
Right now unless you go with a older Samsung still running on 10 or 9, there aren't many good options. 2022 is looking bleak as well. This is one reason why I got another 10+. In my opinion it's the zenith of Samsung Note flagships and of Android OS. I'm a pragmatist, I go with what works best. The hype rolls right off like water from a duck.
We are in living a pond of hyperbole
blackhawk said:
There are security vulnerabilities, simply be aware of them and do what you to mitigate them.
After over a year of zero updates though I know the actual threat level is low. Updates are far more likely to cripple the phone than malware.
Most victims pawn themselves, one way or another. The other common inept screw up of those infected is failure to promptly address abnormal behaviors.
Malware needs to be resolved immediately and the phone shutdown until it is. Trojan preloaders count on a person's lack of wherewithal and failure to act promptly. If I got nailed now, at the worst I be reloaded and 99% fully operational in about 2 hours. 6 if I lost the SD card data.
So what? My data, security, everything is redundant, replaceable, resetable.
Right now unless you go with a older Samsung still running on 10 or 9, there aren't many good options. 2022 is looking bleak as well. This is one reason why I got another 10+. In my opinion it's the zenith of Samsung Note flagships and of Android OS. I'm a pragmatist, I go with what works best. The hype rolls right off like water from a duck.
We are in living a pond of hyperbole
Click to expand...
Click to collapse
The Pixel 6 / Pro is looking better every day. For once they didn't use specs from 2 years prior.
Nightmare[ITA] said:
The Pixel 6 / Pro is looking better every day. For once they didn't use specs from 2 years prior.
Click to expand...
Click to collapse
No SD card slot which makes it useless to me.
It also lacks the intense customization stock Samsung's have by way of the Galaxy store.
Samsung's also have builtin workarounds for the lame swipe gesture navigation; Samsung's can easily be set to have screen navigation buttons.
Word of caution, the Samsung interface on Android 11 variant is reportedly a mess.
The spen is a feature I appreciate more the longer I own* the 10+. It's remote bt control and Smart Capture are extremely useful to me. Otherwise when not needed it neatly nests out of sight.
For power users the Note series is still the weapon of choice in many ways.
*lol, I'm still exploring the features in my original 10+ Pie variant. There are many. I play around with it. Even more on the Q variant and new UI features too, I haven't even played with those yet