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

Root [rom] pac-man

Got a reboot today on the 5/09 nightly. Looks like the phone felt it was too hot. Though it was only in the 80's today and the phone rebooted while I was sitting inside in the AC.... I'm only including the last 3 or so minutes of the last_kmsg. I doubt you need more than that since it seems fairly obvious why the reboot was called.

[high]
[ 1767.979888]
[ 1767.979888] Trip point triggered by current temperature (50 degrees) measured by Temperature-Sensor 0
[ 1767.982574] android_vibrator_off is stating ...
[ 1767.982604] LGE: vibrator_power_set enable=0
[ 1767.998779] android_vibrator_off is exting ...
[ 1768.112518] QSEECOM: qseecom_release: data->released == false
[ 1768.980010]
[ 1768.980010] Trip point triggered by current temperature (48 degrees) measured by Temperature-Sensor 0
[ 1769.980072]
[ 1769.980072] Trip point triggered by current temperature (48 degrees) measured by Temperature-Sensor 0
[ 1770.368072] mdp4_mixer_blend_setup: Error: no bg_pipe at mixer=0
[ 1770.368103] entering mipi_lgit_lcd_off ..
[ 1770.446380] sensor_common_power_set pwr_mask(3), on(0), sensor(1)
[ 1770.457489] exting mipi_lgit_lcd_off ..
[ 1770.461975] mipi_dsi_panel_power(off): success
[ 1770.487274] request_suspend_state: sleep (0->3) at 1770389961548 (2013-05-10 00:30:07.846578513 UTC)
[ 1770.496246] sensor_common_power_set pwr_mask(2), on(0), sensor(1)
[ 1770.501708] hall_early_suspend:
[ 1770.537414] dhd_set_suspend: force extra Suspend setting
[ 1770.554199] dhd_get_dtim_skip bcn_li_dtim=3 DTIM=1 Listen=10
[ 1770.568817] dtv_pipe is not configured yet
[ 1770.584075] vibrator_enable is stating ...
[ 1770.589965] android_vibrator_off is stating ...
[ 1770.593872] LGE: vibrator_power_set enable=0
[ 1770.598083] android_vibrator_off is exting ...
[ 1770.600311] vibrator_enable is exting ...
[ 1771.343383] dhd_ioctl_entry: ifidx 0, cmd 0x89f1
[ 1771.348266] Unknown PRIVATE command SETSUSPENDMODE 1 - ignored
[ 1771.521514] request_suspend_state: wakeup (3->0) at 1771424202270 (2013-05-10 00:30:08.880819235 UTC)
[ 1771.603118] hall_late_resume:
[ 1771.626708] sensor_common_power_set pwr_mask(2), on(1), sensor(1)
[ 1771.666290] entering mipi_lgit_lcd_on ..
[ 1771.797424] exting mipi_lgit_lcd_on ..
[ 1771.842742] mdp4_overlay_mdp_perf_upd mdp clk is changed [1] from 0 to 85330000
[ 1771.850463] mdp4_overlay_mdp_perf_upd mdp bw is changed [1] from 4 to 2
[ 1772.670227] dhd_ioctl_entry: ifidx 0, cmd 0x89f1
[ 1772.673980] Unknown PRIVATE command SETSUSPENDMODE 0 - ignored
[ 1774.050018] QSEECOM: qseecom_release: data->released == false
[ 1774.985198] send sigkill to 10114 (enmod.lockclock), adj 13, size 7950
[ 1775.213775] send sigkill to 19083 (roid.alarmclock), adj 13, size 6208
[ 1775.587646] mdp4_mixer_blend_setup: Error: no bg_pipe at mixer=0
[ 1775.587677] entering mipi_lgit_lcd_off ..
[ 1775.619415] sensor_common_power_set pwr_mask(3), on(0), sensor(1)
[ 1775.641296] vibrator_enable is stating ...
[ 1775.641387] android_vibrator_off is stating ...
[ 1775.641479] LGE: vibrator_power_set enable=0
[ 1775.641479] android_vibrator_off is exting ...
[ 1775.641510] vibrator_enable is exting ...
[ 1775.651550] dhd_ioctl_entry: ifidx 0, cmd 0x89f1
[ 1775.651611] Unknown PRIVATE command SETSUSPENDMODE 1 - ignored
[ 1775.678161] exting mipi_lgit_lcd_off ..
[ 1775.696105] mipi_dsi_panel_power(off): success
[ 1775.752868] request_suspend_state: sleep (0->3) at 1775655586545 (2013-05-10 00:30:13.112203510 UTC)
[ 1775.761657] sensor_common_power_set pwr_mask(2), on(0), sensor(1)
[ 1775.767242] hall_early_suspend:
[ 1775.797363] dhd_set_suspend: force extra Suspend setting
[ 1775.812133] dhd_get_dtim_skip bcn_li_dtim=3 DTIM=1 Listen=10
[ 1775.820617] dtv_pipe is not configured yet
[ 1779.075988] QSEECOM: qseecom_release: data->released == false
[ 1784.103240] QSEECOM: qseecom_release: data->released == false
[ 1788.128753] QSEECOM: qseecom_release: data->released == false
[ 1793.156738] QSEECOM: qseecom_release: data->released == false
[ 1798.187622] QSEECOM: qseecom_release: data->released == false
[ 1803.215393] QSEECOM: qseecom_release: data->released == false
[ 1807.293426] update_heartbeat: battery temperature is 38 celcius)!.
[ 1807.302062] pm8058_get_battery_temperature_adc: therm_raw is 980
[ 1807.309265] chg_is_battery_too_hot_or_too_cold: BATT TEMP NORMAL (STATE: 3) (thm: 980) (volt: 4018)!.
[ 1807.329925] pm8058_get_battery_temperature_adc: therm_raw is 980
[ 1808.246704] QSEECOM: qseecom_release: data->released == false
[ 1813.276062] QSEECOM: qseecom_release: data->released == false
[ 1818.305236] QSEECOM: qseecom_release: data->released == false
[ 1823.338104] QSEECOM: qseecom_release: data->released == false
[ 1828.370056] QSEECOM: qseecom_release: data->released == false
[ 1833.400970] QSEECOM: qseecom_release: data->released == false
[ 1838.450378] QSEECOM: qseecom_release: data->released == false
[ 1843.477630] QSEECOM: qseecom_release: data->released == false
[ 1848.508514] QSEECOM: qseecom_release: data->released == false
[ 1853.537963] QSEECOM: qseecom_release: data->released == false
[ 1858.571044] QSEECOM: qseecom_release: data->released == false
[ 1863.601898] QSEECOM: qseecom_release: data->released == false
[ 1867.133605] update_heartbeat: battery temperature is 38 celcius)!.
[ 1867.142639] pm8058_get_battery_temperature_adc: therm_raw is 982
[ 1867.152099] chg_is_battery_too_hot_or_too_cold: BATT TEMP NORMAL (STATE: 3) (thm: 982) (volt: 4026)!.
[ 1867.173614] pm8058_get_battery_temperature_adc: therm_raw is 982
[ 1868.621490] QSEECOM: qseecom_release: data->released == false
[ 1873.649230] QSEECOM: qseecom_release: data->released == false
[ 1878.675872] QSEECOM: qseecom_release: data->released == false
[ 1883.703033] QSEECOM: qseecom_release: data->released == false
[ 1888.732543] QSEECOM: qseecom_release: data->released == false
[ 1893.764709] QSEECOM: qseecom_release: data->released == false
[ 1898.792541] QSEECOM: qseecom_release: data->released == false
[ 1903.545013] QSEECOM: qseecom_release: data->released == false
[ 1908.579101] QSEECOM: qseecom_release: data->released == false
[ 1913.606994] QSEECOM: qseecom_release: data->released == false
[ 1918.635345] QSEECOM: qseecom_release: data->released == false
[ 1923.666534] QSEECOM: qseecom_release: data->released == false
[ 1927.293487] update_heartbeat: battery temperature is 38 celcius)!.
[ 1927.302032] pm8058_get_battery_temperature_adc: therm_raw is 984
[ 1927.311889] chg_is_battery_too_hot_or_too_cold: BATT TEMP NORMAL (STATE: 3) (thm: 984) (volt: 4031)!.
[ 1927.333435] pm8058_get_battery_temperature_adc: therm_raw is 984
[ 1928.693939] QSEECOM: qseecom_release: data->released == false
[ 1933.726562] QSEECOM: qseecom_release: data->released == false
[ 1938.752136] QSEECOM: qseecom_release: data->released == false
[ 1943.782409] QSEECOM: qseecom_release: data->released == false
[ 1948.839050] QSEECOM: qseecom_release: data->released == false
[ 1953.630706] sys_reboot: sys_reboot is called from android
[ 1953.635650] sys_reboot: reboot cmd is -1582119980
[ 1953.659027] sdio_alInitiating msm_sdio_al_shutdown...
[ 1953.663513] sdio_al: sdio_al_close_all_channels
[ 1953.668762] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_RMNT
[ 1953.692047] sdio_al:channel_close: Ch SDIO_RMNT closed successfully
[ 1953.699127] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_ULS
[ 1953.707611] sdio_al:channel_close: Ch SDIO_ULS closed successfully
[ 1953.713775] sdio_al: sdio_al_modem_reset_operations
[ 1953.718597] sdio_al: sdio_al_modem_reset_operations: Set the state to MODEM_RESTART for card 1
[ 1953.727569] sdio_al: sdio_al_modem_reset_operations: sdio_release_irq for card 1
[ 1953.742431] sdio_al: sdio_al_modem_reset_operations: Notifying SDIO clients for card 1
[ 1953.758331] sdio_al: channel_close: Invalid device state 2
[ 1953.772460] sdio_al: sdio_al_modem_reset_operations: Finished Notifying SDIO clients for card 1
[ 1953.781585] sdio_al: sdio_al_close_all_channels
[ 1953.785949] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_RPC
[ 1953.796447] sdio_al:channel_close: Ch SDIO_RPC closed successfully
[ 1953.803009] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_QMI
[ 1953.812042] sdio_al:channel_close: Ch SDIO_QMI closed successfully
[ 1953.818389] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_DIAG
[ 1953.826812] sdio_al:channel_close: Ch SDIO_DIAG closed successfully
[ 1953.833129] sdio_al: sdio_al_close_all_channels: Call to sdio_close() for ch SDIO_SMEM
[ 1953.842163] sdio_al:channel_close: Ch SDIO_SMEM closed successfully
[ 1953.848815] sdio_al: sdio_al_modem_reset_operations
[ 1953.867584] sdio_al: sdio_al_modem_reset_operations: Set the state to MODEM_RESTART for card 4
[ 1953.888153] sdio_al: sdio_al_modem_reset_operations: sdio_release_irq for card 4
[ 1953.898864] QSEECOM: qseecom_release: data->released == false
[ 1953.906402] sdio_al: sdio_al_modem_reset_operations: Notifying SDIO clients for card 4
[ 1953.914276] rpcrouter_sdio_remote_remove Called
[ 1953.919494] rpcrouter_sdio_remote_remove Completed
[ 1953.937164] sdio_al: channel_close: Invalid device state 2
[ 1953.943298] sdio_smem_unregister_client: sdio_close error (-19)
[ 1953.956909] sdio_al: sdio_al_modem_reset_operations: Finished Notifying SDIO clients for card 4
[ 1953.970520] sdio_al: msm_sdio_al_shutdown: msm_sdio_al_shutdown complete.
[ 1954.934906] binder: 609:1685 transaction failed 29189, size 220-0
[ 1957.017883] msm8x60_multi_sdio_slot_status_irq: MDM2AP_SYNC Status = 0
[ 1957.024383] msm8x60_multi_sdio_slot_status_irq: calling sdc2_status_notify_cb
[ 1957.031158] msm8x60_multi_sdio_slot_status_irq: calling sdc5_status_notify_cb
[ 1957.059112] Restarting system with command ''.
[ 1957.064331] set_dload_mode : 0
[ 1957.068389] restart time : 2013-05-10 00:33:14.427572164 UTC
[ 1957.076538] Going down for restart now

