yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] xc-racer99:
Can't help you here, and I think that most users of the i9000 no longer use gapps as they slow down the device a fair bit. RIL is a little bit dodgy, as we're still using the blobs from 2.3.3 (and, needless to say, things have changed internally since then, not even getting into all the samsung modifications).

Hmm, the issue with Titanium backup sounds as if it doesn't have the necessary permissions/is trying to access the backups with the wrong method/path. You could try changing your backup folder to /sdcard (or one of the other variants of it).

With the taking space from /data, that is not the new internal SD, but rather the /system partition. More on this below..

Alright so this is where things get interesting. Based on your explanation and the command output provided (FYI some of it is truncated due to lack of permissions), you have a 32GB micro SD card, which apps can access normally. Now, if you browse to /sdcard with a file explorer (probably have to be a root explorer, but YMMV), do you get the files on the internal or the external card? If its the ones on the external card, then you have a problem. If you can see the files on the internal SD, then all is good and its likely that the apps haven't been updated to properly access the sdcard in Marshmallow (there have been a number of changes in how Android handles them).

Back to the partition scheme: Currently the data and system partitions share the first partition on the internal storage. What should be /sdcard is the second partition (and was back in 2.3.3 as well). The cache partition, along with a new datadata partition are on the fast internal Nand (the function of the datadata partition is to keep the speed at a decent level as the internal storage is slow). There's been some preliminary looking into merging all the partitions on the internal storage, so we can pick and choose what sizes, but its a pretty big undertaking and I think its petered out.

TL, DR: Sounds as if your internal and external have somehow been switched, check what files are in /sdcard and report back :D

Hope this makes at least some sense...
[Galaxy S I9000 Android Development] androidsfan:
The dodgy RIL could be the reason for the message about the locked SIM?

It surely is linked to the permissions. Directories on my new internal card and my external card have:

drwxrwx--x root sdcard_rw

While directories on my old internal card have:

drwxrwx--- media_rw media_rw

What I meant: Installing a new app (goes to /data) and downloading something (goes to /sdcard -- my new internal card) both reduce space on the same (only 1G) partition. See below.

Browsing to /sdcard I get the files and directories of a new internal sdcard: The directories Alarms, Android, DCIM, Download, Movies, Music, Notifications, Pictures, Podcasts, Ringtones, backups which are all empty except Android, Download (I already downloaded one file) and backups.

From the outputs of df and mount and using the Documents browser and "ES File Explorer" I gathered the following (incomplete) scheme:

/system on /dev/lvpool/system (available 590.6M, used 513.2M)

/data and /storage/emulated (sdcard -- my new internal card -- links to /storage/emulated/0) on /dev/lvpool/userdata (available 1.3G, used 478.7M)

/storage/6135-3862 (aka /mnt/media_rw/6135-3862, shown as "SanDisk SD" card in the Documents browser, as "SD card" in "ES File Explorer") on /dev/block/vold/public:179_25 (that's my external card)

/mnt/media_rw/40DA-07D7 (shown as "SD card" in the Documents browser, in ES File Explorer only accessible through /mnt/media_rw/40DA-07D7) on /dev/block/vold/public:179_1 (5.6G available, used 4.6G, that's my old internal card)

As /dev/block/vold/public:179_1 and /dev/block/vold/public:179_25 are both mounted rw as vfat, and then /dev/block/vold/public:179_25 is made available by fuse, I thought it should be possible to make /dev/block/vold/public:179_1 available in a similar way. (That would be the third solution/workaround from my original post.)
[Galaxy S I9000 Android Development] xc-racer99:
Yep, the RIL (radio interface layer) is the part responsible for any and all interactions with the SIM card and cell network.

Ok, now I understand your situation. Thanks for the very complete and well structured post (much better than mine).

Could you please post the contents of fstab.aries and init.aries.rc please (they're probably too long to go in a post, so pastebin or similar works well)?

You definitely do have something odd going on. I don't have an i9000 myself, but a T959P (a carrier variant with no internal SD) so I can't test this ROM and know if its just you or not. If you're good with potentially having to use Odin to go back to stock, I can send you some test kernels, etc to try.
[Galaxy S I9000 Android Development] androidsfan:
init.aries.rc: termbin.com/3s4h

fstab.aries: termbin.com/5n54

If need be: Could I use heimdall instead of Odin? Can I return to stock even if I only know that I had 2.3.3 on a gt-i9000? If so, I could try some test kernels etc.
[Galaxy S I9000 Android Development] xc-racer99:
Yep, you should be able to use heimdall just fine (in fact, that's what I use but most people use Odin cause they're on Windows so just mention it for simplicitys sake). AFAIK, there's no issues with returning to stock on the i9000 (I know there isn't on my variant, and I can't see why it would be different).

I have a theory for your issue: If you look at fstab.aries, there's the line

/devices/platform/s3c-sdhci.0/mmc_host/mmc0/*/mmcblk0 auto auto defaults voldmanaged=sdcard0:1,noemulatedsd,nonremovable

The "/*/mmcblk0" part is not proper syntax as per https://source.android.com/devices/storage/config-example.html - it should just be "*". So I think vold is reading that there's no sdcard0 so its setting up a /data/media "sdcard" to fill that spot and then mounting the external SD as per normal (eg like "Emulated primary, physical secondary"). I'll PM you a link with a build if you're willing to potentially have to go back to stock;)
[Galaxy S I9000 Android Development] xc-racer99:
You could try Samfirmware - you need to register for an account though. Most links on XDA will probably be dead.

I don't think so - the only place it appears is in https://android.googlesource.com/platform/system/vold/+/android-6.0.1_r63/main.cpp - and the comment above the kDefaultPrimary one is "* Flag that disk is considered primary when the user hasn't explicitly picked a primary storage location */"

You're right about the setprop line being commented out.

Yeah, its a pain that we have to reflash the entire kernel to update a single line in the ramdisk. Unfortunately, you have to have the entire Android source code downloaded to build the kernel... I do have a method where the ramdisk is stored external to the kernel, but its too late in the Marshmallow cycle to implement a new feature like that. If we get a stable-ish Nougat build, I'm going to push for that to be included in them.

FYI, my variant only has one external SD card which is manually partitioned into two. The first partition is vfat and mounted as /sdcard (primary storage, and the sdcard is a symlink, but you get it), while the second is f2fs/ext4 and is /data. My fstab.aries looks like

#Data on SD-EXT
/dev/block/mmcblk0p2 /data ext4 noatime,discard,nodev,nosuid,nomblk_io_submit,errors=panic wait,encryptable=footer,length=-16384
/dev/block/mmcblk0p2 /data f2fs rw,noatime,discard,nosuid,nodev,nodiratime,inline_xattr wait,encryptable=footer,length=-16384

# Micro SD Card
/devices/platform/s3c-sdhci.2/mmc_host/mmc1* auto auto defaults voldmanaged=sdcard0:1,noemulatedsd,nonremovable

I also have the setprop line in my init.aries.rc. I've had the nonremovable line there and removed it, I don't think it does anything in 6.0+ but no error is thrown for backwards compatability.

With the wildcards, it didn't need to be there prior to 6.0. I can't remember why, but before 6.0 we didn't have the second "/mmcblk0" part.

Also, I'm surprised that in the i9000's fstab, there is "voldmanaged=sdcard0:1,noemulatedsd,nonremovable" - the "1" means to use the first partition. With the LVM stuff, I'm not sure which partition it actually is, but I would have thought it would have been mmcblk0p2. Can you check the logcat output, specific for anything with vold or fs_mgr?
[Galaxy S I9000 Android Development] androidsfan:
This sounds very promising. If one simply could uncomment the setprop line in my init.aries.rc it already might work. Or what do you think? As you offered to help with some kernels: Could you provide me one where this would be the only change to the one from my current ROM (omni-6.0.1-20160309-galaxysmtd-HOMEMADE.zip)?

In case the first solution does not work, perhaps I could also try (with your help, that is :o) a version where as the only second change in my current fstab.aries the "/mmcblk0" after the wild card would be removed. Do you think that something else would be worthwhile to try?

My old internal sdcard is definitely mmcblk0p1:

fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 8069 MB, 8069840896 bytes
1 heads, 16 sectors/track, 985088 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 739328 5914592 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 739329 985088 1966080 c Win95 FAT32 (LBA)
Partition 2 does not end on cylinder boundary

Relevant lines in logcat output about my old internal sdcard might be:

[ 09-05 16:43:34.034 200: 293 V/vold ]
/dev/block/vold/public:179_1
--

[ 09-05 16:43:34.513 200: 293 V/vold ]
/dev/block/vold/public:179_1: UUID="40DA-07D7" TYPE="vfat"
--

[ 09-05 16:43:34.515 200: 293 V/vold ]
/dev/block/vold/public:179_1
--
[ 09-05 16:43:34.701 200: 293 I/fsck_msdos ]
** /dev/block/vold/public:179_1

This is exactly paralled by the entries about my external card:

[ 09-05 16:43:49.186 200: 293 V/vold ]
/dev/block/vold/public:179_25
--

[ 09-05 16:43:49.975 200: 293 V/vold ]
/dev/block/vold/public:179_25: UUID="6135-3862" TYPE="vfat"
--

[ 09-05 16:43:49.979 200: 293 V/vold ]
/dev/block/vold/public:179_25
--
[ 09-05 16:43:50.025 200: 293 I/fsck_msdos ]
** /dev/block/vold/public:179_25

There is nothing with fs_mgr.
[Galaxy S I9000 Android Development] xc-racer99:
I've sent you a PM as posting experimental kernels publicly is generally not a good idea;)
[Galaxy S I9000 Android Development] xc-racer99:
Nope, that looks like plenty of debug output. Try https://www.androidfilehost.com/?fid=24651430732237550 WARNING - no one else try this or you'll risk bricking your phone for no reward. The init.aries.rc and the fstab.aries are the ones from Lollipopi9000's github (aka from this ROM). Appears to be slightly different as the vold prop is not commented out in init.aries.rc.

Also, when you're in recovery can you do a data wipe please? Its possible that because there's a data/media device already, its using that by default.
[Galaxy S I9000 Android Development] androidsfan:
Your new kernel seems mostly to be working as desired. So far at least :) Thanks a lot. But does that mean that I for every now ROM have to ask somebody to compile a kernel for me? Is there somewhere a simple introduction how to use a repository as yours to compile one's one kernel?

(I still have the problem with titanium backup and it seems also Super Backup is not fully working, I will experiment a bit. There are other minor problems for the moment, but it's not clear that they are related to the new kernel/ROM. I have also the impression that things got a bit slower again, but that might be just an impression.)
[Galaxy S I9000 Android Development] xc-racer99:
I'm not sure exactly why your setup did what it did. I would be surprised if its a device-specific thing. I suspect something just was messed up somewhere along the line and that you'll be good from here.

Totally possible that things are slower than they were - its my kernel which doesn't have a lot of the optimizations that the default kernel has.

Unfortunately for us, to build the kernel/boot.img, you need either the full source code or several prebuilt binaries from someone who has the full source code (and even then, you need to do some modifications). If you have disk space and a decent internet connection, you can experiment with building the ROM yourself - for Omni, visit https://github.com/omnirom/android and its similar for all ROMs. When it comes to device-specific packages, you'll need a local manifest. I don't know exactly what the i9000 uses, I have a set of patches I apply which are in my aries-common repository and they should be all that's needed for the i9000 as well...
[Galaxy S I9000 Android Development] noni-06:
Hello,

Is someone can tell me if there is a 'real' solution for the SDCard problem?

The ‘sdcard ‘mounted as /mnt/media_rw/073D-17E4 is unusable (no app can write or read it, only root or recovery can) and physical SDCard is not display at all?

Thks
[Galaxy S I9000 Android Development] Sunnymen1975:
The link to the gapps on the first post is not valid :(
[Galaxy S I9000 Android Development] PARUSA:
Hi all,

I have installed "omni-6.0-20151206-galaxysmtd-HOMEMADE.zip" on my good 'ol i9000 but got stuck on boot logo only. What should I do? I don't want to return stock 2.3.6 again. Thanks in advance.
[Galaxy S I9000 Android Development] John D J:
You might have missed a step try wiping dalvik, cache and data in recovery then try restarting.
[Galaxy S I9000 Android Development] PARUSA:
Hi,

so, As I have installed JVU 2.3.6 with CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS. USB on debug mode + checked install from unknown sources...

on the cwm 3.0.0.5, I have wiped the data/factory reset, wiped the cache, and the dalvik.

install zip from sdcard, selected the "omni-6.0.1-20160309-galaxysmtd-HOMEMADE.zip" from internal sdcard...

i keep on getting error status (7). it states I need to use the update.zip which I did and still receiving error.
[Galaxy S I9000 Android Development] sooti:
In case anyone is wondering what the progress of android-7.0 is....

there is non... I mean xc-racer-99 has made some great progress on his device but galaxysmtd has issues with LVM on boot, i've spent too much time on this thing already... might be time to finally give up on the device.. it is almost 7 years old after all.

biggest problem with the device is that its an old samsung that uses weird partition layouts, old buggy closed source exynos crap, and an outdated kernel... even on 6.0 lets be honest, it ran pretty bad, it might be ok for phone calls and txt and as a cool concept but its way too much work. that's why i love qualcomm based devices, they have an open source community and release everything + updates from time to time. exynos has always sucked .

So unless some major progress on the i9000 variant is made I think its time to bury it for now.

I'll let everyone know if some major breakthrough happens but for now its goodbye!
[Galaxy S I9000 Android Development] xc-racer99:
Sad to see you go, you've done some great work on this device. However, I do agree that the time for this phone is coming to an end. I do still use my variant as a daily driver - but I basically just do the odd text here and there.

That being said, I do have a functional build of 7.0 on my variant which does not use LVM. Nothing really seems to be broken (that wasn't broken in 6.0 or before - ie no tv-out and selinux in permissive mode). If someone wants to potentially mess up their phone and test builds for the i9000 for me, let me know.
[Galaxy S I9000 Android Development] ThomasHessen40:
Would like to test times where you can load it

thank you
[Galaxy S I9000 Android Development] DmitTrix:
I can test. I have this phone as a spare one, so I'm OK with taking some risks :)

I can't promise fast turn-around times, though…
[Galaxy S I9000 Android Development] xc-racer99:
I've had it confirmed that it doesn't work. That being said, I have yet to get logs so I have no idea why it didn't work. If you want the busted build to test and grab the logs from /sdcard/aries after you've bootlooped, it's uploaded at https://www.androidfilehost.com/?fid=457095661767102987
[Galaxy S I9000 Android Development] jkd:
Is there tv-out ? Thanks
[Galaxy S I9000 Android Development] Alokhacker:
which build is it?
[Galaxy S I9000 Android Development] xc-racer99:
All of em are broken. Don't bother testing any of them, I've got the logs I need (for now). I'm in contact with [MENTION=6794010]Coldwindofnowhere[/MENTION], among others, and we're working on getting something booting (7.0 has booted on Captivate, so there's hope).

I'll post here again if/when I need another tester.
[Galaxy S I9000 Android Development] xc-racer99:
If anyone is interested, https://www.androidfilehost.com/?fid=385035244224386929 has a shot at working. If it installs properly and boots, please grab a logcat and dmesg for me. If not, please send me the contents of all of /sdcard/aries/*, /sdcard/aries_mtd.log, and/or /sdcard/bml_over_mtd.log

Thanks very much.

Edit: This reportedly does boot!

Edit2: If you flash this

a) Don't try to format any SD cards that Android prompts you too. This will mess up the partition scheme totally...

b) If you want root, read my instructions in http://xdaforums.com/showpost.php?p=69245956&postcount=3
[Galaxy S I9000 Android Development] Alokhacker:
booted successfully... thank you very much...it looks good & its smooth
[Galaxy S I9000 Android Development] xxraid:
booted successfully. GREAT JOB :good:

I'm very happy to know that somebody cares about i9000 and tries to run android 7 on it.

there are some logcat, dmesg and kmesg files

problems on my phone:

* no sim

* reporting corrupted sd card

* tried to run TWRP and change format of file system on sd card, but I'm unable to start TWRP. Maybe something broken with my installation. I'll try to reinstall later. But OS is working.

new post:

I found, that my internal and external sdcards are there (see attached image). The brokend sdcard is another partition. Maybe those with recovery partition. So I formated it, when clicked on repair sd card dialog from running android.
[Galaxy S I9000 Android Development] xc-racer99:
Great, I'll have a look at the partition issue. I suspect the TWRP error is the same kind of issue, but TWRP is not 100% stable on 7.0 yet.

With the no sim issue, could you please grab me a radio logcat? Instructions at http://xdaforums.com/showthread.php?t=2185929 if you need them.
[Galaxy S I9000 Android Development] jupiter5700:
It is fantastic! It is fully worked Android 7 on Galaxy S i9000! RIL is working, i make calls, but GSM is unstable. Wi-Fi working, Browser working. Long sim detect. Some times sim not detect after reboot and Baseband unknown in settings with it. Also trouble with sd-cards. I have one soft reboot while incoming call, i cant answer on it, black screen with incoming ringing. Thank you very much! :good:
[Galaxy S I9000 Android Development] xc-racer99:
Great, glad RIL is working (for the most part). I did a fair number of changes to it so that we didn't need many hacks. I have the same issue with the SIM taking a while to detect but about 19/20 times it does detect properly.

Not sure what the issue with the soft-reboot on incoming call is. Could be either graphics drivers related or RIL related. Only logs will tell me.
[Galaxy S I9000 Android Development] jupiter5700:
After formatting all broken sd-cards with Android 7 and manual reboot ROM is dead. I mount sd-cards in TWRP and was formating internal SD by Windows 7, then i get 7.41Gb capacity instead 5,xxGb. Is System partition merge with Data and with internal SD?
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, for the TWRP issue, can you do the following (presuming you can't access TWRP at all and have access to adb):

adb root

adb shell

mkdir /data/ramdisk

mount /dev/block/mtdblock1 /data/ramdisk

exit

adb push ramdisk-recovery.img /data/ramdisk

where ramdisk-recovery.img is the file attached to this post. If you do have access to TWRP, then just replace the ramdisk-recovery.img in the zip with the one attached to this post and flash the zip.

Ouch, it sounds as if that is what happened. You'll probably have to use Heimdall/Odin and go back to stock (just my suspicion, I couldn't say for sure). 7.0 must do something differently - when you formatted the broken SD it must have wiped all the partitions.
[Galaxy S I9000 Android Development] Alokhacker:
sim is working for me but if we put external sd card sim card doesnt work, if we remove it sim card works. it suppoerts both ext4 and f2fs partitions for data and system. with f2fs rom is much smoother though. It feels smoother than marshmallow and lollypop. home button is not working. sdcard is the only major issue i guess.
[Galaxy S I9000 Android Development] jupiter5700:
With 1Gb external SD-card sim working normally.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Soon ...

Big thanks to xc-racer99.

Still getting issues with RIL, HWacceleration and storage.
[Galaxy S I9000 Android Development] xxraid:
Radio logcat is attached. Thanks.
[Galaxy S I9000 Android Development] xc-racer99:
In the mount, switch /dev/block/mtdblock1 to /dev/block/mtdblock2 My bad, I gave you the wrong partition.

Basically, what I've done with the partition system is that instead of storing the ramdisks in the kernel, the main ramdisk is stored on the partition located on /dev/block/mtdblock1 and the recovery ramdisk is stored on /dev/block/mtdblock2 There should be a ramdisk.img in /data/ramdisk as that is where we (hopefully) mounted /dev/block/mtdblock1

With your sim issue, it appears that you don't have a modem.bin in /radio. You should be able to copy the one from the install zip to /radio.
[Galaxy S I9000 Android Development] xxraid:
I recovered TWRP (using heimdal factoryfs and another build of omni 6.0.1)

Then I wiped everything including /system /data and /sdcard and did fresh install. Succeeded.

TWRP works for me now.

What doesn't work: 1) there is still corupted sdcard problem, but sd internal and sd external card are loaded - some applications are not working because of that, for example camera 2) unstable SIM; after boot i'm prompted for PIN, afterwards it drops down, afterwards it runs again (after 1st boot there was some IMEI warning - see attached image) 3) must wake up with power button, home button is unable to wake up 4) camera is unable to work because of corrupted sdcard

See attached logcat files + images