yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] striked0wn:
Yep.. It really works.. I can't get why.. xD.. o_O.. Maybe derteufel could bring light into the darkness.. (As we're saying in germany).. :).. I can't guarantee that it'll work cause as i remember someone here said if you're flashing stock kernel.. Then using camera and the flashing devils kernel again it'll work.. (Couldn't test that)..

So about the guide i made it this way:

1. Booting into recovery.. (Backed up all my files through adb on my pc)

2. Formatted with devil's recovery system, cache, preload and then data, sdcard ./secondrom (all select to ext4 of course)..

3. Reboot into recovery again.. Made a factory reset (yes i will install a new rom).. To be sure all is deleted.. And formatted the right way..

4. Tried to restore files through adb (which gave me as expected wrong permissions set).. So don't do this.. I've copied internal data from pc onto my extsd card..

Then i've pushed through adb a rom onto my gs3..

After that i've copied with a file explorer important things like camera folder and whatsapp backups back onto my intsd.. :)

Alternative way is to backup whole partitions through recovery onto extsd which i wouldn't do cause best way is to do a factory reset to get no errors and don't having strange errors due to some unknown problems f2fs or something else did with the files before.. :)
[Galaxy S III Original Android Development] coolhof:
I have no problems with the camera.

Have test it on cm11 and stock 4.3.

Also I tried on ext4 and f2fs.

Send From A Devil3 - f2fs - Dualboot Powered Machine
[Galaxy S III Original Android Development] Olioaglio:
Which kernel version are you using? Have you tried YouTube? It stated playback problems after some time running the rom. Play one or two video, then exit YouTube, wait some time and reload YouTube then. Still working or giving error?

Olioaglio
[Galaxy S III Original Android Development] coolhof:
I'm on Devil3 4_0.1.4

Also no problems with the you tube player.

Can't reproduce the problems you have.

Send From A Devil3 - f2fs - Dualboot Powered Machine
[Galaxy S III Original Android Development] striked0wn:
Strange.. Have you tried omni..?!.. [MENTION=420407]Olioaglio[/MENTION] are you using ArchiDroid or omni based rom too..?!..:)

And if it is ArchiDroid could you pls test before formatting to ext4 if the problem exists with official omni nightly..?!..:).. I really don't think it's related to Archi but who knows..:)

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] coolhof:
I use "crDroid Simple"(cm11)

Never tried Omni or ArchiDroid.

Send From A Devil3 - f2fs - Dualboot Powered Machine
[Galaxy S III Original Android Development] Olioaglio:
No, I do not use dualboot ATM. I'm on temasek v59 single boot first rom right now. I really don't know when this nasty problem came up first. I think it could be maybe since the cm11 rework which required kernel patching (think 3.4 0.1.0 with temasek v50 was the last one working properly). Strange. [MENTION=5139098]andreasltcf[/MENTION], is it still working on ext4? Will reformat then.

Olioaglio
[Galaxy S III Original Android Development] striked0wn:
Jep.. Still working..:).. But about the problem with camera i think it was before too.. But don't take this statement and call it around.. Cause i think and don't know..:P

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] Olioaglio:
Just switched to AGNi 2.7.5 R3 kernel with f2fs support and test it with temasek v59 (no fresh install). Will keep you updated.

Olioaglio

Edit: works for the moment with AGNi kernel on f2fs. Though it feels a little laggier than devils. Hope Devil will update soon.
[Galaxy S III Original Android Development] drgreenth:
No problems here. Latest devil, f2fs, temasek v59

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] adzz37:
will this work on stock 4.3 rom?
[Galaxy S III Original Android Development] drgreenth:
Yes it wiill.

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] Marvis21:
Hey Dominik,

missed you here for a while. It was good to read, you still keep your work alive.

A littel donation from Bavaria 10$ for you to show your family there are people understoud your work. Just made my first de/compiling and modding steps. You are one of my inspirations.

Sorry, my spoken english is better. :silly:
[Galaxy S III Original Android Development] ahmed bahaa:
will this work on Resurrection Remix ROM (kitkat)?
[Galaxy S III Original Android Development] DerTeufel1980:
Thank you very much for your donation, it's highly appreciated.

I ll be back from work next week on Tuesday or Thursday, then I should have time for a new kernel version.

Are there any new features implemented in other kernels meanwhile, which I should look at?

Gesendet von meinem Note II mit Tapatalk 2
[Galaxy S III Original Android Development] S1ay3r666:
I think you could update zzmove to version 0.8 and implement some profiles like Battery Yank Extreme
[Galaxy S III Original Android Development] bjpafa:
f2fs -Dualboot

Maibe You should read "Dual-Boot FAQ thread | devil2-kernel by DerTeufel1980 [Note 2]" and all links from there. From DerTeufel1980...:)
[Galaxy S III Original Android Development] Marvis21:
Oh, i would love to see Yankgasm Profile in Boffla Sound Presets. ;) :angel: If its ok for Yank, of course.

And by the way, I was just freeking out yesterday by trying to get dualboot to work, yesterday evening.

Tryied 3 times, till I found out that you have modified the way you manage first and second rom. This thing with red and blue is awesome! :p
[Galaxy S III Original Android Development] striked0wn:
Just pull the script from zip and make it to an init.d script.. Works great on my device with voodoo sound too..:)
[Galaxy S III Original Android Development] Marvis21:
So sorry for Offtopic, but this means what? I have the equalizier settings form Yanks kernel. And then? Make it looking like this

#!/system/bin/sh
# Yankgasm Equalizer Settings changes
echo "10 4 2 4 7" > /sys/class/misc/boeffla_sound/eq_gains
echo "1 4027 1031 0 276" > /sys/class/misc/boeffla_sound/eq_bands
echo "2 8076 61555 456 456" > /sys/class/misc/boeffla_sound/eq_bands
echo "3 7256 62323 2644 1368" > /sys/class/misc/boeffla_sound/eq_bands
echo "4 5774 63529 1965 4355" > /sys/class/misc/boeffla_sound/eq_bands
echo "5 1380 1369 0 16384" > /sys/class/misc/boeffla_sound/eq_bands
echo `date +"%F %R:%S : Boeffla Sound Engine - Yankgasm Equalizer Settings."` >>$log_file

And testing it in Terminal (first try ever to make a script) changes the values correct in Boeffla Sound App.:victory:

Then it set sound every boot to this values, right? :confused:
[Galaxy S III Original Android Development] Buckycasuals:
The way you ask question piss me off. I read your comment in some pages back, Why don't desist from asking such silly and straight forward question without paying a homage to the DEV.
[Galaxy S III Original Android Development] ahmed bahaa:
cuz i dont get any replies, also btw this is my first question about RR ROM, besides dont reply if you aren't interested to

however the reason for my question is that some time ago, when i posted my first question which was about BAM ROM, was that even the kernel supports that type of ROM, but not bam rom (at that time) and that is the only reason for my question

and thank you if you dont wanna reply, it is okay for me! but please dont reply to me like that cuz i hate being humiliated!
[Galaxy S III Original Android Development] habylab:
Is the last test version working well? Haven't seen any negatives.

Sent from my CM11S Galaxy S3. Proud Googy Beta tester.
[Galaxy S III Original Android Development] Scarface1991:
I have absolutely no issues with Devil3.4_0.1.4

The Kernel is very smooth, there are no heating issues and it is very reliable (no softreboots etc). Amazing work [MENTION=4196889]DerTeufel1980[/MENTION]
[Galaxy S III Original Android Development] cloudx720:
is the latest kernel on the first page?
[Galaxy S III Original Android Development] Moster2:
Indirectly yes. If you follow the f2fs link, you will get a post that links here http://xdaforums.com/showpost.php?p=51148539&postcount=1804
[Galaxy S III Original Android Development] Marvis21:
Hey man,

flashed 20140402 RR this morning as Sec-Rom and till now no problem with latest Devil-Kernel. ;)
[Galaxy S III Original Android Development] ahmed bahaa:
thanks a lot man, that was really helpful :) but btw does touch--to-wakeup works fine?
[Galaxy S III Original Android Development] Gokulbalram:
I'm having trouble when I OC it to 1800MHZ. I'm on PA 4.2 B2. All it does is shut down. Help!
[Galaxy S III Original Android Development] Moster2:
Then your phone can either not handle 1800 Mhz or the voltages are too low.
[Galaxy S III Original Android Development] Mostafa Wael:
Has anybody managed to get his phone stable when overclocking the CPU to 2GHz ?
[Galaxy S III Original Android Development] motshek:
In my s3 2Ghz is semi stable... Antutu pass then temperature too high and phone automaticaly underclocking to 700mhz next if temperature is low CPU come back to 2Ghz.

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] Gokulbalram:
Tried changing voltages, they won't go beyond 1500 in DKM. So I put it on 1500 tried 1.8GHZ, with the performance governor and tried antutu benchmark, it just crashes after I run antutu. Otherwise works.

