1.does ICS run on Linux kernel 3(default)
2.cant we use kernel 3 on our X8
3. if 1 and 2 is yes, why dont we try to build kernel 3 and work 100% ICS.
please dont blame me please post your idea (sorry about my bad english)
i once posted the same thing....http://forum.xda-developers.com/showthread.php?t=1495237
it goes like this:we need to port drivers to the kernel which is very hard and takes a lot of time
dont worry our devs our talented enough to port it...never lose hope
{possibility}DX is not updating anymore so probabely hes is busy porting it...hehe
ps-i tried to compile cm-kernel-2.6.32...it failed
Rahat34, there's a wee bit more to it ...
IF you would set out to put together a Linux 3.x.x kernel the challenge you will face is more like this ...
1. You need to forward-port the SEMC drivers out of the 2.6.29 source and also adapt drivers to the updated ABI of Linux 3.x.x
2. You need to forward-port the various CPU governors and stuff others wrote up (like alfsamsung and nobodyAtall in their respective kernels) and also make them fit the Linux 3.x.x ABI.
3. You need to bend others things in the Kernel into shape to work with Gingerbread and Ice Cream Sandwich ROMs ... as you most likely started out with a vanilla kernel source from kernel.org
*ABI = Application Binary Interface - not to be mistaken with "API"
That task is so massive and huge that a single developer - able to do the stunt - will possibly spend MONTHS on porting stuff and testing things out on the get-go (and we're talking about a dedicated amount of hours per day here).
In other words - it's unlikely that someone will take the trouble to port stuff to Linux 3.x.x
thank you B.Jay for the info....i keep learning more tings on xda
samsung galaxy phones have a project - http://code.google.com/p/gaosp/wiki/KernelPort
can fxp have project for x8,x10mini,x10minipro....all devs form these forums(and senior members like you{you know a lot stuff})can work...ofc we have so make testers anf willing ppl(like me)
---------- Post added at 03:26 PM ---------- Previous post was at 03:21 PM ----------
i found a useful guide...its not apt to the title but its quite informative...anyone can give it a try..if you are gutsy
http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Porting-Android-to-a-new-device/
(its not waez )
Related
Hello
Can anyone point me to a guide or summary of alternative kernels please?
You can check our work on the nook color linux kernels in this thread here. http://forum.xda-developers.com/showthread.php?t=1370873&page=285
I also have a guide on using the Git and the Gerrit code review down in cyanogenMod central for the nook color linux tree at this thread link here. http://forum.cyanogenmod.com/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/
If you want to help and have experience on building linux kernels feel free to post a follow up in the first link I have posted. We are using the git and the github to commit code for our linux kernel tree. If you need help on getting up and going on using git, look through the second link I gave, I have all of the links on the github for our project and other helpful tips for you to get started. Right now the top developers are committing code to the jellybean branches. <fat tire> is our top developer and github maintainer for the nook color linux kernel tree, you can find him in the first link I provided and can help you also.
Thanks. I'm able to put a kernel together, but i haven't much experience in original development. I'll keep an eye on that thread though!
Right now we are looking for a few debuggers for the Jelly Bean Kernels. You know how to use debuggers? We need to check for kernel opps that are not being caught by the machines. Last year here there was a developer that rooted 2 kernel opps out and submitted them to Gerrit as a patch. Henk Poley , the developer for the Git extentions used his app and rooted out a few kernel opps on the cyanogenMod stable 7.1 at the time. Check out the my link on debuggers if you are not sure how. Not glamous work but it needs done, and I am getting up and ready to go back to school. Might do that if you want to help.
<Eyeballer> here is looking for someone to strip out all the unnecessary phone .apks for the nook color cyanogenMod builds, like the phone.apk and the telephony.apk along with the voicedialer.apk. I was going to get started on doing that but got sidetracked on getting a proper workflow going on the github. That second thread has links on how to submit work and patches down at cyanogenMod.
~~~~~~~~~~~~~~~
If you are up to a more difficult challenge the wi-fi module needs more work on the Jelly bean builds, they are still getting wake lock problems with it. A few months ago the developers disassembled and reassembled the wi fi module and could not find any code conflicts within the driver or the module. They can fill you in on that up in IRC at #nook color if you want to follow up on that.
Wow. Uh, I don't actually use a debugger, I'm pretty new to building kernels. I used to program C++ in Visual Studio, but so far haven't investigated the debugging process. In my own kernels I use printk, and that's about as sophisticated as it gets.
I wish I could help, but I need the device to available at the moment for my young daughter. Good luck with JB. I'll consider helping if my situation changes.
can someone update .597 kernel here is source
https://github.com/kamarush/semc-kernel-msm7x30-3.0.8
https://github.com/nexx/htc-kernel-msm7x30
also cyanogen start porting 3.0 kernel for msm7x30
http://pocketnow.com/android/cyanogen-porting-linux-30-kernel-to-msm7x30-phones
thers some sorce i just googleing and found this
ps i alo find this : https://github.com/kamarush/semc-msm-3.4
According to a Google+ post (what are we going to call those? Geeps?) Cyanogen himself is working on porting the Linux 3.0 kernel to Android-powered devices running on the msm7x30 chipset.
According to the post “All the subsystem changes from 2.6.35 to 3.0 are super tedious, especially sound.”
What does the 3.0 kernel include?
First of all, it does NOT include any “special scary new features” and “there’s absolutely no reason to aim for the traditional ‘.0′ problems that so many projects have”.
Instead the release includes the “usual two thirds driver changes, and a lot of random fixes” and “some nice VFS cleanups, various VM fixes, some nice initial ARM consolidation (yay!)”.
According to Linus himself, “in general this is supposed to be a fairly normal release cycle”.
So, with no much fanfare, the 3.0 kernel was released, and with the backing of one of the Android greats, it’s coming to smartphones soon.
Click to expand...
Click to collapse
Hi all!
I will try to get the Android Open Accessory (AOA) protocol into our defy/defy+.
Anybody else working on this topic?
Atm I just added the android.hardware.usb.accessory.xml file to /etc/permissions and the com.android.future.usb.accessory.jar to /system/framework (jar taken from the droid sdk API16, my fw is latest quarx CM10).
Right now I can install f.w. the ADK2012 app. So I may on the right way... but I guess that is not all the work... does anybody know if we need to add some kernel modules f.e.?
[Edit] btw... looks like we just need to add a new f_accessory.o to our usb gadget... f.e. see https://www.codeaurora.org/gitweb/q...in;h=5d9d8625e39f815673dedea353f39edccabb1fac
Best regards, Stephan
Like to know this to. If quarx managed to give us sub host, I might be able to use my duomilanove board...
Aren't there other projects for the ADK that doesn't use the protocols?
Please ask all questions in the Q&A section. Thread moved there.
Ok... I gave it a short try with the patch and quarx's linux-2.6.32 but it failed during the compiliation... but meanwhile I noticed that quarx is working on linux-3.0.8 (see its repo in github). There we have our accessory...
So I would say stay tuned for a while and let's if quarx may got this newer kernel working with our defy...
You can find all the steps needed to patch it here:
https://github.com/ezterry/manifest-gingerbread-DS/issues/32
They're saying everywere that you need 2.6.35+ kernel (don't know if it really is mandatory, kernel in the link is 2.6.34)
A kernel with the same chipset that has it enabled can be found here:
https://github.com/XDA-Bam/samsung_kernel_latona_GB
Apparently, you need to enable it in the kernel (config), add the libs to the kernel (driver/usb/f_accesory and include/linux/f_.accesory), add the lib in the framework (might be included from CM side already??), hope it will work (or debug why not).
---------- Post added at 01:21 AM ---------- Previous post was at 01:06 AM ----------
It seems that the files are indeed in the 3.0 kernel.
I already ordered a USB-host shield for my arduino a week ago, I'll try and compile a kernel with it ones it comes in the mail.
Edit:
Tried the changes I listed, will build it tomorrow (or so). Maybe then my shield might arrive to (hate waiting, stupid holidays.. )
Any place to upload it when it works?
Got something build, but it didn't include the /system/framework/com.android.future.usb.accessory.jar and got bootloop without (cause I added the /etc/permision/something_with_usb_accesory.something
Pushed the jar with adb from bootmenu (from another CM rom).
Don't have the usb_shield yet, so can't really test. Will try and install an usb_accessory app. Does someone want the build to try?
Ok, the app fails to launch.
Ok, my repo's:
Kernel: https://github.com/labsin/jordan-kernel/commits/2.6.32
Device: https://github.com/labsin/android_device_moto_jordan-common/commits/jb_2ndboot
But doesn't work. The library isn't build (in framework/base).
And it also doesn't build in the kernel... :/
Anyone??
Might it be possible to check the driver?
Edit: Found it.
It seems to many commits need to be merged in. Can't seem to find a kernel that's not based on the nexus line that has it.
If anyone is still interested in this, I managed to make an Arduino Mega ADK board with the DemoKit application work in accessory mode on my Defy
Quarx backported the USB gadget driver from 3.0.8 kernel into his 2.6.32 based kernel already a while ago. All that was still missing was the accessory configuration in init.usb.rc and the .jar and .xml files. Quarx has already merged my pull request, so in the next CM10.1 nightly with 2.6.32 kernel, USB accessory mode should work out of the box
Thnx. Already saw this actually
Hello
I was wondering if there are any Nexus 4 ROMs using JustArchi's optimizations (link). I did my best to compile OmniROM with these fixes, but I am not very experienced with Android development.
+1 to this post
Looks like our devices are too fast to use these "insignificant" compiler optimizations
I'll give my 5 cents these days to try compiling it..
Cheers
+1 for this thread.. I asked just the same thing in the general Q&A thread and nobody answered.. I'd like to see CM, ParanoidAndroid...etc.. built with ArchiDroids optimizations..
Like to see that too!
I've been searching for a rom with f2fs support + JustArchi's optimizations. Can be possible?
I created a topic earlier here
opssemnik said:
i can tell from personal experiences, its mostly placebo, tried archi´s rom on my gs3, and aside from the fact that the google camera dosent crash after first shot(witch occors on alot of roms ,even official cm, again on my s3), the rom is same speed, if not less than official cm. (on my s3 i9300)
Click to expand...
Click to collapse
Nevertheless, there are other statements that say it is faster, we can only know for sure if we benchmark this and find someone willing to compile a rom. Perhaps @legolas93 is willing to be so kind?
joefso said:
I created a topic earlier here
Nevertheless, there are other statements that say it is faster, we can only know for sure if we benchmark this and find someone willing to compile a rom. Perhaps @legolas93 is willing to be so kind?
Click to expand...
Click to collapse
yeah i saw those,luck for them, thats why best rom threads are not allowed on xda, people get different results on their devices ,i plan to compile aosp with those just to test on the n4, but i doubt i will :/
No one is going to try this anytime soon.
The code is no where near perfect and it sets up an environment where there is a lot of room for errors which will result in VERY bugy, glitchy, crashing Roms.
The code is really sloppy and so far only JustArchi is the only one that has successfully used this in a ROM with out error.
There is still a lot of going back and forth in whether this really works since android isn't 90% thumb
All this is good for is benchmark scores. Just like F2Fs its all placebo in real world performance.
With a quadcore 2 gig phone... You're not missing much.
Legecy devices will benefit in the least from this.
Sent from my SM-T217S using Tapatalk
First build is ready!
It is mako-userdebug.
I used Linaro toolchain(JustArchi's link) and JustArchi "JustArchi's ArchiDroid Optimizations V3" - https://github.com/JustArchi/android_build/commit/d8cc50d2472e497b431b5652516c9248ad7f3947
It is without Gapps (so PA Gapps must be used).
Build Env :
Debian GNU/Linux testing (with make downgraded from 4.xx because AOSP lunch require this).
AOSPA soruces 4.4.2_r1 used for the build.
No ART patches! ART will fail if you try using it.
Will test this today on my phone, and if successfully boot, I'll post a link for the ROM.
p.s : From back these days, where people find that AMD64 arch is here, Linux builds started to optimize the speed of your GNU/Linux for your specific CPU (Gentoo for example, or Debian GNU/Linux moved from i386 to i686 and after that to AMD64). Well, the tests and builds performance charfs finished with this : improvement of the speed was was something like 0.6/0.9% ... So in the real world reality do not expect much from this!
Regards ...
Edit:1
Boot failed
Next time, I'll enable the proprietary drivers in the build.
Currently new build is running with enabled prop drives settings like:
Source:http://nosemaj.org/howto-build-android-nexus-4
To use these proprietary files, comment out this line in device/lge/mako/full_mako.mk:
#PRODUCT_RESTRICT_VENDOR_FILES := true
Cheers!
First Of all.THIS IS NOT A QUESTION OR A CALL FOR ACTUAL HELP.I have seen a few replacements for AOSP and Postmarket OS is one of them.Being in early stages it is very useful if being ported or compiled for Devices with stylus or phablet factor.I am Currently working on the OS after I read the Documentation.I as of Now have managed to Run the Test UI on it.All functions(except GPS ril Bluetooth thermal and maybe MTP)Do work Properly.The Main UI is still un-bootable.I would post it as soon as Possible.The Main Feature of this is THAT IT USES THE MAINLINE LINUX KERNEL.A little crazy to say it but it says it does that and it may take a week to do it.I have compiled it 37 times and it takes a very little time on my machine But the number of fatal errors are in hundreds or Thousands which are all Related to compatibility.
A huge thanks to xda-Website and a shoutout to PMOS(as I would call it) for doing such a great thing.
Again I can't do it myself The only thing I can't seem to make it work is to boot the rootfs for unknown reasons.As Soon as I achieve something I will Post Links.
kernel that works https://github.com/LineageOS/android_kernel_samsung_msm8974
kernel that's official
https://github.com/CyanogenMod/android_kernel_samsung_hlte
zImage that boots(with halium rootfs that works with any rootfs)
https://drive.google.com/file/d/17ksmUn5FTqOuL9mKsOCqrhe3W3mqGwUe/view?usp=drivesdk
the latest linaro 7.3.x toolchain arm for note 3
https://drive.google.com/file/d/1Ld5Nb7rekgbFLAcyW16721_1GITP_2wv/view?usp=drivesdk
zImage that get's to testing
https://drive.google.com/file/d/12sQbEzl4nfK7E3IXwbpxIYy_mKcZ6Q4W/view?usp=drivesdk
common kernel zImage built on nexus 5 model doesn't boot.
https://drive.google.com/file/d/1GyJKCKn9DxynOeTx8Ea4wHSxHm7S1nd1/view?usp=drivesdk
and again help is appreciated.
Sent from my Pixel 3 XL using Tapatalk