Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

Some issues after upgrading to 7.1.0

camera freezing

  • Please log in to reply
24 replies to this topic

#1 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 13 November 2011 - 11:48 PM

Hi there, last week I upgraded from 7.0.X to 7.1.0 using ROMManager from a zip on my SD card, and I have been having a few niggly problems ever since:

1) The lock screen occasionally freezes - the only working button is the Emergency call button. A combination of pressing that, followed by the back button, tends to reenable numpad. The commonly happens when charging my phone.

2) The UI becomes sometimes unresponsive and I have to use the trackball to open the Fast Reboot app, which fixes things.

3) The camera app won't open at all.

Any suggestions? Anyone else experiencing this?

Cheers,
Jim

Edited by burwatti, 13 November 2011 - 11:49 PM.


#2 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts
  • LocationRamstein Air Base, Germany
  • Country:de
  • Device Model:Nexus One/HTC One X
  • MOD Version:Nightlies/Stock
  • Recovery Image:ClockworkMod

Posted 14 November 2011 - 12:36 AM

Try wiping the /system partition and reinstalling CM and gapps. This won't cause any data loss.

#3 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 14 November 2011 - 01:36 AM

Thanks for your quick response. What's the safest way to delete the /system partition?

EDIT: with ClockworkMod Recovery. Got it.

Edited by burwatti, 14 November 2011 - 01:38 AM.


#4 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 14 November 2011 - 01:53 AM

Ok, I've tried wiping /system and have reflashed 7.1.0. The camera still doesn't work (black screens), I'll have to wait and see whether the other problems have sorted themselves out.

I just looked at my log - I get the error:

Quote

E/QualcommCameraHardware( 116): native_access_parm:error (No such file or directory): fd 22, type 1, length 32, status 0

One other problem that I forgot to mention in my initial post - my phone now has real trouble remembering that I have a network operator and I have to click "Mobile network settings > Select automatically" every time I reboot / exit airplane mode...

Cheers, Jim

#5 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts
  • LocationRamstein Air Base, Germany
  • Country:de
  • Device Model:Nexus One/HTC One X
  • MOD Version:Nightlies/Stock
  • Recovery Image:ClockworkMod

Posted 14 November 2011 - 08:45 AM

With the camera issue, try renaming your DCIM folder to something else (like DCIM.bak). Then try to use the camera (the camera app will recreate the folder).

With the Mobile Network, I really don't know on that one. It might be worth it to try a complete wipe. You can save all your apps and app data with a program like Titanium Backup. Just make sure you don't back up system settings as restoring those could also restore your problem.

#6 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 14 November 2011 - 11:45 AM

I tried renaming the folder - this no longer makes the Camera black screen, instead I get a "Camera error: cannot connect to camera" dialog. The stack trace in aLogCat is:

E/CameraHolder( 1641):  java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 1641):  at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 1641):  at android.hardware.Camera.<init>(Camera.java:258)
E/CameraHolder( 1641):  at android.hardware.Camera.open(Camera.java:220)
E/CameraHolder( 1641):  at com.android.camera.CameraHolder.open(CameraHolder.java:124)
E/CameraHolder( 1641):  at com.android.camera.Camera.startPreview(Camera.java:1865)
E/CameraHolder( 1641):  at com.android.camera.Camera.access$5500(Camera.java:94)
E/CameraHolder( 1641):  at com.android.camera.Camera$3.run(Camera.java:944)
E/CameraHolder( 1641):  at java.land.Thread.run(Thread.java:1019)

And a warning:

W/CameraService( 116): CameraService::connect X (pid 1641) rejected (existing client).

I might try a complete wipe this evening...

Cheers, Jim

#7 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 17 November 2011 - 09:34 PM

Sorry about the delayed reply. I've finally had a chance to wipe my phone. First impressions are that it's a lot better - I can get 3G now which I couldn't before (forgot to mention that), but will have to wait a while to see if the UI issues are still there.

Sadly though, the camera problem still exists. If you haven't any other suggestions, I may have to downgrade to 7.0.3. No other Nexus One users had camera issues?

Thanks,
Jim

#8 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts
  • LocationRamstein Air Base, Germany
  • Country:de
  • Device Model:Nexus One/HTC One X
  • MOD Version:Nightlies/Stock
  • Recovery Image:ClockworkMod

Posted 18 November 2011 - 05:26 AM

What is your radio/baseband version? Settings -> About Phone

#9 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 18 November 2011 - 09:03 AM

32.50.00.32U_5.12.00.08

