yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] ezechiele2517:
so what do you advice to do?
[Galaxy S III Original Android Development] GrayJack:
Refer to Revolution HD developers.
[Galaxy S III Original Android Development] ezechiele2517:
where can I download previous versions of the kernel?
[Galaxy S III Original Android Development] AndreiLux:
Nowhere. If you have any impression of a regression made, you bring it up with me. I don't support using older versions for the sake of "it ran better" because that's just uninformed belief.
[Galaxy S III Original Android Development] ezechiele2517:
ok, no problem but with .27 version installed by default with the revolution hd 17.1 rom I had the impression that with power saving enabled I hadn't any lag but with the 29.1 enabiling power saving I see some lag that ins't an issue but it's slower than stock kernel I think
[Galaxy S III Original Android Development] psyntific:
Mate i use arhd with perseus 29.1 and it works like a charm even in power saving mode.. I can even play games like nfs without any issues in power saving mode.. there should be something else that is causing it

Sent from my GT-I9300 on ARHD 17 with perseus 29.1
[Galaxy S III Original Android Development] mariusbarosanul:
WI-Fi fix issue

Hi, Andrei

I'm running Stock JB Rom 4.1.1 and your latest kernel.

The question is related to this Wi-Fi fix

http://xdaforums.com/showthread.php?t=2015482

I flashed it after flashing your kernel, and the problem is still there. Meaning that from time to time the Wi-Fi connection will drop without any reason and then recconect, making VoIP calls a pain.

I had this problem with the stock kernel also, but I flashed your kernel due to Root exploit issue.

Anyways, I have a few questions:

1) This fix works with your kernel ?

2) Do I need to reflash it after you release a new kernel version, or if you revert the Wi-Fi drivers ?

3) Do you have a better solution for this issue ?

Thank you,
[Galaxy S III Original Android Development] mamba720027:
Power saving mode just switch the CPU to dual or single core not too sure which one but yea that's what it does and lock the CPU at 1000mhz. You can do the same in Stweaks and I'm confident their shouldn't be any lags if u haven't touch anything else in Stweaks. To do this in Stweaks under the "Cpu hotplug" menu use the slider where it says "hotplug lock" and slide it from 0-1 to lock in single core or 0-2 to lock in dual core. Then u can drop the CPU frequency to 1000mhz if that's what u desire.

Sent from my GT-I9300
[Galaxy S III Original Android Development] hur8111:
Battery life with 29.1 is much better. i so guess it was new wifi driver that drained battery while standby. 29.1 works perfect for me. Thanks :)
[Galaxy S III Original Android Development] Lither:
Will there be profiles uploaded to be used in STweaks?
[Galaxy S III Original Android Development] Galactus:
Doubt it
[Galaxy S III Original Android Development] drakester09:
I admire your no BS approach Andrei. Kudos.

Thanks for a wonderful kernel. A lot of work and thought are evident in the making of this kernel.
[Galaxy S III Original Android Development] zolkar:
Awesome ! battery life with 29.1 is the best I had since I rooted my S3!! Great job!

Enviado desde mi GT-I9300
[Galaxy S III Original Android Development] habylab:
Battery life definitely is awesome with this. 14 and a half hours plus 5 hours screen time now!
[Galaxy S III Original Android Development] Frag1le:
Exactly, I also admire that he takes our comments serious. It's easy to read positive comments after you spend hours of work on a kernel but it's very difficult to read and really take the criticism serious and process it and build it into a better kernel build.

Ps I said it before but 29.1 really rocks. Great idle and screen-on batterylife.

Sent from my GT-I9300
[Galaxy S III Original Android Development] :
Yes, battery is very good. Got 1h of screen on with a drain of 16%. I could get 10% of drain, but for 20 minutes I was playing on FPSE emulator :)
[Galaxy S III Original Android Development] adelskrev:
Noob question here, first time using this kernel and was wondering what i/o sheduler who works best with this kernel

Regards Jörgen

Skickat från luren.
[Galaxy S III Original Android Development] omniwolf:
if you're a "noob" and are unsure, please don't even open the STweaks app. Andrei has put a lot of work into making the default settings work very well, almost certainly anything you change will make it perform worse.
[Galaxy S III Original Android Development] ghul21:
Perfect sleep with v29.1, not a single wakelock :silly:

