Database Info

How to troubleshoot issues

Ok I have been learning how to and moving forward with flashing different ROMs.
I am currently running a 2.3.6 GB on my Infuse.
I am looking to go to ICS however I want to understand better certain issues I am having with my phone.
Its not every time but I will click to open my applications and wait but nothing happens.
If I lock my screen and then re-open my applications will be there. (this part is consistent)
Now Im also getting a lot of Force Closes - I even uninstalled and re-installed applications and still get the same force close when I try to open with one exception where that fixed the problem.
I tried the fixed permissions from Recovery mode but that did not help.
So I have better than 50% of the time where my applications wont open but locking and unlocking causes it to pop open.
I have several applications that i keep getting force close on.
I also have times when things seem sluggish and times when I go to unlock my phone and its froze so that I have to pull the battery.
I use the Go Launcher and its utilities like Power Master and Task Master to manage battery and tasks and it seems to do a good job and has a lot of people recommending them.
What I would like is a way to be able to evaluate and determine what may be going on and resolve it.
Any guidance would be greatly appreciated.
Thanks.

If one Rom doesn't work for you, try another one until you find one you can settle on for a while.
Remember to always do the appropriate wipes when switching roms, and be careful when restoring apps & data, as it can sometimes cause issues.
I would recommend to give JB a try if you haven't yet.
Sent from my sweet & buttery Infuse

andros11 said:
If one Rom doesn't work for you, try another one until you find one you can settle on for a while.
Remember to always do the appropriate wipes when switching roms, and be careful when restoring apps & data, as it can sometimes cause issues.
I would recommend to give JB a try if you haven't yet.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
I was going to go to JB but have heard its still a bit buggy.
I used Go Backup to restore applications this time around.
I have used a variety of Backup and Restore options to include nandroid, Titanium, AppExtractor however Go Backup seemed to do my apps, sms, mms, contacts and so forth the best.
If you can refer a better process for application backup and restore when upgrading / changing ROMs Im all ears.

Not buggy for me. Cm10 & paranoid android are pretty solid.. have not tried the others but I believe they perform well too.
I use mybackup pro, just personal preference. I find it simple and works for me.
Sent from my sweet & buttery Infuse

I have tried CNA , MIUI, PA, CM10 and Cypher AOKP ROM (my current one). All are pretty stable. Just be aware most, if not all, are MTD based and going back to ICS (different format) can be a process. Also back up EFS using Infuse toolkit just in case your IMEI disappears.
Sent from my SGH-i997 using xda premium

I suspect your problem is related to Go Launcher and the other Go apps, particularly if you are using one of their builds from the last 6 months. If I were you, I'd backup and do a full wipe and install of one of these GB ROMs: http://forum.xda-developers.com/showthread.php?t=1613523. Restore all your apps except the Go apps and see how things run. Go Launcher provides more functionality than any other free launcher, so you'll have to get used to that. I moved to the free ADW launcher when I was on GB - it's kind of simple, but there are some nice themes available for it.
Also, don't use the GO utilities!
Of course, you could move to a JB ROM. They are all pretty good and stable. JB, however, has some irritating bugs and some apps don't function properly on it. I'm using Paranoid Android 2.0. It's really good, but not quite as fast as the straight CM10...

Whizzpopper said:
I suspect your problem is related to Go Launcher and the other Go apps, particularly if you are using one of their builds from the last 6 months. If I were you, I'd backup and do a full wipe and install of one of these GB ROMs: http://forum.xda-developers.com/showthread.php?t=1613523. Restore all your apps except the Go apps and see how things run. Go Launcher provides more functionality than any other free launcher, so you'll have to get used to that. I moved to the free ADW launcher when I was on GB - it's kind of simple, but there are some nice themes available for it.
Also, don't use the GO utilities!
Of course, you could move to a JB ROM. They are all pretty good and stable. JB, however, has some irritating bugs and some apps don't function properly on it. I'm using Paranoid Android 2.0. It's really good, but not quite as fast as the straight CM10...
Click to expand...
Click to collapse
Funny you should show those ROMs as I am using that very ROM - Option C version
Man I really like the Go Launcher and my wife doesnt seem to be having a problem with it.
Oh well I was looking to maybe make the move up to ICS so maybe I will do that tonight.
Also can you use Heimdal to install those packages or just Odin?