Sent from my Magic Talking Parrot. Which is an i9000
[Galaxy S III Original Android Development] motshek:
In my s3 1.8ghz and 1400mv is full stable..antutu never crash...

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] Mostafa Wael:
Look guys, i OCed my CPU to 1.8GHz and it suddenly rebooted at 21% in antutu.

Will overvolting this step to 1500mv help with stability?
[Galaxy S III Original Android Development] torsrex:
Everyone's cpu is different, some can handle high frequencies at lower voltages than others. Increasing the voltage will help with stability, but it's not guaranteed that your specific cpu will be stable at 1,8GHz nor is it reccomended to keep your phone at 1500mv for an extended period of time. Doing so will degrade your chip faster. Also, the s3 throttles the cpu when it reaches a certain temperature, so keeping it at 1,8GHz for an extended period isn't recommended as it'll just throttle once it reaches this temperature. Oc-ing to 1,5 or 1,6 GHz can be worth it if your phone's stable at these frequencies with a relative low voltage bump compared to 1,4Ghz, but oc-ing to 1,8GHz is mostly for getting the highest benchmark result.

If you're absolutely determined to try and get your phone running at 1,8GHz, you could try to increase the voltage of the other steps below it, as it might need a bit more juice while scaling, but this is not reccomended (higher battery drain, higher temperature, faster degrading chip and so on). For reference, power consumption for a cpu is measured by P=f*c*V^2 (where p is power consumtion, f is frequency, c is capacistance and v is voltage).
[Galaxy S III Original Android Development] Mostafa Wael:
So problem is not voltages only, which means Overvolting will not help,

it turns out that my device max stable is 1.7 GHz

does that mean that some people can hardly overclock their CPU for example to 1.5 GHz?

that's weird!!!

i wonder if that would be the same with the LG G Pro 2 for example of for the hTC One M8

:confused:
[Galaxy S III Original Android Development] Gassity:
Cannot find how to format to F2FS? There's no submenu for me
[Galaxy S III Original Android Development] JustArchi:
When you select partition there should be.
[Galaxy S III Original Android Development] tetakpatak:
Only the recent devil dual boot recovery (v6.0.4.5) has this feature under "Mounts and Storage“. You can format these 3 partitions to f2fs: system, cache and "data and data/media".

The older dual boot recovery (version 6.0.4.4) is ext4 only.

tetakpatalked from my N7100
[Galaxy S III Original Android Development] Gassity:
My god! Why there's no new versions in the op post!?

Can you give me a link to the latest kernel and the latest recovery?
[Galaxy S III Original Android Development] Moster2:
Everything is here: http://xdaforums.com/showpost.php?p=49979584&postcount=1116
[Galaxy S III Original Android Development] Scarface1991:
setting different settings inside the devil App for the Sound Engine has absolutely no effect on the latest SlimKat weekly when playing music (except 3d effect). Anyone who can confirm?

I'm using the latest available Devil Kernel.
[Galaxy S III Original Android Development] Gassity:
So I've formatted everything to f2fs, how should I notice the difference? Now I can't even pass antutu benchmark.

And can I use any other kernel with f2fs, or it should be the devil one?
[Galaxy S III Original Android Development] k-semler:
I can't seem to figure out how to enable exFAT support on this kernel. I'm running OmniROM. OmniROM does support exFAT natively, and Boeffla Kernel supports it too. Is there a way to get Devil Kernel to get exFAT to work?
[Galaxy S III Original Android Development] Moscow Desire:
Knock it off folks!

You all know the rules and how to post correctly. No need for us moderators to hafta come in and clean up.

Any more nonsense, and might be some early summer vacations :eek:

2 posts deleted. Back off from the keyboard, take 5, have a coffee.

Carry On.

MD
[Galaxy S III Original Android Development] Mostafa Wael:
Hey guys,

I have been using this kernel for long long time and i must say it is the best kernel ever, but i have the following 2 nasty errors:

-after a couple of videos, a popup says "sorry this video cannot be played"

-unable to connect to WIFIs other than that one i connected to it firstly after i freshly flashed the ROM.

I do not know if these errors are ROM related or not, but i think the WIFI problem is a kernel related issue for sure.

I am using Archidroid 2.4.2 experimental build + Devil3.4_0.1.4 + F2FS formatted file system + Dalvik

Thank you for your wonderful work!

Waiting for next build (my fingers are itching me, didn't know that i am such a flash-holic person :D )
[Galaxy S III Original Android Development] tetakpatak:
On my N7100 I got Antutu score almost 24K with devil2 kernel :D

No kernel without f2fs support can boot as long as you're on f2fs

tetakpatalked from Nexus 7
[Galaxy S III Original Android Development] Gassity:
Made a clean install of Temasek's newest rom and devil kernel, but can't pass antutu again.

All though the kernell is extremely laggy after my experience with the boeffla one, that was rock solid. Hope the kernel would update in a nearest future, cuz it's like a breath of a fresh air for our old farts i9300's.
[Galaxy S III Original Android Development] cba1986:
[MENTION=4196889]DerTeufel1980[/MENTION] Maybe if you have the time you could check why sometimes settings are not applied on boot when using AOSP. Or perhaps the memory issue that cause the camera to FC (Less frequently now)

Thanks in advance
[Galaxy S III Original Android Development] Choristav:
[MENTION=4196889]DerTeufel1980[/MENTION]

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=i9300i

This seems like an exynos device with a 3.4 kernel.
[Galaxy S III Original Android Development] pippoaacc:
I think it could be useful. When restoring a 2nd rom nandroid as first rom (because I switched to f2fs and decided to switch 2nd to 1st rom and drop sammy 1st rom) internal sdcard symlink seemed to be broken. Then I found a sdmount init.d script to mount data/media as sdcard in 2nd rom. So in order to exchange 1st and 2nd rom i needed to delete this script. Now all it's ok. Just in case you face the same problem.

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Original Android Development] DualJoe:
Indeed. That's the most annoying bug currently on I9300. The root fault seems actually related to the hardware video encoder/decoder subsystem. It also affects YouTube app video playback, browser WebM videos, MX Player hardware playback (fallback to software renderer) and probably every other application related to that video interface.

The error in logcat is always OMX related (OpenMAX - Open Media Acceleration). Not sure if that's the root or secondary cause/derived bug but it can be worked around by killing the mediaserver (killall mediaserver) or by using Temaseks camerarestart.apk (does actually the same). After that you have some attempts (surface initializations) again until it breaks once more. Usually you have around 3-4 surface initializations (starting 3-4 videos in YouTube app) before it happens. Sometimes more, sometimes less.

Logcat (YouTube app)::
[Galaxy S III Original Android Development] cba1986:
Glad to know that i am not the only one with this issue.
[Galaxy S III Original Android Development] Olioaglio:
Exactly. 0x80001000 is a memory allocation error. I hate it!
[Galaxy S III Original Android Development] Gassity:
Would there be any update!!?? Tired of this laggy hell!! Have to rebot million times a day, cuz my phone just freezes all the time!

It's 100% related to kernel.

Wanted to reflash any other, but it doesn't boot lol) even with ext4.
[Galaxy S III Original Android Development] Scarface1991:
For me actually it's the opposite. SlimKat runs with this Kernel very smooth. While I experienced problems with other Kernels like Music Stuttering when the screen is off, this kernel works just fine for me.

But yeah an Update would be nice, since there were a lot of changes in the zzmove governor for example.
[Galaxy S III Original Android Development] Darkened_Sky:
rather think it's 100% related to you. why else are you the only one complaining about this kind of problems. probably some false settings (UV, OC...), rogue apps or whatever.

and maybe read the first page. Then you know why your phone doesn't boot after changing kernel. (*just a tiny hint*

it is written in red

)

and in future please be more polite and respectful. You are responsible yourself for what you are flashing on your phone.
[Galaxy S III Original Android Development] Mostafa Wael:
Hey guys,

I just want to report that my mobile sometimes does not connect to any unsaved wifi.

I mean if there is a wifi router and i know the password and it is my first time to gain access to it, i tap on the connect button and then it says "Authenticating..." and after that "saved/secured with bla bla" and as if i did not connect at all.

Is anybody having same issue?

Thanks!.

And by the way this kernel is smooth like hell

DevilQ is amazing
[Galaxy S III Original Android Development] iceman0826:
hw and hw+ no longer works with this kernel

is it me or that i find this kernel the root cause of some videos to not decode with HW or HW+ using MX player?
[Galaxy S III Original Android Development] cba1986:
HW and HW+ modes are working fine using this kernel + Temasek V66
[Galaxy S III Original Android Development] k-semler:
HW+ mode works fine for me.
[Galaxy S III Original Android Development] Gassity:
Lol) let's wait to another Darkened_Sky's "helpful" answer in chasing of "thank you'd"
[Galaxy S III Original Android Development] Mostafa Wael:
Please stop being

rude!!!
[Galaxy S III Original Android Development] tetakpatak:
Guys, please calm down.

Who doesn't like this kernel please don't use it anymore.

Please don't spam this thread with ETA questions anymore, check XDA rules, it is forbidden!

tetakpatalked from Nexus 7
[Galaxy S III Original Android Development] iceman0826:
hmm. maybe i'm missing out some important details like what formats does HW+ or HW supports :D, but another question does HW decodes videos @ 10-20fps? i'm experiencing some lag issues when using HW decode on some videos of mine, HW+ doesn't work for me at all or maybe i need some videos to be converted at proper formats for HW+ decode.?

---------- Post added at 07:11 PM ---------- Previous post was at 06:46 PM ----------

UPDATE: on my problems and whining hehe :D

problem solved i can play videos using HW+ decode, my bad i forgot to update the codec my goodness http://xdaforums.com/apps/mx-player/mx-player-custom-codec-dts-support-t2156254

it's not kernel that caused it, it's my lack of information that caused it hehe..:D

devil kernel still rocks :good: looking forward for updates (also devil tool) hope it does have more options like in stweaks or much better than boeffla manager hehe
[Galaxy S III Original Android Development] DualJoe:
Anyone tried a different kernel yet to see if it's a kernel related bug? I've seen users on AGNi complaining about that as well but none on boeffla so far.
[Galaxy S III Original Android Development] Olioaglio:
Think it might work with Boeffla.
[Galaxy S III Original Android Development] DualJoe:
[MENTION=420407]Olioaglio[/MENTION]:

Are you still having these issues with AGNi pureCM 2.7.6? The kernel should be more updated (CM kernel updates) than current Devil release.

Are you using Xposed/Xprivacy?
[Galaxy S III Original Android Development] Olioaglio:
No, AGNi 2.7.6 kernel seems to have ironed out the problems. I'm still on f2fs on all partitions. Governor wise I'm using zzmoove 0.8 with enhanced profile. I suggest you to try it yourself. As you can leave your partitions f2fs it's not that big deal to try. But be aware that you have to dirty flash your rom again after flashing AGNi kernel, otherwise you are running into bootloop. It's something about different init as far as I remember. Sorry devil for OT hijacking this thread, but I must admit that I'm quite happy with AGNi ATM. It's giving me f2fs, less memory problems, remarkable better battery and good overall performance.

[MENTION=4293606]DualJoe[/MENTION]: Let me know your results/opinion...

Cheers, Olioaglio
[Galaxy S III Original Android Development] DerTeufel1980:
No problem for me. There'll be the point when I'll have more time again :)

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] Olioaglio:
Mmmh... I smell the real xda spirit :P
[Galaxy S III Original Android Development] DualJoe:
Same on AGNi kernel. I could play some more videos with YouTube though until the backend crashed. But that's just a minor advantage...

As i'm addicted to Perseus master profile i'm back on devil kernel. :good:
[Galaxy S III Original Android Development] DerTeufel1980:
That's interesting.... I thought it was related to my Linux 3.4 changes... Seems like it is not....

Can you please delete everything within /data/cfw and then reboot. Do the files get copied back to /data/cfw? And more interestingly, does that fix the problem?

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] Olioaglio:
I'm not that kind of pro, but i did some research on myself done time ago. it turned out, that the error is caused by some kind of memory allocation / buffer failure (0x80001000,1) of omx decoder. I also posted a logcat in this thread some time ago. May i pass some information on what i found related to this?

http://code.google.com/p/android/issues/detail?id=37769

Olioaglio

---------- Post added at 10:20 AM ---------- Previous post was at 10:12 AM ----------

Yes, i should have mentioned :-/ Missing master sequence is one of the real downsides of AGNi kernel. I love master sequence. But the playback problems are (still there) very rare for me since using the kernel and i could always get it back to work with temaseks camera restart tool (btw, what does it actually do?). Maybe this is because it resets some buffer also? I'd be very happy if [MENTION=4196889]DerTeufel1980[/MENTION] would jump in again and tries to iron out this problem.

Cheers, Olioaglio