I am working in Phone 8 development,
I have been given a use case, where i need to handle Notification LED depending on different kinds of Notification, for example, for "Urgent message" i am supposed to Blink Notification LED very fast or blink an Red LED, For "Medium Message" Blink Notification Led at a medium Pace, or blink Amber LED, For "Low Message", Have to Blink Notification LED at a Lower Pace or Blink Green LED,
If Flashing of LED is Not Possible, is there a way where i can flash at least the Window Button which is at the Bottom Center of the Device.
Thanks in Advance.
There is no notification LED on any Windows Phone, be it a red or a green LED, so what you're asking for is impossible.
As for blinking the Windows button, that's a nice idea but there's unfortunately no API for that, so it's also a dead end.
Related
I have been fatal for a few days with this incident. After the latest Chrome updates I am left with a headache.
We have ASUS v161 touch screens (although it happens to us in more models), and we open the chrome in kiosk mode. The power configuration is high performance and we only turn off the screen after 15 minutes (no sleep). We have also tried disabling anything that turns off the hard drive or usb without success.
We have tried to activate all the touch flags, we have deactivated the hardware acceleration, etc ... But it is happening with the last 3 updates.
Chrome version: 88.0.4324.150 (Official Build) (64 bits)
Windows version:
Windows 10 Pro Edition
Version 20H2
Installed on 09/25/2020
Operating system version 19042.746
Windows Experience Feature Experience Pack 120.2212.551.0
The issue is that when you return from the off screen, by touching with your finger, the screen turns on but the web content that chrome shows does not respond.
If we do not open it in kiosk mode, it does not respond until we touch anywhere in Windows or in the chrome address bar, then it begins to respond. But the web does not respond by itself if we do not touch outside of it. The web is frozen, te text cursor are freeze. (This also happens with Edge) It does not happen with Firefox.
If you hit it with the mouse, no problem, all return to be responsive
Video attachment: https://youtu.be/BH2abO6AXaM
In the video it is clear how the system activates the screen with touch, but chrome is frozen, the cursor does not move, it does not respond to any link, there is a moment where the screen goes blank, and at the end you see how it responds when I touchthe address bar. This happens right away if you hit the address bar or any other windows/desktop of Windows.
When Chome wake up all touch response are ok and the cursor blink again. If like's Chrome still sleeping until other event different than touch success.
Thanks a lot
Jorge
I was having this problem too for a few months, but it went away with Chrome v91. Upgrade to the latest version of Chrome if you're still on a lower version.
I have completed the "Build an App" tutorial here: https://www.polymer-project.org/2.0/start/toolbox/set-up and have noticed that the paper-checkbox element is not behaving well - it will intermittently freeze at various stages of the re-render. For example, when it is in the unchecked state, and I tap it, it will freeze with the grey circle surround, but without actually displaying the tick in the checkbox. It will also freeze in other states as well.
I think the problem only occurs for screen gestures. I.e - it will fail on a mobile device for screen taps, and also on my Win10 laptop when I tap the (touch-sensitive) screen, but when I use the touchPAD on my laptop, it works reliably.
I am a raw beginner with Polymer. (and everything ;^)
This seems to be related to a known issue (PolymerElements/paper-checkbox Issue #156).
I can reproduce the buggy ripple animation on your site in Chrome 66 on macOS High Sierra when emulating mobile mode. It seems to intermittently occur after switching views (e.g., to View Three and then to New View) and then clicking the checkbox label (clicking the checkbox itself does not exhibit the problem).
Part of the problem is the checkbox's ripple has a "focus" state, where it shows the middle of the animation (the "frozen grey circle" you mention) when the checkbox gains focus. I'm not sure that's by design.
I recommend voting on the GitHub issue, or creating a new issue if you think it's a different problem.
I have a game I am developing for a client. Its not a particularly intensive game graphically but it does have quite a few different animations and a large number of textures. It seems that there is a threshold for the number of different spritesheet based animations that I have have in Chrome. When I go beyond that point (about 5 different animations) the FPS tanks to about 5FPS.
The weird thing is the game runs at a solid 60FPS all the time in Firefox with no problems.
It appears that it something to do with the way Chrome does hardware acceleration of the 2D canvas.
Note this video of the game, the game runs at a silky smooth 60FPS (see bottom right for FPS counter) when the game is smaller than about 220px high, but as soon as its even a little higher than that then it runs at 5-10FPS:
https://www.youtube.com/watch?v=3VWo6eQmy1g&feature=youtu.be
I think its got to be related to this issue:
https://code.google.com/p/chromium/issues/detail?id=170021
It says fixed but I dont think it is.
Does anyone have any more info on this?!
Cheers!
I'm doing some d3.js visualization development (mostly SVG) and I was measuring the FPS of my transitions using the "Show FPS meter" option in the web tools. Strangely, the FPS appears to be capped at exactly 30fps. Other colleagues using the same version of Chrome consistently get 60fps running the same code.
I can get a higher frame rate out of other browsers and out of Flash so it seems to be something Chrome specific.
Does anybody know what kinds of things might cause Chrome to clamp the frame rate at 30fps? I've read that it might do this if it thinks that a smooth 30fps will look better than a choppy 60fps if there is a lot of variance, but I don't understand why it would need to do that on my fast desktop machine.
Here's an example page that shows the problem:
http://mbostock.github.io/d3/talk/20111018/collision.html
Drag your mouse around and you'll probably see the FPS counter sit around 60fps. On my machine, it sits at precisely 30fps.
I've tried Canary with the same results.
I built a website, and the designer who drew the design of the page has Mac computer. He says that Mouse wheel scrolling doesn't work, only the browsers left "slider" works. I mean when you are with your mouse in center of the screen and you do the mouse wheel scroll, the page doesn't move, and if you drag Browsers scroll - it moves.
The thing is that I've been only using PC so I've got no idea - why that can happen with a website on Mac. It works fine in 5 browsers (IE, Opera, FF, Chrome and Safari on PC), and mouse scroll has problem in any browser on Mac.
Can anyone share with your ideas why could that happen and maybe how to fix it. I have 0% experience with Mac, I don't even know what to do after turn on/off button :)
P.S. i tagged PHP, CSS and HTML because the website is developed using those languages and Flash player & slider.
www.ninogvetadze.com/new
Before you go ahead and deem it a code problem, I'd have your mac user clean his scroll wheel out with either a.) an alcohol wipe or b.) a piece of paper. Rub the mouse ball with the wipe, or apply pressure to it with the paper and roll it back and forth to git any dirt out. I'm willing to bet it is a hardware issue rather than code.
If it is a newer mouse without the scroll ball, then... well, I lost the bet.
only the browsers left "slider" works
If it's on the left, it ain't the browser's standard scroll bar.
mouse scroll has problem in any browser on Mac.
Because all those browsers are using the same Flash player plugin.
the website is developed using those languages and Flash player & slider.
Yep. There you go - the Flash "slider" obviously wasn't tested on a Mac. Now you know why designers with a clue rely on standard-based approaches instead of Flash.
(Edit) Yep - just used the address in your comment above to look at your site. There's a "macmousewheelflash.js" being loaded, which apparently has something to do with adding mouse wheel support to the Flash movie at the top. Looks like that's interfering with proper wheel support for the rest of the page. You could probably just remove that - I don't see where the Flash movie needs to scroll anyway. Or, for that matter, why you need Flash for a simple cross-fade slide show...