mikefarr said:
Funny you should show those ROMs as I am using that very ROM - Option C version
Man I really like the Go Launcher and my wife doesnt seem to be having a problem with it.
Oh well I was looking to maybe make the move up to ICS so maybe I will do that tonight.
Also can you use Heimdal to install those packages or just Odin?
Click to expand...
Click to collapse
Neither. I believe ODIN and Heimdall are more for recovery.
If you have GB now, download the ROM(s) to your phone and go to CWM and install the zip. Make sure you follow the instructions on the OP of the ROM (wipe/factory reset, etc). Don't forget to install GAPPS too.
And if you want to flash JB, go to http://forum.xda-developers.com/showthread.php?t=1878458 (great guide, also shows how to go from GB to ICS first...follow those instructions).

psal217050 said:
Neither. I believe ODIN and Heimdall are more for recovery.
If you have GB now, download the ROM(s) to your phone and go to CWM and install the zip. Make sure you follow the instructions on the OP of the ROM (wipe/factory reset, etc). Don't forget to install GAPPS too.
And if you want to flash JB, go to http://forum.xda-developers.com/showthread.php?t=1878458 (great guide, also shows how to go from GB to ICS first...follow those instructions).
Click to expand...
Click to collapse
Thanks to all that have helped me with this.
Now if it turns out it is the Go Dev Team programs thats my problem I will need some good replacement recommendations :laugh:

mikefarr said:
Thanks to all that have helped me with this.
Now if it turns out it is the Go Dev Team programs thats my problem I will need some good replacement recommendations :laugh:
Click to expand...
Click to collapse
Ok I was reviewing the link you gave to upgrade and had a couple of questions.
9. Flash ICS, then ICS Gapps - this step refers to ICS Gapps
Once it boots into ICS, turn off and remove your external sdcard.- Why do you have to pull your external sdcard?
The in the section for going to JB it says
5. Flash Gapps - Is this a different Gapps file?
Just curious...

Having the SD card has been known to cause problems...best to remove...you can put it in later. ICS and JB have different GAPPS. Look for the link to the correct GAPPS on the IP of the ROM you decide to use.
Sent from my SGH-i997 using xda premium

Thank you for clarifying that psal.
I'll add those details to the guide.
Sent from my sweet & buttery Infuse

psal217050 said:
Having the SD card has been known to cause problems...best to remove...you can put it in later. ICS and JB have different GAPPS. Look for the link to the correct GAPPS on the IP of the ROM you decide to use.
Sent from my SGH-i997 using xda premium
Click to expand...
Click to collapse
Can you recommend a good ICS ROM?
Also when I tried to make sure I had the device driver installed it is not showing me the Samsung Common.
I guess I hear Entropy has a top JB and also heard good stuff on Th3Bill's JB.
Thanks

mikefarr said:
Can you recommend a good ICS ROM?
Also when I tried to make sure I had the device driver installed it is not showing me the Samsung Common.
I guess I hear Entropy has a top JB and also heard good stuff on Th3Bill's JB.
Thanks
Click to expand...
Click to collapse
My USB drivers say USB Composite Device. If you are going to leap from ICS to JB, it probably doesn't matter which one you flash...most of them are really good (I used UNi-yuma-PoRN when I was on ICS). I have used several of the JB's and everyone likes what they like. Try them all and see which one you like best.

psal217050 said:
My USB drivers say USB Composite Device. If you are going to leap from ICS to JB, it probably doesn't matter which one you flash...most of them are really good (I used UNi-yuma-PoRN when I was on ICS). I have used several of the JB's and everyone likes what they like. Try them all and see which one you like best.
Click to expand...
Click to collapse
Ok I went to look up your yuma.
I found it however when I click to download it says it couldnt find it.
Is the gapp just based on the flavor ie. gapp for ICS, gapp for JB and so forth or are they more specific to the ROM?
Hopefully can flash one tonight but if not - tomorrow.

mikefarr said:
Ok I went to look up your yuma.
I found it however when I click to download it says it couldnt find it.
Is the gapp just based on the flavor ie. gapp for ICS, gapp for JB and so forth or are they more specific to the ROM?
Hopefully can flash one tonight but if not - tomorrow.
Click to expand...
Click to collapse
ICS GAPPS were used across the ICS ROMs. Some played around and created inverted GAPPS (black screen, white letters) but ICS had GAPPs and JB has GAPPS. Not sure why...probably due to the different file formats.
Also the mirror in the first link on the OP is down...some upgrades. Try the other mirror
UnipOrnB40a.zip - 326.47 MB

psal - nice work, brother - you're gonna own this place before long :good:
mikefarr- keep on keepin' on, you are on the right track.
andros11- the guide is great - can't wait for the movie :good:

mikefarr said:
Ok I went to look up your yuma.
I found it however when I click to download it says it couldnt find it.
Is the gapp just based on the flavor ie. gapp for ICS, gapp for JB and so forth or are they more specific to the ROM?
Hopefully can flash one tonight but if not - tomorrow.
Click to expand...
Click to collapse
I have tried 3 times to install the 07.28 ver of this ROM
http://forum.xda-developers.com/showthread.php?t=1601844
All 3 times it failed with a error Status 7

mikefarr said:
I have tried 3 times to install the 07.28 ver of this ROM
http://forum.xda-developers.com/showthread.php?t=1601844
All 3 times it failed with a error Status 7
Click to expand...
Click to collapse
I just re-downloaded it from that link without a problem. You might need to clear cookies, cache, etc from your browser and retry it. Of course I downloaded to PC and moved the file over to the phone. And you are on GingerBread?
Google has a lot of suggestions:
http://www.google.com/search?hl=en&...09.309.3-1.1.0.les;..0.0...1c.1j2.27RSU95e5S8

mikefarr said:
I have tried 3 times to install the 07.28 ver of this ROM
http://forum.xda-developers.com/showthread.php?t=1601844
All 3 times it failed with a error Status 7
Click to expand...
Click to collapse
Ok I tried another ROM - RemICS-UX and got the same error status 7.
Something else is wrong or Im missing something grrrrr.

Can't find stable Android 4.x ROM/ Kernel

Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.

Unrelashade said:
Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.
Click to expand...
Click to collapse
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2

mattlowry said:
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own

demkantor said:
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own
Click to expand...
Click to collapse
Thanks guys! Fastboot says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
Click to expand...
Click to collapse
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha

Unrelashade said:
Thanks guys! Fastboot says:
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha
Click to expand...
Click to collapse
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2

Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium

You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?

mattlowry said:
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
demkantor said:
Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
WeekendsR2Short said:
You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?
Click to expand...
Click to collapse
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.44.1107
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
Jun 27 2011, 14:08:29
Click to expand...
Click to collapse
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha

If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Sent from my HTC MyTouch 4G Slide using xda premium

Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2

A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Sent from my myTouch_4G_Slide using xda app-developers app

Unrelashade said:
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha
Click to expand...
Click to collapse
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.

WeekendsR2Short said:
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.
Click to expand...
Click to collapse
Thanks for the info.
demkantor said:
If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Click to expand...
Click to collapse
Ok, right now I'll not try flashing bootloader since everything seems to be normal.
What I did to get last_kmsg:
Code:
Open terminal app
Enter "su" to get root privileges
Enter "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" to save current log.
Close terminal app.
I attached the last_kmsg.txt. What do I do with it now? I don't have knowledge to understand it.
mattlowry said:
Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
I can't remember using a ROM that never crashed, but I'll try a stock ROM if nothing else works. However an old kernel of scverhagens CM 9.1 seems to work flawlessly if battery is not about < 15%. The newest r10 kernel on the other hand always immediately crashes when the phone is not charging. When charging I haven't experienced a crash yet. That's strange and makes me suspect my battery is the problem.
mojoffdawal said:
A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Click to expand...
Click to collapse
Thanks! I guess I'll try an Anker since I have seen so much users here using it.

virtuous rom works great! when i had mine, i was running 4.0.3 overclocked to 1.5ghz. super stable too! daily driver for sure.
Sent from my SGH-T999 using xda app-developers app

Thanks, but the problem is I'm pretty sure that something's wrong with my phone...
I'll try virtuous ROM and a new battery though.

hope it works
Sent from my SGH-T999 using Tapatalk 2

So, I'm reviving this thread, because I stopped writing only because my phone was broken. Now it's back and I'm facing this problem again.
I've tried a lot of the 4.x ROMs here from the forums, but all of them rebooted or shut down after 5 - 10 minutes after flashing. I also tried some without flashing gapps even, but still the same symptoms. Also tested it with my new battery, nothing changed. Even the scverhagen CM 9.1 ROM rebootet shortly after flashing that worked longer previously (guess that was just by chance)
Now I've tried the original image and it works! Ugh. So what can be wrong, any ideas?

