Database Develop

[JFLTE]BeanStalk 4.4.4 Nightlies and Tutorial for Compiling Yourself

** HOW-TO COMPILE BEANSTALK YOURSELF **​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: Pre-compiled nightly builds in the second post
or
Official Builds are found here​
While BeanStalk is offically supported for our device, I noticed that there hasn't been a new build for a little while and loving the ROM as much as I do, I'm addicted to having the latest features. Here is a basic tutorial for building this yourself. If I'm stepping on anyones toes by posting this, please let me know. I am in no way affiliated with the development of this ROM or with scott.hart.bti the creator of it.
I compiled on a Debian Wheezy system, 64bit (squeeze should be the same). A 64-bit computer is required to compile KitKat (ICS and above for that matter), so don’t attempt this on anything less. If you are unfamiliar with installing Debian, you can use LMDE, it's a live Debian system that you can install with minimal linux knowledge and works pretty nice. However the installation process is pretty easy for vanilla Debian and a good learning process, so give it a shot if you have the time.
Do this all as root
Download dependencies:
Code:
apt-get install git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev x11proto-core-dev libx11-dev libreadline6-dev g++-multilib mingw32 openjdk-6-jdk tofrodos python-markdown libxml2 libxml2-utils schedtool pngcrush xsltproc zlib1g-dev lib32stdc++6 lib32ncurses5 ncurses-libs.i686 libstdc++.i686 libgcc.i686 lib32readline-gplv2-dev lib32z1-dev
Link files:
Code:
ln -s /lib32/libncurses.so.5 /lib32/libncurses.so
or for Ubuntu 10.10:
Code:
sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
Install Google’s repo script:
Code:
mkdir ~/bin
PATH=~/bin:$PATH
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod 755 ~/bin/repo
Make your working Directory and start syncing with BeanStalk
Code:
mkdir ~/beanstalk; cd ~/beanstalk
repo init -u git://github.com/scotthartbti/android.git -b kk44
repo sync
Setup the build environment for our device (jflte)
Code:
. build/envsetup.sh
lunch 56 ## or type lunch and find "jflte_userdebug" in the menu
Add the device source code and Proprietary Vendor files by adding the following line to ~/beanstalk/.repo/local_manifests/roomservice.xml
So it should look like this afterwards:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_jflte" path="device/samsung/jflte" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_jf" path="kernel/samsung/jf" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_external_libtar" path="external/libtar" remote="github" revision="cm-11.0" />
</manifest>
Sync the repo again:
Code:
repo sync
Get your prebuilt terminal emulator:
Code:
cd ~/beanstalk/vendor/cm && ./get-prebuilts
Now there is a bug that will cause our builds to fail, so we need to apply the following for our unified devices:
Edit ~/beanstalk/device/samsung/jflte/system.prop
Add these two lines to the end:
Code:
ro.product.device=jflte
ro.product.model=Samsung JFLTE
That should be it, now we can build!
Code:
cd ~/beanstalk
. build/envsetup.sh
lunch 56 ## or type lunch and find "jflte_userdebug" in the menu
time mka bacon
when finished, it’ll be located in ~/beanstalk/out/target/product/jflte/
TIP:
Install the github app and follow scott.hart.bti to see when new updates get added to the sourcecode
Also, if you are into building, checkout my acompile script in my signature, it'll email you when your build is complete using Gmail's snmp and will include the time it took and the last few lines of the output. I find it very useful for knowing when my build is done (especially since they take me about 3+ hours apiece)
Also, I am using the latest NAE Firmware with no problems, however the stock MJA worked fine as well. Here is a link if you care to upgrade your modem drivers.
SOURCES:
This page helped a lot with a great tutorial on building ROMS
This forum is filled with great people who others with the building of ROMS. A great source when you run into errors you don’t understand.
BeanStalk Github for Scott.Hart.bti
jflte kernel source
I hope this helps someone,
-Mike

