yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Rob2222:
According to my understanding of the datasheet the IC is factory calibrated in hardware, cause they did not mention that you have to initialize the current calibration. So it should be already in hardware.

The IC powers up with default values of 0x4000 in CGAIN(0x2E) and 0x0000 in COFF(0x2F). From this state current measurement should be direct usable with a resolution of 156.25µA when using a 10mOhm resistor.

I hope they have assembled a sense resistor. ^^

Which register they initialize with 0x0000?

Do you think its possible to deliver all interesting registers to /sys/ anywhen? :-D

BR

Robert
[Galaxy S III Original Android Development] AndreiLux:
I fixed GPU control now. Have fun.

AOSP is not a personal priority for me, so not anytime soon. When Gokhan implements a stable and good dual-compatibility for his kernel I will implement that into mine when I have nothing else to do.

That is correct, also how I understood it. I already wrote the current output to normalize for 156.25µA several days ago. They initialize CGAIN, as I said;

i2c_data[1] = 0x00;
i2c_data[0] = 0x00;
max17047_i2c_write(client, MAX17047_REG_CGAIN, i2c_data);

I didn't continue work on the fuelgauge yet because I was busy with the GPU stuff, so that'll come next hopefully.

The GPU change is fairly big so I'd like people to comment what their experience is in terms of fluidity in games and especially battery consumption and thermals. Benchmarks will be slightly lower, I'm getting roughly 95 fps instead of 99-100 in Egypt offscreen due to the change.
[Galaxy S III Original Android Development] Le Rat Noir:
A problem with gpu_voltage_control

$ echo "900000 XXXXXXX 1000000 1050000" > /sys/class/misc/gpu_voltage_control/gpu_control

$ cat gpu_control

> Step2: always 1200000
[Galaxy S III Original Android Development] Rob2222:
OK. For me it looks like the samsung dev decided to disable coloumb counting with that to switch back to the modelgauge voltage only algorithm.

Ive googled the codeline and found that version here:

/* Use MG1 */
i2c_data[1] = 0x00;
i2c_data[0] = 0x00;
max17047_i2c_write(client, MAX17047_REG_CGAIN, i2c_data);

Here they already comment, that they switch to modelgauge 1 algorithm, I think.

So for my understanding, when you stop initializing this value to zero, coulomb counting should start right off, as you already said. :-)

EDIT: On top of the linked document it says, that the code is based on the max17040. Thats the cause I think. They maybe didnt had the time to implement and test the new feature.

BR

Robert
[Galaxy S III Original Android Development] AndreiLux:
Huh? I don't have that problem, and 1200000 is the max limit I set. Check if you're not putting an extra 0 in there and missed it.

I hope it doesn't break the rest of the modelgauge algorithm when I do that though, would have to implement more stuff.
[Galaxy S III Original Android Development] Rob2222:
Hey Andrei,

I browsed the Samsung kernel source code (update 1) a little bit.

If I get that right, they have a driver for the 17047 and a driver for the 17050 in the source. The 17047 driver is based on the 17040 (which had only voltage tracking).

The 17050 driver seem ready to be configurable to voltage_tracking mode or coulomb_counter mode.

17047 and 17050 is the same IC just different package, right?

So didnt we/you just need to configure the 17050 in coloumb counter mode?

Or do they really use the older "17047 based on 17040" driver in theire kernel? (didnt figured out yet)

config FUELGAUGE_MAX17050
tristate "MAX17050 fuel gauge driver"
default n
depends on BATTERY_SAMSUNG_P1X
help
Say Y to include support
for MAXIM MAX17047 or MAX17050 fuel gauge driver.
This fuel-gauge can be used in voltage-tracking mode
or coulomb-counting mode.

config FUELGAUGE_MAX17050_VOLTAGE_TRACKING
tristate "use MAX17050 fuel gauge only as voltage tracking"
default n
depends on FUELGAUGE_MAX17050
help
Say Y to use MAX17050 fuel gauge
only as voltage tracking.
This mode is for target that consumes low current
like smart-phone.

config FUELGAUGE_MAX17050_COULOMB_COUNTING
tristate "use MAX17050 fuel gauge as coulomb counting (including voltage tracking)"
default n
depends on FUELGAUGE_MAX17050
help
Say Y to use MAX17050 fuel gauge
as coulomb counting (including voltage tracking).
This mode is for target that consumes high current
like tablet.

In the max17050_fuelgauge.c the coulomb counter mode seems to be implemented.

The config snippet above could explain, why we have the IC in voltage tracking mode... Maybe just cause they think we didnt need the coulomb counter mode.

"This mode is for target that consumes high current like tablet." ... Hey, cmon, I bet S3 can drain "high current", too. xD

BR

Rob
[Galaxy S III Original Android Development] :
flash alpha26 and u will get CRT off again
[Galaxy S III Original Android Development] MuertoKo:
You could just drop exFat to keep the good ones here :P So the update to 3.3 could be worth then... Anyway, 2 versions looks like silly (one with and one without exFat and more "updated") and ppl do like exFat for a reason I can't understand so... Sad you wasted hours upstreaming to 3.3 for nothing, some of us would be glad to get rid of exFat support for it but well, you have the lead!

Gratz on the work anyway ;) (Row is working quite nice, as well as FIOPs... as u said, difference might be hard to notice, but at least it's not underperforming in anything I can test)
[Galaxy S III Original Android Development] Tenacious:
I also agree it's a shame to lose features becose of exfat, and you shouldn't blame you self you shod blame lazy users.

I also kinda miss this thread as it was before, this morning I open this thread and what I read some user crying about ctroff effect which is usles in my humble opinion.
[Galaxy S III Original Android Development] LenAsh:
Agree with both posts above. For the tiny vocal minority who whine, the more considered majority would prefer progress and not regression.
[Galaxy S III Original Android Development] habylab:
Going to reinstall the older kernel, fiops is awesome.
[Galaxy S III Original Android Development] jeebspawnshop:
Perhaps 2 version would be silly, but in the end I believe it would be preferable.

For example;

Version "Neanderthal": exFAT support, and no new features.

Version "Evolved": no exFAT support, lots of new features.

I think EVENTUALLY everyone would stop using the Neanderthal Version and opt for something more Evolved ;)

EDIT: Forgot to mention that I'm still on 28.0 and refuse to install any future kernels unless they drop exFAT and bring all those upstream goodies.
[Galaxy S III Original Android Development] mamba720027:
Letting the rom control the cpu in powersaveing mode can cause that although it didn't in 27.2. why? Simply because its changed up the function under the hood with redundancy that is not optimize for the kernel.

Sent from my GT-I9300
[Galaxy S III Original Android Development] AndreiLux:
I won't do that. Sorry.

Now that's just stupid.

What are you talking about. There's nothing changed regarding power savings mode.
[Galaxy S III Original Android Development] mamba720027:
Not by the kernel,was referring to the rom controlling CPU. All it does is switch the cpu to dual core and limit the frequency to 1000mhz to save energy.

So instead of useing powersaveing feature why not use stweaks to do the same by setting the amount of cores u wanna run by limiting the cores using the "hotplug lock" feature in stweaks and can also set the cpu min and max freq as well,more efficient way I think.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Jinsuke32:
Can anyone please upload v28? Dont care much for exfat
[Galaxy S III Original Android Development] Oleh:
AndreiLux, you are right! The powersaveing mode is working well by 27.02. I checked it with CPUSpy.
[Galaxy S III Original Android Development] gundal:
i have posted them, in all the n2 forums, likely they will all bootloop on the s3 becaause the hardware is not as high quality and wont be able to handle the same voltages or cpu speeds. ifyou wanted you could try 3 2 or 1 since teh max cpu is 1600 on those but im pretty sure all the voltages are still too low...
[Galaxy S III Original Android Development] pulsation:
v28 is attached to this post ; its md5 checksum is 8fefadca653b3f9d28a1b6d8526f9e36 ; I couldn't find any statement about this kernel's redistribution policy, so please notify me if I'm wrong sharing it this way.
[Galaxy S III Original Android Development] Stivikivi:
I have a question

The exfat file system, do you mean the internal storage one or the one for the External sd card? If you mean the external sd card I have ext4 anyway so no problems here. ty
[Galaxy S III Original Android Development] LenAsh:
Thanks for the link. Bit misdirected personally as we now have v28, v28.1 and v28.2 but only a specific changelog for V28.1. Guess I'll have to read through the past few pages and try to unravel the sequence of events again...
[Galaxy S III Original Android Development] AndreiLux:
28.2 just fixed the remaining issues regarding STweaks and the scheduler choice/applying on boot.
[Galaxy S III Original Android Development] :
S Beam not working?
[Galaxy S III Original Android Development] jeebspawnshop:
Haha, yea, I'm pretty stupid ;) But my parents thought I was retarded until I was about 15, so I'm not gonna try break the illusion just yet.
[Galaxy S III Original Android Development] 0asis:
Is there anybody that could give me some tips on how to Undervolt this latest version?
[Galaxy S III Original Android Development] :
First, do this: -25mV for each step.

Then, reboot.

Then, do this: +25mV for each step.

If you get random reboots after doing what I said here, please report here, get a logcat, say what you were doing before it rebooted, and Andrei might fix it for you :)
[Galaxy S III Original Android Development] 0asis:
-25 milivolt ? I mean the values are something like 1 000 000.. And what the point to Undervolt and reboot right after to set the same settings as default (-25 like you said and +25 right after)?

Thanks for your time
[Galaxy S III Original Android Development] AndreiLux:
The values in STweaks are in microvolts not millivolts, that's why they're 1000 times higher.

I don't understand the reboot thing either, it's not an effective way to find stable frequencies. But what he means is to start off at a point, reduce the voltage for a given frequency and then try it out how long it will stably run, then go another -25mV down until it crashes. When it crashes, raise it back 25mV. I also suggest running the performance governor while doing so and limiting your max frequency to whatever frequency you're currently testing.
[Galaxy S III Original Android Development] zappoo:
Any idea why CRT off is sometimes broken? ANy chance of a fix?
[Galaxy S III Original Android Development] :
Guess no one got it :P

Do -25mV and then +25mV so you don't undervolt and still can find bugs and report here to improve kernel. The reboot thing is nothing, actually.

Just posted that as a joke, but since no one got it, well, not a joke anymore, I'm just an idiot ;)

---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------

fbsuspend delay, I guess. Needs to set it on the kernel, on Siyah it is set on STweaks, off by default.
[Galaxy S III Original Android Development] gundal:
lmao i totally understood it.

dude asks how do i undervolt

instructions move them all down 1 step reboot, move them all up one step

guy thinks hes done something, but hes still stock lol.
[Galaxy S III Original Android Development] 0asis:
And so, do you advise me to run the performance governor only for the tests and to choose the default one after that I found my settings? Or is it better to let the performance governor?
[Galaxy S III Original Android Development] mamba720027:
Leave the performance gov :D.

No ,use any governor of your choice after testing with performance gov.

Edit: here's a guide covering uv its for siyah kernel but should also work.

xdaforums.com/showthread.php?p=30087683

Sent from my GT-I9300
[Galaxy S III Original Android Development] :
Leave default if you like it ;)

but battery will decrease
[Galaxy S III Original Android Development] mamba720027:
Hey Audrei is their a reason you have them as microvolts? Seems confuseing to use so I use setcpu to UV the cpu part.

Sent from my GT-I9300
[Galaxy S III Original Android Development] :
maybe a larger voltage range so the voltage precision is higher? 1000 meters is more precise than 1 kilometer, and 0.200 is more precise than 0.2.

If you reach the min voltage possible you might not be able to set it on a mV scale.

v----v----v----v----v = in this scale you can't set voltages between the v

vvvvvvvvvvvvvvvvvv = in this scale you can set voltages where the scale above can't
[Galaxy S III Original Android Development] mamba720027:
I somehow understand the last paragraph diagram more,numeric figures was never my strong suit. I get what you mean but dosent the cpu use +25mv rather than the 15mv if u set it in between?

Edit: ok I take back my word,its not confuseing in microvolts,it only looked confusing cause the numbers were long. After trying it I see wats happening :p

Sent from my GT-I9300
[Galaxy S III Original Android Development] tridibsahabd:
S Beam not working is a known issue. I suggest to add it to the list of "known issues"
[Galaxy S III Original Android Development] Tenacious:
AndreiLux is there a way of fixing this vulnerability Root exploit on Exynos in you kernel without waiting for Samsung to do it which will take a some time.
[Galaxy S III Original Android Development] AndreiLux:
I already replied in that thread yesterday with a potential fix (Without breaking the camera, that's what Codeworkx's fix would do on Samsung ROMs). I'm currently testing out my method.
[Galaxy S III Original Android Development] mamba720027:
So this is what my run looks like with the 28.2 kernel. Single core at 1000mhz watching about 1 1/2 hour of movie,phone calls,music,reading,browsing,etc. Must say after useing 28.2 phone feels alot snappier the way apps load and fluidity of transitions.

Sent from my GT-I9300
[Galaxy S III Original Android Development] MuertoKo:
God...

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] :
Since S Beam is not working, I suppose wifi direct isn't working too. Andrei, didn't the new wifi driver break wifi direct and S Beam? Could you compile a test version only returning to old wifi driver?
[Galaxy S III Original Android Development] 0asis:
Single core at 1000mhz? Omg my phone isn't smooth at all when I do this.

Edit: finally 2 min after the boot it seems okay. I'll test
[Galaxy S III Original Android Development] mamba720027:
Sounds good,might get mix results. I'm thinking if it was dualcore mode,I may get same result but just speculation. I know the cpu sleeps good,used up 2% within 3-4hours with WiFi on and yea I was monitoring it :p after I took a good nap myself.

Sent from my GT-I9300
[Galaxy S III Original Android Development] lvoonjian8888:
Actually, I found that the latest 28.2 version cause my phone charging slow. I confirmed is kernel related as with stock kernel, I had no problem. Anyone?

Edited : Fixed. My phone show it's "Charging(USB)". Once I unplugged and plugged in few times then now it's work back! Suck Samsung USB cable..><
[Galaxy S III Original Android Development] hamer221:
Single core at 1000mhz... so why you buy s3? Galaxy ace 1 runs that speed..

Enviado desde mi GT-I9300
[Galaxy S III Original Android Development] DroidRevenge:
+1
[Galaxy S III Original Android Development] mamba720027:
:D believe me quad core full speed ahead.i Just like test how good stuff work at different settings,this way I'll know if it makes a difference or not when im not next to a charger outlet.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Frag1le:
Mhz speed says nothing about CPU performance.

The singlecore 1ghz on the S3 is much faster then on the Galaxy Ace (which is 800 or 832 mhz btw)

I also wonder if all the batterytuning is worth it.

A singlecore that has more load probably uses the same amount of power as 4 cores doing the same tasks but then all have less load.

But for each his own.
[Galaxy S III Original Android Development] MuertoKo:
I thought the same way.. but after seeing 7h screen time? and 21 online mode? That's just crazy... I'm gonna give single core 1000MHz a run just to see if the difference comes from it or maybe it's due to a way lighter usage than I'm used to... Curious only :P
[Galaxy S III Original Android Development] cba1986:
Sorry for repeat myself but i would really want know the difference between AOSP an Stock at kernel level.
[Galaxy S III Original Android Development] criosray:
That's only in case if task is effectively parallelized to multiple cores. In most cases single app will effectively use only 1 core...
[Galaxy S III Original Android Development] Frag1le:
That's true, but I wasn't talking about a single process/task i was talking about multiple processes.
[Galaxy S III Original Android Development] GrayJack:
It will be fun if custom coder be quicker in normal working fix than Samsung coders. Keep it up, Andrei!
[Galaxy S III Original Android Development] sduford:
That's not exactly a fair comparison. Samsung has to first determine the best way to fix the problem, fix it, and then go through a pretty stringent QA process before they can start pushing to 10s of millions of phones.

Different then a single developer coming out with his fix, testing it out on his own phone and perhaps those of a few friends, then release it out to us hackers and hope for the best.
[Galaxy S III Original Android Development] XPLOSIV10:
I use MS Team HD 6.5 Rom + 27.2 Perseus Kernel and also have 7hour screen time on full Brightness Oo

And no changes in the Settings and without using any mods like Supercharger, JuiceDefender etc.

:eek:
[Galaxy S III Original Android Development] 0asis:
Hum. I don't know how you do guys to have a 6 or 7 hours of screen time.. Seems pretty impossible to me. The max that I got is 4 hours or a little more.
[Galaxy S III Original Android Development] orangerot.:
I thought about flashing this Kernel, but since S Beam isn't working I'm afraid to flash it. Will there be soon a fix for that? I think S Beam is a pretty cool feature I don't wanna miss..
[Galaxy S III Original Android Development] mamba720027:
That's what I used to get but now I can easily pass the 6hours mark and that's not a one time thing :cool: . Now I'm trying 700mhz dual core. Maybe 10hours this time? :D:p