I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app

bit1 said:
I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
It happened with both stock and new battery (Anker).
Thanks, update to latest TWRP had been my next try, if it didn't work now. But it does! Yeaaah so happy Thanks to everyone again. Almost three hours uptime and not a single issue so far!
To conclude: What I did:
Revert completely back to stock with BlueIX6's stock image (except that phone was still s-off and sdcard not wiped).
Then followed instructions to unlock bootloader, flash CWM recovery and finally flashed ROM (see sticky thread). Works like a charm!
In hindsight maybe radio made my phone unstable... I think it's the only thing that's different from now.

[Q] Dialer FC

Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.

BreatheHT said:
Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.
Click to expand...
Click to collapse
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.

Mister J said:
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.
Click to expand...
Click to collapse
i've tried everything like mentioned in the original post.... EVEN RUU
BUT AOKP roms works fine.

I'm started having the same problem this morning on every single sense ROM that I tried. I finally had to flash CM because I needed to call someone. RUU, wiping everything, different radios and different recoveries, nothing worked.
Sent from my One X using xda app-developers app

tried everything possible -_-

NobodY??????

I'm going to try a few other things when I get a chance, hopefully tomorrow. I would like to get this solved.
Sent from my One X using xda app-developers app

BreatheHT said:
NobodY??????
Click to expand...
Click to collapse
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL

area51avenger said:
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app

sweeterman said:
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yep it can't be hardware.

Have you checked HTC for a bug update? I know they have had these problems in the past. Might not hurt to check.
Sent from my HTC One X using xda premium

This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.

redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing... And I don't really have a good backup...

redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.

BreatheHT said:
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.
Click to expand...
Click to collapse
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL

BreatheHT said:
Should I flash CWM again?
Click to expand...
Click to collapse
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
BreatheHT said:
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing...
Click to expand...
Click to collapse
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.

I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.

sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Good to know...I was thinkin bout flashing CWM, but I guess if I haven't had issues with TWRP, "don't fix what ain't broken."
Sent from my now S-Off HTC OneXL

redpoint73 said:
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.
Click to expand...
Click to collapse
Thanks bro
sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Will try, thanks bro!

elfysrfr said:
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL
Click to expand...
Click to collapse
I'm using 2.3.x.x haha 2.4.x.x is so bad... Or not compatible...

[Q&A] CM10.1

A humble request let the development thread be for just development.Just try to keep that one clean and post anything however random(about CM10.1 ofcourse) here.Don't flood the dev thread with about 70 posts regarding black screen problem.
Let this thread be for general questions, comments, discussion, complaints concerning CM10.1 for the Atrix 2.
CM10.1 development thread .
PS: Help the devs in understanding the reason for black screen problem, participate in the poll.
Thanks...
Sent from my MB865 using xda premium

Thanks for creating this thread to keep the dev thread clean.
I got the black screen after I flashed the ROM and the boot logo. How to get past tge black screen? I had to FXZ back to ICS for now. I did a couple of battery pulls but it did not help.
~
Sayantan

Unlock blaxk screen
i cannot unlock after lock using on off button. how to unlock if still black screen? any solution? after i flash gapps camera and gallery fc. it happen when i open camera.

buglist 28/03/13
cLock can't find any location for weather
forfarded call message not work like on scrren from this http://forum.xda-developers.com/showpost.php?p=37850271&postcount=68
and also unavailable change shutter sound and camera save destination.

qwerfv said:
cLock can't find any location for weather
forfarded call message not work like on scrren from this http://forum.xda-developers.com/showpost.php?p=37850271&postcount=68
and also unavailable change shutter sound and camera save destination.
Click to expand...
Click to collapse
+1 for cLock weather issue but honestly I'm so thoroughly impressed with this ROM that I only see that as a minor hitch. I really never thought a fully functional JB would make it to the Atrix! Thank you Devs! :thumbup:
Sent from my SGH-I997 using xda app-developers app

SMONDAL84 said:
Thanks for creating this thread to keep the dev thread clean.
I got the black screen after I flashed the ROM and the boot logo. How to get past tge black screen? I had to FXZ back to ICS for now. I did a couple of battery pulls but it did not help.
~
Sayantan
Click to expand...
Click to collapse
Actually there's no specific reason(at least till now) and hence solution for this black screen bug.Some of the guys who have it have reported to come around it by taking out the battery and rebooting until they get rid of it.But again the number of battery pulls varies from just one time for some to about 40 minutes of battery pull for some others.So can't really say if you tried enough or what else might be the solution.This is the situation as is.
Keep trying or wait till it gets fixed there is really nothing else that you can do at the moment.
Sent from my MB865 using xda premium

