• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM 10.2 Nightlies Discussion

I'm getting much better connection on this new telephony. 4g connects in 1-3 seconds instead of 5-10. 1x data connections also show up. No 3g connections though.
 
Got a reboot today running the nightly from 10/23

Here's the last minute of the /proc/last_kmsg. Let me know if you need more than that.

Code: 
[ 5702.214294] QSEECOM: qseecom_release: data->released == false

[ 5707.292419] QSEECOM: qseecom_release: data->released == false

[ 5711.962219] QSEECOM: qseecom_release: data->released == false

[ 5717.029327] QSEECOM: qseecom_release: data->released == false

[ 5722.095947] QSEECOM: qseecom_release: data->released == false

[ 5726.802673] QSEECOM: qseecom_release: data->released == false

[ 5731.869750] QSEECOM: qseecom_release: data->released == false

[ 5736.934570] QSEECOM: qseecom_release: data->released == false

[ 5739.403442] wl_bss_connect_done succeeded

[ 5739.471038] wl_bss_connect_done succeeded

[ 5739.575958] dhd_ioctl_entry: ifidx 0, cmd 0x89f1

[ 5739.827575] dhd_ioctl_entry: ifidx 0, cmd 0x89f1

[ 5739.831726] Unknown PRIVATE command SETSUSPENDMODE 0 - ignored

[ 5740.918640] pm8058-charger pm8058-charger: pm8058_chg_fastchg_handler begin fast charging

[ 5740.947052] pm8058_get_battery_temperature_adc: therm_raw is 1056

[ 5740.967864] msm_otg_resume: usb exited from low power mode

[ 5740.980194] msm_hsusb msm_hsusb: msm72k_udc: ONLINE -> OFFLINE

[ 5740.987518] lge_skip_stop_charging_with_factory_condition: entered

[ 5740.994537] usb_do_work: usb_cable_type :0

[ 5741.016326] usb_do_work: external_cable_type_set_to_default

[ 5741.021514] sii9244_workfunc_main called : mhl_workreq = 1

[ 5741.027374] sii9244_workfunc_pwroff

[ 5741.030334] MHL_On(0)

[ 5741.032592] MHL_On : alread off

[ 5741.046417] lge_skip_stop_charging_with_factory_condition: battery is present! ignore factory condition

[ 5741.055816] pm8058-charger pm8058-charger: pm8058_stop_charging stopping charging

[ 5741.063934] mhl_pwroff_request

[ 5741.096588] pm8058-charger pm8058-charger: pm8058_stop_charging called when not fast-charging

[ 5741.105102] msm-charger msm-charger: handle_charger_removed: no chargers

[ 5741.137207] msm-charger msm-charger: handle_charger_removed: stopping safety timer work

[ 5741.145233] android_work: did not send uevent (0 0   (null))

[ 5741.166473] sii9244_workfunc_main called : mhl_workreq = 2

[ 5741.174713] sii9244_workfunc_pwron: acc_adc = 1023

[ 5741.224853] pm8058_get_battery_temperature_adc: therm_raw is 1055

[ 5741.297210] msm_otg_suspend: usb in low power mode

[ 5741.476013] dhd_ioctl_entry: ifidx 0, cmd 0x89f1

[ 5741.479705] Unknown PRIVATE command SETSUSPENDMODE 1 - ignored

[ 5741.486236] dhd_ioctl_entry: ifidx 0, cmd 0x89f1

[ 5741.596954] QSEECOM: qseecom_release: data->released == false

[ 5747.071319] QSEECOM: qseecom_release: data->released == false

[ 5747.229705] sensor_common_power_set pwr_mask(6), on(1), sensor(1)

[ 5747.240997] [APDS9900] [apds9900_check_reliablility 932] ### apds9900_check_reliablility fail!! reinit device !! control reg(0),buf(20)

[ 5747.283020] request_suspend_state: wakeup (3->0) at 5746906910873 (2013-10-24 18:37:18.556151405 UTC)

[ 5747.352203] hall_late_resume: 

[ 5747.354370] sensor_common_power_set pwr_mask(7), on(1), sensor(1)

[ 5747.481567] dhd_ioctl_entry: ifidx 0, cmd 0x89f1

[ 5747.485229] Unknown PRIVATE command SETSUSPENDMODE 0 - ignored

[ 5747.660461] mdp4_csc_config: Block type 10 isn't supported by CSC.

[ 5747.660491] mdp4_csc_config: Block type 8 isn't supported by CSC.

[ 5747.671508] entering mipi_lgit_lcd_on .. 

[ 5747.806335] exting mipi_lgit_lcd_on .. 

[ 5747.881652] mdp4_overlay_mdp_perf_upd mdp clk is changed [1] from 0 to 85330000

[ 5747.888519] mdp4_overlay_mdp_perf_upd mdp bw is changed [1] from 4 to 2

[ 5751.508300] QSEECOM: qseecom_release: data->released == false

[ 5751.786315] wlan0: no IPv6 routers present

[ 5755.770294] msm_camera_vreg_enable: 

[ 5755.796295] [CAMERA]: msm_camio_sensor_clk_on[clk should be enable]: 

[ 5755.802124] main_camera_power_on: 

[ 5755.994934] mipi_lgit_lcd_ief_off, 0

[ 5756.056457] imx105_af_init the Infinity AF Position DAC Value is 176

[ 5756.065521] imx105_af_init the 1m AF Position DAC Value is 203

[ 5756.071441] imx105_af_init the 10cm AF Position DAC Value is 461

[ 5756.077087] imx105_af_init the vcm  Start current DAC Value is 164

[ 5756.085723] imx105_af_init the vcm Operating sensitivity DAC Value is 505

[ 5756.092010] imx105_sensor_open_init :: (success)eeprom read success during af_init() 

[ 5756.099456] imx105_sensor_open_init: 1613, rc = 0 

[ 5756.107666] imx105_sensor_open_init done

[ 5756.119140] [QCTK_EEPROM] Start reading EEPROM

[ 5756.123046] [QCTK_EEPROM] Product version = 0x1055

[ 5756.128906] [QCTK_EEPROM] r_over_g = 0x 205

[ 5756.134429] [QCTK_EEPROM] b_over_g = 0x 230

[ 5756.198211] msm_io_csi_irq MIPI_INTERRUPT_STATUS = 0xa0030a

[ 5756.549560] QSEECOM: qseecom_release: data->released == false

[ 5756.833343] vfe31_proc_general: cmdID = RESET

[ 5756.843383] vfe31_proc_general: cmdID = START

[ 5757.413116] send sigkill to 21783 (roid.alarmclock), adj 15, size 4998

[ 5758.470520] pm8058_get_battery_temperature_adc: therm_raw is 1048

[ 5761.597656] QSEECOM: qseecom_release: data->released == false

[ 5765.186309] mdp4_dsi_video_wait4vsync timeout ret=0

[ 5765.216278] entering mipi_lgit_lcd_off .. 

[ 5765.307006] exting mipi_lgit_lcd_off .. 

[ 5765.312652] mipi_dsi_panel_power(off): success

[ 5765.348785] request_suspend_state: sleep (0->3) at 5764972645737 (2013-10-24 18:37:36.621916787 UTC)

[ 5765.358093] sensor_common_power_set pwr_mask(7), on(0), sensor(1)

[ 5765.368652] hall_early_suspend: 

[ 5765.396026] sensor_common_power_set pwr_mask(6), on(0), sensor(1)

[ 5765.401428] dhd_set_suspend: force extra Suspend setting 

[ 5765.412139] dhd_get_dtim_skip bcn_li_dtim=3 DTIM=1 Listen=10

[ 5765.419433] dtv_pipe is not configured yet

[ 5765.479217] vfe31_proc_general: cmdID = STOP

[ 5765.482971] msm_release_frame: frame0

[ 5765.486572] __msm_release, open count =2

[ 5765.499481] msm_release_config: config0

[ 5765.508514] __msm_release, open count =1

[ 5765.512786] msm_release_control: control0

[ 5765.515838] msm_release_control, stop vfe if active

[ 5765.520996] __msm_release, open count =0

[ 5765.524688] __msm_release, release VFE

[ 5765.529907] msm_io_csi_irq MIPI_INTERRUPT_STATUS = 0xd80830

[ 5765.618316] dhd_ioctl_entry: ifidx 0, cmd 0x89f1

[ 5765.622161] Unknown PRIVATE command SETSUSPENDMODE 1 - ignored

[ 5765.636627] vibrator_enable is stating ... 

[ 5765.644958] android_vibrator_off is stating ... 

[ 5765.648895] LGE: vibrator_power_set  enable=0

[ 5765.653045] android_vibrator_off is exting ... 

