I’m hoping you amazing devs can tell me this idea is achievable! I’m told xposed won’t work on my h8314 device running android 8.1so I got hope that a fake WiFi module could be implemented for magisk systemless!!!
Related
Hello all,
I wish to sneak past my phone networks (Three) tether block, so i can use my iPad on the bus via my mobile.
Has anyone got Wifi Tether by Trev Mod to work on Android 4.4? i seem to be running into some issues, and it won't show me an error log either.
If you have it working, or think you know how, could you please let me (and therefore others) know what settings you have used to get yours working?
I am working on Google Play Edition 4.4 (Android Revolution 5.2HD) rooted and S-OFF.
Thanks in advance!
Gary.
captainbirdseye86 said:
Hello all,
I wish to sneak past my phone networks (Three) tether block, so i can use my iPad on the bus via my mobile.
Has anyone got Wifi Tether by Trev Mod to work on Android 4.4? i seem to be running into some issues, and it won't show me an error log either.
If you have it working, or think you know how, could you please let me (and therefore others) know what settings you have used to get yours working?
I am working on Google Play Edition 4.4 (Android Revolution 5.2HD) rooted and S-OFF.
Thanks in advance!
Gary.
Click to expand...
Click to collapse
There is an experimental version of Trev Mod 3.4 that works.
I can't post a link but a search will bring it up.
Tether was working fine on Nougat, after adjusting Windows with TTL, a changed user-agent, etc., and then in Android adding the "dun" parameter to my APN, but with any Oreo or Pie ROM, it gets incredibly slow, as if I do not have "dun" in my APN, even when using ROMs that allow "dun" in APN.
I'd really like to upgrade from Nougat, but don't want to give up tether.
Has anyone else faced this issue and prevailed?
EDIT:
I flashed OOS Oreo, tried what settings I could with no good results, then flashed 4.5.1 firmware and modem into it to see if older firmware was the solution, tried what settings I could to no avail.
Back on Nougat now, which does the job just fine.
Alas however, I may never be able to buy a new phone, unless Nougat can be installed onto it.
You're certainly not the only one. Tethering support is getting harder as carriers find ways of making it more restricted. There are ROMs and Devs that have worked on it with mixed results. It's possible with enough leg work you might get it working on a particular ROM, if you can get the dev to work with you on it. Otherwise it's luck of the draw whether you can find a ROM that will work in your particular case.
Telephony is getting complicated and there are more people concerned with VoLTE and the like. Look what a mess that still is on custom ROMs.
Does anyone know of any ROMs where this is actively being fixed? That is, one can tether without degradation, as one used to be able to do in Nougat? Tethering works, it's just horribly slow.
pbergonzi said:
Does anyone know of any ROMs where this is actively being fixed? That is, one can tether without degradation, as one used to be able to do in Nougat? Tethering works, it's just horribly slow.
Click to expand...
Click to collapse
NLOS is your best bet. If it's not working already the dev is willing to work with users to resolve issues.
Here's an example of Tethering restrictions getting worse, with Google leading the charge:
https://www.reddit.com/r/Android/comments/9r6r13/tether_dun_required_no_longer_works_on_pixel_3_xl/
I'm surprised Google don't get whiplash in their haste to bow to pressure from US Carriers.
Dirk said:
NLOS is your best bet. If it's not working already the dev is willing to work with users to resolve issues.
Here's an example of Tethering restrictions getting worse, with Google leading the charge:
https://www.reddit.com/r/Android/comments/9r6r13/tether_dun_required_no_longer_works_on_pixel_3_xl/
I'm surprised Google don't get whiplash in their haste to bow to pressure from US Carriers.
Click to expand...
Click to collapse
Thank you @Dirk, and agreed--I'm surprised google doesn't get backlash--maybe not enough people tether?
Also surprised that more devs didn't just immediately address that--maybe not enough devs tether?
I may try NLOS, or the Magisk module--it might work.
Does anyone using NLOS know if tether works properly? I will ask in that thread also.
I have a note 5 n920T and the problem that I have is that most of the oreo or pie custom rom dont exist for this particular model. if a rom boots on it usually call audio is an issue. So, I want to modify existing kernel to work with n920T. I have been unable to find any guide related to "modify kernel for another variant of android device". Can anyone point me to any related guide or tutorial or video. I am a newbie to development and watched a few videos related to custom rom development but it doesn't help me as I want to modify kernel belonging to say n920C to work with n920T. I shall be grateful for your guidance. I have programming knowledge including c and c++
The big issue is with the speaker not working properly when ported to the T-Mobile variant. I believe it's a driver issue.
To be honest, none of the Oreo roms for our device are "good". They both are too unstable and have some major issues such as no/bad Camera (most apps will just crash), Bluetooth doesn't work, etc.
I've been using Oreo lately and just today alone I've had 10+ freezes/reboots. Unable to use bluetooth. Many apps using the camera just crash.
I think it's time to upgrade from our device as there's just no third party support anymore. The LG G7 seems to be the best value high-end phone on ebay, however there's not much support via XDA at this time.
Hi friends,
I've been searching for a magisk module to enable systemless-ly wifi IBSS adhoc support, but I have not been able to find it.
Does anybody know if it has been done?
Nowadays very few people cares about that, but it still would be a little victory against google.
Thanks in advance.
-- Sent from My Smartrefrigerator --
I read that the Pixel 4 and 4 XL have DisplayPort Alt Mode disabled on the Kernel and was wondering if anyone has made or started working on a custom Kernel that enables this feature? Is it even possible? Yeah I know I can use Chromecast or cast via WiFi but nothing beats a direct HDMI connection due to virtually no input lag etc.
Thanks.
marsfan89 said:
I read that the Pixel 4 and 4 XL have DisplayPort Alt Mode disabled on the Kernel and was wondering if anyone has made or started working on a custom Kernel that enables this feature? Is it even possible? Yeah I know I can use Chromecast or cast via WiFi but nothing beats a direct HDMI connection due to virtually no input lag etc. Thanks.
Click to expand...
Click to collapse
Based on no replies in over 65 views I would say no, but you may have better luck posting this over in the Kernels section. That, and maybe linking to the piece you found on this disabled feature waiting to be unlocked.
Still no progress on this? This would be the only reason for me to root.
shagggggggy said:
Still no progress on this? This would be the only reason for me to root.
Click to expand...
Click to collapse
No, unfortunately its still not possible. It is 100% hardware capable and only blocked at the Kernel level unlike Pixel 1-3. It's entirely possible to one day have it enabled but right now it doesn't seem to be a priority for any of the great Kernel devs we have here which is completely understandable. Although there are a bunch of us that would love to have this feature, its still a niche feature and so devs priorities are focused on the broader features for us. I read that Google MAY activate the display out over usb when stadia launched as that would make a lot of sense to tout as a feature but that hasn't happened yet and I'm not holding my breath.
Honestly, I'd be ecstatic just to have display out over WiFi (Miracast) enabled and there is a magisk module that enabled it on Pie for the Pixel 2-3, I loved having that when I was still on my Pixel 2 XL.
1dopewrx05 said:
No, unfortunately its still not possible. It is 100% hardware capable and only blocked at the Kernel level unlike Pixel 1-3. It's entirely possible to one day have it enabled but right now it doesn't seem to be a priority for any of the great Kernel devs we have here which is completely understandable. Although there are a bunch of us that would love to have this feature, its still a niche feature and so devs priorities are focused on the broader features for us. I read that Google MAY activate the display out over usb when stadia launched as that would make a lot of sense to tout as a feature but that hasn't happened yet and I'm not holding my breath.
Honestly, I'd be ecstatic just to have display out over WiFi (Miracast) enabled and there is a magisk module that enabled it on Pie for the Pixel 2-3, I loved having that when I was still on my Pixel 2 XL.
Click to expand...
Click to collapse
Where did you get the information that the pixel 4 xl (I have only tried it on the XL model since I don’t own the regular one) is actually capable of this?
I have seen none other source of information than the google commits disabling it in the kernel.
I enabled it at kernel level and all I got was a freeze when the phone booted.
Freak07 said:
Where did you get the information that the pixel 4 xl (I have only tried it on the XL model since I don’t own the regular one) is actually capable of this?
I have seen none other source of information than the google commits disabling it in the kernel.
I enabled it at kernel level and all I got was a freeze when the phone booted.
Click to expand...
Click to collapse
I've read it from multiple sources. I was seeing it quite a bit shortly after the phone was released and haven't seen anything about it recently but I've found an article for you showing the information I was talking about:
Via AndroidPolice:
"A commit has been found in the Android source code that disables DisplayPort over the USB Type-C port in the Pixel 4. The commit message simply reads, "Disable DP function."
The link to the whole article is:
"Pixel 4 has USB video output disabled in software" https://www.androidpolice.com/2019/11/03/pixel-4-has-usb-video-output-disabled-in-software/?amp
It's possible Google never finished it implementing the feature or maybe it didn't work fully before they had to release the phone. Is there any chance you want to PM me a copy of your kernel with it enabled? I have a couple of ideas on trying to get it fully enabled and working semi-reliably.
1dopewrx05 said:
I've read it from multiple sources. I was seeing it quite a bit shortly after the phone was released and haven't seen anything about it recently but I've found an article for you showing the information I was talking about:
Via AndroidPolice:
"A commit has been found in the Android source code that disables DisplayPort over the USB Type-C port in the Pixel 4. The commit message simply reads, "Disable DP function."
The link to the whole article is:
"Pixel 4 has USB video output disabled in software" https://www.androidpolice.com/2019/11/03/pixel-4-has-usb-video-output-disabled-in-software/?amp
It's possible Google never finished it implementing the feature or maybe it didn't work fully before they had to release the phone. Is there any chance you want to PM me a copy of your kernel with it enabled? I have a couple of ideas on trying to get it fully enabled and working semi-reliably.
Click to expand...
Click to collapse
Yes all these articles base back to the commit that actually disables the function in the display driver. There´s no source of information that the Pixel 4 XL is actually capable of doing it. I think that´s why they disabled it.
So I don´t understand why you think the phone is 100% hardware capable of doing this, if you have no other information.
The phone freezes before the bootanimation comes up when the commit is reverted. So I´m not sure what you want to do that doesn´t involve recompiling the kernel with additional changes of your own.
I´d need to recompile the kernel as I did this already last year and the kernel is by now incompatible with the current firmware.
Freak07 said:
Yes all these articles base back to the commit that actually disables the function in the display driver. There´s no source of information that the Pixel 4 XL is actually capable of doing it. I think that´s why they disabled it.
So I don´t understand why you think the phone is 100% hardware capable of doing this, if you have no other information.
The phone freezes before the bootanimation comes up when the commit is reverted. So I´m not sure what you want to do that doesn´t involve recompiling the kernel with additional changes of your own.
I´d need to recompile the kernel as I did this already last year and the kernel is by now incompatible with the current firmware.
Click to expand...
Click to collapse
Yeah that wasn't the actual source I heard that from, like I said this was coming up on a year ago so I'll likely never find the sources.
Look, I mean you're most likely right about it not being a possibility, I know you have more knowledge of this stuff than I do so I'll take your word. I gave up on this a long time ago I was just replying to the OP with what I remembered. I have Chromecasts on my house TV's so it's not even relevant to me anymore.
What's your view on enabling display-out over WiFi? Outside of a Chromecast I mean. There was a magisk module for the Pixel 2 on Pie that re-enabled the Miracast support that Google disabled.