Database Users

Reading current draw from charger chip.

Hello,
the charging chip in the Note (MAX17042) supports current reading, but the kernel driver for it does not support this feature. I hav no datasheet for 17042, but there is one available for 17047, which seems similar enough.
It is possible to read the registers with i2c-tools. Register 10 should read the current, but the value seems to fluctuate too much to be useful. Register 11 should read current average over the last 10 seconds (configurable), and seems much more useful.
Disconnected from charger, I see raw values from -1 (when idle, screen off, bluetooth and Wifi enabled), to -33 (benchmark running, screen at maximum brightness). So one unit seems to be about 20-50 mA.
The scale can be changed (by writing CGAIN register, 46), but at first look it does not appear to make things better.
I am looking for help from people who might have ideas on how to find the exact unit value, and maybe how to get a better resolution. After those issues are solved, it should be easy to integrate it into the kernel.
The tools to read and write the registers are i2cget and i2cset. You can compile them yourself from source (with ndk), or use precompiled binaries from http://my.svgalib.org/android .
The command to read the average current value is:
i2cget -y -f 9 0x36 11 w
The command to write the CGAIN value is:
i2cset -f -y 9 0x36 46 0x4000 w
(0x4000 is the default value).
EDIT:
Register 24 should be written by the application (Samsung) with the design capacity of the battery. I read this value as 2000, which for a 2500mAh battery gives units of 1.25mAh, or R_SENSE=0.004 Ohm.

I have nothing useful to contribute to this but to say how great it would be to be able to monitor the draw of current as we use it.
Congrats for this great find. I hope you succeed in adding this feature to our Note

[undervolting][ics][only siyah]how to check the stability of your undervolts!

ok guys first of all ill start by saying that none of this i mine...its all stuff that i understood from different threads.I am a complete noob so there are gonna be many things ill not be able to understand to you!
i am gonna thank these brilliant people first
-gokhanmoral
-pikachu
-droidphile
-andre
and others(who have started undervolt threads) ive missed!
ok now to the main point!
this works only on ics siyah kernels as currently GM is the only one who supports the following commands!
what you need!!
-terminal emulator
-volt tweaking app (set cpu, voltage control),i wont prefer extweak or xxtweak as you cant edit a perticular freq volt with them
-patience
ok now start by selecting the freq on which you wanna work..undervolt it to your desired volt
e.g ive undervolted my 200mhz to 925mv
now open terminal emulator
type:
su
LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int 14
and press enter
ok what this command does is that it changes your touch screen freq to the number last in the command line..in this case 14 it is
you can alter these numbers as follow:
0-1600 6-1000 12-400
1-1500 7-900 13-300
2-1400 8-800 14-200
3-1300 9-700 15-100
4-1200 10-600
5-1100 11-500(stock)
so as you can see the above command line sets my touch freq to 200 mhz.
ok so as soon you press enter in the terminal emulator your touch freq is changed to the freq of your liking..(remember use the above states numbers and not the freq itself in the command line) and some how that perticular freq takes load in such a pattern which i could not recreate with any stress stability test or even mxvideo test( you can find about it in various threads) and hence if the undervolt is below the stability threshold your phone will crash,hang,reboot...but you will get to know which volt value on which freq is unstable.
After setting the touch screen freq try(you can use voltage control to confirm if your touch freq has changed or not) use your phone normally...scrolll between pages..browse..play games..and if the perticular freq volt is unstable your phone will indefinitely crash within 5-10 min..!
do this procedure for every freq and ull definitely will get yourself the most stable UV's your device can handle!
you can read much about this and other stuff in droidphiles thread
http://forum.xda-developers.com/showthread.php?t=1572937
thank me if it helped!!

Hmm... do we really need another one of these threads lol
Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!

i jus tought of sharing this as it seems to me that this kinda crash which the touchscreen freq produces isnt reproduced by any stability test..hence another way for testing your stability...besides i myself was facing few crashes with my settings lately and this cured it...!

Your CAPS key is broken ...

haha not really...HERE YOU GO...i had words in caps up there aswell...dun knw what went wrong..btw...love your dp!!

Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.

Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...