[ 5765.657745] vibrator_enable is exting ... 



No errors detected

The only lines that jumped out at me were:

Code: 
[ 5747.240997] [APDS9900] [apds9900_check_reliablility 932] ### apds9900_check_reliablility fail!! reinit device !! control reg(0),buf(20)

[ 5747.283020] request_suspend_state: wakeup (3->0) at 5746906910873 (2013-10-24 18:37:18.556151405 UTC)

This was while the phone was in my pocket while driving home... So I can't think of anything specific to reproduce.
 
Same thing here, happened on train. Looked down phone is rebooting.

Otherwise everything I've tried has worked. Bluetooth worked today, wasn't working for me on previous nightly.
 
10/24 nightly works fine also. Camera photo/video works for me. Free memory seemed higher than 10/23 (420 vs 320 MB)
 
I'm not using this anymore but I was getting constant reboots with clean flash. Reboot pretty much every time I used my phone no matter what I was doing. Sometimes it would hang and boot loop as well. Had to pull battery.
 
Interesting, as I never had a reboot on CM10.2 nightly. It's my daily driver and I get a lot of texts, phone calls, and I usually zap my extended battery by 5pm since I use it so much. It's rock stable for me. TWRP 2.6.3.0 is also perfect recovery for me. Chameleon works but laggy compared to this. PACE works but also a little laggy (better than Chameleon). I have not tried Beanstalk yet. I've not been able to try any JB 4.3 independent kernel yet as it has failed at installation.

I run DX toolbox, V6 script, Crossbreeder flash in recovery, Leo AGPS injector, and Supermanager to keep my phone optimized with 300-400 MB free RAM at all times. GPS works fine and usually acquire signal within 10 sec at most on Google Maps. I run Pandora or Google Music frequently while I'm scoping.

I have 8 Android devices and all are rooted with custom ROMS as well as Google TV, Google Chromecast, and Android TV stick. :p

P.S. I moved over from HTC Rezound on Verizon to this as my contract is not up til 2/14 and I did not like Rezound as its reception socks where I live. Spectrum reception is much better (equalling Droid X2 for me, but not much development on Droid X2 so I switched).
 
WOW....


Am I the *only* person that didn't know that long pressing on the reboot option brings up a popup about rebooting to safe mode?

...win.
 
Just a bit of an FYI.


If you're getting reboots.... It's VERY important to get your last_kmsg.

Execute the following from either adb or terminal. The bit after > is the file location/name

cat /proc/last_kmsg > /sdcard/kmsg.txt

then provide that.


*edit*

As I typically, like to explain things a little.... Here's what this is doing. Typically any *nix variant (yes android is running a modified linux kernel) outputs a bunch of useful stuff to dmesg. This is just /proc/kmsg... When you reboot, this gets moved to /proc/last_kmsg. Thus, this file contains all sorts of device logs from your last session.

Cat, this just creates files.

When you cat something without a pipe, it prints to screen ie: cat /proc/last_kmsg will just flood your screen.

The > is a pipe. Thats saying to take all the output of cat /whatever, and put it into the file specified after the pipe. IE: "piping' the output of a file into something else.



Hopefully that helps people understand a little about what they're doing.
 
Also the file only exists after a reboot. It won't exist after a clean boot, eg. from power off.
 
tdm said:
Also the file only exists after a reboot. It won't exist after a clean boot, eg. from power off.
Click to expand...

And that is the reason it didn't work! I was just trying to do it to test it. Cool thanks. If I try this ROM again, which I probably will to get you guys a log cat. I will put it up right away! Thanks
 
Brandonson112 said:
I tried it and it just says this "Unknown id: cat"
Click to expand...

Tried what?

Best bet is to reboot first, so the file exists.

Then...

In Terminal:

su
cat /proc/last_kmsg > /sdcard/kmsg.txt

In ADB:
adb root
adb shell cat /proc/last_kmsg > kmsg.txt
(this actually just outputs straight to kmsg.txt in your adb folder on your comp)
 
Well I have been running this ROM since 10 this morning and oddly enough I haven't had one reboot. I did a clean install just like the other times.

But i do have a different issue. I have a app that uses SSL Certificates. When I log on I get a "no peer certificate". If I log on using the browser in there webpage it works fine. It seems to be just this ROM that does it.
 
I can't get the message after reboot
eqaby6yt.jpg
 
You must log in or register to reply here.
Back
Top Bottom