CyanogenMod 10.1 - Beta 4 - Discussion thread / Bug report

Opening this thread in order for the users to post their issues here instead of the development section or CM10 bug report thread.

This thread refers to discussions/bug reports for CM10.1 (Android 4.2.2) released by arco68 here.
As usual, it would be best to keep an organized fashion of your bug reports for the developers to easily spot them and maybe fix them.

On behalf of the SGW users, big thanks to arco68 and the CyanogenMod Team!

Great job, guys!

Note: bugs concerning custom kernels are to be reported into the corresponding threads! Please, don't post them here.


In order to avoid posting bugs that are not actually bugs, please, make sure you follow this little tutorial before upgrading/installing CM10.1:

For installation, first, make sure you got CM10.1 ROM and the correct Gapps on your External SD Card. Both can be found in the Mirrors section below.

After that, enter CWM and:

• select "wipe data / factory reset"
• go to "mounts & storage" and format /system. This is extremely important!
• under the same menu, format /sdcard (be careful NOT to format /external_sd by mistake)*
• install CM10.1 (from the external sd)
• install Gapps for JB+ (from the external sd)
• reboot your phone
  
  * On newer CWM Recovery versions, you might find the internal memory mounted as /sdcard0 and the external one as /sdcard1. For this case, make sure you don't format /sdcard1 by mistake.

7. Now that we chose what apps we want to be restored without app data, let's go back and enter New/Restore Backup section (yeah, again ).

10. Check only the apps for which you DO need app data to be restored (the ones that were left unrestored from last time ).

[B]Version:[/B] CM10.1 - Beta 4
[B]App/Game/Subject:[/B] WRITE HERE SUBJECT
[B]Bug title:[/B] WRITE HERE BUG TITLE
[B]Probability of occurrence:[/B] WRITE HERE "LOW/MEDIUM/HIGH" (depending on how often the bug occurs)
[B]Description:[/B] WRITE HERE DESCRIPTION

# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=[COLOR="Blue"]0[/COLOR]

# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=[COLOR="Red"]1[/COLOR]

