{
"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"
}
Patches got merged to CM7
Will be included from nightly 27 onwards. Thread is about to be closed. Use nightly thread for further discussion if any.
Achievment earned: RIVER RUNS RED (write in red on first post of a thread with at least 50 pages)
Build #9 contains Kali's latest kernel plus the 2 patches from hrkfdn about the aic3254 dsp chip. no other tweaks involvled, since i like kali's fast and simple work.
get build #9 here - md5: cc9372655750994cddfd12460dcdcb8b
http://postkreative.eu/mad/mad-batfix-B9-signed.zip
http://uberfail.org/mad/mad-batfix-B9-signed.zip
mirrors by phunkycow - thanks a bunch!
just flash this .zip file from recovery. reflash it each time you installed a new nightly build. #6 and newer contains a cleanup-function to remove older deprecated files from system. reported to work with cm6
no workaround needed anymore with #9
Now that we seem to have reached the final version - thanks to you all and your feedback - without it, it would have been much harder to trace down all issues.
FAQ
Q: Where has the CHANGELOG gone?
A: Move to the top of 2nd post - just scroll down a bit.
Q: Do i need anthing else but the latest patch?
A: No. Except for a cm7 RC or nightly rom installed.
Q: Why do i need to reflash after a new nightly?
A: Because we cannot backup the boot image. So once you flash a nightly/RC, you also get its kernel.
Q: Whats this FM-Radio thing i read about?
A: One discussed way to solve the battery drain in cm7 nigthlies and future RC's would be to use hrkfdn's patches and disable all fm-radio support (not only the apk file, but also the libs and framework). This patch is bypassing disabling FM-Radio and still doing its job. Result of quiet some work.
Q: Will this patch work with other roms?
A: Sense based roms dont need it at all. Non sense roms could use the patch on their kernel, but its not sure if this kernel runs with other roms. You can either try it, or ask in your kernel thread to include the patches. But, this is not final/stable yet. Guranteed to work with CM7, reported to work with CM6.
Q: When will this be in CM7 nightlies?
A: When all issues are solved. It seems thats the case with #8 - so expect nightly integration soon.
Known Issues in #9
None yet.
Monitor Status of DSP Chip
get gscript light free from market
start it, menu -> add script
use "dmesg aic" as title
leave "Needs SU?" checked
write "dmesg | grep -i aic | grep -v suspend | grep -v resume | tail -n 25" into the lower command box and save
back in adw: menu -> add -> shortcuts -> GScript Lite -> dmesg aic
This results in one-click-to-check-homescreen-shortcut
Sample dmesg output
Code:
<6>[ 106.647766] aic3254_ioctl: index 13 for 40047313
<6>[ 106.647949] aic3254_set_config: table(0x40047313) index(13)
<6>[ 106.648071] aic3254_set_config: enable rx
<6>[ 106.648498] aic3254_config: size = 15
<6>[ 106.649475] aic3254_config: size = 11
<6>[ 122.602355] aic3254_ioctl: index 29 for 40047313
<6>[ 122.602508] aic3254_set_config: table(0x40047313) index(29)
<6>[ 122.602722] aic3254_config: size = 8
<6>[ 122.603973] aic3254_set_config: disable rx
<6>[ 122.604095] aic3254_powerdown: power off AIC3254
<6>[ 122.604217] aic3254_config: size = 32
at first, the dsp is enabled (enable rx) when i started a mp3 - then the dsp chip is powered off again when i stopped the playback. this power off should occur each time, you stop using sound playback or microphone.
requested feedback:
are there situations, when power off does not work? when you for example have to invoke the old "voice dial" workaround to make poweroff appear again?
Closing comments
build #9 should be the final version. if no more issues arise in the next 48 hours, i will integrate it into cm7 nightlies.
in case you wanna use #5 again, i made a copy of the old opening post below this post, including downloads and instructions.
happy battery life
mad
changelog
#9: remove AicBootFix.apk from app-drawer and list of applications. its secret now!
#8: added final(?) AicBootFix.apk, removed old bootfix, removed suspend/resume messages, added hopes this is the final version without issues
#7: reverted the latest patch of hrkfdn on behalf of himself. this kernel now only contains the first and second spi_aic3254.c patches.
#6: switched to hrkfdn's patches - added aicbootfix - looking forward to keep fm enabled.
#5: no need to use workaround anymore - modified power daemon and kernel driver take care of it. just flash .zip file once - will add itself to cm's auto backup facility.
#4: stoped logcat spam. opened an own thread, since cm7-ace-nightly started beeing the wrong place now.
#3: addind missing wifi module of #2
#2: added kernel and status - decreased ioctl time from 60s to 20s
#1: initial release
archive of old bat fix / method - build #5 - do not use unless you got good reason
This thread/patch aims to fix the battery drain all non-sense ace roms currently have. As soon as this is tested and working for everyone without issues, it will be merged into cm7 and probably also to other roms.
update 2011/03/11: sorry for being away two days. was unforseen. whats the status? hrkfdn started developing a own patch to the aic driver. by now, it seems much better than my solution. it still got an issue with fm radio on boot - but once that is figured out, that patch will be superior to my solution and probably make its way to nightly. until then, have fun with #5 - but dont expect further development here.
This patch contains a kernel, which is based on kali's cm7 kernel. in fact, its absolutly the same, just the driver for the AIC3254 dsp chip is changed.
get build #5 here - md5: f7c7b01a47266b26b8a01f2fc853cfbe
http://www.filesonic.com/file/178617251/mad-#5-aic3254pd_signed.zip
phunkycow's mirrors: http://postkreative.eu/mad/mad-5-aic3254pd_signed.zip / http://uberfail.org/mad/mad-5-aic3254pd_signed.zip - thanks phunky!
old work around after boot not needed anymore. just flash and smile.
to get the current power status:
Code:
[[email protected] xbin]$ adb shell aic3254pd status
Power status of aic3254 chip: OFF
same in terminal emulator on phone:
Code:
localhost / # aic3254pd status
Power status of aic3254 chip: OFF
this is a typical "adb logcat | grep -i aic":
Code:
[ 340.841369] aic3254_set_config: enable tx
[ 340.841766] aic3254_config: size = 12
[ 349.698486] aic3254_powerdown: power off AIC3254
[ 349.698638] aic3254_config: size = 32
[ 381.205322] aic3254_ioctl: Query for AIC3254_POWERSTATUS returned 0 (OFF)
[ 498.071563] aic3254_ioctl: Query for AIC3254_POWERSTATUS returned 0 (OFF)
this is the desired output - since OFF means less battery drain. if you only see ON but never OFF (even though no apps using speaker/microphone), leave feedback.
note: unmodified kernel cannot keep track of power status and init status. flash on non official cm7 roms on your own risk
measurements with battery monitor widget showed, for cm7 the battery drain drops from 11-15mA to 1-5mA to the level, sense roms in standby reach.
regards
mad
I don't have a mirror but I'll seed this until you update: torrent.
Thanks a lot, this made me try CM7
EDIT: I see you are updating but, anyway - the torrent is #4.
#5 might be the last - working on sending the stuff google voice search sends automatic on startup
need feedback: anyone notices, auto-power-down doesnt work anymore after it worked once?
do you need to start voice search again to get power down working?
I'm on cm7, latest nightly. flashed latest version battery fix however even after using voice search, terminal always shows the aic3254 chip as on?
Sent from my Desire HD using Tapatalk
Good on U!
Sent from my DHD Gingerbread
mad-murdock said:
#5 might be the last - working on sending the stuff google voice search sends automatic on startup
need feedback: anyone notices, auto-power-down doesnt work anymore after it worked once?
do you need to start voice search again to get power down working?
Click to expand...
Click to collapse
Noticed. Activated back on some time later.
Hey thanks so much for the patch !
However, when i try to enter command in terminal emulator, i have access denied ???
Do you know why ???
But when i tap dmesg | grep AIC3254, i have this after voice search activation :
Result:
<6>[ 366.089080] aic3254_powerdown: power off AIC3254
<6>[ 426.296417] aic3254_powerdown: power off AIC3254
<6>[ 486.500854] aic3254_powerdown: power off AIC3254
<6>[ 546.708404] aic3254_powerdown: power off AIC3254
<6>[ 606.913177] aic3254_powerdown: power off AIC3254
Cheers
Type in su, enter. Then type in the aic3254 status code.
Sent from my Desire HD using Tapatalk
alexmason14 said:
Type in su, enter. Then type in the aic3254 status code.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Oh thanks a lot
Sent from my Desire HD using XDA Premium App
I can replicate the autoswitching on of aic3254pd by playing music through headphones using the android music player..
I don t understand how to apply this patch sorry .... Just flash via CWM 3.0.0.6 and restart ?
sonydesouza said:
Hey thanks so much for the patch !
However, when i try to enter command in terminal emulator, i have access denied ???
Do you know why ???
But when i tap dmesg | grep AIC3254, i have this after voice search activation :
Result:
<6>[ 366.089080] aic3254_powerdown: power off AIC3254
<6>[ 426.296417] aic3254_powerdown: power off AIC3254
<6>[ 486.500854] aic3254_powerdown: power off AIC3254
<6>[ 546.708404] aic3254_powerdown: power off AIC3254
<6>[ 606.913177] aic3254_powerdown: power off AIC3254
Cheers
Click to expand...
Click to collapse
this is what you want to see! dsp chip powers itself down when unused. when you hear a sound, you should see another power off short after.
better do the aic3254pd status command described above
I don't have google voice installed, so I activate power off with built-in voice dialer. Works perfect for me.
Sent from my Desire HD using XDA Apppt
Great work, thanks! Here is some info from my testing, hope it's useful.
I installed mad-#4-aic3254pd_signed.zip from recovery, rebooted then waited
a while without doing anything with the phone (no power button, no touch).
Here is what I got:
/cygdrive/c/xxx: adb shell aic3254pd status
Power status of aic3254 chip: ON
/cygdrive/c/xxx: adb shell dmesg | grep aic3254_
<6>[ 5.092376] spi_aic3254_init
<6>[ 5.092590] spi_aic3254_probe
<6>[ 9.520355] aic3254_ioctl: parameters(64, 1024, 806041a0)
<6>[ 9.521087] aic3254_config: size = 23
<6>[ 9.524627] aic3254_config: size = 1
<6>[ 9.524963] aic3254_ioctl: update table(64,1024) successfully
<6>[ 9.526031] aic3254_ioctl: parameters(64, 1024, 806341a8)
<6>[ 9.526733] aic3254_ioctl: update table(64,1024) successfully
<6>[ 10.349945] aic3254_ioctl: parameters(24, 16384, 806641b4)
<6>[ 10.351898] aic3254_ioctl: update table(24,16384) successfully
<6>[ 10.370605] aic3254_ioctl: index 23 for 40047321
<6>[ 10.370697] aic3254_set_config: table(0x40047321) index(23)
<6>[ 10.370910] aic3254_set_config: miniDSP command len = 32
<6>[ 10.371002] aic3254_set_config: rx mode 29, tx mode 29
<6>[ 10.371124] aic3254_config: size = 32
<6>[ 10.372253] aic3254_set_config: configure minidsp done
<6>[ 10.372406] aic3254_ioctl: index 15 for 40047312
<6>[ 10.372619] aic3254_set_config: table(0x40047312) index(15)
<6>[ 10.372711] aic3254_set_config: enable tx
<6>[ 10.373138] aic3254_config: size = 23
<6>[ 10.373626] aic3254_config: size = 20
<6>[ 470.774963] aic3254_ioctl: Query for AIC3254_POWERSTATUS returned 1 (ON)
After this I used Google voice and then the power button to turn off the screen:
/cygdrive/c/xxxb: adb shell aic3254pd status
Power status of aic3254 chip: OFF
/cygdrive/c/xxx: adb shell dmesg | grep aic3254_
...
<6>[ 470.774963] aic3254_ioctl: Query for AIC3254_POWERSTATUS returned 1 (ON)
<6>[ 608.652496] aic3254_ioctl: index 1 for 40047321
<6>[ 608.652709] aic3254_set_config: table(0x40047321) index(1)
<6>[ 608.652801] aic3254_set_config: miniDSP command len = 32
<6>[ 608.653015] aic3254_set_config: rx mode 29, tx mode 15
<6>[ 608.653106] aic3254_config: size = 32
<6>[ 608.658111] aic3254_config: size = 23
<6>[ 608.659820] aic3254_config: size = 20
<6>[ 608.660278] aic3254_set_config: configure minidsp done
<6>[ 608.660614] aic3254_ioctl: index 29 for 40047312
<6>[ 608.660705] aic3254_set_config: table(0x40047312) index(29)
<6>[ 608.660919] aic3254_set_config: enable tx
<6>[ 608.661315] aic3254_config: size = 12
<6>[ 608.733917] aic3254_ioctl: index 23 for 40047321
<6>[ 608.734008] aic3254_set_config: table(0x40047321) index(23)
<6>[ 608.734222] aic3254_set_config: miniDSP command len = 32
<6>[ 608.734313] aic3254_set_config: rx mode 29, tx mode 29
<6>[ 608.734436] aic3254_config: size = 32
<6>[ 608.737457] aic3254_set_config: configure minidsp done
<6>[ 608.737670] aic3254_ioctl: index 15 for 40047312
<6>[ 608.737792] aic3254_set_config: table(0x40047312) index(15)
<6>[ 608.737976] aic3254_set_config: enable tx
<6>[ 608.738372] aic3254_config: size = 23
<6>[ 608.738922] aic3254_config: size = 20
<6>[ 614.000122] aic3254_ioctl: index 13 for 40047313
<6>[ 614.000396] aic3254_set_config: table(0x40047313) index(13)
<6>[ 614.000549] aic3254_set_config: enable rx
<6>[ 614.001068] aic3254_config: size = 15
<6>[ 614.001892] aic3254_config: size = 11
<6>[ 616.998382] aic3254_ioctl: index 1 for 40047321
<6>[ 616.998565] aic3254_set_config: table(0x40047321) index(1)
<6>[ 616.998687] aic3254_set_config: miniDSP command len = 32
<6>[ 616.998931] aic3254_set_config: rx mode 13, tx mode 15
<6>[ 616.999359] aic3254_config: size = 32
<6>[ 617.001770] aic3254_config: size = 15
<6>[ 617.006561] aic3254_config: size = 11
<6>[ 617.011535] aic3254_config: size = 23
<6>[ 617.013336] aic3254_config: size = 20
<6>[ 617.059783] aic3254_set_config: configure minidsp done
<6>[ 617.059906] aic3254_ioctl: index 29 for 40047312
<6>[ 617.059936] aic3254_set_config: table(0x40047312) index(29)
<6>[ 617.059936] aic3254_set_config: enable tx
<6>[ 617.059967] aic3254_config: size = 12
<6>[ 617.269744] aic3254_ioctl: index 29 for 40047313
<6>[ 617.269744] aic3254_set_config: table(0x40047313) index(29)
<6>[ 617.269744] aic3254_set_config: enable rx
<6>[ 617.269744] aic3254_config: size = 8
<6>[ 627.686737] aic3254_powerdown: power off AIC3254
<6>[ 627.686859] aic3254_config: size = 32
<3>[ 627.794860] aic3254_config: 3254 power down procedure ,flag 0x24=0x00(0x88)
<6>[ 1173.502197] aic3254_ioctl: Query for AIC3254_POWERSTATUS returned 0 (OFF)
After google voice search and chipset off:
# logcat | grep -i aic
I/AudioHardwareMSM7X30( 1206): aic3254_configure: sound effect (Original)
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 0, 1)
I/AudioHardwareMSM7X30( 1206): aic3254_configure: sound effect (Original)
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 0, 1)
I/AudioHardwareMSM7X30( 1206): aic3254_configure: sound effect (Recording)
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 1, 1)
I/AudioHardwareMSM7X30( 1206): aic3254: change tx mode to 15
I/AudioHardwareMSM7X30( 1206): aic3254_configure: sound effect (Recording)
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 1, 1)
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 1, 0)
I/AudioHardwareMSM7X30( 1206): aic3254: change rx mode to 13
E/HTC Acoustic( 1206): cannot open codec aic3254 device -1
I/AudioHardwareMSM7X30( 1206): aic3254_configure: sound effect (Recording)
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 0, 0)
E/AudioHardwareMSM7X30( 1206): cannot open codec aic3254 device -1
I/AudioHardwareMSM7X30( 1206): aic3254_configure: sound effect (Original)
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 0, 0)
I/AudioHardwareMSM7X30( 1206): aic3254: change tx mode to 29
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 0, 1)
I/AudioHardwareMSM7X30( 1206): aic3254: change rx mode to 29
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 0, 0)
I/AudioHardwareMSM7X30( 1206): aic3254: change rx mode to 13
I/AudioHardwareMSM7X30( 1206): do_aic3254_control (1, 0, 1)
I/AudioHardwareMSM7X30( 1206): aic3254: change rx mode to 29
Sent from my Desire HD using Tapatalk
No complaint here, just reporting so others know.
I flashed CM7 RC2, but it was still necessary to flash mad-#4-aic3254pd_signed.zip again after that and use Google voice to enable the power off of the aic3254.
Can someone explain in easy dummy guide style how to turn off voice after patching this fix. Thanks
Sent from my Desire HD using XDA App
Chezbel said:
No complaint here, just reporting so others know.
I flashed CM7 RC2, but it was still necessary to flash mad-#4-aic3254pd_signed.zip again after that and use Google voice to enable the power off of the aic3254.
Click to expand...
Click to collapse
FYI, things work the same as above for #14
shah_jee said:
Can someone explain in easy dummy guide style how to turn off voice after patching this fix. Thanks
Click to expand...
Click to collapse
I'm assuming that you used Google search and then clicked the microphone. When you are done speaking it should just turn off. If that doesn't help then can you provide more info about what you did and what problem you see.
From a shell:
Code:
$ cat /proc/loadavg
1.60 1.31 1.26 2/1446 19315
According to a.o.
https://www.centos.org/docs/5/html/5.2/Deployment_Guide/s2-proc-loadavg.html, 2/1446 means that I have 2 CPUs and 1446 tasks waiting to be run.
1446 tasks? On a heavily loaded workstation I seldom see more than a couple of 100 tasks. A simple server shows just over 100 tasks. So how come the Note has so many tasks? Besides,
Code:
$ps|wc -l
224
Given that I sometimes get load values of around 80 I start getting doubts that the numbers produced by /proc/loadavg are useful.
Does anyone have any ideas what could cause these high numbers for loads and tasks?
sciurius said:
Does anyone have any ideas what could cause these high numbers for loads and tasks?
Click to expand...
Click to collapse
Threads. Run "adb shell top -t" and you'll break out each thread:
Code:
User 31%, System 4%, IOW 0%, IRQ 0%
User 111 + Nice 297 + Sys 62 + Idle 828 + IOW 0 + IRQ 0 + SIRQ 0 = 1298
PID TID PR CPU% S VSS RSS PCY UID Thread Proc
3670 11496 2 22% R 504052K 49724K bg u0_a25 MediaScannerSer android.process.media
11192 11192 1 1% R 1792K 1164K shell top top
9091 9114 0 1% S 487544K 40000K bg u0_a170 Thread-416 com.mobidia.android.mdm:remote
2342 5579 3 1% S 701848K 101820K fg system Binder_D system_server
2342 2342 1 1% S 701848K 101820K fg system system_server system_server
2342 2430 0 0% S 701848K 101820K fg system ActivityManager system_server
2342 4431 1 0% S 701848K 101820K fg system Binder_A system_server
3957 4175 0 0% S 549604K 47424K bg u0_a16 NetworkLocation com.google.process.gapps
2342 3887 1 0% S 701848K 101820K fg system Binder_5 system_server
7563 7563 2 0% S 492308K 37216K fg u0_a39 ndroid.calendar com.google.android.calendar
2342 5594 2 0% S 701848K 101820K fg system Binder_E system_server
3555 3555 3 0% S 534276K 67664K fg u0_a121 ndroid.systemui com.android.systemui
2342 4165 1 0% S 701848K 101820K fg system Binder_6 system_server
690 690 0 0% S 0K 0K root ksmd
<snip>
I see. I'm used to applications that have one or two threads, but a typical Android app seems to have at least 10. That adds up quickly.
This has been driving me bananas because I can't seem to get it to work.
I want to gradually change the opacity of a layer between 0 and 100 over the course of 1 hour.
I thought setting the value of the opacity property using a counter might work, but it seems to just output a single value.
Any suggestions?
you can write a multi line script like
----------------------------------------------------------
if {dh11}==1 then var_my_opacity= 100
end
if ---- then ----var_my_opacity=50
end
.....
-----------------------------------------------------------
with all var hour ({dh11}) you want and all hour value (1,2,3, >3 and < 5)..... you want
and set you wanted item opacity to "var_my_opacity"
I think part of the problem is I found a bug in the lua interpreter. If I set opacity using a counter to vary between 0 to 100 in 10 seconds and reverse, I get the expected slowly flashing behavior.
{c_0_100_10_st}
But, if I do the same thing as part of a conditional:
({dh24}>=23) and {c_0_100_10_st} or 0
That statement just outputs a fixed value and stops.
Sent from my SM-N910T3 using XDA-Developers Legacy app
and why a "or 0" ?
1 or 0 = 1
0 or 0 = 0
so the "or" function with 0 do nothing.
and a "and" function give "0" only if one of the 2 member is "0", otherwise it is "1"
{dh24) never go up to 23. Hour go to 0 -> 23. So {dh24} can just reach 23 one time otherwise it is "0" from 0 to 22.
dersie said:
and why a "or 0" ?
1 or 0 = 1
0 or 0 = 0
so the "or" function with 0 do nothing.
and a "and" function give "0" only if one of the 2 member is "0", otherwise it is "1"
Click to expand...
Click to collapse
I think you have misunderstood the construct of the if / then command in LUA
pseudo code: If x=1 then y else z
is written thusly: (x==1) and y or z
Think of the brackets as the 'if' command, the 'and' as the 'then' command, and the 'or' as the 'else' command.
Hello community,
I (and others) have some strange behaviour on my new A52s (A528B). After some minutes or an hour, the first (silver / little) 4 cores of the A55 snapdragon goes to fixed maximum frequency of 1804 MHz (not 100% usage, just frequency) and never releases again back to the minimum frequency. I'm im contact with Samsung since days but got no senseful answer until now. The problem can be reproduced in Safe mode/factory reset (checked with adb). I did a bunch of traces and I can drill it down to the Samsung argos CPU booster. This faulty call comes from UFS = File system in case of big transfers. But most times it's simply enough to make a screenshot with Power+Lower. Releasing the boosting frequency most times fails after this and max. frequency remains until next reboot:
Code:
not ok:
<6>[ 191.996499] [3: argosd: 3100] sec_argos:argos_pm_qos_notify() name:UFS, speed:598Mbps, prev level:0, request level:-1
<6>[ 191.996509] [3: argosd: 3100] sec_argos:argos_freq_lock() update cpu freq 0
<6>[ 191.996514] [3: argosd: 3100] set_freq_limit: cflm: id(3) freq(0)
<6>[ 191.996519] [3: argosd: 3100] cflm_freq_decision: input: type(3), min(0), max(0)
<6>[ 191.996530] [3: argosd: 3100] cflm_update_current_freq: current freq: s(1804800 ~ 1804800), g(691200 ~ 2400000), p(806400 ~ 2400000)
ok:
<6>[ 46.281795] [3: argosd: 3100] sec_argos:argos_pm_qos_notify() name:UFS, speed:521Mbps, prev level:0, request level:-1
<6>[ 46.281806] [3: argosd: 3100] sec_argos:argos_freq_lock() update cpu freq -1
<6>[ 46.281811] [3: argosd: 3100] set_freq_limit: cflm: id(3) freq(-1)
<6>[ 46.281816] [3: argosd: 3100] cflm_freq_decision: input: type(3), min(-1), max(0) CFLM_ARGOS = 3, /* argos */
<6>[ 46.281895] [3: argosd: 3100] cflm_update_current_freq: current freq: s(691200 ~ 1804800), g(691200 ~ 2400000), p(806400 ~ 2400000)
What is your opion about this ? Maybe a software or hardware fault ? Is this maybe an expected behaviour ? Should I return or repair the phone ? BTW the battery life time is 1-2 days with 6h SOT @ 120Hz, sounds good to me. But I'm not sure if more energy is wasted than necessary and if the CPUs could be damaged over time. Any opion and reaction - maybe by an kernel developer/expert - would be great.
Some info:
Firmware/kernel A528BXXS1AUHA on phone has signature from 2019 = "S", at https://opensource.samsung.com/ firmware A528BXXU1AUH3 U=2021 exists, I don't understand this why
Code:
config ARGOS
bool "Throughput monitoring Feature"
default n
help
This option enables monitoring the data throughput and doing several actions for
enhancing the performance such as adjusting the CPU freqency, allocating the tasks
to the appropriate CPU and so on
[email protected] {
net_boost,label = "UFS";
net_boost,node = [00];
net_boost,sysnode = "/sys/class/sec/ufs/transferred_cnt";
net_boost,table_size = <0x1>;
net_boost,table = <0x320 0x0 0x0 0xdc500 0x0 0x0 0x0 0x0 0x0 0x0>; 320 = 800 dc500 = 902400
};
Also, I don't know a possibility to use root/twrp on it, it doesn't exist. So I can't change the governor/set the frequencies manually. Userspace governor is not present on the phone.
Thank you so much for any reaction !
Hi,
Recently my screen started turning on and off suddenly (like this video). However the blinking does not happen in Recovery Mode or Bootloader. Also doesn't happen in Ambient mode. So I opened logcat and I see this:
Code:
03-10 12:06:34.915 1044 1191 I SDM : HWEventsDRM::HandlePanelDead: Received panel dead event
03-10 12:06:34.915 1044 1191 D IRIS_LOG_SERV: SetPowerMode-0,1
03-10 12:06:34.915 1044 1191 D IRIS_LOG_SERV: SetPowerMode-0,mIrisServiceMode:0
03-10 12:06:34.915 1044 1191 I SDM : HWCSession::DisplayPowerReset: Powering off display = 0
03-10 12:06:34.915 1044 1191 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 56-0, teardown = 1
03-10 12:06:34.916 1500 1939 D [GF_HAL][CustomizedDevice]: [handleNetlinkMessage] GF netlink thread received msg SCREEN_OFF(2)
03-10 12:06:34.916 1500 1939 D [GF_HAL][EventCenter]: [postEvent] enqueue event<-998>
03-10 12:06:34.916 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Get event -998 end
03-10 12:06:34.917 1500 2293 D [GF_HAL][ShenzhenSensor]: msg : 16
03-10 12:06:34.917 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] request token: 76, target: 1000, cmd id: 11
03-10 12:06:34.917 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] carveout_ion_handle_fd = 0,carveout_ion_handle_len = 0
03-10 12:06:34.929 1500 2293 D [GF_HAL][HalContext]: [invokeCommand] err = 0, errno = GF_SUCCESS
03-10 12:06:34.929 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Wait get event
03-10 12:06:34.947 1044 1191 I SDM : DisplayBase::SetDisplayState: active 0-0 state 0-0 pending_power_state_ 0
03-10 12:06:34.947 1044 1191 I SDM : HWCSession::DisplayPowerReset: Setting display 0 to mode = 2
03-10 12:06:34.947 1044 1191 I SDM : DisplayBase::SetDisplayState: Set state = 1, display 56-0, teardown = 0
03-10 12:06:34.949 1500 1939 D [GF_HAL][CustomizedDevice]: [handleNetlinkMessage] GF netlink thread received msg SCREEN_ON(3)
03-10 12:06:34.949 1500 1939 D [GF_HAL][EventCenter]: [postEvent] enqueue event<-999>
03-10 12:06:34.949 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Get event -999 end
03-10 12:06:34.949 1500 2293 D [GF_HAL][ShenzhenSensor]: msg : 16
03-10 12:06:34.949 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] request token: 77, target: 1000, cmd id: 11
03-10 12:06:34.949 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] carveout_ion_handle_fd = 0,carveout_ion_handle_len = 0
03-10 12:06:34.960 1500 2293 D [GF_HAL][HalContext]: [invokeCommand] err = 0, errno = GF_SUCCESS
03-10 12:06:34.960 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Wait get event
03-10 12:06:35.072 1044 1191 I SDM : StrategyImpl::SetIdleTimeoutMs: Idle timeout set to zero for command mode panels
03-10 12:06:35.072 1044 1191 I SDM : DisplayBase::SetDisplayState: active 1-1 state 1-1 pending_power_state_ 0
03-10 12:06:35.072 1044 1191 I IRIS_LOG_SERV: SetColorModeRI(7, 0)
03-10 12:06:35.080 1044 1210 I SDM : HWCColorModeStc::ApplyCurrentColorModeWithRenderIntent: Applying Stc mode (gamut 1 gamma 1 intent 1), curr mode 7, render intent 0, hdr present 0
It happens exactly every 5 seconds. I tried different solutions, tried flashing new rom, tried factory reset, but the problem remains. Also whenever the screen blinks it turns yellow. If I open a full screen app the screen is back to normal colors then turns yellow again after it blinks. Screen is not yellow in recovery so I'm not sure what the problem is. Anyone has any advice?
thethiny said:
Hi,
Recently my screen started turning on and off suddenly (like this video). However the blinking does not happen in Recovery Mode or Bootloader. Also doesn't happen in Ambient mode. So I opened logcat and I see this:
Code:
03-10 12:06:34.915 1044 1191 I SDM : HWEventsDRM::HandlePanelDead: Received panel dead event
03-10 12:06:34.915 1044 1191 D IRIS_LOG_SERV: SetPowerMode-0,1
03-10 12:06:34.915 1044 1191 D IRIS_LOG_SERV: SetPowerMode-0,mIrisServiceMode:0
03-10 12:06:34.915 1044 1191 I SDM : HWCSession::DisplayPowerReset: Powering off display = 0
03-10 12:06:34.915 1044 1191 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 56-0, teardown = 1
03-10 12:06:34.916 1500 1939 D [GF_HAL][CustomizedDevice]: [handleNetlinkMessage] GF netlink thread received msg SCREEN_OFF(2)
03-10 12:06:34.916 1500 1939 D [GF_HAL][EventCenter]: [postEvent] enqueue event<-998>
03-10 12:06:34.916 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Get event -998 end
03-10 12:06:34.917 1500 2293 D [GF_HAL][ShenzhenSensor]: msg : 16
03-10 12:06:34.917 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] request token: 76, target: 1000, cmd id: 11
03-10 12:06:34.917 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] carveout_ion_handle_fd = 0,carveout_ion_handle_len = 0
03-10 12:06:34.929 1500 2293 D [GF_HAL][HalContext]: [invokeCommand] err = 0, errno = GF_SUCCESS
03-10 12:06:34.929 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Wait get event
03-10 12:06:34.947 1044 1191 I SDM : DisplayBase::SetDisplayState: active 0-0 state 0-0 pending_power_state_ 0
03-10 12:06:34.947 1044 1191 I SDM : HWCSession::DisplayPowerReset: Setting display 0 to mode = 2
03-10 12:06:34.947 1044 1191 I SDM : DisplayBase::SetDisplayState: Set state = 1, display 56-0, teardown = 0
03-10 12:06:34.949 1500 1939 D [GF_HAL][CustomizedDevice]: [handleNetlinkMessage] GF netlink thread received msg SCREEN_ON(3)
03-10 12:06:34.949 1500 1939 D [GF_HAL][EventCenter]: [postEvent] enqueue event<-999>
03-10 12:06:34.949 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Get event -999 end
03-10 12:06:34.949 1500 2293 D [GF_HAL][ShenzhenSensor]: msg : 16
03-10 12:06:34.949 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] request token: 77, target: 1000, cmd id: 11
03-10 12:06:34.949 1500 2293 D [GF_HAL][CaEntry]: [sendCommand] carveout_ion_handle_fd = 0,carveout_ion_handle_len = 0
03-10 12:06:34.960 1500 2293 D [GF_HAL][HalContext]: [invokeCommand] err = 0, errno = GF_SUCCESS
03-10 12:06:34.960 1500 2293 D [GF_HAL][EventCenter]: [threadLoop] Wait get event
03-10 12:06:35.072 1044 1191 I SDM : StrategyImpl::SetIdleTimeoutMs: Idle timeout set to zero for command mode panels
03-10 12:06:35.072 1044 1191 I SDM : DisplayBase::SetDisplayState: active 1-1 state 1-1 pending_power_state_ 0
03-10 12:06:35.072 1044 1191 I IRIS_LOG_SERV: SetColorModeRI(7, 0)
03-10 12:06:35.080 1044 1210 I SDM : HWCColorModeStc::ApplyCurrentColorModeWithRenderIntent: Applying Stc mode (gamut 1 gamma 1 intent 1), curr mode 7, render intent 0, hdr present 0
It happens exactly every 5 seconds. I tried different solutions, tried flashing new rom, tried factory reset, but the problem remains. Also whenever the screen blinks it turns yellow. If I open a full screen app the screen is back to normal colors then turns yellow again after it blinks. Screen is not yellow in recovery so I'm not sure what the problem is. Anyone has any advice?
Click to expand...
Click to collapse
Definitely need to run the msm tool on your device. This will fix. Some reason your display is being powered off intermittently. Msm tool will return to stock condition. Google how to use. https://onepluscommunityserver.com/list/Unbrick_Tools/
mattie_49 said:
Definitely need to run the msm tool on your device. This will fix. Some reason your display is being powered off intermittently. Msm tool will return to stock condition. Google how to use. https://onepluscommunityserver.com/list/Unbrick_Tools/
Click to expand...
Click to collapse
Thank you I'll let you know when I try it.
Edit: Same problem unfortunately.