yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Coldwindofnowhere:
You can just extract it from the zip and flash it using TWRP. A flashable zip isn't needed here.
[Galaxy S I9000 Android Development] Alokhacker:
which file is it? is it boot.img?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Obviously yes.

Unrelated but I got cm14.1 to boot using the ramdisk and the recovery from cm14.0.

Storage is still bugged.

Apparently the scrren freezes sometimes too (still unsure).

But it feels faster.
[Galaxy S I9000 Android Development] Alokhacker:
thats great. I dont mind experimenting with it
[Galaxy S I9000 Android Development] Coldwindofnowhere:
For now I prefer to keep it private until it's more usable.

EDIT: It's really not usable, pvr (graphic driver) crashes randomly.

Maybe some commit from https://github.com/Unlegacy-Android/android_kernel_samsung_tuna/commits/aosp-7.1 will fix it but I don't have time for this now.
[Galaxy S I9000 Android Development] xc-racer99:
Darn, so you're getting the PVR crash as well:( I was hoping it was just something with my setup. Hopefully we'll be able to workaround it in the higher layers somewhere.

I doubt any of the tuna kernel commits will help us as it's using DDK1.9 since it's a lucky OMAP chipset...
[Galaxy S I9000 Android Development] fparri:
I need to revert my i9000 to stock samsung firmware from this rom. Is it enough to flash stock rom via Odin? :)
[Galaxy S I9000 Android Development] Alokhacker:
yes its enough
[Galaxy S I9000 Android Development] unknown:
how to port rom for s1???
[Galaxy S I9000 Android Development] caravagio:
My S1 is the king of all samsung phone... best suport, best roms, best community on xda... now I switch to a note 4, but I still use my S1 for it's great sound ... ty for this alpha nougat... it's still fun to Install Roms after so many years.. ty
[Galaxy S I9000 Android Development] xc-racer99:
Interesting about where the MTP crash comes from. Perhaps it has some thing to do with the namespaces fix that I kept seeing on CM's gerrit (http://review.cyanogenmod.org/#/c/169806/ for part of it). What happens if you revert the commit you mentionned?

Really odd that you guys are having issues with 3G as the few times I've tested it it's working without issue. If someone wants, I can send them some test files. I doubt the espresso3g datacalllist fix would work (assuming you're talking about https://github.com/Unlegacy-Android...mmit/8ecafbe359d04f13c6f8f3642bc5bce7796c71b0 because we use a Data_Call_Response_V3 which only has addresses and doesn't even have the gateways so they can't be switched. However, http://review.cyanogenmod.org/#/c/167493/ is a possibility. I suspect it's much likely that because I forced it to RIL_REQUEST_SETUP_DATA_CALL to be considered as GSM always that 3G isn't working.

With 7.1, if we use the Tuna 4.3 PVR libs, then PVR doesn't seem to crash. Unfortunately, it breaks hardware decoding (but hardware encoding still works). There might be some way to work around this, but I'm not sure yet.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Um gotta try this for storage. Reverting the commit on vold isn't a good idea at all ... AT ALL : breaks pretty much everything.

I already cherry-picked the commit about ril and it doesn't help much.

Awesome about pvr, I feared that our device would be stuck because of proprietary blobs.
[Galaxy S I9000 Android Development] nursoda:
I could install but after first start, I got a black screen (and "System-UI crashed" PopUps) all the time. Is that the PVR issue? Quite unusable, and difficult to record Catlogs ... without seeing anything ;)
[Galaxy S I9000 Android Development] xc-racer99:
No, that's not the PVR issue. If you get the PVR issue, your screen will freeze and the only way to get things to work again is to pull the battery/long press the power button. It isn't present in 7.0 but appears in 7.1. Since CM has moved everything to 7.1, 7.0 isn't getting any more updates so if we want fixes/features, we need to get PVR working properly there.

