Your phone needs to be connected to WiFi or data(depending on your settings) and needs to be idle and charging. Playstore will slowly auto update your apps as long as your phone is not too hot for auto-updates. This process takes a long time.
As for the iPhone 3G, I think it was just software and an aging device. My iPod definitely got pretty laggy with multiple apps open on a device with 128MB of RAM in an OS that doesn't even support running apps in the background. The more mods and plugins loaded the laggier naturally.
But even with a jailbreak, they didn't mod drivers or anything that would make it different from a hardware perspective. They just sideload a store that can then install any apps. You can install bad apps but nothing that would survive a restore in iTunes.
What could have happened is she got an iOS update after the restore that also was a bit laggier and energy intensive. Or maybe the faster discharge and higher energy consumption is what finished an already aging battery. It's very unlikely the jailbreak caused it, more likely triggered it or expedited an existing problem. Like formatting your mom's PC whose hard drive is on death's bed and the IO of reinstalling an OS makes it kick the bucket. Is it the OS's fault? No. But did installing the OS cause the fault? Yes. People will still blame the OS, especially if it's a different OS in case of a jailbreak or putting Linux on your mom's laptop that's still on XP or 7. The new thing, it broke the thing!
It was brand new at the time come to think of it, it wasn't released until 2008 so this more likely happened in 2009. The timing and the dramatic difference from stock to jailbroken is just too striking to have been a coincidence, although you might be alleviating some 15-16 year old guilt, that perhaps it triggered something. Still very worrying that a new and very expensive phone was triggered in to dysfunction from the process but maybe it was unlucky defective model. I definitely think that while it was jailbroken the problems were as a result of the OS but maybe the Cydia apps or something else were particularly draining and then that fast draining cycle triggered something else physically.
Yeah if it was brand new, it might also have been defective, I've seen that happen. It's just between jailbreak and manufacturing defect, which do we default to? Depends on the whole timeline really.
It's not impossible it broke it, but anyway the Pixel is made for that so it's a lot less sketchy to begin with. It's the same risk as installing an OS on a PC really.
Google releases betas and developer previews for the Pixel, it's made to survive buggy code.
Pixel phones are basically the gold standard of Android phones for flashing custom ROMs. Google doesn't lock anything down and provide everything necessary to not only build your own, but it even fully supports relocking the bootloader with your own keys and all the secure boot security features.
In most cases I think Google has an online tool you can run right from the browser to fully reflash the stock OS on it.
The only thing that won't work is apps using Play Integrity which some bank apps and streaming apps use for DRM, including Google Pay/Wallet. There's not much you can do about it especially in the longer term, as this is hardware-backed so unless some major exploit gets dropped, you can't really fake the phone being stock to apps. Reverting to stock should bring back full functionality.
You really have to go out of your way to brick a Pixel and mess with overclocking to do permanent hardware damage.
This is mostly sounding reassuring. My wanted banking app is on a list of apps that people have successfully used on Graphene OS so it's probably ok, but yeh, definitely want to be able to go back. I guess I don't know what answer I'm looking for, but in the anecdote I started this post with, I was amazed that it was somehow possible for changes to somehow survive a re-flashing to stock. I really, really don't want that to happen.
I just replied to that in a dedicated comment. But for your Pixel it's even better because it's something that Google even officially endorses, it doesn't even void your warranty.
I've been modding phones since the Android 2.2 days, and I've never had any major issues or anything that would make me want to go back to stock, and never had issues going back to stock. Even my S7 with a modded bootloader splash screen, it was gone when I flashed stock back on it.
Kimovil shows band support for all phones for all generation networks, 2G upto 5G. It is a better site than GSMarena for searching device models, but lacks reviews and amazing comment sections of GSMarena.
Really depends on the carrier. For example, here in the United States, T-Mobile and Verizon seem to pretty much take anything that will work on their network, and most things will. But AT&T runs a whitelist system, and so I highly do not recommend them at all. As for VoLTE I Have found the only definitive way to make sure is to actually purchase the thing and see and return it if it doesn't. Either that or stick with the big brands.
I'm guessing android app store does some kind of staggered update schedule but the apps themselves got code that demands it always be on the latest version. Just guessing, mind you.
Yupp. I am having auto update off actually, because I like to know what apps are getting an update but even manually checking doesn't work well.
I might remember to check for updates, go in, hit refresh and it says no updates there. OK. Good. Then 10 minutes later I get a notification, there are 10 apps to be updated! Not sure why it didn't work 10 minutes ago, but well, whatever.
This seems to be the norm with most updating software, and it drives me nuts. I use Aurora Store to download and update Google Play apps, and it's the same thing -- no updates, then I'll check again and there's a full list. Same thing in Windows updates, same thing in Linux Mint.
If there's something going on in the background that takes 5 - 10 minutes to complete, then at least the app should be honest about that and say something like "this can take some time" rather than a definite "no updates available," but I've just mentally started interpreting it this way.
I have auto update on Neostore and it works flawlessly, but barely use it as I prefer to update as many apps as possible from the original source (Codegerg, Github, Gitlab, etc) over Obtainium.
How is that phone by the way? I'm kind of swooned by it but I'm wondering if I really should spend all that money and go to all that effort to have it shipped here when I don't even do a lot of photography. It just seems so nice, and the bloody pixel and oppo and Samsung phones I can choose here seem so... meh.
My day to day experience is good. I have worries about the long term issues but it was one of the only ones that had a headphone jack and microSD. I'm not sure I would have sprung for it otherwise.
The OS could be better as I do get some occasional freezes but nothing particularly bad and that could be the launcher I'm using. Also the software support is shit: they've never announced how long it'll get updates for - previous phones were only 2 years of security updates - and when the updates come they don't have a changelog (in fact, their website doesn't even have the latest updates listed but I believe a very minimal changelog turns up when they eventually update the site). Also, there are various things people want fixed or features they want ported (I think there's some camera options from the 5V that never got made available on the 1V despite using the same sensor), though I only know about these because I've had to look at reddit to see what's changed in an update.
In terms of the security updates, I'm basically counting on LineageOS support turning up at some point.
This all sounds very negative but the camera, screen, battery life, and speakers are all excellent. The OS is fairly close to stock android, which makes it less annoying than Samsung. I'm just annoyed that a device that seems built to last, is hamstrung by the software updates.
My understanding is that we don't use whitelists here (I'm guessing except for stolen phones) although I only have random internet posts to go on for that as well. What's the basis on which you say VoLTE is likely. It's looking likely from the collected internet forum posts and that one youtube video that I've seen but I've been unable to find anything the least bit official. Even if not straight from the horse's mouth then at least a very reputable 3rd party like GSM arena but so far no luck. I've at least been able to confirm the absence of evidence of VoLTE on GSM arena's part is not evidence of absence of the feature because of my own personal case confirming that I can get a false negative this way.
Qualcomm modem which come with Snapdragon 8 gen 2 SoC definitely support VoLTE. Sony is not allowed to change it. Could only disable VoLTE in Android, but there is no reason to do it.
From my experience working for mobile carrier (not USA), I would recommend to contact your carrier to know if they support VoLTE for all capable devices or only for specific brands.
We don't block capable devices, the problem is that not all VoLTE configurations work. Without testing device we can't know if it will work with our network and usually brands with biggest market share send their prototypes and try to fix what is possible from their side and we from our side.
discord and messenger are pretty bad when it comes to privacy, neither even bother end-to-end-encrypting calls.
Signal really is the best choice, but due to the phone number registration requirement, unless you're fine with the one-time purchase of some prepaid SIMs or something, that might get a bit annoying.
SimpleX is decent enough with calls for now (when they work), but connection times can be abysmal
This is where I would jump to Matrix / Element, but Element is currently in the middle of re-making their mobile Apps, including the entire calling feature 🥴
Android
Hot
This magazine is not receiving updates (last activity 54 day(s) ago).