• Camera/Gallery app becomes unresponsive when locking&unlocking the screen multiple times (about 4 times in my tests). After that, if the user chooses to force close the Gallery app, when entering the Camera app again, he will be prompted with the following error message: "Can't connect to the camera".
  Please, see the attached screenshot and the log below for more info.
  
  Code:

  [ 08-05 15:13:30.010   441:  456 W/ActivityManager ]
   Activity idle timeout for ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}
   
   [ 08-05 15:13:31.521   441:  503 I/InputDispatcher ]
   Application is not responding: AppWindowToken{414fc260 token=Token{41691380 ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}}} - Window{4122f110 u0 com.android.gallery3d/com.android.camera.CameraLauncher}.  It has been 5003.1ms since event, 5001.2ms since wait started.  Reason: Waiting because the focused window has not finished processing the input events that were previously delivered to it.
   
   [ 08-05 15:13:31.531   441:  503 I/WindowManager ]
   Input event dispatching timed out sending to com.android.gallery3d/com.android.camera.CameraLauncher
   
   [ 08-05 15:13:31.621   441:  503 I/Process  ]
   Sending signal. PID: 5350 SIG: 3
   
   [ 08-05 15:13:31.621  5350: 5355 I/dalvikvm ]
   threadid=3: reacting to signal 3
   
   [ 08-05 15:13:31.701  5350: 5355 I/dalvikvm ]
   Wrote stack traces to '/data/anr/traces.txt'
   
   [ 08-05 15:13:31.701   441:  503 I/Process  ]
   Sending signal. PID: 441 SIG: 3
   
   [ 08-05 15:13:31.701   441:  444 I/dalvikvm ]
   threadid=3: reacting to signal 3
   
   [ 08-05 15:13:31.882   143: 5647 E/CAM_FD   ]
   cam_conf: In config thread
   
   [ 08-05 15:13:31.992   441:  503 I/Process  ]
   Sending signal. PID: 553 SIG: 3
   
   [ 08-05 15:13:31.992   553:  560 I/dalvikvm ]
   threadid=3: reacting to signal 3
   
   [ 08-05 15:13:32.002   441:  444 I/dalvikvm ]
   Wrote stack traces to '/data/anr/traces.txt'
   
   [ 08-05 15:13:32.002   441:  503 I/Process  ]
   Sending signal. PID: 656 SIG: 3
   
   [ 08-05 15:13:32.002   656:  670 I/dalvikvm ]
   threadid=3: reacting to signal 3
   
   [ 08-05 15:13:32.042   553:  560 I/dalvikvm ]
   Wrote stack traces to '/data/anr/traces.txt'
   
   [ 08-05 15:13:32.092   656:  670 I/dalvikvm ]
   Wrote stack traces to '/data/anr/traces.txt'
   
   [ 08-05 15:13:32.212   441:  443 D/dalvikvm ]
   GC_CONCURRENT freed 1916K, 21% free 10090K/12716K, paused 4ms+7ms, total 97ms
   
   [ 08-05 15:13:32.212   441:  503 D/dalvikvm ]
   WAIT_FOR_CONCURRENT_GC blocked 65ms
   
   [ 08-05 15:13:32.422   441:  503 D/dalvikvm ]
   GC_EXPLICIT freed 777K, 21% free 10132K/12716K, paused 4ms+5ms, total 91ms
   
   [ 08-05 15:13:32.632   441: 1243 E/Sensors  ]
   type : 0, deley : 66667000 
   
   [ 08-05 15:13:32.632   441: 1242 E/Sensors  ]
   type : 0, deley : 20000000 
   
   [ 08-05 15:13:33.003   441:  503 I/Process  ]
   Sending signal. PID: 1051 SIG: 3
   
   [ 08-05 15:13:33.003  1051: 1056 I/dalvikvm ]
   threadid=3: reacting to signal 3
   
   [ 08-05 15:13:33.103  1051: 1056 I/dalvikvm ]
   Wrote stack traces to '/data/anr/traces.txt'
   
   [ 08-05 15:13:33.113   441:  503 E/ActivityManager ]
   ANR in com.android.gallery3d (com.android.gallery3d/com.android.camera.CameraLauncher)
   Reason: keyDispatchingTimedOut

• After rendering the Panorama shots, when the camera returns to the Panorama Mode for the user to take another panoramic shot, the camera preview is flickering. This happens only if the Auto-Rotate function is ON and the screen in Portrait mode. With the Auto-Rotate OFF, this bug does not occur.
  Please, see the attached screenshot for, hopefully, more info on this.
• Camera/Gallery app becomes unresponsive when taking a picture, sliding left to see the picture and tapping on it to see it in "full screen" then locking the screen for about 10 seconds. After that, if the user chooses to force close the Gallery app, when entering the Camera app again, the user will be prompted with the following error message: "Can't connect to the camera". Please, see the attached screenshot for more info.
• Setting the light exposure to 4 or -4, the icon on the bottom right doesn't show any number (as it does for any other value) and if slide to the left to enter the Gallery and come back to camera app, the icon appears distorted. This happens only for value "4" or "-4". Workaround: switch to any of the other values and then back to 4.
  Please, see the attached screenshot for more info.
• Zooming in/out doesn't work in video mode. Nothing happens when using two fingers to zoom in or out. No change in the actual image.
  Please, see the log below for zooming issue.
  
  Code:

   E/QualcommCameraHardware(148): Failed to get maximum zoom value...setting max zoom to zero

• The text for the "straighten" option is missing the first 2-3 letters in the default photo editor (please, see the attached screenshot for more info). The options section from that screen cannot be slid more to the left to see the rest of the word.
  This happens most likely because the spaces between the icons (options) from the top row of editing options don't adjust to the new screen orientation (Portrait). They look ok in Landscape mode, but it seems that the space between the icons from that row is kept the same no matter of the screen orientation, leading to some of the options not to be completely visible.

• cLock widget does not properly resize when the launcher is set to Landscape mode (launcher auto-rotate option is ON). The widget is cut off (please, see the attached screenshot for more info). The widget looks good in Portrait mode. But when turning the screen to landscape mode, it's cut.

• Enabling encryption in the Security Settings will make the PIN code for the SIM card (assuming it's set to be requested) not to be requested anymore, thus making the "phone" part of the device unusable. No calls (voice or data), no SMS, no MMS can be sent or received. Workaround: make a nandroid backup before encrypting and restore it afterwards.
• If the user turns off the SIM card PIN code request before performing the encryption, after it's finished, the APNs previously set will disappear and there won't be any way to re-add them manually, thus making the data connection unusable. He will be able to make voice calls and send SMS though.
• After the encryption, if SIM PIN request is OFF, in the notification drawer and quicksettings panel, the user will be informed that he has no service (please, see the attached screenshots for more info) although, by going into Settings -> About Phone -> Status, he will see that the network is successfully recognized and there is definitely some service. (please, see the attached screenshot for more info on this too).

• From time to time, but apparently more often after recently (not immediately after) closing an incoming voice call, the phone reboots.
  This does not happen with kernel 3.4.56 but it does happen with 3.4.57 so it might be because of that reverted commit.

• 
  Some third party camera apps don't work with any CM version from CM9 to CM10.1. For example, Camera 360 Ultimate v4.5 works ok on stock Android 4.1.2 and 4.2.2 (tested on Nexus devices) but doesn't work properly with any CyanogenMod version. After taking a picture, the camera preview gets stuck. No change in preview when tilting the phone.
  Please, see the log below from the moment when taking a picture with Camera 360. Maybe it helps solve this problem.

W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.getParentParam(EffectInfoFactory.java:1433)
W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.search(EffectInfoFactory.java:1303)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeAbstract.setEffect(ModeAbstract.java:106)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeNormal.onCameraStartPreview(ModeNormal.java:370)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraBaseActivity.onCreate(CameraBaseActivity.java:749)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraMain.onCreate(CameraMain.java:551)
V/QualcommCameraHardware(  143): As Auto Focus is not in progress, Cancel Auto Focus is ignored
V/QualcommCameraHardware(  143): cancelAutoFocusInternal X: 0
I/QualcommCameraHardware(  143): stopPreviewInternal X: 0
V/QualcommCameraHardware(  143): initRawSnapshot E
I/QualcommCameraHardware(  143): runframethread: waiting for preview  thread to complete.
V/QualcommCameraHardware(  143): initRawSnapshot X
V/QualcommCameraHardware(  143): takePicture: X
I/ShotSingle(  143): ShotSingle::takePicture end
I/CameraHAL(  143): camera_take_picture--- rv 0
I/QualcommCameraHardware(  143): initPreview: old preview thread completed.
QualcommCameraHardware(  143): destroying MemPool record
camera_set_preview_window---: window is NULL

V/QualcommCameraHardware(  143):  Overlay object NULL. returning 
I/CameraClient(  143): Destroying camera 0
I/CameraHAL(  143): camera_device_close+++: device 0x1f68650
I/SecCameraHardwareInterface(  143): SecCameraHardwareInterface destroyed: pid=143
I/ShotSingle(  143): ShotSingle destroyed: pid=143
I/ShotCommon(  143): ShotCommon destroyed: pid=143
No JNI_OnLoad found in /data/app-lib/vStudio.Android.Camera360-1/libmp3lame.so
I/ActivityManager(  430): Process vStudio.Android.Camera360 (pid 2142) has died.

• 
  
• 
  
  XDA:DevDB Information
  CyanogenMod 10.1 - Beta 4 - Discussion thread / Bug report, ROM for the Samsung Galaxy W I8150
  
  Contributors
  arsradu
  ROM OS Version: 4.2.x Jelly Bean
  
  Version Information
  Status: Testing
  
  Created 2013-09-29
  Last Updated 2014-05-19

reidzeibel said:

Weird things happen on my battery, it charges itself after some period of time ~_~

Click to expand...

Click to collapse