yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Mostafa Wael:
Well that didn't help either :(

Here is what it wrote:

Formatting /system
Extracting ROM files
Creating symlinks
Fixing permissions

set_metadata_recursive: some changes failed
E: Error in /.secondrom/media/bluetooth/back-to-n00t_ROM_V2.zip
Can not install
Installation aborted

That was when i used the no-workaround method

When i used the workaround method it wrote exactly the same after the zip got modified successfully

NOTE: the zip i used is a fresh one. I had two copies. The origional one in a seperate folder (/storage/sdcard1/Touchwiz 4.4.4 port/back-to-n00t_ROM_V2.zip) and the one i test with (/sdcard/bluetooth/back-to-n00t_ROM_V2.zip) and i am 100% sure that zip isn't faulty as i installed it previously on my phone with TWRP

Sadly i didn't find a recovery.log file ....

Please take a look

Sorry for disturbtion :D
[Galaxy S III Original Android Development] Thecrazyskull:
Weird because i tried exactly the same and it just worked fine.
[Galaxy S III Original Android Development] Mostafa Wael:
Can you tell me the

EXACT

steps you did?

And do you suggest to re-download the file?

I am going to download a new ROM based on arter97 port called "eRobot"

Man it has the USSD fixed!

But connectivity is slow.

Will try again and report as always :)

Thanks
[Galaxy S III Original Android Development] hansonchen:
I think you are using f2fs, i'm having issues installing few roms here with f2fs. Some have strange behaviors after successful installation (currently on ArchiDroid 1.7.18)
[Galaxy S III Original Android Development] Mostafa Wael:
Well i am on normal ext4 :D

Thanks for suggestion :)
[Galaxy S III Original Android Development] DerTeufel1980:
Please upload the file from the sdcard/devil location again. It automatically gets created if flashing fails
[Galaxy S III Original Android Development] Mostafa Wael:
No file!!
[Galaxy S III Original Android Development] Mostafa Wael:
Will try tomorrow... It is midnight here in Egypt.... Need some sleep

Will try with the (eRobot ROM) tomorrow
[Galaxy S III Original Android Development] Mostafa Wael:
Formatting /system
Extracting ROM files
Symlinking
Fixing permissions

set_metadata_recursive: some changes failed
E: Error in /.secondrom/media/0/bluetooth/back-to-n00t_ROM_V2.zip
(Status 7)

Installation aborted

here is exactly what i got...

i wrote it in my copybook to be exact :D

and i thought to install another ROM as a primary ROM to see. it was ArchiDroid 3.0 in this case...

and i got this error (set_metadata_recursive: some changes failed) right after symlinking

also no logs... :/

i think your recovery needs to be updated?

i will try to figure it out...
[MENTION=5083850]Anas Karbila[/MENTION] can you link me to the recovery you used to dualboot successfully ??

thanks

waiting eagerly for next version...
[Galaxy S III Original Android Development] Thecrazyskull:
I will warn you the rom from erobot wipes your whole internal storage so back it up!

What i did:

1. i downloaded the back2n00t rom

2. install devil recovery

3. go to dual-boot menu and select create secondary system image

4. go to install zip (i selected internal storage because the rom was stored there) and select rom to second system.

5. select back2n00t rom and just wait untill it finishes.

I used the devil recovery from first post.

http://xdaforums.com/showpost.php?p=47495178&postcount=1

I really hope this helped.
[Galaxy S III Original Android Development] Mostafa Wael:
you used the one in the OP ?

what version of "Devil Touch" it was?

i am having Devil Touch 6.0.4.5....

meanwhile i will be trying again with n00t

thanks for help

P.S. when i will dualboot the eRobot ROM, i will use the nandroid instead
[Galaxy S III Original Android Development] Thecrazyskull:
Yes the one in op.

I think its the recovery because mine is v6.0.4.4

I think that the one in op is updated because i had this recovery on my sdcard about a year ago (if i remember right).

If you want that i upload the one im using tell me i will do it.

EDIT: i remembered that i didn't download it from the op i downloaded it from googymax2 kernel thread so i think thats the one that should be working.

http://xdaforums.com/showpost.php?p=47249482&postcount=2
[Galaxy S III Original Android Development] Mostafa Wael:
So yours is 6.0.4.4 ?

That is the one in the OP

I have it also

Will try in a couple of hours.,...

I am studying now :p

Thanks for help :)
[Galaxy S III Original Android Development] Thecrazyskull:
Oo i thought they where different because you said that you had 6.0.4.5
[Galaxy S III Original Android Development] Mostafa Wael:
Ok ok to clear any confusion can you do the following

1. Navigate to /data/media/.secondrom/ and there you will find a system.img file

2. Tell me the size of the system.img file

That will verify which recovery you are using....
[Galaxy S III Original Android Development] Thecrazyskull:
Not needed because im 100% sure that im using 6.0.4.4
[Galaxy S III Original Android Development] Mostafa Wael:
Okay then...

Did it take somehow longer time when installing the back-to-n00t zip to modify it ?!

That's the last question :D :angel:
[Galaxy S III Original Android Development] Thecrazyskull:
Yes it was about 3min when installing as primary rom takes 1-2 minutes.
[Galaxy S III Original Android Development] Mostafa Wael:
Thanks THANKS thanks Thanks a lot of thanks friend :) :)
[Galaxy S III Original Android Development] DerTeufel1980:
It always takes some time, if you use the workaround method, because it is unzipping the file, modifying it, and then repacking it.
[Galaxy S III Original Android Development] Mostafa Wael:
So did you figure it out?

Sounds to me like recovery needs to get updated/ or shall i say get older??!

Anas karbila got it working on the older recovery

And i am using the newer recovery having problems... :laugh:

And the really weird thing is that there is no log generated...... Again!!
[Galaxy S III Original Android Development] Mostafa Wael:
I installed a Linux USB Driver on my laptop and now my phone is detected in recovery...

when I type 'adb devices'

it shows me my device's serial number with the word "recovery" beside it...

will try tonight and hopefully post a good proper recovery.log
[Galaxy S III Original Android Development] Thecrazyskull:
Your welcome ;)
[Galaxy S III Original Android Development] Mostafa Wael:
Here is a proper log via adb

Didn't break a sweat :laugh:

Recovery used: Devil Touch 6.0.4.5 "the newer one that was attached to the F2FS Post"

Steps done:

-1 created a secondary image

-2 installed /storage/sdcard1/To_be_installed_as_2nd_ROM/Back-to-n00t_ROM_V2.zip normally with no-workaround

-3 installed it again but with the workaround method, i.e. modifying the zip

-4 connected the device to computer and got it detected thanks to the Linux USB driver ;)

-5 Typed the following

adb shell
cat /tmp/recovery.log > /sdcard/recoverydevil.log

here is the log :)

Hope you figure it out :)

Pastebin: pastebin.com/WPZ58t6H
[Galaxy S III Original Android Development] Mostafa Wael:
[MENTION=4196889]DerTeufel1980[/MENTION] sorry I will not be able to provide anymore logs for ~3 days:

I am currently in the hospital and I am having breathing problems.....

will be back when I am better...
[Galaxy S III Original Android Development] DerTeufel1980:
Which you all the best.

I'll check the updater script of the rom meanwhile. It always fails at same file, stating it doesn't have permission to change it....
[Galaxy S III Original Android Development] Mostafa Wael:
And ArchiDroid 3.0.0 28/9 also....

It writes "set_metadata_recursive: some changes failed"
[Galaxy S III Original Android Development] Mostafa Wael:
Okay i am back to the game now, feeling better now :D

I just want to show such a great miracle for the S3 now

I know benchmarks are something like fake but i just do them for fun

And...

I got a blazing 29018 on Antutu !!!!!

I rarely got a score more than 28.5k :victory:

Waiting eagerly for the next version

Everytime i say, now i will get the newer build and remeber that Devil kernel still doesn't support them yet, i just stay on my 28/9 AD 3.0.0

:)

EDIT: Screenshot attached ;)
[Galaxy S III Original Android Development] Mostafa Wael:
Remeber the wifi issue on arter97 port?

I am having the same behaviour but with wifi hotspot

Here is a detailed report:

I am having my mobile data enabled now

I opened the WiFi AP settings from settings and switched it on:

Attitude: WiFi AP is constantly switching on and off

Now i rebooted the phone (normal reboot)

Attitude: WiFi AP working as expected.
[MENTION=4196889]DerTeufel1980[/MENTION] can you tell me the command that is typed in terminal command to test if it has the same logs as in TouchWiz 4.4.4 ROMs?

Thanks

Waiting eagerly for next version :) "as always"
[Galaxy S III Original Android Development] DerTeufel1980:
I suppose it's again related to loaded modules.

Use this at first and second boot and compare the output

adb shell

lsmod
[Galaxy S III Original Android Development] Mostafa Wael:
Can't reproduce the issue :D
[Galaxy S III Original Android Development] nkirk:
Are you running 2000Mhz ?:confused:
[Galaxy S III Original Android Development] motshek:
2000Mhz.... + ArchiDroid 3.0.0

[emoji1] [emoji1] [emoji1]
[Galaxy S III Original Android Development] Mostafa Wael:
Wow wow ? What was that? I barely get a stable 1.8 GHz

I got the 29k with 1.7 GHz

How did you get that 2 GHz stable?
[Galaxy S III Original Android Development] Jole7:
Amazing score man.:good: Can you tell me how you manage to run at 2000 MHZ stable without the phone close itself?
[Galaxy S III Original Android Development] Thecrazyskull:
Thank you very much for this kernel and the awesome performance+battery life
[Galaxy S III Original Android Development] Mostafa Wael:
In the following directory (/data/media/dualboot/META-INF/com/google/android/)

I found something interesting that may help in the dualboot problem i have with back-to-n00t
[MENTION=4196889]DerTeufel1980[/MENTION] Can you take a look ?

https://mega.co.nz/#!5VomULSA!co6rlVWnbrm4FUisMEyH81s5It5mIsPRAwdehK--XLs

P.S i am back to hospital :( but this time it is a serious wound. Will be back around 10-14 days.
[Galaxy S III Original Android Development] abhibnl:
2ghz, seriously? Afaik, that's not stable at all on any s3. S3 can barely handle 1.7-1.8ghz oc.

Sent from Galaxy S3 Powered by AD 1.x + Boeffla
[Galaxy S III Original Android Development] Mostafa Wael:
I got this with 1.7 GHz

Antutu shows the maximum CPU scaling that the kernel can reach, not the tuned CPU frequency.

---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------

http://xdaforums.com/showpost.php?p=56282638&postcount=1170

[MENTION=4196889]DerTeufel1980[/MENTION] hey great dev, can you match the ramdisk with this one in next version???!
[Galaxy S III Original Android Development] Jole7:
maybe our devices can hadle up to 1.9 or 2 GHZ only if you tweak the governor and benchmark inside the fridge.

Am i wright? just a guess!

P.S. only the developer knows better about this
[Galaxy S III Original Android Development] Mostafa Wael:
Concerning the dualboot issue i have successfully dualbooted ArchiDroid 1.7.18 as a 2nd ROM

And everything worked quite well

So does that give a clue ?!
[MENTION=4196889]DerTeufel1980[/MENTION]
[Galaxy S III Original Android Development] mkhawx:
Deleted!
[Galaxy S III Original Android Development] GrayJack:
I suspect some problems with battery charging on latest Devil kernel.

The battery charges too fast - in almost 2 hours from ~10% to 100% when the phone is on. In the same time discharging is also fast so I suspect it doesn't charge to full capacity. Actually I can see a drop down by 5% in first 10-20 minutes after charging without performing any activity on the device.

In the same time the full charging process when the phone is off is about 4-5 hours which is normal.

I didn't change any settings of battery charging in Devil config.

Any ideas on it?
[Galaxy S III Original Android Development] Mostafa Wael:
Well I have nearly the same attitude:

When I charge the phone via USB I get slightly better battery life (although at high current 900mA)

But when I charge using AC "with the ignore unstable power option enabled" it charges quite fast but sometimes my phone discharges a bit faster than normal

P.S the only way to get my phone charged via AC is to check the unstable power ignoring option. Damn Samsung faulty chargers :D :p

P.S also: I am eagerly waiting for Devil kernel to get updated to support the newer back-to-n00t base (V4/V5)
[Galaxy S III Original Android Development] GrayJack:
1. If the charger causes the problem it will be the same with other kernels and during power off charging. But it is not true.

2. The situation is the same when charging from other charger and from Romoss solo9 external battery. All three supplies are faulty? I don't think so.

Upd: I have found some tricky way to "recalibrate" the battery:

If you want to know my opinion - it's something like voodoo magic :) But anyway I will try it and report the result. Frankly speaking I think the problem is in battery control in kernel rather than "calibration".
[Galaxy S III Original Android Development] mkhawx:
How to know about the latest devil kernel? Its tuff reading all the comments for searching :P
[Galaxy S III Original Android Development] Mostafa Wael:
Well yeah same behaviour with other kernels. Boeffla and AGNI and arter97

Did not try with other power supplies though

Will try with external battery....

And i am waiting for your response for rrcalibrating battery
[Galaxy S III Original Android Development] Mostafa Wael:
Latest devil version is called (Devil3.4_0.5.3)

---------- Post added at 08:23 PM ---------- Previous post was at 08:22 PM ----------

I am having literally no vibration on Back-to-n00t based ROMs.

EDIT: after 1st boot (yeah I rebooted to activate the WIFI) I am having very very very weak vibration. It can not be felt while the phone is in the pocket. Only felt with typing and the haptic ffeedback of the soft buttons.

I guess that this vibration is about 2% or 5% if we are having an AOSP ROM and setting the vibration via DevilTools.

Other than that I am enjoying it

RAM management is better than most other kernels (maybe its me who can't play with zRAM and LMK, but at 40% zswap "331 MB" and 80% swappiness RAM is good with me)
[Galaxy S III Original Android Development] rascal0pl:
Could you provide a link ?
[Galaxy S III Original Android Development] Mostafa Wael:
Of course mate

Here you are:

http://xdaforums.com/showpost.php?p=55926111&postcount=2197

Kernel changelog included (as a bonus :D )
[Galaxy S III Original Android Development] GrayJack:
Cannot confirm it changes a lot (just as expected).

But the question about charging speed still exist. Waiting for [MENTION=4196889]DerTeufel1980[/MENTION] for some explanation.
[Galaxy S III Original Android Development] rascal0pl:
Thanks. I just tried it on back for n00t, but it is unstable as hell, rebooting even on app install, I will wait for next version.
[Galaxy S III Original Android Development] Mostafa Wael:
Are you sure?!

well I was enjoying it, except for the WIFI, where you have to reboot once after flashing the kernel to get your WIFI working....

maybe the vibration getting very very low was kinda annoying.. but generally it was fine.

except for RAM management after a long run. it freezes and lags after some time. maybe if [MENTION=4196889]DerTeufel1980[/MENTION] added an option to set zswap up to 500 MB we may have the multitasking improved ?!
[Galaxy S III Original Android Development] DerTeufel1980:
Args, I only tried vice versa. Cm primary and omni secondary... Which was working.

Did it just hang? Or did it reload the Samsung logo?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] PIRATA!:
Hi.

Can you please add md5 codes next to the downloads?

Thank you.
[Galaxy S III Original Android Development] uzb777:
I have this problem too... :(
[Galaxy S III Original Android Development] Zocker Tko:
Just hangs

Gesendet von meinem GT-I9300 mit Tapatalk

---------- Post added at 12:55 PM ---------- Previous post was at 12:43 PM ----------

But when cm as primary and omni as secondary, and both Roms are working fine, then is it super enough or not?

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] fjfcb:
Hey man, please, take a look at this, I'm using omni as first rom now, it is working fine with this version, but vibration is VEEEERY weak, we can't feel it when pressing buttons in keyboard for example. And the lights of the physical keys are not working...

Also, my phone hangs on sammy screen too (the one with the red exclamation mark) id doenst even go to the boot animaiton, sammy 4.3 as secondary rom
[Galaxy S III Original Android Development] DerTeufel1980:
You can control it in deviltools

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] spoonymoon:
This far latest 11/26 boots omni as primary and cm11 v.9 as second just fine - but havent tried the other way around !?

:)

edit: try these gapps on cm 11 >

http://xdaforums.com/showthread.php?t=2012857
[Galaxy S III Original Android Development] habylab:
Could you add yanks battery profiles to this, if possible? For zzmoove ?
[Galaxy S III Original Android Development] fjfcb:
Is it compatible with ART? it is hanging as soon as I Open it *version 1.0.1

edit:

it is force closing with dalvik too
[Galaxy S III Original Android Development] DerTeufel1980:
I was reading "art" few times already. What is this?

Edit: can you get me a logcat of the crash please

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] fjfcb:
Man, you really need some reading :p

http://www.androidpolice.com/2013/1...-in-secret-for-over-2-years-debuts-in-kitkat/

logcat:

http://pastebin.com/fPF1J8nN
[Galaxy S III Original Android Development] Xami:
I'm dual booting with S4 revolution as primary ROM and Omni as secondary and when I boot into S4 revolution the kernel is removed somehow and to get into the secondary rom I need to flash it again but that's not the big problem the problem is in the secondary rom with your kernel the mobile is getting warm. first I was using your Governor then I changed to peagusesq but still its gets warm
[Galaxy S III Original Android Development] Moster2:
He is a kernel dev. That are the guys that only see the light when they need to go to work. Reading about fancy new rom stuff is irrelevant to them :D
[Galaxy S III Original Android Development] fjfcb:
But we are talking about new Android stuff, and I think he is an Android user, so...
[Galaxy S III Original Android Development] Moster2:
That was just a joke :D You shouldnt take it too serious
[Galaxy S III Original Android Development] DerTeufel1980:
ah, thanks for the link.

art seems to be interesting, but it broke root for me on cm11, and also whatsapp wasn't working anymore...hope those bugs get fixed soon (either by google or the app coders).

your crash of deviltools is related to su (to art?). it is failing to extract some scripts, because you are missing root. because of it failing to extract the script, it tries to log the error. because of missing root again, it crashes.

i'll add a check for root, and let it print a warning, if missing. till then, your workaround should be, to root your rom again ;)
[Galaxy S III Original Android Development] DerTeufel1980:
oh well, this has been a mess :p

sorry for all the trouble with omni/cm. too bad i can't try it myself :(

i am 99% sure, this one is working now on cm11 and omni, as primary and secondary ;) of course samsung and aosp 4.3 roms are still working :p

http://www.mediafire.com/download/aaw6yi0ezs1u27a/Devil2-1.6.2-i9300-DUAL-20131126.zip
[Galaxy S III Original Android Development] Mostafa Wael:
Man i got confused :confused:

i find 1.5.3 working like hell on omnirom. Running as my daily driver since it was placed officially in OP.

So are there any differences between the stable official 1.5.3 and the recent test kernels? I am having hard time here with exams and studying so no time to try or flash kernels and that stuff. I will only update my omnirom to the 26th nightly (really missed the ActiveDisplay :laugh:) and flash your 1.5.3 kernel.

Thanks for your attempts to bring your support to all ROMs. Hope you have a success with your trials... :cyclops:
[Galaxy S III Original Android Development] Xami:
+1

I'm also using it as daily driver but after flashing 1.5.3 i can feel the rom is not running as it should also its a bit slow and cellphone gets warm too
[Galaxy S III Original Android Development] DerTeufel1980:
1.5.3 is using omnirom initramfs also for cm, because first feedback was great.

Later I noticed, that this was breaking some stuff for cm roms, hence I had to find a better fix

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] rascal0pl:
yeah, you are right, I'm testing 2-3 roms for a week, but in this case I'm doing it wrong. OK.

I'm downloading back for n00t again, maybe rom file is broken.

Ok downloaded and installed, everything is the same :/

PS. back for n00t v5:

It won't event boot (first start, stuck @ samsung logo). I must flash arter kernel, phone must boot for the first time and pass the configuration, and then when I flash devil - it boots, but it is very unstable.

I'm using f2fs on /data and /cache.
[Galaxy S III Original Android Development] nosphor:
Hi everyone,

Can someone confirm that the latest version of the devil kernel is working with the latest paranoid build ?

Thanks for the answer :p
[Galaxy S III Original Android Development] rascal0pl:
If you guys have nothing to say, just stay quiet. Posting pictures like this is f**** retarded.
[Galaxy S III Original Android Development] GrayJack:
Does it mean that I need to reflash the kernel after updating stock ROM? Normally I've used Mobile Odin for updating without checking "kernel" and "recovery" parts - and it was OK.
[Galaxy S III Original Android Development] DerTeufel1980:
If you don't flash the other kernel, your fine
[Galaxy S III Original Android Development] mardokres:
Hello guys.

I just sold my i9000 few months ago and i have now i9300.

I have few questions.

Can i flash this kernel on original stock Samsung rom 4.3 UGNA8 without any problems?

Can i flash it with Odin or there is only version for custom recovery?

Thanks for any help and many thanks for developer of this kernel, loved it on my old i9000. :good:
[Galaxy S III Original Android Development] coolhof:
Yes you can flash this on stock sammy 4.3.

About flashing with odin I don't now.

I always flash from devil recovery.
[Galaxy S III Original Android Development] inooni:
How can be fixed vibration problem?is there any solution or workaround for it?
[Galaxy S III Original Android Development] DerTeufel1980:
I'll try to check vibration issue in the evening. Had been away from home for more than one week.
[Galaxy S III Original Android Development] GrayJack:
[MENTION=4196889]DerTeufel1980[/MENTION]

Hm, didn't report about that thinking it's something my own, but after publishing the fix by arter97 I'm in doubt.

The problem is with random deadlocks during phone calls. I mean the call is OK, but after it is finished the phone is locked. The screen is black, sometimes several horizontal strips can be observed in dark room conditions. The only way is reboot.

Does somebody observe the same? If so - maybe sane fix should be implemented?
[Galaxy S III Original Android Development] DerTeufel1980:
It never happened to me (note2), but maybe it's a s3 typical issue. With which governor does it happen?
[Galaxy S III Original Android Development] coolhof:
It's not a s3 problem.

Don't have a single problem.

I use kernel Devil3.4_0.5.3-i9300-DUAL-20141009.
[Galaxy S III Original Android Development] GrayJack:
Devil Governor. Should I provide any log to help you investigate this problem?
[Galaxy S III Original Android Development] Jole7:
this is my score with your latest kernel

View attachment 3018748

View attachment 3018755

Thanks for your hard work mate.