I do hope it is the case that the moment i got the ICS OTA update, my keyboard went on the fritz.. (versus hardware failure).
Has anyone experienced any such behavior in their keyboard since the OTA ICS update? also does anyone know of posts of people with the folio failing?
Contact Lenovo if no one can help you. This is a warranty issue.
Related
Hello All,
I've looked through most of the posts on the forum and i have'nt seen a post that quite addresses the issue that i am facing with my phone, but i may be mistaken, and if this is a double post i apologise.
So, onto the issue: i have had the legend for over a year now, and while its a brilliant phone in its class, it does have its short comings. First up, after buying the legend i realized that it can prepped with Android 2.1 upgradeable to 2.2. a few months after buying the phone the 2.2 update became available and i did an OTA install of the 2.2 software. For the first few weeks, all was well.. and then suddenly i had issues with the charging (phone not charging). I took it to the service centre and they diagnosed the the micro USB port had dampness issues and changed it. After that they did a complete reinstallation of the 2.2 as they had to do a complete wipe of the phone while changing the micro USB(not sure why). All was well for a few more weeks and then the freezing issues started.. occasionally the lock screen would freeze up and i would not be able to access the phone(either to make a call or send a message) unless i removed the battery and replaced it... obviously the power button did not work unless the phone was unlocked. I put it down to issues with FroYo and left it at that... however recently i acquired a new phone and decided to root my legend with the cyanogen 7(found it difficult to install the Gapps.. inexperience!!) and the Blayo 0.8... The phone worked well for a couple of days and then it was back to its usual freezing... i am getting frustrated and not sure what could be causeing the problem!! if anyone of you could help or point me in the right direction to someone who can help i would be very grateful!
Thanks for reading through an extremely long post!
Cheers!
Lin
I just got my champagne 32gb from TigerDirect today and as soon as I connected it to wifi it started updating to ICS. Didnt install yet because I'm at low battery. My question is - can I somehow negate the update and keep HC? This is my second prime and the first one locked and rebooted constantly. Im worried this will be the same issue with the ICS update again.
Im still unsure whether the rebooting is a hardware or software issue but I want to be safe and stick to HC while its figured out. How can I cancel the update and keep my HC? Help would be appreciated, thanks.
Since the .28 update today i saw the attached lines on the side of my screen, if i tough the screen they go away but the moment i take my hand off they come back. I am not sure if its the new update this has caused this issue or something else.
Anyone else have had same/similar issues since the new update?
Should I RMA TF201?
v1ks said:
Since the .28 update today i saw the attached lines on the side of my screen, if i tough the screen they go away but the moment i take my hand off they come back. I am not sure if its the new update this has caused this issue or something else.
Anyone else have had same/similar issues since the new update?
Should I RMA TF201?
Click to expand...
Click to collapse
Hey,
i was actually getting that on my tab too
i wasn't very sure
but usually if i press the home key, it would be gone... so i don't know...
Mine has also started doing this since .28 pretty sure this is the artifact issue talked about in the review thread in general. It's done it to me twice now,rebooting seems to have fixed it but never did this to me on any of the older firmwares. Prob have to wait till the next update see if they update the driver or somethin
I also rebooted the pad and its ok for now until as you say it comes back again. I just cant believe how updates which are meant to fix problems are causing more issues.
One thing i also noticed was that when playing NFS it crashed and the game was stuck, i had to reboot pad as nothing would work.
All these + other problems after the recent update!
I'm getting the same lines on my tablet. Just rebooted it and haven't seen the lines return after 5 minutes.
Im seeing these lines , except larger, when connecting to my laptop threw splashtop/my cloud.
Think its the same issue?
Have seen them in other build versions
Have seen them a couple of times on my prime .28 too. But I have seen them in the old firmware as well, so It's not a problem with the update.
They only appear in the homescreens and not in apps and they disappear shortly.
Manar Aleryani said:
Have seen them a couple of times on my prime .28 too. But I have seen them in the old firmware as well, so It's not a problem with the update.
They only appear in the homescreens and not in apps and they disappear shortly.
Click to expand...
Click to collapse
ive only seen this since the update never had it on the .21 firmware. Anyway lets hope its sorted in the next release for now the reboot is doing the trick
Just when I thought ASUS was done with messing up my Prime, they do it again. I will never buy another ASUS product, in fact, in the past 5 months, I have purchased 2 Dells, 2 HP's, and 3 Kindle Fires. All users very satisfied.
I'm having this issue too.
http://www.youtube.com/watch?v=l7AK8Yyriiw
I'm gonna try manual firmware installation to see if this works. Suspects faulty firmware download via FOTA
That's a graphics memory issue. Its driver related, it was basically gone in .21 Update. It could have been re-introduced in .28 with the nVidia drivers update they did.
I'm almost sure it isn't Asus fault. At least not directly
I am in the process of sending my z2 back to amazong for a replacement, due to bad touch issues, but im just wondering if anyone eolse has had theirs replaced and was your new one fine (without touch issues)
When i got my other one, i restored my google account / apps straight away and when they finished i upgraded the fw to .402 straight away, but then still had issues.
I'm just wondering can i leave connecting straight away to my google account, and update the fw, then connect to my google account then restore the z2? i dunno why, im just wondering if this may have helped, or do you think it wouldn't make any difference?
I did do a factory reset of my tablet anyway and this didn't help me.
Thanks
James
I can test with amazon, but as sony did'declared the problem...
Hi Diomorgan, So sont have admitted there is an issue have they?
Where did you see that?
Hi all, I have a weird issue that nobody else seems to be having (based on a forum post search). I recently bought 2 XT1528 Moto E's to set up for use with T-Mobile. They both came out of the box with 5.0.2 installed, and I was able to change the network settings to GSM and set the APN successfully to get it to use T-Mobile's network.
I then upgraded one of the phones to the 5.1 OTA update, but I started experiencing freezes on the 5.1 phone. This would occur intermittently, but essentially, the touchscreen would become unresponsive during use. If I pressed the power button once to lock the screen and once again to unlock it, the touchscreen would work again. It doesn't seem to be related to the phone lagging/becoming overburdened, because the background processes would continue to function even when the touchscreen is unresponsive (Youtube videos would continue to play smoothly, apps would continue to download and update, etc.). This would sometimes occur several times in several minutes (touchscreen becomes unresponsive after ~5 seconds of use), and sometimes it wouldn't occur for several hours.
Going back to the 5.0.2 device, this doesn't happen at all. I can't tell if this is a software or hardware issue, so I was wondering if anyone else had experience with this. If it's a software issue, is there a way to revert back to 5.0.2? It's also entirely possible that it's coincidental that the phone with the faulty hardware was the one that I upgraded to 5.1 (I don't recall if the 5.1 phone exhibited this behavior when it was on 5.0.2).
Has anyone else experienced this or something similar? I'm now a little scared to upgrade the other phone to 5.1 as well, in case this is a software issue. Thanks!
I have not heard of this issue occurring with this phone so perhaps yours has a defect. The 5.1 update released like a month or so ago and this issue hasn't been brought up before now. Any who..you will want to get a replacement at some point.
Sent from my XT1528
Sent from my XT1528
Ace42 said:
I have not heard of this issue occurring with this phone so perhaps yours has a defect. The 5.1 update released like a month or so ago and this issue hasn't been brought up before now. Any who..you will want to get a replacement at some point.
Sent from my XT1528
Sent from my XT1528
Click to expand...
Click to collapse
Thanks for the feedback. I definitely am getting a replacement for the 5.1 phone (if it is a software issue, I need another 5.0.2 phone anyway). I ended up taking the leap and upgrading the working phone to 5.1, and no issues so far, so it definitely looks like a hardware defect at this point. I'll keep an eye on the newly upgraded phone and see if it exhibits these issues. Will report back in a few days.
I have also experience freeze ups with the touch screen, brand new phone latest software with 5.1
Performing a factory reset (from android) seems to fix this on a device that was upgraded to 5.1
Mine happens on the last little bit near the bezel on the right side.
I factory reset 2x.
Sent from my XT1528 using XDA Free mobile app
Is this confirmed as a widespread issue or a limited problem? I have an XT1528 on a Verizon MVNO and have avoided upgrading to avoid the problem.
TIA,
CheapDad
Is this confirmed as a widespread issue or a limited problem? I have an XT1528 on a Verizon MVNO and have avoided upgrading to avoid the problem.
Click to expand...
Click to collapse
Bump, as I'm hoping someone has some thoughts on this.
CheapDad said:
Bump, as I'm hoping someone has some thoughts on this.
Click to expand...
Click to collapse
This hasn't occurred for mine yet, so maybe it just happens to random devices with 5.1.
Sent from my XT1528