yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] JustArchi:
HOWTO: Convert Your External SD Card from FAT/exFAT to EXT4!

Why I should use EXT4 instead of FAT/exFAT?

1. We're running Android, Android is based on Linux. EXT4 is native linux-proposed filesystem, while FAT/exFAT is not.

2. All our internal partitions (/efs /data /system /cache /preload) use ext4, natively.

3. CM has poor exfat support, while fat32 is not recommended for big file systems (over 2 GB) because it doesn't work well with them, thus microsoft implemented exfat.

4. EXT4 has better stability and performance, especially on Android devices, compared to exfat and fat.

When you should not use ext4 over fat/exfat?

- When you for whatever reason use your external sd card in windows environment physically. Android works in MTP mode, you'll use your ext4 external sd card the same way as you use internal one under windows. But if you for whatever reason puts your external sd card f.e. in usb adapter connected with windows then it won't work. So yeah, if you keep your external sd card in your phone then you're fine.

Newbie way (Requires PhilZ Touch Recovery, may not work):

1. Launch PhilZ Touch Recovery

2. Select "Mounts & Storage" => "format /external_sd"

3. Select "ext4" as a filesystem

4. Please note that it can take some time. This way you should get running ext4 filesystem, but personally I didn't test this method, as I prefer more advanced ones ;).

Intermediate Way (Requires USB Adapter and some patience, should work like a charm):

1. You'd need USB Adapter or any device which can read micro sd cards on PC

2. Open any linux-supported partitioning program (f.e. partition magic, gparted, parted), it needs to support ext4.

3. Delete all partitions from your external SD Card (typically, one fat/exfat) and create one ext4 partition.

4. In case you'd also want hardswap create 2 partitions, one primary ext4 one and second primary swap one.

Expert way (Requires ArchiDroid, works always):

1. Launch any terminal from ArchiDroid environment (f.e. Android Terminal Emulator or adb shell through PC)

2. Make sure you have root (su command)

3. Unmount your external sd card (umount /storage/sdcard1)

4. Launch fdisk partitioning program on your external sd card (fdisk /dev/block/mmcblk1)

5. Destroy partition table (o), create new partition (n), make sure it's primary (p) and first one (1).

6. You can check if you're satisfied with your partition layout (p). When you're done exit and save changes (w)

7. Create ext4 filesystem on your partition (mke2fs -t ext4 /dev/block/mmcblk1p1)

8. Reboot

As always, short movie following expert way :cool:

[YOUTUBE]DK1Ft3FRxRQ[/YOUTUBE]

Have fun :).
[Galaxy S III Android Development] Clonimus74:
formated to ext4, now it says "fuse" and I have the same problem with the m3u files
[Galaxy S III Android Development] JustArchi:
I'd suggest waiting a few more hours for AD 2.2, making full wipe and if it won't work then Android doesn't like m3u's :p.
[Galaxy S III Android Development] jackiestuxedo:
Youhou waiting for it :)

Envoyé de mon GT-I9300 en utilisant Tapatalk now Free
[Galaxy S III Android Development] striked0wn:
Battery usage is broken.. Global or only on my side..?!.. :)

Edit: Working now.. Just updated.. :P
[Galaxy S III Android Development] JustArchi:
You've waited for it, and heeere it comes! :victory:

ArchiDroid 2.2

Changelog

ArchiDroid 2.2

-> FULL WIPE HIGHLY RECOMMENDED <-

- [!] ArchiDroid is now built from source, thus it's independent fork of CM now

# ArchiDroid is based on [MENTION=4478519]Cristiano Matos[/MENTION] (crDroid) sources, but it's self-compiled by me

# From technical point of view this is a big change, but from your point of view it still has nearly all functions provided by temasek, f.e. HALO, Navigation bar, and more (thanks to [MENTION=4478519]Cristiano Matos[/MENTION]!)

# Slowly *maybe* AD will have even more unique features, as for now consider it as independent crDroid-fork

- ArchiDroid Backend is more verbose now. You can find logs in /data/media/0/ArchiDroid - RunOnce.log, PermFix.log, err.log (shared)

- Added Finnish language, thanks to [MENTION=4042238]amppen[/MENTION]

- Added Russian language, thanks to [MENTION=2033109]egotheist[/MENTION]

- Added fast dormancy toggle, available if you choose build.prop tweaks. This way you don't need to disable it manualy. Thanks to [MENTION=5139098]andreasltcf[/MENTION]

- Updated Boeffla kernel to 2.0-alpha3 and app to 2.0-alpha6 (this fixes f.e. non-sticking changes in presets after reboot)

