[Q] Current Widget - Battery Issue? - HTC One X

I just downloaded the current widget app and i have charged my phone overnight but the current never reached 0 in the current widget app. It was always between 200-400 mA.
Is this normal? On my DHD the current reached 0 after leaving it for some extra minutes after reaching 100%.
Can anyone please recreate the issue to see if it's just me or it's a battery issue?

The One-X is not supported for now. So you'll see wrong values.

escalator said:
The One-X is not supported for now. So you'll see wrong values.
Click to expand...
Click to collapse
OK, that's why I'm only seeing values between 2000mA 4500mA.

escalator said:
The One-X is not supported for now. So you'll see wrong values.
Click to expand...
Click to collapse
there is fix in 0.36 for HOX, so the values are correct.

Related

[Q] How to tell the charging source and current on a S III?

On the SII, I just checked the following files, they don't seem to exist on the SIII...
/sys/class/power_supply/battery/charging_source
/sys/class/power_supply/battery/batt_current_adc
Anyhow happen to know what they are?
Promethyl said:
On the SII, I just checked the following files, they don't seem to exist on the SIII...
/sys/class/power_supply/battery/charging_source
/sys/class/power_supply/battery/batt_current_adc
Anyhow happen to know what they are?
Click to expand...
Click to collapse
They don't exist. Therefor my trusty Current Widget app won't show "ma" current draw either. Some other battery widgets can approximate it with math but the S3 does not provide the direct value any longer. Bummer eh!
There had to be some equivalent. Can you dump the tree at /sys/class/power (or whichever) for me?
I wrote a charging current app, but many of the users are leaving bad feedback because of this. Quite frustrating for all involved...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Seen some evidence it's /sys/class/power_supply/battery/current_now. I'll look into it some more.
Need testers for the battery current app. Let me know if anyone is willing.
Themad: I found some examples for the LS670 and GT-I9300, might work for the i747.
Can you confirm the model name (Build.Model) contains i747?
Would you be willing to try it for me?
Promethyl said:
Seen some evidence it's /sys/class/power_supply/battery/current_now. I'll look into it some more.
Need testers for the battery current app. Let me know if anyone is willing.
Click to expand...
Click to collapse
No such file on my s3 i747m lh1 stock rom. I have spoken with devs such as the Current Widget dev and and the concensus so far is that the hardware is not providing a value... Specifically it may not even have the sensor. Please prove me wrong. I conceptualized the high drain alert which the CW dev implemented. So if u want me to test, definitely....but my hopes are faded due to possible hardware deficiencies. I at least made my own usb cable to use with my multimeter to accurately measure incoming charging current.
fwiw, I often use "adb shell dumpsys battery" in a loop to monitor my battery progress, and it spits out a bunch of good info, but not necessarily current:
Code:
$ adb shell dumpsys battery
Current Battery Service state:
AC powered: true
USB powered: false
status: 2
health: 2
present: true
level: 97
scale: 100
voltage:4363
temperature: 264
technology: Li-ion
Promethyl said:
Seen some evidence it's /sys/class/power_supply/battery/current_now. I'll look into it some more.
Need testers for the battery current app. Let me know if anyone is willing.
Click to expand...
Click to collapse
Promethyl,
how are you making out with that app?
No news. I need to find someone who owns the the phone. Maybe some Level level calls or something. I just am in Denial..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I have an i747. In /sys/class/power_supply/battery, I see the following on stock I747MVLALH1 4.0.4 firmware.
Code:
batt_charging_source
batt_current_adc
batt_esus_test
batt_full_check
batt_lp_charging
batt_read_adj_soc
batt_reset_soc
batt_slate_mode
batt_temp
batt_temp_adc
batt_temp_adc_spec
batt_temp_check
batt_temp_radc
batt_test_value
batt_type
batt_use
batt_vf_adc
batt_vfocv
batt_vol
browser
call
camera
capacity
charging_enable
current_avg
data_call
device
factory_mode
fg_psoc
gps
health
hotspot
lte
music
online
power
present
status
subsystem
sys_rev
talk_gsm
talk_wcdma
technology
temp
type
uevent
video
voltage_now
wc_adc
wc_status
wifi
On the devices About screen, Model number and Build number both include i747 in the string. Not sure if that helps with your Build.Model question.
So it must be only the ATT builds which have this.
Can I ask you to plug in your phone to a charger of any type and get the output of "
Code:
cat /sys/class/power_supply/battery/batt_current_adc
" ?
Transient77 said:
I have an i747. In /sys/class/power_supply/battery, I see the following on stock I747MVLALH1 4.0.4 firmware.
Code:
batt_charging_source
batt_current_adc
batt_esus_test
batt_full_check
batt_lp_charging
batt_read_adj_soc
batt_reset_soc
batt_slate_mode
batt_temp
batt_temp_adc
batt_temp_adc_spec
batt_temp_check
batt_temp_radc
batt_test_value
batt_type
batt_use
batt_vf_adc
batt_vfocv
batt_vol
browser
call
camera
capacity
charging_enable
current_avg
data_call
device
factory_mode
fg_psoc
gps
health
hotspot
lte
music
online
power
present
status
subsystem
sys_rev
talk_gsm
talk_wcdma
technology
temp
type
uevent
video
voltage_now
wc_adc
wc_status
wifi
On the devices About screen, Model number and Build number both include i747 in the string. Not sure if that helps with your Build.Model question.
Click to expand...
Click to collapse
I just tried cat /sys/class/power_supply/battery/batt_current_adc while charging from my computer and got an output of '0'
I'll try again at home when connected to a wall charger. This is with an AT&T gs3 running stock 4.1.1.
Second that, I just tried cat /sys/class/power_supply/battery/batt_current_adc while charging from my laptop's always on USB port and got an output of '0' running CM10.1 on AT&T i747.
I think the i747 just doesn't have this functionality...I hope someone proves me wrong.
Sandman333 said:
I just tried cat /sys/class/power_supply/battery/batt_current_adc while charging from my computer and got an output of '0'
I'll try again at home when connected to a wall charger. This is with an AT&T gs3 running stock 4.1.1.
Click to expand...
Click to collapse
This Apps Works Great on Notes 3
here is battery info from Battery Monitor widget apk on my MSM8926 device:
here is battery info from Battery Monitor widget apk on my MSM8612 device:
I suggest to use below items for rich infomation:
POWER_SUPPLY_TYPE
POWER_SUPPLY_CHARGE_TYPE
POWER_SUPPLY_VOLTAGE_NOW
POWER_SUPPLY_CURRENT_NOW
or
/sys/class/power_supply/battery/charge_type
/sys/class/power_supply/usb/type
/sys/class/power_supply/bms/current_now: -382639
/sys/class/power_supply/battery/charge_voltage: 4788420
Battery information (model name hidden).
Battery capacity: 2000, from kernel: 2000 (override: -2000)
Available files on device:
/sys/class/power_supply/battery/current_now
Content of /sys/class/power_supply
/sys/class/power_supply/bms/type: Unknown
/sys/class/power_supply/bms/charge_counter_shadow: 51156
/sys/class/power_supply/bms/resistance: 197000
/sys/class/power_supply/bms/charge_full_design: 2000000
/sys/class/power_supply/bms/current_now: -382639
/sys/class/power_supply/bms/charge_full: 2038000
/sys/class/power_supply/bms/capacity: 97
/sys/class/power_supply/bms/charge_counter: 2439
/sys/class/power_supply/bms/status: Charging
/sys/class/power_supply/bms/uevent: POWER_SUPPLY_NAME=bms
POWER_SUPPLY_CAPACITY=97
POWER_SUPPLY_STATUS=Charging
POWER_SUPPLY_CURRENT_NOW=-390452
POWER_SUPPLY_RESISTANCE=197000
POWER_SUPPLY_CHARGE_COUNTER=2437
POWER_SUPPLY_CHARGE_COUNTER_SHADOW=51149
POWER_SUPPLY_CHARGE_FULL_DESIGN=2000000
POWER_SUPPLY_CHARGE_FULL=2038000
POWER_SUPPLY_CYCLE_COUNT=0
/sys/class/power_supply/bms/cycle_count: 0
/sys/class/power_supply/usb/type: USB_DCP
/sys/class/power_supply/usb/scope: Device
/sys/class/power_supply/usb/current_max: 1500000
/sys/class/power_supply/usb/health: Unknown
/sys/class/power_supply/usb/online: 1
/sys/class/power_supply/usb/voltage_max: 0
/sys/class/power_supply/usb/uevent: POWER_SUPPLY_NAME=usb
POWER_SUPPLY_HEALTH=Unknown
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_VOLTAGE_MAX=0
POWER_SUPPLY_CURRENT_MAX=1500000
POWER_SUPPLY_SCOPE=Device
POWER_SUPPLY_TYPE=USB_DCP
/sys/class/power_supply/usb/present: 1
/sys/class/power_supply/battery/temp: 273
/sys/class/power_supply/battery/type: Battery
/sys/class/power_supply/battery/input_voltage_regulation: 0
/sys/class/power_supply/battery/system_temp_level: 1
/sys/class/power_supply/battery/charge_full_design: 2000000
/sys/class/power_supply/battery/input_current_settled: 0
/sys/class/power_supply/battery/charge_voltage: 4788420
/sys/class/power_supply/battery/current_now: -381355
/sys/class/power_supply/battery/power_on_voltage: 3500
/sys/class/power_supply/battery/charge_full: 2038000
/sys/class/power_supply/battery/charge_temp: 537
/sys/class/power_supply/battery/charge_type: Fast
/sys/class/power_supply/battery/capacity: 97
/sys/class/power_supply/battery/voltage_max_design: 4350000
/sys/class/power_supply/battery/health: Good
/sys/class/power_supply/battery/input_current_max: 1500000
/sys/class/power_supply/battery/online: 1
/sys/class/power_supply/battery/input_current_trim: 42
/sys/class/power_supply/battery/status: Charging
/sys/class/power_supply/battery/voltage_min: 4300000
/sys/class/power_supply/battery/voltage_ocv: -22
/sys/class/power_supply/battery/voltage_now: 4348647
/sys/class/power_supply/battery/uevent: POWER_SUPPLY_NAME=battery
POWER_SUPPLY_CHARGING_ENABLED=1
POWER_SUPPLY_STATUS=Charging
POWER_SUPPLY_CHARGE_TYPE=Fast
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_VOLTAGE_MAX_DESIGN=4350000
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=4350000
POWER_SUPPLY_VOLTAGE_NOW=4348647
POWER_SUPPLY_CAPACITY=97
POWER_SUPPLY_CURRENT_NOW=-381890
POWER_SUPPLY_INPUT_CURRENT_MAX=1500000
POWER_SUPPLY_INPUT_CURRENT_TRIM=42
POWER_SUPPLY_INPUT_CURRENT_SETTLED=0
POWER_SUPPLY_VOLTAGE_MIN=4300000
POWER_SUPPLY_INPUT_VOLTAGE_REGULATION=0
POWER_SUPPLY_CHARGE_FULL_DESIGN=2000000
POWER_SUPPLY_CHARGE_FULL=2038000
POWER_SUPPLY_CHARGE_VOLTAGE=4784500
POWER_SUPPLY_CHARGE_TEMP=537
POWER_SUPPLY_TEMP=273
POWER_SUPPLY_TEMP_VOLTAGE=876
POWER_SUPPLY_POWER_ON_VOLTAGE=3500
POWER_SUPPLY_TEMP_COOL=0
POWER_SUPPLY_TEMP_WARM=0
POWER_SUPPLY_SYSTEM_TEMP_LEVEL=1
POWER_SUPPLY_CYCLE_COUNT=0
POWER_SUPPLY_VOLTAGE_OCV=-22
/sys/class/power_supply/battery/technology: Li-ion
/sys/class/power_supply/battery/cycle_count: 0
/sys/class/power_supply/battery/temp_voltage: 876
/sys/class/power_supply/battery/charging_enabled: 1
/sys/class/power_supply/battery/voltage_min_design: 4350000
/sys/class/power_supply/battery/present: 1
/sys/class/power_supply/battery/temp_cool: 0
/sys/class/power_supply/battery/temp_warm: 0
Promethyl said:
On the SII, I just checked the following files, they don't seem to exist on the SIII...
/sys/class/power_supply/battery/charging_source
/sys/class/power_supply/battery/batt_current_adc
Anyhow happen to know what they are?
Click to expand...
Click to collapse
Looking for update apk for samsung charging current
Sent from my SM-G9006V using XDA Free mobile app

