Database Info

[ROM][Beta][in-development] jMod 2.2/AOSP 2.2 - Android for the rest of us - 08/05/10 - G1 Android Development

Release Name: Android 2.2 AOSP Master for Dream/Sapphire
Release Version: AOSP080510-master, jMod080510-master
Release Date: 08/05/2010
Credits: AOSP. dferreira for the help fixing many, many issues. CyanogenMod for kernel/wifi module (from CM6RC2, only purpose being to get camera/camcorder working), Dream/Sapphire prelink map, libcamera2, and the huge APNs list. ChainsDD for SuperUser. XDAndroid Project for HW3D files. HTC for the sounds and some of the drawables on the theme (.9 drawables are mostly my work), and 25 wallpapers.
Base Firmware: 2.2 AOSP
Radio Required: 2.22.19.26i or higher (tested with 2.22.19.26i)
SPL Required: Any (tested with ENG SPL and Death SPL)
Partition Layout: Any/none, Ignored
Wipe Required: Yes
These are AOSP builds from master branch with the goal of having as complete an Android system working under regular SPL as possible.
None of these builds include Google Apps. They share the Gapps package system that CM6 uses, so, if you want to add them, look at Cyanogen's CM6RC2 thread for the download link.
There are now two builds, one called AOSP which is pretty much a fixed AOSP build that's as close to ADP1 builds as possible, and the other is jMod, themed and has a few of my personally liked additions.
You can expect both builds to have:
-Live Wallpaper support (none included)
-rosystem/rwsystem so you can easily mount/unmount system from terminal
-busybox
-SuperUser
-Cyanogen's huge APNs list
Additionally, jMod has:
-HTC Legend theme
-HTC Audio Package (small, to fit regular SPL)
-HTC IME (jMod, supports only en_US and is 1/4 the size of the regular HTC IME
-Over 50 wallpapers from HTC and AOSP
On top of that, you get jm-master.zip. What is it, you ask? It's a patch to build your own jMod. Download AOSP master branch to your computer, merge the contents of the zip into the downloaded AOSP code, then:
Code:
cd device/htc/dream
. unzip-files.sh
cd ../../..
. build/envsetup.sh
lunch (select a version from the list, these releases are based on options 9 (AOSP) and 12 (jMod))
make installclean && make -jx otapackage (where x is the number of your processor cores x2)
After a few minutes/hours, you should have your recovery flashable ota package, plus your fastboot flashable images (only need system and boot) at out/target/product/dream.
===Current issues/To Do list:===
-Only en_US locale currently supported. This was done deliberately to cut down on size and, the Dream being so limited in storage, I don't think I can add some more. I'm sorry, but if you want more languages, try CM6 instead.
-Gallery fixed in landscape position. This is due to a bug that causes graphical artifacts when changing orientation. Will re-enable orientation once it's fixed.
-Video recording issues. Video recording works, but just sort-of. Recording never finishes cleanly, so the file ends corrupted. It will play, but it will end in an error. Also, when finished recording, you get no preview until you either exit the activity or start recording again. To exit the activity, either press back or switch the button to camera and then back to camcorder. Also, recording quality is very, very low.
-On Settings>About Phone, System Tutorial does nothing. This is done deliberately to avoid a force-close when Google Apps are not installed. I'll figure out a way to check for gapps, if it's there, button appears, if not, it disappears. Until then, option does nothing.
Click to expand...
Click to collapse
Once all these are fixed, I'll release a patch update.zip along with the completed v1 with all patches applied for new users.
===These issues are specific to building from AOSP with my patches:===
-No SuperUser. This is temporary until I can build su and set it's permissions (04755) at build time. In the mean time, use the attached root patch below.
-Busybox available at /bin, but not linked tools at xbin, so make sure your scripts call busybox tool.
-The OTA Package might not flash to your phone from recovery. This is due to the updater scripts checking for radio and SPL versions. Specifically, it needs spls (0.95.0000, 0.95.3000, 1.33.0004, 1.33.2004) and radios (2.22.19.26I and 2.22.26.07). With some SPLs and radios, the build will refuse to flash. There's nothing wrong with your phone, it's just those useless sanity checks. I'll modify the lists of acceptable hardware based on user experience, so tell me if build works for you on your SPL and radio (let me know which). For the time being, you can flash system and boot from fastboot (remember to "reboot -w" for a wipe).
-Due to a change that was made for my the themed version, the clock display in the status bar is white. I added the drawables in the patch zip for a black statusbar for mdpi and hdpi devices so that you can see the clock regardless if your build is themed or not, you'll always have a black taskbar, but, if you wish to have none of that, omit merging /core and /services from /frameworks/base into your AOSP build.
Click to expand...
Click to collapse
Report back on any issues that I haven't come across. Don't ask for a2sd hack, or features not found on stock roms. If you want those features, use CM6 instead. This build is supposed to be as close to stock, but with root, as possible.
Also, I take hints, so, if you know how to fix some of the current issues (and it indeed fixes it), PM me and I'll add your name to the credit's list along with your contribution.
These builds are an ongoing work. Don't expect reliability or a "daily driver". Flashing is done under your own responsibility. If you don't like test releases, then go build it yourself and get out of my thread.
As always, feel free to take these builds and use as you please, even re-distribute as your own.
===Current Builds===
08/05/10 AOSP beta:
Download: AOSP080510-master
MD5 Sum: e05f2c24ffc463adb23ae093740dedd7
08/05/10 jMod beta:
Download: jMod080510-master
MD5 Sum: a56580b2b557588ffcb0f0fc1629790f
08/06/10 jMod beta proof-of-concept: build with odexed framework, with a "light" version of Google Apps already included (do not install CM Gapps on top of this), 60 MB free in /data at boot with regular Dream SPL.
Download: jMod080610-master-odex-gapps_lite.zip
MD5 Sum: 108c835a946dfaa8a070ae453d35b538
08/05/10 jm-master AOSP patch:
Download: jm-master.zip
MD5 Sum: f274701352c19788a27aeb0749b74334
06/23/10 root patch for AOSP (flash from recovery):
Download: root.zip
MD5 Sum: b86ba3ed1f39d56a2eeba17274ac8811
===Previous Builds===
6/23/10 Test Build:
Download: AOSP062310-master.zip
MD5 Sum: be60d79da3a88c2146108bed5a70cecf

Hey JIT works correct?

Ace42 said:
Hey JIT works correct?
Click to expand...
Click to collapse
Testing the libdvm.so from this build as we speak.
Hmm, no dice on CM 5.0.8. Since the init.rc in the ramdisk is what reflashes the recovery image, it should be easy enough to take that out though.

It fails at verifying for me, running RA recovery 1.7.0, dumps this on the screen:
Installing update...
assert failed: getprop("ro.bootloader") =="1.33.2004" ||
getprop("ro.bootloader") == "1.33.0004" || getprop("ro.bootloader") == "0.95.3000"
E: Error in /sdcard/full_dream-ota-eng.jubeh.zip
(Status 7)
Click to expand...
Click to collapse
Any help? I believe it is searching for bootloader version 1.33.2004, which is probably a typo of 1.33.2005, which is the engineering SPL I use.

Gonna do a full nandroid backup then wipe EVERYTHING and test. Unless that's a waste...
Sent from my HTC Dream using XDA App

I love living life on the edge. Will flash this since it is an AOSP
Hope a dev looks at this :3
EDIT: Same problem as other guy
Installing update...
assert failed: getprop("ro.bootloader") =="1.33.2004" ||
getprop("ro.bootloader") == "1.33.0004" || getprop("ro.bootloader") == "0.95.3000"
E: Error in /sdcard/full_dream-ota-eng.jubeh.zip
(Status 7)

atomsk813 said:
It fails at verifying for me, running RA recovery 1.7.0, dumps this on the screen:
Any help? I believe it is searching for bootloader version 1.33.2004, which is probably a typo of 1.33.2005, which is the engineering SPL I use.
Click to expand...
Click to collapse
It doesn't know about Danger/Death SPL, replace the assert getprop line in updater-script with the one from CM's update.zip & you're good.
I see it's missing the htc proprietary binaries, and seems to have both a update-script and updater-script. Calls probably wont work on this, does anyone one know if the eclair gapps are going to work for this? Otherwise, we're dead in the water till the mytouch(or other msm7k) froyo release

Nothing wrong with this that an update to the ramdisk and the meta-inf won't fix working on it now

uploading a fixed one soon

what works? wi-fi, camera etc... still broken?

Beackman said:
what works? wi-fi, camera etc... still broken?
Click to expand...
Click to collapse
+1 is everything working? is JIT working?

updated first post, no longer flashes recovery and it should install just fine now on all SPL.
As I said, the previous one was completely unmodified for ADP devices.

Flashing soon

Alright, I edited the original zip and got rid of the ro.bootloader and recovery stuff. I signed it, flashed it, and it does work.... well, parts of it.
Let's go over what does work:
It boots.
You can open applications (And as stated before, no gapps)
You can go into the settings menu and change.. um.. settings
Bluetooth works (It at least loads, I have no Bluetooth device to try it with)
Here is what does not work:
No wifi (No firmware, needs to be added)
No phone (Does not get signal)
No 3d
No gapps
No Camera
And probably many more.
Should you flash this? Probably not, unless you are willing to hack away to get everything working again.

Camera does not work, it says could not connect to camera. Calls and Data and wifi do not work either. Sound works, no 3d acceleration.

Lots wrong but I got it working nonetheless.. It's going to need to be recompiled with the binary files extracted, without it the music app and mediascanner will crap out(mp3s aren't recognized, etc). Don't forget to include the Superuser.apk, su and busybox binaries.
Gapps from 2.1 dont seem to work with it, major roadblock.
Wifi doesn't work because firmware in /etc/firmware isn't there, and apparently needs to be rebuilt because the old firmware didn't work.
The camera app displays what looks like an opengl test, then FCs, I'll give the old one a try.

