We finally got our hands on a Inc device (a big thank you to Ruggar for loaning us the device to dev on) and lo and behold, we are unable to touch the green droid in setup wizard (this is a recently reported issue among quite a few users).
We were unable to replicate this issue before, but have finally found the problem with our loaned test device.
The kernel we use puts us in a bootloop right after installing the Rom. This issue is still being tested and a solution will be in the works.
Using other kernels (like King's) let us boot up the device, but sadly we were unable to get feedback when touching the screen. Turns out the loaned device is an SLCD screen, not AMOLED. These kernels do not contain SLCD drivers, thus you cannot touch the screen.
So, if you have an Inc with an SLCD screen, you cannot currently run ShadowRom. All Inc's with the AMOLED screen can run it perfectly fine.
Rest assured this is a major issue, and we are working on a fix asap. We'll keep you posted.
I had no idea the dincs were so different just because of the screen
thy require a whole new set of touchscreen drivers. we ran into this issue on the eris with the MELFAS and SYN touchpanel. its a huge pain in the ass
I'm using an incredible and i was having the same problem until I installed it without a theme in rom manager
Sent from my ADR6300 using XDA App
That explains all my issues...thanks shadow rom!
Sent from my Incredible using XDA App
haha people can actually use shadowrom to test if they got a slcd or amoled.
Ianxcom said:
I had no idea the dincs were so different just because of the screen
Click to expand...
Click to collapse
The software and hardware need to communicate properly so a different screen without drivers is useless.
i used shadow rom v1 wout problems, when trying v2 is when the touchscreen issues occured.
I have an AMOLED screen, ShadowROM works fine, until I try to flash ShadowROM with a theme...
If you flash the theme after shadowrom has its first boot then it will work
Sent from my ADR6300 using XDA App
Thanks facepunch!
Is this the main shadowrom thread? I thought there would be more, I love shadowrom with the Luna theme, been using for several weeks, will Luna work on other aosp roms too?
Sent from my ADR6300 using XDA App
hfulbri1 said:
Is this the main shadowrom thread? I thought there would be more, I love shadowrom with the Luna theme, been using for several weeks, will Luna work on other aosp roms too?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
This isnt the main thread. I'll post up a main thread as soon as our next revision is released tho
Will the next revision have the fix for slcd screens?
Is there an easy way to find out what type of screen you have?
The easiest way is to look at the SKU on your box. If it ends with W2 then you have an AMOLED screen, if it ends with W3 then you have an SLCD screen.
Other ways I've heard (but cannot verify) if the SLCD screen has little "dots" 1/4 inch apart on it that you can see when the screen is off, at a certain angle in certain lighting.
Another for sure way is to make a nandroid backup, and try to flash ShadowRom.
I have a slcd screen and used koush test 2 kernal...which got shadowrom to work. Just flashed in recovery after rom install.
SamuraiXDroid
samuraixzodus said:
I have a slcd screen and used koush test 2 kernal...which got shadowrom to work. Just flashed in recovery after rom install.
SamuraiXDroid
Click to expand...
Click to collapse
We've been playing with that kernel for a week now, and we're pretty sure we will be including it into our next release.
What do you think the issue was?
SamuraiXDroid
samuraixzodus said:
What do you think the issue was?
SamuraiXDroid
Click to expand...
Click to collapse
Drivers.
Sent from my ADR6300 using XDA App
Related
Hey guys,
Just to let you know there is an application out there now to take care of force recalibration of the screen.
When I first got my nook I know it didn't register touch properly, so I ran some commands and it started working fine.
Decided I should make my first app something that helps people, so here you go. Checkout "nook screen recalibrate". It's a simple minimalistic application the re calibrates then reboots
Updated Version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Here's the market link.
Helpful since you don't have enough posts to post links yet. But thanks for this app!
Ironically when I go to the link and try to push it to my NC, it says it's not compatible. :X
Fine print mentions that is only works with GB (android 2.3 and above).
yep.. i dont think any rom uses anything lower than that
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
assid2 said:
yep.. i dont think any rom uses anything lower than that
Click to expand...
Click to collapse
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
Not sure what exactly that application does.so can't comment.
Sent from my Nexus One
byronczimmer said:
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
Click to expand...
Click to collapse
I think it should work. I shall reduce the requirements.
However there is no way to check cause my touch is working perfect now
However I find it performs better slightly if I do this once a week
Sent from my Nexus One
Updated release v2.0
Updated to version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Force closes on nookie 2.2
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Strange, I had reduced the minimum requirements
I have no other froyo device to test on, let me check once again against an emulator
Sent from my Nexus One
Ok maybe this is in my head, but if I run this every couple nightlies, touch feels slightly better and responsive.
Maybe it's the nightly, maybe the way it interacts, maybe the screen de sensitises over time, maybe it's all in my head
If anyone cares to do some testing, that would be great
Sent from my Nexus One
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Let me know if you wanna try this so I can publish to the market
Sent from my NookColor using Tapatalk
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Try cleaning your screen prior to running the application, make sure you don't touch the screen prior to restarting
Sent from my Nexus One using Tapatalk
kruuth said:
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Click to expand...
Click to collapse
same thing on my end. I ended up reflashing the latest cm7 nightly and its back to the way it was
Sent from my NookColor using Tapatalk
That's extremely strange. First time I've heard issues like this crop up. Do you have a screen guard or something
Sent from my NookColor using Tapatalk
For those who would want to try, scews the S2.
But the link from nolook actually fixes it.
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
edit: only fixed it for a short time. i'm back with some bad touch.
can you attach the .apk i cant go to market to download!! plsss
I have been noticing a weird thing with my Droid 3. I love the phone. I haven't had any issues. I do get this annoying green screen effect during transitions. It only seems to happen if I have Netflix or Youtube running in the background. I can fix the problem by going into my settings and turning off my screen animations. I am in the process of getting it exchanged. I will let you know if it is just a fluke or maybe a possible issue with the phone software.
Is this happening to anyone out there with a Droid 3?
video coming soon. Still uploading
I have the same problem between screen changes
Sent from my DROID3 using XDA App
My wifes did that too, but she was using just texts. I turned off animations and to save battery, and noticed it hadn't come back yet. Thought maybe I was only one
Edit: she says it still does it...hmmm dunno...hope it gets fixed in next update
Sent from my DROID3 using XDA Premium App
tried to replicate the problem on mine, but didn't have any issues. Hmm.
Green is usually an overlay color when drawing from a framebuffer. This just means something is forcing screen output before the frame is fully drawn. It's an out-of-sync drawing issue somewhere in the software or driver and isn't a hardware problem. I wouldn't worry too much about it unless it happens so often that it annoys you. It's not hurting anything.
I've seen this as well with youtube...I've also seen it show a partial view of my homescreen while transitioning between menus....not a big deal, but hopefully it'll get fixed soon
Sent from my DROID3 using XDA App
Happened to my wifes and my phone today. Kept going to green screen when trying to open the camara app. Had to reboot to make it go away. Im also on my third droid 3 phone. First one scratched the paint finish next to the keyboard when sliding open. The second droid 3 the speaker sounded like it was shorting out when calling or talking to someone.
Sent from my DROID3 using XDA Premium App
I had this problem, it went away after a reboot. Haven't seen it since.
Sent from my DROID3 using XDA App
Have you tried rebooting the phone, instead of getting it replaced? A reboot can work wonders.
"Have you tried turning it off and then on again?" - The IT Crowd
Love that show.
Sent from my DROID3 using XDA App
wife's phone did this while in camera mode. looked lik she was peering into the matrix. rebuffer or not, it's an obvious software glitch. i factory reset her phone so that vzw would log the activation.
640k said:
wife's phone did this while in camera mode. looked lik she was peering into the matrix. rebuffer or not, it's an obvious software glitch. i factory reset her phone so that vzw would log the activation.
Click to expand...
Click to collapse
Yeah, a stuck app that is unable to redraw will do the same thing but instead of a flash it's a permanent green-screen until the app is force closed or the phone is rebooted. I've had the camera do this to me a few times and Motorola has already come forward saying the camera app has problems, including this one, that they're working on.
i could live with an occasional software glitch if everythign wasn't so dammed slow. i've yet to see this phone actually perform a function faster than my D2. the software overhead is unbelievable.
640k said:
i could live with an occasional software glitch if everythign wasn't so dammed slow. i've yet to see this phone actually perform a function faster than my D2. the software overhead is unbelievable.
Click to expand...
Click to collapse
Well we could be in luck, it looks like root on the D3 could very likely happen sometime this week. 2.3.4 has been successfully rooted with the phone already on 2.3.4 and the bootloader still locked. We have P3 all over it now, too.
elkay said:
Well we could be in luck, it looks like root on the D3 could very likely happen sometime this week. 2.3.4 has been successfully rooted with the phone already on 2.3.4 and the bootloader still locked. We have P3 all over it now, too.
Click to expand...
Click to collapse
Link? Where is this?
pplude said:
Link? Where is this?
Click to expand...
Click to collapse
You didn't really have to look far haha.. start at the top of page 3 where it starts to get good.
http://forum.xda-developers.com/showthread.php?t=1193893&page=3
We're also looking into the way they obtained root on the Atrix on 2.3.4 with the bootloader still locked.. second post.
http://forum.xda-developers.com/showthread.php?t=1138204
...thats my post. Wow I feel dumb.
pplude said:
...thats my post. Wow I feel dumb.
Click to expand...
Click to collapse
LOL! I just saw that myself. Cheers!
Ha!
@pplude that made my day.
I have the same problem, i get the screen flicker going between handecent and my homescreen running prolauncher. i've had my droid 3 for a couple weeks and after rooting and freezing all that junk, I'm quite happy with the phone. other than this weird green pixel matrix screen... thing..
Not a huge issue, just a lil annoying.
TopHat
I had the green screen issue. I uninstalled youtube updates and haven't seen it since, same thing on my girls d3 hope it helps
The gist is: Is it possible to make a Captivate do this? I know that just about every Motorola android has a nice little reorienting animation when you turn it over. We (and by "we" I mean "you geniuses who know what the hell you're doing") managed to implement the now standard crt screen-off animation. Any chance at getting the "flip?"
Sent from parts unknown.
Boraltis said:
The gist is: Is it possible to make a Captivate do this? I know that just about every Motorola android has a nice little reorienting animation when you turn it over. We (and by "we" I mean "you geniuses who know what the hell you're doing") managed to implement the now standard crt screen-off animation. Any chance at getting the "flip?"
Sent from parts unknown.
Click to expand...
Click to collapse
Yea its possible .
Some of my roms have either flip, flying or bouncing animation.
Sent from my HTC Sensation Z710e using xda premium
Does this need to be built into a rom? Or is there a flashable mod or DIY guide that I'm unaware of?
Sidenote: I love your work, Logic. I do flash your roms. I've just never seen (or don't recall) an animation for switching back and forth between portrait and landscape.
Sent from parts unknown.
LostLogic is talking about something completely different, IE the transitions between apps or pop ups.
As for your question, ICS has it (running it right now) so you can flash an ICS ROM like the team hacksung one. I'm running that right now and it has the aforementioned animation.
Sent from my SGH-I897
Right on, Mike. How is that as a daily driver for a casual user (as in I don't use my phone for all it can do)? Just calls, text, web browsing and some games. I've read the thread, but it's pretty conflicted in terms of reviews. Your take? Or anyone else's for that matter?
Sent from parts unknown.
I've personally been on Build 6 of Teamhacksung's ICS for a couple days and I've had no blaring issues. I use my phone pretty much same as you, based on your description. Definitely loving ICS so far.
How is the battery life on the ICS port? Same as CyanogenMod?
MikeyMike01 said:
LostLogic is talking about something completely different, IE the transitions between apps or pop ups.
As for your question, ICS has it (running it right now) so you can flash an ICS ROM like the team hacksung one. I'm running that right now and it has the aforementioned animation.
Sent from my SGH-I897
Click to expand...
Click to collapse
My bad I misunderstood, just took a quick look via my phone. XD
Sent from my HTC Sensation Z710e using xda premium
caleb4992 said:
How is the battery life on the ICS port? Same as CyanogenMod?
Click to expand...
Click to collapse
Mine looks to be about the same.
Boraltis said:
Right on, Mike. How is that as a daily driver for a casual user (as in I don't use my phone for all it can do)? Just calls, text, web browsing and some games. I've read the thread, but it's pretty conflicted in terms of reviews. Your take? Or anyone else's for that matter?
Sent from parts unknown.
Click to expand...
Click to collapse
If you can live without the video camera it's great, and only getting better.
Sent from my SGH-I897
I agree. I started right around build 4 or 5 I think and I haven't looked back. Ics is just so worth not having video recording right now. Definitely awesome and I use my phone daily for all sorts of things. I wish flash was working because it broke a game I play but otherwise it's worth the few minor problems
Sent from my ice creamed Captivate
hi guys for the past one month . my phone is not at all responsive in the touch screen and in the soft buttons .. it gets stuck and I have to lock the screen and then unlock it to make it work!!! tried many roms but still the same. is my phone aged? lolzz its 10 months old!!
Sent from my HTC Incredible S using xda premium
Hmmm, strange.. Did some Googling and found some interesting stuff. Anyway, I see that you are from India too. Take it to an hTC center, and ask them to look into it. It might be some issue with the phone's hardware. If the service center's guy is not bright enough to check if your phone is s-off, you might get lucky
---------------------------
hTC IncS on Virtuous Quattro RC3
im also facing this issue
when I call someone they cant hear my voice and i tried no. of callsand its still the Same and when I pull out and battery and restart everything seems to be fine..
Sent from my HTC Incredible S using xda premium
hey guys now volume button is not working.. is my phone dying?
You've killed your incs time to buy galaxy nexus.
Sent from my Incredible S using xda premium
itsbeertimenow said:
You've killed your incs time to buy galaxy nexus.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Seriously stop being that naive, I also had that call problem - radio flash did help. Still having same freezing as u occur, which came and shows up with Sense 3.0+ releases. Don't worry your phone isn't even near to it's death
henrylife said:
Seriously stop being that naive, I also had that call problem - radio flash did help. Still having same freezing as u occur, which came and shows up with Sense 3.0+ releases. Don't worry your phone isn't even near to it's death
Click to expand...
Click to collapse
I've got the same freeze issue....tried replacing digitizer, didn't help. Tried various ROMS, didn't help.
Have you tried a non-Sense ROM? I thought I tried that, and it didn't help either
Bringing up an older thread, but I have found a partial solution for my screen freeze issues. This was posted on another forum, so I can't take credit.
Download SGS booster and set to optimized. Slide top three sliders all the way to the left, and bottom two sliders all the way to the right, and apply.
I seem to have way less freezes with this active.
Before doing this i replaced LCD and digitizer, new ROMs (both Sense and AOSP), and nothing made a difference, so I am fairly happy that this software has improved my phone.
Anf no, I am not affiliated, just a user that seems to have been successful with an issue by using this software. There might be other software which does the same thing also, idk.
I had same touch problem and hanging problem.
It's the motherboard problem.
I took it to HTC care center and reported the problem.
Also added a few problem on my own like..AUTOMATICALLY SWITCHING OFF..UNABLE TO ACCEPT CALLS.
They replaced my piece (except back cover, camera and battery).
Try reporting to HTC Care center. :good:
Fist off, huge thanks to these people:
-Ryuinferno - His init.d on any device method
-Matt on code.google.com - Old touch driver and temp install method
Disclaimer:
-I am not responsible for any damage this may cause.... (You've seen this a billion times so I'll leave it at that)
NOTE: This mod causes touch to be unresponsive for about 30 seconds on boot up!
What this does:
-Enables init.d by adding a command into install-recovery.sh to run anything in /system/etc/init.d (method by Ryuinferno)
-Extracts the E015 driver to /system for safe keeping and script usage (E015 is a downgrade of the touch driver that senses touch better)
-Adds an init.d script that changes the touchscreen driver to E015 on every boot (driver supplied by Matt and so was the temp-replace method. It runs his method on every boot essentially.)
-Sends log to /data/Driver.log so user can check proper installation if desired
The advantage of using this over using a kernel with E015 in it is that it does not mess with custom recovery touch sensing.
Instructions:
-THIS WILL NOT WORK UNLESS BUSYBOX IS INSTALLED! You can install it with this app.
-Download the zip from here
-Flash it in a custom recovery. If you don't know how to flash a recovery / root / flash a zip, there are plenty of tutorials floating around.
If you want to undo this:
-Flash this zip through recovery.
Enjoy!
thanks.. works well but the disadvantage of this is that everytime you reboot your phone is not responsive for 5 - 10 seconds.
Touch is far more sensitive. I can no longer rest my finger on the home button without it triggering although PSR values are still the same with lowest I got being 0.36
also can you please provide a revert .zip to remove all changes? I don't want to have to reflash my ROM if I no longer want the mod. Thanks.
DarkRyoushii said:
thanks.. works well but the disadvantage of this is that everytime you reboot your phone is not responsive for 5 - 10 seconds.
Touch is far more sensitive. I can no longer rest my finger on the home button without it triggering although PSR values are still the same with lowest I got being 0.36
also can you please provide a revert .zip to remove all changes? I don't want to have to reflash my ROM if I no longer want the mod. Thanks.
Click to expand...
Click to collapse
My touch is responsive instantly... Weird
Yep I can get a revert out soon
Sent from my Nexus 4 using Tapatalk 2
Thanks for this. I'll wait for a revert as this hasn't been much of a concern for me since I got used to it, but it's great to see this development today. I'm sure a number of folks are thrilled.
Just to confirm, this would qualify as an add-on to any kernel, correct? I noticed you mentioned the advantage of this over kernels with the new sensitivity but reading on your description it appears this will not replace your kernel?
lnfound said:
Thanks for this. I'll wait for a revert as this hasn't been much of a concern for me since I got used to it, but it's great to see this development today. I'm sure a number of folks are thrilled.
Just to confirm, this would qualify as an add-on to any kernel, correct? I noticed you mentioned the advantage of this over kernels with the new sensitivity but reading on your description it appears this will not replace your kernel?
Click to expand...
Click to collapse
It's not a kernel, it's essentially a script that runs on boot.
Revert going up in the next hour
Not only does e015 fix the touchscreen responsiveness, it also fixes the issue where if the phone is connected to an a/c powered usb port, the touchscreen responsiveness is even more degraded.
yea but I've noticed a few bugs with it already (touch being registered as pressed for about 4 seconds longer than my finger) as well as it is making my swiftkey lag behind so I'll probably revert until an official fix is in the works/made.
DarkRyoushii said:
yea but I've noticed a few bugs with it already (touch being registered as pressed for about 4 seconds longer than my finger) as well as it is making my swiftkey lag behind so I'll probably revert until an official fix is in the works/made.
Click to expand...
Click to collapse
Reverter http://goo.im/devs/trter10/RevertE015.zip
DarkRyoushii said:
yea but I've noticed a few bugs with it already (touch being registered as pressed for about 4 seconds longer than my finger) as well as it is making my swiftkey lag behind so I'll probably revert until an official fix is in the works/made.
Click to expand...
Click to collapse
Not seeing these issues myself. The stock keyboard is super smooth. I don't use swift key however.
I've just added this to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
KidCarter93 said:
I've just added this to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks
Sent from my Nexus 4 using Tapatalk 2
Tested out and as someone who hasn't had much of an issue with the reduced sensitivity, this is awesome. No issues with SwiftKey or anything either.
I am however unresponsive for about 10s after boot, not a big deal though.
Sent from my Nexus 4 using Tapatalk 2
lnfound said:
Tested out and as someone who hasn't had much of an issue with the reduced sensitivity, this is awesome. No issues with SwiftKey or anything either.
I am however unresponsive for about 10s after boot, not a big deal though.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This made mine unresponsive for around 30 seconds, it's random also, and makes the touchscreen unresponsive in recovery for around a minute.
Doesn't really seem to make any difference to the sensitivity on my phone either so I guess different phones have different sensitivity? Or I don;t notice the difference.
Using the revert zip didnt do anything so I had to revert to a nandroid backup.
Definitely feels like its improved! Hopefully its not just placebo
Sent from my Nexus 4
Checked the PRS readings and got 0.3-0.5 instead of the usual 0.5-0.6. I'm also using a screen protector that's real thick. All is well!
biffsmash said:
This made mine unresponsive for around 30 seconds, it's random also, and makes the touchscreen unresponsive in recovery for around a minute.
Doesn't really seem to make any difference to the sensitivity on my phone either so I guess different phones have different sensitivity? Or I don;t notice the difference.
Using the revert zip didnt do anything so I had to revert to a nandroid backup.
Click to expand...
Click to collapse
Same here
qwahchees said:
Checked the PRS readings and got 0.3-0.5 instead of the usual 0.5-0.6. I'm also using a screen protector that's real thick. All is well!
Click to expand...
Click to collapse
I checked mine as well, still mostly in 5s but a few in the 3s. Even the 5 presses would've never registered in the past, huge difference.
Sent from my Nexus 4 using Tapatalk 2
This is awesome! It's absolutely more sensitive than stock. Taps are still in the .50's a lot, but I can get them in the .20's. However, ignoring the numbers, the absolute lightest taps are now registering so I'm thrilled with this
Thanks OP!
EDIT: Also, it's so sensitive that I can use my fingernail to tap and swipe (I'm a guy with short nails, so this wouldn't work for someone with longer nails). Even still, such a big difference because this wasn't possible with the original driver.
A few questions...
1) Does the "undo" zip work?
2) Okay to use with any ROM, correct (running stock 4.2.1 odexed)
3) OP: Any idea on the temporary freeze at each initial boot?
If im not reading this wrong, the "fix" uses an OLDER driver ? (i find it funny each time something is fixed by going back in time)