yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] danarama:
1) its against the rules to ask for ETA

2) good to know cm finally caught up.

AndreiLux implemented his own v2 fix in Perseus months ago, so we're all good on that score.

This is good news for cm based kernels though. Such as yank which suffered freezes for me due to cm's long standing use of the v1 fix.
[Galaxy S III Original Android Development] habylab:
Forgive me if wrong, but I thought the fix by Samsung didn't cause mirolags that you get in Perseus?

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] danarama:
I've not had any lags on perseus or devil, micro or otherwise
[Galaxy S III Original Android Development] habylab:
Well, you're lucky then.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] Scarface1991:
Try to start the official XDA App and scroll through the postings. I experienced some stuttering when doing so. And on other Apps like Doods Music Streamer as well.
[Galaxy S III Original Android Development] habylab:
I'm not entirely sure that is the best example, as the xda app is outdated. Try tapatalk for smoother scrolling, I'd say.

I particularly noticed it when switching apply and/or scrolling through my drawer, for example.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] Scarface1991:
Well outdated or not doesn't really matter in my opinion because the scrolling lag doesn't happen on Temasek`s Kernel for example. That`s why it has to be a Kernel issue.
[Galaxy S III Original Android Development] DerTeufel1980:
Because of my broken pc i couldnt root my new device yet again. Totally stock everything. Xda app (and cpu spy plus, another favourite example) is also stuttering. Maybe people should use apps which are coded better.
[Galaxy S III Original Android Development] danarama:
These freezes are not related in any way to NAND operation.
[Galaxy S III Original Android Development] MuertoKo:
If u need any help on your computer feel free to PM, I work in a computer technical service on saturday as a hobby so I'm up to helping for no fee :P

Even though if it comes to power source then it's simply replacing, and that means money! Crap...
[Galaxy S III Original Android Development] habylab:
Regardless, it has been discussed in Andrei's thread about his fix being slow.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] lou_pams:
compatible with touchwiz 4.2.2?
[Galaxy S III Original Android Development] DerTeufel1980:
Seems like replacing power supply fixed it. Thank you for offering help.

can you link me to this please.

No. There are no sources available
[Galaxy S III Original Android Development] MuertoKo:
If I remember correctly as I was involved in one of the recursive discusions it has nothing to do with Andrei's fix. There is though some controversion regarding his last update (adding ABB stuff) and some data missmatch on GPU freq switching (limiting min_freq of the GPU to 266 and see it jumping down to 160), but no proper reports from dev's not Andrei had the time for it.
[Galaxy S III Original Android Development] habylab:
Okay, now this is interesting. Must of been ill when this discussion popped up - did not know about the GPU stuff, which could defnitely cause stuttering.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] MuertoKo:
I can't properly report or anything about that, couldn't get the time to experiment myself... But according to some reports in the thread seems so, might be just an issue on setting values on Stweaks though... If you can check that and reach any conclusion let us know please :)

On the other hand, the "stuttering" issue can't be related to emmc fix, just because it happens on Xda app or whatever, which is not doing any kind of i/o activity right? Not really in the business and this might be pure bs, but makes some sense to me...

Aaaanyway, only weird stuff I have in this kernel is my gps/wifi combo not working as it does in Perseus and I really need it for gaming purposes, not behaving wrong at all, just different... Might be newer Wifi drivers or some gps tweak... who knows!
[Galaxy S III Original Android Development] DerTeufel1980:
There has been an app for gokhanmorals s2 kernel, which displays current gpu freq. I tried it on my note2 and it was working well. Unfortunatelly i have lost the app by replacing my device. Maybe you know it or can find it. It only was posted in his kernel thread. ..
[Galaxy S III Original Android Development] MuertoKo:
Referig to Mali Status? Read this name many times, never managed to made it work though.
[Galaxy S III Original Android Development] DerTeufel1980:
Yes. Didnt remember the name.

Why didnt it work?
[Galaxy S III Original Android Development] MuertoKo:
Can't remember details and I'm not able to find a proper answer by searching but afaik Gokhan had to do some adjustments for it to work on S3... Will try to retest myself but I'm actually using Perseus now due to my special Gps needs, but as your kernel is based off Perseus it should whether work or not on both. Let's try to find the app now... :)

---------- Post added at 12:11 PM ---------- Previous post was at 12:05 PM ----------

Found the app, test, not working:

http://d-h.st/423

Guess it's trying to read the GPU active value from the wrong folder or sort of..??
[Galaxy S III Original Android Development] Teura:
And we're back with the log. It's ~15 hours long, and usage during the logging was a couple of races in Carmageddon, other than that pretty much unused. No music, no surfing the net or anything else really. The log is a couple of hours old and I've already taken care of WeatherUpdateService myself by reducing the update interval (The widget was on my lockscreen and I had forgotten 1h update interval on it). Though that alone doesn't explain anything, and by looking at the logs I've gathered after changing it, it didn't really do much.

But anyway, I again thank you all for helping me with this.
[Galaxy S III Original Android Development] MuertoKo:
Looks right to me...
[Galaxy S III Original Android Development] Teura:
Well, it isn't.

Deep Sleep (): 10 h 36 m 2 s (38162 s) Ratio: 67,2%

Awake (): 5 h 10 m 37 s (18637 s) Ratio: 32,8%

Screen On (): 42 m 52 s (2572 s) Ratio: 4,5%

The ratio between deep sleep / awake with only 42 minutes of screen time is not normal.
[Galaxy S III Original Android Development] DerTeufel1980:
Have you tried without wifi?
[Galaxy S III Original Android Development] Teura:
Yes. I nornally do with Wifi off all the time, but this time it was on for the log since I'm currently located in a place where Edge is the best I can get for connectivity. From experience, Wifi isn't the cause here.
[Galaxy S III Original Android Development] habylab:
Well your phone was in deep sleep for 10 hours 36, but also mainly at 200mhz. You don't have any major wakelocks, and screen time is low. Try tweaking your governor so the up threshold is higher, I'd recommend zzmoove with higher up thresholds.

You also have poor signal for 5 hours, try to find a better modem

200 MHz (): 3 h 59 m 8 s 25,3%

Deep Sleep (): 10 h 36 m 2 s 67,2%
[Galaxy S III Original Android Development] MuertoKo:
It is, at least according to the wakelocks! :D I ment there's nothing on the log that leads to this awaken time, no rogue app, no high alarms, at least no that you hadn't mentioned before. You may try disabiling location in google maps, freezing G+, Greenify Facebook App, switch Off Google Now...

All this usually helps just in case you hadn't done it already, but I actually prefer some drain and more usabilty now, but always nice to know what is killing your battery!
[Galaxy S III Original Android Development] Teura:
The reason I have bad signals I already told in my previous message about the Wifi. Last three days I've been pretty much in the middle of nowhere so the signal will be weak every now and then, so I'm not concerned about that. But as for the other things mentioned, I'll try.

Thanks for these as well. I don't have either G+ or Facebook installed, but I've removed some more stuff I felt like I don't need.
[Galaxy S III Original Android Development] habylab:
Is there a way to test whether FIOPS or ROW is better as an I/O? FIOPS v1 was great but had issues, so removed from his i9000 kernel. Would be interesting to see whether it is a match for ROW now.
[Galaxy S III Original Android Development] amppen:
Well, you could run custom Antutu benchmark with just I/O, SD read and SD write checked. It's fast to test it like this, so you might want to give both schedulers a few runs and see which one has better average score.
[Galaxy S III Original Android Development] gordonx10i:
[MENTION=3262915]habylab[/MENTION]

Androbench

https://play.google.com/store/apps/details?id=com.andromeda.androbench2

A lovely tool for testing read writes.

Also look at "lagfix" it improved my speeds
[Galaxy S III Original Android Development] habylab:
I compared 4 tests for Fiops and Row. Interestingly, Fiops had over 50mb read speed 3 times, but dropped to 31.1 MB on one occasion, so is unstable. The write speed was 2mb lower on average and Row was consistent throughout. Depends whether you want stabability or higher Read speed!

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] amppen:
Good findings. You think there could have been another process that requested for read at that one time, so that the benchmark app had to share read access and had lower speed for that reason?
[Galaxy S III Original Android Development] habylab:
Doubt it, tried with extra reboots and swapping which one I changed too, similar results.
[Galaxy S III Original Android Development] habylab:
I believe, judging by the tunables in Trickster, the zzmoove version is outdated - I can't see a limit for sleep freq for example.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, compared to the version of the author of this governor, it is outdated. But I also made my own changes to the governor, and I don't want to revert them. I have to take a deeper look what changes I want to use.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] habylab:
Awesome, changes are the gradual increase option? Thank you, glad to see you have not just chucked it in.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] ZaneZam:
Hi Teufel,

Yea it's outdated indeed *g* but no need to revert/mod anything your changes will be included (thx btw. working good *g*) in the upcoming new version v0.5 beside of some other stuff ;) u are on my "send to list" so i will provide u the actual sources then.. at least if u are interested

Just finishing everything, but documentation is holding me up a little bit atm ;)
[Galaxy S III Original Android Development] habylab:
Looking forward to it tomorrow then!

...kidding, take your time. Reap the rewards soon.
[Galaxy S III Original Android Development] ThePureHeart:
I'm consistently getting 4-5hrs screen on time, which is great!

Touchwake on

Row

Zzmove, 200-1200MHz

Underclocking has no perceivable difference. Zzmove seems so be a very good performer

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] x10i DauL:
Sry for dumb question, but what exactly is touchwake?

Regarda

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] sherlock5545:
If the screen times out, you can set a specific period of time within which you can turn the screen on again just by touching it.

Sent from I9300 - UltimaROM - Boeffla Kernel
[Galaxy S III Original Android Development] danarama:
I've only every used Devilq recently. It has a few more configurables. I may try zzmove though, it sounds interesting and apepars to be under constant development.
[Galaxy S III Original Android Development] ThePureHeart:
It seems from past experience that devilq visits the higher cpu speeds a little more often.

I've tested zzmove for a day and I'm going to test devilq now for the next run of my battery.

I got 18hrs with 5hrs screen time in zzmove, I suppose it'll be similar on devilq. My underclocking is also probably contributing a little.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] habylab:
I do the same as you, get the same results and pure speed also.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] duttyend:
Linux kernel 3.0.81

Very fast kernel !

Thank you very much !

To let you know, just in case, a new linux kernel version is out.

Keep up the excellent work :good:
[Galaxy S III Original Android Development] danarama:
Request for future (when computer fixed :) )

Please could you implement exclusive wakelocks for bbs from siyah?

Many thanks
[Galaxy S III Original Android Development] ThePureHeart:
Great :)

From my quick tests with above average use it seems zzmove is slightly better on battery life.

I'll be sticking to zzmove for now. Here are my settings for those who want it:

zzmove

200MHz - 1200MHz

row

Touchwake on

If you experience graphics glitches, turn up GPU frequencies a notch for each step.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] danarama:
I'm trying zzmove now too. No matter what I choose, Android OS is taking up the biggest part of my battery. I just can't seem to narrow it down with bbs.
[Galaxy S III Original Android Development] x10i DauL:
Same problem here with latest PA

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Do you think its a pa thing?
[Galaxy S III Original Android Development] habylab:
I have it on the stock too!

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] danarama:
Have you managed to track the root cause?
[Galaxy S III Original Android Development] ThePureHeart:
With 3.57 the Android OS issue has gone for me. I don't think it's a PA issue, probably just a setup issue.

Android OS at 18% for me. Screen is at almost 40%, which is understandable given the 5hrs that it stays on. I also have Anker 2200mAh battery.

What is your screen on time and how long does your battery last you for a full cycle?

Do you have a BBS log available? I can compare it to my next log and see what's different. Maybe also post a screenshot of your battery history from android settings.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] habylab:
Not really, no huge wakelocks!

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] danarama:
It still lasts the day. Just less screen on time (2 hours ish). There are some signal issues through the day but this is always the case. Not much in the logs. Kernel wake locks are a bit higher, mostly network related. My usage has been unusual this weekend but i'll get a log on Tuesday when the days are normal again but not much there. I have the same setup as normal. I can't pin the issue on a kernel or rom change. Using pac nightlies
[Galaxy S III Original Android Development] habylab:
There was an update 3 days ago on the Note 2, could be potential for an update soon then! Not asking, just keeping people informed.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] habylab:
Just noticed, sorry for double post, that my phone always has two cores online with zzmoove. Weird?

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] ThePureHeart:
How did you check that? I've been trying to find a way to monitor activity of each core.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] STAticKY:
I find cool tool the best app for this purpose

TP.
[Galaxy S III Original Android Development] habylab:
I use Trickster settings, has the info too as well as other perks.

Multicore saving, is 2, 1 or 0 best? I read 0, as it is in your kernel, but also 2, as in Perseus. With 2, my phone has 2 cores on, whereas at 0, only one.
[Galaxy S III Original Android Development] ThePureHeart:
I'd like to know more about "charge soft voltage".

It reads 4300000mV and I can't figure out what that reflects.

Battery sticker says 3.8V

Also, does "Step 1 Threshold Up" mean how much load is required to go up to Step 1? If so, does that mean "Step 2 Threshold Down" means load required to go down from Step 2 to 1?

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] danarama:
Imagine it says "threshold up from step 1" and "threshold down from step 2"
[Galaxy S III Original Android Development] habylab:
Good description!

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] danarama:
Using SetCPU, zzmove has decided that it wil not store my "governor" tab settings. I even factory reset and reflashed everything fresh, it just changes back to defaults on every boot. DevilQ working fine.

Bad thing is with defaults, zzmove wants to stay between 1300 and 1400MHz. Although it was fine this morning. I've literally formatted every partition and reflashed everything. Really odd. Gone back to DevilQ
[Galaxy S III Original Android Development] ThePureHeart:
I've also begun to experience problems with zzmove :/, using devilq now as well

