Author Topic: Problem of random reboot and SD card !  (Read 22163 times)

Offline EowynCarter

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 226
  • Karma: 5
    • View Profile
Re: Problem of random reboot and SD card !
« Reply #75 on: May 12, 2011, 08:47:57 AM »
Well, the SD unmounted and re-mounted. Followed by a re-boot.

Offline danbhala

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 5
  • Karma: 0
    • View Profile
Re: Problem of random reboot and SD card !
« Reply #76 on: May 24, 2011, 01:45:16 AM »
New reboot problem:

 >:(

The past two nights I used my Zero's alarm to get me up in the morning for work.

The phone rebooted both times when I hit snooze. Snooze time is for more sleep in the mornings and not having to babysit the phone, enter pin again, check alarm if its still on etc...

Very frustrating, has anyone had the reboot problem when hitting snooze?

Offline maruno

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 20
  • Karma: 1
    • View Profile
Re: Problem of random reboot and SD card !
« Reply #77 on: May 24, 2011, 03:16:29 AM »
New reboot problem:

 >:(

The past two nights I used my Zero's alarm to get me up in the morning for work.

The phone rebooted both times when I hit snooze. Snooze time is for more sleep in the mornings and not having to babysit the phone, enter pin again, check alarm if its still on etc...

Very frustrating, has anyone had the reboot problem when hitting snooze?

I have the very same thing with the stock alarm clock-app in CM7.

mmo_gpf

  • Guest
Re: Problem of random reboot and SD card !
« Reply #78 on: May 24, 2011, 03:25:03 AM »
New reboot problem:

 >:(

The past two nights I used my Zero's alarm to get me up in the morning for work.

The phone rebooted both times when I hit snooze. Snooze time is for more sleep in the mornings and not having to babysit the phone, enter pin again, check alarm if its still on etc...

Very frustrating, has anyone had the reboot problem when hitting snooze?

I have the very same thing with the stock alarm clock-app in CM7.

I'm going to test it right now...
If it fails, I will open a new issue

Regards

mmo_gpf

  • Guest
Re: Problem of random reboot and SD card !
« Reply #79 on: May 24, 2011, 03:33:17 AM »
The alarm has worked fine for me.
It was set to 12:26.
It worked
I hited snooze, and then ZERO said that alarm will sound in ten minutes.
You can see the task bar after I hited snooze with the notification that alarm is still running.

Besides this, here is the log with the alarm working fine without reboot.

05-24 12:26:00.049: WARN/BackupManagerService(173): dataChanged but no participant pkg='com.android.providers.settings' uid=10021
05-24 12:26:00.059: VERBOSE/AlarmClock(2044): Recevied alarm set for 12:26:00.000 p.m.
05-24 12:26:00.069: INFO/AlarmClock(2044): Empty or null intent!
05-24 12:26:00.089: DEBUG/StatusBarService(246): Notification has fullScreenIntent; sending fullScreenIntent
05-24 12:26:00.089: INFO/ActivityManager(173): Starting: Intent { cmp=com.android.deskclock/.AlarmAlert (has extras) } from pid -1
05-24 12:26:00.089: WARN/ActivityManager(173): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x800000 cmp=com.android.deskclock/.AlarmAlert (has extras) }
05-24 12:26:00.099: VERBOSE/NotificationService(173): Active profile: MMO
05-24 12:26:00.099: INFO/PROFILE(173): Group: Gmail containing : com.android.deskclock : false
05-24 12:26:00.099: INFO/PROFILE(173): Group: Phone containing : com.android.deskclock : false
05-24 12:26:00.099: INFO/PROFILE(173): Group: Calendar containing : com.android.deskclock : false
05-24 12:26:00.099: INFO/PROFILE(173): Group: Email containing : com.android.deskclock : false
05-24 12:26:00.099: INFO/PROFILE(173): Group: SMS containing : com.android.deskclock : false
05-24 12:26:00.099: VERBOSE/ProfileManager(173): No active group, returning default: Otro
05-24 12:26:00.099: VERBOSE/NotificationService(173): Pkg: com.android.deskclock group: Otro
05-24 12:26:00.129: DEBUG/szipinf(246): Initializing inflate state
05-24 12:26:00.169: WARN/asset(246): deep redirect failure from 0x01030068 => 0x0a060003, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x00000000
05-24 12:26:00.199: WARN/asset(246): deep redirect failure from 0x01030067 => 0x0a060002, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x00000000
05-24 12:26:00.199: WARN/asset(246): deep redirect failure from 0x01030067 => 0x0a060002, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x00000000
05-24 12:26:00.239: VERBOSE/AUDMSM(116): open driver
05-24 12:26:00.239: VERBOSE/AUDMSM(116): get config
05-24 12:26:00.239: VERBOSE/AUDMSM(116): set config
05-24 12:26:00.239: VERBOSE/AUDMSM(116): buffer_size: 4800
05-24 12:26:00.239: VERBOSE/AUDMSM(116): buffer_count: 2
05-24 12:26:00.239: VERBOSE/AUDMSM(116): channel_count: 2
05-24 12:26:00.239: VERBOSE/AUDMSM(116): sample_rate: 44100
05-24 12:26:00.399: WARN/AudioFlinger(116): write blocked for 166 msecs, 28 delayed writes, thread 0xcc60
05-24 12:26:00.769: INFO/ActivityManager(173): Displayed com.android.deskclock/.AlarmAlert: +652ms
05-24 12:26:05.329: WARN/BackupManagerService(173): dataChanged but no participant pkg='com.android.providers.settings' uid=10021
05-24 12:26:05.369: VERBOSE/NotificationService(173): Active profile: MMO
05-24 12:26:05.369: INFO/PROFILE(173): Group: Gmail containing : com.android.deskclock : false
05-24 12:26:05.369: INFO/PROFILE(173): Group: Phone containing : com.android.deskclock : false
05-24 12:26:05.369: INFO/PROFILE(173): Group: Calendar containing : com.android.deskclock : false
05-24 12:26:05.369: INFO/PROFILE(173): Group: Email containing : com.android.deskclock : false
05-24 12:26:05.369: INFO/PROFILE(173): Group: SMS containing : com.android.deskclock : false
05-24 12:26:05.369: VERBOSE/ProfileManager(173): No active group, returning default: Otro
05-24 12:26:05.369: VERBOSE/NotificationService(173): Pkg: com.android.deskclock group: Otro
05-24 12:26:05.369: VERBOSE/AlarmClock(2044): La alarma volverá a sonar en 10 minutos.


I think you probably have another different issue: alarm sound stored in SD card...? Mine is a tone from rom stored in rom memory.

Kind regards

mmo_gpf

  • Guest
Re: Problem of random reboot and SD card !
« Reply #80 on: May 24, 2011, 03:40:54 AM »
And 10 minutes later, It worked fine again.

05-24 12:36:05.279: INFO/ActivityManager(173): Start proc com.android.deskclock for broadcast com.android.deskclock/.AlarmReceiver: pid=2181 uid=10021 gids={}

No reboots.

Regards

Offline marantz

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 41
  • Karma: -3
    • View Profile
Re: Problem of random reboot and SD card !
« Reply #81 on: June 09, 2011, 01:21:54 AM »
The latest CM nightly builds are based upon a new codebase (Gingerbread 2.3.4), so it may behave differently even from latest CM7.0.3 (still based i guess on 2.3.3).

In my humble opinion, latest builds are much more stable for SD mounting, in one week of use i had only one SD card dismount-remount.  Maybe is not fixed completely, but acceptable for normal use. Give it a try.

Offline lechip

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 11
  • Karma: 0
    • View Profile
Re: Problem of random reboot and SD card !
« Reply #82 on: June 20, 2011, 02:47:02 AM »
Any particular Nightly you guys recommend?

Offline silverius

  • Sr. Member
  • ****
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 293
  • Karma: 0
    • View Profile
« Last Edit: June 20, 2011, 03:21:57 AM by silverius »
GP1 rulando SuperAOSP 8.6

Offline Sabinalu

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 5
  • Karma: 0
    • View Profile
Problem of random reboot and SD card
« Reply #84 on: July 07, 2015, 09:13:41 AM »
I record 247 and never reboot. On UPS backup.

Can't say I've tried a reboot with recording on.

This wont solve power problems, but Have you tried stopping the recording for reboot?