Develop Bugs

[APP][v1.2][Material UI] Unlock History

Description
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please note that this is the free version of Unlock History. Purchasing the full version supports further development of Unlock History and is truly appreciated.
https://play.google.com/store/apps/details?id=com.dhruv.unlockhistorypro
This new app secretly checks and show all successful unlocks, apps used and the duration for which the device was used so you can check if someone else was using the phone, making your android smartphone more secure.
It is also a great tool for parents to monitor the phone usage by the child, or one could spy on their friend's phone as this app works silently.
The feature to set password makes sure that only you can check your device's record.
The complimentary widget not only looks good but also makes it easier to view the last unlock.
Main Features:
- Option to set password.
- Material UI
- Silently checks usage and shows no notifications.
- Automatically starts when the phone boots.
- Older usage data get cleaned up regularly if configured.
- Consumes very less battery.
- Very light weight tracking mechanism.
Play Store: https://play.google.com/store/apps/details?id=com.dhruv.unlockhistory

Datamonitor in upper corner shows always usage?

Hi,
I just got an Note 8 Pro and been playing around with it and it seems the easiest way out is to root and install a another rom, but i'm just curious about the meter you can activate that shows if you data is in use, mine is NEVER at 0 basically, it can hit to 0 a few seconds but usually its higher, jumping 0.1KB/s - 4.0KB/s, I do not use any social media apps - none.
I have tried press Deny and Cancel and NOT using Mi Cloud and stuff like that so what could it be?
In battery usage Android System is using 19% that is the most, i've read that it needs a few recycles and it'll stabilize(?) but my battery feel alright, so why would Android system draw less after a few recycles? I'm at 60% after 18h last charge. 4hS oT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there anything to do? I dowloaded a packet sniffer and i see some Mi.App.Chat-app stuff( i'm not using it) going through Amazon servers and a lot of chinese characters so i'm not sure what im looking at...
IMG does not work...
https:// cdn-21.minfil.com/U5b326Ban5/0692fc6d-1574466844/Screenshot_2019-11-23-00-38-46-680_cn.wps.xiaomi.abroad.lite.jpg
Just root and start over again to install "all" my stuff?

WATCH FIT ELEGANT // Problem of calories counting

Weird problem with my watch fit elgant for cycling calories counting
The bike route is almost the same ( km, time , average speed ) but look at the calories counting
30.17 km was made with the watch not connected to the smarphone => 543 Kcal WTF !!!
30.53 km was made with the watch connected to smartphone => 1138 Kcal ( this is correct according to my profil ( 1.82m / 82 kgs )
Seems there is a serious problem with cycling activity when you use the watch alone !! the count of calories is absolutely wrong !! concerning the running activity the count of calories is ok for me
Don't understant where this difference come from ?? data are almost the same for both route so It's seems that the huawei tru sport algorritm don't take my profil ( height, weight, ) in account when the watch is not connected but when it is no problem !!
Need your point of view
Thanks in advance
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[FEATURE REQUEST]

ⓘ The feature request resolved by taking the following idea (screenshot is attached):​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ו••×
Add in the battery field with samples (pre built) according to the following structure:
Battery >
#BSTATQ# Status (quantity: charge from and discharge at)
#BLEVL# Last level of connect/disconnect
#BLEVLN# Last level (numeric) of connect/disconnect
#BCLEV# Last connect level
#BDLEV# Last disconnect level
#BCLEVN# Last connect level (numeric)
#BDLEVN# Last disconnect level (numeric)
Example # 1:
-Example (string sample):
#BSTATQ# #BLEVL#
-Sample title/content (pre built):
Battery >
Last disconnected/connected level
discharge at 85%
Example # 2:
-Example (string sample):
Charge quantity: From #BCLEV# to #BDLEV#
-Sample title/content (pre built):
Battery >
Charge quantity
Charge quantity: From 30% to 100%
ו••×
ⓘ Zooper support site: Error (can't reach). Kindly check the screenshot given below:​

Development Mi Pad 5 EDL Test Point

After examining the motherboard points, I came up with two EDL test points
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well, heck. Those suckers are labelled as large as life.
But I do have a point.
With Qualcomm it has to do with a GPIO pin.
On my SDM636 it's GPIO57.
I've only seen GPIOs with a pull-down and a 1.8V source nearby.
So, if you're looking for EDL test points for something different, look for one point measuring 0V and another measuring 1.8V.
OTOH, it's easier to just find one point.
You can use a fresh AA or AAA battery (~1.55V) with a resistor to just find the GPIO.
Go from ground -> battery-, battery+ -> resistor, resistor -> GPIO
Use a 1k to 2.2k resistor, you won't hurt anything but it will be assertive enough.
I'm not totally sure that the GPIO number is fixed per SoC and not configurable in the OEM OTP.
But if you had (for example) a working SDM636 device, I'd go look for GPIO57 while your device is still working.
You have to be rooted though.
Code:
# ./edlcheck
0 1 0 1 0 1 0
Mmm, I'll generalize this and give it an argument if anybody wants.