Related
I've got MIUI ROM 1.6.10 installed on my HTC Desire and I really like it, but I've got a big issue with the camera: it's in a constant state of being frozen.
So to clarify, I open the camera app, and it's straight away frozen. I try to press buttons but all I get is the Force Close / Wait dialogue. If I wait, nothing happens. If I force close and open it again, it's frozen still/again.
It used to happen to me in MIUI 1.2 as well and when I upgraded to MIUI 1.4 after a wipe, surprisingly it was exactly the same, but then I tried pressing the Clear Data button for the Camera application and it started working again.
A little bit after it started getting frozen again. Clear data didn't work anymore, neither did a wipe, SD card format and upgrading to 1.6.10, as mentioned above.
The only thing I can think about the might cause the problem is this: before miui I used to have cyanogen ROM. When I look at phone information it says I've got the cyanogen kernel. is that something that could cause problems to the miui ROM? Should install a different kernel?
Can anyone please help? I really like this ROM and I don't want to have to start getting used to something else!
Thanks for reading!
I'm not sure if this is useful/helpful at all but i gather that since it says that you've got cm kernel you didn't perform a full wipe when you installed miui... try doing a full wipe and reinstalling it...
Save important user data and apps, perform a full wipe and flash again.
Does a full wipe erase the previous kernel?
What kernel will I have then?
Can anyone actually explain what kernel is exactly?
Also, how do I do a FULL wipe?
Because I've already done:
- wipe data/factory reset
- wipe cache partition
- wipe dalvik cache
What am I missing?
Cheers
After a full wipe you won't be able to start any rom.
You will get the kernel which is delivered with the rom you flash.
An explanation for the kernel:
http://en.wikipedia.org/wiki/Linux_kernel
Nothing is missing for a full wipe.
Search the miui thread for your problem.
MatDrOiD said:
After a full wipe you won't be able to start any rom.
You will get the kernel which is delivered with the rom you flash.
An explanation for the kernel:
http://en.wikipedia.org/wiki/Linux_kernel
Nothing is missing for a full wipe.
Search the miui thread for your problem.
Click to expand...
Click to collapse
If nothing is missing and I've actually done a full wipe, then why is my kernel still cyanogen?
liranh said:
If nothing is missing and I've actually done a full wipe, then why is my kernel still cyanogen?
Click to expand...
Click to collapse
Because cyanogen is the kernel which is delivered with miui rom.
MatDrOiD said:
Because cyanogen is the kernel which is delivered with miui rom.
Click to expand...
Click to collapse
Wicked thank you. So the kernel is not the problem.
Could I still have missed something from a full wipe? I remember reading in the guide that u need to format /data,or something. But I assumed the wipes I've detailed above were sufficient. Can anyone confirm that for me?
Or can anyone tell me otherwise why I'm having this problem?
Thanks.
Try to update radio on newest version (post #6):
http://androidforums.com/desire-all...sers-anyone-elses-camera-stopped-working.html
MatDrOiD said:
Try to update radio on newest version (post #6):
http://androidforums.com/desire-all...sers-anyone-elses-camera-stopped-working.html
Click to expand...
Click to collapse
Thank you. You reckon the radio might affect the camera?
Edit: Just had a quick look at the thread you gave me. Seems like that might fix the problem. I'll give it a go when I finish work. Thank you very much!
liranh said:
Thank you. You reckon the radio might affect the camera?
Edit: Just had a quick look at the thread you gave me. Seems like that might fix the problem. I'll give it a go when I finish work. Thank you very much!
Click to expand...
Click to collapse
DIDN'T WORK!
It's a shame. I really thought that was the solution, but it didn't work.
I've just downloaded and installed the recommended radio (5.17.5.23), even tried to clear the camera's data again, but it's still frozen.
ANYONE ...? :\
Did you try some other kernels like ManU or Tiamat?
guersam said:
Did you try some other kernels like ManU or Tiamat?
Click to expand...
Click to collapse
No. Do you reckon that might help? Which one would u recommend?
Okay I've tried a different radio, different kernels (Tiamat 3.3.8 and 4.0.5). Nothing helps!
Does anyone have a clue how to fix this annoying problem?
Another lead I had in mind: Could the fact that I have S-ON affect anything?
Update: I've tried pressing "Fix Permissions" in ROM Manager which didn't help either.
................?
The MIUI camera seems to be a bit buggy, I had to update the radio which helped me get rid of the worst crashes (suprise reboots) but it's still FC'ing and crashing the camera totally so that a reboot is necessary.
Try installing Camera360 from Market. It works for me, and at least you will know if it's just the MIUI Camera app that's broken or if you have bigger problems. In case Camera360 can't connect to the camera, reboot and try again.
enemix said:
The MIUI camera seems to be a bit buggy, I had to update the radio which helped me get rid of the worst crashes (suprise reboots) but it's still FC'ing and crashing the camera totally so that a reboot is necessary.
Try installing Camera360 from Market. It works for me, and at least you will know if it's just the MIUI Camera app that's broken or if you have bigger problems. In case Camera360 can't connect to the camera, reboot and try again.
Click to expand...
Click to collapse
I've already tried a different camera from the market and it does work with no problems at all.
It is the miui camera app that's malfunctioning.
If no one has a solution, all that's left for me is to hope the miui devs will fix this critical issue for their next build.
liranh said:
I've already tried a different camera from the market and it does work with no problems at all.
It is the miui camera app that's malfunctioning.
If no one has a solution, all that's left for me is to hope the miui devs will fix this critical issue for their next build.
Click to expand...
Click to collapse
Ah, then it's most probably the same problem that I have, only I get to shoot a few pics before it goes bye bye and then no camera app at all works until I reboot.
It's a shame because I really like the MIUI Camera, but I guess we'll just have to wait for a fix. If you have error logs, try posting them in the official forum for your MIUI build and maybe they can get someone in China working on a solution?
same problem for me but i am on 1.9.16 ported to X10 lol...
I seen somewhere that it was the auto focus that caused problems/ lags for ppl so if i could just get it to work once and maybe turn that off?
Hello everyone,
I know this question was asked and answered, but the answers didn't solve it for me.
I'm using Eagle's Blood ROM, and I have this problem with Synergy and Jugs. The white line from the last frame of the CRT off animation appears 1st when unlocking.
I wiped Cache and Dalvik and fixed permissions, and the problem went away, however when I rebooted, it came back. I did the wipe and permission fix twice and every time it comes back after a reboot.
I'm sorry for asking this here, but I'm new and not allowed to post in the relevant thread.
Great work on the ROMs and Kernels, you guys are what Android is all about
I think its the kernels man.... I had a lot of issues with the custom kernels on eagles blood :l so flash other roms if you want to use the kernels or jus flash the stock kernel again
Sent From my Galaxy S II T-Mobile
Thanks for the reply
I forgot to mention that I also tried the Juggernaut ROM... same problem there too. I will try other ROMs and see if the problem goes away.
to CWM wipe all caches and fix permissions. that will fix it
Pellel2 said:
to CWM wipe all caches and fix permissions. that will fix it
Click to expand...
Click to collapse
Tried that... won't stick. Try rebooting and tell me if it comes back.
benegessrit said:
Tried that... won't stick. Try rebooting and tell me if it comes back.
Click to expand...
Click to collapse
What kernel? I think it's that. Plus, I think it also may be because of slower graphical performance. I noticed it when the rest of my system was laggy and kinda choppy.
-We do what we must because we can. For the good of all us, except the ones who are dead.-
reflash the kernel
and do these steps
I_am_Error said:
What kernel? I think it's that. Plus, I think it also may be because of slower graphical performance. I noticed it when the rest of my system was laggy and kinda choppy.
Click to expand...
Click to collapse
Pellel2 said:
reflash the kernel
and do these steps
Click to expand...
Click to collapse
I had the same problem with both Synergy and Jugs. I don't think it is because of any slow-down or choppiness; I never had this problem with the stock kernel, even though it has its share of lag.
I think it may be the CRT off effect, it could be conflicting with the custom kernels.
I did flash Jugs twice, and every time the problem goes away after I do the wipe-caches-and-fix-permissions thingy. However, as soon as I reboot, it comes back.
I think I found a solution. Fixng permission clearing cache and dalvic cache didn't work. But a hard reboot worked. Hold power button till phone reboot tada!
lookitzjohnny said:
I think I found a solution. Fixng permission clearing cache and dalvic cache didn't work. But a hard reboot worked. Hold power button till phone reboot tada!
Click to expand...
Click to collapse
I just tried that... didn't work
worked for me... i tried other options.. maybe try pulling your battery out and push hold the power button for 5 seconds and then put battery back in and turn on the device,
lookitzjohnny said:
worked for me... i tried other options.. maybe try pulling your battery out and push hold the power button for 5 seconds and then put battery back in and turn on the device,
Click to expand...
Click to collapse
Just tried that, and it worked, then came back after a reboot.
lol, this is so annoying. Btw, I wanted to thank you for the Crysis and Beam Bat. charging mod., they are awesome
I have a question about them that I posted at the thread
I was viewing the most recent CM9 nightly changes and noticed a link to the CM10 development log for our p930. No clue when the nightly builds will start though but its nice to be able to keep up to date on the progress!
http://cm10nightlies.nechko.com/index.php?device=p930&translations=
nice, i'll bet they release a cm10 nightly before the stable cm9, unless that stable v is coming out in the very very near future.
regardless of the official "we ain't working on cm10 until we release the stable cm9" it looks as if they dove right in. good work.
:good:
I dunno, I could see nightlies being at least 2-3 weeks away. There's a chance we could see an RC2 followed closely by a final right around the same time the first official CM10 nightlies are up.
waitng
Patiently waiting for the dev to finish this up enough for a release. hoping it's soon, i want some buttery goodness.
might want to take a peek in the dev forum.
Any picture of cm10
SergioFern said:
i want some buttery goodness.
Click to expand...
Click to collapse
There's no battery goodness for unofficial build at all. drained battery overnight by just laying lazy in airplane mode, all apps stopped. :sigh:
returning to CM9
Billy Madison said:
There's no battery goodness for unofficial build at all. drained battery overnight by just laying lazy in airplane mode, all apps stopped. :sigh:
returning to CM9
Click to expand...
Click to collapse
did you turn the governor from the default performance mode to ondemand mode? that kills the battery pretty hard. i lost 12% overnight connected to HSPA+ in the CM10 preview.
Anyone know where i can find some custom kernels to go with my CM10 ROM? I tried Semaphore 2.6.0 and 2.6.5 (found out later .5 is for Jelly Bean 4.2) and both looked like they installed, but About Phone > Kernel was CM10 still, and Devil Kernel 1.9.5 (failed in TWRP).
Help!
LG P930 - CM 10 (stable) issues
Hi, I am new to the forum so sorry if I am posting at the wrong place. I have CM 10 installed on my LG P-930 (along with built in kernel) and last night suddenly phone rebooted and has been in the bootloop since then. It wont even let me go into recovery to restore from back up, when I press power+vol down, it just starts normally showing LG logo and then CyanogenMod log and is stuck there indefinitely. I have even left it there for about 30 mins but nothing happens. Any ideas?
Thanks
cm-10.1-20130228-NIGHTLY-p930.zip major problems
1- power button dont turn off the screen for sleep mode
2- touch keys lights dont turn on
3- voice typing dont work after flashing gapps-jb-20121212-signed ( it shows force close )
nss007 said:
cm-10.1-20130228-NIGHTLY-p930.zip major problems
1- power button dont turn off the screen for sleep mode
2- touch keys lights dont turn on
3- voice typing dont work after flashing gapps-jb-20121212-signed ( it shows force close )
Click to expand...
Click to collapse
I'm on the same one without those problems... it sounds like a bad flash. Go back to recovery, wipe cache/dalvik, flash the nightly, then Fix Permissions. If not, try a full wipe. Also, the thread for CM10.1 nightly discussions is over here.
mpsantiago said:
I'm on the same one without those problems... it sounds like a bad flash. Go back to recovery, wipe cache/dalvik, flash the nightly, then Fix Permissions. If not, try a full wipe. Also, the thread for CM10.1 nightly discussions is over here.
Click to expand...
Click to collapse
i did all wipes before flashing cm10.1 . new version released i'll try that
i'm new to cm10.1
what is fix permissions ? what should i do in this menu ?
i'm using default CWM flashed via rom manager . is it important to use newer version of CWM TOUCH ?
where can i download and flash cwm touch Recovery?
what is this new KERNEL and GPU driver ? dose it improve the performance and battery usage ?
nss007 said:
cm-10.1-20130228-NIGHTLY-p930.zip major problems
1- power button dont turn off the screen for sleep mode
2- touch keys lights dont turn on
3- voice typing dont work after flashing gapps-jb-20121212-signed ( it shows force close )
Click to expand...
Click to collapse
I flashed it last night and haven't had any problems with it.
nss007 said:
i did all wipes before flashing cm10.1 . new version released i'll try that
i'm new to cm10.1
what is fix permissions ? what should i do in this menu ?
i'm using default CWM flashed via rom manager . is it important to use newer version of CWM TOUCH ?
where can i download and flash cwm touch Recovery?
what is this new KERNEL and GPU driver ? dose it improve the performance and battery usage ?
Click to expand...
Click to collapse
Fix Permissions can be found in the Advanced menu in CWM. Just choose it and let it do its thing... takes about 30sec usually.
I have gotten into the habit of running it after every flash, especially dirty ROM flashes.
The GPU Driver is supposed to fix some graphic glitches in 10.1. I haven't noticed much change in battery with it. As for the kernel... probably best to read the OP in the Wind thread for the details on that.
mpsantiago said:
Fix Permissions can be found in the Advanced menu in CWM. Just choose it and let it do its thing... takes about 30sec usually.
I have gotten into the habit of running it after every flash, especially dirty ROM flashes.
The GPU Driver is supposed to fix some graphic glitches in 10.1. I haven't noticed much change in battery with it. As for the kernel... probably best to read the OP in the Wind thread for the details on that.
Click to expand...
Click to collapse
I hadn't noticed if 'fix permissions' had been fixed.. but I remember learning the hard way (around GB-era p930) that using it in cwm bricked my phone.. It works fine now?
Edit:
Here's a quote from a CM9 rom:
Warning:
Please do not fix permission via new CWM, it screw some files permission! I'm not tried older version. I will set permission if necessary on every files i provide, so please don't fix permission.
For every additional / patch files you don't need to wipe cache / dalvik or fix permission, i will do if necessary.
Click to expand...
Click to collapse
Just want to confirm that this is not an issue now (or maybe if it never was..?) before I end up putting my p930 into bootloop again.. lol
Hi.
I installed a custom ROM (CM10) yesterday but ever since then, when the screen is turned off, it will restart after about 1 minute. If I try to turn the screen on again before 1 min, it'll restart. In other words, when it goes to sleep, restart will be required. Please help me on solving this issue. I searched a lot and I thought maybe it has to do with the maximum CPU frequency, I tried changing it but didn't help.
Any ideas on how to solve this problem?
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
RE
Romman0 said:
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
Click to expand...
Click to collapse
Thank you for the response.
Yes I did wipe the tablet (a full wipe as you mentioned) before flashing the ROM.
First I had tried Jellytime Sosei and when I realized the problem, I tried "Build 4 Linaro Stock" from this post but still the problem exists :/ Before installing the first ROM, I had done a full wipe, but not for the second one.
Thanks again for helping me.
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Its screaming bad install or bad settings, wipe twice then flash again, make sure to change nothing for speed, governor, io scheduler, and stock included kernel.
Don't even install an app for OC. It may be a huge bug showing for the first time, if we go carefully we'll find it, or get it going properly again. Occasionally the blackhole wipe used can clear up flash issues, but wipes internal sd as well.
Tapatalked from my HTC DNA
Thank you guys. I'll try what you said when I get home.
Romman0 said:
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Click to expand...
Click to collapse
I'm gonna give those three that you said a try, when I get home. But, can you give me the link of the original CM10 thread that you're saying? I thought there isn't one for A100, since I didn't find it on their website. Is there a official CM10 ROM for A100?
There is no Official CM10 for the A100, Romman was referring to this link for the original CM10: http://forum.xda-developers.com/showthread.php?t=1792634
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
aminbandali said:
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
Click to expand...
Click to collapse
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
pio_masaki said:
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
Click to expand...
Click to collapse
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
aminbandali said:
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
Click to expand...
Click to collapse
If its fine on stock then its gonna be Rom or kernel, just never heard of this happening before. What governor did you use?
Tapatalked from my HTC DNA
Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!
As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:
I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Ya its all kernel related and user error.
Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.
Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.