yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] DaveX2012:
I bought new charger last week ( Samsung Charger ).
[Galaxy S III Android Development] kadopt:
Samsung usb cable is notorious for being rubbish.
[Galaxy S III Android Development] andip71:
Oh really? Thanks for that information. I must have completely missed it.

Where can we get the betas you mentioned? Would love to check it out, although I have no problems at all.

That was, sorry, waste of money. Original Samsung charger and cable are known to be huge crap.

You can however enable both "ignore" options in Boeffla-Config charge control. This should fix your issue if your charger is not complete crap. Comes with a minimal risk of frying your charger, but never heard of that ever.

Andi
[Galaxy S III Android Development] alcaholjunkie:
I find the USB charger that came with my s3 to be good. I do use a Nokia micro USB cable with it though as the one that came with the phone is crap. ^_^
[Galaxy S III Android Development] boyheadkick:
http://xdaforums.com/showpost.php?p=55202253&postcount=6444

-aL

tapatalked from my super duper palm top computer
[Galaxy S III Android Development] flither:
Confirmed. My Samsung charger died after 3 months, so I binned the usb cable as well. Cheap unbranded charger from a phone shop and usb cable for 3 euro working charmingly fine for almost 2 years ;)
[Galaxy S III Android Development] eeleater:
Funnily enough my Samsung Charger works without any problem whatsoever. Even the cable doesn't have problems. Are there maybe different chargers?

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] kadopt:
My charger is good but the cable is rubbish as it charges with random currents ranging from 300 to 800mA. My moto defy cable can charge up to 1200mA (but I think the limitations is the charger's 1000mA output).
[Galaxy S III Android Development] flither:
As far as I know charge current changes depends on battery percentage. It's on max when battery is less than 50%, then after that it reduces the current, and when near 100% the current drops to minimum. So the random changes doesn't mean the cable is bad, and the max charge current of 800mAh is ok.
[Galaxy S III Android Development] kadopt:
Actually no. Charge depends on kernel setting, charger output and cable quality.

According to your statement if my batt was low then both cables would charge at maximum value but that was not the case, with Samsung was random and with Motorola was always the same value (the one set on kernel settings). Use Galaxy charging current app to monitor the charge values.

My situation is more than proven and tested!

Also voltage and current must be higher than the ones provided by the battery otherwise it will not charge (basic electronics).
[Galaxy S III Android Development] flither:
I was referring to 3c's portal (Battery Monitor Widget maker). But maybe he was talking about stock rom, idk. Here's the link http://www.3c71.com/android/?q=node/2549
[Galaxy S III Android Development] andip71:
beta5

Hi all,

beta5 is ready for you, for all 4 kernels:

2.4-beta5 for CM11, CM11 NG, Omnirom, Omnirom NG !!!

Change log

Support for ppp widget app (allows external modems connected via OTG to work, e.g. 3g or LTE modems)

Improvements for OTG-connected LAN adapters (DNS resolution now working)

Configuration interface /proc/config.gz enabled (important for developers and kernel porters)

Only non-NG kernel: Rebased with latest patches of official kernel repo

Only NG kernel: Implemented security patch "futex-prevent-requeue-pi-on-same-futex"

Added two more fixes (one on mempolicy tmpfs and one on CPU hot plugging)

Boeffla-Kernel startup script redesigned and improved

Boeffla-Kernel internal busybox deployment now working completely fine

Removed some build tweaks to ensure higher stability

Updated ramdisk to version of nightly 01.09.14

Enjoy

Andi
[Galaxy S III Android Development] ScratMan38:
In reality, you both are right.

As said by [MENTION=5605175]flither[/MENTION], the battery charging current (and charging voltage) is managed dynamically, according to the battery's voltage and temperature. This is mandatory to avoid damaging the battery and keep the control of the chemical process in the cells.

[MENTION=3723165]kadopt[/MENTION], the current indication given by monitoring applications is based on the value read from the control registers from the charging system in the phone (a dedicated DCDC converter). But this value is only a limit setting, it fixes the maximum value the DCDC will allow to charge the battery ; it's not the value of the current actually flowing into the battery, this one is adjusted dynamically, as said before.

And the current in the charging cable may not be higher than the max current setting, the charger is providing 5 V to the phone, but the DCDC in the phone converts it to a variable voltage from 3 V up to 4.2~4.3 V during the charging phase. Considering a lowest charging efficiency of maybe 80% (I don't have the exact number, I was working on DCDC for RF amplifiers in the modems, those were at 93%), if the current in the battery is maxed at let's say 1000 mA at 3.6 V, the current in the cable would be (3.6*1000)/(5*0.8) = 900 mA.

Your issue is only due to a protection in the charging system. The DCDC converter is monitoring the input voltage and current, to check its stability. If the voltage and/or current in unstable (it may be due to faulty charger or cable), it will reduce the max current allowed in order to improve the stability of the voltage and current. By disabling this protection with custom kernels, charging at max current will be allowed again, but there is a risk for the DCDC in case of over-voltage at the USB port.

So, in case of issue with slow charging, it's better to keep the stability protection and try with a different cable (first) or charger (if changing cable was not enough).

ScratMan, ex Application & Customer Support Engineer on Power Management and Analog @ ST-Ericsson... RIP ST-E
[Galaxy S III Android Development] kadopt:
[MENTION=3609110]ScratMan38[/MENTION]

Resuming... As I said, dodgy cable. :)
[Galaxy S III Android Development] iamdutchy:
looking for comparisons

[MENTION=947981]Lord Boeffla[/MENTION] could you recommend Governor/IO, CPU and GPU settings for optimal performance on my GS3 i9300?
[Galaxy S III Android Development] andip71:
Not seriously as it depends on so many factors, mainly on your usage pattern.

Of course I would overclock to the maximum both CPU and GPU (also overvolt to make it stable), use intelliactiveq governor, row schedulers.

But best is to ask here, were all the configuration specialists can be found:

http://xdaforums.com/galaxy-s3/general/unofficial-boeffla-kernel-app-profile-t2621308

Andi
[Galaxy S III Android Development] Bryan_B:
Beta 4 and 5 gives me random freezes every time. Using always lastest temasek room, NG kernel. Beta 3 is fine..
[Galaxy S III Android Development] aliw32619:
No problems here , using ArchiDroid 2.X
[Galaxy S III Android Development] XDAMaxe:
no freezes (never had) with boeffla NG-omni and carbonrom ...:good:
[Galaxy S III Android Development] andip71:
I am also on Temasek every then and now, no freezes ever.

Also no other reports on beta4 for almost 3 weeks about freezes.

Andi
[Galaxy S III Android Development] ginzo:
Same for me, no freezes with temasek rom and Boeffla Kernel since ages (at least from v121) xD

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] khanmein:
no freeze on v123 temasek.
[Galaxy S III Android Development] mortoss:
Hi,

