Showing posts with label edge. Show all posts
Showing posts with label edge. Show all posts

Thursday, September 21, 2017

Ubuntu Edge

Ubuntu Edge




How the Edge compares
Ubuntu EdgeApple iPhone 5Samsung Galaxy S4
Mobile OSDual-boots Android and Ubuntu mobileiOSAndroid
Desktop OSUbuntu DesktopNoNo
RAM4GB1GB2GB
Internal storage128GB64GB16GB
Screen720 x 1,280, 4.5 inches640 x 1,136, 4 inches1,080 x 1,920, 5 inches
ProtectionSapphire GlassCorning Gorilla GlassCorning Gorilla Glass 3
ConnectivityDual-LTE, GSMLTE, GSMLTE, GSM
SpeakersStereoMonoMono
BatterySilicon-anode Li-ionLi-ionLi-ion
Price$695$849*$750**
CPU/GPU, screen technology to be finalised before production. * Apple Store ** Best Buy



In the media
�If youre not living on the edge, youre taking up too much room. Say hello to the Ubuntu Edge, the first smartphone to use open-source Ubuntu Touch software as well as Android�
� CNET
�By this time next year, there could very well be one very elegant looking, monstrously powerful smartphone that can actually become a computer�
� Silicon Angle
�In case you haven�t been following the story, the Edge is an awfully handsome concept for a phone that will run Ubuntu and Android�
� TechCrunch
�Apparently the Ubuntu community is nuts about this idea. Within just under eight hours... some $2 million in donations to the project have flooded in, making it whats said to be the fastest and thus perhaps most successful crowdfunding effort ever seen�
� Fast Company
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
What is Ubuntu Edge?

In the car industry, Formula 1 provides a commercial testbed for cutting-edge technologies. The Ubuntu Edge project aims to do the same for the mobile phone industry -- to provide a low-volume, high-technology platform, crowdfunded by enthusiasts and mobile computing professionals. A pioneering project that accelerates the adoption of new technologies and drives them down into the mainstream.

This beautifully crafted smartphone is a proving ground for the most advanced mobile technologies on the horizon, a showpiece for true mobile innovation. And at the heart of it all is convergence: connect to any monitor and this Ubuntu phone transforms into an Ubuntu PC, with a fully integrated desktop OS and shared access to all files.
We�re fascinated by converged computing, the idea that the smartphone in your pocket can also be the brain of the PC on your desk. We�ve shaped Ubuntu so you can transition seamlessly between the two environments. Now all that�s needed is a phone that�s designed from the ground up to be a PC as well.
The Ubuntu Edge is our very own superphone, a catalyst to drive the next generation of personal computing.





The hardware




We�ve scoured the research labs of the biggest companies and most exciting startups for the latest and greatest mobile technologies to specify the first-generation Edge.
Crafted from cool, textured amorphous metal, the Edge has a distinctive, precise look but its rakishly chamfered edges are shaped to fit naturally in the palm -- our design prototype already has a wonderfully solid feel. It�s the right size, too. Edge gestures are the next big thing in mobile, and our testing has found that a 4.5in screen is ideal for comfortable control of all four edges with one hand.

We also believe the race for ever higher resolution has become a distraction. Beyond 300ppi you�re adding overhead rather than improving display clarity. We think colour, brightness and dynamic range are now the edge of invention so we�ll choose a display for its balance of resolution, dynamic range and colour accuracy.
We�ll protect that gorgeous display with something vastly tougher than glass: pure sapphire crystal, a material so hard only diamond could scratch it. For a phone to run a full desktop OS, it must have the raw power of a PC. We�ll choose the fastest available multi-core processor, at least 4GB of RAM and a massive 128GB of storage. The battery will use silicon-anode technology, so we can squeeze more energy into the same dimensions.

With that kind of muscle, this phone can be your main PC anywhere -- and we really do mean anywhere. You can use the desktop wherever you can find a standard HDMI screen, and the dual-LTE chip will get you online with 4G even when you�re travelling abroad. It�s desktop computing gone truly mobile.

The software

Next-generation hardware deserves innovative software. The Ubuntu Edge will dual-boot both the Ubuntu phone OS and Android, and convert into a fully integrated Ubuntu desktop PC.

First, Ubuntu mobile. We designed the interface to create a beautiful home screen that�s free from the usual clutter. You navigate by swiping over an edge of the screen: open your favourite apps on the left edge, switch instantly between open apps from the right, and use the system and app toolbars at the top and bottom respectively. It�s so simple, Ubuntu doesn�t need a home button at all.
Specialist data artists have designed Ubuntu�s welcome screen, with graphics that evolve over time to reflect your use of the phone. We�ve reinvented the inbox so you can read and respond to texts, emails and social media posts in an instant.
From mobile... to desktop. Yes, it�s the full Ubuntu desktop OS used by millions on a daily basis -- and it runs directly from the phone, so you�ll be able to move seamlessly from one environment to the other with no file syncing or transfers required. The core OS and applications are fully integrated with their smartphone equivalents, so you can even make and receive calls from the desktop while you work.
Finally, you can also boot the phone into Android. And there�s a good reason for that...

The rollout plan

As well as being a bonus for app developers and anyone with a big Android app collection, including Android on the phone means we�re able to offer full convergence at launch. On day one, you�ll be able to launch the Ubuntu desktop from within Android using our existing Ubuntu for Android app. That integration is fully functional today, as you can see from this video.

Then shortly after launch we�ll push out a free software update that adds this desktop integration to Ubuntu mobile as well. That�s the real goal we�re working towards. At that point you�ll have a leading-edge smartphone that runs Ubuntu and Android, both of which can also run a fully integrated Ubuntu desktop OS. What other phone can match that?
However you choose to use Ubuntu Edge, the incredible components will keep it running fast and fresh as our software evolves. We�ll push out monthly Ubuntu software updates to add features and polish, and we guarantee to keep supporting the phone for three years.

For developers

HTML5 apps written for other platforms can be brought over to Ubuntu with ease, and any web property can quickly be adapted to run as a web app, with its own icon and access to system services. For richer applications, use our QML toolkit for amazingly productive high-performance engineering.
But best of all, using the Ubuntu SDK you can write and upload a single native application that has desktop, tablet and phone interfaces. It�s a developer�s dream.

Technical specifications
  • Dual boot Ubuntu mobile OS and Android
  • Fully integrated Ubuntu desktop PC when docked
  • Fastest multi-core CPU, 4GB RAM, 128GB storage
  • Micro-SIM
  • 4.5in 1,280 x 720 HD sapphire crystal display
  • 8mp low-light rear camera, 2mp front camera
  • Dual-LTE, dual-band 802.11n Wi-Fi, Bluetooth 4, NFC
  • GPS, accelerometer, gyro, proximity sensor, compass, barometer
  • Stereo speakers with HD audio, dual-mic recording, Active Noise Cancellation
  • 11-pin connector providing simultaneous MHL and USB OTG
  • 3.5mm jack
  • Silicon-anode Li-Ion battery
  • 64 x 9 x 124mm

Risks and challenges

Although our core business is software for PCs and the cloud, we know the phone industry pretty well too. We�ve been working with manufacturers and carriers, so everything we need is already in place. We also have a team based in Taiwan where the bulk of the production will occur; and we have engineers around the world who have built this kind of product before. We�re well prepared for the journey ahead.
And it is going to be a journey. We�ve set such a high crowdfunding target for a good reason. Between design, certification and manufacture, the costs of building a new phone are huge -- but the more we produce, the lower the final cost of each handset. Setting such an ambitious target means a more competitive price per device.
Finally, the very nature of this concept device means the exact component list is fluid until we enter production to ensure we�re picking the best available part at the time. If we are forced to change a major feature or component, we�ll come up with something just as innovative to replace it. If you�ve backed us, you�ll be kept right up to date.

download file now

Read more »

Sunday, August 27, 2017

Ubuntu Logitech diNovo Edge Bluetooth Wireless Keyboard Part 2

Ubuntu Logitech diNovo Edge Bluetooth Wireless Keyboard Part 2


I reported on problems with Ubuntu Logitech diNovo Edge Bluetooth Wireless Keyboard, and now in Ubuntu 11.10 Oneiric and Ubuntu 12.04 Precise the problem resurfaces each time you do a fresh install or Distribution Upgrade. But the solution is slightly different than before.

