yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Zippy Dufus:
local_manifest.xml?

Hello and congratulations on your new build!

I just noticed that the humberos thread and ROM is kaput.

I've been tracking his build with my own DIY build. Below is my local manifest with the concerning line highlighted.

Could you share your manifest so I can continue building an up-to-date ROM?

In advance, thanks.

echo '<manifest>
<project name="android_device_samsung_galaxysmtd" path="device/samsung/galaxysmtd" remote="omnirom" revision="android-5.1" />
<project name="android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="omnirom" revision="android-5.1" />
<project name="android_device_samsung_aries-common" path="device/samsung/aries-common" remote="omnirom" revision="android-5.1" />
<project name="android_kernel_samsung_aries" path="kernel/samsung/aries" remote="omnirom" revision="android-5.1" />
<project name="android_hardware_samsung" path="hardware/samsung" remote="omnirom" revision="android-5.1" />
[COLOR="Red"]<project name="humberos/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="android-5.1"/>[/COLOR]
</manifest>' > /home/android/.repo/local_manifest.xml
[Galaxy S I9000 Android Development] loliciu:
How do I enable SU permissions on lollipop.. apps that require su are not working anymore. :(
[Galaxy S I9000 Android Development] xc-racer99:
When flashing the ROM, you need to flash SuperSU as well. It can be downloaded from https://download.chainfire.eu/696/SuperSU/
[Galaxy S I9000 Android Development] loliciu:
Thanks... and another thing.

If I increase the cache partition size from Recovery will that affect in any way the current state of my installed apps and data?
[Galaxy S I9000 Android Development] xc-racer99:
No, you cannot change the size of the cache partition easily at all. The size of it is specified when the kernel is created. While it probably is possible to override it later, it definitely wipes the whole storage device (include potentially the bootloaders....)

Why do you want to increase the size of the cache partition? There shouldn't be a need to as very little is actually stored on that partition. You can check the usage of the partitions by typing in the command "df" in either a Terminal Emulator or in an ADB shell.

On another note, how is 720p recording for everyone? For me it is very, very laggy but it might just be since I'm using a custom build for the Galaxy S 4G :p
[Galaxy S I9000 Android Development] jupiter5700:
What the file system type on your sd-card0 ? If file system is FAT then convert it to EXT2.
[Galaxy S I9000 Android Development] loliciu:
It's because I can not install apps larger than 15MB from playstore.. my cache is 17.5 MB large and I thought I can increase it.
[Galaxy S I9000 Android Development] xc-racer99:
Hmmm, unless things have changed very recently, the Play Store doesn't download to /cache, it downloads to /datadata/(com.android.vending???). However, it does check for space in /data/download... How many apps to do you have installed? If you've got a lot installed, then you may be running out of space on one of those partitions. Use the "df" command I posted earlier and post the results. Also, post the output of a logcat that happens while trying to install.

Its also possible that iyahman did change the partitions around a little bit. If you could also post the output of the command "mount" that would be great (in a Terminal Emulator, run "su", then run "mount", alternatively run "adb shell su -c mount" if you have a working adb).

Not sure if you've tried this, but it might also be worthwhile to do a complete wipe (backup first!) and then try installing a 15MB+ app first. This will tell you if one of the partitions is just too small or if its some other problem.
[Galaxy S I9000 Android Development] loliciu:
I have 27 apps installed from playstore and the HDPI mini gapps . In data/data folder I have 422MB from which 44.1 MB is free. What else besides apps are stored in here so I can delete them? Do I need su permission to access this folder?
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, that should be enough.... The only things stored in /data/data is the actual application data, not the applications themselves (they're stored in /data/app, which is a separate partition). You haven't encrypted your phone by chance, have you?

I think its probably best if we move this conversation to PM or its own thread instead of cluttering up the thread here.
[Galaxy S I9000 Android Development] resonansER:
Outstanding!

Excellent ROM, I suppose. Please, keep going support and develop this beautiful masterpiece of code! ;)
[Galaxy S I9000 Android Development] Levi Stark:
Don't work on i9000B brazilian version
[Galaxy S I9000 Android Development] redesign93:
Thanks

works smoothly

runs all my apps and gives a decent battery life
[Galaxy S I9000 Android Development] Un Loko:
true,

This package is for "galaxys,galaxysmtd,GT-I9000,GT-I9000M,GT-I9000T" devicesthis is a "GT-I9000B
[Galaxy S I9000 Android Development] resonansER:
Very impressive!

Yes! Battery life is outstanding! I'm shocked and very impressed HOW long now my old phone works with this ROM!!! :good::good::good:
[MENTION=3384506]iyahman[/MENTION], please, give us new version of this excellent ROM!
[Galaxy S I9000 Android Development] iyahman:
Woow.. Sorry for this guys..

I will make a new build this weekend with a little gift from [MENTION=5414656]xc-racer99[/MENTION] to choose bigmem directly from device setting menu.
[Galaxy S I9000 Android Development] meohmy:
I have 2 I9000's in the family and found this runs well on both of them although the oldest of the two phones cannot get a gps connection

with this rom or coderom 5.1.1. Not sure of the reasons for it but I have had no problems up until now.
[Galaxy S I9000 Android Development] hunter_sephiroth:
hey there,

i'm trying to get this to work but when i'm trying to flash via cwm is gives me: error in /... (Status 7), Installation aborted.

CWM version is 6.0.4.4

any suggestions on how to proceed?

thanks in advance :)
[Galaxy S I9000 Android Development] exerramun:
Use Trwp v 2.8.7.0 It works like a charm.
[Galaxy S I9000 Android Development] iyahman:
new build is out, read post 2 for changelog
[Galaxy S I9000 Android Development] hunter_sephiroth:
thanks for your suggestion. would you mind telling me where to get it for the device since on twrp homepage the device is not listed as supported =(
[Galaxy S I9000 Android Development] exerramun:
Download the app & install. Or try latest cwm.
[Galaxy S I9000 Android Development] hunter_sephiroth:
which app do you mean?
[Galaxy S I9000 Android Development] jupiter5700:
Is reboot required?
[Galaxy S I9000 Android Development] xc-racer99:
Yep, a reboot for bigmem is required. I probably should have mentionned that in DeviceSettings but I didn't realize at the time. It also has the same problem as the old bigmem in that if you power off/run out of battery, it will not be enabled when you boot up again. However, if you then reboot it will be.

The only advantage that it brings from how it was before is that you no longer need to manually edit /sys/kernel/bigmem/enable (or something like that, I forget what exactly).
[Galaxy S I9000 Android Development] jt.hesse:
Stuck at Waiting for connection during first boot

I installed the newest version today (08/08/2015, including gapps). During fist boot I'm stuck @ waiting to connect, (WIFI connected, also tried with mobile connection) waited several times for more than 30 minutes.

I found a similar post for humberOS (http://xdaforums.com/showpost.php?p=61108220&postcount=1160) but no answer.

Any help is appreciated. Thanks,
[Galaxy S I9000 Android Development] resonansER:
If you have in your phone microSD 8Gb or 16Gb (including microSDXC UHS-1) during first setup after flashing ROM, please remove this card from your phone! With microSD capacity 8Gb & 16Gb WiFi DOESN'T WORK! Remember this! Only 32Gb and higher.
[Galaxy S I9000 Android Development] MrOban:
I've a problem with the notifications. I only see one notification when wiping down the notification bar, even when there are many. I'm alone with this or is this a known issue?

Thanks for this good ROM.

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] xc-racer99:
Sounds like the dreaded (at least for me) notification bug again... I'm guessing that on the lockscreen notifications are also about 3/4 of the way up the screen and extra-large notifications such as the music player don't render properly? If so, then the only work-around I've found is to force high-end graphics from the Settings, Performance, Advanced menu. In theory this uses more memory and slows things down but in practice I haven't noticed a difference.
[Galaxy S I9000 Android Development] SimonNZ:
Device Encryption fails with this ROM on the i9000. Is there a fix in the works?
[Galaxy S I9000 Android Development] MrOban:
Thanks, I'll try this setting. Now I wait for notifications to proof it [emoji6]

Edit:

Thanks a lot for your advice. This works fine!

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] xc-racer99:
Yep, encryption is busted on my port for the Galaxy S 4G as well. Potentially /datadata related???

