Mixing
![Is it a problem not to have the Relieving Letter from an earlier employer? [duplicate]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjbpfN9tAutmK93bJRC3ZoROZzi2TJDms5n8_qJuhgE0a9b52OOHayv3NGT8igAdFL7byXNst-_1DZK5SjrIJ28_6RQPUpBROqMs5s6jo-ZsjX8kjDwfxJufIitH3TaQRXWaGSQKRQib-f/s72-c/1.jpg)
MacBook: woke up to an empty battery, how to get battery history?
Clash Royale CLAN TAG#URR8PPP
up vote
5
down vote
favorite
On Sunday I purchased a brand new MacBook Pro 13" w/TouchBar. I used it a little last night and put it in my backpack with 75% battery life. I shut the lid and assumed the MacBook was sleeping when I put it in my backpack. Unfortunately when I got to school this morning the battery was completely dead. Since I wonder what happened to the 75% battery I had left and am very concerned damage from overheating might happen with it running in a backpack. I checked Console / sys logs and nothing jumps out.
Is there anyway to see the historical battery life to find out if the laptop was left on overnight?
macbook battery sleep-wake
edited yesterday
bmike♦
149k45265584
asked yesterday
AAA
16818
add a comment |Â
up vote
5
down vote
favorite
On Sunday I purchased a brand new MacBook Pro 13" w/TouchBar. I used it a little last night and put it in my backpack with 75% battery life. I shut the lid and assumed the MacBook was sleeping when I put it in my backpack. Unfortunately when I got to school this morning the battery was completely dead. Since I wonder what happened to the 75% battery I had left and am very concerned damage from overheating might happen with it running in a backpack. I checked Console / sys logs and nothing jumps out.
Is there anyway to see the historical battery life to find out if the laptop was left on overnight?
macbook battery sleep-wake
edited yesterday
bmike♦
149k45265584
asked yesterday
AAA
16818
add a comment |Â
up vote
5
down vote
favorite
up vote
5
down vote
favorite
On Sunday I purchased a brand new MacBook Pro 13" w/TouchBar. I used it a little last night and put it in my backpack with 75% battery life. I shut the lid and assumed the MacBook was sleeping when I put it in my backpack. Unfortunately when I got to school this morning the battery was completely dead. Since I wonder what happened to the 75% battery I had left and am very concerned damage from overheating might happen with it running in a backpack. I checked Console / sys logs and nothing jumps out.
Is there anyway to see the historical battery life to find out if the laptop was left on overnight?
macbook battery sleep-wake
edited yesterday
bmike♦
149k45265584
asked yesterday
AAA
16818
On Sunday I purchased a brand new MacBook Pro 13" w/TouchBar. I used it a little last night and put it in my backpack with 75% battery life. I shut the lid and assumed the MacBook was sleeping when I put it in my backpack. Unfortunately when I got to school this morning the battery was completely dead. Since I wonder what happened to the 75% battery I had left and am very concerned damage from overheating might happen with it running in a backpack. I checked Console / sys logs and nothing jumps out.
Is there anyway to see the historical battery life to find out if the laptop was left on overnight?
macbook battery sleep-wake
macbook battery sleep-wake
edited yesterday
bmike♦
149k45265584
asked yesterday
AAA
16818
edited yesterday
bmike♦
149k45265584
asked yesterday
AAA
16818
edited yesterday
bmike♦
149k45265584
edited yesterday
bmike♦
149k45265584
edited yesterday
bmike♦
149k45265584
149k45265584
asked yesterday
AAA
16818
asked yesterday
AAA
16818
asked yesterday
AAA
16818
16818
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
5
down vote
Open activity monitor and select energy. It might take a while to crunch the logs, but that should show you some recent history for 12 hours of activity.
I think it offered more time in the past if you were sleeping, but now it seems to only show you a 12 hour clock window.
The command line tool pmset -g log should dump a much more detailed and verbose log of history going back further than 12 hours. You will probably want to process that - perhaps printing only the lines that match the string Charge and then paging the results.
pmset -g log | grep -w Charge | more
pmset -g log | grep -w Summary- | more
Once you see if it slept and how the charge went down, I wouldn't worry about it running hot while closed. I run Mac at high CPU/GPU while closed clamshell all the time (most of the day) and have never had any issues with longevity in practice or overheating - the CPU throttles down when the blowers or heat can't escape due to a blockage or insulation to stay within safe temperature ranges.
answered yesterday
bmike♦
149k45265584
It looks like that only goes back 12 hours, we are now 12-24 hours...
– AAA
yesterday
@aaa Yes indeed - you can get more from the command line. See my edit above. You can also use the thermlog to check running thermal conditions, but that is ongoing and not something you can look backwards at AFAIK.
– bmike♦
yesterday
Thank you! That shows that my MacBook was awake all the way up until 5am... not cool! Now to find out what it was doing
– AAA
yesterday
@AAA want to know what was it doing in the middle of the night. Open Console in Utility and scroll back the system log to the time stamp of interest
– Buscar웃
yesterday
Thank you - not a whole lot happening. Mostly lines like this: systemstats[53]: assertion failed: XYZ: systemstats + XYZ
– AAA
yesterday
 |Â
