Related
I work with Cisco devices on a regular basis. To connect to them, I need to use a DB9 serial.
I have tried the usb to serial Prolific 2303 chipset but it isn't supported in the OS (I'm not sure why this was removed from the Android Linux kernel because it is standard in Linux kernel 2.4.31 and later but anyway...)
Anyone know of a way to get serial connectivity so I can use this tablet as a true laptop replacement? Maybe a serial to bluetooth would work? Samsung says the bluetooth supports SPP but I don't want to dish out $70+ to find out it doesn't work.
Maybe someone familiar with compiling kernel modules for Android could assist? I have the pl2303.c source code but I'm not familiar enough with compiling kernels or kernel modules to attempt this.
I've been looking into this myself the past couple of days. The kernel is not compiled with support for USB-Serial converters, but all of the code is there. It looks like the kernel would have to be recompiled along with the required modules. Here is the source I'm using: https://github.com/pershoot/galaxy-2636
So far I've just looked at config and it is easy to enable the required modules, but I haven't managed to get the kernel compilation and ARM toolchain to work just yet.
samsung source
I noticed the pl2303.c and pl2303.h are in the Samsung source I downloaded.
I'm going to try to compile a kernel module in the next week.
I'm fairly shocked this hasn't been a bigger issue. We can't be the only ones wanting this functionality - especially since Samsung support basically told me to pound sand.
I've managed to compile an ICS kernel with the required configuration and modules, once I figure out how to get it on the device I'll test it. If it works I'll build a honeycomb kernel as well and post both in the dev section.
That is fantastic! I'm having issues getting my cross compile to work properly.
Well, I managed to build the kernel & modules properly but the adapter still isn't recognized even with the modules loaded. I think there might be more to the problem than missing modules
I read today that the main linux kernel and the android fork are going to be merging. Maybe that will lead to better device support.
Description
TDH-JR is a Magisk Module for extremely debloating ROMs based on the G920P stock nougat Android. The debloating is quite complete, so as little of your ROM actually runs after flash installing this module.
Screenshots
Coming . . .
Features
The entire debloat operation is systemless (i.e., no modifications occur to your base ROM, Magisk systemless overlays are used to prevent bloat from installing and running.
Extreme Debloat (Just enough ROM to Use, add your own apps)
The resulting debated system passes SafetyNet as long as your kernel also passes (suggest using @tdhite's SkyHigh Kernel).
Downloads
TDH-JR v1.1.20180512. (debloating based on Firrmware version G920PSPT4DRC2):
Android File Host Download
MD5: fcc0410e48d254be48c311a804ba271b
Updated for Magisk 16.40.
Updated for DRC2 stock firmware.
TDH-JR v1.0-20180101 (debloating based on Firrmware version G920PVPS4DQK1):
Android File Host Download
MD5: 5ffc47cae4dcd67bb38cb5afae17a8bb
How to Install -- FOLLOWING IN ORDER IS REQUIRED!
READ THE DISCLAIMER BEFORE INSTALLING!.
Assure you are on the appropriately similar base (stock) firmware.
Download the module from any of the download links above and place it in your /sdcard directory.
Strongly suggest downloading the latest @tdhite SkyHigh Kernel flash (installer) and place the zip in your /sdcard directory
Reboot to recovery (TWRP)
Make a backup of your existing ROM (TWRP nandroid is best)
Wipe Data, Dalvik, Cache (standard factory reset)
Strongly suggest installing (flashing) the latest @tdhite SkyHigh Kernel. That will install the kernel, root the phone with Magisk and install the kernel's support module. Note: if you do not install the SkyHigh kernel, you will have to manually install Magisk before installing the TDH-JR debloating module.
Dirty flashing coming from pure stock cannot debloat your ROM -- the bloat software is already installed and setup.
Dirty flashing over a system in which you previously installed this module cleanly (per instructions above) should work fine.
Flash (i.e., Install in TWRP) the flashable module zip file.
Reboot (to System)
Enjoy!
After cleanly installing (post a factory reset wipe) this module, the initial boot will take many minutes and may reboot once during the initial setup sequence. Many operations are taking place (e.g., Dalvik regeneration, activation, etc.).
Special Thanks and Credits
[MENTION]topjohnwu[/MENTION]@xda (For the venerable Magisk root)
XDA:DevDB Information
TDH-JR Debloating Magisk Module, Tool/Utility for the Sprint Samsung Galaxy S6
Contributors
tdhite
Source Code: https://github.com/TeamSPR/magisk-module-tdhjr
Version Information
Status: Stable
Current Stable Version: v1.1.20180512.
Stable Release Date: 2018-05-12
Created 2018-01-01
Last Updated 2018-05-13
Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use any software from download links provided anywhere within this thread, or convey the same to someone else, you and all subsequent conveyees are bound by the following:
LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THE PROGRAM
Assumption of the Risk of Use
YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THE PROGRAM. THE PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY, IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
Disclaimer of Warranty
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR, CORRECTION OR OTHERWISE.
Disclaimer of Title Warranty
THERE IS NO WARRANTY OF TITLE FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING ANY CONVEYOR OF THE PROGRAM MAKES NO WARRANTY OF ANY KIND THAT HE OR SHE HAS ANY TITLE OR THE RIGHT TO TRANSFER ANY TITLE TO THE PROGRAM TO YOU. YOU ACCEPT THAT, IN FACT, YOU RECEIVE NO TITLE TO ANY OF THE PROGRAM.
Limitation of Liability
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Reserved
Thanks for this! Looking forward to testing between football games. (A guy has to have priorities.)
works great
works great love the update thanks so much no problems so far lags a little during initial setup but no lag after all set up
Nice, thanks! Am I going crazy, or are the links to the module missing?
nostrings said:
Nice, thanks! Am I going crazy, or are the links to the module missing?
Click to expand...
Click to collapse
This? https://www.androidfilehost.com/?fid=673791459329070582
I do not understand this module at all, do we have to install it once we install a new stock rom? Or can i install it whenever i want? (Im on bigdaddys rom, can i install this right now?)
Ryan-sv said:
I do not understand this module at all, do we have to install it once we install a new stock rom? Or can i install it whenever i want? (Im on bigdaddys rom, can i install this right now?)
Click to expand...
Click to collapse
You can try -- I have no idea what BigDaddy loads or does not load from the stock kernel, much less its base. Whatever you do, follow the instructions.
tdhite said:
You can try -- I have no idea what BigDaddy loads or does not load from the stock kernel, much less its base. Whatever you do, follow the instructions.
Click to expand...
Click to collapse
Oh, i also have your kernel, but ok, i'll make a backup before try this
Working great, thanks @tdhite. Kernel seems to be offering support for Synapse, is that correct?
koop1955 said:
? . . Kernel seems to be offering support for Synapse, is that correct?
Click to expand...
Click to collapse
Yup. Just install Synapse and tune to your heart's content.
Sent from my iPad using Tapatalk
koop1955 said:
This? https://www.androidfilehost.com/?fid=673791459329070582
Click to expand...
Click to collapse
Yes. The XDA Labs app wasn't showing the link (see screenshot)
I installed this and i don't have the auto rotate or portrait icon when i pull down the top of phone! It is in auto rotate and i want it in portrait mode! Any help would be much appreciative??
I cannot for the life of me get Sprint Launcher or Sprint ID uninstalled. Anyone have any ideas? The phone restarts when I try to uninstall them.
_Epic said:
I cannot for the life of me get Sprint Launcher or Sprint ID uninstalled. Anyone have any ideas? The phone restarts when I try to uninstall them.
Click to expand...
Click to collapse
Have you tried adding those packages to the list of the directories in the module? It should be in the `config.sh` script. Or just post the paths here, and I am sure someone (or @tdhite) will add them to the list for the future.
nostrings said:
Have you tried adding those packages to the list of the directories in the module? It should be in the `config.sh` script. Or just post the paths here, and I am sure someone (or @tdhite) will add them to the list for the future.
Click to expand...
Click to collapse
I haven't gotten that far into it yet. I may check it out later.
Just a note for future reference - you should really not "uninstall" anything if you are using this module ... just add whatever you don't want on the list, and start again. This will ensure you are can receive OTA updates (though, these may not come anymore, as Samsung is probably abandoning this device for good now), and redo/reapply the magisk module again.
nostrings said:
Just a note for future reference - you should really not "uninstall" anything if you are using this module ... just add whatever you don't want on the list, and start again. This will ensure you are can receive OTA updates (though, these may not come anymore, as Samsung is probably abandoning this device for good now), and redo/reapply the magisk module again.
Click to expand...
Click to collapse
Actually there's a rumor from two Samsung support reps that s6 may actually get oreo! Not a reliable source, but worth holding out hope!
@tdhite Thanks for this module! I just switched over from the tdhjr Rom without a hitch. Feels clean and proper. Definitely a brilliant alternative to the tdhjr rom.
I do have one question, and anyone else who might know is welcome to chime in, which package that was debloated is responsible for how Google assistant works? I thought it was just the Google app, so i installed that (and the Google Assistant app)... But i cant use smart unlock (ya know, unlock with your voice) Does it need to be installed as a system app? Or was there another google related app/package that I'm forgetting about?
Nye-uhls said:
Actually there's a rumor from two Samsung support reps that s6 may actually get nougat! Not a reliable source, but worth holding out hope!
Click to expand...
Click to collapse
That would be super, but judging by past devices and the software they got, I'd say with 99% certainty that this is it. I'd love to be proved wrong, though ?
Modesty - a modest custom kernel for the Samsung Tab S4
Modesty aims to provide a mildly appealing and reasonable alternative to the stock 4.4.78 kernel that comes with The Tab S4. In its pursuit of being both mildly appealing and reasonable, it will eschew features that could compromise device stability, whilst gleefully embracing low-risk, self-contained enhancements. In other words, your lowest expectation should be that this kernel will be at least as stable as the stock kernel.
Since there are currently no other custom kernel projects supporting the Tab S4, there isn't really any previous device-specific work to build on. Development of this kernel is therefore likely to be slow and steady.
"Why is this kernel called Modesty? That's crap! Why not Wolverine, Intrepid or Jupiter?"
Because it's just a operating-system kernel, not a turbo-charged supercar or a mission into outer space. Even as operating-system kernels go, this one is pretty dull. Besides, I'm a weary curmudgeon in his fifties, not a teenager.
This project has the modest aim of modestly enhancing the pleasure you derive from your Tab S4 and is therefore modestly named Modesty.
Key characteristics
Supports both the wi-fi only (T830) and wi-fi/LTE (T835) models.
Forked from Samsung's pristine kernel source code (Linux 4.4.78 for ARGH firmware at time of launch).
Regular merging of the upstream Linux kernel's linux-4.4.y branch (4.4.161 at time of public launch).
Regular merging of Samsung's updates to its modified kernel source as they are made available.
Includes @savoca's KCAL advanced colour/gamma control driver.
Includes @flar2's sound control driver to manage headphone and microphone gain.
Disables a huge amount of tracing and logging features inexplicably left enabled by Samsung in the stock release kernel. These debugging features have no place outside engineering builds.
Packed into a boot.img (boot image) taken directly from Samsung's latest stock firmware and kept as close to the original as possible. No obscure boot-time kernel configuration is stashed away here, and no changes are made to any other part of the file system at either install time or run time.
Provides a fully automated installer, with the option of interactive installation to allow manual selection of features and the ability to automatically root the device with Magisk in the post-installation phase.
Includes WireGuard VPN support (version 0.0.20180818 at the time of public launch), which will be updated as available.
Includes @Lord Boeffla's generic kernel wakelock blocker. The conservative default block-list is: qcom_rx_wakelock and NETLINK.
Utilises Westwood+ TCP congestion algorithm by default.
Includes Veno TCP congestion algorithm.
SELinux operates in enforcing mode and cannot be dynamically switched to permissive mode.
FAQ
Q. Is this kernel still actively developed?
A. No. The final ianmacd release was v1.0.0 on 21st November 2019 and no-one else has picked up maintenance of the project.
Q. Will this kernel also run on Android 9.0 (Pie) devices?
A. No. Modesty targets Android 8.1 (Oreo) and there was never an intention to update it for 9.0 (Pie).
Q. Can I overclock or underclock the CPU using this kernel?
A. No.
Q. How does interactive installation mode work?
A. If the ZIP file name contains the string _interactive or a dot-file called .modesty_interactive is present in the root of the external SD card, interactive installation mode is triggered. Please note that this mode overrides any selections implied by the archive name or the presence of dot-files on the file-system.
In interactive mode, you will be asked whether to root the device afterwards with Magisk. Selections are made using the Volume buttons. Just follow the on-screen prompts.
Q. Can I safely block wakelock X?
A. Perhaps. However, unless you know what a particular wakelock does and are certain that it is causing an actual problem on your device, I suggest you leave it alone.
Q. Why is this kernel labelled beta? Is it safe to use? And who are you, anyway? Can you be trusted?
A. My T830 has been running this kernel every day since I first rooted it, and I can therefore personally vouch for its stability on this model.
A couple of users have reported Modesty running well on the T835. Initially, it was reported that the kernel did not boot on this model, but after trying several test kernels, the user in question discovered that his machine had a non-standard firmware installation. Once this situation was remedied, Modesty booted and worked as designed.
As the person who built the kernel, I know exactly what's in it, and therefore the only risk I'm exposing myself to when I run it is that of my own incompetence. That's not true for you, however, and you should exercise due caution and at least pause for a moment to consider what you are installing, and the far-reaching powers you are about to grant this unaudited code over your device. Although I link to the source code below, you have only my word for it that this bears any resemblance to the kernel actually provided in the installer.
There are likely to be many iterations of this kernel before it sees a 1.0 release. Features may be added or removed along the way, although there is no clear roadmap at this point in time. Development will go where the needs of the users take it.
Please see the Installation section below for an important note regarding the use of this kernel in combination with stock (i.e. unmodified) Samsung firmware.
Q. Can I safely root this kernel?
A. Of course. What use would it be if you couldn't? I recommend Magisk for the task. It has a few minor issues, but as a project is very much alive, something that cannot be said about its peers. Magisk has arguably now established itself as the de facto root solution for Android devices.
It just so happens that I also produce my own builds of Magisk, which you are welcome to use. These are release builds (as opposed to debugging builds), produced from my own fork of @topjohnwu's original source, often augmented with patches. You can use anyone's builds, though.
Again, these builds work for me on various Samsung devices, but they are unofficial and you should approach them with fitting caution.
Q. Can I install Magisk at the same time as Modesty?
A. Yes. The Modesty installer allows you to automatically root your device with Magisk following installation of Modesty..
To make use of this facility, either rename the Modesty zip file to contain the string _magisk or create a file called .modesty_magisk in either the root of your external SD card or in the standard Download directory of the internal SD card. Alternatively, you can utilise interactive installation mode. See above for details.
If any of these trigger conditions is met, the installer will look in the standard internal Download directory as well as in ./Magisk (if present) on the external SD card (if present) for a suitable Magisk zip file to install. Preference is given to versioned files matching the glob Magisk-v*, in which case the latest according to lexical sort order will be used. If none is found, the installer then looks for unversioned release builds (e.g. official Canary channel release builds) called magisk-release.zip in the same locations, selecting the one with the most recent timestamp. If none is found, the installer will then try to find unversioned debug builds (e.g. official Canary channel debug builds) called magisk-debug.zip, again picking the one with the most recent timestamp. Finally, the installer falls back to looking for the most recent file called Magisk.zip or magisk.zip. If still no files have been found by this stage, chaining of Magisk is abandoned.
For example:
Code:
star2lte:/ $ ls -l /storage/0000-0000/.modesty_magisk
-rwxrwx--x 1 root sdcard_rw 0 2018-09-15 14:31 /storage/0000-0000/.modesty_magisk
star2lte:/ $ ls /storage/0000-0000/Magisk/Magisk-* | tail -n 3
/storage/0000-0000/Magisk/Magisk-v17.2-2018091001-ianmacd.zip
/storage/0000-0000/Magisk/Magisk-v17.2-2018091201-ianmacd.zip
/storage/0000-0000/Magisk/Magisk-v17.2-2018091501-ianmacd.zip
When you flash the Modesty archive in TWRP, the most recent version of Magisk that could be found will now be used to automatically root your kernel, i.e. Magisk-v17.2-2018091501-ianmacd.zip in this example.
Q. Why doesn't Modesty have its own Telegram group?
A. Because my experience of Android-themed Telegram groups is that they invariably degenerate into seething cesspits of rudeness, ignorance, superstition and — on a good day — pseudo-science. I don't wish to police such a den of iniquity. Of course, it's a free world (or so I still like to kid myself), so you are at liberty to create your own Telegram group for Modesty if you wish. Just please don't invite me to it.
Building
Building the kernel from source is beyond the scope of this document. If you want to build this kernel from scratch, for example to change its configuration, start with this handy reference tailored to building kernels for Android.
Download
See posting #2 in this thread for links to the latest and all previous versions.
Known Issues
Bluetooth HID (input) devices do not work.
Versions 0.99.11 to 0.99.22 contained a bug that caused Bluetooth HID (input) devices, such as mice, keyboards and gamepads, not to function. They could be paired with the tablet, but their input was not recognised. This bug was finally traced and fixed in 0.99.23.
Installation
Make a back-up of your existing boot partition using the custom recovery environment provided by TWRP. If your device doesn't yet have TWRP, you will need to install it first. Then, use it to flash the Modesty ZIP file. The boot image will automatically be installed in the boot partition of your device.
If your device has unmodified Samsung firmware, you will encounter problems with Bluetooth (namely delayed initialisation and forgotten pairings) after installing this or any other custom kernel. To remedy this, you will need to patch your system with modified libsecure_storage.so libraries. Some custom kernel installers actually install these without telling you, overwriting your system libraries and transparently circumventing the problem before you can run into it. This approach necessarily modifies your device's file-system, however, and that may not be what you want. At the very least, the user should be made aware what is happening to his device.
For this reason, I have instead prepared a companion Magisk module that achieves the same goal without modifying the file-system. This will allow you to run a custom kernel (not just this one, but any custom kernel) on pristine stock firmware without any Bluetooth issues. The module can be found in the official Magisk module repository, accessible from Magisk Manager on your tablet. If you install this Magisk module, you may wish to also disable the secure_storage_daemon by editing /system/etc/init/secure_storage_daemon.rc (change start to stop), as it no longer serves a purpose.
In a similar vein, you may encounter authentication errors when connecting to wireless networks after installing this or any other custom kernel. This problem is not serious and easily remedied by re-entering your passphrase for the networks you use.
Finally, if SecurityLogAgent notifies you that unauthorised actions have been detected, do not be alarmed. This is a normal consequence of having installed a custom kernel. You may wish to disable SecurityLogAgent to avoid being repeatedly notified..
Whilst the above issues are the only ones you can expect to encounter when running this kernel vs. the stock Samsung kernel, they may sound like more trouble than they're worth. In that case, you might be happier just sticking to Samsung's stock kernel. The company supplies a perfectly good kernel straight from the factory.
Configuration
You are encouraged to use either @morogoku's excellent MTweaks (a modified version of Kernel Aduitor) or @flar2's EX Kernel Manager to manage the features provided by this kernel.
Source code
Modesty's GitHub repository.
References
A useful guide to CPU governors, I/O schedulers (and more).
For more information on the some of the individual schedulers included in this kernel, you can also look under Documentation/block in the kernel source.
The WireGuard user guide, control app, home page and source code.
Credits
Thank you to everyone in the Linux kernel universe for getting us this far. Within the Android development community, I am grateful to the following people for their time-saving contributions:
@osm0sis for Android Image Kitchen, which has saved me a huge amount of work in packing and unpacking boot images.
An honorary mention must go to @Chainfire, the extent of whose benefaction to the Android community is still not fully understood or appreciated in some quarters.
Change log
v1.0.0 (final ianmacd release) (2019-11-21)
Kernel proclaimed stable. Version number incremented. No code changes since v0.99.49.
v0.99.49 (2019-11-16)
Updated to Linux 4.4.202.
v0.99.48 (2019-11-13)
Updated to Linux 4.4.201.
v0.99.47 (2019-11-11)
Updated to Linux 4.4.200.
v0.99.46 (2019-11-06)
Updated to Linux 4.4.199.
v0.99.45 (2019-10-31)
Updated to Linux 4.4.198.
v0.99.44 (2019-10-19)
Updated to Linux 4.4.197.
v0.99.43 (2019-10-08)
Updated to Linux 4.4.196.
v0.99.42 (2019-10-07)
Updated to Linux 4.4.195.
v0.99.41 (2019-09-22)
Updated to Linux 4.4.194.
v0.99.40 (2019-09-16)
Updated to Linux 4.4.193.
v0.99.39 (2019-09-11)
Updated to Linux 4.4.192.
Fixes unavailability of external SD card in Modesty 0.99.38.
v0.99.38 (2019-09-08) Release withdrawn (External SD card unavailable)
Updated to Linux 4.4.191.
v0.99.37 (2019-08-26)
Updated to Linux 4.4.190.
v0.99.36 (2019-08-12)
Updated to Linux 4.4.189.
v0.99.35 (2019-08-07)
Updated to Linux 4.4.188.
v0.99.34 (2019-08-05)
Updated to Linux 4.4.187.
v0.99.33 (2019-07-23)
Updated to Linux 4.4.186.
v0.99.32 (2019-07-12)
Updated to Linux 4.4.185.
v0.99.31 (2019-06-28)
Updated to Linux 4.4.184.
v0.99.30 (2019-06-22)
Updated to Linux 4.4.183.
v0.99.29 (2019-06-18)
Updated to Linux 4.4.182.
v0.99.28 (2019-06-12)
Updated to Linux 4.4.181.
v0.99.27 (2019-05-17)
Updated to Linux 4.4.180.
v0.99.26 (2019-04-28)
Updated to Linux 4.4.179.
v0.99.25 (2019-04-07)
Updated to Linux 4.4.178.
v0.99.24 (2019-03-26)
Updated to Linux 4.4.177.
Build only the latest revision of the DTB.
v0.99.23 (2019-03-02)
Fixed bug, introduced in v0.99.11, that caused input from Bluetooth HID devices, such as keyboards, mice and gamepads to be ignored.
v0.99.22 (2019-02-23)
Updated to Linux 4.4.176.
v0.99.21 (2019-02-20)
Updated to Linux 4.4.175.
v0.99.20 (2019-02-11)
Updated to Linux 4.4.174.
v0.99.19 (2019-02-08)
Updated to Linux 4.4.173.
v0.99.18 (2019-01-26)
Updated to Linux 4.4.172.
v0.99.17 (2019-01-17)
Updated to Linux 4.4.171.
v0.99.16 (2019-01-13)
Updated to Linux 4.4.170.
v0.99.15 (2018-12-30)
Rebased on ARK4 kernel source code and boot images.
v0.99.14 (2018-12-23)
Updated to Linux 4.4.169.
Merged four more UPSTREAM commits from android-4.4 kernel branch.
v0.99.13 (2018-12-13)
Updated to Linux 4.4.167.
Merged selected BACKPORT and UPSTREAM commits from android-4.4 kernel branch.
v0.99.12 (2018-12-05)
Updated to Linux 4.4.166.
Realtek USB Ethernet driver upgraded from v2.08.0 to v2.10.00.
v0.99.11 (2018-11-29)
Updated to Linux 4.4.165.
KCAL advanced colour/gamma control driver optimisation.
Added @flar2's sound control driver for controlling headphone and microphone gain. (Configure with MTweaks or EX Kernel Manager).
v0.99.10 (2018-11-21)
Updated to Linux 4.4.164.
Added KCAL advanced colour/gamma control driver. (Configure with MTweaks or EX Kernel Manager).
Lots of tracing and debug logging disabled, further reducing kernel size.
CONFIG_DISPLAY_USE_INFO
CONFIG_SEC_DISPLAYPORT_LOGGER
CONFIG_FB_MSM_MDSS_XLOG_DEBUG
CONFIG_SEC_FILE_LEAK_DEBUG
CONFIG_SEC_DEBUG_USER
CONFIG_SEC_DEBUG_SUMMARY
CONFIG_SCSI_UFSHCD_CMD_LOGGING
CONFIG_MSM_SMEM_LOGGING
CONFIG_PROFILING
CONFIG_DEBUG_INFO
CONFIG_SCHED_DEBUG
CONFIG_SEC_PM_DEBUG
CONFIG_CORESIGHT
Built as monolithic kernel (i.e. without CONFIG_MODULES).
Built as relocatable code (CONFIG_RELOCATABLE_KERNEL).
Assembler symbols stripped (CONFIG_STRIP_ASM_SYMS set).
Embedded kernel config (reported via /proc/config.gz) now falsely reports stock settings to allow disabling of superfluous kernel features that otherwise cause grave Android System warning on boot.
v0.99.9 (2018-11-13)
Rebased on ARJ3 kernel source code and boot images.
v0.99.8 (2018-11-10)
Updated to Linux 4.4.163.
More than 100 fixes applied from upstream AOSP android-4.4 and android 4.4-o branches.
Lots of tracing and debug logging disabled:
CONFIG_IPC_LOGGING (debug logging for IPC drivers)
CONFIG_QCOM_RTB (register tracing)
CONFIG_TRACER_PKT (for tracing IPC protocols)
CONFIG_FTRACE (kernel tracing infrastructure)
CONFIG_CPU_FREQ_SWITCH_PROFILER (CPU frequency switch profiler)
CONFIG_TRACING_EVENTS_GPIO (traces GPIO subsystem)
Fixes to allow kernel to build when above logging and tracing options are disabled.
v0.99.7 (2018-10-30)
Rebased on ARH5 kernel source code.
Reworked the v4l2 fix that restores liboemcrypto-dependent apps to working state.
v0.99.6 (2018-10-28)
v4l2 fixes to restore liboemcrypto-dependent apps to working state.
v0.99.5 (2018-10-21)
Updated to Linux 4.4.162.
v0.99.4 (2018-10-19)
Initial public release, based on Linux 4.4.161.
v0.99.3
Internal build, based on Linux 4.4.160.
v0.99.2
Internal build, based on Linux 4.4.159.
v0.99.1
Initial internal build, based on Linux 4.4.78.
It begins! Awesome to finally see a custom kernel for the Tab S4.
I want to test for you once I can get root back
ianmacd said:
Change log
v0.99.4 (2018-10-19)
Initial public release, based on Linux 4.4.161. Caution: This kernel remains completely untested on the T835.
v0.99.3
Internal build, based on Linux 4.4.160.
v0.99.2
Internal build, based on Linux 4.4.159.
v0.99.1
Initial internal build, based on Linux 4.4.78.
Click to expand...
Click to collapse
Flashed on T835 device doesnt even get past the Boot (custom device) screen is there a way to get logs without using a computer?
Sent from my Samsung SM-G950F using XDA Labs
dr460nf1r3 said:
Flashed on T835 device doesnt even get past the Boot (custom device) screen is there a way to get logs without using a computer?
Click to expand...
Click to collapse
I'll look into it this evening. I'm just about to get off a plane.
Were there any errors when installing? Was your device properly detected as a T835?
Sent from my SM-G965F using XDA Labs
ianmacd said:
I'll look into it this evening. I'm just about to get off a plane.
Were there any errors when installing? Was your device properly detected as a T835?
Click to expand...
Click to collapse
Installing just fine, correctly detected as well.
Sent from my Samsung SM-G950F using XDA Labs
dr460nf1r3 said:
Installing just fine, correctly detected as well.
Click to expand...
Click to collapse
I've gone through the ramdisk of the T835's boot image with a fine-tooth comb and can find nothing untoward. I also verified that I properly removed the dm-verity flag from the T835's device tree.
There are actually very few source code differences between the T830 and T835. Both can be built from a single tree. The only differences lie in the kernel config file and the device tree, but I am building with the default T835 configuration, and with the proper device tree for that device.
Let's try at least ruling out my installer code. Please image-flash this new boot image[/i] to your device and tell me if it boot-loops. If it does, my installer isn't the problem, because it's only used for a ZIP flash. I've already checked the installer code and can't see any bugs, so I don't think the issue lies there.
Can you also please tell me which version of the firmware your device is running? Possibly there's an issue there, too. Samsung has so far released the source to the ARGH kernel only. This seems to work fine on my ARH5 firmware, but it's uncertain whether it would still work on something based on ARI*, and I've seen that a couple of countries do now have ARI firmware available. Mind you, even if it wasn't compatible, it should still get as far as booting.
Anyway, please test that boot image and let me know your firmware version.
While I soldier on with the issues afflicting the T835 build, can anyone else verify the T830 build as working for them?
Don't be shy; I'm running it on my own device, so I'm certain that build boots.
ianmacd said:
While I soldier on with the issues afflicting the T835 build, can anyone else verify the T830 build as working for them?
Don't be shy; I'm running it on my own device, so I'm certain that build boots.
Click to expand...
Click to collapse
Sorry for the noob question if i flash this kernal on my SM-T835 will i lose DEX ? Sorry i'm not quite understanding what KERNEL does ? Thanks in advance!
N1NJATH3ORY said:
Sorry for the noob question if i flash this kernal on my SM-T835 will i lose DEX ? Sorry i'm not quite understanding what KERNEL does?
Click to expand...
Click to collapse
When the kernel is working as intended, you won't lose DeX, but it currently isn't even booting on the T835.
Only those who are able to assist in debugging the current boot failure should install the T835 build at this time.
The T830 build, on the other hand, is rock solid for me, and I encourage anyone who is capable of recovering from an unexpected bootloop to try it out.
Version 0.99.5 released.
This release updates the kernel to the latest upstream Linux.
T830 owners, install at will. T835 owners, beware: The previous release has been reported unbootable on this model, and this release is likely to be similarly afflicted. Investigations are ongoing. Until this issue is resolved, the whole project has been downgraded to alpha status.
Change log
Updated to Linux 4.4.162. Caution: This release is likely to cause a bootloop on the T835.
ianmacd said:
I've gone through the ramdisk of the T835's boot image with a fine-tooth comb and can find nothing untoward. I also verified that I properly removed the dm-verity flag from the T835's device tree.
There are actually very few source code differences between the T830 and T835. Both can be built from a single tree. The only differences lie in the kernel config file and the device tree, but I am building with the default T835 configuration, and with the proper device tree for that device.
Let's try at least ruling out my installer code. Please image-flash this new boot image[/i] to your device and tell me if it boot-loops. If it does, my installer isn't the problem, because it's only used for a ZIP flash. I've already checked the installer code and can't see any bugs, so I don't think the issue lies there.
Can you also please tell me which version of the firmware your device is running? Possibly there's an issue there, too. Samsung has so far released the source to the ARGH kernel only. This seems to work fine on my ARH5 firmware, but it's uncertain whether it would still work on something based on ARI*, and I've seen that a couple of countries do now have ARI firmware available. Mind you, even if it wasn't compatible, it should still get as far as booting.
Anyway, please test that boot image and let me know your firmware version.
Click to expand...
Click to collapse
Firmware Version ist arh5 and after flashing your img the device still constantly reboots on the start screen and doesnt even get to the boot Screen
Sent from my Samsung SM-G950F using XDA Labs
dr460nf1r3 said:
Firmware Version ist arh5 and after flashing your img the device still constantly reboots on the start screen and doesnt even get to the boot Screen
Click to expand...
Click to collapse
Thanks. That absolves the installer of any wrongdoing, at least.
Something is fundamentally wrong with the kernel for the T835.
The boot image is taken from stock firmware, and modified just enough to allow a custom kernel to boot. I very much doubt the problem lies there. A virtually identical image works for the T830.
The kernel config used is the one supplied by Samsung. The only modifications made to it are the same ones I made to the T830's.
I think my next step will be to produce a kernel built without downstreaming the 4.4.y Linux branch, so back to 4.4.78. If that works, it will indicate that an error affecting only the T835 was introduced during all of my merging of the upstream kernel.
I'll post again when I've built the kernel, which won't be for a few hours, as I'm on holiday at the moment.
Sent from my SM-G965F using XDA Labs
ianmacd said:
I think my next step will be to produce a kernel built without downstreaming the 4.4.y Linux branch, so back to 4.4.78. If that works, it will indicate that an error affecting only the T835 was introduced during all of my merging of the upstream kernel.
Click to expand...
Click to collapse
OK, @dr460nf1r3, please try this new T835 build.
This is rewound to 4.4.78, with just a few extra cherry-picked commits to enable it to build cleanly and boot without triggering dm-verity.
In other words, this kernel should be 99% identical to the one that shipped with the machine. This assumes that the source as supplied by Samsung was actually used to build the stock kernel.. They have been known to publish sources that don't match what's on the machine.
ianmacd said:
OK, @dr460nf1r3, please try this new T835 build.
This is rewound to 4.4.78, with just a few extra cherry-picked commits to enable it to build cleanly and boot without triggering dm-verity.
In other words, this kernel should be 99% identical to the one that shipped with the machine. This assumes that the source as supplied by Samsung was actually used to build the stock kernel.. They have been known to publish sources that don't match what's on the machine.
Click to expand...
Click to collapse
Thanks, flashing now will report back in a few minutes
Sent from my Samsung SM-G950F using XDA Labs
---------- Post added at 05:44 PM ---------- Previous post was at 05:17 PM ----------
ianmacd said:
OK, @dr460nf1r3, please try this new T835 build.
This is rewound to 4.4.78, with just a few extra cherry-picked commits to enable it to build cleanly and boot without triggering dm-verity.
In other words, this kernel should be 99% identical to the one that shipped with the machine. This assumes that the source as supplied by Samsung was actually used to build the stock kernel.. They have been known to publish sources that don't match what's on the machine.
Click to expand...
Click to collapse
Did not work still the same issue.. flashed via twrp to boot partition. Noob question, the boot backup i got is 64mb while your kernel hardly has 25.. whats going on here?
Sent from my Samsung SM-G950F using XDA Labs
dr460nf1r3 said:
Did not work still the same issue.. flashed via twrp to boot partition.
Click to expand...
Click to collapse
Well, that's disappointing. I was hoping that it was my screw-up, rather than Samsung's, but at this point almost everything I've done has been backed out and it still won't boot.
Noob question, the boot backup i got is 64mb while your kernel hardly has 25.. whats going on here?
Click to expand...
Click to collapse
Good question.
Your back-up is of the entire partition, including the area with no data on it, so you're getting a file the same size as the partition itself. My boot image contains just the data segment, so it's smaller.
If you pull the stock boot image from the AP file of Samsung's firmware, you'll see that it's a very similar size to mine (slightly smaller, actually):
Code:
$ unzip -p T835XXU1ARH5_T835OXM1ARH5_PHN.zip AP_T835XXU1ARH5_CL14008523_QB19263559_REV00_user_low_ship_MULTI_CERT_meta.tar.md5| tar xf - -O boot.img.\*lz4 | lz4 -dc > boot.img
$ ls -l boot.img
-rw-rw-r--. 1 ianmacd ianmacd 23593232 Oct 21 22:01 boot.img
$ file boot.img
boot.img: Android bootimg, kernel (0x8000), ramdisk (0x2000000), page size: 4096, cmdline (console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_le)
So, what now?
I'll see which other minor changes I can back out, in an effort to arrive at a kernel built from source that is as close to stock as possible. If you're wondering Why doesn't he just build from pristine sources?, the answer is: Because Samsung's source code won't even build out of the box. Many of the kernel header files are simply not in the expected locations. Alas, this is a fairly common problem with Samsung's kernel source code releases.
I suspect the solution to this problem may actually lie in changes that have yet to be made, rather than changes made that need to be reverted. In other words, the T835 may require some kernel modifications or configuration that the T830 doesn't. Theoretically, a kernel compiled from Samsung's pristine sources should just work, but that's starting to look unlikely now.
I'm hoping that I can enable/disable a few further options in the kernel config, rebuild and produce a kernel that works for you. If, however, the problem is that the source itself is faulty, we may have to wait for a future release by Samsung to give us something that compiles into a working kernel.
But I don't intend to throw in the towel on the T835 just yet. There are still a few more things we can try.
ianmacd said:
Well, that's disappointing. I was hoping that it was my screw-up, rather than Samsung's, but at this point almost everything I've done has been backed out and it still won't boot.
Good question.
Your back-up is of the entire partition, including the area with no data on it, so you're getting a file the same size as the partition itself. My boot image contains just the data segment, so it's smaller.
If you pull the stock boot image from the AP file of Samsung's firmware, you'll see that it's a very similar size to mine (slightly smaller, actually):
So, what now?
I'll see which other minor changes I can back out, in an effort to arrive at a kernel built from source that is as close to stock as possible. If you're wondering Why doesn't he just build from pristine sources?, the answer is: Because Samsung's source code won't even build out of the box. Many of the kernel header files are simply not in the expected locations. Alas, this is a fairly common problem with Samsung's kernel source code releases.
I suspect the solution to this problem may actually lie in changes that have yet to be made, rather than changes made that need to be reverted. In other words, the T835 may require some kernel modifications or configuration that the T830 doesn't. Theoretically, a kernel compiled from Samsung's pristine sources should just work, but that's starting to look unlikely now.
I'm hoping that I can enable/disable a few further options in the kernel config, rebuild and produce a kernel that works for you. If, however, the problem is that the source itself is faulty, we may have to wait for a future release by Samsung to give us something that compiles into a working kernel.
But I don't intend to throw in the towel on the T835 just yet. There are still a few more things we can try.
Click to expand...
Click to collapse
Thanks for explaining everything for me. Id like to help you were i can but i dont have a computer by my hands right now for the next time
Sent from my gts4llte using XDA Labs
dr460nf1r3 said:
Thanks for explaining everything for me. Id like to help you were i can but i dont have a computer by my hands right now for the next time
Click to expand...
Click to collapse
Here's a new build to try. This one reverts the last few changes I originally made to the T835's kernel configuration before building. This is as close to stock as possible, whilst still being able to build.
If this doesn't boot, it pretty much means that Samsung has supplied code for the T835 that simply will not compile into a working kernel. At that point, we'll probably have to wait for updated sources. I already have a request pending with Samsung for the release of the BRI sources.
Just to be clear, the current status quo as I understand it is that the Samsung logo never starts to be written from left to right. You never get past the static screen with the device name and the word Custom. Is that correct?
ianmacd said:
Here's a new build to try. This one reverts the last few changes I originally made to the T835's kernel configuration before building. This is as close to stock as possible, whilst still being able to build.
If this doesn't boot, it pretty much means that Samsung has supplied code for the T835 that simply will not compile into a working kernel. At that point, we'll probably have to wait for updated sources. I already have a request pending with Samsung for the release of the BRI sources.
Just to be clear, the current status quo as I understand it is that the Samsung logo never starts to be written from left to right. You never get past the static screen with the device name and the word Custom. Is that correct?
Click to expand...
Click to collapse
Im sorry to tell you but this doesnt boot either in fact it doesnt even reboot the static screen. Your right about the current status quo sadly.
Sent from my Samsung SM-G950F using XDA Labs
{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is not just another ROM - it is a mobile ecosystem (ROM + online services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds are all signed with a custom private key for best trust. This also means you have to factory reset when coming from another ROM!
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
You can LOCK YOUR BOOTLOADER - if you like
Build variants (UNOFFICIAL, CUSTOM)
UNOFFICIAL builds:
full OTA support
no other differences to pure /e/. It is just an unofficial build (if you want to have it official test my builds and report also SUCCESS! this ROM is currently awaiting to get approved by /e/ for official builds)
CUSTOM builds:
2 variants: rooted (magisk) or unrooted
removed: the app "Apps" (see FAQ why)
added: F-Droid, F-Droid priv ext, F-Droid additional repos (disabled by default), AuroraStore, Lawnchair-latest (taken from their TG group), PhoneSky (google play store - patched for microG), Magisk app when choosen the rooted variant
patched with this safetynet patch (this will not bypass safetynet though)
fully patched for AVB / dm-verity support - means you can lock your bootloader! (all builds since 3rd of Sep 2021) - yes even the rooted variant can run on locked bootloader!
SHRP included (accepted by a locked bootloader) - means when you want to use a different recovery you have to flash / re-flash it after flashing / upgrading the ROM. Including this is needed to not brick devices running on locked bootloader.
.. read all the details about locking your bootloader in this post
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
none known (yet)
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build (while I am testing with SHRP only)
Do a full (i.e. not just TWRP/SHRP - as those do not backup your internal storage) backup before doing anything!
Planning to lock your bootloader? Read this first
Installation
Planning to lock your bootloader?
Read on here
Detailed guide:
follow MSe1969's guide here
Quick guide (assuming you have TWRP/SHRP already):
Full clean install as described here (FAQ #2). DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
https://leech.binbash.rocks:8008/e-os/a10/hotdog/ (planning to lock your bootloader? Read this first)
If you have a previous version of my(!) /e/ Q installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
Join my Telegram groups (see "Support" topic)
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
MSe1969, wth.. you did an AWESOME job
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot (let me know if that's the case ofc) ..
Sources
/e/ : https://gitlab.e.foundation/e
my build manifest
MSe1969's stuff
Frequently Asked Questions (FAQ)
Q #0: For CUSTOM builds only: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
Often selinux can cause issues so try that at very first:
Code:
if you have magisk installed:
adb shell
su
setenforce permissive
When " usb debugging root" is enabled in developer settings:
adb root
adb shell
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If your issue is not solved with selinux permissive click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
Yes. With your help! What you can do? Test and report EVEN SUCCESS in this thread.
Q #4: Is there a FAQ specific for /e/?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
App alternatives (to replace google variants): click
Q #5: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #6: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #7: What is the difference between CUSTOM and UNOFFICIAL builds?
See OP
Q #8: Will my banking app (or other root detecting app) work with this ROM?
The answer is .. well .. simple. it depends.
First of all the following technique works regardless of what ROM you are using or what device. It worked with my LG G4, OnePlus 6T and now OP7tpro so its a generic "maybe-solution"
Read on here:
I am using a german banking app which works even when root gets detected. It will prompt and say thats bad but I am still able to use it. The same was the case for the TAN generator app of the same bank but it fully stopped working one day after a (forced) app upgrade.
So I started to play around and found a solution which works for me since several years but there is no guarantee it will work for you or for how long it will work. The process and steps must be followed briefly and nothing more, nothing less must be done.
The following references a banking app but it applies to any app which rejects starting when root or a custom ROM has been detected:
you need root, i.e. Magisk. This ROM has a custom build which includes Magisk already.
uninstall the currently not working banking app(s)
install & setup a work-profile manager like Insular, Shelter, (if you do not care about google trackers: Island), or [fill-in-another] ,.....
configure Magisk that it hides itself (i.e. re-package Magisk with a random name) & reboot just to be sure. and yes that works on signed and locked ROMs, too
newer Magisk versions will clone themself into the island profile during the repackage process so open island then switch to the island tab and remove the magisk app there (so not from the "mainland"!)
install the banking app(s) - BUT DO NOT start it!
clone that app into your work-profile (i.e. open Insular/Shelter/Island/.. find the app, clone it there), repeat that step for any app needed
configure Magisk hide for this app(s) and ensure you select all options (some apps can be expanded in magisk hide, select all options then)
remove any icons of your app(s) from your launcher but DO NOT UNINSTALL them!! (never)
in your work-profile manager (Insular/Shelter/Island/...) find your app and create a quick start launcher (repeat that for any app needed)
now start your banking app quick link (again it HAS to be the one created by your work-profile manager). usually you can identify that you are using the right one bc it has a mini icon of your work-profile manager on top of the regular app icon
enjoy. if it does still detect root or a custom ROM you either have not followed the above steps briefly or you are out of luck.
Background:
You cannot uninstall the app(s) from android (ever) because otherwise Magisk hide will not work. so you always need to keep that app(s) but never starting it.
It can make sense to try another work-profile manager if the above way fails for you as the app devs using different techniques
Q #9: Will DRM protected content work? | Will this ROM satisfy Safetynet?
Likely not. Yes this ROM is signed, selinux is enforcing and you can lock your bootloader but these days this is not enough anymore. While there are some workarounds available these might stop at any time. So do not expect that this will work or work for a long time.
LOCK your bootloaderYes you read correctly: you can lock your bootloader again! Why is that so amazing? The most important thing: security. When your bootloader is locked no one can install or modify without you notice it. Let's say you loose your phone and your bootloader is unlocked. The person can boot into fastboot and flash a custom recovery of his choice and have full access to your data (if not having a pin set) but also can tamper e.g. your system partitions like installing malware. Yea for that the attacker needs physical access to your phone but there is malware around and this is REAL which uses bugs to install themselves even on your system partition. For this the attacker does NOT need physical access to your phone.
On a locked bootloader the device won't boot anymore as a modification like that will be detected.
Anyways.. yea one can say both attack variants are not THAT critical or affecting you as you are paying attention on what you do but .. there is a always a risk of undetectable malware like the good old drive-by downloads etc. so .. its all up to you if you want to have that extra barrier or not..
But before we begin
a HUUUUGE thanks to @WhitbyGreg !!!
All this here would not be possible without his great guide here ! Ofc I need to adapt it and integrate all this within my automation process but it would have been a LOT harder without his thread(s).
So if you love it having a locked bootloader now - give HIM some thanks clicks, donations, hugs.. as well
Checklist: is locking the bootloader something for me?If you answer anyone - even just 1 - of the following with YES - then KEEP AWAY FROM LOCKING your bootloader!
I want to remove (not just disable) system apps (often called bloatware)
I want to add / convert apps into system apps (e.g. Titanium Backup offers such an option)
For rooted variant: I want to update Magisk to the latest version
For rooted variant: I want to change init scripts, XMLs or anything else within system/, product/ etc partitions
For rooted variant: I want to use an ad-blocker which modifies the "hosts" file (system partition)
I want to install another recovery then the one coming with the ROM (SHRP)
I want to flash GApps (LOL! this is /e/ !! even on unlocked bootloader this won't work!)
I want to flash anything else in recovery which modifies: boot, recovery, system or any other partition then userdata
Do you have answered at least 1 of the above with YES ? Then do NOT lock your bootloader. It WILL brick your device if you try.
if you can live with the above - GO GO GO
Lock your bootloader - processDownloads
ROM without root: https://leech.binbash.rocks:8008/e-os/a10/hotdog/ (all CUSTOM(!) builds since 2021-09-03)
AVB key: https://github.com/sfX-android/update_verifier/blob/master/hotdog_eos-q_custom_pkmd.bin
ROM with root: https://leech.binbash.rocks:8008/e-os/a10_rooted/hotdog/ (all CUSTOM(!) builds since 2021-09-03)
AVB key: https://github.com/sfX-android/update_verifier/blob/master/hotdog_eos-q_custom-rooted_pkmd.bin
backup all your data. I am serious EVERYTHING. we need to FORMAT the userdata partition during the lock process and there is no way around. so use TB or Swiftbackup, Migrate or any other. Always a good idea to also having a TWRP/SHRP backup just for the case..
boot your current recovery
flash the ROM of your choice (with or without root)
reboot to the bootloader / fastboot
if you flashed the ROM with root: fastboot flash avb_custom_key hotdog_eos-q_custom-rooted_pkmd.bin
if you flashed the ROM without root: fastboot flash avb_custom_key hotdog_eos-q_custom_pkmd.bin
type: fastboot oem lock
approve locking the bootloader on the phone's screen
< take a deeeeeeep breath >
recovery (SHRP) will load automatically
choose wipe -> format(!) data (there is no way around)
boot android -> you will notice a new bootloader message warning you that you have a custom ROM installed - but it will load
congrats! you now running on a locked bootloader + /e/ OS!
for the rooted variant: start the Magisk app (requires internet), accept the install request and open the magisk app afterwards and let it reboot when asked
enjoooooy
Locked - now what?OEM unlock option
The above does not mention one additional step: disabling OEM unlock in developer options. For a reason. I mean you CAN uncheck that option now that all is running fine but you don't get any more security tbh.
The reason is if you keep it checked an attacker is able to unlock your device but it WILL format the encryption keys when done. that means no way to access your data anyways. If you want to avoid even that then feel free to uncheck OEM unlock in developer settings as well but then a brick will require low level recovery tools to bring your device back to life.
Magisk (rooted variant)
I recommend to disable automatic update checking within magisk settings - remember: when flashing a newer version of magisk it WILL brick your device. you have to wait for me updating it within the ROM.
Anything you do within Magisk can EASILY BRICK your device, installing a magisk module which tampers your system partition: BRICK. So really really check if a module touches anything mentioned in the above checklist topic. Using the magisk variant has HIGH potential of bricking your device.
You can use all standard root functions, magisk hide and even re-pack the magisk app though.
Bricked
Always keep an eye on the above "Checklist" topic! If you change/do something mentioned there you will brick your device with a snap of a finger.
Android does not boot anymore because you flashed a newer version of Magisk or changed something within the protected partitions:
boot recovery (power off, press power on and vol down the same time and keep it pressed until you see the shrp logo)
flash the current ROM version or a later release and reboot
recovery does not load bc you flashed another recovery:
wait for the next OTA and it get fixed automatically
or unlock the bootloader again (this will need to FORMAT the userdata partition)
Sounds like a cool ROM, however I'm curious, what issues might I run into having no Google services? Are most apps going to work ok?
L4WL13T said:
Sounds like a cool ROM, however I'm curious, what issues might I run into having no Google services? Are most apps going to work ok?
Click to expand...
Click to collapse
hard to say. there are some which might not work and/or apps you should avoid (as they contain trackers etc). There is a good list of alternatives in FAQ 4 above
steadfasterX said:
Do a full (i.e. not just TWRP/SHRP - as those do not backup your internal storage) backup before doing anything
Click to expand...
Click to collapse
Do TWRP backups even work on this device? Last I heard, it was broken.
Hi! Why is there no gesture based navigation??? I'd love to see it!!!
at first glance the system is very surprising, like the very idea of a system without GAPPS. Looking forward to the development)
ap81z said:
Hi! Why is there no gesture based navigation??? I'd love to see it!!!
at first glance the system is very surprising, like the very idea of a system without GAPPS. Looking forward to the development)
Click to expand...
Click to collapse
Yea they removed it bc their launcher does not support it yet. There is an open issue on their bug tracker. I don't know when they will fix it tbh but i need it so bad that i found a way to include it. It's a kind of dirty hack but ... it works and will find its way in my next CUSTOM build..
steadfasterX said:
Yea they removed it bc their launcher does not support it yet. There is an open issue on their bug tracker. I don't know when they will fix it tbh but i need it so bad that i found a way to include it. It's a kind of dirty hack but ... it works and will find its way in my next CUSTOM build..
Click to expand...
Click to collapse
ok, I'll be waiting!!!
forgot to mention it here (another reason why users should join my automation channel):
Gestures are supported since the latest version.
breaking news:
I was working on using this device as my DD again but I have very strict requirements:
/e/ OS must work (reason: privacy focus, google-free) [ DONE ]
encryption must work (reason: security, e.g. loosing or selling the phone) [ DONE ]
selinux must run in enforcing [ DONE ]
/e/ OS must be signed with own private key (reason: allowing secure OTA and local/recovery upgrades) [ DONE ]
SHRP must work (reason: a password on startup can be set - allowing to have rich recovery feature set but secured - when the bootloader is locked!) [ DONE ]
and here the fun began:
/e/ OS must run on locked bootloader [ DONE ]
SHRP must run on locked bootloader [ DONE ]
OTA must work on locked bootloader [ WIP ]
so overall I am pretty much where I want to be and can provide a privacy focused, secure, google-free and locked bootloader experience soon...
stay tuned
Ever wanted to lock your bootloader - not on STOCK but on a custom ROM?Most ppl don't know (or don't care) that almost all Oneplus devices offer such an option - if the ROM dev is willing to take the journey implementing it.
This is now possible when running my /e/ OS CUSTOM builds (read more in the OP about the diff between CUSTOM and UNOFFICIAL) and not just that my new CUSTOM builds coming either pre-rooted or not - whatever you wish more.
I have to say that this was something on my to-do list since I bought this device more then 1 year ago. After a lot of work in the past months I am finally where I am and can use it as my DD again. Something which makes me reeeeeeally happy lol
Dunno but maybe someone enjoys having a locked bootloader like I do
Read all the details and how it works: here
Hey just for info, I'v tried without relocking bootloader, to install aa auto as I do on lineage, and it give me the same result as locked bootloader, a black screen, I know that it's not your job to debug aaauto since it's a de-google rom. But the rom is unusable in my case, another question, why Play Store is installed by default ?
Thanks
Also I doesn't find any option to change 60hz/90hz ?
Thetimelost said:
Hey just for info, I'v tried without relocking bootloader, to install aa auto as I do on lineage, and it give me the same result as locked bootloader, a black screen, I know that it's not your job to debug aaauto since it's a de-google rom. But the rom is unusable in my case, another question, why Play Store is installed by default ?
Thanks
Click to expand...
Click to collapse
The CUSTOM builds containing the play store as i need it for some apps which do their license check over it. You csn simply deactivate it or use the UNOFFICIAL build instead (which do not allow locking the BL though).
Thetimelost said:
Also I doesn't find any option to change 60hz/90hz ?
Click to expand...
Click to collapse
Hmm good q. Is there an option for that in LOS? Maybe that's a limitation by /e/ but dunno tbh
steadfasterX said:
The CUSTOM builds containing the play store as i need it for some apps which do their license check over it. You csn simply deactivate it or use the UNOFFICIAL build instead (which do not allow locking the BL though).
Hmm good q. Is there an option for that in LOS? Maybe that's a limitation by /e/ but dunno tbh
Click to expand...
Click to collapse
Thanks for the answer ! Yes on LOS there is an option for it, and after use my op7t pro for 2 year with 90hz I directly spot the difference. ^^
Thetimelost said:
Thanks for the answer ! Yes on LOS there is an option for it, and after use my op7t pro for 2 year with 90hz I directly spot the difference. ^^
Click to expand...
Click to collapse
Hm interesting mine is running at 90 hz all the time it seems. Weird bc /e/ is based on LOS so maybe its an option in a11 first?
When will we get Android 11?
andr052h said:
When will we get Android 11?
Click to expand...
Click to collapse
Why do you want to have it?
steadfasterX said:
Why do you want to have it?
Click to expand...
Click to collapse
I mean, I really like what you have done with your current build, and would love to see that applied to the new Android 11 version as-well.
andr052h said:
I mean, I really like what you have done with your current build, and would love to see that applied to the new Android 11 version as-well.
Click to expand...
Click to collapse
Well first of all I thought no one uses my ROM anyways so there was no need for me upgrading to a11. This ROM is rock stable and does what i need as a daily driver and gets monthly security patches. Many ppl just want to have a newer android version just bc there is one and not bc for a specific reason. That's why I'm asking.
I personaly prefer a good working ROM over having always the newest android version just because there is one
Other then that i may upgrade to a11 but not anytime soon. Main reason is that I am using this as my daily driver so it would be hard alsi dev on it..
Obviously we all know this, but I'll say it anyway: I bear no responsibility for your device!
Background:
Initially I recompiled the kernel, but thanks to @fddm I was able to get this into a Magisk module. This is a take-off from https://forum.xda-developers.com/t/...-tether-lineageos-18-1.4295601/#post-86183959 Feel free to read that (minimal reading) for additional details.
What is this?
This Magisk mod adds the required iptables kernel module for TTL/Tether/unmetering for using your phone as a hotspot. I have Tmobile & with my plan, when I connect any device to the phone it is extremely throttled to around 0.5Mbps. With this mod and the settings below, you can get around that limitation. I go from 0.5Mbps=>80+Mbps with this mod. Root is required (look at above thread for details on that if needed).
Compatibility:
Confirmed OS's that work: LineageOS18.1, LineageOS19.1
ROMs: At this point I can't indicate what ROMs this will be compatible with, but it appears LineageOS18.1 works. I'm attaching that as well as a Android/AOSP12 version if anyone wants to test that. I'm also not sure if this is exclusive to the bramble/Pixel 4a5g device (If anyone knows what they're doing or wants to get ballsy, test & report your results!)
Carrier: I tested this against Tmobile. It depends on how your carrier throttles your hotspot connected devices; Tmobile uses the TTL to determine if its the phone vs a connected device. If your carrier uses that method this should work.
xt_HL.ko: This is the kernel module we're inserting to allow the "iptables ttl set" command. I tested the Android12 xt_HL.ko file on my LineageOS18.1 OS and it does NOT work. This tells me there is some type of versioning. OR: there's an issue with the A12 file...
InCompatibility: (as reported by users in the thread)
ProtonAOSP 12, pixel 4a5g
Steps:
Install Magisk module & read the output; Verify it installed successfully.
Download Termux app from playstore
Termux App: (Shouldn't be necessary if running latest script since that does this step for you on every boot)
su (Grant permissions)
iptables -t mangle -A POSTROUTING -j TTL --ttl-set 64 (should be no errors - if you have errors my kernel is not installed)
Test: Turn on phone Hotspot, connect any device, do a speed test comparing speed on phone should be similar to the connected device.
If any limitations/blocks: (Not sure but maybe http vs https is blocked sometimes)
Install VPN Hotspot app (Green key icon): "Wi-Fi hotspot" ON, wlan1 ON, DISABLE "Tethering HW Acceleration" in settings
Issues:
After running the iptables command you get this error: iptables v1.8.4 (legacy): unknown option "--ttl-set" Try 'iptables -h' or 'iptables --help' for more information. This means the module was not loaded (or isn't compatible. Assuming the correct version was selected, there's no fix. Likely your OS isn't compatible with this module. If anyone has additional troubleshooting to add feel free to chime in.
Technical Additional Info:
ttl_magisk_L18.1: This contains the xt_HL.ko file compiled from the lineage-18.1-20220102-nightly-bramble-signed repo
ttl_magisk_A12: This contains the xt_HL.ko file compiled from AOSP kernel: android-msm-redbull-4.19-android12
Updates:
* I updated the thread title since no one reporting the Android 12 kernel mod is working (only 11 works this far)
* I added "ttl_magisk_L19.zip" script which runs the iptables command for you on every boot. I just tested this on LineageOS19.1 and it works good. I'm working on testing it on LineageOS20.0...
Based on what @fddm said though, it sounds like a Magisk module like this will not work on stock AOSP because it "enforces signatures on modules". If anyone can confirm that, or a workaround that would be helpful. Also https://forum.xda-developers.com/t/...l-tether-lineageos-18-1.4295601/post-86173703 indicates we'll want to disable IP6 via these commands:
ndc interface ipv6 rndis0 disable
ndc interface ipv6 wlan0 disable
If anyone wants to test & get back that'll be great. With Tmobile I didn't need to do that (yet), but again feedback would be great.
I had checked the stock and Lineage configs and neither had signature enforcement enabled. I only had access to this phone for a couple days, so I unfortunately can't test for you.
fddm said:
I had checked the stock and Lineage configs and neither had signature enforcement enabled. I only had access to this phone for a couple days, so I unfortunately can't test for you.
Click to expand...
Click to collapse
So you think this should work on stock? Thanks man! I need my phone for work so can't put it offline for hours atm, but maybe over the weekend I can. I'd like to reflash android 12 stock & see if this works. I'd have to assume there's some interest in this... Someone else to test...who knows
hi, I am on ProtonAOSP 12, pixel 4a5g, tested the ttl A12 zip file. But it gave me error when trying to run the iptables command as per your instruction. So I guess it is not loading the module maybe
creezalird said:
hi, I am on ProtonAOSP 12, pixel 4a5g, tested the ttl A12 zip file. But it gave me error when trying to run the iptables command as per your instruction. So I guess it is not loading the module maybe
Click to expand...
Click to collapse
Apologies for your results. I just updated the OP with an "Issues" section I'll update with issues reported, and any fixes if we discover any. I've only successfully tested this against LineageOS18.1, and was only hopeful it would work against other OS's. Just for kicks, since it's a pretty simple/quick process, you may want to try the ttl_magisk_L18.1 version. BTW that entire command is case-sensitive in case someone didn't know (Eg. Iptables... will not work; iptables... will).
Regarding the fix for your issue...I think Proton is based just on AOSP, and nothing to do with LineageOS. I wouldn't think that would matter but pointing. I would've made an Android12/LineageOS19.0 module but it isnt official yet for this device. I'm not sure how willing the Proton folks would be, but the next logical step would be to have them add the following options to their ProtonAOSP12 "redbull_defconfig" file (or equivalent), build it, and send me over the xt_HL.ko file. Then I'll add a magisk module for that for you to test.
Side note: there are 4 recent AOSP kernel versions for this device. So if there are compatibility restraints with versions, I'd guess we'd have a maximum of 4 to deal with, depending on what OS you have. I don't know for sure, but wouldn't think your ROM being AOSP, LIneageOS, or Proton would make a difference, since typically custom ROMs only customize overlays, features, preferences, 3rd party SW, etc - they don't typically rewrite the kernel for example. But we'll find out. The modules I posted reflect LineageOS18.1 (should be android-msm-redbull-4.19-android11-qpr3 but I didn't verify; though this does work with a June 2021 build which is likely android-msm-redbull-4.19-android11-qpr2 or before) & Android12 (android-msm-redbull-4.19-android12). I don't have one for android-msm-redbull-4.19-android12-qpr1 yet, but there's a chance that's what you need. Recent bramble kernels:
android-msm-redbull-4.19-android11-qpr2
android-msm-redbull-4.19-android11-qpr3
android-msm-redbull-4.19-android12
android-msm-redbull-4.19-android12-qpr1
kevin71246 said:
Apologies for your results. I just updated the OP with an "Issues" section I'll update with issues reported, and any fixes if we discover any. I've only successfully tested this against LineageOS18.1, and was only hopeful it would work against other OS's. Just for kicks, since it's a pretty simple/quick process, you may want to try the ttl_magisk_L18.1 version. BTW that entire command is case-sensitive in case someone didn't know (Eg. Iptables... will not work; iptables... will).
Regarding the fix for your issue...I think Proton is based just on AOSP, and nothing to do with LineageOS. I wouldn't think that would matter but pointing. I would've made an Android12/LineageOS19.0 module but it isnt official yet for this device. I'm not sure how willing the Proton folks would be, but the next logical step would be to have them add the following options to their ProtonAOSP12 "redbull_defconfig" file (or equivalent), build it, and send me over the xt_HL.ko file. Then I'll add a magisk module for that for you to test.
Side note: there are 4 recent AOSP kernel versions for this device. So if there are compatibility restraints with versions, I'd guess we'd have a maximum of 4 to deal with, depending on what OS you have. I don't know for sure, but wouldn't think your ROM being AOSP, LIneageOS, or Proton would make a difference, since typically custom ROMs only customize overlays, features, preferences, 3rd party SW, etc - they don't typically rewrite the kernel for example. But we'll find out. The modules I posted reflect LineageOS18.1 (should be android-msm-redbull-4.19-android11-qpr3 but I didn't verify; though this does work with a June 2021 build which is likely android-msm-redbull-4.19-android11-qpr2 or before) & Android12 (android-msm-redbull-4.19-android12). I don't have one for android-msm-redbull-4.19-android12-qpr1 yet, but there's a chance that's what you need. Recent bramble kernels:
android-msm-redbull-4.19-android11-qpr2
android-msm-redbull-4.19-android11-qpr3
android-msm-redbull-4.19-android12
android-msm-redbull-4.19-android12-qpr1
Click to expand...
Click to collapse
Another note: it appears Proton does quite a bit of work with the kernel, mods/etc (eg. Features list here: https://forum.xda-developers.com/t/kernel-pixel-4a-5g-proton-kernel.4194685/ ). I'm not sure if you flashed their kernel (1 ROM says its not required), but if you did that may explain the incompatibility - but I'm just guessing.
kevin71246 said:
Another note: it appears Proton does quite a bit of work with the kernel, mods/etc (eg. Features list here: https://forum.xda-developers.com/t/kernel-pixel-4a-5g-proton-kernel.4194685/ ). I'm not sure if you flashed their kernel (1 ROM says its not required), but if you did that may explain the incompatibility - but I'm just guessing.
Click to expand...
Click to collapse
Not at all, I am just using the Proton without the Proton Kernal (this is optional). If not mistaken, the Dev mentioned somewhere that by default, the kernel is same as stock
creezalird said:
Not at all, I am just using the Proton without the Proton Kernal (this is optional). If not mistaken, the Dev mentioned somewhere that by default, the kernel is same as stock
Click to expand...
Click to collapse
Mind going into your phone settings & post your kernel version? Thx
kevin71246 said:
Mind going into your phone settings & post your kernel version? Thx
Click to expand...
Click to collapse
sure, here you go
kevin71246 said:
Obviously we all know this, but I'll say it anyway: I bear no responsibility for your device!
Background:
Initially I recompiled the kernel, but thanks to @fddm I was able to get this into a Magisk module. This is a take-off from https://forum.xda-developers.com/t/...-tether-lineageos-18-1.4295601/#post-86183959 Feel free to read that (minimal reading) for additional details.
What is this?
This Magisk mod adds the required iptables kernel module for TTL/Tether/unmetering for using your phone as a hotspot. I have Tmobile & with my plan, when I connect any device to the phone it is extremely throttled to around 0.5Mbps. With this mod and the settings below, you can get around that limitation. I go from 0.5Mbps=>80+Mbps with this mod. Root is required (look at above thread for details on that if needed).
Compatibility:
ROMs: At this point I can't indicate what ROMs this will be compatible with, but it appears LineageOS18.1 works. I'm attaching that as well as a Android/AOSP12 version if anyone wants to test that. I'm also not sure if this is exclusive to the bramble/Pixel 4a5g device (If anyone knows what they're doing or wants to get ballsy, test & report your results!)
Carrier: I tested this against Tmobile. It depends on how your carrier throttles your hotspot connected devices; Tmobile uses the TTL to determine if its the phone vs a connected device. If your carrier uses that method this should work.
xt_HL.ko: This is the kernel module we're inserting to allow the "iptables ttl set" command. I tested the Android12 xt_HL.ko file on my LineageOS18.1 OS and it does NOT work. This tells me there is some type of versioning. OR: there's an issue with the A12 file...
InCompatibility: (as reported by users in the thread)
ProtonAOSP 12, pixel 4a5g
Steps:
Install Magisk module & read the output; Verify it installed successfully.
Download Termux app from playstore
Termux App:
su (Grant permissions)
iptables -t mangle -A POSTROUTING -j TTL --ttl-set 64 (should be no errors - if you have errors my kernel is not installed)
Test: Turn on phone Hotspot, connect any device, do a speed test comparing speed on phone should be similar to the connected device.
If any limitations/blocks: (Not sure but maybe http vs https is blocked sometimes)
Install VPN Hotspot app (Green key icon): "Wi-Fi hotspot" ON, wlan1 ON, DISABLE "Tethering HW Acceleration" in settings
Issues:
After running the iptables command you get this error: iptables v1.8.4 (legacy): unknown option "--ttl-set" Try 'iptables -h' or 'iptables --help' for more information. This means the module was not loaded (or isn't compatible. Assuming the correct version was selected, there's no fix. Likely your OS isn't compatible with this module. If anyone has additional troubleshooting to add feel free to chime in.
Technical Additional Info:
ttl_magisk_L18.1: This contains the xt_HL.ko file compiled from the lineage-18.1-20220102-nightly-bramble-signed repo
ttl_magisk_A12: This contains the xt_HL.ko file compiled from AOSP kernel: android-msm-redbull-4.19-android12
Click to expand...
Click to collapse
Hi, I followed the steps and I am able to get this to work after making the changes to iptables. I did notice that if I reboot the phone the changes are not persisting. Is there any way to fix this?
Thanks!
ankur414 said:
Hi, I followed the steps and I am able to get this to work after making the changes to iptables. I did notice that if I reboot the phone the changes are not persisting. Is there any way to fix this?
Thanks!
Click to expand...
Click to collapse
That is odd. That iptables command should be persistent across a reboot. The steps in the OP are all I did. In fact once I get it working it's hard to undo it! Like I'll delete the iptables rule, reboot, and usually I still get I throttled data. Eventually it'll break again after messing with it. No clue why. Hopefully sometime else can chime in. For reference, please post your OS, build, kernel, assume Pixel 4a5g?...
kevin71246 said:
That is odd. That iptables command should be persistent across a reboot. The steps in the OP are all I did. In fact once I get it working it's hard to undo it! Like I'll delete the iptables rule, reboot, and usually I still get I throttled data. Eventually it'll break again after messing with it. No clue why. Hopefully sometime else can chime in. For reference, please post your OS, build, kernel, assume Pixel 4a5g?...
Click to expand...
Click to collapse
Hi, thanks for the response. I am using a Pixel 4a 5G:
LineageOS 18.1-20220116
Build: lineage_bramble-userdebug 11 RQ3A.211001.00110038514
Kernel: 4.19.160-ge469934bead0
it seems to be working fine connecting with my pc.
Shared out from pc both hotspot and ICS to router connecting devices register no internet
connection from META (oculus) Quest 2 shows connected, Internet works but ( BEATSABER WILL NOT CONNECT TO MULTIPLAYER ) .
Sorry.
tested the ttl A12 zip
Termux commands in op gave no error.
also ran #ndc interface ipv6 wlan0 disable (accepted)
#ndc interface ipv6 rndis0 disable would not take
noT Mobile buy metropolitition
if anyone could give me some advice for my quest2 multiplayer problem would have much love ... its the main reason I run hotspot.
OnePlus 6T
Model: A6013
Android 12
Sec. patch 1/5/2022
ProtronExtended version
12.2.1
[ROM][12L][fajita] ProtonXtended (PXOSP) [AOSP]
ProtonXtended (PXOSP) Android 12 based ROM About Project PXOSP (Proton Xtended Open Source Project) is a fork based on ProtonAOSP to enhance the user experience with useful addition features. Screenshots Screenshots of the PXOSP Installation...
forum.xda-developers.com
Kernel ver.
4.9.227Syberia+-g44a024f66f1a
#1 Tue Jan 25 19:55:25 UTC 2022
Linux version 4.9.227Syberia+-g44a024f66f1a ([email protected]) (Android (7485623, based on r416183b1) clang version 12.0.7 (https://android.googlesource.com/toolchain/llvm-project c935d99d7cf2016289302412d708641d52d2f7ee)) #1 SMP PREEMPT Tue Jan 25 19:55:25 UTC 2022
Magisk custom update channel
24.1 (24100)
@topjohnwu
kevin71246 said:
That iptables command should be persistent across a reboot.
Click to expand...
Click to collapse
iptables rules shouldn't be persistent unless you add them via script at startup. If anything, the opposite should be true. I know some devices will refresh their firewall rules after some time, at which point you have to add it back.
everburn said:
it seems to be working fine connecting with my pc.
Shared out from pc both hotspot and ICS to router connecting devices register no internet
connection from META (oculus) Quest 2 shows connected, Internet works but ( BEATSABER WILL NOT CONNECT TO MULTIPLAYER ) .
Click to expand...
Click to collapse
I have a very hard time believing that module worked for your device, are you sure your kernel doesn't already have xt_HL builtin? That aside, were you having issues before trying this? It's probably a compatibility issue between your unnamed provider and the platforms you want to use. If that's the case, just try out a bunch of VPNs until you find one that works and use it with VPN Hotspot.
fddm said:
iptables rules shouldn't be persistent unless you add them via script at startup. If anything, the opposite should be true. I know some devices will refresh their firewall rules after some time, at which point you have to add it back.
I have a very hard time believing that module worked for your device, are you sure your kernel doesn't already have xt_HL builtin? That aside, were you having issues before trying this? It's probably a compatibility issue between your unnamed provider and the platforms you want to use. If that's the case, just try out a bunch of VPNs until you find one that works and use it with VPN Hotspot.
Click to expand...
Click to collapse
yes its running according to magisk log. I was previously on pixel exp. rom android 12 and termux cmd ended in error
that is why I switched for the kernel. and from what i can tell all data is used as talk text data.... as my wifi hotspot 15GB still shows i have only used 2GB (which i have). as far as my B.S. problem I think it has something to do with multiplayer servers. it works fine on wifey's hotspot same carrier LG stylo 6 stock..
everburn said:
yes its running according to magisk log. I was previously on pixel exp. rom android 12 and termux cmd ended in error
that is why I switched for the kernel. and from what i can tell all data is used as talk text data.... as my wifi hotspot 15GB still shows i have only used 2GB (which i have). as far as my B.S. problem I think it has something to do with multiplayer servers. it works fine on wifey's hotspot same carrier LG stylo 6 stock..
Click to expand...
Click to collapse
If I'm understanding - it works, but some devices connected have random results? TMobile, or any cell phone provider, are known for issues with VPN, etc, so that doesn't surprise me. And a total guess, but TMobile uses cgnat & ip6, so maybe that's causing issues as well - but not sure what provider u have.
kevin71246 said:
If I'm understanding - it works, but some devices connected have random results? TMobile, or any cell phone provider, are known for issues with VPN, etc, so that doesn't surprise me. And a total guess, but TMobile uses cgnat & ip6, so maybe that's causing issues as well - but not sure what provider u have.
Click to expand...
Click to collapse
thats probably it right there thanks
Have tried both on Pixel 4a 5G, Android 11 stock, rooted, RQ1C.210205.006
"unknown option --ttl-set" on both