yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] xc-racer99:
Alright, thanks for the complete rundown on errors. I'll try to go through them:

Bluetooth - having difficulty activating is not surprising. Android technically doesn't support non BT LE devices such as ours - I had to hack in support for no LE/SMP/GATT (the supporting parts of the BT stack AFAIK) with the patch https://github.com/xc-racer99/android_patches/blob/aosp-7.1/system_bt.patch. There's nothing I can really do about this. If you read the OP, it says

This was for 7.0, I guess it's changed slightly in 7.1 so I'll update the OP.

Data - this sounds totally bizarre. I wish I had an i9000 to test this. One of the big differences between the i9000 and my device, the SGH-T959P, is that you guys use the (infineon?) XMM616 for your modem while mine uses the M5720 by STE. I have yet to have an issue with data when I've tested it on my variant. Again, I'm afraid I can't do too much about this :(

Wifi - this sounds weird. There's some noise in the logcat, ie "12-24 02:50:04.778 W/CommandListener( 164): Failed to retrieve HW addr for wlan0 (No such device)". This is very surprising, I have nothing like this in a logcat on my device. I'm thinking perhaps that the MAC address wasn't properly setup. Could you please run "adb shell getprop | grep macaddr"? The RIL actually sets the macaddr so these two issues might be related. Did you check the md5 of the zip after downloading? It almost sounds like a bad download/ flash. The other thing is that yours is a special hardware model which doesn't like having the wifi driver built into the kernel (I did see a reference to this in a commit from the CM10.1 days). [MENTION=6794010]Coldwindofnowhere[/MENTION]'s CM14 has it as a module so it might be working there.

Home button - I probably messed up the keylayout somewhere. My device has a capactive home button as opposed to a hard button. Please try pushing the attached files to /system/usr/keylayout after removing the ".img" at the end of the filename (to get around XDA's filetype filter).

Corrupt SDCard is probably my fault. Please try the new build at https://www.androidfilehost.com/?fid=529152257862690355 as I think I've found and corrected the issue.

Unfortunately, your logcat is very "chatty" - basically android prevents things from creating too much logspam. This sucks for debugging as we lose many lines, so to turn it off run

adb logcat -P ""

right at boot

Since we're having so many issues with mobile network/wifi/bluetooth, I'm wondering if our netfilter code in the kernel isn't working properly.... The thing against this theory is that things work on my variant.
[Galaxy S I9000 Android Development] Ano59:
I just checked file integrity using MD5, it's sane. I'll test and answer about other issues later ! :)
[Galaxy S I9000 Android Development] DanielBR911:
Merry Christmas guys.

I just installed the latest build.

1 - The Home button is now working.

2 - The SD Corrupt problem still persists.

When I open the Gallery the following message appears: "No external storage available". I have checked the permissions and is allowed for storage.

In managed android file I tried to delete a file. It returns an error saying that it is not possible to delete the file.

I installed Open Camera and can not save the photo. ("Failed to save photo").

thanks,

Daniel
[Galaxy S I9000 Android Development] xc-racer99:
Merry Christmas!

Odd that the home button is now working, did you push the keylayouts from my post or not? I didn't change anything in the build...

So, looks like my SDCard issue wasn't the right one. Could someone please send me a logcat of CM14.1? I'm curious how it deals with the lvm partitions. I suspect what's happening is that Android is finding the second partition which holds the LVM partitions /system and /data and since it can't mount these as fat it just barfs the whole disk. Just another thing that Android technically doesn't support anymore... The other thing is that it can't find a primary partition to link to, from logcat

12-24 02:47:20.509 D/vold ( 128): Linking to /mnt/user/0/primary
12-24 02:47:20.510 W/Vold ( 128): Failed to link to /mnt/user/0/primary: No such file or directory

while it should be something like

12-24 12:32:53.599 137 143 D vold : Linking /storage/emulated/0 to /mnt/user/0/primary

Only it would be /storage/UUID since the i9000 doesn't have emulated storage.
[Galaxy S I9000 Android Development] DanielBR911:
1 - I just push the keylayouts from your post.

2 - At moment I'm using CM 14.1. Here my Logcat and Dmesg :

View attachment dmesg.log

View attachment logcat.log

Thanks,

