Database Info

CM 4.2.11.1 Camera and Home Screen issues

Firstly I'd like to thank PSYCHO13OI on the #cyanogenmod IRC channel for spending quite a bit of his time helping me out. I thought I might just throw my problem out there.
I received my new HTC Magic a few days ago, but spent quite a few days prior researching different ROMs.
I've got a 32A that came from 3 Australia.
Firstly, a summary of what I originally did.
After receiving my phone and playing around with the original ROM;
1) I fastbooted into: recovery-RA-sapphire-v1.5.2H.img.
2) I wiped data, and wiped a non-existant ext partition.
3) I partitioned the SD card using 32MB swap-size and a 256MB ext partition. Further I used ext2 -> ext3.
4) Loaded and flashed the following in order:
- DRC83_base_defanged
- update-cm-4.2.11.1-signed
5) Rebooted.
After 30 minutes of the original boot splash screen, I took the battery out (I couldn't, and still can't, figure out how to hard power off) and re-fastbooted into the recovery image.
6) I reperformed steps 1-4, this time actually flashing the kernel port: bc-4.2.11.1-ebi1-signed. I also repartitioned the SD card using a swap size of 256MB and ext partition of 1024MB and went from ext2 -> ext3 -> ext4.
7) Rebooted again.
8) When I get to the "Touch the android to begin." screen, I got this error message:
Sorry!
The process com.android.
phone has stopped unexpectedly. Please try again.
My only option is to force close which still allows me to touch the android and proceed as normal. Otherwise, everything seemed fine and dandy.
A few days later I decided to try using the Camera and Camcorder apps. This caused a reboot. This did not happen on the original ROM.
After the reboot I noticed that the home screen hung after trying to swipe my home screen. This eventually lead to the error message (after 10 seconds or so):
Sorry!
Activity Home(in process
android.process.acore) is not
responding.
I was prompted with the option to either force close or wait. Choosing either will restore complete functionality in 20-30 seconds.
Now this happens after every reboot (and I'm uncertain whether or not it is related to the Camera issue).
Trying to fix both issues, I repeated the flashing process, this time wiping the dalvik-cache as well.
Still no go. I've made the logcats of the first boot after reflashing CM 4.2.11.1 as well as a reboot. I have also linked my last_kmsg after rebooting due to the Camera app crash.
1st Boot: http://pastebin.com/m356cf97e
Reboot: http://pastebin.com/m69a15127
last_kmsg: http://pastebin.com/m76c42ee6
This camera issue is touched on here: http://code.google.com/p/cyanogenmod/issues/detail?id=792
As for the Camera issue, similar to the OP in the above thread, I only have issues when on battery power. However, I do not have any issues in other apps that utilize the camera such as barcode readers.
Things I have not tried:
- Another CM version.
- Wiping battery information or anything else other than data/ext partition/dalvik-cache.
- Reflashing an original ROM (which I did not backup - my friend's Magic is coming in the next week or so, so I'll grab his image).
Hopefully I've documented everything important (and perhaps trivial). I'm open to any suggestions.
EDIT: Some things I forgot to mention.
- 8GB Class 4 SD card
- Added details to my original post about partition sizes/types.

It seems I was wrong about rebooting only in the default Camera and Camcorder apps as I just recently experienced a reboot on the Barcode Scanner app.

Perhaps try an older version of cm. I had more stability on some of the older releases

What would be one of the more stable versions?

i always find CM has better themes and mods "BUT" the rom is laggy. in fact, amon's rom is fast and clean but not much of any theming. wasted.

scyzerd said:
What would be one of the more stable versions?
Click to expand...
Click to collapse
i'm back to 4.2.9.1 atm because it's a little less buggy. something like that or 4.2.8.1 or 7.1 maybe? go for the .1 versions because they will contain bug fixes for any known issues in the first release at that number...

I have that problem too... but I don't get it as often now. maybe once in a blue moon.....
there is two things I notice that when the reboot happens in the camera mode.
1) there are too much tasks running (you can notice it because the phone runs a little laggy, or if you check Taskskiller and the memory running low)
2) the audible selection is turn on
so now I watch taskskiller before I used the camera and reboot deson't happen that often, specially with the audible selection turn off.
let me know if you guy discover some other fix....

I wonder why in the world did you make such a big swap partition, since you have a 32A model you don't need any swap to run the CM ROM. To be honest CM works flawlesly without the SWAP partition on my phone which is also 32A. I have no problems with the homescreen nor the camera. Please try to repartition the SD card so it doesn't use the SWAP partition, you can also ditch the ext partition as the 32A model has more than enough space for applications installation (about 295MB space). Wipe and reinstall from scratch. Enjoy a working CM 4.2.11.1 build, you can even try 4.2.12.2
EDIT: ehhh, and if you encounter an alarm clock bug where the screen doesn't turn on when the alarm goes off, replace the existing alarm application (AlarmClock.apk) with the one provided in release 4.2.9. You lose some functions in the alarm clock but it works

Same problem different ROM
I'm having the same problem on a Rogers Magic 32A using AmonRa's Donut ROM.
The phone reboots after the 1st or 2nd restart of the camera. Plugged in to a charger, I can restart the camera at least 10 times. This isn't surprising since I did a wipe and reinstall the ROM and the problem still occurred with no other apps installed. Very strange.

I have the same problem...No not so much after I start using an other cam app, however the phone still reboots itself.

Sprint Hero Time for data wipe?

I have had a problem occur a couple of times today that has never happened before. I have an extended battery installed(3500mAh). After 2 hours of not using the phone this morning after I pulled it from the charger I noticed the battery was down to 86% when it should have been still at 95% or higher. About an hour after that I went to make a call and the phone would not unlock. In fact it would not respond to any gesture or button push. I had to pull the battery to get it to boot up again. That freezing up has happened twice today. Once with the extended battery and once with the stock battery. Should I wipe the data and start all over again? Or is there another solution?

Have you installed any new programs recently?

No nothing for a couple of weeks now.

Still having a lot of freezes. Should I go to the security settings and tell it to do a factory reset and then start over again with rooting and customizing?

just out of curiosity did you reinstall the location services?

No. The only things I added back in after the last flash were the ringtone trimmer, sound recorder, and the sprint tv.

one thing that I noticed when I had my phone hooked up to ddms looking at the debug log I had a RSS reader app that was add supported and every 30 seconds it would search for and dowload a new add. once I got rid of that app it seemed to help.
another thing that really helped was I downloaded an app called "overclock" it let me set my CPU to 528 when the screen was active really helping with the speed and how fluid the scroll in menu's is, but it also lets you set it to like 128 when the screen is off. seems to really help with battery life as well.

What is throwing me for a loop is that the phone sleeps like it is supposed and I have verified this with spare parts show I am not sure why all of a sudden the battery is draining much faster than before. As far as the lockups, they are just temporary freezes, it locks and I have to remove the battery to get it to reboot.

Well I wiped the data then flashed to the newest sprint rom(1.56) and then rooted again. I then wiped data again and then flashed to fresh 1.1 and installed my apps and setup my home screens. So far no problems and it seems to run a lot faster and smoother.

Quick off-topic question:
When you say "wipe your data" does that mean you rm the /data directory? Or what? Just curious

No. I used Wipe in the recovery screen.

i just did a upgrade on my hero too from fresh 1.0 to 1.1
when you select wipe data from recovery mode, besides wiping data with option 1, do you choose option 2 as well ? wipe dev something. i wasnt sure what the 2nd wipe option is for, so i did the first option only and it only took 2 sec to complete that step. my phone is up and running with fresh 1.1 without any issues, so did i do it rite ? just outta curiosity

The second one is the cache. I think it gets rebuilt anyway on the first boot with fresh installed.

[SOLVED] LGO3D randomly shuts off.

My newly bought shiny LGO3D phone has a habbit of randomly shutting itself down no matter what ROM / Firmware i have on it.
I've tried stock, king ROM, and a few others. all randomly shutdown. i wouldnt mind if it had rebooted by itself at least it would come back on but it just goes off!
i reach into my pocket -- lo and behold the phone is off!
I've read lots of Optimus2x threads about a similar issue ... some blame the android system and some blame the hardware.
i wonder why there isnt a log in the android system describing an error or whatever?
can anyone help?

maybe your battery is a bit loose?
go stick some strips of paper at the bottom edge of the battery to make sure its nudged tight.
not sure, maybe a possible solution

i think i may have solved this issue...
what i did was this:
install CWM and reboot into the CWM menu.
i deleted everything. cache, delve cache, battery stats, everything thats deletable i did it.
i am currently using king_rom (which was doing the same problem for me to start with) and i can say the phone has been running ok for about 2 days now.
keeping fingers crossed.

usually cache + dalvic + battery states are deleted on every rom flash
if it appears again pull out your sdcard
fixed all reboot issues for me... wonderful to have a phone able to play 3d + record 3d/1080p and cant use a sdcard
hoping the 2.3 update will fix it

Blezz said:
usually cache + dalvic + battery states are deleted on every rom flash
if it appears again pull out your sdcard
fixed all reboot issues for me... wonderful to have a phone able to play 3d + record 3d/1080p and cant use a sdcard
hoping the 2.3 update will fix it
Click to expand...
Click to collapse
i never sacrificed the sdcard though its in there and its working fine.

My P905 is rebooting by itself nonstop

