Good news for everyone still waiting for the Colawe Rio W550! The company has confirmed they will be launching with higher specs!
Colawe has just updated their Facebook Page confirming that they will be upgraded the hardware of their flagship smartphone the W550 Rio. The Facebook post confirms that the Rio will now be launching with 3GB RAM and a 13 mega-pixel rear camera.
Colawe Rio W550 Features
- CNC chassis.
- Fingerprint Scanner.
- 3GB RAM.
- 16GB memory.
- 3000mAh battery.
- 13 mega-pixel rear camera.
From the poll we held a few days ago, the above details should also mean that the new retail price for the Colawe W550 Rio will now be $139.99.
Gizchina News of the week
At this stage we’re not sure when Colawe aims to launch their first phone, but it would make sense that there will be a delay as they switch supply chains. The last piece of Colawe news is the rumor that another phone, the Colawe W1000, is on the way too.
It might actually be good but I decided to go with a Redmi Note 4 which cost me $155 with shipping.
It’s not really build quality that worries me the most with these small Chinese brands ( though that does too ) but the software updates and the ROMs. With Xiaomi I know I’ll get some decent ( not great though ) level of software updates for their Redmi series.
Friend, I don’t want bother you, but unfortunately the software updates in Redmi line is not good. I am Redmi Note 3 (mtk) owner and I am stuck in android 5.0
So, based on all of my experience with this phone, I really don’t expect see Android 7 update for RMN 4.
But for the price, you make a good deal! The device is really good
Yes I know, that’s why I said Xiaomi doesn’t provide a great level of software updates but they do provide security updates and bumps to their own MIUI so it’s still decent.
That is why the Note 3 Pro will outlive the Note 4 regarding at least 3rd party ROM’s.
Well Code Aurora is the last surviver in open stuck. So in the worst case with out the source you can modify the closest device (same bord & as less as possible different peripherals) kernel source to work. Luckily Xiaomi for instance doesn’t switch the camera modules often which for instance because drivers is a headache with camera 3 API… With MTK you mainly can blow the horn all do their are & some sources (leaked & re engineered) for them but it’s far from organizing or anything.
i am REALLY REALLY sorry @lazarprodanovic:disqus , but i can’t quite understand what you are trying to say bro
can you rephrase it a bit ? i’m having trouble understanding the grammar perspective of your message.
hopefully you won’t mind
Lol Muhammad!
Firs read:
https://www.qualcomm.com/news/onq/2010/01/22/code-aurorawhat
https://www.codeaurora.org/about-us
Kernel goes per a bord (SoC), & even if the bord is the same some things differ from a device to a device, we call those things peripheral modules alike WiFi chip (all do this day’s those are SoC integrated), Bluettooth, NFC, Camera’s… Naturally every pice of the hardware (module) requires also a driver (module) so that it might work.
When you are without of the support from device manufacturer that does not release kernel source then you pick most similar device with most things exactly the same & then try to understand puzzle the places that remain (different module’s) by picking them from other device’s that have the same part until you find a working one (driver).
For instance most developers do have the camera driver & camera API (interface) problems as Google switched API for a 3rd time to “Camera 3 API” with Android N. Why is that a problem? Well because camera sensor manufacturers won’t write new drivers for older sensors that they even don’t produce anymore & without driver’s you can’t use them naturally. So it remains to patch old API & drivers so that it can work (on the lv that whose previously adapted). This is not an easy task to do as it includes additional things including camera app. For instance you have a Snapdragon camera project originally started by the Qualcomm based on the Camera 1 api that is now really legacy one but CM uses it in Cm13 (N) to provide camera functionality to many other older devices that are stuck with camera drivers only for it. Even this is QC it works with every device & SoC that are in similar positions including numerous Chinese phones with MTK SoC’s. You have flood of apps based on it this day’s for instance:
https://play.google.com/store/apps/details?id=com.fgnm.baconcamera
MTK on the other hand doesn’t provide almost nothing so you are on your own mostly. I used a turn blow up a horn as I couldn’t say blow you know what.
ah .. makes MUCH more sense now
thanks !