yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] DerTeufel1980:
What are you missing now?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] fjfcb:
And why don't you move to omni?
[Galaxy S III Original Android Development] mhb92:
max frequency on cpu and some others... and sometimes i cant use root uninstallers to uninstall some sys apps

and for this i have to install rom uninstall whatever i want and then flash kernel....
[Galaxy S III Original Android Development] spoonymoon:
you are not very specific..

but is as simple as it gets>

factory reset+system format

flash your primary rom+gapps then flash devil 1.53 then flash dual recovery , let it boot up, install devil config 1.0 app

reboot and voila new options is available in cwm - format second system, install second rom + gapps reboot :laugh:

*in devilconfig you can set which rom to boot into or you can choose it from recovery*

regards :)

available apps for kernel settings is:

Devil config

trickster

pimp my rom

android tuner

and properly more..?
[Galaxy S III Original Android Development] mhb92:
ok..this is what i do...except that i dont install dual recovery... is this part needed to be done..? cause i dont use second rom...
[Galaxy S III Original Android Development] DerTeufel1980:
if also just noticed, that using omni initramfs for cm is breaking root. maybe it's the same for you. i noticed it, because deviltools was missing some options :D
[Galaxy S III Original Android Development] spoonymoon:
cm 11 sometimes looses root just flash latest super su then its always working again >

http://xdaforums.com/showthread.php?t=1538053&page=102

EDIT: no dual recovery isent needed for one rom !!

EDIT: remember to set it to always allow in su app, isent working else!
[Galaxy S III Original Android Development] mhb92:
this is what i was waiting to hear...ok cause a lot of people say that there is no problem with root and others...

but as it seems there is a problem :P gonna try installing su after got a broken su

i am pretty sure its gonna work ! thx again for ur work dev :)
[Galaxy S III Original Android Development] DerTeufel1980:
I'll try to push a fixed version later, which doesn't break root anymore.

Could you try thememanager please? It was force closing for me with omni initramfs

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] mhb92:
Well at moments I get FCS of theme provider I think without reason :pp

Also I installed su from recovery and yet I don't have root... :/

I use philz touch by the way
[Galaxy S III Original Android Development] saminem:
we should CERTAINLY create nandroid backup and restore to sec. file system?

and create the secondary system partition on dual boot menu doesn't work for me!! ( yesterday i used googy max dual kernel), made secondary partition at the same time ?
[Galaxy S III Original Android Development] DerTeufel1980:
Which kernel version are you using? Did this happen with older cm versions as well?

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] jagdtigger:
It worked flawlessly with CM10.2...

Kernel versin:

Devil2-2.3.2-i9300-DUAL-20140102

For now i reverted back to tho original CM kernel...
[Galaxy S III Original Android Development] DerTeufel1980:
Please try the one from here:

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

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] jagdtigger:
This one works, thanks :) . I thought the first post always contains the newest version...
[Galaxy S III Original Android Development] DerTeufel1980:
No, I am sorry. I was running out of time lately....

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] jagdtigger:
No need to apologize :) , you making this good kernel in your free time. Its not a big deal to dig up this this thread for the newest :D .
[Galaxy S III Original Android Development] Scarface1991:
Can anyone confirm that on the SlimKat ROM the Equalizer inside the Devil Config App has no effect on the Sound?
[Galaxy S III Original Android Development] Mostafa Wael:
I can confirm that it does not have any effect on Archidroid 2.4 and up and slimkat and CM11 "linaro/sabermod" modded.

Btw if it is so important to know the ROM causing the issue then i will post link to the modded CM11 i am using later "you can try it, it's awesome!!!" :D
[Galaxy S III Original Android Development] kp.nikhil:
i have the same problem on c rom.. im using devil, 3.4_0.1.4

Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
You are having force close of phone app?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] kp.nikhil:
yes.. com.android.phone has stopped

Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
That's strange. The other one reported the force close to be fixed by using the kernel version you are using, too.

I'll check cm for changes. Can you please also get me a logcat

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] kp.nikhil:
here you go
[Galaxy S III Original Android Development] Andro Boy:
I had the same problem just 2 days ago when i was fresh installing temasek v66 (latest one) as second ROM using the older kernel Devil3.4_0.1.0-20140209

and it did give me the same force close issue , but when i flashed the latest one Devil3.4_0.1.4-20140316 it did work just fine :) ....

but their is a thing in this version is that when booting the first ROM (which is archi 1.7.13) it takes some time hanging on the devil logo, then it shows the boot animation and boot up normally . but the waiting time is getting really annoying when u need to restart more than once in a time, so i always use hotboot to restart .

although when using AGNi kernel it boot up flawlessly without any wait .

Thanks,,,

---------- Post added at 09:50 AM ---------- Previous post was at 09:35 AM ----------

Hi, [MENTION=4196889]DerTeufel1980[/MENTION]

could u consider in your to-do list adding UMS option like in beoflla or AGNi kernels .

Thanks,,,
[Galaxy S III Original Android Development] DerTeufel1980:
What's this ums option?

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] Moster2:
I think he is talking about usb mass storage, another way to connect the storage to the PC.
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, ums = usb storage related, but isn't it rom setting

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] Moster2:
I think yes. Boeffla describes that the app unmounts the extSdCard and then remounts it with the ums protocol. So I guess this is rather a request for your config app
[Galaxy S III Original Android Development] leviatus:
Would like to check for those mentioning the camera issue, does it happen on the latest slimkat weekly? Seeing that the camera fix is included in it

Somewhat confused with regards to reflashing a rom on f2fs, the usual procedure works? Eg backup, wipe system/data then flash rom

Noticed that Agni has a modified TWRP for f2fs, has any1 tried using that?

Sorry for all the questions, don't seem to find much info regarding f2fs
[Galaxy S III Original Android Development] DualJoe:
The 'OMX/AVC Decoder' memory leak seems to be caused by f2fs. I can trigger the bug by formatting at least one partition to f2fs (eg. /cache). And only if all partitions are ext4 (or not f2fs) the memory leak is absent.

I test the memory leak by YouTube app. If affected, i can barely start 5-10 videos until it only throws a text message ("video playback problem") on every video.

Migrating back to ext4 can be a pain though. Devil recovery couldn't format /cache at all back to ext4 (probably wasn't able to unmount it). It also killed a partition once leaving it raw or something resulting in rom and recovery crashing immediately after bootup so i had to odin flash a stock recovery to fix that. AGNi TWRP has bugs as well and is not always straight forward either but it could at least format /cache again so i was back on track.

If anyone else experiencing the same please leave some feedback. A second confirmation regarding that fix would be highly appreciated.
[Galaxy S III Original Android Development] Andro Boy:
in some ROMs it's implemented in it like temasek ROM ,

but not all the ROMs have it .

so it can be really helpful to be included in the config app .
[Galaxy S III Original Android Development] Andro Boy:
Hi,

i made a test to see this YouTube video playing issue , first i don't use the official one so i used OGYouTube and i ran through a lot of videos and nothing did happen , actually they all worked without any problem , second i downloaded the official one and their wasn't anything wrong too !!

---------- Post added at 04:38 AM ---------- Previous post was at 04:31 AM ----------

The only problem i have is with any cm ROM , the camera app would work just fine at first but after some changes in options or taking pics. with different mode like 360 or 180 or even changing to video sometimes it crashes and when i open the app again it shows me this message "could not launch camera" or something like that .

I don't know if this is a ROM or kernel prob. but it was always their from my first try to cm 10.2 camera an so on with different kernels too .
[Galaxy S III Original Android Development] Mostafa Wael:
Are you running on f2fs or normal ext4? I think it seems that the video playback issue is conflicting with f2fs formatted partitions. I guess if AndroBoy is running on ext4, then it is a crystal clear confirmation that it is related to f2fs!!! :(
[Galaxy S III Original Android Development] DaReDeViL:
I do face similar camera problems on cm while on ext4 partitions ...

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] DerTeufel1980:
Thank you for your reply. I also thought similar. Too bad we don't know the reason then.

Gesendet von meinem JY-G4 mit Tapatalk
[Galaxy S III Original Android Development] DaReDeViL:
I forgot to mention that I don't have YouTube issue.

There a thing I did to reduce camera crashes on cm: I reverted to stock memset and used linaro gcc 4.7.4

I am pretty sure it's a buffer issue or memory addressing issue.

I also remember that I once played with granularity values and faced a lot of problems related to video playback and calling problems ...

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] DerTeufel1980:
Ah yes. I had seen you reverted It, but I didn't remember. Thanks for reminding. I am gonna try It.

Gesendet von meinem JY-G4 mit Tapatalk
[Galaxy S III Original Android Development] DualJoe:
Yep, but that's a different story. The camera needs much more interfaces/proprietary functions than just the h/w decoder. The device specific low level Exynos stuff is probably still a mess and the root cause here.
[Galaxy S III Original Android Development] Mostafa Wael:
So can we say that the reason is the use of GCC 4.8.3? Will reverting to 4.7.4 help fixing this nasty issue?

At least can we say that f2fs is not guilty anymore? :D

I am not a pro, but i am just trying to clarify it more to other people, like me :) :angel:
[Galaxy S III Original Android Development] DerTeufel1980:
We're also just guessing here. as soon as I find some time, I'll build one with older gcc

Gesendet von meinem JY-G4 mit Tapatalk
[Galaxy S III Original Android Development] DualJoe:
F2FS probably never was guilty. It just triggers an old and nasty bug that the AOSP scene suffers from for a long time: The Exynos driver implementations. It just gets kicked from one corner to the other. Googy is probably right by "kicking the box", tweaking something here and there in memory management or in compiler settings and with a little luck it will be out of sight.

Look at all the threads where people tell how to fix the camera problem. Its hilarious to see how this comes up over and over again. Its all useless crap. It can't be fixed this way. The drivers haven't been touched since the original maintainers left the scene and that's why the camera and all other h/w related issues (including h/w video playback) are still in the same state for months. That's the main issue and its unknown why and under what circumstances they produce side effects.

The big guys are still "on break" and its unsure if they will ever come back. Though they are still listed as official I9300 CM maintainers (Codeworx, xplodwild, MmegaMac). Codeworx Twitter doesn't look too unpromising though. The day they come back, the problems will go.
[Galaxy S III Original Android Development] JustArchi:
To be honest, working on exynos bugs for SGS3, and in general whole smdk4412 family is currently a big waste of time. Xplodwild works on Omni project whole the time, and even if codeworkx will come back, he probably won't spend time on SGS3. Think how much time it required to fix nasty after-call-battery-drain, and now think how much time it will require to fix these.
[Galaxy S III Original Android Development] Andro Boy:
Actually iam not... I am using f2fs.

By the way i did try it too on AGNi kernel and everything is ok.

[MENTION=4196889]DerTeufel1980[/MENTION] will yeah i am facing this camera issue in the second ROM as it is formatted as ext4 ,though I didn't test it on f2fs as first ROM .
[Galaxy S III Original Android Development] Mostafa Wael:
Well i suggest [MENTION=4196889]DerTeufel1980[/MENTION] to build one with the older GCC. I will not personally try it "i am in exams!!!" But it is just a suggestion! Feel free to ignore it if you guys are 100% sure that it is not Linaro 4.8.3 causing it!

And a big thanks to all of you guys for helping and trying to solve the problem :)

And of course welcome back [MENTION=4196889]DerTeufel1980[/MENTION] :D
[Galaxy S III Original Android Development] DaReDeViL:
Don't worry guys, camera problem is fixed in my last kernel. ;)

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] DaReDeViL:
[MENTION=4196889]DerTeufel1980[/MENTION] I'll PM you asap about what I discovered ! ;) it's all about linux mainline updates ...

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] Moster2:
Is it something that potentially also affects the stock cm kernel? Some people also report issues which I personally dont experience though.
[Galaxy S III Original Android Development] DaReDeViL:
Definitely YES !
[Galaxy S III Original Android Development] Iqbal Ansari:
Im running a dual boot setup but having issues with whatsapp,

primary rom is cm11 and secondary rom is sammy stock.

I flashed cm 11 and restored nandroid backup to secondary FS, but on second rom ie stock rom im not able to download media from whatsapp.
[Galaxy S III Original Android Development] cba1986:
Sorry wrong thread.
[Galaxy S III Original Android Development] JustArchi:
Tell me too! :D
[Galaxy S III Original Android Development] DaReDeViL:
I sent a PM to [MENTION=4196889]DerTeufel1980[/MENTION] but I'll resend it to you and lord boeffla and psnadna and yank555

Envoyé de mon GT-I9300 en utilisant Tapatalk
[Galaxy S III Original Android Development] Mostafa Wael:
Thank you [MENTION=1897326]googy_anas[/MENTION] you are the man.

You really showed us how close the s3 community is. One phone, One Family!!!

Thanks for fixing this issue.

I am really speechless. I can not describe what i saw!

It is more than being one family.

I wish i can flash a kernel published by all kernel devs :D :D

Also can anybody tell me how to fully return back to ext4?

My friend wants so i do not know why!!?

Anyways, thanks all devs!
[Galaxy S III Original Android Development] tetakpatak:
Yes, mate- just the same way, only inverted: format to ext4. Please check in my signature (visible if you read this with browser) N7100/Note 2 devil2 kernel dual boot faq thread, the procedure is just the same with your phone.

If you encounter any error messages, just reboot recovery and format again all back to ext4

tetakpatalked from Nexus 7
[Galaxy S III Original Android Development] cba1986:
[MENTION=4196889]DerTeufel1980[/MENTION] a 4.4.2 leaked ROM for gt-n8000 and the official 4.4.2 for n7100 are out

http://www.sammobile.com/forum/showthread.php?t=22057&p=95498#post95498

Could we use the MALI blobs from any of those devices?
[Galaxy S III Original Android Development] DerTeufel1980:
I think mali didn't change

Gesendet von meinem JY-G4 mit Tapatalk
[Galaxy S III Original Android Development] Iqbal Ansari:
Help please!

After trying to dual boot many times I'm having the same issue.

Primary Rom CM11 and secondary rom Stock 4.3. I'm flashing CM11 and restoring stock rom to secondary FS.

My issue is only on stock rom ie secondary rom is that I cant send or receive media in whatsapp and the pictures taken with stock camera cant be saved on memory card and gallery is force closing. I think the issue is secondary rom cannot read the memory card properly.

Any help will be appreciated.

Sorry if its the wrong place to ask this but I'm not getting a solution in the main thread. Somebody running the same setup as mine might help.
[Galaxy S III Original Android Development] Mostafa Wael:
Hey dominik,

I was wondering why isn't the f2fs project on galaxy s3, note 2 featured on xda portal like the Nexus 7 and the xperia devices?

I think it is working quite fine! 2x normal speed, no any unusual bug related to f2fs was detected.

:confused:
[Galaxy S III Original Android Development] DerTeufel1980:
I don't know. Maybe mine was the first one :p

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] Mostafa Wael:
Hehehe :D

I would like to know how is the project of porting 3.4 kernel to i9300?

The dev thread of the porting 3.4 kernel to i9300 has been too inactive for a long time.

Waiting for a new kernel build - my hands are itching me!!! ;) :) :)
[Galaxy S III Original Android Development] DaReDeViL:
I couldn't port 3.4 kernel by my self so I ported myself to 3.4 kernel (i9505) !!! :D :D :p

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S III Original Android Development] JustArchi:
Now THIS is a good idea, wait for me :D.
[Galaxy S III Original Android Development] Mostafa Wael:
Are you going to move to s4 and leave s3 Archi? :(

Or

Are you going to contribute in porting a 3.4 kernel fo s3? :)
[Galaxy S III Original Android Development] Elimn8r:
[MENTION=5161352]JustArchi[/MENTION]

Since you compile philz touch for i9300 now, any chance of getting a stock philz touch just with added f2fs support (ie. no dual boot options) so that we can still flash roms with aroma? :fingers-crossed:
[Galaxy S III Original Android Development] JustArchi:
Point me to the right commit and I'll consider. However even if I consider so, I'll still compile "two" versions of PhilZ recovery - one purely from Phil's sources, and one on steroids. I'm just helping Phil save some time, not making my own kanged fork of this awesome recovery.

Nah, I'm not going anywhere, Samsung is a piece of **** since KNOX till now :D.
[Galaxy S III Original Android Development] DerTeufel1980:
That's true. I am thinking about getting a jiayu device next time. Just waiting for them to release their sources.

Those chinese devices are cheap, fast and rooted by default :D

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] Scarface1991:
What do you think about the Oppo Find7a? Would be really awesome if one of you guys would get this device and build a Kernel for it :D
[Galaxy S III Original Android Development] iceman0826:
how about the newly announced one plus one? http://oneplus.net/ :fingers-crossed:
[Galaxy S III Original Android Development] DerTeufel1980:
There's jiayu store in my home town. They're official importing and selling the devices. They are in talk to jiayu china to release the source code of kernel and device tree, because I asked for it.

I don't know if oppo is releasing their sources, and if they aren't, I don't see a way to contact them.

That's really a nice device. Let's see how it performs, after somebody has gotten one

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] Scarface1991:
I was under the impression that Oppo is very developer friendly since they are supporting CyanogenMod on their flagship devices.
[Galaxy S III Original Android Development] DerTeufel1980:
Maybe. I didn't read anything about it. :)

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] drgreenth:
[MENTION=4196889]DerTeufel1980[/MENTION] can you add those googy findings about cm camera fix to next kernel, thanks!

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] DerTeufel1980:
The fix is, to revert every Linux update. That's not what I am going to do

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] Elimn8r:
[MENTION=4196889]DerTeufel1980[/MENTION] Thanks for this awesome kernel love f2fs and dualboot

Just a couple of things would it be possible to update the sound mods (ie. maybe something like googy-max)

Also Is ntfs support for usb-otg available with this kernel cause I can't seem to get it to work.

I even tried installing Paragon NTFS but wouldn't work with this kernel

If it isn't any chance of getting it in the next build?

Finally, any chance of getting Aroma installer roms working with dualboot?

Please don't feel any pressure, I know your probably busy, but I thought I might as well ask
[Galaxy S III Original Android Development] cba1986:
Really?

Well, that is a shame. Camera is almost unusable with your kernel using AOSP. In stock the camera presents some lags but it is still usable in AOSP crash when you open the camera app.
[Galaxy S III Original Android Development] DerTeufel1980:
I just have seen the kernel sources, but this device also isn't cheap. You can get a jiayu octacore device for 200$

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
There aren't any /much sound mod changes, which I am missing (afaik).

Ntfs isn't working. I always forget to enable the driver... Sorry. I hope next time.

Aroma roms should be working, it's just a warning, because I can't try all of them

Gesendet von meinem T0LTE mit Tapatalk 2
[Galaxy S III Original Android Development] coolhof:
I dont get it.

I have Jb4.3 as the first rom and the last CyanogenMod 11 Nightlies as second and no problems with the camera.

Playback with youtube gives some problems.

For the rest I can enjoy both roms for daily use.

Send From A Devil3 - f2fs - Dualboot Jb4.3/cm11 Powered Machine
[Galaxy S III Original Android Development] Elimn8r:
I just meant the profiles for the eq and maybe 2 different sound mods like googy etc

I tried revolutionary s5 v 3.0 (Aroma) many times (as primary rom) but couldn't get it to work (didn't boot, as if Nothing had been written to system)

Just tried now as Secondary rom and it seemed to work, booted up but the rom was wrecked (just status bar with black screen, couldn't even go to setting from the status bar shortcut):silly::silly::silly:

Just remember N)ot T)o F)orget S)upport for NTFS ;)
[Galaxy S III Original Android Development] zodiaxe66:
Check out "oneplus one" its born with cm11s and is very cheap.

It looks and feel awesome,think it's going to be my next phone and I love the their promotion.

Oppo find 7 is a great phone too. Looking forward to its release..

Have a nice day:o
[Galaxy S III Original Android Development] DaReDeViL:
Actually it's not reverting every Linux update, but only reverting the memory management changes introduced by some linux patches. All the other patches are kept in.

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks. I got you wrong in the pm

Gesendet von meinem T0LTE mit Tapatalk 2