Guest Jack Andrew :) Posted December 25, 2010 Report Posted December 25, 2010 Well, I have just got my Vega for christmas but the touchscreen is faulty i think as when i touch the screen it always thinks i am touching where the notification bar is and i can't get past the EULA... Please help me as i don't want to take it back and wait for getting a new one.
Guest diveboy2 Posted December 25, 2010 Report Posted December 25, 2010 Try a reset or better yet a new rom. May void warrenty though so your call. Make sure the sceen is clean and free from foreign objects. Good luck
Guest Jack Andrew :) Posted December 25, 2010 Report Posted December 25, 2010 Just a question, How do i reset?
Guest MarkoUK Posted December 25, 2010 Report Posted December 25, 2010 Just a question, How do i reset? Just clean the screen and power off and on again.
Guest Jack Andrew :) Posted December 25, 2010 Report Posted December 25, 2010 is there a way to get past the setup?
Guest Higgsy Posted December 25, 2010 Report Posted December 25, 2010 if you given the screen a good clean and repower it could well be a fault. you could try flashing the rom from www.myadventvega.co.uk and see if that helps.
Guest Jack Andrew :) Posted December 25, 2010 Report Posted December 25, 2010 Well we have come to a conclusion that its faulty, i'm not impressed but i am getting it replaced tomorrow :( Just to say i am 15 and didn't go to sleep to wake up to it to not work :')
Guest wkms77 Posted December 25, 2010 Report Posted December 25, 2010 Well we have come to a conclusion that its faulty, i'm not impressed but i am getting it replaced tomorrow :( Just to say i am 15 and didn't go to sleep to wake up to it to not work :') Have you tried holding the power button in for 8 seconds, then release and hold in for two seconds to power on.
Guest montage Posted December 25, 2010 Report Posted December 25, 2010 Well we have come to a conclusion that its faulty, i'm not impressed but i am getting it replaced tomorrow :( Just to say i am 15 and didn't go to sleep to wake up to it to not work :') .. ... think yourself lucky you have one that will work or be replaced!
Guest npuk Posted December 25, 2010 Report Posted December 25, 2010 (edited) Well we have come to a conclusion that its faulty, i'm not impressed but i am getting it replaced tomorrow :( Just to say i am 15 and didn't go to sleep to wake up to it to not work :') Mines faulty too. ;) How are you getting it replaced tomorrow? Currys customer services obviously closed today so cant ring them. Edited December 25, 2010 by npuk
Guest JonnyDixon Posted December 25, 2010 Report Posted December 25, 2010 Mine is also faulty, i think alot of the non flash are
Guest simonta Posted December 26, 2010 Report Posted December 26, 2010 Sorry for the me too...but me too. Bought two, one for me which is fully tricked out and working for 2 weeks, the other, from the same batch, DOA with the same symptoms. Tried everything. 1.04, 1.065, Pauls pack - can't get past the EULA. Thing is, they are the same batch so possibly a timing issue in the load sequence. I'm a Windows guy - anyone understand what happens between end of bootloader and the shell starting up? Might be able to work out a fix with adb. Merry Christmas.
Guest simonta Posted December 26, 2010 Report Posted December 26, 2010 Hmmm. Played with my dead one for a while longer and I'm now wondering if it's a screen calibration problem. I rebooted endless times and eventually managed to get past the EULA by swiping very slowly and carefully on the last millimetre or so on the very right of the screen. It did take a lot of patience and reboots though. Once past it, I long pressed the "back" h'ware button to get to the launcher options and was able to click Settings by touching the very right of the screen. Once there, same technique I used in the EULA to get to Applications->Development->USB Debugging. So now, I've got dev bridge access so can shell etc. Trying to figure out how/if/where Android stores display configuration data that may be relevant. Maybe there's a file or some build prop values I can delete and cause a recal on boot? Would be interested to know if others with DOAs get similar results..
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now