Is there a way to keep the capacitive key backlight always on? Didn't spot anything in the main thread about this.

What is with this "♫" symbol?? It's very annoying, ugly, and it's everywhere on this ROM. in instagram, when entering passwords, in descriptions of apps in the playstore.

Loving this so far, but I do have a few concerns. I did make sure to install correctly (CM recovery -> wipe data, flash, reboot, flash gapps), but I'm running into some minor issues.
- My phone seems to be sluggish at times, especially noticeable when turning the screen off and when it vibrates (anything that vibrates twice in a short amount of time). There's a good half-second delay with each of these, much slower than on CM10. Is this normal? Other than that it runs pretty quickly.
- This is the more major issue, the alarm. Everything else in the gapps package works properly except for the alarm function of the clock. When an alarm goes off, there's no popup or anything, and pressing power stops the vibration from the alarm, but it doesn't actually turn the sound off. I have to kill the Alarm Klaxon service to shut it off. Any idea what could be causing this? I haven't heard of anyone else with this bug yet.

Will try flashing once again with BMM this time..
deveshmanish said:
Actually there's no specific reason(at least till now) and hence solution for this black screen bug.Some of the guys who have it have reported to come around it by taking out the battery and rebooting until they get rid of it.But again the number of battery pulls varies from just one time for some to about 40 minutes of battery pull for some others.So can't really say if you tried enough or what else might be the solution.This is the situation as is.
Keep trying or wait till it gets fixed there is really nothing else that you can do at the moment.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Will try with BMM this time along with the patch. Fingers crossed! (I went through the threads and it appeared that people with BMM probably had a greater success rate with installing in the 3rd system - getting superstitious now! )
Will update the results.
~

Any one found a way to OC the phone on this ROM ?

After flashing this ROM it is not booting. It is stopped at boot logo and showing black screen. Could any one help in this
Regarding , I am on pa ver2.99
Kernel 3.0.0.8
And please tell me which is the best radio apk for PA2.99
Thanks in advance.
Sent from my MB865 using xda app-developers app

android.reddy143 said:
After flashing this ROM it is not booting. It is stopped at boot logo and showing black screen. Could any one help in this
Regarding , I am on pa ver2.99
Kernel 3.0.0.8
And please tell me which is the best radio apk for PA2.99
Thanks in advance.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Enter cm recovery select custom recovery and again flash the rom
Sent from my MB865 using xda premium

any of you guys have problem cannot transfer files through usb? mine, when i connect click turn on USB storage, it just loading and loading and just loading.:crying:

Need help flashing the 4.2.2 ROM
My Atrix 2 is on the JB 4.1.2 leak. Model No. ME865. I have ROM Manager installed. I have copied the zipped ROM and GAPPS files to the external memory card. When I boot into Recovery mode, I cannot see any option to Wipe Data / Factory Reset. I am pretty new at this and so if anyone outlines the steps in detail or posts any link to point in me in the right direction, it would help me much. Thanks in advance.

ozzman77 said:
My Atrix 2 is on the JB 4.1.2 leak. Model No. ME865. I have ROM Manager installed. I have copied the zipped ROM and GAPPS files to the external memory card. When I boot into Recovery mode, I cannot see any option to Wipe Data / Factory Reset. I am pretty new at this and so if anyone outlines the steps in detail or posts any link to point in me in the right direction, it would help me much. Thanks in advance.
Click to expand...
Click to collapse
If you are new to flashing ROM's stay away from this because currently a lot of users face black screen issues etc. Also it should not be installed over JB base as well. Read the entire thread from post one till current and you will see for yourself as it will enlighten you on a lot of aspects what people have already tried & which may save you from heartburn. JB gives a great user experience, enjoy it for a while & then get on the bandwagon when you are more of a informed user.

ozzman77 said:
My Atrix 2 is on the JB 4.1.2 leak. Model No. ME865. I have ROM Manager installed. I have copied the zipped ROM and GAPPS files to the external memory card. When I boot into Recovery mode, I cannot see any option to Wipe Data / Factory Reset. I am pretty new at this and so if anyone outlines the steps in detail or posts any link to point in me in the right direction, it would help me much. Thanks in advance.
Click to expand...
Click to collapse
I agree go for CM10 instead it's been pretty stable.
Sent from my MB865 using xda premium

