For those of us with Froyo screen responsiveness issues - Fascinate General

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

Related

Laggy on stock 1.6 will 2.1 or 2.2 be better?

Hey guys just wanted to get everyone's feedback on the streak. After having it for a full week now it seems like the home screens are laggy now. Jumping from apps to apps can be slow too. Can I wxpect 2.1 or the updated 2.2 to be this laggy again?
Is the flashed 2.2 laggy at all? I dont want to flash a rom yet since rumor it might come by the 15th. I hope and pray.. I dont have too many apps but this lag is killing me softly. Had iphone 4 before and obviously that will always be a smooth UI then had my captivate with flashed rom on 2.2 and that was pretty responsive...
Anything else I can do on 1.6 to help?
Sent from my Dell Streak using XDA App
I run an app called system panel.. And I run it when my 1.6 gets laggy. You can controle the working processes with it and stop the ones who take up to much memory or processing power.
Sent from my second wife.
tosh1 said:
Hey guys just wanted to get everyone's feedback on the streak. After having it for a full week now it seems like the home screens are laggy now. Jumping from apps to apps can be slow too. Can I wxpect 2.1 or the updated 2.2 to be this laggy again?
Is the flashed 2.2 laggy at all? I dont want to flash a rom yet since rumor it might come by the 15th. I hope and pray.. I dont have too many apps but this lag is killing me softly. Had iphone 4 before and obviously that will always be a smooth UI then had my captivate with flashed rom on 2.2 and that was pretty responsive...
Anything else I can do on 1.6 to help?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
My friend had the same strange issue and I believe it was caused by some app he downloaded. All we did to fix this was just reflash to 1.1.1 (now it would be also wise to flash to widely known Dj Steve's 1.2) It's easy and your Streak will work WAY faster.
personally, the 1.6 is a smidgeon laggy, but the 2.x versions are not.
i'd just be patient for 3-4 weeks and wait till the official 2.2 comes out.
Flashing to a XDA-ROM is tricky and troublesome and usually recommended to hardcore gizmo fiddlers.
I can't speak for everybody, but for all those I know owning a Dell Streak have the same problem as you do. We all hope the official Froyo will fix the problem, but it kind of late. I am about 6 months away from my upgrade date. This will be my last Dell. Hope some other will make phone with this size of screen.
When mine gets that way I power it off and back on. This is because I don't know where to find a "reset" app like I had with my Windoze mobile phone. Does one exist for Android 1.6?
I currently use an app called "Fast Reboot" off the market, and it literally just shuts most of the running processes down and boots everything up again. It takes a couple of seconds but it's a hell of a lot quicker than actually rebooting the phone, only for it to take 5-10 mins to start up again. I've not had any major problems using this app but it does have an affect on some widgets like the Battery Smart (android) widget which freezes and no longer shows you how much battery you've got left, but removing and adding it again works fine. Though every so often, I still like to do a proper reboot just in case.

[Q] Are you going back to 2.1

Just taking an assessment here of the number of people going back to 2.1 and waiting out the OTA from Sprint.
I am not... I Repeat NOT looking to start a thread over whether or not it's worth it or a good idea. I am not looking to know what problems you are having or solutions you have found. There are a million threads to go over these issues.
Just taking a count here. Perhaps to help me in deciding whether or not its worth it to go through reinstalling all those apps and whatnot based on what the masses seem to be thinking.
OK if you guys want to use this as yet another repository for conversations on the pros and cons and problems you are having when you switch back please feel free...
I already have. For me, di18 runs circles around froyo. I don't think this is the final froyo. It's too goddamn slow and buggy. If it is, then this is the most sorry ass excuse for a final release from samsung/sprint. I'd give it the golden turd award.
P.S. I'm running stock rooted only.
Even if its "buggy" and/or a bit "laggy", froyo let's me do what I want on my phone..so I could bare with it as I have been for like 2 months aready
Sent from my Epic 4G
No. I've been on the stock rom since I got an epic at the end of October, and this leak is by far the best rom I've used. I have absolutely no problems with this rom whatsoever. The one minor quirk is the screen lag when I open and close my keyboard, the home screen take a second to populate the icons and stuff. Other than that, I really don't have any major problems with this release at all.
DK28 feels like somehow I flashed Windows Mobile 6.5 on my phone. Launcher Pro is buggy and crashes at least several times per day. The phone freezes all the time and i have to mash the home key a hundred times to correct it, and then its vibrating for like 20 seconds registering the previous 100 hits of the home key. The browser is checkerboarding and WTF did my bookmarks go in the browser? Seriously, when you are in the browser, how do you access your bookmarks? They are no where to be found. Random apps are having anywhere from minor to major problems, most of which I fix manually through root explorer and correcting permissions. I did flash it correctly, so its not an issue with that. That said, its a PITA to flash back to DI18 and ive been putting it off. Gonna wait until I am mid throw chucking my phone against a wall, and then I will stop myself and flash back to DI18 that evening.
I guess I'm lucky with DK28. My phone has no ill effects.
acegolfer said:
I guess I'm lucky with DK28. My phone has no ill effects.
Click to expand...
Click to collapse
Same here. I'm keeping 2.2. It runs faster, smoother, and battery last longer. I have had no app conflicts. I'm came from unrooted stock epic, and just downloaded file from google the day it came out to my phone. Used my phone to change the name of the file, and used stock recovery to update. No probs what so ever.
Sent from my SPH-D700 using XDA App
Anyone know if can use stock recovery to update to the final release from the leaked version? Thd update.zip method is so easy
muyoso said:
DK28 feels like somehow I flashed Windows Mobile 6.5 on my phone. Launcher Pro is buggy and crashes at least several times per day. The phone freezes all the time and i have to mash the home key a hundred times to correct it, and then its vibrating for like 20 seconds registering the previous 100 hits of the home key. The browser is checkerboarding and WTF did my bookmarks go in the browser? Seriously, when you are in the browser, how do you access your bookmarks? They are no where to be found. Random apps are having anywhere from minor to major problems, most of which I fix manually through root explorer and correcting permissions. I did flash it correctly, so its not an issue with that. That said, its a PITA to flash back to DI18 and ive been putting it off. Gonna wait until I am mid throw chucking my phone against a wall, and then I will stop myself and flash back to DI18 that evening.
Click to expand...
Click to collapse
As a former Windows Mobile 6.5 user, I would like you to know that even WM6.5 on a TP2 is much more enjoyable to use than DK28.
That having been said, I went from DK28 back to Epic Experience.
Well a couple of things...
1) I think its funny that this has been viewed (at this point) 111 times, but only 17 people were willing to click yes no or considering it. I guess I should have included an option for those people who never flashed the update to begin with.
2) I updated on the day it was released as well. I had to do the flash back to get the GPS working again, but as of now the only real issue I have appears to be the accelerometer rotation lag.
@JSarella and @muyoso: I also was Stock ROM and rooted before the update and just used the update.zip method. However, I am not sure if that makes a difference with regard to the results of flashing to DK28.
@mxcoldhit: The battery life is amazing. I don't even have to use JuiceDefender, I can keep my screen at a normal brightness, have 2 email accounts pushing all day long, listen to an hour of music, make a couple of calls, play some games/do some light browsing, and still have battery to spare... just incredible to me the difference from 2.1 where I could hardly go a few hours of the day and do anything on the phone (without using JD).
I just felt like my phone was a bit snappier on eclair, and have been considering how much that snappiness is worth to me. I have backed up with CWM, so its not such a hassle, but I do love the battery life, flash support, and general feel of Froyo and know I would miss it as I wait at least 3 weeks for a final release. Also, who knows when an RC2 will be released and how much more careful Sprint will be as they actually caught wind of this one and all the excitement around it... I partially wonder if they did it as a teaser just to get a sense of how the community is feeling or to throw us off the scent of the gingerbread rumor... WHO KNOWS!!! Anywho, thanks to everyone who has responded, and I will keep checking in from time to time to see how it looks and what people are choosing to do based on their own personal experiences with DK28.
Already went back, didn't waste any time.
DK28 has been a great experience for me! Faster, smoother, more responsive than DI18 (or earlier) ever was! Dunno what some of you have done to your phones but DK28 has been running circles around the previous Eclair builds for the Epic 4G. My phone has only been on stock and never rooted. Also did a factory reset prior to DK28 so maybe that's why it has been such an utter joy for me.
Not going back and I'd be an idiot to do so!
I'm staying. I haven't had any problems and this thing runs so smooth now. This probably isn't final, but its close.
Sent from my SPH-D700 using XDA App
Only issue that i am having is that my gps is trashed and doesn't want to work. I haven't tried to fix it yet i may just wait and see if there will be another update soon. All in all i love it. I would suggest that once flashed do a wipe, that cleared out most of the bugs. Frustrating downloading apps again but worth it.
Sent from my SPH-D700 using XDA App
Bigjim1488 said:
Only issue that i am having is that my gps is trashed and doesn't want to work. I haven't tried to fix it yet i may just wait and see if there will be another update soon. All in all i love it. I would suggest that once flashed do a wipe, that cleared out most of the bugs. Frustrating downloading apps again but worth it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Titanium backup is your friend
Sent from my Epic 4G
After this morning I am going to have to go with likely to go back. Over time I am finding more and more bugs with DK28. This morning I was driving to work, I keep my phone linked to my car with bluetooth for slacker radio. Twice it loses it's connection and I was like what the hell.... so I look at my phone and it says 2 missed calls which should have gone through the bluetooth but instead just killed the data connection. Then 5 minutes later my whole notification bar goes green. Not a normal green, a look like a video card crashing green /w lines through it.
I just keep seeming to find random bugs here and there and it is getting a bit annoying. I may just wait it out until Samsung figures this whole froyo thing out.
muyoso said:
DK28 feels like somehow I flashed Windows Mobile 6.5 on my phone. Launcher Pro is buggy and crashes at least several times per day. The phone freezes all the time and i have to mash the home key a hundred times to correct it, and then its vibrating for like 20 seconds registering the previous 100 hits of the home key. The browser is checkerboarding and WTF did my bookmarks go in the browser? Seriously, when you are in the browser, how do you access your bookmarks? They are no where to be found. Random apps are having anywhere from minor to major problems, most of which I fix manually through root explorer and correcting permissions. I did flash it correctly, so its not an issue with that. That said, its a PITA to flash back to DI18 and ive been putting it off. Gonna wait until I am mid throw chucking my phone against a wall, and then I will stop myself and flash back to DI18 that evening.
Click to expand...
Click to collapse
LOL! I guess I'm not the only one but I wouldn't go as far to say it is as bad as WinMo 6.5 even though certain things do remind me of my Touch Pro 2. I have realized that this isn't Froyo. It's FRUITCAKE!
I already went back - came from rooted stock, went back unrooted so OTA will work.
My battery SUCKED - I am used to getting a normal day's use with a lot left, I was having to plug in mid afternoon/dinner time. Just like before the 9/30 update and still doing all the tricks to keep battery down, ie airplane toggle, kill all Media, check Wifi status, etc. I HATE to plug in my phone for what I consider normal usage, not high tech, downloading, playing games. I almost returned it in Sept for this, will not go there again.
And GPS did NOT work, no has codes, nothing. I am going on vacation and really need GPS, so that was the final straw.
Liked - phone did seems snappier and faster. changing dock station icons
pics and some programs came up faster
Disliked - email was really slow messaging was different, screens bright was
ok but got popups (might be me and settings)
Didn't have calibration/rotation problems, didn't check camera, no dropped calls
Just lost too much and didn't gain enough to continue. I'm glad those above did well, it could depend on how you use it as well as how it was loaded, no idea, but battery for me was nightmare and unacceptable.
No, not going back unless I have to to get the next update. Battery life is significantly improved and everything is as snappy as it was before, and my gps is working even if it comes on while 4g is connected. No crashes yet and I have been running it since about 5 minutes after the link to the update.zip was posted.
And to access bookmarks in the browser you have to press the button next to the addres bar when a page is not loading. I hope they put it back into the bottom menu though.
Edit:
I haven't made up my mind yet. Many of the froyo roms seem to have minor issues here and there, but are otherwise usable.