Update: The problem appears in Ubuntu/Kubuntu 12.04 Precise also, but the solution is the same.

This solution is using for the Logitech diNovo Edge in Ubuntu/Kubuntu. Symptoms are the bluetooth-device-manager kept prompting me to connect to the device but nothing I did ever worked.

Here is the solution / fix for getting the keyword to work. The source for this information is here.

The problem is in the udev rules. In 11.04 there was a special line in /lib/udev/rules.d/70-hid2hci.rules for Logitech devices that started with KERNEL=="hidraw*".
These seem to be missing in default configurations. This fix adds this line into another file instead which makes things work.

Edit the file: /lib/udev/rules.d/##-bluez-hid2hci.rules (where the ## is the number on your system. Just search for the keywords bluez-hid2hci.rules in the /lib/udev/rules.d/ directory. For example, on my system in Ubuntu 11.10 it was number 62 and on Ubuntu 12.04 is was 97.)

(If you need help editing a file, see bottom section.)

Change this line:
# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]",
RUN+="hid2hci --method=logitech-hid --devpath=%p"
to
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]",
RUN+="hid2hci --method=logitech-hid --devpath=%p"
I have made the changed sections BOLD. Save the changes to the file. I also turned bluetooth off from the icon in the system tray.
After making this change, I turned on my wireless keyboard, unplugged its bluetooth dongle, plugged it back in, paired the keyword with the dongle, and a few seconds later it worked. I did not even have to reboot.
IF YOU NEED HELP EDITING CONFIGURATION FILES UNDER LINUX, please see this link: http://awesomelinux.blogspot.com/2010/09/how-to-edit-configuration-file.html

download file now

Read more »

Wednesday, August 16, 2017

Ubuntu Logitech diNovo Edge Bluetooth Wireless Keyboard

Ubuntu Logitech diNovo Edge Bluetooth Wireless Keyboard


I use the Logitech diNovo Edge in Ubuntu/Kubuntu and I love it. When I installed Kubuntu 10.04 Lucid, this wireless keyboard failed to work. The bluetooth device manager kept prompting me to connect and pair the device with a PIN but nothing I did ever worked.

UPDATE/EDIT: This problem has been reported in version dating from 10.04 to 11.04. This solution works for those, but there is a slightly different solution for 11.10.

Here is the solution / fix for getting the keyword to work. The source for this information is here.

Edit the file: /lib/udev/rules.d/70-hid2hci.rules

(If you need help editing a file, see bottom section.)

Change this line:

# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]",
RUN+="hid2hci --method=logitech-hid --devpath=%p"

to

KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]",
RUN+="hid2hci --method=logitech-hid --devpath=%p"

I have made the changed sections BOLD. I also turned bluetooth off from the icon in the system tray.

After making this change, I turned on my wireless keyboard, unplugged its bluetooth dongle, plugged it back in, paired the keyword with the dongle, and a few seconds later it worked. I did not even have to reboot.

HOW TO EDIT THE FILE (for those who need help with this stage)

New users to Linux may have trouble editing text files at first. Ill try to be simple, and this guide is for people using Gnome or KDE.

The simplest way is using a user friendly program. In Gnome (which is normal Ubuntu), the default text editor is gedit. In KDE (in Kubuntu) it is Kate. Also, this is a protected system file, so you need to use special Administrator privileges before you can edit it. Dont worry. This is simply.

KDE

In KDE, you need to find the "Run Command" option the Application menu. (The App menu is usually in the lower left-hand corner, with a colorful K-button.) In KDE4s new menu style, the "Run Command" is (currently) under the Computer section, near the top of the small list. Find the option and click it.

In the input box that displays, copy/paste the this command into it and press enter:
kdesu kate /lib/udev/rules.d/70-hid2hci.rules

The kdesu program tells the system you want to run the text editor (kate) with Admin access. You will be prompted for your individual user password, which you enter. Then kate should open with a file ready for you. (This is the /lib/udev/rules.d/70-hid2hci.rules file which we told kate to open for us.) If this file does not open, you can open it manually by going to menu File -> Open... and then navigating to the / root directory, down to lib and so on until you find the file 70-hid2hci.rules.

