Working on porting ICS to the Lanyu 910 / X10 Airpad MID-910. I think the kernel sources used for the Pascal2 could possibly work with the 910 after some config changes.
Basically with the 910 we have no stock kernel source available for reference, no stock configuration, no detailed hardware inside the device.. We know it uses the rk2918 rockchip and I know it uses the SWL-2480 / Marvel 8686, simply from observing the identifying markings on the chip. Other than that, all we know is that it uses a 2.6.32 kernel with android 2.3, has an unknown 7" capacitive touch screen, unknown camera, etc. In order for ICS to work with the 910 we'll have to use a 3.0.8+ kernel or backport all of the required components from 3.x to our working 2.6.32 sources -however we don't have the patched sources for the stock firmware, so we are better off to just use 3.0.8 kernel that the source is available for on many rk2918 devices - of course we'd have to make configuration changes to our specific hardware, and possibly patch the sources with modified/new source code for our specific hardware (if we can obtain it).
Pascal 2 has a realtek based wireless chipset.. 910 uses the SWL-2940 / Marvel 8686, the module for this is also included in the kernel sources. The 910 has an unknown touchscreen, so the kernel for the pascal2 may or may not work with the touch screen settings. It is quiet difficult to work on the kernel without in depth knowledge of all the hardware. The 910 has Lanyu printed on the motherboard, and I'm not successful in finding any detailed hardware information for the board on the 910.
Also I am concerned with the memory mappings since the 910 only has 512mb ram and the pascal2 has 1GB+
Really wish these Chinese tablet manufacturers would follow the rules of GPL and release their source code, it would help A LOT with getting ICS to work with the 910.
As far as the rockchip and the ICS rom that vurrut has put together, I am almost 100% sure that the system.img that he used will work with the 910 as long as I get a working 3.0.8 kernel for ICS reconfigured/recompiled and implement some changes in the boot.img for the init services relating to hardware.
If anyone has the X10 airpad (rk2918 based) or the Lanyu 910 and has some important information regarding the internal hardware, please contact me with details, as I can probably get a working kernel for our device in a matter of hours.
Needed:
Gsensor/Accelerometer MFG/Model
Input Keys Controller - MFG/Model
Battery Sensor Chip - MFG/Model
TouchScreen/Display - MFG/Model
Other mainboard chipsets - MFG/Model (excluding RK2918 Rockchip SoC)
It would be of much help if there was someone here knows the MFG/Model of any of the above hardware, and it would also be a great help if anyone knows what linux kernel drivers are used for any of the components inside the 910.
When I was working with the Kindle Fire kernel I had found a very helpful information page on the internal parts of the device, with very detailed information - it was really helpful. I know that with these generic Chinese tablets finding such info may be much more difficult due to lack of interest and lack of popularity when compared to major brand tablets such as the Kindle Fire - but if anyone out there has ran across similar information it would give us GREAT progress in developing an ICS ROM for the 910. Here is a link to the breakdown of components in the Kindle Fire:
http://www2.electronicproducts.com/Amazon_Kindle_Fire_D01400_Tablet-whatsinside_text-123.aspx
The thread to the ICS ROM for Pacal 2 (rk2918) device is here: http://forum.xda-developers.com/showthread.php?t=1734181
A big thanks to Vurrut for all of his work! Hopefully we can use parts of his ROM to get ICS running on our Lanyu/Airpad!
Pls open a terminal, type "dmesg" and upload the log. Then we will see
If you have luck your build has also the kernel config file. You will find it under /proc/config.gz.
- Oma -
Oma7144 said:
Pls open a terminal, type "dmesg" and upload the log. Then we will see
If you have luck your build has also the kernel config file. You will find it under /proc/config.gz.
- Oma -
Click to expand...
Click to collapse
Do you honestly think I would be working on a Linux kernel without a knowledge of the existence of dmesg or config.gz? Did you also forget to remind me of adb shell logcat -d >> logcat.log ?
Sent from my A100 using xda premium
linuxsociety said:
Do you honestly think I would be working on a Linux kernel without a knowledge of the existence of dmesg or config.gz? Did you also forget to remind me of adb shell logcat -d >> logcat.log ?
Click to expand...
Click to collapse
Sry. You've been asking for touch, sensors etc.. In the named logs you will find all that.
- Oma -
Oma7144 said:
Sry. You've been asking for touch, sensors etc.. In the named logs you will find all that.
- Oma -
Click to expand...
Click to collapse
Only partial information can be obtained in this manner as it will only show what device modules are loaded, the information I was wanting was precise model information of the chipsets used in the tablet. And the config for the stock kernel is not included in procfs anyway as the developers must have not said =Y to CONFIG_IKCONFIG
Sent from my A100 using xda premium
]
Code:
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_I2C_LZ300 is not set
CONFIG_I2C_LZ300_ST=y
# CONFIG_I2C_SIS809 is not set
# CONFIG_INPUT_MISC is not set
CONFIG_INPUT_GPIO=y
#
# Magnetometer sensors
#
# CONFIG_COMPASS_AK8975 is not set
# CONFIG_COMPASS_AK8973 is not set
CONFIG_G_SENSOR_DEVICE=y
# CONFIG_GS_MMA7660 is not set
CONFIG_GS_MMA8452=y
# CONFIG_GS_L3G4200D is not set
# CONFIG_INPUT_JOGBALL is not set
# CONFIG_LIGHT_SENSOR_DEVICE is not set
With the Model (SIS809, MMA8452, AK8975 etc.) you have all what you need. This you will also find in the dmsg log.
That's enough to compile from sources.
Anyway.
- Oma -
Oma7144 said:
]
Code:
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_I2C_LZ300 is not set
CONFIG_I2C_LZ300_ST=y
# CONFIG_I2C_SIS809 is not set
# CONFIG_INPUT_MISC is not set
CONFIG_INPUT_GPIO=y
#
# Magnetometer sensors
#
# CONFIG_COMPASS_AK8975 is not set
# CONFIG_COMPASS_AK8973 is not set
CONFIG_G_SENSOR_DEVICE=y
# CONFIG_GS_MMA7660 is not set
CONFIG_GS_MMA8452=y
# CONFIG_GS_L3G4200D is not set
# CONFIG_INPUT_JOGBALL is not set
# CONFIG_LIGHT_SENSOR_DEVICE is not set
With the Model (SIS809, MMA8452, AK8975 etc.) you have all what you need. This you will also find in the dmsg log.
That's enough to compile from sources.
Anyway.
- Oma -
Click to expand...
Click to collapse
Mr. Oma, I am sorry but I think you may be in the wrong thread, the Lanyu 910 only shares one thing in common with the other common RK2918 based tablets, and that is the RK2918 its self, the rest of the hardware that makes up the full system is different on the 910/Airpad than the more popular tablets that are using the RK2918. For example you probably use a RTL based wifi chip in the config you are using also, where the 910/AP uses the SWL-2480 which uses a Marvel 8686 driver in the linux kernel or you can use the libertas driver in more recent kernels. What exactly is the config you pasted here from? At this point I know the internal hardware enough to get a proper config file for the 910/Airpad, however there are compile issues with certain components and without resolving the compile issues there is no kernel image going to be generated unless I disable the problems at hand in the config, if you want more up-to-date information then head over the the x10 forums and check the original thread for 910/AP kernel development: http://forums.x10.com/index.php?topic=27184.0
Have you seen this?
Here is another Tab using SWL-2480 (looks like an Aoson M12).
Here is another 3.0.8 source, originally from a Chinese Tab named Xinboa.
Maybe that helps.
- Oma -
Oma7144 said:
Have you seen this?
Here is another Tab using SWL-2480 (looks like an Aoson M12).
Here is another 3.0.8 source, originally from a Chinese Tab named Xinboa.
Maybe that helps.
- Oma -
Click to expand...
Click to collapse
I appreciate your effort in helping me find info, but I have already researched most the possibilities and am already aware of the sites you linked. The problems aren't finding hardware specs, the problem now is getting 3.0.8 sources to compile with the Airpads hardware selected in the configuration, as I posted in the x10 forum, it doesn't appear that any 3.0.8 kernels have been successfully compiled for other devices using the same board-config as the 910, in fact the link you specified with the swl-2480 is the only device that has similar hardware aside from the rk2918 that I have found. The wifi and audio both fail to compile with Ody.se sources. I have decided to put most of my work now into testing/development of Jelly Bean for the Acer Iconia Tab, as it doesn't seem that many others are interested in the 910/Airpad development. Thanks again
Ok.
Odys-Xpress sources? That's kernel 2.6.32.27, isn't it?
But try the sources from above link. Could search for that
A library for Marvell 8686 SDIO WLAN devices.
So far, the following modules have been verified:
(1) Samsung SWL-2480
(2) Azurewave AW-GH321
(3) USI WM-G-MR-09
(4) Murata SP-8HEP-P
I don't know if they will compile.
- Oma -
Oma7144 said:
Ok.
Odys-Xpress sources? That's kernel 2.6.32.27, isn't it?
But try the sources from above link. Could search for that
A library for Marvell 8686 SDIO WLAN devices.
So far, the following modules have been verified:
(1) Samsung SWL-2480
(2) Azurewave AW-GH321
(3) USI WM-G-MR-09
(4) Murata SP-8HEP-P
I don't know if they will compile.
- Oma -
Click to expand...
Click to collapse
They won't compile with 4.2.0 or 4.4.0 arm eabi toolchain in 3.0.8 sources, i tried them, since 3.0.8 it has been replaced with libertas instead of mv8686, i've done looked into all of it man
linuxsociety said:
They won't compile with 4.2.0 or 4.4.0 arm eabi toolchain in 3.0.8 sources, i tried them, since 3.0.8 it has been replaced with libertas instead of mv8686, i've done looked into all of it man
Click to expand...
Click to collapse
Use gcc 4.5.2 or higher.
- Oma -
Oma7144 said:
Use gcc 4.5.2 or higher.
- Oma -
Click to expand...
Click to collapse
I also tried gcc 4.6.2 and 4.6.3 natively setup with cross compile in Gentoo / Funtoo - I get the same same errors with the wifi and the audio as using the appropriate eabi-arm toolchains.. I tracked down the problems though, it is a dephell with major code changes in common headers. The headers that are included in the sources have changed from 2.6.32.27 and to 3.0.8 and porting everything up to current is quiet more code changes than I am willing to work on. Like I have said though, I am no longer working on this kernel for the generic devices 910/AP, I have more work on my slate now than I need working on the Acer Vangogh / Vendetta kernels for Jelly Bean to incorporate Tiny HAL and newer tegra changes keeping compatability with the only Acer source we have available. But at least I am not limited to products that aren't following the GPL appropriately, and the use of uncommon hardware that makes debugging damn near impossible. I almost have the Vangogh board and Acer specifics ported over to 3.1's grouper from the nexus project and it's much more smoother than working with that chinese developed tab
Ok, than have a good time!
Greetings to Southern Kentucky.
- Oma -
linuxsociety said:
If anyone has the X10 airpad (rk2918 based) or the Lanyu 910 and has some important information regarding the internal hardware, please contact me with details, as I can probably get a working kernel for our device in a matter of hours.
Click to expand...
Click to collapse
Here you go: eboda-TS, MV8686 WLAN, MMA8452Q Sensor, WM8988 Audio, ANX7150 HDMI, HYM8563 Clock, APX192 Powermgt.
Could you pls compile a kernel?
- Oma -
Related
Many people want to run a working froyo on their devices.
This won't be possible in a clean way without compiling a new kernel.
To archive this goal, we need to merge the Huawei specific device drivers (which are for 2.6.29) into a new kernel tree, the 2.6.32.9 one (or even 2.6.35 but 2.6.32.9 comes first since it is stable and thus important to us).
I did some research and preliminary work which I will explain here:
- The base kernel Huawei started with is available here (gitweb) - also check their wiki.
- Huawei started with the Q8650BSDCANLYA324020 tag on the donut_glazed branch (see instructions at the end of the post)
- Huawei has written it's own board driver (note they have used a Q8650 kernel release not a MSM7x25 one, most likely because this board driver is a little older and was not available for the version they wanted)
- After they were finished writing their drivers they released the kernel source (as you can download it from Huawei)
I have checked out the Q8650BSDCANLYA324020 base kernel version and diffed it against the kernel release of Huawei, generated a patch file (and stripped out the DOS linebreaks wtf) which can be applied to the base kernel.
Applying this patch to a more recent kernel (2.6.32.9) is not possible without merging the code into the new kernel tree (and since I'm not a programmer I can't do it - this is were your help is needed).
The other question is in which kernel tree we can port the patch I have extracted. I think we can use Q8650BSDCANLYA504005 on the froyo_almond branch since Huawei used an older version of it. Merging it into the AOSP msm-2.6.32.9 tree may be possible too (but the code aurora msm kernel is an improved AOSP version, so I guess we want that one).
My patch (and some non-pulse-mini fixup patch) alongside with a freshly extracted and fixed .config for the U8120 can be found at http://nico.core.ws/misc/huawei_kernel_u8100_8110_8120/
To port the source you need to checkout the original source (Q8650BSDCANLYA324020), create a new branch in which you apply the Huawei patch, then checkout the froyo kernel (Q8650BSDCANLYA504005) and merge your branch containing the changes from the patch into it.
Another way may be porting the froyo kernel tree back to the eclair one with Huawei patches.
Please post any results/questions/etc. here!
If we should get this working we can also enable the GPU driver (Adreno 200) as requested by many people (and much more (CyanogenMOD anyone? )).
Appendix:
Instructions on how to get the original source:
$ git clone git://codeaurora.org/kernel/msm.git
$ git checkout Q8650BSDCANLYA324020
Instructions on how to apply the patch (assuming "msm" is the kernel tree):
$ cp diff_kernel_msm_aurora_Q8650BSDCANLYA324020.diff msm/
$ cd msm/
$ patch -p1 < diff_kernel_msm_aurora_Q8650BSDCANLYA324020.diff
If you are compiling for U8100 or U8120 phones, you need to apply another
patch which fixes sensors (otherwise your phone won't be able to read battery
level and stuff):
$ cp needed_fixes_for_non_u8110_devices.diff msm/
$ cd msm/
$ patch -p1 < needed_fixes_for_non_u8110_devices.diff
Note that the above instructions will get you nothing new, only the kernel already running on your device.
This thread is about porting the Huawei patch to a froyo kernel.
Very nice! Thank you for this topic!
I hope this will be successfull
Are the Atheros sources included aswell?
[GER]Roxxor said:
Are the Atheros sources included aswell?
Click to expand...
Click to collapse
To be honest, I don't know. They should be in there though (maybe under a more generic driver name or integrated in the board driver) otherwise Huawei would have violated the GPL.
The problems with the fixes:
wifi
They got almost wifi working in other post
radio
FM radio too with an 3rd party app
dpad
dpad crash in this post too 2 pages back just disable this
screen calibration
calibration fix can meaby be fixed with HTC calibrate??(its an calibration app)
sound
I solve the sound problem with my phone is to replace the libaudio.so from 2.1rom,maybe you can try.\
cedric123 said:
here is an source for the adreno drivers.
https://www.codeaurora.org/gitweb/q...b819424af4be;hb=refs/heads/android-msm-2.6.32
Click to expand...
Click to collapse
Basically this is the complete kernel source for froyo without Huawei patches (it's the wrong tag too).
When we have ported the drivers we easily can enable that driver.
cedric123 said:
the froyo kernel source: http://www.huaweidevice.com/tcpsdow...&attachmentName=kernel-2.6.32-U8150-Froyo.zip
Click to expand...
Click to collapse
Thats the source for the U8150, not the ones we want. The only thing which may help us at a future point in there is the kernel config.
cedric123 said:
If you compile a kernel right now you'd get a kernel that won't read the batterylevel and the magnetic compass won't work so we need to make a few adjustments.
Click to expand...
Click to collapse
This is in needed_fixes_for_non_u8110_devices.diff
So nothing new here.
So what can we do to help?
Is there a way to chat in XDA?
Any news on this?
cedric123 said:
here is an source for the adreno drivers.
LINK REMOVED
Here are some are adreno 200 drivers from a Custom nexus one ROM:
Areno Drivers package contains the adreno rivers only(i could miss some drivers here so look for the package above contains all drivers from the nexus rom
LINK REMOVED
Click to expand...
Click to collapse
Possible to make an update.zip for this Adreno 200 driver on 2.1 while 2.2 is not working?
editeditediteditediteditedit
Maybe he's working on the project.
Leito92 said:
Maybe he's working on the project.
Click to expand...
Click to collapse
I dont think so he's not saying anything about it for 1 week now...
But even if he doesnt say anything, this topic can be useful.
Someone with git/kernel/c knowledge need to port the patch.
nicoderboss said:
Someone with git/kernel/c knowledge need to port the patch.
Click to expand...
Click to collapse
Who can do That?
Kallt_kaffe meaby?
nicoderboss said:
Someone with git/kernel/c knowledge need to port the patch.
Click to expand...
Click to collapse
You need some elemental knowledge in C and then simply cut and paste the text in the files.
However, I think that it is more important to be able to compile from source and install the existing Huawei Linux kernel for the U8120. That is, can we compile from source all the code for Android 2.1-update1 and install on the U8120?
It might be good to try to get CyanogenMod on the U8120 for the kernel version that Huawei provides. Then, we can cut down the 1.5MB patch into smaller parts, and even try to get the drivers included in the Linux kernel.
I have not idea how to compile Android 2.1-update1 and get the plain old android source on the phone. I am willing to invest the CPU clocks to compile it, though.
cedric123 said:
Who can do That?
Kallt_kaffe meaby?
Click to expand...
Click to collapse
Dunno, it's quite a huge and advanced task.
Sent from my Vodafone 845 using XDA App
maybe we can get some kernel developers from the desire topic to help us?
I have send Benee, deovferreira, Kali- a PM maybe they could help us
nicoderboss said:
Dunno, it's quite a huge and advanced task.
Sent from my Vodafone 845 using XDA App
Click to expand...
Click to collapse
Can we just replace the normal kernel in the command list for the new kernel so you apply patch in the new kernel(u8150)froyo kernel?
I have had contact with benee a kernel developer for the htc desire. He is willing to help but he needs a device so he can test kernels he build. It is not possible to build kernels without a device because this is a huge project without a good base.
Maybe we can setup a fund raiser to get him a device?
Hello,
I'm trying to build a custom kernel for the atrix 2.
I'm confused whether it is the omap kernel or the goldfish kernel
It has a Omap proccessor but i found init.goldfish.sh
And all the board says is P3
uname -a:
Code:
Linux localhost 2.6.35.7-gac99e44 #1 SMP PREEMPT Wed Sep 21 17:27:49 PDT 2011 armv7l GNU/Linux
Thanks in advanced
tcf38012 said:
Hello,
I'm trying to build a custom kernel for the atrix 2.
I'm confused whether it is the omap kernel or the goldfish kernel
It has a Omap proccessor but i found init.goldfish.sh
And all the board says is P3
uname -a:
Code:
Linux localhost 2.6.35.7-gac99e44 #1 SMP PREEMPT Wed Sep 21 17:27:49 PDT 2011 armv7l GNU/Linux
Thanks in advanced
Click to expand...
Click to collapse
You are going to want to use the omap kernel. Motorola uses a hybrid omap/goldfish kernel for most of thier devices.
I have been working on the CM7 kernel and I have just been using the omap, and it is working just fine with kexec.
As for the board, it will not matter, because you will need to pull the .so files for most of the functions from the phone, from our current kernel on the device, there are also several library files that are important as well.
I would advise you take a look at one of the opensource android kernel how-to docs and see what I mean. The source code that Moto has provided us is incomplete, so building even a stock kernel is not very likely, with out the important modules, libraries, etc.
The how to for cyanogenmod kernel building is a very good example of how to do this.
jimbridgman said:
You are going to want to use the omap kernel. Motorola uses a hybrid omap/goldfish kernel for most of thier devices.
I have been working on the CM7 kernel and I have just been using the omap, and it is working just fine with kexec.
As for the board, it will not matter, because you will need to pull the .so files for most of the functions from the phone, from our current kernel on the device, there are also several library files that are important as well.
I would advise you take a look at one of the opensource android kernel how-to docs and see what I mean. The source code that Moto has provided us is incomplete, so building even a stock kernel is not very likely, with out the important modules, libraries, etc.
The how to for cyanogenmod kernel building is a very good example of how to do this.
Click to expand...
Click to collapse
you mentioned that it is working with kexec. Is kexec really working, or does it still have the same problems as the razr does with cpu1 not coming up and stuff?
lkrasner said:
you mentioned that it is working with kexec. Is kexec really working, or does it still have the same problems as the razr does with cpu1 not coming up and stuff?
Click to expand...
Click to collapse
kexec ONLY has the ability to use one CPU. If you use setCPU or similar and set your CPU speeds accordingly, you will never be able to tell the second CPU is not being used. It took some playing with setCPU to get it right, and it was different for 3 different phones that I did it with.
I have good news - Acer fixed kernel sourses for E350!
I complitely unpack this and get Mediatek folder. This is it's folder:
Code:
narod.ru/disk/63330748001.505f7027fe3648263f598fa74cd1e92a/mediatek.zip
Instructions for unpacking:
All actions must be on Linux OS (for example Ubuntu 12.04)
1. Download Acer Kernel Sourses:
Code:
global-download.acer.com/GDFiles/Document/App.%20Guide/App.%20Guide_Acer_1.0_A_A.zip?acerid=634873347782030348&Step1=SMART%20HANDHELD&Step2=LIQUID%20GALLANT&Step3=E350&OS=ALL&LC=en&BC=ACER&SC=PA_7
And put this to Desktop
2. Open Terminal and input this commands:
Code:
cd /home/user_name/Desktop
Where user_name is name of your User.
Code:
unzip ./App.\ Guide_Acer_1.0_A_A.zip
Code:
cd ./App.\ Guide_Acer_1.0_A_A
Code:
tar -xf Acer_AV041_E350_1.000.18_WW_GEN1_opensource.tar.gz
If all right, you get folder Acer_AV041_E350_1.000.18_WW_GEN1_opensource with content:
Code:
bootable external kernel mediatek prebuilt system
I don't know how to work with kernel sourses, but i think there are people who know.
P.S. Sorry, but my stats don't allow me to insert the links.
back37 said:
I have good news - Acer fixed kernel sourses for E350!
I complitely unpack this and get Mediatek folder. This is it's folder:
Code:
narod.ru/disk/63330748001.505f7027fe3648263f598fa74cd1e92a/mediatek.zip
Instructions for unpacking:
All actions must be on Linux OS (for example Ubuntu 12.04)
1. Download Acer Kernel Sourses:
Code:
global-download.acer.com/GDFiles/Document/App.%20Guide/App.%20Guide_Acer_1.0_A_A.zip?acerid=634873347782030348&Step1=SMART%20HANDHELD&Step2=LIQUID%20GALLANT&Step3=E350&OS=ALL&LC=en&BC=ACER&SC=PA_7
And put this to Desktop
2. Open Terminal and input this commands:
Code:
cd /home/user_name/Desktop
Where user_name is name of your User.
Code:
unzip ./App.\ Guide_Acer_1.0_A_A.zip
Code:
cd ./App.\ Guide_Acer_1.0_A_A
Code:
tar -xf Acer_AV041_E350_1.000.18_WW_GEN1_opensource.tar.gz
If all right, you get folder Acer_AV041_E350_1.000.18_WW_GEN1_opensource with content:
Code:
bootable external kernel mediatek prebuilt system
I don't know how to work with kernel sourses, but i think there are people who know.
P.S. Sorry, but my stats don't allow me to insert the links.
Click to expand...
Click to collapse
Unable to compile module. Some files still missing.
legale said:
Unable to compile module. Some files still missing.
Click to expand...
Click to collapse
May be, but no one said it would be easy...
In the directory mediatek for me miss the sub directory build-----> mediatek/build/......
I have try to compile this source but have more problem. When start with make i see that miss this directory mediatek/build/kernel/Makefile
I have try to change the line include ....mediatek/build/kernel/Makefile with include ....mediatek/source/kernel/Makefile but when start with compile i have error with other thing.
bye.
MT6575 working sources device TCL E928
sourceforge.net/projects/alcatel/files/TCL_E928_20121114.tar.xz/download
i've successfully compiled cifs.ko kernel module for my philips w732 (vermagic '3.0.13 preempt mod_unload armv7', almost without changing kernel config.
Hi legale
Thank you for your link but i have this problem:
../mediatek/build/Makefile:13: *** TARGET_PRODUCT/PROJECT is not set.
I have copy the miss directory into acer kernel but i have this problem.
Where i must set target product for you?
erlucky said:
Hi legale
Thank you for your link but i have this problem:
../mediatek/build/Makefile:13: *** TARGET_PRODUCT/PROJECT is not set.
I have copy the miss directory into acer kernel but i have this problem.
Where i must set target product for you?
Click to expand...
Click to collapse
you should enter PROJECT parameter.
e.g. make PROJECT=jrdsh15_td_ics
legale said:
you should enter PROJECT parameter.
e.g. make PROJECT=jrdsh15_td_ics
Click to expand...
Click to collapse
Ok good.....
but now the problem is missing directory mediatek/build and custom for acer liquid gallant duo......
jrdsh15_td_ics is for alcatel device not for my phone....:crying:
I have send email to mediatek for this.
legale said:
you should enter PROJECT parameter.
e.g. make PROJECT=jrdsh15_td_ics
Click to expand...
Click to collapse
What About Missing Directoery ?
pradeep_kus said:
What About Missing Directoery ?
Click to expand...
Click to collapse
In the acer source missing some directory into mediatek/
I dont have mediatek/build
mediatek/source
The proprietary driver for acer liquid gallant duo in this two directory......
If i try to make kernel i have error.
I hope mediatek reply my email.
Yeah!
Demeter from china-iphone, complitely compile kernel and working boot.img for Philips W732!
Code:
forum.china-iphone.ru/viewtopic.php?f=31&t=23637&p=894418#p894418
His sourses: https://github.com/Demeterp/w732_kernel_src
So what should be released from Acer to help developers create custom roms, especially jelly bean ones?
jorgoxl said:
So what should be released from Acer to help developers create custom roms, especially jelly bean ones?
Click to expand...
Click to collapse
About Jelly Bean i don't know, but it must help to tune cpu governor (in default cpu works on deep sleep, 166 and 1001, but don't use 250 and 500), may be it help to solve the problems with proximity and light sensors... etc.
In theory you can take JB original sourses from Google and mediatek sources for ICS, and may be you can run JB from other device (for example last firmware from JY G2 MT6575)... But so far no one has yet tried to do it... Sorry for my English
Ok guys!i would appreciate it if you could solve the problem with governor!(ondemand mode 166,250,500,1000)!it works only 500-1000!A new custom rom maybe?thaks!
Sent from my E350 using xda app-developers app
Can this src work to build jb?
Could any help make a ics or jb kernel for the
Alcatel t pop 4010x and does anyone know of a Rom also
Sent from my SK17i using xda app-developers app
Can i used thsi kernel on mtk6575 x401 mobile phone?¿
Can anyone help port this to Alcatel 4010 t pop its spec it mt6575 CPU powervr gpu 512ram 150mb Rom please help also id like to port xperia sytle Rom
Sent from my SK17i using Tapatalk 2
If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Come to #omni on Freenode, and have a chat to one of the core developers (they are listed at the top of the user list) - they will be able to help you get your device merged
Please note, in order to add a new device, we will require a maintainer on an ongoing basis for it, to ensure someone is able to investigate bugs that users report on a device. Without this, we unfortunately cannot enable nightly builds for a device.
will a cm kernel tree work for the most part with just a few changes?
azoller1 said:
will a cm kernel tree work for the most part with just a few changes?
Click to expand...
Click to collapse
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged
pulser_g2 said:
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
Click to expand...
Click to collapse
Along these lines, do NOT remove copyright attributions of a changed file. You may ADD copyrights to a header, but do NOT remove anything.
maxwen said:
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged
Click to expand...
Click to collapse
Most likely kernel change will be that reverting out that MDP sync point mess used by CM's AOSP+CAF frankendisplay. Can't link to it from my current location.
I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig
TF300T
OK here goes..
For the Asus Transformer TF300T the kernel forked from the CyanogenMod github:
https://github.com/scanno/android_kernel_asus_tf300t/tree/android-4.3
And the device tree, modified to get OmniROM to finish the build and get a bootable result:
https://github.com/scanno/android_device_asus_tf300t/tree/android-4.3
Hopefully it will be added to the OmniROM github.
n3ocort3x said:
I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig
Click to expand...
Click to collapse
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere
@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆
AL_IRAQI said:
@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆
Click to expand...
Click to collapse
Already on my github
https://github.com/Grarak/android_device_samsung_i9500
kernel tree
https://github.com/Grarak/android_kernel_samsung_exynos5410
proprietary
https://github.com/Grarak/proprietary_vendor_samsung
exynos 5410 repos:
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5410
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5-insignal
https://github.com/intervigilium/android_hardware_samsung_slsi_openmax
pretty much ^^
I'd like to maintain for l900 and i605 (Sprint and Verizon Galaxy Note 2).
device trees
https://github.com/omnirom-slickrick/android_device_samsung_l900 (sprint tree)
https://github.com/omnirom-slickrick/android_device_samsung_i605 (vzw tree)
https://github.com/omnirom-slickrick/android_device_samsung_t0lte (note 2 common tree)
https://github.com/omnirom-slickrick/android_device_samsung_smdk4412-common (same as tree on omnirom github but actually more updated and device settings added back)
kernel
https://github.com/omnirom-slickrick/android_kernel_samsung_smdk4412 (just have needed device settings commits added back in)
thracky said:
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere
Click to expand...
Click to collapse
we already making progress but it needs more work to be done.. at least we are now in system with working wifi, and display but modem doesent work.. something for tomorrow, and i dont want to hijack this thread too sorry if my question was in the wrong section but i thought i mention it because of the post above mine. nevermind i cann offer to maintain m7ul as already discussed with maxwen and oin IRC but a lot of work needs to be done:
here are my sources, device trees are usable but kernel needs more work as said above:
device trees:
https://github.com/n3ocort3x/android_device_htc_m7ul
https://github.com/n3ocort3x/android_device_htc_m7-common
https://github.com/n3ocort3x/android_device_htc_msm8960-common
kernel: its a modified one but its no problem to bring it back to stock features and will push as soon asap the modem stuff is sorted out
https://github.com/n3ocort3x/android_kernel_htc_m7
EDIT modem fixed, only BT left
@sykomaniac , look at first post and become a maintainer
pulser_g2 said:
If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Post a link here to the device tree (and kernel repository) for review, and tell us what device it is (give model numbers and board names and as many details as possible )
Click to expand...
Click to collapse
We have quite a few things that aren't working like bluetooth, camera is buggy, H/W vsync, gps, and fm radio.
https://github.com/SeannyM/android_device_samsung_kylessopen
https://github.com/SeannyM/ba2x-kernel
gt-s7560m with quadband gsm and 850/1900/2100 WCDMA/UTMS
We have a MSM7227a cpu armv7 clocked at 1008mhz stock.
645mb of usable ram
4gb of storage with 1.7 usable
233 dpi 800x480 4inch screen
Adreno 200 enhanced
5mp camera 1.3 front facing
hopefully we can get something official
single sim
Gtab2 10.1 Wifi & 3G (p5110 & p5100)
There you have my device tree for omni
p5110 :
https://github.com/sevenup30/android_device_samsung_p5110
p5100:
https://github.com/sevenup30/android_device_samsung_p5100
omap4-common (had to edit it cuz of duplicate libion entry):
https://github.com/sevenup30/android_device_samsung_omap4-common
other dependencies required from CM & Themuppets
kernel :
https://github.com/CyanogenMod/android_kernel_samsung_espresso10
samsung proprietary:
https://github.com/TheMuppets/proprietary_vendor_samsung
samsung hardware:
https://github.com/CyanogenMod/android_hardware_samsung
apps samsung service:
https://github.com/CyanogenMod/android_packages_apps_SamsungServiceMode
Everything is working (sound / wifi / bluetooth / video playback) BUT!
I must edit build.prop by hand to get sound working until omni build process take care of "product_build_prop_overrides" into custom_XXXX.mk
see:
http://forum.xda-developers.com/showthread.php?t=2484747
Original Samsung Galaxy Note
Samsung n7000 initial bringup:
Modified CM n7000 device: https://github.com/chasmodo/android_device_samsung_n7000/tree/android-4.3
Modified CM galaxys2-common: https://github.com/chasmodo/android_device_samsung_galaxys2-common/tree/android-4.3
CM smdk4412 kernel: https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/cm-10.2
Samsung proprietary stuff: https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-10.2
Samsung hardware tree untouched from OmniRom.
Device info:
Board platform - exynos4
SOC - exynos4210
Board name - smdk4210
Kernel specifics - unified kernel and recovery
It compiles fine using the repos listed above, but throws up a kernel assert error when flashing the Rom. Several compilers for different devices complained about it in the 'All the answers' thread. The way out of this is to flash a CM10.2 kernel immediately after the Rom flash aborts, then Omni boots up fine.
What works:
1. telephony
2. mms
3. WiFi
4. GPS
What doesn't work:
1. data
2. bluetooth turns off as soon as you turn it on
3. both sdcards are invisible from Android; all your stuff is there when you drop into recovery, though
4. Settings/Storage FC when tapped - see #3
5. Performance options also FC
6. Notification drawer cannot be pulled down
Camera cannot be tested because it shuts down as soon as you start it, saying: "No external storage available" - again, see #3
Galaxy Note II / N7100 (International)
Samsung Galaxy Note II / N7100 Bring up details.
I have a working build of the Omni rom for the N7100. Below are the details on what is working and not working. i have been using it for the last 2 days, so far not crashes or reboots all seems to be working fine. i cherry picked a few commits and included it into my build
Working :
WIFI
DATA -3G & 2G
Telephony & MMS & SMS
GPS
Sound
Camera (Both Front and Back)
SD card
Performance control
Notification drawer & Lights
Multi-Window
roadrunner
Not Working :
BT
Backlights(if i install a custom kernel then the lights work)
Device Tree for N7100 - https://github.com/tilaksidduram/device_samsung_n7100
Device smdk4412-common - https://github.com/tilaksidduram/android_device_samsung_smdk4412-common
smdk-4412 Kernel (3.0.100) - https://github.com/CyanogenMod/android_kernel_samsung_smdk4412
samsung hardware - https://github.com/CyanogenMod/android_hardware_samsung
DEVICE: GT-N7100
sources
https://www.github.com/UtkarshGupta/android_device_samsung_n7100
https://www.github.com/omnirom/android_device_samsung_smdk4412-common
https://www.github.com/omnirom/android_hardware_samsung
https://www.github.com/omnirom/android_kernel_samsung_smdk4412
https://www.github.com/TheMuppets/proprietary_vendor_samsung
Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.
dstruct2k said:
Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.
Click to expand...
Click to collapse
I think a few are... There has been chat of it in the IRC channels.
Device name: LG Optimus 4X HD
Codename: P880
Board name: X3
Chipset: Tegra 3 AP33
Everything works, except button backlight.
https://github.com/Adam77Root/android_device_lge_p880
https://github.com/Adam77Root/android_kernel_lge_x3
https://github.com/TheMuppets/proprietary_vendor_lge
Hi,
I wanted to compile a custom kernel with KVM for the ROG Phone 5 on the latest Android 12 (EU variant) so I looked at the Kirisakura kernel for base (from @Freak07) and I looked at the script that starts compiling the kernel. I could not find some things that was required such as the Google's GCC thing or the "DU_Tools" but I still managed to start compiling the kernel after editing the defconfig file using make menuconfig to enable KVM. Once I did that I ran the script but after like two minutes I got an error (Error 2).
So can someone help me doing this please?
Thanks.
Hey Alex - been looking in to creating a build script using docker for this out of curiosity.
Out of interest though - how are you planning to use KVM once it's enabled?
Moved all of my development efforts from XDA.
chrisaw said:
Hey Alex - been looking in to creating a build script using docker for this out of curiosity.
Out of interest though - how are you planning to use KVM once it's enabled?
Click to expand...
Click to collapse
Hey, I didn't tried using docker (because I don't know how to xD) and I want to use KVM because I heard that the Snapdragon 888 is compatible with it so I was thinking about doing a Windows 10 arm VM with native performance.
chrisaw said:
Got this building cleanly and producing a flashable ZIP:
GitHub - cawilliamson/Kirisakura_ANAKIN_ROG5 at master_release_s_1
Contribute to cawilliamson/Kirisakura_ANAKIN_ROG5 development by creating an account on GitHub.
github.com
Build instructions:
Code:
$ cd <kernel sources>/build/
$ ./build.sh
You will need Docker installed on your system via whatever means necessary and this is really aimed at Linux systems although you could also run the build on a Windows or Mac PC if you setup Docker correctly.
Click to expand...
Click to collapse
Thanks I will try that
Moved all of my development efforts from XDA.
chrisaw said:
Your chances of getting that working easily are slim.
Adding the KVM support to the kernel is easy but the problem you then get is about switching the CPU to "HYP" mode. (just based on what I read online)
If you have further info about this I'd be interested in reading it and seeing if we can get something which works. What I can tell you is that /dev/kvm does not get created simply by the changes I made.
Also be aware that /proc/config.gz is spoofed in these kernels with the "stock" config file so running something like "zcat /proc/config.gz" wont show KVM is enabled but it is.
Click to expand...
Click to collapse
Yes you are R8! Without hyp we can't enable KVM support.. but i found a site where telling android 13 has full KVM support.. but don't know it's true or not..
Because KVM support only available on some snapdragon chipset only..
Redirect Notice
Can't all of this work be ported to the Infinix NOTE 8 on Android 10 too?