Closed Bug 1235392 Opened 8 years ago Closed 6 years ago

Device not waking up

Categories

(Firefox OS Graveyard :: Gaia::Feedback, defect)

defect
Not set
normal

Tracking

(blocking-b2g:2.6?)

RESOLVED WONTFIX
blocking-b2g 2.6?

People

(Reporter: gerard-majax, Unassigned, NeedInfo)

Details

(Keywords: foxfood, Whiteboard: [bzlite])

Attachments

(6 files)

User-Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

STR:
 - press power

expected: screen turns on

actual: screen turned on only when plugged on USB 

battery OK and device not slow everything seems normal
Attached file dev-log-main.log
Attached file properties.log
Attached image screenshot.png
I don't see this issue using the latest build:

Build ID               20151228092137
Gaia Revision          15a00047c0868cc8f4c8ec4af253b82ac54d70dd
Gaia Date              2015-12-26 05:30:48
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/dfe030978c0fbf525905264f191634820f6ce98b
Gecko Version          46.0a1
Device Name            aries
(In reply to Marcia Knous [:marcia - use ni] from comment #5)
> I don't see this issue using the latest build:
> 
> Build ID               20151228092137
> Gaia Revision          15a00047c0868cc8f4c8ec4af253b82ac54d70dd
> Gaia Date              2015-12-26 05:30:48
> Gecko Revision        
> https://hg.mozilla.org/mozilla-central/rev/
> dfe030978c0fbf525905264f191634820f6ce98b
> Gecko Version          46.0a1
> Device Name            aries

It's the first time it happened to me, but I filed just in case
Kevin, Can you please try to reproduce this bug? Thanks
Keywords: qawanted
Flags: needinfo?(mozillamarcia.knous)
Alexandre: Have you seen this bug recently? Otherwise I think we can close it out as WFM as I haven't been able to reproduce it on any of my devices with the latest Aries builds.
Flags: needinfo?(mozillamarcia.knous) → needinfo?(lissyx+mozillians)
Well, it's something I have only reproduced twice in months (and mostly on december builds, nothing before), but I am not the only one who experienced it sporadically. I'm not very confident in closing as works for me because we have really no idea if it's the case or not.
Flags: needinfo?(lissyx+mozillians)
I've experienced this issue twice with the latest build (The same as Marcia) in less than a Month.

I hope we can get it solved soon, it's really  frustrating to see that your device isn't responding when you have more or less 40% of battery.
Noticed too with build from 20151130 for sure, unsure for other builds.

Most of the time it happens with sleeping screen but happened one time with the screen being on. Every of 4 buttons were not responding.

When it happened with screen turned off, plugging the phone to the computer was turning the screen on and buttons were still not responding.
At least one time I touched the screen in this situation and it "reactivated" the buttons. It looks like I got no useful logs those times, I'll try to gather more logs the next time, but it's a little bit more complicated as you can't use the shake to log with buttons.
For those that are seeing this bug - is it only happening when the battery is 40% or less?
(In reply to Marcia Knous [:marcia - use ni] from comment #12)
> For those that are seeing this bug - is it only happening when the battery
> is 40% or less?

I didn't paid attention to this when it happened, but for sure the battery was not full.

I'll pay more attention the next time this is happening.

But for what Yunito said, I guess it's more because due to the fact that even if your battery is not empty, you can't use your phone anymore in this situation without a computer around: you can't even long press power button to reboot, and Aries can't get its battery removed.
(In reply to Marcia Knous [:marcia - use ni] from comment #12)
> For those that are seeing this bug - is it only happening when the battery
> is 40% or less?

I'm not sure at all, but I think that It happened to me when battery was at 26% in the first case and in the second one it was 40-43%. But as Clément said, it can't be solved until you connect your mobile phone to your computer or to a charger. To sum up, it can't be solved without charging the phone
(In reply to Yunito from comment #14)
> (In reply to Marcia Knous [:marcia - use ni] from comment #12)
> > For those that are seeing this bug - is it only happening when the battery
> > is 40% or less?
> 
> I'm not sure at all, but I think that It happened to me when battery was at
> 26% in the first case and in the second one it was 40-43%. But as Clément
> said, it can't be solved until you connect your mobile phone to your
> computer or to a charger. To sum up, it can't be solved without charging the
> phone


Actually, plugging it in was not changing anything. The combination to plugging in *and* doing something on the screen was.
The first time I didn't noticed this so I had to plug the phone to a computer and run an `adb reboot`
It has just happened now in my Aries. This time I had battery almost full at 80%. It seemed like it was restarting because when it woke up it showed the typical screen with the Firefox OS logo  but It didn't ask me for the PIN of my SIM.

It's really strange
blocking-b2g: --- → 2.6?
Latest update:

Today, a few minutes ago, the device showed the same status as if it was going to shut down and wake up but this time when I charged it into the power supply or into the computer with an USB it doesn't wake up, it stays froozen and when I try to turn it on, it only lights the screen but the screen remains black and then it shut downs. 

Now I have charging it and waiting if it wakes up, I hope so at least, if now I'll have to talk with the fooxfooder responsible to know if I have to send it to Mozilla or I can flash it (Despite the fact it goes against the rules). 

I'll update this as soon as I know something
Flags: needinfo?(marcia)
Latest update:

Today, a few minutes ago, the device showed the same status as if it was going to shut down and wake up but this time when I charged it into the power supply or into the computer with an USB it doesn't wake up, it stays froozen and when I try to turn it on, it only lights the screen but the screen remains black and then it shut downs. 

Now I have charging it and waiting if it wakes up, I hope so at least, if now I'll have to talk with the fooxfooder responsible to know if I have to send it to Mozilla or I can flash it (Despite the fact it goes against the rules). 

I'll update this as soon as I know something
I solved it pressing at the same time (Volume Up + Volume Down + Power) (It forces to shutdown the device). I couldn't do anything until Jullien helped me. 

I think we should have this fixed ASAP.
Flags: needinfo?(marcia)
Yunito, we would need logs please.   Having logs may help; noting what actions happened prior to the issue occurring may also help.  Having these types of information allows the developer to reproduce the issue and see what code is the root cause.  Please also post your gonk information as well.  The build number will suffice.
I spent some time attempting to reproduce this issue with both an Aries and Flame device without luck.  I tried letting the device sleep in a few different ways (After a boot, timeout, pressing the power button) as well as waited different amounts of time after it fell asleep to wake it up.   I also tested this at both low (30-25%) and high (80-75%) battery for the Flame.

As this issue has been reproduced by others I'm removing the qawanted tag.  Although I did not reproduce this issue and we cannot get a regression window for it, I do NOT believe this issue should be closed.

Environmental Variables:
Device: Flame 2.6
BuildID: 20160125030234
Gaia: 4023297b16fdc46de3ddb04be4f3c575313d1cde
Gecko: 67c66c2878aed17ae3096d7db483ddbb2293c503
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 46.0a1 (2.6) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0

Environmental Variables:
Device: Aries 2.6
BuildID: 20160125140104
Gaia: 4023297b16fdc46de3ddb04be4f3c575313d1cde
Gecko: 3f41d7d0f544ebd98273e39bd945c28878a47427
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 46.0a1 (2.6) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #20)
> Yunito, we would need logs please.   Having logs may help; noting what
> actions happened prior to the issue occurring may also help.  Having these
> types of information allows the developer to reproduce the issue and see
> what code is the root cause.  Please also post your gonk information as
> well.  The build number will suffice.

I'll try to get some logs, the problem is that when it happens, the smartphone is not responding and I'm not sure if I will be able to get some logs. The build number is the latest for the Foxfooding: 20151230201227
Flags: needinfo?(yunito)
Thanks Yunito for the continued efforts in trying to get more information.

I need more than the build id, because the build number is an indication of which gonk layer you have.
The build number is different from the build id.  Please provide the build number.  It's in the settings -> device information -> more information.
Flags: needinfo?(yunito)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #23)
> Thanks Yunito for the continued efforts in trying to get more information.
> 
> I need more than the build id, because the build number is an indication of
> which gonk layer you have.
> The build number is different from the build id.  Please provide the build
> number.  It's in the settings -> device information -> more information.

Okay, sorry for that :D

Build Number: eng.worker.20151130.124658
Flags: needinfo?(yunito)
Attached file dev-log-main.log
It happened again to me so this time I pressed volume up and volume down and I got some logs, what do you think?
Flags: needinfo?(nhirata.bugzilla)
[I couldn't attach more files so I copied it]
proc-meminfo.log

:        1804612 kB
MemFree:          517456 kB
Buffers:          113004 kB
Cached:           337772 kB
SwapCached:            0 kB
Active:           454136 kB
Inactive:         315708 kB
Active(anon):     319100 kB
Inactive(anon):     8588 kB
Active(file):     135036 kB
Inactive(file):   307120 kB
Unevictable:           0 kB
Mlocked:               0 kB
HighTotal:       1060864 kB
HighFree:         141216 kB
LowTotal:         743748 kB
LowFree:          376240 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 8 kB
Writeback:             0 kB
AnonPages:        319132 kB
Mapped:            75528 kB
Shmem:              8636 kB
Slab:              36348 kB
SReclaimable:      20400 kB
SUnreclaim:        15948 kB
KernelStack:        4576 kB
PageTables:         4108 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      902304 kB
Committed_AS:     595688 kB
VmallocTotal:     122880 kB
VmallocUsed:        3704 kB
VmallocChunk:      75632 kB
Um, this part is odd to me and might be the reason why it's still blank?

01-29 16:59:41.617   526   526 D qdhwcomposer: hwc_blank: Done unblanking display: 0
01-29 16:59:41.737   526   526 I GeckoDump: AdbController: Failed to get key: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: chrome://b2g/content/shell.js :: checkReloadKey :: line 529"  data: no]

Not sure how to get into that state yet though...
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: