*Product size, product weight, and related specifications are theoretical values only. Actual measurements between individual products may vary. All specifications are subject to the actual product.
*The actual weight may vary depending on the configuration, manufacturing process, and measurement method.

SIZE


Width:

77.2 mm

Height:

158.2 mm

Depth:

8.3 mm

Weight:

Approx. 188 g


COLOUR

• Midnight Blue
  
  
• Black
  
  
• Twilight
  

5G has been a source of unrest for Huawei. The US government, worried that Huawei could build security flaw "backdoors" into 5G and other communications infrastructure, has pressured governments around the world to avoid using the Chinese giant's equipment. With 5G still a year or two away from the mainstream, Huawei has now started looking to the next generation of mobile internet.

The Chinese company is researching 6G at its R&D center in Ottawa, Canada, reports The Logic. Obviously, this is a forward-looking move on the company's part. It doesn't expect 6G to become a reality in any meaningful sense until around 2030.

Huawei was blacklisted in the US in May, with President Donald Trump additionally signing an executive order essentially banning the company in light of national security concerns that Huawei had close ties with the Chinese government. The government's fear is that the Chinese government could use infrastructure Huawei builds in the US and other countries for spying or espionage. Huawei has repeatedly denied that charge.

Trump's Huawei blacklist, which has since been reversed, meant that the company was blocked from using American products, which includes Google's Android system. Huawei last week unveiled HarmonyOS, an operating system for smart devices, like Smart TVs, car infotainment systems and more, which the company says can be used to power its phones if the US does re-block it from using Android.

Sumber : https://www.cnet.com/news/huawei-starts-...-internet/

Huawei to release a HarmonyOS on its next smartwatch as Oppo looks to join the market
14 August 2019
Following the rising demand for smartwatches lately, Oppo is planning on entering the market with its own offering according to a recent Weibo post by the company’s VP Shen Yiren. The executive shared that Oppo is hard at work on its first smartwatch which should come out sometime next year.


Shirley Yiren post on Weibo
Going into more details Yiren commented that the watch will likely come with a rectangular casing instead of a circular one for the sake of fitting more information on the screen. In addition, fans can expect to see an Oppo branded pair of noise-canceling wireless earphones before the end of this year.

In related news, Huawei is looking to bring a HarmonyOS powered smartwatch in the near future. The company’s past offerings came with its own Lite OS as well as Google’s Wear OS but neither managed to gain significant traction.


Given the shrinking market for Wear OS, Huawei believes it's the right time to test the waters with its new OS on smartwatches. The company believes its new modular operating system will give it a better shot at competing with the likes of Samsung and Apple on the smart wearables front.

https://www.gsmarena.com/oppo_looking_to...-38660.php

Much of the recent conversation around Huawei has revolved around the company’s unfortunate political situation because of a US executive order that restricted many companies from conducting business with Huawei. The repercussions of such a pivotal decision are far too enormous to not pay attention. But in an alternate reality where this executive order does not exist, Huawei would have been in the limelight for its recently revealed Ark Compiler, the latest innovation that claims to bridge the app performance gap between Android and iOS.

Before diving into what Ark Compiler is, we need to take a step back and understand what a compiler is and the purpose it serves in the Android system.

Brief History of Compilers and Interpreters on Android

A compiler is a computer program that translates code from one language into another language, often being native machine language. This can then either be executed directly by the computer or be executed through another program (interpreter). This translation is necessary because we write code in human-readable programming languages (like Java and Kotlin), while the computer only understands native machine language (binary code in the form of 1’s and 0’s). The compiler thus serves as a bridge between the instructions that a human writes and the machine’s ability to understand and then execute those instructions. How quickly and efficiently this conversion and subsequent interpretation take place defines the efficiency of the compiler, thus introducing a direct correlation between the efficiency of the compiler to the performance and efficiency of code, and by extension, apps.

Dalvik VM

In the early days of Android, the OS utilized what was called the Dalvik VM (the interpreter) along with a JIT (just-in-time) compiler. This older video from XDA TV’s Android Basics 101 series touches upon the Dalvik VM and the JIT setup, both of which served the needs of early Android systems where memory constraints were abundant. The Dalvik VM took Java bytecode and converted it into machine code as and when the code needed to be executed (hence Just-In-Time). This was necessary as storage space in phones was a real constraint back then, so this approach allowed apps to work with smaller file sizes in the system.

Compiling and interpreting apps at runtime had the drawback of overall slower app performance as the compilation would take place alongside when the user is using the app.

Dalvik also had limitations with its Garbage Collection mechanism. Dalvik kept track of each memory allocation collectively. Once Dalvik determines that a piece of memory is no longer being used by the program, it frees this memory back to the heap without any intervention from the programmer. This process is called Garbage Collection (GC), and it aims to find memory objects in a program that isn’t accessed anymore and then reclaim the resources used by those objects for freeing up memory. The system determines when a GC is needed on a collective basis, so app developers do not get to choose when GC events occur [even in ART]. So if a GC event occurred in the middle of any intensive processing activity on the foreground app, the system would pause the execution of the process and begin GC, thereby increasing processing time and introducing a noticeable “jank” to the users.

These and other constraints pushed Google to explore alternative approaches for faster performance.

Android Runtime

With Android 4.4 KitKat, Google introduced ART (Android Runtime) in preview form with an AOT (Ahead-Of-Time) compiler, and with Android 5.0 Lollipop, Google dropped Dalvik in favor of ART as the only interpreter available. ART with AOT converted code into machine language at the time of installation of the app, rather than waiting to do such conversion when the app is in use. This approach thus sped up app launch times but also introduced drawbacks in the form of slower installation times and increased disk space usage. To balance it all out, Google adopted a combination of AOT, JIT, and profile-guided compilation with ART on Android 7.0 Nougat, to ensure that no single factor is affected drastically.

ART also worked on making Garbage Collection less obtrusive. The GC process was optimized to be quicker overall with fewer pauses (single short pause versus Dalvik’s two pauses), less fragmentation, and less memory usage. Google’s presentation at Google I/O 2014 goes into better detail explaining the limitations of Dalvik’s GC and ART’s improvements on that end.

Even with these changes over the years, the basic premise of Google’s approach involved interpreting code during execution while varying the timing of the compiling (translation) element. Garbage Collection also continues to be a pain point for app developers because of its inherent interruptive and collective nature. Arguably, Android’s app performance suffers as a result as there continue to be overheads involved.

Ark Compiler by Huawei

Huawei has been working towards developing a more efficient solution and has consequently hired hundreds of experts in the field. The result of this effort is the Ark Compiler, which Huawei claims is the first-ever static compiler that allows for direct translation into machine language, completely removing the need for an interpreter. Ark Compiler was also developed with the goal of maximizing running efficiency for Java and C, so one should theoretically see the best results with these languages.

Huawei presents some key features of the Ark Compiler as below:

Compilation techniques such as AOT and JIT can convert some programs into machine code and run them directly on the CPU, but these techniques are unable to completely untether themselves from the interpreter and limitations attached therewith. The Ark Compiler utilizes static compilation, which lets it untether itself from the dynamic interpreter, opening the possibility of boosting app performance by “leaps and bounds.“

Static compilation has a potential downside of being too rigid and being unable to make adjustments that a dynamic compiler can make during execution. Huawei claims that the Ark Compiler’s static compilation resolves this “by seamlessly translating the dynamic features in the programming language into machine code.“

Existing compilation processes take place during or after installation of the app package on the mobile device. Ark Compiler is designed for deployment during software development, which we presume helps to remove time overheads during installation and execution. We presume that app developers would be able to directly compile different languages into native machine code during the app development process, and the resultant APK could thus not need interaction with an interpreter or a virtual machine to function. This would theoretically reduce the overheads related to JNI, for instance.

Ark Compiler also changes the collective nature of Garbage Collection. It allows for GC events to occur separately for different Java threads. This compartmentalized approach claims to offer less jank on foreground apps.

