Related
I use the Hidden Menu to adjust the LED brightness, but I don't really know anything else about the many things in it. I was looking at the various tests and checking them out today and noticed something weird. When I did the Gyro Cal Test (in Device Test just above the LED brightness one), I got "Functional Test Result: FAIL" as the result. That doesn't sound good.
Can anyone try that test and see if something is wrong with my phone or if the G2x is supposed to fail that test.
I don't know if my device has always failed that test or, if not, when it started. The only thing that is wrong with my phone is that the screen doesn't come back on after the proximity sensor turns it off during a call. Either the other person ends the call or I have to pull the battery. If you know how to fix that, I'm all ears! [I'm running Tsugi with stock kernel.]
And speaking of the Hidden Menu, does anybody know anything else useful in it other than the LED brightness adjustment?
lobsterhead said:
I use the Hidden Menu to adjust the LED brightness, but I don't really know anything else about the many things in it. I was looking at the various tests and checking them out today and noticed something weird. When I did the Gyro Cal Test (in Device Test just above the LED brightness one), I got "Functional Test Result: FAIL" as the result. That doesn't sound good.
Can anyone try that test and see if something is wrong with my phone or if the G2x is supposed to fail that test.
I don't know if my device has always failed that test or, if not, when it started. The only thing that is wrong with my phone is that the screen doesn't come back on after the proximity sensor turns it off during a call. Either the other person ends the call or I have to pull the battery. If you know how to fix that, I'm all ears! [I'm running Tsugi with stock kernel.]
And speaking of the Hidden Menu, does anybody know anything else useful in it other than the LED brightness adjustment?
Click to expand...
Click to collapse
Not all items in the Hidden Menu have to do with the G2x, example FM Radio Test. I get the same results with the Gyro Cal Test.
GTWalling said:
Not all items in the Hidden Menu have to do with the G2x, example FM Radio Test. I get the same results with the Gyro Cal Test.
Click to expand...
Click to collapse
Do you know of anything that is useful in the Hidden Menu or is it all just tests to make sure something is on or not?
Call me crazy, but what it's this hidden menu and how do I access it?
Sent from my LG-P999 using xda premium
F0rgiven said:
Call me crazy, but what it's this hidden menu and how do I access it?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Here are two ways of getting to it here.
It's got a bunch of tests for your phone. I've never heard of any major uses for it other than what I do with it, which is adjust the "Touch LED Brightness." I like to turn them down.
You can also set some parameters that are used for GPS; in particular, some people have reported significant speedups by using the Google SUPL server instead of one of the three that are available in the stock ROM.
wmm said:
You can also set some parameters that are used for GPS; in particular, some people have reported significant speedups by using the Google SUPL server instead of one of the three that are available in the stock ROM.
Click to expand...
Click to collapse
Where can I choose to use Google SUPL? It's not listed on mine. Only T-Mobile, Spirent, and LGE SUPL. The T-Mobile one was chosen by default on mine. Do you know what is meant by "Use XTRAS" in the same sub-menu?
Yes, those are the three I mentioned that are available in the stock ROM. You have to add the Google SUPL server before you can select it. If you go to the SLP Server Setting screen and hit the menu button, you'll get the choices Add, Edit, and Delete. Hit Add and set "name" to Google, "slp address" to supl.google.com, "port" to 7276, and "certification file" to /etc/SuplRootCert. Leave "TLS Setting" unchecked. Hit the menu button and then Save. You should then have a Google entry you can select. I'm not sure about "Use XTRAS", but mine is checked.
wmm said:
Yes, those are the three I mentioned that are available in the stock ROM. You have to add the Google SUPL server before you can select it. If you go to the SLP Server Setting screen and hit the menu button, you'll get the choices Add, Edit, and Delete. Hit Add and set "name" to Google, "slp address" to supl.google.com, "port" to 7276, and "certification file" to /etc/SuplRootCert. Leave "TLS Setting" unchecked. Hit the menu button and then Save. You should then have a Google entry you can select. I'm not sure about "Use XTRAS", but mine is checked.
Click to expand...
Click to collapse
Awesome! And you say this will help with GPS? Do you know what it does/how it works differently? Do you use the Google one? Maybe that makes XTRAS become checked because currently mine is unchecked. It is listed as "Disabled."
I do use the Google server, but it's not clear to me whether it helps or not because my TTFF is not great (but not terrible) and varies a lot. Some people have reported that it gives a big improvement. I don't know what the difference might be other than possibly increased bandwidth or decreased latency when downloading the AGPS data. I don't know what the story is with XTRAS. Sorry I can't help more; you can find several threads here referring to the Google SUPL server.
Just purchased a stock HTC One S and I cant seem to get the dialer keys (7) and (0) to work. Once on the voice mailbox it wont press key 7 to erase, or the 0 when inputing an area code per sei. Also, it seems that certain area of the touch screen is not responsive while trying to select options on the setting panes. Has anyone come across this? Any input would be greatly appreciated. Yes I already did a thorough research but wasn't able to come up with much. Thanks
cmbkcaruso said:
Just purchased a stock HTC One S and I cant seem to get the dialer keys (7) and (0) to work. Once on the voice mailbox it wont press key 7 to erase, or the 0 when inputing an area code per sei. Also, it seems that certain area of the touch screen is not responsive while trying to select options on the setting panes. Has anyone come across this? Any input would be greatly appreciated. Yes I already did a thorough research but wasn't able to come up with much. Thanks
Click to expand...
Click to collapse
hm, maybe try a factory reset and clean the display.
if it still doesn't work I would suggest you to get your one s replaced.
NQNH said:
hm, maybe try a factory reset and clean the display.
if it still doesn't work I would suggest you to get your one s replaced.
Click to expand...
Click to collapse
I tried that. Still acting up. Is it possible it's something I could fix by rooting? Thanks
cmbkcaruso said:
I tried that. Still acting up. Is it possible it's something I could fix by rooting? Thanks
Click to expand...
Click to collapse
it doesn't make sense rooting your phone to solve the problem if the display is broken.
its like, trying to replace your monitor by installing an update
but you can install the recent suitable RUU for your mobile from footballs thread and if the problem still apears your display is definetly broken
NQNH said:
it doesn't make sense rooting your phone to solve the problem if the display is broken.
its like, trying to replace your monitor by installing an update
but you can install the recent suitable RUU for your mobile from footballs thread and if the problem still apears your display is definetly broken
Click to expand...
Click to collapse
I guess i'll do a search on a RUU and how it might be pertinent.
cmbkcaruso said:
Just purchased a stock HTC One S and I cant seem to get the dialer keys (7) and (0) to work. Once on the voice mailbox it wont press key 7 to erase, or the 0 when inputing an area code per sei. Also, it seems that certain area of the touch screen is not responsive while trying to select options on the setting panes. Has anyone come across this? Any input would be greatly appreciated. Yes I already did a thorough research but wasn't able to come up with much. Thanks
Click to expand...
Click to collapse
STOP don't do anything. If your phone has a hardware defect you don't want to void your warranty by unlocking the bootloader. Contact HTC or whoever sold you the phone and try to get a replacement.
cmbkcaruso said:
I guess i'll do a search on a RUU and how it might be pertinent.
Click to expand...
Click to collapse
I could not find that specific thread. Any one got a link please or a little guidance?
Thanks
dc211 said:
STOP don't do anything. If your phone has a hardware defect you don't want to void your warranty by unlocking the bootloader. Contact HTC or whoever sold you the phone and try to get a replacement.
Click to expand...
Click to collapse
+1
Sent from my HTC One S Special Edition using xda premium
Is it just the dialer or does that part of the touch screen not work anywhere else? If the actual touch sensors work elsewhere (IE: homescreen, keyboard, etc...) it is NOT a hardware problem. It is a software issue. Make sure you have the latest update installed (different versions based on carriers/countries). If the issue persists (again, if it is NOT a touch sensor problem) go ahead and root it or install a custom ROM.
EDIT: I must have skipped that sentence in your post. You obviously have a touch sensor problem. Go ahead and request a new device (if possible, depending where you bought it) or send it in to HTC. You can figure that one out on your own; we're adults here...
Well, as for me, battery life of Photon Q with CM never was good enough. But after a day ago I've got my phone from 100% to 1% in 6 (yes, six) hours, I've understood, that I have to do something. BetterBatteryStats was excellent, it pointed me at the culprit in just a few taps. Beside turning phone into some heating appliance it also stored gigs of logs onto internal memory (/data/logger). Next question was: how to deal with it. Tries to simply kill it failed, as it respawned right away. After some searching I've come to build.prop tuning. I've changed
Code:
persist.log.aplogd.enable=1
to
Code:
persist.log.aplogd.enable=0
and added
Code:
persist.service.aplogd.enable=0
, rebooted to recovery, wiped cache and davlik cache, rebooted again and... aplogd is still here and its still can't be killed. So, I welcome any hints on how to fix it.
To disable aplogd, you don't have to do silly things like editing build.prop or such.
It's controlled by persistent property (physically stored in /data/property), so your setting of this property will stick as long as you don't wipe your data.
build.prop just specifies the default behaviour - what's set in /data/property (usually set by setprop command) always wins over the persistent property value indicated in build.prop.
In terminal emulator:
Code:
su
setprop persist.log.aplogd.enable 0
This will make the init process to stop the aplogd process and it won't be started again even after subsequent reboots (till the wipe of data, as mentioned above).
But, what exact output from BetterBatteryStats makes you think that aplogd is the actual cause of your battery issues?
It's behaving pretty harmless regarding the battery here by all accounts as far as I was able to check.
I've enabled aplogd on xt897 CM by default to help users to be able to deliver the logs to developers. As you probably understand: no log provided, no issue exists (from the dev point of view). Bugs can't be fixed when the developer is blindfolded, same as a disease can't be cured over mute phone line to a doctor....
Also, the size and number of files created by aplogd in /data/logger is strictly limited, so when you say
it also stored gigs of logs onto internal memory
Click to expand...
Click to collapse
what exact size of /data/logger folder content have you seen in your case?
(I ask about this because there may be a bug in the aplogd log file size/number limiting code, so I'd like to know if I should look into it or not...).
kabaldan said:
To disable aplogd, you don't have to do silly things like editing build.prop or such.
Click to expand...
Click to collapse
Learning is not about avoid to do silly things its about not to repeat them. I found the forums (http://4pda.ru/forum/index.php?showtopic=386024&view=findpost&p=16243763 for example) where people advised to add "persist.service.aplogd.enable=0" to build.prop and swear it's working.
kabaldan said:
It's controlled by persistent property (physically stored in /data/property), so your setting of this property will stick as long as you don't wipe your data.
build.prop just specifies the default behaviour - what's set in /data/property (usually set by setprop command) always wins over the persistent property value indicated in build.prop.
In terminal emulator:
Code:
su
setprop persist.log.aplogd.enable 0
This will make the init process to stop the aplogd process and it won't be started again even after subsequent reboots (till the wipe of data, as mentioned above).
Click to expand...
Click to collapse
Thanx!
kabaldan said:
But, what exact output from BetterBatteryStats makes you think that aplogd is the actual cause of your battery issues?
It's behaving pretty harmless regarding the battery here by all accounts as far as I was able to check.
Click to expand...
Click to collapse
Process section showed aplogd as eating times more CPU time than any other. Also CPU States section showed that processor was almost all the time runing at 1,5Ghz.
kabaldan said:
I've enabled aplogd on xt897 CM by default to help users to be able to deliver the logs to developers. As you probably understand: no log provided, no issue exists (from the dev point of view). Bugs can't be fixed when the developer is blindfolded, same as a disease can't be cured over mute phone line to a doctor....
Click to expand...
Click to collapse
Of course. I suspect it was kind of "exclusive" to me. I don't argue about enabling it by default, just asked about issue.
kabaldan said:
Also, the size and number of files created by aplogd in /data/logger is strictly limited, so when you say
what exact size of /data/logger folder content have you seen in your case?
(I ask about this because there may be a bug in the aplogd log file size/number limiting code, so I'd like to know if I should look into it or not...).
Click to expand...
Click to collapse
I've cleared all files in /data/logger about same time as posted this topic . Now there is 5086 files. Size according to 'du -sk' is 99820 - almost 100M. So maybe I exaggerated a bit about "gigs", but there was definitely hundreds of "megs" of backup* files.
Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/...apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
blackhawk said:
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/details?id=com.vinance.lockdown&hl=en_US&gl=US&referrer=utm_source=google&utm_medium=organic&utm_term=double+tap+apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
Click to expand...
Click to collapse
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
gsosacristian said:
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
Click to expand...
Click to collapse
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
blackhawk said:
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
Click to expand...
Click to collapse
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
gsosacristian said:
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
Click to expand...
Click to collapse
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
hehe, if it is true that there are really hidden things XD
Anyway, I am testing this app and if I see that it works I will be encouraged to install the stock firmware and by the way I will try to dig deep into the configuration in search of an option that I have overlooked
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
gsosacristian said:
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
Click to expand...
Click to collapse
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
blackhawk said:
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
Click to expand...
Click to collapse
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
gsosacristian said:
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
Click to expand...
Click to collapse
Can't verify that but suspect it... Q sucks.
Lol, Google wants to protect you... I feel safer already. Not.
gsosacristian said:
Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
Click to expand...
Click to collapse
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
droidz94 said:
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
Click to expand...
Click to collapse
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
gsosacristian said:
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
Click to expand...
Click to collapse
Thanks! I'll try that
EXACTLY same problem here. I will not repet your words, I'll just say you described EXACTLY what is happening with my phone, a Galaxy A7 2018 (128GB RAM, Brazilian model - A750G/DS).
I can confirm that:
1 - Problem of screen never turning on after being turned off for the first time happens at all stock ROMs. Tried at android 10, downgraded to 9, couldn't downgrade to 8 because odin would not write the image, but the problem persisted on ALL stock ROMs up untill now.
2 - Problem DOES NOT happen at the TWRP recovery. Flashed TWRP just now, so I can flash a GSI, and I can turn the screen on or off as many times as I wish at TWRP screen, without any problem.
These informations corroborate, almost without a shadow of doubt, the idea that this is actually a software problem, not a hardware one. I'm gonna flash the google 10 GSI now, with quantum kernel V3 (seems to be a requirement, I would like to make as litle changes as possible) and post the results.
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
joaodalvi said:
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
Click to expand...
Click to collapse
[GUIDE][A-ONLY][A750x] Guide on How to flash GSI (Updated: 10.06.2019)
I'm not responsible for whatever damage this could possibly cause to your device. If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal Welcome to GSI For Galaxy A7 2018 ONLY FOR A750F/A750FN/A750GN Some...
forum.xda-developers.com
Try this. You need flash a "GSI Boot Fix" to use a GSI on A750.
I know DEX isn't supported. When trying to force desktop mode w/ a various Usb-c HDMI dongles nothing happens.
Q: Do we actually know if this is a Samsung hardware limitation or lock out in the software/kernel?
I'd think it's gotta be a software/firmware limitation, as the hardware can seemingly handle it.
My guess is Samsung did this w/the battery capacity in mind, not wanting to field any complaints about poor battery life while using DeX/desktop mode.
Did you enable ALL of the required settings in Developer Options?
Now that you mentioned it, I also vaguely remember reading somewhere that this one doesn't do video out from the USB-C. That may also be a part of it.
twistedumbrella said:
Did you enable ALL of the required settings in Developer Options?
Click to expand...
Click to collapse
Thank you for replying! I did enable "force desktop mode" and "enable freeform windows". Anything else I need to do?
jacobsson said:
Thank you for replying! I did enable "force desktop mode" and "enable freeform windows". Anything else I need to do?
Click to expand...
Click to collapse
After doing some investigation, there is no video out on this phone. Unfortunately, that means it likely won't ever work. That said, here are the other two options that would normally be used:
"Force activities to be resizable" allows resizing any app in multi-window, which helps if you were to resize them on the psedu-DeX view
"Enable freeform sizecompat" helps with apps that have compatibility settings that might break freeform with the standard option.
I purchased that NexDock Touch just after the Note 20 Ultra. I haven't gotten around to testing it with this one, but DeX was one of the harder things to give up.
twistedumbrella said:
After doing some investigation, there is no video out on this phone. Unfortunately, that means it likely won't ever work. That said, here are the other two options that would normally be used:
"Force activities to be resizable" allows resizing any app in multi-window, which helps if you were to resize them on the psedu-DeX view
"Enable freeform sizecompat" helps with apps that have compatibility settings that might break freeform with the standard option.
I purchased that NexDock Touch just after the Note 20 Ultra. I haven't gotten around to testing it with this one, but DeX was one of the harder things to give up.
Click to expand...
Click to collapse
Thanks, I tried enabling those too just to see if anything changed. I'd love to know if the usb-c port lacks physical connections internally. I still wouldn't count out the software side of things, maybe we'll know when someone skilled look into making a custom rom.
jacobsson said:
Thanks, I tried enabling those too just to see if anything changed. I'd love to know if the usb-c port lacks physical connections internally. I still wouldn't count out the software side of things, maybe we'll know when someone skilled look into making a custom rom.
Click to expand...
Click to collapse
If the hardware could support it, you would at least get mirroring.
... that's not to say wireless isn't an option down the line.
KOLIOSIS said:
I'd think it's gotta be a software/firmware limitation, as the hardware can seemingly handle it.
My guess is Samsung did this w/the battery capacity in mind, not wanting to field any complaints about poor battery life while using DeX/desktop mode.
Click to expand...
Click to collapse
I don't understand this just because I also charge my phone while using the usb port. So...
I'd for sure donate to anyone who manage to unlock the ability to at least use "force desktop mode" on this device. Then we could at least make some kind of DIY DeX using the Taskbar app.
jacobsson said:
I'd for sure donate to anyone who manage to unlock the ability to at least use "force desktop mode" on this device. Then we could at least make some kind of DIY DeX using the Taskbar app.
Click to expand...
Click to collapse
Hardware
Limitation
The (likely) reason there is no video out is the cover. That is identified as a second screen, just like any connected to DeX. Being the first time the outside screen is a legitimate screen, Samsung probably couldn't get together the software to both limit the outside screen AND fully support an external display. The easiest solution would be disabling the ability altogether.
Does the Fold support DeX? That should give a pretty good indication of future possibility, but not until a future generation. The best we'll get on this one would be unlocking the cover and some sort of wireless screen share.
Multi-displayThe Force desktop developer option enables you to turn on system decoration support on all secondary displays. Force desktop mode also displays a mouse pointer on the secondary displays instead of on the default display. When used with the Enable Freeform windows developer option, Force desktop simulates a desktop experience with multi-window mode and the ability to resize windows.
Click to expand...
Click to collapse
Learn about foldables | Android Developers
developer.android.com
Looks like part of the issue is the cover screen blocking it
I use adb/scrcpy as kind-of 2nd screen workaround on my PC.
Simulate a 2nd Screen with your desired resolution on the phone and then use scrcpy to push this simulated screen to my PC. It crashes the phone sometimes - just reboot.
Not a Dex solution, but sth you can write emails with and use the browser.
msm1111 said:
I use adb/scrcpy as kind-of 2nd screen workaround on my PC.
Simulate a 2nd Screen with your desired resolution on the phone and then use scrcpy to push this simulated screen to my PC. It crashes the phone sometimes - just reboot.
Not a Dex solution, but sth you can write emails with and use the browser.
Click to expand...
Click to collapse
Yeah I tried that too, not bad at all!
Seem to work really good for movie content and office applications as you mentioned.
I tested some gaming and I'm not sure if it's a limitation of the software but I tried some emulation such as Super Mario Bros. 3 and I noticed a lot of "dropped" frames when jumping, could have something to do with the image compression. If it could find some setting fixing this would actually be a really good work-around, using something like a raspberry pi as the middle hand.
jacobsson said:
[...]
If it could find some setting fixing this would actually be a really good work-around, using something like a raspberry pi as the middle hand.
Click to expand...
Click to collapse
Well I am not playing. Using it for office stuff only and not very often. It is just too uncomfortable to set it up, reconfigure the phone and revert it all back afterwards.
The Flip is unfortunatly not made for it. A price I am happy to accept for the pocket-sized form ;-)