yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] metalgearhathaway:
I'm trying to see if I can cope without all the goodies, on archi 1x, thought that might be nicer than stock, what's your opinion?

Sent from my GT-I9300

---------- Post added at 09:16 PM ---------- Previous post was at 09:09 PM ----------

Thanks for the praise and yes I'll try it as I'm a sucker for punishment! Lol!

Although someone mentions gallery issue afterwards?

Also archi and boeffla might bring back stock camera issue? For gods sake!

However, two things, archi says:

1] on first install you need to select stock kernel and go into camera once before using any custom kernel.

2) there is a fix camera option in archi installer to use if the issue arises.

So more to test.

Test test test test test.... Lol

And I thought my S2 was hard work, it really wasn't!

Sent from my GT-I9300
[Galaxy S III Android Development] metalgearhathaway:
Archi 1x fine with boeffla for me, following archi instructions as meetings in my last post :thumbup:

Like a bell end I then nandroid it and restore carbon to look for the camera odex file which is not there :banghead:

Yes I had root explorer on and hidden files visible enabled.

Go to restore my working archi installation and I am treated to a md5 mismatch :banghead:

I swear, if I did not hate Apple, iphones and even more those who buy them, I'd almost get one lol
[Galaxy S III Android Development] ginzo:
I'm sorry for all the troubles... Hope next flash of archi will be OK...

If you were buying an iPhone, you would never have so much fun ??? think positive and be happy ?

I hope that you will solve the camera problem with archi Rom soon!!

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] keneth_c:
TWRP is definitely the way to go... Never faced any issues as such.

Compare that to CWM or PhilZ... I'm sorry... But both are blah! Still can't guarantee results 100%...
[Galaxy S III Android Development] metalgearhathaway:
Back on archi, all fine once more, I know what I'm letting myself in for, but sometimes you wish you could catch a break :)
[Galaxy S III Android Development] ghoster76:
Using this kernel on ArchiDroid 2.5 based on CM, I have the pale color screen instead normal splendid amoled screen color. I mean when I use ArchiKernel, the color is trully better, it might cause by his own products compatible each other, but I don't know why when I'm using boffla kernel.
[Galaxy S III Android Development] TheRuan:
Is there any chance we can get a beta version set to max CPU / OC at 1.8GHz?

I'm liking the 1.7ghz and so far my phone never past 50c, so i believe that short bursts up to 1.8ghz wouldn't overheat the phone.
[Galaxy S III Android Development] nightwing90:
Mee too had the same experience when i used Archi 2.4.6 + Boeffla :rolleyes:
[Galaxy S III Android Development] TheRuan:
Try to compare settings on mDNIe on screen / advanced display for CM, there is also this option on boeffla app.

Archi may have set something about this inside his own kernel.
[Galaxy S III Android Development] JustArchi:
No, my kernel is based on Sammy sources, while Boeffla is based on smdk4x12 sources. And I told you already multiple times that smdk4x12 is not properly upstreamed to any Update higher than 7, and better colors were included around Update12. So naturally, my kernel includes stock colors, while Boeffla includes original ones.

Also, I'm not sure but I swear that I saw Andi including these colors into Boeffla long time ago.
[Galaxy S III Android Development] andip71:
The CM11 Boeffla kernel carries the "older" MDNIE implementation (just like CM11 standard).

The Omnirom Boeffla kernel has the newer MDNIE implementation contained in update12 in (just like Omnirom standard).

According to my "close to stock" objective, the MDNIE are as in the originals.

Install Omnirom kernel if you want.

No chance.

1.8 GHz does not run stable on any of my phones, so I will not put it in.

Plus: I was for more than a year even reluctant to put 1600 OC in, now I went to 1700 even (which is real overclocking, outside of Exynos specs). 1800 will not come anymore, sorry.

Andi
[Galaxy S III Android Development] andip71:
New beta

Hi all,

unfortunately I had to skip my plan to release the kernel as stable now.

Due to a quite significant bug in CPU scaling when you used 1700 MHz overclocking, I want to do one more beta before it will come out as stable.

Version 2.3-beta8

04.07.2014

Correct frequency scaling issues when using 1700 MHz overclocking (the 1700 step is now replaced by 1704, you will be automatically converted) - thanks to ZaneZam for help

Set correct permissions for boeffla-kernel-data folder during every startup

Corrected power preset

Initramfs: Update to version of nightly 03.07.2014

Andi
[Galaxy S III Android Development] boyheadkick:
Well, well, what have we here?knock on configuration? :D
[Galaxy S III Android Development] andip71:
But look at that post:

http://xdaforums.com/showpost.php?p=53894263&postcount=13956

It will come maybe next week.

And it is NOT the known LG feature where you can wake the phone up by a double tap. Just to set expectations.

It is in fact a touch-wake, which does not bring the screen back with one tap but with a double tap only.

Andi
[Galaxy S III Android Development] boyheadkick:
Still a nice addition..gives me another option since i hate how when i close the screen to lock and i happen to accidentally touch the screen it wakes up again..much thanks
[Galaxy S III Android Development] andip71:
That is exactly what it should be about.

Andi
[Galaxy S III Android Development] Delgadovsky:
Well, i usually use roms based in Omni and always using boeffla omni, of course. But know i change to Archi 2.5, based in CM11. I have the zip file from boeffla kernel 2.3 beta 7 and install normally like always do and then remember that is CM11 based. However, all is working good. So, in CM11 is ok to install Omni kernel???? Because the other way cause bootloop... Any one is better than the other? Thanks

Great work Andi :D
[Galaxy S III Android Development] andip71:
At the moment, the initramfs are similar enough to make the Omnirom kernel work on CM11 based roms, yes.

So you can use that combo as well.

Just, go for beta8 please. It has been released this morning.

And to ALL: You might have noticed I included the new flash binary in the flashable zips. So no message anymore about a legacy binary when you flash e.g. in Philz Recovery. To stop that as well :)

Andi
[Galaxy S III Android Development] Delgadovsky:
But to use a CM11 base ROM is better a CM11 base kernel than Omni, right? Probably a stupid question because if was the same you only make 1 kernel type... Just to confirm. ?
[Galaxy S III Android Development] andip71:
Better is the wrong word.

You can use the Omni kernel without issues, nothing will break due to that more or less.

Just the CM kernel is closer to the CM original kernel, from a code base point of view.

Andi
[Galaxy S III Android Development] Buckycasuals:
You can install Omni or CM kernel. I reckon some users saying that OMNI gives a better graphic and screen display than CM. Maybe a placebo :laugh:
[Galaxy S III Android Development] andip71:
Nope, no placebo. "Better" is again questionable.

CM11 kernel has the older Samsung MDNIE control implemented, whereas Omnirom team upgraded to the newer one contained in Samsung source update12 onwards.

So you have the full choice :)

Andi
[Galaxy S III Android Development] marenp:
I will try beta8, but small problem appeared, i am on ArchiDroid 2.5 and when i want to flash new kernel via boeffla config using option load and flash it appears new kernel but when i press to download test kernel nothing happened :/
[Galaxy S III Android Development] andip71:
Then you have either an app blocking boeffla-config from writing into the file system. Or the folder has improper permissions.

I cannot say, but would recommend you download this time manually the kernel and install in recovery. Maybe this solves your issue for the future as the kernel will in future correct permissions itself.

I heard some times already about this on ArchiDroid... not sure what it is in the end.

Andi
[Galaxy S III Android Development] marenp:
Ok, thanks man :)

Edit: manually flashed, and issue is solved, flashing kernel via app working now :)
[Galaxy S III Android Development] boyheadkick:
i can vouch for this...running beta7 with mdnie scenario 8 gives almost the same colors as stock sammy, in my opinion..even my girlfriend has commented that my s3 running carbonrom and boeffla omni has sharper and brighter screen compared to her note2 running stock non rooted touchwiz
[Galaxy S III Android Development] andip71:
Look into the faq please, all described there.

Andi
[Galaxy S III Android Development] szunyi77:
hello

The "Knock on status" to be activated?

I displayed but grayed out and I can not turn it on, unfortunately ...

Thanks
[Galaxy S III Android Development] ZaneZam:
it's not implemented yet (next beta will have it), the settings in the app are only a preparation for that.
[Galaxy S III Android Development] felix297:
Hey Andi,

with the newest beta i got problems with ocing to 1704Mhz. Even if i rise CPU Voltage to 1500mV the device freezes (and overheats, but thats not the problem).

With all the versions before beta8 ocing to 1700Mhz was no problem even with moderate (-25/-50mV) undervolting. I've been using 1,7Ghz since you have implented it. This behaviour is the same as for example with Agni Kernel, it also freezes at 1704Mhz. Can the change of 4 Mhz really have such an impact on stability? Or have you changed something else in the background?

I'm currently using Temasek's V109 Rom. Thank you in advance for your help.

Oh, and i wanted to say that for a long time now: a big THANK YOU for your work on this device!

Greetings from germany,

Felix
[Galaxy S III Android Development] andip71:
First of all, and sorry for OT: Ger-ma-ny. Semi finals, yeah.

Well, before the 1700 were something but not really 1700 as I used wrong clock dividers.

So it is apparent it is now more than 4 Mhz difference.

Maybe you need to increase voltage a bit on the 1700 step to get it stable.

But overclocking is always a game in the end.

Good luck

Andi
[Galaxy S III Android Development] andip71:
Yes. Please guys, read the change log for the app as well. It is posted on the homepage as well as it is available in the app menu...

Andi
[Galaxy S III Android Development] Choristav:
I'd say undervolting is more of a game.

In fact, I'll just take a moment's notice to say that my undervolting limits are changed with pretty much every kernel version.

It takes me about 50mV more to get 1704Mhz stable than what it did before.
[Galaxy S III Android Development] JustArchi:
Maybe it's just me, but I'd prefer to have back two stable 1500 and 1600 steps :).
[Galaxy S III Android Development] andip71:
For me both 1600 and 1704 are rock stable, even with 50 mV undervolting.
[Galaxy S III Android Development] metalgearhathaway:
I agree! I'm sticking with previous beta and 1600mhz, an extra 100mhz will make little difference really, but I am a fan of oc and understand that anyone with time and patience can have some fun with it regardless.

At the end of the day, it's not the CPU that holds this device back, it's the crippling ram limitation.

Still! It's all wonderful stuff and the fact that andi and archi are still supporting this device in its twilight years is pretty awesome!

Sent from my GT-I9300
[Galaxy S III Android Development] felix297:
OK, now i have tried the new beta with 4.3 Stock firmware. Still no luck. Even at the max voltage limit at 1500mV the device freezes at 1704Mhz in any stability test.. And after a while it gets very, very hot, so it's not very healthy (77-80°C CPU). But i also have to say my ASV value is quite bad: 1.

So for now it seems i have to use 1600Mhz with 25mV undervolt. Stable! ;)

Greetings,

Felix
[Galaxy S III Android Development] TheRuan:
Did u try to chance only the voltage for 1704mhz to 1375~1450mV

Btw 1500mV for 1704 isn't overvolt?

Sent from my S4
[Galaxy S III Android Development] felix297:
yes i tried it at default voltage so 1425mV. It freezes. 1500mV is the maximum the kernel can do so its a pretty heavy overvolt. And even there its freezing! It seems like I got a very bad cpu :D
[Galaxy S III Android Development] TheRuan:
Just for curiosity, did u test ur phone using a CM based or Omnirom?

If u can/want to, try last archi rom with boeffla cm11 2.3b8 kernel

http://xdaforums.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859

I'm saying this 'cause i've seen several complains of very high temperature like 75ºC and above, and most people are using stock based firmware.

BTW, are u using the right kernel? cause u have posted under cm11/omni/cm10 thread, no complains from me, i just realized that. :laugh::laugh:
[Galaxy S III Android Development] ayoubij:
I have the same problem, at first I thought I was a rom problem, but it may be the same as you, the undervolting and overclocking to 1704

before the same exact settings was working for 1700 but now not for 1704
[Galaxy S III Android Development] Tommyknocker1981:
1704 with undervolt Light working here. Slimkat weekly 6. Newest omni Kernel.
[Galaxy S III Android Development] TheRuan:
Andi,

Did the other frequencies change too?

I can't get stable using the same voltages as i did on cm11 2.3b7 on b8

I read about the 1704 being changed, but it seems that 1600 and maybe other frequencies changed too, they seem to need about +50mV than before, still testing...
[Galaxy S III Android Development] felix297:
I did test it with the latest Rom from Temasek with CM Kernel and now with the official ND5 4.3 Stock Rom with Sammy kernel. The problem isn't the overheating. Its just the cpu which needs such high voltages to handle 1.7Ghz and therefore it overheats after time. And even on the kernel maximum voltage the cpu can't handle it, no matter if on CM/Omni/Sammy/SammyKKport.

So in conclusion I can say after this frequency correction with the new beta its definitely more critical to get 1.7 Ghz with low ASV values/worse chips.

I think thats not the target for boeffla kernel. Until now it has been a kernel which provides excellent stability with oc at stock voltages for all of us. But now maybe the most of the devices can handle it but not all. I wouldn't suggest a rollback but maybe a warning in the Boeffla-App when you select 1.7Ghz. :)
[Galaxy S III Android Development] cloudx720:
I got asv of 6 :) 1704mhz works fine with 600mhz GPU step don't even get that hot while gaming :D and I game alot! Best kernel ever made.

---------- Post added at 03:45 PM ---------- Previous post was at 03:21 PM ----------

possibly the highest score I have ever got! And possibly the highest score an S3 has ever got?? [emoji2][emoji12][emoji2]
[Galaxy S III Android Development] flither:
Couldn't resist :D
[Galaxy S III Android Development] flither:
wow, best Antutu score for s3 I've seen!
[Galaxy S III Android Development] DualJoe:
The 600/1300MHz uV steps are different than the others (shifted by 12.5mV, 875<> 888). That's ok or another divider bug?
[Galaxy S III Android Development] andip71:
Nothing else changed apart from correcting the fault 1700 mhz.

But I explained either here or in the other thread why some have trouble getting 1704 stable.

To remind again - I am very much contra overclocking. It is a game, known thing.

Plus: there are phones that cannot handle it. There is absolutely ZERO you can do about it in worst case.

And to remind again... Do not undervolt if you want to be stable.

Andi
[Galaxy S III Android Development] andip71:
Very nice ☺
[Galaxy S III Android Development] SuperAce609:
But your phone might have a virus
[Galaxy S III Android Development] SuperAce609:
I find it ironic that boeffla sound is considered a conflicting app. I understand why and it's logical but still. Lol
[Galaxy S III Android Development] TheRuan:
I used to use the original cable + original Samsung charge right before i found Boeffla Kernel (which now allows to me force the 1100mA input).

My point is that in the paste even using original stuf, my phone would take hours, and i mean at least 7 hours to charge.

Honestly in the charging point of view i miss the older chargers.

On further tests I found out that :)

For some reason i had to put a bit more for 1600 too.

Other frequencies remain the same way.

Andi,

I really can't complain about instability, ur Kernel is far away the most stable i've ever seen in my S3, even beta versions are very much stable.

One idea that could be cool to introduce in ur App would be the ability to recognise if the phone was properly shutdown.

For instance:

I try to do some overlock or undervolt and the phone freezes.

When the phone is turned on again, boeffla app could verify a possible reason for it by matching a recent change in min/max frequencies and voltages in cpu and gpu, after that the boeffla app would revert what was done by applying an older setting.

To know that the app could hold a simple table with the voltage list and frequencies, which could be saved every time we apply new voltage or with a new option that would be like a checkpoint.

Felix,

The problem may not be overheating causing the failure as u say, but keep in mind that if u use higher voltage input, it will mean faster heat on cpu, which could easily allow the cpu go over it's maximum temperature = burning it, so don't do it. xD
[Galaxy S III Android Development] felix297:
Yeah I know. I did it just for the test if my CPU can do the proper 1,7Ghz anyhow. But it can't! :D So currently I'm at 1.6Ghz with -25mV.

Greetings,

Felix
[Galaxy S III Android Development] nicola1989:
I have to say last beta is great, nice score with oc at 1700 and - 100 under volt!
[Galaxy S III Android Development] flither:
Boeffla Config already has this option, at least it is working sometimes. I undervolted and had a LOT of crashes, and after reboot the last changed UV was coming back to before crash value, or whole UV table was reverted to stock.
[Galaxy S III Android Development] TheRuan:
It happened to me sometimes too, but i thought it was cause it had applied the lower voltage and crashed before saving the setting in the app itself.
[Galaxy S III Android Development] flither:
if you're applying new, too low voltage, it has been applied to UV table straight away after hitting "apply", thats why the phone crashes, doesn't it?;) so it has to have some kind of "revert to previous state" mechanism built in, or am I wrong [MENTION=947981]Lord Boeffla[/MENTION]?
[Galaxy S III Android Development] andip71:
Well, honestly I have to say... you are both wrong and right.

It is not by intention, but first the app applies the frequency and voltage settings. And then it does write it to the configuration itself. If the phone crashes already before, you are reverted to where you were before, yes.

But the other idea is not too bad, I can try to implement some kind of proper-shutdown detection, although it might be a bit flakey. Let me think over the next weeks when I am relocating finally, then I might have some time for thinking work :)

Andi
[Galaxy S III Android Development] migz012788:
Impressed on this kernel. Been using this since 4.1.2 days. Every version is stable even I used the Beta/test kernels. Im on OC CPU 1704 and UV 75mV. And GPU UV 75mV no issue here. :) everything works well :)
[Galaxy S III Android Development] SuperAce609:
...but this is a kernel though.
[Galaxy S III Android Development] migz012788:
Oh sorry. Hahaha. Edited :)
[Galaxy S III Android Development] hwjrmrm:
Dear Andi,thanks for your kernel. I'm now on CM11 0706,need boeffla kernel tweak setting for battery saving,I dont play games,thanks.
[Galaxy S III Android Development] seroesh:
[MENTION=947981]Lord Boeffla[/MENTION]

Please find attached the screen shot of Kernel wakelocks that I've been plagued with for the last 5-7 days, battery life has significantly! Any help as to how can I rid my phone of these and return back to the normal awesome battery life, I used to get? :(
[Galaxy S III Android Development] andip71:
This multipdp wakelock is known to be a problem with your mobile network provider.

It seems the fast dormancy setting is not correct. But it is mainly second hand information I have now, as I fortunately never faced this issue.

But I am very sure someone can step in here and tell you more...

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

Andi i was just wondering if it's possible for you to compile a experiment version based on archikernel's sources and with all your features? You know clean update13 sourcea from archi and your awesome features including app support! Is it possible? Ofcourse whenever you have free time to do so as you are quite busy these days with your relocation stuff.

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] andip71:
Everything is possible - in theory.

But I am not gonna do that for two reasons:

- I have absolutely zero time as I am relocating in exactly 8 days

- I only base my kernels on official project sources, not on other devs source base (nothing against any other devs, but this is my personal ground rule)

So, no chance for the next 4-6 weeks until I am settled again.

And just btw: What is wrong with the current base? I happily use my kernel and cannot see any flaws that would justify that for the time being?

Andi
[Galaxy S III Android Development] abhibnl:
Well i tested that kernel and call it a placebo or not, battery lyf and smoothness were definately improved. I've no issues with current boeffla version, everything is working as it should. [emoji4] It was asked out of curiosity to have your features on that kernel sources! No problem though, respect your policies!

Sent from Galaxy S3 Powered by Archi + Boeffla
[Galaxy S III Android Development] andip71:
Never say never, maybe in some weeks, when all is fine on my side again, I give it a shot on fresh update13 only sources.

Why not?

But just now it is not possible for me time-wise.

I even have to sacrifice n8000 users currently which are waiting for a kitkat kernel... :(

Andi
[Galaxy S III Android Development] claptraw:
Just a quick but big thanks to Andi! Boeffla Kernel is the best that could happen to my S3. It's performing fast and smooth like never before! I will stick to it until my S3 dies.

P.S.: Nochmal besten Dank, Landsmann. :)

~ GT-i9300 ~ CM11 M7 ~ Boeffla Kernel 2.2 ~ XDA Premium 4
[Galaxy S III Android Development] artyfarty:
:crying: :crying: :crying:

(i'm joking...)
[Galaxy S III Android Development] andip71:
But believe me, it is hard for me to not upgrade to Kitkat on my n8000 either in the next weeks. Anyways, have no time to use my tablet at all, but still...

:)

Andi
[Galaxy S III Android Development] anybuddy:
1. Yes, because every Rom has his own Kernel.

2. No wipe needed.

--------------------------------------------------

Gesendet von meinem GT-I9305

ROM: | CarbonRom | Kernel: | Boeffla-Kernel |

If I've helped you, please press the Thanks Button!
[Galaxy S III Android Development] Maxpawner:
OK thx :D

and one more question, I must have boeffla app on my phone?

Gesendet von meinem Galaxy S3 @ CyanogenMod 10.2 mit Tapatalk 4 now Free
[Galaxy S III Android Development] spoonymoon:
Hei

Will this boot on pacrom 10.2 ?

And will the new pac framework respotories get implemented?

Thx
[Galaxy S III Android Development] Egozy:
You dont have to, but it's the only way to configure the kernel.
[Galaxy S III Android Development] Maxpawner:
Nice OK thx :)

Gesendet von meinem Galaxy S3 @ CyanogenMod 10.2 mit Tapatalk 4 now Free
[Galaxy S III Android Development] amppen:
1. Yes

2. No wiping required after kernel flash

Tapatalked
[Galaxy S III Android Development] andip71:
What the heck is the "new pac framework repository"? Sorry for stupid question, but I do not have the bandwidth to test and follow each and every custom rom.

I am testing the CM kernel on CM nightly, Slim, AOKP and Archi only.

Cheers

Andi