sidroc said:
Camera does not work, it says could not connect to camera. Calls and Data and wifi do not work either. Sound works, no 3d acceleration.
Click to expand...
Click to collapse
Not cool . But hey this is XDA, where reverse engineering and and hacking are the norm .
I guess in the mean time I could start rethemeing.

Calls work if you install the libhtc_ril.so and libhtc_acoustic.so in /system/lib/ and the Audio* files in /system/etc/
Audio isnt working on my setup, did you do anything to make it work sidroc?
Also, disable pinyin and Japanese IMEs in keyboards & layout.

I have extracted some of the relevant files from my htc magic using the .sh scripts that are included in the source tree, but I don't want to flash what I've got for fear of overwriting my recovery.img. Does anyone know how to build a system.img that won't do that?

Wifi works if you push Fw1251r1c.bin into /etc/wifi , you can find it in the CR Froyo release

Related

Here's the HTC Magic Build w/ Arabic Support as requested for the Dream/Sapphire-32b. This build is based off Sapphire HTC Arabic Etisalat 2.56.494.7 as posted in this thread:
http://forum.xda-developers.com/showthread.php?t=565859
Before flashing this rom, like most other Roger builds, this requires SPL 1.33.2005.
The one thing this build has extra is Flash Support in the Brower like the Hero Builds. This is what I was primarily interested in, but in saying that, I decided to release a full build w/ all the extras from my KB7SQI's Roger Mod. This turned out to be quite a nice build. It's very quick & the flash support has been reported to be as good as what's included in the hero builds, but a bit faster. This build is also based on CUPCAKE & not DONUT. Don't bother asking if I'm going to add DONUT support. You'll have to wait till it released by HTC. Sorry, but it's already been asked. I hope the few who will really use this rom enjoy it.
Here's a quick run down. Several apps have been moved to /data/apps to support the G1/Dream. I've decided to Keep It Simple Stupid (KISS) from here on out w/ this mod. Here's the deal, if you want auto apps2sd, then flash the kb7sqi-a2sd-mod.zip after you flash the rom. The stock builds does come w/ an a2sd script in bin & if you choose to have a userinit.sh script on /system/sd, it'll run it otherwise it automatically sets the platform properly, enables compache by default and sets the clock speed to 528/245 Max/Min Mhz. This makes it a win/win for all & make things simpler for me to have to explain. But please NOTE, the auto apps2sd script I've included ONLY moves apps2sd, NO DATA! It's much safer that way. It works exactly the way Soulife's Roger's Remix version does and it's been customized for this build specifically! Thanks Soulife! Screenshots are posted below.
Changlelog:
V2.7.2 - Warez FREE and forgot to mention the following was fixed in V2.7.1
-Network Search was fixed by updating build.props file. Enjoy!
-QuickOffice was removed as requested.
V2.7.1 - Newer kernel & compcache and theme available!
-Since things have moved around a bit, I'd recommend doing a wipe before hand.
-Kernel has been updated w/ swap_free notify support for compcache-0.5.4 test2 and I've backport squashfs-4.0 from 2.6.29
-compcache-0.5.4 test 2 added
-AdvancedLauncher has been removed. If you want to add it back, feel free.
-compache is now enabled by default
-Removed Google Maps. Grab it from the Market.
-There's now a lite, full, & a theme that can be applied after flashing the rom.
-Lite is basically the build w/ Arabic support removed.
-Full build is as before w/ complete Arabic support for those who need it.
-I fixed the Google Sync Issue. Sorry about that.
-Made the builds much easier to maintain.
-Let me say I'm NO graphics guru first off. I have to say thanks to Soulife, Enomther, TheDude, everyone who provided parts from the following themes:
Hero, gChrome, enoch, zalgo and parts from the Cliq rom & Tattoo build. This is a mixture of something old & new. I basically tooks some png's from each & used them to build a mostly hero theme that had a simple/clean look to it. I hope you like it.
V2.5.1.1 - Fixes issues w/ optimized Browser/Flash Player.
V2.5.1 - Build has been optimized & a few minor updates the init scripts.
V2.5 - Initial Release
Here's the links:
Latest FULL version which is a FULL build w/ complete Ararbic Support:
http://dl.getdropbox.com/u/1701190/kb7sqi-magic-full-V2.7.2.zip
Latest LITE version which has all Arabic Support Removed:
http://dl.getdropbox.com/u/1701190/kb7sqi-magic-lite-V2.7.2.zip
Theme which is a work in progress:
http://dl.getdropbox.com/u/1701190/kb7sqi-magic-theme-V2.7.1.zip
And the a2sd update to be flashed after flashing either build:
http://dl.getdropbox.com/u/1701190/kb7sqi-a2sd-mod.zip

