10
Feb
vibrant-official

T-Mobile Samsung Vibrant Returns To The List Of Supported CyanogenMod Devices As The Emergency Dialing Bug Gets Squashed

Posted by in Development, News, Samsung, T-Mobile, Vibrant

Back in December of 2011, the T-Mobile Samsung Vibrant was canned by the CyanogenMod team due to a 911 emergency dialing bug that was considered crucial and unfixable:

We are no longer supporting the Vibrant due to the inability to dial 911. We consider the issues related to this unresolvable without source code from Samsung related to the Radio interface layer and its interactions with the Audio layers and have taken the decision to no longer support this. We apologize for the inconvenience and strongly suggest that Vibrant users use a Samsung ROM due to the 911 issues with any ROMs based on open source code.

10
Feb
cm_thumb

CyanogenMod 7.2 RC1 Changelog Goes Live, New Device Support, Various Bugfixes, Improvements, And A Few ICS Backports Coming Soon?

Posted by in Development, News

Though it has yet to be officially acknowledged on the CyanogenMod blog (and Cyanogen himself posted an official progress update on CM9 just a few days ago), it appears that CM7.2 Release Candidate (RC) 1 is nearly here - an official changelog has been posted to the CM source review.

The official changelog, courtesy of redditor MikeEx:

  • New devices: Samsung Galaxy Ace, Mini, and Epic 4G (slider). LGE Optimus Black, 3D, Hub, Pro, Sol, and One. Motorola Atrix. Sony Ericsson Xperia Live, Pro, and Active. Huawei U8150

  • Common: ICS telephony fix backports - Spencer Oliver

  • Common: ICS Transition effects backport - Russ Underhill

  • Common: ICS Rotation effects backport - Tanguy Pruvot

  • Common: Lockscreen updates and new styles - Andrew Sutherland, Danny Baumann, Danesh M, Sven Dawitz

  • Common: Fix color banding in Gallery while displaying 32bpp images - Sang Tae Park

  • Common: T9 predictive Phone dialer - Danesh M, Pawit Pornkitprasan

  • Common: ADB over network

  • Common: Updated translations - (everyone)

  • Common: Media player and recorder fixes for a number of corner cases - CAF, Danny Baumann

  • Common: Profile resets - Ladios Jonquil

  • Common: Assorted Wifi fixes

  • Common: Control haptic in quiet hours - Danesh M

  • Common: Bluetooth MAP support - Jonathan Bensen

  • Common: Support for Bluetooth GPS dongles - Cuong Bui

  • Common: Better support for mouse and usb keyboards - Emilio Lopez, Tanguy Pruvot

  • Common: Fix timezone detection in Hawaii - Warren Togami

  • Common: Allow photo storage selection when possible - Greg Kochaniak

  • Common: Improved Calendar reminder options - Danny Baumann

  • Common: Improved AVRCP 1.3 compatibility

  • Common: Improved external keyboard and mouse behaviour on some corner cases - Tanguy Pruvot

  • Common: Status bar battery icon configuration - Simon Davie

  • OMAP Common: Support for recent OMAP3/OMAP4 devices - omapzoom

  • p990: Add FM Radio support

  • p990/p999: fix background calls, fix HDMI output in 1080p

  • zeppelin, morrison, motus: Fixed camera zooming issues

  • Samsung Galaxy S devices: Add tv-out

  • Samsung Galaxy S devices: Device specific settings section

  • Samsung Galaxy S GSM devices: Fix emergency dialing

  • Several devices: Fix device identification on Android Market: crespo, jordan, blade, v9

Nothing especially groundbreaking, though there are plenty of nice features in there - likely enough so to hold those more cautious users who are uncomfortable flashing kanged CM9 builds in lieu of the real thing.

07
Feb
image

HP Finally Gives Up Touchpad's Android Kernel Source (From Touchpads Caught Running Android In The Wild)

Posted by in Android OS, Development, HP, News, TouchPad

Remember back when an HP Touchpad was spotted running Android out of the box? Well, it would appear that after some cajoling, the CM team (in association with an attorney) have convinced HP to release the Touchpad's Android kernel source, along with a couple of other GPL components specifically modified for Android-powered Touchpads accidentally released to the wild. In addition to the kernel, HP released code to androidvncserver and i2c-tools. The only thing missing, according to Green (part of the CM team), is the Wi-Fi driver. Green explains this in an announcement on the RootzWiki forums:

I did some digging around and it appears that the wifi driver shipped with both webOS and with the Android are GPL, there are multiple evidences of that including the driver licensing string.

07
Feb
CyanogenMod[1]

CyanogenMod 9 Update: Fewer Superfluous Features, Potentially Longer Wait

Posted by in Android OS, Development, Ice Cream Sandwich 4.0, News

Steve Kondik (aka Cyanogen) put out a public update to the situation with CyanogenMod 9 earlier today, and revealed a few interesting tidbits about Team Douche's progress. Here's a few excerpts we thought were particularly important:

Android 4.0 contains many internal changes that require updated graphics drivers. Unfortunately, these drivers are almost always closed-source and don’t appear until a device or devkit is released with them. For many devices, our hands are tied...

We’ve eliminated the CMParts app, instead choosing to add our custom features directly into the main settings. We are also taking a “just works” approach when it comes to configuration- CM7 had too many options that just weren’t widely used...

07
Feb
2012-02-07 13h29_16

[Updated: Here Are The Winners!] Book Giveaway #14: Use Your Web Developing Skills To Create Android Apps With "Building Android Apps With HTML, CSS, And JavaScript"

