I am trying to hide some status bar icons on MIUI 13.
Do you know of a way to hide icons such as Roaming, Mute, DND...?
I tried these without success:
adb shell settings put secure icon_blacklist zen,mute,volume
Using the SystemUI Tuner app, grating all permissions.
Using the Activity Launcher and opening the System UI demo mode.
ADB AppControl
Old question but I faced the same issue so here is how I fixed it.
First you must have the Developer status enabled.
Then enable the following settings in the Developer options:
USB debugging
Wireless debugging
USB debugging (Security settings)
Restart phone and connect it to your computer where ABD is downloaded
Open terminal where ADB is unzipped
Do the following commands:
./adb devices
This should list the device and show it connected
./adb shell settings put secure icon_blacklist nfc,zen,volume
This will hide, respectively, the nfc icon, the dnd moon crescent icon and the muted bell icon
Related
`Has anyone seen the following error in Datawedge 3.2.4:
Error : Scanner : SCN1: Failed to get supported RSM attribute count. Error=a0000012
Error : Scanner : SCN1: Scanning failed. Error : a000001d .
If so do you know the cause or fix?`
One possibility is that your scanner is trying to connect by wireless or Bluetooth to a nearby network. Finale Data Collector operates in disconnected mode, so you don't need any wireless communication on the scanner. You can turn off the scanner's wireless modes to eliminate any pauses from the start menu or Windows icon on the task bar: Settings > Connections > Wireless manager.
If Finale has crashed or if some other software running on the scanner has crashed, you can do a warm reboot on the scanner by pressing and holding the red on/off button for 10 seconds. The button is in the upper right of Motorola MC70 scanners. A warm reboot will recover from any crashed applications and will not erase your hard drive or lose any data.
There is other scenarios to what you are experiencing
A. Scenario #1
The DataWedge may have become corrupted and needs to be reinstalled. The dataWedge is an application that allows to send scanned data from the barcode scanner to the any Finale application you have running on the scanner.
Download datawedge.CAB (you will need to have a Zebra free account)
You must have, or, order your Docking Station Kit (Chargers/Cradles/Docks in the Enterprise Scanning industry are SKU's sold separately, by factory protocol). Plug it into the wall, and, into your Windows 7(preferable) PC USB Port with mini USB-to-USB Communication Cable.
With your MCxx powered on and PC on the internet, dock your MCxx into the cradle and allow the USB drivers to sync with the computer for approximately 10 minutes - this allows your PC's "Windows Mobile Device Center" sync program to auto-install on your PC. This program allows you to view and transfer programs, files, and updates from your Computer to your handheld.
With your MCxx connected to Windows Mobile Device Center, hold you mouse over File Management and then click "Browse the contents of your device". Once your device window is open, drag-and-drop or copy-and-paste the DataWedge.CAB file into the window, to paste onto the unit.
Once DataWedge.CAB file is pasted onto the unit, the revert over to the MC70 touch-screen. From the docked MCxx, click the Windows Start Icon, then click programs, then click File Explorer. Within Windows File Explorer click the top-left dropdown arrow in the grey takbar to select My Device. There you will find the DataWedge.CAB file that you pasted. Click that file to run the installer. A Selection Screen pops up of where to install, and you must Select "Application" to install Data Wedge onto the MC70, click install. Once installation is finished, allow program a minute to initialize then Start Scanning.
B. Scenario #2 - The default baud rate for the scanner needs to be increased.
Open Data Wedge (by clicking icon in toolbar tray on bottom-right of device homescreen > Advanced Configuration > Profiles > Profile0 > Input > Serial > COM 1 > Port Settings > Baud Rate > 115200 > Back
You will want to change the Baud Rates on ports : COM 1 / COM 3 / COM 7 / COM 8.
Once Complete, Keep Clicking Back until datawedge reports that all changes are saved.
Finlay, if none of the above works it might be very helpful to have another Windows mobile that actually works
you can launch the command "System Info" on the command prompt of both of your Windows mobile terminals (the one that work and the one that doesn't) then compare the diferences on the settings
I have a POS terminal (APEXA G from POSBank) that comes with multi-touch screen made by Silicon Works. The touch works perfectly on Windows there are official drivers for it. But for Linux the touch does not work at all. After inspecting the device on Linux Ubuntu distribution using [lsusb -v] command I get the follow information:
Silicon Works Multi-touch Device, VID:PID 29bd:4101
The touchscreen is connected through usb not serial connection.
I tried several generic drivers online but none of them worked for me.
After emailing POSBank technical support I received their quick response which solves my problem.
Following their instructions here is what I did:
1. Uninstall the old touch drivers:
- Lanuch Device Manager
- Human Interface Device -> Usb Input Device
- Remove a USB input device with a value of VID_29BD in the attribute (PID is 3711 or 4101)
2. install latest drivers chipset, LAN, touch, etc... (These drivers downloaded from POSBank official website)
-------------------------------------------------
Please note:
-You need Windows only to run the software that applies the touch firmware upgrade.
-Touch firmware v1.8 is still not available from POSBank official website yet
you have to contact technical support or email me.
-You Must Install SiW Daemon Control Panel to upgrade the firmware (it is included in the touch driver zip file from POSBank official website)
-------------------------------------------------
upgrade the touch firmware to V1.8 using instructions below:
Open SiW Daemon Control Panel
On device tab press F6
Select Multi-touch device 0
Click File open then select the firmware update file
Click FW update
After Ubuntu boots the touch should start working out of the box no special configuration is needed.
Note: After the upgrade the touch may not work on Windows. Don't Panic. You will hear a beeping sound every time you click on the screen which is a good sign. To fix do the following:
Open SiW Daemon Control Panel on the Device tap
select Multi-touch Device_0 then click Open Device
select Mouse table(2nd tap) and check Emulation Mode
select About tab and click Preserve Settings which preserves the settings through Windows restarts.
If you have any questions please let me know.
I am happy with their solution now touch works for me on Windows and Ubuntu.
Thank you POSBank and special thanks to Peter Kim from the technical support.
I'm building my own Windows CE 6.0 image (NK.bin) and after Windows has been loaded is the screen just black. When i attach a USB to the USB slave port on the device the window saying "USB client Status" shows up and the mouse is visible and i can control it together with the keyboard.
However, I'm stuck at this. I been reading a similar post to remove all settings in project properties according to stackoverflow-post, without any result. I can't connect to the screen with "Windows CE Remote Zoom-in", but can connect with Remote Register and Remote Process.
Any clue?
I added explorer.exe to HKLM/init but the problem was that explorer was not included in the build. I had to choose the "standard" shell to include explorer, when i actually wanted the "thin client shell". This is still an issue to get some features from them both but at least this problem is solved and I can move on to next ;) Thanks again.
I would like to know if there is a tool simillar to mymobiler for Wince 5.0 which I can use to control the device from my desktop.
I use mymobiler (v1.25) but I believe it controls only devices running on WM5 and above.
Any help would be highly apprecited as the screen of my device has stopped working.
I use MyMobiler myself when I am coding for WinCE5.0 (not very often but I do know that it works.)
In your extracted MyMobiler zip file is three versions of remote.exe.
remote.exe
remote.exe.50
remote.exe.40
The only one I have gotten to work on wince5 is remote.exe.40
Just rename the existing remote.exe file (remote.exe.wm) [you may have to click tools, folder options, and uncheck hide extensions for known file types]
Next rename remote.exe.40 to remote.exe.
After that you are good to go. Copy remote.exe to the device through activesync (xp) or WMDC (>XP) and launch it on the device. It was a bit funny connecting for me the first time - I click connect on pc, then had to click the tray icon on the device, and click connect.
Good Luck!
Link to Video Showing it Running 1
This does work, the auto-install doesn't seem to work but if you copy the remote.exe over as mentioned (any location will do), then start remote.exe, click on the MYMobiler icon in the tray and select Connect, it will attach to your PC like the WinMobile version does.
Also, check the ini files in the MyMobiler directory. There's some details on the features/options.
I can confirm that Dave and Mike's solutions work on Windows CE 7 as well.
I was getting an error with the AYGSHELL.dll library when starting My Mobile after the gun was connected.
Run Mymobiler.exe before you connect the scanner to the PC and then connect to the PC using the tray icon from the gun. No error.
I know about firebug and the developer tools for the major modern desktop browsers, but I can't find any way of debugging JavaScript code on mobile browsers.
What are some high level techniques I can use to debug code on mobile browsers?
Android devices can be put into developer mode by going through settings>Phone status then tapping on "Build number" 7 times. This allows you to do a bunch of things (see step 5) including USB debugging. (Some devices might have Build number under Software Info)
To activate USB debugging, look in Settings for the newly appeared "{ } Developer Options", open this and switch on USB debugging. Connect your device using a direct USB connection.
In Chrome on your desktop, in the usual developer tools panel used for debugging, look in the menu for more tools>remote devices. With Discover USB devices selected, you should now see your mobile device on the side.
Select it to see a list of all the chrome tabs you have open and the ability to enter URLs directly.
Selecting one of the links will open up a new window with a mirror of your device screen on the left and all the familiar chrome debug tools on the right. You can still control your device directly or use the mouse on the mirrored screen. It even rotates.
full details on remote debugging from google and how to enable developer mode (link as above) from askvg.com
Android provides a tool set for these purposes:
https://developers.google.com/web/tools/chrome-devtools/remote-debugging/?utm_source=dcc&utm_medium=redirect&utm_campaign=2016q3
Apple does it a similar way:
https://developer.apple.com/safari/tools/
Tutorial: https://css-tricks.com/using-chrome-devtools-to-debug-javascript-in-any-browser-with-ghostlab-2/
You can debug on Safari Mobile with any iPhone/iPad. In Developer menu you can find your device and you can then debug your code with inspector.
If you have an Android Device instead, you can debug on Chrome Desktop (remember to active the debug mode) with chrome://inspect
On the IPhone you can go into settings>Safari>advanced and turn web inspector on
Sometimes I get bugs reported by customers that are not reproducible every time or in our testing. For such cases I recommend Lucky Orange. It records the user activity and also has the option to record console messages.
PS - I'm not an affiliate, I use them for my own projects and like it.
Another solution for basic debugging (which many times is all is needed), is having a console polyfill on mobile without the need to plug into USB on desktop.
mobileConsole is such a console polyfill.
Hope it helps someone, I found it useful.