Here's the complete changelog:
- The kernel has been updated to 2.6.27-00399-gc7f8bce. This kernel inlcudes support for swap_free notify, tun, ipsec, ipfilter, ipv6, fuse, cifs, cramfs, squashfs-4.0, ext2/3, cpu scaling,. Close to what JF's 1.51 kernel contained minus unionfs support, and I didn't apply any multi touch patches. The kernel update was done because of the following security alerts:
- Kernel security update fixes a critical vulnerability common to all linux kernels that are un-patched (sock_sendpage() Local Root0 exploit).
http://www.ryebrye.com/blog/2009/08/...k-in-progress/
http://web.nvd.nist.gov/view/vuln/de...=CVE-2009-2692
http://www.securityfocus.com/bid/36038/exploit
- Updated the init.rc in boot.img to export TERMINFO
- Included the new wlan.ko in /system/lib/modules to be compatible w/ the new kernel and added the following changes:
- Removed most of the wallpaper/ringtones, notifications, etc. Needed the space!
- Added Wifi-Tether
- Updated the apn list
- Updated lucid script in /system/bin to the latest release
- Updated the build.prop to be seen as a T-Mobile G1/myTouch 3G so MyAccount 2.0 works, and protected/paid apps work correctly again.
- Added iptables to /system/bin - WiFi Tethering works great!
- Added Haykuro's HTC_IME.apk.
- Added Java from Hero. Jbed.apk in /system/app & libjbedvm.so to system/lib
Re-added Stericson's tweaked Amazon apk
Compiled/Added Compcache 0.5.4 test 2 w/ARM fix - Enabled by default.
I added these changes taken from Soulife's excellent Rogers Remix:
~added cyanogens sexy black terminal
~added cyanogens log collector (no more excuses for lack of logs)
~clearcache added to bin (clear Android Market, Browser, GMail, Google Maps, StreetView, Youtube cache)
~lowered boot sound in extended (so when i restart my phone at 2am i dont scare the **** out of myself)
Added rwsystem and rosystem to bin (just type rwsystem as su in terminal to mount system as read write etc..)
From Cyanogen's 3.9.9.1 release, I've added:
his terminfo in /system/etc/terminfo
his updated e2fsck, mke2fs, tune2fs, busybox, & his new htop port in /system/xbin
updated toolbox, sh, su in /system/bin
From Cyanogen's 4.0.2 release, I've added:
Added the dropbear SSH server into xbin

sweet thz and that's the only thing i want on my donut ty
FLASH FOR THE WIN

My phone has. everything i need now except a2dp. If we get it then it would the best fone. By the way which flash player does it have?

after flash just found out that this is 1.5 cupcake andnot 1.6 donut..

Thank you for the effort, from a development view point; is it possible to extract Arabic support from this build and have it ready to be applied to any build (Hero, Donut, and possible future ROM’s)? I’m sure Cyanogen, JAC, and the others have the knowledge to so.

Finally an htc magic rom other than haykuros great work can't wait for donut magic or magic with sense coming soon

anyway we can incorporate that ARABIC support in the newer Hero builds ?

can you port the flash player and flash to browser for donut please.. this rom is good

tried to install on Dream (G1) got this error
E: Can't chown/mod /system/xbin
(no such file or directory)
E: Failure at line 27:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
installtion aborted
any ideas, i have already tried to wipe

Hi,
Thanks for this new build.
To enable apps2sd do you do this?
#CONF_FILE="/system/bin/user.conf"
CONF_FILE="/system/sd/user.conf"
USERINIT_SCRIPT="/system/sd/userinit.sh"
apps2sd=1;
Thanks

bestwebs said:
Hi,
Thanks for this new build.
To enable apps2sd do you do this?
#CONF_FILE="/system/bin/user.conf"
CONF_FILE="/system/sd/user.conf"
USERINIT_SCRIPT="/system/sd/userinit.sh"
apps2sd=1;
Thanks
Click to expand...
Click to collapse
did you use it on G1?
can anyone confirm that it works on G1

yes it work fine on g1 with connected letters

It Works Perfect on G1, flashed from JACHeroSki 2.2 and RA Recovery.

It Works
thank you

xaxis said:
tried to install on Dream (G1) got this error
E: Can't chown/mod /system/xbin
(no such file or directory)
E: Failure at line 27:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
installtion aborted
any ideas, i have already tried to wipe
Click to expand...
Click to collapse
I can confirm now, i had to change the SPL to get it to work.. thanks everyone

At last, thank you so much for your work...I can confirm that its working.
Thanks,
-Gus

please if it is not too much to ask explain how to enable apps2sd swapping and other features. or let us now where to look
thanks

bestwebs said:
Hi,
Thanks for this new build.
To enable apps2sd do you do this?
#CONF_FILE="/system/bin/user.conf"
CONF_FILE="/system/sd/user.conf"
USERINIT_SCRIPT="/system/sd/userinit.sh"
apps2sd=1;
Thanks
Click to expand...
Click to collapse
this didn't do it!!

thanks aloooooooooooooooooooooooooooooooooooooooooooooot
you'r a hero

WWARNING:You must Have The Correct Radio and Latest SPL! You can find them here (RADIO MUST BE INSTALLED FIRST) You can find it here
PLEASE DO YOUR RESEARCH BEFORE FLASHING ANY ROM INCLUDING MINE IT WILL SAVE YOU AND OTHERS TIME AND HEADACHE!!!
AOSP Eclair (CyanogenMOD) forked source compiled by JAC. Thanks to Cyanogen for making the source public. Source available here http://github.com/cyanogen And of course Thanks to all the devs on XDA and in the Android community in general for making Android better for the masses.
Install as usual please wipe for good measure. The Danger/Haykuro SPL is required folks as stated above.
If you like what I do consider donating here
We are no longer on 2.01 source. If you are using beta3 with 2.01 source please upgrade to the current stable 1.0 which is compiled using 2.1 source.v1.0 2.1 source was release on 1/27/2010
xROM-Eclair-1.1
-G1/MT3G support
-2.1 AOSP Source with tons of enhancements by Cyanogen and JAC
-5 Screen Launcher.apk
-MT working in Browser.apk and Gallery.apk
-Swipe gestures in Gallery.apk
-Modded Settings.apk with Ext partition info
-A2SD support for ext2/3/4 partitions with noatime etc
-safe boot and shutdown eg. checks for fs corruption
-Cgroup tweaks
-Gallery3D
-Wysie's phone.apk
-Voice to Text service working
-working livewallpapers thanks to jubeh
-lib updates
-Camera lib from (Ncommander)
-Modified APN list
-Reboot option from the power button
-Amazon MP3
-FLAC support
-VM tweaks
-Tether support for USB and WiFi
-TCP optimizations
-Tons of etra modules CIFS AUFS etc
-ZipAligned and Png opt
-RIL tweaks
-Commandline extras: powertop etc
-lock home app in memory control from spareparts.apk
-Compcache control from spareparts.apk
-WifiTether for Eclair included
Kernel
-2.6.29.6-jac kernel compiled for Eclair
-Eclair 2.0 MT API
-Modified RAMdisk for Eclair with trigger support for init.rc etc
-Nexus sdcc driver
-ext2/3/4 FS support
-Squashfs 4.0 and AUFS support
-CPU scaling and freq tweaks
-Deadline I/O fifo=1
Compcache modules compiled with the latest source (01/14/2010)
-many more tweaks for speed and stability
Changelog:
Memory leaks in openssl fixed
Su request issues fixed
reverted vendor.apk
removed provision.apk
VM Tweaks
updated contacts.apk
Download
xROM Eclair 2.1 Stable v1.1 www.justanotherdev.slackdev.com/xROM-Eclair-2.1-1.1.zip
MD5:89395fa568446454aa667a52d751b83e
xROM Eclair Dark www.justanotherdev.slackdev.com/xROM-Eclair-2.1-1.1Dark.zip
MD5:a457d2793e4a89ce48daefba781a0d79
Follow me on Twitter

Source from Cyanogen Many thanks! Heres a quick rundown on building for Cyanogen
You will need to have the standard build envrionment setup for Android available at http://source.android.com/download
The source is available to be repo'd from repo init -u git://github.com/cyanogen/android.git -b eclair
then
build as usual make sure to check out the Cyanogen vendor trees and include the buildspec.mk with this data below
TARGET_PRODUCT:=cyanogen_dream_us
TARGET_BUILD_VARIANT:=eng
TARGET_BUILD_TYPE:=release
You may run into some issues with @Override and Java 5 as well as other misc issues I had to overcome. The most recent repo does not build as is..will try and get more info up soon