Thank you :highfive:
[Galaxy S III Original Android Development] habylab:
Open up stweaks and at the top go to the i/o tab. Comsider changing both to Noop for better battery.

Not exactly true, but good advice.
[Galaxy S III Original Android Development] siavash_Skh:
Using the last version (29.1) for 19 Hrs after a full charge changed my opinion.

The Battery Life is Awesome! Thanks Andrei :)

But why sometime the phone was awake ? how can i find the reason ?
[Galaxy S III Original Android Development] davelyh:
may i know what is your setting,

how could you save so much battery
[Galaxy S III Original Android Development] siavash_Skh:
I didnt change any setting of the kernel

I used the foxhound rom (1.6)

And you see in these 19hrs. My screen time was less than one hour and only some times I turned on the wifi.
[Galaxy S III Original Android Development] Frag1le:
Install Betterbatterystats, fully charge your phone and then after some batterydrain check betterbatterystats to see what's causing the wakelocks and partial wakelocks.

(ps. it says FoxHoun

t

in your signature)
[Galaxy S III Original Android Development] Stivikivi:
Which settings do the ppl have with over 6hours screentime? I could only manage to get up to 5 hours
[Galaxy S III Original Android Development] adelskrev:
Thanks you for your respons :) Tryed some different settings in stweak, but went back to default, working perfekt as it is

Best Regards /Jörgen

Skickat från luren.
[Galaxy S III Original Android Development] gundal:
It is possible yes, but you have to use scripts. Stweaks cannot set frequencies that are not standard.

If you really need help pm me.
[Galaxy S III Original Android Development] cantIntoCode:
Did you manage to find out what that something else was? Can't find a way to get my kernel booting with exfat support from siyah author.

// sorry for offtopic.
[Galaxy S III Original Android Development] simone201:
Check your defconfig....disabling some options causes also problems with exfat...

I have finally fixed it too, check my repos and try to diff my defconfig with urs :laugh::laugh:

// off topic end
[Galaxy S III Original Android Development] AndreiLux:
I implemented the current readouts as promised and even forwarding them to the standard interface on the battery driver; however the registers are being filled with garbage. I went over the datasheet endlessly and over the implementation and I cannot find a fault. This makes me consider the posibility that we do not have a sense resistor implemented in hardware. I tried to locate the fuel gauge on the motherboard but cannot find any matching chip; it is a 10 pin (5 on each opposing side of a square) in a TDFN package. The service manual was not helpful.

Implementation can be found here: https://github.com/AndreiLux/Perseus-S3/commit/c5f87e2377dd12742f14ed5ac5979033c98e0a09

And I attached the test-kernel; debug messages are to be seen in kmsg with the raw values of the registers at hand. All apps who use batt_current from the battery driver also work.

Unless anybody has some miracle revelation, current reading is dead in the water.
[Galaxy S III Original Android Development] Rob2222:
Hello,

on the SGS2 a MAX17042 compatible fuel gauge was integrated in the MAX8997 power management IC.

Cause we don't find a MAX17047 on the ifixit teardown, I would take a bet that the fuel gauge is integrated in the MAX77686 or the MAX77693. This would not be unusual for such a highly integrated system.

Unfortunately there is again no documentation out there. Some hints, that power management is included in these devices I have found here and here. I don't know if it would be useful to contact the author of that code for maybe more information.

So we don't know, if its a full MAX17047 or just a compatible fuel gauge that is included in the SGS3. We also don't have the pinout and can't check if there is a sense resistor assembled or not.

@AndreiLux:

I think the MAX17050 driver in the source is not for the SGS3 now. But have you took a look on it an its initialisation for coloumb counting?

Would it be worth a try / be safe to try to use this driver? Or isn't it even possible?

Here one can read that the 17047 and the 17050 are the same from the drivers point of view.

BR

Robert
[Galaxy S III Original Android Development] AndreiLux:
Who is that reply/quote from?