Edit the file as directed earlier in this article. Save the file, close the file (menu File -> Close), and then finally exit Kate.

GNOME

In Gnome, first open the Terminal through the Application menu. (The App menu is usually in the upper left-hand corner, labeled as Applications.) On my system, it is under Applications -> Accessories -> Terminal.

In the input command window that displays, copy/paste the this command into it and press enter:
gksu gedit /lib/udev/rules.d/70-hid2hci.rules

The gksu tells the system you want to run the text editor (gedit) with Admin access. You will be prompted for your individual user password, which you enter. Then gedit should open with a file ready for you. (This is the /lib/udev/rules.d/70-hid2hci.rules file which we told gedit to open for us.) If this file does not open, you can open it manually by going to menu File -> Open... and then navigating to the / root directory, down to lib and so on until you find the file 70-hid2hci.rules.

Edit the file as directed earlier in this article. Save the file, close the file (menu File -> Close), and then finally exit gedit. You can close the Terminal also.

Hope that helps.


download file now

Read more »

Saturday, August 5, 2017

Troubleshooting Lync Edge 101

Troubleshooting Lync Edge 101


We installed a "simple" Lync Edge system with collocated Front-End and Mediation server and Enterprise Voice connected to the PSTN via a Nortel CS1000 PBX.


After configuring (among other things)
  • Internal DNS
  • External DNS
  • Routing on the EdgeServer
  • Internal Certificate
  • External Certificate
  • Public IP addresses
  • Primary DNS suffix on the EdgeServer
  • Open ports on the Internal Firewall
  • Open ports on the External Firewall
  • The mediation server to find the PBX
  • The PBX with a SIP Trunk
  • The topology, exported it and imported it on the EdgeServer
  • Users with external access, enterprise voice and a valid line URI
  • A Voice Policy, PSTN Usage and Route
  • Automatic login internally and externally
and checking the configuration a few times, we could call�

External Lync <---> Internal Lync
Internal Lync <---> Mobile Phone

But not�

External Lync  ---> Mobile Phone
Mobile Phone  <---  External Lync

The signalling from the External Lync client to the Mobile phone went through, the phone would ring and we could answer the call. On the external Lync client the status shifted from "Calling" to "Connecting call", where it sat for a few seconds and finally displayed "Call failed due to network issues". This indicated that the signalling path were working fine and the problem was happening as the system tried to setup the media stream.


We then used the Lync Server 2010 Logging tool to find this error message:
"Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote"

Which led us to this post on the Lync forums: Incoming PSTN call to external user fails to connect

After investigating the logs some more we saw that the mediation server tried to establish a media path straight to the external client!? Did it not know we had an edge? - No, it actually did not!

After looking in the Lync Control Panel / Topology / Standard Edition / Mediation Server, we noticed that the EdgeServer setting were "Not Set"

With Power Shell we could check this with the following command:

Get-CsService -MediationServer

Identity                 : MediationServer:standard.kressmark.com
Registrar               : Registrar:standard.kressmark.com
EdgeServer            :
SipServerPort         : 5070
SipClientTcpPort     : 5060
SipClientTlsPort      : 5067
AudioPortStart        : 49152
AudioPortCount       : 8348
DependentServiceList : {PstnGateway:10.10.10.40}
ServiceId             : 1-MediationServer-4
SiteId                 : Site:Stockholm
PoolFqdn             : standard.kressmark.com
Version               : 5
Role                   : MediationServer

Also, in the Lync Control Panel / Topology / edge.kressmark.com / Edge Server / Dependents, we could only find �Registrar:�� and �ConferencingServer:�� and no "MediationServer:....

So our Mediation Server did not know we had an Edge, and the Edge server did not know about the Mediation server. My guess is that internal calls to PSTN worked simply because the Mediation server were collocated with the Standard server.

However, we used the following command to make things right:

Set-CsMediationServer -Identity "MediationServer:standard.kressmark.com" -EdgeServer edge.kressmark.com

And after restarting the Lync control panel it displayed correct data, and calls from the external Lync client via the collocated mediation server to PSTN worked (and the other way around as well!)

Puh!

download file now

Read more »

Thursday, February 19, 2015

Ford edge




Read more »