Sent from my GT-I9300
[Galaxy S III Original Android Development] AndreiLux:
New version out.
[Galaxy S III Original Android Development] abelle_abelle:
fixed slow charging issue?
[Galaxy S III Original Android Development] JSale:
Read OP
[Galaxy S III Original Android Development] GrayJack:
Why ExynosAbuse 1.30 still detects possibility of exploit with the new kernel?
[Galaxy S III Original Android Development] qwerty12:
Because - and correct me if I'm wrong - I think it only stat's the permissions on the exynos-mem dev node (reducing its permissions is one workaround to stop the exploit). With AndreiLux's better fix, the only way to tell if the actual exploit is going to succeed is by actually trying to access the non-whitelisted areas of memory (i.e. actually running the exploit) instead of using a preliminary check like looking at /dev/exynos-mem's permissions. Try using alephzain's exploit binary directly instead of a meh wrapper and the program should report failure.
[Galaxy S III Original Android Development] erto90:
So ROW is the default scheduler now? why this ? i remmeber Andrei said that it was so slow while i/o operation or i'm wrong?
[Galaxy S III Original Android Development] Tenacious:
Andrei newer said that he actually said the opposite any way you can read about it in the op.

Ops he actually sad there is some lag during app installation but do you actually do something else with your phone when you are installing apps.
[Galaxy S III Original Android Development] Chris_84:
Hi Andrei! Sorry for the ot! But I think your new kernel is pretty awesome! Everything work as it should. No camera issues or else since now. Great work and I think wifi is much faster also in my opinion. Did some test with streaming and it works great. Will also do some speed test. The overall experience is also very snappy. No lags or slow downs here. Running it on omega rom 34. Kudos to you!

Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member :P
[Galaxy S III Original Android Development] hollow1:
Hehe..see you again Chris,

I didn't tick the set on boot option because I don't know how to play with it :laugh: but really wanna play...:( Beside I play only with audio panel. Yeah...it's good :good: And moreover, testing with a game 1mn I lost battery only 0.5% :victory: better than Siyah (2-2.5%) and stock (1%). I think what it will be if I can play with set on boot of cpu & gpu...:rolleyes:

Wonder what about your settings ? :laugh:
[Galaxy S III Original Android Development] Rikul:
AMazing kernel brah..

There should be a thread regarding the settings we use..

Just to share them :)

Btw can anyone help me the most battery optimised settings.. :D
[Galaxy S III Original Android Development] omniwolf:
No.. this thread shouldn't be just a thread about what settings you use.

The default settings are the best for battery (excluding your reducing voltages, but that must be done by you, as each phone is different).

If you don't understand the settings, please don't touch them. Your phone will work great on the default settings. Almost certainly if you start mucking around with the settings the phone will work less optimally - just leave it alone.
[Galaxy S III Original Android Development] Rikul:
Sorry I wanted to say "there should be a thread" :P

My bad
[Galaxy S III Original Android Development] hollow1:
So do I need to just tick the "Set on Boot" then leave other things at default like that, or there's no need to tick at all both CPU & GPU?
[Galaxy S III Original Android Development] omniwolf:
there is no need to even open STweaks. the "Set on boot" options are only for if you change things.
[Galaxy S III Original Android Development] Frag1le:
Thanks for this quick kernel exploit fix AndreiLux!
[Galaxy S III Original Android Development] andreasy:
May I ask if this issue is kernel related and weather it could be fixed in kernel?

When my phone is connected to my Bluetooth headset, Wi-Fi connection gets very unstable and I notice very frequent disconnection/reconnections. When bt is just enabled but not connected, there is no problem. The problem only appears when bt is connected.

This has been confirmed by many sgs3 users and throughout different Rom bases. So, is there something that could be done in kernel for this?
[Galaxy S III Original Android Development] fifamaniac:
Does this kernel with the exploit fix breaks the camera?

If yes, there is a fix?

Thanx... will give it a shot soon in the journey
[Galaxy S III Original Android Development] EpicDesire:
Read the OP!
[Galaxy S III Original Android Development] fifamaniac:
Thx... have found it!!!

Sorry.
[Galaxy S III Original Android Development] jcurran.jc:
Whwn installing is it ok to just flash over my current kernel/rom.

Do I need to wipe anything.

Thanks
[Galaxy S III Original Android Development] Frag1le:
It doesn't say so in the OP, so i guess not.
[Galaxy S III Original Android Development] Chillz88:
Just flash it.. Thats enough.. Some people wipe dalvik and cache partition before though..
[Galaxy S III Original Android Development] Pretzel Kleo:
I just flashed this over the other one and it works perfect.
[Galaxy S III Original Android Development] Voxyn:
Will the new Wifi drivers fix the battery drain with Wifi enabled in standby??
[Galaxy S III Original Android Development] LenAsh:
Not a problem I encounter... so why not try it yourself - takes 5 minutes.
[Galaxy S III Original Android Development] Rikul:
Actually I am experiencing a idle battery drain..

Not sure of the reason :(