So I'm using this ROM
[ROM][JB]BlackJelly V 0.9.2 - 11/14/12 Based off TMO Official JB LJA
I was wondering, what does a kernel exactly do ? I've read about it but it kinda didn't make sense to me.. and which kernel should i use ?
analogy taken from the kernel master, faux123:
What is a Kernel? The Kernel is the Foundation in which everything else builds upon in any software system.
[Car Analogy]: Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hope that helps...maybe try ktoonsez kernel in the dev section
You could also say that android is relative to the kernel in the sense that it is simply the user interface of Linux of our devices. The kernel basically tells the hardware how to react to how you are manipulating said UI... that is a very... very basic explanation obviously. Your user interface, which is what you see and touch on your screen, is basically a bunch of packages of executable files (apps) that coexist to make use of hardware through library (lib) files, binaries, etc... the kernel is the backbone of Linux machines, the root, the power management, the brain of the OS. make sense?
Related
I know this is a long shot but are there any car modding developers out there who could make a windows mobile version of the greddy emanage support tool.
Would be amazing if I could just plug my HD2 in to my emanage blue piggy back ecu to monitor/change settings.
p.s. currently about 2/3 the way through of fitting an eaton M45 supercharger to my fto
the specs needed for the original software are quite low -
266mhz cpu (for real time monitoring)
128mb ram
50mb hard drive space
svga monitor (800X600)
my beast
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I doubt this would every happen unless Greddy wants to release the source code which I don't see ever happening.
Rhodium500 said:
I doubt this would every happen unless Greddy wants to release the source code which I don't see ever happening.
Click to expand...
Click to collapse
there is one guy who has allready released his own version emanage tools and it was an open source project.
I have just grabbed a copy and it includes .pdb files if these are the source code files (sorry for the newbie question)
http://www.megaupload.com/?d=J9F0CTVO
This version isnt as fully featured as the original greddy one but still measures -
rpm
air fuel ratios
boost
throttle position
Hi I've been acquainting myself with all of the terms and meanings around here but their is just too much to take in all at once.
I've managed to get a general understanding of alot of what these terms etc are.
What I'd like to know is:
What the heck is a Kernel, what does it do and what difference does it make in terms of your phone etc?
I know what a ROM is (I think) and to my understanding a ROM is basically an OS?
I've heard a kernel is how the ROM talks to the Hardware, but what difference does a custom Kernel make etc.
Thanks !
So, in simple terms, think of the kernel as the connection between the two places - hardware and software, that allow communication between each other. Custom kernels just contain numerous tweaks and improvements such as better performance, battery life etc.
A ROM is not an OS. A ROM is simply a version of the OS - with it's own tweaks, additions and functions added to it.
Source of the following image : [Kernel]Amaze ICS(v017)OC~1.73/JRCU/UV/CIFS+UTF-8/Power Saving[Aug-18]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some other good sources : ROM-VS-Kernel
A glossary of Android terms
Thanks you two !
Great information !
Hey guys,
So I just got this device last night. I set up a virtual linux workstation and started downloading my source from samsungs site. - My only problem is that for the 10.1 wifi model, 520, theres like one package.. Then there's the 525's package, the one ending with "UANAF", apparently my device is of the model "520", but it has the UANAF. I wanna start reading up on building a kernel and a CM port from scratch.. (I never did before but I'll see if it's doable in some way..) Would I be able to at all build a CM build from this file? And also, do I use the 525 package or the 520? I'm a bit confused as to why my build is called UANAF when on the site, that's the one for 525.. I just really dont wanna study and then end up compiling from a wrong package and then **** up my device before I really began..
Hay. - I'm attaching an image so you can see what I mean by 520 and UANAF.. Hmf.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cheers if you have any info on what package to use or can hand me some nice starter stuff. As of now, I found out how to build the rom itself, but the kernel building, I'm a bit confused about still. I dunno what files to grab and how to compile. But I have dreams. Don't take them from me. <3
Though I've already sold my own N7 2013, I'd still put this thread here because this is one of the most popular tabs around here
So, as the title says, I'm thinking if it's possible to force the classic dual-pane layout in Android 5.x... Like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's already a shame Google removed Tablet UI in 4.4, yet in 5.x dual-pane is gone even for 10-inch tablets.
Back in Android 4.x, this can be done by decompiling framework-res (I used APKChanger back then, which has apktool 1.5.3 integrated), editing a bool value, saving and recompiling. I actually attempted this for 5.x too, but since apktool 1.5.3 doesn't support Android 5.x, I'm forced to use a bare apktool 2.0.x jar, which I am not so familiar with. I did all the steps just like what I'd do under 4.4, and all that welcomes me is a boot loop...
So, 1) is this even possible at all?
If yes, then 2) is there an easier way of doing this (e.g. an Xposed module)?
And 3) what could I have done wrong with my steps of using apktool - any alternatives?
Thanks in advance!
I have Linux running on a rooted Galaxy Z Fold 4 although it is incredibly slow due to the lack of KVM support in the kernel.
There are multiple ways to run Linux on Android, although many of them are constrained and in order to get the most out of Linux running on the Z Fold 4, I'm looking to run a fully featured build in a VM on my device.
As an app developer myself, I'm looking to contribute to the Limbo VM project to update the application to work more effectively with foldable devices like the Z Fold 4 and hopefully make it easier to run the new Gnome-Mobile-Shell project in an emulator on Android devices for testing apps during development for the platform and to enable Android users to run Linux mobile apps on Android.
Although in order to get started with this project, it would help to have KVM support in the device kernel, though I'm not experienced in modding Android rom kernels and any help from a more experienced rom modder would be welcomed!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}