Related
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
Hello Guys,
Today I woke up with a new idea; I want to port LineageOS to the LG V20 version H990DS. I was tinkering with this idea for about one year, but never actually wanted to make the step. Until today. I used LineageOS and CyanogenMod since 2012.
The reason why I want to create the first port is because I have the time at the moment, so why not help the community? I do have four years of programming skills C/C++. Run Linux as daily driver etc... Do know how to use git, linux, autotools etc... The tricky part however is: I never compiled a Lineage OS rom from source and I don't think the compiling would be a problem, but the LG V20 H990DS isn't officially supported. My question is: Where do I start to program? How can I compile and build a working Lineage OS for the LG H990DS. Are there any good website I can read from?
I saw this:
https://www.youtube.com/watch?v=MGI3NSJFtKA&feature=youtu.be
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
https://www.reddit.com/r/LineageOS/comments/6iie9l/how_to_compile_lineage_os_141_for_unsupported/
https://www.reddit.com/r/LineageOS/comments/684qkp/help_noob_compile_lineageos/
So to make it easy: I want to program a working LineageOS for the LG H990DS, but don't have any understanding about where to start. I do have four years of programming skills, not so much, but know C and C++ well.
Thanks in advance,
Maurice
English isn't my native language, sorry for grammars.
someone help this man up.
Did you check the existing LineageOS thread?
https://forum.xda-developers.com/v20/development/dev-cm14-t3509953/post74550386#post74550386
If you want to help, I'd suggest asking him if there's anything you can do.
Thank you for your response. I do watch that thread, because I want lineageOS for the h990ds device. The problem however is that I don't want to jump right into the code. I want to know what I am doing with each line of code. At the moment I think I have to change some things in the kernel so that it can boot, but I don't know if that's true. And there is so many documentation about how to compile lineageOS, which I don't want to do. I want to program and compile lineageOS. Every tutorial skips the program parts and just compiles lineageOS.
So maybe a good programmer can give my some advice? Where to start and where can I find some documentation?
Best regards,
Maurice
Welcome!
First off, I recommend using Ubuntu 16.04 (I personally use 16.10 however). Be sure to follow the guide you linked from chef central carefully.
For the dual SIM variant, I don't believe any current source exists. Although with the similar hardware and if you have decent skills, you could get it going.
Take a look at the existing v20 trees:
V20-common: https://github.com/LineageOS/android_device_lge_v20-common
Msm8996-common: https://github.com/LineageOS/android_device_lge_msm8996-common
H918 (as a reference): https://github.com/LineageOS/android_device_lge_h918
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8996
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Those are the basics to check out. Now I did see someone converted the H918 tree to H990. Here's a link to that for reference: https://github.com/android-device-lge-h990/android_device_lge_h990
You will definitely need to make a custom defconfig in kernel sources. The device tree changes should be rather easy. You'll need to pull vendor files from stock and import the drivers and dts files from stock kernel source. If/when you get a working kernel and device trees there's a 99% chance you will need to Port other drivers and vendor files as stock files don't play nice in aosp. If I were you, I'd start looking through commit history on GitHub to see how the other devices we're brought up. That is how I learned everything.
Also, git will be your best friend when bringing up large projects, like kernel. Learn git, get comfortable with it. Cherry-picking and merging is what keeps us going.
Best of luck!
I suppose you could say there are dueling work-in-progress H990 trees since the other one is: https://github.com/x86cpu/android_device_lge_h990
The one you pointed to is mine. I was hoping for some collaboration with @x86cpu on there (in theory @x86cpu also has permissions to modify that repository, assuming I've set things up correctly). While the initial steps have been done, it is not finished! Some issues are left for getting LineageOS operational on H990 devices.
Of crucial note the modem fix in its current form is unacceptable to LineageOS (despite working). I've got two variants of one solution almost ready, but they're yet ready.
Thank you for your answer and I will look into it. I sure hope that I can help you some day, but first I want to understand the repository. After that I will help you both to code.
Really thank you and I will do my best to catch up with you.
As for the Ubuntu version. I personally use arch Linux (with plasma), because I like it more than Ubuntu. I don't think that's a problem and else I will compile the Ubuntu programs to arch. And I know my way around got. Use it for about 4 years now and now what merging/branching rebasing etc means and know how to use it.
@emdroidle I could help
Update News Flash Galaxy note 4 running Oreo 8.1
3-29-18
OMG. I said it here first. 32 bit processors CAN be ported to Oreo. Maybe not trebel yet. Smug emoticon
In just a few days , not even I thought it was possible.
Running Oreo via lineageOS 15.1 with root on my Samsung Galaxy Note 4.
The dev who devotes time to compiling builds @ripee has had his daily downloads of 14.1 for the note 4 has more than doubled. Currently running about 250 users testing builds. SMOKIN.....
Here is the OP
https://forum.xda-developers.com/no...0-unofficial-lineage-15-1-rom-t3760969/page92
Update 2-28-18
OpenGapps 8.1 is released for both arm and arm 64.
That means Oreo can be compiled it 32 bit.
Researching Oreo and Oreo go compiler instructions.
Mebbe I can compile AOSP for my older Note 4 .. So cool
https://forum.xda-developers.com/android/apps-games/arm-unofficial-opengapps-builds-android-t3743495
Updated 1-20-18
Newest musings on top. Oreo Go is currently being modded into an older Sony phone. Awesome
So since I posted this OP...my musings have been correct in these posts.
This came out on XDA, check out the links in it.
https://www.xda-developers.com/android-go-old-android-8-1-oreo/
Android Oreo and android in general is getting closer to Linux . Mainly for the same reasons
I have been installing different distributions of Linux on an older laptop.
1. To learn installing hard to find drivers
2. Learning Linux architecture and commands
3. Learning to build Linux kernel for my device
http:// www.kernel.org
4. Learning to build lineageos14 in general
With these guides
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
Thanks @_mone and @ripee
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
Thanks @FSadino
5. Actually compiling lineageOS-14 for my two devices I have access to
Galaxy note 4 Verizon thanks to @ripee for his contribution by building daily's at
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
And my galaxy tab S2 sm-t710
Thanks to @Bonuzz for getting the camera, mic GPS and Bluetooth working, and posting sources
https://forum.xda-developers.com/tab-s2/development/t710-t715-lineage-14-1-t3713097
Thanks to @Ather for getting Samsung to release their Kernel sources and building a android 7 rom
https://forum.xda-developers.com/tab-s2/development/kernel-poseidonkernel-v1-0-permissive-t3588069
https://forum.xda-developers.com/tab-s2/development/rom-poseidonrom-v1-0-deodexedrooted-t3590228
6. Thinking and musing about things
Symlinks, multi boot, and partitions. ( Treble )
In Linux, I have another partition with downloaded files on another drive
When the kernel boots, the directory tree just sees /data even though it's a separate drive
This is because of a symbolic link that mounts the partition as a folder. This prevents me, from deleting that data with permissions
So the Trebel rules tell the vendor to make a separate partition in the drive but the kernel gets a symbolic link to it, and the user (Google) cannot over write the partition with the critical info..when the ROM gets flashed? correct ?
The bootloader has boot path a, or boot path b.
The user files are in protected memory
So with Linux, when I updated my kernel,
The grub bootloader tells me I can use kernel 4.1.x or 4.2.x when I boot
The kernel loads the drivers
And then looks at the symbolic links to mount the drives.
This is somewhere in the /etc files or somewhere
So Trebel has to be a set of decision trees based on symbic links to hardware
Where all the hardware drivers are independent of the kernel
More musings later. Must build....
**************
Dec 2017 sometime
Thanks to all for viewing my first OP.
I'm just learning about building ROMs, and look forward to this thread to spitball ideas and see what sticks.
If I don't know something its because I am correcting my ignorance.
This won't be an actually development thread, just trying to understand hardware from 30 years of not being in the tech field.
Eventually I will tire or wear out of driving truck, and work with my passion again.
I am a follow the steps kind of mind, so I am learning how the world of Android / Linux works.
If I understand the Trebel development correctly...
https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
IF we can modify the older device drivers to be Trebel compliant, then once they work, then they always should work. And any Trebel ROM can work on Any Trebel Device withOUT compiling over and over.
This should result in an explosion of custom ROMs .
So I am suggesting a repository of drivers per device that are compliant for older devices.
How do we do that?
So here is the Google announcement of Trebel
https://android-developers.googleblog.com/2017/05/here-comes-treble-modular-base-for.html?m=1
Here is the developer preview of ”O”
https://developer.android.com/preview/download.html
It details how to install it on your Trebel Device.
Wow. Just Wow.
OH MY GOODNESS. I would love this on my lg g3, oneplus one, and moto e2. WOW.
TotalNoobTrucker said:
If I understand the Trebel development correctly...
https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
IF we can modify the older device drivers to be Trebel compliant, then once they work, then they always should work. And any Trebel ROM can work on Any Trebel Device withOUT compiling over and over.
This should result in an explosion of custom ROMs .
So I am suggesting a repository of drivers per device that are compliant for older devices.
How do we do that?
Click to expand...
Click to collapse
How do you wanna to do that ?
Vendor files are NOT open-source so you cannot make them treble enabled sadly.
Haxk20 said:
How do you wanna to do that ?
Vendor files are NOT open-source so you cannot make them treble enabled sadly.
Click to expand...
Click to collapse
So far all it looks like ROM dev is trial and error with people posting guides on repeatable success... (Community)
I haven't built a ROM, ( haven't built a compiler computer yet) plus I drive truck 70 hrs a week..
but have read
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763/
And
https://forum.xda-developers.com/android/software/how-to-port-samsung-rom-to-samsung-t3481114/
So what's different in the building process? With Trebel?
Google dev page lists an additional partition for drivers called VENDOR
A file called manifest.xml
And a A/B partition.
So assuming I am building a Lineage OS ROM 14.x
In that compile process, everything is compiled in the ROM
Kernel, Lineage front end, AOSP programs etc.
So somewhere in the compiler process the drivers to my N910V are pulled in from somewhere? Github¿?
If they are not open source, they were pulled from system image via ADB or Android image kitchen and uploaded to where?
So i guess we need a guide on how to build Trebel for non Trebel devices. The folks on the other Trebel thread are doing it on newer devices and getting some exciting results.
There is only a couple of Lineage 15.x builds going, but once someone has the Process down to build a Trebel on non / close to Trebel hardware,
It should be repeatable for ANY Oreo and up compiled ROM.
I may not be able to build yet, but since Trebel is the new path, I want to gather Trebel success and Process here. Maybe make a guide..
In conclusion, the drivers may not be open source, but the code is out there somewhere.
Sent from my Lineage OS 14 Samsung Verizon Note 4 from @ripee
My other device is a Samsung T710 running Posiedon 1.0 . Thanks for a stable rooted tablet @Ather
Sent from my Samsung SM-N910V using XDA Labs
TotalNoobTrucker said:
So far all it looks like ROM dev is trial and error with people posting guides on repeatable success... (Community)
I haven't built a ROM, ( haven't built a compiler computer yet) plus I drive truck 70 hrs a week..
but have read
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763/
And
https://forum.xda-developers.com/android/software/how-to-port-samsung-rom-to-samsung-t3481114/
So what's different in the building process? With Trebel?
Google dev page lists an additional partition for drivers called VENDOR
A file called manifest.xml
And a A/B partition.
So assuming I am building a Lineage OS ROM 14.x
In that compile process, everything is compiled in the ROM
Kernel, Lineage front end, AOSP programs etc.
So somewhere in the compiler process the drivers to my N910V are pulled in from somewhere? Github¿?
If they are not open source, they were pulled from system image via ADB or Android image kitchen and uploaded to where?
So i guess we need a guide on how to build Trebel for non Trebel devices. The folks on the other Trebel thread are doing it on newer devices and getting some exciting results.
There is only a couple of Lineage 15.x builds going, but once someone has the Process down to build a Trebel on non / close to Trebel hardware,
It should be repeatable for ANY Oreo and up compiled ROM.
I may not be able to build yet, but since Trebel is the new path, I want to gather Trebel success and Process here. Maybe make a guide..
In conclusion, the drivers may not be open source, but the code is out there somewhere.
Sent from my Lineage OS 14 Samsung Verizon Note 4 from @ripee
My other device is a Samsung T710 running Posiedon 1.0 . Thanks
Click to expand...
Click to collapse
The OEM needs to add support for treble there is no treble for non-treble devices.
Treble works like so:
Vendor files are stored in separate partition (Those files are edited to work with treble)
Then android just takes those files from there and work.
The vendor files are not in system.img but in /vendors (the partition is mounted here)
Only a few devices have vendor files open source there is possible to make the device treble supported but 99% of devices have vendor files closed and so its not possible for some dev here to make the device supported.
Also A/B is new partition layout:
You have your system on A but once update is available its downloaded onto B and then it just switch them (Don't read about that much so I canbe wrong here).
Also I have build ROM for xperia P and if I wanted to build 8.0.0 I cannot use treble sadly that would have made my job lot easier.
Hmm.
Haxk20 said:
The OEM needs to add support for treble there is no treble for non-treble devices.
Treble works like so:
Vendor files are stored in separate partition (Those files are edited to work with treble)
Then android just takes those files from there and work.
The vendor files are not in system.img but in /vendors (the partition is mounted here)
Only a few devices have vendor files open source there is possible to make the device treble supported but 99% of devices have vendor files closed and so its not possible for some dev here to make the device supported.
Also A/B is new partition layout:
You have your system on A but once update is available its downloaded onto B and then it just switch them (Don't read about that much so I canbe wrong here).
Also I have build ROM for xperia P and if I wanted to build 8.0.0 I cannot use treble sadly that would have made my job lot easier.
Click to expand...
Click to collapse
So where are the Xperia P files you imported into your 8.0 biuld¿ Can't you put them in the vendor folder and see if it boots¿ I presume you have to make a manifest.xml file so the ROM can see the files
Sent from my Samsung SM-N910V using XDA Labs
TotalNoobTrucker said:
So where are the Xperia P files you imported into your 8.0 biuld¿ Can't you put them in the vendor folder and see if it boots¿ I presume you have to make a manifest.xml file so the ROM can see the files
Click to expand...
Click to collapse
I haven't done 8.0.0 build yet cause the device got only CM-12.1 and now trying to port 8.0.0 and no putting the files there will not work:
1. Old devices don't have that partition and evenif I reformat it and add it and edited fstab to see it.
2. The files NEEDS TO BE EDITED TO WORK WITH TREBLE. If it was that easy to make partition put there the files and tadaaa treble device then every old device could get 8.0.0 to run but well I don't see threads about it. It's not that easy you NEED THE SOURCES TO MAKE IT TREBLE ENABLED.
Haxk20 said:
I haven't done 8.0.0 build yet cause the device got only CM-12.1 and now trying to port 8.0.0 and no putting the files there will not work:
1. Old devices don't have that partition and evenif I reformat it and add it and edited fstab to see it.
2. The files NEEDS TO BE EDITED TO WORK WITH TREBLE. If it was that easy to make partition put there the files and tadaaa treble device then every old device could get 8.0.0 to run but well I don't see threads about it. It's not that easy you NEED THE SOURCES TO MAKE IT TREBLE ENABLED.
Click to expand...
Click to collapse
Sadly, I think android 8.1 trebel is 64 bit. My note 4 is a 32bit arm71
So I dunno how it could run on my note 4. However the nexus 6 is the same cpu hardware as the note 4
However the nexus 6p is the 8core with 2 other core chipset, which is 64 bit and supported by 8.1 Trebel
So me thinks the older devices are not able to run trebel
Sent from my Samsung SM-N910V using XDA Labs
TotalNoobTrucker said:
Sadly, I think android 8.1 trebel is 64 bit. My note 4 is a 32bit arm71
So I dunno how it could run on my note 4. However the nexus 6 is the same cpu hardware as the note 4
However the nexus 6p is the 8core with 2 other core chipset, which is 64 bit and supported by 8.1 Trebel
So me thinks the older devices are not able to run trebel
Click to expand...
Click to collapse
Yeah that's another problem even if there was a way to edit vendor files treble is 64bit only
If I undertand it correctly, there's another layer between the HAL and the android framework, the HIDL, which decribes the interface of the HAL.
Shouldn't we theorically be able to edit that?
The good news is my sm-t710 is a exynos5433 chipset which supports 64bit. So maybe I will get to play with 8.n someday
android1111 said:
If I undertand it correctly, there's another layer between the HAL and the android framework, the HIDL, which decribes the interface of the HAL.
Shouldn't we theorically be able to edit that?
Click to expand...
Click to collapse
I think so. If you look at the other forum, it seems they're editing only a couple files. The manifest.xml describes what files are the drivers and where to look for them. This is a crucial file, as the drivers are in a separate partition from the system/data partition now. Download one and read it .it's a very simple exchange script
TotalNoobTrucker said:
I think so. If you look at the other forum, it seems they're editing only a couple files. The manifest.xml describes what files are the drivers and where to look for them. This is a crucial file, as the drivers are in a separate partition from the system/data partition now. Download one and read it .it's a very simple exchange script
Click to expand...
Click to collapse
As I said above you NEED the vendor file sources then create /vendor partition to add the vendor files there.
Without sources you can't make Treble running.
So if you ever want to play with 8.0 on your phone you should start porting right now.
---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------
TotalNoobTrucker said:
I think so. If you look at the other forum, it seems they're editing only a couple files. The manifest.xml describes what files are the drivers and where to look for them. This is a crucial file, as the drivers are in a separate partition from the system/data partition now. Download one and read it .it's a very simple exchange script
Click to expand...
Click to collapse
I mean porting as the "hard way" = modifying device tree to work with new sources and patching the sources.
Haxk20 said:
As I said above you NEED the vendor file sources then create /vendor partition to add the vendor files there.
Without sources you can't make Treble running.
So if you ever want to play with 8.0 on your phone you should start porting right now.
---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------
I mean porting as the "hard way" = modifying device tree to work with new sources and patching the sources.
Click to expand...
Click to collapse
I get that to begin the process for non Trebel, that's the idea.
Move all the vendor libraries to the vendor file, and run them through the Google process to make them compliant.
I would have to find a piece of hardware that has the same SoC just to begin.
No wonder the note 4 stalled at 6.0.1, verizion want going to rewrite the code. Just to get to 7. They would rather sell note 8's
Sent from my Samsung SM-N910V using XDA Labs
See scenario 2 on
source android com devices architecture hidl-cpp
We need to code o adapt a passthrough HIDL
It's not a matter of editing a file
TotalNoobTrucker said:
I think so. If you look at the other forum, it seems they're editing only a couple files. The manifest.xml describes what files are the drivers and where to look for them. This is a crucial file, as the drivers are in a separate partition from the system/data partition now. Download one and read it .it's a very simple exchange script
Click to expand...
Click to collapse
It's not a matter of editing a file to tell Android and the kernel where to look for drivers. We are not "editing" manifest.xml, it is generated during the build process. The whole structure and system calls of the drivers is changed to make them suitable for treble. And that is done by the SoC vendor whomever they may be. You can build Oreo to work on older devices by using your existing drivers, but not by using treble, you have to use your existing kernel, and write your own "hooks" into your existing drivers (better be familiar with hex code), and do a LOT of modifications to the Android code. Treble is not intended as a way for older devices to get custom ROMs, as their pre Oreo kernels and drives are not capable.
A N00b's explanation of Project Treble
Okay so I've seen a lot of confusion about how Project Treble does and does not work, so I'm going to provide a small explanation, simplified to a fault, but it'll do:
In ye olden days (Nougat and back), the Android OS was very tightly integrated with the drivers of the system. This made custom firmware very difficult to port (relatively speaking). Certain drivers were more difficult to make workable and as a result you'd have work in progress ROMs that didn't have WI-FI or cameras working, etc. It really was a pain in the butt.
Project Treble changes all of that. What it does is separate the operating system from the drivers, making porting much easier for devices that support it. The problem is that in order to enable this it would require almost a complete rebuild of these drivers, which would in turn require access to the source code and a LOT of work (hence why companies like OnePlus are releasing devices with Nougat so they don't have to use Treble, which is required on all devices that start with Oreo).
In short, COULD Treble be ported to older devices? Yes; Google and Essential have proven that. Is it feasible? Unless you've got some friends at Samsung/HTC/Xiaomi/insert-other-company-here willing to leak source code, no not really. The only device that I could possibly see getting a Treble port is the HTC HD2, simply because that phone is basically the technological equivalent of a cockroach, and I think they may have actually reverse engineered their drivers to get them to work on so many operating systems. I know I've probably made some mistakes in my explanation, but it's my best way if simplifying how this works so that people don't come along, see Treble and expect an Oreo ROM for their Fire Phone or something
2390 said:
Okay so I've seen a lot of confusion about how Project Treble does and does not work, so I'm going to provide a small explanation, simplified to a fault, but it'll do:
In ye olden days (Nougat and back), the Android OS was very tightly integrated with the drivers of the system. This made custom firmware very difficult to port (relatively speaking). Certain drivers were more difficult to make workable and as a result you'd have work in progress ROMs that didn't have WI-FI or cameras working, etc. It really was a pain in the butt.
Project Treble changes all of that. What it does is separate the operating system from the drivers, making porting much easier for devices that support it. The problem is that in order to enable this it would require almost a complete rebuild of these drivers, which would in turn require access to the source code and a LOT of work (hence why companies like OnePlus are releasing devices with Nougat so they don't have to use Treble, which is required on all devices that start with Oreo).
In short, COULD Treble be ported to older devices? Yes; Google and Essential have proven that. Is it feasible? Unless you've got some friends at Samsung/HTC/Xiaomi/insert-other-company-here willing to leak source code, no not really. The only device that I could possibly see getting a Treble port is the HTC HD2, simply because that phone is basically the technological equivalent of a cockroach, and I think they may have actually reverse engineered their drivers to get them to work on so many operating systems. I know I've probably made some mistakes in my explanation, but it's my best way if simplifying how this works so that people don't come along, see Treble and expect an Oreo ROM for their Fire Phone or something
Click to expand...
Click to collapse
So who do we know at Samsung/HTC/Xiaomi ?
Haha.
Or better yet who do we ask there? Do they have only internal development? Customer service? How do some Devs get source code? When a company releases a developers version ( thankfully someone had a way to flash a dev version 5.1.1 of my verizion note 4 so it could get a ROM.. ), does the developers edition phone come with the support and access of developers?
The reason I ask. Is I used to have MSDN access when I worked at [email protected]#$0ft . just asking again. What's the path to be a developer from a builder like Samsung?
Good luck with that
TotalNoobTrucker said:
So who do we know at Samsung/HTC/Xiaomi ?
Haha.
Or better yet who do we ask there? Do they have only internal development? Customer service? How do some Devs get source code? When a company releases a developers version ( thankfully someone had a way to flash a dev version 5.1.1 of my verizion note 4 so it could get a ROM.. ), does the developers edition phone come with the support and access of developers?
The reason I ask. Is I used to have MSDN access when I worked at [email protected]#$0ft . just asking again. What's the path to be a developer from a builder like Samsung?
Click to expand...
Click to collapse
You're going to have better luck getting blood out of a rock than that. Even when they have "developer" editions of phones they don't give you access to their code, that just means it's totally unlocked for you to f*** up or flash ROMs to. The phone manufacturers get the drivers for the SoC from the manufacturer of the chip, and except in binary form that never leaves and stays in house. Only way you're going to get that is by knowing someone who works at Qualcomm, Samsung, etc. who is willing to risk being fired, sued, thrown in jail, or all of the above for stealing the source code and leaking it to you. When a phone manufacturer releases "source code" if you examine it you will find that those closed source drivers are not included, you can build it but a lot of things won't work. (Besides the fact that it is always outdated code).
Hello,
HTC having obviously stopped supporting my smartphone in terms of updating android, I want to create a custom ROM to enjoy the benefits of the later versions of android in Mashmallow.
However, HTC provides the source code of the linux kernel used as well as some tools necessary for the proper functioning of the device. In addition, it also provides a guide to compiling android. Unfortunately, this guide seems incomplete or poorly explained. So I would like to get help in compiling an android rom for this device.
Please do it. unfortunately I have bought this device recently a month ago and feels like i have been cheated by HTC!! No proper support no software or security updates and really poor website with no useful data to end user, it seems that the company produced this model and dumped in the market to get our money and forgotten or ignoring users with at least security updates, even the non branded Chinese phones get better support than this brick from HTC. My first HTC phone was windows mobile on 2008 , it was poorly supported and my bad luck again with HTC u play which has the same situation. I will never buy from this company again.
citorva said:
Hello,
HTC having obviously stopped supporting my smartphone in terms of updating android, I want to create a custom ROM to enjoy the benefits of the later versions of android in Mashmallow.
However, HTC provides the source code of the linux kernel used as well as some tools necessary for the proper functioning of the device. In addition, it also provides a guide to compiling android. Unfortunately, this guide seems incomplete or poorly explained. So I would like to get help in compiling an android rom for this device.
Click to expand...
Click to collapse
Have you been sucessfull in building costom rom
if yes share it please
Dear fellow developers and users of this great device,
I'm working on mainline support for the p4note device family, I started with the N8010 but this is usable on all the other N80XX devices as well as they are technically all the same aside from the modem.
The current status is that an initial device tree will land in 5.11 with some components still missing but its a good start. I'm working on the rest and also I'm working on Android 11 on top of that.
This post will not be updated any longer, you can find my mainline progress here.
There is also a blog which I'll probably woefully neglect as I'm way too busy with everything in life.
Cheers
An update for my mainline progress, there is kernel logs on the display now! I'm currently working on the touch screen config.
Oh Nice to see.
But i think not many people read the General forum anymore ^^
You might want to mention this in the Dev thread.
Do you have a git repository anywhere? I found a Note 10 8000 hidden in a box and wanted to get a working small working terminal up on the wall at my 3D-Printer/Soldering-workstation, I would be happy to be tinkering around som with the code.
Nevermind, found it.
fldc said:
Do you have a git repository anywhere? I found a Note 10 8000 hidden in a box and wanted to get a working small working terminal up on the wall at my 3D-Printer/Soldering-workstation, I would be happy to be tinkering around som with the code.
Nevermind, found it.
Click to expand...
Click to collapse
Hey, great to hear that you want to tinker with it. Remember that I currently work on rev 6 of the hardware, the version info can be found in the atags of the kernel log. You may run into issues with other revisions but it should be fine.
For the wifi settings, you need the correct nvram file. I'm not yet sure whether you can determine it by the version of the hardware, the current way is a macloader in the current hardware repo.
I extracted the touchscreen firmware from the sources and put them in my buildroot repo. The driver will look for a file called maxtouch.fw on boot.
I hope this helps.
Thank you very much for the pointers, I haven't t really been into kernel development since Samsung Galaxy S2 (9100), but getting a proper Linux installation on this device would fit me perfectly so I would happily try things on my side, keep us posted.