Firmware: Chameleon (1.0.41) Firmware [18 APR 2016] | Gecko (20151106) Firmware [13 NOV 2015]


Post Reply 
Support for Android 5 (Lolipop) coming in Q1 2015
02-03-2016, 11:49 AM
Post: #61
RE: 20160121 (1.0.40) - Beta Open Hour Chameleon Android Firmware
(02-03-2016 10:01 AM)Willem55 Wrote:  Please explain to me how to build and compile a OS when even the Hardware specific drivers for the current OS are faulty.
Nice statement from you to hear, that the current chameleon is "faulty" and until now not working proper.
For the Chip itself, the RK3288, rockchip have already all "drivers" in Lollipop, baybe with the same faults as on Kitkat.
If you read through freaktab, most RK3288 boxes are on Lollipop. So we can only win - get the new OS and maybe better drivers since no one cares now about kitkat.
Find all posts by this user
Add Thank You Quote this message in a reply
02-03-2016, 01:41 PM (This post was last modified: 02-03-2016 04:49 PM by GFORCE100.)
Post: #62
RE: 20160121 (1.0.40) - Beta Open Hour Chameleon Android Firmware
(02-03-2016 10:01 AM)Willem55 Wrote:  Please explain to me how to build and compile a OS when even the Hardware specific drivers for the current OS are faulty.
The way I see it the OS comes from RockChip as they need to provide part of the code.

Android is just a common core and presentation layer for a multitude of operating systems build for a great variety of hardware platforms.

Some of these days a very sincere and wise Android developer will post facts regarding how it really is with Android from a developer's perspective. Until such day happens I'll suggest what he/she'll may write in due course.

1) Android has versions just as Windows, Linux, Ubuntu etc. Various versions of Android support various CPU architectures. i.e. Android 4 supports ARMv7 and Android 5 & 6 ARMv8.
2) ARM CPU architectures are developed by a British company by the same name, which also manufactures its own series of CPU's based on these architectures. Your smartphone probably has an ARM processor, maybe even your car (depending on its age and class).
3) ARM (the company) also licenses its CPU architectures to 3rd parties, of which Rockchip is an example
4) Rockchip, Sigma, HiSilicon etc. designs a SoC around a given CPU architecture as above, i.e. based on the ARM license, which requires that their own designs are 100% compatible with the ARM architecture that they've licensed from ARM (i.e. ARMv7)
5) ARM (the company) will provide a HAL (Hardware Abstraction Layer) Kernel so that Android and other OS's can interface with the CPU based on its own architecture (i.e. ARMv7).
6) If Rockchip, Sigma, HiSilicon etc. so choose to implement additional features inside their i.e. ARMv7 compatible SoC's (System on Chip - more than just a CPU, usually features also a GPU and I/O) then they must provide their own revamped HAL (Hardware Abstraction Layer) such that Android (or any other OS) can also interface these features from code (this essentially means programmers can access these new instructions in software).
7) If a company such as Cloud Media selects to use other components in its media player design, that is other than those provided by ARM (specifically derived from a licensed architecture from ARM) then the company that has designed such component will provide any necessary drivers to enable its OS integration (i.e. they are the ones responsible). As the Open Hour Chameleon uses a PowerVR G6110 GPU designed by another British company by the name of Imagination Technologies, it is them (Imagination Technologies) who provide the drivers to Cloud Media, and then Cloud Media compiles the OS (i.e. Android) with those drivers.
8) Kodi and other software compiled for Android or other OS's also make reference in code to the ARMv7, ARMv8 instruction sets.
9) A company such as ARM will issue guidelines to both its ARM architecture licensees and developers using ARM processors in their designs (i.e. smartphone manufacturers) in how best to implement code that is a) recommended (i.e. does not use depreciated instructions) and b) optimised for best performance. It is up to their B2B clients (i.e. Rockchip among others) to adhere to such knowledge-base to best serve its clients.
10) Sometimes ARM finds errata in its architectures and/or ARM architecture based CPU offerings. If so it will issue microcode updates where possible. This is the firmware of the actual CPU. Sometimes CPU errata cannot be fixed in software, in which case a new hardware revision will be released. This is no different than what Intel and AMD have been doing for years. Some errata are never fixed, but these are usually non-critical bugs.
11) Is is up to the system provider (i.e. Cloud Media) to implement system components (both hardware and software) in accordance to the above. First and foremost testing is key. It's often that system providers (also called solution providers) often bypass testing, or limit software testing because it costs considerable money to conduct full-on software testing. If bugs are found it also slows down release of products to market, which makes financial managers unhappy, because it means limiting revenue and essentially net income (among others). It also means the marketing department has less to do, or is forced to increase its efforts to mask the appearance of shortfalls (both outcomes aren't preferred). The business eco-system merry-go-round never stops. Business managers don't understand bugs, all they want is the business to earn money. To a business manager IT departments are seen as a cost centre. Developers understand bugs, yet they aren't overly concerned with the business making money (so long as they get paid). Very often these "departments" do not see eye to eye and friction develops behind closed doors. The end user usually is left to pick-up the pieces. Something along these lines in my opinion is also unfolding within Cloud Media.

...and so forth.

Android is already at version 6. Version 5.1 is now mature, stable. As I have mentioned elsewhere on this forum, Rockchip's RK3368 SoC supports and runs Android 5.1 just fine as I know from using it. Drivers for PowerVR G6110 also exist (I have yet to find someone complaining they don't). If RK3368 works with Android 5.1 then so will RK3288. They are the same SoC except for core count and CPU frequency. Both are also ARMv7 compliant.

Software testing isn't just to find bugs, it's to understand why bugs occur. Without the latter it's much harder to fix bugs. Go to a doctor and he/she will ask you about your symptoms, or escort you to given tests of your health. Go to a mechanic with your car, he will first diagnose what part is failing, and only then recommend replacements. Go to a job interview and they will try to ascertain your credentials, and only then offer verdicts as to your suitability to the given position(s). Software is no different, except its much more involving and detailed due to its innate complexity, especially with various components, architectures and versions thrown into the mix etc. You wouldn't fly a plane in which its software wasn't extensively tested before taking off. Even if you use media players knowing too well that bugs may occur, you would still wonder why is it more common in company A than company B.

It is my personal opinion that Cloud Media would probably be pleased (i.e. benefit) once they port to Android 5.1.
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 2 users say Thank You to GFORCE100 for this post
02-03-2016, 04:45 PM (This post was last modified: 02-03-2016 04:51 PM by chris57.)
Post: #63
RE: 20160121 (1.0.40) - Beta Open Hour Chameleon Android Firmware
I just don't think it's that easy for CM just to upgrade Android on the RK3288 SoC. for one the SDK for the RK3368 is much more mature.
Then there is the economics of investing development resources in a SoC that never took off commercially and was for them a fling with a new SoC manufacturer that was not.. let's say very productive.

Will they upgrade the Chameleon to Android 5 or 6...? I don't know, but then I even doubted they would ever come out with the fixes from januari 26.

Our luck is they kept their android developers on board for the A-500 Pro Sigma SoC based that is supposed to get a dual boot to Android.
As long as they keep an eye on FreakTab and Rockchip on GitHub we might get lucky.

Some focus on problems and faults others on solutions and success... no question who is the happy one.

Chameleon 16GB SD 32GB micro SD <-->HDMIv1.3<-->Onkyo TX-NR1010<-->HDMIv1.3<-->Panasonic TX-P46S10 + 6 Bowers & Wilkins speakers.
10 NTFS 2TB USB drives on 3 hubs attached to a A400, 2 Seagate blackarmour NAS 3TB, 2 Seagate Central NAS 4TB.
Find all posts by this user
Add Thank You Quote this message in a reply
02-03-2016, 05:26 PM
Post: #64
RE: 20160121 (1.0.40) - Beta Open Hour Chameleon Android Firmware
(02-03-2016 04:45 PM)Willem55 Wrote:  I just don't think it's that easy for CM just to upgrade Android on the RK3288 SoC. for one the SDK for the RK3368 is much more mature.
Then there is the economics of investing development resources in a SoC that never took off commercially and was for them a fling with a new SoC manufacturer that was not.. let's say very productive.

Will they upgrade the Chameleon to Android 5 or 6...? I don't know, but then I even doubted they would ever come out with the fixes from januari 26.

Our luck is they kept their android developers on board for the A-500 Pro Sigma SoC based that is supposed to get a dual boot to Android.
As long as they keep an eye on FreakTab and Rockchip on GitHub we might get lucky.