Anyway, I think you're correct, the block diagram of the S2 depicts the fuelgauge as inside a larger IC. I saw the 17050's driver and it hasn't got any special initialization. Just using that driver instead of the 17047's means much more work though as the interfaces to the battery driver are different, so either those need to be rewritten, or the battery driver.
[Galaxy S III Original Android Development] Vaddy23:
Flash content in the browser would stutter when CPU was clocked under 1200mhz on other kernels. Would this have to do with the gpu requiring 1200mhz in order to max out gpu speed? That's ridiculous in terms of battery consumption and to my understanding if I flash alpha 14 the gpu will work as it should by default? Do I have to do anything else besides flash the tar file in order to see the gpu changes? Thank you
[Galaxy S III Original Android Development] AndreiLux:
Normal flash content cannot possibly tax the GPU into scaling to 440MHz to trigger the lock in the CPU to 1200. Video content is done on the hardware decoder separate from that. So I'm not sure what you're getting at. This was meant mainly for gaming. If playback is lagging then it is fault of the HW decoder drivers which arent part of the kernel so wr cant do anything about that.
[Galaxy S III Original Android Development] simone201:
BTW i'm getting no lags at all while gaming with heavy games even if i have applied ur patch...:good:
[Galaxy S III Original Android Development] AndreiLux:
All 3D intensive games with any kind of CPU load above the average are the newest FPS shooters like Nova and so on. We're already locked at 800MHz in such games because of the touch boost as there's always touchscreen contact being made, all other games wouldn't scale under 500MHz anyway because of aggressive governor thresholds under that frequency. GLBenchmark is so ridiculously GPU bound that the fps wont change until you limit the CPU to under 500-600MHz. I suspect that this was just a stupid way of them to increase the bus bandwidth or something, but that doesnt even seem to have much effect in the real world.
[Galaxy S III Original Android Development] simone201:
Completely agree, our cpu management system (of our phone) already locks the freq to 800Mhz while using the touchscreen so there is always a kinda lock at 500 or 800, for different reasons...

The GPU locks are just strange ways of avoiding a "bottle neck" while using huge 3D loads, same as using OC on the normal PCs, but it just makes the phone hotter and drain more battery than expected :good:
[Galaxy S III Original Android Development] Rob2222:
Do I have to enable this? I have flashed the kernel, then via terminal, su, cat /proc/kmsg and I get the max17047_get_amperage messages. But here cgain is 0x0, 0x0 in both subregisters. So the current registers are 0x0 also.

EDIT: OK, had to remove the battery to power cycle/reset the power management IC.

BR

Rob
[Galaxy S III Original Android Development] AndreiLux:
Oh yea, forgot to mention that, you need to remove the battery to clear out the registers to be reset into their default state.
[Galaxy S III Original Android Development] zodiaxe66:
Hi.any thoughts of implementing voodoo control to this kernel.
[Galaxy S III Original Android Development] AndreiLux:
Gokhan has a proper implementation of the old Voodoo Sound and I'll include that once he releases it tomorrow or so I think.
[Galaxy S III Original Android Development] DirkStorck:
Sorry if it allready been answered but I couldn't find it.

Does this kernel support exFat?

Thank you :D
[Galaxy S III Original Android Development] Rob2222:
Hello,

after some more research I am pretty sure, that the fuel gauge module and the charger is included in the MAX77686/MAX77693 combination. It's a Maxim Power-SOC. So Samsung could choose the modules that they wanted in that IC's.

So it could be, that we really don't have a sense resistor in the SGS3 cause if you put many modules in one/two ICs, it could be that you need to save pinsouts.

However, I wonder if R300 in the service manual could be a sense resistor? R300 is not in the service manual part list. But it is depicted in the service manual. But I have no open SGS3 to check, if this is a resistor with a really low value <0.1 Ohm. If it has such a low value, it could be that there is a little chance left. But I think no one here has a opened SGS3 to check.

BR

Rob
[Galaxy S III Original Android Development] Rob2222:
I have reinstalled the original LF2 Kernel.

When charging the max77686 is spamming cat /proc/kmsg with messages like:

"c0 max77686: id=27, org=20, val=18"

Is this the normal behaviour? Didn't checked that before.

BR

Rob
[Galaxy S III Original Android Development] AndreiLux:
It's in the hidden changelog, but yes It works without any issues.

I suppose so. The chances of a sense resistor are very slim in that case if they specialized the chip. I'll re-check the manual for R300. Edit: R300 is on the other side of the motherboard near the baseband processor, and quite far away from the 77693, so I don't think it has anything to do with it.

I removed those messages in my kernel because they were way too spammy, it's normal though.
[Galaxy S III Original Android Development] zodiaxe66:
Great...I know I've tried it and sound is improved greatly
[Galaxy S III Original Android Development] Darkstriker:
I'm looking to find out how far UVs can be taken on the S3. Please vote in my poll:

http://xdaforums.com/showthread.php?t=1738572
[Galaxy S III Original Android Development] Galactus:
Most people underclock, or have their screen brightness set to low. Some turn off all data unless they need it. Others like myself freeze bloatware and only sync apps that need it. I don't want to underclock and I don't want to turn off data and I like my screen brightness at 50-60%. I normally get just under 5 hours screen on time now over a 24 hour period. 6 hours can be achieved but most of the time the phone is on for less than 14 hours
[Galaxy S III Original Android Development] Lither:
The default settings in Perseus STweaks saves battery or do I have to tweak it more?
[Galaxy S III Original Android Development] mamba720027:
Should read the OP.Its their for a reason.

Quoted what Audrei wrote " FIOPS is the new default scheduler, it's a CFQ like fairness scheduler optimized for solid state storage. ROW should be the actual better performer here as it has superior logic, but I didn't set it as default because of some lags when installing applications. ZEN is just a mix of SIO and Deadline and nothing special. BFQ seems to underperform. I recommend the first two over everything else, and added the latter two just for comparison's sake." Quote End.

Also as discussed in this forum before, schedulers show very little difference to recognize when it comes to battery life.

The default is the best. If you want to undervolt or mess with the GPU and other settings that's fine with knowledge of what you're doing. You will save some battery by UV but it may not be much. With usage it varies.

Sent from my GT-I9300
[Galaxy S III Original Android Development] svs57:
I have a question. Does this kernel support USB charging control?

I want to stop charging when connected to USB.

I setprop persist.sys.charging.disable=1

But my SGS3 still charging via USB.

Can anybody help me?

How to stop charging via USB?
[Galaxy S III Original Android Development] mamba720027:
You cant stop USB charging from a feature stand point within the phone but by disconnecting the USB cable u can. I don't see the logic in why you would want to disable it.

Sent from my GT-I9300
[Galaxy S III Original Android Development] 0asis:
How to have a green signal bar ? I mean, my signal is not that poor but the bar is always yellow. Should I change something ??
[Galaxy S III Original Android Development] svs57:
I have a reason to stop charging. I don't want to destroy battery. I work with phone with adb via usb.

I know that it is possible to stop charging.

If I disconnect USB then how can I work via adb?

I don't want install sshd server and work via network.
[Galaxy S III Original Android Development] destrife:
hallo..izzit possible add FAST CHARGE in perseus kernel?
[Galaxy S III Original Android Development] sduford:
The S3 has built-in battery protection, when it reaches 100%, it shuts-down the charger and lets the battery drop 2 or 3 % (although it will keep saying 100% as long as it is plugged-in. That's why sometimes when you unplug your phone it will rapidly drop off a few %.
[Galaxy S III Original Android Development] mamba720027:
you can read up about modems here xdaforums.com/showthread.php?p=26583587 ,some reported to give better signal depending on the area etc. Also theirs a app in the play store name "perka's file stash" with a list of all modem flashable via Odin or cwm for the gs3. Always do a backup before flashing anything.

Edit: yea I know u mention your signal looks great but yellow is usually when your signal weakens,prob while you're walking or moving around somewhere,travel etc.

On the contrary usb charging does not destroy battery life it actually charges the battery slower which is said to extend battery life.

Sent from my GT-I9300
[Galaxy S III Original Android Development] borjaag:
Good battery life with Omega 35 with Perseus 29.1!
[Galaxy S III Original Android Development] 0asis:
Thanks. But in fact i'm at home since this morning and my signal bar is full of yellow as you can see. Don't focus on my battery life which is prety bad for the moment because I'm still testing new things.

Edit: This network signal bar shows the signal of wifi or data/gsm ?
[Galaxy S III Original Android Development] privat75:
data/gsm

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] 0asis:
Hum so I don't understand. Anyway, I'm off topic. Sorry
[Galaxy S III Original Android Development] mamba720027:
Yea if you're getting green bars outside your home then its fine,just means at home your signal seem to be weak.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Infy_AsiX:
I recorded a video showing how my cpu hotplug doesn't work properly and the last core never turns off. I've had this problem as long as I've had the phone. Using siyah's hotplug governor has helped but I'm sure it's not efficient.

