I try to install neverware home edition on yoga book(windows) after disable secure booting at bios.
But after cloudyready logo came out, it didn't proceed anymore.
any idea to install chromium os on yoga book(windows)?
Cloudready shares the identical Chromium OS Kernel.
There is no compiled Kernel with the specific drivers the YogaBook needs (mainly screen, wacom, halo etc) and despite others insist, Lenovo did not release their Nougat Kernel nor Drivers as Open Source... Furthermore Cloudready isn't Open Source, I don't see it ever happen that someone replaces their Kernel for a model specific Custom Rom.
and is there a way for the android version ?
Related
I'm working around with APC8750 and hope can make some fun with Firefox OS
but I find out that it doesn't have the Android device tree (currently it run on Android 2.3) Any instructions to create
device tree for it ? I would like to build Firefox os for this device :victory:
I have Phicomm C230w which is exactly ZTE Open C as far as the specs are concerned, same processor, same screen size and so on.
Just wanted to know if its possible to flash Firefox OS on the device.
Any reply will be highly appreciated
have phicomm released any kernel source or firmware updates for it so we could look at the kernel config?
hecatae said:
have phicomm released any kernel source or firmware updates for it so we could look at the kernel config?
Click to expand...
Click to collapse
Not as far as I know, it does have Android 4.2 installed though
a jellybean kernel and hal may be enough for us to get gecko booting on it.
is the bootloader unlocked, can you issue fastboot commands?
Hello,
I build CWM recovery and Philz touch recovery for this device :
http://forum.xda-developers.com/android/general/rom-cwm11-recovery-port-phicomm-c230w-t2871370
And the kernel is available at :
http://gpl.phicomm.com/
I've noticed that the same issues in all GSIs:
- Broken hotspot
- Notification LED stuck on
- Auto-flash broken
- Broken WiFi (won't matter with custom Kernel with QCACL3)
It's obvious that what we need a custom build vendor. The Mi A1 has the same thing built from 8.1 vendor, which supports all Pie GSIs. Now, I'll be honest, I have little to no knowledge on Android ROM development. I excel in native development in C/C++ in the Android Kernel and the Android userspace. I'll be willing to work with someone to produce a new vendor for the device with patches to allow GSIs to function properly. Contact me on telegram @tytydraco.
Edit: this is the Mi A1 patched vendor: https://github.com/tissot-dev/proprietary_vendor_xiaomi
I see installation instructions for a ROM (which is the Android OS, right?) and I see references to a kernel as well. What is the difference? Am I supposed to install both at the same time, or does the ROM carry the kernel, or how does it work?
Android is similar to mainstream linux operating systems in that the ROM is like the OS portion of a linux distro.
the Kernel is the portion that interfaces between the OS and the hardware.
Pretty much all Roms (there may be exceptions but I cant think of any) come prepackaged with a kernel as well.
so installing the ROM will install the kernel automatically and has the benefit of installing the kernel the developer intended.
There are separate Kernels available that have specific features you may prefer. (overclocking for CPU/GPU, specific modules loaded for emulation if running a linux distro within android etc.)
to install them you would install the rom (And its default kernel) then flash the kernel of your preference over it.
If you are just starting out I would just install the Rom and its default kernel unless you have a very specific use case.
hopefully that helps
There are often more pieces as well due to proprietary code:
ROM - the OS itself often either based on AOSP, the manufacturer software or Lineage (or a mix)
Kernel - refers to the open source linux kernel that controls hardware that it supports.
Firmware - includes manufacturer proprietary code for hardware that is not open source.
Modem - includes proprietary code for modem hardware.
it breaks down further but generally you will start with a stick manufacturer installation including all parts.
then you can flash a custom rom and kernel (Usally as a complete package)
Modem and firmware updates would still come from the manufacturer. (Most roms will tell you if a specific firmware or modem is needed, the modem usually doesnt matter as much anymore but in the early years it was important)
Thanks for the information!
Hello,
For those interested in the original kernel source code for the SM-T813 :
As I am learning how to make ports for Android, I am trying to train on the original sources of the Linux kernel for the SM-T813.
After several weeks of research, I couldn't find the origin of the different kernel repositories.
Also on https://opensource.samsung.com, it was impossible to find the sources. So I contact them at the end of January to have an access to this sources...
... And they are now available !
You can download them on https://opensource.samsung.com (search SM-T813 at mobile phone on release center) or on my repository at https://github.com/Akipe/android_kernel_samsung_gts210vewifi_original_samsung
It is based on the T813XXS2BTK3 firmware with Android 7 Nougat.
I will see to ask for sources of similar tablets.
Will this help with porting new Adnoid version to these tablets?
Pawel_ said:
Will this help with porting new Adnoid version to these tablets?
Click to expand...
Click to collapse
I don't think so,
Kernel sources for this tablet already exist, and are ported to newer versions.
It is more useful for those who want start from scratch, and want to inspect the unmodified source code.
But my goal would be to successfully create from scratch for the SM-T813 LineageOS 14.1 (Android 7); and then try to move to the latest versions.
Since I am a beginner, I still have a lot to learn, and I don't have much time, so we will see