Database Info

Android parts in HP Pre 3 kernel

Hello everybody,
I was just looking around the Pre 3 kernel sources to find something useful about turning on the flash LED to make a torch when I found some lines related to Android.
Maybe HP just used Android sources to make their kernel or maybe this kernel is ready to start Android ?
What do you think about that ?
Code:
# Android
#
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_LOGGER=y
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y
# CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION is not set
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
CONFIG_ANDROID_TIMED_OUTPUT=y
CONFIG_ANDROID_TIMED_GPIO=y
CONFIG_ANDROID_LOW_MEMORY_KILLER=y

legsim said:
Hello everybody,
I was just looking around the Pre 3 kernel sources to find something useful about turning on the flash LED to make a torch when I found some lines related to Android.
Maybe HP just used Android sources to make their kernel or maybe this kernel is ready to start Android ?
What do you think about that ?
Code:
# Android
#
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_LOGGER=y
CONFIG_ANDROID_RAM_CONSOLE=y
CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y
# CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION is not set
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
CONFIG_ANDROID_TIMED_OUTPUT=y
CONFIG_ANDROID_TIMED_GPIO=y
CONFIG_ANDROID_LOW_MEMORY_KILLER=y
Click to expand...
Click to collapse
Qualcomm's reference kernel for that processor is an Android kernel. So all devices based on that processor start with an Android kernel and work from there.
-- Rod

rwhitby said:
Qualcomm's reference kernel for that processor is an Android kernel. So all devices based on that processor start with an Android kernel and work from there.
-- Rod
Click to expand...
Click to collapse
so,is it possible to run android on hp pre 3?

Yes, both the Pre3 and touchpad were developed with android due to mismatch in speed between hardware teams and webOS teams. I.e. webOS teams were way too slow.

pablo_max said:
Yes, both the Pre3 and touchpad were developed with android due to mismatch in speed between hardware teams and webOS teams. I.e. webOS teams were way too slow.
Click to expand...
Click to collapse
On what authority do you make this statement? Do you work in either of those teams? You'll need some facts to back up a bold, unprovable statement like that.
-- Rod

pablo_max said:
Yes, both the Pre3 and touchpad were developed with android due to mismatch in speed between hardware teams and webOS teams. I.e. webOS teams were way too slow.
Click to expand...
Click to collapse
Seriously ? It sounds a little weird, I thought that the Pre 3 was developed with WebOS 2.1.
Anyway, it still would be great to be able to dual-boot Android or at least make Android apps working, maybe within a chroot like there is with the Touchpad.
By the way, would the Touchpad Android IPK work on Pre 3 ? Is there any reason I shouldn't try ?

legsim said:
Seriously ? It sounds a little weird, I thought that the Pre 3 was developed with WebOS 2.1.
Click to expand...
Click to collapse
Without further proof, you should treat that post as trolling. There is no Android available from HP for the Pre 3.
Anyway, it still would be great to be able to dual-boot Android or at least make Android apps working, maybe within a chroot like there is with the Touchpad.
By the way, would the Touchpad Android IPK work on Pre 3 ? Is there any reason I shouldn't try ?
Click to expand...
Click to collapse
You should read the threads on PreCentral where the damage that package does to your kernel installation is outlined. Folks are having to doctor their devices to recover full capability again.
-- Rod

I tried to install the IPK but it didn't want to install the modified kernel.
So I did it manually and now the Pre 3 won't boot anymore.
It's time for doctoring in recovery mode

legsim said:
I tried to install the IPK but it didn't want to install the modified kernel.
So I did it manually and now the Pre 3 won't boot anymore.
It's time for doctoring in recovery mode
Click to expand...
Click to collapse
that's the attitude.
gratz

MTK6575 Based Devices Cyanogenmod

Hi Guys I Want Someone Who Can Help Me To Build CM For MTK6575 .
I Have LG Optimus L4 II E440 Its MTK6575 Based Device And I Have Source Code .
I Think It Will Work On Other Devices .

Even if you have the source code for that device, you can't just build generically for anything with that processor as even if just one part of the device is changes that part would probably cease to function. Also when it comes to building something like that I'll see what I can do once I have a fully functional computer but the source is like 40 GB so it would be a big investment already just to download it. Which version of cm?