It's in vain, he already flashed CM 10.1 & now he posted in the black screen thread.

Did get hit by the Black Screen Bug
RAD7 said:
If you are new to flashing ROM's stay away from this because currently a lot of users face black screen issues etc. Also it should not be installed over JB base as well. Read the entire thread from post one till current and you will see for yourself as it will enlighten you on a lot of aspects what people have already tried & which may save you from heartburn. JB gives a great user experience, enjoy it for a while & then get on the bandwagon when you are more of a informed user.
Click to expand...
Click to collapse
You were right. I watched the video on flashing ROMS from here https://www.youtube.com/watch?v=kumkZiGbTFI and tried it out. Got the black screen issue when flashing over JB. Then FXZd back to stock ICS and reflashed, but got the same thing again. So i'm back on ICS now. I suppose i'll upgrade to JB later and stay there for a while till this thing is sorted out.

Anyone getting YouTube problems.... Freezing... Could not stream at all with March build.
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui
3. Kexec 4.2.2
6. ASOPA 4.2.2

Strange problems with Galaxy r

Ok so it is like this:
I bought my galaxy r here in sweden 1 year and 3 months ago, it was working perfectly for around 1 year.
At the one year mark i started to have some problems with the touchscreen where the phone would feel a pressure in the middle of the screen, to get rid of this i simply locked and unlocked the phone or rubbed a bit with a cloth on the screen.
Recently when I saw there was a cm10.1 rom with nightlies I rooted my phone and later installed the cm10.1 rom. Now the most anoying thing. I have a problem with my battery where the phone just shuts down randomly (mostly when playing games) even though it sometimes have up too 80% battery remaining. Then when I restart the phone it usually have 0% battery left and therefore shuts itself down again, sometimes it restarts with just a 20-30% batteryloss. This have occured more often recently and it shuts itself of 3-4 times a day. I can't remember if it was like this when i was on stock, before I started to flash and root, but i think it was.
A few days ago i flashed stock ics from odin and I confirmed that both of these problems still were there, so i have hard to belive that it is the modding of the software that have caused this.
Do you guys have any suggestions to how i can be able to use my phone normally again?
Im just a poor student so i don't want to waste money on a new phone after just 1 year :/

wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta

Will this help with the battery?

kataria.vikesh said:
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Will this help the crashing/battery?

DippN said:
Will this help the crashing/battery?
Click to expand...
Click to collapse
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.

kataria.vikesh said:
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
Click to expand...
Click to collapse
Nope, im not takeing backup of anything.
And one other thing i forgot to mention earlier, the phone now also thinks it is charging itself evrn when it is not. It think the usb cable is still connected.

I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!

paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.

DippN said:
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
Click to expand...
Click to collapse
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Both of you install CM10.1 using Procedure no 2 from OP.

kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Will try that when i get home, thx.

kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.

paKS7 said:
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
Click to expand...
Click to collapse
Sadly, I can confirm that this did not change anything.
The problems are still there :/

DippN said:
Sadly, I can confirm that this did not change anything.
The problems are still there :/
Click to expand...
Click to collapse
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium

kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?

DippN said:
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
Click to expand...
Click to collapse
May be hardware or software too..when you will vanish all data & cache then Software issue may be gone but if problem still persist, means you have hardware problem.
Also, root will be lost after flashing Stock ROM from ODIN.

I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!

paKS7 said:
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
Click to expand...
Click to collapse
Well, we are not on the same baseband. I'm on I9103XXLQ3.
About the cm verison im not quiet sure, the latest i flashed was "20130406" but since the problem were there the time before that when i flashed cm I cant answer exacly but i have a cm version "20130305" on my desktop and it could be that one that I used.
I never used cm before it was on nightlies so the modem file flashing i dont know anything about.
The thing you mention about that it shuts of when the phone gets busy and touchscreen gets unresponsive I can kind of confirm too.
I will flash GB now, will report back in an hour how it went.

kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.

DippN said:
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
Click to expand...
Click to collapse
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?

DippN said:
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
Click to expand...
Click to collapse
Wipe data again.. If possible after wiping data Just reflash the GB.