Related
Hello everybody!
I need an advice on where to get drivers (or what kernel options to use) for my phone (Motorola Quench XT3) build on Qualcomm MSM7227 chpset.
It would be cool to be able to compile new version of Android from source, like gentoo or LFS; we wouldn't depend on Motorola's software updates. The only thing that seems missing is drivers and kernel configuration. (May be I am wrong - correct me)
So how do I find out what drivers/kernel options to use for my hardware?
Any help is appreciated. I would make an understandable guide for compiling Android for Motorola Quench XT3 if I succeed.
Upd:: Motorola Quench XT3 is a "Boston Orange" phone. Look for mods on cyanogenmod forum, in the z71 variants section.
Therein lies the problem.
Linux drivers for phone chipsets (mostly Qualcomm) are often provided as binary lumps for a specific kernel version. When kernel sources are made available for a specific phone then we can generally compile a full AOSP build by making sure that the kernel we build is compatible with the binary blobs, this get more difficult as the framework gets upgraded and depends on features of newer kernels.
So the things to look for are:
What version of Andriod does it run, what do you want to run?
Have Moto released kernel sources yet?
What are the GPU/Radio/BT/Wifi/Audio chipsets
Do we have binder-friendly driver source available for any of the above.
This is all _hard_ stuff and generally if you've never compiled a Linux kernel before this is not the place to start.
Linux drivers for phone chipsets (mostly Qualcomm) are often provided as binary lumps for a specific kernel version.
Click to expand...
Click to collapse
This is OK as long as binary drivers are available for new kernels, I guess.
What version of Andriod does it run, what do you want to run?
Click to expand...
Click to collapse
It has Android 1.6, and my goal is 2.2.
Have Moto released kernel sources yet?
Click to expand...
Click to collapse
yes, they have sources available for download. I downloaded, but couldn't figure out what ".config" they use, in the bundled script "Android.mk" that depends on external variable KERNEL_DEFCONFIG.
What are the GPU/Radio/BT/Wifi/Audio chipsets
Click to expand...
Click to collapse
Ok, I am trying to find that out. Couldn't find specs in the net (including Motorola website), they only give processor (Qualcomm MSM7227) Is there a command like lspci on Android?
if you've never compiled a Linux kernel before this is not the place to start
Click to expand...
Click to collapse
What is the place to start then? Actually I've configured and compiled kernels for several desktops/laptops, they are fine. I am not any kind of expert, but may be it isn't too difficult to build a working 2.2 Android. There's almost no hope to get it from Motorola. Also I don't care about Motorola-specific software.
Overall, thank you for a good & quick response. I will try to figure out exactly what hardware it uses, and post it here.
P.S.: what else people do to upgrade their phones when it isn't supported by manufacturer?
It's MSM7227 !!!
Hello people!
After a lot of reading I start to understand concepts. Turns out, my phone has a good and popular chipset Qualcomm MSM7227. The same chipset is used in, say, HTC Aria and HTC Legend, which are well supported by cyanogen mod. And looks like chipset determines all major drivers I need! (probably except minor things like flash light)
So, I need help of somebody who knows these things better than me in the following questions:
What could be a difference in firmware between (say) HTC Legend and Motorola Quench XT3, which share the same chipset?
Is there a "generic" build for MSM7227?
Any input is greatly appreciated.
Unfortunately that is rarely the whole of it. Slight differences in implementation can make all the difference. E.G. the radio itself has a firmware that may fundamentally change the interface presented to the CPU. Sound/Display/3D are also up in the air.
Short version, if you can find out the chipset driving each of the above (not just the CPU/Radio SOC) and you can either find:
1. 2.2 binary blobs from another phone
2. Open source drivers that can be compiled for the 2.2 kernel
Then you may be ok.
The reason I said that this may not be the place to start is that what you are trying to do here is get binary blob drivers running for a kernel they were not intended to run with, debugging that is some heavy magic on a desktop, even more so on an embedded device.
I also have the same phone and i was looking for a froyo mod.
I would be willing to test it out (i have the same phone ).
I should warn you though i have no mobile phone hacking experience!
SilentMobius, thank you much for good explanations!!
I googled more, and I have strong suspicion that Motorola Quench XT3 is the same as "Orange Boston" phone. That piece of hardware has been manufactured by many companies under many names (GigaByte G1305 Codfish, Apanda A60, WellcoM A88, Vibo A688, Cincinnati Bell Blaze f800, Commtiva Z71, Muchtel A1, Chinavision Excalibur, Motorola Greco, Nexian A890).
Though I am not sure that orange boston hacks would apply to Quench XT3. Is there a way to check their compatability (in hardware, radio firmware, etc) ?
Cyanogenmod
Turns out we are lucky - Quench XT3 is a part of "Boston Orange", and it runs cyanogenmod. This is very nice, and there is no need to make rom from scratch. Moreover, everything I was thinking of is already done for this phone.
Look on cyanogenmod forums in z71 variants section for mods and other information.
Thanks a lot
Uh, could anyone help me?
I rooted the phone with Universal AndRoot but when i click on z41 on rom manager it gets an error.
Help?
qwerty156 said:
Uh, could anyone help me?
I rooted the phone with Universal AndRoot but when i click on z41 on rom manager it gets an error.
Help?
Click to expand...
Click to collapse
In ROM Manager the phone is known as an Commitiva A71. You are selecting the wrong phone.
Hello peeps,
I see there is not much activity going on between the users of Fit.
I need a list of all the people who are here and using the fit phone.
Members try to participate actively and help get past the Low Activty Barrier
Also, I wanna know who is ready to do what. These are the perspectives what I am looking for. Users can sign up for multiple posts also!
->Kernel Developement Team
-> Custom ROM Developers
-> Maintainers of Custom ROM and Helpers
-> Beta Testers
-> Mods Informer
-> Theme Creator
-> THeme Porter
-> Rom Testing
-> Custom ROM testing
-> Problem Fixes Testing
-> Doubt-clearance Member
-> DEV. Teacher!
As A initiative, I am also creating a Twitter account. Anybody who would like to create a Facebook Group for the phone's DEV and Testing team is free to do so!
Please Enroll your name below and tell us what time can you spend for what purpose!
Please Help Fit have a Bright Future! Please E-Mail us your Selected Criteria. I will add you to the mailing list. You can get all teh information on what the DEVs. are working about and stuff!
The E-mail Address of the Fit DevTeam-> [email protected]
Twitter ID-> @dev_GalaxyFit
Follow us on Twitter for all the updates on Developments
Regards,
Rohan Mallya.
I sign up for
->Custom Rom DEV.
-> Maintainers of Custom ROM and Helpers
->Mods Informer
Ok i want to be kernel developer and doubt clearance but i have to learn to develop kernel
omarhasan76 said:
Ok i want to be kernel developer and doubt clearance but i have to learn to develop kernel
Click to expand...
Click to collapse
Take your time! And, share the sources from where you are learning! Follow us on Twitter
I sign up for
->Beta tester
->ROM and Custom ROM tester
->Doubt Clearance member
Will add up responsibilities as and when I learn
spike1902 said:
I sign up for
->Beta tester
->ROM and Custom ROM tester
->Doubt Clearance member
Will add up responsibilities as and when I learn
Click to expand...
Click to collapse
Thank yoU!
Follow us on Twitter.
If you want, Just e-mail us your real name and your designation! You will be updated with amazing stuff and things
Sticky'd the the thread for you, good luck with Development.
Also for help with kernel development try my good friend Doomlord.
http://forum.xda-developers.com/member.php?u=2784807
->Beta tester
->ROM and Custom ROM tester
and whatever i learn in the process
Kernel Development
This is a general guide for building kernels and modifying them. Device-specific articles for getting the kernel source and setting up the build environment are provided in their respective sections.
Getting the kernel source
The source for your kernel must be made available by your device's manufacturer in order to comply with the GPL.
I dont know where to get it
Setting up the environment
Instructions for setting up the development environment should be included in your source code package. This should tell you the parts of the Android Open Source Project that must be in your working directory in order to allow the kernel to build. It will tell you what version as well. All of the Android Operating System source code is available at [android.git.kernel.org] and most projects are mirrored at [github.com/android]. Both are accessible via your internet browser as well as git.
Modifying the kernel
After the kernel source has been downloaded and your environment is set up, you can begin modifying the kernel. It is recommended (in most cases mandatory) that you run the standard "make xxx_defconfig" for your device before modifying the configuration.
Running
make
or
make -jX [where X is the number of operations to perform at a time]
at this point will make the stock kernel that your phone's official system has. To modify it, we can go two ways: 1) modify the file '.config' in a text editor, or 2) run
make menuconfig
for a graphical interface.
Modifying '.config' with menuconfigEdit
Typing
make menuconfig
will bring up the aforementioned graphical interface for modifying your kernel. Striking the "y" key when an option is selected (with "< >" or "[ ]" before it) will include it in the kernel. Striking the "m" key will add those options with a "< >" as a Linux kernel module (*.ko).
Adding tethering support (netfilter/iptables)Edit
Adding VPN support (TUN)
Adding Linux swap support
Adding ext3/ext4 support
Mofifying '.config' manually
The alternative to using menuconfig is editing '.config' in your preferred text editor. Options that are not to be included in the build are commented out with a "#". Options that are to be included inside the kernel image are uncommented and have the value of "y". Options with the value "m" are to be built into loadable kernel modules.
Adding tethering support (netfilter/iptables)Edit
Adding VPN support (TUN)Edit
Adding Linux swap supportEdit
Adding ext3/ext4 supportEdit
Packaging and flashing your kernelEdit
Additional stepsEdit
You may find that you want to play around with '.config', but don't want to lose your configuration. You can rename your '.config' to whatever you want and give it the suffix "_defconfig" and put it in "arch/arm/configs/" for the next time you wish to use it.
For example: if you had a kernel that had tethering and ReiserFS support, and you wanted to try enabling VPN without breaking your current setup, you could rename your '.config' to 'my_rfs_tethering_defconfig' and move it to "arch/arm/configs/". The next time you wanted to make this kernel you could run
make my_rfs_tethering_defconfig
and have your kernel configuration just as you left it.
Note that this would overwrite your kernel configuration stored in '.config'
omarhasan76 said:
Kernel Development
This is a general guide for building kernels and modifying them. Device-specific articles for getting the kernel source and setting up the build environment are provided in their respective sections.
Getting the kernel source
The source for your kernel must be made available by your device's manufacturer in order to comply with the GPL.
I dont know where to get it
Setting up the environment
Instructions for setting up the development environment should be included in your source code package. This should tell you the parts of the Android Open Source Project that must be in your working directory in order to allow the kernel to build. It will tell you what version as well. All of the Android Operating System source code is available at [android.git.kernel.org] and most projects are mirrored at [github.com/android]. Both are accessible via your internet browser as well as git.
Modifying the kernel
After the kernel source has been downloaded and your environment is set up, you can begin modifying the kernel. It is recommended (in most cases mandatory) that you run the standard "make xxx_defconfig" for your device before modifying the configuration.
Running
make
or
make -jX [where X is the number of operations to perform at a time]
at this point will make the stock kernel that your phone's official system has. To modify it, we can go two ways: 1) modify the file '.config' in a text editor, or 2) run
make menuconfig
for a graphical interface.
Modifying '.config' with menuconfigEdit
Typing
make menuconfig
will bring up the aforementioned graphical interface for modifying your kernel. Striking the "y" key when an option is selected (with "< >" or "[ ]" before it) will include it in the kernel. Striking the "m" key will add those options with a "< >" as a Linux kernel module (*.ko).
Adding tethering support (netfilter/iptables)Edit
Adding VPN support (TUN)
Adding Linux swap support
Adding ext3/ext4 support
Mofifying '.config' manually
The alternative to using menuconfig is editing '.config' in your preferred text editor. Options that are not to be included in the build are commented out with a "#". Options that are to be included inside the kernel image are uncommented and have the value of "y". Options with the value "m" are to be built into loadable kernel modules.
Adding tethering support (netfilter/iptables)Edit
Adding VPN support (TUN)Edit
Adding Linux swap supportEdit
Adding ext3/ext4 supportEdit
Packaging and flashing your kernelEdit
Additional stepsEdit
You may find that you want to play around with '.config', but don't want to lose your configuration. You can rename your '.config' to whatever you want and give it the suffix "_defconfig" and put it in "arch/arm/configs/" for the next time you wish to use it.
For example: if you had a kernel that had tethering and ReiserFS support, and you wanted to try enabling VPN without breaking your current setup, you could rename your '.config' to 'my_rfs_tethering_defconfig' and move it to "arch/arm/configs/". The next time you wanted to make this kernel you could run
make my_rfs_tethering_defconfig
and have your kernel configuration just as you left it.
Note that this would overwrite your kernel configuration stored in '.config'
Click to expand...
Click to collapse
You wrote it or Got it? :/
got it here is a source code some body download and upload it for s5670
https://opensource.samsung.com/reception.do?first=F
omarhasan76 said:
got it here is a source code some body download and upload it for s5670
https://opensource.samsung.com/reception.do?first=F
Click to expand...
Click to collapse
SUre thanks! Checking it out! I have teh SOurce code ALready!
Then upload it or we have to sign up for downloading
omarhasan76 said:
Then upload it or we have to sign up for downloading
Click to expand...
Click to collapse
Oh kay! I will upload it!
I will upload it in an hour! I am downloading the source code of Galaxy i9000! So, I will upload the Fit source code as soon as the i9000 one is over, fine?
as you told to share our researc i fond a step by step tutorial to prepare kernelhttp://forums.androidcentral.com/htc-hero-rooting-roms-hacks/8072-how-build-your-own-kernel-package-source.html
KK
Recently I decided to learn application development and building custom ROMs so i searched online for sources to learn. I found the following playlist uploaded by the user Marakana on youtube :
http://www.youtube.com/watch?v=Mf7z_mrce00&feature=bf_next&list=PLE953C0B85B50AB62&lf=results_main
There is also a book named "Learning Android" written by the same person who uploaded the videos above. I am new to android development and new to Java even,and I found these tutorials very useful ..... I am posting this because this may help someone
I sure does Help! Thank you for your contribution
krishnakanth_590 said:
Recently I decided to learn application development and building custom ROMs so i searched online for sources to learn. I found the following playlist uploaded by the user Marakana on youtube :
http://www.youtube.com/watch?v=Mf7z_mrce00&feature=bf_next&list=PLE953C0B85B50AB62&lf=results_main
There is also a book named "Learning Android" written by the same person who uploaded the videos above. I am new to android development and new to Java even,and I found these tutorials very useful ..... I am posting this because this may help someone
Click to expand...
Click to collapse
Thanks Man!
I am limited to 5 thanks per day..So, I cant thank you! Sorry!
Dude, for all your effort, I can just thank you! My Sister owns this device! It is shocking to see you in here! I thought you would be developing only for SL, S and S2 P:
---------- Post added at 04:29 PM ---------- Previous post was at 04:28 PM ----------
Is Android based on Linux?
Fedora has released Fedora-17-beta-armhfp-xfce, a system image compatible with Tegra devices. A kernel image is not included. So, my first question is: Are there any kernels being tweaked and developed by xda members that are compatible with the the Fedora release? If not, it appears from the many posts in the forums asking about Linux on arm tablets that there is a void to be filled.
I for one want to be free of big brother "Google" and regain not only full control over my device, but my privacy too. Richard WM Jones describes how he installed Fedora on a Trim Slice with Tegra processors. rwmj.wordpress.com/2012/02/29/trim-slice-pt-3/ Can't this be done with the Xoom using a hacked kernel being tweaked/developed by an xda member? Is a kernel already available with drivers that make the Xoom's hardware fully functional in a Fedora installation?
Can the "U boot" ROM supplied with the Slice be ported to the Xoom? We need help from knowlegeable, experienced developers here at xda to make the possibilities a reality.
Thanks,
Armido
Rooted Xoom M601, Quad Band, wireless+3g, Stock Honeycomb version 3.2 Primary usage: Linux Open source Navigation program OpenCPN - via Galoula's Linux Installer/Debian lxde.
Fedora does not replace android but can be installed.
armido said:
Fedora has released Fedora-17-beta-armhfp-xfce, a system image compatible with Tegra devices. A kernel image is not included. So, my first question is: Are there any kernels being tweaked and developed by xda members that are compatible with the the Fedora release? If not, it appears from the many posts in the forums asking about Linux on arm tablets that there is a void to be filled.
I for one want to be free of big brother "Google" and regain not only full control over my device, but my privacy too. Richard WM Jones describes how he installed Fedora on a Trim Slice with Tegra processors. rwmj.wordpress.com/2012/02/29/trim-slice-pt-3/ Can't this be done with the Xoom using a hacked kernel being tweaked/developed by an xda member? Is a kernel already available with drivers that make the Xoom's hardware fully functional in a Fedora installation?
Can the "U boot" ROM supplied with the Slice be ported to the Xoom? We need help from knowlegeable, experienced developers here at xda to make the possibilities a reality.
Thanks,
Armido
Rooted Xoom M601, Quad Band, wireless+3g, Stock Honeycomb version 3.2 Primary usage: Linux Open source Navigation program OpenCPN - via Galoula's Linux Installer/Debian lxde.
Click to expand...
Click to collapse
May 26, 2013: The short answer is apparently no. Not even Ubuntu Touch will replace the android core. However a growing number of linux distributions can be installed using installers like 'Linux Installer' downloadable for free from GooglePlay. This includes Fedora. What is the point of having Ubuntu Touch on tablets if the rich, robust and numerous existing linux programs will not run on Ubuntu Touch?
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 -
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. So don't be an *** ****
*/
hi.. i'm already started make some modifications on ROM with other Brazilian DEV's for "Evertek S.A - SKMtek Genesis Tab GT7305"... we already found the source kernel from another Netbook or Development Board PC who uses the same SOC... but nothing already have been maked to kernel, we use the provided kernel from stock (Kernel 3.4.5+)... and about the ROM we already have two custom ROM's... One is Stock Modded (4.2.2) and another is KitKat Ported ROM from another Evertek Device... *Portuguese-Brazil Language Site/Forum
And we already make some modifications to this KK port...
- ROOT
- BusyBox
- Init.D support
- Build.Prop Mods
- SuperUser
- zipalign apps after boot
.. and other mods.
we already make too much on ROM but nothing about kernel... we want make a better kernel with optimizations and a better TCP/Clock Table, More Governors , More I/O Scheduler and maybe Overclock to 1600mhz to start after have a custom Kernel booting...
Now we need someone who understand about recovery's like CWM or TWRP and Kernel Compilation better than me to we can start make something awesome =D i think this can be used to another company's/Chinese tablets too, using the same SOC (WM8880) evidently... . . . (Found^^Working^^Recovery's)
i can't start testing here because if i flash this kernel using the Stock Recovery (WonderMedia Recovery tool) maybe i can possible brick my tablet... so if someone understand about CMW recovery to start would be nice =D
Update Progress / ChangeLog ¬
Code:
# 25/12:
- [STRIKE]Found Possible match [URL="http://forum.xda-developers.com/showthread.php?t=2305268"]CWM port[/URL] from [URL="http://forum.xda-developers.com/showthread.php?t=2216390"]Asus MeMo Pad 7{ME172V}[/URL] on XDA Forum[/STRIKE] #NOPE...
- FOUND WOKING [URL="http://blog.hadi-cpu.com/2013/09/cwm-recovery-6036-w8850-rc2.html"]CWM Recovery[/URL] from Malasya Blog from Generic WM8850 SOC tablet , Founded [URL="http://blog.hadi-cpu.com/2013/10/twrp-touch-wondermedia-wm8850-jb-version.html"]TWRP recovery[/URL] too but not tested (Thanks to #Rollidark to notify me about and #osinaldi to discover that from malasya blog) [Mirrors -> [URL="https://www.4shared.com/rar/2POyc0B0ba/CWM_WM8850_NSFAT-RC2.htm?sop=true"]CMW[/URL] -> [URL="https://www.4shared.com/rar/rJBfUTQF/TWRP-JB-NSFAT-WM8850.htm"]TWRP[/URL]] // [URL="https://www.facebook.com/groups/NewSmartFrenAndroTab/"]Facebook Group of Recovery Developers[/URL]
- Studying some way to introduce the missing Touch driver to kernel from [URL="https://gist.github.com/psachin"]psachin Github[/URL]|[URL="http://cdn.liliputing.com/wp-content/uploads/2013/01/rock_02.jpg"]apc-rock-II-[/URL]|[URL="https://github.com/psachin/apc-rock-II-kernel"]kernel[/URL] how already modded the Source to work with [URL="http://tinyurl.com/oqxmuam"]Generic Netbook[/URL] who uses the same SOC
-- Merry Christmas to #ALL
# ?? to 23~24/12:
- ROM JB and KK + ADV. Patch developed by Brazilian Dev's team
- found Source Kernel to WM8880 SoC
Brazilian Developers who already help this projects from forum - genesiseries :
Code:
# KK ROM:
- #paulomsilva2006 {KitKat ROM Port}
- #Rollidark {KitKat Patch}
- #Wcfuria
- #? - Pedro Alves
- #? - Pedro Victor
- #? - Walter Moretti
- #? - Moises Teixeira
Code:
# JB Stock ROM:
- #ylukasy {ROM Dev.}
- #Rollidark
- #paulomsilva2006
- +?
if i forget someone.. please comment below :highfive:
Reserved
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
funtikar said:
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
Click to expand...
Click to collapse
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
DvDwx. said:
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
Click to expand...
Click to collapse
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
funtikar said:
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
Click to expand...
Click to collapse
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
what a coincidence , I was wondering today when you will reply lol
ah I see too bad, maybe you will share it at techknowme forum, ... wow Malaysian ?, Im asking because I'm Malaysian, can you pm me the link where its shared?
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
tuyenat3 said:
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
Click to expand...
Click to collapse
man... i just don't want blame anyone but... to we can do something to your tablet we need the kernel source and that don't stay open to developers... on this Chinese tablets we have some little configurations to can work with... but the custom kernel project i need to abandon for two reasons... first i don't have much time to can work to create a stable and functional custom kernel to everyone... second i don't have a kernel source compatible with tablets... what i found is from a electronics engineering Project computer Board ... and to it can fit on tablet is missing too much drivers compatibles with to can work smoothly and functional... someday if i found a new source maybe i can try comeback developer something to that =#
please continue developing this project
I use a genesis 7305 his kernel is very poorly optimized would like to make this usable tablet sorry for my bad English I use Google translator ;-;
2021... I tried to put a Chinese rom, but I brick the tablet, it only responds to fastboot, when I put the sudo command fastboot flash:raw boot uzImage.bin ramdisk.bin and plug in the charger and press power it appears a genesis screen.
Boot FOSSEE-OS from SCARD | FOSSEE-Laptop
laptop.fossee.in
GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
A low cost fossee-laptop based on wm8880 ARMv7 SoC - GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
github.com