yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] dantheman122:
Yep that's right, would just need to be updated. So long as they're both 4.1 based it should work, but it was a bit glitchy and took some tinkering with to get it working perfect. I ended up deciding it wasn't worth the effort and only use my Sammy rom for the camera when it's important. Everything else on my 4.2 rom.
[Galaxy S III Original Android Development] STAticKY:
Never used andrei's implementation so I don't know how bad the flickering was but in temaseks kernel with zzmoove 0.5 it flickers. It not too noticible but I can see it potentially annoying some users. It seems most pronounced when there is a lot of white being displayed...

TP.
[Galaxy S III Original Android Development] DirkStorck:
Hi. At the moment I am trying you kernel 1.4.8 and I must say I like it really a lot...very smooth and that Zzmoove feels really snappy but I have a big problem with MTP that I had with older Siyah kernels as well.

For me it looks like that the content of the external sdcard doesn't get updated.

If I copy I file from internal sd to my external sd and than use the PCs file explorer to look into that folder that contains the new file the file isn't there. Even if I disconnect and reconnect my phone to the PC it is still not there. (its not a file starting with a dot)

Does this kernel handle MTP different compaired to perseus kernel? With that one I never had a problem with MTP.

Thank you for a great kernel!

EDIT: After I have switched between MTP and PTP and back I can see my file! :)
[Galaxy S III Original Android Development] thuanngotau:
First try! Very nice Kernel!

Touch Wake is really impressive, I love it (saving the lifetime of my GS3's physical buttons) but the battery life is my concern since the screen is easily waken up accidently inside my pocket
[Galaxy S III Original Android Development] DaReDeViL:
I will look into this asap.

The phone can not wake up "accidentally" because when it goes to sleep after touchwake timeout it is just like pushing the power button, touching the screen can't can't wake it up !
[Galaxy S III Original Android Development] DaReDeViL:
That's why I don't include any script to wape dalvik cache ;)
[Galaxy S III Original Android Development] DaReDeViL:
I doubt it is related to the deadlock bug we are talking about now, which is "supposed" to happen when switching governors
[Galaxy S III Original Android Development] DaReDeViL:
Nice project m8 !!! Dual-boot also ? :p
[Galaxy S III Original Android Development] alberber:
I've created a new thread in general section about the script and asking for someone who is interested in the same thing. I'm not a linux developer, nor a programmer or so... Just know few things about shell scripts but...

So maybe someone would like to update it. It would be very cool.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] ZaneZam:
hi STAticKY,

in case there is Dynamic LCDFreq Scaling enabled this is a known glitch and exactly as u said on bright areas on the display it is more noticeable. in this case we have to live with that, it's the lcd freq switching event ;) and this was also stated in andrei's thread!
[Galaxy S III Original Android Development] Yank555:
See the github link it explains which tunables need to be changed. You can do it via script (always), using a tool like SetCPU or Android Tuner which gives you access to the governor tunables (and in fact do in the background what the script does). As for stweaks, no clue if support is added, but it certainly can be added.

Well the flickering is "normal" and proof it's actually working. With this you ask the screen to be refreshed only 40 times a second instead of normal 60 times, that is 33% less often, so flickering is inevitable and "the whole point" of this if you want... these 33% less screen refreshs is where the battery gain is supposed to happen.

But I will be honest, I say supposed as I can't say I noticed much of a difference, but anyway, was nice working on implementing it either way and the only way to know for sure is to do it, so with zane we did :D

And indeed there may be one more noticable event when the switch happens (40->60 or 60->40), this is supposed to be reduced by using higher kickin up and down delays, as higher values makes it switch less often as you need to keep your CPU on a similar load level for longer before it decides to switch in either way, so it just doesn't switch wildly all the time. So if that is the flickering you mean, then maybe yes, it might flicker less than Andrei's implementation as he only implemented kickin up.

JP.
[Galaxy S III Original Android Development] JB-007:
Yep i think nothing related to the gov issue, but just noticed this freeze appended with 1.4.8, never before.

I'm using exactly the same settings than prior versions (i/o, gov, freq, uv..)

