I've recently bought a surface go for school (64gb emmc, 4gb ram model) and I love the pen and the build quality however i found windows to be way to slow on a device like this and decided to try android. android-x86_64-8.1-r2 installed fine and it runs great on this hardware except for a few issues such as camera, auto rotate and the like. I've run into a pre-made kernel that fixes these issues and will link it below. I was wondering if someone could help me with implementing this kernel into android x86 to get the full set of features working. Thanks in advance!
Kernel:
(On github) /jakeday/linux-surface/releases
Could you tell me how you implemented that pre-made kernel into Android x86? I'm trying to do the same thing with Bliss OS 11.10 (Kernel 4.19), but I really don't know how. I could have missed something on the GitHub page, but I don't know how to implement a kernel into Android. To be honest, I never implemented a Linux kernel into an OS.
I hope you read this even though it's already been a few months.
Thank you
Related
As I understand it, there is a linux kernel that android sits on. I thought the ROM was like a virtual machine running inside of android and then we loaded apps onto that. I read something that indicated that each custom ROM comes with a kernel. Then we can replace that kernel with another one if we wish. I understand that the kernel must be compatible (although I don't know how to tell) but that seems confusing. It would seem that if the ROM is running in android then as long as the kernel can run android, any kernel should suffice. Clearly that is not the case so what exactly is a ROM and why does it interact directly with the kernel?
A ROM in this case is a system image (full or partial) containing the Android operating system, drivers, applications, and/or kernel.
Like with regular PC OS not all kernels are compatible with the larger OS, primarily across major versions.
check this link
http://www.xda-developers.com/android/understanding-android-fr
Rom futures
does anyone know where roms are going? read somewhere 2.3 and 3.0 are forks. that makes sense if 2.3 continues focus on phones, small devices etc and 3.0 continues down the larger tablet track. I am currently running 2.3.3 on gtab and it runs great. it seems to be very tablet friendly. does 2.3 provide much of the functionality of 3.0 for the small screen. can we expect 3.0 to bring additional utility to tabs like the gtab? just curious where we might be headed. keep up the great work. i stay excited about the next build!
Rumbleweed said:
check this link
http://www.xda-developers.com/android/understanding-android-fr
Click to expand...
Click to collapse
This is a GREAT link! Thanks.
Hi
My goal is to build Ubuntu Touch for the Ideos X5 U8800. So far, I have only had trouble finding and setting up the source for a cm-10.1 build. Finally, I gave up and built cm-11 using Blefish's device source tree. Everything works just fine.
So the question is: Can Ubuntu Touch be built using cm-11, or is cm-10.1 the only option at the moment?
Best regards,
aribk
They switched to Android 4.4 some time ago. Don't know why they haven't updated the wiki yet.
Some sources:
http://news.softpedia.com/news/Cano...-Touch-Based-on-Ubuntu-14-04-LTS-438400.shtml
https://www.mail-archive.com/[email protected]/msg06401.html
https://wiki.ubuntu.com/Touch/Porting (further down)
Ubuntu is based on CM? Thougt the only thing in common is parts of the kernel??
So, it will more or less be able to port ubuntu to other devices just by changing kernel and baseband?
reellamer said:
Ubuntu is based on CM? Thougt the only thing in common is parts of the kernel??
So, it will more or less be able to port ubuntu to other devices just by changing kernel and baseband?
Click to expand...
Click to collapse
Libhybris is being utilized by Ubuntu for Devices, Sailfish, Open webOS and others to form a base layer compatibility with Android hardware drivers (above and beyond just the baseband [radio]). This is what gets the ports to work with Android hardware... http://en.wikipedia.org/wiki/Hybris_(software)
The mainline efforts have focused on Nexus hardware and seem to have formed a consensus that CyanogenMod 10.x is the best jumping off point.
Hi,
I was looking for some Android x86 OS to install on my laptop, so I came across Remix OS. I very much like it, after going through all of features. However, I found Phoenix OS too. I am just super confused now. Which OS should I install; what makes Remix OS better than Phoenix?
Thank you!
Anyone?
u can install them both, and ur problem solved
Thanks! This initiative is not going to resolve my curiosity.
What I mean is u can try install them both and see which one is most working for ur device or PC cause they have pros and cons between one and another
Remix OS and Phoenix OS are just two Android distributions - both based on Android x86. So in terms of hardware support, they might be similar. Phoenix OS seems more refined and ready for market, Remix OS is still just beta and has a lot of bugs. On the other hand Remix OS has a much bigger community, help pages, forums and users - with Phoenix OS you are on your own.
All that said, there is a third option. You could simply plug your Android tablet to a keyboard/mouse/screen and forget about all the Android x86 fever. Your hardware will be fully supported, have access to an official Google Android build with all the support included and in the long term there will be less hassle. And now with Android N on the way which supports Remix OS like windows, you will never notice any difference. I myself am going this route. I will wait for Android N tablets, buy a sufficiently performing one and plug it to some peripherals - instant Android desktop, fully supported by Google. No tricks, no hacks, no unsupported hardware.
Lol... You're having a bad dream...
You can also install a non windowed version of android x-86, after numerous attempts and a lot of failed boots I ended up using AndEx - Exton Android - http://andex.exton.net/?p=451
Does that mean you paid for it as it isnt free?
I have a lenovo Z575 which has an AMD APU with dual graphics. I installed remix os and got the error, which I later fixed following a guide on here from SEPTEMBER 2016...
The fix basically disables the GPU and enforces software graphics.... This makes the system almost unusable and ugly...
I'm wondering why is there still no fix for this? Ubuntu supports dual gpus, and someone who knows what theyre doing posted on google support forums that he merged some files and he got remix os running with dual gpu's, I'm really confused why no one has fixed this...
I'm hoping someone can help me get this running on my PC, if not possible please recommend me some other lightweight operating systems that run fairly well on old hardware...
Would it be better for me to run the lollipop ver. of Remix OS? That seemed to have the dual gpu compatibility...
Hello everybody. I love this community and I have been lurking for a long time.
I have noticed on a foreign language forum that some people were offering a custom rom for my android 9 TV box.
The chinese box is based on a s905x3 CPU and has a mediatek wifi chip for which it is hard (if not impossible to find the wifi drivers).
The site claims that the image was made by modifying the stock rom that came with the box. Is this possible or do all custom roms need to be build from the source?
The custom rom I want to make is going to replace the launcher with kodi.
I am prepared to build the whole rom from source but I do have a couple of questions.
Since the mediatek wifi drivers cannot be found how would I go about including the binary for the wifi?
I have noticed that the box that I have uses a .ko (kernel object) module to drive the wifi chip.
Can I include these kernel objects in build? It is a shame that the kernel is built as a 32bit system. Would that mean that I can only compile a 32bit kernel if I were to reuse those kernel modules and binaries?
Another idea is to perhaps use the kernel from coreelec in my build since it seems to include a lot of drivers.
Is it possible to use a kernel from something like coreelec but use the source from AOSP for the rest of my build?
Is there anything else that I should be aware of?
Thank you all!!!!
Can anyone give me any hints to any of the questions?
Essentially I want to swap out the stock launcher for Kodi. What is the easiest way to do so?