yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
CIFS...

Hi guys,

good news for all here missing the CIFS module.

I was able to make it working again (credits to mkasick).

I am currently testing the stuff, but will release beta11 still today if all goes well :D

Andi
[Galaxy S III Android Development] k6?:
Is there a new cleaner script for changing kernel from 4.3 version or will the old one work,?

Thanks.
[Galaxy S III Android Development] PIRATA!:
Look on Boeffla main site. There's a CWM file to flash. I flash it every time before installing new kernel.
[Galaxy S III Android Development] andip71:
Depends what you think you need it for.

If you move from Boeffla-Kernel to another kernel: No cleaning required. Boeffla stores the settings at a location nobody else uses.

If you move from another kernel to Boeffla: Hard to say, if the kernel developer of the previous kernel provides a script - use it.

Between Boeffla kernel upgrades: No cleaning required. I always make it in a way it is compatible.

Andi
[Galaxy S III Android Development] k6?:
Can't find it :confused:
[Galaxy S III Android Development] andip71:
Look in your folder /boeffla-kernel-data on your internal sd memory, it is there.

But is more an emergency reset script than a cleaning script (as it removes the boeffla kernel configuration completely).

You can find it also here for download (called boeffla-config-reset-v2.zip):

http://boeffla.df-kunde.de/sgs3/other

Andi
[Galaxy S III Android Development] drelite08:
I know this may have already been covered somewhere so I'm sorry if Its a question repeated but what is a safe mA charge rate to set the config to when charging via USB charging (when connected to a computer) I would like it to charge faster than 475mA but really unsure what a safe amount is to set it to. Thanks in advance.
[Galaxy S III Android Development] shoalinagent:
Hey andi,

Just want to let you know ive been using variants of your kernel since 4.1.2 and im still in amazement of the features and optimisation of your work. Nothing to report, just that I appreciate your efforts and patience with the community and it always seems to me you are quite underrated.

Very satisfied user.

Many thanks:thumbup:

NeatRom 6.2 - 4.3 - Boeffla b9
[Galaxy S III Android Development] andip71:
So far I never heard of any issue when it was set to higher currents.

As long as you do

NOT

enable the "ignore unstable power" option in Boeffla-Config, you should be safe as the S3 charging logic within milliseconds adjust the charging rate down to a reasonable level if the USB port cannot supply what you configured (you can see the real charging rate then in the overview tab of the config app).

Go for 700 or 900 (this is what I use mostly), should be ok.

Andi
[Galaxy S III Android Development] drelite08:
Fantastic thank you so much for the advice.
[Galaxy S III Android Development] andip71:
5.1-beta11

Hi all,

next day, next beta for you :)

Version 5.1-beta11

Change log

CIFS module is working again - only note: Make sure you mount your device to a path outside of /storage, for instance /mnt/cifs is a good path (credits tomkasick)

Removed almost all busybox symlinks for improved custom rom compatibility

Enjoy

Andi
[Galaxy S III Android Development] PIRATA!:
I'm so sorry...but can you reti me in two words why cifs are used and because not everyone uses them? :P
[Galaxy S III Android Development] klisio:
Information from: http://www.boeffla-kernel.de/
[Galaxy S III Android Development] MysteryIII:
Normal USB gives you 500mA maximum by specification. But there are many USB Ports aside from specification so it is hard to tell. Nowadays you even have USB Ports with special power support to load your devices even if you PC/Laptop isn't on. This ports can have even 1A (1000mA) and a bit more.
[Galaxy S III Android Development] Moster2:
Whats normal usb for you? Dont tell me 2.0. USB 3.0 is supposed to have 900mAh
[Galaxy S III Android Development] MysteryIII:
Yes, it is. I don't have USB 3.0, the phone doesn't have USB 3.0 so it isn't required. By the way if you have a PCIe Device (if you just expand your PC) it cannot support this 900mA.

But that aside you are right and as I already told... the specification is not the maximum overall. ;)

And sorry for spamming in this thread, Andi.
[Galaxy S III Android Development] mad_ady:
First world problem for me: the upcoming cifs support won't give me the motivation to mount my shares via NFS, like the UNIX god intended...
[Galaxy S III Android Development] andip71:
Hehe :)
[Galaxy S III Android Development] MIKEMON:
Tried a lot, for three days leave, but one recommendation!

5 custom rom I've tried, no, beats the stock rom from Sammy

He came back, I stock official fw. I am very happy with Boeffla kernel and sound.

Just my opinion
[Galaxy S III Android Development] mad_ady:
Quick technical question: why is it that we can't mount cifs shares under /storage? What is the limiting factor? Just curious...
[Galaxy S III Android Development] boyheadkick:
i was gonna try UMS mode, and then i remembered i have 64 gigs of internal and dont have an external card :D

sorry for gloating, couldnt resist lulz
[Galaxy S III Android Development] ddaflorez:
how do i save my settings with bconfig v2 ? always i restart they become to default :mad:

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] andip71:
It is a limitation of the workaround to enable CIFS again on firmwares > 4.2.

If you need to understand it more in detail:

Zygote: Restrict slave mountspace so Dalvik apps can mount system-wide volumes

Android 4.2 implements multi-user storage using per-process mount namespaces. Originally, everything under "/" (the entire filesystem hierarchy) is marked as a recursive-slave mountspace for all zygote instances. This is done so that user-storage sandbox mounts under /storage/emulated are hidden from other apps and users.

Unfortunately this means that any Dalvik app (actually, any program whose clone/fork ancestry includes a Dalvik zygote, which is everything except services spawned directly from init) cannot mount system-wide volumes. Thus, apps like CifsManager are effectively broken in Android 4.2, since its cifs mounts are only visible to the CifsManager app itself. All other apps see empty mountpoints instead of the mounted volume. Furthermore, Linux provides no provision for a process to "escape" a recursive-slave mountspace in versions prior to Linux 3.8 (setns syscall).

Here, we restrict the slave mountspace to /storage (and, due to a possible kernel bug, /mnt/shell/emulated) so that Dalvik apps can mount system-wide volumes elsewhere (with appropriate permission, as in earlier versions of Android), while retaining full multi-user storage compatibility.

This change requires that a tmpfs volume is mounted as /storage in init.rc. If this volume is unavailable, then Zygote falls back to the previous behavior of marking the entire filesystem hierarchy as slave. It also implicitly requires that EMULATED_STORAGE_TARGET is path-prefixed by (part of the subhierarchy of) ANDROID_STORAGE, which is the typical case.

Which settings? All settings or just governors and/or schedulers do not stick?

Cannot be. Please send be all log files of your boeffla-kernel-data folder to my support e-mail: support@boeffla-kernel.de

Thanks

Andi
[Galaxy S III Android Development] MrDSM:
Hi everyone and specially Andi,

I've made a full charge and till everything is OK! :D

I've turn on Wifi and now with 2 hours, i didn't lost any %...

Thanks a lot for your work in this Kernel.

I am using the Beta 9.

;)
[Galaxy S III Android Development] NexxP963:
The same for me. After trying some custom roms I always came back to stock rom. A good configured stock rom + Boeffla Kernel is really great! - > this is not a contempt or a offense to the custom rom devs, it's my opinion

S3-Stock / Phillz Recovery / Boeffla Donation
[Galaxy S III Android Development] ddaflorez:
Which settings? All settings or just governors and/or schedulers do not stick?

Cannot be. Please send be all log files of your boeffla-kernel-data folder to my support e-mail: support@boeffla-kernel.de

Thanks

Andi[/QUOTE]

where to find those logs ?

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] Moster2:
/sdcard/boeffla-kernel-data
[Galaxy S III Android Development] jinosong:
AndiP,

Did you ever include the Bluetooth tethering update by the CM team that was released in late October?

I ask because it actually helped in improving Bluetooth sound when Googy included it his kernel.
[Galaxy S III Android Development] pricey2009:
It wont work on stock rom will it...?
[Galaxy S III Android Development] jinosong:
Geez, I'm sorry. I thought I was in the other thread. :D
[Galaxy S III Android Development] lelex45:
Wow really nice kernel. Thank you Andi :good: Battery life is very good! 6 Hours of screen on time are really impressive.
[Galaxy S III Android Development] ddaflorez:
sent as "boeffla config v2 kernel logs"

Enviado desde mi GT-I9300 mediante Tapatalk

---------- Post added at 03:15 AM ---------- Previous post was at 03:07 AM ----------

May anyone share his/her configuration for this kernel ? first time using but feel some lagg on the task manager :sad:

mine:

cpu: lulzactiveq gov. 200-1600 mhz and -50mv on all freqs.

gpu steps: 266-400-533-640-700

gpu voltages: 975-1000-1050-1075-1100

internal and external sd io: row

zram: disabled.

tweaks: boeffla tweaks actived.

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] boyheadkick:
you're making the same mistakes i did when i first started using this kernel..and that is oversetting the tweaks

my config:

governor zzmoove battery yank