Posted by in Contests / Giveaways, Development
Last Updated: February 15th, 2012

You're already a web developer, master of HTML, CSS, and JavaScript. You have a great idea for an Android App, but your particular skill set doesn't help you create that app. Or does it? O'Reilly media just released a 176-page 2nd edition of "Building Android Apps with HTML, CSS, and JavaScript" by Jonathan Stark and Brian Jepson that explains how to do just that.

This contest is now over. Here are our winners, selected at random:
  • Simmy
  • Daniel Harris
  • Geremy Hamlett
  • superkrrk
  • John Halbert

Congratulations, guys - all of you will be contacted for your information in the near future!

06
Feb
andevcon3_125x125

[Updated: Here Are The Winners!] AnDevCon III Is Happening May 14-17 In The SF Bay Area, Get Your Tickets Early (Or Score A Couple From Us)

Posted by in Contests / Giveaways, Development, News
Last Updated: February 18th, 2012

The newest iteration of AnDevCon (Android Developer Conference) is creeping up on us, and if you want to save some serious cash, now is the time to register. While the event doesn't actually kick off until May 14, 2012, you can stick a solid $550 back in your pocket by picking up your tickets before March 2 - a pretty substantial savings. Unless you don't like saving money, of course.

This contest is now over. Here are our winners, selected by the AP/AnDevCon committee:
  • Chainfire
  • Jesse Chen

Congratulations, guys - you will be contacted for your information in the near future!

04
Feb
image

[Updated: Here Are The Winners!] Lightning Giveaway: Win 1 Of 20 Free ClockworkMod Touch Recovery Codes For ROM Manager

Posted by in Contests / Giveaways, Development

If you want to install the ClockworkMod Touch recovery on your Android device, there are currently two ways of doing so:

The Giveaway

Today, we're giving 20 of you a chance to enable the latter in your ROM Manager for free. The giveaway is short and sweet - it'll end tonight, and all you need to do is leave a comment.

We're also testing a new giveaway management tool by Rafflecopter, which you will hopefully like.

03
Feb
cropped

ClockworkMod Touch Recoveries Now Out For All Flavors Of Samsung Galaxy S II, Epic 4G; Motorola Cliq; LG Optimus Black, 2X, 3D; HTC Rezound, G2, MT4G

Posted by in CLIQ / DEXT (Morrison), Development, Epic 4G Touch, G2 (Vision), Galaxy S II, HTC, LG, Motorola, myTouch 4G (Glacier), News, Optimus 2X (Star, p990), Optimus 3D (p920) / Thrill 4G (p925), Optimus Black (p970), Rezound, Samsung

The work to bring touch-enabled recoveries to all supported ClockworkMod devices continues, and since the last update a couple of days ago, the following devices now have ClockworkMod Touch available:

  • Non-US Samsung Galaxy S II
  • Sprint Samsung Galaxy S II Epic 4G Touch
  • AT&T Samsung Galaxy S II
  • T-Mobile Samsung Galaxy S II
  • Samsung Epic 4G (looks like this one disappeared shortly after due to some bugs)
  • Motorola Cliq
  • LG Optimus Black
  • LG Optimus 2X
  • LG Optimus 3D
  • HTC Rezound
  • HTC G2
  • HTC MyTouch 4G

This article deals with a couple of advanced topics. If you’re unfamiliar with some of the terms, hit up our primers here:

31
Jan
cropped

[Updated] Koush Adds ClockworkMod Touch Recovery Support To HTC EVO 4G, EVO 3D, Desire, Desire HD, Sensation, Thunderbolt; Motorola Atrix 4G

Posted by in Atrix 4G (Olympus), Desire (Bravo/BravoC), Desire HD (Ace), Development, EVO 3D (Shooter), EVO 4G (Supersonic), HTC, Motorola, Sensation / Sensation 4G (Pyramid), Thunderbolt (Mecha)

Koushik Dutta, the mastermind behind ClockworkMod recoveries and other goodies, has been hard at work today after releasing the initial beta versions of the new Touch iteration of CWM for the Nexuses. "What was he doing?" you may ask. Adding support for more devices, one by one. They are, as of this moment:

  • HTC EVO 4G
  • HTC EVO 3D (CDMA/GSM)
  • HTC Desire GSM
  • HTC Desire HD
  • HTC Sensation
  • Update #1: HTC Thunderbolt added
  • Motorola Atrix 4G
  • and, of course, Galaxy Nexus (CDMA/GSM) and Nexus S/S4G that we already knew about

This article deals with a couple of advanced topics. If you’re unfamiliar with some of the terms, hit up our primers here:

31
Jan
image

Blackberry's Playbook OS 2.0 Will Support Android Apps After February 6th, RIM Provides Helpful Tips On Assuring Acceptance To App World

Posted by in Android OS, Applications, Development, News, RIM

RIM, in the official BlackBerry developer's blog, announced today that Blackberry Playbook's OS update to version 2.0 will bring compatibility with Android applications. RIM's post has several helpful tips for developers looking to bring their creations to the Playbook, offering some recommendations for ensuring your approval into BlackBerry App World:

  • Before submitting your Android application to BlackBerry App World, please make sure to remove all mention of the word “Android” from your application. Both in the application description and the application itself.
  • Please remove all links to Android Market from within your application.
  • When submitting your Android application to BlackBerry App World, please make sure to select a minimum BlackBerry PlayBook OS of 2.0.

Page 27 of 86«First...1020...2526272829...405060...Last»