Your issue sounds more like either a bad download (check the md5sum) or some corruption with /data (try wiping /data and trying again). To get a logcat when in an issue like this, you can do it via ADB, see http://xdaforums.com/showthread.php?t=2185929 for instructions.
[Galaxy S I9000 Android Development] nursoda:
Thanks for your swift and comprehensive answer! Strange. I did format *all* partitions and checked MD5 (on my PC). Will re-try later maybe. It's just booting RR 5.7 (6.0.1) now.
[Galaxy S I9000 Android Development] pxrave:
thanks for bring the nougat flavour to us

any news on cm14.1?
[Galaxy S I9000 Android Development] xc-racer99:
I know [MENTION=6794010]Coldwindofnowhere[/MENTION] had it booting. Unfortunately, there's a bug somewhere in 7.1 which causes our prebuilt graphics blobs to crash frequently making the phone borderline unusable for normal use.

I've discovered that by using the Galaxy Nexus's graphics blobs that we no longer get the crash. Unfortunately, this breaks hardware decoding as the graphics drivers no longer allocate the correct buffers to use (the lines containing GRALLOC_USAGE_SW* in hardware/samsung/exynos3/s5pc110/sec_mm/sec_omx/sec_osal/SEC_OSAL_Buffer.cpp for those interested). This no longer works because the gralloc blob for tuna expects it to be GRALLOC_USAGE_HW (since tuna uses OMAP4's TILER to allocate buffers but we use Samsung's MFC). If you change this to GRALLOC_USAGE_HW, then you get a null pointer exception in the kernel. It might be possible to modify the kernel code so that GRALLOC_USAGE_HW is treated as if it were SW but I've yet to seriously investigate that.

If the above doesn't make sense, the tl;dr version is there's graphics issues that are partially solvable but break hardware decoding (aka video playback).
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Alpha 2

New build is up, but this is still far from perfect

Changelog:

Latest CM 14.0

As people wanted, cmc is back

Tweaked art settings (lag should be gone)

Fixed video recording

Fixed MTP crash

Fixed adb authkey issue

Disabled SDcardFS

More stable RIL (but there are still issues with 3g)

Note that cm's file manager is bugged on my side, please use android built-in fm or an other one.

http://www.mediafire.com/file/5d1fdr0f75rywml/cm-14.0-20161120-UNOFFICIAL-galaxysmtd.zip
[Galaxy S I9000 Android Development] jupiter5700:
Great! But where are ThemeChooser and Theme Manager apps? :)
[Galaxy S I9000 Android Development] Coldwindofnowhere:
http://www.cyanogenmod.org/blog/cm14-is-landing
[Galaxy S I9000 Android Development] VENESOLANITO:
I was trying to do this

http://xdaforums.com/showpost.php?p=65705911&postcount=496

But when I write: adb shell stop

tells me: stop must be root (I already have that option enabled in the developer options)

who has Bigmem patched, to test the 720p videos

Thanks in advance and sorry for my english
[Galaxy S I9000 Android Development] xc-racer99:
When you have root enabled in developer options, it means that you can use the "su" command once you've run "adb shell". In order to run all adb commands as root without having to add "su" to them, run "adb root" first. No idea if the process you're trying will help though...
[Galaxy S I9000 Android Development] caravagio:
For an alpha is working great... Not so many lags as I expected...
[Galaxy S I9000 Android Development] xxraid:
Without gapps works better then omni 6.0.1 for me. Great job ;)

Looking forward for next release.
[Galaxy S I9000 Android Development] jupiter5700:
Use latest rom at last week. Mostly all work fine. No more camera, mtp issue. With 3G also good now. After some turn on/off airplane mode H data work fine. Only one issue with fileman (see in attach). I turn root access on, but it not resolve problem.

Thanks for this great rom! Will wait for theme manager included.
[Galaxy S I9000 Android Development] xc-racer99:
Unfortunately, the only way theme manager will come is if we managed to get 7.1 working our device (and the theme manager gets merged in cm14.1 - it's currently very unstalbe). The PVR issue is there with our blobs on 7.1 so we need to:

1) Find newer blobs for the S5PC110 platform (that's what we use right now)

2) Use the Galaxy Nexus (OMAP4) blobs and fix hw decoding by doing

a) Telling the blobs we're not actually doing encoding when we are so that it allocates the right type of buffer. Haven't really tested/figured out how to do this yet.

b) Figure out what the buffer returns actually looks like. I've gotten the graphics buffer to allocate, mfc to allocate, things appear on the screen but it appears as if the picture is repeated fuzzily 6 times along the top and the bottom 3/4 of the screen is fuzz. If you're an expert of color formats, android OMX, etc then we might be able to fix things this way

c) Or, just forget about hw/decoding and just use the OMAP4 blobs as they are.

Great to hear your other issues are gone. Don't know what's up with your fileman issue.

Edit: And just to note, the PVR crash exists in previous version of Android as well. However, due to changed timings in 7.1 it happens way more frequently.
[Galaxy S I9000 Android Development] Alokhacker:
I would love to see your aosp build as its very fast
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Nice to hear those issues are fixed :) I'm aware of the FM issue, there must be something wrong upstream, as other file managers (life android built-in fm or root explorer) are working just fine.

I will try to build cm-14.1 with omap4 blobs but don't complain about hw decoding.
[Galaxy S I9000 Android Development] xc-racer99:
FYI, https://github.com/xc-racer99/propr...mmit/ac9e2d30378b036038dbf7aa9e22996865f11f06 and https://github.com/xc-racer99/andro...mmit/0471749ba8735efd32564852094afb972d36099d were the only ones necessary to get the system booting with the PVR blobs. If you're wanting things to semi work when trying to do hw decoding, then you need

diff --git a/drivers/gpu/pvr/osfunc.c b/drivers/gpu/pvr/osfunc.c
index 28e2b00..38f6ce42 100644
--- a/drivers/gpu/pvr/osfunc.c
+++ b/drivers/gpu/pvr/osfunc.c
@@ -190,6 +190,7 @@ OSAllocPages_Impl(IMG_UINT32 ui32AllocFlags,
}
#endif

+#if 0
if(ui32AllocFlags & PVRSRV_MEM_ION)
{

@@ -205,6 +206,13 @@ OSAllocPages_Impl(IMG_UINT32 ui32AllocFlags,
PVRMMapRegisterArea(psLinuxMemArea);
goto ExitSkipSwitch;
}
+#else
+ /* Ugly hack to force the right allocation type when using OMAP blobs on S5PC110 */
+ if(ui32AllocFlags == 838943232)
+ {
+ ui32AllocFlags = 302060032;
+ }
+#endif

switch(ui32AllocFlags & PVRSRV_HAP_MAPTYPE_MASK)
{

and

diff --git a/exynos3/s5pc110/sec_mm/sec_omx/sec_osal/SEC_OSAL_Buffer.cpp b/exynos3/s5pc110/sec_mm/sec_omx/sec_osal/SEC_OSAL_Buffer.cpp
index 1fdb914..7932b63 100644
--- a/exynos3/s5pc110/sec_mm/sec_omx/sec_osal/SEC_OSAL_Buffer.cpp
+++ b/exynos3/s5pc110/sec_mm/sec_omx/sec_osal/SEC_OSAL_Buffer.cpp
@@ -208,7 +208,11 @@ OMX_ERRORTYPE getAndroidNativeBuffer(OMX_HANDLETYPE hComponent, OMX_PTR Componen

pganbp = (GetAndroidNativeBufferUsageParams *)ComponentParameterStructure;

+#if 0
pganbp->nUsage = GRALLOC_USAGE_SW_WRITE_OFTEN;
+#else
+ pganbp->nUsage = GRALLOC_USAGE_HW_RENDER;
+#endif

ret = OMX_ErrorNone;

If you're not interested at all in getting hw decoding to work, then don't apply either of those patches and it should just error out IIRC. Interestingly, hw encoding does work....

Yeah, I can probably create a 7.1 build sometime. I'll create a thread sort-of where I post my findings with fixing issues/finding issues. Will post link here if I get around to it.

Edit: No, I haven't forgotten to create a thread. 7.1.1 just has some major bugs that I've been trying to iron out. Think I've finally got the graphics to stop crashing. Still working on hardware decoding although I don't have much hope.

Edit2: [MENTION=4825729]Alokhacker[/MENTION] I've created a thread for my AOSP build at http://xdaforums.com/galaxy-s-i9000/i9000-development/aosp-7-1-rom-discussion-t3523073 Hopefully it boots!
[Galaxy S I9000 Android Development] sir mordred:
Hi [MENTION=5414656]xc-racer99[/MENTION] and [MENTION=6794010]Coldwindofnowhere[/MENTION] first of all great work.. :good: you ported latest android to neaarly oldest hardware.. :good:

i saw you new RIL implementation on >7.0 from your gits. (libsecril-shim etc.) and my device is using exactly the same RIL (i have galaxy wonder) and i ported your RIL implementation to my build..(and excluded external custom ril class(e.g SamsungRIL.java) and here is the results of my attempt:

SIM is detected but calling, sms or mobile data is not working..

logs are attached..

Atleast give me some tips while you are porting into your device

for example variables in ril.h is device-specific or not..

thanx/regards
[Galaxy S I9000 Android Development] sir mordred:
and also here is the some commits which also make better/optimize your current builds..give it try ;)

ART optimization for devices which have single-core CPU https://github.com/cyanogenmod-nougat-samsung-msm7x30/android_art/commit/abc6daf45b2d14ea40e95a7556ec086c6d002ed2

Enabling multi-window mode on lowram devices https://github.com/cyanogenmod-nougat-samsung-msm7x30/android_frameworks_base/commit/fb1a7eb0991d3931b084e3b96dade4975e0680f8

and enabling free-form multiwindow mode instead of default one https://github.com/cyanogenmod-nougat-samsung-msm7x30/android_frameworks_base/commit/fed17dd92068307c6fdaca2408878d9aa9721279
[Galaxy S I9000 Android Development] xc-racer99:
As much as I'd like to credit for the secril-shim, I can't, it originally came from http://dmitry.gr/index.php?r=06. Thoughts&proj=05. Android M on Nexus S and then was heavily reformulated at https://github.com/Unlegacy-Android/android_device_samsung_tuna/commits/aosp-7.1/ril/libsecril-shim I did have to make some changes for our specific hardware. As you're using a similar RIL (but probably slightly different unless you used the Exynos3RIL.java class exactly), you'll likely need to make a few changes. As to what you need to change, I would recommend looking through your previous RIL class and seeing where differences are. ril.h header is probably not device-specific, the only difference in ours is that we need rild to allow an older RIL version (either 2, 3, or 4 in our case - device dependent. My T959P uses version 3 but I don't know about the i9000). However, the espresso3g device needed some changes to ril.h If you didn't have a custom ril.h before, you probably don't need one now though.

Unfortunately, your logcat is slightly truncated, see http://stackoverflow.com/questions/34587273/android-logcat-logs-chatty-module-line-expire-message to get the full logs.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Got 7.1.1 to boot, bt is broken for some reason (uptream messed ?). Issues present in 7.0 are still here :) but yeah kinda faster. I'll upoad something tomorrow, but don't except it to be stable nor heavily tested.

Crash log if anyone intrested:

E BtGatt.JNI: ERROR: initializeNative(L950): Failed to get Bluetooth GATT Interface##

this commit is already there so there soudn't be problems ... maybe something with 7.1.1 merge.
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, great. Which PVR drivers did you use? With tuna's, I had crashes all over the place on AOSP. Also had the BT crash there. Since PVR was so unstable I didn't both figuring out anything about BT.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
That's weird, pvr is quite stable using tuna blobs here ... I will do more testing.

EDIT: okay i'm getting them aswell, have you tried using the original driver ?
[Galaxy S I9000 Android Development] Coldwindofnowhere:
http://www.mediafire.com/file/v1ja3xsvlycdkw0/cm-14.1-20161211-UNOFFICIAL-galaxysmtd.zip

If you want to play with it ... note that crashes happend quite often
[Galaxy S I9000 Android Development] jupiter5700:
Okay, that's good job! You now have very good skill on i9000 developing. May be you could make working CM12 rom for i9000? Cause we have not fully working CM12 rom for now (RIL is broken).:good:
[Galaxy S I9000 Android Development] VENESOLANITO:
[MENTION=6794010]Coldwindofnowhere[/MENTION]

Thank you very much for the great work you are doing for our SGS

So far I have had 2 restarts but it works quite well taking into account the SGS time

Can be of good daily use at least in my case

If active XLMem or Bigmen restarts from time to time but deactivated I have not rebooted

sorry for my english

edit.

I returned to android 7.0, every now and then I had no signal and to repair it I had to restart the phone

At the time I was out of signal, I'm going to install it again to see if it works better or was to see if it was a problem of the telephone operator
[Galaxy S I9000 Android Development] Draal:
Hello,

I installed this cm14 with opengapps (pico). Google's syncronization works smoothly. Only when installing apps were there occasional involuntary warmstarts.

The system runs faster than the Android 6.01 I tested here. Wifi works also better.

Only, compared to previous Androids, Clash of clans I almost do not start (I think, however, that this game is also the limits for the hardware of the i9000 ;) ).

Enclosed much the same still a screenshot on the compressed appmenu, which is somewhat a little wrong ;)

THX for this fine Rom

Draal
[Galaxy S I9000 Android Development] xxraid:
I'm using Android 7.1.1 at the moment and have device OC to 1.2GHz, using smartassv2, bfq, increased voltage and bigmem enabled. Work like a charm. No restarts. But must have flight mode enabled :) and using SGS i9000 as a toy :) and skype phone.

After enabling SIM (flight mode off) device start to hang, and looks like 1frame / 30sec game. Even if all OC things are disabled and operatest in stock device freqs.

I'll try to get some logcat from device and attached it here. I'm impressed of this Android 7.1 build. Works faster then 5.1 and 6.0.1 for me. No GAPPS installed and using Pure APK as replacement for Google Play (which solved battery drain as well).
[Galaxy S I9000 Android Development] Alokhacker:
which apk did you use for google play replacement?
[Galaxy S I9000 Android Development] VENESOLANITO:
in my case

I am using odemand and sio, without oc, bigmem deactivated

The signal goes away and to repair it I have to restart the device but at the same time it is running out of signal again

You have to use it as you say (flight mode), the phone works pretty well with nougat 7.1.1 :laugh:

For now I will continue using nougat 7.0 that does not give me restarts nor the signal is lost, Activated oc and bigmem with kernel auditor and i`m not using gapps

I think it's this apk https://apkpure.com/apkpure/com.apkpure.aegon
[Galaxy S I9000 Android Development] xxraid:
Yeap, exactly this app. Or just downloading APK from this website, upload it to internal storage and install APK. Installing from untrusted sources must be enabled. There is risk, that apps from this site might be injected by unwanted "features", but I use it for more then 1 year and nothing bad happened.

Connecting with google services is not important for me, so I don't need google play.
[Galaxy S I9000 Android Development] sir mordred:
i tried to get logs without chatty(and tried various methods) but still spams chatty logs...i couldnt configure it..

what could be the reason for the RIL issues? that thing(RIL) started to make me crazy :silly: can you send your radio logs please so i can compare with my logs.. :good: thanx

and yeah my ril is version 4 so im using custom ril.h to allow older rils such as mine to run...

and dou you have any suggestions mate?

thanx again
[Galaxy S I9000 Android Development] xc-racer99:
Well, see my radio logcat attached

Personally, I'd get a logcat from your device on a previous android version and then compare with your current radio logcat. A lot of errors that are spat out aren't actually errors but just normal functionality.

Otherwise, I don't really have any ideas. I don't use data, so if it's just that part that's giving you issues then I can't help. I had to hack things a little bit on my device for data when I first tested (that's where I override the setup type to either just GSM or CDMA).
[Galaxy S I9000 Android Development] sir mordred:
thank you so much mate :good:

and may i ask how did you get that logs(chattyless log :P ) ?

which adb command? i tried many of them but nothing worked sadly
[Galaxy S I9000 Android Development] xc-racer99:
Well, I rebooted my device, ran adb logcat -P "" and then ran my adb logcat -b radio right afterwards. I think the "chatty" part swallows the logs when they happen so you can't retrieve them right away.
[Galaxy S I9000 Android Development] :
WOW. I haven't visited SGS forum for a year and WOW we have android 7.1.1 now. Big congrat to Coldwindofnowhere, xc-racer99 and the team. It looks smooth but why quick setting panel UI is android 6.0.1's? I can't try this ROM bcs I own a Vibrant
[Galaxy S I9000 Android Development] Coldwindofnowhere:
CM 14.1

Here is the last update of the year:

Changelog:

Android 7.1.1 r6

No more crashes due to the graphic driver

Working ril (except data on the first boot apparently ?)

Fixed internal storage issues

Updated kernel

Latest TWRP (without their new app, tell me if you want me to add it back)

Also still no theme manager :)

Most of the merit goes to [MENTION=5414656]xc-racer99[/MENTION], thank him for his work.

Link: http://www.mediafire.com/file/xfcjvn1y1vjwwpu/cm-14.1-20161223-UNOFFICIAL-galaxysmtd.zip

Merry Christmas guys !
[Galaxy S I9000 Android Development] jestar_jokin:
Thanks to you both for your amazing work on keeping the I9000 alive! :good:

I've installed this build, here's a few notes:

I upgraded from Full Advance 6.0.1 (20160919)

My "/data" partition was formatted as f2fs, but I got errors wiping/installing things, so I changed it to ext4 and all seemed to work fine.

On first boot, it got stuck at the Cyanogenmod logo animation. A reboot fixed it.

The browser does not seem to render pages at all. I can type in search terms or URLs, and I see the small loading bar move, but the page area remains blank/black. When I pull down the menu bar and swipe it up again, it leaves a green trail on the page area (like nothing gets drawn over the image buffer).

I'm looking forward to more great progress in the new year! :D
[Galaxy S I9000 Android Development] Coldwindofnowhere:
Worry not about wiping "errors", when you switch to f2fs, those are harmless.

About the bootloop, first boot can be really long, the first time I got cm to boot I thought it was a bootloop, but in fact, it wasn't.

When it comes to the browser, I haven't noticed it, thanks for the feedback ...

First of all, was it happening with the previous cm 14.1 build ?

Apparently, it comes from the changes google made to android webview:

From my logcat:

12-29 16:14:00.631 2481 2481 D WebViewTimersControl: onBrowserActivityPause
12-29 16:14:00.631 2481 2481 D WebViewTimersControl: Pausing webview timers, view=com.android.browser.BrowserWebView{d67728e VFEDHVCL. .F...... 0,0-480,764}
.....
12-29 16:14:00.934 1190 1235 I OpenGLRenderer: Initialized EGL, version 1.4
12-29 16:14:00.934 1190 1235 D OpenGLRenderer: Swap behavior 1
12-29 16:14:00.934 1190 1235 W OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
12-29 16:14:00.934 1190 1235 D OpenGLRenderer: Swap behavior 0
[COLOR="Red"]12-29 16:32:54.204 2569 2618 E libEGL : validate_display:99 error 3008 (EGL_BAD_DISPLAY)[/COLOR]
...
12-29 16:14:04.273 1190 1235 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...

Ever had this issue [MENTION=5414656]xc-racer99[/MENTION] ?

Edit: ugh webview crashing using any app ... something on our video driver again ?
[Galaxy S I9000 Android Development] xc-racer99:
Yeah, looks like I do get that issue... Although I virtually never use webview.

I'll do some digging and try to find out what's up. I certainly hope it's not our EGL drivers again.... For anyone that's installed gapps, does webview work then?

Edit: Or, alternatively, a chromium build and then selecting that webview implementation in Developer options?