Tye:P said:
Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.
Click to expand...
Click to collapse
yeah i myself was having issues with uv's..found this way indirectly with the help of droidphile...would love to see if it helped you!
busky2k said:
Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...
Click to expand...
Click to collapse
mate your issue can be solved simply by installing extweak and setting the smooth scaling level to your max freq..on default the level is 1200..but this issue was solved in the 3.2.7.X versions of siyah..which version are you using?

i'll try to UV with xxtweak

doesnt matter what uv tool you use...but i should be an app which uv's indivisual freq's and not all at once as then you wont be able to figure out which volt is giving error on which freq!

Just another list of questions...

Hi all, I know there are threads already created for questions etc but I've an extensive list of them and I don't think its appropriate to spam them in someone else's thread. And I'll update the first post of the answers and replies I've received for the questions I've posted!
My phone's information: will5's MIUI ROM 2.5.25 GB 2.3.7
My list of questions
Android OS
::Hard rebinding hard keys::
Is that possible? My power button recently got damaged and its really tough to press the power button now which is quite a problem, is there any way to rebind the power button to say the camera button? (specifically the 2nd-click of the camera button, not the first click (focus)) MS2Toolbox is able to wake screen with the camera button but thats just soft-sided and I need to hard bind for turning on the phone and using the recovery etc... :crying:
::Allow app to stay active when screen-off and when not in foreground:: http://forum.xda-developers.com/showpost.php?p=29658020&postcount=95
I want to let my app, specifically Opera Mobile, to be constantly active as I run a script (user javascript) on it which repeats its function periodically. Is there a way to keep it active throughout deep-sleep, or when in the background? Currently its working well when I switch the screen off as long the app was in the foreground. The script and Opera Mobile still runs perfectly and I do not experience battery drain (weird). I have been doing so for the past few months and it takes probably only 30% of my battery overnight when I sleep despite the periodic data connection. However, this didn't happen on the MIUIv4 ROM when I tested it. The app is 'frozen' or suspended, it seems, the moment I switch the screen off. Tried apps which disabled deep sleep etc but didn't work. Any ideas?
Overclocking
::What are the default VSELs for the respective frequency for MS2?::
I know there's one here http://forum.xda-developers.com/showpost.php?p=11620994&postcount=1 by santiemanuel, but it gives VSELs WAY above those I'm using or the defaults from MS2Toolbox. Say, for 300MHz, the stock vsel is 33 and 30 is considered unstable. How ever the default in MS2Toolbox for that frequency is 17 if I'm not wrong. I'm using that at the moment and it seems to be running fine (used powersave governor to enforce 300MHz to test it out). Just to confirm, should I really follow that table?
WiFi
::Changing Milestone 2's WiFi MAC address::
Hi guys, I've been trying to look for a way to change my M2's MAC address but have not been able to get it to work.
I've googled up for methods but the common ones do not work.
Tried so far:
- The nvram.txt file
Can't find it in the usual folders stated.
- busybox ifconfig tiwlan0 hw ether <MAC>
- busybox ip link set dev tiwlan0 addr <MAC>
Tried these two commands but didn't work either in terminal emulator. Even did the off-on-immediately spam commands but no luck.
Unsorted
Code:
http://forum.xda-developers.com/showpost.php?p=29675172&postcount=905