dreamwave said:
Even if you have the source code for that device, you can't just build generically for anything with that processor as even if just one part of the device is changes that part would probably cease to function. Also when it comes to building something like that I'll see what I can do once I have a fully functional computer but the source is like 40 GB so it would be a big investment already just to download it. Which version of cm?
Click to expand...
Click to collapse
I Think CM 10.1/10.2 Or CM 11 !
I Have Installed Lubuntu 12.04 And I Will Start Programing From There But I Dont Know From Where I Can Download The CM Build !

vikole said:
I Think CM 10.1/10.2 Or CM 11 !
I Have Installed Lubuntu 12.04 And I Will Start Programing From There But I Dont Know From Where I Can Download The CM Build !
Click to expand...
Click to collapse
I made some 1.5 based rom at one point for my g1 but I remember like...none of it. Once you read up on building android you should be fine. I'll just warn you you will be working with BIG data, probably around 40gb to download.

dreamwave said:
I made some 1.5 based rom at one point for my g1 but I remember like...none of it. Once you read up on building android you should be fine. I'll just warn you you will be working with BIG data, probably around 40gb to download.
Click to expand...
Click to collapse
Can You Help Me ??:highfive::highfive::highfive:

vikole said:
Can You Help Me ??:highfive::highfive::highfive:
Click to expand...
Click to collapse
I'll have to see. I have hard drive issues so I couldn't do it myself but I think I can guide you to a few good guides. There's a really good xdauniversity one I saw at one point I'll try to find.

porting cm to a new device - whats needed and difficulties

