Android 10 Images are online - Google Pixel 3 Guides, News, & Discussion

ota to come

There seem to be two versions of 10.0.0:
qp1a.190711.019
qp1a.190711.020
Posted for every Pixel phone. Any guesses what the difference is? Carrier-specific build? For which carrier?

stevexyz0 said:
There seem to be two versions of 10.0.0:
qp1a.190711.019
qp1a.190711.020
Posted for every Pixel phone. Any guesses what the difference is? Carrier-specific build? For which carrier?
Click to expand...
Click to collapse
Going back to the OG Pixel, the first one has always been the standard build and any additional builds were carrier specific (radio changes for the most part).

Related

Google changing CDMA support

People are up in arms and worried over this, thinking the Verizon GNex was being dropped. Turns out it it was something different...
Apparently recent CDMA devices have core telephony functionality that is not implemented in the kernel or framework, but in .apk files that are only supplied in binary form.. No source code... So basically closed source components.
These .apk files need special "platform keys" to work properly. These can not be gotten from AOSP source.
This worries me... Could this be something that Verizon is forcing the OEMs to do for the new LTE phones... An effort to limit what we can do on rooted devices? Could this be why LTE and data is so hard to get working in AOSP ROMs? Causing us to need to run stock based ROMs if we want the full functionality...
Maybe it's not so bad, but I don't know enough about development to know or not.
Anyone want to pipe in on this?
Edit:
Some further reading reveled a bit more info.
Turns out the real problem is the way the file/libraries are signed. Specifically signature mismatching, (using different signatures in the same ROM build) and how the CDMA telephony files/libraries are provided by the carrier. (Verizon/sprint/etc)
When Google signs official Nexus builds, it uses certain signatures, Custom ROMs made from pulling AOSP source are signed with different signatures, and OEM builds are signed with yet another signature. The files/libraries provided by the carrier may be signed by a different signature as well, I am not 100% on that bit.
What this tells me, is that the telephony functions are carrier specific and/or OEM specific as well.
I think this means that besides just being carrier locked, (which is not out of the ordinary) these telephony bits will not work well with custom builds of AOSP. (Non-nexus/google pure AOSP/CM builds)
Meaning, we must use ROMs based of of stock OEM builds, or maybe ports from other devices from the same carrier.
We are lucky that we have a Nexus device that we can base our AOSP ROMs off of. In the future, we might not be so lucky.
Any devs want to chime in? Maybe I am completely off base on all of this.
Added some info.
I don't know what to believe on this yet as there are so many different sites reporting different things.
Plus the thunderbolt didn't have these issues. Maybe cause is s-off? Then again we used the radios provided to us by HTC. Had full cm7 with working ril...so I don't see why the rezound would be any different.
Sent from my ADR6425LVW using XDA App
nosympathy said:
I don't know what to believe on this yet as there are so many different sites reporting different things.
Plus the thunderbolt didn't have these issues. Maybe cause is s-off? Then again we used the radios provided to us by HTC. Had full cm7 with working ril...so I don't see why the rezound would be any different.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
All I care about... the politics of it all is just noise, unless it causes us issue.

AT&T Official ICS ROM vs Custom ROMs?

