A little bit of background: Back when pixel C (dragon) was released, it was using a chip from nvidia. Through time, when device stopped being maintained from Google, Nvidia drivers also went out of maintenance as well; meaning the developers faced big issues matching them with new Android versions. Now, while pixel C is still pretty much alive (I still use one myself), attempts to keep it up to date with third party roms are........ not completely successful.
So the question is this: Does the fact that Tensor chip is an exclusive SoC for Pixel affect development of third party roms in the future when Google drops support for them?
From what I've been reading Tensor is based off the current (or next?) gen Exynos, so it shouldn't delay developers in creating ROMs. At least, I hope that's the case as I am not crazy about stock A12 on my Pixel 6
Related
Will there be an update??? Verizon vs985
Android N official
I doubt it....
I don't think it'll happen through the carriers.
I was wondering how long it would take before someone asked. Everyone was surprised to get Marshmallow, especially as fast as we did, but pretty much unless the OEM makes an official announcement everyone can find, I always figure wait six months and if an update doesn't come, then it likely won't. I doubt it in this case, two years of updates is about standard and with 48A, they actually went 2 years and several months.
Effectively, no.
Why?
Because, Qualcomm has pledged no support to providing additional chipset drivers for SD800/801 devices since they don't conform to Google's standards and such which apparently is a CTS (conpatibility testing suite) making sure devices are ready for the Play Store. There have been articles floating around suggesting the same and the GPU in the phone is partly to blame. Any custom support would likely happen sooner than later but if you're betting your cards on official support, I don't think that's going to happen.
Try a quick Google search and you'll probably understand in better detail as to why.
Here's a great recent article talking about Qualcomm not supporting our SoC (System on Chip) for Android Nougat, that @nagi_007pk mentioned:
From Store to Shelf: An In-Depth Capitulation of Why MSM8974 Devices Are Excluded from Nougat
Hi guys, I'm a jailbroken iPhone 6S+ user. I'm currently a slave to Apple's ecosystem (iPad, Apple TV, Watch but not a Mac) I apologize for the wall of text below, but I know you guys are always glad to give a helping hand.
I've been using iOS since the iPod Touch 2G, taking a break for a couple months only in the Galaxy S3 days, which was my first and only android experience. Many iOS users are in the same boat as me.
Android was a whole different thing back then. Nowadays, when I see the curved, bright and saturated screen of an S7 and how well it pairs with the material design, I feel like I'd love to give that a spin. My problem is that I've been fed constant complaints on behalf of android users, using different handsets and at different times. Here are my main concerns:
I've always heard that, after a "honeymoon" period, almost without fail, all android handsets start to experience stuttering, freezing, rebooting, framerate drops, etc. (maybe one of those at a time, sometimes all of those are common occurrences) does this happen? This is the most important one for me, because if there's something that none of my iPhones ever suffered from, was reduced performance.
Software glitches which are mostly hardware-specific. I've visited the 6P subreddit, only to find a plethora of people complaining about the camera app freezing or crashing, some focus issue I believe as well, or maybe just reduced performance in other parts of the OS (which is the purest form of android). I've also heard that Samsung's bloatware, although only a fraction of what it was back on the S3 days, still causes the phone to feel sluggish at times. Haven't heard about Huawei or HTC bloatware, but I have watched reviews which mentioned some lag here and there.
Software updates. The whole ordeal of having to choose a phone thinking about whether it will get updates in the future or not is pretty sad. I know that Nexus phones are guaranteed to get updates for two years I believe, but as I stated before, visiting the 6P subreddit, I've seen people complain about Google updating the OS but leaving bugs unresolved for several iterations of it. How do you handle this when choosing a phone?
Customization. If there's one area that I've been always convinced Android was leaps and bounds ahead of iOS was this. However, as a jailbroken iOS user, I find that I get most of what you guys can get out the box, but in a prettier package. As in, jb tweaks are very tightly integrated and always match the OS look and feel. In Android, you work with apps or, after rooting, with "modules" I think they're called. How do these differ from JB tweaks (stability-wise as well)? How different is the process of waiting for root vs waiting for a JB? Is rooting as necessary as jailbreaking?
Lastly:
Apps. I am aware of the differences in general app quality when comparing the App Store and the Play Store. Big names such as FB, Twitter, Instagram, etc are mostly the same. But when you start digging a little bit deeper, you find that there's a big difference in not only availability, but also variety and polish. At least, that's how my experience was and what I tend to hear from Android users. How's the Play Store these days? Has this changed a bit?
I apologize once again for the wall of text. If you could answer each point with one or two lines I'd be immensely grateful. Honestly, since these points are big question marks in my head right now, I wouldn't even know what handset to look into, because I don't want to be unpleasantly surprised later on. Android screens though... Damn. Most of them are sexy.
Anyway, thank you very much for your time. Any help is deeply appreciated.
Stuttering/Freezing. You might find this on some low-end devices but the "flagship" devices that I've used haven't suffered from this. This would generally be caused by lower end hardware (lower clocked CPU and lower RAM).
Software glitches. I own the 6P and have never had the camera crash or freeze, never had any software issues with this phone actually. Samsung phones are pretty well known to suffer from being sluggy, this is due to their Touchwiz UI which hogs quite a bit of RAM. The HTC devices I've owned haven't had this issue. Can't speak for Huawei's own UI. The Huawei 6P uses pure Android, I don't notice any real lag issues on this phone.
Updates. If you want guaranteed software updates your best bet is a Nexus. I've noticed no major bugs on the 6P apart from a 4G bug that was specific to an Australian carrier but that was patched pretty quickly. There have been things in Android that people label as bugs that haven't been patched immediately though. Even if you choose a device that may not be updated officially you will very often be able to update via a custom ROM, custom ROMs are often developed for devices long after official support has stopped.
Customization. Android is definitely far ahead in terms of customisation. Most people find customisation via a custom ROM (a customised version of the OS, sometimes based on the stock OS, sometimes based on AOSP (Android Open Source Project or "pure Android"), sometimes based on something like CyanogenMod). A ROM will almost always have extra features and tweaks, these features are usually very well implemented and tie in very nicely with the OS. When speaking about modules you'd be referring to Xposed Modules which are used with the Xposed Framework. Xposed basically opens up a lot of customisation ability, it requires root, it can be used on a stock ROM with root or with a custom ROM. There are a plethora of modules available, too many to even begin to list, the best way to see what they can achieve is to look in our Xposed Modules section. As for root in general, you don't generally need to wait for root like you would with jailbreaking. Having root access is also far more flexible than jailbreaking, you can pretty much do anything with your phone, you have full access to the otherwise blocked system partition. Root methods will vary from device to device but you'll usually need an unlocked bootloader. The easiest devices to root and modify are the Nexus devices, they're designed to be tinkered with, development phones first and foremost.
Apps. In the early days of Android, and even up until a few years ago, the Play Store really lacked in terms of availability and quality. The last few years have seen a dramatic increase in both areas though, there's a wide variety available and the quality has become top notch.
In summing up, it looks like the worries you have are misconceptions commonly held by Apple users.
As a former board level apple technician who used the first ever apple products in kindergarten nearly 30 years ago, I must say I can't even use an iPhone. With all respect, most of your thoughts are not accurate.
Sent from my Nexus 6P using XDA-Developers mobile app
With the release of Android 10, we have yet to realize the state one ui will be in when Samsung gets around to the update, however my question being is one where porting might be an option from tab s4 to tab s3, or is it just custom roms until developmentally impossible? (the developmentally impossible part being unlikely)
I want to start a real conversation about advance compatibility porting, as is the issue with dex, if we could get a bare bones port started until we could make our own variants stable, just like we did with the google lens.
I understand the issues with infringements, and hard bricks, but I believe if we could make a port just like the one ui/pixel experience rom. [see thread(https://forum.xda-developers.com/note-fe/development/rom-team-pixel-pie-1-0-t3934106) for details] We could maybe port oem updates to different devices ((minding scaling and resizing issues) not the best example, I know).
Now I'm not too keen on porting whole oem updates from proprietary device to proprietary device, or even from oem apps, but maybe we could come up with a solution.
Any response will be appreciative.
Hi all
I used AOKP on Samsung and LG some years ago, and it was incredible. I've tried many other ROMs (like 2 a month for a year), it was not the same. crDroid came close, but is still lacking. I want to buy a new phone that is known to have very stable AOKP support. I'm talking about someone who's used the device for 6-12 months at least with no known issues (or minor issues that legit don't bother them), and uses almost every aspect of the ROM's features (I've seen phones that don't support the ribbon, for example, which is a deal breaker).
My budget is anywhere from $300-$1000, I don't really care, so long as the device has at least 2GB RAM and an OK processor.
I don't care too much about the GPU because modern games block rooted devices anyway.
Phone size etc doesn't matter, though I'd prefer bigger rather than smaller.
At least 1920x1080 res, but larger is fine.
I'd prefer very good battery life. I don't want a second hand phone as people tend to ruin batteries, and replacements tend to have terrible shelf lives.
Getdroidtips dot com has some phones listed (I can't post the exact link to the list because too low rep ). The Google Pixel XL looks like a very good choice, but it seems you can't buy them new anymore.
Any suggestions from existing AOKP users? All advice will be much appreciated.
@aggregate1166877
I'm not an AOKP user.
The latest AOKP Custom ROM is based on Android 8.1. A Custom ROM such as TWRP is required to flash it, what presupposes that device's bootloader can get unlocked.
So your options are restricted to Android devices a TWRP exists for and its bootloader can get unlocked.
This phone is not causing interest in developers? It selled a lot and it has flagship features, but there is no custom rom or mods...is there a specific reason? Or simply it is not "good" for developers?
Good question
There are mutliple reasons for this. On the one hand, realme is relatively careless with the publication of (current) sources, the basis for many modifications. In addition, the prerequisite is the Deep Test App, which unlocks the bootloader. Realme does not support all models, which one often does not know before, because realme probably has certain requirements for the support they do not clearly communicate. And probably with the most important reason is that you have no freely accessible MSM tool to ensure the possibility of self-restoring the phone in the case of a brick. There was only the sending to support, which is partially desastrous with realme. At that time I tried at the X50 Pro and was confronted with all the restrictions mentioned. Some points can now be watched at OnePlus since they have changed to the common code base of Coloros. All Custom Roms, etc. will be provided there on the original Oxigenos basis. Unfortunately it was to be expected. Therefore, at the OnePlus Community there were also a lot of concerns that have so far been confirmed ...
I thought that nowadays sources where avaible easily comparing years ago, I was wrong...I was "out of the scene" for 3-4 years so I was not updated with Realme things. All this it's really bad, because this phone is partially destroyed by Realme UI, too much bugs all over the interface.