yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Olynth:
I dont think your problem is kernele related, i think router settings are the problem. The router askes you to log in every time wifi disconnects and reconnects.
[Galaxy S III Android Development] mahe.:
Thanks. but it doesn't happen with AOSP ROMS. like my friends are not having any issue if they connect from device like moto G and nexus 5.
[Galaxy S III Android Development] viktor92:
I'm a flashaholic too, but I'm really trying me to calm down because the phone is performing like a charm with beta 5 linaro. Thank you andi an zane :good::good:

pd.: anyway I'm keeping an eye over the next kk arter port V3 :D
[Galaxy S III Android Development] AssassinGEO:
I was right. It's all about intelliactive. Running pegasusq standard and getting the battery life of old intelliactive.

Now, with intelliactive, I get 20 mins of SOT from 100% to 90. Big jump and couldn't fix it no matter what I do. But I need that governor as all others are laggy, slow, jittery. Any help? :(
[Galaxy S III Android Development] andip71:
Quick OT:

For all users with a OnePlus One device, Boeffla-Kernel is now finally available for it as well.

Find thread here:

http://xdaforums.com/oneplus-one/or...-kernel-1-0-2-0-beta-09-t2899974#post55918936

Andi
[Galaxy S III Android Development] Clark789:
Puuuh, strong argument for the OPO... ;)

Regards

Clark
[Galaxy S III Android Development] lsalamun:
Zzmoove moderate - 1600MHz, touchboost 800MHz?

No lag for me.
[Galaxy S III Android Development] AssassinGEO:
All zzmoove governors give me very stuttery performance. Video playback as well as camera recording are also jittery, so I keep away from them.

Also, not the best battery life with zzmoove, too. My phone hates that governor.

Just moved from pegasusq to intelliactive and getting good battery life again. That's why I mentioned that governors are getting messed if choosing one and then another. From standard pegasus, intelliactive is performing badly, from pegasusq, it performs smoothly with good battery life.

One thing still left: intelliactive starts to suck the battery again after recharge. My phone always hated boeffla, too, and intelliactive was first governor to fix compatibility with boeffla and my phone and now even that configuration screws up everything.

My phone sucks, really. Back to old days when I didn't knew anything about rooting and my phone was running smoothly and I was getting 6.30hrs of SOT. I f*cked my phone up, even tho I was careful.
[Galaxy S III Android Development] lsalamun:
What's your asv level? I'm lucky to have 7 while most people have 2 [emoji1]

Yesterday i watched captain america and not a single stutter, also, i am frequently recording videos and not a hitch, don't know ehat could be the problem for you, maybe a placebo?
[Galaxy S III Android Development] AssassinGEO:
2. What's the difference?

Btw, wish it could be a placebo. Just believe me, you will be frustrated by zzmoove while using my phone. Camera video recording is soo jumpy, you can't call it a placebo.

Same goes to media playback and overall UI performance. Stutters everywhere and after some time, animations get worse and it needs a restart. : \

EDIT: Drain after recharge with intelliactive. Battery or governor problem?

I really don't know what to do. All other kernels\ governors are giving lags. How to live with this phone :(
[Galaxy S III Android Development] ZaneZam:
The question is what did u set in addition? I think i read between the lines that no governor fits your needs and all are laggy so something different must be the problem. What happens if u start from scratch by resetting app settings?
[Galaxy S III Android Development] lsalamun:
Well ASV level is the 'quality' of your chip, he higher the better, but, i assume that this could make any problems.

Did you try getting back to stable version of kernel, resetting app, full wiping, or maybe using greenify as i see you have lots of notifications? (app running all the time can also slow down the device nevertheless of governor and kernel settings).
[Galaxy S III Android Development] abhibnl:
I was on zzmove battery yank and phone was fluid, i was on zzmove moderate phone was more fluid, i switches to zzmove performance n it was freaking fluid. I really can't understand why it's laggy for you. Now i'm using pegasusq as battery lyf is good with it and phone is fluid at the same time.

Sent from Galaxy S3 Powered by Temasek + Boeffla
[Galaxy S III Android Development] AssassinGEO:
So, I have 2... Defective phone, already?

Btw, nothing is needed. Only intelliactive gives performance which is good and never slows down.

Phone is fluid for me, too, but these governors make it lag every half or minute. Zzmoove is the worst of them.

The thing is, I was on AOSP for 5 months and everything was fluid, games were running smoothly and video recording was smooth, too.

Then I decided to move to 4.3 and as soon as I did it, I started having problems and it took 2 months to get my phone stable with 4.3. But, since then, 4.1.2 or AOSP ROMs are veeery laggy for me. Games are stuttering as crap and video recording is jittery (same ROM, same old settings).

So, again, has my phone got defective?
[Galaxy S III Android Development] MD500:
Try using unbouce module to limit wakelock time, debloat ROM, greenifying app,this may work.

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] AssassinGEO:
Thanks for tips, but hey, as I mentioned, this happens only with intelliactive governor. :)

I have some other global problems, but I don't сare about them, as for now. I just wanna know what the hell happened with the governor I was using for so long and why can't I fix it even after resets, mega wipes and etc.
[Galaxy S III Android Development] rp158:
Andy, I recognize myself: the kernel is the last adress for misty bugs :)

Thanks for your work.
[Galaxy S III Android Development] lsalamun:
Haha it's not defective, these levels are quality of the chip, not in degradable phase, in manufacturing phase, for ex. higher elvel chips can go higher with verclocking and undervolting without any issues or crashes, while lower can not go in such extreme manners and so on, many i9300 have asv 2 (mass production hehe) you don't have to worry just don't go extreme with kernel tweaking. :)
[Galaxy S III Android Development] AssassinGEO:
I always overclocked my phone higher than I have now, it can do it. But why does intelliactive drains my battery fast after charge? I thought I would get some ideas here :(

I just managed to get 3.49h of SOT from 79 to 10%, so the battery is working more than normal for me, but that crap!
[Galaxy S III Android Development] lsalamun:
When i tested intelliactive, i figured out that it keeps the cpu more on the higher frequency, so, i skipped it, in cpu-z also it kept the clock on highest level for almost 2 mins, then turned off 2 cores and lowered the clock, so, obviously it will drain more battery but give more smoothness, it's like interactive but with some minor tweaks, and you can explaint PegasusQ as Ondemand but with hot-plugging.

And a quote from explanation of governors:

LINK

Either you sacrifice the battery life over performance, vice versa, or you buy a new battery, nothing i can say more unfortunately.
[Galaxy S III Android Development] AssassinGEO:
No, dude, remember my pics? That SOT was very good for such an old battery. Intelliactive was giving the same time as pegasus.

It does the same even now, but it's bugged.
[Galaxy S III Android Development] lsalamun:
Well then, time passes - battery dies.

Try after a few cycles (don't reboot and get crazy with the phone), if it doesn't get better, either change to a more battery saving governor or buy a new battery, but hey, governors are really not that big game changers, they are like 10%, maybe more maybe less, you know apps are getting heavier with every update, maybe thats the cause.

But first, chillax with all that flashing mania and see if it'll settle down. :)
[Galaxy S III Android Development] AssassinGEO:
I'm not flashaholic, dude :D I was on 4.3 for 4 months, then on AOSP for 5 months and now on 4.3 since May. As soon as intelliactive started doing this crap, I started wiping, resetting, reconfiguring. Turned out that it's all about the governor. Apps are also all older ones, downloaded apk's, tested it. Believe me, no app drains my battery, and it lasts as long as it did when bug is gone, as I already mentioned.

I'm charging now and see if that comes again. Will probably wait, maybe that bug will vanish itself.
[Galaxy S III Android Development] lsalamun:
Then intelliactive has some weird stuff going on in there :D

-OT new Tapatalk rocks!
[Galaxy S III Android Development] nkirk:
Did you try trimming the emmc? You can do it either via boefflea app or through lagfix app.

I suspect it could be an application/bloat which keeps the disk and cpu busy all the time. Try installing a unmodified stock rom after a mega wipe and trim afterwards. Try out the kernel in default config and see if it improves the situation.

And no. Its not the asv level. Mine is 2. I hve no issue with any governor, performance or battery life. Phone accepts heavy uv too.

Ps; an Asv 7 will have a tad bit better battery life and better thermals comparing a lvl 2 chip at stock state. Thats due to the factory uv, I mean the lower voltages/leaks.

//nkirk
[Galaxy S III Android Development] dedicatedgr:
sound on headphones

When i m listening music for 10 minutes with headphones i have no sound issue. i try to set on boeffla sound and mess with settings reboot.. 4 minutes sound and after bye bye.

whatever i done the same.

I tried also with screen on so its not the cpu state...something happens between my sound chip and kernel.

I dont have the same problem with bluetooth.

I m on sensation s5 v7 4.4.2 rom Archiport based.
[MENTION=947981]Lord Boeffla[/MENTION] help me please.. i m on the latest beta
[Galaxy S III Android Development] andip71:
Well, I would not know how to help. It is for sure not kernel related, as all other users would have the same issue then. Also when you switch off Boeffla-Sound, the kernel behaves like stock kernel in this area.

So I suspect something else is going on. Other audio mods, init.d scripts (especially when you came from other kernels there might be left overs in init.d folder etc). Other apps hooking into the analog signal path...

I have not more input, I am sorry.

Probably I would go for a clean new install first...

Andi
[Galaxy S III Android Development] SignetSphere:
Have you tried changing the profiles of the governors on the config app? (for eg. zzmoove - battery yank extreme etc.) I think the profiles are messing with this one. Try changing the governor profiles that balances battery and performance like zzmoove - optimal. Also set the min frequency of the CPU to 700 or 800 Mhz. This is what I did when I was having issues with the audio while my phone is on standby (screen off). After I applied those settings the stutters my sound issues have disappeared. Note that we're using the same custom rom here.
[Galaxy S III Android Development] Amir12hbk:
I love thie kernel from my S3

he was amazing!!

I wish you could make it to Note 3 N900 (4.4.2) (International Exynos)

we have only one kerne l :(

but I love to say.. Great work man!
[Galaxy S III Android Development] C.3.S.4.R:
i have a problem with the carging rates, i set to max in both 1600mA , and i have a good cable and an asus carger 2.1A but when i plug my phone only gives 1A i try disable safe margin and unstable power, but still in 1000mA and max are 1600mA help please
[Galaxy S III Android Development] andip71:
You did unplug the charger, then change the settings, and then plug the charger again, or?

If this does not help, also especially if you already set the two ignore switches to on, something else is odd.

Also when some of the chargers claim they can deliver 2.1, in reality it is many times different.

I can charge with my HP Touchpad charger up to 1600 without issues...

Andi
[Galaxy S III Android Development] C.3.S.4.R:
yes i did, and i have also an ipad charger that gives 2.1A too but same results. i try with different rates and toggle on and off the switches but still getting 1000mA current
[Galaxy S III Android Development] vladakster:
Speaking of charging, I'm wondering how you can limit charging current when you don't have a actual value of it?
[Galaxy S III Android Development] andip71:
Then I have no clue. Maybe the connector on S3 side dirty or faulty. I cannot say, pure speculation.

I think I do not understand that question?

Andi
[Galaxy S III Android Development] C.3.S.4.R:
i dont think so, when i'm on 4.1.2 works well i dont know if that affects but i have try a lot of chargers right now 5 in total and 3 cables and nothing, i'm gonna flash stable version of kernel and see how it works with that
[Galaxy S III Android Development] vladakster:
If I'm not mistaken, S3 doesn't have current sensor, so, how do you limit charging current?
[Galaxy S III Android Development] andip71:
Yes, s3 has no current sensor that can be read from outside.

But it has a Max-Chip to control the charging itself. And the chip can be programmed to only expect a certain max current.

So if you set this to 700 mA, it will only try to get 700 mA out of your charger.

And my app shows what the charger is told to use for the current (and as it does constant monitoring if the current is stable enough and then adjusts the current rate, this rate can even change).

If that were not in place, the S3 could not make sure it only takes 500 mA from an USB port and much more from a wall charger.

Andi
[Galaxy S III Android Development] vladakster:
Thanks for clarification my Lord! ?
[Galaxy S III Android Development] andjeomilosrdja:
Maybe try diffrent app for current reading? Could be the app issue.
[Galaxy S III Android Development] C.3.S.4.R:
i have tryed with the boeffla kernel config overview, with galaxy charger current, and also with the android terminal emulator and the same... maybe is and issue only in my s3
[Galaxy S III Android Development] andjeomilosrdja:
Don't jump to conclusion,maybe it's not the phone but rather usb cable;) (just to be sure)
[Galaxy S III Android Development] C.3.S.4.R:
i try with 3 usb cables and same.. well i dont give a f*ck
[Galaxy S III Android Development] MIKEMON:
to charge your phone, it is quite care if you have 4.3 or 4.1.2 fw

I recommend to flash stock rom a try with this kernel
[Galaxy S III Android Development] Wasim625:
My device is not opening my 80 g.b SATA hard drive via OTG cable. Is there some setting I am missing in the kernel or anything else or simply it can't use the 80 gb hard drive with the fone?

Whenever I connect the hard drive the fone says blank SD card. And prompts me to Format the HDD to make it usable with the fone.

It works, by the way, on a 16 gb usb and a 20 gb IDE hard drive.

Sent from my GT-I9300
[Galaxy S III Android Development] andip71:
I already connected a 320 GB USB harddrive via OTG successfully. It was however formatted as NTFS when I remember rightly.

So maybe you would need to activate NTFS module, if your drive is NTFS formatted.

Just a wild guess...

Andi
[Galaxy S III Android Development] MIKEMON:
Yep, for me too, everything is fine
[Galaxy S III Android Development] moffa89:
I connected a 1,5 TB USB harddrive via OTG successfully with no problems and it was NTFS formatted too. [emoji16]
[Galaxy S III Android Development] moffa89:
and what is the standart mb value for i9300 in zram for stock 4.3 100mb or 300mb? swappiness is 60 on stock?
[Galaxy S III Android Development] andip71:
300 mb on one device.

Andi
[Galaxy S III Android Development] moffa89:
Thx andi, because the kitkat ports arent good for me [emoji16]
[Galaxy S III Android Development] SuperAce609:
Isn't 4 devices technically faster? What zram settings do you recommend? I always use 4 devices at 90 swap with 240mb.
[Galaxy S III Android Development] andip71:
He asked what stock zram is.

I always recommend 4 devices, yes.

I barely use zram though, and when then 4 devices and 600 mb total size.

Andi
[Galaxy S III Android Development] MIKEMON:
yep, that's exactly my settings

the stock rom
[Galaxy S III Android Development] ikong7:
I want to install viper audio mod do I need it or its just the same with the boeffla sound options?...
[Galaxy S III Android Development] andip71:
It is definitely not the same.

Boeffla-Sound works directly on hardware of the WM audio hub, Viper mod is a pure software solution.

I think there are people using both together and are happy, but for the start I would advise to only use one of them.

Andi
[Galaxy S III Android Development] drmjp93:
Andi,

Can't it be made possible that wifi direct works?
[Galaxy S III Android Development] andip71:
Wifi direct working with all my Samsung based kernels.

I do not know what exactly you mean.

Andi
[Galaxy S III Android Development] drmjp93:
M on CM 11, inbuilt option for wifi direct in wifi settings, don't work.

So in mid sept, i heared someone talking about Bofella should make it work.

In that correspondence, i m querying if wifi direct (inbuilt) works?
[Galaxy S III Android Development] andip71:
Ok, you are in the wrong thread. That is why I was confused.

You are in the Samsung thread, not CM !!!

But no, for CM it is known to be not working and will most likely never work as some code required for it is not disclosed by Samsung.

Andi
[Galaxy S III Android Development] drmjp93:
Extremely sorry for the wrong place.

Thank for the info.
[Galaxy S III Android Development] mpasanthosh:
DAC Direct

Hi Guys,

Can some please explain me what the DAC Direct is and how can i use the DAC direct if it is turned on.

I read that 'By switching DAC direct to on, you will bypass the output mixer in the signal path and connect the DAC directly to the headphone amplifier.'.

If is the case i set an EQ in stock music player and it should not affect the signal output ?

How do i verify if it is turned on or turned off?

Please confirm if my understanding is correct/help me with more inputs on this topic.

I have a Audison Bit 10 wired to a Helix P400 powering Focal K2 power series comps in my car and would like to use my mobile to provide the input signal to DSP.
[Galaxy S III Android Development] andip71:
The output mixer has nothing to do with the EQ in stock equalizer.

DAC direct changes the signal path within the Wolfson Micro Audio hub to have a short cut between data input and audio output to the headphone. It bypasses basically a circuit on the audio hub which is called output mixer where many different signals can be mixed together (digital data, microphones, etc.).

So all functionalities will still be available if you use DAC direct or not.

And the only way to find out if it is switched on or not is to look up in the Boeffla-Config app.

Andi
[Galaxy S III Android Development] moffa89:
And what are your swappiness ? 60? 80? [emoji16]
[Galaxy S III Android Development] andip71:
60 is stock.
[Galaxy S III Android Development] moffa89:
Okay thanks
[Galaxy S III Android Development] Clark789:
Just a gloss: after installing the new Boeffla App (2.1.48) and the new SuperSU (2.13) the energy consumption of my S3 is much lower than before...

And some apps (esp. Spiegel Online) runs a lot smoother than before...

Regards

Clark
[Galaxy S III Android Development] AssassinGEO:
Apps can't change the overall system performance. It's you thinking like that ;)
[Galaxy S III Android Development] Clark789:
No, i don't think that. I only noticed it... ;)

And i'm not the only one.

Cheers

Clark
[Galaxy S III Android Development] boyheadkick:
actually it does..exactly the reason we debloat the unwanted apps, specially the ones who have high wakelocks, and retain the useful ones
[Galaxy S III Android Development] AssassinGEO:
Well, I'm with latest boeffla app and no supersu installed. I think I'm good :)
[Galaxy S III Android Development] SignetSphere:
uh... doesn't the boeffla app need root permissions to work? How can you even use it? :eek:
[Galaxy S III Android Development] andip71:
Yes, but maybe he has a different superuser mechanism installed?

supersu is not the only one, there is still Koush's superuser as well...

Andi
[Galaxy S III Android Development] SignetSphere:
Of course I know that xD but isn't Koush's superuser app hasn't been updated in such a long time now? Also searching xda... he's already a retired developer.

EDIT:

Well If he is using a different superuser app (clockwork mod's superuser perhaps? But that hasn't been updated since feb.) then it's fine i guess? XD
[Galaxy S III Android Development] AssassinGEO:
Forgot to mention that I don't have the app itself installed, didn't mean the whole root. :)
[Galaxy S III Android Development] MEHDIMYADI:
[MENTION=947981]Lord Boeffla[/MENTION]

CPU Governor ZZMoove v1.0 beta1 released.

please release new ver.
[Galaxy S III Android Development] andip71:
Hehe, thanks. Yes, I know. I am using it for more than a week in my OnePlus kernel.

And have ported it already to this kernel.

Just need to do a final compile and give it out.

Maybe even later today :)

Andi
[Galaxy S III Android Development] andip71:
New app

Hi all,

I just released Boeffla-Config V2 in version 2.1.49 now.

And the good news is: This is the last time you need to manually download and install. This version has from now on an online-updater included, so in future this goes easy for you and with only 3 clicks :)

Boeffla-Config V2, version 2.1.49

17.10.2014

App updater now downloads and install new app fully automated !!!

Kernel, modem and recovery flash now possible for tar, img and bin files

Improved LED test button behaviour

New menu to manually check for app updates added

WIFI supplicant scan interval can be overwritten in settings

Settings regrouped

Enjoy

Andi
[Galaxy S III Android Development] 87Fra87:
I have boeffla kernel and sensation ROM 7. With boeffla config i have disable zram but after one day RAM is saturated now free RAM is 100 mb i have kill RAM but after free RAM is only 120mb. What i can do? I want that when i kill RAM after free RAM is 300 or 400 mb.....
[Galaxy S III Android Development] andip71:
New beta

Hi all,

ok, next beta for you now (both Android 4.3 and 4.4. kernels). Maybe the last one before the version gets the next stable again.

Version 5.4-beta6 /

Version 6.1-beta6

17.10.2014

Update zzmoove to version 1.0-beta1

Update exFat driver to 1.2.9

Update the flash binary in the boeffla-kernel-reset recovery script, bump to version 3.1

Only 5.4-beta6: Update ramdisk to version of firmware XXUGNH4

Enjoy

Andi
[Galaxy S III Android Development] MIKEMON:
Hello friend

primarily thanks for the update and hard work

great thanks

New Zzmoove you do not know what has changed?

But great to see again step towards

Thanks everyone i ZaneZam for governor, which is my favorite ..
[Galaxy S III Android Development] ZaneZam:
ZZMoove Changelog: http://xdaforums.com/showpost.php?p=42637763&postcount=2

in Current Test-Versions ;)
[Galaxy S III Android Development] mahe.:
phone restart while charging gone away?

Hi Andi,

while reading NIK60rom KK-4.4.4 thread. i have that phone restart while charging gone away after using devil kernel. So the phone restarting issue is related with kernel? many suggested that it is with boot-loader. your comments on that..

link

http://xdaforums.com/showpost.php?p=55977097&postcount=214
[Galaxy S III Android Development] andip71:
Seems the kernel. Maybe in combination with bootloader, never analysed it deeply.

But I have no plans to fix anything on it.

I only charge when phone is switched on + 4.4 kernel has only low priority for me as it is experimental.

Andi