As a result of these changes, Ark Compiler can seemingly improve Android system operation fluency by up to 24%, response speed by up to 44%, and the smoothness of the third-party applications by up to 60%, claiming to bring Android app performance at the same level as that on iOS.

The Ark Compiler is currently compiled and optimized for ARM chip architecture. Huawei hopes that in the future, collaborative hardware and software design will work towards maximizing Kirin chip capabilities.

The Ark Compiler supports standard Java usage, allowing for the direct compilation of third-party apps without needing the app developer to make any code modification. Ark Compiler also allows for “adjustments to the code structure” for further improvements to performance and memory. Huawei has chosen to make Ark Compiler an open source system, which would allow third-party developers to adopt and adapt the technology for their needs, furthering its adoption with app developers and mobile phone manufacturers.

While Huawei does not mention any cons to the Ark Compiler, one can expect large app sizes at the very least, but this should not pose any problems on current generation devices which come with ample storage. We also expect that Ark Compiler will not be available for all CPU architectures, as Google’s compatibility woes are not Huawei’s headache. Ark Compiler is designed to be used during development and not during installation; this presents an indication that Huawei may have possibly modified how apps are deployed and installed on Android devices, and also may have worked on their own APK design. If correct, this could pose a major compatibility problem in the ecosystem, and it would be a long while before this would become a standard Android feature, if ever.

Not compiling on a user’s device also raises a big question on optimization. ART currently optimizes on a per-micro-architecture basis, meaning that the resulting binary would be different for a Snapdragon device versus an Exynos device, or even for a Snapdragon 845 versus a Snapdragon 625. This approach makes sense for manufacturers who have full control of the SoC, like Apple and Huawei. However, with the rest of the Android world using many different SoCs, forcing a generic optimization to be used across devices will be a roadblock for the standardization of the Ark Compiler, again. Consequently, do not expect Ark Compiler to arrive on your favorite custom ROM anytime soon.

For clarification, the Ark Compiler is developed to work with Android, and Huawei has mentioned nothing in relation to its alleged homebrew OS and its compatibility with Ark Compiler, so we make no presumptions on this end.

Huawei plans to hold two major conferences dedicated to developers and the larger ecosystem. These are the Huawei Device China Developers Conference and the Green Alliance China Developers Conference. Both events will address specific open source issues related to Huawei’s Ark Compiler, in an effort to make the benefits of this technology as widely accessible as possible.

Special thanks to XDA Senior Recognized Contributor Dees_Troy and Recognized Developer arter97 for their assistance and inputs.

Sumber https://www.xda-developers.com/huawei-ar...rformance/

Vodafone Spanyol bekerja sama dengan Huawei meluncurkan layanan komersial 5G di pasar Spanyol.

TEMPO.CO, Jakarta - Spanyol menjadi negara pertama di Eropa yang membuka pintu pada jaringan 5G Vodafone Spanyol yang bekerja sama dengan Huawei, sebuah perusahaan telekomunikasi raksasa asal Cina yang saat ini diblokade Amerika Serikat.

Jaringan 5G Vodafone di Spanyol pada Sabtu, 15 Juni 2019, secara komersial meluncurkan layanan ini di 15 kota, seperti Madrid dan Barcelona.

Dikutip dari rt.com, Minggu, 16 Juni 2019, melalui kerjasamanya dengan Huawei, Vodafone mencoba memberikan layanan supercepat pada jaringan telepon dan pengunduhan (download) hingga satu gigabit per detik di pasar Spanyol. Layanan ini juga akan tersedia di Valencia, Malaga, Seville, Zaragoza, San Sebastian, Bilbao, Vitoria, La Coruna, Vigo, Gijon, Pamplona, Santander, dan Logrono.   

Untuk layanan komersial ini, Vodafone menggunakan peralatan dari manfaktur Ericsson asal Swedia dan Huawei. Saat ini Huawei masuk dalam daftar hitam Amerika Serikat, dimana beberapa perusahaan asal Amerika Serikat tak boleh melakukan transaksi dagang dengan Huawei.

