yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] metalgearhathaway:
Andi,

I cannot thank you enough for catering for the minority who have this issue. I can confirm that video recorder initialise appears to be functional once more, if it develops an issue I will be sure to let you know!

As you know, I love you kernel and have spent a fair amount of time in a short period getting to know it as well as my tiny brain will allow and I have really enjoyed nailing my intelliactive profile to resolve my and hopefully others A2DP issues! This minority kernel release feel like a nice reward and I am thrilled to be back here with you guys :)

:good:
[Galaxy S III Android Development] metalgearhathaway:
2.3 beta2cf

24 video's recorded sucessfully

Oddly, best ever scores on Antutu & 3D Mark.

No adverse effects!

:good:
[Galaxy S III Android Development] habylab:
Working really well the test version Andi sent me. Same as above!

I haven't used this kernel in a couple of months, so this is nice to see. What are peoples opinion of Intelliactive versus others, such as pegasusq? Wheatley also? Wheatley seems cleaver and tuned towards deep sleep.

Sent from my CM11S Galaxy S3. Proud Googy Beta tester.
[Galaxy S III Android Development] metalgearhathaway:
My tuned intelliactive profile works really well (see link in my signature), deep sleep works perfectly and system is snappy through my tweaks.

I use intelliactive mainly because it was the only governor I could control well enough to achieve my personal goal of having my music stream over bluetooth (A2DP) perfectly without glitches. If you do not use A2DP, then to be fair to the other governors, there is not loads in it.

Basically, Pegasusq and intelliactive perform very similarly, although the later is slight more responsive UI wise I find.

zzmoove is the place to be if you are looking for battery savings for all accounts, but I often find zzmoove a bit buggy and seems to result in a slightly more unstable system. However, that instability may only apply to my chip and configuration, others may guide you better on that.

If you want a nice balance of everything and removal of stuttery music then I recommend my Intelliactive settings :) :D
[Galaxy S III Android Development] andip71:
Good morning!

Allright, after I got two confirmations already, cam issues are fixed by them going on the experimental "camera workaround" kernel, I do want to give it to more interested users for testing:

CM11:

http://boeffla.df-kunde.de/sgs3/boe...wnload/Test/camera_workaround_(experimental)/

Omnirom:

http://boeffla.df-kunde.de/sgs3/boe...wnload/Test/camera_workaround_(experimental)/

So if you are facing camera issues, I would be grateful if you could test the experimental kernel and let me know if it gets "workarounded" (I would not call it fixed, as for me this is more a workaround).

Thanks

Andi
[Galaxy S III Android Development] Yeti47:
Thanks, I only use still shots that occasionally freeze on me. Have tried the new kernel and will let you know if I face any issues. It's a random event as only seems to happen when we're out with the kids and a good photo opportunity comes up :( . Testing at home normally works...
[Galaxy S III Android Development] habylab:
That sucks, let's hope it is fixed. A quick, usable mobile camera is what is needed!

Sent from my CM11S Galaxy S3. Proud Googy Beta tester.
[Galaxy S III Android Development] Yeti47:
Sorry, seems to have no effect with this issue. Happens randomly as before.

Have reverted to previous kernel now.
[Galaxy S III Android Development] andip71:
Thanks for the feedback. That is what we need. I think then your specific issue was not linked to the glitch that was supposed to be fixed by the kernel changes.

Andi
[Galaxy S III Android Development] Derpoholic:
Hey! Noob here, running CM 11 snapshot (latest). Will this work for me? Also What's the difference between kernel and rom?
[Galaxy S III Android Development] kadopt:
Yes it will. Kernel is the rom's "core" and the rom is everything around it (kinda).

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] habylab:
Hey!

Give the cm11 version a go from the website! The latest beta on there is pretty stable.

In basic terms, the ROM is the files sitting on our phone and the kernel is the thing that runs and manages the phones resources that are being used. Make sense?

There's plenty more on what each is if you have a look around XDA and a Google too!

Sent from my CM11S Galaxy S3. Proud Googy Beta tester.
[Galaxy S III Android Development] andip71:
Hi mad_ady... thanks for the very interesting summary and investigation.

Very useful indeed. I will send you a PM.

Why you have this wifi issue, I can currently not say. But I also tried to setup a new build-box recently, and faced a similar issue (just only on the n8xxx kernels).