show 3 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
Open activity monitor and select energy. It might take a while to crunch the logs, but that should show you some recent history for 12 hours of activity.
I think it offered more time in the past if you were sleeping, but now it seems to only show you a 12 hour clock window.
The command line tool pmset -g log should dump a much more detailed and verbose log of history going back further than 12 hours. You will probably want to process that - perhaps printing only the lines that match the string Charge and then paging the results.
pmset -g log | grep -w Charge | more
pmset -g log | grep -w Summary- | more
Once you see if it slept and how the charge went down, I wouldn't worry about it running hot while closed. I run Mac at high CPU/GPU while closed clamshell all the time (most of the day) and have never had any issues with longevity in practice or overheating - the CPU throttles down when the blowers or heat can't escape due to a blockage or insulation to stay within safe temperature ranges.
answered yesterday
bmike♦
149k45265584
It looks like that only goes back 12 hours, we are now 12-24 hours...
– AAA
yesterday
@aaa Yes indeed - you can get more from the command line. See my edit above. You can also use the thermlog to check running thermal conditions, but that is ongoing and not something you can look backwards at AFAIK.
– bmike♦
yesterday
Thank you! That shows that my MacBook was awake all the way up until 5am... not cool! Now to find out what it was doing
– AAA
yesterday
@AAA want to know what was it doing in the middle of the night. Open Console in Utility and scroll back the system log to the time stamp of interest
– Buscar웃
yesterday
Thank you - not a whole lot happening. Mostly lines like this: systemstats[53]: assertion failed: XYZ: systemstats + XYZ
– AAA
yesterday
 |Â
show 3 more comments
up vote
5
down vote
Open activity monitor and select energy. It might take a while to crunch the logs, but that should show you some recent history for 12 hours of activity.
I think it offered more time in the past if you were sleeping, but now it seems to only show you a 12 hour clock window.
The command line tool pmset -g log should dump a much more detailed and verbose log of history going back further than 12 hours. You will probably want to process that - perhaps printing only the lines that match the string Charge and then paging the results.
pmset -g log | grep -w Charge | more
pmset -g log | grep -w Summary- | more
Once you see if it slept and how the charge went down, I wouldn't worry about it running hot while closed. I run Mac at high CPU/GPU while closed clamshell all the time (most of the day) and have never had any issues with longevity in practice or overheating - the CPU throttles down when the blowers or heat can't escape due to a blockage or insulation to stay within safe temperature ranges.
answered yesterday
bmike♦
149k45265584
It looks like that only goes back 12 hours, we are now 12-24 hours...
– AAA
yesterday
@aaa Yes indeed - you can get more from the command line. See my edit above. You can also use the thermlog to check running thermal conditions, but that is ongoing and not something you can look backwards at AFAIK.
– bmike♦
yesterday
Thank you! That shows that my MacBook was awake all the way up until 5am... not cool! Now to find out what it was doing
– AAA
yesterday
@AAA want to know what was it doing in the middle of the night. Open Console in Utility and scroll back the system log to the time stamp of interest
– Buscar웃
yesterday
Thank you - not a whole lot happening. Mostly lines like this: systemstats[53]: assertion failed: XYZ: systemstats + XYZ
– AAA
yesterday
 |Â
show 3 more comments
up vote
5
down vote
up vote
5
down vote
Open activity monitor and select energy. It might take a while to crunch the logs, but that should show you some recent history for 12 hours of activity.
I think it offered more time in the past if you were sleeping, but now it seems to only show you a 12 hour clock window.
The command line tool pmset -g log should dump a much more detailed and verbose log of history going back further than 12 hours. You will probably want to process that - perhaps printing only the lines that match the string Charge and then paging the results.
pmset -g log | grep -w Charge | more
pmset -g log | grep -w Summary- | more
Once you see if it slept and how the charge went down, I wouldn't worry about it running hot while closed. I run Mac at high CPU/GPU while closed clamshell all the time (most of the day) and have never had any issues with longevity in practice or overheating - the CPU throttles down when the blowers or heat can't escape due to a blockage or insulation to stay within safe temperature ranges.
answered yesterday
bmike♦
149k45265584
Open activity monitor and select energy. It might take a while to crunch the logs, but that should show you some recent history for 12 hours of activity.
I think it offered more time in the past if you were sleeping, but now it seems to only show you a 12 hour clock window.
The command line tool pmset -g log should dump a much more detailed and verbose log of history going back further than 12 hours. You will probably want to process that - perhaps printing only the lines that match the string Charge and then paging the results.
pmset -g log | grep -w Charge | more
pmset -g log | grep -w Summary- | more
Once you see if it slept and how the charge went down, I wouldn't worry about it running hot while closed. I run Mac at high CPU/GPU while closed clamshell all the time (most of the day) and have never had any issues with longevity in practice or overheating - the CPU throttles down when the blowers or heat can't escape due to a blockage or insulation to stay within safe temperature ranges.
answered yesterday
bmike♦
149k45265584
edited yesterday
answered yesterday
bmike♦
149k45265584
answered yesterday
bmike♦
149k45265584
answered yesterday
bmike♦
149k45265584
149k45265584
It looks like that only goes back 12 hours, we are now 12-24 hours...
– AAA
yesterday
@aaa Yes indeed - you can get more from the command line. See my edit above. You can also use the thermlog to check running thermal conditions, but that is ongoing and not something you can look backwards at AFAIK.
– bmike♦
yesterday
Thank you! That shows that my MacBook was awake all the way up until 5am... not cool! Now to find out what it was doing
– AAA
yesterday
@AAA want to know what was it doing in the middle of the night. Open Console in Utility and scroll back the system log to the time stamp of interest
– Buscar웃
yesterday
Thank you - not a whole lot happening. Mostly lines like this: systemstats[53]: assertion failed: XYZ: systemstats + XYZ
– AAA
yesterday
 |Â
show 3 more comments
It looks like that only goes back 12 hours, we are now 12-24 hours...
– AAA
yesterday
@aaa Yes indeed - you can get more from the command line. See my edit above. You can also use the thermlog to check running thermal conditions, but that is ongoing and not something you can look backwards at AFAIK.
– bmike♦
yesterday
Thank you! That shows that my MacBook was awake all the way up until 5am... not cool! Now to find out what it was doing
– AAA
yesterday
@AAA want to know what was it doing in the middle of the night. Open Console in Utility and scroll back the system log to the time stamp of interest
– Buscar웃
yesterday
Thank you - not a whole lot happening. Mostly lines like this: systemstats[53]: assertion failed: XYZ: systemstats + XYZ
– AAA
yesterday
It looks like that only goes back 12 hours, we are now 12-24 hours...
– AAA
yesterday
It looks like that only goes back 12 hours, we are now 12-24 hours...
– AAA
yesterday
@aaa Yes indeed - you can get more from the command line. See my edit above. You can also use the thermlog to check running thermal conditions, but that is ongoing and not something you can look backwards at AFAIK.
– bmike♦
yesterday
@aaa Yes indeed - you can get more from the command line. See my edit above. You can also use the thermlog to check running thermal conditions, but that is ongoing and not something you can look backwards at AFAIK.
– bmike♦
yesterday
Thank you! That shows that my MacBook was awake all the way up until 5am... not cool! Now to find out what it was doing
– AAA
yesterday
Thank you! That shows that my MacBook was awake all the way up until 5am... not cool! Now to find out what it was doing
– AAA
yesterday
@AAA want to know what was it doing in the middle of the night. Open Console in Utility and scroll back the system log to the time stamp of interest
– Buscar웃
yesterday
@AAA want to know what was it doing in the middle of the night. Open Console in Utility and scroll back the system log to the time stamp of interest
– Buscar웃
yesterday
Thank you - not a whole lot happening. Mostly lines like this: systemstats[53]: assertion failed: XYZ: systemstats + XYZ
– AAA
yesterday
Thank you - not a whole lot happening. Mostly lines like this: systemstats[53]: assertion failed: XYZ: systemstats + XYZ
– AAA
yesterday
 |Â
show 3 more comments
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f336218%2fmacbook-woke-up-to-an-empty-battery-how-to-get-battery-history%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
