Database Info

CM9 Alpha 11 fault

Hey people.. earlier when i was using ICS there was battery problem.. so i flashed xxkpe but also it became freezing after that I flash ddlf2... the freeze problem stopped... Now again when I flash CM9 Alpha 11... it started freezing can anybody tell me whats the matter?

Give it a while to stabilise. I experience freezing occasionally on all rooms, sometimes even freezes 3 after 3 times I pulled the batt.
Sent from my GT-I9003 using xda app-developers app

bscraze said:
Give it a while to stabilise. I experience freezing occasionally on all rooms, sometimes even freezes 3 after 3 times I pulled the batt.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
till then what shall I Do? Switch back to ddlf2 again?

anuragvivek93 said:
till then what shall I Do? Switch back to ddlf2 again?
Click to expand...
Click to collapse
Anything will do, depends on which rom you like. If after 1 day it doesn't stabilise idk then.
Sent from my GT-I9003 using xda app-developers app

Wipe Cache/Dalvik and data.
DON'T use the device after the first boot, let it just sit there alone for 10 minutes, reboot it and start using it after, works for me everytime, i guess it's just cache regenerating all over again which can cause slow performance and can get corrupted sometimes causing freezes.

Skander1998 said:
Wipe Cache/Dalvik and data.
DON'T use the device after the first boot, let it just sit there alone for 10 minutes, reboot it and start using it after, works for me everytime, i guess it's just cache regenerating all over again which can cause slow performance and can get corrupted sometimes causing freezes.
Click to expand...
Click to collapse
i tried again today but the freezing dont stop as soon as I flash CM9 from ddlf2

can anybody help?

anuragvivek93 said:
can anybody help?
Click to expand...
Click to collapse
Did you follow the steps ONE BY ONE on the CM9 thread? you should use the flashing from stock method, all of the steps.
If you did that, try another base rom (XXKPU) and then flash CM9 on it.

Skander1998 said:
Did you follow the steps ONE BY ONE on the CM9 thread? you should use the flashing from stock method, all of the steps.
If you did that, try another base rom (XXKPU) and then flash CM9 on it.
Click to expand...
Click to collapse
i could have but last try i tried CM9 it was freezing and i put if offf.... Now the phone is not getting on ? Is phone bricked? i cant go into recovery or download

anuragvivek93 said:
i could have but last try i tried CM9 it was freezing and i put if offf.... Now the phone is not getting on ? Is phone bricked? i cant go into recovery or download
Click to expand...
Click to collapse
If it was working fine before you turned it off, it's probably not a brick.
Maybe it's a hardware failure?
Try using the reset button between the speaker and the camera and try to turn it on (Search to find pictures about it).
If that doesn't work, keep trying to access download, if that also doesn't work, it's probably hardware related, although that in my opinion would be weird.

RemICS v1.6 mobile data issue

I have flashed with chinmay_7d's RemICS v1.6 . Yeak it looks cool, but I am facing an issue. When I turn on mobile data usage, the phone will turn off after some time (5-6 minutes) and it is not possible to turn on the phone again . It is needed to plug in it and turn on and then only it is working. In this condition, it is showing android is upgrading. There is no problem with using internet while plugged in. Anyone know how to fix this...? I like this ROM very much and so if it if fixed, then that will be cool.

are u coming from earlier versions of RemICS? followed all the installation steps?, go back to re-flash and tell us

tavomt said:
are u coming from earlier versions of RemICS? followed all the installation steps?, go back to re-flash and tell us
Click to expand...
Click to collapse
Yes I am .Actually this issue was with 1.5.4 also. I have followed all the steps and cleared dalvik Cache and formatted cache partition. I have even done the factory reset and wiped all apps. I think the issue is because, it is reading the battery profile incorrectly or battery is actually drained when mobile data is turned on and that is triggering switch off thing.

alwinaugustin said:
Yes I am .Actually this issue was with 1.5.4 also. I have followed all the steps and cleared dalvik Cache and formatted cache partition. I have even done the factory reset and wiped all apps. I think the issue is because, it is reading the battery profile incorrectly or battery is actually drained when mobile data is turned on and that is triggering switch off thing.
Click to expand...
Click to collapse
Not sure if I'm right, but I think the practical solution to your problem would be to perform a flash from 0 up KPQ or KPU (which are the most stable to install this ROM), it may be the modem or the base ROM you used (for 3 months I have this ROM and never gave me any problems with KPQ)
Another thing, have you tried testing with Dhiru CM9 Base? to see if the same thing happens?

