yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Teura:
This morning, instead of waking to alarm as I should, I woke up to Omnirom logo. Luckily only 5 minutes late, and it wasn't even important for me to wake up at this time. But, problem here is that it won't boot to system, no matter how long I wait.

I've got Omnirom nightly from 9th and Devil kernel 3.4 installed, and that combination has been working fine for this long, but now I can't even boot the phone. Thus, logcat. Can someone tell if it's kernel or rom related?

I had to zip the logcat, as it starts with ~200 kB, and then suddenly jumps ~900 kB (800kB limit for .txt). Then a small delay, and another 900 kB.

E: Restoring /system from my backup after updating to 9th nightly and 3.4 made the phone able to boot up again. But I'd still like to know what caused the inability to boot.
[Galaxy S III Original Android Development] gregdeberg:
Hello :)

Do you know if an aroma script exists to convert ext4 to F2FS ?

Thank you :)
[Galaxy S III Original Android Development] JustArchi:
https://github.com/JustArchi/ArchiD...F/com/google/android/aroma/exec/adreformat.sh

Example:

adreformat.sh /system f2fs
[Galaxy S III Original Android Development] gregdeberg:
Thank you !

is it works for all android devices or just S3 ?

Thank you :)
[Galaxy S III Original Android Development] JustArchi:
It should work on all devices as long as:

a) You have tool available for reformatting to specific filesystem

b) You modify paths to proper ones in the script itself (on the top)
[Galaxy S III Original Android Development] gregdeberg:
Ok thank you but it seems to be too difficult for me...
[Galaxy S III Original Android Development] Marvis21:
Just to mention, i have had a strange freeze yesterday (maybe just a hiccup in space :confused:). I have set a alarm for a little sleep and woke up by a strange short noise. Looking at the time i saw it was 2 min before the alarm should ring. Looking at the phone i found it with black screen, not waking up but it vibrates by pressing the menu or the back key. Hard restart needet to make it responsible. Couldn't reproduce, so i don't know what was the reason. 5 new alarms works fine. I am on Temasek V 45.1, Devil 3 and f2fs.
[Galaxy S III Original Android Development] brouwerchris:
Since a week on SlimKat 2.8 with Devil3.4 kernel all on f2fs,all was fine till this morning.As allways I charged my S3 during the night,in the morning take my phone to work with full battery.Today no green light to indicate fully charged,after toggling powerbutton Devil boot image on screen,wait one minute,nothing happens.Long press power toggle to reboot,phone reboots normal.No issues since.:confused:
[Galaxy S III Original Android Development] gilliardmelo:
Well.. everything is running well. I was afraid to format without success. Today i press YES then an option to choose

the FS appears. :laugh::good:

Thank you everybody that reply my questions.
[Galaxy S III Original Android Development] Choristav:
Would you read a tiny PM about something huge for some of us?

It's about UMS.

Thank you very much.
[Galaxy S III Original Android Development] Mostafa Wael:
i guess our great dev is busy working on something BIG!!!!!! may be some merges of the 3.4 kernel branch :D

i wish him best wishes with porting the 3.4 kernel to our beloved S3 :)

good luck dominik. keep it up!
[Galaxy S III Original Android Development] cba1986:
Somebody has news about [MENTION=4196889]DerTeufel1980[/MENTION]?

Is he alright?
[Galaxy S III Original Android Development] spoonymoon:
Yes hope soo too. ..

But if you ask me he's really disapointed over the few donations vs. He's over one month hard work every evening to make this new filesystem/recovery!

I'm pretty sure he really thought it at least would give back money wise somehow equal to work! But it diden't it seems :rolleyes:

When this system is bug free at some point, it easily can be ported to most other devices etc. .think about it, it's no less than a genius invention witch makes our phones fly to say the least :cool:

Hell it should be samsung/android community making this, not Devil alone - he's no less than a genius

Like fat32/ntsc filesystem in windows

There's only one thing to say. ...hats off :victory:

:)
[Galaxy S III Original Android Development] xeizo:
Why shouldn't he be? I guess he's just busy with life, xda tend to be a little too intensive at times. Remember this is a site for hobbyists even if some are obviously very skilled :)
[Galaxy S III Original Android Development] cba1986:
Because he didn't post in a while.
[Galaxy S III Original Android Development] Gold_Diesel:
He replied 3 days ago in a different device section, he's fine :)
[Galaxy S III Original Android Development] xeizo:
Oh, I see, well this is the internet as our governments love it too:

