Tryintg to figure out how to add tables to posts.
So|Exactly|How
does|this|new
fangled | thing | work
and |just |what
is | it | good |
for | |
Ok, so the patch for tables is not installed.
Fail.
Not a fail to make the attempt, I have tried this myself as I would like to be able to make columns in posts too. I guess there must be some reason the admins haven't put the patch on, although they might look into it if asked. This thread should be in the About xda-developers.com forum to get their notice, or asked in this thread. (requests) From the Users to the Mods & Admins
Yes, the only option I've found so far is using preformatted text, and wrapping it in code tags. That gives an ugly font, etc. Even then you have to take into account the font. The editing box has a proportional font, and the display is fixed width. The third column shows what can happen.
Code:
So Exactly How
does this new
fangled thing work
and just what
is it good
for
sysadmn said:
Yes, the only option I've found so far is using preformatted text, and wrapping it in code tags. That gives an ugly font, etc. Even then you have to take into account the font. The editing box has a proportional font, and the display is fixed width. The third column shows what can happen.
Code:
So Exactly How
does this new
fangled thing work
and just what
is it good
for
Click to expand...
Click to collapse
Another way to do it is using a smart trick from Lesicnik1:
A1[COLOR="White"]---------------------[/COLOR][COLOR="Red"]A2[/COLOR][COLOR="White"]---------------------[/COLOR]A3
B1[COLOR="White"]---------------------[/COLOR][COLOR="Red"]B2[/COLOR][COLOR="White"]---------------------[/COLOR]B3
C1[COLOR="White"] --------------------[/COLOR][COLOR="Red"]C2[/COLOR][COLOR="White"]---------------------[/COLOR]C3
A1---------------------A2---------------------A3
B1---------------------B2---------------------B3
C1 --------------------C2---------------------C3
Hello,
I recently purchased the XZ2 and overall I am happy with it however the battery life isn't great and it seems the problem is that the phone doesn't go often into deep sleep. I am looking at the battery info by the phone as well as the app called accu battery. Attached are a few screen shots
Overnight the phone was in deep sleep for only 1 hr despite having wifi and blue tooth turned off. Also as you can see from the graph, the battery only slows down discharging when I turn the phone to airplane mode and the graph starts to flatten.
And what is RCS ?
I think the battery is good when the phone is being used but something is happening when the phone is not!
Can anyone shed a light on this ?
Thanks
thatu said:
Hello,
I recently purchased the XZ2 and overall I am happy with it however the battery life isn't great and it seems the problem is that the phone doesn't go often into deep sleep. I am looking at the battery info by the phone as well as the app called accu battery. Attached are a few screen shots
Overnight the phone was in deep sleep for only 1 hr despite having wifi and blue tooth turned off. Also as you can see from the graph, the battery only slows down discharging when I turn the phone to airplane mode and the graph starts to flatten.
And what is RCS ?
I think the battery is good when the phone is being used but something is happening when the phone is not!
Can anyone shed a light on this ?
Thanks
Click to expand...
Click to collapse
RCS is rich communication services where it promotes better carrier messaging for everyone from Google.
Thanks,
Do you think the battery usage on my phone is normal ? On my Z5 the phone goes to deep sleep very quickly, the XZ2, it doesn't.
thatu said:
Thanks,
Do you think the battery usage on my phone is normal ? On my Z5 the phone goes to deep sleep very quickly, the XZ2, it doesn't.
Click to expand...
Click to collapse
I dont know but your rcs really that high mine only got to 3% and doesnt even constantly shows up. Maybe somehow related to your carrier perhaps.
nolihowell said:
I dont know but your rcs really that high mine only got to 3% and doesnt even constantly shows up. Maybe somehow related to your carrier perhaps.
Click to expand...
Click to collapse
Thanks
It is interesting cause when I switch on airplane mode the graph almost flattens. I will try to stop RCS and see if it changes anything
After a Full Charge and a normal Usage +over night standby connect the phone via USB cable, activate Debug Mode and ADB, then do a "ADB Bugreport"
The .zip file which will be created can be uploaded to https://bathist.ef.lc/
This will show you how much Doze, Deepsleep and whatever your phone has. Way more accurate than ANY other app.
Like this:
Duration / Realtime: 36h11m52.024s
Code:
Aggregated Checkin Stats:
Metric | Value
Screen Off Discharge Rate (%/hr) | 0.66 (Discharged: 22%)
Screen On Discharge Rate (%/hr) | 13.01 (Discharged: 36%)
Screen On Time | 2h45m59.535s
Screen Off Uptime | 1h7m16.273s
Userspace Wakelock Time | 23m44.667s
Sync Activity | 2m12.654s (89 times)
JobScheduler Activity | 7m32.307s (527 times)
App Wakeup Alarms | 661 times
CPU Usage | 2h20m29.119s user time, 1h50m49.538s system time
Kernel Overhead Time | 43m31.606s
Kernel Wakelocks | 40m48.298s (1.283107e+06 times)
Wakeup Reasons | 30m15.526s (3565 times)
Mobile KBs/hr | 13326.44
WiFi KBs/hr | 16984.52
Total WiFi Scan Activity | 2m10.686s (106 times)
Total WiFi Full Lock Activity | 30.917s
Mobile Active Time | 3h3m15.876s
Signal Scanning Time | 1m19.575s
Full Wakelock Time | 9m1.827s
Interactive Time | 2h45m5.054s
Phone Call Time | 0
Device Idle Mode Enabled Time | 17h23m13.272s
Device Idling Time | 17h25m44.636s
Total GPS Use | 10m28.636s (15 times)
Wifi Power Usage | 0.00%/hr, 0.00% total
Wifi Transfer Time | 3m55.544s
Wifi Idle Time | 10m10.627s
Bluetooth Power Usage | 0.00%/hr, 0.00% total
Bluetooth Transfer Time | 0
Bluetooth Idle Time | 0
Camera Use | 4m1.165s (19 times)
Flashlight Time | 0 (0 times)
Modem Transfer Time | 6h22m3.379s
Modem Idle Time | 1h0m15.345s
Device's Power Estimates:
Ranking | Name | Uid | Battery Percentage Consumed
0 | OVERCOUNTED | 0 | 0.08%
1 | SCREEN | 0 | 15.59%
2 | com.kiwibrowser.browser | 10235 | 12.58%
3 | IDLE | 0 | 8.92%
4 | CELL | 0 | 5.69%
5 | ROOT | 0 | 2.83%
6 | ANDROID_SYSTEM | 1000 | 1.92%
7 | WIFI | 0 | 1.83%
8 | com.whatsapp | 10191 | 1.68%
9 | GOOGLE_SERVICES | 10046 | 1.63%
Userspace Wakelocks:
Ranking | Name | Uid | Duration / Hr | Count / Hr | Total Duration | Total Count
0 | ANDROID_SYSTEM : deviceidle_maint | 1000 | 9s609ms | 1.52 | 6m42.987s | 55
1 | RADIO : RILJ_ACK_WL | 1001 | 5s417ms | 28.51 | 3m46.287s | 1032
2 | ANDROID_SYSTEM : ConnectivityService | 1000 | 5s39ms | 0.06 | 3m16.559s | 2
3 | GOOGLE_SERVICES : *net_scheduler* | 10046 | 2s907ms | 8.01 | 2m48.706s | 290
4 | ANDROID_SYSTEM : DeviceMonitorService | 1000 | 2s158ms | 18.84 | 1m31.485s | 682
5 | GOOGLE_SERVICES : NlpWakeLock | 10046 | 1s861ms | 6.16 | 1m13.868s | 223
6 | AUDIOSERVER : AudioMix | 1041 | 1s745ms | 0.69 | 1m13.328s | 25
7 | GOOGLE_SERVICES : NlpCollectorWakeLock | 10046 | 1s565ms | 0.72 | 1m10.625s | 26
8 | com.whatsapp : sendinactive | 10191 | 1s482ms | 0.50 | 56.452s | 18
9 | GOOGLE_SERVICES : GCM_CONN_ALARM | 10046 | 1s | 0.77 | 52.161s | 28
Kernel Wakesources:
Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count
0 | netmgr_wl | 22s153ms | 22.93 | 13m21.925s | 830
1 | NETLINK | 6s941ms | 14136.75 | 4m11.277s | 511719
2 | IPA_RM12 | 6s883ms | 31.05 | 4m9.16s | 1124
3 | IPA_WS | 6s512ms | 191.56 | 3m55.75s | 6934
4 | suspend_backoff | 5s322ms | 1.05 | 3m12.675s | 38
5 | [timerfd] | 5s42ms | 174.43 | 3m2.524s | 6314
6 | PowerManagerService.Broadcasts | 3s71ms | 5.30 | 1m51.173s | 192
7 | alarmtimer | 2s696ms | 1.33 | 1m37.599s | 48
8 | ipc00000098_1326_rild | 1s540ms | 39.84 | 55.747s | 1442
9 | qcom_rx_wakelock | 1s25ms | 14.14 | 37.131s | 512
Kernel Wakeup Reasons:
Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count | Show Count vs Time
0 | 103:qcom,glink-smem-native-xprt-modem | 14s457ms | 31.02 | 8m43.315s | 1123 |
1 | unknown | 5s483ms | 14.28 | 3m18.489s | 517 |
2 | Abort:Last active Wakeup Source: lpass_IPCRTR | 7s938ms | 12.82 | 4m47.368s | 464 |
3 | Abort:Last active Wakeup Source: ipc0000004c_395_kworker/5:3 | 7s353ms | 10.91 | 4m26.181s | 395 |
4 | Abort:Pending Wakeup Sources: IPA_WS | 3s421ms | 6.13 | 2m3.846s | 222 |
5 | 669:qpnp_rtc_alarm | 2s63ms | 4.86 | 1m14.691s | 176 |
6 | 109:gsi | 1s888ms | 4.39 | 1m8.343s | 159 |
7 | 109:gsi:108:ipa | 734ms | 1.66 | 26.596s | 60 |
8 | Abort:Last active Wakeup Source: charge_service | 921ms | 1.57 | 33.369s | 57 |
9 | Abort:Some devices failed to suspend, or early wake event detected | 1s326ms | 1.30 | 48.034s | 47 |
App Wakeup Alarms:
Ranking | Name | Uid | Frequency (count/hr) | Count
0 | GOOGLE_SERVICES | 10046 | 6.46 | 234
1 | ANDROID_SYSTEM | 1000 | 4.25 | 154
2 | com.whatsapp | 10191 | 3.78 | 137
3 | com.google.android.apps.maps | 10123 | 2.21 | 80
4 | com.sonymobile.xperiaweather | 10178 | 1.30 | 47
5 | GOOGLE_CALENDAR | 10102 | 0.11 | 4
6 | RADIO | 1001 | 0.06 | 2
7 | com.android.chrome|com.sonymobile.email | 10186 | 0.03 | 1
8 | com.google.android.apps.messaging | 10124 | 0.03 | 1
9 | com.sonyericsson.xhs | 10162 | 0.03 | 1
Modem only active when not in WiFi and Sleeping
Many thanks Haldi, I will do that.
I actually disabled background data for RCS and now it isn't using as much battery however the phone still isn't going to deep sleep, last night I turned wifi off before going to sleep but all night the phone only went into deep sleep for a few minutes!!
I also found an app called Carrier Services which was also allowed to run in the background and I turned that off this morning. Will monitor and see
So I did the bug report and ran the analysis on Battery Historian
As you can see my Screen Off discharge rate is way too high compared to yours and the app wakeup alarms is much higher even though the duration is for 20 hrs
* I just got a small System update, it must be some bug fix. Will test again tomorrow
Aggregated Checkin Stats:
Metric | Value
Screen Off Discharge Rate (%/hr) | 2.85 (Discharged: 53%)
Screen On Discharge Rate (%/hr) | 11.71 (Discharged: 26%)
Screen On Time | 2h13m10.368s
Screen Off Uptime | 13h50m58.12s
Userspace Wakelock Time | 1h5m46.754s
Sync Activity | 1m47.624s (184 times)
JobScheduler Activity | 25m0.72s (1819 times)
App Wakeup Alarms | 2038 times
CPU Usage | 3h8m7.937s user time, 3h35m52.326s system time
Kernel Overhead Time | 12h45m11.368s
Kernel Wakelocks | 12h46m24.953s (9.264288e+06 times)
Wakeup Reasons | 9h30m6.077s (26131 times)
Mobile KBs/hr | 24.36
WiFi KBs/hr | 5338.85
Total WiFi Scan Activity | 6m49.085s (289 times)
Total WiFi Full Lock Activity | 3m2.244s
Mobile Active Time | 1m27.466s
Signal Scanning Time | 0
Full Wakelock Time | 30m14.366s
Interactive Time | 2h22m17.646s
Phone Call Time | 9m50.741s
Device Idle Mode Enabled Time | 5h54m25.35s
Device Idling Time | 5h55m27.862s
Total GPS Use | 15m41.08s (13 times)
Wifi Power Usage | 0.00%/hr, 0.00% total
Wifi Transfer Time | 2m29.24s
Wifi Idle Time | 1h1m48.565s
Bluetooth Power Usage | 0.00%/hr, 0.00% total
Bluetooth Transfer Time | 0
Bluetooth Idle Time | 0
Camera Use | 50.278s (3 times)
Flashlight Time | 0 (0 times)
Modem Transfer Time | 4h36m2.482s
Modem Idle Time | 1h10m48.001s
thatu said:
Screen Off Uptime | 13h50m58.12s
Kernel Overhead Time | 12h45m11.368s
Kernel Wakelocks | 12h46m24.953s (9.264288e+06 times)
Wakeup Reasons | 9h30m6.077s (26131 times)
Device Idle Mode Enabled Time | 5h54m25.35s
Device Idling Time | 5h55m27.862s
Modem Transfer Time | 4h36m2.482s
Modem Idle Time | 1h10m48.001s
Click to expand...
Click to collapse
There is something definitely wrong.
For the next Run make sure to charge your phone to 100% before the night and take a bug report the first thing in the morning. So you have a pure Idle Only report.
I did what you suggested and the phone is not going into deep sleep!
Aggregated Checkin Stats:
Metric | Value
Screen Off Discharge Rate (%/hr) | 2.81 (Discharged: 22%)
Screen On Discharge Rate (%/hr) | 0.00 (Discharged: 0%)
Screen On Time | 4m40.185s
Screen Off Uptime | 7h44m11.366s
Userspace Wakelock Time | 15m51.141s
Sync Activity | 38.232s (28 times)
JobScheduler Activity | 2m2.073s (167 times)
App Wakeup Alarms | 89 times
CPU Usage | 45m39.997s user time, 1h13m29.406s system time
Kernel Overhead Time | 7h28m20.224s
Kernel Wakelocks | 7h54m28.964s (4.421029e+06 times)
Wakeup Reasons | 5h29m34.644s (12299 times)
Mobile KBs/hr | 10.74
WiFi KBs/hr | 0.00
Total WiFi Scan Activity | 10.34s (5 times)
Total WiFi Full Lock Activity | 1.985s
Mobile Active Time | 0
Signal Scanning Time | 0
Full Wakelock Time | 0
Interactive Time | 4m39.628s
Phone Call Time | 0
Device Idle Mode Enabled Time | 6h43m34.372s
Device Idling Time | 6h45m6.188s
Total GPS Use | 57.042s (4 times)
Wifi Power Usage | 0.00%/hr, 0.00% total
Wifi Transfer Time | 0
Wifi Idle Time | 0
Bluetooth Power Usage | 0.00%/hr, 0.00% total
Bluetooth Transfer Time | 0
Bluetooth Idle Time | 0
Camera Use | 0 (0 times)
Flashlight Time | 0 (0 times)
Modem Transfer Time | 2h22m51.037s
Modem Idle Time | 48m45.393s
What information should I be looking for ?
Thanks in advance
Just to add, I find that my phone does go into deep sleep when stamina mode is activated
A bit more information ...
Last night the phone had the following stats:
Last screen off was at 9:48 PM and battery was at 78%
I woke up at 2:41 AM and battery had dropped to 61%
then I decided to switch to airplane mode and went back to sleep
Woke up at 7:47 AM and battery level was 58%
Seems something with the network keeps forcing the phone to stay on ?
Appreciate your thoughts as I would rather not turn on airplane mode when sleeping
Thanks
Properly battery drop at night about 8-9h is only 2%
Thanks Kris,
That is what bothers me, something is keeping the CPU running and I don't know what it is!
I think I have narrowed down the problem ... it has to do with the carrier and possibly the transmission towers where I am.
I switched the phone from LTE to WCDMA and the excessive drain overnight has disappeared, I didn't turn on Airplane mode and the battery usage overnight was flat and the phone went into Deep Sleep as it should.
Now I noticed a setting called Enable VoLTE so I will switch back to LTE and disable the VoLTE option and see if the phone sleeps.
thatu said:
I think I have narrowed down the problem ... it has to do with the carrier and possibly the transmission towers where I am.
I switched the phone from LTE to WCDMA and the excessive drain overnight has disappeared, I didn't turn on Airplane mode and the battery usage overnight was flat and the phone went into Deep Sleep as it should.
Now I noticed a setting called Enable VoLTE so I will switch back to LTE and disable the VoLTE option and see if the phone sleeps.
Click to expand...
Click to collapse
I use airplane mode over night.
Because my opinion is that nothing can be so important, that someone would need to wake you.
And if it's important enough, then there are emergency numbers.
thatu said:
I think I have narrowed down the problem ... it has to do with the carrier and possibly the transmission towers where I am.
I switched the phone from LTE to WCDMA and the excessive drain overnight has disappeared, I didn't turn on Airplane mode and the battery usage overnight was flat and the phone went into Deep Sleep as it should.
Now I noticed a setting called Enable VoLTE so I will switch back to LTE and disable the VoLTE option and see if the phone sleeps.
Click to expand...
Click to collapse
voLTE is voice-over-LTE, a voice technology which allows to do calls on LTE network, resulting in a clearer and most stable connection.
I don't think that voLTE affects battery life when you are not calling, but anyway voLTE should not work with 3G, so you won't know wether it affects or not.
MartinX3 said:
I use airplane mode over night.
Because my opinion is that nothing can be so important, that someone would need to wake you.
And if it's important enough, then there are emergency numbers.
Click to expand...
Click to collapse
I would agree however I am overseas and away from my family (6hr difference) and hence would prefer to have a phone line in case of an emergency
marcogiannetta said:
voLTE is voice-over-LTE, a voice technology which allows to do calls on LTE network, resulting in a clearer and most stable connection.
I don't think that voLTE affects battery life when you are not calling, but anyway voLTE should not work with 3G, so you won't know wether it affects or not.
Click to expand...
Click to collapse
Understood. That is what I was saying, I will switch back to LTE and disable this option ... the results are that the culprit is VoLTE
I think I got to the bottom of this battery drain issue on my XZ2 ... after weeks of investigating and testing different settings, my XZ2 now lasts for 2 days
What is causing the phone not to go into deep sleep and/or keep using battery overnight was the Enable VoLTE option. When enabled, the phone doesn't go into deep sleep and the battery hardly lasts for a day.
The battery chart attached shows the consumption over two days (almost), the first flat period, the phone was set to WCDMA then last night I set it back to LTE but disabled the VoLTE and the phone also went flat with battery consumption.
I think this is directly connected to whether the carrier is implementing VoLTE, or maybe testing or there is some sort of issue between the carrier and the handset. This may not be a problem in other places/other handsets .... needs more testing.
I will continue to monitor and report if anything changes but happy now
Thanks to all who provided input.
When I using GoogleCamera, some warnings appear:
HTML:
2020-06-02 14:10:23.108 8949-8949/com.google.android.GoogleCamera W/CAM_CameraHWManager: No front camera found on this device!
2020-06-02 14:10:23.108 8949-8949/com.google.android.GoogleCamera W/CAM_FacingController: No OneCameraCharacteristics found for: FRONT
I use this command to dump my camera hardware info
HTML:
adb shell dumpsys media.camera
HTML:
Number of camera devices: 3
Number of normal camera devices: 3
Device 0 maps to "0"
Device 1 maps to "1"
Device 2 maps to "2"
Active Camera Clients:
[]
== Camera HAL device [email protected]/legacy/0 (v3.3) static information: ==
Resource cost: 100
Conflicting devices: None
API1 info:
Has a flash unit: true
Facing: Back
Orientation: 90
== Camera HAL device [email protected]/legacy/1 (v3.3) static information: ==
Resource cost: 100
Conflicting devices: None
API1 info:
Has a flash unit: false
Facing: Back
Orientation: 90
== Camera HAL device [email protected]/legacy/2 (v3.3) static information: ==
Resource cost: 100
Conflicting devices: None
API1 info:
Has a flash unit: true
Facing: Back
Orientation: 90
You can see there are 3 cameras on my phone:
HTML:
Camera 0: flash unit: true, facing: BACK, so this is a back camera.
Camera 1: flash unit:false, facing: BACK, I think this is a FRONT camera because of no flash unit
Camera 2: flash unit: true, facing: BACK, so this is a back camera.
I have tries many camera apps, no app can open FRONT camera.
ROM used: P-MR3-RC002-RZR-200226.3141