[Q] Display is eating too much battery

Hello, i have a problem in my note 2. I am currently using DN4v2.1 rom and i added the MOD2vL. My problem is that my display is eating too much battery, as you can see from the attachment below, it has the highest percentage. My battery drops dramaticaly in just few minutes. How can i stop this? Thank you and your help will be a very good help. Thanks.
ceethatjay said:
Hello, i have a problem in my note 2. I am currently using DN4v2.1 rom and i added the MOD2vL. My problem is that my display is eating too much battery, as you can see from the attachment below, it has the highest percentage. My battery drops dramaticaly in just few minutes. How can i stop this? Thank you and your help will be a very good help. Thanks.
Click to expand...
Click to collapse
It's normal buddy. Our display need a large amount of energy.
Even you are using other ROM, it will be the same.
my solution is, try go to setting and find adaptive display and set it to basic.
THe color will be faded but it save battery.
hope this can help.
Thanks man!
ceethatjay said:
Hello, i have a problem in my note 2. I am currently using DN4v2.1 rom and i added the MOD2vL. My problem is that my display is eating too much battery, as you can see from the attachment below, it has the highest percentage. My battery drops dramaticaly in just few minutes. How can i stop this? Thank you and your help will be a very good help. Thanks.
Click to expand...
Click to collapse
The display always has the highest percentage, because the screen always uses the most amount of power on any device. It's normal. The thing you should check is the "screen on time". You can check that by clicking on the display percentage on that screen. Try lowering the brightness or turning on adaptive display.

