Every now and then (like 1 every 3-4 times) when I use the camera app, the entire phone locks up and the only thing that I can do is take off the back cover and remove the battery. This has happened to me twice now. I think that both times that this happened, I was trying to record a video.
Has anyone encountered this problem ?
My G2X is running the newest build of Cyanogen 7 (GB 2.3.4).
This is really annoying me. Has anyone found a solution if you are experiencing this ?
This happen to me when I OC to 1.5ghz.
I test again by lowering to 1.2 ghz and problem ended.
if you oc..lower it..or test another kernel.
I do use setCPU but the only thing that I do with it is set the CPU to 216 when the screen is off. I don't do any overclocking otherwise.
I am having the same freezing issue also. When I switch from camera to video it freezes every time and I have to do a battery pull. I'm running Cyanogen 7 Nightly. Did you find out any info on a fix for this? I've googled everything I could and didn't find anything.
Related
I've been using my Captivate for recording videos recently and the camera has just been randomly locking up. I started experiencing this way back on Cognition 3.02, and now it still happens on Cognition 4.1.1 and CyanogenMod7. The camera just freezes in the middle of recording, I could be in the middle of recording something and it can happen from 3 seconds into the video to 40 seconds. Then the camera doesn't work at all and takes forever to load. Is there a fix for this?
I currently have CyanogenMod7 on my phone.
-Thanks
Well I've heard that CM7 isn't exactly stable, so that might be the issue. But I'm not sure what to tell you about it happening on any version of Cognition. That's a hella stable ROM.
Does anyone have a fix for this at all?
Hey guys, tried a search but couldn't find anything. I am running a rooted stock 2.3.3 with faux kernel and for the longest time I had GPS disabled without knowing it (what can I say, I'm good with directions). I recently enabled it and have been getting reboots at random times while it is on. I turned it off today and have not had a crash yet, so I assume this is the problem.
Has anyone had or fixed this? I have thought about installing the weapon ROM, seems to get a lot of positive reviews for stability which is most important to me. If there is an easy fix though, I'd rather just stay put on my current setup.
Thanks!
It did the SOD thing last night when I was sleeping (had GPS off the whole day) so I figured something was buggy and wiped it to install weapon. Hopefully it works out *crosses fingers*.
Hey everyone,
I've been having issues with Carbon Rom running the kernel it came with for a few days now and was wondering if anyone else is seeing the same issue. Randomly when the phone is put into sleep mode I can't wake it back up. It doesn't happen with any consistency. I could wake it up 10 times and it will be fine and other times after trying to wake it up once it won't. I have to soft reset to get it back up and running again. I've adjusted the performance settings from the default minimum 384 MHz to 486 MHz and am now running it at 594 MHz and it seems ok for the moment. I know that some phones don't like having the processor dialed back to the minimum without having issues like I'm having.
Can anyone give me some insight into what the "normal" frequency should be or if you have another answer it would be appreciated. I did a full wipe as well as cache when I originally flashed it from the stock rom. I haven't done any other tweaking to it otherwise. Thanks in advance for any insight you can give.
grenadejumper23 said:
Hey everyone,
I've been having issues with Carbon Rom running the kernel it came with for a few days now and was wondering if anyone else is seeing the same issue. Randomly when the phone is put into sleep mode I can't wake it back up. It doesn't happen with any consistency. I could wake it up 10 times and it will be fine and other times after trying to wake it up once it won't. I have to soft reset to get it back up and running again. I've adjusted the performance settings from the default minimum 384 MHz to 486 MHz and am now running it at 594 MHz and it seems ok for the moment. I know that some phones don't like having the processor dialed back to the minimum without having issues like I'm having.
Can anyone give me some insight into what the "normal" frequency should be or if you have another answer it would be appreciated. I did a full wipe as well as cache when I originally flashed it from the stock rom. I haven't done any other tweaking to it otherwise. Thanks in advance for any insight you can give.
Click to expand...
Click to collapse
i started having this issue on the 6/11 build as well as a few other issues(see my posts on the carbon thread)...i had to revert back to the 6/04 build
Thanks for the help. I'll have to do the same. The latest nightly seems even worse. I've had SOD at least half a dozen times in the last half hour.
In the last weeks, I started to have an issue with "android os" going crazy without reason.
It's happening on WIFI or HPSA+
I noticed that sensors.qcom is always in my list when it is happening. I'm on stock (rooted) and I made a clean reinstallation of the OS a few days ago , and I installed only half of my apps... and the bug is already back ! so I'm trying to find what app is starting this issue (Don't get me wrong, the bug is probably on the google side , however, I'm sure there is an app starting it). Yesterday I uninstalled Greenify (I only had 2 apps greenified) and so far so good ... not sure if it is linked yet.
btw, BBS is no help with this issue.
anyone has the same problem here ?
on this thread, a few people are talking about sensors.qcom : https://productforums.google.com/forum/m/#!msg/nexus/HV2TICIjX9U/WbZ8yOfNBbsJ
Hopefully you figured it out but I just had this issue starting today. BBS didn't help either but for me the fix came when I switched off Lens blur in the camera. I took a picture yesterday and didn't finish editing in after doing a lens blur. Switching it back to regular camera mode fixed my issue. My guess is some app is using one of the physical sensors so try looking there.
Matrix_19 said:
In the last weeks, I started to have an issue with "android os" going crazy without reason.
It's happening on WIFI or HPSA+
I noticed that sensors.qcom is always in my list when it is happening. I'm on stock (rooted) and I made a clean reinstallation of the OS a few days ago , and I installed only half of my apps... and the bug is already back ! so I'm trying to find what app is starting this issue (Don't get me wrong, the bug is probably on the google side , however, I'm sure there is an app starting it). Yesterday I uninstalled Greenify (I only had 2 apps greenified) and so far so good ... not sure if it is linked yet.
btw, BBS is no help with this issue.
anyone has the same problem here ?
on this thread, a few people are talking about sensors.qcom : https://productforums.google.com/forum/m/#!msg/nexus/HV2TICIjX9U/WbZ8yOfNBbsJ
Click to expand...
Click to collapse
This is a big issue on alot of phones with Qualcomm cpus. My suspicion is its a hardware fault more common than people think.. Most people don't notice it especially heavy phone users, it will blend in well with other usage. Another reason is because it can stop by itself sometimes and doesn't happen nonstop. It is random.
Facts I know.
Whenever sensors.qcom shows up in battery stats, it will also be accompanied by high Android OS usage. Battery stats is not accurate, this bug could consume 50% of battery and it might just say 2%.
Check Cpu-z you will see all sensor information is missing.
CPU is constantly running near full speed.
It appears to be completely random, happening mid standby.
It is not caused by any app. I have tried on a completely stock rom.
Check wakelock detector kernel tab, you will see the wakelocks that cause this (there is millions)
You can fix it by restarting phone or enabling/disabling some sensors. Last time I had this happen (yesterday) my phone had lost 25% in 4 hours standby. I stopped it by enabling autobrightness and all sensors information returned in cpu-z along with cpu speed going back to normal. It is not caused by having auto brightness off however, just the toggling of sensors seems to stop it.
See my threads here
http://en.miui.com/thread-87409-1-1.html
http://en.miui.com/thread-63939-1-1.html
I listen to allot of online radio eg 'tunein' and mp3 stored on my phone, problem is that this phone plays back audio choppy when the screen times out.
This happeneds esspecially when streaming audio - its intermittent with mp3s..I have had allot of phone and Ive never ever had this kinda problem before...
Im rooted and have played with the stock kernel settings abit but have no change in behavior,.. Anyone know what I can do here? I hate to have one of the most advanced unusable phones ever
JF-GINO said:
I listen to allot of online radio eg 'tunein' and mp3 stored on my phone, problem is that this phone plays back audio choppy when the screen times out.
This happeneds esspecially when streaming audio - its intermittent with mp3s..I have had allot of phone and Ive never ever had this kinda problem before...
Im rooted and have played with the stock kernel settings abit but have no change in behavior,.. Anyone know what I can do here? I hate to have one of the most advanced unusable phones ever
Click to expand...
Click to collapse
When I was on my Note 2 I had to increase the low end on the cpu speed. I think the Lowest I could use was 400 to 500 (sleep mode) I own the setcpu pro app so it was easy to adjust. Give that a look see. Every time the screen went off while Bluetooth was on it would skip and shutter. I noticed today my Edge seems to have the same problem.
Charles
ceabbott2 said:
When I was on my Note 2 I had to increase the low end on the cpu speed. I think the Lowest I could use was 400 to 500 (sleep mode) I own the setcpu pro app so it was easy to adjust. Give that a look see. Every time the screen went off while Bluetooth was on it would skip and shutter. I noticed today my Edge seems to have the same problem.
Charles
Click to expand...
Click to collapse
Hey, you too eh? hmm,.. I tried raising the cpu limit with no change,.. mine does stay awake on bluetooth only... anywho, there is not much I can do with the stock kernel., I tried just about everything, scripts, build hacks,.. no I noticed that Wifi does not stay connected and only gets max 3mps - Ive been thru 2 phones and this Canadian version is buggy, have no problems with my note 3 or my LG , wish I could figure all this out. or wait for a custom rom/kernel for my variant
JF-GINO said:
I listen to allot of online radio eg 'tunein' and mp3 stored on my phone, problem is that this phone plays back audio choppy when the screen times out.
This happeneds esspecially when streaming audio - its intermittent with mp3s..I have had allot of phone and Ive never ever had this kinda problem before...
Im rooted and have played with the stock kernel settings abit but have no change in behavior,.. Anyone know what I can do here? I hate to have one of the most advanced unusable phones ever
Click to expand...
Click to collapse
Make sure power saving mode is off if not try turning that off and it may resolve the issue.
Also like in one of my previous posts on my device anyway I've been experiencing what I'd describe as antenna issues. Both wifi drops and blue tooth cuts in and out. Doesn't matter if the screen is on or off for me
when I experience these issues.