So maybe we have the same issue, then it is related to a combination of toolchain/gcc version etc. etc.

Andi
[Galaxy S III Android Development] VictorLapin:
[MENTION=971570]mad_ady[/MENTION]

I can additionally test your build if you will provide a flashable zip. Great work overall.
[Galaxy S III Android Development] mad_ady:
[MENTION=5790246]VictorLapin[/MENTION]: I am not advanced enough to make flashable zips, but here is the kernel image and here's how to flash it:

http://www.mediafire.com/download/b9s5q77c7d8f66n/boot-adrianp6.img

1. Download a flashable zip for boeffla-kernel to your phone. You will need it to restore the original kernel.

2. If you have flashed boeffla-kernel, you can flash this with this command either from adb shell, or from a shell on your phone:

dd if=/sdcard/Download/boot-adrianp6.img of=/dev/block/mmcblk0p5

(If you are not running a boeffla-kernel, flash one before running the above command so that you get boeffla's modules)

3. Reboot. If you use Boeffla-Config app, it should list the kernel as adrianp6.

4. Plug into dock

5. Do the dance of joy.

6. Restore your boeffla-kernel, so that your WIFI starts working again. :D

[MENTION=947981]Lord Boeffla[/MENTION]: Regarding the wifi issue - it doesn't list anything unusual under Catlog or dmesg when turning wifi on... But this behavior also happens when flashing a different kernel on top of your kernel (e.g. when flashing Sale's kernel from NeatRom AOSP over Boeffla, but without reflashing the ROM). I noticed in the kernel config some references to some files in the firmware. Could that be related to the issue?
[Galaxy S III Android Development] drew071:
Sorry [MENTION=2332422]temasek[/MENTION] and [MENTION=947981]Lord Boeffla[/MENTION]

i was just making people aware that under certain conditions features did/do work.

Also, i can confirm superbeam works flawlessly on Boeffla kernel without changing the setting from Auto.

drew071
[Galaxy S III Android Development] nicesoni_ash:
Did you try with wifi off? On a working wifi connection, I too can can get it working on auto. Strange?

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] n. tympanicus:
It would be nice if new options in stweaks get marked somehow so we can know what is new
[Galaxy S III Android Development] zeli9:
What do you mean stweaks? This kernel does not use stweaks.. This kernel config app has been written from scratch and not based on stweaks by gokhanmoral.

The new features can be seen in the changelog - click the menu key and select change log.
[Galaxy S III Android Development] psychok9:
Guys, can I set or show the color profile for the screen? Like movie, vivid, etc?
[Galaxy S III Android Development] zeli9:
In relation to this post I must apologize to Yank since his latest beta kernel is working fine as it should! All cores get fired up when needed and go offline properly. Probably was just some sort of glitch, no idea.. Sorry for the OT, I just thought I should report this. So FYI, folks: both Andi's and Yank's kernels are working perfectly fine with zzmoove profile!
[Galaxy S III Android Development] brujo55:
yes.
[Galaxy S III Android Development] psychok9:
Thanks. I've flashed lastest Boeffla-Kernel on 10.2 CyanogenMod rom (cm-10.2-20131002-NIGHTLY-i9305) and found the configuration, but don't seems works.

:confused:

I'll try a total wipe userdata.

update:

Wipe data/user/system... but it seems doesn't apply the movie profile.
[Galaxy S III Android Development] tisazalay:
Just remember to change scenario before changing mode. Use UI for scenario, apply and then change mode to movie, natural, etc.
[Galaxy S III Android Development] Kyle07:
Feature Request/Suggestion

Hi, Andi.

I was wondering whether it would be possible for you to allow the Boeffla-Config App to "Load&Flash" even if there is no Boeffla Kernel installed yet? Like after it has stated that one doesn't have kernel support, offer to flash a compatible kernel i.e. BK. I ask this because every time I update CM (which is quite frequently) I have to head off to your kernel download page to get the latest beta before I can Load&Flash again to new betas.

I have no idea how feasible this is technically but I thought I'd ask anyway.

Also, as a side note - I need to flash the kernel twice every time for WiFi to work. This is a new-ish development.

Regards,
[Galaxy S III Android Development] Egozy:
Andi already refered to that. Won't happen because this feature, flashing from the app, requires having a kernel which supports this (busybox related, afaik).
[Galaxy S III Android Development] Kyle07:
Ah, I see. Missed that bit of info.
[Galaxy S III Android Development] psychok9:
Thanks a lot!!! Now seems works! How can I apply it on all application, camera, etc?
[Galaxy S III Android Development] Striatum_bdr:
It applies to whole phone, it's kernel... I didn't understand if you used Boeffla config app from play store to set your kernel...

With the app each change of setting is applied immediately, saved and auto restored at each boot or Rom update

---------- Post added at 11:57 PM ---------- Previous post was at 11:51 PM ----------

I don't understand why you have to do this. I use multizip installer feature of philz recovery, in the multizip folder I copy the Rom file, the kernel zip (renamed with a z as first letter to have it last in the list), and then I flash in the same motion the Rom + the kernel, and at boot Boeffla config app restores automatically the config.

You just have to update each file accordingly. As long as the kernel version doesn't change I just replace the Rom file with the new one.
[Galaxy S III Android Development] psychok9:
I've downloaded Boeffla-Config from Play Store, obviously with previously Boeffla kernel flashed. Are there other ways?

Yeah it's applied instantly.
[Galaxy S III Android Development] partyk93:
Well, I've a question - I have Omega ROM v9.0 (based on AOKP).

Can I use this kernel? I prefer not to wipe and reinstall system if not so I ask ;)

EDIT: Ok, I tried, it works perfectly.
[Galaxy S III Android Development] andip71:
Hi,

sorry, was too late. Just wanted to answer, it should work of course.

Just be careful to take the correct one (10.1 vs. 10.2).

Cheers

Andi
[Galaxy S III Android Development] RohanAJoshi:
Using kernel on Temasek's rom, working good without any bug.

its almost perfect now with mdnie settings.

but one thing missing is that speaker equalizer...

cause default cm sound is creeks on some songs and tones (cause of high mids). and more creeks while speaker tuning is on.

please consider it as request..

thanx...
[Galaxy S III Android Development] MBurns2:
mate did you try boeffla sound ?
[Galaxy S III Android Development] RohanAJoshi:
yes, that's what i m saying, speaker equalizer support in boeffla sound.
[Galaxy S III Android Development] VictorLapin:
[MENTION=947981]Lord Boeffla[/MENTION] simply rename [MENTION=971570]mad_ady[/MENTION]'s file and replace the original boot.img in the kernel zip should do the trick, right? Just for future efforts.
[Galaxy S III Android Development] mad_ady:
In theory, yes. However last time I tried it CWM complained about having a broken zip...
[Galaxy S III Android Development] VictorLapin:
Will make a nandroid and try to repack it with WinRar
[Galaxy S III Android Development] VictorLapin:
I managed to repack [MENTION=947981]Lord Boeffla[/MENTION]'s flashable zip with [MENTION=971570]mad_ady[/MENTION] boot.img. Phone really charges in the dock now (dance of joy here). And wifi works too, I was able to search play store for updates and download one without any issues (another dance of joy here).

Zip is included. Hope Andi won't mind for two lines of additional credits in the update script :D
[Galaxy S III Android Development] mad_ady:
Hmm, wifi didn't work for me with that kernel, which is strange... Could it be a ROM issue? What ROM are you on, VictorLapin?

I will try to flash your zip to see if wifi starts working...
[Galaxy S III Android Development] VictorLapin:
I'm using latest SlimKat weekly
[Galaxy S III Android Development] mad_ady:
I flashed your zip, and you're right, wifi works now. Before, I was flashing the kernel with dd, not by using recovery. Flashing the zip seems to have done the trick. Also, when I said my ROM's stock kernel also didn't work with wifi after I had Boeffla-Kernel, I forgot to mention that I also wrote that kernel with dd.

So, the question remains - what's different between flashing a kernel with CWM and writing it with dd (apart from the step where it copies the modules to /system)?
[Galaxy S III Android Development] andip71:
Aaaaaaaaaaaaaaaaaah.... Ups, then it is clear.

In CM world, the modules are not contained within the kernel image itself. So the CWM flashable zip has some commands in to copy the modules from the zip to the correct location /system/lib/modules on the device.

If you only flash with dd, you miss the whole module part.

Andi
[Galaxy S III Android Development] andip71:
Have no issue with it. Just have to say, I will not provide support for it here.

In the next beta, mad_ady's changes will be included, I already provided him a test kernel which he apparently tested fine. Of course, if no more issues come up anywhere during the next days.

Cheers

Andi
[Galaxy S III Android Development] mad_ady:
Yes, I get that, but:

1. Wifi is not built as a module

2. Modules are copied to /system/lib/modules by your CWM installer (and remain there even if I dd some other kernel to /dev/block/mmcblock0p5)

3. My dd'ed kernel was able to load some of your modules (ntfs, but not NFS or cifs) even if wifi didn't work. Now, the kernel flashed by CWM can load all your modules (even if they don't have the same version string - I didn't bother to replace them).

So, what else am I missing?
[Galaxy S III Android Development] VictorLapin:
I understand that [MENTION=971570]mad_ady[/MENTION] already had boeffla-kernel installed and then just replaced image itself with dd. I.e. modules *were* placed in the /system/lib/modules correctly by first installation. There must be something else...
[Galaxy S III Android Development] andip71:
mad_ady:

1) Wifi IS built as a module. Always, it is the dhd.ko.

2) This is true.

3) Maybe some of the modules are less sensitive when they are not built with the same kernel build as the zimage. Just a suspicion.

Andi
[Galaxy S III Android Development] mad_ady:
Oh, I hadn't realized it was a module... Then it may make some sense. Though, the modules in VictorLapin's zip are not compiled by me... :D
[Galaxy S III Android Development] VictorLapin:
Sure thing, it's just a workaround till the next beta comes.
[Galaxy S III Android Development] RuralGalaxy:
With beta2 I felt more battery drain like beta1... But is my opinion... All works great! ;)

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Android Development] nicesoni_ash:
This is related to the experimental kernel for camera workaround fix, since no one else reported this I doubt my problem is due to this experimental kernel but I started to get lots of freezes and reboots after flashing this kernel so I moved to beta2 and since then my phone is quite stable.

Just for the info.

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] JustArchi:
3):

Active by default.
[Galaxy S III Android Development] arsal_93:
Q : I have this "No Network Problem" in my phone,so I have to use a patched kernel for my phone with a patched modem.So I wanted to know is this version of Boeffla Kernel patched ? Cause the other Boeffla version (For Stock) was already patched.
[Galaxy S III Android Development] andip71:
The kernel in the "experimental" folders on my homepage are now including the camera "workaround" and also this dock change.

So - let's see :)

Andi
[Galaxy S III Android Development] metalgearhathaway:
You know, with very little tweaking, ondemand works rather well and might be easier to adjust to alleiviate A2DP, testing a profile on that tomorrow :) Cheers for re-introducing it :) :good:
[Galaxy S III Android Development] SuperAce609:
Best use for zz insane is using the phone clocked at 1Ghz. Performance is practically the same as 1.6 but less heat and other stuff.

Except when compressing and messing with zip files. Then i crank up to 1.6.
[Galaxy S III Android Development] BonzenPaule:
Hello lads, I need your help for a situation I'm facing.

My phone is getting really fast hot with the use of just one or two apps which is usually not a big problem for me. The thing is that I am traveling a lot at the moment and for that I use Google Maps Navigation & Google Play Music at the same time in my car. To the use of GPS comes the heat from the sun which is a big part of the problem.

The phone starts to get really hot after some time and my car charger stops charging the battery. That means I can only use Navigation for one or two hours before the battery is empty.

Should I try a different governor for my navigation? My Rom is CM 11 04 April nightly and at the moment i tried "zzmove Battery extreme" & "zzmove performance" and i lowered the AC Charge to 700 what didn't help either. The phone still got extremely hot with just little sun shining on my front car window.