E98x LP Battery issues Potentially resolved

Hi All I am Posting my results, I need a few ppl who could help and see if this is going to help everyone or only me
And to the critics, I will be doing a screen on time (SOT, ppl are asking and not getting answered) test, I am as eager to fix this so if you would like me to run anything while the screen is on, please let me know
An hour ago i put brightness at 100 while battery was at 50% been browsing the net with chrome using mobile data and it dropped to about 10%. Much less heat than expected although brightness was limited to 84 at some point. Will do a 50 brightness test tomorrow from full charge but wont be touching the phone much
Steps to Follow to give me info
Hi Guys,
Had a bit of time, this is the info I need, hopefully I will get responses from a view e98x variants, even other LGs would be great but please specify the details of your phone.
Download Battery Doctor from the Play Store google dot com/store/apps/details?id=com.ijinshan.kbatterydoctor_en&hl=en
Get it running , opened, etc and then look at the app usage info (scroll down) for the last 24 hours (seen in screenshot attached)
When opened please send me the screenshot or the the list of draining APPS, I have hidden my top drainer that consumed 98% of my battery in the other attached screenshot. At the time of my screenshot I have not uploaded, it has used 34% of my battery and has been disabed for 19 hours. I cannot yet suggest the name or anyone to do anything with the service yet as I am still attempting to find out what breaks (so far nothing.)
I will send battery updates as far as I can.
Another Test
So the next thing I have done is charge full again, set the brightness to 50% and played Hearthstone for 3 Hours, I am personally pleased with the results as i could not achieve 3 Hours with the Phone before.
i get 3.5-4.5 hours screen from 100%
with [ROM][5.0.2]STOCK LOLLIPOP G.PRO V1.5 of bountyman334
with few modification mostly removing system apps
hello
Can you explain me what should I do to improve the battery life?
I never could have more than two hours of charge with brightness set to 100%.
sorry for my bad english
brunosp7 said:
hello
Can you explain me what should I do to improve the battery life?
I never could have more than two hours of charge with brightness set to 100%.
sorry for my bad english
Click to expand...
Click to collapse
Can you follow post 2 and send me the details, The item I disabled eventually disabled my MTP and USB Tethering, as it doesnt bother me yet, I am yet to attempt tpo fix it. I would Highly recommend 30 - 60% brightness, anything more seems to not have a major impact on brightness, it just reduces battery life and cause heat, which reduces the maximum charge of the battery in future
here is my screenshot, hope it helps u!
ROM 5.0.2 STOCK LOLLIPOP G.PRO V7 of bountyman334
Alibabara said:
here is my screenshot, hope it helps u!
Click to expand...
Click to collapse
Thanks alibabara, but your screenshot doesnt show
brunosp7 said:
ROM 5.0.2 STOCK LOLLIPOP G.PRO V7 of bountyman334
Click to expand...
Click to collapse
Hi brunosp7, the app I expect to see is not listed, this is a good thing, however viewing the list, it appears that some apps remain open after use. do you have an app that keeps backround apps in check, something like this battery doctor or clean master?
sparke-frostie said:
Hi brunosp7, the app I expect to see is not listed, this is a good thing, however viewing the list, it appears that some apps remain open after use. do you have an app that keeps backround apps in check, something like this battery doctor or clean master?
Click to expand...
Click to collapse
right now I'm not using any app to stop background applications.
by the way, I think the application you want is not listed because the battery doctor app disabled many programs and services the first time I started.
sorry for my bad English.
brunosp7 said:
right now I'm not using any app to stop background applications.
by the way, I think the application you want is not listed because the battery doctor app disabled many programs and services the first time I started.
sorry for my bad English.
Click to expand...
Click to collapse
even after disabling the app it still showed up in battery docter, however I had not enabled the super thingy to allow it to fully disable apps. can you take a look to see if you can find the app lgatcmd on your phone, either enabled or disabled

