Basically the title!
I'm thinking of getting an mx5 here in India! Coming from Nexus, Cant get myself to use anyother environment other than stock! Is there any AOSP or AOKP or CM builds for this ? I did a Brief search and found no support!
Thanks in Advance!
Meizu MX5 has locked bootloader, we need a way to unlock it to start the development
iicc said:
Meizu MX5 has locked bootloader, we need a way to unlock it to start the development
Click to expand...
Click to collapse
Gotcha, So, even if we were to unlock the bootloader, We still don't have the kernel sources right? Its a mediatek helios SoC, and AFAIK they haven't released the sources, Right?
prince147 said:
Gotcha, So, even if we were to unlock the bootloader, We still don't have the kernel sources right? Its a mediatek helios SoC, and AFAIK they haven't released the sources, Right?
Click to expand...
Click to collapse
Yes but without sources we can build roms. The problem is that maybe there would be something that cant be fixed in the rom, or requires an extensive reverse engineering.
You can see the cm12.1 rom for mx4, it is almost perfect. And was built without sources
Related
My question is can I use a devices stock kernel to create a build for said device?
My T-Mobile Sony Xperia Z has a locked bootloader and can only run roms using the stock kernel. I've seen other AOSP looking roms run off a devices stock kernel so I was hoping it possible.
Can anyone guide me in this? I would love for my phone to have HALO and different modes like phablet or tablet mode from Paranoid Android. Is this possible with a stock kernel or would features like that require a custom one? I assume it could be run just like Facebook Messenger does it..just as an app I mean.
knightsray said:
My question is can I use a devices stock kernel to create a build for said device?
My T-Mobile Sony Xperia Z has a locked bootloader and can only run roms using the stock kernel. I've seen other AOSP looking roms run off a devices stock kernel so I was hoping it possible.
Can anyone guide me in this? I would love for my phone to have HALO and different modes like phablet or tablet mode from Paranoid Android. Is this possible with a stock kernel or would features like that require a custom one? I assume it could be run just like Facebook Messenger does it..just as an app I mean.
Click to expand...
Click to collapse
Why do you think this isn't done already if it was this easy? The PA, CM framework and such needs code in the kernel and the stock kernel can't be remade because nobody's got the signing code for it, except Sony.
You'll need a unlocked bootloader for Omni ROM.
@MikeChannon, I think this thread can be closed.
Skickat från min C6603 via Tapatalk 2
TheHawk002 said:
Why do you think this isn't done already if it was this easy? The PA, CM framework and such needs code in the kernel and the stock kernel can't be remade because nobody's got the signing code for it, except Sony.
You'll need a unlocked bootloader for Omni ROM.
@MikeChannon, I think this thread can be closed.
Skickat från min C6603 via Tapatalk 2
Click to expand...
Click to collapse
You're wrong. It's not impossible to use stock kernel with a custom ROM, sometimes it's even inevitable, because there are no kernel sources available or the bootloader cannot be unlocked.
Adam77Root said:
You're wrong. It's not impossible to use stock kernel with a custom ROM, sometimes it's even inevitable, because there are no kernel sources available or the bootloader cannot be unlocked.
Click to expand...
Click to collapse
It's pretty much impossible to do so with an AOSP-based firmware. Occasionally it's tried, but always leads to poor results (see CM9 ICS builds for I9100 prior to kernel source release that used an initramfs repack.)
At a minimum it requires initramfs changes, and since the initramfs is signature-checked as part of the kernel image on every device I know of, it's not possible without terrible terrible hacks. Personally, I would prefer to not bother at all supporting any locked device that requires workarounds in the build. It leads to difficult to maintain code, and if people want to run an open source firmware, they should just not buy a locked (or non-unlockable) device in the first place.
Entropy512 said:
It's pretty much impossible to do so with an AOSP-based firmware. Occasionally it's tried, but always leads to poor results (see CM9 ICS builds for I9100 prior to kernel source release that used an initramfs repack.)
At a minimum it requires initramfs changes, and since the initramfs is signature-checked as part of the kernel image on every device I know of, it's not possible without terrible terrible hacks. Personally, I would prefer to not bother at all supporting any locked device that requires workarounds in the build. It leads to difficult to maintain code, and if people want to run an open source firmware, they should just not buy a locked (or non-unlockable) device in the first place.
Click to expand...
Click to collapse
I also prefer having sources and building kernels rather than doing bad hacks, I just pointed out that it's possible and sometimes is a must (Not talking about Omni, just in general.), there are devices without unlockable BL. E.g. we were using 2nd-init method on p880 before official JB came out and BL unlock became possible.
Adam77Root said:
I also prefer having sources and building kernels rather than doing bad hacks, I just pointed out that it's possible and sometimes is a must (Not talking about Omni, just in general.), there are devices without unlockable BL. E.g. we were using 2nd-init method on p880 before official JB came out and BL unlock became possible.
Click to expand...
Click to collapse
May I ask if you ever had a AOSP based firmware or just remakes of the stock ROM to look like AOSP? Because there you've the big difference. It's (obviously, because Entropy is Entropy ) just like @Entropy512 said.
Skickat från min C6603 via Tapatalk 2
TheHawk002 said:
May I ask if you ever had a AOSP based firmware or just remakes of the stock ROM to look like AOSP? Because there you've the big difference. It's (obviously, because Entropy is Entropy ) just like @Entropy512 said.
Skickat från min C6603 via Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. I know the difference between a themed and a real AOSP rom. If I didn't, I wouldn't be a RD. What I wrote is totally possible and legit.
Sent from my OmniROM-powered LG Optimus 4X HD
http://www.sammobile.com/2013/11/05/samsung-releases-android-4-3-kernel-source-for-galaxy-s3/
Wow man latest news isn t it?? Using Internet Explorer??
And? Could you explain a bit in how it help us?
Thanks.
Enviado desde mi GT-I9300 usando Tapatalk
It means we can finally have custom kernels woooooo
Sent from my GT-I9300 using XDA Premium 4 mobile app
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
ahmedmelm said:
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
Click to expand...
Click to collapse
http://source.android.com/source/building.html
Read everything on left hand side
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
http://source.android.com/source/building.html
Read everything on left hand side
Click to expand...
Click to collapse
That's way cool. But any matter to accelerate the process? Would really compiling this kernel and pushing it to existing ROM work?
What do you think source code is exactly? What is it you think you want?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
granets said:
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
Click to expand...
Click to collapse
No. Read following for explanation.
dhiru1602 said:
Blobs are userspace components which correspond to the HAL (Hardware Abstraction Layer). It is this layer which is responsible for communication between the kernel and the operating system. GPU kernel driver is opensource, but the GPU HAL is closed source. This is the case with all the devices, but on our device, much more components of the HAL are closed source like FIMC, FIMG, HWJPEG, TVOUT. Samsung doesn't release the source code for this components because it doesn't necessarily have to. Without the source code, we are forced to use the compiled binary which may or may not work properly. Since we are left without options, we often mess around with the Android framework, making dirty hacks to get them to work. We will not be able to futureproof our device with newer versions of Android unless we have the source code since making edits on compiled binaries is not possible and hence we have to wait for official releases so that we could get newer binaries (blobs). Here is the list of all the blobs that we use on our device. Having proprietary code is not uncommon, but Samsung doesn't release the source code for essential parts of the OS like Graphics subsystem, OMX and DSP, which makes things more complex provided there is no documentation for the SOC, nor they are wiling to help developers.
Click to expand...
Click to collapse
dhirend_6d said:
No. Read following for explanation.
Click to expand...
Click to collapse
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
granets said:
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
Click to expand...
Click to collapse
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
rootSU said:
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
Click to expand...
Click to collapse
These include the latest mali r3p2. So we have now userspace binaries + kernel source drivers. It makes this possible, which is awesome. It's coming for all exynos4 devices.
http://developer.sonymobile.com/201...-aosp-for-xperia-on-github-video-open-source/
Enjoy
I wonder if camera and modem will be supported in the future.
well thats good news
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Yeah we already knew because author already posted here http://forum.xda-developers.com/showthread.php?t=2907471
Sent from my D6503 using Tapatalk
Felimenta97 said:
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
I'd argue it's an official release - a release for developers, but it's still official.
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
funky0308 said:
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
Click to expand...
Click to collapse
I see this too much... Aka agreement on ur post
And secondary point,
Not a rom, its neither a aosp rom
Yes official but its purely there for CM11, AOSP and any deviant developers to correct problems with their builds or correcr sonys problems
Its a greed thing sony is doing, it will benefit sony as well as xda devs
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Cigaras said:
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Click to expand...
Click to collapse
Unlocked bootloaders ONLY. If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void, thus creating problems for Sony, with non Devs users returning phones and help queries etc...
waynekirby said:
If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void
Click to expand...
Click to collapse
But if AOSP is provided by Sony themselves, why would they threat it as warranty voiding?
Lets take for example Xiaomi, for Mi3 and Mi4 gsmarena.com said that You could choose either MIUI or AOSP, and You get OTA updates for both (I am not sure if that is official, I do not own a Xiaomi device). Would be great if Sony would do something similar, Google Play Edition would also work for me, as long as I get to keep all the Bravia Engine and X-Reality goodness
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
I highly doubt this. If it's true, you should be able to show that, though...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
adyscorpius said:
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
Click to expand...
Click to collapse
I don't understand your point here...
I know there are differences, that's why Sony works on this, officially.
We have CM and AOSP ROMs for Z1/Z2 but Sony now hired guy from here to help them in building AOSP that'll work on LB and is released by Sony.
That way, they still can control and approve what will go to device abd what won't...
Maybe I'm wrong but what's the point of releasing AOSP without kernel support from bootloader?
We already have that..
My guess would be - they want us to use AOSP but they don't want us to unlock bootloader and mess with DRM keys.
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
funky0308 said:
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
Click to expand...
Click to collapse
Would be nice if instead of your warrenry being voided, its changed
So free repairs for sony fauls so long as its not caused by you rom
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Haldi4803 said:
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Click to expand...
Click to collapse
We only are getting source it seems but to have this for locked bootloaders sony must compile and sign a rom and kernel
Hi folks! I just read this news.. and I'm wondering if this may mean that, finally, custom ROMs won't lose anymore the ability to properly use low power cores of our SoC.
And, I know, I'm a dreamer.. could this news lead to a stable and functional Marshmallow ROM?
Cheers
If only I could unlock the bootloader on mine
98lumina said:
If only I could unlock the bootloader on mine
Click to expand...
Click to collapse
I'm on xt1052.. which version do you have?
XT1058 i want to downgrade from Lpa23.12-21.7 to lpa23.12-21.1
Does the source being released mean that Deva can now access low power cores?
best news I've heard all day !
stealtheye said:
Does the source being released mean that Deva can now access low power cores?
Click to expand...
Click to collapse
I don't actually know.. I'm waiting for some devs to reply!
stealtheye said:
Does the source being released mean that Deva can now access low power cores?
Click to expand...
Click to collapse
No. That's something deep inside the stock rom. Kernel sources have been around a long time, just not for lollipop.
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
vsrookie said:
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
Click to expand...
Click to collapse
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Jonny said:
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Click to expand...
Click to collapse
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Vendor tree example >>> https://github.com/omnirom/android_vendor_omni
Device tree example >>> https://github.com/omnirom/android_device_sony_kitakami-common
The Android system does use functions from the kernel but its not really "aware" of doing so, you can run custom ROM's like DU, Omni etc from stock kernels most of the time without any issues.
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Boristruyens said:
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Click to expand...
Click to collapse
Tbh that is a massive probability, making device and vendor trees is not non-trivial and is a lot of work. For instance the HTC 10 still doesn't have a stable CM build, and there are some hard hitters in the AOSP dev world that own that device. I'll have a look and see what I can do but I'm an app developer and an apk editor (i.e. Java and Smali are more my languages than C/C++) more than a source builder so I might not be able to do much.
Can i use it for making recovery for moto m
The P9000 has a kernel on github anyway ...