webOS Hardware

[#1]

When I make a phone call and get the phone to my ear instantly (so sensor shuts off the screen) 1 in 8 phone calls my phone would just cut off and shut off. Then I have to hold the power button and switch the mute three times to bring it back to life.

If I make a phone call and let the phone stand in my hand for like 5 seconds before i bring it to my ear it will work just fine.

I also noticed that screen doesn't instantly turns on after I get it away from my ear, sometimes it dimms up really slowly. These occasions are rare but they are still there.

Finally I doctored it (mainly because Skype started to sign me out after 15-20 minutes while on WiFi) and problem is still there.

This problem occured first like few weeks after I got the phone (which is like four months ago) and its been there ever since.

Post relates to: Pre p100ueu (O2)

[#2]

There are many threads out there concerning similar problems. Some of them are while making a call, some while running a particular app. 

I bought a Pre 3 two weeks ago, and after four days I upgraded to 2.2.4 and immediately started seeing random reboots. I cannot pin it down to any particular situation. The reboots happen between once and five or six times a day. Usually, they are when I am not looking at the phone; I just unlock it, and all my cards are gone leaving me with a clean screen.

I've downgraded to 2.2.0, with no improvement.

I've disable calender sync (following that advice in another thread) with no improvement.

I've just installed jsTop, and enabled auto GC, hoping it might just be a memory problem, but it shows me only using 50MB most of the time anyway.

What I have never seen in the discussions is any advice about how to diagnose the problem. If I was on a desktop machine, I'd look in /var/log/ to see if there was anything bad happening just before the reboot, or if a reason came up in the boot log for the last boot. I can't even find out what my phone's uptime is!

If anyone's reading this, could I (we) have some advice on how to get some diagnostic information?

[#3]

> I'd look in /var/log

OK, I've installed Internals, and found the rolled-over messages. Taking a look in them.

[#4]

So, on a clean (full) restart, scheduled using Preset Reset, we have:

paulb@***:~/tmp/downloads$ grep shutdown /media/HP\ PRE3/downloads/messages

2012-02-23T11:35:05.250091Z [6336] webos-device user.notice root: /etc/rc6.d/S10orderly_shutdown: runlevel=6
2012-02-23T11:35:05.289428Z [6336] webos-device user.notice root: /etc/rc6.d/S10orderly_shutdown: com.palm.power service not running
2012-02-23T11:35:05.306549Z [6336] webos-device user.notice root: /etc/rc6.d/S25shutdown_animation starting
2012-02-23T11:35:05.313964Z [6336] webos-device user.notice root: /etc/rc6.d/S25shutdown_animation stopping LunaSysMgr
2012-02-23T11:35:05.578460Z [6337] webos-device user.notice root: /etc/rc6.d/S25shutdown_animation done stopping LunaSysMgr
2012-02-23T11:35:06.658935Z [6338] webos-device user.notice root: /etc/rc6.d/S25shutdown_animation done

and then:

2012-02-23T11:35:20.775726Z [21] webos-device kern.notice kernel: pmklogd started
2012-02-23T11:35:21.102905Z [21] webos-device kern.info kernel: [131075.591644] kjournald starting. Commit interval 5 seconds
2012-02-23T11:35:21.104248Z [21] webos-device kern.info kernel: [131076.428771] kjournald starting. Commit interval 5 seconds
2012-02-23T11:35:21.104705Z [21] webos-device kern.info kernel: [131081.554138] kjournald starting. Commit interval 5 seconds
2012-02-23T11:35:21.108825Z [21] webos-device kern.info kernel: [131091.071319] kjournald starting. Commit interval 5 seconds
2012-02-23T11:35:21.133178Z [21] webos-device kern.info kernel: [131092.381317] rockhopper: start re-registering driver
2012-02-23T11:35:21.177276Z [21] webos-device kern.warning kernel: [131093.789062] bootmark (starting): 28EE99C289D846B1E3448F297D7DD73B
2012-02-23T11:35:21.507415Z [22] webos-device kern.info kernel: [131094.121093] kjournald starting. Commit interval 5 seconds
2012-02-23T11:35:21.537445Z [22] webos-device kern.info kernel: [131094.147247] kjournald starting. Commit interval 5 seconds
2012-02-23T11:35:22.130584Z [22] webos-device daemon.warning upstart: (00022/753571891) tempdb main process (1171) terminated with status 2
2012-02-23T11:35:22.171844Z [22] webos-device user.notice root: org.webosinternals.ipkgservice upstart: script called
2012-02-23T11:35:23.017211Z [23] webos-device user.debug logctld: main: About to start main_loop
2012-02-23T11:35:27.189941Z [27] webos-device user.notice powerd: {powerd}: Powerd started on palm-rib.
2012-02-23T11:35:27.190948Z [27] webos-device user.info powerd: {powerd}: CHG_LOGIC: debug_battery_taper (charging, type=0, 1195.000000mAh, 100%, 32C, 0mA, 4177mV, (avg)0mA, min=40mA, max=4141mV, taper_state=start, battery_state=charge-termination, battery-authentic charger-connected)
2012-02-23T11:35:28.237121Z [28] webos-device user.notice mojodb-luna[1188]: [core.app] mojodb starting...
2012-02-23T11:35:28.868743Z [29] webos-device user.notice SmartKeyService: start: started service com.palm.smartKey
2012-02-23T11:35:28.869079Z [29] webos-device user.notice SmartKeyService: main: started service com.palm.smartKey
2012-02-23T11:35:30.355560Z [30] webos-device user.emerg hidd: HidInit: Touchpanel Reader Thread started
2012-02-23T11:35:31.636779Z [32] webos-device user.warning LunaSysService: SystemRestore::startupConsistencyCheck() started
2012-02-23T11:35:31.636871Z [32] webos-device user.warning LunaSysService: SystemRestore::startupConsistencyCheck() running - checking wallpaper and ringtone consistency
2012-02-23T11:35:31.642883Z [32] webos-device user.warning LunaSysService: SystemRestore::startupConsistencyCheck() running - restoring volume icon file
2012-02-23T11:35:31.651489Z [32] webos-device user.warning LunaSysService: SystemRestore::startupConsistencyCheck() finished
2012-02-23T11:35:33.674377Z [34] webos-device user.notice BrowserServer: startService: BrowserServer started on service bus
2012-02-23T11:35:36.214630Z [36] webos-device user.notice mojodb-luna[1188]: [core.app] mojodb started
2012-02-23T11:35:39.040100Z [39] webos-device daemon.warning upstart: (00039/663331410) dnsmasq main process (1454) killed by TERM signal
2012-02-23T11:35:39.071868Z [39] webos-device user.crit PmNetConfigManager: {netcfg.mgr}: startARequestCycle: dnsmasq not up
2012-02-23T11:35:39.091461Z [39] webos-device user.notice BrowserServer: IP address changed: 192.168.1.203. Restarting network
2012-02-23T11:35:39.116577Z [39] webos-device user.crit PmNetConfigManager: {netcfg.mgr}: startARequestCycle: dnsmasq not up
2012-02-23T11:35:39.160095Z [39] webos-device user.crit PmNetConfigManager: {netcfg.mgr}: startARequestCycle: dnsmasq not up
2012-02-23T11:35:40.907012Z [41] webos-device user.notice root: CustomizationService upstart: customization launch prereq not met
2012-02-23T11:35:48.570617Z [49] webos-device kern.warning kernel: [131120.936187] (&mm->mmap_sem){++++++}, at: [<80484e00>] kgsl_get_vma_from_start_addr+0x24/0x150
2012-02-23T11:35:48.578826Z [49] webos-device kern.warning kernel: [131121.024414] [<80484e00>] kgsl_get_vma_from_start_addr+0x24/0x150
2012-02-23T11:35:48.583770Z [49] webos-device kern.warning kernel: [131121.118682] [<806db774>] (down_read+0x48/0x5c) from [<80484e00>] (kgsl_get_vma_from_start_addr+0x24/0x150)
2012-02-23T11:35:48.584045Z [49] webos-device kern.warning kernel: [131121.128417] [<80484e00>] (kgsl_get_vma_from_start_addr+0x24/0x150) from [<8048615c>] (kgsl_ioctl+0x85c/0x15d0)

I'm not sure what all that means, or what the marks of a good, planned restart are, but it's a place to begin. Now all I have to do is wait for an unscheduled restart. Hmm, maybe I ought to trigger a luna restart, and see what that looks like in messages, as I don't know whether the unplanned stuff is a full or luna restart.

[#5]

---

PaulBland wrote:

I'm not sure what all that means, or what the marks of a good, planned restart are, but it's a place to begin. Now all I have to do is wait for an unscheduled restart. Hmm, maybe I ought to trigger a luna restart, and see what that looks like in messages, as I don't know whether the unplanned stuff is a full or luna restart.

---

I don't know how to help you on this issue, but I can tell you that a Luna restart is very fast compared to a full phone restart.  A Luna restart could be from 10-30 seconds.