Database Develop

Unstable Wifi Connection on CM7

I'm having issues with the wifi connection having to be reset every few minutes when used. It seems to outright lose signal and can't even scan for networks until a reset. I'm on CM7 stable, using the latest OC kernel by Dalingrin. Anyone experiencing similar?

I have a similar issue.
From time to time (something like every 5 min), the connection seems ok (in the wifi pannel, it is stated as connected), but I can't access anything anymore by wifi. I have to disconnect and reconnect to my wifi router in order to make it work.
(I also use the last stable CM7... And apart from that, it's gorgeous ! )

So I'm indeed not alone in seeing this... interesting. Thanks for letting me know. As well, I agree, everything aside from the wifi works great and the tablet tweaks incorporated are nothing short of brilliant.

Mine is table with CM7 final and with Philmod 6, both with the 03/31 and 04/04 kernels.

same here - cm7 stable + 4/4 OC
just loaded up nightly 39 + 4/14/11A OC to try that combo

politiclaw said:
I'm having issues with the wifi connection having to be reset every few minutes when used. It seems to outright lose signal and can't even scan for networks until a reset. I'm on CM7 stable, using the latest OC kernel by Dalingrin. Anyone experiencing similar?
Click to expand...
Click to collapse
Is this not the same issue all over about AES? Check your router, if it's WPA2 it's AES, if it's WPA it could be AES.
CM7 and some routers have issues when AES is used, try to disable it.

installed nightly 39 + oc 4/14a no wifi issues so far

khaytsus said:
Is this not the same issue all over about AES? Check your router, if it's WPA2 it's AES, if it's WPA it could be AES.
CM7 and some routers have issues when AES is used, try to disable it.
Click to expand...
Click to collapse
Tanks : that worked for me !

FixB said:
Tanks : that worked for me !
Click to expand...
Click to collapse
You mind Starring this issue on the Cyanogen tracker? Make sure you put all the relevant information as well as your Router HW and FW. Thanks!
http://code.google.com/p/cyanogenmod/issues/detail?id=3314

I posted my remarks in a comment on the tracker.
But I'm afraid I don't know what you meant by "my Router HW and FW" ?

FixB said:
I posted my remarks in a comment on the tracker.
But I'm afraid I don't know what you meant by "my Router HW and FW" ?
Click to expand...
Click to collapse
hardware and firmware, ie brand name and model number and the version of software it's running.

animatechnica said:
installed nightly 39 + oc 4/14a no wifi issues so far
Click to expand...
Click to collapse
Can anyone else comment on this? I might just go down this route, but I'm wondering if there a few more who did similar and are seeing no wifi issue as a result.
Also, I'm surprised to see a CM7 final release with a wifi issue such as this. If it indeed is related to encryption (AES vs TKIP), that's further perplexing. While I could go about changing the settings for my router, I can't go about doing so for many others - particularly in public. As well, if I'm to tether from my N1, I'm going to do it with a password, meaning I'm to do it with AES as there isn't much choice built in.
I hate to say this as I'm impressed with the amount of work that went into (and normally always goes into) CM, but I figure it has to be said. To be fair, I'm not sure how widespread this issue may be (does it affect the version of CM7 on tablets, only?) but I'm surprised it can exist in a version of cm7 considered stable.

politiclaw said:
Can anyone else comment on this? I might just go down this route, but I'm wondering if there a few more who did similar and are seeing no wifi issue as a result.
Also, I'm surprised to see a CM7 final release with a wifi issue such as this. If it indeed is related to encryption (AES vs TKIP), that's further perplexing. While I could go about changing the settings for my router, I can't go about doing so for many others - particularly in public. As well, if I'm to tether from my N1, I'm going to do it with a password, meaning I'm to do it with AES as there isn't much choice built in.
Click to expand...
Click to collapse
I'll try 39 etc but I suspect if they made changes in that regard they would have said to retest in that logged bug.
As far as I know, I've heard reports this happens on some phones as well, not just tablets, not just the NC.
And it doesn't affect most people, in fact I'll bet it affects a minority of folks. If it affected everyone I'm sure CM7 wouldn't have released that way of course.
And yeah I'm with you, I _do not_ want to use my N1 tethered with Open encryption, but not much I can do until this is fixed.

khaytsus said:
I'll try 39 etc but I suspect if they made changes in that regard they would have said to retest in that logged bug.
As far as I know, I've heard reports this happens on some phones as well, not just tablets, not just the NC.
And it doesn't affect most people, in fact I'll bet it affects a minority of folks. If it affected everyone I'm sure CM7 wouldn't have released that way of course.
And yeah I'm with you, I _do not_ want to use my N1 tethered with Open encryption, but not much I can do until this is fixed.
Click to expand...
Click to collapse
Did you try 39 out? This issue is MIGHTY annoying for me as it is kind of hard getting a company with 39 000 employees to back away from AES on the WLAN..
Also going away from AES at home means that I cannot have my access point using 300 Mbit 802.11N which also is a real bummer.
I found this at the CM7 bugtracker, look at the final few posts there is a wifi-driver to try out.
http://code.google.com/p/cyanogenmod/issues/detail?id=3314
Also noticed there was a complete guide about pushing the file here: http://forum.xda-developers.com/showpost.php?p=11974146&postcount=22

So if CM7 on my phone works fine on wifi, that means a NC should work the same more or less, correct?

henel321 said:
Did you try 39 out? This issue is MIGHTY annoying for me as it is kind of hard getting a company with 39 000 employees to back away from AES on the WLAN..
Also going away from AES at home means that I cannot have my access point using 300 Mbit 802.11N which also is a real bummer.
I found this at the CM7 bugtracker, look at the final few posts there is a wifi-driver to try out.
http://code.google.com/p/cyanogenmod/issues/detail?id=3314
Also noticed there was a complete guide about pushing the file here: http://forum.xda-developers.com/showpost.php?p=11974146&postcount=22
Click to expand...
Click to collapse
I guess you didn't notice who posted in that bug, and posted tiwlan_drv.ko in the bug?
Anywho, for me it did help my own and work AP's, but it's still broken tethering to my phone. So it seems better but not perfect, give it a try. Just make a copy of the original tiwlan_drv.ko and push the single file from that zip up in its place and reboot.

[Q] Sim contacts not available - critical bug on all custom kernels

Hi. This developer gathering sounds promising, I'm glad you guys help each-other for the benefit of users and leave personal fame aside.
But. GT-S5830i Spain (Moviestar) (S5830IBGLH4 S5830IXECLH2)
All your kernels have the Sim contacts not available critical bug. And I say critical as it's a basic function of a phone.
There is only one workaround, flashing the S5830CVJKL4 baseband (odin-izing just the phone=modem part is enough).
- then I've noticed that it greatly affects network reception with 30-70% less signal and no signal at all in some places.
- and it does not end here: antutu gpu scores goes down from the already low 290~ish to <190~ish.
- flashing the whole stock S5830CVJKL4 firmware with it's stock kernel has the same bad network reception and low antutu gpu scores.
So this workaround ends up doing more harm than good.
So now I have some questions for all of you, Rafael.Baugis, axyllum, hell-lock:
- what source do you use for building as Samsung provides no less than five S5830i sources: GT-S5830I_CHN_GB,
GT-S5830I_HK_GB, GT-S5830I_MEA, GT-S5830I_SEA_SWA_GB and GT-S5830i (I'm guessing none of them, but some C/M version).
In the light of these findings, can we say:
- "The kernel can be used on any rom." notice in all your releases is just wishful thinking and a bit misleading?
- there is yet another hardware difference (the modem) at least with this Moviestar version and should be blacklisted for now?
- there is something special with this S5830CVJKL4 firmware?
Thank you very much for your hard work.

It's not really critical if there's a workaround.
Also, simpler workaround: use your Google account to sync contacts.

WHAT THE ****!! That bug is on my kernel too??!!
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
I am using GT-S5830I_CHN_GB ...

hell_lock said:
That bug is on my kernel too?
Click to expand...
Click to collapse
Unfortunately.
I've checked the 3 custom kernels vs. 6 stock roms and 6 custom roms for the s5830i. This Moviestar version does not work, and from the number of complains all over the threads here, I'm guessing there are other models that simply do not work. These should be blacklisted so people don't get their hopes up and start flashing each time one of your kernel versions is updated (this needs input from all the people complaining, a forum search should be a good start, maybe I will do it later).
It's a shame that all that is missing is a suitable config/driver for the kernel - or could the problem be in the locking mechanism - the phone I'm testing is factory unlocked. The source code will clear this up I think, but who do we have to push to get the Moviestar source code as I understand they are bind to release it on request? I will look into this.
Bottom line, there is nothing wrong with your kernels other than not addressing this phone's issues.
GermainZ, there are people that can live with the google contacts sync, good luck with that, but for people that use many sim cards interchangeably it would be a problem (requiring multiple g-accounts, selective syncs). What would you say if your sdcard does not work and the answer you get from support is: "You can use the skydrive cloud instead". Easy to spot unsuitable tasks.

bobdynlan said:
Unfortunately.
I've checked the 3 custom kernels vs. 6 stock roms and 6 custom roms for the s5830i. This Moviestar version does not work, and from the number of complains all over the threads here, I'm guessing there are other models that simply do not work. These should be blacklisted so people don't get their hopes up and start flashing each time one of your kernel versions is updated (this needs input from all the people complaining, a forum search should be a good start, maybe I will do it later).
It's a shame that all that is missing is a suitable config/driver for the kernel - or could the problem be in the locking mechanism - the phone I'm testing is factory unlocked. The source code will clear this up I think, but who do we have to push to get the Moviestar source code as I understand they are bind to release it on request? I will look into this.
Bottom line, there is nothing wrong with your kernels other than not addressing this phone's issues.
GermainZ, there are people that can live with the google contacts sync, good luck with that, but for people that use many sim cards interchangeably it would be a problem (requiring multiple g-accounts, selective syncs). What would you say if your sdcard does not work and the answer you get from support is: "You can use the skydrive cloud instead". Easy to spot unsuitable tasks.
Click to expand...
Click to collapse
Do you know what file is missing? I may fix it.

bobdynlan said:
Hi. This developer gathering sounds promising, I'm glad you guys help each-other for the benefit of users and leave personal fame aside.
But. GT-S5830i Spain (Moviestar) (S5830IBGLH4 S5830IXECLH2)
All your kernels have the Sim contacts not available critical bug. And I say critical as it's a basic function of a phone.
There is only one workaround, flashing the S5830CVJKL4 baseband (odin-izing just the phone=modem part is enough).
- then I've noticed that it greatly affects network reception with 30-70% less signal and no signal at all in some places.
- and it does not end here: antutu gpu scores goes down from the already low 290~ish to <190~ish.
- flashing the whole stock S5830CVJKL4 firmware with it's stock kernel has the same bad network reception and low antutu gpu scores.
So this workaround ends up doing more harm than good.
So now I have some questions for all of you, Rafael.Baugis, axyllum, hell-lock:
- what source do you use for building as Samsung provides no less than five S5830i sources: GT-S5830I_CHN_GB,
GT-S5830I_HK_GB, GT-S5830I_MEA, GT-S5830I_SEA_SWA_GB and GT-S5830i (I'm guessing none of them, but some C/M version).
In the light of these findings, can we say:
- "The kernel can be used on any rom." notice in all your releases is just wishful thinking and a bit misleading?
- there is yet another hardware difference (the modem) at least with this Moviestar version and should be blacklisted for now?
- there is something special with this S5830CVJKL4 firmware?
Thank you very much for your hard work.
Click to expand...
Click to collapse
all kernel sources from samsung have this issues in SIM contacts!
the roms VJKL4 and rajrocks work SIM contacts!
but need to flash param.lfs in ODIN.

hell_lock said:
Do you know what file is missing? I may fix it.
Click to expand...
Click to collapse
That's the problem. I guess the Spain Moviestar version is based upon GT-S5830I_EUR_XX source (GT-S5830i_Opensource.zip). If that's so, there are quite a few differences between the european kernel and the chinese one you are using, confirming my theory that you can't build an universal kernel that works on all roms.
Differences are mostly incremental patches, touchscreen stuff, but also the suspected different locking stuff. modules\drivers\char\brcm\fuse_ril. I have zero inside knowlege of this stuff, but I interpret lines like #define BCM_CFG_SIM_LOCK_SUPPORTED as: CHN kernel enforces a check for SIM LOCK & other SIM related stuff while the EUR kernel does not.
Samsung will not help modders with this (network sim stuff) instead will direct you to mod the kernel from the right source. So the feasible solution is to build different kernels for phone models that have this issue - bye bye universal kernel (it never was universal, it just worked cause samsung did a great job; samsung would have not bothered to keep each platform with a coresponding kernel source).
Attached the actual different files (not a diff patch) between the CHN and EUR Samsung opensource.
Rafael.Baugis, did not know that all samsung sources are having this issue. Did you also test build from this EUR one?

bobdynlan said:
GermainZ, there are people that can live with the google contacts sync, good luck with that, but for people that use many sim cards interchangeably it would be a problem (requiring multiple g-accounts, selective syncs). What would you say if your sdcard does not work and the answer you get from support is: "You can use the skydrive cloud instead". Easy to spot unsuitable tasks.
Click to expand...
Click to collapse
I never said it shouldn't be fixed, I simply said it's not critical (considering not many people use more than a sim card; you're right I didn't think of all possible scenarios, I never thought of yours).
And I'm most certainly not the support.
Also, regarding the EUR kernel, it's outdated. I could try compiling the stock kernel from it if you want.

Is sim working on any source based kernel??
Sent from my GT-S5360 using XDA

[MOD][MAY30] Enable WiFi on LDZ22D

I've managed to enable WiFi on lenok by coping several files from bass and kernel with the wlan driver enabled, courtesy of intersectRaven. It seems to be working without any issues, so here's a flashable ZIP.
Requirements:
LG G watch R running the 5.1.1 update (LDZ22D). This wasn't tested on anything else.
TWRP installed as custom recovery
unlocked bootloader
Instructions:
(optional) make backup of system and boot in TWRP, so you can revert changes my ZIP makes
install intersectRaven kernel 20150530_08XX or newer. Doesn't matter if you choose single or dual core. I recommend reading through his thread first. kernel thread | link to folder with his lenok kernels
reboot into TWRP
flash lenok_wifi_zip-XX.zip (you can get it to the device with adb push lenok_wifi_zip-XX.zip /sdcard/)
reboot the device
Whenever you flash anything that modifies boot.img (say, a kernel), you have to re-flash lenok_wifi_zip-XX.zip file.
Needless to say, this breaks OTAs - when next Android update hits, you'll have to restore from backup or flash whole images.
Downloads:
0c8d3fa95380e7ac75201bed0cab85fb lenok_wifi_zip-02.zip
AndroidFileHost: https://www.androidfilehost.com/?fid=23991606952612046
Basketbuild: https://basketbuild.com/filedl/devs?dev=Tassadar&dl=Tassadar/lenok/lenok_wifi_zip-02.zip
dev-host: http://d-h.st/FLCk
Notes, warnings...
You're flashing this from your own will. This file brings over bunch of files & bits of firmware from Urbane, something might break. There's also a chance LG didn't just do this because "hey, buy urbane, it has WiFi!" and there is some actual reason why WiFi was not enabled on lenok - including some HW difficulties. Using this method to enable WiFi has the potential to cause permanent HW damage. Also keep in mind that WiFi on G Watch R might not have been certified for use.
It's working just fine for me so far, but I haven't been using it for very long. The voice recognition is slower than on BT and less reliable (sometimes even claiming "offline"), not sure if that's "how's it's supposed to be" or if it is bug specific to this mod. Some guessing about what might be causing it in this post.
One last thing - please, don't discuss common "halp I don't know how to install recovery/flash kernel/flash a ZIP" problems in this thread and focus only on issues related to the mod itself. Thanks.​

Lets start the party, flashing right now

Flashed everything. Now the G Watch R reboots into TWRP or maybe Bootloader. But no normal reboot into android?

Glad to see that someone mirrored what Paul O'Brien did for me back in the N1 days. He gave me the ROM and I gave the kernel to enable FM radio.

Flashed stock boot.img, recovery.img and system.img to get the G Watch R back to work. Now I'm waiting for comments with working hack until I'm gonna try it again..

tried,everything seems good,got the wifi

Why the kernel requirement?

SferaDev said:
Why the kernel requirement?
Click to expand...
Click to collapse
The stock kernel doesn't have wifi drivers enabled. That release of intersectRaven's kernel is based on urbane's sources, and has all the drivers enabled.

Tasssadar said:
The stock kernel doesn't have wifi drivers enabled. That release of intersectRaven's kernel is based on urbane's sources, and has all the drivers enabled.
Click to expand...
Click to collapse
Alright seems logical, G Watch R had the hardware inside but no certification in the device specs. I'll give it a try later. Thanks, if you need anything don't hesitate to ping me.
SferaDev

Hi firstly thank you for this mod!
I have a simple and noob question is it normal that with wifi turned on i can receive notifications but i can't answer them?

fabioio said:
Hi firstly thank you for this mod!
I have a simple and noob question is it normal that with wifi turned on i can receive notifications but i can't answer them?
Click to expand...
Click to collapse
What do you mean "answer"? Voice recognition? I've noticed that it is much slower and less reliable (sometimes even claiming "offline"), not sure if that's the same on Urbane or not. Urbane has different mic configuration and different sound firmware files, which don't work on lenok - so lenok might be missing some optimizations that make voice recognition over wifi faster (BT and WiFi use different "formats" of data sent into the cloud, that's why it might matter how they are "prepared" on the device by the FW).
Or maybe it is the same on Urbane? I really dunno, get some users with watches that have wifi by default and make them tell us

Tasssadar said:
What do you mean "answer"? Voice recognition? I've noticed that it is much slower and less reliable (sometimes even claiming "offline"), not sure if that's the same on Urbane or not. Urbane has different mic configuration and different sound firmware files, which don't work on lenok - so lenok might be missing some optimizations that make voice recognition over wifi faster (BT and WiFi use different "formats" of data sent into the cloud, that's why it might matter how they are "prepared" on the device by the FW).
Or maybe it is the same on Urbane? I really dunno, get some users with watches that have wifi by default and make them tell us
Click to expand...
Click to collapse
yeah i meant that! i actually can't use voice recognition i always get some connection problem!

Why would they disable it when it clearly works?

Works great

123421342 said:
Why would they disable it when it clearly works?
Click to expand...
Click to collapse
Clearly for market reason. LG want everybody buy urbane.They are sucks.

akaHardison said:
Clearly for market reason. LG want everybody buy urbane.They are sucks.
Click to expand...
Click to collapse
wifi certifications take time and cost money, that is probably why

suljo94 said:
wifi certifications take time and cost money, that is probably why
Click to expand...
Click to collapse
You should know that this watch has already have certification it needed.FCC has already approved this watch using WiFi.

No LG bashing guys, keep in clean in here. This is about the mod, nothing else.
What could actually be permanently damaged by this? I want WiFi, but not bad enough to risk damage to the radio chip. In other words is it a generic warning, or is there actually an above-typical risk of damage?

Koopa777 said:
No LG bashing guys, keep in clean in here. This is about the mod, nothing else.
What could actually be permanently damaged by this? I want WiFi, but not bad enough to risk damage to the radio chip. In other words is it a generic warning, or is there actually an above-typical risk of damage?
Click to expand...
Click to collapse
It's just that we have no idea. While I'm inclined to believe lenok doesn't have wifi just due to marketing reasons, there might be some key differences between bass and lenok that I don't know about, and that _might_ cause some problems later.

Great work Tasssadar!
Regarding the voice recognition "issue" I've noticed it works pretty decently if I'm close to the WiFi AP but gets worse and worse as I move away, so it might have something to do with WiFi signal quality.
Shame on you, LG.

Disabling Doze Not Working

On my S7 Edge, S8, and S8+, I've been able to selectively disable Battery Optimizations from apps like Nine (Email), Facebook Messenger, and other apps to ensure they don't go into deep sleep mode (Doze) to ensure timely receipt of emails or Facebook Messenger Messages.
On my Note 8, the menu is unchanged from the other devices, but I noticed the functionality is no longer working. The difference being Android OS 7.1.1 vs. 7.0 on the other devices.
In FB Messenger, the tell is when you open the app after a few minutes, if you see the orange bar that says "connecting to network", you know the app disconnected in deep sleep (Doze). With Battery Optimization disabled for this app, this disconnect should no longer occur, but it is.
In Nine, the tell is when your phone randomly pushes a bunch of emails to you, sometimes 20-30 minutes delayed when on the earlier Samsung models, the emails come in right away. This is not an app-related configuration issue, but Doze issue.
Perhaps a glitch? Has anyone else tested on their Note 8 and experienced the same?
I wouldn't even know how or where to report a bug like this to Samsung.

No one ever replied. Has anyone experienced the above? Perhaps resolved now? I ended up going back to my S8+ because of this problem.

Had same problem with random disconnections even with Battery Optimizations and Battery Monitor disabled for Messenger, Im using an old version now (91.0.0.19.70) with the old interface and no problems since... I found latest versions of messenger very buggy at least for me.
About Nine, don't know as I use Outlook and never had a problem with it since I have this phone.

iFlasher said:
Had same problem with random disconnections even with Battery Optimizations and Battery Monitor disabled for Messenger, Im using an old version now (91.0.0.19.70) with the old interface and no problems since... I found latest versions of messenger very buggy at least for me.
About Nine, don't know as I use Outlook and never had a problem with it since I have this phone.
Click to expand...
Click to collapse
On my S8+, I use the latest versions of FBM (beta stream). No issues with regards to connectivity itself (the app is buggy sometimes as its beta though). It was only on the Note 8 where even disabling the battery optimizations for Messenger (and other apps) still forced them to disconnect.

I have the same issue. My phone is Factory unlocked and from Malaysia, used with an American Sim card inside.

So I recently bought the Asian version
SM-N9500
Android 7.1.1
I also experience the issue. Took EVERYTHING off app optimize battery usage. Even took it off monitor list and added to white list. Delay is still there.
I've just downloaded an app off the play store called PNF No-Root which basically pushes every 5min (you can set different interval up to 1min) that syncs everything. So far i've gotten whatsapp msg 2m-3mins late but so far I can't figure out what else to do to fix this.
This is driving me insane when my entire business is built online and I need to respond ASAP.

Was this ever resolved? I'm worried the issues will carry through on the S9

settings>devicemaintteinance>battery>unmonitored apps>ad apps, select which apps you do no want to be monitored an will be always running

winol said:
settings>devicemaintteinance>battery>unmonitored apps>ad apps, select which apps you do no want to be monitored an will be always running
Click to expand...
Click to collapse
I'm aware of these steps. The issue was on the Note 8, these steps were ineffective as opposed to the S7 / S8 series of devices where it worked just fine. I was wondering if this was ever resolved on the Note 8.

WorldIRC said:
I'm aware of these steps. The issue was on the Note 8, these steps were ineffective as opposed to the S7 / S8 series of devices where it worked just fine. I was wondering if this was ever resolved on the Note 8.
Click to expand...
Click to collapse
For resolved you mean that if it works in note 8? Well, it works fine with my 950F exynos 128 GB, in fact, vital systems app are not easily dozed, the likes such as chrome, keyboard, playstore, gallery, sms, gmail, etc

winol said:
For resolved you mean that if it works in note 8? Well, it works fine with my 950F exynos 128 GB, in fact, vital systems app are not easily dozed, the likes such as chrome, keyboard, playstore, gallery, sms, gmail, etc
Click to expand...
Click to collapse
Do you use Facebook Messenger on your phone?

No, I do not, I never do, in fact I have all facebook related things disabled with bk

winol said:
No, I do not, I never do, in fact I have all facebook related things disabled with bk
Click to expand...
Click to collapse
Ok it would be tough to test with you then. With Messenger, if Doze is enabled, the app will keep losing its connection and every time you open it, it would say connecting to network. With Doze disabled for Messenger, this problem goes away, except on the Note 8.

I was able to test a Canadian S9+ on Oreo, the issue does not seem to affect it. I am optimistic that the Oreo update for Note8 will address this.

Yes, it's not just the Note 8, I think and I strongly believe that the problem is related to the crappy nougat version 7.1.1., I had the very same problem (email not syncing, and delaying (lollipop and marshmallow don't have it!) even on pixel, opo 3t, and s8, all of them had Android 7.1.1., the problem was almost fixed on 7.1.2.
Now, had the pixel 2 xl, with Oreo, for a while, switch back to Note8, and the problem came along.
This is the main important reasons to make me update to Oreo on note 8

Ariyax said:
Yes, it's not just the Note 8, I think and I strongly believe that the problem is related to the crappy nougat version 7.1.1., I had the very same problem (email not syncing, and delaying (lollipop and marshmallow don't have it!) even on pixel, opo 3t, and s8, all of them had Android 7.1.1., the problem was almost fixed on 7.1.2.
Now, had the pixel 2 xl, with Oreo, for a while, switch back to Note8, and the problem came along.
This is the main important reasons to make me update to Oreo on note 8
Click to expand...
Click to collapse
I almost figured it had to do with 7.1.1.

Pixel 4/4 XL HDMI/DisplayPort Alt Mode Kernel?

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.