Mediatek 8 core, LTE-enabled MT6595 allegedly in line for a January release

It has just been one month since the official unveil of the octa-core MT6592, and rumours of an upcoming LTE-enabled 8 core chipset are already rife.

The upcoming chipset, reportedly dubbed MT6595, will carry the 8 core functionality of a MT6592, with an added on-board modem for 4G LTE. What’s more, the MT6595 might come with support for TD-LTE, FDD-LTE, WCDMA as well as TD-SCDMA, thereby avoiding a lot of confusion that is prevalent at the moment. According to Taiwanese outlets, this 4G enabled chipset might see a release as early as this month!

Gizchina News of the week

Mediatek 8 core, LTE-enabled MT6595 allededly in line for a January release

News of another chipset in the works, the MT6590, has been going around. With not a lot known about the MT6590, it is being said that the chipset might feature a 20nm manufacturing process, bettering the 28nm process used in the MT6592. We’ll keep you updated on this, so stay tuned.

Previous iOcean to launch “the best” $130 Android smartphone!
Next Moto G with unlimited data plan packaging leaked, another blow to Chinese phone makers?


  1. Nahúm Pérez Mesa
    January 2, 2014

    Cool! ^^

  2. Yury
    January 2, 2014

    MT6590 will be 28nm

  3. January 2, 2014

    I really want to like MTK. It’s great that they’re competing with Qualcomm. I really like how they’ve invigorated the Chinese Smartphone market.

    But, it’s past the point of acceptable delay for them to not to be supporting Open Source.

    There are no 3rd party ROMs available for ANY MTK based phones that are based upon CM, PA, AOSP, AOKP, Omni, or anything else. In fact they’re starting to make LG (the previous bad guys in the proprietary software game) look good!

    So until they clean up their act and strike a partnership with CM (or other group/company), I’m going to have to rate ANY phone using their processors as a “NON-STARTER”.

    It’s unfortunate that it’s like this, but if they really want to win, then they should be doing the following:

    1) Posting their source code to AOSP with 48 hours of each release.

    2) Building a porting kit for the popular ROM packages (i.e. CM, PA, etc.)

    And if they really want to jump ahead of Qualcomm and Samsung:

    3) Posting complete code for a complete Google Edition build for a reference platform phone.

    4) Build a ROM swap app for easy ROM swapping between stock ROMs and custom ROMS. (Like CM has done)

    5) Build a ROM repository for their customers ROMS and for Open Source ROMs build for hardware that uses their chips.

    6) Set hard guidelines for making sure their phones have unlocked bootloaders.

    And the whopper would be:

    7) Get the BSP (Board Specific Packages: which are the changes that each hardware vendor makes for it’s specific phones), back from the manufacturers, and build their OWN CM, PA, Omni, etc. for EVERY phone they can (or build a universal ROM for dozens of phones). Theoretically, they could do this since they have the previous BSPs from the manufactures, so they DON’T need manufacturer support to do it themselves.

    What I’m saying is that MTK created a monster with two dozen heads in China, and now it’s time to tame the beast and jump ahead in relations with the development community.

    I’m sorry MTK, until you clean up you software act, you’re not on my buy list any longer.

    • highwind
      January 2, 2014

      But you DO notice that atleast 95% of all customers do absolutley NOT care about “custom roms” and the like?

      • January 2, 2014

        Clearly this isn’t what Oppo thinks, they ship a CM10.2 version of their N1, and instructions on how to switch the ROMs easily. Nor is it what HTC, Samsung, Sony, and LG were thinking when they made GPE editions of their popular phones.

        Non-stock ROMs (i.e. deviation from AOSP source) are usually for the benefit of the hardware manufacturer and/or the carrier. They seldom benefit the consumer.

        Custom ROMs ARE pro-consumer and are usually optimized versions of the stock code from Google.

        • highwind
          January 2, 2014

          You may talk yourself into this if you like to believe but it is a given fact that:
          – Mediatek is the fastest growing smartphone soc manufacturer DESPITE not offering souce codes…
          – 95% of all android user dont even care which Android version they are running…
          (The two latest android versions 4.3 and 4.4 together do not even have a market share of 5% of all devices running Android… and as “custom roms” are usually built on the latest available versions you can do the math by yourself to evaluate how “important” open source codes and custom roms are for the massmarket)

          On a side note:
          Comparing a soc manufacturer (Mediatek) to Smartphone manufacturers (Oppo, HTC, Samsung, Sony) is quite non-sense and the second largest smartphone manufacturer (Apple) doesnt offer source codes / support custom roms either

          • January 2, 2014

            It was my understanding that manufacturers COULDN’T make source releases, since they were not allowed to post code that had come from MediaTek to the AOSP. Correct me if I’m wrong on this point.

            • highwind
              January 2, 2014

              Dont think they are prohibited to do so as FAEA just released source code for one of their Mediatek Smartphones… (dont know which one atm – google will help if you are interrested)

              I think it is just that Mediatek doesnt offer any support and neither they nor most of the manufacturers have any interrests because doing so would cost money / personnel and doesnt return any profits which they cannot afford in such a price driven market