Last ten posts in the Note 2 forum ...

He will be back! :D
[Galaxy S III Original Android Development] markey97:
I'm sure [MENTION=4196889]DerTeufel1980[/MENTION] is alright and I think I also know what he's doing... hehe :good:;)

The same thing I do since some evenings...

But i don't want to reveal too much...or to make you think about some stuff...

Just wait and see.:D
[Galaxy S III Original Android Development] Unuce:
f2fs problem

i get problem with f2fs..

when i do all and tru to boot up i get bootloop :(

now i just tried to clen install rom and i get something abotu encrypting eror :(

what should i do?
[Galaxy S III Original Android Development] gilliardmelo:
Hey dude, I was passing by the same trouble. Try it:

Flash an original recovery

Use an option: Wipe Format/Data (in this moment, your /data will be formatted and this error message dissapears)

Flash a custom recovery

Follow the steps to format as f2fs again

Don't worry, it is totaly reversible.
[Galaxy S III Original Android Development] Unuce:
i do not use newest kernel,all gone well now :))

other question : can i now install philz recovery and boeffla kernel?
[Galaxy S III Original Android Development] PedroJuuu:
Camera is not working on Revolution Remix after minutes/hours of use :S

With stock kernel it does not happen

Any ideas?

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] KMino:
If not using the new file system, yes.
[Galaxy S III Original Android Development] Olioaglio:
No Boeffla and/or Philz when using f2fs. Neither is compatible with f2fs

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

if i want to install a new ROM but it is not f2fs friendly, can i flash it normally, then after flashing i can custom backup the /system then format it back to f2fs then restore the custom backup i did?

thank you!
[Galaxy S III Original Android Development] Unuce:
Thx:)

How can i configure kernel?

Sent from my GT-I9300 using Xparent Blue Tapatalk 2
[Galaxy S III Original Android Development] Olioaglio:
Yes.
[Galaxy S III Original Android Development] pippoaacc:
Big problem with new recovery installing omni as 2nd rom. I formatted system before updaing the rom, but recovery installed the rom without camera for two times in a row. In addition to this, flashing supersu zip didn't work in that I simply didn't have root at all. I reverted back to previous devil recovery, reflashed the rom and now all it's ok. Any ideas?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Original Android Development] BradleyR2010:
Anyone else getting random crashes with the 3.4 Kernel showing weird lines on the screen only fixed with a reboot?

also the screen responds way to slow when pushing the power button.

Im all stock 4.3 its driving me crazy :P
[Galaxy S III Original Android Development] xeizo:
No probs with weird lines using NA8 stock as system 1 here, but stock 4.3 is slightly laggy, if you want speed like fast and snappy why don't you try a AOSP Kit Kat rom like ie our rom (SmartDroid AOSP) .. very much faster, goes well with someone who appreciates the speed of f2fs he probably wants the rom itself to be speedy as well ;)

Btw, I do use you kernel manager, really like it! :p
[Galaxy S III Original Android Development] Gold_Diesel:
I'm using stock 4.3 (MK6 w/ f2fs) with 3.4 kernel and I seem to be getting random reboots. I thought it was my undervolt settings but I'm beginning to think that this is not the case.

Anybody else getting issues?

Edit: It was just the undervolt settings, no random reboots now.
[Galaxy S III Original Android Development] BradleyR2010:
I was reading the Note 2 Thread and some user are facing the same so its probably something in the kernel

http://xdaforums.com/showpost.php?p=50321965&postcount=7738
[Galaxy S III Original Android Development] _polimorph_:
I had this also. There were paralel vertical purple lines on the screen and of course the system became unresponsive. I was on temasek's v46 and Devil3.4.
[Galaxy S III Original Android Development] Olioaglio:
No probs here yet.
[Galaxy S III Original Android Development] Gold_Diesel:
I haven't had any screen issues on stock 4.3, have you tried a different ROM or anything like that?
[Galaxy S III Original Android Development] DualJoe:
In case i want to patch the rom zip for f2fs how exactly is it done? Can i just replace 'ext4' with 'f2fs'?

format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0", "/system");
format("f2fs", "EMMC", "/dev/block/mmcblk0p9", "0", "/system");

Edit:

Found this...

So i did it this way (i prefer 'mkfs' to 'rm -rf'). It can be faster than 'custom backup/restore method' if you download Roms to PC first anyway. Rom.zip doesn't need new signatures either so changes can be done quite fast.

run_program("/sbin/mkfs.f2fs", "/dev/block/mmcblk0p9");
run_program("/sbin/mount", "-t", "f2fs", "/dev/block/mmcblk0p9", "/system");

I've noticed that the addon.d backup part does work nevertheless with ext4 (even though its f2fs). Its invoked even before i mount it f2fs. I guess the recovery mounts /system f2fs manually before starting a rom install. Otherwise i can't explain why it works anyway (and it does work indeed).

mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
[Galaxy S III Original Android Development] granets:
am I the only one that can't ,mount the external SD card with this recovery??? Is there any solution to that? I am able to mount and use my external SD card with all recoveries but this one
[Galaxy S III Original Android Development] S1ay3r666:
Great kernel but i need some good battery settings.

Can someone please share his battery profile?

I woul appreciate it :)

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] spoonymoon:
Had this also, just format it in cwm/windows, mine worked after that, mounted fine afterwards .

About these vertical lines, and system crash afterwards I have it to but I'm on normal ext4 formated sd's, and with aosb 1.30 rom, don't even have newest recovery (f2fs one) but the previous, and then on new 4.01 kernel

Never seen this before 4.01..

Edit: i wonder if our great dev is coming back to this thread? sure hope soo :)
[Galaxy S III Original Android Development] granets:
not an option. recently formated my 32!!! GB sd card full of music, not going to do it again. I was just wondering how come philz recovery can mount my sdcard, cwm can mount it too and this recovery, based on it, can't...
[Galaxy S III Original Android Development] pippoaacc:
Still no solution. I can't use new recovery. Any idea?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Original Android Development] Robin2:
Is there a way to save a profile of settings for the Devil config app? After updating a rom and reflashing the kernel, all settings reset.
[Galaxy S III Original Android Development] S1ay3r666:
Yes settings - > save or settings - > load ;)
[Galaxy S III Original Android Development] Robin2:
I don't have that option.

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] S1ay3r666:
Mmhh i use deviltool v1.1.2
[Galaxy S III Original Android Development] Robin2:
Where can I find that app? I use Devil Kernel Manager from Play Store.

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] Moster2:
The app in the store is not by DerTeufel, take this one : http://xdaforums.com/showthread.php?p=41346443#post41346443
[Galaxy S III Original Android Development] cloudx720:
Looks like the dev has left us in the cold? :(
[Galaxy S III Original Android Development] Gold_Diesel:
He's either busy with Real life stuff or he's working hard on this kernel!
[Galaxy S III Original Android Development] Jpbest:
I've done everything that appears in the tutorial, but when I format it doesn't give me the option of reformating to f2s

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] shaarky:
You don't have then latest Devil2 recovery
[Galaxy S III Original Android Development] FadeFx:
Or he is working on note2 kernel currently and will look back here later

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] cba1986:
Let's hope!
[Galaxy S III Original Android Development] BradleyR2010:
DKM will have profiles soon, I just got busy at work and got distracted creating an extension for muzei :p
[Galaxy S III Original Android Development] Velogr1992:
hey guys ,

i ve set

scheduler :row

zwap 40% ->331mb

swappiness to 130%

do u think it is a good option or you have any better suggestions?

thx
[Galaxy S III Original Android Development] drgreenth:
I think maximum swappiness for linux kernel is 100% and using such a high value may affect overall performance. I would recommend something around 60-70%

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Original Android Development] _Beni_:
since my last post im running on SlimKat with DevilKernel. No problems with the kernel.

Couldn't block the recovery formating /system? i always must do a backup, format to f2fs and then restore.

btw, could you update this post to version E, it still redirect to C?

http://xdaforums.com/showpost.php?p=49979584&postcount=1116

Is it normal when my phone is off and i'm going to charge it, it hangs at the devil kernel logo?
[Galaxy S III Original Android Development] DualJoe:
Yes, it's a known bug.
[Galaxy S III Original Android Development] cba1986:
[MENTION=4196889]DerTeufel1980[/MENTION] please don't take this as a rush. But i wonder if there is any news on the i9300 front.

Thanks!
[Galaxy S III Original Android Development] tetakpatak:
Hey guys, leave him alone. What if he went for a vacation week to ski with the family? I wish he has :)
[Galaxy S III Original Android Development] cba1986:
Nobody is rushing [MENTION=4196889]DerTeufel1980[/MENTION] i am just asking. It's only that It's been couple of weeks since the last update or even a word from him, in this thread at least.
[Galaxy S III Original Android Development] tetakpatak:
He was never someone of big words. Besides, he likes to see people educate themselves.
[Galaxy S III Original Android Development] xeizo:
Theres still plenty of usable and unique stuff in this thread, f2fs, Devils dual boot recovery, his almost 3.4 kernel etc etc it's a very up to date thread even if he doesn't update it at the moment :D
[Galaxy S III Original Android Development] tetakpatak:
It will need next update when Android 4.5 or 5.0 gets released ;)
[Galaxy S III Original Android Development] FistFull95:
EDIT: Somehow the MTP fixed itself I guess. Though I have an even bigger problem now lol. Whenever I install something to either the first FS or the second FS, I think it gets installed to both, thus corrupting at least one of the FSs. Am I doing something wrong?
[Galaxy S III Original Android Development] cloudx720:
He used to reply a lot more in this thread just saying...
[Galaxy S III Original Android Development] pippoaacc:
Probably a noob question, but is there a way to exchange 1st and 2nd rom w/out nandroid?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Original Android Development] shaarky:
I don't think so as the second ROM is stored in directory .secondrom while the primary ROM is in different partitions already and mounted. But it's my personal guess only.
[Galaxy S III Original Android Development] metalgearhathaway:
Hi chaps, new to the S3 and this kernel, I have downloaded the latest kernel Devil2-2.3.2-i9300-DUAL-20140102 and devil tools 1.1.2. When I run devil tools it crashes immediately. Am I using the right version of DT?

I am running latest Carbon nightly kitkat rom btw.

Thanks in advance!

EDIT: Rebooting after installing app, seems important! Working now.

EDIT 2: Wow, kernel runs very smoothly! I have quickly got my settings together with some mild overclocking and the results are pleasing performance wise, both blistering in benchmarking and more importantly UI transitions are impressively smooth!

My test setup for the next 24 hours (to test stability and battery resilience - I am only 48 hours into S3 ownership):

Overclocking Details:

CPU: 1600mhz - no volt changes

GPU max 600mhz - voltage @ 600mhz = 1152500

GPU stepping control:

160mhz up @80%

266mhz up @90% down @45%

350mhz up @90% down @65%

440mhz up @90% down @70%

600mhz down @65%

Keeping devil gov in place, seems good immediately and I will try ROW as my IO as it was default, but I normally prefer cfq, but if it is good for the OP then it is certainly worth my time testing!

Many thanks for providing a nice alternative to the boeffla based kernels :) :good:
[Galaxy S III Original Android Development] Mostafa Wael:
Hey guys,

Can i use cyandelta to update my CM11?

I am using f2fs filesystem with devil3. kernel

I am not using dualboot

Also i saw recently that CyanogenMod has made some changes to the initramfs, so is it safe to flash the latest nightly along with the latest devil kernel?

Thank you!
[Galaxy S III Original Android Development] duttyend:
CM11 nightly incompatibility (March 4th and on)

Hi, just wanted to let you know that something has changed in CM11 nightlies from March 04 on, which makes them incompatible with custom kernels. I read that Boeffla kernel has been fixed by its creator who adjusted ramdisk or something in that direction.

It would be awesome if DerTeufel could fix our favorite kernel :good:
[Galaxy S III Original Android Development] spoonymoon:
Yes it sure would , be he has left i9300 thread

He got dissapointed, and left it seems !

We all miss him. ..and hope he's ok

Thanks for all your tremendous work through time Der Teufel :)
[Galaxy S III Original Android Development] metalgearhathaway:
Maybe just maybe he may fancy making one final revision for us? Such a great kernel would be a pity for it to become obsolete :(

Sent from my GT-I9300
[Galaxy S III Original Android Development] Choristav:
Why are you even saying things you have no idea about?

He's online right now browsing through PMs. I'm pretty sure he's just busy.
[Galaxy S III Original Android Development] cloudx720:
Don't we deserve an answer from Der Teufel? IMO yes we do at least some glimmer of hope...
[Galaxy S III Original Android Development] Andr3y29:
PM him. Go on another thread where he posts (Galaxy Note II I think) and let him know you want him here. Or learn about developing, take the Perseus source or if this is available on GitHub take this. Or just let him alone. He is a man like the others. Not a robot. He has his own life. If he sold his S3 that's it. I really like this kernel, but that's it. If it works now, and you like it, then use it so. I am using the original Perseus which has not been updated since the first half of 2013 with 4,1 for battery and it works. If I would discovered NxTGeN, I wouldn't even thought of a ROM under 4.3. Let the guy alone. He has his own life and he does whatever he wants with it. He is active on other threads, so he is alive. Just get over his absence.
[Galaxy S III Original Android Development] Gold_Diesel:
He doesn't actually have a S3, he has the Note II but the kernels are literally almost the same so developing for one = developing for the other. If he was stopping developing this kernel he wouldn't have spent the time trying to port Linux kernel 3.4 code into this kernel and he would've announced that he's stopping development not just stop posting.

If he was developing the kernel in secret he would be asking people about bugs so, I'm afraid to say, I don't think he is developing currently.

I think he's taking a break, respect that and please don't make rude accusations. Nobody wants to put in the immense time and effort for people who don't appreciate the hard work.
[Galaxy S III Original Android Development] Andr3y29:
That's what I actually wanted to say.
[Galaxy S III Original Android Development] cloudx720:
Who's made rude accusations? I just think he should atleast say something, anything...:(
[Galaxy S III Original Android Development] maxq1:
so sad to see this supposed to be dev thread turn into a "where's the dev / post your whine/s here" forum. devs share their work on an as-is basis (for that alone, we mere mortals should be thankful enough!) and are no way obliged to update it and say "hi" from time to time on the forum for our convenience or interest, regardless if you have donated to the dev or not.

on this note, i think a cleanup is in order, mods..
[Galaxy S III Original Android Development] cba1986:
Nobody is whining. Is that it is just odd that [MENTION=4196889]DerTeufel1980[/MENTION] went from posting 4 update in a row to not post a anything in a almost a month.
[Galaxy S III Original Android Development] FadeFx:
It is not the first time he left the thread alone for a while, thats how he works. Once the note2 kernel got the stuff he plans to give it, he will be back to port the stuff here.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] mrjoy:
Quick question. While f2fs format,if i goes to stock to cm rom then i should again format all partions as f2fs?
[Galaxy S III Original Android Development] KMino:
No, as you won't be able to access f2fs without kernel support and you'll end up in a boot loop et. Backup all and reformat those f2fs partitions to ex4 and restore. You can use Boeffla 2.2 beta5a, it'll work with new CM versions..

Sadly no updates here, one must move on so be it.. :(
[Galaxy S III Original Android Development] Andr3y29:
He must use a kernel that supports f2fs, otherwise it will end in a bootloop. For now, only Devil Kernel, Agni Cm and Agni PureStock supports that. It is actually another, XPure Kernel I think it is called, but it is an abandoned project. If you will flash Boeffla, you will get a bootloop.
[Galaxy S III Original Android Development] KMino:
Boeffla works using it now on latest CM. If he converts his partitions back to ex4 as I stated...

I forgot to ad, must use devil recovery to backup and restore. As no other recovery can restore its f2fs backups...
[Galaxy S III Original Android Development] cloudx720:
IMO all the work he did to get f2fs working on our device failed to get the recognition he was hoping it would receive, people not donating ect...real shame tbh. As this is an amazing kernel, one of the best for our i9300.
[Galaxy S III Original Android Development] tetakpatak:
Guys, let developer alone, he may enjoy some free time now. You don't need an update if the kernel works perfectly fine and he hasn't got any obligation to answer the questions.
[Galaxy S III Original Android Development] spoonymoon:
+1
[Galaxy S III Original Android Development] mrjoy:
You told that format " /cache - we will not have an option to select f2fs" but there i have option to select f2fs during format cache partition but there is no option to select f2fs during formating data partition.....but i had already formatted /data, /sdcard and secondrom as f2fs....
[Galaxy S III Original Android Development] Moster2:
Who is you? DerTeufel for sure didnt say that