Related
It looks like changing the dates/time on our clocks have no effect on whether or not you WILL receive the update, just how fast you get it if you were already part of the group scheduled to receive it. It looks like the Google servers picks a list of Xooms that are next for the updates, and pushes those updates to each Xoom on that "list" when your device communicates with the google servers. So, in short, you get the update when your number is called...so changing the dates will not guarantee you an update, you HAVE to be on the next phase list. So those who changed their dates on the Xoom were already on the phase list, they just got their updates faster because they forced their Xooms to communicate with google's servers quicker by forcing an update check. Hope that makes sense guys
Is this supposed to make me feel better?
no, but it just explains what your doing when your changing the time. If your not on the list you won't get it, but it does its check only so often so changing the date is a guarentee whether or not your on the list to get the update pushed. This way people can understand what theyre doing and not have to complain.
rjoudrey said:
Is this supposed to make me feel better?
Click to expand...
Click to collapse
LOL..No, it doesn't make me feel better either, but at least you can get an idea of how it works. It would be nice to know how often and when does Google send out the updates from their servers, so we push our Xooms to check for updates during those times!
So ....
If we missed out on the update for whatever reason can we expect our number to be called again?
RadDudeTommy said:
no, but it just explains what your doing when your changing the time. If your not on the list you won't get it, but it does its check only so often so changing the date is a guarentee whether or not your on the list to get the update pushed. This way people can understand what theyre doing and not have to complain.
Click to expand...
Click to collapse
thanx for understanding what I was trying to say RadDude! Just informing you all how the updates work
Brenardo said:
So ....
If we missed out on the update for whatever reason can we expect our number to be called again?
Click to expand...
Click to collapse
you cant miss the update, your "Xoom ID" is stored in each phase, so if your group was sent the update and your Xoom was powered off, etc.. once you turn your Xoom on, the Xoom will check in with the Google server, and the server will automatically send you the update.
MRCANNADY said:
LOL..No, it doesn't make me feel better either, but at least you can get an idea of how it works. It would be nice to know how often and when does Google send out the updates from their servers, so we push our Xooms to check for updates during those times!
Click to expand...
Click to collapse
Well in 3.1 they added a check now ability for the system update. So they should let us know a little more about how they implement Over The Air updates. I'd imagine if the majority of the users on the list that is available checked as soon as it came out there might be an issue with server power or whatever. But I dont understand what is taking so long, and if more people buy xooms how long will it take next time?
RadDudeTommy said:
Well in 3.1 they added a check now ability for the system update. So they should let us know a little more about how they implement Over The Air updates. I'd imagine if the majority of the users on the list that is available checked as soon as it came out there might be an issue with server power or whatever. But I dont understand what is taking so long, and if more people buy xooms how long will it take next time?
Click to expand...
Click to collapse
it wont cause any server issues whatsoever, if they wanted to push out the updates to everyone immediately, they can with a push of a button (literally) My guess is that they are just playing it safe in the event that something goes wrong with the updates, better to have a small group with problems instead of EVERY single Tablet owner. I was told that the the list of each group in every phase grows as long as there are no reported issues with the updates.
I don't know about you, but I haven't seen one thing about 3.1 screwing up anything, so push that button.
Sent from my Xoom using XDA App
RadDudeTommy said:
I don't know about you, but I haven't seen one thing about 3.1 screwing up anything, so push that button.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
LMAO!!! Seriously, I think Google likes torturing people! Maybe if we all sign disclaimers they will push the update to all tab owners at once...send me the form to sign Google!!
Push the freekin button already!
Like they're doing OTA updates to one up Apple pretty much, and it is just a fail unless your the one sitting there with 3.1... then again I did always have to wait a month or so with my iPhone for the jailbreak community to make the update... but like, this is for stock I'm waiting. I feel like I'm in court for a traffic ticket waiting for the judge to call my name.
Sent from my Xoom using XDA App
RadDudeTommy said:
I don't know about you, but I haven't seen one thing about 3.1 screwing up anything, so push that button.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
HA! Exactly! We should start a petition: "PUSH THE BUTTON, GOOGLE!"
(in case it doesn't come across, I'm kidding about the petition.)
there should be an option to update manually from your computer like apple does, or just wait for ota...
I just got the OTA update last night...glad i didn't have to wait too long...
at 1st i was changing dates every hour or so...then just said hell with it when it comes it comes...lol
What I really really want to know is if having a rooted xoom and an overclock kernel excludes me from the update or makes me incompatible.
I have seen people say that as soon as they reverted to stock they received the update. I also know that rooted users cash manually install it through adb but I don't have experience with that and would rather do something easier.
In essence if I wait long enough, can I still get 3.1 OTA even though rooted, etc etc?
Sent from my Xoom using XDA Premium App
IndivisibleP said:
What I really really want to know is if having a rooted xoom and an overclock kernel excludes me from the update or makes me incompatible.
I have seen people say that as soon as they reverted to stock they received the update. I also know that rooted users cash manually install it through adb but I don't have experience with that and would rather do something easier.
In essence if I wait long enough, can I still get 3.1 OTA even though rooted, etc etc?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
If you are rooted, the OTA update will fail on install when it comes. You can either 1) Go back to stock and wait or, 2) Do the install methods available for rooted users in the Development section.
dscribe said:
If you are rooted, the OTA update will fail on install when it comes. You can either 1) Go back to stock and wait or, 2) Do the install methods available for rooted users in the Development section.
Click to expand...
Click to collapse
thank you. Over to the development section it its then...
Sent from my Xoom using XDA Premium App
I want that button get pressed now hahaha
I've decided to be patient, and only checks like 5-10 times a day :silly:
On a more serious note: On Google's Nexus page they write:
Nexus 7 comes with Android 4.2, the latest version of the world's most popular mobile platform.
Click to expand...
Click to collapse
Are Google shipping new Nexus 7 with 4.2? If they are, surely they should be able to release an OTA?
(I can't link to pages yet, but the quote is from google.com/nexus/7)
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Taps fingers.......
Now.
Now.
Sent from my SGH-I747M using xda app-developers app
I check when somebody on the forums confirms its release.
I'm very passive that way.
*Sent from Nexus S*
no point in checking now....when 4.2 gets pushed to AOSP you WILL see it everywhere. and then the devices should get it within the day.
save your fingers, i think you are going to need them on the 13th (official launch of the nexus 4 and nexus 10)
I'm not going to get AOSP 4.2 since i'm on AOKP. Just don't wanna miss some of it's features. But some tim aftere release there will also be AOKP 4.2
What update.
Google will personally call everyone who owns a nexus 7 Tablet two hours before its release . During the call you will be given information on how to obtain this Life saving Technological Breakthrough. They will also explain to you the update procedure. Google will also get your mailing address as to where to send you a refund check for the full amount of the cost of Android 4.1.2 . The check refund is to say they are sorry for having to wait for the new Os. If you mention 3 times while on the phone with them about . thats 3 times talking bad about apple and Ms They will increase your refund by 3x .. Please be prepared to do a short online survey (required).
On topic.. I do not check The day it comes as soon as i log into the forums i will see all the post from all of you guys checking for me...
Have a nice day The above story comes direct from the small part of my brain that does not as i tell it to..
I'll check around the 14th. No point really in checking before then.
erica_renee said:
Google will personally call everyone who owns a nexus 7 Tablet two hours before its release . During the call you will be given information on how to obtain this Life saving Technological Breakthrough. They will also explain to you the update procedure
Click to expand...
Click to collapse
LOL :laugh:
Never... because as soon as it gets pushed to AOSP rascarlo merges the source and I get my fix rasbean FTW.
Sent from my Galaxy Nexus
ÜBER™ said:
Never... because as soon as it gets pushed to AOSP rascarlo merges the source and I get my fix rasbean FTW.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Uber no more eclipse for you?
Travisdroidx2 said:
Uber no more eclipse for you?
Click to expand...
Click to collapse
Nope. Building rasbean been using it and like it so much I run it on my tablet.
Sent from my Galaxy Nexus
Hey there,
quick question, as i'm new to this, since this is my first android phone. so i've heard that 4.2.2 was released about a week ago. now apparently this update comes in waves, meaning that not everyone will get it at the same time. now i've got two questions about it, since i still haven't received this update:
- is this normal that you have to wait so long to get an update that's already available to a lot of people? (don't wanna do the framework trick)
- what is the purpose of that? please don't tell me, google couldn't handle the traffic when some people want to download this tiny update at the same time? oO
i'm just asking because im starting to worry if there's something wrong with my phone that makes it unable to receive system updates. i don't need the update that bad.
Yes. Don't worry.
I have a n4 ,n7 and n10. Framework worked for me 1st time with all the devices. Its very easy. Why not just do it???
rican408 said:
I have a n4 ,n7 and n10. Framework worked for me 1st time with all the devices. Its very easy. Why not just do it???
Click to expand...
Click to collapse
Because i've read that it messes up / resets settings of certain apps.
Worked fine for me.
Clearing Google services framework from the apps section definitely works.
I haven't gotten it either. Framework worked on N10 and gnex. I'm mainly not forcing it on N4 out of curiosity of how long it will take. Yes, I'm strange but not really needing update on N4. No reboots, no butter in the update, etc.
Sent from my Nexus 4 using Tapatalk 2
I haven't got it either. Is that related to the country or the batch of the phone you purchased?
Still havent got it either. I dont wanna force it with the framework data delete trick, the update is nothing interesting so id like to wait and see how long it would take to recieve the OTA.
Sent from my Nexus 4 using xda app-developers app
i know in canada, the updates go through service providers(if purchased from them) instead of google servers. maybe this is what is happening if you don't see the update yet?
melo_mx said:
i know in canada, the updates go through service providers(if purchased from them) instead of google servers. maybe this is what is happening if you don't see the update yet?
Click to expand...
Click to collapse
Is there a way to check this?
jb91 said:
Hey there,
quick question, as i'm new to this, since this is my first android phone. so i've heard that 4.2.2 was released about a week ago. now apparently this update comes in waves, meaning that not everyone will get it at the same time. now i've got two questions about it, since i still haven't received this update:
- is this normal that you have to wait so long to get an update that's already available to a lot of people? (don't wanna do the framework trick)
- what is the purpose of that? please don't tell me, google couldn't handle the traffic when some people want to download this tiny update at the same time? oO
i'm just asking because im starting to worry if there's something wrong with my phone that makes it unable to receive system updates. i don't need the update that bad.
Click to expand...
Click to collapse
So you have to torce update Kipling google framework,then update,reboot band you're ok
I ended up getting bored and sideloading it
No update for me yet either
Sent from my Nexus 4 using xda premium
ragnarok12 said:
No update for me yet either
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
No update for me either, but I don't mind it. Nothing major that I've read so far will force me to manually update my phone. If it doesn't come by Google I/O, then I'd worry, but by then KLP will probably be out.
facetubespam said:
No update for me either, but I don't mind it. Nothing major that I've read so far will force me to manually update my phone. If it doesn't come by Google I/O, then I'd worry, but by then KLP will probably be out.
Click to expand...
Click to collapse
The whole update cycle can take weeks before everyone has it.
gee2012 said:
The whole update cycle can take weeks before everyone has it.
Click to expand...
Click to collapse
This. People don't realize that updates are rolled out in batches.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
This. People don't realize that updates are rolled out in batches.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Is there any reason for that? I still don't understand why they would do it this way.
jb91 said:
Is there any reason for that? I still don't understand why they would do it this way.
Click to expand...
Click to collapse
I'm curious about this too. Oddly, clearing the cache from my Google Framework didn't work. I'm curious to see if battery life gets ANY better with this update.
jb91 said:
Is there any reason for that? I still don't understand why they would do it this way.
Click to expand...
Click to collapse
They stagger the updates so their servers don't get overloaded with everyone trying to download the update at once. Microsoft does the same thing with Windows updates but they finish within a few days.
Canada here. My N7 took five days to get the OTA. It's been five days since the rollout began and still no OTA on my N4 yet.
Hey Everyone,
I maintain a website, randomphantasmagoria.com, where I maintain a firmware archive of official production Google ROMs for every Nexus and Google Experience device from the OG Droid onward. I plan to archive the Google Experience One ROMs as well, assuming the ROMs actually come from Google and not from HTC.
If someone is buying one, I'd love if you could help me out with something. I need some information on the phone, and you will need to get it as soon as you turn the phone on for the first time, before doing any out-of-the-box system updates.
Here is the info I'll need:
1. The bootloader version. You will have to reboot into bootloader (fastboot) mode to do this. When you do, the bootloader version should be displayed on screen.
2. The baseband version from Settings | About Phone.
3. The value of ro.build.fingerprint from /system/build.prop.
4. IF YOU HAVE AN UPDATE NOTIFICATION: Before applying the update, do the following. Turn on USB debugging after the notification appears on screen. Go into Settings | Developer Options and select "Take Bug Report". Your phone will email a text file to the email address on your Google account. Open that text file and search it for ".zip" (without the quotes) and post the URL to the ZIP file.
This will be unbelievably helpful.
Thank you in advance!
Sent from my Galaxy S 4 (SGH-I337) using Tapatalk 4 Beta
Any takers for when they get the phone?
oldblue910 said:
Hey Everyone,
I maintain a website, randomphantasmagoria.com, where I maintain a firmware archive of official production Google ROMs for every Nexus and Google Experience device from the OG Droid onward. I plan to archive the Google Experience One ROMs as well, assuming the ROMs actually come from Google and not from HTC.
If someone is buying one, I'd love if you could help me out with something. I need some information on the phone, and you will need to get it as soon as you turn the phone on for the first time, before doing any out-of-the-box system updates.
Here is the info I'll need:
1. The bootloader version. You will have to reboot into bootloader (fastboot) mode to do this. When you do, the bootloader version should be displayed on screen.
2. The baseband version from Settings | About Phone.
3. The value of ro.build.fingerprint from /system/build.prop.
4. IF YOU HAVE AN UPDATE NOTIFICATION: Before applying the update, do the following. Turn on USB debugging after the notification appears on screen. Go into Settings | Developer Options and select "Take Bug Report". Your phone will email a text file to the email address on your Google account. Open that text file and search it for ".zip" (without the quotes) and post the URL to the ZIP file.
This will be unbelievably helpful.
Thank you in advance!
Sent from my Galaxy S 4 (SGH-I337) using Tapatalk 4 Beta
Click to expand...
Click to collapse
Just a thought. Perhaps this request may be better in the android general section as everybody hear already owns a One so not many will be able to afford to own both.
Also, I suspect that when this device is released, the information you require will be readily available on xda.
bobsie41 said:
Just a thought. Perhaps this request may be better in the android general section as everybody hear already owns a One so not many will be able to afford to own both.
Also, I suspect that when this device is released, the information you require will be readily available on xda.
Click to expand...
Click to collapse
When the device is released, based on my past experiences with Nexus devices, it's not a given that the originally shipping firmware info will be available on XDA, unfortunately. The overwhelming majority of people turn their phone on for the first time, see an OTA notification out of the box, and just update it without giving a second thought to the fact that the current firmware info could be useful. haha
But yeah, if nobody indulges me here, I'll probably ask in the Android general section as well.
Isn't HTC archiving the roms themselves? I read that they were going to allow all current Ones to change over to the Google experience edition.
Sent from my HTC One using xda premium
vash1053 said:
Isn't HTC archiving the roms themselves? I read that they were going to allow all current Ones to change over to the Google experience edition.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
^^^^^This is great if it's true
Sent from my HTC One using Tapatalk 2
plmiller0905 said:
^^^^^This is great if it's true
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I agree but I haven't heard that anywhere and I would very much doubt it. Would love to be wrong though.
bobsie41 said:
I agree but I haven't heard that anywhere and I would very much doubt it. Would love to be wrong though.
Click to expand...
Click to collapse
And even if they did, there is no guarantee they'd have the original shipping firmware archived, especially if there's an OTA update out of the box. All I really need is the information in the first post for the shipping firmware. From that point forward, it'll be easy to get all the info for the subsequent updates because XDA will be abuzz with it every time there's an OTA.
I'm looking at getting one, if I can trick the US Play Store to take my Canadian credit card... if so, I can try and get this information for you.
Thanks, man!
Sent from my Galaxy S 4 (SGH-I337) using Tapatalk 4 Beta
Arbelac said:
I'm looking at getting one, if I can trick the US Play Store to take my Canadian credit card... if so, I can try and get this information for you.
Click to expand...
Click to collapse
Same here, if Google will take the card one is mine. Then I'll gladly share the info.
Sent from my SGH-I317M using Tapatalk 2
Disregard this entire thread. This is an HTC ROM, not a Google ROM. It's been verified. For the purposes of my website, I'm not interested. Thanks everyone!
Hi Everyone,
As I do with many Nexus devices, I intend to maintain a thread here with links to all the stock OTA updates for the HTC One Google Play Edition. Each time there is an OTA update, its direct link on Google's servers will be posted here for reference and posterity. I also mirror these files at http://www.randomphantasmagoria.com/htc-one/m7_google.
Any questions about flashing these OTA updates can be discussed and answered here as well.
You must have S-OFF on your bootloader in order to flash OTAs manually on a GPE One.
----------------------------------------------------
Current firmware (m7_google): Android 5.1, Build LMY47O.H9
LMY47O.H10 from LMY47O.H9 - https://android.googleapis.com/pack....10-6.04.1700.9_LMY47O.H10_release_453155.zip
-----------------------------------------------------
LMY47O.H9 from LMY47O.H6 - https://android.googleapis.com/pack..._10.33R.1718.01L_LMY47O.H9_release_449435.zip
-----------------------------------------------------
LMY47O.H6 from LRX22C - http://android.clients.google.com/p...00.6-5.11.1700.3_LMY47O.H6_release_430567.zip
-----------------------------------------------------
LRX22C from KTU84P - http://android.clients.google.com/p...00.3-4.09.1700.1_LRX22C.H3_release_403340.zip
-----------------------------------------------------
KTU84P from KTU84L - http://android.clients.google.com/p...00.1-4.07.1700.4_KTU84P.H1_release_381467.zip
-----------------------------------------------------
KTU84L from KOT49H - http://android.clients.google.com/p...00.4-3.62.1700.1_KTU84L.H4_release_377648.zip
-----------------------------------------------------
KOT49H from KRT16S - http://android.clients.google.com/p...WE_3.62.1700.1-3.58.1700.5_release_343526.zip
-----------------------------------------------------
KRT16S from JWR66Y - http://android.clients.google.com/p...WE_3.58.1700.5-3.07.1700.1_release_341696.zip
-----------------------------------------------------
JWR66Y from JDQ39 - http://android.clients.google.com/p...3.07.1700.1-2.14.1700.15_R_release_332395.zip
JWR66Y from JWR66V - http://android.clients.google.com/p...E_3.07.1700.1-3.06.1700.10_release_332016.zip
-----------------------------------------------------
JWR66V from JDQ39 - http://android.clients.google.com/p....06.1700.10-2.14.1700.15_R_release_330258.zip
SPECIAL THANKS
EthanFirst
saturn_de
madasahat
jasalta387
This space for sale, rent, or lease.
Considering that HTC has delivered the GPE KitKat update to Google for release, it's logical to expect it to begin rolling out this week or next. If anyone gets the OTA update, please get the filename of the OTA ZIP before applying it. You can find it in your /cache folder if you're rooted. If you're not rooted, the process is a bit more involved. PM me for details.
Thanks!
Both links send you to a 404 error page.
NJGSII said:
Both links send you to a 404 error page.
Click to expand...
Click to collapse
DOH! Stupid typos. My bad. I fixed it. Thanks for pointing it out.
Thanks to XDA forum member @EthanFirst, we now have the link to the direct OTA update for JDQ39 to JWR66Y. Thank you!
Thank for create forum. :good:
How to get the OTA URLs
The easiest way to get the OTA URLs is to search in the output of:
Code:
adb shell dumpsys dropbox --print event_log
On Linux this can be done with "grep":
Code:
adb shell dumpsys dropbox --print event_log | grep android.clients.google.com
This can be done even after the update.
Wonder if tomorrow will vebthe day now that n4 and other nexus devices have gotten full access to otas. And moto x devices are starting to get it.
sent from my gpe HTC one
monkeypaws said:
Wonder if tomorrow will vebthe day now that n4 and other nexus devices have gotten full access to otas. And moto x devices are starting to get it.
sent from my gpe HTC one
Click to expand...
Click to collapse
I guess we'll find out! If anyone gets the OTA, please make sure to post the filename so I can list it in the OP and mirror it on the website!
Sent from my Xoom using Tapatalk 4
I did the GPe conversion to my phone and got an OTA message only to realize it was another 4.3 update. I hope today is the day. I really hope Google isn't sitting on it until Samsung gets the S4 GPe update to them.
Sent from my HTC One using XDA Premium 4 mobile app
RobBull69 said:
I did the GPe conversion to my phone and got an OTA message only to realize it was another 4.3 update. I hope today is the day. I really hope Google isn't sitting on it until Samsung gets the S4 GPe update to them.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I really am sad to this GPe stuff, the idea is great, but something always fails: if isn't a delay by HTC, it's a delay from Google and we stay watching damn Motorola getting updates...
I thought that it would come after N4 OTA (wich sucks but I can understand), now it seems like we are waiting for Samsung update, probably the delays are just Google marketing at work...
15 days is pretty good for deliverance but first time we prayed for 15 days, now we pray for 15 work days...
My opinion? We are not getting 4.4 update before December. Now I know why my previous phones were nexus and my next probably will be too...
RobBull69 said:
I did the GPe conversion to my phone and got an OTA message only to realize it was another 4.3 update. I hope today is the day. I really hope Google isn't sitting on it until Samsung gets the S4 GPe update to them.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well seeing as Motorola is Google I can see why they would get it faster...
Sent from my HTC One using xda app-developers app
eng.stk said:
I really am sad to this GPe stuff, the idea is great, but something always fails: if isn't a delay by HTC, it's a delay from Google and we stay watching damn Motorola getting updates...
I thought that it would come after N4 OTA (wich sucks but I can understand), now it seems like we are waiting for Samsung update, probably the delays are just Google marketing at work...
15 days is pretty good for deliverance but first time we prayed for 15 days, now we pray for 15 work days...
My opinion? We are not getting 4.4 update before December. Now I know why my previous phones were nexus and my next probably will be too...
Click to expand...
Click to collapse
The GPE updates aren't scheduled together. The HTC One GPE got JWR66Y almost a week before the GS4 did. Also, it appears there were some problems with those initial KitKat builds. I'm sure that has something to do with the delays. For me, 3 weeks after a full Nexus rollout is acceptable. A full Nexus rollout did not start until about 3 days ago. KRT16O only launched for N7 and N10 wifi models, and was quickly pulled. KRT16S started about 3 days ago and THAT is the one that is seeing rollout to the complete Nexus line. So, as far as I'm concerned, my 3 week counter began 3 days ago.
Sent from my Nexus 7 using Tapatalk 4
oldblue910 said:
The GPE updates aren't scheduled together. The HTC One GPE got JWR66Y almost a week before the GS4 did. Also, it appears there were some problems with those initial KitKat builds. I'm sure that has something to do with the delays. For me, 3 weeks after a full Nexus rollout is acceptable. A full Nexus rollout did not start until about 3 days ago. KRT16O only launched for N7 and N10 wifi models, and was quickly pulled. KRT16S started about 3 days ago and THAT is the one that is seeing rollout to the complete Nexus line. So, as far as I'm concerned, my 3 week counter began 3 days ago.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
HTC is still claiming that the timing is up to Google, at least on their Twitter. https://twitter.com/HTCUSA/status/403666789080375296
They have made no indications that they need to use a new build or re-deliver code to Google.
dipdewdog said:
HTC is still claiming that the timing is up to Google, at least on their Twitter. https://twitter.com/HTCUSA/status/403666789080375296
They have made no indications that they need to use a new build or re-deliver code to Google.
Click to expand...
Click to collapse
Just because they didn't communicate it doesn't mean it isn't going to happen. We'll see.
dipdewdog said:
HTC is still claiming that the timing is up to Google, at least on their Twitter. https://twitter.com/HTCUSA/status/403666789080375296
They have made no indications that they need to use a new build or re-deliver code to Google.
Click to expand...
Click to collapse
I wish they never would have made a deadline promise. they never should have updated us that they sent the code to Google. samsung isnt doing this. how do we know they havent sent their code to Google as well. there has never been a need in the past to tell consumers this info.
CraigP17 said:
I wish they never would have made a deadline promise. they never should have updated us that they sent the code to Google. samsung isnt doing this. how do we know they havent sent their code to Google as well. there has never been a need in the past to tell consumers this info.
Click to expand...
Click to collapse
Agreed 100%. We really don't need to know.
oldblue910 said:
Agreed 100%. We really don't need to know.
Click to expand...
Click to collapse
Communication is always good as long the info provided holds its truth.
Sent from my HTC One using Tapatalk
I have a Nexus 4 and a Nexus 7 beside my HTC One GPE. None of those got an OTA update yet to KitKat. So please stop whining and blaming HTC for a "delay". There is no delay. The roll-out is just slow like always with Android.....