Related
I have installed 4.4 rom latest, also using kernels suitable. My problem is that when I use VPN apps like OpenVPN connect, the connection speed gets very slow. I checked the logcat and find errors like:
exec() res=0, status=256 for /system/bin/iptables -t mangle -D st_mangle_POSTROUTING -p tcp -o tun0 --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
12-26 16:04:17.561: I/ip6tables(131): ip6tables: No chain/target/match by that name.
12-26 16:04:17.568: I/ip6tables(131): ip6tables terminated by exit(1)
I have searched this problem and found something useful (prevent spam):
android.googlesource.com/platform/system/netd/+/ca5b4e8%5E!/
it says:
SecondaryTableController: force the MSS to match pmtu on TCP SYN
Without this change, the VPN sets up a tun/ppp that needs a small
MTU, and during TCP SYN the MSS will end up matching the outgoing iface
MTU which is potentially too big.
This leads to connection flakiness. The wrong MSS is visible by
tcpdump-ing on the tun/ppp device.
With this change, the MSS now is correct.
It requires the kernel to be configured with
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
If kernel is not configured, it silently fails.
Click to expand...
Click to collapse
So I did look for a 4.4 kernel with this config enabled, I have checked config source of all current 4.4 kernels including franko,Mpokang,ASKP,Fancy, etc, but sadly I did not find one. I guess the reason is it's not included is because the code change happened not a long time ago, and for the same time the Galaxy Nexus kernel stood unupdated.
If kernel developers see this thread, thanks for all of your hard work and I wish you can check if the config is the reason of my problem. It will be better if I can post this thread in the development section, but it seems it's forbidden.
--Archie
You can try to get their attention by mentioning @nameofdeveloper in here to get them to notice the thread, or send a PM to them directly. I think XDA will not allow you to post in developer sections until 10 or more posts.
Have you tried a 4.4 kernel with that patch to see if it works?
Getting VPNs to work flawlessly has always been tricky issue with the custom kernels, hopefully yours can be addressed soon.
kaijura said:
You can try to get their attention by mentioning @nameofdeveloper in here to get them to notice the thread, or send a PM to them directly. I think XDA will not allow you to post in developer sections until 10 or more posts.
Have you tried a 4.4 kernel with that patch to see if it works?
Getting VPNs to work flawlessly has always been tricky issue with the custom kernels, hopefully yours can be addressed soon.
Click to expand...
Click to collapse
Thanks for your reply, since many custom kernels are based on the CM kernel, I think the most efficient way is to let CM team know this bug and fix it. Unfortunately CM team dose not accept a bug report of a nightly build version. Now I have resolved this issue by patching a kernel and building myself. I have built a patched kernel based on CM 11.0 source code and the VPN issue is gone. People have this issue may use this kernel(source from CM, patched by me)
[kernel_tuna_4.4.2_CM_MSS_fixed_Archie_20131227] pan.baidu.com/s/1bnzP2GJ (to prevent link spam)
longkas said:
Thanks for your reply, since many custom kernels are based on the CM kernel, I think the most efficient way is to let CM team know this bug and fix it. Unfortunately CM team dose not accept a bug report of a nightly build version. Now I have resolved this issue by patching a kernel and building myself. I have built a patched kernel based on CM 11.0 source code and the VPN issue is gone. People have this issue may use this kernel(source from CM, patched by me)
Click to expand...
Click to collapse
Good to know the build worked. You can submit your patch information to the Cyanogenmod JIRA: http://jira.cyanogenmod.org as a feature or improvement, but you want to get the attention of @dhacker29 since he currently maintains the Maguro kernel on Cyanogenmod. You can make a pull request on github or send him a PM here directly.
http://www.github.com/dhacker29
Has someone put this bug to jira.cyanogenmod.org ???
Ive the same bug with my htc phone...
Guyz can any 1 port nexus 5 lollipop update for galaxy grand duos i9082.
When will the new lollipop update come for our grand duos....???
Sent from my GT-I9082 using XDA Premium 4 mobile app
::thumbup:
Sent from my GT-I9082
pawitp said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo.
Device-specific source code for the Samsung Galaxy Grand Duos are available from https://github.com/pawitp/android_device_samsung_i9082 and https://github.com/pawitp/android_kernel_samsung_i9082.
Compatibilitiy Patches: https://gist.github.com/pawitp/cba169c87dba57eea8ef
(Please give credit if you use them in your ROM and if you fix something, please submit patches.)
Do not submit bug on CyanogenMod issue tracker
Downloads
ROM: http://goo.im/devs/pawitp/i9082_cm12.0
Google Apps: For now, find your own package
What works?
Wi-Fi
Bluetooth
RIL (Calls, SMS, Mobile Data)
Dual SIM
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera (photo)
Video playback
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
screenrecord does not work
FM Radio does not work
Sometimes wake up causes music stutter
Video recording does not work
.wav playback does not work (.mp3 works fine)
SELinux is in permissive mode
Wi-Fi HAL (i.e. Scanning MAC Address Randomization) not implemented
Sim Tool Kit (STK) not fully working
Video in YouTube app sometimes freeze
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Additionally, Dual SIM has the following limitations:
Both SIMs are always enabled (no way to disable one SIM)
"Receive incoming call while data is enabled" is always enabled
3G may not work properly if Dual SIM mode is enabled with only 1 SIM inserted
Installation
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install ClockworkMod recovery with SELinux support (.tar) (.zip by codekidX). Older CWM will result in a "status 7" error.
Reboot into recovery
Wipe data if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again.
Changelog
20141116: Initial release
FAQ
How do I enable/disable Dual SIM?
Dual SIM support is enabled by default. If you only use 1 SIM and wants to disable Dual SIM support, you can use the following instruction:
Enable:
Code:
su
setprop persist.radio.multisim.config dsds
Disable:
Code:
su
setprop persist.radio.multisim.config none
(Instruction screenshots)
Are delta updates available?
Delta updates are not yet available for CM 12.0.
Can you include Feature X into your ROM?
No. This ROM will have CyanogenMod's feature set.
Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
No. This is an AOSP ROM and cannot have TouchWiz applications.
Can you include call recording?
No. CyanogenMod does not include call recording to avoid potential legal issues.
Can you add Feature X to the stock ROM?
No. I don't work on stock ROMs.
What kernel does this ROM use?
A slightly modified version of the stock kernel, the source code is linked above.
I've heard that Broadcom doesn't release source, how can you make this ROM?
Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Can I use your ROM as a base?
http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Will you make this official CM?
Due to the amount of work and commitment involved, I am not planning to make an official CM port.
Can contacts be saved to phone/SIM?
No. It is not supported in AOSP-based ROMs.
Can I send files over Wi-Fi Direct?
Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Can I mirror your ROM?
You're free to, but I will not list it in this post.
Is overclock (OC) available?
1.3 GHz OC is available in Settings -> Performance -> Processor (enable developer mode first). Higher frequencies are not enabled since benchmark does not show additional benefit.
Will feature X from a previous version of CM be implemented?
I don't know, probably will be, eventually. I don't really involve myself in the feature-set side of CM.
Will you add OTA support?
No.
I cannot add APNs
Make sure you set the correct MCC/MNC code, the APN will not appear otherwise. Also make sure to use menu -> save (back button means discard).
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model (I9082 or I9082L):
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
Dual SIM:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- My real-life friend for letting me borrow his phone to work on this
- RampantRhino for donating a phone to help me continue with this project
Click to expand...
Click to collapse
See this
Press thanks if I helped
Sent from my GT-I9082 using XDA Premium 4 mobile app
Legendary PAWITP has given us a great cm12 ROM
I find it almost 100% similar to the official lollipop
Great ROM...
I cannot thank "pawitp" enough....
Grand users are lucky to have such great developers like pawitp, xenon, and others...
Has anyone managed to get IPTV Multicast video streams to playback on the g pad v500? I am referring to the kind of IPTV multicast that several telcos provide, see e.g. http://grinch.itg-em.de/entertain/faq/allgemein/multicastadressliste/
When I try to open such a stream in VLC on my gpad, nothing happens. No error message, playback just indicates it's stopped. On the galaxy s5 it works without problems.
I did some google research and it seems that the kernel needs to be compiled with a multicast switch/flag. So I tried several firmwares; I came from v50020d and I tried the 5.0 CM nightly build and LiquidSmooth, but the problem remains the same, so I guess it is no use to randomly try other builds (by the way, it took me ages to get TWRP running, but now it works without a problem )
Any suggestions?
Take a look at this config. I think it blocks multicast by default.
http://forum.xda-developers.com/showthread.php?p=57231715
thanks for the hint.
indeed my system/firmware/wlan/prima/WCNSS_qcom_cfg.ini had
Code:
# Flags to filter Mcast and Bcast RX packets.
# Value 0: No filtering, 1: Filter all Multicast.
# 2: Filter all Broadcast. 3: Filter all Mcast and Bcast
McastBcastFilter=3
and the file config suggested there has McastBcastFilter=0.
However it still doesn't work; VLC now says "No media found" (instead of no message) - are there further configs that may block multicast traffic?
following https://code.google.com/p/android/issues/detail?id=51195, the option CONFIG_IP_MULTICAST=y needs to be set when building the kernel. Indeed /proc/net/igmp does not exist.
Perhaps one of the available custom kernels in addition to changes in the WiFi config would work. The easiest solution would probably be to use CM and get ckret or Rick_Roll to add the multicast module support to their kernels or build the cm kernel yourself.
With http://forum.xda-developers.com/lg-g-pad-83/development/rom-android-5-0-lollipop-lrx21m-t2941207 it works!
I prefer the CM GUI though, so I will try to get it in there.
thanks again.
solution
Thanks to rick.roll, I've got a solution now.
The working configuration is:
* cm-12-20150106-NIGHTLY-v500.zip - http://get.cm/get/mkB
* RedKernel r014 with Multicast support - https://www.androidfilehost.com/?fid=95887005526789182
I guess it would work on any CM12 build with this kernel.
This is the Official Jaguar rom for Honami, which is based on AOSP with some flavors from Slim and Dirtyunicorn. The main difference from other roms is the emphasis on security and multiple features. With that in mind , let's see what Jaguar has to offer:
1. Hardened Kernel, modified M5 built with UBERTC 6.0; hardened rom built with HYPERTOOL 5.4
2. CPU overclocked to 2572 and GPU to 600
3. All ciphers enabled in kernel instead of just a few
4. Hardened/Fortified Bionic and Libs
5. Fstack protection strong to resist buffer overflows
6. Many System apps and processes are made read-only, to reduce elevation of privilege
7. Selinux replaced with Tomoyo and Yam security
8. Disc encryption, keymaster to 256 bit AES instead of 128
9. Latest TWRP with working brightness and ability to decrypt Data
10. Random number generation mixed hardware/software, as recommended by Linus Torwalds
11. Options to randomize host on every boot
12. Option to have a separate password for lock screen and boot
13. Qualcomm's Time Services disabled due to leaking on early boot. Instead, Timekeep is ported from Nougat (time set locally without Internet or GSM signal)
14. WIFI Background Scanning disabled to prevent leaking
15. Internet disabled for both WIFI and Data until Afwall is set and activiated (Afwall included in download, install as regular app)
16. The phone is VOLTE ready and you have all network options available in Cell menu (not just LTE/WCDMA/GSM)
17. GRsecurity features, such as Sidechannel implemented
18. Some Pax Security Features
19. Option to deny USB connection: denied always; denied when locked; and allowed always
20. Hardened webview with Google and other "interesting" IPs removed
21. Prevention of bruteforcing screen pin: the phone will reboot upon 3 unsuccessful attempts
22. Perfect_Event_Paranoid ported from Grsecurity: now third party apps can't use other apps including system to elevate privileges
23. Camera hardware button works to focus, take pictures and start video recording
24. Option to disable writing to Tombstones (a lot of private info is dumped there if there is a crash)
25. Option to disable continuing writing of logcat
26. Option to disable device cameras: back; front, both or none
27. Always latest Google Security Patches
28. Always latest Code Aurora Security Patches
29. Changes ported directly from Google Android Gerrit, so most of those in MM and even N are in this rom
30. About 80% of kernel changes are ported into Jaguar kernel from 3.10 and 3.18 (not Sony AOSP 3.10, but Linux/Google/Code Aurora one)
31. Rom is odexed to significantly increase boot speed (under 30 seconds) and application start
32. Many more security features ported from Linux and Copperhead OS
33. Sony Timekeep
34. DNS Encryption, as well as the choice of multiple DNS providers
Other features include: Stereo Sound; Layers Theme Engine; Native Call Recording with interface integrated in Dialer with no restrictions; Privacy Guard; Native Wakelock Blocker; Native Black List; Global Menu; Slim Recents; Traffic Indicators; Advanced Reboot; Slim Pie; CPU Info on Screen; Ram Bar in Recents; Open source Superuser included and integrated in Settings; True Offline Charging with Screen Off; Kernel Adiutor included (unzip and install as a normal app) and integrated in Settings; FM Radio and Recording plus more
Things users need to know to have smooth experience:. These are not bugs, but rather an explanation of some features
1. If you want to do data encryption, keep in mind that unlike Android, Jaguar uses 256 bit encryption. If you were encrypted on other roms, you won't be able to decrypt. So, wipe encryption and then re-encrypt on Jaguar. Also, keep in mind that if you ever did factory reset on official TWRP 3+ for honami, your data partition is screwed and have to be resized to enable encryption. This has nothing to do with the rom, but rather with the official TWRP itself. Fastboot my unofficial TWRP 3.0.2, which, by the way has working brightness, as well as ability to decrypt and mount data
2. Jaguar contains a script running on early boot, which cuts the internet access to both WIFI and Data until Afwall is running. This is done to prevent leaking, as well as having all your internet traffic routed through some interesting number of servers, including this IP: 26.147.196.22. So, install Afwall and activate it, otherwise, no Internet for you
3. If your system language is different from English and you want to make changes in Phone/Cell Network settings, switch to English first, make the changes and then return to your language. The changes you made will hold. If you try to make the changes in your language, you will have com.android.phone crash. Localization takes time and is virtually impossible to implement in Jaguar, which is a one-person-rom
4. Qcom Time Services daemon is disabled to prevent leaking. That means that you have to set Time/Zone to automatic to get it directly from your carrier. Otherwise, you won't have the correct time on reboot. Forget it. Sony TimeKeep is now setting the correct time on reboot and without the Internet, even in Airplane mode
5. Dnscrypt: in Settings/Security you have a new feature allowing the use of different dns providers (all encrypted), instead of your provider's default one. In Afwall, you must allow access to 'apps running as root'. Otherwise, no internet
6. Supersu is no longer bundled with the rom. Activate Developer settings and enable builtin root there. Open source Superuser is now included. Activate root choices within the app
7. If you use Gapps, they must be flashed right after the rom and before reboot. If you reboot even once, you will have multiple Gapps f/c due to incorrect permissions
Download: All updates and change logs are in Post #3 now
Instructions:
YOU MUST HAVE LATEST STOCK LP 5.1.1 FLASHED ONCE ON YOUR DEVICE. Otherwise, you may experience hardware (mainly Gps problems). If after the official LP 5.1.1, you downgraded to any other official stock version, you must reflash stock LP 5.1.1
1. Have TWRP (fastboot my unofficial version), unlocked bootloader and root.
2. In TWRP, wipe data/factory reset, then wipe System/Data/Cache/Dalvik
3. Flash the rom
4. If you use xposed, flash the latest installer. Xposed no longer works and will never work with roms that incorporate Nougat security features. Xposed used a security hole that was closed by Google. Bye bye Xposed...
5. If you want Gapps, flash them before any reboot. Otherwise, you will have multiple problems due to permissions.
6. Reboot, install Afwall and Kernel Adiutor as normal apps; activate Afwall to have Internet
7. Enjoy the rom, say thank you, donate or do both
Warning: If your device and/or anyone in the immediate vicinity dies, don't blame me: it is all China and Russia's fault. :laugh:
Credit: CM, AOSP, Slimroms, DU, Copperhead OS, Myself5 (kernel)
UPDATED KERNEL SOURCE: https://forum.xda-developers.com/devdb/project/dl/?id=23107 . Don't flash. This is not kernel, but rather sources to compile kernel
Kernel Sources: https://github.com/AOSP-Argon/android_kernel_sony_msm8974
XDA:DevDB Information
Jaguar Rom , ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP, Slimroms, DU
Version Information
Status: Stable
Current Stable Version: 6.0
Stable Release Date: 2016-02-09
Created 2015-08-29
Last Updated 2017-02-09
Update on Further developemnt
February 16. I broke my Z1 screen again and I am not in the mood for after market screens. And I am sick and tired of Sony crappy treatment of development community.
I am now looking at Lenovo Zuk Z2 or Z2 pro. Both excellent phones with the latest CPU and made out of metal and glass by Motorola which they bought from Google a couple of years ago. Zuk is friendly to developers and their blobs don't dumb down camera and they don't seek to "unify" bugs for all their devices. I no longer wish to support a fat bastard corporation that can't make a good phone, but thinks that just by putting their logo on the phone would make it worth $700.
RE Jaguar. I will continue to maintain Jaguar mainly with security patches... for a while, but my main work will be concentrated on Zuk. There is a lot of work to be done cleaning Android N and implementing security and other features from Jaguar...
This is where you get the latest update
March 21. New release:
1. March Security patches
2. New Superuser
3. Updated kernel
Download: https://forum.xda-developers.com/devdb/project/dl/?id=23814
____________________________________________________________________________
February 9. New release:
1. February Security patches
2. DNS_Crypt (in settings/security)
3. Seccomp (secure computing implemented in kernel)
4. Open Source Superuser integrated
5. Silent SMS notification enabled
6. 1440p profile in camcorder added
If you enable Dnscrypt and you use Afwall, allow internet to apps running as root...
If you prefer closed source Supersu, just flash the zip...
Download: https://forum.xda-developers.com/devdb/project/dl/?id=23069
____________________________________________________
January 20. Good News! Time service completely fixed. Qcom's crappy and creepy service taken out and replaced with Sony open source TimeKeep ported from MM/N. No connection to the internet needed. Everything is done locally on the device. TWRP has also been modified to set the correct time on boot.
The wayTimeKeep works is that before the shut down, it saves the properly set time and on reboot restores it (after the down time calculation). TWRP also reads that value on boot. For those who have encrypted data: the correct time in TWRP will be set after you enter boot password and data is decrypted and mounted.
Download Rom: https://forum.xda-developers.com/devdb/project/dl/?id=22743
Download TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=22742
___________________________________________________________________________________
January 5. New release with January security patches and more. Also back is qcom time domain.
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22428
You may flash dirty if on a previous release. Otherwise, fresh install (read directions)
P.S. This build included an experimental kernel. So, if you have any problems, flash the stable version in fastboot (unzip the file first): https://forum.xda-developers.com/attachment.php?attachmentid=3995799&d=1483894575
__________________________________________________________________
December 13. Stereo Sound is here. This is based on Dontbelive mode, but it is just clean stereo sound (ear piece and loud speaker), no bass or any other ridiculous "improvements" that do nothing, but distort. And as a result, just a clear stereo sound for games, videos, songs etc...
Just flash the zip in TWRP and reboot. Remember, this is not a rom, but a stereo-sound mode to flash on top of Jaguar...
After installing this, you have to make one call to recalibrate the sound. Otherwise, you may have distortions in the ear piece....
Download: http://forum.xda-developers.com/devdb/project/dl/?id=22080
Credit to Dontbelive...
___________________________________________________________________________________
December 9: New release to include:
1. December Security Patches
2. Signature spoofing feature (cherry-picked from Omnirom)
3. USSD should work now
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21987
__________________________________________________________________________________
November 16. Kernel with DirtyCow fix. Download and flash in recovery. This is not for fastboot.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21563
___________________________________________________________________
November 10. Rom updated to include November Security Patches+. I have also removed Supersu, as the rom has a built-in root manager. However, if anyone wants to install Supersu, you can easily flash it in recovery
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21427
________________________________________________________________________________
October 10. Kernel-no-overclock.
Unzip and flash in fastboot.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=20848
_________________________________________________________________________________
October 9. Updated Kernel, which includes:
1. Updated higher frequency voltage
2. Improved Prima/Wifi driver
Your CPU variant may require voltage adjustment in Kernel Adiutor for new frequencies. Try to give a load for CPU and if you have freezing or random reboots (which you shouldn't), adjust higher 3 by +10/20. This latest kernel achieves 40000+ antutu score with Ondemandplus with temperature rising to about 58 at the highest load...
Note that some CPU/GPU variants just won't go to 2803 for CPU or 600 for GPU
Instructions: Unzip boot.img and flash in fastboot: fastboot flash boot boot.img or use various apps to install without fastboot
Download: http://forum.xda-developers.com/devdb/project/dl/?id=20838
__________________________________________________________________________________
October 8. Rotating Home Screen: if you want your home screen rotate like on a tablet, flash the attached file in recovery and reboot. So, when you set display to rotate, home screen will be included
__________________________________________________________________________________
October 5. New release:
1. Kernel overclocked to 2803: experimental, I have used it for 10 days without problems
2. October security patches from Google and Code Aurora
3. Over 80 commits from Google Master Gerrit which included changes to bionic, art, frameworks and system
4. Updated Afwall
5. Maybe more
This rom is now about 40% Nougat. One of the side effects: Xposed framework no longer works, but getting rid of it and instead using Privacy Guard is almost as good. Don't forget, Xposed is an exploit, which provides hooks for good and bad things.
Rom Download: http://forum.xda-developers.com/devdb/project/dl/?id=20788
Afwall/Kernel Adiutor Download: http://forum.xda-developers.com/devdb/project/dl/?id=20787
You can flash dirty if on a previous release
_________________________________________________________________________________
September 8. Rom updated to include:
1. September Google security patches
2. Latest Code Aurora patches https://www.codeaurora.org/projects/security-advisories
3. MPdecision is permanently disabled due to interfering with other hotplug and CPU frequencies. Default is MSMdecision, but you can pick several others in Kernel Adiutor
4. CPU overclock and underclock removed: no benefit whatsoever
5. More hardening ported from 3.18, 4.1 and 4.4 kernels: https://android-review.googlesource.com/#/q/hardened,25 You won't find those in any rom custom or stock. This is from 3.18-4.4 kernels and it has nothing to do with Sony AOSP. That's why it works...
6. About 70-80 commits from Android Master Branch. Folks. This is no longer a lollipop rom
7. PXN security feature implemented, which takes advantage of special instructions on ARMv7 to prevent unprivileged execution. See here: https://android-review.googlesource.com/#/c/265892/
8. Further integration of VOLTE
9. Kernel Adiutor: author has decided to go with Mobile Ads/Adview/Adbanner. So these were removed...
10. Camera: improvements to camera wrapper (missing entries), as well as some modifications in /frameworks/av/camera, so, you have a sharper picture. See photo attached, although, XDA reduces pictures... . This was taken with Open Camera. Not the crappy Sony Open Camera, but the fully open source one, with many features including several focusing modes: https://f-droid.org/repository/browse/?fdfilter=open+camera&fdid=net.sourceforge.opencamera. Tell me bootloader locked stock camera is better. It is not...
11. Maybe more...
WARNING: you need to do one thing after flashing the rom: flash the latest stock baseband. BASEBAND ONLY. If you don't, you will only have LTE: no H+/H/2G. This is a one-time procedure and is due to Volte implementation. You can either use FlashTool to flash stock baseband or a Partition Backup App (from Googleplay or elsewhere) to backup and restore your modems. With FlashTool, first flash the rom, then reboot, then flash the latest baseband. With Partition Backup, first, backup your modems, then flash the rom, then restore modems and reboot. You have been warned. I don't want to hear cries: where is my 3G!
Download Rom: http://forum.xda-developers.com/devdb/project/dl/?id=20287
Download Afwall/Kernel Adiutor: http://forum.xda-developers.com/devdb/project/dl/?id=20282
You may flash dirty if on a previous release. Otherwise, clean flash...
1st! Thanks @optimumpro
Sent from my Xperia Z1 using Tapatalk
Downloaded and flashed so far great ROM but 1st issue I noticed I believe data is turned off at ROM start up so setting up Google etc... Is hard without WiFi other than that ultra smooth and really fast great work. @optimumpro I don't suppose you know how to get OK Google everywhere to work do you on all ROMs I have tried its never there
Hope to see FAB in recents in next build if possible though as the remove recents is kinda small and the hover notifications kind of cover over it
Sent from my Xperia Z1 using Tapatalk
Is there still a bug when you turn Bluetooth off and on and it changes the Bluetooth MAC address? (as well as the same WiFi MAC for every device)
danny19901 said:
Downloaded and flashed so far great ROM but 1st issue I noticed I believe data is turned off at ROM start up so setting up Google etc... Is hard without WiFi other than that ultra smooth and really fast great work. @optimumpro I don't suppose you know how to get OK Google everywhere to work do you on all ROMs I have tried its never there
Hope to see FAB in recents in next build if possible though as the remove recents is kinda small and the hover notifications kind of cover over it
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Data is off by default on first boot only to prevent the phone from connecting before you set it up (firewall etc.). Just turn it on and it will stay on despite reboots. Ok Google? Oh, that's too complicated for me.
matcho13579 said:
Is there still a bug when you turn Bluetooth off and on and it changes the Bluetooth MAC address? (as well as the same WiFi MAC for every device)
Click to expand...
Click to collapse
Not sure about bluetooth, but wifi mac is fine.
The ROM is one of the best i have tested..
There are 2 ways to get superuser: Developer option and supersu
jos_031 said:
The ROM is one of the best i have tested..
Click to expand...
Click to collapse
Totally agree with you.
I was also able to set my WiFi MAC without any problems.
The layers thing is also a very good alternative.
My Z1 is now really hot, I hope it will calm down after some days of use.
@optimumpro: Keep on with this good mix [emoji3]
schickel said:
Totally agree with you.
I was also able to set my WiFi MAC without any problems.
The layers thing is also a very good alternative.
My Z1 is now really hot, I hope it will calm down after some days of use.
@optimumpro: Keep on with this good mix [emoji3]
Click to expand...
Click to collapse
Tweak cpu voltages and governors. You should not have any overheating. Also, don't put any stress on cpu while the phone is charging. Phones are not designed to be used while on a charger: they only get current from the battery, unlike laptops, so, when you are on charger and using the phone, you stress the battery and cpu.
Does everything work with this rom? modem, camera and recharge while the phone is off?
dejawho said:
Does everything work with this rom? modem, camera and recharge while the phone is off?
Click to expand...
Click to collapse
Yes everything seems to be working great modem, camera etc...
Prime Red Dark Layers Theme is really nice I tried Scarlett but has Playstore changelog no text bug
Oh I have xposed installed also for flat style status bar, always correct, force expanded notifications this ROM is by far the best ultra quick
1 big question just noticed how come colour picker tint overlay is still in the dialer ? I thought this was removed in 5.1.1 ? As you can see with the red overlay (This is my very Old Number)
Sent from my Z1 using Tapatalk
I noticed that when I get a call, the phone has to switch back to GSM signal. If I don't have GSM listed in the preferred network types, I could not be reached on the phone - goes straight into a busy tone... Anybody else experienced this?
caki25 said:
I noticed that when I get a call, the phone has to switch back to GSM signal. If I don't have GSM listed in the preferred network types, I could not be reached on the phone - goes straight into a busy tone... Anybody else experienced this?
Click to expand...
Click to collapse
This is a normal behavior. Your phone is a GSM phone. Now, if your carrier provides voice over 3g, then your phone will swith to 3g/H+ from LTE. If you have Volte (voice over LTE), it will stay on LTE. In most of the world there is no Volte yet, so, if your data is LTE, then when you get a call, the phone switches to 3g/H+. If your carrier does not provide calls over 3g (2g only) and you are on WCDMA/LTE, then you won't receive any calls. In that case you should switch to GSM/WCDMA/LTE.
Again, as I have already said, that's the behavior on all roms. Other roms just don't have the options in cell menu that this rom has and changing networks in phone test menue does not stick on reboot. So, you have to know what you are doing...
optimumpro said:
This is a normal behavior. Your phone is a GSM phone. Now, if your carrier provides voice over 3g, then your phone will swith to 3g/H+ from LTE. If you have Volte (voice over LTE), it will stay on LTE. In most of the world there is no Volte yet, so, if your data is LTE, then when you get a call, the phone switches to 3g/H+. If your carrier does not provide calls over 3g (2g only) and you are on WCDMA/LTE, then you won't receive any calls. In that case you should switch to GSM/WCDMA/LTE.
Click to expand...
Click to collapse
I guess I managed to jump too hastily again ... it does make sense of course, and I should have noticed that before. The default setting threw me off I guess, since that was without GSM and when my boss tried to reach me, he just got a busy tone anyhow, thank you so much for the explanation and this wonderful ROM. I just can't move away from Layers anymore
caki25 said:
I guess I managed to jump too hastily again ... it does make sense of course, and I should have noticed that before. The default setting threw me off I guess, since that was without GSM and when my boss tried to reach me, he just got a busy tone anyhow, thank you so much for the explanation and this wonderful ROM. I just can't move away from Layers anymore
Click to expand...
Click to collapse
"Default setting". That's my fault, I shouldn't have assumed that everyone has voice over 3g. I will change this in the next release, but your selection GSM/WCDMA/LTE should stick after reboot.
Thanks for a great ROM! Will this be your main ROM from now on?
Do you recommend to use the kernel defaults or do you have other settings for voltage, governor etc. that you recommend?
This is a really good ROM! Good job @optimumpro! :good:
The feature I really miss from your unofficial DU ROM is the ability to block System Wakelocks. I have serious wakelocks on my phone due to Play services and I don't like Xposed too much (compromises security and drains battery).
Could you add this feature? Thanks!
OK starting to get Random Reboots but I think it's my kernel settings as I had no issues at all except when screen waked up wouldn't let me unlock for a little while so I altered few things fixed that problem now I get random reboots
Sent from my Z1 using Tapatalk
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