Sebelum Spanyol, ada dua negara di Eropa yang mengkomersialkan layanan 5G yakni Switzerland dan Inggris. Akan tetapi, Washingtong mendesak sekutu-sekutunya agar meninggalkan teknologi 5G Huawei dengan alasan keamanan. Walau ditekan Amerika Serikat, anggota parlemen Inggris belum menerbitkan larangan Huawei berpartisipasi dalam regenerasi jaringan, namun operator EE dan Vodafone Inggris sudah melepaskan Huawei dari projek 5G mereka.        

Sebelumnya CEO Vodafone, Nick Read memperingatkan memblokir Huawei dari pasar jaringan 5G di penjuru Eropa bisa menciderai operator dan konsumen. Hal ini juga bisa menghambat peluncuran layanan 5G mungkin hingga dua tahun.

“Secara struktur ini merugikan Eropa. Tentu saja Amerika Serikat akan baik-baik saja karena mereka tak pakai Huawei,” kata Read. 

Ketegangan antara Amerika Serikat dengan Huawei terjadi di tengah kemelut perang dagang negara itu dengan Cina. Amerika Serikat dan Cina adalah dua negara dengan perekonomian terbesar di dunia. Trump menuding Huawei adalah mata-mata Beijing, namun hal ini ditampik oleh perusahaan itu.

Sumber https://dunia.tempo.co/read/1215098/kesa...ign=dlvrit

Seorang analis dari Tianfeng International, yang mengungkapkan Huawei akan siap untuk mendorong smartphone tersebut beberapa waktu ke depan.

TEMPO.CO, Jakarta - Beberapa sumber Cina telah mengungkapkan bahwa Huawei siap meluncurkan perangkat dengan OS HongMeng-nya (diperkirakan akan dinamai Ark OS untuk pasar global) Oktober ini, demikian dilaporkan laman GSM Arena, Kamis, 13 Juni 2019.

Memo tersebut berasal dari Guo Mingxi, seorang analis dari Tianfeng International, yang mengungkapkan Huawei akan siap untuk mendorong smartphone tersebut beberapa waktu ke depan.

Namun, kabarnya ponsel tersebut tidak akan berasal dari seri utama Huawei Mate 30, kemungkinan akan menjadi ponsel pemula untuk pasar kelas menengah.

Menurut Global Times, OS baru dikembangkan bersama dengan perwakilan Tencent, Oppo dan Vivo juga hadir untuk menguji OS baru itu. OS baru itu diklaim sekitar 60 persen lebih cepat dari pada Google Android.

Alasan utama untuk peluncuran yang pertama kali dilakukan di Cina adalah bahwa OS tidak akan memenuhi persyaratan audiens internasional, sehingga Huawei harus sedikit mundur dengan peluncuran.

Analis itu juga meramalkan bahwa meskipun ada masalah antara Amerika Serikat dan Cina, Huawei akan berhasil melampaui 200 juta tonggak pengirimannya dari 2018. Dan juga akan mendorong antara 215 juta dan 225 juta unit, memperkuat tempat kedua di dunia, bahkan jika itu harus menunda tujuannya untuk menjadi produsen top secara global.

Sumber https://tekno.tempo.co/read/1214793/huaw...ign=dlvrit

