yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] xc-racer99:
I'm using the default toolchain. Trying to debug random errors for a tiny bit of extra performance has never seemed worthwhile to me.

With the pin unlock, I guess I didn't setup that part of the RIL correctly. It's a bit hard for me to test when my variant uses a different modem (which has subtle differences).

Interesting, it's looking like the static busybox included isn't working for you. Perhaps it was a bad download, have you tried re-downloading the zip? Another option (after verifying that a new download is the same as the old one) is to replace the busybox file in the zip with one from the AOSP zip. The updater.sh appears to be failing when it's trying to set the log file, so another thing to try is to remove the folder /sdcard/aries from your SD.

The adb issue is typical - since you haven't explicitly allowed ADB yet (since you haven't booted up), you can't access ADB. One of the security features of Android that is annoying for debugging:D
[Galaxy S I9000 Android Development] davejohncole:
I downloaded the original file again and the files are identical. md5sum matches the value on the file host.

I replaced busybox in the lineageos zip with the one from your aosp zip and I still get a segfault when running fdisk.

rm -rf /sdcard/aries and booting again... Have to go to work now so I am not sure if this final step changes the boot. Will report back once I get to work. :)

BTW. Thanks for persisting with this. I am happy to keep working on this if you want to continue.
[Galaxy S I9000 Android Development] angelcalibur:
could be interreting to build with another TC.

If you want, you can try with our optimisation :

<project path="prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9" name="AOSP-JF-MM/platform_prebuilts_gcc_linux-x86_aarch64_aarch64-linux-android-4.9" groups="pdk,linux,arm" remote="github" revision="aosp-7.1.1" />
<project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" name="B--B/Custom_Toolchains" groups="pdk,linux,arm" remote="github" revision="arm-linux-androideabi-4.9-Linaro-generic" />

And if you want, you can follow our AOSP optimised build in our git :

https://github.com/AOSP-JF-MM/platform_manifest/tree/aosp-7.1.1

Dev leader is really busy since 2 month, and build for S4, LG G5 and Xiaomi Mi5 device.

But our build are really awesome. make it could be the same for galaxysmtd device.

Impossible for me to build, my old comp is not able to build any nougat Rom :crying:
[Galaxy S I9000 Android Development] xc-racer99:
Thanks for the options. Unfortunately, I don't have a ton of time to dedicate to this project, particularly since I have a different variant. I'm happy with the performance I'm getting on AOSP so I don't see a reason to change at the moment.
[Galaxy S I9000 Android Development] davejohncole:
I forgot to add after getting to work... It is still stuck in the boot animation and adb logcat never stops "waiting for device".
[Galaxy S I9000 Android Development] xc-racer99:
Ok, you'll never get past the adb issue because of secure adb - which really sucks for debugging...

Does the AOSP build work? You should be able to get adb while booting up on those builds because they use "insecure" adb.

I'm not sure exactly what to try next, seeing as I don't have the variant I can't suggest a magic bullet. Maybe try getting a 6.x ROM to work first, then flash again? The one last thing I can think of trying is if you output your /sdcard/aries_mtd.log - it might have some interesting info in.
[Galaxy S I9000 Android Development] xc-racer99:
Yeah, the shader errors are typical. Our graphics chip can't handle everything Android tries to throw at it but it shouldn't really matter. The selinux errors are not important as you'll notice they're followed by "permissive=1" - so it's just spitting out an error.

The big thing that jumps out to me is

01-02 23:51:40.785 126 137 D vold : Preparing: /data/system/users/0
01-02 23:51:40.785 126 137 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
01-02 23:51:40.785 126 137 E vold : Failed to prepare /data/system/users/0: No such file or directory
01-02 23:51:40.785 126 137 E vold : Failed to prepare user 0 storage
01-02 23:51:40.786 1 1 I vdc : 400 127 Command failed
01-02 23:51:40.787 1 1 I vdc : vdc terminated by exit(144)