BUILDS:
If you would just like a compiled version, here are mine (they are stock, except for reverting this commit because I like the transparent Vol panel personally)
These builds are using the SlimRom's JFLTE Kernel which is kernel 3.4.82 vs the standard 3.4.0 from Cyanogenmod that is used stock with BeanStalk Offical builds.
NOTE: These are unified builds, meaning they can be flashed all all the S4 variants that were previously known as: jflteatt, jfltecan, jfltecri, jfltecsp, jfltespr, jfltetmo, jflteusc, jfltevzw, jfltexx
JFLTE BeanStalk 10/30/14 Nightly
Unofficial BlissStalk 10/29/14 Nightly
Unoffical BlissStalk 10/20/14 Nightly
Unofficial BlissStalk 10/17/14 Nightly
JFLTE BeanStalk 4.4.4010 Nightly 8/1/14
JFLTE Beanstalk 4.4.4010 Nightly 7/18/14
JFLTE Beanstalk 4.4.4007 Nightly 7/11/14
JFLTE Beanstalk 4.4.4001 Nightly 6/25/14
JFLTE BeanStalk 4.4.285 Nightly 4-21-14
JFLTE BeanStalk 4.4.278 Nightly 4-14-14 ## NOTE: If you have issues with receiving calls and/or texts, make sure to clean flash this build, that will fix it.
JFLTE Beanstalk Nightly Build 3-29-14 ## NOTE: No new features over the 3-24-14 build but uses SlimRoms kernel source instead (3.4.82 vs 3.4.0)
JFLTE Beanstalk Nightly Build 3-24-14
JFLTE Beanstalk Nightly Build 3-18-14
JFLTE Beanstalk Nightly Build 3-17-14
JFLTE Beanstalk Nightly Build 3-11-14
JFLTE BeanStalk Nightly Build 3-7-14
JFLTE BeanStalk Nightly Build 2-28-14
Slim Beta 4.4 Gapps Toggleable
PA GAPPS
Photosphere Addon ( Google Camera is in the PlayStore now, this is just for the 4.4 camera )
Sound Packs (System Sound Themes for switching on the fly)
ISSUES:
- Some people are having issues with the compass not always pointing north.
Enjoy,
-Mike
Changelog:
Again, I only compile, the code changes are done by the ROM Dev's
Code:
10/20/14
-New Version Number (001) to reflect being out of beta now.
-New Boot Animation
-ViperFX add and CM DSP removed
-SuperSU added to Downloads Section
-Netflix Fix added to Downloads Section
-Mem and CPU info removed from About Phone section
-More Bliss Stalk logos and names added.
-Torch Changes from CM11
-JFLTE Humidity Sensor permissions fixed
10/17/14
-Switched to BlissROM sources for a BeanStalk fork that is more current with changes and commits.
-Menus Updated
-Omni Switch Added
-Settings Menu Updated
-Xposed moved to the "Bliss Downloads" section for latest version.
-Bluetooth code updated by CM11
-Camera driver updated.
8/1/14
- No code changes in the beanstalk source since last build
- Enabled transparent lockscreen status bar
7/18/14
- Ad blocker
- EOS Weather
- Navigation Bar swipe left to open in Window
- App Circle SideBar
- Floating windows fixes
- Update to 4.4.4_r2 / Beanstalk 4.4.4010
7/11/14
- Hover added
- Driving mode
- Update Roboto fonts to Android L versions
- Use Android L navbar icons
- Reset battery stats
- Reworked non-intrusive incall ui
6/25/14
-Updated dialer
-Shake settings
-Glowpad transparency in dialer
-Doubletap custom tile
-Updated terminal
-Adjusted Auto-Brightness curve
-Android 4.4.4
4/21/14
- Update to BeanStalk 4.4.285
- CM Fixes for unifyed devices (JFLTE)
- Faster Framework animations
- Fixes the sometimes missing first task in AOSP and SlimRecents
- Shake to lock? (still trying to find this in settings)
- Smart Phone Call in Dialer (type number and hold to you ear to dial)
- CM11 Fixes
4/14/14
- Update to BeanStalk 4.4.278
- Fixes to the LTE tile
- Option for Screen Color in Settings (hue, contrast, etc)
- Theme support added to Ringtones
- Voice+ integrated into Settings
- Latest CM11 commit merges
- Toggle Flashlight when shaking
- Add On-The-Go mode (use camera as display overlay, for walking)
-Add Fast Charge QS Tile
- SlimRecents: Make expanded layout pretty
- Implement SIM card management
3/29/14
- Fixes to the LTE tile
- Option for Screen Color in Settings (hue, contrast, etc)
- Theme support added to Ringtones
- Voice+ integrated into Settings
- Latest CM11 commit merges

Cool Ty , looking forward to giving it a try
Sent from my SPH-L720 using Tapatalk

Nice! Will you continue to build Beanstalk for our device? I just left it for PAC since it hadn't been updated in ages.
Sent from my SPH-L720 using Tapatalk