scheduler zen

readahead 1024

stock cpu frequencies, no undervolt

gpu all stock, no under/overvolt

no system tweaks

no zram

and here's my LMK values:

foreground apps - 8mb

visible apps - 16mb

secondary servers - 24mb

hidden apps - 32mb

content providers - 128mb

empty apps - 164mb
[Galaxy S III Android Development] ddaflorez:
no oc/uv ? what about performance ? will try yours and see...

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] boyheadkick:
no OC/UV/OV..as advised by [MENTION=947981]Lord Boeffla[/MENTION] himself a few pages back
[Galaxy S III Android Development] mad_ady:
Thanks for the detailed explanation, Andi. I'm not sure I understand it all, since the whole mechanism differs from what I was used to under standard gnu/linux. Also, from your explanation I take it that no other mounts (nfs, luks encrypted volumes, sshfs, etc) can be made under /system, right (for the same reasons), right?

I'll try to get away with it by making a symlink from /storage/sdcard0/whatever to /mnt/mountpoint.

One thing I don't fully understand is why a root process (the mount command) still has ties with the zygote process that spawned it...

Edit: nevermind my confusion. It's normal that a root shell has as parent id the zygote process that spawned it.

But a question remains: if I mount a cifs share from adb would I go around this limitation?
[Galaxy S III Android Development] blue_moon:
Which rom do u have and what is your boeffla settings?
[Galaxy S III Android Development] Edge330:
Since beta9 I'm not happy with battery, losing to much battery in stand by.
[Galaxy S III Android Development] danierakes:
Let me guess u r running stock deodex rom or custom rom right? Try with stock rom/odex rom ..u will satisfied. ...
[Galaxy S III Android Development] JustArchi:
How the hell deodex can cause more battery drain? Dude, do you have a slightest idea what you're saying?
[Galaxy S III Android Development] maazy:
Well, every time I flash a new beta, battery goes fast on first cycle. At least, it's what happens on my setup. Give some time so the kernel can kick in.
[Galaxy S III Android Development] andip71:
No, have not included as this is the Samsung kernel. Would not mess this up by implementing other drivers (objective = close to stock).

Easy answer, also stated in OP: You do undervolting = no support.

Disable undervolting and see in another charge cycle.

Never tried to mount via an adb session. But you could try and let us know :)

Exactly, that is very normal. Battery life can only be judged after a full new battery cycle.

And again: Do not overrate the influence of kernel on battery life. No kernel ever will double your battery life, neither would it make a drain if something is not completely wrong.

Andi
[Galaxy S III Android Development] renierx:
Hi, I am playing with GPU overclocking for 2 weeks (with latest beta kernel + MK6 and ML2 ROMs) and suspect that only first 4 frequency steps are used. I use Taiji benchmark scores to determine maximal GPU frequency used and here are my GPU freq. settings and Taiji scores:

700/700/700/700/700 : 48+ fps

533/533/533/533/533 : 43+ fps

350/350/350/350/350 : 31+ fps

160/266/350/533/700 : 43+ fps

160/350/533/700/700 : 48+ fps

160/160/266/350/533 : 31+ fps

350/350/350/350/700 : 31+ fps

etc.

I have also tested many other combinations but always with score corresponding to 4th GPU step. I believe that I always use stable overvolting for OC frequencies and that it is not the cause of lower than expected scores. Could anybody check and confirm it? Is there any suitable tool to monitor GPU frequencies? Many thanks!
[Galaxy S III Android Development] MysteryIII:
Do you use Multitasking? I often switch between apps, so I need good multitasking values. With this settings I would expect that apps in background are closed very fast so no multitasking. Am I wrong?

It's a little difficult for me to find the right values for that purpose without getting lags, so I just want to get some experience here.

(I only know unused memory is wasted memory)

Thanks!
[Galaxy S III Android Development] boyheadkick:
To put it simply, i could not use multiwindow before without the available ram dipping down to 50mb amd my device starting to freeze..now i can use multiwindow and still have 100mb of free ram..with those values the content providers like fb clients and sync are closed aggressively, considering they aren't needed to run all the time..same goes with empty apps

Thats just me though and how i understand LMK..im not guaranteeing this will give you the desired multitasking experience like, say a 2gb ram device..

Tapatalked from my OmegaDroid i9300
[Galaxy S III Android Development] MysteryIII:
Thanks for the info. I will test the settings for a while ;)

€: For me this settings seem to be to aggressive. Every time I reboot my phone it freezes after inserting the pin number. After pulling out the battery and then restart it works, but another reboot and the same thing happens.
[Galaxy S III Android Development] duffymm:
Anyone can suggest some infos about the best Way to debloat a stock Samsung rom?

I Mean which apk delete without risk and which apk prevent to load on startup and how.

Thanks a lot for support.

Beta11 works great, Just finished setting the audio engine, great work.
[Galaxy S III Android Development] malachow:
A little bit of OT, but look here: https://docs.google.com/spreadsheet/ccc?key=0AqTvctlW89DtdC1qVUlLeVFTV3ZOdUtDclpBdVRQOUE&pli=1#gid=0
[Galaxy S III Android Development] duffymm:
Thanks a lot
[Galaxy S III Android Development] maazy:
Wow, thanks you very much. Was looking for something like that!
[Galaxy S III Android Development] dyval:
Beta11 works perfectly as always. Thank Lord Boeffla.:good:
[Galaxy S III Android Development] gieffe22:
yes i confirm this...when gpu freq were introduced i tested with antutu all the freq...

step 5 is useless(probably was the samsung trick to boost benchmark score)...step 4 is the most important and rappresent the 3d freq (game 90% of time)...if you read my old post you can find my impressions about this (but was the beta 5 i think and at times the scores were higher than actual...i dont know why)...
[Galaxy S III Android Development] renierx:
gieffe22: Thanks for confirming!

Lord Boeffla: if you can confirm that GPU 5th step (Frequency 4 in the config utility) isn't used, what about removing it as useless?

Odesláno z mého GT-I9300
[Galaxy S III Android Development] andip71:
Well, if this can be proven by someone (without a tool showing GPU frequencies like it was available long time ago on ICS), I would rather tend to look why the 5th step is not taken into account.

But as always... GPU stuff does not have my highest priority. You can still configure all steps you want by using only the 4 steps, so this should be a fair workaround.

Cheers

Andi
[Galaxy S III Android Development] janres155:
Debloat

For those who are asking for the safe applications to remove in the system, I provided my own list for ROMCleaner.

You should first check it and put "#" to the apps you don't want to remove.

Also you should put "#" to the line for the odex of the corresponding app.

PS I also added an odex line even though the app doesn't have a .odex.
[Galaxy S III Android Development] danierakes:
Its not about the deodex rom (clean rom) thing im talking about..its about the tweak that included in the deodex rom/custom rom coz sometimes it will gave error/clash when we flash another custom kernel......
[Galaxy S III Android Development] JustArchi:
What?! :eek:

Deodex has nothing common with flashing custom kernel. It can't cause problems if done properly.
[Galaxy S III Android Development] MIKEMON:
Yes, it is true, but for me it is ODEX system preferences.

everyone must know what is expected, I add the stock, just what I want and what I need.

---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------

Boeffla kernel on stock rom, runs absolutely without error

stable and smooth work
[Galaxy S III Android Development] JustArchi:
Well, sure, it's up to you what and how you flash, however please hold these "deodex battery drain" theories because they have nothing common with reality. Deodex doesn't cause any issues if done properly. Check yourself -> http://xdaforums.com/showthread.php?t=2585670
[Galaxy S III Android Development] MIKEMON:
had, I deodex rom several times, but every time I had a problem.

Lately, I have stock ODEX, Boeffla kernel and I have no problem

system is fast, smooth and stable
[Galaxy S III Android Development] Edge330:
What is best settings for idle mode in boeffla app to improve battery?
[Galaxy S III Android Development] andip71:
Atfr+lpa in theory.

Andi

Gesendet von meinem GT-N8000 mit Tapatalk 4
[Galaxy S III Android Development] adnan7khan:
Thanks .I'm on it :)

Bro. how to Disable ZRaM Compression??

+

(Couple of Days back.. I played with GPU Frequency Values..Selected Last 1 & My Phone Turned into Tetris Game... hahaha)

If you Feel, My Post Helped You, Just Hit & Kill the Thanks Option :p

Twitter : Adnan7khan ;)
[Galaxy S III Android Development] andip71:
You cannot disable compression of zram. It would render zram useless.

Andi

Gesendet von meinem GT-N8000 mit Tapatalk 4
[Galaxy S III Android Development] JustArchi:
You had poorly deodexed roms then :).
[Galaxy S III Android Development] connta:
hello andi

i am so glad that you introduced back gpu manipulation module but i seem to have found something wrong with it, this is the situation:

back on 4.1.2 i used syah kernel and had my gpu uv tested to be 850 875 950 1000 1025 for the default freq profile 160-533Mhz. back on 4.1.2 i had a mali stat app which would draw freq and voltage in overlay and i could monitor if the voltage/freq really ramps up to what i set and it did. i used nenamark to determine lowest possible voltage since nenamark gave me a clear artifact/slowdown situation on exact same time in the demo, i took this as a good indicator and it was, never had any problems with my voltage setup.

then came the 4.3, new drivers etc and when you released the gpu module everything seemed to work just fine with my old settings but i noticed one thing, the phone was noticeably hotter and started throttling in gpu intensive tasks. since now its winter and its kinda cold this should not happen as i didnt had any problems on 4.1.2 even in summer time on 35C+... this made me wonder and start testing.

sadly the mali status app does not work on 4.3 and i cant monitor real time parameters so i set every frequency uv to setting i know will not hold from 4.1.2 and the results were interesting. every freq step failed after being uv too much except the last setting. the last setting seemed to apply the correct frequency since i checked some benchmark results and they were as expected but it did not seem to apply the voltage correctly. i found this out by setting very high clock with insanely low voltage that would work when hell freezes over and yet the gpu functioned normally, gave appropriate score for 640Mhz clock while supposedly being set to 900mV, no nenamark slowdown or artifacts, which is impossible since when 4th step is set to 440Mhz/900mV will fail completely bug out the gpu. also from 4.1.2 i know that minimum voltage for 640Mhz was 1075mV, i can understand that different kernel/rom/whatever could give +-25mV different results or something to that extent but this behavior is not normal.

this leads me to believe that gpu is applying max voltage for the 5th step no matter what is set in boeffla config and i think this could be a pressing issue since voltages are involved, hope you have time to investigate.
[Galaxy S III Android Development] ARCANAAA:
Hi does any1 know which country i have to select on sammobile? Because im from belgium and when i select this country i get a very outdated firmware..

Another question.. are thw firmwares from sammobile odex or deodexed already?

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Android Development] MRDOCA:
Hey everyone. Can someone please post there snappy lagg free battery friendly settings. Pleasea also post how much battery time and screen time you get with your settings. I set my wifes up and shes complaining it lags and freezes on facebook lol. She is has omega 53 installed. Ive got it setup similar to my s4s kt kernel settings but with zzmove and yank battery. Row. Read ahead 2048. Uvd 50. Rest is left alone. Battery life seems good. Just laggy and freezy in fb

Tapped on my Omega driven I9505
[Galaxy S III Android Development] renierx:
Hi, look at my yesterday's post: http://xdaforums.com/showthread.php?p=49110132#post49110132

I believe that the 5th (last) GPU step isn't applied at all. It could explaing why it doesn't crash with your "insane" freq/voltage settings.
[Galaxy S III Android Development] connta:
it seems it is, as far as clock is concerned. i get appropriately increasing scores going from 440-533-640 and they are consistent.

i used antutu 3d rating application and it is giving me around 100 points more with each step respectively, i could be wrong, didnt double check which i will do now.
[Galaxy S III Android Development] renierx:
I just run the NenaMark2 several times and it leads me to these conclusions:

- it isn't able to reach higher score than approx. 60.1 fps

- the 5th GPU step isn't used at all, all scores are in accordance with 4th step

160/160/160/160/160 : 40.8 fps

266/266/266/266/266 : 56.0 fps

350/350/350/350/350 : 59.9 fps

533/533/533/533/533 : 60.1 fps

640/640/640/640/640 : 60.1 fps

700/700/700/700/700 : 60.1 fps

160/160/160/160/640 : 40.1 fps

160/160/160/266/266 : 55.9 fps

160/160/160/266/640 : 56.2 fps

160/160/160/350/640 : 58.6 fps

160/160/160/640/640 : 59.6 fps
[Galaxy S III Android Development] gazza1988:
Hi guys I'm after v5.1 stable. It's not coming up on my phone as a link on the website. I can find the beta versions and stable 4.x etc but not stable 5.1
[Galaxy S III Android Development] Robi959:
For heating you have right. On 4.1.2 i did not have problems with heat.
[Galaxy S III Android Development] boyheadkick:
Battery stats from my last charge..not too much activity, just some social media

Tapatalked from my OmegaDroid i9300
[Galaxy S III Android Development] janres155:
Hi Lord Boeffla

I think that pegasusq has been greatly improved by Samsung, because I never had good battery life before with pegasusq stock values even with Greenify Pro.

Now, I already had 4 1/2 hours of screen-on time by watching movies and with 46% battery still remaining.

Janres