I had started a thread I just got the official ICS Upgrade
In that thread some had indicated that a custom ROM should
be used and not the the official ICS Upgrade from AT&T.
In an effort to not get that thread of track i will ask here:
What is the real difference with the AT&T Official ICS ROM and the Custom ROMs?
I am fully aware AT&T has loaded a bunch of junk in,
and I went through and disables and deleted much of it.
But what truly is so awful about it?
And if it truly is so bad, what is the "Correct" ROM to use?
Thank you
No such thing as correct or incorrect, it is all personal taste. Some might like one ROM over another. Does that make it better than another? Nope.
Take cars for example. Some people like to leave it stock. Some might like to increase its performance and add engine modifications. Some might like it to handle the roads better so they might upgrade its suspension. Others might like to change its appearance and paint it and add body-kits. Is one car better than the other? Depends on who you ask.
Harry_Y said:
I had started a thread I just got the official ICS Upgrade
In that thread some had indicated that a custom ROM should
be used and not the the official ICS Upgrade from AT&T.
In an effort to not get that thread of track i will ask here:
What is the real difference with the AT&T Official ICS ROM and the Custom ROMs?
I am fully aware AT&T has loaded a bunch of junk in,
and I went through and disables and deleted much of it.
But what truly is so awful about it?
And if it truly is so bad, what is the "Correct" ROM to use?
Thank you
Click to expand...
Click to collapse
This thread will get real out of hand.
But before it dissapears. the main reason most of us say its bad, is with the history of At&t's releases. They mess stuff up, have issues within the kernals, and a big BIG issue with them right now that w/o source, we dont know if its fixed.
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
gsrrr said:
No such thing as correct or incorrect, it is all personal taste. Some might like one ROM over another. Does that make it better than another? Nope. .
Click to expand...
Click to collapse
not taste/opinion in the fact(from their history) that the coding is a mess. and broken everywhere.
You come to a developer forum to run fully stock?
That's what goes through my head when I see people afraid of flashing.
If you want the AT&T firmware at least wait for somebody to post a debloated version since your going to disable them anyways or actually learn how to do it yourself. Since you have access to the forum with so much information.
Maybe take it 1 step further and grab the AT&T firmware and customize it to your liking, you don't even have to post it just use it.
This isn't a great thread cause Versus threads go nowhere...
MotoMudder77 said:
This thread will get real out of hand.
But before it dissapears. the main reason most of us say its bad, is with the history of At&t's releases.
They mess stuff up, have issues within the kernals, and a big BIG issue with them right now that w/o source, we dont know if its fixed.
........
Click to expand...
Click to collapse
Thank you
Harry_Y said:
I had started a thread I just got the official ICS Upgrade
In that thread some had indicated that a custom ROM should
be used and not the the official ICS Upgrade from AT&T.
In an effort to not get that thread of track i will ask here:
What is the real difference with the AT&T Official ICS ROM and the Custom ROMs?
I am fully aware AT&T has loaded a bunch of junk in,
and I went through and disables and deleted much of it.
But what truly is so awful about it?
And if it truly is so bad, what is the "Correct" ROM to use?
Thank you
Click to expand...
Click to collapse
Dude. Do the math. You're posting in a development forum that strives on customizing, building, and creating custom sh$t for our devices. Why would you think that 90% of the people here are looking for and using custom roms?
gsrrr said:
No such thing as correct or incorrect, it is all personal taste.
Some might like one ROM over another. Does that make it better than another? Nope.
- Snip -
.
Click to expand...
Click to collapse
I can appreciate people wanting to customize their devices.
That being said customizing just for the sake of customizing is not really
of interest to me; Increased functionality or an issue being corrected is.
So the real question for me would be what real issues with the
Stock ROM get corrected? and what Real features get added.
Thank you
task650 said:
Dude. Do the math. You're posting in a development forum that strives on customizing, building, and creating custom sh$t for our devices. Why would you think that 90% of the people here are looking for and using custom roms?
Click to expand...
Click to collapse
I fully understand that, I also realize people get emotionally attached to things.
What I'm trying to learn is what is the Real advantage with the custom ROM.
Thank you
Harry_Y said:
I fully understand that, I also realize people get emotionally attached to things.
What I'm trying to learn is what is the Real advantage with the custom ROM.
Thank you
Click to expand...
Click to collapse
Go to the dev section, pick a random rom thread and look at the features.
That is just an example of what is beneficial.
Harry_Y said:
I fully understand that, I also realize people get emotionally attached to things.
What I'm trying to learn is what is the Real advantage with the custom ROM.
Thank you
Click to expand...
Click to collapse
There are many different things. Mods add to the functionality of the phone. Take the 14 toggle mod for instance, no need to enter settings to change common things. Skip tracks with volume buttons. You can also increase battery life with various kernels by UV/uc. It allows you to make your phone function and do what you want it to. The stock firmware is too limiting in this ability
Sent from my SGH-I777 using xda premium
Harry_Y said:
I can appreciate people wanting to customize their devices.
That being said customizing just for the sake of customizing is not really
of interest to me; Increased functionality or an issue being corrected is.
So the real question for me would be what real issues with the
Stock ROM get corrected? and what Real features get added.
Thank you
Click to expand...
Click to collapse
Of course there is an increase in functionality or else why would devs create custom ROMs. What each ROM has that differs from others are listed in their respective threads. Check it out and see if any interest you. If you are satisfied with stock, stay stock. Not a big deal.
LiLChris06 said:
You come to a developer forum to run fully stock?
That's what goes through my head when I see people afraid of flashing.
Click to expand...
Click to collapse
Honestly, I used to hang around here for the community - but that's quickly turning me into a simple lurker.
I'm extremely interested in the developers work. However, I find that the stock factory firmwares are every bit as good or stable as anything that gets turned out in the dev areas. The stock ROMs also do everything I need and want. Plus, I don't like AOSP Android, and that seems to be what everybody is focusing on these days. Also, the 3rd party roms generally have too much changed, removed or added for my tastes.
Edit: Oh, and while I generally like the OEMs code, I have no problem using a good 3rd party kernel.
AT&T releases are typically buggy. The developers here either fix those bugs, or use firmware bases from the international version that are more robust and stable. It is too early to know what bugs this UCLE5 release may contain, but the original AT&T UCKH7 firmware had lockscreen security issues, the official AT&T update UCKK6 broken bluetooth hid and serious power management issues. The AT&T ICS leaks leading up to this version, UCLD3 and UCLD4 had a very serious flaw in the kernel which caused several people with the I777 to lose their device due to eMMC chip damage. Since the kernel source code for the current official AT&T UCLE5 has not been released yet, it is not possible to confirm that the kernel supplied with the UCLE5 release is free of this serious issue. Therefore, it would be advisable to either not run this firmware, or use a modified rooted version in which the kernel is replaced with a known safe kernel.
creepyncrawly said:
AT&T releases are typically buggy. The developers here either fix those bugs, or use firmware bases from the international version that are more robust and stable. It is too early to know what bugs this UCLE5 release may contain, but the original AT&T UCKH7 firmware had lockscreen security issues, the official AT&T update UCKK6 broken bluetooth hid and serious power management issues. The AT&T ICS leaks leading up to this version, UCLD3 and UCLD4 had a very serious flaw in the kernel which caused several people with the I777 to lose their device due to eMMC chip damage. Since the kernel source code for the current official AT&T UCLE5 has not been released yet, it is not possible to confirm that the kernel supplied with the UCLE5 release is free of this serious issue. Therefore, it would be advisable to either not run this firmware, or use a modified rooted version in which the kernel is replaced with a known safe kernel.
Click to expand...
Click to collapse
Thank you for a very clear explanation.
raduque said:
Honestly, I used to hang around here for the community - but that's quickly turning me into a simple lurker.
I'm extremely interested in the developers work. However, I find that the stock factory firmwares are every bit as good or stable as anything that gets turned out in the dev areas. The stock ROMs also do everything I need and want. Plus, I don't like AOSP Android, and that seems to be what everybody is focusing on these days. Also, the 3rd party roms generally have too much changed, removed or added for my tastes.
Edit: Oh, and while I generally like the OEMs code, I have no problem using a good 3rd party kernel.
Click to expand...
Click to collapse
you definitely haven't been running an android device if you say this (marked in BOLD). Considering the fact that for our device in particular, they have released BS that is not only buggy as hell, but has bricked a ton of devices. I think you should probably do a little research before making such bold comments. :laugh:
I got board enough to try the full LE5 including kernel. So far better than D4 and previous ics. Tegrak works as it does on the 9100 base kernels so that tells me i777 is catching up or has caught up. Could be just odex, but all benchmarks higher than on any of the aokp or 9100 sammy roms I've tried.
I'd like to see someone customize this if it remains stable. I've added 15 toggle from other roms, but I jusy like having firmware meant for device.
I-777 UCLE5
Tegrak oc/uv 1.452 ghz
Stable & Fast
task650 said:
you definitely haven't been running an android device if you say this (marked in BOLD). Considering the fact that for our device in particular, they have released BS that is not only buggy as hell, but has bricked a ton of devices. I think you should probably do a little research before making such bold comments. :laugh:
Click to expand...
Click to collapse
lol
I've been running Android devices and flashing firmwares since 2009.
I also haven't seen any of the bugs or issues mentioned on this forum. Doesn't mean they don't exist. The stock 2.3 rom that came with my GS2 from AT&T was amazingly, impressively stable compared to what came with my Vibrant, or even ANY of the community roms for it.
UCLE5 bug:
unable to use wide image for wallpaper, so you can only get a fixed wallpaper, not a scrolling wallpaper. This bug was present in the leaks, and has not been fixed in the official release.
creepyncrawly said:
UCLE5 bug:
unable to use wide image for wallpaper, so you can only get a fixed wallpaper, not a scrolling wallpaper. This bug was present in the leaks, and has not been fixed in the official release.
Click to expand...
Click to collapse
IMO, non issue.
raduque said:
IMO, non issue.
Click to expand...
Click to collapse
Yes, many would not care. Many would. Ask AT&T or Samsung, and they will probably say it is a feature.

