Wednesday, June 5, 2013

Some Reasons Why Cherry Mobile postponed their Jelly Bean Update for Flare

UPDATE: CM resumes the JB update for Flare starting on June 10 You can read the original thread of the post on Facebook. See our reminders here -June 5 2013, 11:09AM


CM Flare running Android 4.1.2 with Build Number 24


We are discussing a lot of news about the Cherry Mobile Flare on our previous articles, the All-time Favorite device –according to Cherry Mobile Page itself, and we are watching out on every news and update from the various forums, Facebook groups and users, but it remains uncertain, Is Flare will be Ice Cream Sandwich forever?
-----------------------
..NO its not!

UPDATE: CM resumes the JB update for Flare starting on June 10 You can read the original thread of the post on Facebook. See our reminders here -June 5 2013, 11:09AM




----------------------
A series of screenshots we uploaded here that showing us CM Flare running Android 4.1.2 Jelly Bean, a much sweeter update from its default OS, the 4.0.4 Ice Cream Sandwhich, that gives a lot of suggestions from the users to fix the bugs present on the device. Users are hoping that it can be fixed by the Jelly Bean update.


Bugs from the earlier build
But some users are already update their device to 4.1.2 from different Cherry Mobile service centers or Mini EB’s but they’ve found out a lot of bugs from the Build number v.24 (Cherry_Flare_V006024 to be exact) which could disappoint the users. Here’s what they’ve found out so far:
  • Rear camera error
  • G-sensor error
  • Gallery app functionality of image detection problems
  • Songs from the default Music app could not detected
  • Lux app compatibility
  • Notification vibrate, the phone is shaking always when new notifications are coming, not sure if this is a feature or a bug
  • Multi-touch bug is still there (maybe a hardware issue)
  • And many more
We couldn’t tell what other bugs are present on the build version unless we try it on our own, but then, we will not recommend Flare users to update their device to JB by your own, it may be risky and dangerous.

Devs are not recommending to do an JB update to their own, but they release a series of files so that brave users can try this out, but the docs doesn’t have any documentations, instructions given to prevent a increasing number of dead flare to be recorded. Because, in general, the build of the firmware is not yet stable, it’s now under development stage, bugs are present, but the new features are there.

The unready after-sales support

Since June 1, 2013, the date where Cherry Mobile supposed to be will update all Flares to Jelly Bean on their official service centers nationwide are cancelled.


“To all FLARE users, Cherry Mobile will postpone the release of the Jelly Bean update scheduled tomorrow June 1, 2013….Due to the HIGH NUMBER of Flare users that will go to our Service Centers, we are carefully planning the process of the said Update. It is also a consideration that we want to serve all of our valued customers in a swift and orderly manner… We will announce the new date of the update as soon as possible. Our sincerest apologies. We are doing our best to serve you better.” –Cherry Mobile on FB Fan page, posted on May 31 2013, 6:45 pm

This post is now hidden on their timeline, but we saved a link from it, maybe not only because they we’re not ready for a bulk number of customers to come on their SC, but also for the criticisms they received from this post.
-----
UPDATE: CM resumes the JB update for Flare starting on June 10 You can read the original thread of the post on Facebook. See our reminders here -June 5 2013, 11:09AM
-----
Some users are asking CM Service Centers on telephone about it but they are saying “inaaral pa namin” (We are now studying on it)

Devs from the CM Flare official users group got a copy of tools and sources from some certain friends of Cosmic. Devs can organize their own Mini EBs (Eye Ball –meetups) in their area, to reach users without a CM Service Center/Support in their area and official receipt in their hands can update their device.

Flare users thought that in order to “serve all of our valued customers in a swift and orderly manner”, Cherry Mobile maybe hiring a additional tech support personnel to do this big thing and train their new and existing tech support to reach Flare users to the highest mountain of the Philippines. It is true, many users are living in a very isolated area where no Cherry Mobile support are existing in their area, that’s why third party devs from Facebook users group are organizing some mini EB’s in their area. So, if that’s the case, why go for Over-The-Air updating process. But like we’ve said earlier, this is not possible. Let’s wait and wait and wait. As the saying goes, patience is a virtue.

PS: We are not releasing any sources from this site for JB Update. We also notice that some readers are asking for a sources of that tools and instructions from our blog, but then again, we don’t have any sources and tools to release. We reminding also Flare owners to be careful on uncertain and unstable firmware build of Jelly Bean from somewhere, whenever you get a copy of so called “final” build. And it can be risky to do it on your own, but if you are brave, try to ask Google and devs for that. CM are now working on a much flawless and sweet Jelly Bean update. Let’s wait for that.

Connect with us