No errors detected
[/high]

Hope you don't mind me hiding the paste to keep the post somewhat clean while people are scrolling by.
 
How everyone's battery life?just flashed it this morning and fully charged it and it went down to 2% in 5-6 hours of being fully charged.
 
I've found that as long as I stay off WiFi, it's pretty decent.

My biggest problem with battery life is the fact that I don't get a very good Verizon signal at my house.
 
Stackrat said:
I've found that as long as I stay off WiFi, it's pretty decent.

My biggest problem with battery life is the fact that I don't get a very good Verizon signal at my house.
Click to expand...

I don't know if it's an option for you. But you could use something like tasker to toggle your cell radio off when your home. Then toggle it on every so often to get txts and voicemails. Though that sorta defeats the purpose of a phone

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
Though that sorta defeats the purpose of a phone
Click to expand...
Pretty much... :D

To clarify, I get acceptable battery life on 4G (with poor signal), but terrible battery life on WiFi. Though, like IMCarmen, I work from home and can leave it on the charger all day.
 
Stackrat said:
Pretty much... :D

To clarify, I get acceptable battery life on 4G (with poor signal), but terrible battery life on WiFi. Though, like IMCarmen, I work from home and can leave it on the charger all day.
Click to expand...

That makes no sense. Are you running a fairly recent one of the roms? A month or so ago tdm added some filtering into the kernel because it wasn't filtering packets at all. WiFi life improved alot after that fix.

You should never get worse life on Wi-Fi than 4g... that makes pretty much no sense at all.

Sent from my VS920 4G using Tapatalk 2
 
Stackrat said:
Pretty much... :D

To clarify, I get acceptable battery life on 4G (with poor signal), but terrible battery life on WiFi. Though, like IMCarmen, I work from home and can leave it on the charger all day.
Click to expand...

Thread Hi-jack!!!

Working at home FTW! I took all of this past week off and did absolutely nothing but hang out with my chickens and ducks and flash roms on my phone :D

Let the regular thread subject be resumed... :]
 
Yoinx said:
You should never get worse life on Wi-Fi than 4g... that makes pretty much no sense at all.
Click to expand...

This. Unless you have a weak signal and you're constantly trying to connect. Lte is a hog because it uses Lte and cdma and hops towers, and it will is local and more efficient.
 
Looks like basketbuild either crashed or got wiped.

Seems like they're rebuilding indexes as the nightly rolls out.
 
Yoinx said:
That makes no sense. Are you running a fairly recent one of the roms? A month or so ago tdm added some filtering into the kernel because it wasn't filtering packets at all. WiFi life improved alot after that fix.

You should never get worse life on Wi-Fi than 4g... that makes pretty much no sense at all.

Sent from my VS920 4G using Tapatalk 2
Click to expand...
I'm on RC1 now, but was always running Trigger's kernel. I've been running it for a while because the CM10.1 kernel kept getting hung up when switching in and out of WiFi. I just kept going with it.

Tomorrow I'll reflash RC1 and try it's kernel.

PS: I have 3 WAPs in my house. I never have a poor WiFi signal.
 
Stackrat said:
I'm on RC1 now, but was always running Trigger's kernel. I've been running it for a while because the CM10.1 kernel kept getting hung up when switching in and out of WiFi. I just kept going with it.

Tomorrow I'll reflash RC1 and try it's kernel.
Click to expand...

i wish trigger had kept up with development on his kernel because I really liked it and felt it had a lot of potential. Lately I just run the stock kernel on all the roms.

I'm interested in hearing from people about how the latest build is running. Is it lagging? Is it smooth? I downloaded it but have yet to flash it.
 
IMUcarmen said:
i wish trigger had kept up with development on his kernel because I really liked it and felt it had a lot of potential. Lately I just run the stock kernel on all the roms.

I'm interested in hearing from people about how the latest build is running. Is it lagging? Is it smooth? I downloaded it but have yet to flash it.
Click to expand...

You can ask lyfkevin @ XDA to make a spectrum version of his wind kernel. It's got generally positive reviews.

I've been strongly considering doing in kernel mpdecision so maybe I'll get that pushed out soon.
 
tdm said:
You can ask lyfkevin @ XDA to make a spectrum version of his wind kernel. It's got generally positive reviews.

I've been strongly considering doing in kernel mpdecision so maybe I'll get that pushed out soon.
Click to expand...

thanks for the suggestion mr tdm. Could you provide a link to his kernel thread please? either way, thanks!
 
Stackrat said:
I'm on RC1 now, but was always running Trigger's kernel. I've been running it for a while because the CM10.1 kernel kept getting hung up when switching in and out of WiFi. I just kept going with it.

Tomorrow I'll reflash RC1 and try it's kernel.

PS: I have 3 WAPs in my house. I never have a poor WiFi signal.
Click to expand...

Trigger stopped development on that kernel prior to tdm's filtering that he fixed in the kernel. When you're on Wi-Fi with that kernel it doesn't filter any packets.

Tdm could probably explain better. But that's why you're getting bad life on Wi-Fi.

Sent from my VS920 4G using Tapatalk 2
 
IMUcarmen said:
i wish trigger had kept up with development on his kernel because I really liked it and felt it had a lot of potential. Lately I just run the stock kernel on all the roms.

I'm interested in hearing from people about how the latest build is running. Is it lagging? Is it smooth? I downloaded it but have yet to flash it.
Click to expand...

It's running great for me. Notice less lag in the screen turn on lately too. I did trace the stock lock screen to though. I also always flash my tweaks zip when I flash this Rom though.

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
It's running great for me. Notice less lag in the screen turn on lately too. I did trace the stock lock screen to though. I also always flash my tweaks zip when I flash this Rom though.

Sent from my VS920 4G using Tapatalk 2
Click to expand...

I went ahead and flashed the newest version of pacman last night and so far it's running great. I haven't applied any tweaks and it's pretty smooth. It's running much better than it did the first time I tried it that's for sure.
 
Got a reboot today. I can post the last_kmsg if you'd like.

It was another thermal shutdown. Panicked at 39 Celsius ie. 102 Fahrenheit right after I removed the phone from my pocket.

Seems a bit low to panic...

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
Got a reboot today. I can post the last_kmsg if you'd like.

It was another thermal shutdown. Panicked at 39 Celsius ie. 102 Fahrenheit right after I removed the phone from my pocket.

Seems a bit low to panic...

Sent from my VS920 4G using Tapatalk 2
Click to expand...

That seems very low. I am worried about using this phone if it panics at 102
 
You must log in or register to reply here.
Back
Top Bottom