yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] JustArchi:
No need to hurry Andi :).
[Galaxy S III Android Development] andip71:
Upload for CM variant started. Let's see if it goes through. If not I need to switch to ssh and do again.

Edit: Already switched to ssh now, this ensures it will be up in a few hours.

Andi
[Galaxy S III Android Development] nelsonw:
Hi! I have CM11 and 2.4 beta 1 kernel. While I was sleeping last night, my phone wasn't. But battery consumption was 2.9% not bad. Or BBS is wrong or why the phone didn't slept? On kernel wakelocks is power management something. Thanks!
[Galaxy S III Android Development] andip71:
Well, you lost about 3,9% per hour, clear indication the phone was not sleeping.

Check partial wake locks to see which app caused it.

Andi
[Galaxy S III Android Development] nelsonw:
RILJ (phone) and NplWakeLock (Google Play Services)

Any clue?

I changed to AFTR+LPA and now the phone slept for a few minutes... So i'll keep quiet so it can sleep... LOL
[Galaxy S III Android Development] rafaelbo:
RILJ is related to modem, but some users reported it may be fixed by turning android device manager (locate device) off.

Nlp is related to location services, Google location reporting.
[Galaxy S III Android Development] andip71:
[MENTION=5161352]JustArchi[/MENTION]: Both repos up now (CM11 and Omnirom).

Andi
[Galaxy S III Android Development] grebarne:
Hi I flash with this kernel 2.3a boeffla-kernel-2.3a-Omnirom-i9300.CWM for omnirom omni-4.4.4-20140714-i9300-NIGHTLY but it's not fix "charging animation not shown when device switched off".

someone has the issue ?

thanks advance.
[Galaxy S III Android Development] miketino:
Good luck with it all man:)
[Galaxy S III Android Development] mad_ady:
Some good news about the NG beta:

1. The phone doesn't freeze when plugged into a dock

2. I can now mount ext2/3 images on the phone. The previous kernels would fail and only allow me to mount vfat images.

Regular (but possibly not used very much) stuff such as nfs mounting also works.

Great job Andi and good luck with your new setup!
[Galaxy S III Android Development] quebec1:
i try on my I9300 with rom aosp NeatROM v6 (4.4.4) the kernel 2.3 stable, but i had some problem:

1) when the phone is power off, and i try to charge it i see on the phone battery with a withe circle at center and phone dosen't charge

2) in three hourse i had three freeze, when I pressed the button to turn the display does not turn it on and so I had to remove the battery.

now i reinstalled kernel 2.2 and it's all ok, but if i try 2.3a do i solve these problems?

sorry for my english
[Galaxy S III Android Development] Full HD:
Should be solved with 2.3a

Version 2.3a stable

13.07.2014

Fix "charging animation not shown when device switched off" issue if you are using a version higher than nightly of 07.07.2014 (by updating initramfs to CM nightly 12.07.2014)
[Galaxy S III Android Development] dhirend_6d:
Using NG kernel on NeatROM. The new zzmoove is actually better than pegasusq. Smoother scrolling. Smoother everything as a matter of fact. Bravo zanezam, :claps:
[Galaxy S III Android Development] boyheadkick:
Google play services updates keep this issue alive..i wonder how google does that

-aL

tapatalked from my super duper palm top computer
[Galaxy S III Android Development] flamelab:
The NG kernel is almost excellent here on SlimKat. Congrats to all those involved :)
[Galaxy S III Android Development] raviainani:
Tried CM11 version of NG on CM11... But laggy when playing games (subway surfers) no matter what config

Omni version NG on CM11 solved the issue. Smooth even more than Butter:D

Just wanted to report... Thanks a lot for all your work Lord and all those who are involved in this

i9300-cm11- boeffla-kernel-2.4-NG-Omni Version
[Galaxy S III Android Development] thycpt737:
NG is awesome! Unbelievable Antutu score with zzmove governor profile!
[Galaxy S III Android Development] khanmein:
did u test glatest google camera when taking blur will cause FC?
[Galaxy S III Android Development] abhibnl:
So u really mean gpu performance is far better on omni NG than NG? Overall UI responsiveness too? I wonder WHY? Both are based on same sources just intramfs is different.

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] Nic2215:
I'm using temasek rom cm based, just home screen and between the pages to pick application (I'm using trebuchet though) only I got lag with cm based kernel, but with omni ng non. So definitely got difference.
[Galaxy S III Android Development] raviainani:
I know what you mean but seriously this is happening...:confused: but anyways no matter what this is all time amazing kernel

