yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] xc-racer99:
What exactly does "rarely find my network" mean? As in data doesn't work (this is kind-of a known problem but I thought I'd fixed it) or does it just not connect at all (ie read no signal)? Also, in Settings, About Phone, what does your baseband version read?

In terms of why its not working properly, its because we are using an ancient prebuilt radio blob meant for GB. Needless to say, Android has changed internally and so there's a variety of hacks that have been implemented to get them to work.

A radio logcat and a normal logcat of when you're getting the issue would be appreciated (see http://xdaforums.com/showthread.php?t=2185929 - also, make sure to remove sensitive info like IMEI and phone number from them - sometimes it shows up...)
[Samsung Galaxy S (4G Model)] Targaff:
xc: By "find my network" I mean it just doesn't find my phone service provider (so "no signal", I guess). Every so often if I'm driving around it'll connect, but it only lasts for about a minute. Earlier builds with the same phone and SIM work fine in the same circumstances.

I don't have it installed right now so I can't get a log to you, but I'll provide one next time I get a chance to try it.
[Samsung Galaxy S (4G Model)] xc-racer99:
That's really odd, I've never experienced this bug myself. I'll try implementing another hack for the next build that reportedly improves reliability on the i9000.
[Samsung Galaxy S (4G Model)] FBis251:
You should be careful:

http://www.nydailynews.com/news/nat...ted-cell-phone-jammer-metro-article-1.2561018
[Samsung Galaxy S (4G Model)] xc-racer99:
Umm, wrong thread? Perhaps http://xdaforums.com/showthread.php?t=1709955?:D

Unless I accidentally included some signal jammer without knowing;)
[Samsung Galaxy S (4G Model)] FBis251:
Woops that's right, i clicked on the wrong reply box while checking both threads. I also realized that post was made in 2012! The most recent reply bumped it
[Samsung Galaxy S (4G Model)] racav1904:
Please help me

I get this error when i tried to install this

E: error executing updater binary in zip

Please help me
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, I'm only going to reply to this thread, the same also applies for Lollipop.

Do you have a second partition on your SD card? This is necessary as the data partition is stored on it. More info is in the OP. If you do and are still having trouble, please copy the omni_mtd.log, omni_bml.log, and the bml_over_mtd.log from your sdcard (whichever of these exist).
[Samsung Galaxy S (4G Model)] xc-racer99:
Test unified build

Alright, so I think I have a working build that is unified for both the T959P and T959V.

If someone could please download it from https://www.androidfilehost.com/?fid=24591023225176732 and test it on a T959V that would be appreciated. I did change the GPS setup a little bit as the old code made no sense whatsoever.
[Samsung Galaxy S (4G Model)] Kyndig66:
Installed perfectly. I don't have a sim card for this device so testing will be limited. I'll get back to y'all when I have more info. Wang Chung!
[Samsung Galaxy S (4G Model)] Kyndig66:
GPS not working (tested with GPS status as well as maps). Video Recording freezes device. Same BT from setting's issue. Fine from pulldown as noted in OP. Wi-Fi is good. Came from previous build so I flashed ROM, pico Gapps and SuperSU all together without issue. Occasionally installation of apps (maps for example) didn't want to play well (memory issues as noted in OP also).

---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------

T959V, not P
[Samsung Galaxy S (4G Model)] xc-racer99:
Great, thanks for testing! Would you mind uploading the galaxys4g_post-install.log from your sdcard? Also, what is the contents of /proc/hwrev? It looks like for some reason your device was detected as a T959P as opposed to a T959V.
[Samsung Galaxy S (4G Model)] Kyndig66:
Will do. I'll need to reinstall it. The ROM lags horribly and I just flashed back to the previous build. Can't wake the device up sometimes, warm boot hangs. Battery pull often needed. App installation is hit and miss. I'd hold off on a full release. I'll help any way I can.
[Samsung Galaxy S (4G Model)] Kyndig66:
hwrev only says 0xD.

Log attached
[Samsung Galaxy S (4G Model)] heliosophos:
How much mb should i create the ext4 partition?
[Samsung Galaxy S (4G Model)] xc-racer99:
It depends on how many apps you want to install and how big your SD card is. For me, I have a 2GB ext4 partition on a 16GB card. I currently have ~20 apps installed (not big games) and have 1.4GB free still. At the very least I would make it 500MB.
[Samsung Galaxy S (4G Model)] heliosophos:
ahhhh ok ok now i get it... I thought it was for OS...now i have another question... i already have CM 4.2.2 with CWM 6... i won't have any problems? ty for answering btw :good:

---------- Post added at 11:54 PM ---------- Previous post was at 11:33 PM ----------

Can I create an ext4 partition using my pc with minitool partition wizard without any problems?... and only ext4?... also I already have CM 4.2.2 with CWM 6... so I won't have any problems with that? ty!
[Samsung Galaxy S (4G Model)] xc-racer99:
Well, it does use a slightly different partition layout. While in theory it may work, the first time you install may fail - do not panic, just reboot to recovery and install the zip again. This is because (if) it fails, it still installs the new kernel with the updated partition scheme which is there when you reboot to recovery.

Minitool partition wizard should work, it did when I tested it a while ago (I don't have a Windows computer so I can't test again).
[Samsung Galaxy S (4G Model)] Kyndig66:
I always use Gparted
[Samsung Galaxy S (4G Model)] heliosophos:
HELP

Guys i need your help... i installed with no problems this rom... but i extracted the sd card and i didn't know that the OS install stuff in the sd card... so the OS doesn't work anymore... and now i have problems with the data partition when i try to install again the rom... it gives me the error "failed to mount '/data (no such device)" and when i check the data partition on TWRP it says "present:no, size:0mb, free:0mb, removable:no"... and i can't wipe the partition... when i try to format it in fat, fat32 or any other... the TWRP freeze and reboot again in TWRP... so i don't know if a have to install another TWRP version with odin and format the data partition or is there any solution? also i get the error "updater process ended with error:7"... so pls help what should i do or any solution? i really don't wanna use odin t.t

BTW: ty for reading this and taking time to answer... and sorry for my english xD pls help! ty!!!!
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, so the issue is that there is no longer a data partition so you obviously can't wipe it. You need to create a second partition on the SD card. I would recommend doing this on the computer, using MiniTool Partition wizard (or similar) - created in f2fs or ext4. Alternatively, if you don't have a card reader, you should be able to do this in TWRP with the Partition SD card function - set the sd-ext size to whatever you want the size of /data to be (typically 2048MB/2GB is around right) and the swap size to 0. Do note that this will wipe the SD card entirely. If you use the TWRP method, you might get an error when booting up saying "unsupported SD card" and asking you to format it. Do NOT do it as it wipes both partitions off the SD card.

Hope this helps, let me know if you need clarification on anything.
[Samsung Galaxy S (4G Model)] heliosophos:
Ahhh ok ok... i do have a SD card reader, but the rom will detect automatically that partition i created or i need to do something else? the reason i removed the sd card were becouse the app link2sd keep telling me error trying to create a scrip with the partition i created on TWRP, so i remove it becouse i thought it was damaged or something like that... i'll try that..ty for answer me
[Samsung Galaxy S (4G Model)] xc-racer99:
Yes, the ROM automatically detects the second partition. link2sd and/or app2sd scripts do not work on this ROM as I've essentially implemented them at a lower level already
[Samsung Galaxy S (4G Model)] heliosophos:
ahhhhh ok ok i get it... the second partition f2fs or ext4 needs to be primary or logical? couse i'll use minitool partition wizard ty for taking time to answer me...really... ty!!!
[Samsung Galaxy S (4G Model)] xc-racer99:
Has to be primary.
[Samsung Galaxy S (4G Model)] heliosophos:
ok ok, now my phone is back to life... but it doesn't get root anymore, i can't wipe dalvik and the error says "failed to mount '/data' (operation not supported on transport endpoint)" when i try to wipe it... so what should i do to root it? factory reset works but at the end shows the same message in red letters... i do factory reset and then install super SU 2,76 and the phone doesn't get root... it says "succesfull" at the end shows that error... what should i do? btw: i was able to root it before with that version of super SU
[Samsung Galaxy S (4G Model)] xc-racer99:
Odd that you can't wipe dalvik, I would try re-running the ROM install zip to clear out any cobwebs.

I've personally never tried SuperSU 2.76, the highest I've used is 2.70 (I think). This is also the version that I built the systemless part around, so there may be incompatabilities with other versions. You could try removing /data/su.img (if it exists) (you can do this from recovery in the terminal emulator if need be - run "rm /data/su.img"), and then creating a file in /cache or /data called .supersu with the contents "SYSTEMLESS=false" (without the quotes) to force the install in system-mode.
[Samsung Galaxy S (4G Model)] heliosophos:
how do i create that file? to install the superSU with system-mode... i downloaded 2.76 with aroma
[Samsung Galaxy S (4G Model)] xc-racer99:
Well, from recovery, in either the terminal emulator or from an adb shell, run the following command (make sure /data is mounted first):

