Database Users

Why not add an Optical Track Wake to your Incredible...

I am not sure if you are like me & like pressing the optical track device to wake your phone or not... but I have a solution for that if you do.
Seems many Incredible ROM's have left out the important Optical Track Device Wake feature. Flashing this over certain ROM's will make it where you can press it, and the screen will come on.
I have personally tested it on Desire/Sense ROM's, and it works. Only thing is, sometimes you may have to hold it down for a few seconds, and sometimes its instant.
INSTRUCTIONS:
First, make a Backup/Nandroid Backup, then flash this zip file via Recovery, then reboot.
If this helps, please feel free to use that "Thanks" button. lol
I am not responsible for any issues this causes, as everything you flash is solely at your own risk.

The same zip is also available in rom manager under the virtuous goodies. Thanks for posting it here as well.

I believe the proper way to do so is to push qwerty.kl to /system/usr/keylayout/qwerty.kl
I think the keylayout you posted is from a Z rom...correct me if I'm wrong.

The rom I run uses this and I have often noticed the uncertainty of wether its instant or not. However, when plugged into my car charger, it wakes up perfect every time.
I also use a lockscreen widget to save on the power button usage. Works very well.
Sent from my ADR6300 using XDA App

NexusOneOwner said:
INSTRUCTIONS:
First, make a Backup/Nandroid Backup, then flash this zip file via Recovery, then reboot.
Click to expand...
Click to collapse
Is there a quick way to convert this to an Edify script for CWM 3.x.x.x and beyond? I'm running a GingerSense ROM now and would like to give it a whirl, but I don't want to downgrade CWM just for a mod.
UPDATE - Ran Amend2Edify on the script and CWM 3.0.0.8 keeps aborting flash.

its usefull for some roms
but not for all
thanks

I figured it out; opened the zip file up, pulled the file out and embedded it in my ROM before flashing. Works like a charm. (And developer has promised to include it in next version anyway).

Worked for me, Thanks.

[Q] Possible destroyed my Note.

Hi guys,
Pretty new to the android scene (came from iOS). After using my Note at stock rom for about 2 months I decided to go ICS. Well.. here is where the pain started. It seems I have really ruined my phone, however I do not understand why.
What did I do?
I rooted my phone with CWM and used ODIN 1.8 to flash a default rom (as the guide told me to) so I could flash ICS afterwards. At the moment I flashed the first rom something strange happend. The phone was clicking itself (I will add youtube links as soon as I can) just at the middle of the screen. For example, if I were to send an SMS (vertically placed) it will press T or G constantly, depending on the rom. <-- Weird right? It actually switches to G or T depending on the rom, which should indicate software problems and not hardware.
As far as I know it has something to do with the way android mounts the SD card. Because as soon as I plug in the USB, the problem is gone. As soon as I unplug its back again. The ''clicking'' seems to be localized on the same place no matter if I go portrait or landscape, must be hardware right?
I've flashed over 50 times. Using different kernals, rockroms, ICS etc. etc. They all show the same problem. Even after ''factory resets'' in CWM, reinstall stock rom etc. I've even deleted everything on the internal SD card (as far as I could see files, not sure about hidden files) but that didn't help either.
Didn't make a backup either (dumb ****ing me) but I figured it wouldn't matter because I had a stock rom from my country zipped anyway.
The fact that it only shows up unplugged, must be an indication it has something to do with the fact that it only occurs during the mount of android to the phone.. but I can't figure out how to solve it.
HELP

Clicking itself? As in, it was registering touches at the center of the screen, without you actually touching it?

Yes, exactly that. It simply registers touches without me touching it.
There is no damage either, screen is clean as can be.

I've seen a few users here on the forum having issues with their touchscreen, and almost all the time the charger/cable is identified as the culprit. Search the general and Q&A forums with "touchscreen", you'll find a few of these posts.
It seems the screen is affected by voltage fluctuations, or incorrect voltages due to use of third-party cables/ chargers. If your Note is connected to the computer and the earthing for your machine is not proper, it can cause issues too. Some people suggest using a different power outlet, or at a friend's place, just to be sure. Also, the screen seems to get damaged that way very quickly, and no software changes seem to solve anything.
I personally haven't experienced a problem like that, but I'd recommend that you flash a stock rom for your country using Odin on the PC, and get the phone replaced.

This may sound dumb... but try taking your s-pen out of the back.
Some users report over sensitive screens, and it wouldn't surprise me if it would go THROUGH the back of the phone.
Give it a shot, let us know.

Just try full flash via odin with .pit file and repartition checked. Maybe it will help you.

Hi Guys,
Thanks for your input!
After the suggestion about voltage it got me thinking. So I charged the battery to 100% using a different power outlet. Problem seemed to be gone for a while, but as soon as the battery hit 80% or so it started again. Seems the voltage regulation is off scale or something like that. Either way, the damage seems to be permanent.
I flashed back to stock rom, gonna mail it to the samsung repair center tomorrow.

