Related
Hi all, hope someone can help me.
I've recently bought a refurbished Advent Vega from Curry/PC World Ebay outlet. I've installed ICS Custom rom onto it but am having a problem with the screen being unresponsive when the tablet is cold.
I know its not an issue with the rom as the same issue occurs with other roms including the vega's stock rom.
I believe it is some sort of heat problem, that when the device is cold (when it has been off all night) the screen is really unresponsive, to the point that the unlock slider won't move without pressing extremely hard on the screen, this still doesn't unlock but it does move around a little.
After a while the screen will gradually become more reponsive but still a bit jittery and then after a bit longer once it has warmed up a bit the screem works perfectly. If I charge the tablet it seems to fix it quicker but I believe this is due to the heat again as the battery charging heats the tablet up quite quickly.
I've read a couple of other articles about squeezing the left hand or right hand side of the tablet and many people say that this works but it doesn't for me.
Does anyone else have any other suggestions on how this can be fixed.
Thanks for any help you can provide.
Try this shuttle test rom.
http://dl.dropbox.com/u/37483979/P10_image_20110411_v1.10.4_std_dev.exe
It was posted over on modaco by a guy called alex zhou.
Install the test rom with NVflash, it will calibrate the screen correctly on first boot (press the back button).
Then install recovery boot
http://dl.dropbox.com/u/37483979/com.modaco.vegarecoveryboot_c2.apk
and boot to CWM recovery.
format data, cache, boot and system then turn off.
Now NVflash the test rom again, run it and calibrate the screen again.
Now install what ever rom you want and your problem should be gone
Good luck
Thanks to Ged over on modaco for the dropbox upload for the files.
Thanks so much for your help. Works perfectly well now thanks even when it is cold.
Your welcome, glad it fixed it.
The next release of vegaice will include a improved touchscreen driver that will correctly calibrate the screen but if the problem returns again just redo the above fix.
Richard
Hi Richard - I registered with XDA (after months of lurking) just so I could thank you for this same advice when you gave it to mmace. I now gather I can't thank anyone till I've posted at least once, so this is it - if I now can I'll thank you on both threads, FWIW.
Anyhoos, to make this more than just a "thank you note" I'll explain - I bought a Vega with an "unresponsive screen" very cheaply on eBay hoping I could at least make a cheap netbook of it with a keyboard/mouse - my Tosh Folio100 permits this more easily than the Vega, it transpires, as it defaults to USB host status. When it arrived I found an otherwise tidy tablet stuck in language selection and tried various roms in the hope that the USB could be enabled. ICS b1, unlike the others, showed some vestigial responsiveness on the screen itself so I started looking for a way to calibrate it - I didn't find Alex's posting on Modaco but when I found mmace's here I followed your instructions (resisting the temptation to just stick with Alex's rom once it fixed the screen completely!) and now (fingers crossed) have a fully working Vega for peanuts....
Please let me stress - when it arrived this Vega's touch screen was totally non-functioning, no amount of pressure or flexing of the case made any difference. In ICS the language selection would scroll but not select. After running Alex's rom the problem disappeared completely.
Two questions now occur to me -
1. Why the load/clear/reload/load regime? I followed it religiously but can't help wondering whether I couldn't have just skipped the clear and reload.
2. Why isn't it possible to run a standalone version of the recalibrator on an adhoc basis when required? - If the touch screen fails again once the tablet's been in use for a while this procedure will be far more of a nuisance.
Anyway, Richard, I thank you for the sage advice and my wife thanks you for her now having a tablet instead of a netbook. Only thing is, I was going to buy a new touch screen for my Tosh (which is 'starred') but since it would cost more than this now-perfect Vega I can no longer justify it.....
Thank you indeed.
My Vega has suffered from random screen badness since I first went to vegacomb.
I had to live with it by treating it like it was a baby not to be upset!! Otherwise the screen and the dummy went outta the pram.
Could anyone provide some more download links? as Richards dropbox is creating too much traffic and has been disabled for a while.
Sent from my Advent Vega with a screen like a slapped ass!
recovery boot problem with this method
hello
i have exactly the same issue as cboard with a vega probably bought at the same time!
i have followed richardmlea's post but seem to be having trouble with the vega recovery boot. I have installed it into the test rom with the file manager but when i run it it boots to recovery (android man with the orange arrow) but hangs here, if i eventually then press the power button it shows the vega recovery options but none of them work and just send me back to the android/orange arrow recovery screen. in the bottom of the recovery page it says something like
formatting: ... misc
i'm sure this will also solve my 'cold' vega problem so would be grateful of any help
thanks
keith
kiffmoore said:
hello
i have exactly the same issue as cboard with a vega probably bought at the same time!
i have followed richardmlea's post but seem to be having trouble with the vega recovery boot. I have installed it into the test rom with the file manager but when i run it it boots to recovery (android man with the orange arrow) but hangs here, if i eventually then press the power button it shows the vega recovery options but none of them work and just send me back to the android/orange arrow recovery screen. in the bottom of the recovery page it says something like
formatting: ... misc
i'm sure this will also solve my 'cold' vega problem so would be grateful of any help
thanks
keith
Click to expand...
Click to collapse
Same issue here,
Also, tried to install CWM from Rom Manager but unable to gain root access?
Any suggestions to install CWM rather than the stock vega recovery?
Bad nand blocks
Glad it helped you all.
More Vega’s saved from the scrap heap; I can feel the ozone layer growing back as I type. I think I may burn a tree to celebrate.
x5starguerillaa said:
Same issue here,
Also, tried to install CWM from Rom Manager but unable to gain root access?
Any suggestions to install CWM rather than the stock vega recovery?
Click to expand...
Click to collapse
This Issue is caused by block in the bad nand ram. The bad blocks you have are in the boot partition so recovery is not flashing correctly to the ram. If the bad nand where elsewhere (everyone has them to some degree) they would be causing a different problem.
The solution is to install a rom that re-partitions the nand differently (effectively moving the physical locations of the recovery and other partitions on the nand)
This was the reason 2 versions of Moddedstock were created. Moddedstock re-partitions Nand to make more space for larger versions of android (originally Vegacomb). Newbe5 discovered that altering the location and size of the boot and recovery partition fixed the problem for some but created the same problems for others. He created Moddedstock version 2 so there was a second version so people could have a second roll of the dice, so to speak.
All versions of VegaICS have the same partition layout as moddedstock version 2 (I think) but of regardless which is one now being used, there is only one base. This is why some people get stuck at the boot logo after installing Vegaics and others cant boot recovery.
Ideally we need 2 partition layouts again.
The solution for both of you above is not to install or boot CWM recovery after calibration on the factory test rom. Instead turn it off, put it in nvflash mode (back/power button thing) flash moddedstock and when booted select boot to recovery. If this fails any point (installing, booting or recovery) get the other version of moddedstock and try that one, one of them should work for you.
Good luck
Richard
I tried the shuttle test rom in my viewpad 10s with totally unresponsive touchscreen, but it didn't work. After hitting "back" button to start screen calibration, it jumped to setup screen and the touchscreen is still not working at all. Already tried to reflash the shuttle rom few times.
Any idea how to fix it? Thanks.
Answered on modaco thread
http://android.modaco.com/topic/352220-how-to-fix-touch-problemadvent-vega-p10-10s/
rchoi999 said:
I tried the shuttle test rom in my viewpad 10s with totally unresponsive touchscreen, but it didn't work. After hitting "back" button to start screen calibration, it jumped to setup screen and the touchscreen is still not working at all. Already tried to reflash the shuttle rom few times.
Any idea how to fix it? Thanks.
Click to expand...
Click to collapse
Is it possible to restore a cwm backup after doing this or will that simply undo what this process fixes?
Edit: I'm running VegaICS Beta1 btw
Sent from my Vega using XDA
Thanks for advice on bad nand blocks Richard. I will give that a whirl later this evening.
Sent from my HTC One X using XDA
fubofo said:
Is it possible to restore a cwm backup after doing this or will that simply undo what this process fixes?
Edit: I'm running VegaICS Beta1 btw
Sent from my Vega using XDA
Click to expand...
Click to collapse
It depends on what you are referring to.
Restoring the CWM will not undo the touchscreen fix. However, most roms that are not android 2.2 (everything useful except corvus5) will fail to calibrate the screen properly*, so over time heat (and probably other things) cause the calibration to go off. Using the shuttle tools calibration app wont work properly.
Eduardo's new touchscreen driver fixes this problem so the calibration works correctly. Unfortunately this driver was made after Vegacomb beta 1 was released. There are a couple of updates that I know of (*one by Scanno one by Areo) that include the new touchscreen driver.
If your CWM backup contained this new Touchscreen driver, after you restore your backup you shouldn't have any further problems. You may occasionally loose calibration but the screen calibration app (in shuttle tools) will work correctly and the touchscreen will work again after calibration (so no need flash another rom).
If it’s the partition layout and the nand issue you are referring to.
A cwm backup won’t change the partition layout but will restore the contents of the recovery and boot partitions. The bad nand will still be there but in a different place (relative to the old partition layout). If the errors are somewhere critical the tablet may not boot after restoring the backup or boot to recovery may not work. If the errors are somewhere less critical it may not affect you at all. The bad blocks are common to all nand, as long as there are not too many they won’t cause any problems.
Thanks for getting back richard.
I do have the latest VegaICS beta1 installed along with the UpdatedApps patch and Kernel supplied by scanno. No my concern was not about the recovery partition issue, it was reference a full system backup from CWM.
So just to confirm:
I should be able to create a complete system backup (nandroid) then apply this fix? A nandroid restore should not undo the fix so long as I have the latest kernel installed (I believe I do), would that sound about right?
Sent from my Vega using XDA
Exactly right.
Fingers crossed anyway.
I only had to do the fix once, a few days later the new driver was released and I used it immediately. The only touchscreen related issue I have had since was a slight loss of calibration after I had been playing a game for about 4 hours. The screen had got very hot and started to loose accuracy. The screen calibration in shuttle tools restored normality in seconds and it hasn't happened since.
I have since put a sheet of Mylar between the LCD and the motherboard to deflect heat away from the touchscreen. This may have helped, its defiantly cooler.
http://forum.xda-developers.com/showthread.php?t=1585071
Great, thanks for that. I'll have a go and get back with any success. My screen has random sensitivity issues and regularly hits keys multiple times, gets a bit annoying after a while lol.
I take it the Vega tools you refer to is the shuttle tools app?
Sent from my Vega using XDA
fubofo said:
I take it the Vega tools you refer to is the shuttle tools app?
Sent from my Vega using XDA
Click to expand...
Click to collapse
Doh!
Yes, do. I will change it to avoid confusion for anyone else.
richard's advice if you can't boot to recovery
hi richard
thanks for your further advice on bad nand blocks and booting into recovery, followed you further method and at present (touch wood!) the unresponsive 'cold' screen issue has been solved
appreciate your help saves me sending it back to currys ebay!
keith
Ive got a problem where after installing the P10_image_20110411_v1.10.4_std_dev rom, and rebooting into recovery. Im presented with this screen:
Code:
Android system recovery <3e>
Android system recovery utility
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
_______________________________________________________
Formatting MISC.....
Now im able to highlight the options using the up/down volume keys but i cant select anything. The power button just hides all the options and the back button seems to do nothing.
Has anyone else come across this or got a resolution?
Hi everyone,
I've been a proud GT-I9100 user now for almost a year, without any bigger problems. However, since two weeks, my sgs2 is rebooting itself when disconnected from the USB cable.
Every time I disconnect my device from the charger, it reboots 5-10 seconds after disconnection. As you are aware, the reboot sequence is normally:
- SGS2 text screen
- splash screen
- bootanimation
- lockscreen
- asks PIN code
- ready to use.
In this case, however, it completely skips the SGS2 screen, splash screen and the PIN code. In short, the bootanimation suddenly shows up and then you are again ready to go just in a few seconds without putting in your PIN. As I said, it's been like this for two weeks, but I was too lazy to do anything about it until I accidentally removed the plug while browsing the web and lost some important information in the process. I already tried a different charger and cleaned the USB port with pressurised air without any effect (not that I expected it to have).
I've heard of a "soft reboot". Could my issue be that and how could I fix it?
Rom: Hydra h2o v. 1.4.1.
Kernel: Hydra r26
Recovery (came with the rom): CWM Touch 5.5.0.4.
All found at: http://forum.xda-developers.com/showthread.php?t=1403044
Any help would be appreciated!
Oh, and one more question. If I wanted to flash the official firmware back with ODIN, would it overwrite my kernel? If so, would a Nandroid restore also restore my kernel back? (Stock --> CF-Root via ODIN --> NANDroid restore --> back to hydra kernel?)
Thanks in advance! :fingers-crossed:
edit: Here is a video where I show both the "soft reboot" and a normal one to compare. Please don't mind the quality which is a bit shabby.
http://www.youtube.com/watch?v=vDSFvV91tuo
Try to wipe data/factory reset in cwm recovery mode(backup your current rom first)
Then reboot device... if the problem still appear, flash another stock rom via ODIN PC...
If the problem is the software, won't backing up in CWM and restoring it after a wipe just make the phone exactly as it was before wiping? So the problem won't go anywhere. In fact, as I think of it, if the problem is software based, would anything, including ODIN stock flash, help at all if I later restored the NANDroid backup? Would it just bring the problem back?
What kind of reboot this even is? I've actually never seen a thread about a reboot which skips the SGS2 screen, splash screen and PIN code...
Flash back to stock -> Root -> Find out which Kernel you want that is used in the custom ROM and flash it separately through either odin if tar file, or through cwm if zip file.
T__ said:
Flash back to stock -> Root -> Find out which Kernel you want that is used in the custom ROM and flash it separately through either odin if tar file, or through cwm if zip file.
Click to expand...
Click to collapse
Thanks for the reply.
However, I already know that this way I can get rid of any software bug causing reboot, including this (i hope so, else it's gonna be a warranty case). The question i'm pondering, is still, will the problem will come back when restoring a nandroid backup of the phone as it is now.
Anyone know the effects of a nandroid restore? Or the kernel question?
Hi
I'm trying to repair a friend's GS3 i9300 that went through the washing machine.
I've placed in rice for 3 days and everything seems to work with the exception of the capacitive soft keys. USB connection to copy files via the drag and drop method in "my computer" doesn't seem to work. Though USB does work as I can do operations through Odin like flashing CWM so on.
Anyway, the main issue was that my capacitive keys didn't seem to work. So I thought an easy fix would be to install a AOSP rom with the nav on screen menu keys enabled.
Well, it wasn't so easy. The phone is behaving strangely.
Steps I've taken:
1. Flash 4.1.2 official with samsung base rom. Everything works with exception of soft keys. So I go to try the AOSP based rom.
2. Root, flash with cyanogen mod 10 4.1.2 - it resets after a few seconds of booting into the OS, so I can't do many operations.
3. Try slimbean rom, 4.1.2, same as the above.
4. Try Rovolt rom 4.1.2 same as above.
5. Try Cyanogen version 9 (4.1.1) - touch screen does not work BUT capacitive buttons do work. (WTF?). Because touch screen doesn't work I can't do anything.
6. Try Slim bean 4.1.1 - touch screen again doesn't work but capacitive buttons do work and light up. Again, wtf.
Capacitive buttons also work in CWM recovery mode.
It seems anything AOSP based rom doesn't work. Either I can restarts with a 4.1.2 base or no touch screen features for any earlier AOSP roms on a pre 4.1.2 base (but capacitive buttons do light up and work).
It is very strange indeed.
so in a nutshell:
-Samsung based roms seem to work, but capacitive buttons don't work. Does anyone know how to get onscreen nav buttons to work on a samsung based rom?
-AOSP based roms on 4.1.2 automatically reboot after a few seconds in the OS. Capacitive buttons not working.
-AOSP based roms prior to 4.1.2 (such as Cynogen mod 9) do boot fine, but touch screen doesn't work. Capacitive buttons do work.
-CWM capacitive buttons work.
It's so strange. Any advice for me? I just want this phone to work - whether with onscreen nav keys or the whole kit.
Thanks
There is a build.prop tweak to enable soft keys in sammy rom. He. Qemu. Something I don't remember lol, search for it. Once you add it to build. Prop and restart your mobile you will have onscreen buttons
《posted from cm10.1》
bala_gamer said:
There is a build.prop tweak to enable soft keys in sammy rom. He. Qemu. Something I don't remember lol, search for it. Once you add it to build. Prop and restart your mobile you will have onscreen buttons
《posted from cm10.1》
Click to expand...
Click to collapse
Thanks - It would be great if you or someone could direct me to how I could do that by flashing a .zip in cwm. Or via a file explorer. I can't use solid explorer as I can't browse to root (not back button obviously).
Thanks!
Hujbalo said:
Thanks - It would be great if you or someone could direct me to how I could do that by flashing a .zip in cwm. Or via a file explorer. I can't use solid explorer as I can't browse to root (not back button obviously).
Thanks!
Click to expand...
Click to collapse
I'm not an S3 owner but i thunk this can help. and one more thing,
i suggest you explore more.
Sent from my GT-I8160 using xda app-developers app
Did you do a full wipe before flashing? Always do that before flashing a new rom. Also wipe system partition just to be sure. If it doesn't work try and flash a official image with odin.
kickokim said:
Did you do a full wipe before flashing? Always do that before flashing a new rom. Also wipe system partition just to be sure. If it doesn't work try and flash a official image with odin.
Click to expand...
Click to collapse
Everything has fixed itself but for one thing.
Reception. Reception in doors or reception in genearl is not as strong as it was before the water damage. Outside i can get decent reception, but inside it kinda cuts off frequently. Any suggestions? Does it cost much to replace the antenna?
take off the back of the phone and use a small screw driver to remove the antenna module.
btw, for water damage, its best to soak the device in 100% pure, 200 proof, ethyl alcohol, first to flush water away from sensitive contacts before putting it into rice
do not use isopropyl or cleaning alcohol as these leave residue on trace.
qemu.hw.mainkeys=0
Add that line on build prop on stock samsung rom for soft keys
Sent from my GT-I9000 using xda app-developers app
Im new to Android world, so please help me.
Now, my Nexus 7 Wifi is now unlocked and rooted by your tutorial, and
flashed Xenon HD Custom Rom.
I was in Jelly Bean 4.2.2 before. And i found some site that says
XenonHD is updated to 4.2.2 version, so i try to get it, and installed it to
my device. But after evrything done, i checked my device's version and it
says 4.2.1, but im sure i downloaded the right one, dated April 2013, as
far as i know. So, my device was downgraded to 4.2.1
Question:
a) Is it just that easy for downgrading an Android device? Because on
iOS, there are lots of concerns first before you can actually do
downgrading..
b) After installing apps, i made a backup with Nexus Root Toolkit, and
after the backup process, it reboots, and i notice that something is
wrong, the X animation logo goes somewhere at the lower right, and
when it goes to lockscreen, since im locked on landscape orientation,
half right side shows first then the half left side, youll really say that, it is
not okay. I tried rebooting by XenonHD settings, i tried to turn off and turn
it on again, same thing happens, what should i do?
c) About XenonHD, is it just one theme available? or i can download more
themes elsewhere? can somebody point me to where can i do that?
d) should i be re-flashing for XenonHD 4.2.2? How would i do that?
e) And what more can i do to my device to achieve it AWESOMENESS
Thanks in advance..
a) Yes, on many android devices it's that easy to downgrade. You don't need to jump through all the hoops like iOS requires you to.
b) Sounds like something may have gone wrong during the install process. Perhaps you could post a picture of what it looks like.
c) not sure, never used it.
d) Guess that's up to you. If it's an upgrade then it could fix the screen issue you're having. You'd flash it the same way you flashed the 4.2.1 version.
I'm sorry for spoonfeeding.
zeneleven said:
a) Is it just that easy for downgrading an Android device? Because on
iOS, there are lots of concerns first before you can actually do
downgrading..
Click to expand...
Click to collapse
Yes. XenonHD says it's 4.2.2 though, so I'm pretty sure you flashed an old build or the dev forgot to edit some text to make it say 4.2.2.
zeneleven said:
b) After installing apps, i made a backup with Nexus Root Toolkit, and
after the backup process, it reboots, and i notice that something is
wrong, the X animation logo goes somewhere at the lower right, and
when it goes to lockscreen, since im locked on landscape orientation,
half right side shows first then the half left side, youll really say that, it is
not okay. I tried rebooting by XenonHD settings, i tried to turn off and turn
it on again, same thing happens, what should i do?
Click to expand...
Click to collapse
Flash a different ROM or reflash your current one. Backups shouldn't have any effect on the ROM; if the backup app you're using negatively impacts your experience, switch it (I use titanium backup). TWRP recovery also supports nandroid backups.
zeneleven said:
c) About XenonHD, is it just one theme available? or i can download more
themes elsewhere? can somebody point me to where can i do that?
Click to expand...
Click to collapse
From the ROM thread, it says it supports CM10.1 themes (theme chooser). Search "CM10 themes" on Google Play to find them, then go to your settings to apply.
zeneleven said:
d) should i be re-flashing for XenonHD 4.2.2? How would i do that?
Click to expand...
Click to collapse
First, download the ROM to your device (if you haven't already), and google apps.
Make a backup of your data (nandroid or Titanium backup or some other backup app).
Then hold the power button, and select either "reboot"/"restart" or "recovery".
If you select "reboot" and no option for "recovery" comes up, hold down the volume down key while the device is restarting, then navigate using the volume buttons once the bootloader pops up, to the "recovery" tab.
Verify that the recovery installed is indeed TWRP (TeamWin recovery). If it isn't stop, and get TWRP before continuing.
Once your recovery pops up, select "factory reset", and swipe.
Then, select "install" from the menu that pops up, navigate to the folder labeled "downloads" and select the ROM file, and then select "add more zips", then select the gapps (google apps) file.
After that, swipe the little bar to start flashing, then after it's finished, select "reboot system".
Once the thing has properly booted into the setup screen, set it up, and restore your data.
zeneleven said:
e) And what more can i do to my device to achieve it AWESOMENESS
Click to expand...
Click to collapse
Install M-Kernel and Trickster Mod (app).
Install Nova launcher.
Install fdroid (for freedoms).
Install MX Player.
Ive already re-flashed with XenonHD's latest update i think, and yeah its on 4.2.2. and still, got the lockscreen problem which i solved by changing the lockscreen orientation, locking it to portrait.. and got more error like "Apollo" and its launcher "has stopped" something.. and the voice dictation, exits when being used, wherever im in..
Now, im planning to switch to Cyanogenmod for 4.2.2, since it has few themes available.
About Kernel? Can someone help me how to do that? a great guide will be greatly appreciated, done searching and cant find it, i swear.
Thank you so much in advance
I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.
hecksagon said:
I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.
Click to expand...
Click to collapse
Interesting I wonder if its repeatable? I guess its will be hard to test unless you already messed up, nobodys gonna mess up on purpose just to try this out without a hardware recovery option but maybe someone who messes up on accident will report back here on what they found out.
Wasn't able to repeat it on the Ouya kernel with CM ROM installed but it seems to work all the time if you get a boot loop in CM10 kernel and CM ROM. I'm still not feeling safe enough to actually flash the CM kernel, so I am still using fast boot to boot the kernel from a laptop.
On a side note, I do have xbmc set up as my launcher and have list of working skins that can launch android apps from. Once I figure out how to get the crazy CPU usage I am getting worked out I plan to make a guide for a full media center.