Please watch and see how this is possible. I've got two s3s here suffering it. https://www.youtube.com/watch?v=qY7QPmVCTSY All stweak settings at default after a flash.

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] ajrcz:
A good start, kernel very well..
[Galaxy S III Original Android Development] shaarky:
I'm afraid that Allshare Cast functionality is broken with this kernel :( - it gets connected, but after while it disconnects.Can someone test it as well?

*update* Installed Syah kernel and it's ok
[Galaxy S III Original Android Development] gingerneil:
This looks like a great Kernel. Is there USB ethernet included, or can it be in a future release ? I am looking for support of the same chipset that the nexus 7 works with out of the box.
[Galaxy S III Original Android Development] mamba720027:
Somethings half default here like CPU set to 200-1400mhz with GPU 160-266mhz.

Ok so its not a kernel bug thing its how Audrie set it up for the cpu to work. If u change "cpu load bias count" to 1 then "hotplug freq from 3 core to online" and change this to 1400mhz ,you will notice just one core online And the other 3 offline. Have to disable anything running in the background as to make sure its not adding a load to the CPU if trying this. Theirs more to it than this,that's just a trial and error thing I ran from my limited knowledge and understanding. I don't recommend anyone doing this or messing with the settings.

Sent from my GT-I9300
[Galaxy S III Original Android Development] erto90:
same thing here.. don't know if is a bug or a bad configuration.. please Andrei enlight us :o
[Galaxy S III Original Android Development] mamba720027:
Yea I notice it took long to go offline still after I ran some more videos to bring it back online,then I tried set "run quedepth from 3 cores to online" to 275 and "run quedepth from 4 cores to offline" to 175 and goes offline faster now. When the phone sleeps for a minute and I checked it also shows offline. Can try that with the above setting I mention just to see what's up. :p

Edit: Forgot to mention I had "cpu online up bias threshold" as 85 and "cpu down bias threshold" 50.

Sent from my GT-I9300
[Galaxy S III Original Android Development] naveediftikhar:
deleted
[Galaxy S III Original Android Development] gundal:
Samsung favors having 2 cores running and is optimized towards that I didn't really like how it behaved which is why in my governor tweak profile I play with some of this values to shut cores off faster and take more load to bring them on.
[Galaxy S III Original Android Development] mamba720027:
Ok see wat u mean,I never really bothered with the 2 cores running,just wanted to make sure all 3 cores shut down when theirs not a heavy load.

Maybe I'll check those profiles out later,rember seeing u post them a while back,I normally be running dual core most times,find the device more fluid when it comes to loading apps or editing something large. Amazing kernel with all these features,kind of fun when understand how the cores work as to try different settings to see what results can produce.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Crunozaur:
I've installed the 29.1 on my Omega v34 + JKay (14.5.2 I think) but it was really laggy. According to FPS meter my max fps was 40 and it felt really bad. I reflashed back to 27.2 and it works great again

What could cause that? I cleared my cache/dalvik ofc. Restart didn't help.
[Galaxy S III Original Android Development] mamba720027:
Try upgrade to omega v35. I don't have lags running same rom and the default kernel settings. Can also reset Stweaks and any other apps u use kernel related then install 29.1

If this laggyness was only in fps meter then shouldent bother.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Crunozaur:
No, it felt really sluggish thats why I checked fps using that app

Kinda offtopic but do I need a full wipe for v34 -> v35 upgrade? I suppose not?

__

Meh, I suppose I should do a full wipe cuz I'm using JKay. I just did a MegaWipe (and lost some save states/data even I backup liek everything), so I'm kinda reluctant
[Galaxy S III Original Android Development] sachilleas:
My phone does not work this way. After it has finished charging, i can hear the plug in sound and it starts charging again (after some minutes). Is it a problem?
[Galaxy S III Original Android Development] mamba720027:
Offtopic.In omega rom change log it always state if a full wipe is needed. Was no need for a full wipe.

Did your full wipe without any addition mods then running Perseus solve the lag?

Get an iPhone. You just quoted an answer asking the samething already explained. Plus your chargeing is not kernel related.

Sent from my GT-I9300
[Galaxy S III Original Android Development] hur8111:
Hi whats the name of the app? Thanks :)
[Galaxy S III Original Android Development] Cyberz22:
Good kernel. I get good battery time with it.
[Galaxy S III Original Android Development] Tiger22:
It is "System Panel"

Greetz Tiger22