arf_cz said:
Just try full flash via odin with .pit file and repartition checked. Maybe it will help you.
Click to expand...
Click to collapse
Any idea where I can find this PIT file? Alot of people are talking about it but I am not able to find it.
EDIT: nvm found it

Its not only the .pit file, you need complete full flash (3 files - code, modem and csc).
For me, when i mess up my gnote trying a lot of different roms/kernels/ics stuff, helped this pack (open eu):
link in attached file (cant post links)
it includes odin and some other unimportant stuff. You need only odin, .pit file, modem file, code file and csc file.
In odin tick re-partition, auto reboot, f.reset time and phone bootloader update.
Put pda, modem, csc and pit files, than start and good luck!

Just chill
Hey there,
First things first, it is very hard to get your android messed up so, just and follow the below steps one-by-one and let me know. Please understand by following this process all your data, apps and settings will be reset.
1. Take a back up of all your data using Titanium or MyBackup.
2. Move the back up file to a location on your PC.
3. Flash a ROM that you can root and get CWM to work.
4. Once flashed and rooted, unplug the device and boot in recovery mode.
5. Once in recovery mode
a. Format Data/Factory Reset
b. Format cache
Under the advanced option in recovery mode select
a. Wipe Dalvik Cache
b. Wipe Battery Stats
Under the mounts option in recovery mode select
a. Format SD/MMC
b. Format System
c. Format Ext SD
Once done, select reboot. Now, the phone will be stuck on the flash screen, hold the power button down for as long as the phone does not turn off.
Now launch Odin, select the ROM of your choice.
Press the Power + Middle (Menu) + Volume down button until you get a warning on updating a new firmware, press the volume up button.
Plug the device and update.
Do check and let me know if this helped. The problem here is of the Battery Stats being clogged by moving from Gingerbread to ICS especially LP1 leak is disastrous and cannot be used as a daily ROM.
Please keep in mind the above steps and follow accordingly whenever you are ready to move a much advanced version of the firmware such as ICS and you will never face a problem.

sunil.inxs said:
Hey there,
First things first, it is very hard to get your android messed up so, just and follow the below steps one-by-one and let me know. Please understand by following this process all your data, apps and settings will be reset.
1. Take a back up of all your data using Titanium or MyBackup.
2. Move the back up file to a location on your PC.
3. Flash a ROM that you can root and get CWM to work.
4. Once flashed and rooted, unplug the device and boot in recovery mode.
5. Once in recovery mode
​a. Format Data/Factory Reset
​b. Format cache
Under the advanced option in recovery mode select
​a. Wipe Dalvik Cache
​b. Wipe Battery Stats
Under the mounts option in recovery mode select
​a. Format SD/MMC
​b. Format System
​c. Format Ext SD
Once done, select reboot. Now, the phone will be stuck on the flash screen, hold the power button down for as long as the phone does not turn off.
Now launch Odin, select the ROM of your choice.
Press the Power + Middle (Menu) + Volume down button until you get a warning on updating a new firmware, press the volume up button.
Plug the device and update.
Do check and let me know if this helped. The problem here is of the Battery Stats being clogged by moving from Gingerbread to ICS especially LP1 leak is disastrous and cannot be used as a daily ROM.
Please keep in mind the above steps and follow accordingly whenever you are ready to move a much advanced version of the firmware such as ICS and you will never face a problem.
Click to expand...
Click to collapse
I'm on Imilka's AOSP ICS ROM (GB -> Chinfire repack -> AOSP). If I just delete battery stats via recovery, that should be it, right?

sunil.inxs said:
Hey there,
First things first, it is very hard to get your android messed up so, just and follow the below steps one-by-one and let me know. Please understand by following this process all your data, apps and settings will be reset.
1. Take a back up of all your data using Titanium or MyBackup.
2. Move the back up file to a location on your PC.
3. Flash a ROM that you can root and get CWM to work.
4. Once flashed and rooted, unplug the device and boot in recovery mode.
5. Once in recovery mode
a. Format Data/Factory Reset
b. Format cache
Under the advanced option in recovery mode select
a. Wipe Dalvik Cache
b. Wipe Battery Stats
Under the mounts option in recovery mode select
a. Format SD/MMC
b. Format System
c. Format Ext SD
Once done, select reboot. Now, the phone will be stuck on the flash screen, hold the power button down for as long as the phone does not turn off.
Now launch Odin, select the ROM of your choice.
Press the Power + Middle (Menu) + Volume down button until you get a warning on updating a new firmware, press the volume up button.
Plug the device and update.
Do check and let me know if this helped. The problem here is of the Battery Stats being clogged by moving from Gingerbread to ICS especially LP1 leak is disastrous and cannot be used as a daily ROM.
Please keep in mind the above steps and follow accordingly whenever you are ready to move a much advanced version of the firmware such as ICS and you will never face a problem.
Click to expand...
Click to collapse
Argh, thanks alot for your information.
Unfortunatly I already sent the phone to Samsung for repairs. But your story sounds logical, as well as others did. However I cannot test it at the moment. If Samsung wont fix the problem i'll try your method and get back to this topic.
For those who're insterested, here's a short video of the problem ->
youtube .com/watch?v=_8UV_9jz-Wo <- space between youtube & .com
Thanks alot everyone, will get back to you! cheers
Martijn

