2012.02.09 posted
Traveling for more than 20 hours, exhausted right now.
Hurried to pay network fees for the school network, see my post,found that the ZTE officials responded, see the following:
Coming from [email protected]
--------------------------------------------------------------------------------------------
Dear users:
Hello!
Thank you for your support and interest in the ZTE products;
We has plans recently to release the Blade(V880) (International Edition) 2.6.35 kernel source code on the ZTE official phone support site, please keep attention with it;
As for the Blade(V880) Unicom version for mainland China, the official does not support the Android 2.3 system.Thus,it would not be include in the kernel source.
If you have any other questions, please contact us or please call the customer service hotline 0755-26779999 or 400-880-9999, we will be happy to serve you! Thank you!
I wish you:
Good health! Work happy!
--------------------------------------------------------------------------------------------
This is a relatively significant results achieved since the release of my article.
You can search the link of my original post by google.
But it's in Chinese,to help you to get to know it,I will translate it to English as following.
Since my English is not good,I hope you can know the general idea of my article.
---------------------------------------------------------------------------------------------
2012.02.06 posted
Is very hard to type so many words, worked so hard to write the article,just for two purpose:
First,to let all Blade(V880) users get access to know an important information, ie, mobile phone manufacturers open source really means what?
The other wish is,to express a strong sound to ZTE officials, that is, we really need you to open up the kernel source code.
Mobile phone manufacturers open-source means what to commom users?
For the Android source code, always means Android system source code and the Android Linux kernel source code.
The Android system source code released by the official Google, some Mod team (such as CyanogenMod) release modifide the source code.
The open source I mentioned here, refers to the kernel source code.
Linux and its kernel, here only a brief description, not too much introduction, if you are interested with it,google can help you a lot.
First, we know, the Android system is based on the linux kernel, the most common platform architecture is arm.
The linux kernel can be considered to be an underlying system, which is responsible for hardware drivers and process management and resource call.
Linux kernel source code from the linux community and internal contains the source code for each platform's hardware drivers.
With any specific Android phone, the hardware configuration is not all the same.
In order to perfect run, a targeted kernel must be especially compiled for it.
What is targeted means?
Adding the appropriate driver code for the debice ,which not included in the common hardware driver support list of the original kernel source;
Some features and drivers which would not suit or not need for the target machine should best not be compiled into the kernel, to save system resources and improve the efficiency of the running kernel;
some special needs of the upper system (such as swap) should be compiled in the kernel.
ZTE Blade(V880) can the most complex mobile phone in the world, not one of.
In fact, its own hardware structure is not complicated ;It is different version, different batches of the machine hardware model being very complex.
Complex version: common overseas such as British oranges, Germany BASE, Japan's Softbank, Switzerland, Singapore...;
The Unicom version for mainland China (Model V880 and V880+), the Hong Kong version, the Asia-Pacific version.
Complex batch: especially the Unicom customized version of the machine of April, July,August, September, November and other batch.
The V880 various versions of hardware model is inconsistent, this is nothing to blame.
As for the domestic configuration is lower than the overseas version of the configuration, ZTE's strategy, I declined to comment.
The biggest problem is the domestic version of each batch of hardware models are complex and variable.
The most obvious phenomenon is that when a new purchased V880 was using an unofficial 3rd Rom, there always some hardware can not work proper.
For example, recently several V880 + users asked why they could not find a Android 2.3 Rom which support swap and hardware works well at the same time.
Before this ,you should know that the blade for China mainland does not has official Android 2.3 support.
I just explained: original official leaked 2.6.35 kernel from overseas, can normally driven man V880 hardware, sensors are normal, but does not support swap;
Why 3rd Rom makers do not add swap support to it?
The linux kernel does not like the .apk package can decompile out, it has to be overall re-compile.
When recompiling, you should link all the source code but not only the swap parts.
The problem is due to the complexity of the hardware models, in order to compile a commom kernel for variable batch, we need to add more driver code.
More difficult, the ZTE officials did not announce new hardware model of change, not to mention its driver source code.
The result is,when recompile the kernel to add the swap function, we do not know which driver to be add in due to the variable hardware model.
The official original kernel,hardware is running well, but does not support swap; 3rd compiled kernel support swap, but always leave some of the hardware does not work properly.
If ZTE Corporation release the 35 kernel source code (containing the driver source code of the various batches of different models of hardware),
Problems such as the V880 + have, would not be a problem.
This is the significance of open kernel source code:
Drive better, more powerful third party compiled the kernel, and can more better 3rd Rom, new functions and new features.
Burstlam has being the leader in developing Rom for balde (V880) for a long time.
He has complained many times in his articles about ZTE's not releasing the kernel source,there is a part of his article which he release his Android 4.0.3 Beta Edition:
First, note that is also a major problem in the capture of the GPU core part is already there has been progress, but unfortunately there were no suitable ADRENO chip library file to do the actual test.
Because currently 7X27 only use the ARM V6 platform with chip combination ADRENO. Be able to find updated versions of library files are just ARMV7 platform ...
I have not aimed to look ZTE will do, only aims to look SONY X8 for the same configuration update, and then have a chance to really hard solution.
I think that if ZTE can release a V880 kernel source code, Burstlam will be quite happy, of course, all the V880 users will be more happy.
On the android 4.0, to correct a misunderstanding, the ICS does not necessarily need the linux 3.0 kernel,where 2.6.35 kernel is also OK.
That means, if the 35 kernel source code released, the process of android 4.0 on the Balde(V880) will be accelerated;
Another information, MIUI v4 will organize code more portability, MIUI may be used on Blade(V880) when ICS can be perfect run.
In fact, ZTE announced earlier by the 2.6.32 kernel source code; 35 kernel source code, not know the reson, has been reluctant to release.
Look at other mobile phone manufacturers, such as
HTC, already announced a large number of models of the 35 kernel source at
*****sorry ,new menmber has no right to post outside links*****
Samsung has been open source release page
*****sorry ,new menmber has no right to post outside links*****
In addition, domestic Huawei also released its classic models U8800/U8800 of + 35 kernel source ...
So those whose balde(V880) does not work proper,
those who tried of finding patch for your Rom,
those who eager to early using a perfect Android 4.0,
those who have similar hardware configuration mobile With Blade(V880),
those who think this article is helpfull for you,
Be sure a lot of click, reply, vote and reproduced,so that more people aan see this,
To let the ZTE official developers see the majority of the user's requirements.
Personally think that send an email to the ZTE also a good way to express your wish to ZTE officials.
ZTE's handset division, e-mail address: [email protected]
Replies are stereotyped as we reflect, ZTE (Is it a computer auto-reply?):
Dear users:
Hello!
Thank you for contacting us.
Phone kernel source code can not open, please understand us!
If you have other questions, please contact us or please call the customer service hotline 0755-26779999 or 400-880-9999, we will be happy to serve you! Thank you!
I wish you:
Good health! Work happy!
Why other manufacturers can open the kernel source code, while ZTE can not?
I do not know here, "Unable to open" ,is for what reasons and for what consideration, in short, the answer is not satisfactory.
Hope you continue pay attention about this article, untill ZTE release the source code.
(At least given the model of the new hardware,so we can go to the hardware vendors to find the driver code)
PS: I knew how much influence can initiate a lot of people to participate in the petitions, just sincerely hope that brings together the power of the masses,
Clicks,reply, multi reproduced, so that the ZTE official to hear the voice of the user's and the early release of the 35 kernel source code.
great news.
my proximity sensor (v880+) works only on official rom. kernel is 2.6.35.7.
so when will it be released? in a week? month?
Great news. ZTE are always slow to release Linux kernel source code, despite the requirements of the GPL. Keep pushing them.
ZTE Blade/Libras have Android 2.3.5 & a more recent build of the 2.6.35 kernel than ZTE have released source code for so far, including better hardware support for new models.
well, i just got an email from zte on their plans to release the v880 kernel,
***
Dear Sir / Ma’am,
Thanks for contacting ZTE.
We don't have this plan now.
Thanks for your understading.
Best Regards
xboxee said:
well, i just got an email from zte on their plans to release the v880 kernel,
***
Dear Sir / Ma’am,
Thanks for contacting ZTE.
We don't have this plan now.
Thanks for your understading.
Best Regards
Click to expand...
Click to collapse
I got a similar reply last year. Probably wouldn't hurt to remind them about their source code release obligations at regular intervals.
What they need to understand is if they don't release complete kernel source code for every compiled kernel then they're effectively selling phones with pirate software.
They're breaking the terms of the copyright license that the Linux kernel was given to them under & which allows them to sell Android devices (GPL v2) which says that they must release complete source code.
wbaw said:
I got a similar reply last year. Probably wouldn't hurt to remind them about their source code release obligations at regular intervals.
What they need to understand is if they don't release complete kernel source code for every compiled kernel then they're effectively selling phones with pirate software.
They're breaking the terms of the copyright license that the Linux kernel was given to them under & which allows them to sell Android devices (GPL v2) which says that they must release complete source code.
Click to expand...
Click to collapse
actually i got a prompt reply from them. and in my second letter i reminded about GPL and my non-working proximity sensor (in fact, absence of proper kernel driver for it). it this is what they said
Dear Sir / Ma’am,
Thanks for contacting ZTE.
Please contact the local dealer where you purchased the device or network operator to upgrade your device.
Should there be further assistance, please do not hesitate to contact us.
Best Regards
just wrote another letter, well, let's see.
xboxee said:
well, i just got an email from zte on their plans to release the v880 kernel,
***
Dear Sir / Ma’am,
Thanks for contacting ZTE.
We don't have this plan now.
Thanks for your understading.
Best Regards
Click to expand...
Click to collapse
Well,a lot of Chinese V880 users got the e-mail as following(of course,in Chinese):
尊敬的用户:
您 好！
感谢您对中兴产品的支持和关注；
我司已计划近期公布V880（国际版）2.6.35内核源代码到中兴官方手机支持网站，请您留意；
V880国内版本，官方不支持Android 2.3 系统；
如您还有其它问题请及时联系我们,或欢迎拨打客服热线0755-26779999或400-880-9999,我们将竭诚为您提供服务!谢谢!
祝您:
身体健康！工作开心！
The reply of ZTE is positive.
If you have any doubt,just wait for official news.
bingo1991 said:
Well,a lot of Chinese V880 users got the e-mail as following(of course,in Chinese):
尊敬的用户:
您 好！
感谢您对中兴产品的支持和关注；
我司已计划近期公布V880（国际版）2.6.35内核源代码到中兴官方手机支持网站，请您留意；
V880国内版本，官方不支持Android 2.3 系统；
如您还有其它问题请及时联系我们,或欢迎拨打客服热线0755-26779999或400-880-9999,我们将竭诚为您提供服务!谢谢!
祝您:
身体健康！工作开心！
The reply of ZTE is positive.
If you have any doubt
Click to expand...
Click to collapse
ok, but when? this is what i was asking about. it seems (taking into consideration replies to my letters) like 2 divisons just don't know what either of them do.
xboxee said:
actually i got a prompt reply from them. and in my second letter i reminded about GPL and my non-working proximity sensor (in fact, absence of proper kernel driver for it). it this is what they said
Dear Sir / Ma’am,
Thanks for contacting ZTE.
Please contact the local dealer where you purchased the device or network operator to upgrade your device.
Should there be further assistance, please do not hesitate to contact us.
Best Regards
just wrote another letter, well, let's see.
Click to expand...
Click to collapse
Well, following the GPL the person or company that distributed the compiled software to you is responsible for providing the source code on request. So that would be the retailer of your phone, for the source code of the kernel on your phone when it was sold. ZTE would only have to supply the source code to the next company in the supply chain, strictly speaking, if they weren't distributing rom updates.
I believe ZTE are distributing compiled 2.6.35 Blade kernels directly through their update server to people with Blades or Libras bought in some countries. Those kernels are clearly slightly later versions with more modifications than are in the 2.6.35 kernel source which they've released for their other devices. The new wifi driver in zte roms refuses to load with a kernel compiled from their source, some new hardware in newer models of the phone doesn't work either. The wifi driver says it's GPL too, if you grep the binary, no source code for that yet either - unfortunately qualcomm probably own all the copyright on that.
Anyway, we can't take legal action, the only thing we've got is a bit of pester power. Hopefully they'll take notice that at least a few of their customers want GPL compliance. Only a copyright holder, like a Linux kernel developer, or busybox developer could take action.
---------- Post added at 04:22 AM ---------- Previous post was at 04:07 AM ----------
bingo1991 said:
Well,a lot of Chinese V880 users got the e-mail as following(of course,in Chinese):
尊敬的用户:
您 好！
感谢您对中兴产品的支持和关注；
我司已计划近期公布V880（国际版）2.6.35内核源代码到中兴官方手机支持网站，请您留意；
V880国内版本，官方不支持Android 2.3 系统；
如您还有其它问题请及时联系我们,或欢迎拨打客服热线0755-26779999或400-880-9999,我们将竭诚为您提供服务!谢谢!
祝您:
身体健康！工作开心！
The reply of ZTE is positive.
If you have any doubt,just wait for official news.
Click to expand...
Click to collapse
Sounds good. Hopefully we'll have some kernel source code updates from ZTE soon.
I think there are some language problems when we try emailing zte.com.cn in English. The English speakers there don't seem to understand that they're using the Linux kernel, which is GPL, which legally obliges them to release the source code for all the different versions that they use, at least if they want to keep selling phones in Europe & the USA.
English translation of the Chinese text, from Google...
Dear users:
Hello!
Thank you for your support and interest in the ZTE products;
Division I has plans recently announced the V880 (International Edition) 2.6.35 kernel source code to the ZTE official phone support site, please pay attention;
The V880 domestic version, the official does not support the Android 2.3 system;
If you have other questions, please contact us or please call the customer service hotline 0755-26779999 or 400-880-9999, we will be happy to serve you! Thank you!
I wish you:
Good health! Work happy!
Click to expand...
Click to collapse
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
What about use a base of stock roms and make the things work??? I know Cm its for armv, but all its adaptable,
Enviado desde mi XT890 usando Tapatalk 2
as for MIUI (there already is a MIUI port on the razr i, not complet I think, but it exist). MIUI is mostly a framework mod.. this is platerform independant AFAIK.
I don't think CM & Cie are so dependant of the SoC architecture. There's lot of différences between some ARM SoC .. maybe more than you can imagine. If CM can be adapt to so many device with so many ARM SoC witch a so différent, why not for a x86 Soc ?
I think you're a little bit pessimist here...
I didn't say it's impossible but it's more complex then a normal port for an ARM device. The issue is it requires more knowledge on the issue and will eat far more time. A CM port to x86 is a very unlikely goal for a single dev , and I'm saying this because a few months ago I discussed this issue with the people behind Android x86.
So a talented DEV will be able to achieve this but it will take time and a bigger struggle , that's why to start of developing for this device it would be more reasonable to look at Android code already ported to x86.
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
Sure there is some ARM dependent code in the repos but most of android doesn't really depend on the arch (like apps using the sdk dont need to be recompiled for working on the I, see play store apps). I have worked with o1 and android-x86 and there isn't really that much change from CM and android-x86, just some extra optimizations for x86 which can be added in later.
There are plenty of device on where even custom rom seems to be impossible. mostly because of a locked bootloader.
Look at the Motorola Defy. At the beginning, the development of a custom rom like CM was pretty impossible.... but they did it. They did it so far that the Defy became one of must used device with Cyanogenmod. And you now the most astonishing? It's thanks to only 2 devs.
I think bypassing a locked bootloader like the Moto one is far more tricky than adapting a CM ROM to a x86 SoC (while the device is natively unlocked).
AFAIK, android-x86 project is not so close to the Android we have on our phone.
When you develop a custom rom you can either take the AOSP source and try to put it on your phone : the tricky way. Mainly when you don't have access to the source of the drivers (ARM or x86 .. same fight)
Or you can take the official rom and mod it to reach the AOSP/CM/MUI/etc level. And I think on most device it's the way to go (unless the manufacturer release all the source code of the device.... something that never appends).
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
You really know what you are talking about? As others already mentioned above CM is in most a framework - porting android to x86 seems to be not such a big gap as motorola did it already and for sure you can run android on your pc - do you own an arm pc (in this case i think an rasperry pi...). The toolchain remains the same so why you make such a story out of it? Are you a razr i owner or do you just want to frighten all razr i devs and owners awaiting a CM port??
ARM architecture is different in some points but most of the work will do the compiler and to be honest i think there will be some more x86 phones in the future, intel never developed it for one or two phones....
So what is your intention with this topic??
kind regards.
lord0815 said:
So what is your intention with this topic??
Click to expand...
Click to collapse
That's what I'm wondering. Any dev that's taking on this task obviously knows it's going to take a bit of extra work. It would have been different had the OP offered some help and advice, but he just posted the obvious while making it seem like a bigger deal than it is (at least I'm guessing it's not as big a deal as he makes it seem, considering the other posts in this thread). Nothing but fear mongering and pessimism at this point. Sure, we will have to wait a bit for the devs to figure things out, but I know enough of them picked up this phone that something will eventually come. Plus, there seems to be a bit of dev interest in the Intel Yolo as well.
I don't know much about porting or developing and getting cm to run with all the necesary source and drivers is probably not easy but I do know that one of the basic options when running the build/make command for AOSP and CM is an x86 build for emulation. So basic x86 infrastructure exists does that ensure compatibility with this phone maybe not but it might help and certainly it would still require SOC and device optimization drivers but its probably the better place to start then tackling trying to port ARM based code and drivers.
However in the meantime my thinking is maybe a CM style rom could be achieved by first stripping down the rom making it "blurless" and then porting CM features especially since the latest Moto ROM's are comparatively closer to stock then sense or touchwiz. Of course I don't have the phone yet its in England waiting to be brought to me.
Hello!
This is my first post, any suggestions on how to improve are gladly taken!
I would like to install a Bliss Rom which does not support my Huawei P8 Lite (Android 5.0).
Is it possible? And if not, what ROMs would you suggest?
I think our cute little p8lite doesn't have any custom roms.. But we have to hope we will get a few.. Maybe some roms ported from honor 4x?
Ps. And remember... You can't install roms from another devices
i wish to be a lot or custom rooms to our p8 lite too !
will we ever get a cyanogenmod?
You may want to follow @XePeleato 's efforts in porting (help appreciated) here -> http://forum.xda-developers.com/p8lite/general/rom-aosp-5-1-1-ale-l21-t3350106
Unfortunately at the current phase the RIL is not working (you are not able to call / receive call)
The problem probably lays in the HIiSilicon Kirin chipset. The chipset is fairly unique, with only a few devices built with it, there are no general fixes for issues like RIL problems, so everything needs manual fixing, which is like modify-rebuild-try, after every effort to trying to fix issues.
It takes time, and manual labour, which is very tedious.
XePeleato said, he'll wait for the official 6.0 releases, and try to do some things after that.
I'm also interested in the building process itself, already downloaded a linux vm, and the CM source code itself, and I'm trying to learn how the system is working, so there are mulltiple people who are willing to make ROMs.
There is a person who works on cyanogenmod for our p8lite.
https://github.com/hak86/android_device_huawei_hi6210sft
PatrickDelta said:
Hello!
This is my first post, any suggestions on how to improve are gladly taken!
I would like to install a Bliss Rom which does not support my Huawei P8 Lite (Android 5.0).
Is it possible? And if not, what ROMs would you suggest?
Click to expand...
Click to collapse
You can install sokkoban's rom. It is emui but contain a lot of features that aren't available now on Huawei p8 lite. Especially camera modes like light painting, super night mode etc. http://huaweip8lite.blogspot.com/?m=1
First of hello hello to everyone here
I'll try to be as straight as possible.
I am having trouble compiling stock kernel from Huawei's source code for my device - Huawei Y5II - CUN-L01.
As this is my very first attempt to make a kernel i had a lot of troubles and i still do. After many attempts, i finally successfully compiled stock kernel for my device, the only problem is - it gets stuck in a bootloop which means something is wrong.
My device has mediatek - mt6735 with cortex A53 proccessor inside. I would like to ask is it possible to compile kernel for my device as arm64 ? Default one is armeabi - armv7l. I searched all over google for as hard as could and i keep reading that my proccessor is actually 64bit. Now i want to know is it possible to compile the kernel as 64bit and will it work with my current stock rom ? If not, can someone please guide me in how i can get some error logs and get any info on why my phone gets stuck in bootloop after i compile and flash arm version of my kernel.
I know my questions may be newbie but i am having really hard time understanding all of this, if someone can put some guides on what should i do i would be grateful. Also, i have many defconfig files in my configs folder and at first i wasn't sure which one to pick, and after trying to see differences between them i can't seem to find any with the naked eye, eventually i downloaded kernel auditor on my phone and searched all the way through the props and found that i should use "hq6735_35u_b1n_l1_defconfig" because it says it was the "flavor" for my kernel.
Thank you in advance and i hope to get some help
I think your getting arm64 and armeabi mixed up and all. Defconfig basically means the settings for your device, does it use this touchscreen or that or should it use this driver or that.
I undesrtand that, and i think of armeabi and arm64 like windows x64 and windows x86 bit i am confused about my kernel because on the web it says my proccessor is arm64 and my current kernel is based on armeabi. Correct me if i am wrong but just like on pc, if proccessor is 64bit it can also run 32bit version, phones work the same way ?