For more info on encryption, visit https://source.android.com/devices/tech/security/encryption/
[Galaxy S I9000 Android Development] jupiter5700:
Bugreport https://youtu.be/u6t5k4hFZFM . Quick settings panel hungs.
[Galaxy S I9000 Android Development] xc-racer99:
Alright, I could reproduce this as well. However, it is only reproducible when high-end graphics are not forced. If high-end graphics are forced, this also works no problem. So, I guess the Settings, Performance, Advanced, force high-end graphics fixes more than the notification bug.

Looks like there is some major problem with Omni's low-ram device configuration....
[Galaxy S I9000 Android Development] jupiter5700:
I have problem with SWAP creating. Does kernel SWAP support?
[Galaxy S I9000 Android Development] jt.hesse:
Thanks resonansER, I should have written that. I used 32 GB micro SD, and I removed even this card. Still same problem. Tried different language as well (english), but it is still stuck.
[Galaxy S I9000 Android Development] SimonNZ:
Deleted.
[Galaxy S I9000 Android Development] qu4nt1n:
Merci, Iyahman, t'assures comme un Dieu, et la Terre te remercie!

thx Lyahman, you rule, and planet earth welcomes your efforts!

, and incidentally so do I!
[Galaxy S I9000 Android Development] xc-racer99:
I'm very well aware that encryption concerns /data and /data only. However, what I was trying to point out, and I guess I didn't do a very good job at, is that we have "two" /data partitions. Or rather, part of /data is stored on another partition, /datadata (which is yaffs2 based) in order to speed things up.

P.S. I'll edit my earlier response to simply to say that encryption is currently not working.

Edit: I just recompiled a boot.img for the Galaxy S 4G that removes the use of /datadata and presto! encryption works. I'll see if there's some way I can encrypt the phone while keeping /datadata around but no promises....
[Galaxy S I9000 Android Development] TLH11:
Im not getting 3g :s

I might missed something?

thx
[Galaxy S I9000 Android Development] fathi48:
notification bare bugs still not fixed

when I tried to change brightness level in notification bare, notification bare freeze

sorry my bad english
[Galaxy S I9000 Android Development] xc-racer99:
Alright, I think I figured out the encryption bug. It should be fixed as of this commit. What was happening is that the prop vold.decrypt was not being set before /datadata was run so setupdatadata.sh thought it was a normal boot. This prevented /data from being unmounted and caused encryption to fail.

For those that are impatient, putting a file called .nodatadata in /data/data or /datadata and then rebooting should also enable you to encrypt your device.

Please note that I tested this on a Galaxy S 4G, but it has a different partition layout. It should work on other devices....

Have you tried to forcing high-end graphics in Settings, Performance, Advanced as stated earlier? This worked for me and several other people.
[Galaxy S I9000 Android Development] almorabitms:
Salam. I went to install your rom, but first i have some questions

1. Do the status bar fetures exist , such us center clock, transparent status bar

2. The battry status, is it good, and is it become hot when charging

3.delay when calling a namber

4.change lockscreen wallpaper

Forgive my english:p
[Galaxy S I9000 Android Development] buddyforever:
WHAT IS NOT WORKING?

same bug as Unofficial build from Humberos.

Read but not sure what are those bugs? Can you please explain?

Thanks...
[Galaxy S I9000 Android Development] udhy:
What is a bigmem?
[Galaxy S I9000 Android Development] jupiter5700:
It is feature that give you about 14Mb RAM more in compare to without bigmem.
[Galaxy S I9000 Android Development] Zippy Dufus:
Here is how I enabled bigmem and checked the result:

$ adb devices -l

List of devices attached

38319EDD326800EC device usb:2-1.2.4 product:GT-I9000 model:GT_I9000 device:GT-I9000

$ adb shell

$ su

# cd /sys/kernel/bigmem

# ls -l

-rw-rw-rw- root root 4096 2015-08-15 09:40 enable

# free

total used free shared buffers

Mem: 388728 384372 4356 0 17372

-/+ buffers: 367000 21728

Swap: 196604 123492 73112

# echo "1" > enable

# reboot

== after reboot ==

# free

total used free shared buffers

Mem: 403304 400396 2908 0 4136

-/+ buffers: 396260 7044

Swap: 196604 19956 176648

​

Note, I build this ROM myself but I use the same toolchain as lyahman.
[Galaxy S I9000 Android Development] DmitTrix:
Is there any downside of having it turned on? I mean, why not to turn it on by default? why would one wish to keep this turned off?
[Galaxy S I9000 Android Development] xc-racer99:
Yep, there is a downside. 720p recording is broken as that extra available memory is "stolen" from the memory reserved for the camera. This is why a reboot is necessary to activate it as the reserved memory is re-arranged. When its enabled, if you left the Camera app on 720p recording, you won't even be able to access the camera, if I remember correctly...
[Galaxy S I9000 Android Development] DmitTrix:
Thanks for the detailed explanation!
[Galaxy S I9000 Android Development] guenterm800:
Sorry, he TWRP-app don't know Samsung S1 (I9000), can I use "Samsung S Blaze"? I think it's not the same, or? Somebody can help?
[Galaxy S I9000 Android Development] puasson.:
@Iyahman

The most fast and stable your firmware is omni-5.1.1-20150718-galaxysmtd-HOMEMADE. Better you don't exactly make. If you correct the problem does not correctly display the names of folders "LOST.DIR" and "DCIM" in the internal memory, then it is firmware will be simply gorgeous.
[Galaxy S I9000 Android Development] almorabitms:
any one 😯😯😯😯😯

Salam. I went to install your rom, but first i have some questions

1. Do the status bar fetures exist , such us center clock, transparent status bar

2. The battry status, is it good, and is it become hot when charging

3.is the delay when calling a namber exist ???

4.change lockscreen wallpaper , is it possible and how???

????? Forgive my english
[Galaxy S I9000 Android Development] staoddo:
Recomend Gapps OmniRom 5.1 Builds for I9000 by Iyahman (08/08/2015)

Recomend Gapps for this ROM please... Why is this strange thing, that my UI is all pinky, no normal colors. I activated the `'Force high-end graphics' Setings>Performance>Advanced Reboot. Still No change. Might be because I installed HDPI_GAPPS-5.1.1-20150819-signed.zip ? Or to try it with tk_gapps-modular-nano-5.1.1-20150816-signed.zip . A?
[Galaxy S I9000 Android Development] udhy:
Use gravitybox lp module for customization
[Galaxy S I9000 Android Development] puasson.:
HDPI_miniGAPPS-5.1.1-20150819-signed.zip However, the display of colors on the screen is not connected with a view Gapps.
[Galaxy S I9000 Android Development] staoddo:
so what is it ? why all UI is pinky?
[Galaxy S I9000 Android Development] xc-racer99:
Alright, I have two guesses:

1) The color calibration data is way off for some reason. Go to Settings, Advanced, Color Tuning and play with the toggles (by default, Red, Green, and Blue are at 1.000 while Red Gamma and Green Gamma are at -0)

2) You have some sort of hardware issue. Try installing a different ROM (even if you were successfully running something else before) and see if the problem persists there.

Also, I'm assuming you've tried a factory reset and/or a reflash.

Good Luck!
[Galaxy S I9000 Android Development] staoddo:
1. here is all ok

I did factory reset. This is second reflash. All the same. To look for another ROM? I like this one how's all smooth... I did also "Force high-end graphics" too.
[Galaxy S I9000 Android Development] althafvly:
xposed in omni

how can i install xposed in this omni rom??

help

thanks
[Galaxy S I9000 Android Development] staoddo:
I reflashed from stock and installed CodeROM V 2.0 Stable KK 4.4.4. The same pinky UI. When entered Display >Color Calibration> changing al 3 colors here from 0 to 100% all changed but Green no change. So Green is not working. In stock flash GB 2.3.6 All colors and display is ok. Could it be something from kernel?
[Galaxy S I9000 Android Development] puasson.:
What is it I do not know. I use firmware omni-5.1.1-20150718-galaxysmtd-HOMEMADE.zip. It is faster, more stable and I had not noticed problems with the mapping of colors on the screen. However, when I used firmware omni-5.1.1-20150808-galaxysmtd-HOMEMADE.zip, the problems with the display of colors on it was not there.
[Galaxy S I9000 Android Development] xc-racer99:
Hmm, that is interesting. It could definitely be related to the kernel, most likely to one of the commits seen at https://github.com/CyanogenMod/andr.../cm-11.0/drivers/video/samsung/s3cfb_tl2796.c

I would suggest trying a kernel (and therefore probably the entire ROM) that was compiled prior to February 10, 2014. If things work properly there, then the "sane defaults" referenced in "detect invalid factory calibration data" commit do not work for your phone....
[Galaxy S I9000 Android Development] staoddo:
Last try was with last CM11 cm-11-20150816-NIGHTLY-galaxysmtd.zip Works well but not ass well as last this Omni. But the same pinky UI.

Suggest me a ROM to try prior to February 10, 2014. Hope this one is good to try with > cm-10.2.1-galaxysmtd.zip ? So I am starting from stock firmware again from scratch with odin.
[Galaxy S I9000 Android Development] xc-racer99:
Yep, CM-10.2 should be fine to test with to see if the issue is what I think it is. It may not be, but its a good starting point since its obviously not a hardware issue.
[Galaxy S I9000 Android Development] staoddo:
Tested ... The same pinky and violet UI. Actually when I looked carefully at display saw that is cracked in few places. So might be HW problems... But just green color?...

But to verify myself that my steps are ok: 1) I flash the stock firmware of GB 2.3.6 from Odin (pit, pda, phone, csc). 2) Root. Flashing the kernel + CWM from odin CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.zip (At this step phone display looks perfect) 3) From CWM (wipe data, cache, dalvik) and flashing custom ROM 2 times. +gapps + root. But Here is the issue. After first flash boot animation turns pinky, the TWRP loogo boot animation. The same is after first flash with custom Roms from CM or CodeROM that I tested. So could be HW issue or I messed smthn here?
[Galaxy S I9000 Android Development] saladin_hs:
for me 3) from CWM I flashed successively (wipe data, cache, dalvik) CM10.2, omnirom 4.4 and then HumberOS ROM and all is OK
[Galaxy S I9000 Android Development] xc-racer99:
Nope, your steps look fine to me. My display has a small crack in it as well and it doesn't give me any issues.... Could still be hardware though...

In an attempt to narrow down the problem, I would suggest flashing either CM7 and/or CM9 (if you can find a download link for either...) and see if the issue appears there. Also, I would try a custom kernel on stock GB and see if the display looks ok then (only bother doing this if the issue is still present on CM7/CM9). The whole reason behind this is to see where things went wrong and then we can get to trying to fix it. It might just be that you have some kind of crazy device that doesn't work with any of the custom ROMs...

Also, does the initial splash screen (the very first thing that appears when booting up) appear white or is it coloured?

Another thing to check is that on stock by typing in the code *#0*# in the dialer and then going to the screen test. Check out the different colors and make sure that your hardware is still working correctly!

If you're interested, there's some info on https://en.wikipedia.org/wiki/PenTile_matrix_family on the way that screen displays colours.
[Galaxy S I9000 Android Development] staoddo:
Tested *#0*# code in stock Red, Gren, Blue, Dimming ok all. Touch - Passed.

On your other question, the very first screen is white and normal. But turns pinky on bootanimation.... Sooo. As suggested I started with flashing CM7.2-galaxysmtd. Works perfect!!! the display, youtube is nice looking etc. The next try is CM9 and I flashed this rom cm-9.1.0-galaxysmtd.zip and here is the surprise!!! Pinky-violet again all UI. So this is the situation... Sugest some next steps this case. Seems to me this phone is crazy enough to not accept Android 4 and up.
[Galaxy S I9000 Android Development] xc-racer99:
I can't suggest any steps in this case. It would appear that you have a special phone! I can try creating a kernel image specifically for your phone but I can't guarantee it will work any better. For a bit of context, the kernel version changed from 2.6.35 to 3.0 starting with ICS and many, many changes came with it.

If you want me to try to get it working properly, send me a PM and I'll create some test kernels for you. No sense in gumming up this thread any more:D Also, and I know this sounds crazy, but you could try removing the DeviceSettings.apk from the Omni installer zip, flash with your modified file (make sure to do a data wipe too), and see if the problem is still present. I doubt this will work, but its worth a shot.
[Galaxy S I9000 Android Development] Nirak:
Flashed latest version and it's working quite good (regarding the age of the device)! However, since my device has a dead emmc it runs on a 16Gb sd card. After flashing i found out i could no longer use the camera and gallery (giving me a 'no external sd card found' error). In older versions i could edit vold.fstab file to correct the needed paths, but after reading a little more i learned that in Lollipop there's no such file anymore (it's 'baked' in the bootimage?).

Any advice would be more then welcome.
[Galaxy S I9000 Android Development] xc-racer99:
Yep, vold.fstab has been renamed fstab.{boardname}, so in our case fstab.aries. It is built into the boot.img so it can't be edited and can only be change by a recompilation. To do this you would need the full Omni source code. Since I do have the source code on my computer, if you can tell me what needs to be changed then I can probably run off a boot.img for you. It won't have the special toolchain that Iyahman has used, but it should work nonetheless.
[Galaxy S I9000 Android Development] Nirak:
Tx so much xc-racer99! much appreciated.

Have been searching which lines i changed initially in Vold.fstab (it's been a while). But this is what makes the camera and gallery app 'think' i have placed an extra sd card:

Old:

dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.0/mmc_host/mmc0

New:

dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
[Galaxy S I9000 Android Development] Zippy Dufus:
Thanks for the info guys!!

So I have a second i9000 with a dead emmc. Is the above all that is required to make it run from the external card?