i9300-cm11- boeffla-kernel-2.4-NG-Omni Version
[Galaxy S III Android Development] abhibnl:
Will definately try Omni version on my temasek's 114 too.

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] Yeti47:
Works fine for me, as long as you save to internal sdcard. Used to use xposed and pictures2sd and it failed.
[Galaxy S III Android Development] 200:
yes, and i spoke too soon. also the connect error appeared twice. going back to 2.3 for the moment on omni. :(
[Galaxy S III Android Development] boyheadkick:
Huh, so i'm not the only one..what rom you running?

-aL

tapatalked from my super duper palm top computer
[Galaxy S III Android Development] DualJoe:
Why is led brightness in CM color picker much brighter than under normal conditions? After pressing 'ok' the battery led goes darker immediately. Led brightness in Boeffla config is set to max (130) already.
[Galaxy S III Android Development] Buckycasuals:
A question: [MENTION=947981]Lord Boeffla[/MENTION]

What happens if i manually change SE_linux disabled to Permissive manually using an app.
[Galaxy S III Android Development] WhoDunnit:
Which app would do that? SELinux ModChanger can change between Permissive and Enforcing, but only if SELinux is enabled.

At the moment in 2.4 NG it is Disabled, so modchanger cannot change anything. In 2.3 you can switch, but when you switch to Enforcing, do expect problems with SU.
[Galaxy S III Android Development] JustArchi:
What? I'm using my AK with SELinux enforcing by default and never faced any issues with superuser.
[Galaxy S III Android Development] w0rinal:
Is blinking set to on? Apparently the brightness increases steadily until it has reached the desired level, but when the time it's lit is not long enough to reach that level, it doesn't.

That's my assumption

Sent from Boeffla Kernel powered Slim GT-I9300
[Galaxy S III Android Development] WhoDunnit:
True, and I already asked Andi to enable it (but hopefully defaulted to Permissive) in 2.4 NG. Most reported problems where for Samsung ROMs anyway, but searching XDA does give CM11 examples as well. So the answer should be rephrased: "At worst you could get a few unwanted results with apps that need special (root) permissions. On a recent ROM it is unlikely that you find any problems since those should have been fixed already." :angel: Agreed?
[Galaxy S III Android Development] Regash:
i have root problems on the latest slimbean boeffla combo because i enabled the root but the boeffla app told me it has missing root, pls help :((
[Galaxy S III Android Development] zeli9:
Sure, there is indeed no such thing as best ROM, best kernel, - we all have our preferences based on our own experiences and usage patters, people are free to use what they want. My earlier comment was concerning support from kernel developers for all available ROMs, which is simply not possible. I think people need to realize this. tbh, there are really too much half-baked custom ROMs around... I believe the QA and testing should be more strict, there are people releasing untested ROMs to the public without properly testing them, in fact some of them are being released without having been tested on the specific model they are being released for... this is unacceptable IMO. Sorry for the slightly off-topic discussion, but I though I need to clarify my position on the matter.
[Galaxy S III Android Development] Yank555:
I do agree with you on most of what you say ;)

Only thing is, the changes required for support of, let's say MIUI or Pac Man, is pretty ridiculous and not causing issues to other systems, so why not add them.

I was a bit lazy (I'm being very honest here :D) and got asked later to add MIUI support, Andi had done it already, and told me what to do, so that was pretty easy, and I added it in the next update of my kernel.

With PacMan I was asked first, had a look (took me a minute only), added it and pointed Andi to it and I think he will add it as soon as he finds time to do so.

QA will in fact be done by users if noone else does it, if something is flawed and can't be stabilised, it will not get used. But I'm not saying I find it ok to not test prior to releasing, I tend to test everything I release, I say tend to because :

- I won't be able to test as extensively a kernel for a ROM type (Sammy or CM10.1) I don't use one on a daily bases (CM10.2)

- I can't test i9305 versions as I don't own such a device, I normally don't maintain stuff if I don't have the device, but I got asked often and it's pretty the same device, so I made an exception

Changes we apply in these kernels are rather 'small' so you can assume if it works in one, it will work on the other, all these kernels are ~98% based on Sammy's sourcedrop, so one single base.

JP.

Send from my Note 3 (n9005)
[Galaxy S III Android Development] zeli9:
Thanks for the interesting input! Sure, small changes that don't have a potential to break anything and if they are easy to introduce should be welcome, I was referring to more substantial feature requests that people using various ROMs have been asking for. I do love accommodating and friendly developers, but I also believe that there's a limit to what they should accept, especially if such new features can cause major issues. Same thing applies to kernel developers.

But with pro developers like yourself and Andi users can feel safe with new releases since they have been tested to the best of your abilities and for that we thank you! :)
[Galaxy S III Android Development] andip71:
Hey,

try to remove root again, start the app again and have asking for root again.

Then accept.

Sometimes this helps.

But you are not using SuperSu or any other Superuser App on top of the inbuilt one, right? I heard many times this is causing weird issues.

Thanks

Andi
[Galaxy S III Android Development] AdrianM:
Go to Developer Options (if you don't know where that is, use Google) and make sure Root acces is set as "Apps and ADB". It might fix your problem.
[Galaxy S III Android Development] MBurns2:
Guys someone knows how to solve the first wakelock here? Thanks a lot

Inviato dal mio GT-I9300 con Tapatalk
[Galaxy S III Android Development] SiNtEnEl:
Did u mess with the Charge settings under Miscellaneous? Do u notice charging issues?

If so reset those settings, and restart the phone and charge your phone again. Check if the wakelock is gone.

If not try to fully charge the phone offline, then power it on. Check if the wakelock is gone.
[Galaxy S III Android Development] brujo55:
[MENTION=947981]Lord Boeffla[/MENTION]

linux update soon?
[Galaxy S III Android Development] GTMoraes:
Bootlooping on latest CM10.2 Nightly Based ROM (PAC-man AIO ROM). Probably outdated kernel
[Galaxy S III Android Development] MBurns2:
Mate i only change wall charger to 1000..as ever.

Thanks i will do some test

Inviato dal mio GT-I9300 con Tapatalk
[Galaxy S III Android Development] drelite08:
What governor are most of you using? When I used the stock boeffla kernel I found that zzmoove optimal to be best for me.
[Galaxy S III Android Development] dongfangri:
Sometimes some settings will not take effect.

For example, I set the max. cpu freq. to 1600MHz through boeffla-config, cm 10.2 settings - preformance - cpu also says max freq. is 1600Mhz. but max cpu freq. can only reach to 1400Mhz, according to the report of boeffla-config and system panel.

My settings:

Boeffla 1.0 B7 + official CM10.2 1016

Preset: Power
[Galaxy S III Android Development] GTMoraes:
Overclocking works here, both on Boeffla Settings and on the overall phone feel. Have you allowed root permissions?

Sent from my Nokia 1100 using Snake II
[Galaxy S III Android Development] andip71:
Yes, 2.0-beta1 will have the upstream to 3.0.100 built in.

But first I will make 1.0-beta7 stable, as with 2.0 series there will be massive changes the way the app and the kernel communicate. So, stay tuned.

PAC man rom not yet supported, also will come with 2.0-beta1 only.

PAC man requires support for an additional framework apparently (Yank pointed me to this), and I will put that into the kernel for the new beta.

Only explanation I have:

Make sure, CM does not overwrite the settings with its own settings.

There are configuration options in CM as well under settings, make sure you push them to the same config or better deactivate it.

Because then it is a competition between the app and the rom, and the rom will win this finally.

Just an idea, as it is working just fine for me.

Andi
[Galaxy S III Android Development] donalgodon:
[MENTION=947981]Lord Boeffla[/MENTION]

This kernel is so freakin' amazing that it ought to be the stock kernel included with CM for the GT-I300. A person would have to be deaf to not hear the difference between the stock kernel and Boeffla sound.

It's brought new life to the aging SIII. :good: Thanks for all your work.
[Galaxy S III Android Development] HorstiG:
Hammer :thumbup:

HGT - Galaxy S3 - Carbon-JB 4.3.1 - Boeffla Kernel CM10.2
[Galaxy S III Android Development] SavanTorian:
where i can get carbon 4.3.1 for s3 for testing? ;D
[Galaxy S III Android Development] alirezaafkar:
http://goo.im/devs/carbon/i9300/nightly
[Galaxy S III Android Development] GTMoraes:
Looking forward to it. It's a major improvement to use your kernel. Excellent work there :)

Do you think that 2.0-beta1 will be rolled out by the end of the week?

Sent from my Nokia 1100 using Snake II
[Galaxy S III Android Development] DualJoe:
No, charging led is not blinking and i can't set it to max either. Double brightness is only possible in CM11 LED color picker. I guess its a rom issue.

[MENTION=947981]Lord Boeffla[/MENTION]:

V2.4b1.CM11.NG: Occasional Wifi disconnects and Auditd constantly restarting. No Auditd bug on V2.4.CM11.

07-16 10:04:57.424 I/auditd (6321): Starting up
07-16 10:04:57.424 E/auditd (6321): Failed on audit_set_pid with error: Protocol not supported
07-16 10:04:57.424 I/auditd (6321): Exiting
07-16 10:05:02.439 I/auditd (6325): Starting up
07-16 10:05:02.439 E/auditd (6325): Failed on audit_set_pid with error: Protocol not supported
07-16 10:05:02.439 I/auditd (6325): Exiting
07-16 10:05:07.449 I/auditd (6329): Starting up
07-16 10:05:07.449 E/auditd (6329): Failed on audit_set_pid with error: Protocol not supported
07-16 10:05:07.449 I/auditd (6329): Exiting
07-16 10:05:12.464 I/auditd (6332): Starting up
07-16 10:05:12.464 E/auditd (6332): Failed on audit_set_pid with error: Protocol not supported
07-16 10:05:12.464 I/auditd (6332): Exiting

Edit: WiFi disconnection:

IEEE 802.11: deauthenticated due to inactivity (tim er DEAUTH/REMOVE)

Quite common bug on android though....
[Galaxy S III Android Development] Moster2:
Try to use titanium backup with superuser. It wont succeed in uninstalling apps or moving apps to system for example.
[Galaxy S III Android Development] JustArchi:
Do you have any other myths? :p
[Galaxy S III Android Development] ScratMan38:
Is it with stock CM superuser app or Chainfire's SuperSU ?

Titanium Backup have some incompatibilities with CM su app, by installing SuperSU and updating su binaries, it's working fine.
[Galaxy S III Android Development] JustArchi:
I've tested both superusers and both of them work fine.
[Galaxy S III Android Development] Delgadovsky:
Every time i flash a new rom always need to install Supersu app to update the binaries... The stock SU doesent update it. But i think that nothing have to do with kernel cause happen in all roms
[Galaxy S III Android Development] ScratMan38:
Yes, usually it works ; but I already had some failures in TB by using stock su from CM on several phones. Sometimes it works, sometimes not...

That's why now I systematically update su app with SuperSU.
[Galaxy S III Android Development] Moster2:
Make sure that it is also really removed and not just visually inside of the app.

The app stays installed with current archikernel and also stock cm kernel. Really only happens with superuser, not supersu.

It does not manage to correctly uninstall stuff.
[Galaxy S III Android Development] nightwing90:
I hope u already flashed Omni NG on temasek's 114 (CM 11 base ). I'm also waiting for your feedback so that I can try Omni NG kernel on my ArchiDroid 2.5.1(CM11 base) :cowboy:
[Galaxy S III Android Development] ayoubij:
Thats true. With built in superuser it doesnt work. With chainfire supersu it works
[Galaxy S III Android Development] JustArchi:
I'm not kidding you, it works okay. I even rebooted my phone to make sure. Maybe on other ROMs it does not, but on my AD 2.X and Enforcing AK, it works flawlessly.
[Galaxy S III Android Development] Moster2:
Going to try it later.
[Galaxy S III Android Development] ginzo:
Strange but I'll try it....! ?

Andi said that for temasek rom was suggested cm11 ? kernel, not Omni ? ?

But I'll give a try to check and compare ?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] LegendM:
Guys how can I download? Download link redirect to website,website redirect to here :D
[Galaxy S III Android Development] Moster2:
Click on Downloads on the left on the website?

http://www.boeffla-kernel.de/index.php/2012-10-31-06-13-16
[Galaxy S III Android Development] LegendM:
Well,seems like I have to rest,thanks for quick answer. My bad
[Galaxy S III Android Development] ginzo:
I confirm that boeffla ? omni kernel seems to make my phone with temasek rom v115 smoother! I see the difference ??

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] cloudx720:
There is no difference with omni and cm ng kernel, tested both for hours... Both exactly the same you guys talk out of your ass!

---------- Post added at 09:56 PM ---------- Previous post was at 09:43 PM ----------

Keep getting "can't connect to camera" error cm11 ng kernel...after taking video and alot of camera shots..it was my daughters prom and it let me down :( will this bug ever be fixed ffs always comes back this annoying bug. Can't wait to get my upgrade, FCK the S3!
[Galaxy S III Android Development] andip71:
I also think these camera issues will probably never get fixed...

Takes too long already ?

Andi
[Galaxy S III Android Development] boyheadkick:
hearing this from you yourself is disheartening andi..i hope i can save enough to buy me a nexus5 in the coming months :(
[Galaxy S III Android Development] marenp:
It's not S3 fault at all... I don't have any problems with that, video recording plus taking snapshots, taking pictures.... Everything is fine.
[Galaxy S III Android Development] ayoubij:
What about making a version of the kernel with the camera fix :$
[Galaxy S III Android Development] boyheadkick:
andi's been doing that for long, he makes one, it works...but then the rom devs make another change in their kernel bases and everything get's borked again..
[Galaxy S III Android Development] 200:
omni-4.4.4-20140716-i9300-NIGHTLY
[Galaxy S III Android Development] andip71:
There is no fix that works for 100% of the people.

It is not even kernel fault only. So it makes no sense at present before this gets stable in stock.

And this might never be, or how comes this problem is open for months now already...

Andi
[Galaxy S III Android Development] lchiocca:
Wow Andi! You got internet again! That was a fast move. Welcome back ;) how's the new place?
[Galaxy S III Android Development] abhibnl:
Is the camera problem again due to closed sources?

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] cloudx720:
Camera works flawless with the normal cm/omni kernel, its the ng kernels based on update13 that breaks camera functionality.
[Galaxy S III Android Development] VictorLapin:
No issues with NG Omni kernel here. I wouldn't blame sources... Maybe it's something hardware related.
[Galaxy S III Android Development] kanjac:
+1 everything is OK :thumbup:

always last CM NIGHTLY + last Boeflla kernel
[Galaxy S III Android Development] adripred:
I think the problem is in the camera app used. I noticed that some treatment for the delay in recording the files on the external SD is necessary so that it does not freeze completely.

When configured apps camera to record the internal SD had no problem in any of them.

When I set up the camera for recording apps on the external SD just snap camera showed no errors. I noticed that Snap camera has a certain "delay" to start the video recordings (which gives the impression of it being slower).

I may be wrong, but that's the impression I got.

Regards!
[Galaxy S III Android Development] abhibnl:
Anybody noticed signal indicators not working with latest NG kernel? I'm sure it was working on normal version. But i'm not sure if it's kernel related at all.

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] adripred:
I also realized this, but only for the 3G signal indicators are not showing up. The WiFi signal indicators are showing here.

Regards!
[Galaxy S III Android Development] AssassinGEO:
Seems like most of you,S3 users here,haven't seen that fixed camera libs thread in apps and themes section. Go ahead and find it,download v5 or v4 (most stable,except taking snapshots while recording),and "restart camera by temasek" and enjoy your camera. Just one app and you will fix your "cannot connect to camera". You just got to research some.
[Galaxy S III Android Development] marenp:
I see all network indicators, on NG kernel and before it, no problem at all...

---------- Post added at 04:30 PM ---------- Previous post was at 04:29 PM ----------

Same here :) no problem at all.

---------- Post added at 04:31 PM ---------- Previous post was at 04:30 PM ----------

+1 :D
[Galaxy S III Android Development] adripred:
I had the best overall result with Snap camera than with these V4, V5 versions ...

Actually I only rarely use the Restart camera app.

Regards!

---------- Post added at 12:32 PM ---------- Previous post was at 12:29 PM ----------

Using the CM or Omnirom? I´m using CM.

Regards!
[Galaxy S III Android Development] abhibnl:
Same here! Wifi indicators are fine.

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] boalala:
Q about touch wake delay setting.

Hi.

I'm using omni rom + boeffla kernel NG 2.4.

When I set the touch wake delay in the boeffla kernel configuration app, it works OK.

But after I reboot the phone, the touch wake delay setting from settings page(under advanced section) of an omni rom overwrites it.

So the previous settings from boeflla configuration app doesn't apply anymore.

(I set it to 0 at the boeffla configuration app, but it is not allowed to set it to 0 in the settings of the omni rom. So I want to keep the setting of a boeffla configuration app.)

Is there any help available?

I looked it up many times but i didn't get the answer. :<

I would apologize if this issue has been repeated here.

I appreciate very much all your works.:)
[Galaxy S III Android Development] flither:
[MENTION=931437]boalala[/MENTION] - in my case any change to touch wake slider in Boeffla changes the setting in the rom and vice versa, nothing overwrites nothing. I would try Boot Up Delay in Boeffla Configs settings so the kernel should overwrite this setting AFTER rom, but I could be wrong though :)