first =), glad to see you back JAC

Working great for me! Flashed from CM 4.2.11.1 without wipe with no f/c's or problems.
Would be nice if you could include bash and nano, but I can manually push them over from CM. Just waiting for a ram hack version of the kernel

senab said:
Working great for me! Flashed from CM 4.2.11.1 without wipe with no f/c's or problems.
Would be nice if you could include bash and nano, but I can manually push them over from CM. Just waiting for a ram hack version of the kernel
Click to expand...
Click to collapse
I enjoy ram hacks, but they seem to break bluetooth for eclair roms. Gonna flash this later and see how it is, I'm sure it will be good though.
Nice to see you back JAC

justanothercrowd said:
-Reboot option from the power button
Click to expand...
Click to collapse
where can i find this in the Source?

Does this include the modifications in Phone.apk that Cyanogen uses in his current builds?

Long press the power buton, you'll find the reboot option.

pj_bj said:
Long press the power buton, you'll find the reboot option.
Click to expand...
Click to collapse
He wants the source for it, meaning he wants to be able to either, 1) Make his own rom and include this feature, or 2) Wants to pt it in an existing rom

Glad to see you back. Can't wait to flash.

E: Can't chown/mod /system/xbin/busybox (no such file or directory)
E: Failture at line 23: set_perm 0 0 04755 SYSTEM:xbin/b
Installation aborted.
This comes when i try to flash over my wiped CM 4.2.11.1 on T-Mobile G1

bluedragon1982 said:
E: Can't chown/mod /system/xbin/busybox (no such file or directory)
E: Failture at line 23: set_perm 0 0 04755 SYSTEM:xbin/b
Installation aborted.
This comes when i try to flash over my wiped CM 4.2.11.1 on T-Mobile G1
Click to expand...
Click to collapse
You need the Danger/Haykuro/Death spl

JAguirre1231 said:
You need the Danger/Haykuro/Death spl
Click to expand...
Click to collapse
justanotherdev via twitter
@bluenazgul it should fit on the stock SPL..i havent actually tested that though
but i dont want to change SPL cuz the warranty

I would like to make a port for 32A/EBI1, where can i find the source code of 2.6.29.6-jac kernel?

The Gapps you're using on this rom are from the milestone dump, huh?
Do you know exactly what it was that cyanogen did to fix the Google Sync problem?
I'd like to get that change into my AOSP build. I haven't looked (or even cloned) the source yet, but I've got a hunch it's something he changed on his sync provider. Guess I'll check out the source.

welcome back,JAC!

Just flashed xROM Eclair/AOSP, I had to admit it's awsome one. It takes 4 mins for the first reboot, that's the fastest first reboot amoung all the eclair roms i've flashed. But for me , there are some problems:
1. I've got android.process.acore FCs for several times.
2. There's no swap support for this rom by default, when I add swap, the phone seems to be faster. Is swap recommended for this rom?
3. I use Mybackup Pro to backup my phonebook, but only 25 of my 500contacts will be restored, which never accured on donut and cupcake.
Thanks JAC for your excellent roms and happy new year.

bluedragon1982 said:
justanotherdev via twitter
@bluenazgul it should fit on the stock SPL..i have not actually tested that though
but i dont want to change SPL cuz the warranty
Click to expand...
Click to collapse
I'm sure you can roll back to stock spl at any time, and the haykuro spl brings so much more space for apps and such. Anyways the only thing I can see if you need to use the warranty is if you brick, but if you do that then they can't see what spl you have anyway

waaaaaaat a new xrom took so long thank u

Amazing!!
Incredibly fast. Animations are sweet! Flashed this over wesgarners Y rom. No problems that i noticed. Didnt get to try out BT. Played Zilch.... Whoa so fast!!!!
Thanks to you, Cyanogen, Et al.....

Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
Make sure you have a second partition on your SD card formatted to ext4 before flashing!!!! This can be created with either CWM recovery or with TWRP. gparted on Linux should also work. If you "SD card not supported" try repartitionning. If you get "Encryption unsuccesful" then you need to format the second partition as ext4 (or f2fs, your choice).
If on a BML rom (stock-based GB)...
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. It will reboot a couple of times, don't be worried.
4. If you want gapps, reboot to recovery, wipe data+cache and install gapps.
5. If you want root, flash SuperSU whenever
If on an MTD rom (CM7 and all ICS+)
1. Reboot to recovery
2. Wipe data, dalvik/art cache, system, and cache partitions
3. Install zip
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess.
Bluetooth only enables from the notification pulldown, not when you go directly to settings. It does work just fine afterwards though
If you're coming from either the last Lollipop build or the initial pre-release Marshmallow build, there is a bug in TWRP that will prevent flashing anything but the ROM. To get around this, please flash the Marshmallow zip, then reboot to recovery, and then follow the typical instructions.
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
If you come across a bug, feel free to let me know by posting in this thread. I will not be working non-stop on this project, but will try to fix bugs that affect me as this is still my main phone (out of choice, not necessity).
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Video Recording
Automatic Brightness
Encryption
Compass
GPS
Headset Buttons
Semi-Working
Powered-off charging animation - works at first, but then stops working. Seems to be an Omni problem, but it still charges...
What doesn't
SElinux is currently in permissive mode. Will not be going to enforcing, this would require a data wipe as well
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+
Everything else is not tested!!!
XDA:DevDB Information
Unofficial Omnirom 6.0 for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/omnirom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: OmniRom
Version Information
Status: Beta
Created 2016-01-11
Last Updated 2016-05-12