KOMPAS.com - Posisi Huawei kini semakin sulit. Setelah terancam kehilangan lisensi Android dari Google, vendor perancang chip, ARM juga dikabarkan akan meninggalkan Huawei. ARM yang bermarkas di Cambridge, Amerika Serikat, diketahui telah menginstruksikan karyawannya untuk menangguhkan sejumlah perjanjian bisnis dengan Huawei. Dalam sebuah laporan yang didapatkan BBC, ARM akan menghentikan seluruh kontrak aktif dengan Huawei dan anak perusahaan untuk mematuhi larangan perdagangan AS yang baru-baru ini dikeluarkan. "ARM mematuhi pembatasan terbaru yang ditetapkan oleh pemerintah AS. ARM menghargai hubungan dengan mitra lama kami HiSilicon dan kami berharap untuk resolusi cepat tentang masalah ini," ungkap pihak ARM. Baca juga: Google Akan Cabut Lisensi Android Smartphone Huawei ARM sendiri adalah perusahaan perancang chip yang desainnya dijadikan sebagai dasar dari sebagian besar prosesor perangkat mobile di seluruh dunia. ARM tidak memproduksi prosesor komputer, melainkan melisensikan teknologi semikonduktornya kepada pihak lain. Dalam hal ini, Huawei juga merupakan salah satu pelanggan lisensi semikonduktor yang dikeluarkan ARM. Prosesor Kirin merupakan salah satu dari chip yang juga menggunakan rancangan ARM sebagai dasar pembuatan. Dikutip KompasTekno dari The Verge, Jumat (24/5/2019), meski ARM tercatat dimiliki oleh perusahaan asal Jepang yakni Softbank, ARM merancang desain chipnya di wilayah Amerika Serikat, sehingga mau tak mau ARM pun harus mengikuti aturan ini. Baca juga: Huawei Masuk Blacklist Amerika Serikat Seorang analis mengatakan bahwa hal ini menjadi pukulan telak bagi bisnis Huawei. Ia mengatakan kebijakan tersebut akan sangat mempengaruhi perusahaan dalam mengembangkan chip Kirin yang juga dibangun berdasarkan rancangan ARM. Selain itu rancangan ARM juga banyak digunakan pada BTS 5G termasuk milik Huawei. Keputusan ini membuat pihak Huawei angkat bicara. Meski dalam posisi yang sulit, Huawei optimistis kondisi ini akan dapat segera diselesaikan. "Kami menghargai hubungan dekat kami dengan mitra, tetapi menyadari tekanan dari beberapa di antara mereka, sebagai akibat dari keputusan yang bermotivasi politik," kata juru bicara Huawei dalam sebuah pernyataan. Baca juga: Cari Pengganti Google Play Store, Huawei Lirik Aptoide Dengan dicabutnya linsensi dari ARM, Huawei akan kesulitan untuk melanjutkan pembuatan prosesornya sendiri yang menggunakan desain ARM. "Kami yakin situasi ini dapat diselesaikan dan kami tetap memprioritaskan untuk terus memberikan teknologi dan produk kelas dunia kepada pelanggan kami di seluruh dunia," pungkas Huawei. Update: PR Manager Huawei Indonesia Bianca Resita Djemat menyampaikan bahwa Huawei telah memperoleh lisensi permanen untuk arsitektur ARMv8 sehingga dapat sepenuhnya mendesain prosesor ARM secara independen. Pengembangan chip Huawei pun disebutnya akan berlanjut di masa depan, terlepas dari faktor-faktor eksternal. Berikut pernyataan lengkap dari Huawei Indonesia: Huawei telah memperoleh lisensi permanen untuk arsitektur ARM8. ARM8 adalah set instruksi ARM 32/64-bit. Prosesor saat ini adalah produk dari set instruksi ini. Huawei menekankan bahwa Huawei dapat sepenuhnya mendesain prosesor ARM secara independen, dan melengkapi hak kekayaan intelektual, dan serta dapat mengembangkan proses ARM secara independen untuk jangka panjang, terlepas dari lingkungan eksternal. Dengan kata lain, bahkan jika ARM nantinya tidak dapat mengotorisasi instruksi ARM diatur di bawah tekanan tertentu, Huawei tidak akan terpengaruh. Tidak ada blokade secara teknis, dan penelitian serta pengembangan chip Huawei akan berlanjut di masa depan.

Artikel ini telah tayang di Kompas.com dengan judul "Chip Ponsel dan 5G Huawei Terancam Pemutusan Lisensi ARM", https://tekno.kompas.com/read/2019/05/24...isensi-arm.
Penulis : Yudha Pratomo
Editor : Reza Wahyudi