alwinaugustin said:
Yes I am .Actually this issue was with 1.5.4 also. I have followed all the steps and cleared dalvik Cache and formatted cache partition. I have even done the factory reset and wiped all apps. I think the issue is because, it is reading the battery profile incorrectly or battery is actually drained when mobile data is turned on and that is triggering switch off thing.
Click to expand...
Click to collapse
Have you tried to fix permissions on CWM? I got some problems with it too. After fixing and installing 1.5.4 again no problem. Now I'm on 1.6 and all is fine...

@ tavomt :
I think I can directly flash to stock rom.

Please help me
sI have tried fix permission and after that also this issue persists.
Also I have flashed with CM10 alpha from dhiru. This is also showing the same behavior. :crying:
Now flashed with RemICS JB . But the issue is still there. :crying::crying::crying:
I think I need to go back to REMICS 1.0, as there is no issue on it. But I desperately like to use this ROM. If anyone has got a fix, please post and help me.
Sometimes, when I take apps also , the phone gone off (Google Currents and Angry bird )

alwinaugustin said:
Now flashed with RemICS JB . But the issue is still there. :crying::crying::crying:
Click to expand...
Click to collapse
What is your baseband version? Mine is xle4 and have no such problem using remics(kernel bam & chaos) and rem-jb. Try using 2g only for a day, and see if the problem still persist.
Sent from my GT-I9003 using xda app-developers app

issobuddy said:
What is your baseband version? Mine is xle4 and have no such problem using remics(kernel bam & chaos) and rem-jb. Try using 2g only for a day, and see if the problem still persist.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
my baseband version is I9003DDKP3 . Actually i am using 2G and use 2G network is already ticked

alwinaugustin said:
sI have tried fix permission and after that also this issue persists.
Also I have flashed with CM10 alpha from dhiru. This is also showing the same behavior. :crying:
Now flashed with RemICS JB . But the issue is still there. :crying::crying::crying:
I think I need to go back to REMICS 1.0, as there is no issue on it. But I desperately like to use this ROM. If anyone has got a fix, please post and help me.
Sometimes, when I take apps also , the phone gone off (Google Currents and Angry bird )
Click to expand...
Click to collapse
The issue you are facing is exclusive to you. So i will not consider this a bug from my ROM.
I suggest you to follow correct flashing procedure. Wiping data before flashing a new ROM is a good practice.
It is possible that a third party app you are using is responsible.
Sent from my GT-I9003

Hmmm... but I have tried it also..now I think its better go back to stock . Can anyone give me the URL to download latest stock for our phone.....?
Sent from my GT-I9003 using xda app-developers app

alwinaugustin said:
Can anyone give me the URL to download latest stock for our phone.....?
Click to expand...
Click to collapse
Here?
http://forum.xda-developers.com/showthread.php?t=1133787
Sent from my GT-I9003 using xda app-developers app

Issue persists in Stock also
:crying::crying::crying:
The sad thing is that the problem persists after flashing stock ROM also. I have first flashed to XXKPE and then to XXKPU using Odin as given in the following link
http://blog.vigitalsolutions.com/2012/08/18/upgrade-samsung-galaxy-sl-i9003-to-cyanogenmod-9-cm9/
The issue is there in both the stock ROMS. Actually this issue was not present before. Now don't know what to do. I am only able to connect to internet in plugged in state.
Some times it turns off during call also .
:crying::crying::crying:

[Q] Complete freeze

I have the latest stock JB installed from the google factory images with simple root v1.0 and clockworkmod recovery 5.0.2.0, and my phone completely freezes from time to time. If I push the power button the screen goes off, but if I push it again, only the buttons light up, so I have to pull out my battery to reset it. It happens more and more and it get's really annoying. I just had a full wipe a couple days ago, and it did the same thing before, but I didn't had any problems like this with ics. Anyone else having similar problems or is my phone getting crazy? Any advice?

It's called sleep of death. Try to flash another kernel see if that works.
Sent from my Nexus S

kwibis said:
It's called sleep of death. Try to flash another kernel see if that works.
Sent from my Nexus S
Click to expand...
Click to collapse
Thx! Didn't know what it was called, now I can look into it!

Good luck!

kwibis said:
It's called sleep of death. Try to flash another kernel see if that works.
Sent from my Nexus S
Click to expand...
Click to collapse
What? He has stock JB, with the stock kernel. There's hardly anything more stable than that....

The graphics driver had been throwing bugs, but the new r6 release had an update so possibly fixed bug. May be the cause of the OP issue

polobunny said:
What? He has stock JB, with the stock kernel. There's hardly anything more stable than that....
Click to expand...
Click to collapse
Haven't had my phone running stock so I cannot tell whether it is very stable. But the problem he described indicates this particular issue. And now bedalus confirms.
Sent from my Nexus S

[Q] Hardware issue?

Does anyone have a problem with random "pauses" while using apps? It's totally not noticeable for applications that aren't continually running animations (ie: kindle, text scrolling) but becomes evident when doing thins such as:
- recording video (the "pause" will cause the recording to stop randomly for both continuous and time lapse)
- playing games (will cause the game to go to the pause screen)
- tasker programming (I think this is affected because tasker will randomly close itself without a FC dialog, profiles and tasks seem okay)
I turned on debugging to see if it was a dirty screen or anything, but the touch coordinates don't change at all when the "pause" happens. Anyone have an idea how I can fix this? It is rather crippling to the N5.
I am rooted and I have seen this problem on all roms (and I believe I noticed it on stock too...)
I use a ballistic case, if anyone else has had problems with it...
Thanks in advance!
Using N5 on Carbon + Franco kernel

I guess no one's ever had this problem before? =[

Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar

Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app

mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
I've tried out a few roms (factory reseting and cache clearing between each one) to see if it was any one problem, but whether AOSP or CM based, I still have the problem =/
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!

Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!
Click to expand...
Click to collapse
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?

mistahseller said:
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?
Click to expand...
Click to collapse
I used the Chainfire's autoroot (http://forum.xda-developers.com/showthread.php?t=2507211) on Windows.

mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm, I think it worked. I haven't tested it out for lengthy periods of time but I haven't noticed any pausing anymore! =]
I followed the unroot instructions to return to stock. Although I didn't relock the bootloader.
Then I booted up stock and it seemed like it works fine.
I reinstalled CWM recovery through adb (same as I did the first time) and proceeded to reflash
It seems like the problem is gone now on custom ROM as well. Interestingly enough, if I nandroid restore my old backup, I do get the problem again.
Is there something different between reflashing stock part and wiping from factory/data reset + system partition format + wipe cache + wipe davalik?
Thanks for your help guys! I was sure before that it was hardware since I had the problem on stock w/ root, but thankfully it's not a hardware problem! =]

Phone won't stay off

Running stock Lollipop rom with Franco R68. Rooted with CFAR. Since I flashed latest TWRP this afternoon the phone won't shut down. Every time I turn it off it turns back on after a few seconds. Not a major problem but is this happening to anyone else?

pepdavies said:
Running stock Lollipop rom with Franco R68. Rooted with CFAR. Since I flashed latest TWRP this afternoon the phone won't shut down. Every time I turn it off it turns back on after a few seconds. Not a major problem but is this happening to anyone else?
Click to expand...
Click to collapse
i dont have this particular issue but i found 2 other threads stating this issue here and here

Haven't seen it yet but I had it on KitKat randomly. I don't have a clue how to fix it, reboot don't help.

Pretty sure this is an r68 issue, I'm sure franco will fix this soon!

pepdavies said:
Running stock Lollipop rom with Franco R68. Rooted with CFAR. Since I flashed latest TWRP this afternoon the phone won't shut down. Every time I turn it off it turns back on after a few seconds. Not a major problem but is this happening to anyone else?
Click to expand...
Click to collapse
not because of twrp.
the recovery and rom are in two different partitions. most likely its an app causing the issue.

nexus.freak said:
i dont have this particular issue but i found 2 other threads stating this issue here and here
Click to expand...
Click to collapse
Thanks but neither of those issues are the same as mine

It was Franco. All fixed now. Thanks

pepdavies said:
It was Franco. All fixed now. Thanks
Click to expand...
Click to collapse
Having the same problem too! May I know what the "fix" was? The only way I managed to get rid of it was to reflash r67.

jamentangent said:
Having the same problem too! May I know what the "fix" was? The only way I managed to get rid of it was to reflash r67.
Click to expand...
Click to collapse
Franco uploaded a fixed version of r68