Related
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.
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
Just tried the Charge/Inc2/X2 swap....got drug around for 120 minutes of nothingness. Officially the offered ended at midnight because yesterday a final version was finished to go OTA on Monday August 1st. I'm being sent another Fassy in which if problem persists I can get an original X or Inc2.
Yeah, I tried to do this today as well and looks like samsung called off the replacement for droidx, inc2 or charge due to the new update fixing all the issues. Good news for me though that they're letting me upgrade early since they know I really don't want this phone anymore. Well, better than nothing!
Fascinate is a better phone anyway. You guys should be glad the missed calls should be fixed and you can keep it.
Sent from my SCH-I500 using XDA App
johnnyplaid said:
Fascinate is a better phone anyway. You guys should be glad the missed calls should be fixed and you can keep it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Im half tempted to keep fassy over inc2.... A double up on RAM would be great tho. But i cream in my pants at SAMOLED. choices choices
Sent from O-H! via Glitchy CM7 Fascinate.
I checked for the OTA update a couple hours ago, Bing! Yep, it's here.
I'll be glad if this is the fix we need to keep enjoying our Fascinates. The temptation of a new device is certainly sweet, but this phone is a great performer. We've seen the leaps and bounds accomplished with this phone. We've all enjoyed the greatness brought to us by the developers in this forum.
Thanks All ;-)
Rockin stock ED05 OTA.....for now
Fassys are still laggy phones despite their processor and I still have that problem where buttons will seem like it's pressing by itself. I was actually doing this for my brother and he's plenty sick of this phone and wants a 4G device already after tasting the awesomeness that is my Thunderbolt with full sense 3.0 on it
It would be nice for a bigger screen, more RAM & 4G. I heard even though the screen is bigger on the Charge, resolution is worse and I don't really care for a thicker, heavier phone. I've never had problems with my buttons and such. I'm happy waiting for the Galaxy S 2, a true upgrade.
Sent from my SCH-I500 using XDA App
johnnyplaid said:
It would be nice for a bigger screen, more RAM & 4G. I heard even though the screen is bigger on the Charge, resolution is worse and I don't really care for a thicker, heavier phone. I've never had problems with my buttons and such. I'm happy waiting for the Galaxy S 2, a true upgrade.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Then us two can complain and maybe get a galaxy s 2 equivalent which is a more relevent replacement.
Sent from my I500 using Tapatalk
johnnyplaid said:
It would be nice for a bigger screen, more RAM & 4G. I heard even though the screen is bigger on the Charge, resolution is worse and I don't really care for a thicker, heavier phone. I've never had problems with my buttons and such. I'm happy waiting for the Galaxy S 2, a true upgrade.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
To each their own but I think you are wrong about the resolution of the screen of the Charge. It is truly a beautiful and clear screen. I mean I thought the Fascinate had an awesome screen... Not when compared to the Charge. Don't get me wrong. I loved the Fascinate but extremely pleased with the Charge performance wise, radio wise, and stability. So far, top notch.
Sent from my SCH-I510 using Tapatalk
Correct, to each their own but the Charge appears heavier, thicker and not nearly as attractive. I could see getting a heavier phone if they had to fit dual-core, but isn't it the same processor?
Charge & Fascinate should have same resolution except Charge is stretched over larger screen, if I'm not mistaken. That should decrease the pixel density.
I would enjoy the higher res. camera & front facing camera though.
Galaxy S 2 should embarrass almost all phones out.
ed05 did not fix anything... I still get missed calls and so have others.
IF still having issues I would continue to let Verizon know. The more we as a group complain for having the issues the more they will realize their "fix" did not work.
Well... I restored my cm7 backup last night, after trying to get a replacement upgrade yesterday (replacement fassy on the way). Then I odined the new ed05 radio. This morning I've gotten 2 voicemails with no missed calls. And my gf tried calling me a few minutes ago, but all I got was a phantom ring. I called my voicemail to stop the ringing, and 10 minutes later I got a text asking if the call came through at all.
Its hard for me to tell if it's cm7 causing problems or what... I couldn't stand that nasty touchwiz tho. I'm on the latest nightly from last night. Vzw forums seem to indicate ed05 fixes the problem. If I'm still gonna be missing calls then I want my damn upgrade to the charge!
Edit: Seems like missing calls and phantom rings are happening again during deep sleep in latest cm7 nightly. I should probably just go back to the 7/17 build. Don't much feel like messing with the stock rom to test it for missing calls. So I'll just take you guys' word on whether it fixes the problem.
In other news the replacement Fascinate the tech support guy on the phone ordered for me last night around 7:30pm showed up today at about 3:00pm. He told me not to expect it til middle of next week. Pretty awesome! But I live in Houston and apparently their warehouse is in TX somewhere. Still pretty excellent delivery time. I'm messing with the Glitch kernel on it now, hopefully it overclocks better than my original cuz it looks so shiny and new!
Sent from my SCH-I500 using XDA Premium App
I should clarify that I have only had 1 voice mail with no missed call notification since flashin the full odin ed05 package. Although imo performance and gps is alot better with ed05 vs the previous versions... phone all around operates smoother. I was getting 2 vm's with no notification a day, so it does seem like improvements were made.
Were you getting missed calls with this Rom before or after changing kernels?
Sent from my SCH-I500 using XDA App
after flashing the modified stock kernal.tar... I have since flashed back to the stock
ed05 rom/radio/kernal and will post results after a couple days. I didnt realize by flashing the modified stock kernal.tar, I was reverting back to ed01 kernal lol. The funny thing is the kernal version never changed, but maybe it dont??
droidstyle said:
after flashing the modified stock kernal.tar... I have since flashed back to the stock
ed05 rom/radio/kernal and will post results after a couple days. I didnt realize by flashing the modified stock kernal.tar, I was reverting back to ed01 kernal lol. The funny thing is the kernal version never changed, but maybe it dont??
Click to expand...
Click to collapse
Nope the kernel version doesn't change as long as you're using a Froyo kernel. You can see if you have the ED05 kernel by using Terminal Emulator and typing "cat /proc/version" and see if it's dated July 8. Anything earlier is pre-ED05.
Sent from my SCH-I500 using XDA App
scarfman4 said:
Nope the kernel version doesn't change as long as you're using a Froyo kernel. You can see if you have the ED05 kernel by using Terminal Emulator and typing "cat /proc/version" and see if it's dated July 8. Anything earlier is pre-ED05.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
ok I tried using terminal emulator and it says not found?
droidstyle said:
ok I tried using terminal emulator and it says not found?
Click to expand...
Click to collapse
How are you typing it? It should look like this:
cat /proc/version
There should be a space after the "cat" before the first forward slash. There should be no space after "proc" before the second slash.
Sent from my SCH-I500 using XDA App
scarfman4 said:
How are you typing it? It should look like this:
cat /proc/version
There should be a space after the "cat" before the first forward slash. There should be no space after "proc" before the second slash.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
ahh didnt notice the space after cat lol!
Here is the results:
Linux version 2.6.32.9(gcc version 4.4.1) #1 Fri July 8 18:12:14 KST 2011
How many ppl still have there evo since launch with no problems. I never had any problems with my evo since launch.
Sent from my PC36100 using Tapatalk
Me. No cracked camera lens, no screen lifting, no light leakage, no dead pixels, rooted about a week after I got it, never had a boot loop, never lost any data . . . it's been a good ride, and I'm not through yet.
I've had mine since launch and haven't had a single problem. Been rooted the entire time. I generally tend to take pretty good care of my phones though. I'm extra careful now after learning of this GB mess. I'm pretty sure that if I were to break my OG now, I'd try and fix it myself instead of being stuck on stock after an exchange.
Sent from my PC36100 using XDA App
Add me to the list. I have not had one issue.
I also never had 1 issue... UNTIL.... I foolishly accepted the GB update, Now the phone is slow as ****, has random reboots, and freeze-ups, as well as a slew of other bugginess, I was never rooted before, nor had the intention to root, but after this mess that sprint has created, I will root once I can, and enjoy the features I paid for over a year ago....
I've had mine since launch but I do have issues. I have burn ins, power button crack and phone is separating at the top but I'm waiting to do a return until there is root for 2.3.3.
Pocket posted....
not a single problem here, ever
I haven't had a problem either but I haven't had it since launch either lol but thanks to Sprint and there stupid pop up updates I accidentally updated to 2.3.3 and waiting for my turn to experience this thing we call rooting
Sent from my PC36100 using XDA App
Unfortunately I'm on my third one. The first one wouldn't allow me to save pictures so they gave me a new one. Eventually I found out I had a bad media card. The second one charging port went bad.
Sent from my PC36100 using XDA Premium App
I still have my original evo with no screen protector pre-ordered it from best buy ! Only one minor scatch on the screen. No other problems ! Rooted running Deck rom right now .
Running decks rom too best aosp rom so far. Does anything have to do with the hardware version and the problems everyone's having like cracked power buttons, Light leakage etc.
Sent from my PC36100 using Tapatalk
Notification bar area doesn't work, camera lens fixed a few weeks ago, crack at power button, crack at volume rocker, light leakage, and a little bit of screen lifting. Oh and usb port a little fudged up. Gotta do the jingle and dance to get it to charge. All these issues and yet It's still the most awesomest ever.
Sent from the Evo
Mine's been good to me as well, only had to have the screen replaced once when it was non-reactive. Other than that it's been fine! Even survived a swim in a lake!
Had mine 2 weeks no. No issues yet.Awaiting root!!!
Got mine on June 4 (launch day) and haven't had a single problem. Been rooted for 5 months now. I just fell back in love with my phone after I flashed MIUI. I was waiting for the Samsung Galaxy SII but now I feel I can keep my EVO for at least another year.
No problems here...
Sent from my PC36100 using XDA Premium App
Not 1 problem! Love my evo
Sent from my PC36100 using XDA Premium App
Have my original still. Am pleased to say it has not given me any problems at all, and I tend to be hard on phones. I think this phone is in the best shape for its age of any phone I've just about ever had, lol.
Had it since launch. No problems whatsoever. Love my evo.
Sent from my PC36100 using XDA App
I just switched back to my evo for a bit from the shift i got in may. I've had the OG evo since launch, no issues until last may other than some software stuff when i was messing around too much while rooting (lol). In may the phone fell out of my pocket and messed up the unlock button. It is now extremely difficult to press. With no lock and screen off and lock widget however, there is no need for it. I just reactivated the EVO yesterday and rooted, im rockin MikG 2.XX and lovin it. I might just have to roll with it until the new shift OTA is released and I can root it
Don't know what the hell is going on but it's so frustrating I am about to throw my phone out the window. Recently I upgraded to stock plus v3.01 ROM and also Ext4 4 ALL kernel since I was running into the dreaded data/data memory full issue. Everything seems to be working fine until recently the phone would slow to a crawl right around midnight, I would be watcing a flash video clip before midnight, then right at 12, everything just slow down and nothing I do would resolve this...I can reboot, take the battery out..etc..phone would still be super slow, pretty much the same way until next morning. GoLauncher EX would crash all the time during this time as well, is if there's some kind of ghost process running in the background sucking up all the resources. I checked Mybackup and doesn't look like there's any schedule backup service...so I am pulling my hair out still don't know what's wrong. Anyone else experienced this before, any idea what can be causing this?
This happened to me when i was using that same rom! What i did was just install a different rom.
Try looking on Ebay for a new flux-capacitor for it they always go bad
I had this ROM too... it was cool, but a battery hog.... Back to CM7 Nightly's.... shouldn't have left to begin with....
1. does not belong in this forum
2. try asking the developer, or even in the ROM's forum
Too much porn. Those midnight shows will do it.
Sent from my ADR6300 using XDA App
Thanks for the feedback..looks like the ROM is the culprit..time to upgrade to something else
Cool story bro
CM7 nightly
Haven't had any problems with Stock+ regarding this issue....
definitely very strange.....
Very strange issue. Has it been reported to the ROMs dev?