yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
Let me answer in the following way:

USB Tethering is a function provided by the rom. It relies on USB drivers in the kernel.

As I have never touched the USB drivers, I suspect it is broken for you in the rom.

I cannot confirm 100% as I never use it, but I know from some users it worked for them in the past (at least on Samsung kernels).

Andi
[Galaxy S III Android Development] _Negan_:
I agree with you but it's easy to understand also Andy's think...at the moment with custom roms we re near to fully working bug free kit kat versions but not yet done...anyway I have a custom too with boeffla omni obviously and I will never change my ROM with original...I can't give up smoothness and some features that custom like fusion ROM or beanstalk has...:)
[Galaxy S III Android Development] aliw32619:
Is UV good for my phone's life ?
[Galaxy S III Android Development] josipborac:
It can make battery last longer but lord doesn't recommend it.
[Galaxy S III Android Development] aliw32619:
That's why i'm not gonna use it because my phone was behaving strange lately and it froze 2 times, had to battery pull
[Galaxy S III Android Development] josipborac:
Yes. Those are side effects of UV too much.
[Galaxy S III Android Development] metalgearhathaway:
Looks like we inadvertently started a little debate! LoL, it is interesting to hear what features push people towards different flavours available.

I totally understand, as a sum of all parts it becomes a bit of a deal breaker, if all of those plus whatever you have not mentioned were real concerns to me I would revert to sammy stock too.

However, I either live without the need of some of those, have found work arounds or simply live with an issue, although for me there are no actual issues.

Just for kicks, in contrast I find:

- camera not as strong as Samsung Stock (with all its features)

I totally agree! I workaround this issue by using Fixed Cam for CM 10.2_CM11 V2.3.zip found here: http://xdaforums.com/galaxy-s3/themes-apps/30-nov-fixed-camera-app-cm10-2-cm10-2-t2505973

- WIFI direct not working flawlessly

I thankfully have no need, but if I did that would be an annoyance.

- comfort functions like slide-to-screenshot etc missing

I find that the comfort features of lockscreen notifications, quick panel and definable interface outweigh the vanilla features. Definatly a individual and personal taste choice!

- battery is always a bit better for me on stock than on CM/Omnirom

Yes, the all important battery life. This is definately personal, I find I get 4.5hours screen time and an easy 10 hours bluetooth ad2p streaming before my battery dips below 5%, even with my maxed out settings. If I had to have more than that then I would a) return to stock clocks and if unsucessful I could maybe sadly return to stock rom :eek:

- fm radio native support

Yes! If you make good use out of it, then its a real deal breaker. SpiritFM jsut will never be mature enough it seems to be a perfect alternative. Thankfully I have cheap unlimited data (£12pm) and I steam everything over my Deezer subscription service, so I negate the need for the radio thankfully.

- I never had the case stock firmware just refused to work out of the blue

Being fairly new to the S3 ( 8 weeks now), I tried all S3 roms, the support for them is nowhere near as strong as it is for the S2 (i9100), I was quite surprised!

Trying the roms, I found many had flaws or omissions that made it impossible to settle on one, i cycled through them all in my search. Typically, it was one of the last few I tried that came out a winner, crDroid, he calls it "simple", in essence it is CM with all the interface features you would expect. [MENTION=4478519]Cristiano Matos[/MENTION] does a wonderful job of only merging reliable enhancements meaning that his rom feel clean with no rough edges. I've been using since build 12, now on 17, roughly released every week. Total quality, mixed with your kernel with just the right settings in intelliactive and you are steaming away with a highly polished device in your palm!
[Galaxy S III Android Development] aliw32619:
So should i use -25 then?
[Galaxy S III Android Development] josipborac:
Well. You just to have try it by yourself. -25 should work.
[Galaxy S III Android Development] pricey2009:
Do not use any undervolt as it is not going to be of any benefit.
[Galaxy S III Android Development] aliw32619:
I found that Archi's default ultra power save profile was using -25 UV
[Galaxy S III Android Development] metalgearhathaway:
Yeah, I've done some extensive testing on that over the past week, if there is any improvement it is at a scale that is almost impossible to ratioanlise, don't waste your time. The main thing is being able to deliver more power if required, to ensure stability. Undervolting generally will let to either less than a percents battery improvement or crashes.
[Galaxy S III Android Development] aliw32619:
Ok i disabled it lol
[Galaxy S III Android Development] kadopt:
Not true, read this.

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

[edit] Also if what you said was true then overvoltage would have no issues and that is also not true as it increases power consumption and heat production and that can eventually damage the ic.

With UV you're making the device do the same work with less energy.[/edit]

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] Kord:
Thanks for explaining :)

I'm just asking because on previous CM Versions (10.1/2) USB Tethering used to works flawlessly. For me it's not so necessary, but it's good to have this feature working in some cases :)

Regards :good:

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] andip71:
All is somehow true and somehow not.

Fact is: UV makes a phone more instable. This many times reverses the advantages of saved power by having the system in a state where it behaves shaky, which even needs more battery.

Heat can damage the device: Only true in theory. In the S3, there is a function called thermal throttling included. So it will reduce frequency down or does a complete forced crash in case the CPU gets too hot.

So, in theory what you say is right.

In real life with the S3, it does not apply as per theory.

Andi
[Galaxy S III Android Development] kadopt:
Regarding UV, well I don't recommend tweaking the device if the user does not have enough knowledge of what he is doing like with overclocking. I have a UV of 100mV in a asv3 device and have no issues.

As for the heat, I was going more for the overvoltage but a ic running hotter will last less than a ic running cooler. Fortunately most cpus and gpu have thermal throttling. Also even for the overvoltage probably the maximum value is within cpu VID so there shouldn't be problems as well.

My experience comes mostly from computer modding (x86-64) and oc, etc, and that train of thought may not apply to our device as you said.

Although unrelated my Intel core i7 920 runs at stock speed with only 0.97v instead of the base 1.20v specified my intel.

[edit] Also why is there different voltage steps for the various clock rates of the cpu, since they can all have the same value for the maximum clock rate? Because it would be a waste of energy otherwise. [/edit]

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] RSDamasceno:
[MENTION=971570]mad_ady[/MENTION], [MENTION=947981]Lord Boeffla[/MENTION] & others.

I know its possible to view network shares (windows) and access them on android with apps like solid explorer and es explorer, but is there any way to mount a network share into CM11 do that other apps can access the data natively (like poweramp for example)?

I tried both CIFS manager as well as the other mount manager app and neither of them seem to work. Any suggestions?
[Galaxy S III Android Development] RSDamasceno:
Some news about that, man?
[Galaxy S III Android Development] yusuf_adsas:
Love it

I have an sgs3 and use Boeffla's cm11 kernel 2.2 beta6.

So many things I can do with, and being a music lover I use the sound tweaks in Boeffla's config app. Transforms my sgs3 beautifully to producing much better sound.

One of the main reasons i'm keeping my sgs3 is because of this. It's a shame Andie from Boeffla only made kernels for the sgs3 and note 10.1..wish i could use it in other devices like my note2.

Thank you Andie for your hard work, we are forever grateful.

Any chance you will be making for other devices? Which one(s)?

Yusuf
[Galaxy S III Android Development] mad_ady:
Well, I use NFS constantly with Boeffla Kernel. I don't use cifs because of the performance difference, but it works the same way.

The problem is that since android 4.2 you can't use mount manager directly (and it hasn't been updated). Android 4.2 added a restriction that if an app/process mounts something, only that process can access it. The solution has two parts:

1. Don't mount under /sdcard

2. Use the --mount-master switch in SuperSU 1.93 or later to do the mount so that the processes can all see the share.

With this in place your programs will be able to access your remote files natively, with the exception of apps that don't let you navigate outside /sdcard.

You can find the tasker app I made to handle NFS here: http://xdaforums.com/showthread.php?t=2655242
[Galaxy S III Android Development] RSDamasceno:
Oh, thanks man...

But did not understand what you mean by that:

(sorry for Google translate)
[Galaxy S III Android Development] boyheadkick:
[MENTION=947981]Lord Boeffla[/MENTION] i remember back when i was running aosp roms on my old acro s, i used to use a certain governor called wheatley..are you familiar with it and could it be possibly added to the governors in your kernel?

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] mad_ady:
It means that instead of doing:

su -c "/sbin/busybox mount -o nolock,ro,hard,intr,vers=3 -t nfs 192.168.1.5:/DataVolume/Download /mnt/nfs/Download"

you need to be doing

su --mount-master -c "/sbin/busybox mount -o nolock,ro,hard,intr,vers=3 -t nfs 192.168.1.5:/DataVolume/Download /mnt/nfs/Download"

If you have tasker, try out the link I sent you. It handles these commands in the background.
[Galaxy S III Android Development] andip71:
Hi Yusuf, I have a golden rule: I only provide software (in this case kernels) for devices I personally own. This is to be able to test myself, try things out and ensure quality.

So far I have: 3x Galaxy i9300, 1x n8000, 1x n8010. Hence, for these devices, kernels are available in different flavours.

I might go for a S5 still later this year.

But apart from that, no other kernels to be expected. Sorry.

This is working fine, also with CIFS Manager.

You need to load the CIFS module in Boeffla-Config V2.

Then mount the drive in CIFS Manager, but outside of /sdcard path. This is really important as mad_ady already wrote.

Try to mount it to e.g. /mnt/mycifs folder (which you need to create first). I do it this way and it works fine.

Never heard about it, honestly. If you can give me a reference I would be able to look at it.

However, if this is a very old governor which was developed for single core CPUs it might not be worth looking at it.

Todays governors need to support hot plugging of CPU cores (although I implemented SmartAssV2 as well, which does not do that) ideally.

Andi
[Galaxy S III Android Development] artyfarty:
http://rootzwiki.com/topic/14685-kernel27-mar-glados-v23-for-jb-422/page-10?p=405813#entry405813

wheatley governor
[Galaxy S III Android Development] Nic2215:
definitely no problem with that, the v2 app preset also got uv..
[Galaxy S III Android Development] HellStorm666:
Installed the cm11 nightly of today.

Kernel beta6 works, kernel rc3 doesn't (android stopped.)

What is the latest, adviced kernel to use with nightly 20140409?
[Galaxy S III Android Development] andip71:
Latest 2.2. stable.

Install the correct version (Omnirom vs. CM11 Boeffla Kernel) depending on your rom.

Andi
[Galaxy S III Android Development] mad_ady:
[MENTION=947981]Lord Boeffla[/MENTION]: I manged to get a clone of your git repo for the s3 omnirom kernel, and I also got the NDK toolchain from here: https://developer.android.com/tools/sdk/ndk/index.html (I got the linux 32bit version android-ndk-r9d-linux-x86.tar.bz2).

However, I noticed that your kernel was last compiled with gcc 4.7, which is not part of this toolchain (it has arm-linux-androideabi-4.6 and arm-linux-androideabi-4.8). I also noticed you tried to compile it with 4.8, but then reverted back to 4.7.

Could you tell me, please:

1. What toolchain are you using and where you got it from? Also, if you are on a 64bit system, would there be any problems if I'm using a 32bit toolchain to cross-compile (the target code shouldn't matter on the host architecture)?

2. For my first magic trick I will attempt to compile usbserial.ko, pl2303.ko and ftdi_sio.ko, but if I want to compile my complete kernel (and have the modules built in for instance), what steps would I need to do to go from kernel source to flashable zip? I assume:

make menuconfig
make
make modules
make bzImage
//possibly some other makes that involve the initramfs, etc

Could you point me in the relevant direction?

3. In the near future (in a couple of weeks maybe), I'd like to try out some fixes for the dock issue. You mentioned it would be worth a try to disable some features or try some things (I'll need to check back what they were). Also, can you show me in which direction I need to start digging?

Cheers!
[Galaxy S III Android Development] Moster2:
Regarding the toolchain, you can get it directly from google: https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/
[Galaxy S III Android Development] andip71:
Ok, I included wheatley into an internal test build for myself. Will give it a try for some time and then decide if I can release it in the new beta to the public or not.

BTW: It does not hot plug CPU cores. But maybe this is even not a showstopper in the end.