[Q] "Carrier IQ" snoopware present in ICS or JB ROMS?

I remember reading about Carrier IQ some time ago; it sounded fairly undesirable as a potential security risk and generally a waste of network bandwidth.
Does anyone know if it is present in the GS3 in any of the official ROMs?
I'm guessing that a generic non-operator specific ROM (e.g. BTU) would be safe - but it would be nice to be reassured.
fasty said:
I remember reading about Carrier IQ some time ago; it sounded fairly undesirable as a potential security risk and generally a waste of network bandwidth.
Does anyone know if it is present in the GS3 in any of the official ROMs?
I'm guessing that a generic non-operator specific ROM (e.g. BTU) would be safe - but it would be nice to be reassured.
Click to expand...
Click to collapse
check the link below hope it might help u a bit with the same
http://forum.xda-developers.com/showthread.php?t=1768205

Daydream will be back. Axon 7 development is still ongoing

I wrote an email to the chief technical officer of ZTE and asked if development for the Axon 7 is still ongoing. Here is a screenshot of the answer.
Can you link exactly who you wrote to? I would like to confirm this.
MishaalRahman said:
Can you link exactly who you wrote to? I would like to confirm this.
Click to expand...
Click to collapse
Pm for now to avoid possible email spamming.
As for all the others who read this, here is a little more explanation:
He is the technical chief officer of zte and stands in direct contact with the dev team. He is also the reason we got the zip for disabling system write protection in the first place. Without him i wouldn't have gotten the update.zip (with disabled system write protection) and @raystef66 couldn't have made a flashable zip for us.
Great contact! Thanks.
Anyway to get the PIE IMS so we can get wifi calling working on Oreo or Pie?
amphi66 said:
Great contact! Thanks.
Anyway to get the PIE IMS so we can get wifi calling working on Oreo or Pie?
Click to expand...
Click to collapse
Volte works on Oreo china
amphi66 said:
Great contact! Thanks.
Anyway to get the PIE IMS so we can get wifi calling working on Oreo or Pie?
Click to expand...
Click to collapse
VoLTE should work on any of the big Oreo ROMs. WFC is hit or miss (even on stock ROM). I'm assuming Oreo is gonna be the last android version we can install and still have these things work (unless some dev out there finds a way to get past this roadblock in the future). Either way, I kinda doubt ZTE would provide any further updates for us beyond Oreo. I'm assuming that the response given in the OP meant that they would fix everything that's still broken and missing on 8.0; not begin development for Pie (especially since the Axon 10 is just around the corner, pulling resources into a 3-year-old phone just isn't a sound decision from a business standpoint).
HunterBlade said:
pulling resources into a 3-year-old phone just isn't a sound decision from a business standpoint).
Click to expand...
Click to collapse
It is if ZTE expect some form of customer loyalty on future purchase decisions. Would you buy the Axon 10/11/12 etc. based on your Axon 7 experience? Yes they had disruptions from trade sanctions etc. but that's not the consumers fault and imo ZTE should be doing everything they can to restore faith in their brand.
They're basically starting again.
They need an affordable flagship like the Axon 7 was. If they don't, it will be hard to gather enough sales to start a customer pool and try for return purchase later on.
Current customers are wary, sceptical and untrusting after that whole fiasco and rightly so.
amphi66 said:
Great contact! Thanks.
Anyway to get the PIE IMS so we can get wifi calling working on Oreo or Pie?
Click to expand...
Click to collapse
VoLTE nd Wifi calling wok fine for me on ZTE's Oreo B20.
RobboW said:
They're basically starting again.
They need an affordable flagship like the Axon 7 was. If they don't, it will be hard to gather enough sales to start a customer pool and try for return purchase later on.
Current customers are wary, sceptical and untrusting after that whole fiasco and rightly so.
Click to expand...
Click to collapse
They just need to copy and paste the Axon 7 with newer specs.
Maybe bumping it to 6" in order to have more internal space would do the trick.
I still can't understand how did they think that the Axon 9 Pro was a good idea. They litterally took all that was great about the A7 and...deleted it.
Now...a bit of an on topic question. Instead of releasing 8.0, could they not enter the Android One program with it...especially since they were aiming for stock experience?
Maybe it's been asked before, but what are the implications of entering the AO program,because IIRC, I may have read some time ago something about a partition not existing on the device and ZTE not gambling with a large release, but I can't remember specifically?
TorqueSsS said:
They just need to copy and paste the Axon 7 with newer specs.
Maybe bumping it to 6" in order to have more internal space would do the trick.
I still can't understand how did they think that the Axon 9 Pro was a good idea. They litterally took all that was great about the A7 and...deleted it.
Now...a bit of an on topic question. Instead of releasing 8.0, could they not enter the Android One program with it...especially since they were aiming for stock experience?
Maybe it's been asked before, but what are the implications of entering the AO program,because IIRC, I may have read some time ago something about a partition not existing on the device and ZTE not gambling with a large release, but I can't remember specifically?
Click to expand...
Click to collapse
The vendor partition stuff is something else entirely. Some people believed that ZTE would bring Treble support to the Axon while that made very little sense (Treble is a requirement for phones that SHIP with Oreo and above, but it's optional for Oreo, and its main advantage is it makes it easier for OEMs to update major Android versions). It was developed by djkuz and NFound eventually anyways, but only because of the generic ROM benefits
I don't think you can simply slap Android One certification on the middle of a product's life, but even if they could, it would make absolutely zero sense for them... Why be commited to security updates and newer Android versions on a phone that has surely stopped giving any revenue since long ago? Plus I'm not even sure if people prefer stock Android to stuff like One UI where you have a bunch of options
Do not expect to much from ZTE for the Axon 7. Until now they did not release a stable OS and it will not change for the next update.
dodo34 said:
Do not expect to much from ZTE for the Axon 7. Until now they did not release a stable OS and it will not change for the next update.
Click to expand...
Click to collapse
Marshmallow and Nougat were perfectly stable, if not the chinese versions. i'd say that counts.
The important thing is them fixing Daydream because it doesn't only entail adding daydream back, to run it properly you need to have thermals and the kernel properly tuned. Daydream should put the phone at ~1.3 GHz but I believe they'll have to mess around to make it work as intended anyways
plus all this is useful for LOS
Marshmallow and Nougat had a very bad design and UI because of mifavor. Oreo is nice but extremly unstable.
dodo34 said:
Do not expect to much from ZTE for the Axon 7. Until now they did not release a stable OS and it will not change for the next update.
Click to expand...
Click to collapse
What next update?
I thought this device was EOL as far as zte was concerned. There hasn't been an official update since august of last year and that had a security update of july '18. That's 6+ months ago. I think we're on our own now....
gpz1100 said:
What next update?
I thought this device was EOL as far as zte was concerned. There hasn't been an official update since august of last year and that had a security update of july '18. That's 6+ months ago. I think we're on our own now....
Click to expand...
Click to collapse
how can you ignore the OP this much??
??
seriously, read the OP first
Also, the chinese version still gets updates, the last one was abt 2 weeks ago?
Choose an username... said:
how can you ignore the OP this much??
??
seriously, read the OP first
Also, the chinese version still gets updates, the last one was abt 2 weeks ago?
Click to expand...
Click to collapse
Not ignoring OP at all... Simply going by zte's past actions. I've seen these sort of promises with other devices (moto x pure comes to mind) in the past. I'll believe it when I see it.
Got a link to this update from 2 weeks ago? What was the actual update?
gpz1100 said:
Not ignoring OP at all... Simply going by zte's past actions. I've seen these sort of promises with other devices (moto x pure comes to mind) in the past. I'll believe it when I see it.
Got a link to this update from 2 weeks ago? What was the actual update?
Click to expand...
Click to collapse
All I'm saying is, @GodOfPsychos contacted this ZTE guy, he said that an update was going to be released, and then XDA'S EDITOR IN CHIEF contacted that guy and got the same response (with which an article was made). They can bail at any time, but it's not like they are promising Pie anyways
I'm guessing you can't see the attached screenie in the OP? I can see it just fine from XDA Labs
We won't get official Android Pie for Axon 7.
The most I read into that is update to include cut out features like Daydream, probably a security update too. Just a finish of what Oreo 8.0 was supposed to be. I don't think we will even see official Oreo 8.1
If they had just kept with the whole "best sounding phone" idea I'd probably already have bought another ZTE. It was the thing that distinguished them in the crowded market of samey-same phones. At this point I'm clinging to my Axon 7 with my tight little hands, and any update to its stability will be appreciated. [Full disclosure, I'm running the GSI Liquid Remix unofficial build of Pie, but if they do update the official Oreo and get it rock solid, I could see downgrading just to be on an official ROM.]

Is the v30 still considered an android enterprise recommended?

In case of buying the phone , will i still be receiving the (monthly) google security patches or will i have go for a custom rom?
Regarding the european variant models , single or ds .
tnx in advance!
nicorb said:
In case of buying the phone , will i still be receiving the (monthly) google security patches or will i have go for a custom rom?
Regarding the european variant models , single or ds .
tnx in advance!
Click to expand...
Click to collapse
Lg isn't very good with updates. Latest security update we have is from April.
If you want regular software updates,lg isn't the Phone for you.
But custom ROMs are great here.
tech_infinity said:
Lg isn't very good with updates. Latest security update we have is from April.
If you want regular software updates,lg isn't the Phone for you.
But custom ROMs are great here.
Click to expand...
Click to collapse
according to you, which rom deserves to be tried?
nicorb said:
In case of buying the phone , will i still be receiving the (monthly) google security patches or will i have go for a custom rom?
Regarding the european variant models , single or ds .
tnx in advance!
Click to expand...
Click to collapse
Well, enterprise recommendation means updates atleast every 90 days...
the European H930 (single sim) has that, its usually every 2 months (even though some updates, like the january one were quite delayed, dont know why)
dont know about official OTAs for the H930DS though
continua.mente said:
according to you, which rom deserves to be tried?
Click to expand...
Click to collapse
There are a lot of good roms for the Phone. But you should worry about which ROMs to flash after you actually buy the phone.
tech_infinity said:
There are a lot of good roms for the Phone. But you should worry about which ROMs to flash after you actually buy the phone.
Click to expand...
Click to collapse
I've already bought it
nicorb said:
Is the v30 still considered an android enterprise recommended?
In case of buying the phone , will i still be receiving the (monthly) google security patches or will i have go for a custom rom?
Regarding the european variant models , single or ds .
tnx in advance!
Click to expand...
Click to collapse
Yes, it's still on the list. As @SGCMarkus points out, that means updates at least every 3 months -- not every month. Sometimes it's been faster than 90 days, but that's the requirement, as well as one major Android letter update. Pie will be that one.
The only reason V30 got on the list with Nougat was because of the "imminent" update to Oreo. Only Oreo phones could have have Enterprise Recommended status. Once we got on Oreo, then the updates have come every 2 or 3 months -- as that was when the Enterprise Recommended requirements kicked in.
Thanks everybody, u have been most helpful !
ChazzMatt said:
Once we got on Oreo, then the updates have come every 2 or 3 months -- as that was when the Enterprise Recommended requirements kicked in.
Click to expand...
Click to collapse
Unless of course you're on a 932, in which case you're over six months now ?
redoregon said:
Unless of course you're on a 932, in which case you're over six months now ?
Click to expand...
Click to collapse
Yes, the Pie Upgrade debacle threw off the updates schedule.
LG expected to have Pie rolled out before end of June.

Categories

Resources