Hey there,
I went from stock to CM10.1 and everything works correctly, except that I get bluescreens and now random reboots. I update nightlies hoping that the problem disappears.
Is there anyone that can help me with that issue. It happens randomly, even when it just sits there doing "nothing".
Please help, I don't want to go back to T-Mobile stock (that's where it last worked)!
ami2510 said:
Hey there,
I went from stock to CM10.1 and everything works correctly, except that I get bluescreens and now random reboots. I update nightlies hoping that the problem disappears.
Is there anyone that can help me with that issue. It happens randomly, even when it just sits there doing "nothing".
Please help, I don't want to go back to T-Mobile stock (that's where it last worked)!
Click to expand...
Click to collapse
You could always use the stable version of CM10. It's still Jellybean, just 4.1.2 instead of 4.2.2. My biggest problems with CM10.1 are bluetooth and connecting it to the PC as a Mass Storage Device. With CM10, I have never had issues.
Go up and read the threads in the general forum. The last really stable cyanogenmod releases were the M3 "snapshot". Anything after that is what you get, random reboots, graphical problems etc. Try that one.
fraughtsigewulf said:
You could always use the stable version of CM10. It's still Jellybean, just 4.1.2 instead of 4.2.2. My biggest problems with CM10.1 are bluetooth and connecting it to the PC as a Mass Storage Device. With CM10, I have never had issues.
Click to expand...
Click to collapse
srpanadero said:
Go up and read the threads in the general forum. The last really stable cyanogenmod releases were the M3 "snapshot". Anything after that is what you get, random reboots, graphical problems etc. Try that one.
Click to expand...
Click to collapse
Ok i will try the M3, and not do the nightlies.
I ll report back if that solved my problem.
Fixed. read post above.
Thank you so much for your help!!
I see problem fixed sorry to hijack but what version of clockword mod are u running. I have 5.5. Orsomething like that but can download and roms? Error 7 keeps popping up. And if i upgrade cwm where and how would that be. Sorry once again
parmakr said:
I see problem fixed sorry to hijack but what version of clockword mod are u running. I have 5.5. Orsomething like that but can download and roms? Error 7 keeps popping up. And if i upgrade cwm where and how would that be. Sorry once again
Click to expand...
Click to collapse
That has nothing to do with the problem. But it is because you are using an old recovery, either update CWM or use goo manager to install TWRP, which is touchscreen anyways. Then you wont have the Error 7 anymore.
Related
Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
and finglha
bradleyrogers89 said:
Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
Click to expand...
Click to collapse
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
lossofsilence said:
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
Click to expand...
Click to collapse
Yea it has happened to me too, I just powered off with a long press on the 'N' and power button. Restarted and it worked fine.
Actually i'm on 10.1 too.
This thing happens sometime. This is normal for early alfa soft.
On first clean install test i had 3 or more times stop on Cyanogen logo. But it started work on fourth time. Same happened with second clean install too (messed Adnroid to death with my hard tests and modifications ). Power OFF/On have sometime magical power.
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
bradleyrogers89 said:
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
Click to expand...
Click to collapse
I have no problem adjusting brightness on 1/28
codya321 said:
I have no problem adjusting brightness on 1/28
Click to expand...
Click to collapse
It's weird. I couldn't get it to work without using the Tablet UI. Once I switched, it started working. Oh well, it's working fine now. Thanks for the help, you guys are the best.
CM 10.1 needs some time for settle. Then it works wthout lag
Sent from my GT-I9100 using Tapatalk 2
Hey Guys!
I recently upgraded from the latest CM9 Nightly to Jscullins 4.1.2 using clockwordmod....i also upgraded my GAPPS....
Whenever i boot up to CM10...it works fine for a minute and then freezes. The only way i can get it out of the freeze is by doing a Hard restart..
When I say "Freeze" i mean the touchscreen stops working...of it just freezes.
How do I fix this??!! Please Help!!
Thanks!
kmanleafs said:
Hey Guys!
I recently upgraded from the latest CM9 Nightly to Jscullins 4.1.2 using clockwordmod....i also upgraded my GAPPS....
Whenever i boot up to CM10...it works fine for a minute and then freezes. The only way i can get it out of the freeze is by doing a Hard restart..
When I say "Freeze" i mean the touchscreen stops working...of it just freezes.
How do I fix this??!! Please Help!!
Thanks!
Click to expand...
Click to collapse
I don't know if it will work or not, but you can give the attached zip file a try.
chicle_11 said:
I don't know if it will work or not, but you can give the attached zip file a try.
Click to expand...
Click to collapse
Thanks but the title says "4.2.2" and i have 4.1.2...and what exactly is it?
kmanleafs said:
Thanks but the title says "4.2.2" and i have 4.1.2...and what exactly is it?
Click to expand...
Click to collapse
Again, I don't know if it will work for not.
It's a fix for touch sensitivity issues.
Make a backup, just in case.
Edit : cm10 needs more room than CM9. Make a backup, then run acmeuninstaller. Use AcmeInstaller 3 to flash the CM10 rom along with the appropriate gapps. You might as well upgrade your moboot to 0.3.8 and and your cwm to 6.xxx. You can find these files in Goo.im, under developers and Jscullins. For cwm use the 12/15 one.
Once installed you can restore your apps using advanced restore in cwm (you want to restore the data only).
Good luck.
Ok...i noticed that it is actually a HEAVY LAG, rather then a freeze. I was able to go into the "Usage" Panel in settings and noticed that i have 148MB in "System" and around 20GB in 'SD Card". When I tried to exit...it froze and the screen turned off and it wouldn't turn back on...I do NOT want to do a complete restore....
kmanleafs said:
Ok...i noticed that it is actually a HEAVY LAG, rather then a freeze. I was able to go into the "Usage" Panel in settings and noticed that i have 148MB in "System" and around 20GB in 'SD Card". When I tried to exit...it froze and the screen turned off and it wouldn't turn back on...I do NOT want to do a complete restore....
Click to expand...
Click to collapse
Well then, I hope you have a backup.
You do need to use AcmeInstaller 3 to flash cm10, or you will keep running into problems.
Edit:make sure that the battery is fully charged before doing anything.
If the tablet remains unresponsive, you might have to use this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you do, you will have to do a complete restore.
Hey there,
I use the cyanogenmod 10.1 since Alpha 1. http://forum.xda-developers.com/showthread.php?t=2094554
This version was just good. I only got problems while using bluetooth...
Yesterday I installed the new version Alpha 2 and only got problems since then. Freeze while using bluetooth, browsing and after finishing a call.
I reinstalled it with Teamwin, but it didn't change anything.
Does anybody know how to fix this?
Greetings
Scarecrow666
Scarecrow666 said:
... This version was just good. I only got problems while using bluetooth...
Click to expand...
Click to collapse
Hi!
CM 10.1 has known issues with bluetooth, and more precisely, with bluetooth headsets and car audio. You can't help that. You can also read their forums, where lots of people complain about that.
Also, you are installing beta 2 and not alpha 2, right? Because beta 2 is the newest.
Also, you are installing beta 2 and not alpha 2, right? Because beta 2 is the newest.
Click to expand...
Click to collapse
Yeah of cource... my mistake. I read about the problems with bluetooth...but that has nothing to do with my problems of this beta 2.
Browsing is impossible and I have to restart my phone after every call because it freezes.
Scarecrow666 said:
Yeah of cource... my mistake. I read about the problems with bluetooth...but that has nothing to do with my problems of this beta 2.
Browsing is impossible and I have to restart my phone after every call because it freezes.
Click to expand...
Click to collapse
After that much updating it is recommened you do a factory reset and a full system wipe. Then install the rom + gapps. issues should be fixed then
mrjraider said:
After that much updating it is recommened you do a factory reset and a full system wipe. Then install the rom + gapps. issues should be fixed then
Click to expand...
Click to collapse
Ok thank you
I'll try that later and post you the result
did as you say,
now, I can say that browsing is working. But after I put the calendar on the home screen the phone crashed again.
now it even freezes while booting
Hmm a clean install is recommended. Meaning:
Start from stock android from sammy and flash back to CM 10
mrjraider said:
Hmm a clean install is recommended. Meaning:
Start from stock android from sammy and flash back to CM 10
Click to expand...
Click to collapse
I did.
But still some problems:
- freeze while browsing (turned flash etc off and it worked...)
- face unlock
But that's fine. I can make calls with my mobile phone again and I can move the widgets
Thank you for your help so far!
I experience random restarts despite of the ROM I have flashed. I have tried JellyBeer ROM, PA ROM, Stunner ROM, Sweet ROM and many more with their respective default kernel. My stupid phone even restarts in CWM and trying to flash a new ROM.
What could be the issue? How can I get this fixed?
Random restarts are quite common with ROMs under development or if not flashed properly. Update the ROM to a stable version or re-flash the ROM wiping cache, factory reset and see. You can flash a stable ROM to get rid of the problem.
All wipes and reflash may solve your problem...
Varad297 said:
Random restarts are quite common with ROMs under development or if not flashed properly. Update the ROM to a stable version or re-flash the ROM wiping cache, factory reset and see. You can flash a stable ROM to get rid of the problem.
Click to expand...
Click to collapse
benito.brazil said:
All wipes and reflash may solve your problem...
Click to expand...
Click to collapse
I always flash a stable version of the ROM with a full wipe. Even I format preload,cache,system, etc. Whatever ROM I flash it does not help.
But I simply can not understand what cause the restarts on my phone ?
No harm in just re-flashing a ROM. I face random restarts on the PAC currently, this is a common problem. Else try one of the stable 4.1.2 TW ROMs. Hope you don't face a restart then!
It might be a app you are using. Install catlog from play store and find the cause. You say it happens on all ROMs you flash. Is there any particular app you restore
#Galaxtus - Over and Out
Varad297 said:
No harm in just re-flashing a ROM. I face random restarts on the PAC currently, this is a common problem. Else try one of the stable 4.1.2 TW ROMs. Hope you don't face a restart then!
Click to expand...
Click to collapse
Yes. I'm using sweet ROM v9. I still get random starts here and there.
Galaxtus said:
It might be a app you are using. Install catlog from play store and find the cause. You say it happens on all ROMs you flash. Is there any particular app you restore
#Galaxtus - Over and Out
Click to expand...
Click to collapse
Thanks I'll try this for sure and let you know. I have installed the app. Can you please tell me how can I use this to make sure what's the problem ?
If you're getting random reboots on TW and AOSP based Roms, I would suspect an app driving the system nuts.
AA1973 said:
If you're getting random reboots on TW and AOSP based Roms, I would suspect an app driving the system nuts.
Click to expand...
Click to collapse
I only use well reputed apps such as Facebook, solid explorer, google handouts, flipboard etc
Facebook App has a good reputation? Would be new to me. Look at their app reviews and star(s) on Google play.
try a proper stock rom with en see if it happens.
Galaxtus said:
It might be a app you are using. Install catlog from play store and find the cause. You say it happens on all ROMs you flash. Is there any particular app you restore
#Galaxtus - Over and Out
Click to expand...
Click to collapse
Can you please tell me how to use this app to pin point the issue? I have already installed it.
AA1973 said:
Facebook App has a good reputation? Would be new to me. Look at their app reviews and star(s) on Google play.
Click to expand...
Click to collapse
I mean like they are used by everyone plus I have been using it for a year now. Never had a problem. I always use the apps that I have been using for a long time. Nothing new
My stupid phone even restarts in CWM and trying to flash a new ROM. What could be the issue?
dasunh said:
My stupid phone even restarts in CWM and trying to flash a new ROM. What could be the issue?
Click to expand...
Click to collapse
Option 1>>>Open Catlog and press record and minimize it has it will start the log process. Use your phone normally and see anything happens.
Option 2>>>I would suggest you one thing flash any ROM best choose CM base ROM and flash gapps and reboot. Don't sign in to google just cancel the process and add it later from settings. Live it stock without loading any apps and see if it reboots for you.
Option 3>>>Might be a faulty motherboard don't know. Was the case when you brought the phone in the first place?
#Galaxtus - Over and Out
Galaxtus said:
Option 1>>>Open Catlog and press record and minimize it has it will start the log process. Use your phone normally and see anything happens.
Option 2>>>I would suggest you one thing flash any ROM best choose CM base ROM and flash gapps and reboot. Don't sign in to google just cancel the process and add it later from settings. Live it stock without loading any apps and see if it reboots for you.
Option 3>>>Might be a faulty motherboard don't know. Was the case when you brought the phone in the first place?
#Galaxtus - Over and Out
Click to expand...
Click to collapse
Thanks for the info. I really appreciate it mate. I have clicked the thanks button
Once I got the phone it was working fine. I'm not sure about the power button too. I'm working on it to figure out whether it's the kernel or the ROM the power button.
You can try the following:
1. re-flash the samsung stock rom ....i would recommend you go with Official ICS Rom 4.0.4. Perform a clean data wipe, cache and dalvik cahe.
2. Do not use any other apps other than whats included in stock rom. Observe carefully for 2-3 days.
3. If all goes smooth, you can try installing well-known apps like facebook, whatsapp, etc etc
4. if you still have issue, i suggest you change your battery. Go for the official samsung battery only. Observe your phone's behavior.
Hope it helps you
HAve you ever tried to change the battery. I saw lots of Note batteries gone bad after 9-12 months. I could be the reason. Not sure though.
How do i fix this? I'm using stock 20c as my primary and have installed all the necessary files as well as a hexec comp. kernel (optimus prime 2.7) . I tried booting up slimbean 4.3 with iodak v8 but the phone shuts down instead of booting. Also tried slimbean 4.22 with no luck using the patched cm kernel in the multirom thread, iodak, and optimus prime 2.7 cm version but the phone still shuts down after hitting the boot option. Have also tried deleting and reinstalling but no luck. YES, I'VE SEARCHED FOR MY PROBLEM AND LOOKED AT EVERY SINGLE POST IN THAT THREAD AT LEAST TWICE and none of the posts help with my issue, I've seen my problem mentioned a couple of times but the authors somehow fix it without posting why or have a completely different issue. Is there anyway to fix my problem?
juanacevedo said:
How do i fix this? I'm using stock 20c as my primary and have installed all the necessary files as well as a hexec comp. kernel (optimus prime 2.7) . I tried booting up slimbean 4.3 with iodak v8 but the phone shuts down instead of booting. Also tried slimbean 4.22 with no luck using the patched cm kernel in the multirom thread, iodak, and optimus prime 2.7 cm version but the phone still shuts down after hitting the boot option. Have also tried deleting and reinstalling but no luck. YES, I'VE SEARCHED FOR MY PROBLEM AND LOOKED AT EVERY SINGLE POST IN THAT THREAD AT LEAST TWICE and none of the posts help with my issue, I've seen my problem mentioned a couple of times but the authors somehow fix it without posting why or have a completely different issue. Is there anyway to fix my problem?
Click to expand...
Click to collapse
Honestly man I do not think that you really search because I answered this question twice ...
Anyway to boot your second 4.3 ROM, you need either to put your phone on charge and then select Slim OR just after having selected Slim, wait one second and then hold the power button as if you wanted to turn on your phone. These two methods will boot your second ROM.
The last method is easier but longer in time : you need to backup your two ROMs and then invert their position ... I don't think I'm really clear ... In your case you need to have Slim as first ROM and Stock as second.
All your ROMs will then boot normally without any trick
Sent from my LG-P880 using xda premium
juanacevedo said:
How do i fix this? I'm using stock 20c as my primary and have installed all the necessary files as well as a hexec comp. kernel (optimus prime 2.7) . I tried booting up slimbean 4.3 with iodak v8 but the phone shuts down instead of booting. Also tried slimbean 4.22 with no luck using the patched cm kernel in the multirom thread, iodak, and optimus prime 2.7 cm version but the phone still shuts down after hitting the boot option. Have also tried deleting and reinstalling but no luck. YES, I'VE SEARCHED FOR MY PROBLEM AND LOOKED AT EVERY SINGLE POST IN THAT THREAD AT LEAST TWICE and none of the posts help with my issue, I've seen my problem mentioned a couple of times but the authors somehow fix it without posting why or have a completely different issue. Is there anyway to fix my problem?
Click to expand...
Click to collapse
I Got same Problem, but With offial stock 4.1.2 AS secundary. When i Boot it it "shuts down", but i can't Start anything after it. I need To remove akku To get it up again...press power button after multrom Boot works for me...is that normal ? :/
Sent from my LG-P880 using xda app-developers app
The "ectoplasma22" solution worked, I thanked him with the button, but I do it publicly, thank you!
This is my first message, I have yet another 9 to be able to write in the multirom development section, to report this bug, the solution is not elegant, and this problem must be seriously considered.
PS. Of course, respecting the times of the developers and their dedications. Thanks everyone!