I just recently flashed eclipse 2.1 over my the old eclipse I think it was 2.0.4 or something like that. Anyway, in my opinion it is the best rom for the x2 so thanks goes out to him for working hard keeping it relevant in this every so updating community. So, my problem is, after flashing to eclipse 2.1 my phone will not flip from vertical to horizontal when trying to type or really do anything for that matter. I know it's not a problem with the device because when I load "super stickman golf" the phone has no problem switching. My question is, 1) is there anyone else having this problem and 2) can it be fixed? I love this community and I think it's great to see developers who aren't being paid work so hard to bring up roms that add value to our phones. Thanks for taking the time to read this post and have a great afternoon/morning/day.
Just tried this, seems to be working for me fine. Went rom 1.2 rc1 tho to 2,1.
Yea, I may have changed something in settings without knowing I guess. Seems as if everyone would be having the same problem, I may just reflash and see if that fixes the problem. Thanks for the quick response.
Fixed it, I'm an idiot. It was just something in the settings that was unchecked.
DroidX2User said:
Fixed it, I'm an idiot. It was just something in the settings that was unchecked.
Click to expand...
Click to collapse
Why is everyone hesitant to doing an SBF?? Clean slate = Clean install
Dee Ex Two - See Em Seven
Pixelation said:
Why is everyone hesitant to doing an SBF?? Clean slate = Clean install
Click to expand...
Click to collapse
because NOR flash memory has a finite number of write cycles (less than the NAND flash memory like your SD card!) and it IS possible to flash your phone too much. I did it to my MyTouch3G, can't do anything to it now, can't even wipe it, nothing saves it just goes through the motions, It's as read only as you can get.
like every time it reboots I have to go through initial setup in an intolerably slow way.
I mean, it functions, which is impressive given the situation, but consider this.
Cheapxj said:
because NOR flash memory has a finite number of write cycles (less than the NAND flash memory like your SD card!) and it IS possible to flash your phone too much. I did it to my MyTouch3G, can't do anything to it now, can't even wipe it, nothing saves it just goes through the motions, It's as read only as you can get.
like every time it reboots I have to go through initial setup in an intolerably slow way.
I mean, it functions, which is impressive given the situation, but consider this.
Click to expand...
Click to collapse
How did you get to that "overflash" point? That's nuts and Im sorry you're going through that!
Sent from my MB870 using xda premium
Related
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.
ok guys...this is killing me. my phone is absurdly laggy. It got bad with stock gingerbread, got worse with CM9, and now with CM10. lately, when I get a phone call, I can't even answer the phone because just dragging the slider lags so much the whole phone locks up. when I get to my desktop I need to use my task killer to kill everything before I can do anything.
what gives? is this the hardware? does everyone have this same problem? or is it unique to me? I'm ready to throw it through a wall.
no widgets running right now. and when I check running apps, there really isn't much going on. I'm about ready to go back to stock and see what happens. I got the phone a year ago and can't live through another year of this. heck, I got an iphone 4s from work and don't want to consider using it in place of my android.
help me please.
Wipe cache and dalvik in BSR and see if that helps. If not I would SBF back to 2.3.4 and start fresh. When on CM10 I see very little lag.
Sent from my JB'd X2
Are you running any scripts? One thing I noticed after flashing CM10 was that some scripts caused more problems than they fixed, namely V6 Supercharger and KAK.
nope, no scripts. I did flash CM10 over CM9, and the same issue existed in CM9 so maybe it's just carried forward from that. Maybe I will have to sbf and start from scratch as suggested.
thanks
If you just simply flash a ROM over another without wiping data/cache/dalvik, you will most likely experience these types of problems. I would try first what was suggested above, wipe cache and dalvik. If nothing works SBF. I would say to flash the ROM again but we cant flash ROMs once in CM10.
I suggest wiping your SD/Phone memory, Wiping the Cache, and Dalvic cache and see if stock Gingerbread is still laggy.
Croda said:
ok guys...this is killing me. my phone is absurdly laggy. It got bad with stock gingerbread, got worse with CM9, and now with CM10. lately, when I get a phone call, I can't even answer the phone because just dragging the slider lags so much the whole phone locks up. when I get to my desktop I need to use my task killer to kill everything before I can do anything.
what gives? is this the hardware? does everyone have this same problem? or is it unique to me? I'm ready to throw it through a wall.
no widgets running right now. and when I check running apps, there really isn't much going on. I'm about ready to go back to stock and see what happens. I got the phone a year ago and can't live through another year of this. heck, I got an iphone 4s from work and don't want to consider using it in place of my android.
help me please.
Click to expand...
Click to collapse
What are your CPU-Settings?
Have a look here: http://forum.xda-developers.com/showthread.php?t=1571697
Try with "ondemand".
Chris
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.
I installed the Smooth Bean JB 4.1 rom yesterday. It really is a awesome piece of work, but I have two issues.
1. Slowness. I changed the minimum speed to around 400 rom 200 but it still transition from screen to screen slowy at times.
2. Black screen. After getting everything just rightl I noticed the screen will go black occatiionally. I can press the power button to blank the screen, and come back and it's normal again.
I follows the Developers instrutions to NVflash first, clean all settings, factory reset and load. Everythings looks normal but for the top issues.
This is not every second issue. I can still use the G-Tablet and it does work perfectly but then it goes black or slows down.
Why not ask on the dev's thread for this ROM? Nobe is very helpful and supportive, and you'll get a faster response there.
Sent from my SCH-I535 using xda app-developers app
not enough replies
schwinn8 said:
Why not ask on the dev's thread for this ROM? Nobe is very helpful and supportive, and you'll get a faster response there.
I haven't replied to enough post to be able to post on the DEV thread. I get a error when I try telling me this.
Click to expand...
Click to collapse
Ok. I didn't realize the board prevents posting there based on post counts. So be it.
Sent from my SCH-I535 using xda app-developers app
You can always wipe data/reset only, and reflash the ROM. It sounds like a hardware issue, but I assume you were not having these problems before. i cannot think of a fix for this, I have not seen anyone else have problems with a blackout screen.
The temporary slowdowns are due to 100% cpu usage, which happens to all of us. I would suggest holo launcher, or apex, because they use less RAM and less CPU, and they are better than stock, and FREE!!!!! There are many launchers better than stock and use less CPU.
Another thing you can do is get system tuner, and delete system apps you dont use, like calender, or smspush, stock Email. This can create issues though if you delete the wrong stuff.
afitzroy said:
I installed the Smooth Bean JB 4.1 rom yesterday. It really is a awesome piece of work, but I have two issues.
1. Slowness. I changed the minimum speed to around 400 rom 200 but it still transition from screen to screen slowy at times.
2. Black screen. After getting everything just rightl I noticed the screen will go black occatiionally. I can press the power button to blank the screen, and come back and it's normal again.
I follows the Developers instrutions to NVflash first, clean all settings, factory reset and load. Everythings looks normal but for the top issues.
This is not every second issue. I can still use the G-Tablet and it does work perfectly but then it goes black or slows down.
Click to expand...
Click to collapse
Which update are you using? The most current one that you have to apply the update is going to run mainly off of the GPU instead of the CPU. I changed it that way so that the strain on the processor wouldn't be to over whelmed. Since currently we are still working with the 2.6.39 which has a lot off small issues when the CPU gets overloaded, for most SOD, that why I choose that config. There also might be some remidence of previous ROM builds within the nand or like everyone else blames on is Bad Blocks. I am currently working on a neat format tool that should help or devices handle those, but since we switch from 200m, to 250m, and also 300m systems it is going to take awhile to build it up. The best word of advise is to get a copy of the one time NVflash Format tool from here Click and run it a couple of times before NVflashing the 250m modded one.
I updated using Smooth Bean 1.3.2 with the re-mixed update file. Since I was having problems getting my tablet to power to 100%, and the black screens I performed the "format" that was listed above. Now my tablet won't boot at all. I think i'll let it power completely off, and if I can get it running i'll clear out all data and start from scratch.
Thanks everyone for your advice and hopefull I'll be up and running soon. From what I can see Smooth Bean 1.3.2 was the best rom yet.
Fixed
afitzroy said:
I updated using Smooth Bean 1.3.2 with the re-mixed update file. Since I was having problems getting my tablet to power to 100%, and the black screens I performed the "format" that was listed above. Now my tablet won't boot at all. I think i'll let it power completely off, and if I can get it running i'll clear out all data and start from scratch.
Thanks everyone for your advice and hopefull I'll be up and running soon. From what I can see Smooth Bean 1.3.2 was the best rom yet.
Click to expand...
Click to collapse
My tablet is now booting, and i'm loading everything from scratch. Thanks again.
afitzroy said:
My tablet is now booting, and i'm loading everything from scratch. Thanks again.
Click to expand...
Click to collapse
Glad to help. If you have any issues please feel free to PM me or update this tread. I typically use the mobile app so I will see everything that is updated.
Sent from The Darkside via Me...
Works beautifly
nobe1976 said:
Glad to help. If you have any issues please feel free to PM me or update this tread. I typically use the mobile app so I will see everything that is updated.
Sent from The Darkside via Me...
Click to expand...
Click to collapse
I reloaded the G Tablet from scratch and I even wiped the 16gig SD card. I have never installed a ROM that was this responsive. It is incredible, and i'm loving how fast it is. Normally I have to tweak the min CPU but with this I never had too. Thanks for your Smooth Bean, Effort, and I'll donate when I move to your thread.
I do have one issue that has not gone away though. When I'm in your Smooth Bean thread and click "thanks" my screen goes black. This also seemed to happed when i opened ES Taskmanager. To fix it, I press power to blank the screen, and then I come back in and the screen is good.
Any ideas?
afitzroy said:
I reloaded the G Tablet from scratch and I even wiped the 16gig SD card. I have never installed a ROM that was this responsive. It is incredible, and i'm loving how fast it is. Normally I have to tweak the min CPU but with this I never had too. Thanks for your Smooth Bean, Effort, and I'll donate when I move to your thread.
I do have one issue that has not gone away though. When I'm in your Smooth Bean thread and click "thanks" my screen goes black. This also seemed to happed when i opened ES Taskmanager. To fix it, I press power to blank the screen, and then I come back in and the screen is good.
Any ideas?
Click to expand...
Click to collapse
Yeah it seams that I over did a few things and will be reworking them. Hope to post a new update with changes as long as thing go alright. This new one should be all good.
Sent from my Under Rated Gtablet using xda app-developers app
edited wrong thread my mistake Mods
I recently flashed my Samsung Fascinate with PowerWashed Team's PWGB Version 2.0 (Beta 3). I'm terribly new to using custom ROMs, but I'm quite pleased with the results. I've only had one concern with this ROM regarding the back light on the soft keys. They light up every time I touch my screen or press a hard key.
I've attempted to find a setting for this in the OS and in CwM Voodoo Lagfix Recovery v2.5.1.x screen, but wasn't able to find such a setting (Again, I'm very green so it could be right under my nose and I simply don't know it.)
I also attempted to install myriad apps to keep the back light off on screen touch including:
Screen Filter (No effect)
Night Mode (No effect)
Light Flow Lite - LED Control (No effect)
Light Manager - LED Settings (This app actually stops the back light from coming on, however it's unpredictable and works >15% of the time)
I've also done a lot of searching on the matter. I've seen where others have stated the problem, but none where there was a solution or enough information for me to further investigate a way to fix this. It's also been complicated to find information due to a variety of search terms (soft keys, led, etc.) yielding results about the camera or other things that are unrelated to my issue coupled with my lack of direct knowledge on the matter.
I'd really appreciate any advice on either directly fixing this or a source of information so I may learn more from what is causing this behavior and fixing it myself. Thanks, everyone for all the time and effort you've put in for making things like this accessible to individuals like me. I can't tell you how much I appreciate it.
This behavior is a product of the kernel, and most people find it desirable. If you install the kernel control app nstools, you should see an option called cmled timeout, allowing you to set the led backlight timeout.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
This behavior is a product of the kernel, and most people find it desirable. If you install the kernel control app nstools, you should see an option called cmled timeout, allowing you to set the led backlight timeout.
Click to expand...
Click to collapse
Thanks for the information! Unfortunately, the ROM I flashed has a stock kernel and doesn't offer this option. So, I suppose that's the first thing I need to address, but now I know where the problem lies! Thank you so much for your time and input, I'll put it to good use.
Are you saying the back lights light up even if you just touch the screen? That's strange, they only have ever lit up for me when I actually touch a soft key or hit the power button to wake the phone up.
Well good luck, I'm not sure what kernel is best for GB as I started flashing custom roms during ICS and I'm now on Jelly Bean and never going backwards.
Crawshayi said:
Are you saying the back lights light up even if you just touch the screen?
Click to expand...
Click to collapse
Yes, exactly this. It is really odd and very bothersome when trying to read at night. Even if I use the volume rocker to turn the page the lights will come on. It's maddening. I'm currently looking at the kgb kernel, but I think the nstools led option isn't actually going to address this quirk. (Directly, I believe I will end up disabling the led altogether)
If you don't mind, what rom did you choose?(Ignore, I was on mobile and did not see your signature at the time)
How has the performance been? I'm interested in doing the same, but was afraid my fascinate wouldn't handle jb very well.
Well needless to say it's different for everybody when it comes to roms, sometimes your phone will have no problem running a certain rom where as someone else's might not even boot. As for myself I've been pretty fortunate and have been able to try any rom I've wanted to with success, and I'll give you a few of my thoughts on it.
If you're wondering about performance, well simply put JB blows everything else away and runs like a dream on the Fascinate. Once you spend a few days with it you'll never want to go back honestly. Even on our aging hardware, it runs amazingly fast, even without kernel performance tweaks.
Anyway, as far as roms go, if you're most concerned with stability and reliability then I would highly suggest CM10 (whatever the latest nightly version is). Of all the roms I've tried, it's by far the one that's given me the least hassle. That said, I'm quite fond of the tweaks offered in AOKP, mainly the voltage settings (for battery life) and the fact that it seems to vibe much better with Devil kernel than CM10 does. I've been running my current rom/kernel for a couple of weeks now, and I'm happy enough with how it's running to keep it as my daily driver for a while.
This isn't to say the GB roms aren't any good, because of course they are, but considering how nice JB roms run on our phone you'd be doing a disservice by not at least giving them a shot.
Crawshayi said:
If you're wondering about performance, well simply put JB blows everything else away and runs like a dream on the Fascinate. Once you spend a few days with it you'll never want to go back honestly. Even on our aging hardware, it runs amazingly fast, even without kernel performance tweaks.
Click to expand...
Click to collapse
You sold me on the idea of JB. Flashed it today, and I love it so far. Plus, my soft key lights aren't constantly on! Win-win.
Thank you so much for the guidance. Your input helped turn a satisfactory experience with ROMs into a trully positive one.
Glad to hear you liked it man, I was reluctant at first too due to (at the time) no 'official' releases, but I'm glad I made the jump. I'm quite enjoying AOKP M1 and will probably stay on it for a long time. Which rom did you end up trying?
Crawshayi said:
Glad to hear you liked it man, I was reluctant at first too due to (at the time) no 'official' releases, but I'm glad I made the jump. I'm quite enjoying AOKP M1 and will probably stay on it for a long time. Which rom did you end up trying?
Click to expand...
Click to collapse
I was really impressed with your review, so I chose to go with the same rom. It also seemed like the most stable option and easiest for me to understand the installation procedure (very important for me since this is my only device and more than just my daily driver, it's my life line). I had been extremely hesitant to go to JB for fear of junking my phone up, but I'm really glad I took the extra risk. I just needed an extra bit of encouragement. Thanks again for all your input!
If you managed to install AOKP smoothly you can pretty much install any rom the same way, basically meaning wipe data and cache/davlik then flash whatever you want to. Luckily this phone happens to be very hard to break, and you'd have to do something pretty extreme to brick it. I highly recommend Titanium backup pro so you can just backup the apps you want, and restore them in no time when you're trying different roms. Also, I've been using some voltage settings that make battery life insanely good, so if you're interested in doing that let me know and I'll post them.
olalaelaine said:
I was really impressed with your review, so I chose to go with the same rom. It also seemed like the most stable option and easiest for me to understand the installation procedure (very important for me since this is my only device and more than just my daily driver, it's my life line). I had been extremely hesitant to go to JB for fear of junking my phone up, but I'm really glad I took the extra risk. I just needed an extra bit of encouragement. Thanks again for all your input!
Click to expand...
Click to collapse
Regarding the key back light, since you are on aokp jellybean now if you still want to tweak the settings, goto settings and then device settings. There you can adjust the timeout on them
Crawshayi said:
If you managed to install AOKP smoothly you can pretty much install any rom the same way, basically meaning wipe data and cache/davlik then flash whatever you want to. Luckily this phone happens to be very hard to break, and you'd have to do something pretty extreme to brick it. I highly recommend Titanium backup pro so you can just backup the apps you want, and restore them in no time when you're trying different roms. Also, I've been using some voltage settings that make battery life insanely good, so if you're interested in doing that let me know and I'll post them.
Click to expand...
Click to collapse
just a little hint: NEVER RESTORE SYSTEM APPS WITH TITANIUM YOU WILL GET BOOTLOOP
Sent from my SCH-I500 using Tapatalk 2
I've restored Nova before that was a system backup with no problems but I agree about anything else. Not sure what system apps anyone would even want to backup really
Crawshayi said:
I've restored Nova before that was a system backup with no problems but I agree about anything else. Not sure what system apps anyone would even want to backup really
Click to expand...
Click to collapse
Dude I mean like system UI or settings lol
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Dude I mean like system UI or settings lol
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I've actually done that before just to see what happened (system settings) and it didn't bootloop, it simply didn't restore anything. Not that I mind re-setting everything after a clean install, just figured I'd try to save a little time
Crawshayi said:
I've actually done that before just to see what happened (system settings) and it didn't bootloop, it simply didn't restore anything. Not that I mind re-setting everything after a clean install, just figured I'd try to save a little time
Click to expand...
Click to collapse
Are you trying too teach him too restore system apps lol?
Sent from my SCH-I500 using Tapatalk 2
Nope not at all, just chiming in on what happened when I tried it. It should be a no brainer to anyone flashing roms to not restore system apps, even if they're new to it honestly
Crawshayi said:
Nope not at all, just chiming in on what happened when I tried it. It should be a no brainer to anyone flashing roms to not restore system apps, even if they're new to it honestly
Click to expand...
Click to collapse
I know but it would surprise you I've had people complain because they flashed a i9000 ROM and it didn't work because the developer is stupid LOL
Sent from my SCH-I500 using Tapatalk 2