Hello, suddenly when I tried use the stock Camera app to take photo, the device rebooted by itself. This has happened several times. Next, it happened two times that the screen flashed for a few times and then the system rebooted automatically. Now, it is rebooting by itself again and again like crazy. Know what is going on? Is this caused by some kind of automatic software update with buggy software or a hardware failure?

petercohen said:
Hello, suddenly when I tried use the stock Camera app to take photo, the device rebooted by itself. This has happened several times. Next, it happened two times that the screen flashed for a few times and then the system rebooted automatically. Now, it is rebooting by itself again and again like crazy. Know what is going on? Is this caused by some kind of automatic software update with buggy software or a hardware failure?
Click to expand...
Click to collapse
Hard to say.
if I were you I'd first make a full backup (titanium backup if you're rooted) then I'd reflash the firmware through odin and then a factory reset. If the problem is solved, then it is a software issue, and you can restore one by one your apps until you find the one that was causing the problem.
If the problem persists after a factory reset, then is definitively an hardware issue.
---------- Post added at 12:56 AM ---------- Previous post was at 12:55 AM ----------
petercohen said:
Hello, suddenly when I tried use the stock Camera app to take photo, the device rebooted by itself. This has happened several times. Next, it happened two times that the screen flashed for a few times and then the system rebooted automatically. Now, it is rebooting by itself again and again like crazy. Know what is going on? Is this caused by some kind of automatic software update with buggy software or a hardware failure?
Click to expand...
Click to collapse
Hard to say.
if I were you I'd first make a full backup (titanium backup if you're rooted) then I'd reflash the firmware through odin and then a factory reset. If the problem is solved, then it is a software issue, and you can restore one by one your apps until you find the one that was causing the problem.
If the problem persists after a factory reset, then it is definitively an hardware issue.

aviator1 said:
Hard to say.
if I were you I'd first make a full backup (titanium backup if you're rooted) then I'd reflash the firmware through odin and then a factory reset. If the problem is solved, then it is a software issue, and you can restore one by one your apps until you find the one that was causing the problem.
If the problem persists after a factory reset, then is definitively an hardware issue.
---------- Post added at 12:56 AM ---------- Previous post was at 12:55 AM ----------
Hard to say.
if I were you I'd first make a full backup (titanium backup if you're rooted) then I'd reflash the firmware through odin and then a factory reset. If the problem is solved, then it is a software issue, and you can restore one by one your apps until you find the one that was causing the problem.
If the problem persists after a factory reset, then it is definitively an hardware issue.
Click to expand...
Click to collapse
If it's continuously rebooting (boot loop) then titanium would do no good even IF the OP were rooted, the use of titanium backup requires that the OS boots fully and remains stable during the backup process.
I think the best course of action is to get into recovery and let the device sit for a minute or two. If it sits there in recovery without rebooting then at least you know it's not an issue with the power button or other hardware buttons or the battery. At that point, clear cache and then reboot. If a boot loop persists after cache clearing then a factory reset is next, and you'll lose any programs that were installed after initial setup but your data on the SD card and external SD will remain intact.

After about 30 minutes of non-stop crazy self-rebooting, the device became hot but returned to normal. My device is not rooted. What is the best way to back up everything include the S Note contents, Action Memo, photos, etc.?

petercohen said:
After about 30 minutes of non-stop crazy self-rebooting, the device became hot but returned to normal. My device is not rooted. What is the best way to back up everything include the S Note contents, Action Memo, photos, etc.?
Click to expand...
Click to collapse
As far as I could understand you did not have a continuous boot loop but very frequent random boots. In this case you should be able to use Kies to backup your apps and data. If you have a smart card reader you can even backup its contents copying them direcly to a pc and use kies to backup only the data and apps that reside on your internal memory.

Having the same problem
aviator1 said:
As far as I could understand you did not have a continuous boot loop but very frequent random boots. In this case you should be able to use Kies to backup your apps and data. If you have a smart card reader you can even backup its contents copying them direcly to a pc and use kies to backup only the data and apps that reside on your internal memory.
Click to expand...
Click to collapse
My Pro is also rebooting and flikkering. I just plug it into a chager to correct the problem. mine starts doing the flikkering and rebooting when the battery falls to 30 %...

The same here in italy... mine starts the loops at about 50% of battery... do you have lollipop? mine starts the loops after the update... any solution? I have to leave it reboot for one hour ?
@petercohen do you solve it in this way?
thank you!
no rooted note pro 12.2 lte