As of now (i.e. maybe this will change) I'm not quite sure how you end up with the conclusion that the SDK for RK3288 is a) different to the SDK for RK3368 SoC and b) less mature than the SDK for RK3368 SoC. The only differences I can see are that of the GPU (TI-764 vs PowerVR G6110) because the core count and frequency is transparent to a developer. Maybe you know something that others don't, in which case please share and spill the beans Smile

Perhaps you're right, maybe Cloud Media is regretting their choice of who they decided to deal with when it comes to SoC choice for the Open Hour Chameleon. I say maybe purely because Cloud Media as a company are very tight lipped, perhaps even too much for their own good (i.e. they would benefit PR wise if they communicated certain aspects far better). At the end of the day end users may or may not take that into account, but most consumers don't feel sorry for a company unless they have a past history of supporting them, and especially if they are fanboys. What end users will likely ask themselves on average is, okay which company offers the best media player solution, how much does it cost, and where can it be bought. If people see that other Rockchip based media players are more refined then they'll proceed to the checkout (offline/online) in that direction. If on the other all Rockchip based media players showcase the same flaws then that's when a company such as Cloud Media may feel more at ease, except that it's not much consolation if a company has a product it has invested $$$ into and isn't selling very well. At such times it's usually not very pleasant to work as a Product Manager in such company Smile As the saying goes, success is that of many fathers, albeit failure is always that of one.

With all things said I too say - fingers crossed. Being realistic however my expectations aren't very high. Very simple errors such as all the translation quirks (Singlish vs English) should have been fixed looooong ago, but they aren't. I guess $50-100 is a lot of money for Cloud Media to go on proz.com, post a job request, find a translator/proof reader, agree a price, send their XML (or whatever format) files over and get it done. At one point I was even thinking of offering to do it for Cloud Media, but I kind of lost interest given they don't wish to "connect" with their community. I am sure that other such jobs could be achieved here by other forum members, i.e. to re-design the UI menus, perhaps redesign some icons, images etc. This forum is probably full of many talented people (perhaps not developers yet people or other talents and traits) who would be happy to help (even if it can be a little strange for a company to be asking the public for help). After all a company is only as good as the people that run it, this is true whether one refers to the CEO or tea lady. It's team work that makes a company great. Great people can do great things and like I say, this forum is no different. All for one and one for all Smile
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 1 user says Thank You to GFORCE100 for this post
02-03-2016, 06:35 PM (This post was last modified: 02-03-2016 06:42 PM by Willem55.)
Post: #65
RE: Support for Android 5 (Lolipop) coming in Q1 2015
here is the SDK for RK3368 https://www.mediafire.com/folder/4ojpuo3...8_SDK_0713 10GB
here is the SDK for RK3288 https://bitbucket.org/T-Firefly/firefly-rk3288 4GB
or here if you want to stick with Tronsmart https://mega.nz/#!1t8HVIYK!RqifnmnsJ8ADp...pO8QfRlHKs 5.1GB

nuff beans shared.. enjoyWink

Some focus on problems and faults others on solutions and success... no question who is the happy one.

Chameleon 16GB SD 32GB micro SD <-->HDMIv1.3<-->Onkyo TX-NR1010<-->HDMIv1.3<-->Panasonic TX-P46S10 + 6 Bowers & Wilkins speakers.
10 NTFS 2TB USB drives on 3 hubs attached to a A400, 2 Seagate blackarmour NAS 3TB, 2 Seagate Central NAS 4TB.
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 2 users say Thank You to Willem55 for this post
02-04-2016, 04:10 PM (This post was last modified: 02-04-2016 05:00 PM by GFORCE100.)
Post: #66
RE: Support for Android 5 (Lolipop) coming in Q1 2015
(02-03-2016 06:35 PM)Willem55 Wrote:  here is the SDK for RK3368 https://www.mediafire.com/folder/4ojpuo3...8_SDK_0713 10GB
here is the SDK for RK3288 https://bitbucket.org/T-Firefly/firefly-rk3288 4GB
or here if you want to stick with Tronsmart https://mega.nz/#!1t8HVIYK!RqifnmnsJ8ADp...pO8QfRlHKs 5.1GB

nuff beans shared.. enjoyWink

Thanks for posting those SDK kit links. These SDK's are indeed different. My apologies for my earlier comment, which suggested quite the opposite (even if to account for ignoring the different GPU component as found in RK3288 and RK3368 SoC's).

Upon further scrutiny I see where my mistake lies, though there is also light at the end of the tunnel per se, and as such while my comment was far-fetched, it's not entirely misplaced. Allow me to shed my thoughts on the matter as to why...

My grand error stems from the fact I looked upon the RK3288 and RK3368 SoC as both ARMv7 architecture based SoC's. The truth speaks otherwise, i.e. the RK3288 is a native ARMv7 CPU/SoC while the RK3368 is a native ARMv8 CPU/SoC. The good news is that upon further research besides relatively minor hardware differences, RK3368 includes a full ARMv7 compatibility strap allowing it to run ARMv7 code as if it was a true AMv7 CPU/SoC. Furthermore if we look at Kodi, we learn that all Kodi code (specifically the build for Android) as of present is pure ARMv7 code. Kodi from my understanding won't support ARMv8 until Kodi 17 at the earliest.

Insofar as ARMv7 compatibility of the RK3368 goes, I can confirm that the Kodi build found in the latest OHC 1.40 Beta firmware works without fail (i.e. new errors don't appear in contrast to what is the case when this same build is run on OHC - though more people would need to test this) on RK3368, which is forcing use of its ARMv7 emulation mode. People with RK3368 players and extensive sound setups (i.e. external sound decoders for pass-through testing) would ideally be required to perform further testing, as always. One should also note that RK3368 players are Android 5.1 based as oppose to Android 4.4.2 of the OHC.

What does this all mean in lame man terms?

The below is all true (unless I stand corrected):
1) RK3268 and RK3368 all support ARMv7, either natively or via emulation
2) All Kodi code is pure ARMv7 (i.e. no new features of ARMv8 are used at present)
3) Kodi found in OHC 1.40 Beta firmware works the same if not better on Android 5.1 than on Android 4.4.2 (i.e. feels more refined)
4) There are no new compatibility issues that crop up when running custom Kodi between these platforms (integration is seaming-less)
5) All Rockchip codecs found in custom RockChip Kodi builds conform to ARMv7 specifications

What else?
- USB 2.0 controller is part of the RK3288 & RK3368 (very likely identical - i.e. no drivers change necessary)
- Ethernet controller is part of the RK3288 & RK3368 (very likely identical - i.e. no drivers change necessary - same as above)
- Drivers for TI-764 and PowerVR G6110 differ between the two (need to be changed before compiling Android)
- Drivers for Bluetooth need to be added (integrated before compiling Android) unless this is the same ordeal as regarding the USB 2.0 and Ethernet controllers as mentioned above
- Drivers for OHC specific USB Wifi dongle need to be added (integrated before compiling Android)
- OHC UI code is generic, i.e. will work on any Android version probably as far back as Android 2.0 (can be converted to Android 5.1 easily)
- OHC installed Apps will probably also work on Android 5.1 without issue - if not newer versions can be downloaded given these are 3rd party Apps (Cloud Media didn't write these Apps but instead chose to use off-the-shelf 3rd party Apps). Is anything except the OHC UI written by Cloud Media? (please prove I'm wrong)
- There is no show stopping compatibility information as I see in Android 5.1 relating to ARMv7 code other than a remark as found on page 11 of the Android 5.1 Compatibility Definition document.

With all that said Android 5.1 should work fine on OHC bar minor build differences relating to drivers (most importantly of the GPU). Since Cloud Media are waiting on new custom Kodi builds to head their way, they can at least use developer resources by starting the shift to Android 5.1...........or if that doesn't tickle their fancy for whatever "other" reason, then pursue the march onto fixing other lesser bugs such as: a) translation errors, b) allowing deleting previously added shortcuts to the UI menu, c) changing the style and navigation of the installed Apps list so as to limit forcing scrolling to specific Apps each time (especially if their names start with letters towards the end of the alphabet) etc.

It would appear the below is how Cloud Media can proceed in the context of offering OHC technical support:
1) Make the move to Android 5.1
2) Fix various other non-Kodi related bugs
3) Concentrate on releasing new OHC firmware with newer custom Kodi builds either received directly from Rockchip, or copied from firmware of other competing media player brands
4) Wait for Kodi to include native Rockchip codecs (expected in future "standard" Kodi releases)
5) Do nothing of substance (i.e. give up and let competition eat them for breakfast hehe)

I would personally vote for (1) and (2). (3) is already is the norm. (4) is about the same as (3). (5) is the road to bankruptcy, or at least bleeding cash flow.

