yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] MuertoKo:
Well anyway, you can easily ruin that 2% extra for having one single random reboot, i bet it drains more battery on boot than you can save with UV... To test UV you just have to wipe, plane mode, and put a long video from SD card to play... easy and quite easy to repeat in almost same conditions, but as it's so slight even a single difference can lead to miss-testing. If it was a big one you could easily see a difference by doing this, right?

I tested like this and couldn't find a difference so won't lose my time again :P

Anyway, I'm happy with the voltage setting to proper values according to my chipset like this kernel does (I've written them down to make sure to use them whatever kernel I use :P), that's enough for me, but everyone is free to UV as much as they want :)

Anyway, back to Perseus, I've flashed 28 and STweaks worked just great as usual, no issues, tested a bit with sliders and schedulers, all works good in the App (all but having noop as default scheduler for Internal, which has already been reported before) and we'll see difference with FIOPS... but as said by Andrei I could never find difference with schedulers (well yes, but when using some of those "battery saving schedulers" that killed my performance on i/o but well, quite logic there :P)
[Galaxy S III Original Android Development] svs57:
How to covert internal SD to ext4.

fdisk /dev/block/mmcblk0

Device Boot Start End Blocks Id System

/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT

Partition 1 does not end on cylinder boundary

Can I just do

mkfs.ext2 /dev/block/mmcblk0p1
[Galaxy S III Original Android Development] qwerty12:
The internal SD always has been ext4; look at /data/media. /storage/sdcard0 (/mnt/sdcard0 for pre-JB) is a mountpoint faked to emulate vfat's behaviour - read and write for all (as long as they have the right Android permission) in order to keep compatability with apps (there's an interview with a Google engineer about the Galaxy Nexus that talks about it on the Internet somewhere).

What AndreiLux is saying is that because of his upgrading the Linux block subsystem used in Perseus, the exfat module will not load/ function correctly so external cards formatted in exFAT will not be visible to a S3 running Perseus 28. You can format any exFAT cards to FAT32 if you want Windows compatibility but a limit of 4GB on files or to ext4 which Windows lacks compatability for but you're not limited to 4GB when it comes to files.

Regarding the toolchain: It's arm-eabi-4.4.3. I know because /proc/version says GCC 4.4.3. Linaro toolchains often have higher versions of GCC AFAIK and 4.4.3 is pretty standard for Android kernels since it's in the prebuilt Android repo. The module I built using it loaded fine, anyway.
[Galaxy S III Original Android Development] svs57:
Thank you for your explanation.

Now it's clear for me.

I created swap and ext4 partitions on ext SD and init.d script for use its.

I don't need any FAT because I don't use Windows.
[Galaxy S III Original Android Development] Flypwnz:
Stweaks FC always on new 28 version. Tried all ways to resolve this, but no luck ;(
[Galaxy S III Original Android Development] sduford:
That statement is self-contradicting. The wasted heat that builds-up in your phone is energy, that energy comes from the battery. So while it may not make a huge difference in battery life compared to keeping the CPU in deepsleep as much as possible, if it's enough to affect your phone's temperature it's not an insignificant amount of energy saving.
[Galaxy S III Original Android Development] KennyLegend:
Isn't that what I said? :confused:

Sent from my GT-I9300
[Galaxy S III Original Android Development] TheMasahiro:
10.000 score in antutu bench? Thats odd.... i get 16.000 on siyah,,. am I doing something wrong? Games lagged as hell on v28....
[Galaxy S III Original Android Development] AndreiLux:
I decided that it was a bad choice with exFat. I will revert the 3.3 changes. You can stay on either version if you're not affected, or stay on v27 until the new one later today.

STweaks crashing is a problem of 1) Superuser 2) If you leave it in the background the shell terminal will close but STweaks won't, in that case just restart it.

Try upgrading your Superuser. I personally can't reproduce STweaks crashing every time, just the first time.
[Galaxy S III Original Android Development] gundal:
Sure, here is my logic

defaults parameter mine

30000 sampling rate 20000

82 up threshold 90

5 down diff 10

40% thres for response 81

1200 freq for fast down 1600

95 up thres fast down 98

37 up step 18

6 splice amount 4

13 down diff 8

With the default settings when the load is measured if the cpu load is over 82% off current freq step it will scale up.

New logic added in perseus .27 now gives us 3 up steps instead of just a fixed one.

so your cpu will step up more aggressively based on how much above the threshold it is, not just if its over, this is

great.

Right now, if we are coming in with a load of 83%-88% we increase freq by 300mHz if we are 89-94% we increase freq by

400 mhz and if we are 94-100% then we increase freq by 700 mhZ.

This is too fast for me.

For a few reasons the amount we jump has gone up because our max cpu is 1800 instead of 1600 (at 1600 the jump ups are 200,300,600mhz)

The logic I use on my N2 is as follows:

Load of 90-94 = 100 mhz jump

load of 95-98 = 200 mhz jump

load of 99-100 = 400 mhz jump

The responsiveness of the phone is not compromised at all, the cpu just steps up less and only when it has really high

loads. It still gets to 1800 and does many operations there, but it comes out of 1800 fast and when it jumps down it jumps

down further. The fastdown has been upped from 1200 to 1600 , meaning it now requires 98% or higher load to jump up when above 1600 mhz not 1200 mhz, I found that the phone was always in 1800 or like way lower, never in the 1700 - 1200 range as it used to need 98% load to be in that range. The cores hotplug has been slightly changed to turn off cores quicker when not in use and takes more samples to turn them on so they only turn on if load exists for longer duration of time.

IF im completely flawed id love to be pointed out as to why, but cpu spy and real world results say try this ^
[Galaxy S III Original Android Development] cba1986:
There is so much difference between stock and AOSP that this kernel cannot be used in both?

Siyah works very well................
[Galaxy S III Original Android Development] Tenacious:
No joy supersu is all ready latest version trayed also downgrading it still same, also went step further installing stock kernel deleting all trace of perseus rebooting and then installing v28 again still fc, restarting stweak also has no affect. Forgot to mention before I'm on foxhund 1.6 but seeing that others are on different roms so it isn't rom specific.
[Galaxy S III Original Android Development] erto90:
someone can report something about new schedulers? can be changed in STweaks?
[Galaxy S III Original Android Development] habylab:
Yes it can be. There is a phone and sdcard scheduler option. Fiops v2 seems far stabler than the Galaxy S version. Battery life pretty good too, can't judge yet though.

---------- Post added at 03:46 PM ---------- Previous post was at 03:43 PM ----------

Hit the reset settings in the extras tab, last on the right in steaks.
[Galaxy S III Original Android Development] _andrea_:
Hi, same problem with Stweaks here: I'm on InsertCoin 4.0.0 (official 4.1.2 base) Perseus 28.1; Stweaks opens but after some seconds FC
[Galaxy S III Original Android Development] naveediftikhar:
@ andre i dont knw if any xould reoroduce this or not but jus notice another guy report this and i aswell reported this back when u releases 27..there is a evident lag in games and banchmark tests which stress the gpu..m not talkin abt the benchmark score but the test itself lags in open gl(antutu)...lags alot!
[Galaxy S III Original Android Development] mamba720027:
Here's alogcat of the fc with stweaks,hope this helps.

https://www.dropbox.com/s/edsuswq11hb1gkp/2012-12-14-10-40-30.txt

Sent from my GT-I9300
[Galaxy S III Original Android Development] qwerty12:
I think I can reproduce the STweaks bug.

Assuming that STweaks is already working fine for you (like it is for me):

Rename /data/.perseus to something else

Shutdown and remove your external microSD

Turn the phone back on and start STweaks

I wasn't hit by this bug because I always had an external microSD card inserted. If the phone is started without a card, the mmcblk1 folder does not exist.

Using the logcat above, compare

(internal eMMC)

12-14 10:40:57.141 I/com.gokhanmoral.stweaks.app.q( 7225): [Running command:`echo iosched internal /sys/block/mmcblk0/queue/scheduler|awk '{print ". /res/customconfig/actions/" $1,$1,$2,$3,$4,$5,$6,$7,$8}'`]
[B]12-14 10:40:57.156 D/com.gokhanmoral.stweaks.app.q( 7225): --> Line received: noop[/B]
12-14 10:40:57.156 D/com.gokhanmoral.stweaks.app.q( 7225): --> Line received: [%nexttweaks%]
12-14 10:40:57.156 I/com.gokhanmoral.stweaks.app.q( 7225): [Finished command:`echo iosched internal /sys/block/mmcblk0/queue/scheduler|awk '{print ". /res/customconfig/actions/" $1,$1,$2,$3,$4,$5,$6,$7,$8}'`]

with

12-14 10:40:57.156 I/com.gokhanmoral.stweaks.app.q( 7225): [Running command:`echo iosched sd /sys/block/mmcblk1/queue/scheduler|awk '{print ". /res/customconfig/actions/" $1,$1,$2,$3,$4,$5,$6,$7,$8}'`]
12-14 10:40:57.166 D/com.gokhanmoral.stweaks.app.q( 7225): --> Line received: [%nexttweaks%]
12-14 10:40:57.166 I/com.gokhanmoral.stweaks.app.q( 7225): [Finished command:`echo iosched sd /sys/block/mmcblk1/queue/scheduler|awk '{print ". /res/customconfig/actions/" $1,$1,$2,$3,$4,$5,$6,$7,$8}'`]

(Also: if you're using swap on your external card, swapoff before removing the card >.<)

EDIT: Putting "sd_scheduler=fiops" into /data/.perseus/default.profile may help. No it won't, STweaks reads customconfig.xml...
[Galaxy S III Original Android Development] davi_ssilva:
Sorry for the noob question but I have one little doubt about this kernel. Andreilux said in the op that it's better we format our cards to ext4 or fat32 before flashing alfa 28. So... am I supposed do this on my internal sd card or my external sd card? Or both?

Enviado de meu GT-I9300 usando o Tapatalk 2
[Galaxy S III Original Android Development] Tenacious:
@ qwerty12 that whod explained it becose I don't have external sdcard.
[Galaxy S III Original Android Development] AndreiLux:
Yes you're completely right. I'll fix that in a moment.
[Galaxy S III Original Android Development] mamba720027:
I will try this when I get home or spare time if Audrei does not already upload a fix before,and you're right I don't have an sdcard,all makes sense :)

Sent from my GT-I9300
[Galaxy S III Original Android Development] spoogedemon:
So no possibility to use v28 without formating the external SD? :confused:
[Galaxy S III Original Android Development] eden1988:
AFAIK v28 broke exFat, only if you're using exFat then reformat your sdcard either to fat32 or ext4 or the best is to wait for Andrei to update his kernel.

If not then it's fine to update to v28 if you aren't running exFat.
[Galaxy S III Original Android Development] AndreiLux:
I already updated it a few hours ago, please read the OP...

I'm just going to fix that STweaks issue in 28.2 and then that's all for today.
[Galaxy S III Original Android Development] cmajetic:
ist the I/O tab gone in STweaks now? Or does 28.2 just fix the STweaks crash (didn't have it) and the exfat bug? I'm a bit confused sorry
[Galaxy S III Original Android Development] eden1988:
Thanks Andrei, btw STweaks takes quite a bit of time to load, like about 5 secs or so, not that I mind but any chance that the loading time can be made faster?
[Galaxy S III Original Android Development] psyntific:
Thanks alot Andrei... When I'm installing a new version of the kernel should i un install stweaks before that?

Sent from my GT-I9300 on ARHD 17 with perseus 28.1
[Galaxy S III Original Android Development] gundal:
there is no need to uninstall anything when flashing a newer version of the kernel, your profile will even remain intact.
[Galaxy S III Original Android Development] psyntific:
Yea it makes sense now cuz i was wondering y de values didn't change back to default after the fresh installation

Sent from my GT-I9300 on ARHD 17 with perseus 28.1
[Galaxy S III Original Android Development] gundal:
if you do want the default values back, you can use the restore defaults option from stweaks extra menu or flash my profile 0 from this post

http://xdaforums.com/showpost.php?p=35405919&postcount=2077
[Galaxy S III Original Android Development] :
I'm using the most updated SuperSU and it's crashing. Previously kernel version was working.
[Galaxy S III Original Android Development] DrAnGeR:
Hey guys ,where can i find the newest kernel? sorry for the dumb question but still trying to find it. (On op says 27.2, i assume that its not the latest am i right?)
[Galaxy S III Original Android Development] AndreiLux:
I removed it.

I just spend two ****ing hours trying to find out why the wrong schedulers were applied at boot and finally found that the cause is Samsung's ramfs smdk init file. Twats. I'll upload 28.2 shortly when I have everything tested and working. It will fix all issues.
[Galaxy S III Original Android Development] Tenacious:
V28.2 working great no stweaks fc.

Thanks Andrei

Rebooted couple times and I/O is always as set in stweaks.
[Galaxy S III Original Android Development] MuertoKo:
Fiops is gone and we have "zen" and "row" the default, right?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
FIOPS is gone due to the 3.3 revert. Luckily back-porting ROW was a very quick and easy matter. FIOPS will take me a bit but I've been dwelling into the block subsystem long enough the last few days to be confident to even write my own scheduler if I wanted to. It will come back some time in the next versions. I also removed BFQ due to it being in my opinion useless.
[Galaxy S III Original Android Development] XPLOSIV10:
I have row + row as default. Not zen.
[Galaxy S III Original Android Development] BioVolt:
I also have row and row as default.
[Galaxy S III Original Android Development] GrayJack:
Me the same.
[Galaxy S III Original Android Development] abelle_abelle:
does the latest version has the battery charging problem taking 1 hour more then usually to fully charge
[Galaxy S III Original Android Development] ICavalera:
I was told that flashing this latest kernel on my foxhound rom I would get back the crt animation. But I flash it, but nothing. Because, because said that the problem was at kernel.

Other hand, I flashed already. And it seems that may rom is no longer that soomth as it was on v27.

I'm using nova launcher, and the animations from there and even on some apps is no longer smooth.

That's my doubts and appreciation of my experience.
[Galaxy S III Original Android Development] gnam:
Please the fu**ing CRT OFF!!!
[Galaxy S III Original Android Development] JYJY:
Pay him or f**k off.. He didn't owe you anything.
[Galaxy S III Original Android Development] hamer221:
This kernel used to be good in the past.

Enviado desde mi GT-I9300
[Galaxy S III Original Android Development] cink40:
Doubt that, but was and is a very good kernel.

Tapatalked
[Galaxy S III Original Android Development] MuertoKo:
Glad to hear then :) Btw I ment I have row as default in both options, but that I saw as well zen as an option (hadn't seen or read about zen before)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] LenAsh:
ROM?

2 things wrong with your pathetic trolling - 1) you don't know the difference between a ROM and a kernel and 2) your post has absolutely no meaning or contribution value.

---------- Post added at 10:32 AM ---------- Previous post was at 10:17 AM ----------

You need to grow up. The CRT off thing is bling only and has no real value in the spirit of kernel development.

The developer has more to worry about than pandering to your spoilt brat demands. And exactly how large a donation have you made to him???

If not having CRT off makes you throw a childish tantrum, look elsewhere for your toys.
[Galaxy S III Original Android Development] Oleh:
Hi AndreiLux,

I’m using the AnonoROM v18 and the Perseus Kernel.

Unfortunately the version 28.2 of Perseus is definitely slowly as 27.2. The 27.2 is much faster. What is the reason?
[Galaxy S III Original Android Development] AndreiLux:
Your imagination.
[Galaxy S III Original Android Development] Oleh:
No, it’s the reality.

I’m using as test the simple game Fly Boy by power saving mode. Using 27.1 all is working well and the 28.2 give me more lags. The ST-Settings and environments are always identical because I do nothing except burn 27.2 or 28.2 kernel.
[Galaxy S III Original Android Development] www1:
game, set, match rotfl

You win Andrei :good:
[Galaxy S III Original Android Development] Oleh:
Can you explain please?
[Galaxy S III Original Android Development] mincorp:
no, doctor, no!! i swear they're coming to get me -))

sorry for OT, but it was just too rich for me..

great kernel, btw!!
[Galaxy S III Original Android Development] AndreiLux:
And I'm telling you that I changed almost nothing outside of the I/O schedulers in the kernel. I'm not doing any art here but empirical technical changes, and I didn't change anything to related to 3D.
[Galaxy S III Original Android Development] pulsation:
Hello :) I'm using your kernel for a few months, congratulations for your nice work.

However, is exfat support so important? I don't know how many people care about it, but it is absolutely not my case. Please correct me if I'm wrong, but it looks like some pretty strong enhancements have been dropped because of a useless and proprietary filesystem. The original v28 works really fine here.
[Galaxy S III Original Android Development] DirkStorck:
Hi. I wanted to try your new version..but after boot and fater I unlock the phone and have entered the pin my phone freezes :(
[Galaxy S III Original Android Development] AndreiLux:
The kernel has a large install base right now, and for the one day that it didn't have exFat people were complaining in all the forums. Generally I don't really even need to provide STweaks if I target the more savy users but the kernel was and hope to always be a "best setting out of the box" thing. I will try to bring FIOPS back by backporting it in the future. I'm upset myself since I wasted quite a few days on upstreaming to 3.3.
[Galaxy S III Original Android Development] zappoo:
Gundal - any chance you will post your 5 different profiles, please?
[Galaxy S III Original Android Development] cba1986:
It's a shame that you had to drop 3.3 because of ExFat. I dropped exfat long ago. It is a nasty file system.

But thanks for all your efforts.
[Galaxy S III Original Android Development] Interhead:
Nice work

Perseus alpha11 tested on stock rom 1704Mhz stabele and no problems so far:-) (1800Mhz@1425mv freezes my phone)