Revan1988 said:
The same here in italy... mine starts the loops at about 50% of battery... do you have lollipop? mine starts the loops after the update... any solution? I have to leave it reboot for one hour ?
@petercohen do you solve it in this way?
thank you!
no rooted note pro 12.2 lte
Click to expand...
Click to collapse
Me to I'm in Italy and it is three weeks I'm running a rooted lollipop (Flashfire method) with no reboots so far. Just to stay on the safe side I removed Knox and did a factory reset.
The problem looks like a poor electrical contact somewhere, may be the battery connector, or a defective battery, but first is better to exclude a software problem with a factory reset and, possibly, a firmware reflash.

tykenicol said:
My Pro is also rebooting and flikkering. I just plug it into a chager to correct the problem. mine starts doing the flikkering and rebooting when the battery falls to 30 %...
Click to expand...
Click to collapse
Re solder the battery connector will fix your problem. Battery connector with cracked solders will cause flickering screen, auto reboot, auto shutdown..

hey everybody, it seems lots of users have the same problem. and here there are many posts in troubleshooting section. it seems there is something related to software and battery when it is bellow 30%. honestly I don't think sammy made thusands of deffective batteries but rather there is a problem with battery handling from the software.

meneses.leonardo said:
hey everybody, it seems lots of users have the same problem. and here there are many posts in troubleshooting section. it seems there is something related to software and battery when it is bellow 30%. honestly I don't think sammy made thusands of deffective batteries but rather there is a problem with battery handling from the software.
Click to expand...
Click to collapse
This is not software problem, you can verify the source of this particular problem easy. Pressing hard on the back, battery connector location is near the center, or more practically, pressing directly on the battery connector when the rear case removed, you will see the magic. This hardware defect is so easy to fix but most people can't because they don't have solder equipment or don't believe it's the source of problem.

My phone had a heart attack...

Hello,
I think my phone just had a heart attack...
It sounds funny, but not for me. I just don't know how to describe what just happened.
I was just chatting with my sister on WhatsApp, I wasn't doing anything special.
Then, the screen froze, and the phone rebooted.
Recently, I had some "home restarting", sometime once a day, sometimes more, but less since I upgraded to Lineage OS 17.1 (from the previous Lineage OS version).
But this time, it's a full reboot by it's own. Scary...
And the nightmare starts now.
After the boot logo, I arrive on a black screen, asking in English (not my language) for my password... but I never used any password when I start my phone.
So I try my PIN code, the only possibility coming to my mind, and it worked.
Yeah ! It works ! Nope... new black screen in English...
That time, it says that my password is correct, but that unfortunately, my data is corrupt.
I have an inner drop of sweat running on my forehead while reading that...
Then... "To resume using your phone, you need to perform a factory reset. When you set up your phone after reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Only one button : "erase all data", my only option...
I have an inner tear running on cheek while reading that... but what else could I do ? Nothing... so I press the button...
I have a kind of "work in progress" white popup that blinks for half a second, and the phone reboots... on the same password screen !
Next thing to do : the diagnostic of the patient. I power off the phone, then boot in TWRP.
TWRP is in English, not in my language like I set it up a long time ago, and it starts on an unusual screen asking me if I want to keep my system partition in "read only".
It sounds like the patient is in a coma... so I agree on "read only" by pressing the button.
I want to check my data partition, so the most simple way : I choose "install" to go into the "/sdcard"... and it's empty.
Then "up a level" and I go into "/data"... empty... "/system"... empty... "/firmeware"... empty... "/boot"... empty...
Only empty folders, and sometimes empty folders into empty folders.
I go back in the functionalities to go into "partition mounting", and I choose all partitions... but "Data" can't be selected, no matter how much I do the heart massage.
I go back to check in the mounted folders... more empty folders...
So... does anyone have an idea about how to solve such a problem ?
Is there anything to do, or does it look like a DNR wish from an old phone which had a great life and tells me it's time to let it go ?

You have a chance to check if someone made a cruel joke by providing you with a script that did the rest with your unconscious approval, or if it is a hardware failure.
Just install the original ROM, do not unlock the bootloader and use the OPO for a long time and watch the device behavior.
.
.

You saved my day (literally, as you answered during the same day). Thank you.
I hoped to have something without data lost, but as I can use my phone again, it's already a good thing.
I guess you are right : a script that did the rest with your unconscious approval.
When I think about it, as OnePlus system images are not validated by Google, they are not DRM Widevine L1.
So I installed Disney+ from another source... and I guess I got it there.
The good thing is that the market place now sees my phone as already having Disney+ and I can install it (or maybe it's the update from November 19th).
For those having the problem, I followed those steps :
I did the installation process, except that I didn't do the factory reset / data formatting, in the (vain) hope to recover my data.
Apply all the stuffs : Lineage OS nightly-bacon-signed, open_gapps-arm nano, magisk.
Restart the phone : again, the black screens, but this time it reboots to erase everything... it took a very long time.
The phone restarts by itself and I go throw the setting process like for new phones.
It restores what it can restore... some settings of the OS to find back to tweak them...