Related
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.
I have a problem with my Xt720.
I have the Froyo Rom by khalpowers V3. (this one http://forum.xda-developers.com/showthread.php?t=1002993)
Everything works just fine and how it should. But after about 20 minutes when my screen turns off or when I turn my screen off, I can't turn it on again.
I press the Powerbutton and all that happens is that the led row lights up but the screen stays black.
I'm not sure but I think the touch screen doesn't work either because I can't unlock it by sliding the unlock thing. (or I just can't find it when the screen is off)
This began today and I did nothing extraordinary with my phone. When it started I had the Dexter's Froyo (http://forum.xda-developers.com/showthread.php?t=939644) Version 1.2. But it has never been a problem before.
Then I flashed the above called Rom by khalpowers and it's still the same problem.
Everytime it happens I have to remove the battery and reboot the phone to use it again. This is very annoying and not how it should behave.
Wat do?
Monthana said:
I have a problem with my Xt720.
I have the Froyo Rom by khalpowers V3. (this one http://forum.xda-developers.com/showthread.php?t=1002993)
Everything works just fine and how it should. But after about 20 minutes when my screen turns off or when I turn my screen off, I can't turn it on again.
I press the Powerbutton and all that happens is that the led row lights up but the screen stays black.
I'm not sure but I think the touch screen doesn't work either because I can't unlock it by sliding the unlock thing. (or I just can't find it when the screen is off)
This began today and I did nothing extraordinary with my phone. When it started I had the Dexter's Froyo (http://forum.xda-developers.com/showthread.php?t=939644) Version 1.2. But it has never been a problem before.
Then I flashed the above called Rom by khalpowers and it's still the same problem.
Everytime it happens I have to remove the battery and reboot the phone to use it again. This is very annoying and not how it should behave.
Wat do?
Click to expand...
Click to collapse
Let it charge for a while and try again. Your battery may be extremely low. Turning on the button lights is one thing it does when there isn't enough power to boot even to the "display a charging battery" mode. This has happened to me.
I've had this issue ever since I got my phone. This would just happen completely randomly (nothing to do with battery or anything else). It happened pretty unfrequently and barely ever happens ever since I put on Dexter's 1.3. Not sure what causes it - but it looked to be completely random for me.
Monthana said:
I have a problem with my Xt720.
I have the Froyo Rom by khalpowers V3. (this one http://forum.xda-developers.com/showthread.php?t=1002993)
Everything works just fine and how it should. But after about 20 minutes when my screen turns off or when I turn my screen off, I can't turn it on again.
I press the Powerbutton and all that happens is that the led row lights up but the screen stays black.
I'm not sure but I think the touch screen doesn't work either because I can't unlock it by sliding the unlock thing. (or I just can't find it when the screen is off)
This began today and I did nothing extraordinary with my phone. When it started I had the Dexter's Froyo (http://forum.xda-developers.com/showthread.php?t=939644) Version 1.2. But it has never been a problem before.
Then I flashed the above called Rom by khalpowers and it's still the same problem.
Everytime it happens I have to remove the battery and reboot the phone to use it again. This is very annoying and not how it should behave.
Wat do?
Click to expand...
Click to collapse
Another suggestion. Since you've already swapped ROMs, maybe it's related to the SD card. Perhaps try backing your SD card up, reformatting it and copying the data back (do this on the PC not through USB access). Then reinstall your rom in OpenRecovery and factory wipe.
(You don't happen to be running WidgetLocker?)
@Mioze: The battery was at 70% a few hours after I loaded it to 100%, so that's probably not the problem. I don't have widgetlocker and it also happened with the sd card taken out.
But it didn't happen since I've started this thread so maybe I'm lucky and syrenz was right.
i have had this problem on every rom. it is related to sdcard. happens to me almost everytime i try to unrar one of khals rar files it always happens when im doing something sdcard related. last time it happened i did a battery pull and when it powered up my sdcard would stop checking for errors and everytime the screen turned off it wouldnt come back up. i had to plug into pc and check for errors and then it worked again without having to reformat it. my advice is get a faster sdcard. the stock one just doesnt cut it.
Trying a 4Gb Kingston Sd card now I used with my Dslr before.
I used the stock sd the whole day after I checked it for errors yesterday and it went well until I tried to download something from the store.
By now there seems to be no problem. Going to update my post if the problem still exists.
If it's ok: Thank you all for your efforts to help me.
Now this is ironic, as my phone began doing this today after put a new 32GB class 10 (Patriot) microsdhc card and reflashed Dexter's 1.3 and added bugfix v3 to it. After some tinkering, I think I nailed it down to me undervolting the processor.
I'm assuming the new microsdhc card need's a little more power than I was allowing. I was clocking the processor to 720Mhz/Vsel43, I left the speed at 720Mhz, but increased the vsel to 45, which seems to have solved the above described problem. However when I tried to copy my music over to the phone, it borked out again. So I've increased the vsel to 50 and things seem to have settled down. (fingers crossed)
G.
Ack! I spoke too soon. I just tried to install Steve Lin's Gingerbread keyboard and the phone reboots at the end of the download, even though I tried increasing the vsel. Going try clearing the Dalvik/Cache and see if that helps any.
I've flashed my XT720 to the khalpowers MIUI-Optimized V3 with the camera update.
I originally had a Sandisk 8GB Class 4 SD card, but after installing a new Adata 8GB Class 6 SD card, I started having the same issues. I was running Milestone Overclock on non-custom overclock settings, so it was running at 1GHz @ 74 vsel.
Honestly, I don't know that I've seen a discernible difference between the Class 4 and Class 6 card, so I may go back to the original card until I get more concrete data on how to fix this.
Let me share my 2 cents regarding sd cards.
first trouble shouting:
1. use the phone without the sdcard to see if the problem disapear
2. while doing 1. test the sdcard. Have in mind that sdcards are little bit different from normal hdd. For example i had 2 sdcards which locks the phone, but seems good on normal fs checking (even bad sector check option forced). but this 2 cards failed on the following test
test read speed of the sdcard for every 100 MB of it. for my desktop the script looks like:
Code:
i=0; while [ $i -lt 75 ]; do echo $i; dd if=/dev/mmcblk0 of=/dev/null bs=1M count=100 skip=`expr $i \* 100`; i=`expr $i + 1`; done
dd utility will probably report the speed (else just type time dd ....., then you will have the time)
if the card is good, then the speed has to be almost constant
for example on the good card i am using now is almost constant from 13.1 till 13.6 MB/s
for one of the bad, i observerd droping from 10 MB/s to 3 MB/s for a specific space range. then had run several tests just in this range and it turnout that this area of the sdcard is slow. That means that the card is on it way to the RIP.
For us it means that some sdcard io will timeout and soft lookup can happen (e.g. so called warm reboot, or just system_server kill by the watchdog). The other possibilities is more worse, just freeze and the watchdog cannot kill the system_server (probably because hang io operation)
Personally i was runing adb shell when the phone had freeze. it turns out that the linux works somewhat, but even as root i was unable to kill any process (probably because io hung operation), also every operation with the sdcard has hangt the current adb session, so i have to open new one....
secondly performance
0. If you wish you can perform the read speed test from above, but with write and to observe weak areas of the new sdcard
1. align the partitions on 8192s boundary (both of them to start on 8192*X sector)
2. format the fat32 so 64k logical cluster is formed (i use mkfs.vfat -S 4096 -s 16 options )
3. do the read_ahead tweak
4. be sure to using noatime mount options
5. vold checks the fat partition for you, make sure that thex ext[234] partition is checked before is mounted
6. If you decide to move the /data/dalvik-cache, move it to the /cache partition, not the ext[234] one
and do not forget, that free internal phone storage has no benefits. so as the internal nand is faster, use it as much as you can
p.s. and just to share: i have troubles with the thumbnail service. it turns out that when it runs (e.g. when i lock the display) it find some broken images and crashed badly, invoking warm reboot. after deleting this broken images, this problem was solved
I've been using the Kingston 4gb sd for a few days now and the problem's gone.
So that might be the solution.
I use 8GB C2 sdcard, and turn off desktop cache in system setting of ADW, this problem was gone.
It seem to be caused by ADW places cache in SD.
I've left my Adata 8GB Class 6 SD card in for now, but after removing the SD Speed Boost app, it appears my problem has gone away. I've never had the persistent memory setting enabled on ADW, btw.
Edit: I was curious if the SD Speed Boost would work after a reinstall, but 20 minutes after, I was pulling my battery, so I'm pretty sure it was that app at fault.
easye420 said:
i have had this problem on every rom. it is related to sdcard. happens to me almost everytime i try to unrar one of khals rar files it always happens when im doing something sdcard related. last time it happened i did a battery pull and when it powered up my sdcard would stop checking for errors and everytime the screen turned off it wouldnt come back up. i had to plug into pc and check for errors and then it worked again without having to reformat it. my advice is get a faster sdcard. the stock one just doesnt cut it.
Click to expand...
Click to collapse
I got the issue even I'm using the class 10 SD card it seems not related the SD speed.
Annoying.......
This problem just started happening to me but I doubt that it is a SD card problem. Mostly since my phone has been unresponsive since yesterday afternoon and I can't even get the LEDs to light up or get the screen on at all. I got it to work after relentless battery pulls and taking the SD card and SIM out. But I decided to turn it off so I could pop the SD and SIM card back, it went back to its non-responsive mode. I also am unable to get to recovery mode or even the bootloader. My tech always seems to break all on the same day (my bike too >_<).
just try without sdcard
Sent from my Milestone XT720 using Tapatalk
I'm almost positive this is sdcard related it only happens to me when I'm doin something sdcard related. Happens like clock work when I try to unrar one of khal themes that's 100 or more megs same when I use the unyaff app to extract my data.img from my back up. Ive had this problem ever since upgrading to 2.2 never happened on 2.1 I've just gotten used to it. I dont think its gonna go away I'm thinking the sdcard must timeout or something.
easye420 said:
I'm almost positive this is sdcard related it only happens to me when I'm doin something sdcard related. Happens like clock work when I try to unrar one of khal themes that's 100 or more megs same when I use the unyaff app to extract my data.img from my back up. Ive had this problem ever since upgrading to 2.2 never happened on 2.1 I've just gotten used to it. I dont think its gonna go away I'm thinking the sdcard must timeout or something.
Click to expand...
Click to collapse
Well just did a battery pull again and just took out the SD card and put the battery back in and tried to turn it on again but to no avail. Really annoying not having having my phone.....
This is also happening to me too... regardless if i have anything installed or accessing any files on my SDcard... and i already flashed my xt720 back to stock... and still the same... already changed my SDcard from the 8gb that was included on the package to 16gb... but still the same... i am very dissapointed with this device... just got this last week...
Still Annoyed....
My problem is still persisting after 2 days now and I'm torn between junking this phone and getting something else or trying to find a way to get my phone back in working order. I've tried just about everything I can do physically with the phone (battery pulls, w/o SD or SIM or with both in or one or the other out, etc........). So far all I have right now is a $400 dollar paper weight.
On another note, for some reason it keeps phoning my dad or sending him text messages with random assortments of code or error messages..........
Hey all-
I love this rom, but have been having some weird problems that I can't seem to find answers to. I appreciate the help!
-Whenever I reboot the phone or plug in the charger, the locations app opens and asks about downloading maps. After I download said maps, the locations app still opens whenever I reboot the phone/plug in the charger, only now it wants me to activate my premium navigation. I don't use this, so I click cancel, but the problem continues.
-Whenever I answer or make phone calls, the speaker phone comes on. I can turn it off and speak normally, but it shouldn't default to on whenever I make a call. I found a similar issue online, which said that it was due to an accelerometer fault. It was suggested that I uncheck the option that said 'flip to activate speaker'. This solution did not help. It was then suggested that I recalibrate the accelerometer and restart the phone. I could not do this. Whenever I try to recalibrate the accelerometer, I get an error which says 'calibration aborted'.
- The phone turns off randomly. Usually when I'm in the middle of doing something on the phone. It may be due to a faulty battery cover, but I'm not sure. Is this a reported issue with the rom?
- I am unable to turn the phone off without removing the battery. The lock button works fine, but holding it down does not bring up the power menu. It was working fine, but then it randomly stopped.
I have re-flashed the rom multiple times, and even done some full wipes and then re-flashed, but these issues keep returning.
THanks all
-Gideon
Look I don't know if this actually helps but here it goes:
1. When installing the Rom make sure that you have formatted the sd card. For me this was a solution for many bugs, including navigation ones.
2. Some Roms have an option in call settings that has the speaker turning on when a call is answered, it could be in tweaks also.
3. Do you do Titanium Backup? If so this may also be the culprit. By backing up system data and application info, all previous settings and in your case bugs and problems may be coming back too.
What I do:
1. Format sd
2. Full wipe
3. Mount USB storage
4. Transfer Rom zip
5. Unmount and install from zip
6. After Rom is settled, then I put my Titanium backup files on the sd but only restore the apps not the settings or system data.
7. Also I fix permissions with rom manager just to prevent any bugs.
Again just what I do, hope it helps you out.
5.
Sent from my HTC Inspire 4G using XDA Premium App
ROM: Hydro JB
Kernel: Unt's 10.4.4.18
Internal memory non data2sd: Journaling off on mmcblk0p8
Lately I've been having these random hiccups on my display, it happens randomly and practically impossible to recreate when I want to. The thing that happens is that the display does the closing app animation (screen goes black for miliseconds) and then returns to the app as if I had changed apps with recent app list or opened a new app. This has never happened before, the latest changes I made were flashing Unt's kernel and turning journaling off. It comes and goes whenever it pleases, haven't tried doing fix permissions (don't know if that would help), did try doing cold booting but the problem reappeared. Sometimes it can be hours of use until I experience it again and sometimes happens faster. Any ideas? Maybe I should try turning journaling on again? But having journaling off has made my I/O faster.
Thanks in advance,
Stock, Non-Rooted, Verizon Galaxy S3 4.1.2
I535VRBMF1
I've been experiencing the media scanner battery drain issue now for months and I can't figure out how to solve this issue. I've tried the following:
+ Factory Reset
+ Removed SD Card, removed all files, formatted and copied all files back
+ Delete cache for many apps including podcasts
+ Removed SD Card and reboot - Media Scanner still runs!
This problem typically runs after reboot and continues to run, with the phone running hot for about an hour. I typically lose about 20% of battery power doing this. It's inconsistent. Sometimes the scanner crops up and refuses to stop at all. During this time, the phone has a wakelock and becomes warm to the touch, draining battery at a rapid rate.
Skyeclad said:
Stock, Non-Rooted, Verizon Galaxy S3 4.1.2
I535VRBMF1
I've been experiencing the media scanner battery drain issue now for months and I can't figure out how to solve this issue. I've tried the following:
+ Factory Reset
+ Removed SD Card, removed all files, formatted and copied all files back
+ Delete cache for many apps including podcasts
+ Removed SD Card and reboot - Media Scanner still runs!
This problem typically runs after reboot and continues to run, with the phone running hot for about an hour. I typically lose about 20% of battery power doing this. It's inconsistent. Sometimes the scanner crops up and refuses to stop at all. During this time, the phone has a wakelock and becomes warm to the touch, draining battery at a rapid rate.
Click to expand...
Click to collapse
This is not the verizon forum.
However if it is still running after removed SD card, the problem is probably on your internal memory (/sdcard) It may be worth backing up your data and factory reset (wiping internal SD).
Someone said its to do with thumbnails so try and clear these first just incase that helps.
please use the /!\ button to report your post to be moved to the correct forum.
Moved to VZW SGS3 Q&A section.
Skyeclad said:
Stock, Non-Rooted, Verizon Galaxy S3 4.1.2
I535VRBMF1
I've been experiencing the media scanner battery drain issue now for months and I can't figure out how to solve this issue. I've tried the following:
+ Factory Reset
+ Removed SD Card, removed all files, formatted and copied all files back
+ Delete cache for many apps including podcasts
+ Removed SD Card and reboot - Media Scanner still runs!
This problem typically runs after reboot and continues to run, with the phone running hot for about an hour. I typically lose about 20% of battery power doing this. It's inconsistent. Sometimes the scanner crops up and refuses to stop at all. During this time, the phone has a wakelock and becomes warm to the touch, draining battery at a rapid rate.
Click to expand...
Click to collapse
I suggest you root your device and download 'Rescan Media Root' from google play.
That fixed my problem.
I also heard adding '.nomedia' file in all your folders that does not have media files will prevent scanning those file.
rootSU said:
This is not the verizon forum.
However if it is still running after removed SD card, the problem is probably on your internal memory (/sdcard) It may be worth backing up your data and factory reset (wiping internal SD).
Someone said its to do with thumbnails so try and clear these first just incase that helps.
please use the /!\ button to report your post to be moved to the correct forum.
Click to expand...
Click to collapse
One of the first things I did was do a factory reset but the problem remained. I'll move on to deleting the thumbnails and see if that helps.