::SOLVED::
Overclocking
::How do I check the current VSEL and frequency at any point in time?::
I'm trying to underclock and ultra-undervolt to save as much battery as possible and want to know how's the selected governor working in order to manually optimize the settings to my preferences.
::How do I know its an unstable VSEL?::
Q: Quite vague a question but... as said in the first question, I'm running 300MHz at a VSEL of 17 instead of 33, nearly half of the stock. How would I be able to tell if its unstable? When I'm running in powersave governor, it shows that the 'system' process stopped responding at boot and I've the wait/close option, but after selecting wait the dialog disappears and the phone still works as per usual. However its very sluggish, clearly because of the underclock. Regardless, does the system process being unresponsive at the start shows it is unstable?
A: djlooka via PM
djlooka said:
...My suggestion is: try with that setvsel app for defy (see my answer in the CM9 thread) which comes with a useful mini-stress tester app (you can install it from within the main OC app). It can stress test every single freq step, so you can find its 'sweet-spot-vsel'.
One could also think that there's some advantage in fine tuning the middle steps. IMHO it's wasted time
After some days of tweaking, I realized that our phone will stay in the two the middle steps (combined) for less than 5% of the time. So even if you could save some % of the power by losing 1 or 2 vsel points (let's say 10% of the original vsel), the "on the road" gain would be infinitesimal (10% x 5% = 0.5%).
Anyway it's fine to OCD a bit even about those 2 steps
My final word is: find the lowest possible vsel for both the top and bottom freqs by stress testing. To be extra careful, raise them by one point for rock solid.
E.g.: 300-22 is the best combo for my lowest step -> I put 300-23, and so on.
Click to expand...
Click to collapse
::3 steps shown in the bootloader but 4 shown in MS2Toolbox::
Q: This has been bugging me recently. I've read recently that the M2 has 4 steps for its CPU. So the CPU actually follows the 4 steps shown in MS2Toolbox or the 3 in the bootloader? Note: When I change the values in the bootloader, the values changes respectively in MS2Toolbox for the 2nd,3rd,4th rows (did not tick auto apply in M2T to prevent overlaps with bootloader settings). But the 1st row shows values lower than the one in the 2nd row automatically.
A: djlooka @ http://forum.xda-developers.com/showpost.php?p=29806494&postcount=908
djlooka said:
...Our phone, instead has 4 steps (300, 600, 800, 1000 MHz - the same as the Defy+).
AFAIK, when you set a configuration which allows only 3 steps (in the bootmenu), the hw internally adjusts to have the last 2 steps equal (e.g. 300, 600, 800, 800 MHz).....
Click to expand...
Click to collapse
Applications
MX Player - Does not require codecs. If it requests for ARMv7 NEON codec, get the NEON version of the player instead.

Podcast Addict Issues

I am reposting this because the issue remains and when I first posted in July I received a single response from a user that was also experiencing this.
I can't seem to find an answer anywhere. Basically when listening to a podcast with the Podcast Addict player at ~1.9x or faster the audio stutters and produces a static sound distorting the audio. Waking the screen immediately stops the issue. The issue gets worse if you increase the speed or enable the "skip silence" feature.
I made sure to disable any battery saving options for the app and enabled any workaround options within the app. I even contacted the developer who pretty much just said that the phone is governing the processor too low with the screen off. I have tested other podcast apps and they seem to function fine even at faster playback speeds. For some reason, this only affects Podcast Addict.
Is anyone else experiencing this? Anybody have a suggestion for a fix? I am completely stock OOS version 4.5.14. I have the 8/128GB model if it makes a difference.
It seems to have issues even if the screen is on and the app is not in the foreground. Within ~5 seconds of being put into the background, it begins to stutter.
I have been working with OnePlus' own "bug hunter team" to fix this but I have not heard from them in over a month since I reported it to them. They asked me clear cache and reproduce the effect on my device and send them logs, which I did but I haven't heard anything.
Can anyone test this and tell me if they don't have an issue with screen off?

I also couldn't get rid of the static sound in Podcast Addict when playing back at fast speeds (for me, around 1.7x or faster). This was on a Galaxy S8+. I've been listening to a podcast audiobook Wildbow's "Worm" (which weighs in in at 6,680 pages) and the static sound was killing my ears. Gave up on Podcast Addict today, and switched to Pocket Casts and not having any static problems now when listening at faster speeds.

I think I found the problem with Podcast Addict stuttering... it's the logging.
I've gotten into the habit of pinning my CPU frequency to 299 MHz maximum to save battery, and PA would stutter, so I dug into ADB to figure out what was going on. After getting rid of the hidden adware that the phone's manufacturer kept running in the background, CPU usage dropped enough that I could run PA without much stutter, but if I opened the notifications or ran any other app, it'd start stuttering again. So I dug further.
And it seemed that as I increased maximum CPU speed from 299 MHz to 1.3 GHz, CPU utilization would increase, too, if Podcast Addict was running. That was strange behavior, so I knew something was going on.
Apparently the system is somehow hooking into PA and logging everything PA is logging internally. When I run:
adb logcat -D -v long > c:\test\logcat.log
... the logcat.log file swells up to 80 - 110 MB in a mere minute. Without PA running, it's generally around 113 KB / minute.
So I started killing logging processes.
I killed logcat, and CPU usage dropped dramatically, but logd started hogging the CPU.
So I killed logd. It restarted, but no longer hogged the CPU.
So CPU utilization dropped from ~83% for PA, utilizing 4 to 5 cores, to ~60% for PA, utilizing 3 cores. Even with the CPU pinned to a maximum 299 MHz, playback was smooth.
As for logcat, after killing it, if you run it from your computer:
adb logcat -D -v long > c:\test\logcat.log
it'll begin log-spamming again (its the AudioTrack thread which is spamming the log) and the phone's CPU usage spikes again, but now, after having killed logcat once, when I stop logcat logging via ADB, logcat stops spamming the log and the phone's CPU usage returns to using 3 cores.
Get the CPU usage info:
adb shell dumpsys cpuinfo
inside that info, you'll see the PID of the applications. Look for logcat and logd. There might be more than 1 logcat, kill them all.
Let's say logcat is running two instances, with PID 239 and PID 760, for example (it'll be different each time you boot the phone), and logd with PID 13020.
Then issue the following commands from a command prompt on your computer:
adb shell
su
kill 239
kill 760
kill 13020
exit
exit
On my computer, if I type the commands too fast, ADB can't keep up, and ADB will crash, so give it a few seconds in between each command.
The above-described log-spamming behavior reoccurs upon reboot, so you'd have to do this after each boot.
Now I can listen to podcasts (I usually listen at 2x, sometimes as high as 3x for podcasters who talk slowly) without stutter, with the octa-core CPU pinned to 299 MHz maximum.