Who has gone back to DI18 after trying EB13?

Returned to stock DI18 yesterday after experiencing glaring issues within less than one day of using EB13. That's a testament to how bad it is. EB13 is definitely not ready for prime time and must've been rushed out with glaringly known issues to appease the public with a 2.2 release. The stability, functionality and feature loss are not worth whatever minor gains in EB13 Froyo 2.2 such as bluetooth voice dialing, in-browser Flash support, etc. For now DI18 is the way to go for stability (record 600+ hours uptime before forced reboot) and for the most part everything work or have work around. Froyo 2.2 update is a failure for Sprint in comparison to T-Mobile Vibrant because theirs actually made improvements and resolve issues.
Method of upgrade was ODIN to stock DI18, run Samsung update for EB13, boot into recover mode, cleared cache and applied factory defaults.
EB13 issues found within a short time span and was concerned what else might surface:
- Instability, phone shut down when clicking on a link in browser
- Video camera live view and recording lag. I use the video camera every day so it was glaringly obvious.
- Graphical glitch in browser when dragging page where a block of the page is offset. This is glaringly obvious too and surprised it got by QA.
- Samsung update hung towards the end on second flash, good thing for old reliable stand-alone ODIN
You should try ODINing to EB13 rather than the Samsung method, most users so far have had a nearly flawless EB13 experience
I think it really depends on the exact methods people are using to upgrade. I haven't had any glaring issues, just some small things that existed on the stock 2.1, like weird button miss presses, some keyboard lag. Just waiting for a good EB13 rom before I say anything is defunct.
I wouldnt go all the way back to eclair....try if u don't like eb13 use dk28 I haven't gone to eb 13 but if I don't like how eb13 rides im going to dk28 especially now with a OC kernal
sent from my Epic 4G
If I only had one Epic, I would stay on di18, or a custom ROM based on di18. Since I have 2 Epics, one will stay on di18 and the other will continue to beta test Froyo ROMs. There is little progress between dk28 and EB13. Most of the bugs from dk28 still exist in the latest release. I really hope our devs here can clean this mess up.
Im sad to say. But I just did. The low fps on low light video recording killed EB13 for me. Useless since I go out and do pegan nightime rituals and record the clan meeting. Now instead of having awesome night time videos off me wearing my long night hooded warlock trechcoat, it looks like a disaster video of blurr. How can I continue my rituals with this shat samsung!? Foorrrr shaaaammme!
At first I went back to a rooted/customized DI18. Unfortunately, the damn system update message kept popping up saying that an update was available and needed to install. I eventually got sick of the message and flashed the phone to Froyo using Odin. What do I have to remove to prevent the system update from trying to update my rooted phone?
OregonLAN said:
At first I went back to a rooted/customized DI18. Unfortunately, the damn system update message kept popping up saying that an update was available and needed to install. I eventually got sick of the message and flashed the phone to Froyo using Odin. What do I have to remove to prevent the system update from trying to update my rooted phone?
Click to expand...
Click to collapse
You can delete the system updater.apk in the system/app directory. This will prevent your phone from downloading and prompting you to update.
Sent from my SPH-D700 using Tapatalk
Weird, I used the update.zip method of updating my rooted epic from stock and have only had small annoying problems that were today outweighed by the single fact that the gps now locks instantly to within ten feet...indoors.
Sent from my SPH-D700 using XDA App
Color me lucky?
Used Samsung method after returning to stock. Battery, GPS et al rock solid on EB13. Enjoyed Bonsai, but am now "in the groove" - custom ROM had some nice details, but gaps as well. EB13 is a hi function 4G smarter phone for me!
I did. After the latest issue of losing 4G for 2 days straight I reinstalled eb13 and nothing. I went back to DI18 and 4G came right up, what a shocker.
EDIT: I'm running on midnight ROM eb13 4.0 and with the new wired tether apk posted in the themes and apps area, my phone is running flawlessly! I just had to correct this post.
Sent from my SPH-D700 using XDA App
I went back. I record videos all the time and that's what killed it for me. Even in still-camera mode the pictures look almost pastel, hate it.
I'll be going back to Eclair. I really didn't like anything froyo had to offer besides the updated youtube app (if I can't get that on 2.1) and flash support.
I just got froyo this morning OTA, went to class, came home and flashed it again hoping to fix my main problems. Didn't work. I just got done wiping my phone, flashing DI18, reboot, flashing EB13, and still it's still messed up.
I really don't care about the camcorder deal because I don't use it often but the laggy sleep/wake and no auto correct are really annoying for me. I only use my epic for browsing here and there and mainly texting/music. Now the audio sounds bad and on top of that my dictionary vanished. I don't even know if anyone else is having this problem because no one seems to say anything about it. Not to mention they changed the call log (the little phone button) and you can't toggle through ringtone volume>vibrate>silent any more with the volume buttons.
Gonna go back to DI18, root, remove system updater(thanks for that tip^), fix the yamaha calibutil thing, and sit happily while I wait for a stable(r) release. What a pain.
k5_ said:
What a pain.
Click to expand...
Click to collapse
Yup! Sick of it.
Well, I'm done messing with this phone. It has been in a desk drawer for 2 months waiting for an upgrade. Now that it officially has Froyo, I can advertise it as such and sell it on eBay. It's back to the EVO for me until my contract renewal comes up. From there, who knows. I loved the screen but hate the bugs!
ansong said:
Weird, I used the update.zip method of updating my rooted epic from stock and have only had small annoying problems that were today outweighed by the single fact that the gps now locks instantly to within ten feet...indoors.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I used that method too and I get gps locks in about 3 SECONDS now.....before I couldnt even get the nav to work...(Turn by turn voice directions were completely gone)
However EB13 is kinda buggy....nothing major yet just a lot of scrolling glitches and such.
im gonna wait for some eb13 roms before abandoning ship
abduljaffar said:
Im sad to say. But I just did. The low fps on low light video recording killed EB13 for me. Useless since I go out and do pegan nightime rituals and record the clan meeting. Now instead of having awesome night time videos off me wearing my long night hooded warlock trechcoat, it looks like a disaster video of blurr. How can I continue my rituals with this shat samsung!? Foorrrr shaaaammme!
Click to expand...
Click to collapse
aaaahhhhhhahahaha!
Sorry, someone had to say it.
In all seriousness, does anyone know how I can get the froyo gmail and that cool call notification bar option onto di18?
nicholishen said:
aaaahhhhhhahahaha!
Sorry, someone had to say it.
In all seriousness, does anyone know how I can get the froyo gmail and that cool call notification bar option onto di18?
Click to expand...
Click to collapse
Buy another phone.....preferably one not made by Samsung.
eb13 was anything but rushed lol
This is pretty sad. All of the people in this forum griped and moaned and yelled about not having froyo, now that they got it they dont want it. Bunch of kids
Now I dont profess to be an expert, but the low light thing is there, it is a bug and im sure they will fix it. is it a deal breaker? OMG no it isnt.

Screens that loose responsiveness on froyo.

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

Back to stock observations

Well as I found out when my SD card died it also took out my GPS, nothing will make it work again. So I put the phone back to stock, got the ED03 Froyo OTA update and took it into my verizon store, long story short I'm getting another phone tomorrow. I've been rocking on the stock froyo for a few days now and its kinda wierd since I've basically been rooted from day one. For one battery life is horrible with anything turned on, however with everything toggled off my battery life is alot better than any custom ROM or undervolted kernel. I didnt expect that. Phone isnt as laggy and i expected either. Whats really bizarre is when your stock the Market actually WORKS! No matter what I flashed my Market was always laggy, sometimes never worked at all. I usually have to start a download two or three times. This was for any ROM or kernel I tried, I assumed it was normal. Well on stock Froyo, the Market loads immediately, when I click to dowload it downloads and installs immediately. WOW! Now when I get my new phone I'm gona root it , is there anyway to get this good Market performance?
I don't have any market issues on comrom 1.3
My phone performs much better on stock ED03 than Community ROM v1.3. Is there a lot more broken with that ROM than the kernel & status bar?
For the past few days I've also been running stock ED03 with the basic bloat removed and minimal apps installed. Battery life is a bit better, but it's still not great. The phone is typically dead (or screaming for a charger) by the end of the day with normal use.
Everything seems to work with the exception of bluetooth calling (after I hang up) in my car. At first I thought it was those custom kernels causing the issue, but even the stock kernel/ROM does it.
After I hang up a call via bluetooth in my car, the phone crashes and bluetooth crashes which makes the phone hang for a minute or two. I can turn bluetooth off then on to get it to re-connect to the car, but it'll just crash again after the next call is done. Through some reading, I found that Samsung is real shady with their implementation of bluetooth. I can believe it based on our GPS issues, jacked up RIL code, weak wi-fi signal and a lower overall cell signal than other phones.
It's **** like this that keeps me from wanting the SGS II.
I'm out of the loop but it seems as it stands LG is the way to go
AuroEdge said:
I'm out of the loop but it seems as it stands LG is the way to go
Click to expand...
Click to collapse
I don't know I just played with a htc thunderbolt yesterday at a verizon store and that thing is bad ass even without 4g. If us cellular got that phone id be all over it. But from what I hear we getting the moto atrix which I'm not a huge fan of...now that moto xoom tablet on the other hand...if verizon wasn't so damn expensive.... My $.02 haha
As for the stock experience I just flashed back from cm7 to stock and all I got was pissed off haha
Sent from my SCH-I500 using XDA Premium App
ive had issues with the market in custom roms too. sometimes when i download an app instead of installing it just disappears, and i have to redownload it sometimes more than once to get it to install. but that wont make me go back to stock. custom roms/kernels are waaay better than stock and theres bound to be some issues here and there
AuroEdge said:
I'm out of the loop but it seems as it stands LG is the way to go
Click to expand...
Click to collapse
I had the LG G2x for a little over a week and it wasn't too bad. There were very minor annoying things (which I cannot remember) that reminded me of Samsung, but it wasn't as bad. It was supposed to be stock Android, but a developer soon discovered that it wasn't. It was just themed to appear stock, so I don't think the G2x currently performs as good as say a Cyanogen ROM.
Also, that phone was plagued with that reboot bug. Outside of the reboot bug and the LCD screen, it's not a bad phone. I couldn't keep it because A) the software bugs reminded me of why I don't want another Samsung. I'm not going to buy a phone and put up with that BS again - although, that phone should get heavy dev support soon; B) Maybe it was the 4" screen or the bottom heavy bezel or the bleeding LCD screen, but I felt the phone was too much of a lateral step rather than a step up from the SGS series of phones. I needed more to keep myself satisfied.
LG has the potential to do good, but so far... they're on shaky ground to me. Just like Samsung. They need to fix the reboot issues and stop copying Samsung.
As it stands I will stick it out with my Fascinate till I see a Verizon phone I really like. Which sucks because I don't see any on the horizon that look promising except for maybe the Motorola Targa. When it comes to community efforts there are two reasons I look to them from time to time -- stability and believe it or not BLN
Beware of the LG Revolution when it drops. It's not going to be a "With Google" device, meaning Verizon is probably going to beat and rape it until it's a mere shadow of it's original self.
Running stock ED03, rooted, modified to support cwr, de-binged, de-bloated, and deodexed. I did this all myself, a lot of reading of how to's. Next up I found something on converting rfs to ext4 I hope it easy enough and works well. So far its great, with the prospect of awesome, if file extention Change is doable and improves phone as much as I read about.
Sent from my SCH-I500 using XDA Premium App

Categories

Resources