UCyborg
Content Type
Profiles
Forums
Events
Posts posted by UCyborg
-
-
Back to Android, besides using the app, it's possible to manipulate several files to achieve the desired effect (root needed, assuming Linux kernel in use has USB mass storage functionality compiled in):
- /sys/class/android_usb/android0/enable - write 0 or 1 in here to disable/enable USB functionality (needs to be disabled to be able to write to other files).
- /sys/class/android_usb/android0/f_mass_storage/lun/file - write the path to block device that you want to expose through USB mass storage, external SD card's first partition should be /dev/block/mmcblk1p1
- /sys/class/android_usb/android0/functions - USB functions to enable, some possible values are mtp, mass_storage and adb. Multiple values can be separated by comma.
su echo 0 > /sys/class/android_usb/android0/enable echo /dev/block/mmcblk1p1 > /sys/class/android_usb/android0/f_mass_storage/lun/file echo adb,mass_storage > /sys/class/android_usb/android0/functions echo 1 > /sys/class/android_usb/android0/enable
These commands (need Terminal Emulator app) will make SD card appear just like any USB flash drive on the computer and enable ADB support at the same time (equivalent to having USB debugging checkbox ticked in developer settings on the phone).
It's a good idea to unmount SD card in the storage settings first, though depending on the usage (eg. only reading from it), one might be able to get away without unmounting it and causing havoc on the card's file system.
0 -
It looks like clearing old entries in Device Manager that was setup by INF file that came with those drivers from Windows Update, deleting said drivers, setting up fastboot device entry using device update wizard and picking built-in ADB Device helped with the issue of the said device entry for fastboot mode being reset under certain circumstances.
I plugged the phone with ADB enabled with the same OS builds and recoveries I was experimenting with the last time and cannot reproduce the issue anymore when rebooting into fastboot mode afterwards.
0 -
1909 doesn't download Candy Crush with default settings. Settings app is still clunky and buggy, tends to hang if you minimize it and crashes at times. Control Panel never had such issues.
MS started to even hide Win32 application crashes about 1-2 years ago with default settings. Even if you have debugger registered, you don't get the opportunity to attach it at the moment of the application crash. Was it to not scare the average Joe?
Homegroup remnants are still lurking (Give access to sub-menu in file/folder context menu). Supposedly next year's build for the masses will rid of them. They fixed the initial delay from 1809 when opening New sub-menu for creating file.
Also, it would make more sense for notification center to open on the screen on which the taskbar with the button to open it resides, plus an option to show notification area on other taskbars would be nice. If 3rd parties can do it, surely MS could too and have it neatly integrated into the shell. Oh well.
0 -
I'd try clearing the traces of the old drive from Device Manager and running diskpart from the administrative Command Prompt and typing in automount scrub and rebooting the system.
0 -
1 hour ago, burd said:
Do you use any software/registry to enable aero or have any clue how do i get it
0 -
1 hour ago, cdob said:
Just to confirm, there are XP and later manufaturer drivers. Most likely you used this one in the past.
https://developer.sony.com/file/download/xperia-e3-xperia-e3-dual-driver/Correct.
1 hour ago, cdob said:The manufacuter so0109adb.inf file uses the same driver and settings for ADB and fastboot mode.
winusb.sys is used in both cases.The device ID when in fastboot mode is VID_0FCE&PID_0DDE, so that *.inf couldn't help the OS detect it as compatible with the driver. But you can still set it for use with fastboot mode by manually selecting it in driver update wizard.
1 hour ago, cdob said:Back to Windows 10 default files. No drivers added.
ADB is installed out of the box.
At fastboot select winusb.sys manually.Install Xperia "S1Boot Fastboot" device:
Run device manager, goto "Other devices".
Is there a "S1Boot Fastboot" device with a yellow question mark?
Verify the Compatible Id "USB\Class_ff&SubClass_42&Prot_03"Select
'Update Driver', 'Browse my computer for driver software',
'Let me pick from a list of available drivers on my computer',
'Universal Serial Bus devices',
Manufacturer: WinUsb Device / Model: ADB Device
Confirm the 'Update Driver Warning'Is there a "S1Boot Fastboot" device at 'Universal Serial Bus devices'?
It is used the driver winusb.sys?Yup, yes to all questions. Already got it to work that way.
It's good that at least for ADB mode, it works out of the box either way. Though by default settings, OS might still see fit to download "drivers" from Windows Update, even though no specialized driver is usually involved since it's all just about the .inf file identifying and setting up the device to be driven using winusb.sys.
0 -
Thanks, I didn't look in system winusb.inf and manufacturer supplied INF must have been downloaded from Windows Update, placing the entry in Device Manager that usually appears under Universal Serial Bus devices under a different category, so I didn't realize it was already supported out-of-the-box.
I use Win10 versions 1809 and 1909 on my two machines. Depending on the software currently running on the phone, hardware ID differs, so who knows which is the "right" one. Vendor ID is always VID_0FCE, as should be.
That problem requiring re-install was actually encountered when putting the phone in fastboot mode. I suspect a conflict happened due to an old entry having a different compatible ID (adb vs fastboot and the fact that fastboot ID is missing from winusb.inf), but the same vendor and device ID. The ID when in fastboot mode is constant, but otherwise it seems to depend on the OS running, even though it should be constant as well as long as we're talking about the same phone model, in this case Xperia E3.
I did some cleaning up in Device Manager and removed two drivers that were downloaded from Windows Update for ADB, so now I have phone's entries under Universal Serial Bus devices, not under some custom categories like before. I also added USB\Class_FF&SubClass_42&Prot_01 ID to the list of Prevent installation of devices that match any of these devices ID group policy, so the OS won't try "updating" them. Manually installing ADB Device through update wizard in Device Manager while phone is in fastboot mode also works and makes it visible to fastboot utility.
If I encounter that problem again with fastboot mode requiring driver re-install, maybe I can just add the USB\Class_FF&SubClass_42&Prot_01 ID to the CompatibleIDs value under device key in registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB in hope to prevent it in the future.
0 -
I found this, which isn't really universal since it defines a bunch of specific device IDs to identify them and is outdated anyway. There's also this pull request posted on that project's GitHub page and also another repo containing a dead link to already singed driver (or more precisely, signed INF that identifies ADB interface by the universal compatible ID).
So what are my options? Anyone found such a driver/INF that can be just installed and forgotten about or do I have to go the signing the modified android_winusb.inf with self-signed certificate route if I don't want to disable driver signature enforcement and such?
So far, my phone has used like 6 different device IDs to identify itself and under certain circumstances, I even have to re-install the official driver/INF for it to work again and confirming that I do want it installed, even if device ID doesn't match.
Windows should really have universal ADB driver at this point, like it does for USB mass storage devices...
0 -
Quote
-- 1.5.13 (13.12.2019) --
* version for Windows 10 November 2019 Update (v1909)
* fixed loading CustomThemeMaterial
* using theme default glow size when TextGlowMode set to 0x00000003
* render glow effect under text only when window caption is set to centerI still don't get any glow on normal windows with TextGlowMode set to 0x3, even though it's there on ribbon-utilizing applications. I can specify the amount by saying eg. 0x000c0003.
0 -
Approx. 2 years ago, I noticed the tray refusing to open. I only use that thing once in a blue moon, so I just left it back then. This summer, I finally poked into the designated hole to open it manually.
Now it opens normally most of the time, except the first time after turning on the PC, when it only opens after second press of the eject button.
The unit is almost 11 years old. As far as reading is concerned, that works.
0 -
On 11/25/2019 at 1:17 AM, BudwS said:
For a change of pace, recreated an XP Pro system on an XPS M140 Dell laptop. Had to re-learn XP speak. Got it up and running but had to use IE 8 as the newest MS browser. Shades of Win 10 Insider Preview IE 11. Got IE 8 to access Google.com but very little else. Crap started to appear way back then. However, an old Firefox had no problems under XP Pro SP3.
I still remember installing Slovenian language pack changing Bliss background to plain blueness, the delay before it shut down (must be when MS started to implement delays in their OSes), the refusal to activate online if it was done too many times, repair install turning the OS into a slow snail, update scanning taking 15+ min.
I have an old PC from late Vista era with some small upgrades, which still has full driver support for XP. Funny, if I enable the ability to wake it up from sleep (was called standby back then) with the mouse, that leaves fans running while asleep.
0 -
Tools->Folder options...->View tab->uncheck Always show menus.
1 -
All operating systems are a joke!
0 -
There's this known Slovenian online shop Mimovrste where selecting payment and delivery method is impossible since the JavaScript there throws errors and consequently the site doesn't react to clicks on radio boxes.
0 -
On 11/5/2019 at 10:40 AM, Jody Thornton said:
I never thought I'd do it again, but Pale Moon 28.7.2 works with all of the sites I visit.
In my case, even Basilisk doesn't stomach everything I throw at it anymore.
1 -
Fortunately, the old Explorer search bar has persisted for several days now.
A notable issue from Windows 8 still remains. File operations performed in protected locations only modifiable by admins aren't logged in the undo history, worse, such operations even clear it. And if you eg. create a file named 1.txt, rename it to 2.txt, then use Notepad to save a file named 1.txt in the same folder with 2.txt and use Undo functionality, Explorer will simply overwrite 1.txt with 2.txt, now named 1.txt, without a warning. You get the warning in Win7.
*Sigh*
0 -
Cattle Decapitation - The Geocide
0 -
Cattle Decapitation - Bring Back The Plague
0 -
You can't access System32 folder on 64-bit OS from 32-bit program without going out of your way to do so. All accesses to it transparently redirected to SysWOW64. So it makes no sense to specifically add SysWOW64 anywhere.
The only way to access actual System32 folder on 64-bit OS from 32-bit program is by accessing Sysnative folder. You can navigate into it using 32-bit Command Prompt (cmd.exe) or any other 32-bit application.
So keep 32-bit stuff in SysWOW64 folder and don't worry about it unless you encounter a problem worth worrying about.
https://www.samlogic.net/articles/sysnative-folder-64-bit-windows.htm
1 -
What did they do? Change version number in the .exe, disabled Microsoft's "fix" or what?
0 -
It's not just the height. It changes how searching from Explorer works. Also, UWP stuff in Explorer? Yikes!
0 -
On 11/24/2019 at 8:25 AM, bigmuscle said:
This will be fixed in the upcoming release.
Thumbs up for still working on this project!
0 -
Thank you for your answers. The new "feature" also has a bug that when you right-click on the search bar, you don't get the usual context menu. Works fine once reverted.
Can always go back to 1809 and try some newer build in the future. I'm mostly interested in bug fixes for the existent features.
0 -
Is it normal for Win10 1909's Explorer to have larger address and search bar?
0
Windows 10 not shutting down after upgrade from Windows 7
in Windows 10
Posted · Edited by UCyborg
Small remark
It probably has to do with hibernation file not being the sufficient size, a problem that was likely inherited from the old Windows 7 installation. I suspect hibernation/hybrid sleep didn't work on that particular Windows 7 installation.
Windows 10 just changes "shutdown" to "log off and hibernate", aka. "fast boot" by default, so the issue showed up and then disappeared with disabling fast boot.
I have a Win7 install with that problem, but I don't know why the size wasn't set right in the first place (or maybe the default just doesn't work correctly under certain circumstances). I just turned hibernation off so it can go to sleep (and saves some disk space). If power outage occurred during sleep, it would cause the session to get lost since it's not backed up to disk.
Hybrid sleep feature (can be turned off without disabling hibernation) is also the reason such transitions are much slower by default than they are on Vista predecessors. Maybe it's better if system is loaded on SSD disk.