Quadrant score 6626

AnTuTu score 14274

CF-Bench score 28358,7306,15726

Battery drain is good depending on usage..

Ordred Gold 2850mah High Capacity Battery For Samsung Galaxy S 3 III I9300 on ebay

looking forward to test it.

Thanx for this exelent Kernel
[Galaxy S III Original Android Development] AndreiLux:
That battery is a rip-off, most probably it will have less real capacity than your stock one.

I'll release a new version in a few days after I have the occasion to fix some things and hopefully be able to implement something new.
[Galaxy S III Original Android Development] sak500:
I"m running @ 1800mhz @ 1425 w/o problems.

My scores

Quadrant 6776

CF 30831﻿ 7530 16850

Antutu @ 14761 #3 at the time.

BTW with 3rd party battery you'll lose NFC feature as it's built-in the samsung battery.
[Galaxy S III Original Android Development] Hacre:
I love this.
[Galaxy S III Original Android Development] VECTUS:
You sir just made me waste a perfectly good cup of java laughing over this comment...
[Galaxy S III Original Android Development] Rob2222:
AndreiLux:

Any News on getting direct current readings out of the MAX17047 fuel gauge IC?

BR

Rob
[Galaxy S III Original Android Development] AndreiLux:
I got my device yesterday and until now I was busy to rebase the kernel and reapply all the changes to have clean commits, so far I fixed ExFat and got to the the same point as alpha12 feature wise. Later tonight and tomorrow I will continue work on the fuel gauge. It's not guaranteed that it will work as Samsung is strangely initializing a register to a value that does not exist on the datasheet, and as it is related to the calibration of the sense register in connection to the columb counter, it's going to get whacky results until I check with a multimeter and compare the output values to determine what resistor we actually have in the device. I already implemented the functions in the fuel gauge driver itself to read out the current register but I need to forward it to the battery driver and there's like 3 layers of abstraction and since I wasn't familiar with it I need a day or two to properly check it out. So by the end of the week for sure there' be a verdict on it.
[Galaxy S III Original Android Development] Rob2222:
AndreiLux:

Take your time!

Can you say which register gets initialized to which undocumented value?

I would like to take a look in the datasheet regarding that.

Maybe its a battery parameter.

It could be that I can help understanding the IC a little.

BR

Robert
[Galaxy S III Original Android Development] AndreiLux:
The CGAIN register is used as a divisor value to the current reporting to be able to calibrate and also normalize the current relative to a variable sense resistor resistance; they say the standard resistor should be 10 mlliOhms but there's also different resistor values and their corresponding default CGAIN values in the datasheet. The problem is that Samsung is initializing the register in their driver to 0x0000 which is weird. The datasheet says it is "factory calibrated" but I don't know if this means by driver or actually burned into the chip register, if it is the former, then it's weird, if it's the latter, then things are straightforward and I can just ignore the driver values.

No need to help in terms of understanding, I've gone through the datasheet thoroughly, what's left is that I just need to implement and test it.

PS: Oh yea, I also uploaded a new version in the meantime, and this time it's tested ;)
[Galaxy S III Original Android Development] tvhak:
thanks bro glad you have your phone. hope you like it. but i guess you will
[Galaxy S III Original Android Development] tvhak:
one thing i do notice is that the phone gets hot really quick

with 2 minutes Internet browsing he's all ready hot
[Galaxy S III Original Android Development] Le Rat Noir:
A little slower than alpha10 ! I also observed an Antutu hang, never seen before! Weird

How to set the GPU clock? Via a script like this ?

#Frequency steps

echo "160 200 267 400" > /sys/class/misc/gpu_clock_control/gpu_control

#Voltages

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

I tested this via adb but the values ​​are changing of themselves every time. Need help ;)

Good work :)
[Galaxy S III Original Android Development] AndreiLux:
I didn't change anything between 10 and 13 to grant a performance difference, so you're having a placebo.

And yes GPU control works like that, however, it does not do anything currently due to monkey-programming on Samsung's part trying us to prevent changes to it and I will have to rewrite/throw out some things in the Mali power management so that the changes properly stick. I will update the FAQ when things will work.

@tvhak I checked the temperatures between Perseus and latest Siyah and they are identical after 3 runs of CF-bench and a run of Antutu... sorry but I can't reproduce your overheating.
[Galaxy S III Original Android Development] Le Rat Noir:
Thanks you for your quick answer !

An other question: Cm9 & AOSP support ?