themisterwilson said:
Nice! Will you continue to build Beanstalk for our device? I just left it for PAC since it hadn't been updated in ages.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Well our device has official support from BeanStalk already here, it seems that the builds for our devices stopped though when Cyanogenmod moved our device source into a unified code (combining jfltespr, jflteatt, jfltevzw, etc in one source "jflte"). Trying to build this ROM straight will fail because of this unification (see above in the tutorial for the fix), so I'm guessing that's why we haven't seen an official build in a while. I'll be more than happy to keep uploading nighties as I build them until the official builds start back up though, as long as I'm not stepping on the current maintainer's toes.
Cheers,
Mike

You keep on keeping on :thumbup::beer:
Sent from my SPH-L720 using xda app-developers app

Man thanks for the nightly it's amaze balls.....so grateful to be back on the stalk!!!!!
Sent from my SPH-L720 using XDA Premium 4 mobile app

Thanks so much been waiting for a version of stalk I could run on USC!
Sent from my SCH-R970 using Tapatalk

btoddweber said:
Man thanks for the nightly it's amaze balls.....so grateful to be back on the stalk!!!!!
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My sentiments exactly! Thank you! Been amazing all day
Sent from my SPH-L720 using Tapatalk

Is the back to kill app option here? Looked everywhere and can't seem to find it. Also can't get a GPS lock!
Sent from my SCH-R970 using Tapatalk

Came across this on Google. Thank you so much for the tutorial and compiles. Please continue to share your builds as I will be using this on a T-Mobile S4.

bignick1215 said:
Is the back to kill app option here? Looked everywhere and can't seem to find it. Also can't get a GPS lock!
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
At one time I believe it was in the developer options at the bottom, can you use pie (with custom app) or hw buttons?
Sent from my SPH-L720 using Tapatalk

Not in developer options and the hw buttons Dont have a kill option! I guess I could use xposed but I just Dont care for it. Its really minor I just tap the greenify widget before I lock the screen and has the same affect. The GPS not locking on the other hand I've yet to get me a work around for that one.
Sent from my SCH-R970 using Tapatalk