(1), (2) and (3) are not only logical but rational in my opinion. One person can be wrong, a few might be mistaken, but when a large audience thinks the same it's usually indicative of the general atmosphere regardless whether we make reference to politics, business ideas, OHC, or even best tasting beer Smile
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 2 users say Thank You to GFORCE100 for this post
02-04-2016, 08:09 PM (This post was last modified: 02-04-2016 08:15 PM by Willem55.)
Post: #67
RE: Support for Android 5 (Lolipop) coming in Q1 2015
I agree it's all doable, but I think their first priority now is android on the Sigma SoC in the A-500Pro and for the Chameleon just follow whatever the competition does on their RK3288 players with regards to fixes and upgrades.
As far as breakfast and cashflow goes VTEN and Gecko are doing fine and the focus is on the A-500Pro best of both worlds that will find it's way to a budget VTEN2G.

I don't think they sold a lot op Chameleons.. my guesstimate is that it's less than 1% of there total current operational players install-base.

Some focus on problems and faults others on solutions and success... no question who is the happy one.

Chameleon 16GB SD 32GB micro SD <-->HDMIv1.3<-->Onkyo TX-NR1010<-->HDMIv1.3<-->Panasonic TX-P46S10 + 6 Bowers & Wilkins speakers.
10 NTFS 2TB USB drives on 3 hubs attached to a A400, 2 Seagate blackarmour NAS 3TB, 2 Seagate Central NAS 4TB.
Find all posts by this user
Add Thank You Quote this message in a reply
02-06-2016, 04:12 PM (This post was last modified: 02-06-2016 04:16 PM by pipor.)
Post: #68
RE: 20160121 (1.0.40) - Beta Open Hour Chameleon Android Firmware
(02-02-2016 06:54 AM)tosh123 Wrote:  
(02-01-2016 10:54 PM)locki Wrote:  
(02-01-2016 09:31 PM)pipor Wrote:  
(02-01-2016 05:18 PM)pipor Wrote:  netflix on 1.0.40 is fullhd ( 1080p ) or not?
No one knows I ?

maximum is 480p because no hw certification ... it never will works on OHC...

https://en.wikipedia.org/wiki/List_of_Ne...le_devices

why?

http://www.digitaltrends.com/home-theate...d-netflix/

Looks like other boxes have a modded Netflix until 1080p/24
http://forum.kodi.tv/showthread.php?tid=238923

[EDIT]
file for testing seems to be here:
https://drive.google.com/file/d/0B9ExZCB...FDQUE/view
there is for Lollipop
Find all posts by this user
Add Thank You Quote this message in a reply
12-29-2016, 10:25 AM
Post: #69
RE: Support for Android 5 (Lolipop) coming in Q1 2015
From Kodi Faq...
Kodi v17 now requires that Android devices run Android 5.0 or later.
On the chameleon we have android kitkat 4.4 :-(
Kodi v17 (Krypton) FAQ
I hope wll they upgrede chameleon to android 5 or 6... :-)
Find all posts by this user
Add Thank You Quote this message in a reply
01-08-2017, 08:38 AM
Post: #70
RE: Support for Android 5 (Lolipop) coming in Q1 2015
Either update it or release the code to somebody who can and make it truly open.

What has cloud media got to lose by giving the home brew community the tools they need ?

Should have been like this from day one. Considering the box boots from memory card

Y'know, I think, I think that a week from now, you'll be less in the mood for being amusing.
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 4 users say Thank You to Daveydguk for this post
01-23-2017, 01:43 PM
Post: #71
RE: Support for Android 5 (Lolipop) coming in Q1 2015
Has anybody seen mi wash board ?

Y'know, I think, I think that a week from now, you'll be less in the mood for being amusing.
Find all posts by this user
Add Thank You Quote this message in a reply
01-23-2017, 02:06 PM
Post: #72
RE: Support for Android 5 (Lolipop) coming in Q1 2015
Been to the gym?

Some focus on problems and faults others on solutions and success... no question who is the happy one.

Chameleon 16GB SD 32GB micro SD <-->HDMIv1.3<-->Onkyo TX-NR1010<-->HDMIv1.3<-->Panasonic TX-P46S10 + 6 Bowers & Wilkins speakers.
10 NTFS 2TB USB drives on 3 hubs attached to a A400, 2 Seagate blackarmour NAS 3TB, 2 Seagate Central NAS 4TB.
Find all posts by this user
Add Thank You Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)