How To Guide Limit Charge

If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
That's something I've been wondering how to do! kudos
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
Will this work for the older Pixel devices as well (such as my Pixel 4)? : o
Help The Peace said:
Will this work for the older Pixel devices as well (such as my Pixel 4)? : o
Click to expand...
Click to collapse
No reason why not looking at the command, give it a try
danw_oz said:
No reason why not looking at the command, give it a try
Click to expand...
Click to collapse
Sounds good. But will it also drain battery from then on? Or will it continually "charge" to keep it at 80%? And is your command an ADB command?
You can use this in Tasker with a "run shell" task when the device boots since this reverts to 100 if you ever reboot the device.
Does this command require root?
Other than prolonging the battery condition/longevity, is there another reason to set a charge limit?
Last question: The command stays in effect until reboot?
Thanks.
snovvman said:
Does this command require root?
Other than prolonging the battery condition/longevity, is there another reason to set a charge limit?
Last question: The command stays in effect until reboot?
Thanks.
Click to expand...
Click to collapse
I believe it does require a root, yes
I don't know any other benefit for limiting charge other than preserving the battery's long-term, overall health. Not allowing your battery to go too low or too high will help keep its maximum charge for a longer time
And yes, the setting will revert back to the default 100 after a reboot. I use Tasker to run the command on each boot, gotta love automation!
does limiting the charge affect the battery optimization algorithms?
thanks for this. if only every phone was this easy
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
Thank you!
For what it's worth, this works with the Battery Charge Limit [ROOT] app (XDA thread). Go into the app's settings, enable Configurable CTRL File Data, click Configure Control Data, click I Understand, paste "/sys/devices/platform/google,charger/charge_stop_level" (without quotes) in the Set Path to Desired File, and since this app expects you to set values for Enabled and Disabled, I set both to 75, since that's what I want my battery to charge up to.
If I start using an automation app like Tasker, then I can set it a different way, but I kinda like this app method anyway.
Edit:
Now I am using the Advanced Charging Controller (ACC) Magisk Module and the AccA app which is a front-end/GUI for configuring the module.
Forgive my ignorance I have not paid much attention to the forums over the last couple of years.
Is there a benefit to limiting the charge percent? is 90 the default recommendation?
dms76 said:
Forgive my ignorance I have not paid much attention to the forums over the last couple of years. Picked up a job where I can't slack and read ll day long.. LOL
Is there a benefit to limiting the charge percent? is 90 the default recommendation?
Click to expand...
Click to collapse
The point is to limit battery degradation. Tesla does it with their cars. Personally, I'd rather just have an alert to notify me and I use AccuBattery Pro for that. I rarely charge overnight but if I actually do, I let adaptive charging handle handle the slow charging.
nycdiplomat said:
You can use this in Tasker with a "run shell" task when the device boots since this reverts to 100 if you ever reboot the device.
Click to expand...
Click to collapse
i did that but it won't do anything. it still charges above my set value, so i was wondering.
what i did in tasker:
created a profile > event > system event > device boot
created a task > run shell > "echo 65 > /sys/devices/platform/google,charger/charge_stop_level"
i rebooted to make sure tasker was running (had battery optimization disabled on tasker), and tasker seems to run but it won't work. the "65" value was just set while i was testing it and since my phon was below 50% charge i did not want to wait that long so i started with 55, then 60 and so on. as i write this i'm waiting for it to hit 65% and hopefully stop charging. all i can think of is that i probably used the wron profile in tasker?
regards
roirraW edor ehT said:
Thank you!
For what it's worth, this works with the Battery Charge Limit [ROOT] app (XDA thread). Go into the app's settings, enable Configurable CTRL File Data, click Configure Control Data, click I Understand, paste "/sys/devices/platform/google,charger/charge_stop_level" (without quotes) in the Set Path to Desired File, and since this app expects you to set values for Enabled and Disabled, I set both to 75, since that's what I want my battery to charge up to.
If I start using an automation app like Tasker, then I can set it a different way, but I kinda like this app method anyway.
Click to expand...
Click to collapse
No problem!
Yeah for sure, that’s the beauty of android, there are several ways of going about things.
I use Tasker because that way it’s just one less app that I have on my phone. I like to have as many things inside of Tasker as possible to keep things organized and consolidated.
Although I’m currently back on iOS after being on Android for six years! I didn’t like the 6 Pro enough to keep it and I’m not going to get into details because there’s already a lot of hate threads for it - and I don’t want to add to that.
Let’s just say that I’ve been enjoying iOS more than I thought I would, especially considering I’ve been on android for so many years. So we’ll see what Google cooks up for the 7 series.
Anyways, back to topic, definitely going to miss Tasker for how much that can be done with it! The Shortcuts app on iOS is the closest thing to Tasker and it’s nowhere near as robust lol
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
does this work without root? i tried this using tasker but it did not work. how did u test it?
boxemall said:
does this work without root? i tried this using tasker but it did not work. how did u test it?
Click to expand...
Click to collapse
Yes, As far as root required.
boxemall said:
does this work without root? i tried this using tasker but it did not work. how did u test it?
Click to expand...
Click to collapse
You need root.
I just got one of these: https://chargie.org/
Seems to work well so far.
cmh714 said:
I just got one of these: https://chargie.org/
Seems to work well so far.
Click to expand...
Click to collapse
I have looked at them before but they seem very expensive for what they are, it is easier just to set a silent alarm for a few hours after you intend to get up.

Question Boot Animation glitch while on QHD, custom roms

I seem to be having an issue when using the QHD+ (doesn't occur while on FHD) option across all roms, rooted and stock. The boot animation glitches right before it's finished and was wondering if anyone had the same experience? I've done a little bit of research on desc.txt, but haven't found anything to remedy it. I've tried changing the fps and resolution within desc.txt. Also tried various custom boot animations to no avail.
I know it's a small thing, but wondering if anyone had a solution to this (besides switching to FHD)?
Android version? Phone model?
TheGhost1951 said:
Android version? Phone model?
Click to expand...
Click to collapse
Sorry currently on A13, WatchDogs custom ROM, LE2125 unlocked
First line of desc.tx should look like this for the bootanimations.zip.......
g w h 0 0 30
W=width in pixels
H=height in pixels
I believe the 0 0 is the x,y coordinates for animation reference position
g I believe is for global
30 is the frames per second
The first line changed with A12+
Should be the same for A13 maybe
TheGhost1951 said:
First line of desc.tx should look like this for the bootanimations.zip.......
g w h 0 0 30
W=width in pixels
H=height in pixels
I believe the 0 0 is the x,y coordinates for animation reference position
g I believe is for global
30 is the frames per second
The first line changed with A12+
Should be the same for A13 maybe
Click to expand...
Click to collapse
Thanks for that, man. Do you know if the FPS matters? Or is it just a visual thing. Also, is it the width and height of the image, or the screen resolution? Will test some things when I get home
kodayoda713 said:
Thanks for that, man. Do you know if the FPS matters? Or is it just a visual thing. Also, is it the width and height of the image, or the screen resolution? Will test some things when I get home
Click to expand...
Click to collapse
You want the w and h to correlate to the screen size for optimal clarity. Fps determines how fast or slow it plays...and it determines how long it will play
TheGhost1951 said:
You want the w and h to correlate to the screen size for optimal clarity. Fps determines how fast or slow it plays...and it determines how long it will play
Click to expand...
Click to collapse
So, I spent the last two hours messing with it and had no luck fixing the glitch. I just don't know what it could be. I've reached out to a few of the rom groups and no response. I also haven't seen anyone else report this problem. I don't think it's a hardware issue, and it seems to happen on every rom I've tried. Any ideas?
Does it happen with any bootanimations?
TheGhost1951 said:
Does it happen with any bootanimations?
Click to expand...
Click to collapse
Yes. Used the stock one on Nameless, WatchDogs, Lineage. All seem to have that issue, unfortunately. I'm thinking it's the implementation of QHD? Or some DPI issue?
kodayoda713 said:
Yes. Used the stock one on Nameless, WatchDogs, Lineage. All seem to have that issue, unfortunately. I'm thinking it's the implementation of QHD? Or some DPI issue?
Click to expand...
Click to collapse
I tend to believe that during boot, it is switching from one mode of display quality to the mode you changed to. You stated that on FHD, it doesn't happen. Possible?
TheGhost1951 said:
I tend to believe that during boot, it is switching from one mode of display quality to the mode you changed to. You stated that on FHD, it doesn't happen. Possible?
Click to expand...
Click to collapse
That's my thought. I guess there would have to be some back end changes made, and not something that could be changed in the boot animation sequence?
kodayoda713 said:
That's my thought. I guess there would have to be some back end changes made, and not something that could be changed in the boot animation sequence?
Click to expand...
Click to collapse
That is my thoughts since it works ok on FHD mode.
TheGhost1951 said:
That is my thoughts since it works ok on FHD mode.
Click to expand...
Click to collapse
Thanks for the help, good sir. I will continue searching
How did you manage to remove orange state text?
lukacarina said:
How did you manage to remove orange state text?
Click to expand...
Click to collapse
Wrong thread.....

Categories

Resources