echo SYSTEMLESS=false > /data/.supersu

Alternatively, wait until tomorrow morning and I'll have a new build uploaded that brings support for 2.76 in systemless mode, I'm just putting the finishing touches on it right now.
[Samsung Galaxy S (4G Model)] heliosophos:
:eek: omg that sounds amazing... how can i know the new things? i'm so excited! i wanna ask you something... my notification bar turns black when i check it... is that something that needs to be fix or the problem is my rom? i wanna tell you that you're work is amazing!!
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright to "fix" the black notification bar, got to Settings, Performance (you may need to enable developer options first by going to About Phone and clicking on Build Number repeatedly), then I think its under Advanced, but the option that you want to enable is "Force High-End Graphics".

I'll post a brief changelog of the device-specific changes when I post the new build (uploading now, but won't update this thread until tomorrow - and it may not be until late afternoon). For all the common omni changes, you can view their gerrit at http://gerrit.omnirom.org/
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Changelog for 2016-08-02

First unified build (ie it works on both the T959P and T959V)

Screen recording now works in portrait mode

MMS should be able to be sent when data is disabled (will still use data though)

Default Camera app portrait photos are no longer square

SuperSU systemless updated to 2.76

Slightly less audio latency with UI sounds (and some sounds have changed)

Data should also be working on boot

Slight changes to battery and graphics config

Security patch level of August 5, 2016 (I'm a time traveller...)

md5sum: df587e0bd69552e0ece4b4ba3e214f45

Huge thanks to [MENTION=7393498]rich@rd[/MENTION] for testing on the T959V the unified build, his help has been essential to making sure the GPS is still working there. Build is currently only on Google Drive (in the Unified folder) as I seem to be having issues uploading it to the mirror right now.
[Samsung Galaxy S (4G Model)] heliosophos:
Downloading!!
[Samsung Galaxy S (4G Model)] Kyndig66:
My mirrors:

Mirror #1 Google Drive

Mirror #2 Dropbox

MD5 - DF587E0BD69552E0ECE4B4BA3E214F45
[Samsung Galaxy S (4G Model)] robonxt:
Wow... So many new updates... Gotta start finding where I stash that phone and start hacking! Thank you [MENTION=5414656]xc-racer99[/MENTION] for spending time to work on this amazing old phone!
[Samsung Galaxy S (4G Model)] heliosophos:
well nice rom... it works really nice... although sometimes it says that system is not working and if i wish to close it... and after 4 days with it all of the sudden system crashed and i had to factory reset it... when i turn the phone on... the omni logo just shows once and then restart over again... but anyway... i wasn't able to root with the systemless either... might be couse the partitions problems i have... so i installed the gapps so i can have playstore... it works but when it should start to install the app it just download the app all over again... its a infinite loop... do you know how can i fix it without being root? ty so much!
[Samsung Galaxy S (4G Model)] xc-racer99:
Odd, I haven't had any crashes like the one you've described.

With gapps, I haven't tried any recently, but last time I tested they worked just fine. I've only ever tried the smallest OpenGapps package (if you already tried this one, maybe download a different day - some days have bugs in them).

With root, did you flash SuperSU2.76? On the latest build, this is the only one that is officially supported. I am working on a method of getting things to work better, but its yet to reach production levels as there's still a few bugs to work out.
[Samsung Galaxy S (4G Model)] xc-racer99:
It's coming...

[MENTION=6794010]Coldwindofnowhere[/MENTION] and others

Got Nougat to boot on my SGS. FC's like crazy with com.android.phone (among others), disabled video decoding, camera, and bluetooth to get it to build; needed some kernel stuff to boot properly along with several hacks. Will try to cleanup my work so others can use it; watch the staging/aosp-7.0 on my github (probably no more updates today though). Good news is that our RIL version is still supported so that should eventually work once we re-enable all the hacks for the blobs...
[Samsung Galaxy S (4G Model)] robonxt:
...And I just updated my phone to the newest M version! WOW!
[Samsung Galaxy S (4G Model)] mataflakitas:
Woooow ...7.0 im waitt ...thanks x-race .....:D:D:D:D:D
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, I've failed to get RIL working on Nougat :( I think the issue is well beyond my abilities, probably would need to directly modify the libsec-ril.so binary as we're getting a SIGSEGV with rild somewhere. It works roughly 1 in 20 times, but causes a SoD the other 19 times... (but I could disable it entirely and probably avoid the SoD). I haven't worked at all on the hardware video decoding problem.

If anyone wants a semi-working Nougat build just because, let me know and I can upload one. I can also push the changes to get it booting to my github. I doubt I'll work too much more on it, and I don't think I'll upload another Marshmallow build unless there's some major security flaw that gets revealed (ie stagefright) (or if I feel like it;)). However, I may try some alternative RIL code on Marshmallow just for the heck of it.
[Samsung Galaxy S (4G Model)] robonxt:
Pretty. Please. ?! ;)