Have you done a wipe of /data? Can you try formatting /data as ext4 or f2fs (whichever you're currently not using)?

FYI, you can save your logs as .txt files and attach them to your post to keep the length down. Once you have enough posts here on XDA to be allowed to post links, you can post a full logs to sites such as https://paste.omnirom.org/ or http://pastebin.com/ and then post links to them.
[Galaxy S I9000 Android Development] davejohncole:
That was the problem! I reformatted /data as ext4 and then AOSP booted! Thanks for persisting with me.

I have attached a short adb session and the boot logcat in case it has something of interest to you.
[Galaxy S I9000 Android Development] Black Manta:
Is there any way to fix (or whatever) the black status bar and black background if you pull down the status bar? :)
[Galaxy S I9000 Android Development] xc-racer99:
That's because we're a low-ram device. You can edit your build.prop and remove the low-ram override but you'll use more RAM and probably get less performance.
[Galaxy S I9000 Android Development] angelcalibur:
Maybee he can use the deviltools : https://xdaforums.com/showthread.php?t=2276036

And in memory management, change ram setting to maximum ram (brake cam)

and in Zram setting, choose 30%

overclocking device to 1400 mhz is stable for me on CM13.
[Galaxy S I9000 Android Development] nchc:
[MENTION=5891038]angelcalibur[/MENTION] reckon an optimised slim build would reduce ram usage for S1 or would the ram efficiency etc be of little benefit?
[Galaxy S I9000 Android Development] angelcalibur:
between lineage and slim, i think you have a lot of difference between them for rom usage.

a simple AOSP rom, without any feature could be more lite to reduce ram, but i9000 is really an old device you know...

I've tested to flash lineage 7.1 rom, and installed deviltools and i confirm, you can't change anything to increase Ram.

The only things you can change is the overclocking for CPU, but rom is really instable...

i've got bootloop every 2 minutes ! :silly:
[Galaxy S I9000 Android Development] xc-racer99:
There's a reason the thread is labelled "AOSP 7.1 ROM/Discussion" and "LineageOS". It's probably possible to get things running better, but I don't have the time/desire to do so since I'm back to using AOSP. All my sources are uploaded, so anyone/everyone is welcome and invited to run off their own custom builds/make improvements.

Available RAM is already pretty much at maximum due to CMA since I prefer having access to the camera at all times (again, someone could compile a bigmem kernel if they want to). Unfortunately, Lineage seems to use the hardware decoding when doing simple things such as viewing pictures in the Gallery (hence why it often stops), plus it has a lot higher RAM usage overhead than AOSP (so the allocation of the CMA areas fails a lot more often).
[Galaxy S I9000 Android Development] Draal:
Hello Developers,

I think there is potential in android 7.0/1 for the SGS. My observations shortly:

Alpha cm 14.0 from Coldwindofnowhere: stable, fast, battery-powered, but no hsdpa

Alpha cm 14.1 from Coldwindofnowhere: permanently crashes of android.phone.com

Alpha lineage os 14.1 from xc-racer99: sluggish, no root access (neither with superSU from xc-racer99)

Alpha AOSP from xc-racer99: stable, fast, wifi unstable, no root access (neither with superSu from xc-racer99)

thank you

Draal
[Galaxy S I9000 Android Development] xc-racer99:
And you'll notice they're all labelled "Alpha" - for a reason :D

Interesting that you're having difficulty with the root access, I haven't had an issue when using the Magisk root on my AOSP builds. I don't use SuperSU but it worked when I initially tested. I don't recall having issues with wi-fi either but I don't often use it. Does it just drop randomly and not reconnect or does it totally not work? I can try updating the kernel driver...

Just an FYI, I'm no longer building Lineage as I agree that its slower, plus it has a lot of bugs that aren't necessarily device specific (cough, BT, cough)....
[Galaxy S I9000 Android Development] Draal:
Hallo xc-racer99,

my observation is, that wifi randomly drop, but it reconnect after a request. Messages come however only after a request.

However, the root access is'nt so important at this time. Tuning will come later. ;)

Nice Day

Draal
[Galaxy S I9000 Android Development] angelcalibur:
Hi [MENTION=5414656]xc-racer99[/MENTION] !

Can you try to make another build with Android 7.1.1 release 26 ?

I've try to build it but impossible for me to make a build because of my old computer (too old to build android nougat).
[Galaxy S I9000 Android Development] xc-racer99:
Alright, try https://www.androidfilehost.com/?fid=529152257862708650 - as always, it's untested. Built on 7.1.1_r28 and the latest device-specific source code on my github.

Edit: Add for root, try installing the attached Magisk zip, then install Magisk Manager either from the Play Store or the Magisk thread at https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Edit2: If you're having difficulty booting, replace the boot.img in the zip with one from the previous AOSP build. I might have accidently used a kernel for my variant as opposed to the i9000's (just a guess...)
[Galaxy S I9000 Android Development] angelcalibur:
Thx dude!

i'will make a backup of my daily rom and will try yours!

EDIT : [MENTION=5414656]xc-racer99[/MENTION] build doens't boot for me and impossible to access to recovery...

Anyone can try the build ?
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, I wonder if it's the kernel that's no good.... Can you try flashing the kernel from the previous build with heimdall/Odin and see if that gets you access to recovery at least? I had no issues on my variant so I'm not sure what's up - I did make some changes to the onenand driver but they shouldn't have affected the i9000...
[Galaxy S I9000 Android Development] jupiter5700:
I try to flash with old (previous release) 7.1.1 kernel for i9000 and rom booting fine! As usually have trouble with 3G data carrier and some times after turn on\off airplane mode GSM fully lost connection.

UPD. OMG, after some reboots 3G was working!
[Galaxy S I9000 Android Development] xc-racer99:
Great, maybe I accidently used the kernel for my variant.... Glad it's mostly working.
[Galaxy S I9000 Android Development] jupiter5700:
Magisk work fine too! But 3G is unstable, often dissapear. May be some logs need to attempt fix 3g data?

PS/ Also new kernel from 8 of march is work fine! Just flash it! No problems.
[Galaxy S I9000 Android Development] xc-racer99:
What happens if you type in *#*#4636#*#* in the Dialer, click on Phone Info, and change WCDMA Preferred to GSM Only?

A radio logcat (adb logcat -b radio) might help, but I highly suspect it will show "GENERIC_ERROR" when trying to setup a data call. I don't have any issues with data myself, but I rarely use it and I have a different modem (the STE M5730 as opposed to the XMM6160 IIRC). Have you had a 7.x ROM that has data working all the time? I seem to remember complaints in 6.x as well with the stability of the data connection.
[Galaxy S I9000 Android Development] jupiter5700:
*#*#4636#*#* settings by defauls is on screenshots. adb log will be later. With latest CM13 from sooti i have no problems with 3g data and cellular stability.

If i turn settings to GSM Only then seems nothing happens, and only EDGE data available.
[Galaxy S I9000 Android Development] jupiter5700:
ADB Logs here http://www108.zippyshare.com/v/4R5wxRWC/file.html Also i will send you private message with links to videos related to three logs from five (by names).
[Galaxy S I9000 Android Development] angelcalibur:
Can you upload the kernel you used?

are you able to reboot to recovery in case of we need to go back to our old daily used rom?
[Galaxy S I9000 Android Development] jupiter5700:
Link to the Kernel is here. No problem with TWRP it starting by 3 buttons as usually... But new kernel also working fine, as i say before.
[Galaxy S I9000 Android Development] mkfsf2fs:
Hi, first of all thanks for working on i9000 support for newer android os versions.

When I try to build the sources i get some errors, I guess they might be pretty obvious for someone with a decent amount of experience - which i lack...

I obtained the aosp 7.1 r28 sources and added the manifest file. Then I 'repo sync'ed and called 'lunch aosp_galaxysmtd-userdebug' and finally make.

Do I miss some additional packages? (or is this expected - as you said the recovery might result in problems)

best regards

____________________________

edit: I solved the problem by changing

TARGET_USERIMAGES_USE_F2FS := true

to

TARGET_USERIMAGES_USE_F2FS := false

in

device/samsung/aries-common/BoardConfigCommon.mk

(What leaves the question how to build with f2fs...)
[Galaxy S I9000 Android Development] xc-racer99:
I haven't tried building recently at all, I think the issue is related to TWRP and how it looks for mkfs.f2fs. Try reverting e7c885655525daabfae8637dfbb8018f7f64a1de in bootable/recovery, IIRC.

Good luck!
[Galaxy S I9000 Android Development] mkfsf2fs:
:eek: actually it was my own stupidity... I forgot to apply the patches -.-

But I made another observation during building:

including ./vendor/samsung/omap4-common/proprietary/Android.mk ...
including ./vendor/samsung/smdk4412-common/proprietary/Android.mk ...
including ./vendor/samsung/toro/proprietary/app/Android.mk ...
including ./vendor/samsung/toroplus/proprietary/app/Android.mk ...
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
No private recovery resources for TARGET_DEVICE galaxysmtd
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'out/target/common/obj/APPS/Browser_intermediates/classes.noshrob.jack', needed by 'out/target/common/obj/APPS/BrowserTests_intermediates/jack.check.timestamp', missing and no known rule to make it

When I did not apply the "packages_apps_Browser.patch" patch I could get past that error... (But probably wont get the package?)
[Galaxy S I9000 Android Development] xc-racer99:
What's your local manifests like? I used the previous (Marshmallow) browser as the Nougat browser (Browser2) is just a webview test shell. You can probably remove the entire Browser project from packages/apps/Browser if you don't need a built-in browser.... Alternatively, you could sync up Lineage's browser or use https://github.com/Unlegacy-Android/android_packages_apps_Browser (aosp-7.1 branch)
[Galaxy S I9000 Android Development] mkfsf2fs:
The local_manifests are on aosp-7.1 as well as the patches. In the packages.xml it says:

<!-- Browser2 is just a webkit test, so use the old Browser -->
<remove-project path="packages/apps/Browser2" name="platform/packages/apps/Browser2" />
<project path="packages/apps/Browser" name="platform/packages/apps/Browser" revision="marshmallow-mr2-release" />

While the packages_apps_Browser patch in the patches repository (also aosp-7.1) changes in the opposite way:

-LOCAL_PACKAGE_NAME := Browser
+LOCAL_PACKAGE_NAME := Browser2

So that patch should not occur in aosp-7.1 to get the older browser...
[Galaxy S I9000 Android Development] mkfsf2fs:
Hey,

I have been running this rom for some time now and it works pretty well but unfortunately rild crashes very often and I have no cell connection anymore...

I have built the rom on my own (Android_7.1.1_r28 and Android_7.1.1_r40) (without the busybox patches (not required anymore)).

The crash eventually happens but I can yield it too by booting, unlocking sim, going to airplanemode and returning from airplane mode.

The crash message looks like this:

--------- beginning of crash
05-27 02:09:40.815 147 429 F libc : Fatal signal 7 (SIGBUS), code 128, fault addr 0x0 in tid 429 (rild)
05-27 02:09:40.823 134 134 W : debuggerd: handling request: pid=147 uid=0 gid=1001 tid=429
05-27 02:09:41.077 1415 1415 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-27 02:09:41.077 1415 1415 F DEBUG : Build fingerprint: 'Samsung/aosp_galaxysmtd/galaxysmtd:7.1.1/N6F27C/user05270005:userdebug/test-keys'
05-27 02:09:41.078 1415 1415 F DEBUG : Revision: '0'
05-27 02:09:41.078 1415 1415 F DEBUG : ABI: 'arm'
05-27 02:09:41.078 1415 1415 F DEBUG : pid: 147, tid: 429, name: rild >>> /system/bin/rild <<<
05-27 02:09:41.078 1415 1415 F DEBUG : signal 7 (SIGBUS), code 128 (SI_KERNEL), fault addr 0x0
05-27 02:09:41.078 1415 1415 F DEBUG : r0 00000000 r1 00000000 r2 00000008 r3 00000000
05-27 02:09:41.078 1415 1415 F DEBUG : r4 000000a5 r5 b21005f0 r6 00000000 r7 00000014
05-27 02:09:41.078 1415 1415 F DEBUG : r8 00000000 r9 b23f98b8 sl b2100500 fp b2100610
05-27 02:09:41.078 1415 1415 F DEBUG : ip 00000000 sp b18cc69c lr b18cc69c pc b23cf4ea cpsr 00070030
05-27 02:09:41.088 1296 1316 I art : Starting a blocking GC Alloc
05-27 02:09:41.088 1296 1316 I art : Starting a blocking GC Alloc
05-27 02:09:41.123 1415 1415 F DEBUG :
05-27 02:09:41.123 1415 1415 F DEBUG : backtrace:
05-27 02:09:41.123 1415 1415 F DEBUG : #00 pc 000534ea /system/lib/libc.so (je_arena_maybe_purge+417)
05-27 02:09:41.123 1415 1415 F DEBUG : #01 pc 00054475 /system/lib/libc.so (je_arena_malloc_hard+420)
05-27 02:09:41.123 1415 1415 F DEBUG : #02 pc 0005602d /system/lib/libc.so (je_arena_ralloc+1284)
05-27 02:09:41.123 1415 1415 F DEBUG : #03 pc 0006366d /system/lib/libc.so (je_realloc+200)
05-27 02:09:41.123 1415 1415 F DEBUG : #04 pc 00041c09 /system/lib/libbinder.so (_ZN7android6Parcel13continueWriteEj+308)
05-27 02:09:41.123 1415 1415 F DEBUG : #05 pc 0004292f /system/lib/libbinder.so (_ZN7android6Parcel12writeAlignedIiEEiT_+30)
05-27 02:09:41.124 1415 1415 F DEBUG : #06 pc 000118ad /system/lib/libsec-ril.so (RIL_onMultiClientUnsolicitedResponse+116)
05-27 02:09:41.252 430 518 W NativeCrashListener: Couldn't find ProcessRecord for pid 147
05-27 02:09:41.287 134 134 W : debuggerd: resuming target 147
05-27 02:09:41.287 134 134 E : debuggerd: failed to send signal 18 to target: No such process

The whole log is attached...

Do you have any idea what the cause could be? :/

Best regards

EDIT:

When switching to airplane mode the cellular connection indicator becomes "unconnected" but the label below still shows the name of the provider... perhaps the airplane mode is not entered properly?
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, the issue looks to be with binder... Can you grab a dmesg and a radio logcat (adb logcat -b radio) after it happens as well? That will tell what the last call was to the RIL that crashed it (it was an unsolicited request - ie originating from the baseband, based on the regular logcat you posted there) and also if there was some issue allocating memory in the kernel.

RIL is really quite hacked up on this device as its using a vendor-customized version that's designed for Gingerbread (or maybe even Froyo....).
[Galaxy S I9000 Android Development] mkfsf2fs:
Here are the requested logs. (Since my phone booted in airplane mode I had to first disable it and unlock my sim, afterwards I went back into airplane mode and turned it off again)

(I marked the spot where I turned airplane mode off in the radio log)

Hopefully, the logs will be conclusive :/
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, I'm not even noticing the crash in the radio logcat.... It seems that the lower level keeps going regardless of whether rild crashes or not.

Can you try replacing /system/vendor/lib/libsec-ril.so with the one attached to this post (remove the .txt extension which I added so I could upload it)? It reverts one of the changes I manually hexedited into it (https://github.com/xc-racer99/propr...mmit/5b010a3208131a8927d5812b12b833890a3935fe if you're interested).

I didn't really test locking/unlocking SIM cards when I did a bunch of the changes to the RIL, plus my variant uses a different RIL chip and blobs.
[Galaxy S I9000 Android Development] mkfsf2fs:
I have replaced the libsec-ril.so (which was located at /system/lib/ - guess doesn't matter) and have started my phone. seems like the rild daemon crashes because it cannot find the changed library name...

Now there isn't any cellular connection anymore (no matter if just booted or toggled airplane mode)

And thanks for pointing me at the hex modified blobs. I always wondered how that old libs are kept compatible :)

EDIT: I have changed the hex value for linking of libsec-compat.so (was libsec-compatcy.). Now ril starts... i will test it a bit.

EDIT 2: Thank you! That did it, rild is not crashing anymore :D

EDIT 3: Clean logs switching airplane mode on and off.
[Galaxy S I9000 Android Development] xc-racer99:
Oops, thanks for catching my typo. Interesting that its working now, I guess my "fix" did more harm than good.

Most of the hex modifications (and shims) that I've tried to port for our device (and variants) initially came from the Unlegacy Android project at https://gerrit.unlegacy-android.org/ - those guys are way, way smarter than I am :)
[Galaxy S I9000 Android Development] jupiter5700:
If your new RIL will working good then upload it, please.
[Galaxy S I9000 Android Development] mkfsf2fs:
Oh, sorry I totally forgot to do so.... here it is.

[MENTION=5414656]xc-racer99[/MENTION]: Don't be too hard on yourself ;) Without you we would not have an up to date i9000:D

btw.: Will you eventually update you repo (https://github.com/xc-racer99/proprietary_vendor_samsung)?
[Galaxy S I9000 Android Development] xc-racer99:
Sure, done. I've reverted the changes to the other variants' libsec-ril.so as well, hopefully correctly this time :)
[Galaxy S I9000 Android Development] jupiter5700:
Thank you for new RIL! It is work well now, no crashes, but i still have trouble with HSPDA data transfer. It is not work for me. "H" icon is not appear. Only EDGE (2G) mode work fine. Any ideas?
[Galaxy S I9000 Android Development] Puegue:
Excuse Me,

I have got the Samsung galaxy s i9000 with android 2.3. Now I have installed cwmr 3. I tried to install lineageos 14.1. The devise bootet, but only two "Samsung GALAXY S" texts appear. It bootet again and again. I think it was in a bootloop. I tried it lots of times but I can not fix it. I have seen some videos with persons who had got installed lineageos 14.1. I would be very happy, when you would help me.

Best regards
[Galaxy S I9000 Android Development] artyfarty:
You should flash a file called dbdata.rfs or something
[Galaxy S I9000 Android Development] Puegue:
Can you or someone else give me a download link for such a file.
[Galaxy S I9000 Android Development] MYEUHD:
The file is attached to this post

https://xdaforums.com/showthread.php?t=2184403
[Galaxy S I9000 Android Development] Puegue:
I have flashed the file "dbdata" with odin. Then I tried to install the lineageos 14.1 zip again, but it aborted again with this Error (attached foto).
[Galaxy S I9000 Android Development] xc-racer99:
That error always shows the first time you flash a ROM that has a different partition layout - that way the user doesn't lose all the data on his phone unless he's sure. Just flash the zip again and it should work install.

My only idea is trying to change the network type in the *#*#4636#*#* hidden settings menu (type this code into the dialer), but I would find it unlikely this would work. Another thing you could try is modifying your build.prop so that ro.product.device reads galaxys4gmtd - again, I would find it unlikely this would help, but you never know :)
[Galaxy S I9000 Android Development] Puegue:
Ok ... Thank You ....I tried flashing Lineageos 14.1 again, but now I am again in the Boot loop.