I threw this out on Twitter and at Cyanogen's forums, but I thought I'd give you guys a shot as well as this seems to be the most active forum there is.
I'm absolutely DESPERATE to get cyanogen back on my phone. I had 6.1 RC1 set up perfectly - I tweaked the **** out of my phone - and then I tried to use the camera... no dice. Nothing. Can't use any camera application at all. I always get the same response: Activity Camera (in application Camera) is not responding. I get a black screen, then the option to force close or wait.
I have tried putting on 6.0, 6.1 RC1, and the nightly build... none had a working camera. I flashed everything back to stock, and the camera is working like a charm again... BUT EVERYTHING ELSE SUCKS!!! I can no longer stand stock, thus my offer to pay for help. I just got my phone, and it was new, so I thought maybe the radio version or the HBOOT versions were causing problems. I have:
HBOOT: 2.02.0000
Radio: 2.15.00.09.01
I don't see how either of those would cause a problem with the camera since everything else was running smooth as silk.
Thanks for the great work you all do, and thanks for any help you can give me.
you try flashing any other kernels? try flashing snap's kernel
I used to have that problem, do you have google goggles installed? Or any other apps that may use the camera? Try uninstalling them, then opening up the camera, then you can reinstall them after.
Is your phone hardware revision 0004? If so, you're probably going to have to wait for HTC to release the source code to the kernel from the 3.30 update, because the 0004 models have a new camera which seems to require a new driver. You'll probably have the same issue with the stock ROM if you flash a custom kernel on it.
I had SNAP 7.6 installed, forgot to mention that.
WrlsFanatic said:
I had SNAP 7.6 installed, forgot to mention that.
Click to expand...
Click to collapse
what Ninja said, i remember reading about those 0004's in the general forum
Noxious Ninja said:
Is your phone hardware revision 0004? If so, you're probably going to have to wait for HTC to release the source code to the kernel from the 3.30 update, because the 0004 models have a new camera which seems to require a new driver. You'll probably have the same issue with the stock ROM if you flash a custom kernel on it.
Click to expand...
Click to collapse
This is exactly why. You are SOL for a bit.
apristel said:
This is exactly why. You are SOL for a bit.
Click to expand...
Click to collapse
Actually, it says I have hardware version 0003. Any other way to check my camera version?
WrlsFanatic said:
Actually, it says I have hardware version 0003. Any other way to check my camera version?
Click to expand...
Click to collapse
Maybe try fixing permissions or something..idk. I think its an option in rom manager maybe? I read about ppl talking about it when stuff is broken and they say it helps.
Other than that, try flashing miui to see if that camera works, its based off of CM so if it works, thats always a good sign..if worse comes to worse, you can flash CM6 and then push the camera from MIUI.
From CM6 and 6.1 RC, just try some other kernels, king's, netarchy's or even the new toast .35 kernel.
ms79723 said:
Maybe try fixing permissions or something..idk. I think its an option in rom manager maybe? I read about ppl talking about it when stuff is broken and they say it helps.
Other than that, try flashing miui to see if that camera works, its based off of CM so if it works, thats always a good sign..if worse comes to worse, you can flash CM6 and then push the camera from MIUI.
From CM6 and 6.1 RC, just try some other kernels, king's, netarchy's or even the new toast .35 kernel.
Click to expand...
Click to collapse
OK, I'll try that and let you know how it goes. THANKS!
to run the fix_permissions script open up a terminal emulator and enter
Code:
su
fix_permissions
or with adb just 'adb shell fix_permissions'
Also try wiping the camera apps cache or maybe even cache & dalvik from your recovery.
Had what sounds like the same problem, all i had to do was reboot to fix mine tho and i could recreate the problem by pressing the camera button twice when trying to take a picture, not sure what it was but i had all the same settings as you, i wiped everything flashed a sense rom then wiped everything and flashed back to CM6 6.1 RC1 and everything seems to be fine hope this helps
Try wiping and flashing through Amon RA (if you have been using ROM Manager instead).
Can someone link to some kernels that will be stable with Cyanogen RC1 so that I can try them? Also, just to make sure, I should be able to flash this over top of cyanogen without a problem, right? Of course I'll no a NAND backup, but I'm hoping it will work without that.
Sent from my PC36100 using XDA App
WrlsFanatic said:
Can someone link to some kernels that will be stable with Cyanogen RC1 so that I can try them? Also, just to make sure, I should be able to flash this over top of cyanogen without a problem, right? Of course I'll no a NAND backup, but I'm hoping it will work without that.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
scroll to the bottom. And yep, you can flash them on top of cyanogen without a problem. did you try flashing miui and seeing if that camera worked?
Just tried Kings 2 bfs... No dice. I'll try another tomorrow.
Sent from my PC36100 using XDA App
There have been some reports of people with version 003 having the new camera. So if you bought your phone in the month of November chances are u have the new camera and will have to wait till cyanogen writes drivers for it.
xHausx said:
to run the fix_permissions script open up a terminal emulator and enter
Code:
su
fix_permissions
or with adb just 'adb shell fix_permissions'
Also try wiping the camera apps cache or maybe even cache & dalvik from your recovery.
Click to expand...
Click to collapse
Not knocking your help, I appreciate it, but as stated - and as I figured - I simply will not be able to use my camera until the source code with the new camera drivers comes out. I did try this, and it didn't do anything.
And I can't wipe the camera app cache because I can't even open the application. Click on "Camera", screen goes black, eventually it force closes.
Maxy6 said:
Try wiping and flashing through Amon RA (if you have been using ROM Manager instead).
Click to expand...
Click to collapse
Amon Ra is all I've ever used, so that isn't a problem.
As for the $100, if this really can't be fixed, then I'll just wait until the future Cyanogen release that will include the newer camera drivers and throw in anothere $50 to those guys for all their help. I'm sure it will happen eventually.
WrlsFanatic said:
Amon Ra is all I've ever used, so that isn't a problem.
As for the $100, if this really can't be fixed, then I'll just wait until the future Cyanogen release that will include the newer camera drivers and throw in anothere $50 to those guys for all their help. I'm sure it will happen eventually.
Click to expand...
Click to collapse
Yeah, most of the phone sold in November have the new camera that just doesn't work well with the old kernels out there atm. I'm using Myn Warm 2.2, and the only kernel I can use is the Stock #10 while having the camera work.
Related
Ok, so I did part 1 and part 2 of Toast's root for full NAND access
I also flashed to the latest radio
how do I fix it so I can see apps like NYTimes, etc? Thanks
I have the same issue. Any details on this would be greatly appreciated.
Not sure if I completely understand, but I am fully rooted (Toast 1/2 Nand etc). I just searched for NY times in App Market, downloaded, installed, and it works fine.
I have new Radio, and Running Bugless Beast Rom.
sterlinron said:
Not sure if I completely understand, but I am fully rooted (Toast 1/2 Nand etc). I just searched for NY times in App Market, downloaded, installed, and it works fine.
I have new Radio, and Running Bugless Beast Rom.
Click to expand...
Click to collapse
Well, you have a custom ROM loaded, so that would change the result. I too have the latest radio, but I'm still using the stock ROM with my recovery. There has to be something we can do fix this issue. I don't want to load any custom ROM's because I haven't seen one that appeals to me. I'm wondering of users that have kept the stock ROM, but have it rooted via Toast method have this issue or are they using apps that aren't effected by this????? Someone has to know of a fix or a file that we can copy over the one that has broken us.
Well at least we know there is a cure for it. Either run a custom rom, or talk to the dev who made it work in his ROM to see what he did to cure it.
sterlinron said:
Well at least we know there is a cure for it. Either run a custom rom, or talk to the dev who made it work in his ROM to see what he did to cure it.
Click to expand...
Click to collapse
I agree, but that's why this thread was made, in hope that someone who knew how to fix this issue would chime in here and let us know, so that we didn't have to bother anyone for a fix....
Wishful thinking I guess....
well guys..the only way i fixed my issue was flashing to the OMJ rom..now it all works fine
eyecon82 said:
well guys..the only way i fixed my issue was flashing to the OMJ rom..now it all works fine
Click to expand...
Click to collapse
I wish you would have waited.... I am testing a fix now...
LilRico said:
I wish you would have waited.... I am testing a fix now...
Click to expand...
Click to collapse
.i was using “Supersonic_1.32.651.1_rooted.zip" which has known issues with the market place....
FIXED!!!!
Many thanks to XpAcErX on this post!
http://forum.xda-developers.com/showpost.php?p=6838616&postcount=809
XpAcErX said:
those apps were missing from the market for me when i had toasts PC36IMG.zip rom flashed from the root in part 1, perhaps you nandroid restored that rom.
flashing flipz OTA Update 1.32.651.6 and the newest radio fixed the issue for me.
flipz OTA Update 1.32.651.6: http://geekfor.me/evo/21/ota1326516
Radio: http://geekfor.me/evo/radio/radio139000531/
Click to expand...
Click to collapse
I flashed the flipz OTA Update 1.32.651.6 in recovery mode, and then flashed the radio but it made my phone go in a constant re-boot. I did a wipe, Dalvik wipe and a cache wipe and success!!!! I was booting with no issues AND all the apps that I wanted in the market were showing up with no issues + I had full root access!!!! I lost some of my data, but that's a small price to pay... Good thing I had my backups! Thanks again to XpAcErX. OP should link to this post for future reference.
Any one tried this.
Im installing it now
http://incredibleroms.com/roms/jager/
I'll give it a try.
Failed on install in Rom Manager.
Reverting to leaked 2.2 now.
Bummer it looked great without sense.
Jager : Update
I got it up and running well. I installed it using ROM Manager, wiped the cache and let it do its thing. Something odd though. I cant seem to get the "Checking phone storage" icon in the status bar to go away. 720p recording, 8mp camera, wireless tether and adw launcher are all included and working. Im going to try to get ahold of the developer, seems like some good work.
-Craig
Edit
Sent from my ADR6300 using XDA App
Its 2.2 through and through. Im giving it another shot and reinstalling it to troubleshoot the "Checking phone storage" error.
also failed for me in rom manager, coming from 2.2 sense leak
SR3TLAW said:
I got it up and running well. I installed it using ROM Manager, wiped the cache and let it do its thing. Something odd though. I cant seem to get the "Checking phone storage" icon in the status bar to go away. 720p recording, 8mp camera, wireless tether and adw launcher are all included and working. Im going to try to get ahold of the developer, seems like some good work.
-Craig
Click to expand...
Click to collapse
Checking on that right now not sure about the rom manager issue will have to check with koush on that... Working on an update now with more fixes and changes...
CJ
CaptainJager said:
Checking on that right now not sure about the rom manager issue will have to check with koush on that... Working on an update now with more fixes and changes...
CJ
Click to expand...
Click to collapse
Fantastic rom although it took me a few time to get it to work. Here is what i did. (Tried it from rom manager and no go)
In recovery,
1. to wipe/factory reset.
2.wipe cache partition,
3. then go to advanced options at the bottom and format cache.
4. Format dalvik cache (not sure if this was necessary but i did it just in case)
5. Reboot
After a couple of minutes you will be good to go.
So far no real bugs in fact it less buggy than the stock froyo and skyraider and quicker it seems
Performance- Linpack results
Peak so far - 40.707 MFLOPS, .13 secons
avg - 38-39 MFLOPS .14 seocnds
Fully de-odexed and slim
I like it a lot so far but just my opinion but you should def try it out
jgrimberg1979 said:
Fantastic rom although it took me a few time to get it to work. Here is what i did. (Tried it from rom manager and no go)
In recovery,
1. to wipe/factory reset.
2.wipe cache partition,
3. then go to advanced options at the bottom and format cache.
4. Format dalvik cache (not sure if this was necessary but i did it just in case)
5. Reboot
After a couple of minutes you will be good to go.
So far no real bugs in fact it less buggy than the stock froyo and skyraider and quicker it seems
Performance- Linpack results
Peak so far - 40.707 MFLOPS, .13 secons
avg - 38-39 MFLOPS .14 seocnds
Fully de-odexed and slim
I like it a lot so far but just my opinion but you should def try it out
Click to expand...
Click to collapse
Oh haha didnt know i was responding to the creator of the rom duh/ Anyways while i got you thanks for the rom, i like all of your roms. also right now i have the 2.2.4 version installed but when i go to the site it shows the previous one and not the 2.2.4?
...
Thanks dude. Let me know what the deal is. Also, something to look into, when you answer your phone, the htc sense slide up slide down is appearing, not the slide deal. Looking forward to trying out your work.
-Craig
Is ADW really the way to go, Ive played with Launcher Pro; its pretty bad-ass.
jgrimberg1979 said:
Fantastic rom although it took me a few time to get it to work. Here is what i did. (Tried it from rom manager and no go)
In recovery,
1. to wipe/factory reset.
2.wipe cache partition,
3. then go to advanced options at the bottom and format cache.
4. Format dalvik cache (not sure if this was necessary but i did it just in case)
5. Reboot
After a couple of minutes you will be good to go.
So far no real bugs in fact it less buggy than the stock froyo and skyraider and quicker it seems
Performance- Linpack results
Peak so far - 40.707 MFLOPS, .13 secons
avg - 38-39 MFLOPS .14 seocnds
Fully de-odexed and slim
I like it a lot so far but just my opinion but you should def try it out
Click to expand...
Click to collapse
I just cant get this installed....followed your steps. Anything else maybe you left out? I tried rom manager already.
santana11981 said:
I just cant get this installed....followed your steps. Anything else maybe you left out? I tried rom manager already.
Click to expand...
Click to collapse
Which version are you using, because i am using 2.2.4 but when i tried the previous one which was 2.2 it didnt work. when i check about 45 mins ago the old one 2.2 was back up and the version i am on 2.2.4 was taken down for some reason. I just checked a second ago and the latest one is back up, so try that one if you havent yet, but dont use rom manager because it doesnt work for some reason and follow the steps that i put up
installed this rom and I had no data connection. Rest the phone and no luck, also did a battery pull and still no data. Did *228 and let it reset after programming and all seems to be working fine. Thanks for a great rom.
jgrimberg1979 said:
Which version are you using, because i am using 2.2.4 but when i tried the previous one which was 2.2 it didnt work. when i check about 45 mins ago the old one 2.2 was back up and the version i am on 2.2.4 was taken down for some reason. I just checked a second ago and the latest one is back up, so try that one if you havent yet, but dont use rom manager because it doesnt work for some reason and follow the steps that i put up
Click to expand...
Click to collapse
I clicked the link in your original post and that still shows 2.2.0....but when i went to main page i see updated version...thanks dude
Wow, I had no idea people would have this much trouble with it. I can post my 2.4 version of it up if anyone wants to give that a try. Hit me up if your interested.
I can post the 2.24 version if anyone is interested.
SR3TLAW said:
I can post the 2.24 version if anyone is interested.
Click to expand...
Click to collapse
its back up now
This is an unusal situation but eventually everyone should be able to get it, like i said it took me a couple of trys. Its deferent than most roms because this on actually forces a full wipe, which is def unusual. Also one thing i noticed when i put it in the cooker just to see the specs and it show "unsecured boot" which is unusal for roms to have
Yea it is back up.
Some bugs I found:
Search feature is not working from home screen.
At first install the messages app doesent seem to be installed correctly and for some reason their is no phone app in the launcher home row.
MMS does not work
couldn't get teh wireless tether in AP mode working
Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?
patsfan1130 said:
Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?
Click to expand...
Click to collapse
You sure its Skyraider? That happened to me... Phone wouldnt shut off, if your in dark you can see the screen doesnt even shut down. With me though, it would shut off if plugged in.. Turned out the phone was damaged, a power surge damaged it. Got it replaced. If you flash another rom and it still wont shut down, then your gonna need a replacement.
Thanks for the response Mike. No, It does not happen with any other ROM I flash. Been bouncing between CM, Virtuous and uncommon for a week now and the power button works as it should.
I dunno, I realize I am a n00b with all of this but it simply doesnt make sense to me
Again, Thank you for the response
What radio are you using? A lot of people using 2.05 were having that issue and it went away when they upgraded to a 2.15 radio baseband.
No problem. But what you have going on is very odd, i wasnt aware that a ruu could do that. Try upgrading to the latest radio.
That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28
patsfan1130 said:
That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28
Click to expand...
Click to collapse
Yes, that's the baseband version and you should be good to go with the one you are using. The only other things I can come up with is to ensure you are S-OFF and running HBOOT 0.79 or higher.
Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.
patsfan1130 said:
Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.
Click to expand...
Click to collapse
Not a problem. This is how we learn. To find your HBOOT version power down then reboot into recovery. When you get to the white recovery screen look in the top left corner. The first line should state S-OFF and the second line should state your HBOOT version.
I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
patsfan1130 said:
I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions
Click to expand...
Click to collapse
Well that's unfortunate. I read a couple of posts in the Skyraider thread that sounded as though a couple of people had the "recommended" setup (like you) but also had the reboot problem. Those posts seemed to get no response so I guess there was no fix found. Most of the discussion on this problem starts around post #2432 in the Skyraider thread if you want to do some more digging but I couldn't really find anything more.
Some other factors to consider:
When you first flashed the ROM did you wipe all data? (factory reset, wipe data cache, wipe dalvik cache).
If you flashed a custom kernel, try going back to the stock kernel.
What version of ClockworkModRecovery are you running? They released a buggy update a couple of weeks ago and it was pulled shortly after release so if you have a version higher than 2.5.0.5 then you should revert to an older version of CWM.
You could flash the 2.15.00.09.01 radio baseband but I don't think it would make a difference with this problem. Also, if you screw up or accidentally flash the same radio over itself then you will have a brick so use extreme caution if you decide to go that route.
That pretty much exhausts my knowledge on the subject so if everything is as it should be then you could always try wiping everything and flashing the ROM again.
RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
I didn't think of that but definitely a possibility. Good call.
Best of luck.
RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
Well wouldn't you know it! Problem solved
I did not know the add ons were not compatible
Thanks everyone!
I'm glad I was able to help...
Really though, good to hear you got it working. Enjoy.
Now CM7 Nightlys Android 2.3.2 Gingerbread available:
http://mirror.teamdouche.net/?device=hero
Gapps:
gapps-gb-20110120-signed.zip from here http://goo-inside.me/google-apps/
All changes to the source code, from which the nightlies are built from, are listed there.
It is not suited for end users but hey, it´s something where you can track the current progress.
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_device_htc_hero,n,z
HTC Hero @Github
is this the same as beta3?
CM7 Nightly ROM zip is a little bit smaller,maybe some little fixes
and updates there,but don`t know,not tested at the moment.
Nightly ROM has also the the other kernel "2.6.29.6-flykernel-12pre2"
Beta 3 has "2.6.29.6-flykernel-12a" kernel!
But Flykernel-12a is newer than Flykernel-12pre2, isn't it? Also, could anybody tell me how nightlies work? Is it like you get updates pushed to your device through the CyanogenMod menu, like OTA? Please explain lol
12a should be newer,but don`t know why now 12pre2!
Maybe more optimized for CM based ROMs.
You can ask erasmux:
http://forum.xda-developers.com/showthread.php?t=730471
wow,there is something that is good for expecting
12a will be used soon if I read the commits at github:
https://github.com/loxK/android_device_htc_hero/commit/53b03bf186cd4a4d47b3604cd6290e8dc8cfdb1b
I believe it was something about CM asking for IPv6 to be build as module, while in 12a this is included statically (straight into the kernel).
Krizp0 said:
Also, could anybody tell me how nightlies work? Is it like you get updates pushed to your device through the CyanogenMod menu, like OTA? Please explain lol
Click to expand...
Click to collapse
I second this question. I've never used nightlies before. Could someone please explain how they work?
Download and flash them. No OTA update (but its a great idea).
Wipes in between are not necessary but sometimes you need them.
Not every new nightly is better then the last one (performance).
i think that my Hero doesn't like these 2.3 roms ... i've flashed few of them, none will boot.
could it be the recovery or something ?
1immortal said:
i think that my Hero doesn't like these 2.3 roms ... i've flashed few of them, none will boot.
could it be the recovery or something ?
Click to expand...
Click to collapse
Yeah. You need the lastest recovery 'cause of some drivers.
RA-hero-v1.7.0.1
Link: http://forum.xda-developers.com/showthread.php?t=561124
thats the one i'm running, and also tried the other one, from clockworkmod, same thing:
1. wipe EVERYTHING.
2. WIPE again.
3. flash the rom.
and .... nada, nothing.
even replaced the sd card, still same crap.
this Hero ran cronos twice, and since then... not a single 2.3 rom.
2.1, 2.2 , no probs, reflashed the radio, tried everything.
wtf ???
1immortal said:
thats the one i'm running, and also tried the other one, from clockworkmod, same thing:
1. wipe EVERYTHING.
2. WIPE again.
3. flash the rom.
and .... nada, nothing.
even replaced the sd card, still same crap.
this Hero ran cronos twice, and since then... not a single 2.3 rom.
2.1, 2.2 , no probs, reflashed the radio, tried everything.
wtf ???
Click to expand...
Click to collapse
Hmmmm maybe some are boot oc but i dont think so.
How long have you waited till you think its bootlooping? Do you only see the "HERO"-screen or do you see the bootanimation? keyboard lights are off all the time?
can't even see the bootanimation. only seeing the spl logo, and it reboots there.
1immortal said:
can't even see the bootanimation. only seeing the spl logo, and it reboots there.
Click to expand...
Click to collapse
huuuuuuu crazy Okay sorry i dont know. You can create a logcat (dont ask me) and post it over the CM forum. Also you can tweet Lox and show him your log. Maybe he know anything.
or ... i could recreate the "will it blend ?!" with this phone ...
1immortal said:
i think that my Hero doesn't like these 2.3 roms ... i've flashed few of them, none will boot.
could it be the recovery or something ?
Click to expand...
Click to collapse
yes, woudl be recovery and your wiping within the recovery OR it could be a previous rom or something you did while using a previous rom that has somehow messed up one or more files on the phone. there are parts of the phone's memory that can sort of seem to get stuck. I can't explain more as I have no further details other than first hand experience with this phenomenon.
wiping several times in a rom, or wiping fully (all types of wipes in recovery menu) then flashing a totally different rom (like a 2.1 sense rom) then wiping fully and flashing the rom you want to use could maybe fix it - if in fact this is the cause of your problem.
try wiping ONLY dalvik cache AFTER flashing the rom. i use recovery 1.6 and everything works.
Found this,seems there is another bug at Android 2.3.2 too.
Not only the SMS bug!
Android 2.3 Shows Security Bug, Can Gain Access To Content On microSD Cards
http://www.talkandroid.com/28696-and...microsd-cards/
Have you tried wiping with fastboot? Then flash the ROM.
posted from the other side of town with a 2nd class stamp
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?