Database Info

[Q] sensation crashing during unlocking the screen

Hi there guys!
i just bought a htc sensation a month ago and make its s-off an flashed also a custom rom (senseless rom 1.2)
now my problem its, that the phone is rebooting sometimes, when i try to unlock the device from sleeping.
i push the power button, the phone doesn't react, so i push a second time. after pushing 2nd time, the display splash on and at the next moment off.
2 seconds later, i got the boot-splash of the device.
anyone had this problem already?
EDIT: this problem was coursed also before s-off, therefore i choose this section to disks about! =)

I'm having this problem as well. I have not rooted or s-off'd or anything else. Stock rom, most apps from the market. This started happening the other day when I installed an update to version 2.3.4. This is happening several times a day and is getting extremely annoying!!

hi,
i just followed this problem again.
i am using now the Beast Rom, and the phone has still this problem.
any ideas?

yasinis said:
hi,
i just followed this problem again.
i am using now the Beast Rom, and the phone has still this problem.
any ideas?
Click to expand...
Click to collapse
Try flashing ARHD 3.6.1 from Mike1986 very stable, good support and fully operational. way better than stock.
Sent from my HTC Sensation XE with Beats Audio using xda premium

Defrag your micro sd card and fix file system errors. Uncheck enable fastboot and turn off your phone then turn it back on again. Lastly, try not to use "kill all" in task manager. Hope it help you guys.

Crashing as well
Same here with crashing.
During unlock, when using GPS. It's now several times a day. The device has become unfit for purpose. Will try the SD card trick.

Sensation constantly turns off with custom ROM's

I have had this issue since I rooted/s-off my senation.
I flashed Android Revolution and I noticed my Sensation would turn off about 10 times during the day and I would have to restart the phone.
I then decided go back to stock using my backup with clockwork and I noticed it continued to reboot, but not as often.
I then wiped/cleared cache and tried to flash a new ROM (Synergy)
It was ok for the first couple days and now its back to rebooting about 10 times a day.
Is anyone else having similar issues? I have a US Tmobile Sensation.
Thanks

If I were you I would run the ruu for your device and if it occurs return to t mobile for a replacement.

Had same issues and nobody helped me.... Here's the repair. Hit the thanks button if it helps you.
I went on eBay and bought a new battery, apparently the initial battery died while flashing from a Rom to another. I suggest you buy the highest mAh you can find, I personally found one called Anker with 1900 mAh.
Good luck to you
Sent from my HTC Sensation Z710e using XDA Premium App

epg0 said:
I have had this issue since I rooted/s-off my senation.
I flashed Android Revolution and I noticed my Sensation would turn off about 10 times during the day and I would have to restart the phone.
I then decided go back to stock using my backup with clockwork and I noticed it continued to reboot, but not as often.
I then wiped/cleared cache and tried to flash a new ROM (Synergy)
It was ok for the first couple days and now its back to rebooting about 10 times a day.
Is anyone else having similar issues? I have a US Tmobile Sensation.
Thanks
Click to expand...
Click to collapse
A few things....
Obviously something funky happened....and no it's not normal...even for custom ROMS. ARHD works fine, so does Synergy.
For ****s & giggles try InsertCoin ROM. The latest build is VERY stable and fast.
ALWAYS make sure that the MD5 Checksum the developer gives for the download matches. Bad downloads do happen. Firefox has an MD5 checksum addon.
Also...make sure there is no possibility of any 3rd party app causing conflicts/reboots. Play around with a new ROM for a little bit (hour or so) before installing 3rd party apps. Just to be sure it's stable on it's own.
In recovery....
~Data wipe
~Clear cache
~Clear Dalvik cache
~Install a custom ROM (IC for example)
~Reboot
*DONT TOUCH THE DEVICE FOR 10 min. LET IT SIT.
~When the 10 min is done....reboot device.
~Setup your Sensation how ya like.
Good Luck!!

Thanks for the suggestions. I will try another ROM and the suggestions you guys posted.
I do not have any crazy third party apps. They are all popular ones and only a few.
If all else fails I will try a new battery first and if that doesnt work I will root it back up and send in for a replacement.

epg0 said:
Thanks for the suggestions. I will try another ROM and the suggestions you guys posted.
I do not have any crazy third party apps. They are all popular ones and only a few.
If all else fails I will try a new battery first and if that doesnt work I will root it back up and send in for a replacement.
Click to expand...
Click to collapse
Also it wouldn't hurt to try another kernel
Sent from my Nexus S 4G using Tapatalk

Any way around not having to clear the "cache" on BOOT?

So I am running into the problem that my phone wont boot up if I turn my phone off, or it dies.
The only way around to getting it back on is getting CWM up and doing a "cache wipe".
The symptoms I am having when I try to turn it on is I do not get past the LG logo. The soft keys are lit and the screen back light comes on and off (black screen) with a 2-3 second intervals forever (have not went past 10min).
I am running xboards tweaked 2.3.3 with fauxes stock volt kernel, any more into?
Thanks guys.

No one? Really?..

Sounds like an errant app is causing you problems. Once you boot start uninstalling apps one at a time that you think are the culprit and try rebooting. Do this until your phone can boot again and then you'll have a good idea of the problem app.

Paul Nur said:
No one? Really?..
Click to expand...
Click to collapse
The only thing I can think of is maybe an issue with the custom kernel. Do you remember having the issue before you flashed Faux's kernel?

jboxer said:
Sounds like an errant app is causing you problems. Once you boot start uninstalling apps one at a time that you think are the culprit and try rebooting. Do this until your phone can boot again and then you'll have a good idea of the problem app.
Click to expand...
Click to collapse
.. and that. lol

jboxer said:
Sounds like an errant app is causing you problems. Once you boot start uninstalling apps one at a time that you think are the culprit and try rebooting. Do this until your phone can boot again and then you'll have a good idea of the problem app.
Click to expand...
Click to collapse
I installed fauxes OC (over clock), and its working fine now, I was having problems with SV (stock voltage), maybe that was the culprate?
P.S. After restarting my phone (I have been doing it every so often to test for stability) my home screen got reset to factory? I had all my apps and everything, it was just factory..??? Only happened once tho.
phburks said:
The only thing I can think of is maybe an issue with the custom kernel. Do you remember having the issue before you flashed Faux's kernel?
Click to expand...
Click to collapse
^^^^^^^^^^

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.

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.