The response on the touch screen for my atrix is all screwed up, I was wondering if anyone else had these issues.
I first got the phone in april and it worked flawlessly, for the last week the touch screen response has been really weird. sometimes it doesn't recognize input at all, other times it thinks i'm touching somewhere else, it often randomly selects a point on the screen completely on its own.
i'm unlocked, have a custom recovery. i started getting the issues on alien3, i flashed a new custom recovery and alien4 and i still have the problems.
i'm worried its hardware at this point, and i don't know what options i have for warranty since i got it on ebay. am i screwed?
First try again flashing everything from the start.
1. Flash the newest recovery: http://forum.xda-developers.com/showthread.php?t=1204500
2. Flash this radio for GingerBread ROMS: http://forum.xda-developers.com/showthread.php?t=1163009
3. FULL WIPE - Dalvik, Cache and data. (Also internal&external SD if you want to)
4. Flash any FULL WIPE ROM you want, like Alien #4.
5. If still didn't resolve the problem and you want to try more stuff, try flashing other kernel ?
Like: http://forum.xda-developers.com/showthread.php?t=1156040
You can try also flashing full SBF, read more about it here: http://forum.xda-developers.com/showthread.php?t=1136261
Try Touchscreen Booster from the Market.
Went through the same pain and read everything on XDA until I found a thread about the app.
Was driving me nuts but have had a stable screen for 3 weeks now.
I am using Super Optimized setting.
Sent from my MB860 using XDA App
If you problem doesn't get solved by clean flashing a new ROM, then it's a hardware issues -> as in "you need to replace digitizer".
Andy_Thatcher said:
Try Touchscreen Booster from the Market.
Went through the same pain and read everything on XDA until I found a thread about the app.
Was driving me nuts but have had a stable screen for 3 weeks now.
I am using Super Optimized setting.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+1 this works.
Sent from my MB860 using XDA Premium App
Im having the same issues and went about flashing the whole phone to no avail. I will for sure try touchscreen booster and post my results. If that doesnt help, is it the digitizer that needs replacing or the lcd? Digitizers are a lot cheaper on eBay lol
The only app I found says its for the galaxy. Installed it anyways, selected "super optimized settings" and so far so good. Thanks so much Andy_Thatcher!!
Andy_Thatcher said:
Try Touchscreen Booster from the Market.
Went through the same pain and read everything on XDA until I found a thread about the app.
Was driving me nuts but have had a stable screen for 3 weeks now.
I am using Super Optimized setting.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
this actually seems to be helping a lot. thank you. i will try a new kernel in the future but this is working great right now.
Apologies, did mean the Galaxy app.
Sent from my MB860 using XDA App
I have these issues to. They appeared randomly and there are random periods where it goes away, then comes back, sometimes worse than others. The SGS Touchscreen Booster app definitely helps, but it doesn't make it go away for me.
The only thing I haven't tried listed in this thread yet is flashing a new Kernel.
I've considered buying a new digitizer and replacing it myself, but the fact that the occurs so randomly and can even sometimes stop after rotating the screen, I'm very hesitant to do so.
i have tried this, but the problem still persist. I tried Optimized & Super Optimized settings, but its still the same
Even though the affects sound the same the cause maybe different. I know that sounds unlikely but I know that the Screen Booster worked for me.
There are a couple of other paths you may want to look at.
I was always convinced that the issue was not hardware based otherwise no matter what I did to the software it wouldn't have changed the fault but software changes did.
In my case before I implemented the app I would get a few hours respite by installing another base.
I have never used AT&T's OTA for Gingerbread so have been able to to SBF to what ever build I liked. For a while going to the initial Froyo build worked but as said only for a day at most. I had reached the point where I didn't care if it was Froyo or Gingerbread I just wanted a working phone.
No doubt I will get some flack for that comment however my phone has never hard bricked and I have been up and down the builds like a man possessed.
This is where I put the statutory do this at your own risk. It worked for me but I do not know the history of your device.
Then I came across this http://forum.xda-developers.com/showthread.php?t=1131649 thread.
It worked ! Well for a couple of days.
At that point I started get get some respite to SBF'ing to Pudding 2.3.4 Pre-Root.
My trouble with all of this is that I do not understand the issue. I suspect it was a software glitch I created due to messing with builds. Screen Booster worked for me and if I were you I would spend a little more time before going down the other paths.
Again how I got it to work was as follows.
Install.
Set to Super Optimized, initially there was little change in the behaviour of the phone and I thought it was a bust.
Rebooted
Set to Super Optimized again and it started working.
If anyone should know why this screen behaviour happens please let me know. I am close to getting another Atrix so I can take Screen Booster off this one to try and figure it out.
Related
Ever since I flashed EB01 I have been having problems with screen responsiveness, It will seem to work fine then after awhile will work selectively.
When I had voodoo installed, it started to do it I was running superclean 2.4
I flashed today back to EB01 Stock rooted non-voodoo, was still seeing it after awhile.
I also just flashed MIUI to play with today, and still am seeing it.
Baseband. EB01
Kernel: 2.6.32.9 [email protected] #1
I have the same problem, with any ROM that is not an official ROM from Verizon. It seems to be happening as soon as I root it. It is intermittent and locking and then unlocking the screen fixes it.
Sent from my froyo'd Fascinate
Mine works fine.
glenniosaurus said:
Ever since I flashed EB01 I have been having problems with screen responsiveness, It will seem to work fine then after awhile will work selectively.
When I had voodoo installed, it started to do it I was running superclean 2.4
I flashed today back to EB01 Stock rooted non-voodoo, was still seeing it after awhile.
I also just flashed MIUI to play with today, and still am seeing it.
Baseband. EB01
Kernel: 2.6.32.9 [email protected] #1
Click to expand...
Click to collapse
First...post questions in general. Second did you wipe data prior to instal?
dalrym05 said:
Mine works fine.
Click to expand...
Click to collapse
And what was the purpose of your response in this thread?
What launcher are you using? I had this problem and switched launchers from Zeam back to Launcher Pro, when I did that, all my lag issues with screen responsiveness were fixed.
jenisiz said:
And what was the purpose of your response in this thread?
Click to expand...
Click to collapse
Same as yours pointing his out. Seriously many people here need to take a chill pill. In all reality his did help as it shows that he does not have the problem. The more people that have the problem the bigger it is. This helps weed it out.
I had this problem last night trying to press the h key. I am running SC 2.4
Sent from my SCH-I500 using XDA App
happens to me also. I wonder why it dosnt happen to everyone??? And yes, i wiped and flashed.
Happens to me too. Seems to get worse with time. I was running superclean but flashed back to stock because the responsiveness got so bad my phone wasn't really usable. Happening again with debloated froyo too
It's happened to me on every Froyo ROM, even vanilla on occasion. It's probably just Samsung's ****ty kernel and so there's nothing much that can be done until there's source to work with.
Sent from my SCH-I500 using XDA App
I think I might have found a solution. I went into stock recovery and wiped cache. After a reboot I no longer have the responsiveness issues.
Edit: unfortunately I still have the unresponsiveness issues...seems it was temporary fix. Also, it is always the middle of my screen from top to bottom which becomes unresponsive. How about the rest of you guys?
Sent from my froyo'd Fascinate
cstrife999 said:
Same as yours pointing his out. Seriously many people here need to take a chill pill. In all reality his did help as it shows that he does not have the problem. The more people that have the problem the bigger it is. This helps weed it out.
Click to expand...
Click to collapse
His post contributed nothing as it provided no useful information to the op. He's looking for an ans...who cares if it worked for him. If that's the case we would have over a hundred posts pop up in here saying "mine works". If that's what you're going to say then at least provide some information the op cam use.
I too have been perplexed with this problem. Posted up in general but no solution has been found. I usually get so annoyed I go back to eclair for a while till I get ambitious enough to try again.
I will also point out that I loose all screen sensitivity when the charger is plugged in. Yes, stock charger and does not do this at all on eclair.
http://forum.xda-developers.com/showthread.php?t=957150
My phone and girls phone do this, mine is on sc2.4, hers is on sc2.2.
Its only slightly annoying at the moment for me, but she texts a lot and complains about the keyboard not working all the time.
The only unresponsiveness that I've noticed is that when I need to end a call, I find that I frequently have to tap "End" multiple times.
I'm also running Beautiful Widgets, so I assumed that that might have something to do with it.
Since BW requires an extra screen tap when coming out of a locked screen, I was assuming it was just a bug with the widget until I saw these posts.
Ok look if your useing set cpu and you set it to on demand your going to see lag but if you have this app and set it to conservative you will not have lag. If you are useing this app this will help you if thats your prob. If not them I suggest you DL'ed it to help your over all speed. I'm useing go launcher ex. Also as a side note I don't have any prob with my phone.
hmmmmmmmmm
calebv2 said:
Ok look if your useing set cpu and you set it to on demand your going to see lag but if you have this app and set it to conservative you will not have lag. If you are useing this app this will help you if thats your prob. If not them I suggest you DL'ed it to help your over all speed. I'm useing go launcher ex. Also as a side note I don't have any prob with my phone.
Click to expand...
Click to collapse
That's a great point. I never thought of that but I had also been noticing some lag while set cpu was set to on demand. Switched to conservative and did seem to notice a difference. Thanks.
I've always had SetCPU on conservative, 1GHz max and 200MHz min. Maybe I don't see it as much as you all say but it's enough for me to notice.
Sent from my SCH-I500 using XDA App
A week ago I Odin'd back to stock and upgraded to the official 2.2 VIA Kies Mini. I have not rooted since or really even restored any of my old apps. No mods, just a stock Vibrant now. While I was playing WordFeud the phone locked up for about 20 to 30 seconds then on the screen it stated a screenshot has been taken. I then checked the Gallery and sure enough there was a picture of the screen. My question is has anyone seen this or know what happened. I checked the WorFeud app help and it didn't mention anything about a screen capture feature. Is there some sort of button combination on the new 2.2 Release that allows for screen captures to be taken? I was pretty confused by this, please let me know your thoughts and/or experiences.
OK, I see others have encountered this too and I would of found that if I searched correctly, as in spell correctly. OK, I see that people are saying to hold the back button and hit the home or menu button. I have tried these methods and have yet to make it work again. Either way, since this is sort of covered already, without a clear answer though, MODS feel free to delete.
Crap, didn't see your thread.
I encountered the same thing today and it was pretty nice. Still trying to figure out how to do it. Its a nice feature!
I did it too....im not rooted at this time. Cant figure it out.....
Sent from my SGH-T959 using XDA App
Yeah I've done that too accidentally. Don't know how though.
Updating to Stock 2.2 from Kies is probably your first mistake, that ROM is so bad I couldn't stand it for more than a day. Flashed Trigger and reborn I was. Plan into getting a custom ROM for your phone because screenshots are not the only thing you will encounter annoying from Samsung's Froyo.
I ended up with screen shots in my gallery and I have no idea how they got there. There was never a notification or anything.
There is something built in, but I don't think the Vibrant really supports multitouch on the capacitive buttons. My girlfriend can do this on command, but only in the mms app. She clicks back, and when she feels a delayed haptic feedback, she pushes home and it works everytime.
Sent from my SGH-T959 using XDA App
Yes I have had the same thing happen, it definitely a timing thing I tried to master but only get 10% effective so I stay with shoot me,, just a weird glitch in the phone
roumenjr said:
Updating to Stock 2.2 from Kies is probably your first mistake, that ROM is so bad I couldn't stand it for more than a day. Flashed Trigger and reborn I was. Plan into getting a custom ROM for your phone because screenshots are not the only thing you will encounter annoying from Samsung's Froyo.
Click to expand...
Click to collapse
Yeah, I was rocking Macnut R14 for a while after trying a few others. I updated to Samsung 2.2 to test out because a friend was thinking of trying it and asked if I would try it first. I was bored of it within a hour I think but gave it a few days. Bionix and DOW Kernal on it now.
Hi all, I have bought my X10 some months ago.
I upgraded regularly my phone up to the first dualtouch release (rooting the phone regularly).
I experienced random problems with the stock roms (reboots) when using some applications and in particular when data is on.
The battery used to go hot sometimes and I had to remove it and put it back in place so that the phone could work again.
I have tried some 2.2 custom roms and the most stable I have found is the tripnmiui 2.2, probably in my case more stable than the stock rom.
I went back to the last 2.1 stock release (2.1.B.0.1) but the video recording works badly and I have reboots when capturing videos generally after 40 seconds.
I have noticed it reboots with trip's rom as well if I take videos in 720p.
I have not tried to go back to older stock releases supposing the last one was performing better.
Would you please suggest me a 2.1 stock rom or a 2.1 custom rom where the camera and video work just fine and I have little battery problems?
If there is a 2.2 rom where I can use video and camera like in the stock rom, would you please suggest it to me?
I am really pissed off.
I am an Ericsson employee (not SE) and I bought this phone so that when I am at the customer they do not see me hanging around with an Apple or a HTC or a Samsung (I received some comments in the past about going around with a Nokia).
But if this phone is so bad I swear I am gonna change it asap and never get another one (in Italy they unfortunately give us company phones which are more like K550, like stone age phones which I will never use).
If there is a way to fix it good, hoping that we get 2.3 asap, either way this is gonna go for sale and I'll get a new samsung or a HTC maybe.
Please help me if you can.
The 2.1 ROM bitsnacker by go3asy with camera enhancements and speed enhancers and performance mods is awesome. Plus it looks cool. No problems at all. Give it a look in the development section.
I personally love the phone. Gingerbread hopefully comes at the end of the month. Maybe.
If you need any links for things I will post them when I get home if you need any or help the flashing stuff.
Just let me know or others know.
Sent from my X10i using XDA Premium App
Any of you have experienced camera problems (reboots) with stock roms in particular the most recent when capturing at 720p?
It is really strange in my opinion. I also got random reboots while using applications and that battery priblem (it becomes hot at times when data is on and the phone starts rebooting or does not turn on for a while).
Thanks Voelker, I will surely give it a try. I guess it would be great if you can provide the link as well. Thanks in advance.
LordRevan said:
Any of you have experienced camera problems (reboots) with stock roms in particular the most recent when capturing at 720p?
It is really strange in my opinion. I also got random reboots while using applications and that battery priblem (it becomes hot at times when data is on and the phone starts rebooting or does not turn on for a while).
Thanks Voelker, I will surely give it a try. I guess it would be great if you can provide the link as well. Thanks in advance.
Click to expand...
Click to collapse
I will provide a link when I get home to a computer in this post.
Sent from my X10i using XDA Premium App
Ok, I have found the ROM and installed it.
I still have an issue with my video recording in HD.
Recording stops after a few seconds and the system reboots.
Using bb_54 according to the build.
I am thinking something is wrong with the camera.
I have seen that there is a post with a zip file to fix the camera.
Maybe something went wrong in some of the flashing???
LordRevan said:
Ok, I have found the ROM and installed it.
I still have an issue with my video recording in HD.
Recording stops after a few seconds and the system reboots.
Using bb_54 according to the build.
I am thinking something is wrong with the camera.
I have seen that there is a post with a zip file to fix the camera.
Maybe something went wrong in some of the flashing???
Click to expand...
Click to collapse
Yeah the reboots shouldn't happen. You can use flashtool over or seus to see if that can repair it. But I hope your problem gets solved.
Sent from my X10i using XDA Premium App
The key words here is that you mention the overheating.
This was caused by a early baseband that overheated the chipset.
So you have residual damage on the motherboard and that causes the reboots.
I had the same issue.. after they replaced my motherboard all was good.
Overheating happens really rarely to be honest though.
I don't understand if there is a relation between overheating and video not working.
I just wanted to understand where the camera firmware resides and if and how it is flashed when changing baseband/rom.
Ok, last test performed. Went back to an old stock 2.1 release (2.1.A.435). Video recording in HD still causing reboot after a variable amount of time. Some other random reboots happen and the overheating problem happen sometimes as well. I would definitely say it is a hardware problem then. I will try to give the phone to an authorized maintenance center.
The X10 is now having maintenance. Let's just hope they won't waste my time trying upgrades or SW repairs.
My launcher keeps freezing up. Have to force stop it from the apps menu. Any help?
malaeus said:
My launcher keeps freezing up. Have to force stop it from the apps menu. Any help?
Click to expand...
Click to collapse
Not that I know of, have you also tried clearing its cache? Maybe even go so far as to clear the cache and data? If neither of those helps, then something's been tweaked or corrupted in your system; at which point a factory reset/manual update would do the trick I imagine. Be sure to back up all your apps and important information off the internal SD card if it comes to that though.
*EDIT:
Just noticed in your signature that you're unlocked and on a custom ROM. Have you tried a third-party launcher? Could it be an issue with the ROM itself?
Was kinda afraid of that. Its a stock blob in CWM wrapper. So it "shouldn't" be corruption but.... we all know how that goes. I've wiped cache etc and even reinstalled the launcher with root. Same issue develops after a few hours.
Tnx for your help. Which other custom rom would you recommend? I wanna stay mostly stock.
malaeus said:
Was kinda afraid of that. Its a stock blob in CWM wrapper. So it "shouldn't" be corruption but.... we all know how that goes. I've wiped cache etc and even reinstalled the launcher with root. Same issue develops after a few hours.
Tnx for your help. Which other custom rom would you recommend? I wanna stay mostly stock.
Click to expand...
Click to collapse
Haha, no clue, I haven't watched the dev thread as well as I should I haven't unlocked just yet due to the drop of warranty and lack of proper nvflash. I would do the same honestly, try and keep stock. Maybe just try an earlier version. I'll have a look at the dev section and see if anything pops out. Have you checked the md5 sums and everything, or just tried redownloading?
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
buxtahuda said:
Haha, no clue, I haven't watched the dev thread as well as I should :embarrassed: I haven't unlocked just yet due to the drop of warranty and lack of proper nvflash. I would do the same honestly, try and keep stock. Maybe just try an earlier version. I'll have a look at the dev section and see if anything pops out. Have you checked the md5 sums and everything, or just tried redownloading?
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
Click to expand...
Click to collapse
I've redownloaded 3 times. Everything else works nicely. I did test the motley kernel, however I've since reverted to stock kernel. And I've wiped and reinstalled after that when the launcher kept crashing. I might give virtuous a try if this continues.
Aye, seems to me as though the ROM just isn't handling the launcher well or has some kind of mem leak or something. Try out Virtuous Prime or Primalicious, they both seem pretty true to stock but Primalicious has less minimalist icons. And it is the stock launcher right?
buxtahuda said:
Aye, seems to me as though the ROM just isn't handling the launcher well or has some kind of mem leak or something. Try out Virtuous Prime or Primalicious, they both seem pretty true to stock but Primalicious has less minimalist icons. And it is the stock launcher right?
Click to expand...
Click to collapse
actually. now both launchers i use crash in the same way.
all items disappear. however i can still swipe, and if i randomly tap things open that should be visible.
i use stock asus launcher. as well as GO launcher HD
it just seems that after awhile of either using or sitting the tablet, the launcher just fails. and it takes me frantically tapping it to bring up the "not responding" text.
otherwise i just go into settings/apps and kill it.
thanks for your help. im going to try out a couple different ROMs to see if it can solve this issue.
seems every device i have ends up with very weird unexplainable issues. and ive changed up everything from device to device (you know, scientific method and whatnot) and can not seem to isolate what causes these problems.
malaeus said:
actually. now both launchers i use crash in the same way.
all items disappear. however i can still swipe, and if i randomly tap things open that should be visible.
i use stock asus launcher. as well as GO launcher HD
it just seems that after awhile of either using or sitting the tablet, the launcher just fails. and it takes me frantically tapping it to bring up the "not responding" text.
otherwise i just go into settings/apps and kill it.
thanks for your help. im going to try out a couple different ROMs to see if it can solve this issue.
seems every device i have ends up with very weird unexplainable issues. and ive changed up everything from device to device (you know, scientific method and whatnot) and can not seem to isolate what causes these problems.
Click to expand...
Click to collapse
Welcome to electronics and programming Lol, really the most important thing is to start off strong and have a solid base to build from. We haven't though, we're still having to shuffle official updates to try and reach that point. Although I have faith in our dev's and they've worked toward fixing a lot of the issues already, it will only get better once true stock gets stable and the dev's get proper nvflash access. Until then I'm afraid things will be pretty sporadic. That's what we get for falling for all the hype on a brand new device.
*EDIT:
Also, have you set your I/O scheduler to something other than noop? Check out ATP Tweak in the dev sub-forum and see if that doesn't help.
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
buxtahuda said:
Welcome to electronics and programming Lol, really the most important thing is to start off strong and have a solid base to build from. We haven't though, we're still having to shuffle official updates to try and reach that point. Although I have faith in our dev's and they've worked toward fixing a lot of the issues already, it will only get better once true stock gets stable and the dev's get proper nvflash access. Until then I'm afraid things will be pretty sporadic. That's what we get for falling for all the hype on a brand new device.
*EDIT:
Also, have you set your I/O scheduler to something other than noop? Check out ATP Tweak in the dev sub-forum and see if that doesn't help.
Sent from my Transformer Prime TF201 using XDA Premium HD via my tethered HTC Vision
Click to expand...
Click to collapse
yes, i am sadly very used to unstable builds on my devices. but, its always better than what the original manufacturers release.
and thats just the price to be paid for staying on the bleeding edge of this tech.
i am fairly experienced with the basics of flashing ROM's and beta testing, but i am faaaar from being a programmer/developer so i am not quite sure how to change the I/O scheduler anything past using pre-done scripts like the V8 Supercharger.
ill check out that tweak, thank you again for your help.
I installed CM10 on my Droid X2 and I just couldn't get past the screen sensitivity -- everything was jumpy to the point where the phone wasn't usable. Is this something others have noticed, too? Is there a way to adjust the sensitivity?
sjwoo said:
I installed CM10 on my Droid X2 and I just couldn't get past the screen sensitivity -- everything was jumpy to the point where the phone wasn't usable. Is this something others have noticed, too? Is there a way to adjust the sensitivity?
Click to expand...
Click to collapse
What do you mean it was jumpy? Are you saying it is too sensitive? I dont know of any way to adjust it but I have no problems with it.
jsgraphicart said:
What do you mean it was jumpy? Are you saying it is too sensitive? I dont know of any way to adjust it but I have no problems with it.
Click to expand...
Click to collapse
Yeah, way too sensitive. Damn, maybe it's just my Droid X2. I'd scroll up an down and it was just super sensitive, moving up and down at the slightest touch.
- Sung
Also -- the screen seemed to flicker way more. I think some of it was intentional (the screen dimming and brightening). As much as I liked the look, I went back to CM7.
I haven't noticed any screen flicker, or too sensitive touch
It has seemed less sensitive, to me
You are not the only one. Had same thing on my DX2. It happened 4-5 times.
I just kept trying to get "power off / reboot" screen and reboot. After reboot everything was good.
Also had faster battery drain, purchased a 3600mAh and it would almost last 10 hours on CM10.
Two days ago went back to CM7, battery will last 14-16 hours with same usage.
Going to wait for next CM10 release to try again.
Sent from my MB870 using xda app-developers app
sjwoo said:
Also -- the screen seemed to flicker way more. I think some of it was intentional (the screen dimming and brightening). As much as I liked the look, I went back to CM7.
Click to expand...
Click to collapse
Thasian483 said:
You are not the only one. Had same thing on my DX2. It happened 4-5 times.
I just kept trying to get "power off / reboot" screen and reboot. After reboot everything was good.
Also had faster battery drain, purchased a 3600mAh and it would almost last 10 hours on CM10.
Two days ago went back to CM7, battery will last 14-16 hours with same usage.
Going to wait for next CM10 release to try again.
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
You guys need to understand that this ROM will never be perfect. Even the next update will have issues.
Understand, also understand ANY ROM can have issues, including Vz ROMs.
It's about what works for each person, in this case I am waiting for the next release, please don't get defensive because we had issues. They happened, no big deal, we have made decisions to move back to CM7.
I happen to think DZK has done a great job with CM10 and I will be moving back.
Sent from my MB870 using xda app-developers app
Thasian483 said:
Understand, also understand ANY ROM can have issues, including Vz ROMs.
It's about what works for each person, in this case I am waiting for the next release, please don't get defensive because we had issues. They happened, no big deal, we have made decisions to move back to CM7.
I happen to think DZK has done a great job with CM10 and I will be moving back.
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Oh I'm not being defensive. Sorry to come off that way. I just see that you guys are newcomers to the forums. A lot of newcomers have been posting about issues not understanding that our Droid X2 is not like other phones that get custom ROMs. Our CM10 is not really complete and most likely never will be because motorola hates us and doesnt want to unlock our bootloaders. If you guys are new to the DX2, I didnt want you expecting a full featured bugless ROM like, lets say the Galaxy Nexus would get. Even though its CM10, we are running it on a Gingerbread Kernel which will always cause issues. That, along with not being able to change or update the drivers doesnt help. Thats why I said even the next update will most likely have the same issues. Most of us just chose to deal with them.
jsgraphicart said:
Oh I'm not being defensive. Sorry to come off that way. I just see that you guys are newcomers to the forums. A lot of newcomers have been posting about issues not understanding that our Droid X2 is not like other phones that get custom ROMs. Our CM10 is not really complete and most likely never will be because motorola hates us and doesnt want to unlock our bootloaders. If you guys are new to the DX2, I didnt want you expecting a full featured bugless ROM like, lets say the Galaxy Nexus would get. Even though its CM10, we are running it on a Gingerbread Kernel which will always cause issues. That, along with not being able to change or update the drivers doesnt help. Thats why I said even the next update will most likely have the same issues. Most of us just chose to deal with them.
Click to expand...
Click to collapse
I wasn't aware of the Motorola situation when I purchased the DX2, but quickly found out. I came from the Samsung world (Fascinate) as my last device and it seemed custom ROM's were very easy. With the DX2 it has been anything but easy. But for now really happy with the device overall and the CM10 ROM will make it great. The primary reason for my move back to CM7 was a call issue that seems to be well documented. If it isn't corrected with the new version of CM10 I will make adjustments and stick with it. Also the DX2 community here on XDA is great.
I haven't had the any call issues, but I make/receive very few calls
mostly texts and emails
jsgraphicart said:
Oh I'm not being defensive. Sorry to come off that way. I just see that you guys are newcomers to the forums. A lot of newcomers have been posting about issues not understanding that our Droid X2 is not like other phones that get custom ROMs. Our CM10 is not really complete and most likely never will be because motorola hates us and doesnt want to unlock our bootloaders. If you guys are new to the DX2, I didnt want you expecting a full featured bugless ROM like, lets say the Galaxy Nexus would get. Even though its CM10, we are running it on a Gingerbread Kernel which will always cause issues. That, along with not being able to change or update the drivers doesnt help. Thats why I said even the next update will most likely have the same issues. Most of us just chose to deal with them.
Click to expand...
Click to collapse
Hey there -- just wanted to also say that I hope I wasn't coming off as a complainer (which probably meant I was!). I'm totally and absolutely grateful for all of dragonkiller's work on porting CM. I HATED my Droid X2 with BLUR -- and it has been a great joy to use since I switched to CM7.2.
I do wonder, though, that Jellybean requires a more powerful processor? CM10, outside of the sensitivity issue, felt slower in every way. I just may keep CM7.2 on this phone forever -- it's just a great ROM.
If JB felt slower to you then something is wrong. Did you install it from a clean 2.3.4 SBF?
Sent from my JB'd X2
GoClifGo05 said:
If JB felt slower to you then something is wrong. Did you install it from a clean 2.3.4 SBF?
Sent from my JB'd X2
Click to expand...
Click to collapse
Actually upgraded from CM7 to CM10 first time. Since moving back to CM7, I did an SBF with a clean install of CM10 and things are MUCH BETTER. Not going back at this point. This is only day two, but things are good. I did figure out that when I installed an app that CM10 did not like the screen started acting strange, but getting rid of the app and rebooting solved the issue.
I did end up with one strange problem, still working on it. I used Titanium to restore most of my apps, but wanted to do a clean install on Flash Player. So went in found the apk from my file mgr, selected "install", went to what I call the Android Install screen with two buttons at the bottom (Cancel & Install), tried to select the Install, nothing happened. I do have "Unknown Sources" checked in Security. I have tried other apk's just to test and none seem to work. Tried to move the apk's to the SD0 card, and that had no effect either. The strange thing, I had Flash Player working before going back to CM7.