After beta5 ng instalation I had to roll back to beta4 due to 6 random reboots about 40-90 sec. after the boot. I use Neatrom. No reboots on beta4 at all.

Thx
[Galaxy S III Android Development] andip71:
Can only have been a flashing problem. No reboots here at all, on many different roms.

But I never use Neatrom honestly...

I would re-download again and try again.

Andi
[Galaxy S III Android Development] simplicio11:
No reboots on CM 11 latest nightly ( Beta 5 NG).
[Galaxy S III Android Development] ficko_98:
No reboots on slimkat 7.8 too!
[Galaxy S III Android Development] nicola1989:
No random reboot on the last cyanogenmod and lastly kernel
[Galaxy S III Android Development] Bryan_B:
Thats strange...

My phone random freeze and reboot only with beta 4 and 5. With beta 3 with same settings, its fine...

zzmove moderate, no zram, no uv and no oc.

Any idea?
[Galaxy S III Android Development] andip71:
Well, from beta3 to beta4, only 3 things have changed according to the change log:

- Update to zzmoove 0.9-beta4 (credits to ZaneZam)

- Support for external OTG connected webcams

- healthd spamming kernel log fixed

Nothing makes really sense for your issues, but I would at least try pegasusq for a test, to rule out the first point etc.

Andi
[Galaxy S III Android Development] NoxOn3:
@ lord boeffla Ok, just one question. I'm on PacMan 4.3, and I want to run spirit.fm. With the "stock" deliverd aosp kernel I had no problems with it playing music. With your kernel radio seems dead. Any idea how to fix it without changing kernel? Irgendeine Idee?

---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------

Ok, just one question. I'm on PacMan 4.3, and I want to run spirit.fm. With the "stock" deliverd aosp kernel I had no problems with it playing music. With your kernel radio seems dead. Any idea how to fix it without changing kernel? Irgendeine Idee? Möchte mein Radio gerne weiter nutzen!
[Galaxy S III Android Development] Bryan_B:
Running pegasusq and no freezes or reboots till now.
[Galaxy S III Android Development] ZaneZam:
running zzmoove only for ages here and no freezes :D
[Galaxy S III Android Development] flither:
running zzmove? what a surprise ;) but seriously - I never had problem with any gov, must be questionable phone or...some tunables didn't load properly? hmmm
[Galaxy S III Android Development] migz012788:
Hi. I've flashed Carbon Rom with this kernel. I'm having issues on the Backlight. (menu and back key). even though I enabled backlight for 3 seconds, it will lit up temporarily after I enable it. And it will lit up until the screen is off (not by 3 seconds on what I chose in settings) and afterwards after I try to turn on the screen, the backlight will not lit up, even though I press on menu and/or back key.