Have had a couple of UI freeze ups again - problem not gone away :(

-Jim

#10 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts
  • LocationRamstein Air Base, Germany
  • Country:de
  • Device Model:Nexus One/HTC One X
  • MOD Version:Nightlies/Stock
  • Recovery Image:ClockworkMod

Posted 18 November 2011 - 10:36 AM

And you aren't restoring any system settings when using Titanium Backup (if you are using it)?

#11 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 19 November 2011 - 04:05 PM

Nope - I just restored apps and app data.

#12 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts
  • LocationRamstein Air Base, Germany
  • Country:de
  • Device Model:Nexus One/HTC One X
  • MOD Version:Nightlies/Stock
  • Recovery Image:ClockworkMod

Posted 19 November 2011 - 05:42 PM

I doubt this is related, but it may be worth a shot. The recommended radio version for Gingerbread is 5.08 (we just use the two sets of numbers after the underscore "_"). You are currently running 5.12, which google decided to skip over when they released the update to Gingerbread (they included the 5.08 radio with the GIngerbread OTA update).

#13 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 20 November 2011 - 02:52 PM

Okay, worth a shot - so where would I get the radio update for 5.08? BTW I had applied the OTA Gingerbread update before flashing Cyanogen..

#14 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts
  • LocationRamstein Air Base, Germany
  • Country:de
  • Device Model:Nexus One/HTC One X
  • MOD Version:Nightlies/Stock
  • Recovery Image:ClockworkMod

Posted 20 November 2011 - 10:03 PM

I wonder if at some other point you updated to the 5.12 radio. But to update the radio, you will either need to be running Amon_RA or ClockworkMod v2.x recoveries. Then I believe the radio is available on the wiki, but if not, xda will have it for the N1 wiki.

#15 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 01 December 2011 - 06:54 PM

Hi bassmadrigal, sorry it's taken so long to reply again. I've finally gotten around to trying to flash the radio.. but can't. I downloaded the 5.08 radio from the wiki - trying to flash it with ClockworkMod Recovery which doesn't work as CMRv3 no longer supports amend scripting. So I tried to flash it using fastboot, but this didn't work either - giving me an error as follows:


> fastboot flash radio passion.radio-5.08.00.04-signed.zip
sending 'radio' (26114 KB)... OKAY
writing 'radio'... FAILED (remote: image update error)

Any suggestions?

I've reflashed 7.1.0 and the problems are all still there (I haven't performed any backup at all). I think I'll downgrade to 7.0.3 now for the time being, my phone is getting more and more unstable - freezing and crashing, whilst I'm suffering from the power button issue meaning that I have to kick start the phone every time using the battery trick. Sad times.

Thanks

#16 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 01 December 2011 - 07:19 PM

Hmm... I just downgraded to 7.0.3 (performing a complete cache and data wipe) and the camera problem is still there... When running 7.0.3 previously, there was no problem at all. It's too early to tell whether the other problems are now in this version, but I'm totally confused.

-Jim

#17 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts
  • LocationRamstein Air Base, Germany
  • Country:de
  • Device Model:Nexus One/HTC One X
  • MOD Version:Nightlies/Stock
  • Recovery Image:ClockworkMod

Posted 01 December 2011 - 07:36 PM

With flashing through recovery, you would need to be running ClockworkMod v2.x or Amon_RA. Or if you wanted to flash through fastboot, you need to unzip the file and flash the img file.

And to really get yourself back to a stock configuration, you NEED to wipe the /system partition along with performing a Factory Reset/Data Wipe. Those two will wipe out everything except for your sdcard.

#18 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 01 December 2011 - 08:30 PM

Ok, I've flashed 5.08, and I just formatted /system, did a factory reset, and reinstalled 7.1.0. The camera still doesn't work...

I really appreciate your help with this, by the way.

#19 bassmadrigal

bassmadrigal
  • Moderators
  • 4,058 posts
  • LocationRamstein Air Base, Germany
  • Country:de
  • Device Model:Nexus One/HTC One X
  • MOD Version:Nightlies/Stock
  • Recovery Image:ClockworkMod

Posted 01 December 2011 - 09:11 PM

Maybe you should try reverting to a stock build to see if something got screwed up with your hardware. Because with a clean system the camera *should* function properly. Have you tried backing up your sdcard and completely formatting it (you can also wipe the sdcard through the recovery)? I am really running out of things it could be... unless it is hardware. :(

#20 burwatti

burwatti
  • Members
  • 12 posts
  • Device Model:Nexus One
  • MOD Version:7.1.0-N1
  • Recovery Image:Cyanogen

Posted 01 December 2011 - 09:24 PM

I think that's worth a go. I haven't got the time tonight, so I'll keep things as they are and see if any of the other problems reappear. I'll let you know what happens when I revert to stock. I hope it isn't hardware... It *shouldn't* be. Anyway, I can upgrade my phone in January.. Think I'll get the Galaxy Nexus :-)

Thanks again for your help, bassmadrigal. You're a hero.





Also tagged with camera, freezing