bloodyhippo said:
I'm on Imilka's AOSP ICS ROM (GB -> Chinfire repack -> AOSP). If I just delete battery stats via recovery, that should be it, right?
Click to expand...
Click to collapse
This should work, if not take the long route..
Sent from my GT-N7000 using xda premium

Well bloodyhippo,
It turns out you were right. According to Samsung my Note's screen was defective, most likely due to to a lousy/non-grounded power connector.
Which is pretty upsetting as this basicly means I can't charge or flash my phone at 90% of all places im at.
They've replaced the screen, phone works like a charm.
Let this be a warning to all.. The G Note has a REAL sensative screen..!

extreemwisse said:
Well bloodyhippo,
It turns out you were right. According to Samsung my Note's screen was defective, most likely due to to a lousy/non-grounded power connector.
Which is pretty upsetting as this basicly means I can't charge or flash my phone at 90% of all places im at.
They've replaced the screen, phone works like a charm.
Let this be a warning to all.. The G Note has a REAL sensative screen..!
Click to expand...
Click to collapse
Buy a UPS for clean energy and a surge protector.

Vega screen is unresponsive when cold

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?

Does JB or ICS improve touch sensitivity

My number 1 complaint with the 10.1 is that i get finger ache trying to use the tab for an extended period
I just had a play with an IPAD and i'm SOOOO jealous how little you have to touch the screen to make it move etc
will a software update to JB or ICS improve the touch sensitivity of the tab?
Thanks

m.r.davies said:
My number 1 complaint with the 10.1 is that i get finger ache trying to use the tab for an extended period
I just had a play with an IPAD and i'm SOOOO jealous how little you have to touch the screen to make it move etc
will a software update to JB or ICS improve the touch sensitivity of the tab?
Thanks
Click to expand...
Click to collapse
Yeah that's also an issue for me it's responsiveness for touch are not that great...
Hope they fixed this with project butter since it guess where are you gonna touch the screen and react milliseconds before the touch happens
Sent from my GT-N7000 using xda premium

I agree, hopefully Project Butter on JB will solve it.
If you are rooted or know how to, try this.

ICS sensitivity and responsiveness is night and day over HC..
But now after running JB, it is night and day over ICS

force1stiptopped said:
ICS sensitivity and responsiveness is night and day over HC..
But now after running JB, it is night and day over ICS
Click to expand...
Click to collapse
I take it JB is better than ics then!?
Which rom you using? Stable enough to use as an everyday OS?

m.r.davies said:
I take it JB is better than ics then!?
Which rom you using? Stable enough to use as an everyday OS?
Click to expand...
Click to collapse
It really is like night and day and my WiFi tab is as smooth as my Galaxy note check this ROM out if rooted.
http://forum.xda-developers.com/showthread.php?t=1765254#

mobileguynz said:
It really is like night and day and my WiFi tab is as smooth as my Galaxy note check this ROM out if rooted.
http://forum.xda-developers.com/showthread.php?t=1765254#
Click to expand...
Click to collapse
Thanks man
I'm not currently rooted, and have never done such things
I dare not ask too many questions in fear of being flammed, i've read a lot and i'm a bit overwhelmed.
to use this rom, shall i root my device using the tutorial here:
http://forum.xda-developers.com/showthread.php?t=1239185
and do i need to bother with clockwork thing? or just follow the above tutorial?
Cheers

m.r.davies said:
Thanks man
I'm not currently rooted, and have never done such things
I dare not ask too many questions in fear of being flammed, i've read a lot and i'm a bit overwhelmed.
to use this rom, shall i root my device using the tutorial here:
http://forum.xda-developers.com/showthread.php?t=1239185
and do i need to bother with clockwork thing? or just follow the above tutorial?
Cheers
Click to expand...
Click to collapse
Yeah I know what you mean but the best advice is read everything and you need to be prepared for issues and dig under the bonnet so to speak.
This is off topic so don't ask anymore about root here
yes cmw is required which is recovery and Backup everything.
Lots of posts scrolling screens and I used the recovery from here using Odin to flash. http://droidbasement.com/db-blog/
guides here http://forum.xda-developers.com/showthread.php?t=1462961