1) Toolchain is contained in the legacy toolchains NDK archive: android-ndk-r9-linux-x86-legacy-toolchains.tar.bz2

And I am also using 32 bit toolchains still, so no side effects to expect.

2) Build process

make arch=arm boeffla_defconfig

make -j4 ... (or if you have more CPU cores in your pc, increase number)

Modules are already built by that.

Then you need to unpack an existing stock kernel to get initramfs out, and repack it with your new zImage (bootimg). There is a tool called mkbootimg which supports that.

Also you need to copy the modules into the flashable cwm zip for the kernel.

I suggest you start reading there:

http://source.android.com/source/building-kernels.html

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

http://xdaforums.com/nexus-s/development/hack-compiled-mkbootimg-unpack-repack-t891333

3) Best is for you to start reverting my charge logic commit out (search for commits on samsung_battery). Maybe that makes a difference already. But could also be Linux Upstream that causes it. Then you would probably need to start all over from scratch with a non-upstreamed version you get from official repos.

It will anyway be a complex and cumbersome time. But you can make it !!! :good:

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

quick question: Do you know how often both CM and Omni teams update the their kernel?

I'm asking this just to better understand how it works, because I always see the ROM itself being updated all the time, but I'm not sure about the kernels.

thanks!
[Galaxy S III Android Development] mad_ady:
Thank you for the resources. I will go ahead and read, tinker and break things!

Funny thing - the PL2303 module was already in your kernel's default config. I'll need to give it a go when I get home...:

CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_PL2303=y
[Galaxy S III Android Development] JustArchi:
https://github.com/omnirom/android_kernel_samsung_smdk4412/commits

https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/commits
[Galaxy S III Android Development] DiReis:
ok, so, it looks like it is not updated that much..

I was asking this because I was curious about things getting updated on the "Stock" Kernel for CM/Omni and being left out from Boeffla.

good to know
[Galaxy S III Android Development] andip71:
As Archi already told you by giving the links... currently there are almost no kernel code changes anymore done by the kernel development teams of CM and Omni.

This was different 2-3 months ago, but meanwhile seems the kernels are almost final.

That would need, the functionality should be already available out of the box, no module loading etc. required.

Andi
[Galaxy S III Android Development] mad_ady:
Yes, I've just tried it, and the usb dongle works out of the box. I plugged in my pl2303, it was recognized in dmesg, a /dev/ttyUSB0 exists...

All I needed to do was to track down a compatible build of GNU screen and I was able to connect via serial cable to my media player which I'm currently debugging. This will speed up my personal projects, since I don't have to wait for the computer to become available anymore :D

Thanks a load!
[Galaxy S III Android Development] RSDamasceno:
http://xdaforums.com/showthread.php?p=51775245
[Galaxy S III Android Development] cloudx720:
Love this kernel so much, even running battery saving preset phone is fast lol. Latest cm11 nightly+boeffla total awesome sauce!
[Galaxy S III Android Development] boyheadkick:
Thanks...i always liked that governor because it's not too aggressive when scaling up, but is aggressive on racing back down to idle..hope you get positive results in testing

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] metalgearhathaway:
You can emulate the gentler scaling if you buy the donate version of Boeffla config v2 and play with the tunables on governors, bit of a fun project for you, I've played around with intelliactive to get the results I wanted, fairly easy to work with too!
[Galaxy S III Android Development] andip71:
So far wheatley governor is running stable. Performance for normal usage seems to be sufficient as well. Too early to comment on battery usage however. As the governor does not hotplug, all cores are switched on all the time (apart from deep sleep of course). We have to see what this means in fact.

But I think I can bring a beta1 with that governor included quite soon...

Want to share the tunable settings with us?

If others find them good as well, I could put it as a standard profile into the profiles list as well.

Andi
[Galaxy S III Android Development] metalgearhathaway:
Of course, although it is rather simplistic in the the end. All I do with intelliactive is reduce the hispeed_freq, which by default is 1400mhz, I chop that down to a more than reasonable 1000mhz. With that in place the device only jumps up to my 1600mhz overclock amount when its really needed, 1000mhz becomes the first port of call when some of medium activity is occuring.

