Related
hi, after installing CM 7.1 my tattoo screen doesn't respond well and htc calibration doesn't solve it, it says there's an error in calibrating.
now, in CM 7.0.3 the screen responded in a perfect way, is there any way to take a "file" in CM 7.0.3 zip and substitute it in 7.1 zip to make the screen work properly?
thank you
i made a test with the dev tool pointer location that clearly shows that there's a problem with certain coordinates. any idea to set it properly??
thanks
last thing.. in 7.0.3 pointer location was perfect.. if there's no way to fix it in 7.1 then I must go back to 7.0.3... but I'd like to be sure of this..
can anyone help me?
Have you tried with HTC-calibration app?
yes, i did. htc calibration can't set calibration, and at the end of the procedure it says: invalid calibration points.
I tried to insert good calibration points in calibration_points file with the command:
echo 812,907..etc > /sys/class/input/input1/calibration_points
but the values don't change, they remain the same...
I went back to 7.0.3 ...
mmmmmm I don't know how i can help you...try with a wipe and re-flash...it is the only thing I could propose you...Sorry
i wiped cache, data and dalvik and reflashed..nothing.. wiped all again and installed nightly 226.. same error... i thing there's something wrong with the new kernel for my tattoo...
btw thanks i'll enjoy my 2.3.3..
Flash the attached file in recovery, and then try to recalibrate.
thank you very much for the file, I flashed it, but unfortunately when I launch HTC Calibrating the response is the same : "invalid calibration points".
btw thank you again for the attempt
arco68 I executed this:
1) I was on 2.3.3
2) went to recovery and wiped data/cache
3) restored a previous installed 2.3.7 with bad calibration issue
4) Flashed your file.zip
5) rebooted
result: not working..
I was wondering... do I have to make a clean install of 2.3.7 from update.zip then flash your zip and check the situation or I won't have any advantage from this kind of procedure?
thanks
another thing, my recovery is clockworkmod v5.0.2.0
Oh well. The fix erases current stored calibration points. I thought that it might help. It's weird cause I don't have this issue myself.
I'm not a developer but I think there's something wrong with the new kernel and my tattoo... anyway I thank you for your advices!!
My calibration too is wrong.
Screen's height is ok, width is 10/15px smaller [centered].
It's quite hard to type on the keyboard.
I'm on NB241
in my device, on the contrary, height is smaller and width is ok
p.s. I'm from Rome too, the first one that find a solution post on this tread!!
Htc Calibrate tool was behaving bad, don't know why.
... i rebooted the phone and then i recalibrate it well.
Maybe i left the phone on the table and not in my hands?
G
check my post, see if that helps in calibration
http://forum.xda-developers.com/showpost.php?p=19347289&postcount=60
+1
i have the same problem with calibrating the screen. htc calibrate works good at nfinity 1.08 and i have no problem with touchscreen. but with full wipe/factory reset and installing nfinity 1.09 and above the problem is back again, and htc calibrate says Invalid calibration points. I've tried Arcos and Rallapag fix/zip with no success. for now i am back to nfinity 1.08
Check progress in DEV section http://forum.xda-developers.com/showthread.php?t=1562595
( I have posted less than 10 posts, so I can't write in the dev section. )
Stupid question : is it using Holo?
And, if it is based on CM9, it is rooted, isn't it?
If WiFi works, I'm SURELY going to try this!
I installed it yesterday. Wifi works, it uses Holo, hat root and performs better than I expected.
Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.
Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
/=\lex said:
Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.
Click to expand...
Click to collapse
Yea is pretty smooth overall eventhough hardware aceleration is not working, this port looks really promising,
Tried it yesterday and in My view its the smoothest ics ROM ever tested.i had some fcs but will try Tor correct rights via rommanager.if GPS is working i will use this one.its a must Have for me.
Sent from my Legend using XDA
Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
Click to expand...
Click to collapse
I'll try keeping it on for more time. By my first impression, it doesn't look so buggy, I think it is also quite stable. I'll tell you if I find anything.
Anyway, this is a great ROM, thanks for your work!
EDIT : Stupid question : to install GApps I have to flash the zip, right?
EDIT 2x : Yea, it was a very stupid question. Flashed from clockwork recovery. Works perfectly.
Its getting better and better. but still GPS not working. Hope you get it fixed soon.
Realy great job!!!!!
really good job. Just need GPS and Camera.
Hoping for 2.5 soon...also hoping based on Android 4.0.4.
How is work going?
Sent from my Legend using XDA
I have a problem with the latest 3.0 version.
After i flash gapps i keep getting boot loops.
If i dont flash it and just flash the rom it boots fine.
Dont know what the problem is. Can someone help me?
I have the exact same problem as DareFace, but I think zeubea is aware of the problem.
zeubea-cm-9.0.0-ALPHA3.0.1 and Google Apps
I tried install this ROM multiple times today, everything works until i install gapps (full or tiny). After that phone enters infinite boot-loop (HTC logo on white background).
Radio 7.13.35.05
Bootloader HBOOT-1.01 (S-ON)
ClockworkMod Recovery 5.0.2.0
Edited @ 08:31PM GMT+2
After installing gapps over gapps works as a charm. That's weird...
I had the same bootloop problem until I installed another kernel that Zeubea provided. It's till get some fc's, mainly for clock and email, but the email still works, clock is inaccessible atm.
It's even better than cm 7.2RC1, running oc'ed at 787mhz ! It's so smooth and beautiful. Let's hope that the gps and camera will get fixed soon. If I had capabilities to donate, I so would do it.
Thanks Zeubea! The Legend community loves you, keep up the wonderful work of making our ICS dreams come true when htc can't and won't deliver.
The reason for bootlooping is the clock issue.
The default clock in 3.0.0 is 806MHz - something every Legend doesn't handle, so it bootloops.
The 3.0.1 version has this "problem" fixed.
I faced another issue releted to sounds. I change both ring and notification sounds and after some time i realise that they are reverted to default!
I have this weird thing where the danish keyboard force-closes.
It's everytime i type the word "lige". It doesn't do it with the english keyboard
I've tried to turn off the spelling correction, since it's in english, and there isn't a danish one, but it doesn't help.
Other than that it's great
bootlooping after flashing cm9 gapps, possible fix
boots up normally after flashing the zip in CWM, but after flashing gapps it bootloops, and after awhile of countless flashing i discovered it bootloops even before flashing gapps, so i tried different step to flash it and finally it boots up normally, here's what i did :
1) full wipe, dalvik cache and cache partition, factory reset
2) flash the main cm9 zip
3) full wipe, dalvik cache and cache partition, factory reset (again)
4) flash gapps (not tiny version)
5) reboot, if it boots up normally thats great, if not its ok, continue to step 6
6) boot into CWM
7) dont wipe or anything*
8) flash the main cm9 zip
9) instead of rebooting device, continue by just flashing gapps (not tiny version)
this were the steps i did to fix the bootloops after flashing gapps, apparently the gapps tiny version is not compatible with cm9 on the htc legend thats why i stick to the normal gapps file, i hope this helps anyone of u experiencing the bootloops after flashing gapps
I have some kind of problem with wifi connection. If "Keep Wi-Fi on during sleep" is set to "Only when plugged in". After I wake up phone wifi is turned on it cannot find any networks.
EDIT: Logcat trimmed to "network|wifi|power|conectivity" http://pastebin.com/pdUAbfDy
And terminal emulator displays an error "Unfortunately, Terminal Emulator has stopped" when I try to open it.
EDIT: Logcat http://pastebin.com/ChRUu3jS
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?
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
jnktechstuff said:
MOD : EDIT
try dleeting you who system, except your recovery , there should be a system whipe that should work, then reflash ur rom
Click to expand...
Click to collapse
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..
yeatsie said:
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..
Click to expand...
Click to collapse
check you camera connector. It may come lose from the motherboard. Try reseat the connector.
Sent from my A500 using Tapatalk
.
opened up the A500 last night - all looked good, all connectors in place, nothing obviously wrong?
Noticed the screen when i switch to the rear camera has artifacts from other screens in the background (ie Pulse app title heading etc) suggesting some kind of software glitch?
yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
Known issue in the CM10 alpha test ROM. You should go to the one in general rather than making your own thread which WayDownSouth is unlikely to see.
http://forum.xda-developers.com/showthread.php?t=1789711
yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD
Moscow Desire said:
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD
Click to expand...
Click to collapse
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.
yeatsie said:
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.
Click to expand...
Click to collapse
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD
Moscow Desire said:
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD
Click to expand...
Click to collapse
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..
yeatsie said:
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..
Click to expand...
Click to collapse
Boot loader is different from cwm recovery. When you boot, it should say in white text.
If in doubt, run Acer recovery installer from the market. It will tell you which version.
MD
ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app
I have always had this intermittent problem on my a500. I have always used the stock ROM since I purchased it, and it's been the same since each OTA upgrade, so I doubt that it's a problem inherent to one custom ROM or the other.
A Dalvik cache clean has never worked for me, sometimes a restart has helped, but more often than not it doesn't help.
If someone discovers a set of steps that fixes this problem every time it occurs, I would be glad to hear of it.
yeatsie said:
ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Hi, What was your final solution to this problem? I'm trying to fix mine right now.
-Thanks-
No fix as yet, pretty much gave up trying to use the camera.
Sent from my Nexus 7 using Tapatalk 2
If anyone else's having this problem with ONE OF THE CAMERAS (Not both of them but frontal OR main) then this should be the solution:
Watch this video someone uploaded https://www.youtube.com/watch?v=Cjevl8I6rIA but HAVE THIS IN MIND:
That cord (FLEX) he's talking about is for the FRONTAL camera. Not related with the main or back camera. So that should fix the green trouble for the frontal one.
But, if the main camera shows green image or weird lines, that's likely because its connector is not correctly attached to the main board. That connector is NOT a flex, but it's a built in block in the board of the same camera unit. You need to remove or lift the main board, totally remove the main camera unit, clean the connector (both male and female) with alcohol and connect it again applying some pressure. If the trouble really was the connector not being correctly placed, that totally fixes it.
If it worked, let me know
That totally worked and fixed my green screen camera problem, thanks! (was a total pain to re-seat the camera but worth it)
Title says it all guys blowing of the dust of this thing can anyone point me to the most stable ROMs out there CM10 prefer
Sent from my HTC6435LVW using Tapatalk 2
I'd like to know this too. I often have to turn wifi off then on to reconnect.
Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings
Team EOS 4, Katkernel here too, make sure you reboot a few times after installing it. follow the guide in this forum, install it like it directs you to.
FULL wipe(cache, dalvik, factory, system), install ROM, cache/dalvik wipe, install gapps, cache/dalvik wipe, install Kernel, cache/dalvik wipe, reboot.
Get Kat apk to boost volume and GPS fix.
I was having systemUI issues, reinstalled everything a few times and now it's running great. Keep it under 1400mhz, 1200mhz seems to work well for me. Nightly 109 was eating up my battery too quickly, 111 is doing better, I hope they can improve more if possible, great ROM either way, I'm very grateful.
Sent from my Transformer TF101 using xda app-developers app
I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.
Astania said:
I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.
Click to expand...
Click to collapse
Just reply to a few other threads, XDA has thousands
+1 for EOS4/KAT kernel. No-name is pretty good as well if you like CM 10.1.
EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing
+1
talman26 said:
EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing
Click to expand...
Click to collapse
Aye...EOS 4.2.2 (v109) + 1400, very stable, no big issues, suitable for daily drive tab
+1
Team EOS4, Been using it for months and not a WiFi hicup.
*Detection* said:
Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings
Click to expand...
Click to collapse
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
Can you still get into recovery? If so, can you flash from the microSD?
danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs
Team EOS 4 + Kat Kernel = FAST and STABLE :victory:
PS: If you wish to use Phablet UI i suggest you use Trebuchet from CM 10.1
*Detection* said:
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs
Click to expand...
Click to collapse
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!
danilimpsy said:
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!
Click to expand...
Click to collapse
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Sent from my Transformer TF101
zAlbee said:
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Click to expand...
Click to collapse
As I already said...flashing ROM FAILED over 5 to 7 times...and I CAN´T get to APX...i´m stucked at NO SYSTEM...just can get to Recovery, but NO flashing!
Try a different PC, or reinstall APX drivers
99% that APX mode does work, either you are doing something wrong, or your PC is struggling with the APX drivers
APX mode is volume up & power from powered off state while already plugged into PC, the only notification for entering APX mode is USB connect sound, nothing will appear on TF screen
I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment
hulk69 said:
I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment
Click to expand...
Click to collapse
Have to ask, what recovery did you use and did you do a full wipe before installing?
I find EOS 4 to be MUCH more stable on WiFi than any ICS ROM (including Stock and stock based ROMs)