Thanks man
So back on topic, I really want the smoothness! and
I've read that build is alpha, but are you happy it's stable enough?
smooth scrolling will be amazing, but a tab that keeps crashing is a lot more annoying and I will wait a while otherwise
Otherwise i'll go for the root, and then install that app mentioned above
Cheers for all your advice guys

m.r.davies said:
Thanks man
So back on topic, I really want the smoothness! and
I've read that build is alpha, but are you happy it's stable enough?
smooth scrolling will be amazing, but a tab that keeps crashing is a lot more annoying and I will wait a while otherwise
Otherwise i'll go for the root, and then install that app mentioned above
Cheers for all your advice guys
Click to expand...
Click to collapse
Latest build is up and mine is WiFi only this is suitable for daily use. JB mixed in with CM 10 is really smooth and once Samsung puts out the drivers for camera 3G etc this ROM really does make the tab buttery smooth. Things are so much more fluid. JB ROM has given my tablet and experience as good as the iPad 2. There are things to fix and alpha meet early days but the dev has worked really hard on this and to a lot of us forgotten by Samsung tab owners a huge WOW.

Great, I want to try this
Can I ask, does CM mean clockwork mod or cyanogen mod?

m.r.davies said:
Great, I want to try this
Can I ask, does CM mean clockwork mod or cyanogen mod?
Click to expand...
Click to collapse
Sorry I typed wrong I meant ClockworkMod Recovery
Cyanogen is CM 9 or CM10 whole ROM
See. http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
I use http://droidbasement.com/db-blog/

m.r.davies said:
Great, I want to try this
Can I ask, does CM mean clockwork mod or cyanogen mod?
Click to expand...
Click to collapse
Usually, clockwork mod is abbreviated by CWM and cyanogen mod is abbreviated by CM
Sent from my GT-P7510 using xda app-developers app

1. Download Odin from available threads
2. Download a recovery for Odin flashing (like cwm), be sure to get the correct one for your tab (if you have WiFi only its 7510 or p4wifi, for 3g its p4 or 7500)
2.a you can start downloading the ROM you want right now as well, so you don't have to wait later on.
2.b download appropriate gapps (for ICS or jb)
3. In Odin make sure nothing besides the auto reboot and the thing the right if it is checked
4. Put your tab in download mode: turn it off. Turn it on while holding volume down, you'll get a screen with two icons on it. The right one should already be selected so press volume up to select, if not then press volume down to switch then volume up to check. The tab will tell you to press volume up to continue, do it. Congrats, now you are in download mode.
5. Connect your tab to your computer. One iPod the empty squares above should turn yellow and something written in it*
6. Click PDA for file selection. Select the recovery.tar.md5 you downloaded.
7. Press start, when finished your tab should reboot.
8. Get the downloaded ROM on the tab, however you wish.
8.a backup everything you want backed up. Photos mucpsic and other stuff won't be deleted if its on the "sdcard"
9. Turn off tab. Turn on again while holding volume down.
10. Enter recovery by pressing volume down then using volume up to select (you want the left icon)
11. Navigation in CWM: volume keys=up/down, power button=confirms selection
You want to wipe data, wipe cache and then to into advanced and wipe dalvik cache, return to the top
14. Select apply update, select choose zip, find ROM you downloaded, confirm.
14.b sometimes it might not be best to flash gapps at the same time as ROM, so it may be better to reboot phone then when started reboot again into recovery then flash gapps like you flashed the ROM.
For future ROMs only 8+ is needed, sometimes 8a and wiping data in 11 is not needed, this is usually for small updates of the same ROM (like cm night lies) however you can always try not to wipe data then if you have problems reboot into recovery and do the three wipes.
* if nothing turns yellow make sure you have drivers. You can install lies to get drivers(but make sure no lies process is running when you start odi ) or search for drivers and download them

The touch sensitivity is much better but still has its moments but that could be the ROM its self

flashing and broken screen

my phone slid out of my pocket and bottom half of screen cracked and wont respond to touch. i can use it annoyingly with forced 4-way auto rotate on using xposed/app settings for apps.
currently phone has euphoria os aka new mahdi no longer updated and i use kernel adiutor to flash zips since twrp doesnt have 4-way autorotate.
i feel its time to flash another rom or atleast have full control in twrp. is there a way to make twrp have 4-way autorotation? that will help greatly with recovery control and flashing files but i still have the obvious issue with flashing a new rom. im pretty sure that in most roms the initial setup doesnt allow 4-way autorotate. i was wondering if its possible to do a flashable scripted answer file type method similar to a windows slipstream install that can be flashed at the end of regular zip installs to allow rom to boot directly to home screen on first boot?