Daniel
[Galaxy S I9000 Android Development] xc-racer99:
Great, thanks. I think I found the CM (LineageOS?) commit that fixes storage for you guys (https://github.com/lineageos/android_system_vold/commit/55982f4dee0f89eb41b7e0e522bd2392b6a69e18).

I'll run off another build and let you test :) With the keylayouts, could you check and make sure that the needed change is only the cypress-touchkey.kl file? To do this, simply change "key 102 HOME WAKE" to "key 102 HOME" in /system/usr/keylayout/aries-keypad.kl on your CM14 ROM. I believe it's only the one file that needs changing based on the Android docs at https://source.android.com/devices/input/key-layout-files.html and the validatekeymaps tool.
[Galaxy S I9000 Android Development] DanielBR911:
View attachment dmesg.log

View attachment logcat.log
[Galaxy S I9000 Android Development] DanielBR911:
GPS Test (permissive)

View attachment dmesg.log

View attachment logcat.log
[Galaxy S I9000 Android Development] xc-racer99:
New Build Uploaded!

Changelog for 2016-12-26

Home button should now work

SD card/internal storage should work properly

Added ability to have a larger /data (see below)

Since some people have said that the /data partition is now too small, I've devised a method of being able to use either the whole microSD or just the second partition of the microSD for /data. To "activate" it, run "adb shell touch /cache/.sd_as_data" if you want to use the entire microSD as /data, or "adb shell touch /cache/.sd2_as_data" if you want to use a second partition on the microSD as /data. In both cases, the respective partition must be formated either as ext4 or f2fs. To remove this and go back to the "regular" partition scheme, simply delete the file you create from /cache or format /cache. Please note that because this relies on the file in /cache, anytime you wipe /cache you will need to recreate the file. This is totally opt-in and nothing will change if you decide not to use it. Please note it may cause your speed to decrease if you use a slow microSD card. Big thanks to [MENTION=7925883]DanielBR911[/MENTION] for testing.

For those interested, the kernel patch is located here

Download from https://www.androidfilehost.com/?fid=385035244224408087
[Galaxy S I9000 Android Development] HikingMoose:
Nevermind,

I answered my own post with a little more digging.
[Galaxy S I9000 Android Development] Monfro:
[MENTION=5414656]xc-racer99[/MENTION]

Can You please compile a kernel for Captivate?

Everything is the same as I9000, except for hardware keys which are coded into kernel.

It would be great to port Nougat to Captivate.
[Galaxy S I9000 Android Development] xc-racer99:
Alright, have a look at https://www.androidfilehost.com/?fid=745425885120696775 - rename it to boot.img and replace the boot.img in the zip with this one.
[Galaxy S I9000 Android Development] Monfro:
Thank You very much!!!
[Galaxy S I9000 Android Development] Technohacker1995:
Guys i wanted to know whether the Galaxy S is able to handle AOSP Nougat because I was planning to build AOSP for the Galaxy SL.

Do reply soon :)

Cheers!

Technohacker
[Galaxy S I9000 Android Development] xc-racer99:
Yep, it can handle it. It's not perfect, but it runs pretty darn well (without gapps) for a 6 year old phone. I use it as my daily driver although I'm a very light user.
[Galaxy S I9000 Android Development] Technohacker1995:
Do you think the Galaxy SL can handle it?

Cheers!
[Galaxy S I9000 Android Development] xc-racer99:
Looking at the specs, probably it will run OK. Just don't expect a quad-core phone:laugh:

For comparison, I think 7.1 runs at about the same speed 5.1 or 6.0
[Galaxy S I9000 Android Development] Technohacker1995:
okay thanks! :laugh:
[Galaxy S I9000 Android Development] Alokhacker:
Superb rom... Very fast, very stable and amazing battery life. How do we root our device?
[Galaxy S I9000 Android Development] xc-racer99:
From the OP:

Basically that post contains a custom Magisk and SuperSU zips that you can use to root with.
[Galaxy S I9000 Android Development] Alokhacker:
If I flash Magisk-v9-SGS.zip nothing happens but phone boots normally, if I flash SuperSU-2.79-SR1-SGS.zip phone doesnt boot. stuck at boot animation. Same problem I face when I use superSU-2.79 SR1 but with superSU-2.79 SR3 its booting normally but no root, I guess your SuperSU build is based on SR1, SR3 based may work properly.
[Galaxy S I9000 Android Development] xc-racer99:
Ok, I guess there's been some changes to selinux with SuperSU - it worked when I initially tested, looks like I'm going to have to test again... Can you get some logs please? I'm curious what is going on.

Edit: And can you also please try the attached SuperSU zip? It's based off of 2.79SR3 but is untested

With Magisk (what I use, FYI), it's not an all-in-one root solution. You then need to flash the root Magisk module (https://xdaforums.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921 - I use r266-2) and install the PHH Superuser app (either from the Play Store or F-Droid).
[Galaxy S I9000 Android Development] xc-racer99:
New Build Uploaded!

Changelog for 2017-01-19

Updated interactive governor - should result in fewer slowdowns if you use this governor

Changed low memory killer parameters so it kills a little quicker (ie before it runs out of memory)

Disabled a bit more background stuff to hopefully free a bit more memory

Fixed/cleaned up the shims that are used for the RIL - should prevent SSL issues (eg with Hotmail accounts) as well as being slightly faster and more reliable

Selinux is still in permissive mode (a dmesg could possibly help me in putting this to enforcing, if people are interested). I still don't know if the TWRP included in it is functional or not (someone can let me know, I guess :))

Download from https://www.androidfilehost.com/?fid=745425885120701744
[Galaxy S I9000 Android Development] Alokhacker:
Flashed this one and it worked. may be the original SuperSU SR1 had some issues. This one is working fine
[Galaxy S I9000 Android Development] jupiter5700:
Bug report. Some times black screen issue apeared. Video hardware decoding mostly not support. Some times i cant accept calls, only black screen with ringtone, home button is not help as erlier.
[Galaxy S I9000 Android Development] xc-racer99:
Alright, for the black screen issue, can I get a bit more info please? Have you tweaked the performance settings (governors, frequencies, under/overvolting etc) at all? Does the screen just not turn on? If you get a dmesg, do you have something like

PVR_K:(Error): PVRSRVSwapToDCBufferKM: Failed to get space in queue [1456, ../../../../../../kernel/samsung/aries/drivers/gpu/pvr/deviceclass.c]

in it? This is a bug in 7.x, presumably in the kernel since and I think it's related to a timing issue where part of the display system is shut down too early.

With the video hardware decoding issue, can you get a dmesg? I suspect that the system is low on memory and that the MFC is failing to allocate the CMA memory region. You can adjust the low memory killer so that it kills less frequently to attempt to fix this issue.

The black screen with the ringtone might be related to the same black screen issue above - does the phone make noise but you just can't pick up?

Is the home button entirely broken? I haven't changed anything with it on the last build.

Also, if anyone is interested, I could probably upload a build of LineageOS for the i9000 - still no theme manager though.
[Galaxy S I9000 Android Development] Alokhacker:
Home button works, it does not wake device up. Device hangs very often. which governor scheduler do you use? does kernel support zram/swap?
[Galaxy S I9000 Android Development] jupiter5700:
Yes, sometimes i can't picup incoming calls. I do not tune kernel settings. All is by default. Sorry, but i can't take dmesg info due to i was return to 4.2.2. Cause i9000 is my primary phone.
[Galaxy S I9000 Android Development] xc-racer99:
Interesting, I don't have the device hanging on me much at all. I use the default settings, ie interactive governor, no OC, ROW scheduler. There is no zram/swap in the kernel as it uses CMA and the two don't play well together. The home button doesn't wake the device because AOSP doesn't support this (it's a custom ROM thing). Since my variant doesn't have a physical home button I won't implement this.

Ok, thanks for the info. I'll try to figure out what's up with all of the power management issues... Absolutely no guarantees though.
[Galaxy S I9000 Android Development] angelcalibur:
Hi!

Need to update my old galaxy S and i wanted to know if this aosp build is working for daily use?

And i'am using slimkat rom, and i want to know how to update to another rom, with marsmallow or nougat if possible...

Because i've got some issu when flashing (i've got statu 0 or 7, impossible to mount etc...).

thx!;)
[Galaxy S I9000 Android Development] jupiter5700:
As we know, CM project unfortunately was closed. Okay, xc-racer99, it will be interesting to test LineageOS for i9000!:good:

May be later we can see theme manager in LineageOS?
[Galaxy S I9000 Android Development] xc-racer99:
Alright, a build for the i9000 of LineageOS is at https://www.androidfilehost.com/?fid=457095661767134629

Totally untested, no idea if it boots. My variant needed only the CM changes, so hopefully the i9000 is the same... Sources are on my github under the cm-14.1 branch

Edit: Sounds like the recovery included in this build is non-functional. Replace the ramdisk-recovery.img in the zip with the one from one of my AOSP builds and then try flashing it. Some people have managed to get it to boot, others haven't. YMMV. First boot (if it does boot) is incredibly slow.
[Galaxy S I9000 Android Development] jupiter5700:
Thank you for lineageOS i9000!!! Just flash LineageOS to my i9000, but i have only endless boot with boot animation. May be i do somthing wrong. Also from TWRP i cant reboot or turn off phone, always i have only simple reboot to TWRP. What data formatting system is need for this LineageOS rom? I try with ext4. Will try with f2fs later.
[Galaxy S I9000 Android Development] xc-racer99:
Guess I should have warned that the first boot is extremely slow. It took roughly half an hour on my device from what I recall. Part of the reason is that I had to disable dexpreot because if I didn't I'd start getting random crashes (this is the case for all Lineage builds, they introduced a bug somewhere and haven't fixed it....). ext4 should work just fine

Your TWRP issue sounds weird, I don't recall that on my device. Maybe the TWRP team merged something recently that I missed. If you replace the ramdisk-recovery.img in the zip with the one from my AOSP build then you'll get that recovery build.
[Galaxy S I9000 Android Development] jupiter5700:
Okay, finally rom was start successefully! RIL work, SMS work, Camera work. Sometimes some apps crashes with error, Gallery for example (after exit gallery). Long switching between landscape and portrait mode (also on AOSP 711). Once the phone is fully hung up, when I hung up the phone after a call. And as usualy i have problem with 3G data (not work for me).
[Galaxy S I9000 Android Development] ioannis_m:
Can you please tell me the proper way to flash the lineageOS on I9000?

I got a bootloop and during flashing ended in TWRP system and data not mounted.Tried it again from 2.3.6 with odin > 10.1 cyanogen > 10.2 > 4.4.2 > 5.1.1 omni > 6.0.1 omni all booted succesfully but on 14.1 system and data not mounted.:confused:
[Galaxy S I9000 Android Development] xc-racer99:
Sounds like the TWRP I included with the LineageOS build doesn't work properly.... Replace the ramdisk-recovery.img in the zip with the one from my AOSP build and try again???? As I noted, since I don't have this variant I haven't actually tested any of these builds but have run them off based on what works on my variant (which uses a different partition scheme since I don't have an internal SD).
[Galaxy S I9000 Android Development] soumyabrata:
Porting to s7500

Can this rom also be ported on Samsung Galaxy ace plus (s7500)? Will you guys port it? :o:)
[Galaxy S I9000 Android Development] xc-racer99:
Sorry, no. The Ace Plus is totally different internally than the first-gen Galaxy S devices (QCOM chipset vs Samsung chipset). Would require a lot of work, someone with knowledge, the device, and the time to work on a (relatively-speaking) ancient low-powered phone:D The ARM world is not like the x86 world, unfortunately...
[Galaxy S I9000 Android Development] gorgooger:
This is quite amazing, faster than expected. But really needs long to settle.

FM radio is not working, at least not with sound.
[Galaxy S I9000 Android Development] PGHammer:
Why is N for Dual-Core Surprising?

Why is it surprising? Is it a single-core?

Consider that the dual-core TI OMAP-driven Galaxy Nexus has at least two Nougat ROMs out for it (Dirty Unicorns for Tuna and PureNexus for Tuna 7.1.1); the latter is my default, in fact, and it's by my right elbow.
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, Ok. My variant doesn't have the FM chip in it enabled (at least, not that I could ever get working....). I know that we had to disable some FM-related things to get it to build but I don't think these parts had been enabled in 6.0 either. Did the FM radio work there?

Yeah, it's a single core clocked at 1Ghz with a puny 512MB of RAM (and only 440MB is user available, even with CMA - stock only had ~330MB of available). It's basically the same chipset as the Galaxy Nexus's predecessor, the Nexus S.
[Galaxy S I9000 Android Development] PGHammer:
So how much storage does it have - and does it support microSD? The Galaxy Nexus does not - however, it makes up for it with a large base storage capacity. (If it does, I would not know, as I don't use the FM radio feature, even on devices I know that have it - such as my Lenovo A7-30F; instead, I copy music from my desktop's music collection.)
[Galaxy S I9000 Android Development] gorgooger:
I don't know whether fm radio did work for 6.0, because I only tried officiall Cyanogenmod, there fm radio worked. The FM signal level indicator and autoscan works, only the output is missing. Ah and I didn't see RDS.

F-droid is working, I installed Firefox and at least YouTube is working in the browser.
[Galaxy S I9000 Android Development] gorgooger:
RAM 440MB Which is much more than the ~384 MB of stock

Device internal 5.78GB But you can plug in an uSD card this space will somehow be added, I have a 4 GB card.
[Galaxy S I9000 Android Development] Bishopandme:
cool !

like that...
[Galaxy S I9000 Android Development] VENESOLANITO:
I install LineageOs, supersu(https://xdaforums.com/attachment.php?attachmentid=4009437&d=1484849584) and work well :)

But I want to know how to disable or change the bigmen?
[Galaxy S I9000 Android Development] xc-racer99:
Bigmem isn't supported on this kernel, CMA is used instead. There is an option of CMA where the RAM for video decoding and camera is normally not allocated except when it is needed. What bigmem does is disable/reduce the space allocated for video decoding and camera but this breaks things (ie 720p recording and/or playback).
[Galaxy S I9000 Android Development] VENESOLANITO:
Ok, everything works fine for me except the camera when I'm going to use it the screen stays black or it closes

In the ROM CM14. 1 happens that when it is activated bigmen and in memory is 440MB so I was asking how to modify that to leave the memory at least 405MB

I do not know if I explain myself well by my english
[Galaxy S I9000 Android Development] angelcalibur:
I'have tryed to flash this lineageOS build, but impossibe to use it.

Flash succed, first boot is really long but succeed too.

When i try to enter the pin code, smartphone freeze.

I have to remove the battery...

This build can be used as a daily rom?
[Galaxy S I9000 Android Development] xc-racer99:
Ok, I think I understand your issue now. Theoretically, the camera should be working all the time. Unfortunately, the system doesn't always clear enough memory in time so that's why the Camera won't open. There is no way (without recompiling another kernel) to have the memory for the Camera always reserved which is what you're asking for.

Which PIN code are you talking about? Are you using a pin on your SIM? I haven't tested that part of the RIL, it might be broken... Logs? If you're talking about the regular unlock screen, then I don't know what's happening.

I used the build I created for my variant as a daily driver for a couple of weeks (I'm a very light user and don't have gapps), but I've since gone back to AOSP as it's much lighter and has fewer bugs. If you use your phone on a regular basis, I would not recommend running this ROM (or anything newer than KitKat, to be honest).
[Galaxy S I9000 Android Development] davejohncole:
Does not boot...

Has anyone managed to get this going? During installation a number of error messages displayed about missing partitions (I think) and then when I booted the device just shows the initial lineage boot animation. I left the phone overnight to see if it would eventually boot, but no such luck.

If you have managed to get it to boot I would really like to see what your partition table looks like. I found this "guide" to repartitioning, so I am game to try it if given details of a working device.

(Not allowed to post outside links - so...) iwf1.com/how-to-re-partition-your-android-tablet-or-smartphone-all-options-included-change-size-fs-type-etc/2/
[Galaxy S I9000 Android Development] xc-racer99:
Now, I don't have this variant myself (despite building for it...) so the partition scheme is a little bit foreign to me but looking at the code I think I know what's going on... However, what I think is happening is that the recovery included in the Lineage build is non-functional. Try replacing the ramdisk-recovery.img in the zip with one from one of my AOSP builds, flash the zip, reboot to recovery, flash the zip again.

As to what the partition layout is, here goes:

/system is mounted on /dev/lvpool/system

/data is mounted on /dev/lvpool/data

/sdcard is mounted on /dev/block/mmcblk0p1

/cache is mounted on /dev/block/mtdblockx (x is some number, I don't remember which at this moment - you're probably not having issues with any of the MTD partitions - if you were, then you wouldn't be able to get into recovery).

I don't recommend following the guide you posted as the i9000 uses LVM for the /system and /data partitions.

If you post the exact output of the missing partitions text along with output of the adb command "ls /dev/lvpool" then I'll try to help you more.
[Galaxy S I9000 Android Development] angelcalibur:
Hi!

I'am talking about the pin code to unlock simcard.

I can try again by disable it and see what happen, and i know it's a part of RIL (i made build for S4 device : AOSP, Slim, SlimSaber ROM...).

I don't have any log and don't really have the time to make any build for this galaxysmtd device.

I'am using cm13 build, with overclocking at 1400, and governor mode on performance. Not bad for an old device, but so laggy sometimes! :p

was on slimkat and think i will go back to this rom.

witch TC are you using when you build rom?
[Galaxy S I9000 Android Development] etguerin:
I've tried to install... but i have an error 7.

I am on TWRP and ROM Full Advance 6.1

Is there something to do to install it whithout pb ?

Thx for your job !