I tested from 800mhz upward with a range of standard apps and activities I perform, I found that below 1000mhz led to issues with A2DP operation, so I nudged up in 50mhz values until I found a sweet spot, just happened to be 1000mhz. Works very well for me.

I did experiment with above_hispeed_delay and timer_slack values (reductions) but this leads to gui transition issues.

Maybe at the weekend I'll try playing around with zzmoove for a laugh, although I have to say intelliactive is just amazing!
[Galaxy S III Android Development] boyheadkick:
I haven't quite grasped the specifics on tuning governor values yet as im still reading up on that subject...thanks for the advice :thumbup:

As i remember it was my favorite governor on my old acro s (dual core snapdragon s3) because it gave me a good balance of performance during screen on with normal operation and some games, while always maintaining an almost flatline battery usage when in deep sleep..

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] metalgearhathaway:
Well, here is the place to learn, I'm certainly up for learning more on the subject, so post questions and we can all learn from each other :)
[Galaxy S III Android Development] aliw32619:
Lol thanks Andi and ZaneZam
[Galaxy S III Android Development] aliw32619:
http://xdaforums.com/showthread.php?t=2631573
[Galaxy S III Android Development] cheese458:
Andi, has your config changed recently since the addition of zzmooze moderate and battery plus? Or just any change in preference?
[Galaxy S III Android Development] andip71:
Just a bit. Now using zzmoove moderate instead of zzmoove battery yank.

And cfq as both schedulers.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] VictorLapin:
Sorry for being persistent, Andi, but what about a test kernel build for dock debugging?

Tapatalked from Nexus 7
[Galaxy S III Android Development] you_man:
And you did not want to add new profiles :D

Why abandoned zen?
[Galaxy S III Android Development] andip71:
Have not found any time for it these days. Not forgotten though...

Impossible for me currently, as I am running my private slim kernel atm. Profiles are not compatible.

I feel the phone a bit smoother with cfq when using zzmoove. But zen is still great.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] VictorLapin:
Okay, will be waiting for it

Tapatalked from Nexus 7
[Galaxy S III Android Development] SuperAce609:
Does anyone here have a Wi-Fi issue? Like it's still connected but there's no connection. Messages are literally on hold until there's a connection but still being connected to Wi-Fi. This started happening after i upgraded to Kryten's first Ultima based on 4.3. Then started happening again after i switched back to 4.1.

Do you guys think it has something to do with the modem or baseband? Ever since back then, these Wi-Fi issues won't go away no matter what ROM i flash.

I have the UGNA8 baseband. Forgot what modem. I think it was MG4? I asked Kryten and he told me the Wi-Fi driver is handled by kernel. Logical enough, boeffla is my default kernel everywhere i go.

Any thoughts master ultra lord boeffla? I really can't depend on Wi-Fi anymore. It's like having no connection. I have to get texted and told to check Whatsapp xD
[Galaxy S III Android Development] davidian666:
I have the same problem with latest slimkat weekly and boeffla omni 2.2. I didn't have this problem with the test kernels...
[Galaxy S III Android Development] andip71:
Nothing changed for wifi between test kernels and stable.

Have no wifi issues on my side.

Reset your configuration and check with changing it for a while.

Also check with kernel that comes with Omnirom. Might also be a glitch in the rom version etc.

And yes: modem and baseband has nothing to do with wifi. Wifi drivers are in the kernel only.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] _Negan_:
Andy when you will change phone which phone is in your intention? Because I hope to buy same phone as you, I have changed many roms but one thing never change and is your kernel! Thanks for all
[Galaxy S III Android Development] andip71:
Galaxy s5. But not very soon, in a few months. Currently planning 3 apartment moves in the next months. Hence no money and time...

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] _Negan_:
Perfect...will be my choice too.
[Galaxy S III Android Development] VictorLapin:
Mine too, as soon as it will be added to the list of Slimroms supported devices ?

Tapatalked from Nexus 7
[Galaxy S III Android Development] metalgearhathaway:
I purposely avoid phones for the first year to allow the custom roms to start maturing :)

Sent from my GT-I9300