Hey guys,
I'm used to my Android phones (Eris, Incredible, Thunderbolt) and their ridiculously responsive touchscreens and using this tablet is really not responding well. The edges of the screen force me to push quite hard to get it to sense my touch and I find myself touching app icons twice sometimes three times in order to get them to register - but then in some areas (usually towards the middle) the screen is much more responsive...? Also (strangely) once the touch is registered - I can for example drag the icon around the home screen quite easily but the initial touch took awhile to register?? Hope that makes sense. I haven't seen anything about this so far so I was wondering if it's something to do with the ROM, something common, etc...please let me know if you have any input!
THANKS!
P.S. - FYI I'm quite happy with the device over all for it's price point. I went with Vegan Beta 5.1.1 and it's very "stock-ish" and I like that - also I'm quite confident my unit was brand new as there are no dead pixels or anything else wrong that I've noticed so far and the packaging had all the tell tale signs of a product being brand new. Woot does NOT mess around with shady stuff - very rarely will you find someone with bad things to say about them and I've never gotten a High end games that wouldn't run on my phones run great on it and there are no dead pixels or anything else wrong that I've noticed so far. Woot does NOT mess around with shady/refurb stuff unless they say it outright.
As for the touch screen again let me know how senstive yours is because it's the only thing that's got me a little bummed out.
There is a calibration fix app floating around. I think roebeet posted it. Search for touch screen calibration.
Try using a multitouch testing app from the market to get a true visual clue to how your touchscreen responds (there are a few, search for multitouch test). Run the calibration app and compare.
This Made my Screen much more Responsive!
There is a a tool to recalibrate the screen.... I have read that it is in TNT lite, and I am running Calkulin's ROM and it is in this as well (I don't know if Vegan has it or not... but you can check with a root explorer program).
First, the way to check (as best I know... still a newb) use a root explorer program, and look in system/bin... there should be a file in there called TSCalibration... I believe if this is there, then you have the tool you need...
From here, you need to create a file called Calibration.ini on the root of your SDcard (/sdcard). The easy way to do this is to connect the Gtab to a computer, and create it the INI file with your computer... put it on the root of the SDcard (internal memory)... oh, and yes... the ini file is blank, this is how it should be.
Now shutdown your Gtab, and restart it... let it sit for a minute or two after bootup, and DO NOT TOUCH THE SCREEN DURING BOOTUP...
That is it! From what I have read, the TSCalibration file looks for Calibration.ini on the SDcard... if it see's it, it re-calibrates the screen... after this is done, it's a good idea to delete the Calibration.ini file, otherwise it will re-calibrate on every bootup.
A couple of notes:
From what I have read, the Stock TSCalibration looks in /sdcard2 (external), instead of /sdcard... the hacked version in most ROMS fixed this...
I am one of the (many) wooter's that just got their G Tablet... I will say that right out of the box, the dock on the right side of the screen was a pain to get to work... I ran this calibration and now it works like a dream!! I was really surprised that even a brand new device needed to be re-calibrated.
If I screwed any of this up, please correct me! Thanks, and good luck!
cbmboy said:
There is a a tool to recalibrate the screen.... I have read that it is in TNT lite, and I am running Calkulin's ROM and it is in this as well (I don't know if Vegan has it or not... but you can check with a root explorer program).
First, the way to check (as best I know... still a newb) use a root explorer program, and look in system/bin... there should be a file in there called TSCalibration... I believe if this is there, then you have the tool you need...
From here, you need to create a file called Calibration.ini on the root of your SDcard (/sdcard). The easy way to do this is to connect the Gtab to a computer, and create it the INI file with your computer... put it on the root of the SDcard (internal memory)... oh, and yes... the ini file is blank, this is how it should be.
Now shutdown your Gtab, and restart it... let it sit for a minute or two after bootup, and DO NOT TOUCH THE SCREEN DURING BOOTUP...
That is it! From what I have read, the TSCalibration file looks for Calibration.ini on the SDcard... if it see's it, it re-calibrates the screen... after this is done, it's a good idea to delete the Calibration.ini file, otherwise it will re-calibrate on every bootup.
A couple of notes:
From what I have read, the Stock TSCalibration looks in /sdcard2 (external), instead of /sdcard... the hacked version in most ROMS fixed this...
I am one of the (many) wooter's that just got their G Tablet... I will say that right out of the box, the dock on the right side of the screen was a pain to get to work... I ran this calibration and now it works like a dream!! I was really surprised that even a brand new device needed to be re-calibrated.
If I screwed any of this up, please correct me! Thanks, and good luck!
Click to expand...
Click to collapse
THANK YOU SOOOO MUCH! This worked PERFECTLY! My tablet now responds perfectly acoss the entire screen. You just made my week!
Thank You! Thank You!
cbmboy said:
There is a a tool to recalibrate the screen.... I have read that it is in TNT lite, and I am running Calkulin's ROM and it is in this as well (I don't know if Vegan has it or not... but you can check with a root explorer program).
First, the way to check (as best I know... still a newb) use a root explorer program, and look in system/bin... there should be a file in there called TSCalibration... I believe if this is there, then you have the tool you need...
From here, you need to create a file called Calibration.ini on the root of your SDcard (/sdcard). The easy way to do this is to connect the Gtab to a computer, and create it the INI file with your computer... put it on the root of the SDcard (internal memory)... oh, and yes... the ini file is blank, this is how it should be.
Now shutdown your Gtab, and restart it... let it sit for a minute or two after bootup, and DO NOT TOUCH THE SCREEN DURING BOOTUP...
That is it! From what I have read, the TSCalibration file looks for Calibration.ini on the SDcard... if it see's it, it re-calibrates the screen... after this is done, it's a good idea to delete the Calibration.ini file, otherwise it will re-calibrate on every bootup.
A couple of notes:
From what I have read, the Stock TSCalibration looks in /sdcard2 (external), instead of /sdcard... the hacked version in most ROMS fixed this...
I am one of the (many) wooter's that just got their G Tablet... I will say that right out of the box, the dock on the right side of the screen was a pain to get to work... I ran this calibration and now it works like a dream!! I was really surprised that even a brand new device needed to be re-calibrated.
If I screwed any of this up, please correct me! Thanks, and good luck!
Click to expand...
Click to collapse
Thank You so much for this post. You have saved my G-Tab from going back on eBay where I got it brand new couple of days ago!!! WOW. This is quite the FIX. The G-Tab is now very responsive. Now, if I can find a fix for the dismal viewing angles. Ughh.
http://forum.xda-developers.com/showthread.php?t=934500
Here is a link to the app. Don't forget to take the calibration.ini out of the root. Some have reported perminent sensitivity problems caused by recalibrating constantly. The app lets you recalibrate with a touch and is simple and easy to use.
Related
I did one flash...to TNT version 4xx, and I loved it...but I'm finding I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything so I think my original files are history
I know there are lots of threads, and I tried to follow one about snagging a rom and moving it to the Root and all it does is re-install TNT I think I am "not getting something".
Can someone walk me through this....
The force closes can be fixed by re-partitioning your sd card. Part 1 Step 7 in this tutorial:
http://forum.xda-developers.com/showthread.php?t=865245
But partitioning will erase everything, and is usually done after installing cwm and before flashing a rom.
You really don't want to go back to stock, especially if it's only to gain stability. All the force closes will go away when the tablet is properly formatted.
If your looking to go back to stock, I like nvflash, but there are easier ways.
http://forum.xda-developers.com/showthread.php?t=861950
Force closing is a known issue that can be easily fixed by repartitioning your internal sd card to the right specs. It has nothing to do with your newly flashed rom.
What you need to do is back up all your data on the sdcard and then go into clockworkmod advance and repartition to 2048/0.
Added by edit.
To be honest, your original post tells me the gtab isn't for you. I say a mainstream device like the ipad is more for you. Here is why. In order to use the gtab, you need to do the following things.
(1) Install clockworkmod.
(2) Use clockworkmod to repartition to fix the force closing issue.
(3) Use clockworkmod to flash a new rom.
And you're done. The entire process takes about 10 minutes at most.
Again, steps 1-3 should take you 10 minutes at most and the device is ready for use. If you find yourself frustrated by one of these steps or that you're spending more than 20 minutes, then the gtab is not for you and you need to get a mainstream device.
goodintentions said:
Again, steps 1-3 should take you 10 minutes at most and the device is ready for use. If you find yourself frustrated by one of these steps or that you're spending more than 20 minutes, then the gtab is not for you and you need to get a mainstream device.
Click to expand...
Click to collapse
This recommendation is of course assuming you have no determination whatsoever, and are incapable of learning anything new.
brettdwagner said:
This recommendation is of course assuming you have no determination whatsoever, and are incapable of learning anything new.
Click to expand...
Click to collapse
Look, for most people this device is a toy. I use it at work, and I suspect most people don't do this. Let's admit it. Modding a device isn't for everybody.
I went into modding the gtab as a total android newbie. And yet it took me all of 15 minutes to figure out how to install clockworkmod, repartition, and flash a custom rom. Then a week after I flashed a custom kernel.
You just can't ask everybody to go through the headache of modding a device if they have neither the will nor the time.
I said 15 minutes because that was my first time ever modding an android device. After that first time, it took me about 5 minutes to do my second device.
It's a simple process to go through. If a person gets stuck on any of those 3 steps, then I think it's best that they get a mainstream device. The gtab just isn't for everybody.
HeadRusch1,
I think you can handle modding the gTab. If you understand how a file system works, can extract a zip, and have already flashed a custom ROM then your about 90% of the way to a smooth running gTab. As mentioned above, you simply missed one step.
I understand the "10 minutes or forget it" argument, however I think it's wildly inaccurate when gauging a new user's potential competency with the gTab. If you find yourself frustrated then go read some more, search for a solution, or ask a question. It should take a long time to get comfortable modifying Android devices, there are tons of loosely documented best practices, but don't bail early because it's hard.
PS.
This assumes your looking for a device to tinker with. Goodintentions is right for users who are looking for iPad equivalent. I just assume that users looking for a cheap iPad rarely make it as far as XDA. And if they have, then it's a good opportunity to encourage further exploration.
The reason I gave the 20 minutes advice is because I've seen too many people buying the gtab thinking they got an ipad. The gtab isn't mainstream at all even though it's outsold a lot of the mainstream devices out there (ahem xoom) by several orders of magnitude. Customer support for the gtab is almost non-existent. And don't hold your breath for updates from viewsonic.
I absolutely love my gtab. I am currently running vegan ginger OC to 1.2ghz. The speed on my gtab is absolutely stunning. There's no jerking at all. My touchscreen is incredibly sensitive. Viewing angle has never bothered me. I love the full size usb where I can just put a memory stick in there just like my laptop. The autocad app is extremely helpful for me. In fact, it's been a whole week since I turned on my laptop.
That said, again, this device is not mainstream. Meaning it's not for most people. I am absolutely convinced that most people would be better off with something like the ipad or transformer.
Based on my experience, there are two types of people in the world of gadgets. (1) Those who sees a problem and see the end of the world and (2) those who sees a problem and try to get around it.
An example of #1 is my friend Sarah. She wanted to use my gtab to get a feel for it. She said the touchscreen bothered her and that she was more comfortable with a laptop touchpad more. And then she said "I don't know, I think I'll be better off with an ipad." LOL. Boy is she going to be so surprised to find out the ipad also uses the touchscreen rather than an touchpad.
Anyway, another example is one of my colleagues. After I told him the autocad app doesn't work with 3-D view yet, he acted like it was the end of the world. Me, I just use the side, top, and front views in my demos. Works just fine for me.
Anyway, I'm rambling now. The point is my experiences tell me most people are better off with something like an ipad or transformer. Since those devices are mainstream, people can't say "of course you can't do this, you can't do that". With the gtab, since it is not mainstream, the smallest inconvenience means the end of the world.
HeadRusch1 said:
I did one flash...to TNT version 4xx, and I loved it...but I'm finding I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything so I think my original files are history
I know there are lots of threads, and I tried to follow one about snagging a rom and moving it to the Root and all it does is re-install TNT I think I am "not getting something".
Can someone walk me through this....
Click to expand...
Click to collapse
Plug the gtablet into the computer.
Mount it for file transfer when prompted.
Check for an "update.zip" file at the root of the SD card (That's the tablet's 16gb internal memory). Delete it using your computer. That was causing TNT to be reloaded.
Here's the link to the original 3588 version they shipped with: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip Save it to your computer. Rename it "update.zip". Copy it to the root of the gtablet SD. Shut off the tablet. Unplug the USB cord. Restart with power & vol +
It should update.
If anyone notices a mistake, feel free to correct me. I've only flashed from stock 3588 to Vegan Ginger. So a whole 1x.
For what its worth, I tinkered and now I'm good.
Got NVFLASH working, went back to stock. Then went to Clockwork, then went to Vegan 5.1.1, then to CM7, now back to Vegan. I've found some apps that work and I'm liking it more. For the record, I own an Ipad2 as well.
Now, to those who chose to comment: You guys need to understand that many of those links are drowning in "extra information", and that is fine if you don't mind clicking hyperlink to hyperlink to do some trial and error, but now with multiple install path choices and whatnot, it gets confusing and it also means you have some time. I asked for someone, possibly someone in my shoes who has been down the path, to walk me through the steps.
Some of you did, some of you projected some assumptions with the underlying message of "RTFM".
This, too, was my first dip into the Android pool. Thanks for the help.
HeadRusch1 said:
I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything...
Click to expand...
Click to collapse
I had that issue and didn't have clockwork.
Solution:
1: install clockwork
2: boot into clockwork, and select 'fix permissions'.
3: reboot, tablet fixed
I have been noticing that ever since I got my refurbished fascinate (to fix 3g issues) every time I get a call I get a phone app poke lock. The exact line from the dumpsys Power is
poke lock 'PhoneApp': POKE_LOCK_IGNORE_CHEEK_EVENTS
And that's as far as my knowledge takes me. the only way I know to clear it is to reboot and that sucks to do after every call. Can anybody help me?
Thats actually a setting In your phone to ensure the phone doesn't lock as your in call....apparently someone who owned it before you set it, and your carrier got to lazy to update full settings.....
Ill find info on fix, however sure fire way to fix, is flash a new kernel or simply go to Settings+ Factory data reset.....
Be advised obviously this will wipe your entire phone to scratch....backup your contacts, and as a final disclaimer this is about 90% to work...
Best of luck!!
Sent from my SCH-I500 using XDA App
This problem plagues me from com rom to cm7, otb to pbj. When I forget to reboot, it eats my battery alive, not to mention driving me nuts
Sent from my SCH-I500 using XDA Premium App
Maybe
Well i think i found you solution, ive NEVER dealt with this issue so im not 100% sure but i am a web developer and a professional coder, so it does seem like a great place to start,
You will need Root explorer and head on over and find the file
libs/ui/Input Dispatcher.cpp
from there the simplest way i would think is to move this file onto your computer, and edit the coding as the link below (and where i got this information) describes.
http://gitorious.org/rowboat/frameworks-base/commit/a87ea46/diffs
To open and edit the CPP file it varies on what system your computer runs.....
Mac:
http://www.codeblocks.org/
http://www.freescale.com/webapp/sps/site/homepage.jsp?code=CW_HOME
PC:
http://www.codeblocks.org/
http://www.editplus.com/
Linux:
http://www.eclipse.org/downloads/moreinfo/c.php
Now, i am a bit tired, so if i have read this alllll backwards and that actually tell you how to get to the problem you ALREADY have lol then, im at a lost! I'll look more and more into this for you and hopefully get you more and more detail till its fixed!
Now I know I'm up pretty early for a Saturday, but I can't for the life of me find
/libs/ui/inputdispatcher.cpp
with root explorer searching or just exploring around. I have a couple folders named "lib" (one in the root directory, one in /system, plus app files), but for the life of me I cannot find a ui subfolder. Anyody? Am I blind or do I just need some more sleep?
I get this same poke lock so I am interested to see if this is something that shouldn't be happening.
Sent from my SCH-I500 using XDA App
Ok
Mk sorry ive took so long to come back around, i keep mighty busy with my 5 month old, gimme a few more minutes to quest my phone and find it, then ill give both of yall my best and final answer lol
EDIT-
OOOOOk Melon, your first post you told me what dumpsys power is telling you poke lock 'PhoneApp': POKE_LOCK_IGNORE_CHEEK_EVENTS
HOWEVER if you look RIGHT above it, you will see "mPokeLocks.size=1:" Now we need to get that 1 to a 0, however i havent found a positive fix to this, alteast i now know why your situation is occuring, please be patient im trying to see how to edit that file to "0"
EDIT EDIT-
And again, i just spent an hour looking into this deeper and deeper, and this is allll i can tell you
1. Its a glitch in gingerbread
2. What i said in the first edit stands true, you must get that "1" to a "0"
3. I've got into everything from busybox, down to the files its self, yes i've found the appropriate files, but not sure how to edit them
4. Im running a Full EC09 2.3.3 i know you said you have flashed and went from every ROM however i can't seem to see why flashing through an outside source (not on your phone) like using Odin and taking the file found here http://www.mydroidworld.com/forums/fascinate/8081-gingerbread-fascinate-release-thread.html (mine) will not erase and clear that setting with a new system update.
5. Im really about to lose my mind at how deep this rabbit hole is going for this (what seems to be) a simple fix!!!
Final thoughts, even if you have done it 500 times, go get Odin, download the kernel from the link about and click start! (after putting your phone in download mode obviously lol) and if that just doesnt do it, i really have no other clue!!!!
I'm not against trying this, but I'm currently running com rom 2.1 and still having the issue. Would flashing this ruin any frameworks? Also, I don't know if I care to jump to EC09 and all of it's sd frying badassery
Sent from my SCH-I500 using XDA Premium App
Agreed on frying the sd, it did mine! but i back up my stuff, as far as mixing signals and messing with the frameworks, i'd really advise NOT to flash it as i have no clue on that and i wouldnt want to completely render your phone useless!
phew, i mean theres your flip of a coin, i've read atleast 5 other forums of people having the same issue and the best result is to do a killall -9 com.android.phone, but that only fixes until the next call comes in.....
So keep working with it, and hope theres a fix soon....or flash EC09 back up your data and hope for the best, either way here its kinda a lose.
But the best thing i can still guarantee if YOU know any other way, is that in that dumpsys file that says the number 1 if you can get that to 0 somehow, someway, and replace it in phone i'll put 50$ says that will without a doubt fix your problem, but locating that, and changing that in-leis the problem its self!!
Sorry i couldnt do more for you
Best of Luck
I have been looking for a Boot Animation of the UT Vols to go with the Splash Screen that i have on my New Thunderbolt. I cannot find one anywhere. Is there a way to make one using a file like this? http://www.youtube.com/watch?v=PZFXfWh7bes Can someone help me out here?
I don't know how to do it, but I think it can be done. You might ask bobz1993 how he did the "Lightning Vortex". I would like to know how this turns out, because I am a big UT fan too.
Thanks. Go Vols. I'll let you know if I can get it made.
I've been busy with school, but luckily Wednesday is my free day. I can easily convert this to be a boot animation, but the size of the video could make a correct full screen a little complicated. should I crop the sides or crush it to fit? I'll get it done tomorrow.
Thanks so much. Just use your judgement as to what you think looks best. I know the clip is way longer that my phone runs a bootanimation so again what ever is best. The Vols are in good hands.
Coincidentally my phone just broke... so i won't be able to test it first... Lost the display on the phone but still usable if I aim correctly... Will be calling verizon tonight for another refurb...
Do you just want the video or should i add a tbolt logo at the end or something? My phone honestly could play thru that entire video and then some before starting...
Sorry to hear about your phone. That sux. If you were to add anything at the end maybe the big. T. Like is on the playing field. Or just the clip I'm just excited to see it and try it out on my phone. Nice
Sorry I didn't get to it yesterday.. Was really busy with school... My refurb already came in today and I'm currently making the vid into an animation.
I'm working to get root back on the new phone now, but it came with new firmware this time and apparently there's a different process... If someone could record the steps to make a clockwork backup from bootloader (not booting straight into recovery) so I can have my phone back the way it was, I'd really appreciate it.
Ok I understand. When you get everything on your end working and have the time from your busy schedule. I hope you can post it here for me to download. Go Vols
UT Vols BootAnimation
Ok, i finally sat down today and with alot of research on google and reading thru alot of forum here on XDA i finally decided to try and make my first BootAnimation to go with the Splash Screen i found of UT Vols. I would like to Thank Bobz1993 for letting me know that this was possible and everyone else who posts. Anyway i know this is not perfect and has no sound. but tell me what you think guys. Go Vols.
Did you make this a Flashable zip? When I tried to install from CWR, it said that installation was aborted. Thanks for your effort.
I just use root explorer just go to the folder where your bootanimation.zip is stored.I think this varies depending on Rom installed. On mine it's in the system /media folder. There You will find your current bootanimation.zip there I just renamed it. Usually I put. 1 on the end of zip. Then just copy and past this new one there and reboot. Let me know how it turns out.
It works. It looks good but it runs too fast. If it can be slowed down a little, it would be perfect.
UT Vols BootAnimation
I think you are right it does run fast. i have tried 2 other speeds the lowest one is way to sluggest and the other well its on the borderline too. I think maybe because the clip i used to make this is all cut up with so many different scenes, with the program used to make it only uses 1 of every 10 shots. that makes it even more choppy. thanks for the honest review i will try to find another clip with 1 continious fluid shot of some hard hitting action maybe then it will be more fluid when slowed down to a good speed. i will upload the other speed though the slower one incase anyone wants that one.
I did make it a little while ago, but AfterFX is messing up the frame order on me... It is at right speed with sound, but it jumps so looks like ****.
And its over 42MB atm... I may clip some parts out to lower the size and just put it up...
All, I've gone through many of the forums here and all I am now is confused. Issue: Had CWM and NVFLASH on and Honeycomb on gtab. Some issues, wanted to go back to stock. Followed instructions; however, now it's in a loop. I cannot get to it via PC. Holding power and volume key, see the 3 birds and "recovery key detected, goes to gtablet screen, goes to screen with a box (arrow in it pointing down) and status bar across bottom, goes to w/tap n tap screen, goes to screen with tnt; then reboots through the process again and again. I've spent the past two weeks going through the internet and reading the various methods to unbrick, none work; because I can't get to the internal SD card.
Is there a way to fix this? Is there a way to use the external micro-SD card? Or do I just need to throw this thing away? Any assistance would be appreciated. Oh, I've tried the Code Red and every other unbricking method I came across.
Thank you in advance, Michael
[email protected]
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
nobe1976 said:
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
Click to expand...
Click to collapse
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
There is a way to "install clockwork from external SD" - search that phrase and you should find it.
BTW- If you plan on trashing it, I'll pay for shipping to my house. I'll 'throw it away' for you
new_to-droid said:
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
Click to expand...
Click to collapse
Well all and all I know your fustration. The first link I beleive you are using is the Stock 1.1 from the 3588 branch. That one I used before and had nothing but issues. The best one to use is from the 4349 branch perfered with CWM pre-installed. After flashing that file shut the Tablet off during boot up. Then boot into recovery mode by holding down the volume + while pressing the power button. Do a Wipe Data Factory reset, Clear Cache, and then under advance Wipe Dalvic Cache then go back to main menu of CWM and reboot device. Make sure you don't select reboot recovery since that will not let you boot into anything but CWM. TNT TabUI will then boot up and you chould be good to go.
Thanks...but
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
$$Price?
Sent from my Droid using XDA
new_to-droid said:
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
Click to expand...
Click to collapse
Sorry to see that your experience with your newly found failure did not come with a price of knowledge. Truth be sayed I am no programmer, geek or knowledge of script writing either, but what I can pass along to all new-to-android persons is that your best path is to read and follow instructions to the T or you will end up with a expensive paper wait. The web link I posted above is pretty self explained and I give that man credit because I was a newbie too once. Then somewhere in these forums I found that website and was able to recover from just about anything that happened to my poor Gtab. Hell, I even had to drill a hole in the back of the case just because I wanted more and there was ICS from Team DRH. But truth be said that web link is your path and only path to going back to the stock UI and recovery.
Price
50 plus shipping to us only
new_to-droid said:
50 plus shipping to us only
Click to expand...
Click to collapse
I'll buy it. DIBS EVERYONE!
PM me with your info and I'll have the money sent right away.
Even if I couldn't get it to work, I could use it for parts for my current g-tab.
EDIT: Don't mind my post count. I'm very active on SD, just not here.
Just wanted to mention that I have not been PM'd or replied to. Hope this guy got his tab to work.
I have a Droid Razr that had a small accident that left the lcd screen shattered, but the Gorrilla glass intact. I now use this phone with my Lapdock and it works perfectly. My problem is that I have been trying to find a way to upgrade the phone to JB with the leaked version that got released on Christmas Eve.
The screen doesn't not work at all. The soft buttons work fine and so do the external buttons. Both ports work as well. The screen does not light up nor does it accept any input. The lapdock will start up as soon as the phone gets completely booted.
My question is there a way to upgrade the phone from ICS to JB without using the recovery menu. I can't navigate the recovery menu, so I can't install the zip file. If I had the two original files that came from the cache system folder, I could just reboot the phone and it would upgrade, right? If that is the case, does anyone have those original files that I could download?
I would love to upgrade this phone now instead of waiting for the OTA. Newer is always better.
By the way the phone got slammed in the house door and the frame is bent, so there is no fixing the phone at this point. The only use is to use it as a permanent dock on my lapdock 500.
Thanks to anyone that helps me or for even reading this post!
Do you suspect that you are able to select the options however can't see what you're doing? in that case I would search a video tutorial for a generic similar installation and simply follow the same steps using their screen as your guide.
joemas said:
Do you suspect that you are able to select the options however can't see what you're doing? in that case I would search a video tutorial for a generic similar installation and simply follow the same steps using their screen as your guide.
Click to expand...
Click to collapse
I thought of that and tried it without success. I don't know how far through the process I get, cause I can't see the screen, but I suspect it might be when I am trying to get from the Android to the recovery menu. I really don't know if I get to it on the first try or not. It is such a crap shoot. You just don't know if you make a mistake or not. very frustrating. Thanks for the reply.