It has become quite clear that there is a small unlucky group of us that experience touch screen unresponsiveness at various times, mostly on froyo roms.
http://forum.xda-developers.com/showthread.php?t=1007304
http://forum.xda-developers.com/showthread.php?t=961042
Clearly I realize there are other threads that have discussed this in the past. I would like to find out just how common this problem really is and what we can do to fix it.
My personal experience: My screen works almost flawlessly on any eclair rom. Every froyo rom I have flashed (almost all the super cleans, vanilla AOSP, MIUI etc) I will experience unresponsive spots on the touch screen. Typically it starts in the lower left 1/4 then spreads to the entire screen. A brief lock and unlock of the phone usually gets it working again, only to return a few moments later. When my factory Samsung charger is plugged in the screen is completely useless.
Originally I thought it was a kernel problem but it still happens on the new OE released EC10 kernel as well as on the AOSP built ones. I think it is a hardware problem on certain phones. Why only froro? I have no idea.
Please participate in my survey so we can figure out how bad this really is.
I have also have the screen responsiveness issues. The middle of the screen becomes unresponsive and I have to lock and unlock to get the screen to work. This is only an issue with froyo ROMs. My wife has a fascinate and even though I flashed her phone the same way, she never has had screen responsiveness issues.
Sent from my SCH-I500 using XDA Premium App
johntinman said:
My wife has a fascinate and even though I flashed her phone the same way, she never has had screen responsiveness issues.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Excellent information, same method different results. Only difference, the phones themselves.
So far, my Fascinate is running SC 2.9. 2 with absolutely no problems. Did it take a while for those symptoms to start or was it right away?
Sent from my rooted Fascinate running SC 2.9.2 and Tapatalk.
tfotos said:
So far, my Fascinate is running SC 2.9. 2 with absolutely no problems. Did it take a while for those symptoms to start or was it right away?
Sent from my rooted Fascinate running SC 2.9.2 and Tapatalk.
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
It always happened right away (sometimes within a few hours). I should point out this is not developer related. I have the same problems on fully bloated stock roms. I should have mentioned that in the op.
If you Odin back to stock DI01, does it still happen? If so, it sounds like a hardware defect. I, for one, have never seen any screen responsiveness issues at all on my phone, no matter which kernel or rom I'm on.
Sent from XDA Premium on my Super Clean Fascinate
I am having the same issue. Mine is most often around the letters "s" and "k" and it seems intermittent. I was running DJ05 up until a few weeks ago. Then I flashed an EB01 kernel with DarkRevenge, and started to notice this problem. No issues when running DJ05.
ivorycruncher said:
If you Odin back to stock DI01, does it still happen? If so, it sounds like a hardware defect. I, for one, have never seen any screen responsiveness issues at all on my phone, no matter which kernel or rom I'm on.
Sent from XDA Premium on my Super Clean Fascinate
Click to expand...
Click to collapse
Yes, I tried this too. Along with various cocktails of wiping and clearing cache's, no change.
*When I return to any eclair rom it works fine, again why only with froyo??
Just flashed JT's new EC10 kernel and so far no screen responsiveness issues (8+ hours), I'll keep you posted.
Update: my screen responsiveness issues have come back.
Sent from my SCH-I500 using XDA Premium App
I had this problem on some versions of SC 2.8 and at first with 2.9, but now on SC 2.9.2 I haven't had it.
Mine was mostly around letters O, I, N, K, but also sometimes E, R, A, and S. It usually happened after I had already pressed the letter. Take for example this message "I ran into...." I could type the letter I to start, but when I came to it again, it wouldn't register. Same with the letter N.
I had this happen after flashing certain themes. If I ran the ROM themeless, it wouldn't happen.
Factory wiped, ROM (2.9.2) refreshed, and have been running Nitsuj's gb theme with no probs for a few days now.
2.9.2 Voodoo Fascinate
GizmoDroid's CWM fix has stopped my screen resposiveness issues. It's worth a shot. I'm currently running Superclean 2.9.2 voodoo with EB01 radio.
Sent from my Froyonate
I also have the issue. Sometimes it will happen on the lock screen stopping me from unlocking the phone. Same fix though. Had it on all SC roms, AOSP and blackhole.
Sent from my SCH-I500 using XDA App
johntinman said:
GizmoDroid's CWM fix has stopped my screen resposiveness issues. It's worth a shot. I'm currently running Superclean 2.9.2 voodoo with EB01 radio.
Sent from my Froyonate
Click to expand...
Click to collapse
Just did the whole process twice, no change. . . It always seems to be okay at first but a little while later it rears it's ugly head. While in portrait mode if you bisect the phone vertically it is the right hand side that goes dead, the left works fine.
Back to eclair.
Legato525 said:
I also have the issue. Sometimes it will happen on the lock screen stopping me from unlocking the phone. Same fix though. Had it on all SC roms, AOSP and blackhole.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ditto on mine. After a while it becomes so bad that it happens everytime after it goes to sleep by itself. I would have to reboot to keep it going ok for awhile.
iorikun said:
Ditto on mine. After a while it becomes so bad that it happens everytime after it goes to sleep by itself. I would have to reboot to keep it going ok for awhile.
Click to expand...
Click to collapse
Just tried adryn's EC01 ROM and radio and it still happens....don't bother.
Sent from my SCH-I500 using XDA Premium App
So everyone on here thats had a problem with screen responsiveness has tried a rom/kernel with voodoo lagfix?? If not then give it a try and see if you get the same results.
Keep me Fascinated
SC 2.9.2
EC10 Voodoo Lagfix
Nitro Dark v4
Yes, I've tried Voodoo, nonVoodoo with same issues.
dw77x said:
Just did the whole process twice, no change. . . It always seems to be okay at first but a little while later it rears it's ugly head. While in portrait mode if you bisect the phone vertically it is the right hand side that goes dead, the left works fine.
Back to eclair.
Click to expand...
Click to collapse
Yep same thing here. Not sure when it started but it was most prominent with maybe SC2.8 I think.
It seemed to go away with SC 2.9, but it happens ever now and then.
Always the right side of the screen, simply turn the screen on/off to fix.
Download Advanced Test Card from the market. Give it a try.
Keep me Fascinated
SC 2.9.2
EC10 Voodoo Lagfix
Honeycomb v4 - Animated
Related
Hey guys,
Just curious what your thoughts were on changing the ROM from the original one on the phone to Epic, (whatever the newest one is I think it's 2.5 somebody correct me if it isn't). So I guess if you've done this what are the most noticable changes and is it worth the time it takes to do this.
-Jim
I'm really enjoying the epic 2.5 rom. I liked the phone stock but I found it to hang up quite a bit, blur seemed a little power hungry, and there were some apps installed that I did NOT want that constantly bugged me (city ID!). I switched to epic and my phone seems much much more responsive and my batter life seems mildly improved, by about roughly 10%. I'll more than likely continue to use epic until the bootloader gets cracked and we get something like cyanogen on the D2
I also use epic 2.5 and it sometimes randomly reboots, but otherwise its amazing. Battery life is great!
Sent from my DROID2 using XDA App
what's your battery life like? because that's my main problem with my d2 since i text quite frequently and that seems to drain the battery like no other.
so you guys say go for it? also how do you back your contacts up when you change the roms?
hockeyhead019 said:
Hey guys,
Just curious what your thoughts were on changing the ROM from the original one on the phone to Epic, (whatever the newest one is I think it's 2.5 somebody correct me if it isn't). So I guess if you've done this what are the most noticable changes and is it worth the time it takes to do this.
-Jim
Click to expand...
Click to collapse
If you are looking for a rom with little to no Blur left, try installing Motoboy's R2D2 SuperClean. It doesn't have all the Star Wars stuff and you are left with a solid system. I experienced a few bugs that were show stoppers on Epic 2.5. Those being the slide to unlock reboots, and the calendar not allowing me to add events. Matt has posted a fix for the calendar, but as of yet nothing stops the unlock reboots. Personally I find both of the roms to be better than what was shipped with the device. Ultimately which rom to flash should be your decision not someone else's.
Link?
zibrah3ed said:
If you are looking for a rom with little to no Blur left, try installing Motoboy's R2D2 SuperClean. It doesn't have all the Star Wars stuff and you are left with a solid system.
Click to expand...
Click to collapse
Can you post a link for Motoboy's R2D2 SuperClean?
wecramer said:
Can you post a link for Motoboy's R2D2 SuperClean?
Click to expand...
Click to collapse
Read the instructions carefully, then read them again. This is a slightly tougher install than Epic.
http://forum.xda-developers.com/showthread.php?t=796908
Well I'm a new Droid 2 user. I had the original D1 and just got the D2 about a week ago. Epic was the first rom I downloaded and I like it a lot it reminds me of my D1 roms I had installed. It's pretty fast and hardly lags. I had a few problems at first. My phone rebooted randomly about twice and I'm not sure if this was a problem for everyone or if I just had a corrupt file installed, but whenever I would use titanium backup my messaging app stopped working. It really pissed me off because my messages still worked, but I couldn't see them. It kept force closing, but eventually it started to work. I'm enjoying this rom so far.
EDIT: I'm having the lock reboot problem now, it has happened maybe four or 5 times and it has been getting annoying lol. I haven't really looked for a fix, but I will be soon.
The lock screen reboots are a known bug in Epic 2.5 but I'm back with epic after tweaking R2D2 too much and I haven't had a problem after installing lock screen on/off widget and setting it off.
Sent from my DROID2 using XDA App
What do u mean by the lock screen reboots? Just out of curiousity? I haven't had any reboots but I don't use a lock when my screen shuts off... is that what ur refering to or just the regular slide lock?
Sent from my DROID2 using XDA App
Slide to unlock from screen off. If lockscreen is disabled it doesn't do the reboots.
Sent from my DROID2 using XDA App
hockeyhead019 said:
What do u mean by the lock screen reboots? Just out of curiousity? I haven't had any reboots but I don't use a lock when my screen shuts off... is that what ur refering to or just the regular slide lock?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Yeah I've heard that people without a slide-to-unlock feature are fine, but people like me that HAVE to have a lockscreen, are expeirencing problems. It has happened to me a couple times already
@Herromoto
Maybe you could disable the slide lock screen and put a pattern lock on. I don't know if the widget will disable the pattern or the pattern will make a reboot but it's worth a shot.
Sent from my DROID2 using XDA App
newk8600 said:
@Herromoto
Maybe you could disable the slide lock screen and put a pattern lock on. I don't know if the widget will disable the pattern or the pattern will make a reboot but it's worth a shot.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Yeah I heard that's a solution people use, but I am too hard headed to do that lol, I like the old school lock screen too much
I know that some of us unlucky few have had problems with screen responsiveness and froyo. This is not the "lag" that some experience, but dead zones on the screen. The only fix is to lock and unlock the phone. In my case, the middle of the screen from top to bottom will not register touches. I have heard of others where the right or left sides of the screen will become unresponsive. What is bizzare is that on 2.1 Eclair ROMs it would never happen. It only happens with 2.2 Froyo. I have tried all of the variants of leaked froyo ROMs (DL30, EB01, EC01), voodoo, and nonvoodoo with no success. I thought that maybe getting the official froyo update would remedy this problem, but it did not. I called Verizon and they are sending me a replacement. I spoke with CS and a Samsung Tech Support Specialist and they both stated that they haven't heard of this problem yet. The Samsung TSS said that it sounds like a hardware issue and the phone would need to be replaced. Regardless of whether or not you have insurance or not, there is a manufacturer warranty for a year. The Fascinate was released in Sept 2010, so all should be covered. Talk to them about a replacement so you can enjoy the hard work of the developers here and appreciate the froyo goodness.
Been running evil fascinate for 24 hours now, and this its the first froyo rom that I have not had issues
With the screen wigging out on me.
Sent from my SCH-I500 using XDA App
Tried Evil Fascinate and screen stopped responding. Sending phone back tomorrow.
I installed ED01 today (coming from superclean) and did experience some ridiculous lag. It was like nothing I had ever seen. It was so bad that the screen wasn't responding at all until I slept and woke the phone. I don't know what I did to bring that on myself.
Anyway, I think I infuriated some part of Touchwiz. I'm still fully stock except for root, and I haven't had any issues for the six hours since I changed launchers to ADW.
That was just unlivable though. Now I finally have an idea of the sort of lag people are complaining about.
Recent events: Odin DI01 -> EA28 -> OTA ED01 -> Root Explorer & Titanium w/o root -> Super Oneclick 1.8 beta -> old version of Superuser -> issues -> remove all user apps -> manual lagfix -> new Superuser -> more issues -> unroot -> ADW -> manual root again -> fine -> 3/30 recovery-all odin -> nandroid -> here
Jesus....
I actually have no input...other than that last paragraph must have been a b**ch to type.lol
soba49 said:
I installed ED01 today (coming from superclean) and did experience some ridiculous lag. It was like nothing I had ever seen. It was so bad that the screen wasn't responding at all until I slept and woke the phone. I don't know what I did to bring that on myself.
Anyway, I think I infuriated some part of Touchwiz. I'm still fully stock except for root, and I haven't had any issues for the six hours since I changed launchers to ADW.
That was just unlivable though. Now I finally have an idea of the sort of lag people are complaining about.
Recent events: Odin DI01 -> EA28 -> OTA ED01 -> Root Explorer & Titanium w/o root -> Super Oneclick 1.8 beta -> old version of Superuser -> issues -> remove all user apps -> manual lagfix -> new Superuser -> more issues -> unroot -> ADW -> manual root again -> fine -> 3/30 recovery-all odin -> nandroid -> here
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
So.....I decided to add a line for my son and decided to go with a white Fascinate. The darn thing wouldn't let me update it from D101 to ED01. It kept getting stuck on Updating modem on the install screen. I was able to ODIN to ED01, but was just fed up with the number of problems I have experienced with 2/3 of the Fascinates I owned. I returned to Best Buy and exchanged for a Thunderbolt and now I am happy. I have had other HTC devices (Nexus One, G2) and absolutely loved them (still miss my N1) and appreciated how well they were built. I was going to hold out for the Charge or the Galaxy II, but after this debacle with Verizon, Bing, Samsung, and Froyo I have had enough.
Update: had the thunderbolt for less than a day and took it back. My main reasons were size of phone, weight of phone, and the Fascinate's screen is far superior. The GPU must suck on the the tbolt because animations weren't as smooth and games did not play as well. Spent $200 less to get a nice white Fascinate and now I'm happy.
I can vouch for the op's statements. Been there done all of that. Only solution was a replacement phone. Why only 2.2, I have no idea. Moral of the story, stop trying to make it work. Get your phone replaced and enjoy the good stuff.
johntinman said:
I know that some of us unlucky few have had problems with screen responsiveness and froyo. This is not the "lag" that some experience, but dead zones on the screen. The only fix is to lock and unlock the phone. In my case, the middle of the screen from top to bottom will not register touches. I have heard of others where the right or left sides of the screen will become unresponsive. What is bizzare is that on 2.1 Eclair ROMs it would never happen. It only happens with 2.2 Froyo. I have tried all of the variants of leaked froyo ROMs (DL30, EB01, EC01), voodoo, and nonvoodoo with no success. I thought that maybe getting the official froyo update would remedy this problem, but it did not. I called Verizon and they are sending me a replacement. I spoke with CS and a Samsung Tech Support Specialist and they both stated that they haven't heard of this problem yet. The Samsung TSS said that it sounds like a hardware issue and the phone would need to be replaced. Regardless of whether or not you have insurance or not, there is a manufacturer warranty for a year. The Fascinate was released in Sept 2010, so all should be covered. Talk to them about a replacement so you can enjoy the hard work of the developers here and appreciate the froyo goodness.
Click to expand...
Click to collapse
Huh. So far so good here after ota update. Screen was constantly dropping out previous to this especially when form input was required.
Sent from my SCH-I500 using Tapatalk
I think I have experienced this problem on mine. I use the pattern lock and sometimes I just can't finish the pattern until I turn it off and on via the power button. I've been using froyo builds to a while so I can't quite remember when that started to happen. What I did notice is that I no longer have this problem with CM7 rom.
Sent from my SCH-I500 using XDA App
In my quest to figure this out I flashed the cm7 that PK was/is building. I did not have it loaded long enough to fully evaluate (due to not enough working yet) but I did not notice the screen problem then either. Again, only FroYo?
alexgreen said:
I think I have experienced this problem on mine. I use the pattern lock and sometimes I just can't finish the pattern until I turn it off and on via the power button. I've been using froyo builds to a while so I can't quite remember when that started to happen. What I did notice is that I no longer have this problem with CM7 rom.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
alexgreen said:
I think I have experienced this problem on mine. I use the pattern lock and sometimes I just can't finish the pattern until I turn it off and on via the power button. I've been using froyo builds to a while so I can't quite remember when that started to happen. What I did notice is that I no longer have this problem with CM7 rom.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
This definitely started when I went from the eclair build that my phone came with (DI01 I think) to EB01. I moved away from pattern unlock to PIN unlock so I didn't notice the unresponsiveness as much. I just flashed ED01 so let's see how it is with this build.
With their stock launcher i was having lag issues but i dont like it anyway, so i put adw on it and no more screen lag for me. I dont know if this is a fix or if I just got lucky there.
DaleV said:
With their stock launcher i was having lag issues but i dont like it anyway, so i put adw on it and no more screen lag for me. I dont know if this is a fix or if I just got lucky there.
Click to expand...
Click to collapse
I've always used Launcher Pro so not true in my case.
I updated to ed01 ota and had lots of problems with the twlauncher so I had to do a factory reset and I still had lag. Then I thought for 5 seconds and one word: LauncherPro. LauncherPro took away all my lag on the launcher and froyo has been as fast as 2.3 for me. I would do a factory reset install a speedy rom and kernel. Maybe even go back to stock for a while because my friend had the same problem and it seemed to work for him as well.
Sent from my SCH-I500 using XDA Premium App
I ran the original Toxic Baby on my Girlfriends phone, I personally havent had a problem with these ROMS that wasnt user error, and I tend to think this is too, but her screen orientation is acting strange, not working.
On home screen (with auto orientate on) its vertical, but keeping the phone vertical and opening an app, it auto-switches to horizontal. the only way that I can find to correct this is to turn the auto-orientate off, which leaves ALL screens vertical.
I've tried factory data reset, flashing back to stock (ODIN) wiping ALL data from the boot screen but the problem persists. does anyone have some insight in to this?
The accelerometer is probably busted,I'm just guessing though.
gorealmighty said:
I ran the original Toxic Baby on my Girlfriends phone, I personally havent had a problem with these ROMS that wasnt user error, and I tend to think this is too, but her screen orientation is acting strange, not working.
On home screen (with auto orientate on) its vertical, but keeping the phone vertical and opening an app, it auto-switches to horizontal. the only way that I can find to correct this is to turn the auto-orientate off, which leaves ALL screens vertical.
I've tried factory data reset, flashing back to stock (ODIN) wiping ALL data from the boot screen but the problem persists. does anyone have some insight in to this?
Click to expand...
Click to collapse
The included kernel is for captivate. You need a vibrant kernel.
I recently tested a cappy kernel for my simply galaxy series gb rom and had the same.
Sent from my GT-I9000 using XDA Premium App
explodingboy70 said:
The included kernel is for captivate. You need a vibrant kernel.
I recently tested a cappy kernel for my simply galaxy series gb rom and had the same.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I'll try that, hell, it cant hurt to. but Ive run the ROM on my phone with no problems, infact ive been torn on flashing a kernel over it just to try it, but I like the way they run without an additional MOD. of course I know no two phones are alike even if they are the exact same phone.
Is there a Kernel you could recommend?? (im kind of using her phone as a guinea pig now ) Ive been looking at Bali and deadhorse. I just dont know how they will interact with Jcc's ROM plus Voodoo.
gorealmighty said:
I'll try that, hell, it cant hurt to. but Ive run the ROM on my phone with no problems, infact ive been torn on flashing a kernel over it just to try it, but I like the way they run without an additional MOD. of course I know no two phones are alike even if they are the exact same phone.
Is there a Kernel you could recommend?? (im kind of using her phone as a guinea pig now ) Ive been looking at Bali and deadhorse. I just dont know how they will interact with Jcc's ROM plus Voodoo.
Click to expand...
Click to collapse
I'd stay clear of dead horse. I really haven't tried any of the other kernels since I've been working on my GB rom. Overstock is always stable and worth a look. I'm using one of cmenards kernels on my GB rom and always used on froyo.
Sent from my GT-I9000 using XDA Premium App
explodingboy70 said:
I'd stay clear of dead horse. I really haven't tried any of the other kernels since I've been working on my GB rom. Overstock is always stable and worth a look. I'm using one of cmenards kernels on my GB rom and always used on froyo.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
hm. I appreciate it. Flashing Overstock wont take away firefly will it? (shes unfortunately fallen in love with firefly)
Thanks for the insight guys. I appreciate it!
gorealmighty said:
hm. I appreciate it. Flashing Overstock wont take away firefly will it? (shes unfortunately fallen in love with firefly)
Thanks for the insight guys. I appreciate it!
Click to expand...
Click to collapse
No flashing a kernel will affect the rom visually in no way. There may be kernel specific features that the rom dev may have listed such as bln but otherwise your cool.
Sent from my GT-I9000 using XDA Premium App
I just tried out 3 different ROMS. Cherryblur, Ninja, and Red Pill. All three of them cause my touchscreen to be unresponsive at times. When I try to interact with my phone a lot, sometimes I have to wait a couple seconds before I can actually press on what I want to press on. Does anybody have issues like that? I went back to 1.83 and everything is dandy. Is there a fix for this? Haven't seen anything like this yet on the forums.
kshiuan said:
I just tried out 3 different ROMS. Cherryblur, Ninja, and Red Pill. All three of them cause my touchscreen to be unresponsive at times. When I try to interact with my phone a lot, sometimes I have to wait a couple seconds before I can actually press on what I want to press on. Does anybody have issues like that? I went back to 1.83 and everything is dandy. Is there a fix for this? Haven't seen anything like this yet on the forums.
Click to expand...
Click to collapse
This is an issue with the SBF... which one did you use?
Im using the official GB and im having the same problem, especially on phone calls....the screen locks itself up
mpalatsi said:
This is an issue with the SBF... which one did you use?
Click to expand...
Click to collapse
I didn't use any of the SBF's. I have not used any SBF's period to flash besides a long time ago when I was playing around with Froyo.
bandityo said:
Im using the official GB and im having the same problem, especially on phone calls....the screen locks itself up
Click to expand...
Click to collapse
I don't think that's what my issue is. Anyone know what I need to do to fix it? It's quite annoying.
For background:
I was on 1.8.3 and decided to jump to a GB ROM today. Went with Cherryblur at first. Noticed the lag, so I tried Red Pill and then settled on Ninja. However, Ninja is still giving me these touchscreen lag issues. When CWM'ing new ROMS I ALWAYS wiped data/cache/Dalvik. Then I would install the ROMs on CWM and apply jug's battery fix. Was there anything else I needed to do? I figured I shouldn't be SBFing anyways.
Sent using my Ninja Atrix 4G.
went from leaked gingerbread back to syndicate 1.1.0 and now the autorotate doesn't work, only when i open the keyboard. I did all the fixes, it still doesn't work, any idea how to fix it. I've had 3 epics and never had the problem of it not rotating, always slow rotating or something like that, but never no rotating.
Did autorotate get turned off in the Launcher Pro settings?
Specialksg1 said:
Did autorotate get turned off in the Launcher Pro settings?
Click to expand...
Click to collapse
this is fullyloaded touchwiz and its on.
I wiped data and everything, still doesn't work.
Try this
Did you calibrate the accelerometer first? That might fix it. Mine get kinda wonky after reflashing and especially after using Odin.
i did the calib_yamaha, I calibrated the sensor, nothing did anything, I flashed the gb leak again and it works fine, I flash back to sf 1.1.0 and it doesn't work, so now I'm stuck on the gb leak which is a problem because the phone barely works and keeps dropping calls so I really need to get back to froyo.
robl45 said:
this is fullyloaded touchwiz and its on.
I wiped data and everything, still doesn't work.
Click to expand...
Click to collapse
Are you referring to rotating the home screen, or any and all apps? I might be mistaken, but I don't think TouchWiz rotates the home screen, at least not without sliding out the keyboard...
Also, I would recommend upgrading to SRF 1.2, it's even better than 1.1
Sent from my SPH-D700 using XDA App
styles420 said:
Are you referring to rotating the home screen, or any and all apps? I might be mistaken, but I don't think TouchWiz rotates the home screen, at least not without sliding out the keyboard...
Also, I would recommend upgrading to SRF 1.2, it's even better than 1.1
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
the apps, they don't rotate at all, nothing rotates unless you pop the keyboard out.
This happened to be when I tried a different rom couldn't get it to work for the life of me.
Cleared data, Flashed SR v1.20 and it works now.
fastmikey1969 said:
This happened to be when I tried a different rom couldn't get it to work for the life of me.
Cleared data, Flashed SR v1.20 and it works now.
Click to expand...
Click to collapse
so why would 1.20 be any different that 1.1.0? I actually tried to get 1.20 last night, but the website kept coming up that it could not be found.
robl45 said:
so why would 1.20 be any different that 1.1.0? I actually tried to get 1.20 last night, but the website kept coming up that it could not be found.
Click to expand...
Click to collapse
Well, because 1.2 *is* different than 1.1 - hence the change in version numbers...
Why would you expect the two to be exactly the same? Kind of a silly question
A better question would be, "WHAT is different between the two, that would cause the auto rotate problem in 1.1?"
I don't know that answer, though... I think it may have been tied to the fully loaded version, because I remember experiencing it only once - when I briefly tried fully loaded, before going back to standard
Sent from my SPH-D700 using XDA App
styles420 said:
Well, because 1.2 *is* different than 1.1 - hence the change in version numbers...
Why would you expect the two to be exactly the same? Kind of a silly question
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
why would they be any diferent for rotation?
robl45 said:
why would they be any diferent for rotation?
Click to expand...
Click to collapse
Ok let me clarify my post. Running SR v1.1.1, rotate worked fine. Flashed Revoltion rom, didn't like it, few things didn't work like autorotate.
So I flashed another rom which fixed it, chose SR 1.2 to give it a try. If I flashed v1.1.1 that may have worked also.
so can we get back to the issue, i've tried 1.1.1 and the autorotate doesn't work. it appears to be a froyo issue as it worked fine for months and months and now only gingerbread roms will rotate. could that be because i'm using eh17 modem? i wouldn't think so.
robl45 said:
why would they be any diferent for rotation?
Click to expand...
Click to collapse
Well, one or many of the changes between 1.1 and 1.2 might have affected rotation as a side effect - whatever caused the glitch in 1.1 must have been changed for a completely unrelated reason, and the glitch disappeared...
I think, from what you've reported, that it had something to do with the extras in the fully loaded version - that used a hacked TW, right? 1.2 doesn't have a fully loaded package that I'm aware of... But try the standard version, or just use the most recent version since it *is* better
robl45 said:
so can we get back to the issue, i've tried 1.1.1 and the autorotate doesn't work. it appears to be a froyo issue as it worked fine for months and months and now only gingerbread roms will rotate. could that be because i'm using eh17 modem? i wouldn't think so.
Click to expand...
Click to collapse
It does nut appear to be a froyo issue, because 1.2 is froyo without the issue... In fact, so far the only froyo that appears to have this issue is the fully loaded version of 1.1... Several examples of froyo without the issue vs one with the issue would indicate that froyo is not the problem at all...
Unless I missed the part where you duplicated the issue on several other froyo roms - all I've seen mentioned is SRF 1.1 fully loaded... Have you seen the problem on 1.1 standard edition?
But you are correct about the modem having nothing to do with it
Sent from my SPH-D700 using XDA App
well you could be right, but i've been using the 1.1 for months and months, longer than any other rom and havent had a problem, and I've run many other roms, never had a problem. only time i've ever seen something like this is since running gingerbread leaks, now they work and the old one doesn't, I've flashed that same rom probably 10 times, never had a problem, gone from bonsai to that one and back again, never a problem so I would doubt the rom would have anything to do with it. I'll try the 1.2 if I can get it downloaded. last night the page wasn't coming up.
styles420 said:
Well, one or many of the changes between 1.1 and 1.2 might have affected rotation as a side effect - whatever caused the glitch in 1.1 must have been changed for a completely unrelated reason, and the glitch disappeared...
I think, from what you've reported, that it had something to do with the extras in the fully loaded version - that used a hacked TW, right? 1.2 doesn't have a fully loaded package that I'm aware of... But try the standard version, or just use the most recent version since it *is* better
It does nut appear to be a froyo issue, because 1.2 is froyo without the issue... In fact, so far the only froyo that appears to have this issue is the fully loaded version of 1.1... Several examples of froyo without the issue vs one with the issue would indicate that froyo is not the problem at all...
Unless I missed the part where you duplicated the issue on several other froyo roms - all I've seen mentioned is SRF 1.1 fully loaded... Have you seen the problem on 1.1 standard edition?
But you are correct about the modem having nothing to do with it
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
settings>display>horizontal calibration> place the phone screen upside down on a ledge but with a bit sticking out so you can touch it (like a dresser or desk or counter etc..>calibrate
its sounds strange but it worked for me
Thanks but I did that still didn't work
Perhaps a full odin back to stock froyo, then reinstall everything from there...
I'm wondering if gingerbread updated something that froyo relied on for sensor data (this is a long shot, falling under the category of "I don't see how they're related, but why not?")
Otherwise, it *almost* sounds like a hardware issue - except that you said it works fine on gingerbread... well, unless GB is using a different sensor reading...
Sent from my SPH-D700 using XDA App
styles420 said:
Perhaps a full odin back to stock froyo, then reinstall everything from there...
I'm wondering if gingerbread updated something that froyo relied on for sensor data (this is a long shot, falling under the category of "I don't see how they're related, but why not?")
Otherwise, it *almost* sounds like a hardware issue - except that you said it works fine on gingerbread... well, unless GB is using a different sensor reading...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
i've only run gb for like 2 weeks, was working fine on froyo, can't understand it. I did download srf 1.2 last night as the site would come up now. so i might play with that this weekend, although the GB is working now and making phone calls without dropping so aside from random reboots its working. kinda makes it hard to sell the thing eventually though if it won't rotate.
well I put on the srf 1.2, autorotate works fine, im perplexed as to why that is since autorotate worked fine for the 6+ months that I ran it and i've never had autorotate stop working on any of the 3 epics i've had and any of the roms. but at least its working now and i have a stable phone.