yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] seroesh:
I had a nandroid backup, but that was of JB 4.1.2 of Samsung ROM and actually since it was the first time I rooted the fone and had a custom rom and kernel.. I actually don't know how to use a nandroid backup, however, after my first custom rom v46 of Temasek and beoffla kernel, it went all okay for months.. and my bad, I didn't nandroid that before updating it :(

I'll be great if you can PM me how to revert from nandroid backup, there was so man options in recovery nandroid backup :| Since I know how to do a rom and a kernel and etc. now, but I'm still a bit of a n00b in other departments.

But if that's too much for you, I'll understand.. thanks anyways... i'll google it too to get an insight.. high time i shud know that.
[Galaxy S III Android Development] boyheadkick:
I'll try to find some sources and tutorials for you tomorrow..i'm on mobile right now..

-aL

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] Pablo.x:
Could you share with us your Boeffla Config? Thanks Lord. ☺

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] andip71:
Look at the Unofficial Boeffla Config thread, hosted by boyheadkick.

Link is in the OP.

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

Fingers crossed, going to flash v72 and Beoffla kernel! :x
[Galaxy S III Android Development] andip71:
v72 of what? Temasek?

He meanwhile released v74...

Thanks

Andi
[Galaxy S III Android Development] seroesh:
lol, he's being really quick.. I had v72.. things seemed to be working fine.. just one systemui restart, I wonder why that's been having otherwise things are stable.. should I put ANDI2 profile?
[Galaxy S III Android Development] RuralGalaxy:
Last beta with Omni works great, I didn't have any reboot or freeze. Is fast and smooth, and sound module is essential! ;)

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Android Development] seroesh:
[MENTION=947981]Lord Boeffla[/MENTION]

update, since last night's update and your kernel, I've had only two systemui restart - otherwise things are as good as they are to be expected, love the sound and the battery management of your kernel! Will apply ANDI2 today - I hope that's the one your still using and if not, can you share your current kernel profile.
[Galaxy S III Android Development] BodjieJed:
If you're ROM is CM11 based and with the new theme engine, then the system UI restart is being caused by that. It's a known issue from CM11 since the new theme engine was implemented. I don't think the kernel has anything to do with it. I'm no expert or anything, correct me if I'm wrong. :D
[Galaxy S III Android Development] seroesh:
I'm no expert either, but I think you are right, but not everyone is facing it and sadly i'm one of the victims :|
[Galaxy S III Android Development] BodjieJed:
From what I heard it's a memory leak issue being caused by the new theme engine.
[Galaxy S III Android Development] aliw32619:
Why my readahead buffer jumps to 4096 automatically?

And can i flash the new beta with Fusion 1.0.2 sp?
[Galaxy S III Android Development] andip71:
Because some other app or setting in your rom does change the read ahead buffers again. There are also some mods around which place scripts into init.d that cause this.

Lot to investigate for you :)

I think Fusion will boot loop if you do not use the Fusion bundled Boeffla kernel. Dragon, the Fusion dev, modifies my kernel before he bundles it to the rom.

So I guess, this is not possible at the moment.

Andi
[Galaxy S III Android Development] aliw32619:
I only enabled Battery tweaks and Sleep tweaks in init.d does that cause this? And i only use social apps like twitter , instagram and whatsapp
[Galaxy S III Android Development] zaryab360:
Which version is for Carbon KK?
[Galaxy S III Android Development] metalgearhathaway:
Omni :)

Sent from my GT-I9300
[Galaxy S III Android Development] mad_ady:
I was able to flash and boot a custom built kernel by using ArchiKitchen (thanks Archi!). So, I will begin to play around with the code inside samsung_battery.c and see if I can isolate the dock bug.

However, I changed the kernel release version string to differentiate it from other kernels (under General Setup - Local Version I added -CM-adrianp1). Now the Boeffla config app doesn't recognize the kernel as a Boeffla Kernel.

[MENTION=947981]Lord Boeffla[/MENTION], can you tell us what are the rules for kernel identification under Boeffla Config app? I'd like to keep using the Boeffla Config app while playing around. Currently my kernel is seen like:

root@android:/ # uname -a
Linux localhost 3.0.101-CM-adrianp1-g89511c2-dirty #1 SMP PREEMPT Wed Apr 23 18:02:48 EEST 2014 armv7l GNU/Linux
[Galaxy S III Android Development] fmehdi:
how to have dual boot with boeffla kernel
[Galaxy S III Android Development] josipborac:
You can't.
[Galaxy S III Android Development] blackhand64:
If you want to dual boot try another kernel such as googy max.

Accidentally thanked you
[Galaxy S III Android Development] nguoikhongten03:
Which version is for Temasek 4.4.2 v74 ? Thanks
[Galaxy S III Android Development] josipborac:
The omni version
[Galaxy S III Android Development] nguoikhongten03:
ok thanks :D
[Galaxy S III Android Development] lukaaa47:
it is CM version !

btw. does this kernel have built-in fix for CM camera bug like others, for example googy max2 kernel?
[Galaxy S III Android Development] VictorLapin:
Correct, for Temasek rom you need CM version

Tapatalked from Nexus 7
[Galaxy S III Android Development] kadopt:
Using omni without issues.

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] VictorLapin:
My mistake then, sorry

Tapatalked from Nexus 7
[Galaxy S III Android Development] andip71:
Yes, you need to have the String "Boeffla-Kernel" in it.

This is not possible, and also not planned. See OP.

No, it has not. I know what Googy did to fix it (thanks to him for the good communication).

But I am not intending to implement that at the moment. I wanna stay close to stock, so I go with the CM team fixing it one day.

It also seems, the fix causes other issues, so... I keep my fingers away atm.

BTW... what kernels apart from Googy have the fix built in already? I thought it was only Googy so far...

I also use Omnirom version without issues on Temasek rom. But currently both are possible.

Andi
[Galaxy S III Android Development] FlemishDroid:
Do you use Crossbreeder? In CB is a script that changes readahead buffer to 4096.

I need an invite for the OnePlus One...someone? Thx. [emoji39]
[Galaxy S III Android Development] boyheadkick:
Everyone is drooling for an invite..lol :D

-aL

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] cKenny:
my phone installed carbon nightlies + boeffla 2.3 beta 1.

Since Boeffla 2.3 beta 1, the touch wake status alway turn off after a reboot.

Any one can advise what to configure so that touch wake status won't be changed after each reboot?

Thanks!
[Galaxy S III Android Development] andip71:
I think somewhere in Carbon you can configure touch-wake as well.

So, the rom overwrites the Boeffla-Config settings.

Unfortunately, you have to configure touch-wake in the rom if it provides the settings for it. Please search, somewhere you will find them and you can enable it there.

Andi
[Galaxy S III Android Development] SuperAce609:
Has anyone been facing sleeps of dearth recently? Like just now i was playing music but i couldn't turn the screen on no matter what button i pressed. The song kept playing but after it was over, the next one didn't play.

I've been having a lot of these recently. Only happens when the screen is off though. No other issues whatsoever.
[Galaxy S III Android Development] kadopt:
Try other cpu governor / governor profile, bump minimum cpu speed to 400mhz or reduce your UV (if you're doing uv).

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] SuperAce609:
No uv at all. I was using lulzactiveq 300-1600. Been doing so for a long time now and these issues just started coming up recently. Switched to zzmove optimal to see if it occurs again.
[Galaxy S III Android Development] boyheadkick:
If this doesnt fix it, you'll have to change idle mode to IDLE+LPA

-aL

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] BrhoomHD:
is it recommended to use your kernel ``omni`` for paranoid rom 4.4.2??
[Galaxy S III Android Development] NickName98:
It worked for me....
[Galaxy S III Android Development] cloudx720:
Slimkat+omni kernel? did I do it right? :D
[Galaxy S III Android Development] Full HD:
Yes :)
[Galaxy S III Android Development] BioVolt:
Just a random question.

I wonder if in the future it would at all be possible to include an option in the kernel sound settings to use .IRS files which are used in Viper4Android addon?
[Galaxy S III Android Development] SuperAce609:
I do use idle+LPA.

What are the recommended settings for storage r/w? I have cfq for internal and external both set at 2048 mb readahead buffer. Anyone recommend other settings? I'd like something balanced
[Galaxy S III Android Development] nelsonw:
Hi guys, I'm using CM11 and the UI restarts and Camera issues are annoying. What other AOSP ROMs are available? What do you guys use? Thanks!
[Galaxy S III Android Development] Yeti47:
UI restarts are OK on temasek's latest v76 cm11 build and omni is also stable. :)
[Galaxy S III Android Development] Proud2bNoob:
Is there a way to change a profiles settings without switching to it? It always takes a long when the zram is turned off while creating a new profile.

Also it would be great if the settings only were changed after you save them.
[Galaxy S III Android Development] SuperAce609:
UltimaAOSP. You won't regret anything. No bugs or issues.
[Galaxy S III Android Development] boyheadkick:
i find zen to be quite good with multitasking..readahead i have 256 internal and 512 external
[Galaxy S III Android Development] metalgearhathaway:
For users that have not latched onto the sharing profile thread, it is well worth while, plenty of great profiles authored by enthusiasts.

I have just posted up my 3rd revision of my Intelliactive settings and would be grateful if people would test and provide feedback if you have the time and inclination! :)

http://xdaforums.com/showpost.php?p=52393838
[Galaxy S III Android Development] SuperAce609:
I updated to the latest beta for omni version and I'm still getting sleeps of death. Changed governor to zzmove as well. Is there ANY type of logs I can provide?
[Galaxy S III Android Development] JustArchi:
Probably not connected with the kernel at all.
[Galaxy S III Android Development] SuperAce609:
I have no idea. I just started getting these issues recently and I don't remember changing anything. No UV whatsoever.

The other day, the screen wouldn't turn back on but the music kept playing but stopped after the song finished and didn't play the next one. And another time before that, the low battery LED kept blinking but the screen didn't turn on. It's as if the phone is still on but doesn't turn the screen. Do you have any clues?
[Galaxy S III Android Development] boyheadkick:
try going to back to stock kernel values, that way, you'll see if the kernel really does have something to do with it..just reset the config app to go back to stock values..
[Galaxy S III Android Development] SuperAce609:
Okay, I'll do that. Lol it'll be weird as hell without boeffla sound enabled.
[Galaxy S III Android Development] Kord:
[MENTION=947981]Lord Boeffla[/MENTION]

Do you consider adding blacklist in your app for Touchwake? I'm asking because I'm using Active Display ported from Motorola and it interfere with Touchwake. Also Double tap to sleep (CM11 feature) is affected. If it can be done it will be great!

Regards :good:

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] JustArchi:
Andi, I'm glad to tell you that I managed to fix conflicting DSP with Boeffla Config V2 :).

https://github.com/omnirom/android_...mmit/b68b0c131a7cfae151140cc5926740cb87f23600

So you can remove DSP manager from conflicting apps, unless you want to keep it of course.

Cheers!
[Galaxy S III Android Development] ansonchan:
[MENTION=947981]Lord Boeffla[/MENTION] hi,wanna ask if we use the option ignore the unstable power,will it hurt our phone or battery or the charger?as i have found that my charger has something wrong already which it can only charge at 600 ,but after i have enabled the ignore unstable power it can charge normally back to 1000,so my concern is that will it hurt my phone or battery or charger? thanks
[Galaxy S III Android Development] kadopt:
Mate you have probably a dodgy usb cable or charger (most likely the cable because it's rubbish really) so it's better to test with other stuff before.

My stock charger with motorola cable can charge up to 1200mA with the safety features enabled.

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] mortoss:
My charger goes up to 1400mA with HTC cable and safety on. However it feels like my phone lasts longer when charged up to 800..
[Galaxy S III Android Development] metalgearhathaway:
That's great, although can't people just disable or delete dsp manager with titanium or rootappdelete?
[Galaxy S III Android Development] kadopt:
I actually just delete it with aroma file manager after every rom update along with other apps like cm stuff, etc.

My phone had to go to maintenance once and they said they repaired some power supply stuff in the mainboard (issue was being unable to flash anything with Odin, only bootloader was working). Now I only charge with stock current (1A) but I'll try lower to confirm your report.

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] JustArchi:
Of course you can, but what's the reason for removing something if you can actually fix it? ;)
[Galaxy S III Android Development] nicola1989:
Because Boeffla kernel have sound enhance

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] metalgearhathaway:
Agreed, I just wondered whether you might come back with information like dirty left over information etc :)
[Galaxy S III Android Development] andip71:
What is the exact name of the app in Google play store? Or do you have a link for me?

Well, this works for your rom now. But not with official Omnirom, or? Did they also change it, I guess not?

Andi
[Galaxy S III Android Development] andip71:
It can damage your charger or the charging cable in worst case. However I never heard of that in real life. But surely, there is some rest risk.

I would still recommend to invest something like 10 dollars for a better wall charger.

Andi
[Galaxy S III Android Development] NickName98:
I was «playing» with the settings of the kernel and I realised 700mhz with -75mv is the same with 200mhz no Undervolt.

Is that correct?

I mean... Why not use 700mhz as minimum cpu frequency?

I know having 200mhz Undervolted can save even more power but 700mhz feels much faster and it isn't that bad to the battery..
[Galaxy S III Android Development] andip71:
Well, depending on AVS level of your phone (AVS level decides about your voltage table), this can be the case, yes.

But: Power is not only depending on voltage, but also on frequency.

So 700 MHz with the same voltage as 200 MHz would still consume more battery.

Andi
[Galaxy S III Android Development] Hbohd:
Oh, Active Display is a feature included in few custom roms (I think I saw it in Liquidsmooth, SOKP f.e.).

I haven't enjoyed it for real, it 'replaces' lockscreen when you have some notification (I hope I understood it well :p), I prefer to use 'lockscreen notifications' feature for that.

Here is first presentation of it I came across: http://m.youtube.com/watch?v=3TMycL9mzpg

Ps. I think touchwake interferes with some 'pocket mode' mode (basing on proximity sensor, it switches screen on when you take your phone from pocket).
[Galaxy S III Android Development] JustArchi:
They merged my commit, so yeah, it's already in nightly.
[Galaxy S III Android Development] ilovehc:
Hi, i'm using EHNDROIX V 4.4.2 Rom, but i'm facing camera problems with your kernel...i'm using the CM11 based one. Should i try the other one for Omni? I don't want bad surprises!

Thanks in advance!
[Galaxy S III Android Development] andip71:
You can try. But don't expect it to work. Camera problems are well known across many kernel / rom combinations.

This is a known big mess at the moment. Depending on which camera module you have built in.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] Kord:
Acdisplay ->http://xdaforums.com/showthread.php?t=2641557

Thanks Lord :)

Regards :good:
[Galaxy S III Android Development] szunyi77:
Use standard. BANKS Gapps! https://drive.google.com/folderview?id=0B1_VgIbDrK25SUJONUFNSFpGQms&usp=sharing

This camera + lib .. Stable, no fc .. replace the stock camera.

Edit. : Sorry .. I wanted the message to be sent [MENTION=5053100]ilovehc[/MENTION]

Sorry for my bad english..
[Galaxy S III Android Development] SuperAce609:
Question, which zzmove profile is most performance oriented out of them all? I know there's a performance profile but there's also gaming and insane so i don't know. Lol
[Galaxy S III Android Development] pricey2009:
Insane is the most performance related but expect heavier battery drain..
[Galaxy S III Android Development] SuperAce609:
With 7000mAh, i literally don't worry about battery. Lol

Edit: I'll take that back, insane makes performance look like a battery profile xD. A little too much though. Lol I'll stick with the performance profile.
[Galaxy S III Android Development] andip71:
new beta

Hi guys,

small update for latest beta kernels:

Version 2.3-beta2

06.05.2014

Hot plugging of CPU cores now supported for all governors available (also wheatley, smartassv2 etc) - credits to JustArchi

Enabled previously disabled governors again (ondemand, performance, powersave, userspace)

Improved support to switch touch LEDs off completely in config app (for roms that do not provide this functionality still)

Update to latest kernel commits

Initramfs updated to version of 06.05.14

Enjoy

Andi
[Galaxy S III Android Development] SuperAce609:
Oh man. This is turning to such a giant governor buffet :D.

Though i decided to run my phone at 1Ghz but with performance profile. Should balance out the under clocking and heat. So far so good.
[Galaxy S III Android Development] metalgearhathaway:
Cheers Andi!

I have moved over to googymax just for now, as the video recorder failing to start recording has proved to be a real pain in the butt, so I have found a different rom (Liquid Smooth) that the googymax fix works with properly (i.e. it don't work on Carbon, AOKP or Pac builds).

Liquidsmooth dev has just merged the googymax fix into his own kernel build, I am going to test that also, but more than anything it would be great if you could take a look at the fix and see if it's applicable in your kernel build? Naturally, after all the time I have spend playing with tunables, I am keen to get back to my tasty boeffla :) :fingers-crossed:
[Galaxy S III Android Development] habylab:
The fix will work in every kernel, it just depends whether the kernel developer has over done the commits, and I'm assuming this isn't and will be fine!

Sent from my CM11S Galaxy S3. Proud Googy Beta tester.
[Galaxy S III Android Development] dyval:
How did you install Googy-max kernel my friend? did you use devil recovery or philz?thanks
[Galaxy S III Android Development] metalgearhathaway:
flashed via CWM recovery :)
[Galaxy S III Android Development] RuralGalaxy:
:eek: Downloading.... ;)

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Android Development] f0xy:
Lord Andi already answered this question.

The camera fix used is a temporary fix as it should be fixed within the ROM and he wants to keep the kernel as close to stock and as fresh as possible which is what the majority like about this kernel.

In my opinion when you start adding all this it just gets complicated
[Galaxy S III Android Development] metalgearhathaway:
I managed to miss the post, cheers, makes sense. I keep on missing moments of filming my little son doing stuff due to the issue, so action taken for the interim period whilst the camera Hal gets its overhaul! :)
[Galaxy S III Android Development] SuperAce609:
I have a confession to make, I've just realized setCPU was set to lulzactiveq and at 300-1600 while boeffla settings at zz performance 300-1000.

Could that have been the cause for my device never waking up? I've uninstalled setcpu, though I just used it for the temperature widget.
[Galaxy S III Android Development] f0xy:
Same here pal I'm a big snapchatter and it does get frustrating :)
[Galaxy S III Android Development] boyheadkick:
didn't the boeffla config app warn you about a conflicting app?it should have..
[Galaxy S III Android Development] andip71:
Yes, that is true.

If the memory management is really messed up by an improper linux upstream from 3.0.31 to 3.0.64 (which is done for the CM based kernel by CM team), then the root should be fixed by the devs that did that upstream.

As I want to stick as close to stock (even with bugs), I am not really intending to change that.

However, as I am curious (just not affected, so could not test), I reverted the mm back to 3.0.31 based on Googy's idea on a test kernel (CM11 and Omnirom).

They are not public as I have no clue about side effects, whatsoever.

But if someone affected or curious want to give it a try, PM me for a link.

I would never say, if this turns out to be fine, I would not merge it into my main branches :)

In fact, 3.0.31 is even closer to stock than an incorrect 3.0.64. At least closer to Sammy sources, hehe.

So, let me know if you wanna test.

Cheers

Andi
[Galaxy S III Android Development] JustArchi:
Andi, are we able to compile fully working AOSP kernel from Sammy source drop? Without doing major changes?
[Galaxy S III Android Development] andip71:
Good question Archi. I guess we would need to try it finally :)

Hard to say.

In fact, I was already thinking about it really. But had not yet enough time to give it a try already. Maybe after my holidays etc.

Andi
[Galaxy S III Android Development] JustArchi:
Lately I've been trying to apply some updates and it's the first time since I had so many conflicts in different places, AOSP kernel in fact is a mix of everything from everywhere, and I have a bad feeling about this, you know that :). It would be great if we had an alternative, even with small modifications to fit AOSP (not that many of them anyway).
[Galaxy S III Android Development] RohanAJoshi:
[MENTION=947981]Lord Boeffla[/MENTION] : Sir, I read latest beta changelog as updated sources but I checked your git for both cm and and omni kernel and I did not found this commit in both kernels :

omni : https://github.com/omnirom/android_...mmit/084c4ed422875e4f64f4fe362f30a06750641f36

.

and same is cm : https://github.com/CyanogenMod/andr...mmit/eba4e205b4e3d82ab8dd6bb6855d51d4f214e153

.

these commits are not merged in your git, so please will you update kernel with this commit ?
[Galaxy S III Android Development] andip71:
So far you have to trust me, it is included in the latest betas.

I have not yet pushed the latest changes to github (and currently cannot yet do as I have something work in progress...)

Edit: Ok, branched my repo for the experimental stuff which is work in progress. So I just pushed beta2 sources to github for you.

Andi
[Galaxy S III Android Development] andip71:
I fully agree.

Think will give it a try when I find a few hours of time.

Andi
[Galaxy S III Android Development] metalgearhathaway:
PM Sent, yes please Andi :)
[Galaxy S III Android Development] andip71:
You have pm here on xda.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer