Hey guys
I currently run [email protected] (JFv1.43) on my dev phone. Are others seeing cupcake being pushed down by OTA to their phones? If so, I'll just wait it out
Thanks
From what I understand, JF killed OTA capability on his builds for this very reason. He's working on a Cupcake mod right now.
Guys
I got cupcake pushed to my phone 20 minutes after bootup time last night. For some reason, when you go to about phone -> system updates, it tells you there are no updates but a few minutes later, it presents you with one in the notification bar. So far, I'm happy with cupcake but I think it's slowed down the phone a little
sam008 said:
Guys
I got cupcake pushed to my phone 20 minutes after bootup time last night. For some reason, when you go to about phone -> system updates, it tells you there are no updates but a few minutes later, it presents you with one in the notification bar. So far, I'm happy with cupcake but I think it's slowed down the phone a little
Click to expand...
Click to collapse
Is that the official T-Mobile one or are you ADP?
ADP - got a gift from a google employee
Related
Just one quick thing it worked great on my g1 and now have rc29 but does anyone know if I will get future ota updates. Want to make sure incase new ones will only be ota?
My opinion,
I hope they start placing the updates online. Have the phone sync the update onto the phone at my free will and so on. Pick and choose which ones i want to install?!?!
Yeh would be great but takes tmo forever to get updates like the wing I am surprised they had this one. Is a first they realeased that quick.
M9x3mos said:
Yeh would be great but takes tmo forever to get updates like the wing I am surprised they had this one. Is a first they realeased that quick.
Click to expand...
Click to collapse
Remember Tmo has nothing to do with this phone. All updates come straight from google. Tmo just tells google what software they want on the phone.
forcing upgrade
there is a file released by google that you name update.zip then do the hokiepokie while you turn on the g1 and it gets the OTA update without all the over air stuff...
its laid out here on this site
it only took me a few mins, I was sick of waiting
bhang
I'd like to see how many G1s have root RIGHT NOW how many are still rootable and how many are locked up ATM.
edit: I dont think this will be an accurate poll of the % of how many G1s in the "world" are unlocked, just a view of the % of how many are rooted amongst the profile of a XDA-Dev type, ie: early adopters, tinkerers, hacker types, tech geeks and any other stereotype you'd like to throw in, but my point is this sample has a bit of bias.
that said, im suprised at the #s so far, its under 2 dozen at this point, but I'd have figured there would be more locked, I'll be intrested to see it after a good number of votes how it goes...
THE SO CALLED "l33tspeak" was meant tounge in cheek, please don't think I actually use those terms, C'mon guys I don't type in "business english" but gimme some more credit than that...jeez ;(
I took the update like a chimp without checking the forums first. D'oh!
mariom said:
I took the update like a chimp without checking the forums first. D'oh!
Click to expand...
Click to collapse
same here. first day i got my phone it asked me to update so of course i did.
selling it on ebay for a dev phone though so its all good
my rc30 story
I bought mine on day 1 here in the US so I knew I had to deny the update till I got the JF rc30 worked out, so I was ready, I use my g1 as my alarm in the morning and when it went off 1 day (6am) I picked up the phone and touched the screen while doing so...by the time I looked at the screen it was flashing rc30.....
But I had a replacement on the way from tmob cause my trackball died 15 days after I bought it so, I couldn't take it back I had to get a swap from tmob, and it was not upgraded yet, so I have been both boats...
Bhang
I rooted with JF's first RC30 and then flashed to RC30 v1.2.
I have the original JF rc30, I need to put JF 1.2 and the DEV boot loader.
Mine keeps popping up to update.
Still reading up on the benefits of custom firmware so going to keep pressing "update Later" till I decide.
EDIT: Stupid G1 hung then quickly popped up with the update popup as soon as I pressed enter. Great.
Wish I could root mine. :-(
I ordered my phone the minute it came available for pre-order, and I've been following AndroidGuys, ModMyGPhone, and this site ever since. Rooted G1 here, thanks to this forum though.
aad4321 said:
the selections need to be clarified a little bit, its like total slang
Click to expand...
Click to collapse
"l33tspeak" is irritating as hell. I didn't participate in this poll.
jashsu said:
"l33tspeak" is irritating as hell. I didn't participate in this poll.
Click to expand...
Click to collapse
it was meant sarcasticly, and I know sarcasam never translates well in forums, I was making a joke
Preorder owner rooted as soon as JF came out with his mod. Moved all the caches, Installed all the tweaks and will install dev bootloader just have't had the time.
I got my g1 december 9th (yesterday) and it already shipped with rc30.very dissapointed!
so if we already have rc30, we can't undo it?
^ nope
..too short...
I hope that 1 guy got his flashed
At this point there is no way to change from a "real" RC30 to one of JFs RC30s... but I think the dev bootloader could be the key, if somebody can get the dev bootloader on those ota rc30s and its all done but it is signed using the "dev keyset" maybe some balsy htc or goog or android disgruntled dev/employee will leak the secret key used to sign the real OTA updates. Probably not. To easy. It happened to dish network, and has kept lotsa peeps watching TV. Kickin Chicken baby. So it does happen just not often.
Who knows I'm sure when it happens it will be 1 slick quick dirty lil hack.
Bhang
2 days after I got mine I rooted it. Was scared to death, i didn't have the funds to just run out and get another one at full price. So i took the risk, and rooted. I'm happy as a lark.
i've rooted around a bit -- renamed ota certs file to block updates, relocated browser cache to sd, etc, but i'm holding off on flashing untill i have a really good reason to.
r00ted R30 G1 White
the day i got the unit for my gf for a early xmas gift i looked at it and it was at R29 i got all the stuff needed and flashed the unit with the recovery image and then to R30 happy happy JOY JOY
share your excitement , to all the haters out there just wait it out but your time will come soon he he maybe later but u never know
bhang said:
I hope that 1 guy got his flashed
Click to expand...
Click to collapse
That one guy is me. Who stupidly hit update last night
JUst want to throw out there that I got the update for the HTC Arrive just now. Currently updating as I type this. Hoping my power doesn't go out because I'm in Texas and the weather is insane right now...
ms79723 said:
JUst want to throw out there that I got the update for the HTC Arrive just now. Currently updating as I type this. Hoping my power doesn't go out because I'm in Texas and the weather is insane right now...
Click to expand...
Click to collapse
I figured that out today, currently at 15% of creating a backup.
cyclical said:
I figured that out today, currently at 15% of creating a backup.
Click to expand...
Click to collapse
That backup just seemed to take too long. Unfortunately, nothing HTC specific. Still have that 160 SMS character mess...ugh.
Ugh, Im hoping this didn't break MMS...there's only one way to fix that -.-
Didn't realize this update was going to take this long, since when I updated my Focus to NoDo it took like 10 minutes.
Oh well, next time I won't start an update right before bed. But even though the update won't actually change anything that I will notice, I still have to do it ASAP, because I just do!
tiny17 said:
Didn't realize this update was going to take this long, since when I updated my Focus to NoDo it took like 10 minutes.
Oh well, next time I won't start an update right before bed. But even though the update won't actually change anything that I will notice, I still have to do it ASAP, because I just do!
Click to expand...
Click to collapse
lol, I did the same thing. Ended up having to stay up until 12:30 am so I could have my phone back. I use the alarm on it to wake me up at 6 am
Driver loaded?
So, I got the update a couple of days ago, daughter yesterday, wife this morning. I've got two more Arrives to go.
One thing I noticed was that when the phone was put into update mode, my Win7 gave the "found new hardware" dialog and I have a HTC 9#### (I don't remember the number but it was something like 96300 or so -- and a quick google the other day revealed it to be the right model number) driver show up when I clicked on the details. When I plug it in now, it just goes to Zune software again and I can't see the number.....but a driver got loaded.
Did MS push a driver or did whatever flashing mode cause Win7 to recognize it? This might go along with the tethering work being carried out......
EDIT: 93100. Looked through history.
Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc
I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc
Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.
And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc
the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....
Hello there, I tried to find an answer to this question but I was not able to!
Pixel XL, Project Fi everything is stock, not rooted and I didn't unlock the bootloader...
The first OTA update (the one with 60 mb) took like an hour to install (I thought that the device was stuck and I restarted it, but after reboot same thing, downloaded the file from scratch and took the same time!)
I got the 7.1.1 notification today, downloaded in no time, but installation took a lot of time!
Step 1 like an hour, and Step 2 still happening and didn't finish yet!! (more than an hour!)
I don't have any problem with the device, running smoothly (except this OTA thing)
Ideas?
Same here, installing the updates took a while. Plugging into power and using WiFi makes it faster but they still take a while.
donslade said:
Same here, installing the updates took a while. Plugging into power and using WiFi makes it faster but they still take a while.
Click to expand...
Click to collapse
so is it normal? the phone didn't finish Step 2 yet!
depending how many apps you have installed it can take a while... but you can use your phone normally....
this is the new feature that preloads your update to be ready for the next update... it eliminates the previous versions "android is upgrading" or "optimizing apps" that used to show up after updates
I'm not sure mine took an hour but I run a very lean set of apps it might have taken an hour from start to finish
Definitely intended to go slow. This is so you don't see any performance issues as you are able to use your phone normally.
Last update took my phone almost 2 hours to complete.
Updates are done differently than before. Remember before how after rebooting you'd have to wait forever for apps to prepare? All of that is now done in advance, kinda. Lots of changes but I think what you're seeing is due to the new way updates are installed. Overall it's a good change but the time delay is now before rebooting but at least the phone is very usable during this period.
That's great guys, thanks for sharing this! I didn't think it will take that much, but it took more than 2 hours!
What is the latest update version for Pixel phones?
7.1.1 with December 5 security updates
Charkatak said:
What is the latest update version for Pixel phones?
Click to expand...
Click to collapse
7.1.1 (NMF26Q)
You don't have to wait for the OTA, just download it when a new version is available.
https://developers.google.com/android/ota#sailfish
Install via: adb sideload
krelvinaz said:
7.1.1 (NMF26Q)
You don't have to wait for the OTA, just download it when a new version is available.
https://developers.google.com/android/ota#sailfish
Install via: adb sideload
Click to expand...
Click to collapse
Is this 7.1.1 (NMF26Q) build for US Pixel phones as well? I read somewhere that this update corrected some LTE issues for EU carrier.
Obviously lies
troy` said:
Definitely intended to go slow. This is so you don't see any performance issues as you are able to use your phone normally.
Click to expand...
Click to collapse
Yes there is something wrong with your phone. Your phone is supposed to update only once with the latest, not go through sequential updates that take forever. If you bought this on eBay, or especially a Chinese seller, It probably has some irremovable malware on it. Do not accept people's answers on the internet as a solution. If it's behaving abnormally and you notice it is behaving abnormally, there IS something wrong with it regardless of what people are saying on the internet because they probably know about this malware but are trying to disguise your symptoms.
AndroidInitiate said:
Yes there is something wrong with your phone. Your phone is supposed to update only once with the latest, not go through sequential updates that take forever. If you bought this on eBay, or especially a Chinese seller, It probably has some irremovable malware on it. Do not accept people's answers on the internet as a solution. If it's behaving abnormally and you notice it is behaving abnormally, there IS something wrong with it regardless of what people are saying on the internet because they probably know about this malware but are trying to disguise your symptoms.
Click to expand...
Click to collapse
Lol. Way to resurrect an old Post... You are delusional. This was the way they worked 2.5 years ago, and it's the way they still do things today. I've continued to use Pixel phones this whole time. 1, 2, and 3. All non XL models. Also, the Earth isn't flat.
troy` said:
Lol. Way to resurrect an old Post... You are delusional. This was the way they worked 2.5 years ago, and it's the way they still do things today. I've continued to use Pixel phones this whole time. 1, 2, and 3. All non XL models. Also, the Earth isn't flat.
Click to expand...
Click to collapse
This is because a malware used to run on android that had been reduced to the size of one pixel on the android screen, making it virtually undetectable to the human eye, hence the name, The Google Pixel. Regardless, it still performs poorly.