Hey,
i'm just curious about what the title describes. First of all.
What do i really need:
-kernel sources
-binary blobs (extractable)
-recovery / boot.img (extractable)
Let us just talk about the fairphone 2. Additional to the things mentioned we get the full source code of the OS (which i do not need?).
Where do the difficulties lie? For my understanding we just take the kernel sources, the official cyanogenmod (e.g.) source code, the binary blobs and the recovery / boot.img.
How difficult would it be to port Cyanogenmod to the fairphone 2.
Why is it difficult to port a device with existing (again cyanogenmod just as an example) cyanogenmod to a newer Cyanogenmod (Android) version?
I ask this to estimate/evaluate/judge (don't know the right term) the effort needed to do this. I think i'd be able to do that if i put enough work into it (i "speak" c and java), but i just need some answers.
Especially for example why it is more difficult to port Android 6 instead of Android 5 (which is the currently running Android version)
Thanks!
bigCrash

Has nobody an answer? Just one?
Im specifically interested in why it is more difficult to port e.g. cyanogenmod if there is only an older version of stock android and how important the kernel is? Why do we need kernel sources? Can't one just self-compile a kernel.
Where are the limits if i have a device running 4.2. Why can it possibly run 5.1 but not 6? Is the kernel limiting? Or only the effort to realize such a thing.
Thanks!
bigCrash

[KERNEL] Major Linux Updates

Hello, I decided to come up with a project that aims to port higher Linux versions. When I say higher Linux versions, I mean those that are Linux 3.5 and up. The goal is to port Linux major updates as high as I can, but the main priorities are one that are LTS like Linux 3.10, 3.14 or even 3.18.
Only Android 7 will work on non-LTS versions. Oreo/pie and Android 10 support will be added only on LTS versions to lessen the conflicts when merging non-LTS versions.
What works:
Boots
Battery
Charger
Touchscreen
Display
USB
Sound
Buttons
Deep sleep
Camera
Video playback
Fingerprint
The rest of the sensors
WiFi
Bluetooth (works on Linux 3.7 and up)
Internet connection
Anything else I can't mention
What doesn't work:
You tell me
Drivers that can't be updated (yet) due to them being heavily modified by CAF and Samsung:
USB
Sound
MMC
Newer versions are more stable than the other due to the fact that I fix more bugs with every update.
The highest version as of now is Linux 3.8. I can only merge major updates during weekends due to my work.
Sources:
Linux 3.5
Linux 3.6
Linux 3.7
Linux 3.8
Linux 3.9
Feel free to open up issues and submit pull requests
It is highly recommended to delete mpdecision from /system/bin/ before flashing

Reserved

i don't understand what is this, is there some wiki i can read?

saikyom said:
i don't understand what is this, is there some wiki i can read?
Click to expand...
Click to collapse
These are kernel updates. Our device comes with Linux 3.4, but I've managed to update that up to 3.8

darrendude1 said:
These are kernel updates. Our device comes with Linux 3.4, but I've managed to update that up to 3.8
what are the benefits of updated kernel..cheers
Sent from my Unknown unknown using XDA Labs
Click to expand...
Click to collapse
Read these:
https://kernelnewbies.org/Linux_3.5
https://kernelnewbies.org/Linux_3.6
https://kernelnewbies.org/Linux_3.7
https://kernelnewbies.org/Linux_3.8

@pascua28
What a Huge Task! As Well as a Pain on the Ares!
Now, I do Have a few Q's for you.
1 IS this "Kernel Patch" Just for your beloved Galaxy S5's ?
2 Will this be for the "Basic" Kernel in an OS (e.g. LineageOS) ?
3 Wouldn't this hurt some of the "Custom Kernels" that we currently have and use?
And of course I must ask, how far do you intend to take this (e.g up and coming 5.7 ) ?
That Said, I am in! I have downloaded all the Kernels . Mostly to compare your changes. Have also saved your GitHub page.
Am wondering though, With some of these "Custom" Kernels..... Wouldn't we see much faster , smoother , and hopefully more Darn Battery with some of the Tweaks that we have with them? Or at least with some kernel manager?
Or, would these break those Kernels (now thinking about it)?
Certainly will be watching this!
Again , this is a huge task to undertake! Sure would love to see 4.1 and above for our phones. Maybe with Your updated Kernel, we could really see some major changes with our phones.... Plus, hopefully easier to Port into the likes of Android 10! ... or Of course jumping a bit here, and a bit positive, but Android 11 !
Good luck sir

godofsalt said:
@pascua28
What a Huge Task! As Well as a Pain on the Ares!
Now, I do Have a few Q's for you.
1 IS this "Kernel Patch" Just for your beloved Galaxy S5's ?
2 Will this be for the "Basic" Kernel in an OS (e.g. LineageOS) ?
3 Wouldn't this hurt some of the "Custom Kernels" that we currently have and use?
And of course I must ask, how far do you intend to take this (e.g up and coming 5.7 ) ?
That Said, I am in! I have downloaded all the Kernels . Mostly to compare your changes. Have also saved your GitHub page.
Am wondering though, With some of these "Custom" Kernels..... Wouldn't we see much faster , smoother , and hopefully more Darn Battery with some of the Tweaks that we have with them? Or at least with some kernel manager?
Or, would these break those Kernels (now thinking about it)?
Certainly will be watching this!
Again , this is a huge task to undertake! Sure would love to see 4.1 and above for our phones. Maybe with Your updated Kernel, we could really see some major changes with our phones.... Plus, hopefully easier to Port into the likes of Android 10! ... or Of course jumping a bit here, and a bit positive, but Android 11 !
Good luck sir
Click to expand...
Click to collapse
1. This is a full Linux upgrade. Nobody has ever done that to our beloved S5 cause it's a truckload of work
2. Uhm, I don't know. LineageOS is very strict on what kernel base to use, but I may propose to use this as a base when I reach 3.10
3. This project might be a good base for custom kernels since it is more updated and I will use this base too for my future custom kernels
4. As far as I can and as long as it works. Of course, I don't wanna die yet by not going too far.
Certainly, it won't break any kernel managers. You can even clone the latest source and add some custom features. It's up to you, but right now, in the process of upgrading, I won't be adding any custom features
Regards

pascua28 said:
1. This is a full Linux upgrade. Nobody has ever done that to our beloved S5 cause it's a truckload of work
2. Uhm, I don't know. LineageOS is very strict on what kernel base to use, but I may propose to use this as a base when I reach 3.10
3. This project might be a good base for custom kernels since it is more updated and I will use this base too for my future custom kernels
4. As far as I can and as long as it works. Of course, I don't wanna die yet by not going too far.
Certainly, it won't break any kernel managers. You can even clone the latest source and add some custom features. It's up to you, but right now, in the process of upgrading, I won't be adding any custom features
Regards
Click to expand...
Click to collapse
Well, Thank You. for the reply, as well as, all the information.
YES your project is a HUGE amount of work. Good guess, IS , you seem to want to take on this challenge! Good for you...
Yes, I do intend to really follow your project. Really looking forward to the great results that I hope we (you) can achieve !
Awesome...
Thanks

Hi guys! Linux 3.9 is up!

this is amazing work!
thank you very much for it.. I bet it's ugly as hell, but you learn a lot..
I'm patiently waiting for 3.10.0 since that's required by docker (running debian using Linux Deploy)

shmizan said:
this is amazing work!
thank you very much for it.. I bet it's ugly as hell, but you learn a lot..
I'm patiently waiting for 3.10.0 since that's required by docker (running debian using Linux Deploy)
Click to expand...
Click to collapse
Yeah, very tedious and requires a lot of skill

This is huge. Thank you for doing this, I will definitely be following this

pascua28 said:
Yeah, very tedious and requires a lot of skill
Click to expand...
Click to collapse
Yes, as well as time, the correct machine and layout....
Plus I believe it requires most patience than what I have!
BTW... This is great work, have not seen any issues on my S5..... (yet, but don't think that will happen though)
Thank you!
Sent from my Galaxy S5 using XDA Labs

Is this working on 5+ (katcc6)?

robla1000 said:
Is this working on 5+ (katcc6)?
Click to expand...
Click to collapse
Nope, S5 only. And at this point klte only until @pascua28 is finished bringing the kernel up to 3.10

Only working properly is klte, for now. Other variants might work but with bugs. Will fix for other variants when we get to 3.10

3.5 to 3.9 didn't work for me,I have klte

didn't work?
I ran 3.8 for weeks without any issues.. what exactly does not work?

many reboot ,i couldn't use

vlad3647 said:
many reboot ,i couldn't use
Click to expand...
Click to collapse
It's not for higher Android version.. If you have Android 9 or 10 then wait for version 3.10

[ROM] [UNOFFICIAL] LineageOS 14 for Meizu M5C [MT6737m]

LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- Make a backup of your important files
2 - Unlock bootloader with this guide
3 - Flash the TWRP, link here
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package ARM64 > 7.1 > Micro and below: visit OpenGAPPS
If during the gapps flash it gives you an error then in the TWRP terminal or on the adb shell you have to execute this command: "mkdir /tmp/bin"
Download:
Releases · XRedCubeX/android_device_meizu_m5c
Contribute to XRedCubeX/android_device_meizu_m5c development by creating an account on GitHub.
github.com
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
NOT Working:
Camera
Hotspot
Offline Charging
Special Thanks
LineageOS
Moyster for device trees
Device Tree:https://github.com/XRedCubeX/android_device_meizu_m5c
Vendor Tree: https://github.com/XRedCubeX/android_vendor_meizu_m5c

Assim que possível, irei testar!

Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?

thiagosousa777 said:
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
Click to expand...
Click to collapse
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better

XRed_CubeX said:
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
Click to expand...
Click to collapse
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM

thiagosousa777 said:
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
Click to expand...
Click to collapse
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest

XRed_CubeX said:
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
Click to expand...
Click to collapse
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...

thiagosousa777 said:
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
Click to expand...
Click to collapse
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources

XRed_CubeX said:
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
Click to expand...
Click to collapse
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them, don't you?
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.

thiagosousa777 said:
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them.
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
Click to expand...
Click to collapse
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working

XRed_CubeX said:
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
Click to expand...
Click to collapse
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?

thiagosousa777 said:
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
Click to expand...
Click to collapse
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone

XRed_CubeX said:
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
Click to expand...
Click to collapse
Thanks for the clarification! It is a shame that Meizu does this (I wonder if they are not violating the terms of the Linux GPL license by distributing the kernel without publishing the modifications made to the source code).
Anyway, if a solution to this kernel problem related to the touch screen comes up, please let me know. In the meantime I'll keep reading Halium's documentation until a solution comes along, or until I get a compatible phone.

Great work!

Hello. I've been testing this ROM on my M5c and love it. The ROM is very good, fluid, lightweight... the only problem is that the camera doesn't work, as well as the cellular network data. Congratulations for the excellent work.
The ROM will no longer receive bugfixes?

pls compile

publish a release