I've got a charging problem... I've been plugged in for at least 4 hrs and only charged 50%.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] danarama:
Itr's weird how it all of a sudden just went odd and nothing, no matter how fresh I start - can revive it.
[Galaxy S III Original Android Development] dhirend_6d:
That s not zzmove. That is because of the charging voltage I presume. O__O

This kernel supports sTweaks?? If yes, open sTweaks and goto the Power tab. There, in the end you will find Hard Charging Voltage. Change it to 4.35 V(Default).
[Galaxy S III Original Android Development] ThePureHeart:
Nope, I didn't say it had anything to do with the governor, just a separate problem :)

I only see soft voltage charge and it's already at 4.3 which is the default for this kernel

I've flashed kernel again so that should fix it

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] dhirend_6d:
Hmm. I once had this problem. I could only charge upto 54 percent. And it was because of the hard voltage. Ohk so you reflased the kernel. But reflasing the kernel resets everything?? O__O If nothing works just try the reset button in sTweaks.
[Galaxy S III Original Android Development] ThePureHeart:
It's not compatible with STweaks but I've reset everything.

It seems to be fixed now.... I hope :D

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] habylab:
Use Trickster mod

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] danarama:
It doesn't work for me. It's not the settings app though. Theres no way with default settings that zzmove should be running my cpu at 100% permanently.
[Galaxy S III Original Android Development] zodiaxe66:
One way to avoid your battery acting crazy is always to flash on full battery.it shouldn't be necessary on gs3 because it auto calibrate,but sometimes it apparently is..there is a tool on gs2 forum called "fuelgauge tool",should work on gs3 to. I think:p

Or try one of the battery calibration tool's on market.

Root of the cause:unknown...to many kernel flash in to short of a time,before bat.bin settles?
[Galaxy S III Original Android Development] orangerot.:
Resetting the battery stats is completely nonsense and has nothing to do with a not charging phone.. They don't even have to settle.. Also a kernel flash has nothing to do with them.. Maybe the battery gauge is a little bit incorrect right after a rom flash as the system needs more power (setting up stuff in the background after/during first boot) but after a few minutes, when the setup is finished they'll be back to normal without resetting them...

I think there's also a complete explanation about the "mystery of resetting battery stats" and why it's unnecessary (search for it, to lazy to explain it :D)

If the phone doesn't charge it's your charger fault. If it supplies an unstable power your phone will decrease the charging input until a stable power is detected.. Often it goes into a loop ending up somewhere at 200 ma/h instead of 1000.. Result is that your phone charges slow or even decharges while charging..

Workaround is to throw away the crappy stock charger or enable "ignore unstable power detection" and enable "ignore safety marging".. I'm not completely sure if this kernel has that feature (can't test it as I'm on leaked 4.2)but since it's based on perseus it should be available ;)
[Galaxy S III Original Android Development] danarama:
In my signature 2 posts up ;)

Xda app hides it from you
[Galaxy S III Original Android Development] ThePureHeart:
Dianne Hackborn from Google/Android debunked the whole battery stats nonsense.

Read more: https://plus.google.com/app/basic/stream/z13dgb0rksywh3muq222fzkqnwfgdbgrk04

Sent from ThePureHeart's I9300 Boss Edition

---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------

Those two options (ignore 100mA safety margin and ignore unstable power detection) are available in this kernel. What do they actually do?

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] orangerot.:
They turn of that unstable power detection -> if unstable power is detected there won't be a "decrease loop", but the input stays on 1000 ma/h and the phone charges up ;)
[Galaxy S III Original Android Development] ThePureHeart:
I needed this yesterday :eek: Thank you so much! :3

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] sherlock5545:
Not entirely related, but the Nexus 7 sometimes gets stuck at 100% on the battery indicator and there's no other way than wiping the stats to make it work properly again. At least for that reason it's useful :)

Sent from I9300 - UltimaROM - Boeffla Kernel
[Galaxy S III Original Android Development] habylab:
Hope your computer isn't R.I.P. like the X-bone!

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] DerTeufel1980:
no, it is not ;)

uploaded new kernel :)
[Galaxy S III Original Android Development] RuralGalaxy:
Downloading! Thx master!

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] habylab:
Oh you little devil, you ;) could I ask for your opinions on Pimp My ROM, whilst you're here. A lot of kernel tweaks included, are they needed? Like disable I/o overhead statistics, disablw sleepers etc. Thank you.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] nfsmw_gr:
Can you please update the kernel config app?

It's the only reason i can't switch to this kernel. :(

Thank you. :)
[Galaxy S III Original Android Development] MrxSiN:
Deleted. Just an awful question. It already in Changelog

zzMoove 0.5 is released. Waiting it be ported in this kernel :D