- Updated Archi's presets for Boeffla kernel, misc changes (system tweaks off)

- Updated Temasek's kernel to 061013

- Updated Googy Max kernel to 1.7.5

- Updated Onandroid (built-in component) to 9.10

- Updated Xposed to 2.3.1

- Updated Cool Tool to 5.1

- Updated CM source (Android 4.3.1!)

Download

All Files XDA

Stable: ArchiDroid 2.2 XDA

Oldstable: ArchiDroid 2.1.7 XDA

Remember that you don't need anything else to flash. Google Apps are included already.

As noted in the changelog, full wipe is highly recommended.

Thank you guys for continuous support. This is the "milestone" release, featuring independent ArchiDroid, built from source :cool:

With this release I'm dropping support for ArchiDroid 2.0.3, consider it as archival release from now on. 2.1.7 is still supported but don't expect any more updates regarding 2.1.X branch.

If you respect my time put into this project you can always consider a small donation. Thank you!
[Galaxy S III Android Development] crital:
Flashed 2.2 successfully. Thank you for your work :good:
[Galaxy S III Android Development] ssmmdd:
I'll be giving 2.2 a go shortly.

Btw, [MENTION=5161352]JustArchi[/MENTION] , I figured out that for some reason the settings in STweaks were all buggered, No idea how. I re-copied 2.1.7 to the SD Card, flashed it, and everything seemed fine. My apologies for before! One of those weird things, I guess.

Also, many thanks for the fatxx to EXT4 conversion walkthrough. I've just done it (your "expert" way) and it worked flawlessly. My 16GB MicroSD card is free from M$'s evil shackles!

So, to thank you for the awesomeness that is ArchiDroid, please buy yourself some beer: Donation Confirmation number: 91X43608FY177661B.
[Galaxy S III Android Development] meevrocks:
Wow finally 2.2! Is it okay to backup 3rd party apps via Titanium Backup and restore app+data after wiping and installing 2.2?
[Galaxy S III Android Development] AUSTAB2012:
Downloaded can't wait to get home to flash this
[Galaxy S III Android Development] edil_sa:
testing it a week now... very smooth... very fast and no glitches so far!

thx guys!!
[Galaxy S III Android Development] Sc0rp10:
in most cases yet but some apps might not work properly after app+data specially if they are system apps. also restoring system settings through TB might cause problems
[Galaxy S III Android Development] Iceman_jkh:
Just posting back, cos I figured out a solution.

Go to Display and Lights -> Notication Light and put a tick in Notification Light AND Use Custom Values.

If notification light is unticked, you get NO notification LEDs from Lightflow.

If Use Custom Values is unticked, it only shows flashing/pulsing LEDs from Lightflow (those notifications set to Always On will not show).

Cheers.
[Galaxy S III Android Development] gesaugen:
I've been experiencing total reboot crashes on this rom after a few day use. It works normally and then just sudden I can't recharge it at all so it discharges the battery to the max and then it can be recharged but when I power it up, it factory resets itself and after configuring itself and rebooting, it gets stuck on the archidroid boot logo and I can only shut it down by removing battery. But when I place battery back again, it immediately boots again and gets stuck on samsung logo. I can go into recovery (I have Philz CWM)

any idea why it acts so strange all of the sudden.

and btw it's great rom, best for S3 by far. Battery lasted for 15 days in stand by!!!
[Galaxy S III Android Development] vldesco:
I don't have my S3 for some time, but as far as I remember, when a factory reset is done, some files needed by archidroid to work are deleted too, so you must reflash the rom.

No idea why you have this issue.
[Galaxy S III Android Development] Minto107:
Yeah that's very possible. I remember it was putting some stuff in /data partition
[Galaxy S III Android Development] slonioo:
This ROM is not any more developed. EOL in the threads name means "End Of Life", if I'm correct?
[Galaxy S III Android Development] AndreasThaler:
Impressive!

Wow! Nice Kernel & ROM. Battery life is _very_ good. Speed is _very_ ggod. Nice Installing. Nice to have root from the start. Thank you so much. This saved the life of the old mobile!
[Galaxy S III Android Development] LegendM:
I'm using galaxy s8, but still after all this years, new versions of android, new devices etc. Nothing is better than this rom. This is the best rom I ever used and probably ever existed for any android device. I really really really wish [MENTION=5161352]JustArchi[/MENTION] is still active but he didn't even log on in last 2 years so..
[Galaxy S III Android Development] mohamed xash:
this rom is the best eol or not.

for those who are getting file explorer FC's and random bootloops.install it in barebone mode. it's just that good
[Galaxy S III Android Development] leduletz:
flashing from scratch

Hi guys, I'm very new on this territory and I would need some advice please.

So, I have a stock S3 and I want to flash this AD.

Please tell me the steps I have to perform, in order to get the thing done.... I am a little bit lost in the beginning of the process.

Many thanks!
[Galaxy S III Android Development] JCFB:
Just no, this is a rom that isn't updated since 2015. You'll be better off flashing the last official lineageos 14.1 build with some custom kernel. Trust me, I used this rom for like 4 months back in 2017 and even then it wasn't that good. It's kinda slow and sometimes buggy. Now i'm using a lineageos 11 rom updated in 2018 with a cm11 based custom kernel and my phone feels very smooth, but of course it is an EOL rom based on android 4.4 so it isn't the most updated out there.

So like I said just flash the official lineageos 14.1 and you're good to go
[Galaxy S III Android Development] macsy:
Sure I can try, but can you please give me the link to it? And the steps to flash it?

Many thanks!
[Galaxy S III Android Development] 3dward87:
Hi

Can you be more specific? there are too many of them, and dont know which one is most stable.

I am looking to flash something with a newer version of ROM, cause in 4.3 (tried with Stock, and ArchiDroid) if I use whatsapp web, whatsapp crash.

Thats the only reason.
[Galaxy S III Android Development] quadlt:
*sigh* Archi. Clean 2.2 install, same problem, 'disabling' illuminate buttons option makes it same as illumination time out : 'Don't turn off'. Any ideas?

EDIT:

WARNING EVERYONE! Titanium backup doesn' work and results in 'Problem with parsing the package'. Tried both with 4.1.2 Sammy and 4.3 (Archi's 2.1.7) backups.
[Galaxy S III Android Development] Sc0rp10:
I used titanium backup to restore about 20 apps with data and it's working without a problem. May be your backup is corrupt?
[Galaxy S III Android Development] JustArchi:
No issues on my side as well. Maybe your backups are corrupted? Maybe you're using old path back from 2.0.X version, which doesn't work correctly on 2.1.X and 2.2.X?
[Galaxy S III Android Development] JustArchi:
Thank you bro, I highly appreciate it. Imagine if every user who downloaded my rom donated at least 1$... :angel:
[Galaxy S III Android Development] striked0wn:
Sometimes it doesn't work.. Don't know why.. But set backupfolder from /storage/emulated/0/(your backupfolder) to /storage/emulated/legacy/(your backupfolder) might help :).. Or you move your backups to external sd.. Will work for sure.. And it's safe.. ;)
[Galaxy S III Android Development] quadlt:
Well, backups don't really bother me at the moment. It's the hardware buttons that still don't turn off no matter what. Answer on that please.
[Galaxy S III Android Development] JustArchi:
Settings => Buttons => Backlight => [ ] Illuminate buttons => OK

Now lock your phone and unlock it after ~2 seconds. In my case buttons backlight is perma-off now (while before backlight worked only if you clicked on a button).
[Galaxy S III Android Development] czuppa:
Screen colours

Dear Sir

Your rom is really awesome and very fast. But screens colours in Boeffla kernel is a little awful in my opinion.

Is there a way to change this?

Best regards
[Galaxy S III Android Development] Egozy:
Flash a different kernel. You can also choose a different one in aroma.
[Galaxy S III Android Development] malachow:
No need to flash different kernel.
[MENTION=2848949]czuppa[/MENTION] - just go to Boeffla Config app & change 2 values in MDNIE tab for Natural and UI - your colors should be dull again. ;)
[Galaxy S III Android Development] czuppa:
thanks a lot. Because I love this combination. In fact, Antutu benkmarch is really good
[Galaxy S III Android Development] benedictros:
I don't think JustArchi would post a stable build that doesn't work with TitaniumBackup. It would cause a lot of havoc. Yours seems to be an isolated case. Not to be rude, but try not to post alarming messages like this in bold and red color if you aren't 100% sure about what you're saying. You can cause a lot of confusion.

Hope you get your ArchiDroid + TiB restore working, man. Good luck!
[Galaxy S III Android Development] JustArchi:
If any bug exists in stable build then either it has not been discovered in experimental, or it's not fixable in near future.

As for now in whole AD 2.X history there was only one "important" bug which was not discovered in experimental, in version 2.1.4 and fixed in 2.1.4.1. I consider it as a very good score regarding whole AD history. Trust me or not but AD is not "only a rom", it's far beyond basicly anything right now because it utilizes both compiling from source and adding backend/aroma/everything.

While you can find CM10.2 SelfKANG ROMs I'm not sure if anybody offers such flexibility in them :p

Speaking of experimentals, I've just added first commit regarding managing user presets. Now AD saves your choice after installation. It only lacks of load function :p.
[Galaxy S III Android Development] quadlt:
Negative, still puts my buttons on Always on mode.

EDIT : Now it works. Had to do few locks.
[Galaxy S III Android Development] JustArchi:
Which kernel do you use?
[Galaxy S III Android Development] quadlt:
I edited my post before, now it works fine just took a few more locks/unlocks to set up.
[Galaxy S III Android Development] JustArchi:
Glad it worked. You know CM changed a bit how backlight now works (rom-handling instead of kernel-handling) so we have a little confusion here.
[Galaxy S III Android Development] JustArchi:
Hey.

I'm glad to tell you that I successfully implemented first working version of your idea with user presets ;).

It works like this:

During custom preset selection aroma saves your choice in /data/media/0/ArchiDroid/AromaPreset in special *.prop files. Additionally it stores preset version in version.txt file. On preset selection screen you now have also "Previous Preset" choice, which checks if preset version matches the version of created preset, and if it does then aroma loads your old config, if it does not match then aroma takes you to custom preset.

I needed to implement version check because I often make important changes to aroma and if f.e. I add new choice under build.prop tweaks then if you load your old preset updater-script will crash with null pointer exception (no entry for if check).

I think that such implementation is quite good, if you have any additional ideas/suggestions feel free to write them.

Cheers :).

EDIT:

I've tested this feature multiple times and it works flawlessly. As long as ArchiDroid folder exists on your internal memory you can keep your preset, even if you're making full wipe (without /sdcard wipe).
[Galaxy S III Android Development] JustArchi:
User Presets are now available in experimental. Have fun testing them (remember that firstly you need to have your preset, so you need to flash current 2.2.1 at least one time).

Happy experimental flashing!
[Galaxy S III Android Development] Clonimus74:
I flashed a different ROM and I have no problems with copying to the SD card.

I will try flashing 2.2 but it will have to wait until I return from vacation.

I will update
[Galaxy S III Android Development] wess786:
Hi,

I've selected the undervolting option in AROMA, but it feels to choppy. How do I get it back to the default one?

Verstuurd vanaf mijn GT-I9300 met Tapatalk 4
[Galaxy S III Android Development] malachow:
Reflash AD with update mode in aroma & changing undervolting option. ;)
[Galaxy S III Android Development] JustArchi:
Eventually you can just load different preset in boeffla config app (afaik my presets are stored in /data/.boeffla).

Up to you.
[Galaxy S III Android Development] Tak0r:
WOOOW you're are awesome!!! never expected to see this so soon! Going to Test 2.2 now since I haven't found the time sooner!
[Galaxy S III Android Development] JustArchi:
Keep in mind that this feature is implemented in current experimental, so if you want to test it you're going to flash 2.2.1 (experimental), not 2.2 (stable) :).
[Galaxy S III Android Development] wess786:
I already updated via the AROMA installer instead. Everything is working fine now. :)

Verstuurd vanaf mijn GT-I9300 met Tapatalk 4
[Galaxy S III Android Development] raylogic:
Hey JustArchi, I have posted a couple of times previously that I have random problem of wifi not switching on after going to sleep. Even when trying to manually toggle on it stays greyed out. The way to make it work was by toggling airplane mode on and off. I hoped problem for me would go once moving to 2.2 as full wipe etc, but no, the problem is even worse. From boot I am unable to switch wifi on. So now I come back to restore 2.1.7 to see what happens and now it works again but randomly as before...

Hope you can give me some advice my friend.

R.

Powered by Archidroid 2.1.7
[Galaxy S III Android Development] JustArchi:
Hey Ray.

Did you flash ArchiDroid from internal memory, as suggested by me several times? It's really important.
[Galaxy S III Android Development] raylogic:
Yes from internal sd for 2.2 and 1.7 but I cut remember before that. Problem only since 1.7 flash. Maybe I should refresh an earlier build to see if the problem goes away? Did modem versions change? Maybe I should try a different one? Sorry I really have no idea where to go with this. :-[

Powered by Archidroid 2.1.7
[Galaxy S III Android Development] kobety:
When trying to backup TitaniumBackup the application, I get an error saying that "I have not enough space to do the backup," How I can fix it? I have the rom version 2.1.7 and would like to move to the 2.2
[Galaxy S III Android Development] JustArchi:
That sucks :(. No, really nothing important changed apart from converting ArchiDroid to build from source.

I think that you should flash latest XXEMG4 from Samsung via Odin, then copy aroma file manager and newest ArchiDroid to your external sd card, then flash PhilZ Touch Recovery, boot it, format /system /cache /preload /data /sdcard and then move your ArchiDroid .zip file from external sd card to internal sd card through aroma file manager. Now you can try flashing again.

This is the full cleaning. I'm sad that you have such problems but trust me I haven't faced it ever before.

Make sure you have right path, either use /storage/emulated/legacy path or /storage/sdcard1 (external sd) if you have one.
[Galaxy S III Android Development] kobety:
Thanks for the reply! but how I can see/change the path?
[Galaxy S III Android Development] JustArchi:
Check options in titanium backup ;).
[Galaxy S III Android Development] kobety:
It solved alone....xS
[Galaxy S III Android Development] benedictros:
I just got the same error. Here's what i did:

Launch Titanium Backup

Press Menu button > Preferences > Backup Folder Location (under backup settings submenu)

Then just browse to the folder you want to select as your backup directory. Titanium Backup will then ask if you want to move your previous backups (if you have any) to that new location. Just accept if you like. Should work after that.

Question about the XXEMG4 modem...

I've done my research, but I am still rather confused about the modem update feature in the ArchiDroid 2.2 Aroma installation. Is there any particular advantage to installing the "latest modem" XXEMG4? I understand that the modem is what transmits signal from the provider (cell data), and the effectivity of the modem depends on many things (like provider, region, etc.). But does the XXEMG4 have any particular updates that make it worth trying? Currently, my phone is on its stock XXELKC modem.

Just flashed 2.2 and it's even smoother than my previous 2.1.7 setup. :) Well done once again, JustArchi.
[Galaxy S III Android Development] JustArchi:
Modem is "closed source". You'll never know if up-to-date modem provided by Samsung is better or worse. You can only make some tests and think that newer=better. It's optional feature, if you're satisfied with your current modem then you don't need to update.

XXEMG4 is a bit "better" because it converts EFS to EFS V2, if you're running both rom and modem XXEMG4. Additionally modems pre-xxemg4 can't read EFS V2, thus it's included by me in case somebody would like to have XXEMG4 flashable in aroma.

Read more -> http://xdaforums.com/showpost.php?p=43946365&postcount=15

XXEMG4 in aroma acts the same as emergency zip, it just flashes XXEMG4 modem.

Personally - call it placebo or not but I'm getting slightly better signal and less battery drain on XXEMG4, in comparision with XXEMB6, which I used before. But if you want to get all advantages provided by that you also need to convert your EFS to V2, this means flashing full XXEMG4 rom through odin provided by Samsung.

Up to you, as always.
[Galaxy S III Android Development] MuerteDiablo:
Het [MENTION=5161352]JustArchi[/MENTION],

Yesterday I flashed the 2.2 update and it works great so far. Only got one little problem.

If I make a picture with the camera it works but when I zoom in I can't take pictures anymore and none of the touch buttons work(e.g. back and menu). I've got to press the home button and remove the app from recently used to use it again.

It's not a big problem, just a bit annoying.

Greetings from the Netherlands

P.S. I will try to translate the language file soon! After this week I've got more free time on my hands:)
[Galaxy S III Android Development] JustArchi:
Reproduced successfully. However I'm wondering if it's not global CM issue, because afaik camera is more or less untouched.

As for now I suggest using Focal instead.
[Galaxy S III Android Development] MuerteDiablo:
Yeah I'm using Focal but can't use that one from within whatsapp or other applications. It doesn't show up there..
[Galaxy S III Android Development] ez321:
Accidentally lost the default Archi audio profile settings in Boeffla kernel app, can anyone post the settings ?
[Galaxy S III Android Development] JustArchi:
Hey raylogic.

Which version did you test? Is it 4.2.2 leak or official 4.1.2?

Because basically you can easily use f.e. Googy Max Kernel with dual-boot feature to have AD 2.0.1 and any Sammy 4.1.2 rom in the same time.

If you can give me more detailed info on which Sammy roms screen mirroring works - it would be great. Because if it works on XXUFME7 but on AD 1.6 it doesn't then I'll be happy to look into this issue and hopefully fix it. But I'm not sure if it's attached to AD 1.6 because AD 1.6 didn't change that much in terms of XXUFME7, especially framework and kernel stuff.

You can also try oldstable ArchiDroid 1.5.3, it's based on 4.1.2.

Anyway if it works on any 4.1.2 Sammy ROM then you can obviously use Googy Max Kernel with dualboot feature and have AD 2.0.1 in the same time as well. However if it works only on 4.2.2 XXUFME7 leak then it's not possible.

Hope I helped a bit :fingers-crossed: