[ROM][JB][4.3][2013-12-29] CyanogenMod 10.2


@M1cha I've just switched over to this ROM and like it a lot, but am running into two problems which I suppose may be interrelated: first, the phone sometimes fails to go into Deep Sleep consistently because of kernel wakelocks from msm_otg; a reboot typically "fixes" this issue temporarily, but it then shows up sometimes again after charging. Secondly, charging doesn't work consistently: using the same chargers or USB cables, I can sometimes plug in and see no charge, and sometimes plug in and it charges fine.

When it plugs in and doesn't charge, here's all that shows up in dmesg:

Code: 
[ 1021.199969] chg_gone_irq_handler: chg_gone=0, usb_valid = 1
[ 1021.200427] chg_gone_irq_handler: Chg gone fsm_state=3
[ 1023.125377] adjust_soc: ibat_ua = 148900, vbat_uv = 4086406, soc = 95, batt_temp=128
[ 1043.124980] adjust_soc: ibat_ua = 141600, vbat_uv = 4085521, soc = 95, batt_temp=130

When it plugs in and starts charging successfully, here's what shows up in dmesg:

Code: 
[ 5383.139141] adjust_soc: ibat_ua = 124100, vbat_uv = 4006066, soc = 83, batt_temp=86
[ 5386.930687] chg_gone_irq_handler: chg_gone=0, usb_valid = 1
[ 5386.930962] chg_gone_irq_handler: Chg gone fsm_state=3
[ 5386.931603] msm_otg msm_otg: USB exited from low power mode
[ 5387.054905] pm8xxx-led pm8xxx-led: resume red set 255
[ 5387.055241] pm8xxx-led pm8xxx-led: resume green set 255
[ 5387.055515] pm8xxx-led pm8xxx-led: resume blue set 0
[ 5387.068914] unplug_check_worker: usb_now=500, usb_target = 500
[ 5387.268883] unplug_check_worker: Stopping Unplug Check Worker USB == 500mA
[ 5387.509018] msm_otg msm_otg: Avail curr from USB = 1500
[ 5387.509170] msm_otg msm_otg: current: 0 -> 1500 (mA)
[ 5387.509262] pm_power_set_property_usb: usb_target_ma 1500
[ 5387.510910] msm_otg msm_otg: USB in low power mode
[ 5388.068975] unplug_check_worker: usb_now=700, usb_target = 1500
[ 5388.269036] unplug_check_worker: usb_now=850, usb_target = 1500
[ 5389.069372] unplug_check_worker: usb_now=900, usb_target = 1500
[ 5389.269127] unplug_check_worker: usb_now=1100, usb_target = 1500
[ 5390.069188] unplug_check_worker: usb_now=1300, usb_target = 1500
[ 5390.269280] unplug_check_worker: usb_now=1500, usb_target = 1500

The references to msm_otg in the successful use case are what make me wonder if the two issues are related somehow, and if they're in turn related to OTG functionality not yet working in your open source kernel. What do you think?
 
Suddenly my camera doesn't work anymore. Reboot doesn't solve the problem. Says it cannot connect. Had this problem before in older builds and even the latest one and a reboot always solved the problem. I'm using your latest build 2013-12-03. :S

Sent from my MI 2 using Tapatalk
 
wietje91 said:
Suddenly my camera doesn't work anymore. Reboot doesn't solve the problem. Says it cannot connect. Had this problem before in older builds and even the latest one and a reboot always solved the problem. I'm using your latest build 2013-12-03. :S

Sent from my MI 2 using Tapatalk
Click to expand...
Flash it again

Sent from my Mi2s
 
wietje91 said:
Suddenly my camera doesn't work anymore. Reboot doesn't solve the problem. Says it cannot connect. Had this problem before in older builds and even the latest one and a reboot always solved the problem. I'm using your latest build 2013-12-03. :S

Sent from my MI 2 using Tapatalk
Click to expand...

I have this problem too after open the camera and at the same time rotate the phone. After a re flash with cache wipe all works ok.

Enviado desde mi MI 2 mediante Tapatalk
 
Still not working. It's really strange. It was working fine till today. I've been using the latest build since release. Now I can't take pictures anymore :(

Sent from my MI 2 using Tapatalk
 
Still no solution for my camera. Reinstalled, cleared cache, dalvik cache everything. After reinstall, camera works perfect. But when I recover my apps (root apps like greenify trickster, wireless tether) with titanium camera isn't working anymore. And no I don't flash systems apps from the backup. I find this really strange, because everytthing was working perfect the last few weeks and now suddenly camera doesn't work anymore. I didn't make big changes or such. When I boot an old cofface rom from other system, camera works just fine.
 
Code: 
12-20 15:52:21.558 E/mm-libcamera2(191): mm_camera_open:  ctrl_fd = -1
12-20 15:52:21.558 E/mm-libcamera2(191): Errno:110
12-20 15:52:21.558 E/mm-libcamera2(191): mm_camera_open:  opened, break out while loop
12-20 15:52:21.558 E/mm-libcamera2(191): mm_camera_open:  after while loop
12-20 15:52:21.558 E/QCameraHWI(191): startCamera: cam_ops_open failed: id = 0
12-20 15:52:21.558 E/QCameraHWI(191): isCameraReady mCameraState 0
12-20 15:52:21.558 E/QualcommCamera(191): int android::camera_device_open(const hw_module_t*, char const*, hw_device_t**):  end rc -1
12-20 15:52:21.558 E/CameraClient(191): Could not open camera 0: -1
12-20 15:52:21.558 E/CameraClient(191): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
12-20 15:52:21.558 I/CameraClient(191): Destroying camera 0
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7beee10 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7beed58 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7beecb8 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7bc8fa8 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7bef450 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7bef328 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7bef208 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7bef078 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7bc9170 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7be9a68 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7bbe018 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7bb3040 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7beb4e0 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7beb248 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7beb108 successful
12-20 15:52:21.558 I/OMXNodeInstance(191): OMX_FreeBuffer for buffer header 0xb7bbe4a0 successful
12-20 15:52:21.568 E/CameraHolder(10945): fail to connect Camera
12-20 15:52:21.568 E/CameraHolder(10945): java.lang.RuntimeException: Fail to connect to camera service
12-20 15:52:21.568 E/CameraHolder(10945):    at android.hardware.Camera.native_setup(Native Method)
12-20 15:52:21.568 E/CameraHolder(10945):    at android.hardware.Camera.<init>(Camera.java:366)
12-20 15:52:21.568 E/CameraHolder(10945):    at android.hardware.Camera.open(Camera.java:322)
12-20 15:52:21.568 E/CameraHolder(10945):    at com.android.camera.CameraManager.cameraOpen(CameraManager.java:304)
12-20 15:52:21.568 E/CameraHolder(10945):    at com.android.camera.CameraHolder.open(CameraHolder.java:210)
12-20 15:52:21.568 E/CameraHolder(10945):    at com.android.camera.Util.openCamera(Util.java:457)
12-20 15:52:21.568 E/CameraHolder(10945):    at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:311)

This is the logcat, when I try to open camera
 
Hello M1cha & linuxx

First thanks for your terrific job!
Tell me please is there any USB DAC support in Cyanogen?
If there is't will it be possible in your builds? It's very important for me...

Thanks again!
 
rsync from phone averages at 350 kbps (both on small and big files) over WiFi. I used to get cca 2 Mbps on older Samsung Galaxy (CM 10.1). Testing speed via sftp (initiated from PC to phone's DropBear SSHdroid server) gives cca 2Mbps.

Code: 
rsync: Android port by Dylan Simon: http://github.com/dylex/android_external_rsync
ssh: Dropbear client v0.53.1

rsync -vHrltpD --chmod=Du+rwx,go-rwx,Fu+rw,go-rw --no-perms --delete-excluded --delete-after -e "ssh -y -p 22 -i '/sdcard/rsync/dss_key'" /storage/sdcard0/ user@comp:/home/user/BackUp/

Code: 
# top
Mem: 1875332K used, 46736K free, 0K shrd, 12912K buff, 542300K cached
CPU:  0.0% usr  0.0% sys  0.0% nic 80.2% idle  0.0% io  0.0% irq  0.0% sirq
Load average: 1.60 1.69 1.54 1/1439 30718
Idle alternates between 100 % and cca 10 %. Changing CPU governor and I/O scheduler does not make a significant difference.

Anybody can help how to proceed further with debugging?

EDIT: I've given up and initiate rsync from PC instead from Mi2. Not so much comfortable, though.
 
Last edited:
Sorry in advance for the following noob question: maybe I just didn' read enough of the 61 pages here.
I would like to test this rom on my mi2s with last cwm, true dual boot turned on. Sytem 1 is running WIUI (android 4.1.1). It's running great, but I wont to get more specific rights management (app-ops), and I need android 4.3 for that.

I downloaded the ROM from post #1-link, md5 is good, installed it via cwm to system 2, reboot system 2, and get stuck on cyanogen-mod bootscreen.

Can I get some advice what went wrong?
 
principio said:
Sorry in advance for the following noob question: maybe I just didn' read enough of the 61 pages here.
I would like to test this rom on my mi2s with last cwm, true dual boot turned on. Sytem 1 is running WIUI (android 4.1.1). It's running great, but I wont to get more specific rights management (app-ops), and I need android 4.3 for that.

I downloaded the ROM from post #1-link, md5 is good, installed it via cwm to system 2, reboot system 2, and get stuck on cyanogen-mod bootscreen.

Can I get some advice what went wrong?
Click to expand...
Wipe /data ? And tdb is enabled?

Sent from my Mi2s
 
Well yes, tdb is actually enabled.
But wipe /data? Isn't that what its all about with tdb, that you can access all your data from two /system partitions? I thought that wiping /data will delete all data as well on system 1. And then I would have the same problem when I want to return, don't I?
 
principio said:
Well yes, tdb is actually enabled.
But wipe /data? Isn't that what its all about with tdb, that you can access all your data from two /system partitions? I thought that wiping /data will delete all data as well on system 1. And then I would have the same problem when I want to return, don't I?
Click to expand...
No, tdb separate data partitions

Inviato dal mio MI 2(s) utilizzando Tapatalk
 
  • Like
Reactions: principio
linuxx said:
No, tdb separate data partitions

Inviato dal mio MI 2(s) utilizzando Tapatalk
Click to expand...
Happy using this rom now.
Only the camera is not responding. On github I have seen that there was a topic about 13 megapic settings, but I don't get there at all. Any ideas?

Gesendet von meinem MI 2 mit Tapatalk
 
principio said:
Happy using this rom now.
Only the camera is not responding. On github I have seen that there was a topic about 13 megapic settings, but I don't get there at all. Any ideas?

Gesendet von meinem MI 2 mit Tapatalk
Click to expand...

You have MI2S 32Go?!

Envoyé de mon MI 2S en utilisant Tapatalk
 
You must log in or register to reply here.

Similar threads

ingbrzy
  • Locked
MIUI 13 22.4.27/29
Replies
254
Views
108K
MIUI 13
gogocar62
gogocar62
ingbrzy
  • Locked
MIUI 13 22.10.26 (Final)
Replies
267
Views
322K
MIUI 13
Kozuso
K
ingbrzy
  • Locked
MIUI 13 22.10.19
Replies
93
Views
78K
MIUI 13
Birraque
Birraque
ingbrzy
  • Locked
MIUI 13 22.10.12
Replies
142
Views
71K
MIUI 13
mik101
mik101
ingbrzy
  • Locked
MIUI 13 22.9.29
Replies
251
Views
112K
MIUI 13
moskito99
moskito99
Top Bottom
Back