bignick1215 said:
Not in developer options and the hw buttons Dont have a kill option! I guess I could use xposed but I just Dont care for it. Its really minor I just tap the greenify widget before I lock the screen and has the same affect. The GPS not locking on the other hand I've yet to get me a work around for that one.
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
There is not an option for mapping long-press actions to the back button currently, you could the BeanPie or LMT for that however (that's what I do). As for GPS, I get a lock just fine, what firmware are you using? I 've only tested with MJA and NAE (both located here). Anyone else having GPS issues?
Cheers,
-Mike

That explains the GPS lock! I'm on mja baseband but older firmware
Sent from my SCH-R970 using Tapatalk

Rebooted for the 3rd time and got instant GPS lock!
Once I toggle off and back on its a no go again! Turned it on then rebooted and it works again.
Sent from my SCH-R970 using Tapatalk

bignick1215 said:
Rebooted for the 3rd time and got instant GPS lock!
Once I toggle off and back on its a no go again! Turned it on then rebooted and it works again.
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
Haven't noticed any problems with GPS, but I'll try to re-create tomorrow and get back to you.
Cheers,
Mike

No problems at ALL on my end. Great job!!!! And many thanks again!!! Very glad to have stalk again
Sent from my SPH-L720 using XDA Premium 4 mobile app

mikshepard said:
Haven't noticed any problems with GPS, but I'll try to re-create tomorrow and get back to you.
Cheers,
Mike
Click to expand...
Click to collapse
Much appreciated! And thanks for the great work.
Sent from my SCH-R970 using Tapatalk

btoddweber said:
No problems at ALL on my end. Great job!!!! And many thanks again!!! Very glad to have stalk again
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1 many thanks!
Sent from my SPH-L720 using Tapatalk

CM11 manifest repo?

Hi, I'm working on my build environment in order to cook ROMs for our beloved P990 myself. However, there are some questions I couldn't answer yet. Maybe our developers can help me...
manifest repo
So I've found 2 manifest repos, but none of them has a cm-11.0 branch, yet:
https://github.com/djnoxd-p990/android
https://github.com/p990-dev/android.git
TonyP has a device specific repo (no manifest repo) for cm-11.0, but no matching manifest repo. So... @DJNoXD/tonyp/hjunii: please upload your latest manifest repo.
linaro toolchain
TonyP wrote that he was using the default gcc toolchain (gcc 4.6 and gcc 4.7 for cm-10.1 and cm-10.2). Has anyone tried the linaro toolchain, yet? From what I found out so far gcc completely disables the fpu by building code that uses the cpu for floating point operations, which results in a performance decrease of 5%-40% in average. Linaro is not doing such things, so I'm hoping for a big performance increase when using it...
kernel 3.10
There's a new kernel release from nVidia for our tegra device: kernel 3.10 (https://android.googlesource.com/kernel/tegra/). Anyone tried that one, yet?

Like this?
https://github.com/tonyp/android_vendor_cm/tree/cm-11.0-tonyp
https://github.com/p990-slimrom/android_device_lge_p990/tree/kk4.4_new
Good luck

As far as I know - no. These are "normal" repositories. But in order to build a complete ROM I need the "manifest repo", which is some kind of enveloping repository. It is tiny (look at https://github.com/CyanogenMod/android for example), but contains a file called default.xml, which references all "normal" repositories that are needed.
I hope I got that right. Please tell me if I write total bull****.

https://github.com/p990-slimrom/platform_manifest/tree/kk4.4
But I think you don't need it. I'm building CyanogenMod for O4x with unofficial sources with local manifest added to CyanogenMod sources
My manifest (you have to change repos):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/p880" name="P880-dev/android_device_lge_p880" groups="device" />
<project path="kernel/lge/x3" name="P880-dev/android_kernel_lge_x3" />
<project path="vendor/lge" name="P880-dev/proprietary_vendor_lge" />
</manifest>
EDIT: the kernel, which you're pointing is not for tegra 2 (Nvidia ended support) and porting that to newer tegras is so much difficult, so developers usually don't do it.

Yay, that's what I was looking for!
Alright, so now let's start building a ROM.

Good Luck!
Gesendet von meinem SM-T210R mit Tapatalk

thorstenhirsch said:
As far as I know - no. These are "normal" repositories. But in order to build a complete ROM I need the "manifest repo", which is some kind of enveloping repository. It is tiny (look at https://github.com/CyanogenMod/android for example), but contains a file called default.xml, which references all "normal" repositories that are needed.
I hope I got that right. Please tell me if I write total bull****.
Click to expand...
Click to collapse
I have included the device specific stuff into the default repo, This make the work easier for me.

[FIX] Voice messages

First of all, thank user @Bobgle for the fix. He killed the fish with that, so big kudos.
I just had to add a little line of code to the /system/etc/media_profiles.xml. I know it's not your rom which has the problem, I'll tell the other developer how to fix it as well. I first found out that it was a common problem through your NOPE Kernel FAQ, though, so it's definitely worth adding.
This is the line of code:
Code:
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="96000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="1" />
Has to go right between these two and should look like this:
Code:
<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="8000000"
minFrameWidth="176" maxFrameWidth="1280"
minFrameHeight="144" maxFrameHeight="720"
minFrameRate="1" maxFrameRate="30" />
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="96000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="1" />
<AudioEncoderCap name="amrnb" enabled="true"
minBitRate="5525" maxBitRate="12200"
minSampleRate="8000" maxSampleRate="8000"
minChannels="1" maxChannels="1" />
Once you've done that it's working. I also replaced this line in the media_codecs.xml:
Code:
<MediaCodec name="AACEncoder" type="audio/mp4a-latm" />
with:
Code:
<MediaCodec name="OMX.google.aac.encoder" type="audio/mp4a-latm" />
I'm not sure if that was necessary. Anyway, it's working.
Click to expand...
Click to collapse
I've put his message in the spoiler. I'll put it simply below, hopefully correctly.
-Open /system/etc/media_profiles.xml
-Find
Code:
<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="8000000"
minFrameWidth="176" maxFrameWidth="1280"
minFrameHeight="144" maxFrameHeight="720"
minFrameRate="1" maxFrameRate="30" />
-After that line of code squeeze in this:
Code:
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="96000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="1" />
-Save and close
-Open: media_codecs.xml (Same folder.)
-Find:
Code:
<MediaCodec name="AACEncoder" type="audio/mp4a-latm" />
-Replace the line with:
Code:
<MediaCodec name="OMX.google.aac.encoder" type="audio/mp4a-latm" />
-Save, close reboot.
Post results, and stuff and hopefully he will be able to answer stuff. The issue was in the ROM itself apparently, so it should work for any CM10 based such.
Edit: Of course, since this is not thoroughly tested, make sure you do a backup before you edit anything.

Not helped.
Desire C,MiniCMv7,NOPE Kernel

Dark_AssassinUA said:
Not helped.
Desire C,MiniCMv7,NOPE Kernel
Click to expand...
Click to collapse
I'm using the CyanogenMod10 (Build #3 by cute_prince) so I guess that MiniCM uses different encoders and decoders. I'll take a look at it, the fix should be similar.
Edit: Okay, it seems to be completely the same. The encoder should be included and working, are you sure you've edited all the things you have to edit? I was just messing around so I don't know what exactly I've changed, it could be that I've forgotten something, I'll upload my files. I've taken these directly from my phone where voice messages are working flawlessly with WhatsApp and Facebook.
To test if your aac encoder is now working, you could try downloading a recorder which supports the filetype. I used Easy Voice Recorder. Make sure to select AAC.
The problem with voice messages was simply that most apps use aac files, most cm roms did have the codec, but it simply wasn't registered in the files.
Edit2: If it still doesn't work after pushing my files in the correct directory (/system/etc/) try clearing all the caches (dalvik cache, too). If it isn't working after you did that, I would guess that this fix only works for cute_prince's rom.

Bobgle said:
I'm using the CyanogenMod10 (Build #3 by cute_prince) so I guess that MiniCM uses different encoders and decoders. I'll take a look at it, the fix should be similar.
Edit: Okay, it seems to be completely the same. The encoder should be included and working, are you sure you've edited all the things you have to edit? I was just messing around so I don't know what exactly I've changed, it could be that I've forgotten something, I'll upload my files. I've taken these directly from my phone where voice messages are working flawlessly with WhatsApp and Facebook.
To test if your aac encoder is now working, you could try downloading a recorder which supports the filetype. I used Easy Voice Recorder. Make sure to select AAC.
The problem with voice messages was simply that most apps use aac files, most cm roms did have the codec, but it simply wasn't registered in the files.
Edit2: If it still doesn't work after pushing my files in the correct directory (/system/etc/) try clearing all the caches (dalvik cache, too). If it isn't working after you did that, I would guess that this fix only works for cute_prince's rom.
Click to expand...
Click to collapse
Wow,it`s working!
Huge thanks from Ukraine!
From newbies(like me) made flashable zip

Dark_AssassinUA said:
Wow,it`s working!
Huge thanks from Ukraine!
From newbies(like me) made flashable zip
Click to expand...
Click to collapse
Glad I could help.

wwooowwwww .....thnxx bro...really it worked....i always had to switch back to sense bcoz of voice message problem in watsapp n other such apps...u saved my life...

[Module] More Fonts for Custom ROMs

[Magisk Module, Magisk 17.x or higher]
Additional fonts for the Font-Manager in
Pie
Havoc OS 2.X [9.X]
BootleggersROM 4.0 [9.X]
crDroid 5.X [9.X] Update: Works again in v5.4
MSM Xtended v8.5 [9.X]
SkyDragon OS [9.X] (Problems after ROM update), Update: works again on build SkyDragon-OS-P-oneplus3-20190513
Oreo
Dirty Unicorns 12.X
Replaces the original Font.apk with a pimped up Version. The original font selection is of course still included too.
In the current version of the module about 91 additional fonts with free license were added. I know that there are many beautiful and cool fonts out there, but their license in almost all cases does not include sharing or using in applications or... (there is almost always a hook ).
For further versions of the modules, references to other fonts with a free license are welcome!
The respective module only works in the intended ROM!
The Havoc module only works in HavocOS, the SkyDragon module only in SkydragonOS and so on...
For HavocOS 2.X [9.0]:
In Build 2.1 a restart seems to be necessary to set newly selected fonts system-wide (to take effect on status bar/lockscreen).
MoreFontsHavoc2.X[Pie]V5
For crDroid 5.X [9.0]:
MoreFonts_crDroid5.X[Pie]V2
For BootleggersROM 4.0 [9.0]:
MoreFontsBootleggers4.0[9.0]V2
For SkyDragon OS [9.X]/SkyDragon-OS-P-oneplus3-20190513:
MoreFontsSkyDragonOS[9.X]V5
For MSM Xtended v8.5 [9.0]:
MoreFontsXtendedV8.5[9.0]V1
For Dirty Unicorns 12.X:
MoreFontsDirtyUnicorns12.X_V1
Credits to:
@topjohnwu for Magisk, it´s documentation and templates.
Havoc-Crew, Skydragon-Crew, Bootleggers-Crew, Xtended-Crew, crDroid-Crew, DU-Crew for their excellent work!

Original font selection plus the following added fonts:
V1 + 28 fonts
V2 + 42 fonts

42 fonts added in Module-Version 2.

this is great ????
will try it soon

15 fonts added in Version 3

this thread need more attention
great job dev

- Module for BootleggersROM added
- V4 +5 fonts

Module for MSM Xtended v8.5 [9.0] added

Module for SkyDragon - Update to SkyDragon build 20190112

Module for crDroid 5.0 [9.0] added

Module for Dirty Unicorns 12.X added

Caution! The crDroid module only works in crDroid 5.0, no longer in 5.1! Before the update, make sure to deactivate the module!

Great work!
Any chance to make it work in the crDroid 5.4?

littl3viking said:
Great work!
Any chance to make it work in the crDroid 5.4?
Click to expand...
Click to collapse
I will try tomorrow to see if it still doesn't work with crDroid 5.4.

littl3viking said:
Great work!
Any chance to make it work in the crDroid 5.4?
Click to expand...
Click to collapse
It's working again! I haven't tried it since Versin 5.1, but on my OP3 with crDroid 5.4 it works again.
To be on the safe side you should make a TWRP backup before you install the module, but it worked for me without any problems! I tested crDroid-9.0-v5.4 with Magisk 19.2.
If it also works for you, you can give me a short feedback here, thank you.

The modules still work in the following Pie-Roms, just tested with Magisk 19.2 on a Oneplus3:
BootleggersROM 4.1
HavocOS-2.5
Xtended-XP7 v14
The modules work again in the current version of the following Roms:
crDroid v.5.4
SkyDragon-OS-P-oneplus3-20190513
To be sure, before installing the module make a TWRP backup in case of emergency!
(Link for the Skydragon module added again.)

C-3OP said:
It's working again! I haven't tried it since Versin 5.1, but on my OP3 with crDroid 5.4 it works again.
To be on the safe side you should make a TWRP backup before you install the module, but it worked for me without any problems! I tested crDroid-9.0-v5.4 with Magisk 19.2.
If it also works for you, you can give me a short feedback here, thank you.
Click to expand...
Click to collapse
Thanks!
I'll test and let you know if it worked.
Edit: working on crDroid 5.4. Thanks ?

Is it possible to add 'Road Rage' font to bootleggers module? Or tell me the procedure/location to place desired fonts?
Cheers.
Sent from my Redmi Note 7 Pro using Tapatalk

messypenguin said:
Is it possible to add 'Road Rage' font to bootleggers module? Or tell me the procedure/location to place desired fonts?
Cheers.
Sent from my Redmi Note 7 Pro using Tapatalk
Click to expand...
Click to collapse
I'm not sure about the license, but of course you can do it yourself.
Unzip the Magisk Module
Take the CustomFonts.apk from system>app>CustomFonts.apk
Decompile the app (e.g. with APK Easy Tool)
In the folder of the decompiled app go to CustomFonts>assets>fonts and add a zip folder with your font. The zip folder must contain the font as .tff and a text file "fonts.xml". I'll write the text of the .xml below, or you can take it from the zip folder of another font and replace the name of the font with the name of your font with a text editor, e.g. notepad++.
Now compile and sign the app (APK Easy Tool)
Replace the apk in the unzipped Magisk module, zip the whole thing and you have your own module with the font or all fonts of your choice.
Attention, at your own risk, of course! But if you unpack the module and decompile the apk, you'll see how it's built and it's actually self-explanatory.
I'm not sure if the copy/paste will do the correct formatting, so it's best to just open the font.xml from another font folder in the editor and edit it.
Text of the fonts.xml, replace "NameOfYourfont".ttf with the name of your font:
<?xml version="1.0" encoding="utf-8"?>
<familyset version="22">
<family name="sans-serif">
<font weight="400" style="normal">"NameOfYourfont".ttf</font>
</family>
<alias name="sans-serif-thin" to="sans-serif" weight="100" />
<alias name="sans-serif-light" to="sans-serif" weight="300" />
<alias name="sans-serif-medium" to="sans-serif" weight="500" />
<alias name="sans-serif-black" to="sans-serif" weight="900" />
<alias name="arial" to="sans-serif" />
<alias name="helvetica" to="sans-serif" />
<alias name="tahoma" to="sans-serif" />
<alias name="verdana" to="sans-serif" />
<alias name="sans-serif-condensed" to="sans-serif" />
</familyset>

Thanks for the detailed write up. Very helpful [emoji106]
Sent from my Redmi Note 7 Pro using Tapatalk

[ROM][S9/S9+/N9]Resurrection Remix 8.7[Q][UNOFFICIAL]

Hi guys,
I really love RR and since there seems to be no one else who is willing to maintain the latest Resurrection Remix ROM for the Samsung Galaxy S9 and S9+ for Android Q, I offer you this unofficial version.
-/\-/\-/\-/\-/\-/\-/\-/\-/\-
Note:
By downloading this ROM you take full responsibility of all consequences by your own!
I'm not responsible if you brick your device or do any other damage.
-\/-\/-\/-\/-\/-\/-\/-\/-\/-​
Download and changelog for starlte and star2lte:
https://freeze.ws/RR
​
-/\-/\-/\-/\-/\-/\-/\-/\-/\-
Please don't ask me for support how to flash!
-\/-\/-\/-\/-\/-\/-\/-\/-\/-
Kernel Source: https://github.com/yarpiin/White-Wolf-Uni-LOS
Resurrection Remix Source: https://github.com/ResurrectionRemix
-/\-/\-/\-/\-/\-/\-/\-/\-/\-​
There are four changes I've made:
- The default networkTransitionTimeout is decreased from 60 to 30 seconds.
- The bluetooth icon in the status bar is visible as soon as bluetooth is enabled (and not only if a bluetooth device is connected).
- The battery LED color can be set individually for the range 90 to 99% (so you have <90% charging, 90% to 99% nearly full and 100% full).
- I did some small undervolting starting with release from May 2022. If you don't want this, just flash another kernel, e.g. White Wolf.
Everything else is default RR!
-\/-\/-\/-\/-\/-\/-\/-\/-\/-​
This is the roomservice.xml with all sources I use for the build:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!--Device trees-->
<project name="ResurrectionRemix-Devices/android_device_samsung_universal9810-common" path="device/samsung/universal9810-common" remote="github" clone-depth="1" revision="Q" />
<project name="ResurrectionRemix-Devices/android_device_samsung_star2lte" path="device/samsung/star2lte" remote="github" clone-depth="1" revision="Q" />
<project name="ResurrectionRemix-Devices/android_device_samsung_crownlte" path="device/samsung/crownlte" remote="github" clone-depth="1" revision="Q" />
<project name="ResurrectionRemix-Devices/android_device_samsung_starlte" path="device/samsung/starlte" remote="github" clone-depth="1" revision="Q" />
<!--Hardware-->
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" clone-depth="1" revision="lineage-17.1" />
<!--Vendor-->
<project name="BlissRoms-Devices/proprietary_vendor_samsung" path="vendor/samsung" remote="github" clone-depth="1" revision="q" />
<!--Kernel-->
<project name="yarpiin/White-Wolf-Uni-LOS" path="kernel/samsung/universal9810" remote="github" clone-depth="1" revision="master" />
</manifest>
-/\-/\-/\-/\-/\-/\-/\-/\-/\-​
As long as there is no RR for Android 11 and as long as I stick to my SGS9, I will provide security updates in this thread.
I hope you enjoy it.
-\/-\/-\/-\/-\/-\/-\/-\/-\/-​
Big thanks to the LineageOS team, to synt4x93, to yarpiin, to garett_09 and especially to all the RR developers.
Thank you for this amazing ROM!!
-/\-/\-/\-/\-/\-/\-/\-/\-/\-​
One more hint:
Here you find the latest basebands for the SGS9 (big thanks to jaeck!):
https://forum.xda-developers.com/t/...0-22-08-2021-android-10-pie-stockrom.3858990/
For me, the latest version from 07/27/2021 performs best concerning battery consumption in comparison to the modems of the whole last two years.
-\/-\/-\/-\/-\/-\/-\/-\/-\/-
Feel free to donate, if you want to
​

Does Android Auto work?

abra-kadabra said:
Does Android Auto work?
Click to expand...
Click to collapse
Just tried it with my F36. It didn't work using USB at all and using bluetooth the google assistant tried to do something after pushing the assistant button of my car, but there was also no connection possbile.
But to be honest, I'm not even sure if my car supports Android Auto. Maybe someone else could test who is sure that his/her car supports it.

Thanks Freeze24 i was gonna build this since i have the same device, going to try and see how the performance and battery life is.

Just curious, how is this compared with the official one?

nnaaffffuu said:
Just curious, how is this compared with the official one?
Click to expand...
Click to collapse
In fact it's the same with the following differences
- the latest security fixes are included
- the bluetooth icon is visible in the status bas as soon as bluetooth is enabled and not only if a device is connected
- the networkTransitionTimeout is set to 30s instead of the default 60s (this is the time your device stays awake after a change in the network connection occured)

Hi Freeze24,
Thank You for opening this thread and all your good work. Your Rom with the latest security patches is very welcome and much apreciated.
(Just Downloaded the newest one and everything is running fine.)

Hey, why the other thread was closed?
I cant get a working safetynet and i cant make my bank apps working? any help please...

Havel_88 said:
Hey, why the other thread was closed?
I cant get a working safetynet and i cant make my bank apps working? any help please...
Click to expand...
Click to collapse
garett_09 doesn't maintain this ROM anymore, that's why I took over with this unofficial build.
To be honest, I also didn't get banking apps work with newer Magisk versions.
Gladfully I still have an old Canary version which works. But I even couldn't reinstall this old version any more, because you need to hide Magisk and in the hiding process it downloads the APK from the Magisk server and then you have again the new version which doesn't work... at least for me.
So I'm really stuck. Can't reinstall my phone.

### UPDATE ###
Unfortunately there are no updates coming from the RR team since September.
Thus I decided to implement the security fixes by myself.
-> Updated patch level to 2022-04-05
-> Download: https://freeze.ws/RR
I've implemented the following fixes:
Code:
CVE-2021-0652 CVE-2021-0705 CVE-2021-0708 CVE-2021-0651
CVE-2021-0483 CVE-2021-0926 CVE-2021-0653 CVE-2021-0928
CVE-2021-0650 CVE-2021-0930 CVE-2021-0919 CVE-2021-0970
CVE-2021-0704 CVE-2021-0967 CVE-2021-0964 CVE-2021-0968
CVE-2021-0965 CVE-2021-0952 CVE-2021-0969 CVE-2020-0338
CVE-2021-39623 CVE-2021-39621 CVE-2021-39626 CVE-2021-39627
CVE-2021-39629 CVE-2021-39628 CVE-2021-39659 CVE-2021-39674
CVE-2021-39692 CVE-2021-39667 CVE-2021-39704 CVE-2021-39706
CVE-2021-39707 CVE-2021-39705 CVE-2021-39796 CVE-2021-39803
CVE-2021-39808 CVE-2021-39809 CVE-2021-39807

Thanks for your work. Good rom.

### UPDATE ###
-> Updated patch level to 2022-05-01
-> I did some small undervolting. If you don't want this, just flash another kernel, e.g. White Wolf.
-> Download: https://freeze.ws/RR
I've implemented the following fixes:
Code:
CVE-2022-20004
CVE-2022-20005
CVE-2021-39700
CVE-2022-20114
CVE-2022-20011
CVE-2022-20112
CVE-2022-0847
CVE-2022-20009

I would love to use this rom, installed yesterday and very happy with it but cannot get CTS to pass for magisk which i need for banking apps to use as my daily rom. Have you managed to get this working?

Have you tried Magisk Canary?
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
I'm not sure if it will work. At least you need to hide the Magisk app itself and use the MagiskHide function.

I sorted it, thanks

Slayerkodi said:
I sorted it, thanks
Click to expand...
Click to collapse
So it's working?

Freeze24 said:
So it's working?
Click to expand...
Click to collapse
Yes it's working fine, I didn't use canary just original magisk, no issues - works fine

### UPDATE ###
-> Updated patch level to 2022-06-05
-> Download: https://freeze.ws/RR
Code:
CVE-2022-20006
CVE-2022-20138
CVE-2022-20130
CVE-2022-20124
CVE-2022-20134
CVE-2022-20135
CVE-2022-20142
CVE-2022-20144
CVE-2022-20147
CVE-2022-20123
CVE-2022-20131
CVE-2022-20129
CVE-2022-20143
CVE-2022-20141
CVE-2022-24958
CVE-2022-25258
CVE-2022-20132
CVE-2022-25375

### UPDATE ###
-> Updated patch level to 2022-07-05
-> Download: https://freeze.ws/RR
Code:
CVE-2022-20219
CVE-2022-20229
CVE-2021-0981
CVE-2022-20223
CVE-2022-20221
CVE-2022-20224
CVE-2022-20230
CVE-2022-20227

### UPDATE ###
-> Updated patch level to 2022-08-05
-> Download: https://freeze.ws/RR
Code:
CVE-2022-20344
CVE-2022-20350
CVE-2022-20358
CVE-2022-20346
CVE-2022-20353
CVE-2022-20347
CVE-2022-20360