Cheers
[Galaxy S III Original Android Development] qtwrk:
Alright,,, thanks both of you, I guess i was mislead in the first place...
[Galaxy S III Original Android Development] FPSKunal:
Guys I am facing a problem with my first ROM. The WiFi is not working on the first ROM but WiFi is working fine on the second ROM. On my first ROM whenever I try to connect I get authentication error. I have tried two different Roms and it is the same. 1st ROM is Sammy based and second ROM is PA 3.60. Any help would be appreciated.

"Sent from Westeros using a Raven"
[Galaxy S III Original Android Development] xclub_101:
Reboot with 1.4.8 and Viber :(

Yesterday I installed 1.4.8 and I used Viber for like 20-30 minutes and all was OK, today however I had a reboot in the middle of a call (like 2-3 minutes into it) just like I had before with 1.4.5 and 1.4.6 :(

I am with Omega 43.2 (4.1.2-based) and I have zram (400mb/90%) and touch-to-wake active (20seconds).

I will now return to Siyah 1.9.1 which I had for 1-2 days before 1.4.8 - however I did not use Viber so much during those days so I can't say 100% that Siyah 1.9.1 is "safe" in that regard.
[Galaxy S III Original Android Development] ThePureHeart:
[MENTION=1897326]googy_anas[/MENTION]

You might want to check this out about zzmove 0.5. developer said it's not up to scratch yet so if anyone has trouble, please keep this in mind.

http://xdaforums.com/showthread.php?p=42565034

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] romskii:
On zzmove there are several lags, we know :P

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] ZaneZam:
Did I wrote anything about lags? In fact there are freezes but actually u are right, those freezes are kind of inifinite lags :)
[Galaxy S III Original Android Development] romskii:
No, there are some lags.

It takes a long time after waking up the phone to do something, like the cpu needs some secs to calculate (think about what to do :D)

The battery life on your new version is amazing

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
Push up you screen off CPU freq. limit, it will be faster, but you may have a little less good battery in standby, that's the price to pay ;)

Or just try to use 4x up and down fast scaling when screen off, that helps as well.

JP.
[Galaxy S III Original Android Development] FadeFx:
I tried to reproduce the bug mentioned in zzmoove by switching governors several times from and to zzmoove and running all day with it afterwards i have yet to see a freeze. There are some microlags here and there, but i think they are caused by zram, which in turn is way better than in previous versions where i had to disable zram as it gave me big lags after a while of use. [MENTION=1897326]googy_anas[/MENTION]

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] romskii:
Hmm... On version 1.4.7 everything was fine with stock values. And smooth :)

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] alberber:
I actually reverted back to 1.4.7. Feel it smoother.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
Since you went from 0.4 to 0.5 (zzmoove) you can't use 'the same' settings, there are a bunch of new tunables (which you need to consider if you're on 0.5), some tunables behave differently (like fast scaling), and other tunable's defaults may have changed (not sure, though).

JP.

Sent from my SlimBean 6 / Yank555.lu CM10.1 kernel v1.6c-beta2 (Linux 3.0.81) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] sherlock5545:
Great kernel, thanks for the hard work. As of now I don't experience issues with the new version of zzmove.

Sent from my GT-I9300
[Galaxy S III Original Android Development] alberber:
I think the problem is some of us don't understand very well those new tunables so... I would like to know more about these things but I must wait till Zane or someone create some profiles or scripts... I guess I could ruin battery/performance in my phone if I started changing parameters which in fact don't know what they mean.
[Galaxy S III Original Android Development] Yank555:
Obviously, playing with governor tunables is a bit more 'demanding' than just chosing one, but well worth the effort ! :)

I found Zane's explanations in his sources pretty good, have you given a look at them ? i think the link must be 1 or two pages back.

If anything is not clear don't hesitate to ask, if I can I'll try to answer/explain ;)

But in essence, the new beast needs to be calmed down a bit more than the old one ;)

JP.

Sent from my SlimBean 6 / Yank555.lu CM10.1 kernel v1.6c-beta2 (Linux 3.0.81) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] DaReDeViL:
Version 1.4.9 ONLINE !!! ;)

[14/06] Version 1.4.9 :

- Linux : Updated to

Linux 3.0.82

:good:

- Fixed some lags

- Fixed misbehaving MTP

EDIT : I am in serious need of a break. I think 1.4.9 will match 99% of what's expected, so there won't be any 1.5.0 version until there's something really interesting to play with ;)
[Galaxy S III Original Android Development] romskii:
Already flashed ;)

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] alberber:
Yeah, it's more difficult. Thanks for your sincere help. And yes, I took a look at Zane's Git but, really, very hard to understand every concept when you don't have a good base in programming, computer science... Even harder when it's not written in your natural language (Spanish), you know...

But thank you very much, good to know there are people disposed to help others. :thumbup:

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] FadeFx:
Your comfort goes first... thanks for what you have done yet...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] Jeshuuu:
direct wifi works? When I tried this kernel does not work. this solved?

Sorry for my bad english.
[Galaxy S III Original Android Development] i04055:
after flash the 1.4.9 my computer cannot detect the phone neither adb... anyone have the same issues?
[Galaxy S III Original Android Development] sohail77:
Where's the guide for dual boot..:confused::confused::confused:

The dual boot process is same as siyah kernel or its different
[Galaxy S III Original Android Development] STAticKY:
Same as siyah

TP.
[Galaxy S III Original Android Development] asphaltkiller:
yes me
[Galaxy S III Original Android Development] MrxSiN:
other things is, reset settings to default doesnt apply to GPU volt. It not reseted
[Galaxy S III Original Android Development] EJ98:
The abb still does not apply on boot, needs manual application in stweaks ...:(

Spy sappin' my post!
[Galaxy S III Original Android Development] amppen:
You could put your values manually to your profile file (/data/.siyah/default.profile) using a text editor. I'm sure they will stick then.
[Galaxy S III Original Android Development] romskii:
Could you check microphone?

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] DirkStorck:
Hi [MENTION=1897326]googy_anas[/MENTION]. Thank you for looking into that MTP problem...It is working allmost perfect for me now but I still got a litle problem.

Here is what I jhave did.

1) Connect cell phone to PC

2) Copy a file from internal to external sdcard

3) Look into that folder...the file isn't there.

4) Disconnect and reconnect cell phone to PC

5) Look into that folder...and the file is there. ! :D:laugh:

Before the file wasn't still there after 5)

Thanks again for a realy great kernel! :good::highfive:
[Galaxy S III Original Android Development] alberber:
Many thanks to Googy and Zane for the great kernel and governor. My phone is very responsive again and the battery is good as well.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] GabrielSousa:
i have this problem too
[Galaxy S III Original Android Development] DirkStorck:
Works for me without any problem....
[Galaxy S III Original Android Development] lmulli:
ADB works fine if I switch the connection type to PTP. Doesn't show as a drive though with either MTP or PTP chosen as the connection type.
[Galaxy S III Original Android Development] DirkStorck:
Hi,

if I understand it right I can run Samsung based 4.1.2 ROM as first ROM and a CM10.1 based ROM as second ROM.

What is the best CM1.1 based ROM or which do you use?

Thanks!
[Galaxy S III Original Android Development] STAticKY:
Not a good idea to ask what the "best" ROM is as its subjective. You will get flamed Lol. In my opinion you can't go wrong with temaseks rom

TP.
[Galaxy S III Original Android Development] romskii:
Or Stock CM, or or or

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] STAticKY:
Exactly Lol. Try all the roms then make a decision yourself. We all have different uses for our devices. What's good for me might not be for you

TP.
[Galaxy S III Original Android Development] lmulli:
I wouldn't limit yourself to using just cm based ROMs. There are a myriad of good ROMs out there for you to try. I've settled on carbon for now but that's not to say that its better than any other such as temaseks, aokp, paranoid, root box etc...

Spend a day or two trying them all and see which ones you like best, after all its you who is going to be using it and what suits one person may well not suit another.
[Galaxy S III Original Android Development] exxpired:
Do you still need to play system sounds and reboot to get the call sound working?
[Galaxy S III Original Android Development] agentg1001:
Hmm mtp actually stopped working for me after installing 1.4.9
[Galaxy S III Original Android Development] STAticKY:
Not sure about other ROMs but I do on temaseks rom

TP.
[Galaxy S III Original Android Development] DirkStorck:
For now I am trying "ReVolt 4.3"...lets see how it woks out :)

---------- Post added at 05:38 PM ---------- Previous post was at 05:25 PM ----------

Now I have that problem TOO :crying: :( :crying:

The only thing I have done in the mean time was to install a second ROM.

Thats really serious!!! HOW should I now use adb or copy any file to my phone from my PC using MTP ?!?
[Galaxy S III Original Android Development] lmulli:
Adb should work fine if you switch to ptp in storage or at least it does on mine.

As for copying files from your computer to the device, for now I'd just dump any files in your drive/dropbox folder.
[Galaxy S III Original Android Development] DirkStorck:
ADB doen't recognize my phone any more and the USB icon on my phone where I can choose between MTP and PTP doesn't show anymore too, :crying:

Dumping files into gdrive folder isn't the solution....it worked before...something must have screwed up my phone...

YIPI YA YEA!!! I have got it working again (adb and MTP). I followed the procedure and used the driver from that forum [25.04.13 LATEST]Samsung USB Driver for Mobile Phones 1.5.23.0 [Win 8/7/XP] :D :D :D
[Galaxy S III Original Android Development] ANGEL4RIM:
I tried siyah for a few days and it was fine . I'll flash yours to see .

Is it okay if I flash your kernel over siyah? No need to wipe anything before flashing?
[Galaxy S III Original Android Development] ThePureHeart:
Come on dude... you don't have to wipe anything when it comes to flashing. Just flash.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] brujo55:
zzmoove governor update out.
[Galaxy S III Original Android Development] djskarpia:
problems with charging

i have problems with charging... since first boot i connected ac cable and while connected to power supply it continue discharging...so i changed from 800 ma to stock value but it's very very slow in charging.. ( i used always stock value but it wasn't so slow) ... what can it be? i9300 with carbonrom... thanks
[Galaxy S III Original Android Development] brujo55:
[MENTION=1897326]googy_anas[/MENTION]

please fix the slow battery charge whit this kernel.

i need to wait 3.5hours for full charge
[Galaxy S III Original Android Development] voodoofox:
Hi I got a deadlock changing governors.

I was on zzmove and changed to lulz.

I am on PA 3.6 and 1.4.9

I can send you my kernel settings.
[Galaxy S III Original Android Development] GabrielSousa:
didnt work for me :(

mtp dont work for me :(
[Galaxy S III Original Android Development] FadeFx:
Try using a non Samsung charger and cable. Their products are trash.

Use galaxy charging current from playstore to monitor your charging

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] MrxSiN:
1 more time, im back to 1.4.4. Same settings on 1.4.9 and use it for 2 days but it seem 1.4.4 more smooth in my phone. No screen artifacts, no lag, etc. 1.4.4 is the succesful one for me. :D
[Galaxy S III Original Android Development] DaReDeViL:
Version 1.2.0 ONLINE !!! ;)
[Galaxy S III Original Android Development] romskii:
For me boeffla was easy. STweaks is much more comfortable

No need for boeffla sound engine here. Voodoo sound is included. Try it and feel the power ;)

For changes look at the first post

Gesendet von meinem GT-I9300 mit Tapatalk 2

---------- Post added at 06:05 PM ---------- Previous post was at 05:36 PM ----------

But you don't have taken optimizations on lulzactiveq like on pegasusq?

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
I indicated the space savings instead of the compression ratio :eek:

In fact we are talking the same figures ;)

If the compressed size if 40% of the original, the compression ratio is 40%.

But the space savings is 60%.

So forget my previous post and let me try to rephrase :angel:

Using LZO I get an average of 33% compression ratio, meaning the amount of RAM needed is only 33% of the actual data size and the space saving is 67%.

Using Snappy I get a compression ratio between 30% and 45%, meaning the amount of RAM needed is between 30% and 45% of the actual data size and the space saving is between 70% and 55%.

So in compression ratio, the lower, the better !