Thanks for working to bring Android N to this device!

I'm interested in building/compiling my own ROM, any suggestions where I should look first and start?
[Samsung Galaxy S (4G Model)] xc-racer99:
Sure, I can run off a build, make sure it boots, and then upload it. Might be a few days though.

For building your own ROM, you can see the official Google docs on building AOSP at https://source.android.com/source/initializing.html, you can also check out xda-university at http://xda-university.com/as-a-developer/introduction-how-an-android-rom-is-built.

If you're wanting to build this particular ROM, check out post #2 of this thread. If you run into any issues, send me a PM.
[Samsung Galaxy S (4G Model)] robonxt:
No hurry, thanks for all your hard work!
[Samsung Galaxy S (4G Model)] xc-racer99:
Nougat Build

Alright, so here is the experimental Nougat build of AOSP.

Built-in Camera app doesn't work (OpenCamera does, but only for photos), hardware decoding/encoding is broken (that's why there's no video), GPS is busted, and RIL is totally busted and disabled (so anything that needs the cell network is not working, like MMS, SMS, calls, data, etc). BT, wi-fi, and most other things should work. Also, there's no Browser app. I haven't tested gapps as I use FDroid all the time.

It does mess about with the partitioning scheme, so you may need to go back to GIngerbread after using it, YMMV. This is an unofficial build and very limited support will be offered.

Download from https://drive.google.com/file/d/0B7vXjzo0Hj-iNTRQUmxzRWhiU1E/view?usp=sharing

Edit: And to root, flash the attached Magisk zip. You can then install any of the modules, including Superuser, from http://xdaforums.com/android/software/mod-magisk-v1-universal-systemless-t3432382. Don't try flashing the uninstall zip or any of the official Magisk install zips as they won't work.
[Samsung Galaxy S (4G Model)] mataflakitas:
Graciet ....?????

Enviado desde mi Nexus 6P mediante Tapatalk
[Samsung Galaxy S (4G Model)] xc-racer99:
Nougat status

Alright, I've been working in the background on 7.0 (I know, I didn't think I would but, you know... :)) Here is my status:

RIL is now working (data and SMS for sure, presumably calls as well)

GPS is working on the T959P (can't test on the T959V as I don't have one, but I expect it will work too)

Hardware video decoding is now working

Video capture is still busted in all camera apps

Hopefully I'll get around to uploading a new build sometime. The partition scheme will change again, I'll have more details on that when I upload the build (basically it formats the SD card to ext4 and uses an emulated SD).

Edit: Download link is at https://www.androidfilehost.com/?fid=457095661767098516 The first time you flash, it will error out. Flash it again and it will go properly. PLEASE NOTE: It will wipe your entire SD card! In order to make things work better, I've set it up to use the entire SD card as /data as opposed to having two partitions. The advantage is that you don't have to pick a size of /data. Also, the recovery doesn't work very well (ie you can only sideload a zip package afterwards). To get around this, replace the ramdisk-recovery.img in the zip with the one attached to this post (built against 6.0, but it works for the most part (except restoring...))
[Samsung Galaxy S (4G Model)] robonxt:
Thanks! I'll find time to backup KItkat and see if this old phone can still call with Nougat

EDIT: it's working! 7.0 on this old s4g! Thanks [MENTION=5414656]xc-racer99[/MENTION]!

Downloading stuff from the built-in browser doesn't work until you go to settings and enable storage permissions for it. Same thing with app installer, I had to adb install from my computer. I fixed after clearing the data for it.

How do you get Magick to work? I flashed the v6 zip in your post and there was no icon for it. Do I need to install the Magick Manager apk from their thread?
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, flash the attached zip (its updated to Magisk v7). Then, if all you want is root, flash the file from http://xdaforums.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921 and then install the SuperUser zip from FDroid/Play store (instructions in that link). Otherwise, you can look through http://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 for full instructions. Do not try to use any of the built-in install/uninstall zip/features in an app as they will not work with our non-standard boot image.

With the Browser permissions, yes, that's because I'm using the Marshmallow browser as the Nougat browser is just a testing shell that can't really do anything... I haven't noticed any issues installing APKs directly from a file manager.

I'm still working on getting video recording to work, I think http://review.cyanogenmod.org/#/c/165008/ should be a solution. I'm also working on getting it so that we need fewer build hacks and also trying to get slightly better performance.
[Samsung Galaxy S (4G Model)] xc-racer99:
7.1 is coming....

Google released the 7.1 source code in past couple of days. Surprising, nothing really needed changing (save the build hacks) so 7.1 is now booting on my T959P. I'll try to upload the build later today. I did also manage to get video recording on 7.0. I have no idea what works properly on 7.1 but I suspect most things will.
[Samsung Galaxy S (4G Model)] robonxt:
Is there going to be a 7.X thread for this phone? And thanks for keeping on working on this phone, you da best!
[Samsung Galaxy S (4G Model)] xc-racer99:
Yeah, I might as well create one sometime. Not look a ton of people use this phone though. I'll post the link to the new thread here when I create it.

Edit: Thread is at http://xdaforums.com/galaxy-s-4g/development/rom-aosp-7-x-galaxy-s-4g-t3485237
[Samsung Galaxy S (4G Model)] kripget:
Nice rom! Good job! Working perfectly fine! Just a bit laggy but awesome for its running on marshmallow os! Thanks a lot for your efforts!
[Samsung Galaxy S (4G Model)] powerpoint45:
Great! I got it working after partitioning sdcard from within TWRP.
[Samsung Galaxy S (4G Model)] slaithe:
Ah, I've had much more success with this!

My phone is still often quite sluggish (I have gapps pico), but I'm still able to install all the apps I want while with ASOP 7.1 (with gapps pico), it was quite unuseable.
[Samsung Galaxy S (4G Model)] graycow9:
Been awhile, playing around with OMNI Mallow I find a smoother experience with KSM turned off and su enabled on boot :o

The 7.1.X ROMS recoveries aren't playing nice with my T959V[emoji14]still looks nice though :) I like the Lineage camera app
[Samsung Galaxy S (4G Model)] graycow9:
Still on the Mallow here :) finding more and more stability and speed to tweak in. I even have GAPPS installed so it's pretty incredible.

Not sure if it helps but I plateaued out my minfree settings- so the first 2 are at 20mb- the second 2 are at 45mb- and the last 2 are at 54mb.

I assume it works because the values change less. But no freeze on Worms and my battery is more solid.
[Samsung Galaxy S (4G Model)] slaithe:
I now have an unlocked T-Mobile Galaxy S4 running Optimized LineageOS and loving it!

https://xdaforums.com/galaxy-s4/i9505-orig-develop/jdcteam-optimized-cyanogenmod-14-0-t3479888

As for my still functional Galaxy S 4G, I keep it in airplane mode, in battery saver mode, with pico GAPPS (open_gapps-arm-6.0-pico-20170127.zip).

Went into Dev options and turned off Background Processes. While I have a NOGAPPS/microG setup on my new S4, I can download any purchased apps on my old S 4G and copy apk to my new S4. I don't have many purchased and one certainly won't work as it most heavily relies on latest GAPPS. Too bad, so sad. Otherwise I'm using old S 4G a mini tablet, a timer, a music player, Kodi remote and whatever. As weak as it is, it still is useful, now and then.
[Samsung Galaxy S (4G Model)] Fury_Phoenix:
Corrupted

omni-6.0.1-20160607-telusgalaxys4gmtd-HOMEMADE.zip is corrupted. Specifically the boot.img.
[Galaxy Note 3 Q&A, Help & Troubleshooting] MaceFremonti:
On the old Jellybean browser you could save webpages for offline viewing. I am going through a divorce and need to convert these pages into files that can be worked with, i.e. get them to my attorney. Currently the only way to access them is to view them on the phone through the browser. Any help in locating these files or being able to work with them would be GREATLY appreciated. I found a database of the pages in data/data/com.android.browser but not the actual file of the saved webpage.....not that it matters but they are evidence of my soon to be ex spouse's "mistakes."