Not sure what you're looking for exactly, but poke around in /storage/.cache/connman and find your wifi folder. There is a file there that shows the current settings.
Posts by Jaaxx
-
-
Your file is not being read because of an error on line 38. Double check it. I've heard certain text editors in windows can cause problems, if in doubt use nano via ssh.
This is the problem:
-
What LE version?
What hardware?Full log? -
That error has been around for a long time. I recall seeing an explanation before, but the gist is that it's benign and expected. If you check your logs you will see it uses libamcodec instead of libamplayer.
-
Short loud hiss on startup directly after LE boot logo. AV sync appears acceptable on local sources, but live TV is unwatchable with a very slow frame rate. Briefly tried enabling/disabling Sync in settings made no difference.
Audio is very much stuck in 2.0 PCM. Tried Dolby and DTS sources in 5.1 and 7.1 with/without passthrough and I only get 2.0.
-
Is there not a non-nand device tree for gxl_p212?
-
Pelican - Just give up now. It has been determined that any issues you are having are purely in your head and unless you can provide evidence to the contrary, that is reproducible on every variant of s905/s905x board in production, then you can just frig off back to Android.
I'm currently seeking therapy help me upgrade from 8.0.1f.
-
I can confirm that both brightness and contrast settings are broken, at least in the current MM build.
Thankfully, there is a very simple solution - don't use those sliders!
Those broken sliders do not mean that "there is something fundamentally wrong with the driver in MM kernel builds", because the output is perfectly fine when both sliders are untouched at 50%.When a kernel level code breaks userspace there is a problem. I think it's a safe bet that whatever is breaking bright/cont settings may also be affecting other things. Although given this is Amlogic code it may be more correct to say "never implemented correctly/fully" rather than "breaking."
-
It is more than just color range issues for my s905x box. There is something fundamentally wrong with the driver in MM kernel builds.
The best evidence I have is that the brightness and contrast adjustments while using hardware acceleration are totally fubar on MM, but work exactly as expected on the Nougat-y builds.
I had a post about it HERE, but unfortunately the pic links got jacked with the new forum conversion. I'll try to get some screenshots or pics later.
-
I don't have an s905, but I'm happy with my s905x. However, I am considering picking up an s905 just for the gigabit ethernet because I don't have a 4K tv or any other fancy video requirements that would require s905x.
-
Almost anything *can* be repaired. That is not one of them.
Buy a new box.
-
That shouldn't have any effect in the guide screen.
Ooops. You are correct.
I get the same behavior reported here if I leave Settings->TV->Guide->"Default Select Action" set to "Show Information." However, after install one of the first things I do is set this to "Switch to Channel." With that setting it directly jumps and closes the guide, so I did not notice this behavior before..
I want to switch channels 99% of the time anyway and the other 1% of the time I can use the Info button on my remote.
-
Settings->TV->Playback->"Start Playback Minimized"->OFF
-
Settings->System->Add-ons->Manage Dependencies
-
Amlogic routes sound to all outputs simultaneously regardless of Kodi's settings. Simply mute the TV or the Receiver depending on which you aren't using at the time.
-
Something is fundamentally wrong with display on some S905x boxes and the MM kernel.
On MM I cannot lower my brightness below 50% without the display becoming "solarized" with almost a photo negative effect. Also, the contrast only seems to only effect the blue/red channels somehow.
On the nougat frankenstein these issues are gone, picture is much sharper, and with accurate color. However, I get some issues with double refresh rate changes on channel switch in LiveTV and other odd screen blanking events.
So for me right now it's a toss up between the two. Looking forward to seeing what changes when and if the full nougat kernel can be added.
-
What are these 8.0.1l-mm versions?See this thread - thread-8463-post-50209.html
-
8.0.1l with MM kernel (freshly rebased on latest LE kernel)Should this be used with the same device tree as the nougat version?
Edit: Current device tree works fine here.