In space savings, which is (100% - compression ratio), the higher the better.

JP.

PS: Damn, instead of clearing things up, I just did the opposite, sorry for that :eek:
[Galaxy S III Original Android Development] DaReDeViL:
Not now. It's planned for next version ...

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] DaReDeViL:
:eek:

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] qtwrk:
Flashed 1.2 , everything is good so far, continuing test.

The lag I mentioned before seems gone...
[Galaxy S III Original Android Development] Yank555:
Saw you switched back to LZO, that's a good move I think, worth a try, been doing the same in my beta and looking how it goes ;)

Just to be clear :

LZO = better compression, slower (but update made it faster)

Snappy = worse compression, faster (but less since the LZO update)

JP.

Sent from my CM10.1 20130504 / Yank555.lu CM10.1 kernel v1.5n-beta4 (Linux 3.0.78) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] DaReDeViL:
Yes i went for the lzo compression. Guess who helped me make the choice ? :D

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] romskii:
Mr Yank. I only see here german speaking Devs. Home sweet home

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] igoa:
Something wrong with the entropy. From 4096 bits only nearly a half is avaliable -> nearly every second jumps to 4096 -> immediately drops down to a slightly lower value than before jump and so on ... something "eating" entropy very fast ... In Perseus the is no such problem and avaliable entropy nearly 4096 bits always
[Galaxy S III Original Android Development] JB-007:
I tested 1.2 and noticed lags are gone. Now I'm able to down to 1ghz without lags.

Good job!!!!!!!
[Galaxy S III Original Android Development] DaReDeViL:
If only someone can clearly explain what is the benefit of having entropy always around 4096 ?

I benchmarked my kernel with seeder activated and deactivated ==> with entropy always around 4096, all benchmarks are lower than with "standard" entropy. Even cpu usage is lower on idle !

That being said, I may be wrong.

Anyway, you can always install the seeder app to have the same exact effect you're looking for :cool:
[Galaxy S III Original Android Development] STAticKY:
Try that same test but substitute seeder with crossbreeder...
[Galaxy S III Original Android Development] qtwrk:
just wanna say , is it really have any effects about this "entropy" thing ???

i tried before but didn't see any effective effect ? did i miss something ?
[Galaxy S III Original Android Development] mitky82:
Good kernel. I revert back to 1.1.0 because i have 2 reboots when i use facebook app and 1 shutdown when i watch flash video on stock browser. Whit 1.0.0 and 1.1.0 i dont have any problem. I don't touch anything from stweaks.

GT-I9300 XXEMC3
[Galaxy S III Original Android Development] xerxen:
Is the Hotspot error fixed? Its all what gok's kernel rly need
[Galaxy S III Original Android Development] DaReDeViL:
If on sammy 4.1.2 it's working. On cm10.1 it's not working but you can use third party apps until it's fixed

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] DaReDeViL:
Didn't you already have this problem with my other kernel ?

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] TigerCourage:
Will you be able to fix it? Or that depends on Gokhan?
[Galaxy S III Original Android Development] DaReDeViL:
I think it isn't even working on stock cm10.1 (if someone can confirm)

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] andrewilley:
One thing that I need from a kernel is the ability to adjust the S3's Headphone Amplification gain setting. The system default of 60+ creates a nasty low-level background hiss during audio playback, which is really annoying during low-volume listening. I've now set the gain to 40, which completely removes the hiss and gives me a perfect volume range for night-time listening. Result!

However, for some reason, after about 3-4 days this control stops working and the gain reverts to 60+ again, even though STweaks still shows my value of 40. Once this hasd happened, adjusting up or down in STweaks no longer does anything at all. If I reboot the phone, it automatically picks up my chosen 40 setting again correctly, and the adjustment control starts working again too.

Any thoughts on why this setting should stop working after a while?

Andre
[Galaxy S III Original Android Development] tr4usut:
Waiting one vrrsion for 4.2

Gửi từ GT-I9300 của tôi bằng cách sử dụng Tapatalk 2
[Galaxy S III Original Android Development] FadeFx:
Wait for Samsung to release 4.2.x kernel sources.

_________________________

tapatalked from GalaxyS3