Profile cover photo
Profile photo
Kyle Manna (2bluesc)
493 followers
493 followers
About
Posts

Post has attachment
Add a comment...

Post has attachment
Add a comment...

Post has shared content
Ever wanted to download adb or fastboot without having to download the whole of Android Studio?

...but didn't want to download executables from some random warez site?

Good news this week:

https://dl.google.com/android/repository/platform-tools-latest-darwin.zip

https://dl.google.com/android/repository/platform-tools-latest-linux.zip

https://dl.google.com/android/repository/platform-tools-latest-windows.zip

These links will always return the adb/fastboot binaries currently shipping with Android Studio. No need to guess what the current version is, or update your own links: just follow these and get the latest binaries, direct from the source.

This is thanks to +Siva Velusamy and Kevin Quinn, not me.
Add a comment...

Post has attachment
Kyle Manna (2bluesc) commented on a post on Blogger.
Add a comment...

Post has shared content
Why there aren't Qualcomm processors in Chromebooks? Because Qualcomm doesn't support open source.
One difficulty is Qualcomm's reluctance to open-source and upstream the various drivers that make up Linux support for the embedded devices. If Qualcomm doesn't demonstrate ongoing support for their devices in the Linux kernel, then Google (or a Chromebook OEM) would best significant engineering risk if an update needs to be made in the future. Qualcomm seems to prefer the business model of Android where they can "ship it and forget it".
Add a comment...

Post has shared content
UPDATE: As of this morning we have lost DNS routing to our domains and Gerrit is now offline - with little doubt as a reaction to our blog post yesterday. The blog post in its entirety is pasted below.

A fork in the road

Last week, we released the final CM-13.0 releases, updated to the latest security patches, in anticipation of what follows.

Yesterday, Cyanogen Inc (Cyngn) announced that they were shutting down the infrastructure behind CyanogenMod (CM). This is an action that was not unpredictable given the public departure of Kondik (cyanogen himself) from the company, and with him our last remaining advocate inside Cyngn’s leadership.

In addition to infrastructure being retired, we in the CM community have lost our voice in the future direction of CM – the brand could be sold to a third party entity as it was an asset that Kondik risked to start his business and dream. Even if we were to regroup and rebuild our own infrastructure, continuing development of CM would mean to operate with the threat of sale of the brand looming over our heads. Then there is the stigma that has grown to be attached to anything named ‘Cyanogen’. Many of you reading this have been champions of clarifying that the CM product and CyngnOS were distinct, yet the stain of many PR actions from Cyngn is a hard one to remove from CM. Given CM’s reliance on Cyngn for monetary support and the shared source base, it’s not hard to understand why the confusion remains.

It will come as no surprise that this most recent action from Cyngn is definitely a death blow for CyanogenMod.

However, CM has always been more than the name and more than the infrastructure. CM has been a success based on the spirit, ingenuity and effort of its individual contributors – back when it was Kondik in his home, to the now thousands of contributors past and present.

Embracing that spirit, we the community of developers, designers, device maintainers and translators have taken the steps necessary to produce a fork of the CM source code and pending patches. This is more than just a ‘rebrand’. This fork will return to the grassroots community effort that used to define CM while maintaining the professional quality and reliability you have come to expect more recently.

CM has served the community well over its 8 long years. It has been our home, bringing together friends from all over the world to celebrate our joy of building and giving. Its apt then that on this Eve of a holiday we pay our respects. We will take pride in our Lineage as we move forward and continue to build on its legacy.

Thank you & Goodbye,
The CyanogenMod Team
Add a comment...

Post has attachment
I hope this fixes the USB-C charging issue with the 2A@9V charger included with the Google Pixel where the phone requires a restart to charge with this charger, yet works fine with other non USB PD chargers.
Add a comment...

Post has attachment
Amused that the public domain C library #PDCLib is hosted on Bitbucket instead of +GitLab. Still Awesome! http://pdclib.e43.eu
Add a comment...

Post has shared content
Issues with included fast charger?

The other day I ran in to an issue where the stock 18W charger wouldn't charge my Pixel phone. Every other USB Type-A to Type-C worked fine though and the 18W charger even worked with the Type-A to Type-C adapter. My 15W Nexus 5X Type-C charger charged the Pixel just fine. The Nexus 5X charged via the Pixel charger without issue as well. Then to finish the plug-all-the-things adventure I saw that my phone wouldn't charge off my Dell XPS 15 or even appear as a USB device.

In short, all the chargers work, but the new USB-C only charger and laptop didn't charge the Pixel.

Called Google support and screwed around. They wanted to send me a a new charger and do some billing juggling. I declined and I tried to tell them it doesn't seem to be the charger.

After I hung up I power cycled my phone and everything charged and the laptop sees the device. Today it happened again and was resolved just as quickly: reboot the phone.

This leads me to suspect that the charger chip (appears to be Qualcomm SMB1350 with QC 3.0) in my Pixel is flakey or if all the SMB1350s are flakey.

Anyone else experience similar issues? Since Quaclomm treats all its datasheets like gold, I can't find any real details on the SMB1350. Is this a dedicated chip, does it have firmware? Is this going to plague my the next 2 years of owning a Pixel? Or, is my Pixel a failing magic butterfly?
Add a comment...
Wait while more posts are being loaded