I assume that the issue might be on kernel?(not sure). Because I've tried to re-flash Carbon Rom in its stock kernel, the backlight is working fine. However, after I flashed the latest Omni-NG Boeffla kernel, the issue occurs again on what I have mentioned above.. Any insights about this? Thanks :)
[Galaxy S III Android Development] drgreenth:
Is it normal that with NG version I cannot read my ext4 external sd card?
[Galaxy S III Android Development] andip71:
No. Exfat enabled?

Andi
[Galaxy S III Android Development] drgreenth:
Why would I need exfat with ext4?

And no its not enabled.
[Galaxy S III Android Development] andip71:
Lol. True, I did not read properly. Sorry.

So no, I don't know then, never formatted my external sd card ext4. So I never tried.

But see also no reason why it should not work...

Andi
[Galaxy S III Android Development] K00li79:
Hey I like to give some feedback regarding the NG kernel. If running liquid smooth 3.2 the phone gets rather hot. With the normal cm kernel everything is fine ^^

Don't know if it's just me?

Not that it's a problem... My phone is flying pretty fast as it is now. ^^
[Galaxy S III Android Development] viktor92:
Yesterday I've upgraded to AD v2.5.3 from v.2.5.2, installed Boeffla 2.4 beta 5 linaro NG, and the temps were totally normal.

ps.: I'm back (as always) to AD 1.7.x

ps.2: With both roms I've used zzmoove without any problem.
[Galaxy S III Android Development] K00li79:
I use to be on normal cm11 and temps were fine on that rom to. It just heats up on liquidsmooth I guess. (in my case)
[Galaxy S III Android Development] sashundera:
Hi guys, I flashed 2.4 beta 5 and it all went okay, I installed the app and then enabled ums, then I clicked on profiles and clicked again on the default one just to see what hapens and the app FC'd. Then I went to open it again and it told me that the profile isnt yet enabled, that it can screw my settings so I decided to reboot. I then got the the CM setup screen, like I had wiped my phone? Everything was still there though, apps, wi-fi password, and it all works for now, including the app. I was just wondering why it did that, is it normal? Did I do something wrong? I still have my CWM back up, in case something happens. And I havent touched anything in the app, only enable UMS mode.
[Galaxy S III Android Development] mad_ady:
For a test disable Boeffla-Sound. If playback is ok, reenable it but keep DAC direct off.
[Galaxy S III Android Development] drgreenth:
You should give it a try. It does not work. No idea why I would use anything else than ext4/f2fs. Phone is the only device to use that card. Normal kernel works like a charm. I cannot mount it even by hand with NG.
[Galaxy S III Android Development] andip71:
What with the non-ng Boeffla kernel?

Does it work there?

Andi
[Galaxy S III Android Development] drgreenth:
Yes it does. Like a charm. Mounts to /storage/sdcard1
[Galaxy S III Android Development] andip71:
Ok. Just for me to check Configs again...

On 2.4-beta5 Boeffla non - ng it works, on ng it doesn't?

Thanks

Andi
[Galaxy S III Android Development] drgreenth:
Yep. Just like that.
[Galaxy S III Android Development] andip71:
Hi,

if you have capacity for a test, please let me know.

I found something in the kernel config which could explain it not being working on the NG kernel.

If you are willing to test (I have no ext4 formatted sd, so sorry), please PM me and let me know if you need Omnirom or CM11 kernel version.

Thanks

Andi
[Galaxy S III Android Development] sashundera:
I flashed 2.4 beta 5 and it all went okay, I installed the app and then enabled ums, then I clicked on profiles and clicked again on the default one just to see what hapens and the app FC'd. Then I went to open it again and it told me that the profile isnt yet enabled, that it can screw my settings so I decided to reboot. I then got the the CM setup screen, like I had wiped my phone? Everything was still there though, apps, wi-fi password, and it all works for now, including the app. I was just wondering why it did that, is it normal? Did I do something wrong? I still have my CWM back up, in case something happens. And I havent touched anything in the app, only enable UMS mode.
[Galaxy S III Android Development] andip71:
Interesting report, I cannot really say why this happened. Not without bc.log files etc.

