New firmware 1.08e and Duet Web Control 1.06
Posted by chrishamm
|
Re: New firmware 1.08e and Duet Web Control 1.06 May 20, 2015 01:43PM |
Has anyone tried accessing Duet Web Control 1.06 from an Android smartphone/tablet? I tried a Samsung Galaxy note, a galaxy tablet and an ancient Archos tablet. So cool to be able to do this but all three showed exactly the same problem rendering the Head Movement controls:
I know the browsers in these things are pretty basic but so much renders correctly I was just curious to know if it was perhaps an easy fix.
RS Components Reprap Ormerod No. 481
I know the browsers in these things are pretty basic but so much renders correctly I was just curious to know if it was perhaps an easy fix.
RS Components Reprap Ormerod No. 481
|
Re: New firmware 1.08e and Duet Web Control 1.06 May 21, 2015 07:33AM |
It works OK in Chrome on my Galaxy S4.
Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod
Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod
Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
|
Re: New firmware 1.08e and Duet Web Control 1.06 May 21, 2015 12:08PM |
Amazing isn't it shadow651. Tech stuff becomes a "Legacy item" while you're unboxing it these days 
RS Components Reprap Ormerod No. 481
RS Components Reprap Ormerod No. 481
|
Re: New firmware 1.08e and Duet Web Control 1.06 May 21, 2015 02:06PM |
Quote
Radian
Amazing isn't it shadow651. Tech stuff becomes a "Legacy item" while you're unboxing it these days
Ugg I know the feeling!
On the one hand I get why google did it, because the devices basically weren't getting the updates in a timely fashion or at all. Even if the device manufacturers went along with it, every cell provider then had to make a separate agreement for every device with the manufacturer. So updates just didn't happen.
But at the same time it throws a large percentage of users (~40% if I recall) under the bus.
It all comes down to the bad decision in the early days of android to have critical updates for a web browsing app go through such red tape.... Anything that surfs the web will need frequent critical updates for new day 0 vulnerabilities.
I think the new generation of devices LG G4, Samsungs Galaxy S6 are shipping with chrome out of the box and not including android web anymore.....
At least in the open source world, issues like this are less common!
|
Re: New firmware 1.08e and Duet Web Control 1.06 May 22, 2015 04:06PM |
Quote
Radian
Has anyone tried accessing Duet Web Control 1.06 from an Android smartphone/tablet? I tried a Samsung Galaxy note, a galaxy tablet and an ancient Archos tablet. So cool to be able to do this but all three showed exactly the same problem rendering the Head Movement controls:
[attachment 54969 DWC_Android.png]
I know the browsers in these things are pretty basic but so much renders correctly I was just curious to know if it was perhaps an easy fix.
Inspired by DC42's PanelDue, I've built a touch screen for my Ormerod with a Raspberry Pi, and a SainSmart 7" touch screen, running Raspbian. (The Pi allows me lots of useful things, like being to access my printer as a Wi-Fi hotspot, and also being able to share the Ormerod's SD card as a network shared drive, but I digress
)In any event, I can confirm I found the same problem with Chromium on Raspian, as well as Minimum Kiosk Browser stable, but working in Minimum Kiosk Browser GTK 3 version, as well as Ice-Weasel (Raspbian version of Firefox).
I suspect the issue is todo with Bootstrap not scaling something correctly, but I got bored trying to debug it, and just switched to using Minimum Kiosk Browser GTK 3 version, since it's the fastest browser I've found for this on Raspbian anyway.
Sorry, only registered users may post in this forum.