Related
Haha I see so many people complaining about bricked vibrants, apps not working, .zip files not working right, market issues, bad battery life and screwy bugs...
Am i a lucky guy who just got one of the "few" working vibrants??
I got my vibrant on release day from a preorder at radioshack...
It was not hardware locked and came with the original firmware.
Im currently running bionix 1.9.1 with the kk oc/uv kernel, launcher pro plus and have 76 user apps installed and this rom still keeps up. 2g is kept on until i need to use 3g. (2g 12 hours, 3g on the rest)
I previously installed oclf on all roms but this rom you dont need one, even with the cpu running at 200 MHz and 1000 MHz.
I have a livewallpaper running, no led notifer on for my sms, beautiful widgets, weatherbug and youtube all on 2 hour update and my battery lasts from 7am off the charger until 10 pm when im home with about 35% remaining with brightness on the lowest setting.
My gps works on spot , unfortunately not in my basement where my room is located. Wifi and bluetooth also work perfect.
Ive softbricked once when flashing a cappy .zip and just got into recovery and performed a nandroid
So whats up how many of you guys have a awesome, powerful vibrant like me?
I guess I am also one of the lucky ones
Mine always worked fine. Not hardware locked. GPS always worked too. The only problems I've had with it have been inflicted by the user (i.e. ME)
I think most Vibrants sold are working properly. I think the representation of folks who come to this forum in search of ways to "fix" their phones is disproportionate.
your not alone
I have had no problem with my phone I have flashed it with 3 different roms and it has been awesome. The only thing I have noticed is the gps does not tell me when I have a satellite lock but is is always accurate to 10-15 meters
My Vibrant is working like how I wanted it, the only issue is definitely GPS. Although, spotty, it at least work at the moment. I just wish it is more accurate so when my phone gets stolen, I have a fighting chance to get it back (via one of the many great anti-thief programs).
mine runs great
I guess you can consider me a lucky one as well.
I got mine on a release day back in July, and aside GPS issues at the beginning I had no complaints. Running Fusion Bionix ROM, and couldn't be happier.
I will def skip the Foryo OTA even if it comes before a working Froyo ROM is available from the brilliant devs on here.
At my work there are 5 of use with Vibrants and they all run fine. Honestly people who have issues are typically going to be more vocal than people who have no issues. So it seems like there are rampant issues with the Vibrant when in fact its only a minority of people having issues.
i ordered mine the day it came out (couldn't preorder cause on an employee account). gps wasn't that great, but worked most the time. rooted it and got rid of bloatware, still just unreliability of gps. started changing things like startup/shutdown animations, ji2 gps, and stuff, no problems. started flashing roms and am on bionix 1.9.1 oc, no problems.
My box date is 7/11/2010. Mine has been rock solid and not hardware locked. Love this phone. Fast, sexy, and unbrickable. The only problems I've had were caused by my own shenanigans.
Running a custom ROM should exclude you from voting. If you have to re-engineer a device to get what you paid for, you aren't getting what you paid for....
-bZj
Mine had the hardware lock and GPS issues, but both are fixed now. I've been lucky in that everything else I've thrown at it works fine. Overclocking is fine, voodoo is fine. The thing is smooth as butter and battery life is pretty damn good now.
Remember people happy with their phones don't usually post.
Sent from my SGH-T959 using Tapatalk
I don't know what the hell happened to my phone after the update. I don't even know what to say
SpacelySprokets said:
I don't know what the hell happened to my phone after the update. I don't even know what to say
Click to expand...
Click to collapse
Then don't say anything?
I like being a smartass.
Most people won't post to say hey my vibrant is working great! Rather they would post when they encounter a problem and need help quick. I haven't had any problems that I couldn't easily fix by myself l.
Sent from my SGH-T959
My vibrant worked great, untill the last update. Now I get lag sometimes real bad.
I was real happy. Now I'm looking for roms.
down8 said:
Running a custom ROM should exclude you from voting. If you have to re-engineer a device to get what you paid for, you aren't getting what you paid for....
-bZj
Click to expand...
Click to collapse
No i don't think so , ive had android phones in the past and since the vibrant was gonna be a large seller for tmobile i expected a large development community like we are seeing and expected roms. So i bought the phone intentionally to mod it but thanks!
Also since most people on XDA have rooted their phone, you can expect they will have more problems than the average consumer. It's one of the downsides of modding. I don't think stock phones have been soft bricking only modded ones.
down8 said:
Running a custom ROM should exclude you from voting. If you have to re-engineer a device to get what you paid for, you aren't getting what you paid for....
-bZj
Click to expand...
Click to collapse
Really? I paid a premium for a device I could customize to my liking (cough-cough iPhone anyone???), well if it weren't for the dev section here I would've been very upset with the outcome.
CitrixLemon said:
Also since most people on XDA have rooted their phone, you can expect they will have more problems than the average consumer. It's one of the downsides of modding. I don't think stock phones have been soft bricking only modded ones.
Click to expand...
Click to collapse
Read the numerous posts here about JI6 OTA update from the users that just received their phone, some of them were sad pandas when they had to stare at the Vibrant screen after they click update button.
If you read enough, and comfortable enough to mod your phone soft bricking it should the least of your concern
hello guys I have a nexus with one gingerbread 2.3.4 and when I use the 3G network after 2-3 minutes the phone restarts. with this bug I can not use Internet
any ideas? Thanks!
Yes. Me to.
What ROM and/or kernel combo you guys using?
I have the stock rom ota gingerbread 2.3.4, nothing changed, full stock. I recently tried miui 1.5.20 the problem is the same. may be a hardware problem?
Does the phone get hot to the touch on the back? Does the phone still reboot if you turn off 3g data and you go exclusivly Wifi?
Had the same issue with my old Nexus 1. Called HTC support and they immediately said it was a defective board. RMA'd and got refurb, but at least it does not reboot when I use 3g.
Good luck.
thanks jhsiao36, think if I update the radio version 5.12.00.08 can change something or brought it in for service?
poltor said:
thanks jhsiao36, think if I update the radio version 5.12.00.08 can change something or brought it in for service?
Click to expand...
Click to collapse
I didn't help for me. I tried the 5.12.00.08 radio and it suffered from the same 3g reboots. But when I disabled 3g and used Wifi, never suffered from reboots.
If the phone is still under warranty, definitely encourage you to call them. HTC's customer and tech support is the best I've ever seen. They replaced it no questions asked, even though my phone is rooted and bootloader unlocked.
jhsiao36 said:
HTC's customer and tech support is the best I've ever seen. They replaced it no questions asked, even though my phone is rooted and bootloader unlocked.
Click to expand...
Click to collapse
+1 They are awesome to deal with. It really makes me sad that they are starting to lock down their phones, because I won't buy a phone if I can't run custom ROMs on it.
But with the radio, I highly doubt flashing to 5.12 would help. Google released the 5.08 radio with the OTA update to Gingerbread. If 5.12 was any better, I'm sure they would've included it. There had to have been a reason they stuck with 5.08.
If you aren't afraid of losing anything, or already made backups, you could try the passimg method of giving you a completely stock install. See if the problem occurs with that as well. This would rule out software vs hardware.
No one can really solve it?
JetChung said:
No one can really solve it?
Click to expand...
Click to collapse
I really don't think it can be resolve without sending it back to HTC for a replace/repair. As I said in my previous posts, I've tried 3 different ROMs - stock, cyanogenmod 6 and 7 - all exhibit the same issue - reboot when on 3g, but perfect if on Wifi. And yes, it will reboot even on a freshly install ROM (no apps installed).
HTC knows of this issue and they will replace/repair. I got a refurb and it works perfectly - stock, cyanogenmod 6 or 7.
Sorry, probably not the answer you wanted to hear, but search on <insert your favorite search engine> and you will find that this is a fairly widespread problem.
Thank you for your answer! It does not work, had sent a factory repair.
After several tests, on Monday I sent the phone in for service. I think it's a hardware problem, maybe a bad batch of motherboards.
my S / N: HT05... and your?
I will tell you just back from assistance.
Did you ever overheat it? I believe that the N1 has a problem if you really push it that it can overheat. Once it happens once it will happen again and every time it takes less and less to cause the reboot. Eventually it reboots just with 3G.
I was running mine in the car-mount with GPS, Google Maps (3G), screen on brightest, on a hot summer day while charging ... and it rebooted. Didn't think much of it but then it started rebooting every time I used GPS and charging.
In the end it was pretty near useless ... rebooting all the time. I sent it in twice (the first time they couldn't reproduce the problem) and the second time they replaced the board. Problem solved.
Now I am very careful not to overheat it.
Yesterday my tablet offered to update, but it failed the update - tried twice. The only thing I've done is root the tablet, I haven't uninstalled any default apps or anything.
I figured no big deal I'd try at work from my development machine today where I could unroot it and check adb logs and such.
Today I check for updates and I get "Your device is up to date" but I'm still on 3.0.1.
--- UPDATE ---
Checked the devel forum and found that this appears to be the case - they pulled the update and promise a new build tomorrow:
http://forum.xda-developers.com/showthread.php?t=1158359
hmmm, I wonder if it's anything to do with getting kicked out of the browser on a regular basis since I installed 3.1. And maybe the laggy keyboard?
so.. what'll happen if you successfully updated and aren't having any problems?
Seems like nothing if you already have 3.1 installed successfully... My tablet is still on 3.1 with no issues there.
I got a message to update to 3.1 today and have tried 3 times to apply the update, failed each time. I have unrooted, factory reset, and still failed. I am hoping that it is on ACER's end and not something in my tab.
My tablet is back to stock and still only gets 1/4 of the way through the application of the update before getting the orange ! in a triangle.
I spoke to ACER yesterday. They said there is a known problem with the 3.1 update and they should be releasing a new one soon. I asked how soon, but got no response. Once I got the update notification today, I thought maybe it was the new one?? Guess not.
Model: A500
Version: 3.0.1
Kernal: 2.6.36.3-00001-g9b3ce2b
Build: 1.104.02_COM_GEN1
EDIT: I am in ATL and bought my tablet from BestBuy in Kennesaw GA opening weekend.
Any advice?
I lost my opportunity to install 4.010.08. Two days ago I got the notice of an update. I tried to hold off as I wanted to see if I could capture the update and share it with others. After I got off work the next day and with some alogcat info I tried to check for updates and it was gone. Now I'm stuck on 3. 01 still. Hopefully they push out the update again as this time ill be ready.
Sent from my SO-01B using XDA App
I, also, am having no operating system issues with 3.1. Overdrive Media Console has gone flakey with respect to audiobooks, but I was blaming that on OMC, not 3.1. I was very surprised to learn that Acer pulled the update. This begs the question, of course, what will happen with regard to the new update for those of us who successfully updated to 3.1? I had no problems and I had a rooted tablet, but had not made any other modifications.
-----
Doc Kinne
Somerville, MA
cybermage1 said:
Yesterday my tablet offered to update, but it failed the update - tried twice. The only thing I've done is root the tablet, I haven't uninstalled any default apps or anything.
I figured no big deal I'd try at work from my development machine today where I could unroot it and check adb logs and such.
Today I check for updates and I get "Your device is up to date" but I'm still on 3.0.1.
--- UPDATE ---
Checked the devel forum and found that this appears to be the case - they pulled the update and promise a new build tomorrow:
http://forum.xda-developers.com/showthread.php?t=1158359
Click to expand...
Click to collapse
Is there a source other than what someone on XDA has "said"?
People lie. I'm not saying the original user lied but I've already seen a few posts linking to that one claiming along the lines, that 'Acer has said they pulled the update' when there is absolutely no official source.
The update has worked and is working for many of us. A friend of mine also got an update yesterday, which doesn't fall in line with the update being 'pulled' by Acer.
As you can see, many of us are getting different builds. What I SUSPECT is the case, is people are rooting and changing their build.props and it's confusing the update procedure on some units. People who don't know the ups and downs of rooting have done just that. They've switched files and components, wpa supplicant files etc. and noone knows the exact process that the device/software users to grab an update. This is just complete speculation on my part, I updated fine and so did a friend of mine that owns it. I did not root, he did not root. We both got the same build of 3.1 and he got his weeks after I got mine.
The point of my message is this, post rumor or something in the title so people don't just read your message and run with it. Because down the line, people are going to quote your thread as well and then lots of people will think "Acer pulled the update!, what's wrong with the one it put out originally!?" and that isn't necessarily the actual case.
Neoprimal said:
Is there a source other than what someone on XDA has "said"?
People lie. I'm not saying the original user lied but I've already seen a few posts linking to that one claiming along the lines, that 'Acer has said they pulled the update' when there is absolutely no official source.
The update has worked and is working for many of us. A friend of mine also got an update yesterday, which doesn't fall in line with the update being 'pulled' by Acer.
As you can see, many of us are getting different builds. What I SUSPECT is the case, is people are rooting and changing their build.props and it's confusing the update procedure on some units. People who don't know the ups and downs of rooting have done just that. They've switched files and components, wpa supplicant files etc. and noone knows the exact process that the device/software users to grab an update. This is just complete speculation on my part, I updated fine and so did a friend of mine that owns it. I did not root, he did not root. We both got the same build of 3.1 and he got his weeks after I got mine.
The point of my message is this, post rumor or something in the title so people don't just read your message and run with it. Because down the line, people are going to quote your thread as well and then lots of people will think "Acer pulled the update!, what's wrong with the one it put out originally!?" and that isn't necessarily the actual case.
Click to expand...
Click to collapse
It does explain how I was able to get the update days ago, but now cannot.
Quick question: If the "No update Your device is up to date" window somehow managed to appear thousands of times in a relatively short period of time, is it possible that it will permanently burn itself into my display? Thanks for your help. (lol)
I'm not rooted, didn't change at all my A500 and yet can't update my tablet. "your device is up to date"
Sent from my A500 using XDA Premium App
zolhof said:
I'm not rooted, didn't change at all my A500 and yet can't update my tablet. "your device is up to date"
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
Be patient young padowan....it will come. Or use a ROM like I did. 3.1 working flawlessly.
TFordham said:
Be patient young padowan....it will come. Or use a ROM like I did. 3.1 working flawlessly.
Click to expand...
Click to collapse
Which rom do you suggest?
Sent from my A500 using XDA Premium App
rorytmeadows said:
It does explain how I was able to get the update days ago, but now cannot.
Click to expand...
Click to collapse
It absolutely does not. This happens on phones as well. If your device is showing an update and you decide to factory reset or even reboot before you download the update, there is a possibility that you're moved down a bit in the server queue.
It's very rare that it happen on a reboot, but it is def. possible if you do a factory reset. Any number of things can explain a stalled update, it doesn't at all mean Acer pulled it.
I'm still waiting for an official source...nothing so far on Acer's FB or anything like that. If anyone could provide one, that'd be great.
I just bought my new A500 yesterday. It is not rooted. When I connected to my home network for the first time, I received a message telling me that an update was available. I assumed it was the 3.1 that everyone was talking about. It downloaded and installed with nary a hitch. I got confirmation of successful update. After the update, I realized that I was having some of the same issues that others were talking about, namely a dodgy keyboard and the inability to activate CAPS Lock. It is then that I discovered that I had NOT received the 3.1 upgrade, but rather, something below. Here is what I found when I looked at Settings > About device.
Android Version: 3.0.1
Kernel Version: 2.6.36.3
Build Number: ACER_A500_1.141.07_COM_GEN1
Whatever version this is, it too is not quite ready for prime time. I hope they release a reliable update soon!
That is the Build that I had to be at before I was moved to Build Number ACER_A500_4.010.08_COM_GEN2 and VER 3.1.
Good luck with your new A500 hope you like it as much as I like mine.
ok, i just got off the phone with a senior acer tech, yes and actual technician not from india. So this should put your mind at ease. Acer sold more units then they expected and it resulted in google not having enough server to service all of the android devices. So for example acer put out 4 million units but there is only 3.7 million on the google registery as of yet. all the people including my self that have 2 units and one updated and on didn't will have to wait a little. PS the 3.1 update is loaded with bugs as well. Don't think it's the holy grail.
problems with 3.1 are less then 3.0.1 but they are there like random closes, slow downs even though it's doing nothing, late coming out of sleep and wifi issues and still no support for external hard drive, and most keyboards don't work.
all in all if you don't have it yet it's coming, if you do well wish and hope for 3.2 update soon like me
mnaderi said:
PS the 3.1 update is loaded with bugs as well. Don't think it's the holy grail.
problems with 3.1 are less then 3.0.1 but they are there like random closes, slow downs even though it's doing nothing, late coming out of sleep and wifi issues and still no support for external hard drive, and most keyboards don't work.
all in all if you don't have it yet it's coming, if you do well wish and hope for 3.2 update soon like me
Click to expand...
Click to collapse
You're kidding - and after I got right royally slapped for saying exactly the same thing a month ago.
Just proves this place is chock full of fanbois.. (them, not you)
lolz @ mnaderi. my experience has been completely opposite. i've been on 3.1 for about a week now and it's waaaaay better than 3.0.1. the browser is much smoother and rarely ever force closes. hooked up my keyboard and mouse, no issues at all. hdmi out to my 1080p tv. everything is working great. i will admit it does have a few bugs here and there but compared to 3.0.1 it is a very nice improvement. i've had far less issues. i'm even using the stock launcher because i can resize the widgets now. was using launcher pro previously. all in all, a great update. still waiting for my mom's iconia to say its ready to be updated to 3.1. got the 1.141 update last night.
btw, i've never rooted my iconia. these things are too new, it's not worth rooting right now because the development is so weak. i'll give it another 6 months when we start seeing some really nice custom ROM's from some of the amazing developers on xda.
tekmoe said:
lolz @ mnaderi. my experience has been completely opposite. i've been on 3.1 for about a week now and it's waaaaay better than 3.0.1. the browser is much smoother and rarely ever force closes. hooked up my keyboard and mouse, no issues at all. hdmi out to my 1080p tv. everything is working great. i will admit it does have a few bugs here and there but compared to 3.0.1 it is a very nice improvement. i've had far less issues. i'm even using the stock launcher because i can resize the widgets now. was using launcher pro previously. all in all, a great update. still waiting for my mom's iconia to say its ready to be updated to 3.1. got the 1.141 update last night.
btw, i've never rooted my iconia. these things are too new, it's not worth rooting right now because the development is so weak. i'll give it another 6 months when we start seeing some really nice custom ROM's from some of the amazing developers on xda.
Click to expand...
Click to collapse
I agree that development is weak, but I root for getting rid of ads and access to all folders (and a restart button on screen).
In the wake of many user complaints about web browsing speeds and other performance issues, Amazon has told the New York Times that it will be releasing a software update for the Kindle Fire "in less than two weeks." That timeframe would put this new software update about a month after the 6.2 update released at the end of November.
http://www.theverge.com/2011/12/11/...ta-software-update-coming-less-than-two-weeks
Oh God lol, now I have to root again....
Sent from my Kindle Fire using xda premium
Well hopefully this time it will be at least a worthwhile update. instead of a no visible difference update like the last one or take away a feature like the one before that.
Sent from my Kindle Fire using Tapatalk
Let's hope the Development get a solid kernel and Rom by then...I don't want to be stock when they update the bootloader and lock it down after all the returned rooted and bricked fires due to people testing kernels that didn't know what they were doing and then returning them.....
Sent from my ADR6400L using Tapatalk
Lets hope some concrete updates...... But wht about some hardware issues......
http://mirolta.com/2011/12/12/amazo...for-kindle-fire-to-encounter-critical-issues/
The OTA will be a non-issue as much as the 6.2 update was. Sure you might have to reroot but Big Deal! That took all of a 30 seconds to do again.
Stuff about Amazon changing to a locked bootloader ignores the fact that most people never root or modify their device. The ones that do are a very miniscule minority of the total users that have the unit. Besides, has any device manufacturer locked a bootloader for a device that was originally released as unlocked? I don't think so.
I bet a lot more units are returned due to some malfunction than due to some someone screwing up their unit trying to modify it.
My wife has her unit stock... no mods, no tweaks, just uses it the way it came. I have mine rooted, different launcher and tons of apps that I have loaded from Android Market or side loaded via other means. I think the device is great for the price.
People who use forums like this have a very skewed idea of how many people actually modify their devices... most never do, never know about it and don't even know forums like this.
krelvinaz said:
The OTA will be a non-issue as much as the 6.2 update was. Sure you might have to reroot but Big Deal! That took all of a 30 seconds to do again.
Stuff about Amazon changing to a locked bootloader ignores the fact that most people never root or modify their device. The ones that do are a very miniscule minority of the total users that have the unit. Besides, has any device manufacturer locked a bootloader for a device that was originally released as unlocked? I don't think so.
I bet a lot more units are returned due to some malfunction than due to some someone screwing up their unit trying to modify it.
My wife has her unit stock... no mods, no tweaks, just uses it the way it came. I have mine rooted, different launcher and tons of apps that I have loaded from Android Market or side loaded via other means. I think the device is great for the price.
People who use forums like this have a very skewed idea of how many people actually modify their devices... most never do, never know about it and don't even know forums like this.
Click to expand...
Click to collapse
Exactly ... That's a well explained post
Yeah, companies lock bootloaders for concrete reasons. They are not going to all of a sudden lock the device down a month after it was released just to mess with modders. Because that is literally the only thing it would do.
The Nook Tablet, for instance... I believe the reason the bootloader is locked is because they had to as part of an agreement with Netflix to provide higher quality streaming to the device. B&N decided that annoying the tiny minority of modders was worth it in exchange for high quality Netflix streaming - something that a much larger percentage of users can benefit from and of course an extra marketing bullet point for them to use.
I'm fine with them updating the device. Look at all the Android phones that don't get regular updates. All people do is whine about NOT getting updated! The KF is some great hardware for the price but it still has issues. Touchscreen responsiveness still needs to be improved, battery life REALLY needs to be improved, and they have to fix the sleep of death as well. I will GLADLY go through the hassle of re-rooting and re-installing the market if these things are fixed.
Of course I'd prefer to have a custom ROM so I can get updates without having to redo all that stuff, but it's only a matter of time.
please, dear god, let non-rooted users change the lockscreen wallpaper
Is there a way yet to block OTA updates (that is also easy to reverse)?
Don't want to be caught with my pants down by this update if it does more than anticipated ....
andTab said:
Is there a way yet to block OTA updates (that is also easy to reverse)?
Don't want to be caught with my pants down by this update if it does more than anticipated ....
Click to expand...
Click to collapse
Haven't read through it, but this post seems to cover it.
ryanlbowen said:
please, dear god, let non-rooted users change the lockscreen wallpaper
Click to expand...
Click to collapse
This. 10char
Also hoping for a clean re-root-only response to this update... I have it stowed away as a gift for my wife, and take it out at night to perform nerd-surgery. It would be great to not have issues right before holiday, as it's going to be enough fun explaining the different launchers, etc.
ReverseWolf said:
Also hoping for a clean re-root-only response to this update... I have it stowed away as a gift for my wife, and take it out at night to perform nerd-surgery. It would be great to not have issues right before holiday, as it's going to be enough fun explaining the different launchers, etc.
Click to expand...
Click to collapse
I have nothing to contribute to this, just lmfao at your analogy of what you do late at night. ;-)
Sent from my MB860 using XDA App
andTab said:
Is there a way yet to block OTA updates (that is also easy to reverse)?
Don't want to be caught with my pants down by this update if it does more than anticipated ....
Click to expand...
Click to collapse
Not the best solution, but it's easy: turn off wireless.
You don't need a widget for this, but it's nice. I recently installed a power control widget ( I used Widgetsoid ) to allow me to turn off wireless ( as well as adjust brightness, volume, toggle USB, and turn off GPS ).
Since I'm mostly content with my setup for now, I leave the wireless turned off to conserve battery and avoid the next update. I'd rather wait until I hear from the good folks here that the next update is OKAY before I turn on wireless and let it update. In the meantime, if I need wireless, I can check here just to be sure there is no update waiting to be pushed, flip on the wireless, do what I need, then turn it back off.
Like I said, it's not the best solution, but it works for me, and it's really simple.
ReverseWolf said:
Also hoping for a clean re-root-only response to this update... I have it stowed away as a gift for my wife, and take it out at night to perform nerd-surgery. It would be great to not have issues right before holiday, as it's going to be enough fun explaining the different launchers, etc.
Click to expand...
Click to collapse
Let me ask you something- same situation here.. My wife's just came in the mail today. I'd like to know more about device setup before said "nerd surgery" as I want to do a similar thing.. Did you login with your own amazon account or hers? If I login w/ hers I don't want her to get a "Congrats on your Kindle registration" type of email- as this is a surprise after all.. But- I'm also thinking that if I go ahead and login w/ mine- anything I do as far as loading apps, etc will be wiped out when she has to login w/ hers?
Sorry to be long winded- overall my main question is- Whats the best way to tinker/root/play with this thing w/o giving away any surprises or having to re-do work?
I'd leave it in the box. When my wife's came, she wanted it right away. It auto registered to MY account, not hers. Didn't add anything to it, it just happened.
I had to deregister it and then reregister it to her account. Doing so is like a default reset.
Also, it is going to auto update at least once as they come with 6.1 and 6.2 is the current. Might even be 6.3 or whatever the new OTA is by the time she opens it.
Do you remember if she got an email when you deregistered and assigned it to her account?
Dont recall. I don't read her email so I don't know and I did a quick check of my email and don't see anything either...
I definitely got an email when I registered mine.
Sent from my BAMForever Thunderbolt
Android 5.1.1 Experience and Discussion
OTA 5.1.1 Link https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
Factory Images 5.1.1 https://dl.google.com/dl/android/aosp/volantis-lmy47x-factory-3efdc8d4.tgz
marcomsousa said:
Android 5.1.1 Experience and Discussion
OTA 5.1.1 Link https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
Factory Images 5.1.1 https://dl.google.com/dl/android/aosp/volantis-lmy47x-factory-3efdc8d4.tgz
Click to expand...
Click to collapse
Wish these were also available for the LTE model
[/COLOR]
Zylograth said:
Wish these were also available for the LTE model
Click to expand...
Click to collapse
Want to trade?
*WARNING* RE-enable OEM Bootloader Unlocking after Update!!!
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
I wish I had my laptop set up so I could remote in from work right now and begin downloading the image.
I take it Root is still working?
bjacks12 said:
I wish I had my laptop set up so I could remote in from work right now and begin downloading the image.
Click to expand...
Click to collapse
I've been thinking off using one of my phones as a hotspot for my laptop...Just not thinking it will be quite fast enough and stable enough to download and get a good MD5. My company watches everything.
techiedj said:
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
Click to expand...
Click to collapse
Why not just get it over with and UNLOCK it? Once you are unlocked, the state of that checkbox is irrelevant.
techiedj said:
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
Click to expand...
Click to collapse
Why is that important? Will I brick my device if I don't? Please explain for an absolute newbie!
Thank you!!!
s0101 said:
Why is that important? Will I brick my device if I don't? Please explain for an absolute newbie!
Thank you!!!
Click to expand...
Click to collapse
If you don't unlock, and leave your bootloader unlocked it can. If you have the check box checked then the bootloader remains locked. So if you get caught with a bad flash or anything else that causes a bootloop there is no way to gain access to the bootloader and run fastboot.
Not off to a great start. I've had my 3rd crash triggered simply by browsing to the reddit nexus 9 board. Now it appears to be on a forced cache erase after the consecutive crashes.
From this we can safely say nobody in Google pays any attention the forum moaning otherwise they might have noticed this issue.
Anyone get an OTA for the LTE version yet? They haven't posted the factory images which scares me a little that LTE might get left behind. The 5.0.2 links went up for both at the same time.
stuken said:
Not off to a great start. I've had my 3rd crash triggered simply by browsing to the reddit nexus 9 board. Now it appears to be on a forced cache erase after the consecutive crashes.
From this we can safely say nobody in Google pays any attention the forum moaning otherwise they might have noticed this issue.
Click to expand...
Click to collapse
Mine's still running really warm and it's losing power over USB just by being on. I'm watching the battery drain simply from the screen idling on Google Now. Come the **** on Google, heat and battery drain should have been primary concerns.
Edit: Fortunately though, it seems like the entire device is running buttery smooth, which is literally a first on stock Android for me. Even my Nexus 6 hiccups without a custom ROM and that has the S805 and 1 more GB of memory.
Still no OTA for LTE on 5.01 -> 5.02 ...
What the hell is Google doing... firstly releasing almost beta Lollipop that on our Nexus have serious issues.. after waiting and being the last device to be updated still no upgrade to LTE which is more expensive and deserves at least same support.
If our model is left behind, I will surely not buy a Nexus device ever again.
atomikpt said:
Still no OTA for LTE on 5.01 -> 5.02 ...
What the hell is Google doing... firstly releasing almost beta Lollipop that on our Nexus have serious issues.. after waiting and being the last device to be updated still no upgrade to LTE which is more expensive and deserves at least same support.
If our model is left behind, I will surely not buy a Nexus device ever again.
Click to expand...
Click to collapse
LTE takes time. I wouldn't worry about it. I bet factory images are up within a day or two. I'm an LTE owner too, so I'm in the same boat. I'm just happy it actually started rolling out, as it started to look like it wasn't happening. This is a much bigger update than 5.0.1 -> 5.0.2
Updated this morning. So far so good
So far, it's definitely an improvement on performance but it remains to be seen with this is another cache-wipe factor or something. One of the first-impression fixes is that the light sensor seems to actually work now, while it was almost useless before.
I noticed the stock kernel is now on 2,5GHz high and that both cores are allways on, which i am not sure if it was happening on 5.0.x. I remember Franco noticing it on Nexus 6 5.1 too, so i guess it's a common practice by google to not turn cores off anymore.
Well so far so good. I never had major issues before. OTA side loaded fine. Did a factory reset to set up fresh. Now that everything is set up I'm just waiting for it to charge completely. It did get warm installing and updating everything, but no issues so far. Everything went smoothly.
There's a new apk named 'Who Am I?' That is disabled by default in this update. Turns out it's a widget that literally shows you the time and what your name is. Maybe it's for people with dementia or short term memory.
The way things have been going, most of us might have needed that widget by the time this update got to us if we'd waited much longer.