Guest dibbles Posted August 24, 2011 Report Share Posted August 24, 2011 (copied my post over from tabletroms) A point for the Dev team... For some reason my screen started to become less and less responsive, this is using build 7 installed on ver 2 of the modified 1.10 ROM. I was not sure why this started to happen but I was getting more "dead" spots on the screen making it very very difficult to do much. (it started at the same time as I was having difficulty downloading anything from the market as it came up with a problem authorising purchase message, even when the apps were free) Managing to get the Vega into recovery mode I decided to wipe everything and install build 7 again, the results were the same. I wiped again and then restored my modified 1.10 ROM. That went well but the screen was still not responding too good. It took me ages just to get the screen lock to unlock. When I did unlock it I then managed to get back into recovery and install VC 1.7. As it was booting the first time I held the back button down to invoke the USB host mode whilst I had a mouse attached. The mouse enabled me to navigate easily to the Screen Calibration utility. This I ran. The screen was then absolutely perfect. I then got the tablet back to the build 7 ROM and it is now great. So a question... Is the screencalibration apk, which I can take from the VC 1.7 ROM, compatible with this build 7 (I think not though)...? If it is then I will install it, as it would be simpler that way to use it. Also have you thought of including it with the ROM..? Once the USB host mode problems have been resolved it would be easier to use the utility for those who have a totally dead screen. As it was I could have just about managed, I think, without using a mouse. Prior to me thinking about the screen calibration utility I had noticed another user who was returning their Vega due to his screen becoming unresponsive. If I had thought at the time I could have suggested the above to try but at least it has been a working option for me and might be useful for others in such a situation. If I, or any other user, is in a similar situation it does get a little convoluted with having to flash ROM's etc, made more difficult without USB host or ADB (AFAIK), to get to the utility within VC 1.7 when it would be useful to have a compatible one built in, if it was possible. Thanks Link to comment Share on other sites More sharing options...
Guest premieral Posted August 24, 2011 Report Share Posted August 24, 2011 Is the screencalibration apk, which I can take from the VC 1.7 ROM, compatible with this build 7 ( I downloaded the screen calibration apk from this forum and ran it yesterday as my screen was a little less responsive than i liked in certain areas, it ran fine and is now working beautifully again. Link to comment Share on other sites More sharing options...
Guest dibbles Posted August 24, 2011 Report Share Posted August 24, 2011 I downloaded the screen calibration apk from this forum and ran it yesterday as my screen was a little less responsive than i liked in certain areas, it ran fine and is now working beautifully again. Is this the one that you used with build 7...? ...link in the first post of the above thread. Link to comment Share on other sites More sharing options...
Guest premieral Posted August 24, 2011 Report Share Posted August 24, 2011 yes thats the one it installs as module AP and will give an unable to find IT7260 device but i ok`d that and ran recalibration as before and all is good, but be aware i have not had any problems with this rom that others have found and i have mine loaded over modded stock v1 so i cant guarantee you will get the same result. hope it works for you tho Link to comment Share on other sites More sharing options...
Guest ejtagle Posted August 24, 2011 Report Share Posted August 24, 2011 yes thats the one it installs as module AP and will give an unable to find IT7260 device but i ok`d that and ran recalibration as before and all is good, but be aware i have not had any problems with this rom that others have found and i have mine loaded over modded stock v1 so i cant guarantee you will get the same result. hope it works for you tho The old calibration app does not work for the new vegacomb 3.2... It does absolutely nothing... I know, because i wrote the new touchscreen driver that VC3.2 is using. But, the screen selfcalibrates everytime the tablet is turned on from a total shutdown. So, make sure you are not touching the screen while the tablet boots... And, it is not a bad idea to wipe the screen with a soft cloth from time to time... Link to comment Share on other sites More sharing options...
Guest dibbles Posted August 24, 2011 Report Share Posted August 24, 2011 The old calibration app does not work for the new vegacomb 3.2... It does absolutely nothing... I know, because i wrote the new touchscreen driver that VC3.2 is using. But, the screen selfcalibrates everytime the tablet is turned on from a total shutdown. So, make sure you are not touching the screen while the tablet boots... And, it is not a bad idea to wipe the screen with a soft cloth from time to time... Great to read and most useful knowing that the screen will recalibrate from a total shutdown :) Thanks for posting that. Link to comment Share on other sites More sharing options...
Guest premieral Posted August 24, 2011 Report Share Posted August 24, 2011 The old calibration app does not work for the new vegacomb 3.2... It does absolutely nothing... I know, because i wrote the new touchscreen driver that VC3.2 is using. But, the screen selfcalibrates everytime the tablet is turned on from a total shutdown. So, make sure you are not touching the screen while the tablet boots... And, it is not a bad idea to wipe the screen with a soft cloth from time to time... now you tell us :lol: Link to comment Share on other sites More sharing options...
Guest dibbles Posted August 24, 2011 Report Share Posted August 24, 2011 Just a point though. If the ROM will self calibrate each time it cold boots I'm not sure what went wrong with mine. The only way that I could resolve it was to run the Screen Calibration tool when I installed VC 1.7. Link to comment Share on other sites More sharing options...
Guest Zarjaz Posted September 10, 2011 Report Share Posted September 10, 2011 The old calibration app does not work for the new vegacomb 3.2... It does absolutely nothing... I know, because i wrote the new touchscreen driver that VC3.2 is using. But, the screen selfcalibrates everytime the tablet is turned on from a total shutdown. So, make sure you are not touching the screen while the tablet boots... And, it is not a bad idea to wipe the screen with a soft cloth from time to time... If the screen recalibrates on startup, why am I having so many issues with screen response (i.e., lack of response!) with 8.1? I have had to revert to Corvus 5 because of this...and have no screen issues with this ROM. I know that I am not the only one with screen responsiveness issues running Vegacomb, as I've come across many complaints about the same issue. And yet there doesn't seem to be any explanation, and perhaps no work underway to resolve. In the meantime, a proper screen recalibration app would be useful.... Link to comment Share on other sites More sharing options...
Guest Oldbarzo Posted September 10, 2011 Report Share Posted September 10, 2011 If the screen recalibrates on startup, why am I having so many issues with screen response (i.e., lack of response!) with 8.1? I have had to revert to Corvus 5 because of this...and have no screen issues with this ROM. I know that I am not the only one with screen responsiveness issues running Vegacomb, as I've come across many complaints about the same issue. And yet there doesn't seem to be any explanation, and perhaps no work underway to resolve. In the meantime, a proper screen recalibration app would be useful.... Hi Don't understand why so many people are having screen problems with VC 3.2 Bld 8.1. I have been running this rom from the first day it was available from Tabletroms site and have had no major issues other than the BT/WiFi issue, which I could cure with the Bld 7 patch if I was inclined. But I don,t use BT so no need. I have no calibration issues, no freezes or boot looping, the rom just runs perfectly for me. Obviously there must be major differences in the support chips and nand memory in the Vegas that have been sold for the discrepencies we are encountering in, not only VC, but other Roms for this tablet. Stransky Link to comment Share on other sites More sharing options...
Guest 4L0M Posted September 11, 2011 Report Share Posted September 11, 2011 (edited) Hello Everybody. I bought a Vega yesterday and installed VegaComb 3.2 (8.1) and happily used the tablet for a few hours, it was a fantastic rom, then i started having exactly the same problem as the original poster. The screen was unresponsive to the point of not being able to even use the unlock screen. If i rebooted then 1 out of 3 times i could unlock the tablet with uber massive lag. click a few icons but within a minute or two, the screen is impossible to use. I managed to install the screen calibration app, but got the same error message as the OP. device is not supported or whatever message. i ran the calibration tool anyway, but it didn't make a difference. The Vega was unusable. In the end i had to flash modded Stock V2 on it, the screen was still megalaggy until i then used the calibration tool. The calibration tool recognized the device this time, and worked like a charm. As i only bought the vega yesterday, i'm a n00b as to whether there is a compatible screen calibration i can use with the vegacomb rom? Can the calibration tool be ported to it? Any help would be greatly appreciated, as i thought the vegacomb was fantastic. I'm currently using corvus 5.1 which is another great rom, but i would rather use vegacomb as the UI is gorgeous. I read that vegacomb calibrates the screen every time it starts up, but this definitely does not work on my tablet. ( I made sure the screen was never touched when it booted). As a side note which may or may not have anything to do with this problem, it only started after trying some games, some of which must have been older games as they did not render in full screen on the tablet, i wonder if this could be a possibe cause to the screen calibration dying? Cheers guys. Edited September 11, 2011 by 4L0M Link to comment Share on other sites More sharing options...
Guest Zarjaz Posted September 11, 2011 Report Share Posted September 11, 2011 Hello Everybody. I bought a Vega yesterday and installed VegaComb 3.2 (8.1) and happily used the tablet for a few hours, it was a fantastic rom, then i started having exactly the same problem as the original poster. The screen was unresponsive to the point of not being able to even use the unlock screen. If i rebooted then 1 out of 3 times i could unlock the tablet with uber massive lag. click a few icons but within a minute or two, the screen is impossible to use. I managed to install the screen calibration app, but got the same error message as the OP. device is not supported or whatever message. i ran the calibration tool anyway, but it didn't make a difference. The Vega was unusable. In the end i had to flash modded Stock V2 on it, the screen was still megalaggy until i then used the calibration tool. The calibration tool recognized the device this time, and worked like a charm. As i only bought the vega yesterday, i'm a n00b as to whether there is a compatible screen calibration i can use with the vegacomb rom? Can the calibration tool be ported to it? Any help would be greatly appreciated, as i thought the vegacomb was fantastic. I'm currently using corvus 5.1 which is another great rom, but i would rather use vegacomb as the UI is gorgeous. I read that vegacomb calibrates the screen every time it starts up, but this definitely does not work on my tablet. ( I made sure the screen was never touched when it booted). As a side note which may or may not have anything to do with this problem, it only started after trying some games, some of which must have been older games as they did not render in full screen on the tablet, i wonder if this could be a possibe cause to the screen calibration dying? Cheers guys. Exactly my experience...but yet we are told that it does a screen recalibrate every time it cold boots. If it did actually do this, then we wouldn't see these problems would we.... I'be had my Vega since April, and tried a load of ROMs. I really like Vegacomb, but if the screen plays up when I am away from home - like it did when I was in Austria last week - I can't flash the modded stock until I get home...unless I take my laptop, which sort of defeats the point of just taking my tablet! I guess I have to stick with Corvus. Link to comment Share on other sites More sharing options...
Guest N3ls0n Posted September 11, 2011 Report Share Posted September 11, 2011 I love this rom VC(8.1), but I'm having real trouble with the top centimeter of the screen. It is completely unresponsive, almost impossible to close browser tabs or use search facility in the market. Everywhere else the screen is perfect. I have tried the calibration app but it had no effect. Recently I went back to stock 1.10 and then Pauls R8 and the screen was perfect. So, decided to try VC (8.1) again with modded v2... you guessed it, top of the screen unresponsive. Newbe5 and the guys have done an amazing job with this and I'm sticking with it, as much as this is an annoyance, the pros outweight the cons. If anyone has found a solution... please share Nelson Link to comment Share on other sites More sharing options...
Guest CoWPlagued Posted September 11, 2011 Report Share Posted September 11, 2011 People need to be more respectfull. Ejtagl wrote the driver so he knows what it does and for the majority of us it works perfectly. In some cases there maybe other factors (such as the bad sector issue) corrupting data or other hardware faults. If people believe they have found a bug in the driver or have located another issue, provide evidence and help it get resolved. Regarding the unresponsive top of screen. It's not the screen that's the issue at all, download any number of multi touch apps and you can see the screen registering the touches perfectly. Also changing the dpi can resolve the issue at the expense of others. It's on the list of things to look at. Try clicking the bottom line of things rather than in them and this can help for now. Link to comment Share on other sites More sharing options...
Guest Kerbside Posted September 16, 2011 Report Share Posted September 16, 2011 I love this rom VC(8.1), but I'm having real trouble with the top centimeter of the screen. It is completely unresponsive, almost impossible to close browser tabs or use search facility in the market. Everywhere else the screen is perfect. I also have the issue where the top part of the screen is unresponsive. However, I suspect the issue is in some software layer above the driver. This is based purely on the observation that for me, the issue only really happens in applications that place user interface controls near the top centre of the screen (e.g. browser tabs, or the market search box). This seems to be backed up by the following test: * Open multiple tabs in the browser and reproduce the lack of sensitivity issue (i.e. can't switch tabs). * Go to the browser settings and on the Labs tab, check the Quick Controls option (this causes the tab bar in the browser to disappear). * Exit settings and return to the main browser page. * Scroll a link on the page to the top middle of the screen where the browser bar would normally be. * Touch the link. It is selected without any sensitivity issue (even though the link is in the same location as the problem tabs were). Andy Link to comment Share on other sites More sharing options...
Guest ejtagle Posted September 16, 2011 Report Share Posted September 16, 2011 I also have the issue where the top part of the screen is unresponsive. However, I suspect the issue is in some software layer above the driver. This is based purely on the observation that for me, the issue only really happens in applications that place user interface controls near the top centre of the screen (e.g. browser tabs, or the market search box). This seems to be backed up by the following test: * Open multiple tabs in the browser and reproduce the lack of sensitivity issue (i.e. can't switch tabs). * Go to the browser settings and on the Labs tab, check the Quick Controls option (this causes the tab bar in the browser to disappear). * Exit settings and return to the main browser page. * Scroll a link on the page to the top middle of the screen where the browser bar would normally be. * Touch the link. It is selected without any sensitivity issue (even though the link is in the same location as the problem tabs were). Andy I also think it could be a sw layer above the driver itself. Specially, if the multitouchscreen apps show that there is no unresponsive touchscreen points... Perhaps, the changed dpi settings ? --- Link to comment Share on other sites More sharing options...
Guest thwacker Posted September 16, 2011 Report Share Posted September 16, 2011 It might be worth trying to change your DPI settings. I saw this in an earlier Vegacomb 3.2 build 5 thread: Bunjit, on 18 August 2011 - 01:16 PM, said: This way is easier to change DPI settings and allows you to change as much as you like on the fly without re-flashing: It's very easy, and fast enough to test until your hearts content: 1. Download ES File Explorer from the market (free!) 2. Open ES, go to /settings - Check Root Explorer, Check Mount file system options 3. Navigate to home/System in ES 4. Select build.prop and openin ES note Editor (if you just get darkened screen, tilt device and menu will appear) 5. Scroll down and change the density line to suit: ro.sf.lcd_density={120} 6. Save 7. Reboot Try a setting of 127 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now