Should I try what SuperAce just wrote and use a performance profile with max 1 GHz? Or should I even consider changing the rom / kernel which would be really hard for because I love boeffela :(:(:(

So in conclusion I need just enough performance for music and navigation with as least heat as possible. Every suggestions are welcome! Thanks in advance!
[Galaxy S III Android Development] xrad:
I have been facing the same issue a long time ago. I then switched to using a generic phone holder that I can fix to the air vents in the cockpit. In summer the A/C is nicely cooling the device. In winter I have (mechanically) turned off the vent where phone is attached to so it doesn't get heated air. As a bonus, the phone is better accessible if you need to check the overall traffic map, for instance. Also it not longer blocks the view through the windscreen.
[Galaxy S III Android Development] habylab:
I have been having the same issues, but I've undervolted less and am now stable. I'm pretty sure the only change is related to camera and nothing too intensive, just mem stuff. Will see if it is okay today.

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] nicesoni_ash:
I even tried with no undervolt at all but still getting reboots so came back to beta2 and it's all good now.

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
Interesting, nobody else is reporting reboots with the experimental kernel so far...

Andi
[Galaxy S III Android Development] mad_ady:
I had the same problem ages ago with a Fujitsu Siemens PDA (Windows Mobile), because GPS + iGo would run the CPU in 100% and it would overheat. The solution then was to force the CPU in a low performance mode (I wrote some scripts that used the GUI to navigate and set the correct CPU state and then it would start iGo).

You can try with Boeffla app to limit the number of cores on and the maximum frequency so that it won't go past 600-700MHz. I would recommend trying to limit to only one active core (if possible) and run your navigation app. It should move slower, but it should take longer for the phone to overheat... Find the lowest frequency for your app and then use tasker or an equivalent app to set that custom profile (send an intent - see the FAQ) when you turn on Maps. From what I figured the overheat is not due to the GPS being on, but rather due to the recalculations and redraws in the app.

I will probably hit the same problem when I'll go on vacation this summer...

<offtopic>Are you the same BonzenPaule from wdlxtv? If yes, hi, small world :)</offtopic>
[Galaxy S III Android Development] habylab:
You can ignore mine. Just too much of an undervolt!
[Galaxy S III Android Development] BonzenPaule:
Thank you for the advice. I will try that and report back next weekend if it helped me.

Offtopic: yes I am the same from WDlxTV. Really funny we 2 end up again in the same forum. :D
[Galaxy S III Android Development] SuperAce609:
So i just jumped on that experimental kernel. What type of errors should we not see? So i know what to keep an eye out for.
[Galaxy S III Android Development] Buckycasuals:
I have a feeling that the latest update has problems with WIFI connection.
[Galaxy S III Android Development] andip71:
I have a feeling, WIFI works very well on my side.

Also, nothing has been changed regarding WIFI.

But seriously... feelings do not help. Do you have any facts?

Andi
[Galaxy S III Android Development] Buckycasuals:
[MENTION=947981]Lord Boeffla[/MENTION] I will continue experimenting. The beta3t1 that you posted some pages back. What effect will it have on camera? Noob here :laugh:
[Galaxy S III Android Development] andip71:
Hi,

there are people on CM and Omnirom that face various issues with various camera apps.

Like freezing, not being able to record videos, etc etc.

Just look at the threads and you will see, it is full of that issues reported.

The test kernel - only if you are affected by that problem (which has something to do with which camera module your S3 has) - could help to work around this problem.

Andi
[Galaxy S III Android Development] SuperAce609:
Is anyone using the Google camera with the experimental kernel? Panorama and photosphere don't work. After the first shot the camera goes wild and doesn't let you line up the shots. It starts moving by itself even if you don't move the phone or camera.
[Galaxy S III Android Development] andip71:
Lol, the kernel cannot move apps or things like that :)

But:

- where you affected by camera problems before?

- did you ever install a camera fix? (if so, it must be removed!!!)

- you should only use this kernel on a clean rom, no cam fixes ever applied

Andi
[Galaxy S III Android Development] artyfarty:
tried now panorama. i have a soft reboot.
[Galaxy S III Android Development] SuperAce609:
Yeah i did install the other fix from another thread. But i went back to stable 2.2 and it still happened. Is it a Google camera issue? Or was the fix installed by the experimental left over or something?

Can anyone else use panorama and photosphere on google camera?

Edit: i just uninstalled all updates to google camera to factory version and the issue is still there.
[Galaxy S III Android Development] andip71:
Guys, sorry. You need to try, check and sort this out on your own. I cannot help with anything as I never had any camera issue (only using the cam coming with CM or Omnirom, never tried another cam).

I am one of the lucky ones not affected.

But will read what you post of course.

Andi
[Galaxy S III Android Development] SuperAce609:
I don't really know anymore since i uninstalled all Google camera updates and the issue is still there.

I'm gonna have to do a clean rom install. Unless other people have the same issue as me then I'll know there's something else wrong.

---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------

Did you install any other fixes as well? What kernel are you using?