Are you, by any chance, doing undervolting? It sounds a bit like a slight file system corruption on the /data volume.

If it does not occur again, you should be fine. But if it does again, let me know.

Andi
[Galaxy S III Android Development] khanmein:
enable boeffla sound with v4a installed cause no sound when watching mx player.
[Galaxy S III Android Development] andip71:
Viper4Android... well, I never use it.

But I know there are people around that use both Boeffla-Sound and v4a together. So maybe they can comment on it.
[Galaxy S III Android Development] Bryan_B:
Boeffla-Sound and V4A here working fine with MX Player.

Maybe its something with your mx player config.
[Galaxy S III Android Development] drgreenth:
I have capacity for testing. PMed.
[Galaxy S III Android Development] andip71:
Thanks. Answered... ☺
[Galaxy S III Android Development] Ping_2000:
I had same problem.

I had to reset xprivacy settings for config app.

Greetz

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] khanmein:
it works but after awhile everything no sound even call, dock sound, etc..
[Galaxy S III Android Development] Scarface1991:
I use both, the Boeffla Sound EQ and V4A together (incredible sound btw when used together in combination) and MX Player works fine, no sound issues at all. Seems to me like a ROM issue. What ROM are you using?

I use Temasek's CM11 and can't remember when I had sound issues the last time.
[Galaxy S III Android Development] makankaki:
i'm using this kernel (cm11) on SpiritRom, i cant watch video online, only heard audio, and there is no video.

with stock kernel, works fine
[Galaxy S III Android Development] GTMoraes:
Won't this GPU freq and load polling end up taking too much resources?

I used to use a tiny app that measured the system usage, and it brought my i9300 to the knees most of the time.

Sent from my Nokia 1100 using Snake II
[Galaxy S III Android Development] coolnand:
I'm at temasek v58 now. Some people have reported amazing battery life with this kernal. I have never got good battery life out of aosp ROMs and all except for Sammy ROMs. I dunno whether it appropriate to ask here, but is thr any settings I can use with ur kernal to improve the battery life? And yes I'm already on this kernal. Beta 7. Any help would be much appreciated!! :)
[Galaxy S III Android Development] cinciopillo:
I'm using this kernelwith Omega9 9.0 (CM10.2, Android 4.3) with no issue.

I will try to use it also after a ROM upgrade to Omega 10 (Android 4.3.1) and will report soon
[Galaxy S III Android Development] SkywalkerZ:
There shouldnt be an issue as android 4.3.1 is just a .(point) update from google which just fixes bugs and some lag issues
[Galaxy S III Android Development] JustArchi:
No, because we're talking about kernel interface here. Kernel itself needs to store this value anyway, it depends what you're going to do with the info kernel provides you, not feature itself.

Just take a look at /sys and /proc paths to notice that already it's overloaded with everything.
[Galaxy S III Android Development] rimad:
Can't turn wifi on :/ flashed latest stable 1.0 kernel,archi latest rom! Tried clearing cache and dalvik, tried reflashing kernel...no luck.
[Galaxy S III Android Development] andip71:
Most probably the modules are missing then.

Go into Recovery mode, flash the kernel again there. I am 99,99% it works then.

Andi
[Galaxy S III Android Development] cerealguy:
On last Jellybam 1.0.0 RC2 , last 1.0 stable cause bootloop...I've resolved reflashing rom...Anyone have the same problem?

Inviato dal mio GT-I9300 con Tapatalk
[Galaxy S III Android Development] rimad:
It worked! Thank you
[Galaxy S III Android Development] cerealguy:
Inviato dal mio GT-I9300 con Tapatalk
[Galaxy S III Android Development] menl:
wait for new beta!
[Galaxy S III Android Development] zerosys:
Wow, 1.0 works fine with my 4.3.1 rom!

But i have a question, the developers of my new rom are bringing out nightlys, is there any problem with flashing the new version every day and then flash the 1.0 Boeffla Kernel every day. Or could that either destroy the device or simply make rom dont work or something like that?
[Galaxy S III Android Development] donalgodon:
There's always a risk to flashing anything, and while flashing does incur some wear on the SD memory, it's not likely to cause any catastrophic failure, so the short answer is no, it won't damage your device to flash the ROM and then the kernel.

I try to not flash every single day, but I sometimes do update daily. It just depends on whether or not the nightly actually has introduced changes that make doing so worthwhile.

It's your choice, but if your worried about the potential wear from flashing, I wouldn't be, generally speaking. I've never had a device fail from too many read/write cycles, and I've flashed thousands of ROMs to various devices over the last few years, sometimes three or four times a day.

Relax, and use your device the way you want to. If it's going to die, it will, but the odds are very much in your favor.
[Galaxy S III Android Development] andip71:
Yep, 2.0-beta1 will have Pacman compatibility, so your issues should be resolved then as well (untested as I do not use Pacman, but you will tell me :) )

Andi
[Galaxy S III Android Development] menl:
small test for latest BAM-Rom 1.0 RC3

Boeffla-Kernel 1.0 stable - bootloop

latest Yank555 - bootloop

latest temasek - working!
[Galaxy S III Android Development] GTMoraes:
Any ETA of it? Any "closed alpha" or something? I really miss some of the Boeffla Kernel features

Sent from my Nokia 1100 using Snake II
[Galaxy S III Android Development] andip71:
Latest tomorrow.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] BioVolt:
Looking forward to this update, missing Boeffla kernel so bad ╯﹏╰
[Galaxy S III Android Development] indigold:
Will ur kernel work on temasek rom
[Galaxy S III Android Development] tisazalay:
It does already and probably will... [MENTION=2332422]temasek[/MENTION] will move to omnirom base and I'm pretty sure boeffla will support it too :)

Edit: [MENTION=2332422]temasek[/MENTION] just uploaded a screenshot of its upcoming omnirom based rom using temasek's kernel. Boeffla will work.
[Galaxy S III Android Development] andip71:
How should we help with these kind of vague report?

Which kernel exactly, NG, non-NG?

Configuration?

Which app for video online?

And and and...

I mean, I will anyway not be able to help as on all my roms (CM11, CM11 Temasek, Omnirom, Slimkat) video streaming is working fine. But maybe others could contribute.

Andi
[Galaxy S III Android Development] makankaki:
Non-NG, zzmoove (battery plus) CPU and GPU voltage -25mV

i tried YouTube and IGN

btw, i dont know what the difference between NG and non-NG. (and of course i use the kernel without NG written on it)
[Galaxy S III Android Development] andip71:
Just tried Youtube on Official CM11, latest nightly, with both Boeffla CM11 kernels.

Playing just fine.

Do not know what SpiritRom has done different...

Andi
[Galaxy S III Android Development] Scarface1991:
Maybe you could try to make a Nandroid backup and afterwards try a different ROM (like Temasek CM11 for example) and see if it works with a different ROM, if it does then you know it's a ROM issue.
[Galaxy S III Android Development] khanmein:
temasek.. now working.. very weird one even my ext sd card often become empty
[Galaxy S III Android Development] aliw32619:
Every time i restart my phone my Readahead buffer jumps to 2048 what's causing this? Using AD 2.X Boeffla Beta5 NG
[Galaxy S III Android Development] andip71:
Yes, weird. Welcome to the world of experimental AOSP software :)

My ext sd card is never empty. I have a 64 GB sandisk class 10 card.

Maybe beta5 kernel is a little bit more "picky" about lower-quality SD cards than previous versions, as I reverted some tweaks back to be closer to stock again.

But this is then just like the "stock" kernels.

Another app conflicting, a script in init.d conflicting, rom settings under performance settings conflcting...

That are the usual suspects.

Andi
[Galaxy S III Android Development] aliw32619:
I scanned for app conflicts and no potentially conflicting apps found , so what else should i do?
[Galaxy S III Android Development] andip71:
What I wrote:

another app conflicting, a script in init.d conflicting, rom settings under performance settings conflcting...

The conflicting apps scan cannot cover all apps, as I do not have a list of all possible apps that can conflict. init.d, rom settings... just work through all of them...
[Galaxy S III Android Development] jackq:
I have some wakeup issues when use Boefflas kernel and Temasek CM11 ROM v134 or earlier.

Tried beta 4 and 5.

when someone calls me the screen remains switched off after a few seconds the screen turns on. bell also is intermittently not play continuously. The same is in clock, alarm sound works but the screen remains off. On stock kernel is all OK.

Tried to clear all files using Boeffla cleaning script, installed kernel again - nothing help, any clues?
[Galaxy S III Android Development] andip71:
Known issue, no direct fix available.

If you search this thread, you will see from a user comment, Temasek in his kernel put a hack in which makes the device respond faster. But with the cost of battery consumption, so I will not put that in.

Andi
[Galaxy S III Android Development] cink40:
I believe that kernel in temasek ROM is stock CM kernel?