[GUIDE] Using OnePlus 8 on LineageOS 18.1 as gaming console (HDMI out etc)

Hi guys, I just got a OnePlus 8 and loaded LineageOS 18.1 onto it and wanted to use it to play games on my 4K TV.
The following is a list of the problems and solutions I encountered to get there.
First, I used a USB-C to HDMI adapter on my 4K TV.
I connect my DualShock 4 to it via bluetooth for a console experience.
a) Problem 1 - Full screen output is shifted to the right slightly (black bar on left side)
Solution 1 - I rooted and used this Magisk module here with the OnePlus 8 preset. It requires enabling in Developer settings (Cutouts) after installation.
https://forum.xda-developers.com/t/module-n3o-no-nonsense-notch-overlay.4226413/
b) Problem 2 - Aspect was weird (black bars on top and bottom)
Solution 2 - SecondScreen with the resolution set to 1080p fixed this. Full screen on TV.
c) Problem 3 - Despite setting SecondScreen to 1080p, phone was outputting to my 4K TV at 4K30Hz (and presumably just upscaling). Horrible input lag and frame rates. I could find NO SETTING to change this anywhere. ADB commands such as adb shell wm size etc had no effect and I think are just what SecondScreen uses behind the scenes as they produced a similar effect. But when I connected it to my 1080p monitor there were no issues, things were smooth and responsive so....
Solution 3 - I bought something like one of these: an EDID emulator for HDMI and it is working like a charm. Fools the phone into thinking the TV's max res is 1080p and so the phone outputs at that. Now buttery smooth frame rates.
https://www.amazon.com/Passthrough-Generrtion-Headlesskeep-Extenders-3840x2160/dp/B08RCMFLMK/
d) Problem 4 - Brightness on phone weirdly tied to brightness on TV. I had to run it at full backlight to get full brightness on TV
Solution 4 - Disabling the display anti-flicker setting seemed to unlink the brightness on the phone and TV. Now I can play at normal brightness on TV with zero on phone (set by SecondScreen)
e) Problem 5 - Using a phone as a video game console uses battery.
Solution 5 - Got a new USB-C adapter that allows charging. Not this, but something like this. Confirmed can charge and have video out to my TV at the same time.
https://www.amazon.com/Multiport-Delivery-Converter-Compatible-Chrome-Book/dp/B087Q62H89/
And there you go. So far this seems totally viable and cool, and I am a fussy, hard-to-please kind of person.
I am looking forward to using this to keep playing some RPGs I would like to get through, with a console experience at home but still able to pick up and continue a bit when out.
Hope this helps someone! Spent hours googling and trying to figure this stuff out.

It's **** like this that got me into modding droids in the first place. You are a legend and a gangster. Keep on doing whatever. XD

This is an excellent guide and gives me more confidence to install the mod and mess with it. Thanks
Useful info like this will hopefully increase the likelihood that the community will use roms to implement the desktop experience. Maru was one example I saw a redditor post but it's in early development.
Also check out Taskbar which is an excellent app for DTE on non-rooted phones