Thanks Time!
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to the OMAP4 AOSP team for their work on porting CMA to a 3.0 kernel.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-6.0 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree (create the local_manifests folder if necessary).
After syncing the source, open a terminal and in the directory where you downloaded the source code type "./device/samsung/aries-common/patches/apply_patches.sh" to apply the patches necessary to have a working build. Then run "source ./build/envsetup.sh" and then "brunch galaxys4gmtd". For future builds, only the envsetup and the brunch parts are necessary. Please note that you will have to re-run the apply_patches.sh script after each time that you run repo sync. (Note: the patch script no longer runs automatically)
You should be able to use my trees for other first-gen galaxy S devices. You will need to apply a patch similar to https://github.com/xc-racer99/andro...mmit/fe6bc6b82881a12fc4a5647812f3cf0f52f79c6a to your device tree (if coming from Omni 5.1). I haven't done anything to P1 trees and may have broken the kernel for it...
Changelog
2015-12-20
Initial pre-release - many bugs
2015-12-26
Second pre-release - fewer bugs, but still plenty
2016-01-07
Initial actual release. Quite stable with minimal bugs
2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
Added T959P build
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
Added download mirror thanks to @FBis251
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Changelog for 2016-02-29
Updated Omni source - plenty of new features
Low-resource spinner from LegacyXperia (means that the loading spinner isn't the only thing using the CPU)
Miscellaneous performance tweaks (see github if interested)
md5sum for T959V: a7aa8cca3259208eafba7c2cccecdbfd
md5sum for T959P: 879256c93a0e58de0fb9c9e1be91e0e9
Changelog for 2016-04-02
Security fixes in the kernel
Freed roughly ~4MB of RAM in kernel
Updated android drivers resulting in better multitasking
OpenDelta updating system removed as we weren't using it (it used ~3MB of RAM)
Recents menu now has less lag when opened
Selinux contexts have changed. It could likely be put to enforcing now but this would require a complete data wipe so its still permissive
Live Wallpapers removed - we're low-ram
Bootanimation now fits the screen better
PowerHAL removed - it was broken and has been for a while...
Misc other changes - if you didn't notice problems, you won't notice the solutions
Known bug - Camera on T959V is broken...
md5sum for T959V: 247a721f4c27c5191a2a460e4c72ba3b
md5sum for T959P: d15339d8aa10f765155bdd8d1bb0c5f5
Changelog for 2016-04-08
Fixed camera on T959V
Security patch level of April 2, 2016 (latest to date)
Headset buttons fixed
T959V md5sum: 2b1560b99402c73275d1f69b3ceb9a22
T959P md5sum: e102cce0d624383fb85a32321c98c645
Changelog for 2016-05-09
Uses CMA kernel by default
Performance Control can now modify voltages
Systemless SuperSU is now supported
WebM playback is now working
EFS backup in TWRP now works
Data on boot should now work - no need to toggle airplane mode anymore
md5sum for T959P - 118789dd68760d9fd18cc961398bf346
md5sum for T959V - f9375a8d9792c3a0d222c113213c014d
Changelog for 2016-06-07
Security patch level of June 1, 2016
Microphone mute now works when in call
Battery now charges to 100% and should read properly after a system crash
Standby times should be improved
Slightly less RAM - but should result in better graphics performance
CMA crashes fixed (at least, I haven't crashed once since I started testing the patch a week or so ago)
PowerHAL is back - CPU is boosted when turning screen on to avoid delay
md5sum for the T959P: eeed77fb84189e84f2264e32d18ce454
md5sum for the T959V: b6457319d248029429183c342514b072
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

Source, Downloads, Misc Notes
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-6.0-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-6.0 branch). The patches folder holds all the necessary patches along with a script to apply the patches.
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-6.0 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-6.0 branch)
Downloads!
All builds are found at https://drive.google.com/folderview?id=0B7vXjzo0Hj-iOGJ4dmdCd09OZmM&usp=sharing. As well, recent builds are mirrored on https://files.fernandob.com/#xc-racer99/Omni6.0
Gapps
Gapps cause the first boot to be very, very laggy. Things do improve after that. The best way to get through the Setup Wizard (IMO) is to skip everything possible (ie connecting to Wifi, settings up a Google Account, etc) and then reboot. You can manually add a Google Account later in Settings. While any (small) Marshmallow gapps should work, I have had success with OpenGapps pico package from www.opengapps.org (untested on recent builds).
SuperSu
SuperSu can be found at http://forum.xda-developers.com/apps/supersu. If on May 2016+ builds, systemless 2.71 works (other systemless versions may work, untested). If you're on an older build, you need to either force system mode (create a file in /system or /data called .supersu with the contents "SYSTEMLESS=false") or use an older version (ie version 2.52 or earlier). August 2016 build updates the systemless to 2.76.

Woooow thanks

As you suggested, Gapps caused lots of problems...made the ROM very slow and laggy, lots of FC's, lots of random reboots, etc. I re-flashed without Gapps. Was able to restore apps with TB and root with SuperSu. The basics...calling, browsing, messaging, camera...are working fine. Haven't taken it for a ride yet, but GPS test picked up 5 satellites and I haven't even taken it outside yet. If I desperately need another app, I guess I can find the .apk somewhere. Since I did a TWRP backup, maybe next week I'll try the pico gapps again and see what happens. At any rate, wonderful work.

Update: Took it out for a spin this afternoon....GPS works fine.

Been running the 1/7 for a few days. loving it so far

New Build Uploaded!
Alright, I've uploaded a new build
Changelog for 2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
I've also uploaded a T959P build as I had a request for one. Let me know if you guys find any more bugs.

New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.

DickyG said:
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.
Click to expand...
Click to collapse
Sounds good. Do note that when/if you flash gapps, you will need to do a complete data wipe first, otherwise you will get force-closes like crazy.
I've always just reflashed SuperSU manually and never relied on the script to restore it so I can't help you there.

Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.

SuccubusInc said:
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.
Click to expand...
Click to collapse
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.

xc-racer99 said:
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
Click to expand...
Click to collapse
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Installing '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: run_program("/tmp/updater.sh") = = 0
E:Error executing updater binary in zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Error flashing zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Updating partition details...
Click to expand...
Click to collapse
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.

SuccubusInc said:
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
Click to expand...
Click to collapse
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.

xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
I'll try out Blastoff if I can find it. But it probably failed because I did not partition my sdcard. I'll see if that helps later.
Thanks a lot.

xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
Hey, xc-racer99, after about four assorted blind attempts at installing your work, I flashed back to stock/AntonX kernel with Heimdall and full wiped, then used CWM to create a 4GB partition on my sdcard. The ROM installed through CWM, then TWRP without an error and booted up after fifteen minutes or so of OMNI animation, and is running on my SGS4G without any issues. The only noticeable lag was for the first five minutes after the initial boot. Now my device is gliding smoothly after a few tweaks in the performance settings and turning off background processes. Thank you so very much.
Next time, I'll read the entire post before blundering through the install process with the assumption that I know what I'm doing [as usual].
Sorry for the trouble, if indeed I was any.

xc-racer99 said:
Alright, I've uploaded a new build
Changelog for 2016-01-23
...
Fixed Google Play (and other apps) download error (I think...)
...
Click to expand...
Click to collapse
I tried Pico gapps and the store works perfectly for me now. Thanks!

New Build Uploaded!
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0

Wooow...thanks

xc-racer99 said:
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
Click to expand...
Click to collapse
Finally got pico gapps to run...the initial setup took quite a while but now that it's settled in, no problems. It's also interesting to note that Link2SD is running fine while it seems to be a major problem for other Lollipop & Marshmallow ROM's on other devices.

Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
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.
If on a BML rom (stock-based GB)...
Untested, but is setup to hopefully work. If it doesn't flash my 6.0 Omni first
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want gapps, reboot to recovery, wipe data+cache and install gapps.
5. If you want root, flash according to instructions in Post #3
If on an MTD rom (CM7 and all ICS+)
1. Reboot to recovery
2. Wipe data, dalvik/art cache, system, and cache partitions
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 20+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess.
If you're coming from either the last Lollipop build or the initial pre-release Marshmallow build, there is a bug in TWRP that will prevent flashing anything but the ROM. To get around this, please flash the Marshmallow zip, then reboot to recovery, and then follow the typical instructions.
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
If you come across a bug, feel free to let me know by posting in this thread. I will not be working non-stop on this project, but will try to fix bugs that affect me as this is still my main phone (out of choice, not necessity).
This build is very close to the official AOSP source code. Recovery is TWRP but otherwise there aren't any added "features"
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully. Opengapps pico works on the latest 7.0 build, untested on 7.1 but should work just fine
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Camera (built-in app needs workaround, see below)
RIL
SMS
Recovery
Bluetooth - first time it won't enable if enabling through settings, back out and then second time it will. Works just fine from status bar pulldown
Wifi
Vibration
Automatic Brightness
Compass
GPS on T959P, untested on T959V
Headset Buttons
SElinux in enforcing mode - this may have broken the T959V's gps...
Partially working
Camera and Browser apps need to have all their permissions manually enabled through settings for full functionality. This is because I've used the older Camera app (which hasn't been updated for dynamic permissions) and the older Browser app as the new one is simply a test shell with no features (thanks Google!)
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+
Everything else is not tested!!!
XDA:DevDB Information
AOSP 7.x for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/xc-racer99/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Created 2016-10-22
Last Updated 2016-10-21

Thanks Time!
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to the OMAP4 AOSP team for their work on porting CMA to a 3.0 kernel.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow https://source.android.com/source/initializing.html. The branch you want when you run repo init is the latest tag from https://source.android.com/source/build-numbers.html#source-code-tags-and-builds for your desired android version (7.0 or 7.1). Before you run repo sync, from the WORKING_DIRECTORY/.repo folder, run "git clone https://github.com/xc-racer99/local_manifests -b BRANCH" where BRANCH is either aosp-7.0 or aosp-7.1. Continue on with the build guide, the device codename you want is "galaxys4gmtd".
If you want to build the kernel, follow the instructions in WORKING_DIRECTORY/kernel/samsung/aries/AOSP_README. Put the resulting arch/arm/boot/zImage in device/samsung/galaxys4gmtd-kernel
Other aries devices (captivate, i9000, i9000B, vibrant) should be fairly easy to do (ie the galaxysmtd on my github as well as the captivate trees work). The fascinate and p1 would need a fair bit of work.
Changelogs
Changelog for 2016-12-19
December security patches
goes back to the older graphics drivers so hardware recording works but has a kernel patch to prevent crashes
Tweaked the graphics drivers options so it seems a little bit faster
Tweaked the RIL a little bit for better stability
Other things I've forgotten about, see github for details
Changelog for 2016-12-19-V2
Kernel without slowdowns....
Changelog for 2017-1-19
selinux to enforcing - this may break the T959V's GPS - if it does, let me know and send me a dmesg and I'll fix it
Update to the interactive governor - should have less slowdowns if using the default governor
Slightly better RIL reliability (I think)
Better low memory killing - we now don't run out of memory as often
Hardware decoding re-enabled
Slightly less intensive background services
Based on 7.1.1_r13

Source Code, Downloads, Root Options
Main Source
https://android.googlesource.com/
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see aosp-7.x branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see aosp-7.x branch).
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see aosp-7.x branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see aosp-7.x branch)
http://github.com/xc-racer99/android_patches for all the patches necessary for the device to work properly (see aosp-7.x branch)
Downloads!
All builds can be downloaded from AndroidFileHost at https://www.androidfilehost.com/?w=files&flid=58191
Gapps
The smallest http://opengapps.org/ package for 7.0 is known to work, but any small 7.0 gapps package should work. However, they will cause the device to slowdown significantly as they use a fair bit of RAM. Gapps are untested on 7.1
This ROM is compatible with MicroG (https://microg.org/ and http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616) gapps. This is an open-source reimplementation of Google Play Services that doesn't track you and uses way less battery than the original.
Root
Root is achieved via Magisk or SuperSU.
MagiskDue to our odd partition layout, you need to use my custom Magisk install zip (source code here) attached to this post and not the official install or the Magisk Manager install. Then follow the instructions on how to root/install other modules from http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Also, don't try to use the official Magisk uninstall tool as it won't work.
SuperSU
Please note: I've been told this doesn't work any more, YMMV
Again, we need a custom SuperSU install zip for it to work due to our partition scheme. It should be an all-in-one zip so it's simplier than Magisk (but not open source). This is based off of the latest (at time of writing) 2.79SR1 release, the diff is below
Code:
diff --git a/META-INF/com/google/android/update-binary b/META-INF/com/google/android/update-binary
index d437f6f..3a312bf 100644
--- a/META-INF/com/google/android/update-binary
+++ b/META-INF/com/google/android/update-binary
@@ -642,16 +642,23 @@ detect_systemless_required() {
find_boot_image
CONTINUE=true
+if false ; then
if [ -z "$BOOTIMAGE" ]; then
# no boot image partition detected, abort
return
fi
+fi
# extract ramdisk from boot image
rm -rf /sutmp
mkdir /sutmp
+if false ; then
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if (! $CONTINUE); then return; fi
@@ -1331,6 +1338,8 @@ else
ui_print_always "Boot image patcher"
ui_print "******************"
+if false ; then
+ # SGS Modification - we don't have a "real" boot image
ui_print "- Finding boot image"
find_boot_image
@@ -1357,6 +1366,10 @@ else
fi
check_zero_def "- Extracting ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero_def "- Decompressing ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if ($CONTINUE); then
@@ -1545,6 +1558,7 @@ else
check_zero_def "- Calling user boot image patch script" "sh /data/custom_boot_image_patch.sh /sutmp/boot.img"
fi
+if false ; then
if ($CONTINUE); then
DEV=$(echo `resolve_link $BOOTIMAGE` | grep /dev/block/)
if [ $? -eq 0 ]; then
@@ -1564,6 +1578,10 @@ else
dd if=/sutmp/boot.img of=$BOOTIMAGE bs=4096
fi
+else
+ cp /sutmp/ramdisk.packed /ramdisk/ramdisk.img
+ umount /ramdisk
+fi
rm -rf /sutmp
fi

Link for the download ROM is not working... it is private... ?!?

Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191

pickandrew said:
Link for the download ROM is not working... it is private... ?!?
Click to expand...
Click to collapse
Shaggy_thecat said:
Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191
Click to expand...
Click to collapse
Thanks, I used the link that I would use if I was already logged in, my bad. OP is now updated.

It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?

graycow9 said:
It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?
Click to expand...
Click to collapse
Hmm, flash the ROM, go into recovery, change the filesystem of /data to ext4 or f2fs. The error sounds as if the sdcard is formatted as fat while it shouldn't be. If that doesn't work, please send me the contents of /sdcard/aries_mtd.log after you've installed it.
Hadn't noticed the new "persistent logging" section. I suspect that what it does it keep the logcat contents over a reboot. Since the logcat does have a max size, it is probably safe to enable it. I highly doubt it contains any more info than a regular logcat.

Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.

Domunus said:
Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.
Click to expand...
Click to collapse
Ok, sounds like a messed up somewhere. I'll do some testing and try to release an updated build. Could you please post the output of /sdcard/aries_bml.log and /sdcard/aries_mtd.log? The "Encryption Unsuccessful" message sounds as if the SD wasn't properly formatted to ext4/f2fs.

Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?

Domunus said:
Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?
Click to expand...
Click to collapse
Odd, I thought my install script removed the extra partition.
Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Doesn't work....
I'll try to do some more testing with gapps and from stock with 1 or 2 partitions when I get a chance.

I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling. ?
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app

graycow9 said:
I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling.
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, I get a bad handshake as well. Only happens with hotmail/oulook accounts, my gmail and my other email work just fine.
I figured out what was causing the issues with install from BML - on TWRP boot, it wasn't setting up the sdcard properly. I've now fixed it so that it should work regardless (in the next build, obviously).

Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Click to expand...
Click to collapse
Gave this a try and still no luck.
Update **
It actually killed the recovery. Recovery just keeps crashing and rebooting when trying to get in to it. Tried it from the a clean install and same results. Will wait for your next build. Thanks for putting time in to this!

Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore ?? (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build ?
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app

graycow9 said:
Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
I've never used the contact sync.
With SIM not registering, it's because Google introduced a bug and the workaround the bug causes the SIM to occasionally not work. One of the problems with legacy devices I guess.
With the files not saving, manually grant the storage permission in Settings->Apps - it doesn't seem to automatically update for most apps.
With root, sounds like I should modify the SuperSU install zip as it's easier to use (but not open-source). For the PHH Superuser, you need
1) The Magisk-7-SGS.zip from my thread.
2) The phh-superuser-r259.zip from the Magisk root thread (link in OP)
3) The PHH Superuser app from the Play Store or FDroid
Even then, it only works for certain apps as it doesn't mount anything to /system/xbin/su which is what some apps look for
Edit: And I have no issues if you keep posting here with the problems you find, it's good to know.

bootloop
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?

asmalldharma said:
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?
Click to expand...
Click to collapse
Well, it depends on where you are bootlooping. If you're stuck at either of the first two splash screens, then you're out of luck with ADB as it isn't available yet. If you're bootlooping but getting to the bootanimation, then you can. To do so, run
Code:
$ adb root
$ adb shell mkdir /data/ramdisk
$ adb shell mount /dev/block/mtdblock5 /data/ramdisk
$ adb push ramdisk-recovery.img /data/ramdisk
$ adb reboot recovery
where ramdisk-recovery.img is from the AOSP 7.0 zip.
If you're stuck at the first or second splash screens, then you need Odin or Heimdall. With heimdall, you can do
Code:
$ heimdall flash --KERNEL boot.img
where the boot.img is the one from Omni 6.0, the one from 7.x won't work on its own as the recovery is not stored in it. You can use Odin to go back to stock.
I haven't tried gapps so I guess I should sometime and see what the issue with them is.

Gets to the second splash screen. I'll give that a shot when i have some free time. I'm really looking forward to getting this working as I'm amused by the idea of my oldest android phone running the newest OS before my other two.
Update: couldn't get it to work with my cheap laptop. Kept throwing up the libusb 12 error. Then when i finally gave up and pulled the battery, I noticed it was starting to bulge a little. I think I'm out for a while. I'm hoping i can come back to this soon.
Sent from my A0001 using XDA-Developers mobile app

Enhanced twrp for op3 and op3t
Download from official server:
Download for oxygenos and other non-treble ROMs: https://glassrom.pw/op3_recovery.img
Download for treble ROMs: https://glassrom.pw/op3_recovery-treble.img
Download from CDN:
Download for oxygenos and other non-treble ROMs: https://cdn.glassrom.pw/op3_recovery.img
Download for treble ROMs: https://cdn.glassrom.pw/op3_recovery-treble.img
Unofficial mirrors:
Hosted by @Sytis https://storage.ceres-sys.de/glassrom
Don't ask these questions. Seriously:
Features: none. It's a recovery. It should be as simple as possible because you rely on this stuff to recover your device in case something goes wrong
Seriously. Were you expecting features from a custom recovery?
Screenshots: it looks like TWRP
Important. There is a blank option and a system_root option in the mounts section. These are only for compatibility with scripts. Do not try to tick them yourself
Some scripts may throw a "failed to umount /system_root" message. This is fine
Important: why do some ROMs refuse to flash?
Some ROMs like oxygenos and glassrom use a feature called "downgrade attack prevention". If TWRP's build date is higher than the build date of the ROM the installation script assumes a downgrade attack is happening and the flashing fails
System nandroid restore fails:
You are not supposed to be restoring file-based backups of the system partition on a device with dm-verity in the first place. Backup and restore system image backups.
Glassrom users: if this is your first time flashing glassrom remember that the current enhanced twrp will always have a build date higher than the current glassrom build. In other words you can only flash a newer glassrom build as long as your enhanced twrp build is older or in other words:
Switching to glassrom: use official twrp, flash glassrom and then flash enhanced TWRP to enforce downgrade attack prevention
Updating glassrom: no need to switch to official. Always update glassrom before you update enhanced twrp
This was intentionally done to prevent downgrade attacks on glassrom. Using enhanced twrp with glassrom is recommended
This TWRP addresses a number of issues that have been plaguing the op3:
Uses a backported F2FS driver (5.1-rc1-3.18) that fixes an issue where TWRP would get stuck on the TWRP splash screen for a long time if the user was using F2FS
Uses an upstream kernel that was taken from lineage's common kernel https://github.com/LineageOS/android_kernel_qcom_msm8996
Added all crypto footer code back to resolve all encryption issues
Improved detection of device variant. Recovery now validly detects op3 and op3t
A full selinux policy so that files do not get labelled incorrectly. This resolves a bunch of issues like "device doesn't boot after restoring nandroid"
Built against full lineage source. No minimal manifest or any other nonsense
Upstreamed sdfat driver for better suppport for USB-OTG drives
No prebuilt kernels. Uses a fully source built kernel
Kernel built with a compatible GCC 8. No weird compiler optimisation
Ext4 is the default filesystem instead of f2fs
Current issues: even if the source code is out building TWRP against lineage is not something a beginner can do. If somebody is willing to contribute build documentation they are more than welcome
XDA:DevDB Information
Anupritaisno1's enhanced twrp builds, Tool/Utility for the OnePlus 3
Contributors
anupritaisno1, anupritaisno1, dianlujitao
Source Code: https://github.com/GlassROM-devices
https://bitbucket.org/anupritaisno1/aarch64-linux-gnu
Version Information
Status: Stable
Current Stable Version: 3.3.0
Stable Release Date: 2019-05-01
Created 2019-05-03
Last Updated 2019-05-02

A request to moderators:
People often ask "screenshots" and "features" while this really doesn't make much sense in the context of a recovery. It's a recovery
Please delete such posts to keep the thread clean

Reserved

Feedback:
update-scripts that use run_program("/sbin/busybox) doesn't work as of the latest TWRP builds.

aboodyaiman said:
Feedback:
update-scripts that use run_program("/sbin/busybox) doesn't work as of the latest TWRP builds.
Click to expand...
Click to collapse
Busybox was removed. I've updated my flashable zips to use run_program("/sbin/mount", "/system"); instead.
Replacing 'busybox' with 'toybox' should work too.

Dirk said:
Busybox was removed. I've updated my flashable zips to use run_program("/sbin/mount", "/system"); instead.
Replacing 'busybox' with 'toybox' should work too.
Click to expand...
Click to collapse
Have you tried this*? I'm waiting feedback :silly:
I'm not in a good time for messing around..
*i mean the recovery as general

aboodyaiman said:
Feedback:
update-scripts that use run_program("/sbin/busybox) doesn't work as of the latest TWRP builds.
Click to expand...
Click to collapse
Busybox is pretty terrible and most of it's executables aren't even compliant to standards
Please update your scripts to use toybox or ship the actual statically linked binaries

Dirk said:
Busybox was removed. I've updated my flashable zips to use run_program("/sbin/mount", "/system"); instead.
Replacing 'busybox' with 'toybox' should work too.
Click to expand...
Click to collapse
You should specify the "-o rw,remount" flag otherwise if mount system partition read-only is ticked there's a high chance system is mounted read-only and the script won't actually touch the system partition. This can be achieved by using a shell script instead of run_program()
Your command can also fail with "cannot find /system in the fstab". Instead of calling mount that way you should use this edify command and then call mount with run_program() to make sure it doesn't fail
Code:
mount(fs_type, partition_type, name, mount_point)
Please see https://source.android.com/devices/tech/ota/nonab/inside_packages
Toybox uses a slightly different mount command so merely replacing all instances of busybox with toybox will not work

anupritaisno1 said:
Busybox is pretty terrible and most of it's executables aren't even compliant to standards
Click to expand...
Click to collapse
IMHO bb is much more sophisticated then tb. If compiled with long options enabled bb is more posix compliant then any other multicall binary I know of.
The original decission to replace bb by tb by google was made because of license politics (bb: gnu copy left; tb: apache) - technically bb is superior to tb, for the amount of implememted commands as well as the posix compliance of the implemented commands (if configured correctly). I.e. parts of dns and resolver libs in tb are broken from the beginning of tb used in android (though this doesn't matter in recovery only use). fgrep/egrep are another broken/non-posix-compliant topic, which is solved by adding standalone binaries.
The claim you've made is at least questionable, and since you are publishing your sources (aka complying to gpl), the main reason for not using bb is not true for your twrp builds.
You may consider to put in bb additionally. For los integration, I've made a bb setup not overriding any tb links and installing bb as well as it's links to /system/xbin. With nearly no effort the installation target could be changed to i.e. /xbin or /bb/bin. If the installation dir is added in the path after the path to tb, you'll ship a recovery not only compatible with latest pie sources, but also with backward compatibility for flashable zips relying on bb.
https://github.com/nvertigo/android_external_busybox/tree/nlos-16.0

nvertigo67 said:
IMHO bb is much more sophisticated then tb. If compiled with long options enabled bb is more posix compliant then any other multicall binary I know of.
The original decission to replace bb by tb by google was made because of license politics (bb: gnu copy left; tb: apache) - technically bb is superior to tb, for the amount of implememted commands as well as the posix compliance of the implemented commands (if configured correctly). I.e. parts of dns and resolver libs in tb are broken from the beginning of tb used in android (though this doesn't matter in recovery only use). fgrep/egrep are another broken/non-posix-compliant topic, which is solved by adding standalone binaries.
The claim you've made is at least questionable, and since you are publishing your sources (aka complying to gpl), the main reason for not using bb is not true for your twrp builds.
You may consider to put in bb additionally. For los integration, I've made a bb setup not overriding any tb links and installing bb as well as it's links to /system/xbin. With nearly no effort the installation target could be changed to i.e. /xbin or /bb/bin. If the installation dir is added in the path after the path to tb, you'll ship a recovery not only compatible with latest pie sources, but also with backward compatibility for flashable zips relying on bb.
https://github.com/nvertigo/android_external_busybox/tree/nlos-16.0
Click to expand...
Click to collapse
Thanks. I guess I was wrong about busybox
I'm still not considering shipping busybox. Whenever I've tried it something broke so I'll just be sticking with toybox on that part
What I might be able to do is make a zip that copies busybox to /sbin/busybox and since it's just copying in ram there shouldn't be much of a problem. Users can flash this zip as a way to have backward compatibility with older zips. That sounds like a much better option honestly as then the fix is not just tied to my recovery but can be used on every recovery that doesn't have busybox on the op3
Edit: I also do not think shipping your busybox is a very good idea. You're compiling busybox with this
-Wno-error=implicit-function-declaration -Wno-implicit-function-declaration
Click to expand...
Click to collapse
I don't even know why this is a compiler warning. This should be an error but if you're shipping busybox with that warning disabled instead of fixing it that's just asking for trouble

anupritaisno1 said:
What I might be able to do is make a zip that copies busybox to /sbin/busybox and since it's just copying in ram there shouldn't be much of a problem.
Click to expand...
Click to collapse
...and on every second page of this thread, you'll be asked, if flashing bb is necessary on each update. Then you'll need to answer every time: "no, you need to flash it prior to each flashing of a bb needing zip."
If you just say bb is droped upstream and you want to keep your twrp clean.
Anyway: I've fixed the static build target.
anupritaisno1 said:
Edit: I also do not think shipping your busybox is a very good idea. You're compiling busybox with this
Click to expand...
Click to collapse
Thanx for the heads up - you are absolutly right here! (This was on my todo list more then 2 years ago, then I fogot to do it... I don't like people pointing me to my old and forgotten todos... )
https://github.com/nvertigo/android_external_busybox/commit/f512d6cbb4181970b47383a6efe0c01f27a0d978

nvertigo67 said:
...and on every second page of this thread, you'll be asked, if flashing bb is necessary on each update. Then you'll need to answer every time: "no, you need to flash it prior to each flashing of a bb needing zip."
If you just say bb is droped upstream and you want to keep your twrp clean.
Anyway: I've fixed the static build target.
Thanx for the heads up - you are absolutly right here! (This was on my todo list more then 2 years ago, then I fogot to do it... I don't like people pointing me to my old and forgotten todos... )
https://github.com/nvertigo/android_external_busybox/commit/f512d6cbb4181970b47383a6efe0c01f27a0d978
Click to expand...
Click to collapse
I haven't really checked the code but I'm not that sure about this part
Shouldn't it be like
Code:
#ifndef _GNU_SOURCE
#define _GNU_SOURCE
Idk just sounds more correct that we don't want a redefinition here

Is there any need for a manual mount of 'fakecache' like in Enhanced TWRP of OP2 ?
I hope not...
Thanks for the development !

gps3dx said:
Is there any need for a manual mount of 'fakecache' like in Enhanced TWRP of OP2 ?
I hope not...
Thanks for the development !
Click to expand...
Click to collapse
The entire fakecache experiment was me trying to port treble to the op2
That obviously failed and I'm in the process of removing that hack even from the op2
It's not there on this TWRP. That's for sure

F2FS 5.2-rc1-3.18 is out
The update will first arrive on glassrom and then on enhanced TWRP

anupritaisno1 said:
F2FS 5.2-rc1-3.18 is out
The update will first arrive on glassrom and then on enhanced TWRP
Click to expand...
Click to collapse
Glassrom is out but I've sadly not received any feedback from the twrp testers yet
The new release might be delayed and I'm also busy working on op2
It will definitely come in 1-2 days

Glad you made this twrp @anupritaisno1.
Working great here and happy to see all issues I had with other versions (some warnings on terminal, time issues etc...) are gone!
Keep up the good work

@anupritaisno1
Any chance your TWRP is not compatible with PIE ? ( i.e either that PIE is not supported or PIE is NOT the highest SDK supported )
I ask since many users across OP3 & 3T forum complained about "BSoDwWL" (Black Screen of Death with White Led ) issue that appear randomly ( not during recovery, but in android ) and freeze the device for ~15sec which ends in systemUI reboot.
I'm not sure, but around the week I updated myy recovery to your TWRP, I started to suffer for that issue - which is partially in accordance with this report - i.e that SOME TWRP is responsible
please don't get me wrong... as it might be TWRP original code fault - not something directly related to your own wonderful work here.
I wonder if you encountered this issue as well ?
Does TWRP 3.3.x is already Q compatible ? what's the LAST twrp version that its higher SDK support is PIE (3.2.x / 3.1.x ) ?

gps3dx said:
@anupritaisno1
Any chance your TWRP is not compatible with PIE ? ( i.e either that PIE is not supported or PIE is NOT the highest SDK supported )
I ask since many users across OP3 & 3T forum complained about "BSoDwWL" (Black Screen of Death with White Led ) issue that appear randomly ( not during recovery, but in android ) and freeze the device for ~15sec which ends in systemUI reboot.
I'm not sure, but around the week I updated myy recovery to your TWRP, I started to suffer for that issue - which is partially in accordance with this report - i.e that SOME TWRP is responsible
please don't get me wrong... as it might be TWRP original code fault - not something directly related to your own wonderful work here.
I wonder if you encountered this issue as well ?
Does TWRP 3.3.x is already Q compatible ? what's the LAST twrp version that its higher SDK support is PIE (3.2.x / 3.1.x ) ?
Click to expand...
Click to collapse
Please get me a copy of /sys/fs/pstore/console-ramoops-0 on the next boot after the crash

gps3dx said:
@anupritaisno1
Any chance your TWRP is not compatible with PIE ? ( i.e either that PIE is not supported or PIE is NOT the highest SDK supported )
I ask since many users across OP3 & 3T forum complained about "BSoDwWL" (Black Screen of Death with White Led ) issue that appear randomly ( not during recovery, but in android ) and freeze the device for ~15sec which ends in systemUI reboot.
I'm not sure, but around the week I updated myy recovery to your TWRP, I started to suffer for that issue - which is partially in accordance with this report - i.e that SOME TWRP is responsible
please don't get me wrong... as it might be TWRP original code fault - not something directly related to your own wonderful work here.
I wonder if you encountered this issue as well ?
Does TWRP 3.3.x is already Q compatible ? what's the LAST twrp version that its higher SDK support is PIE (3.2.x / 3.1.x ) ?
Click to expand...
Click to collapse
Hi I checked this myself
There seems to be absolutely no difference between drivers from 5.0.8 and 9.0.2
It feels as if oneplus simply took the drivers from 5.0.8 and smashed them onto 9.0.2 so I have no idea what crashes you're observing. Please submit logs