Recently i have ported a cm12.1 beta 7 stable v2 rom
Everything is working fine except for front camera & Bluetooth
Plz can anyone know how to fix this?
I have tried many lib files, but non of them r working
Plz help on it to fix this issue
Anyone plz
Your issue is gonna be a kernel issue and without the source there is nothing you can do. It is a common issue with devices running that chip set. That's why developers don't touch devices with it.
zelendel said:
Your issue is gonna be a kernel issue and without the source there is nothing you can do. It is a common issue with devices running that chip set. That's why developers don't touch devices with it.
Click to expand...
Click to collapse
My phone is Symphony h150. Its mediatek mt6582 chipset.
I don't know about any source file. But i think not.
So ur telling me that there's no way
rabin69x said:
My phone is Symphony h150. Its mediatek mt6582 chipset.
I don't know about any source file. But i think not.
So ur telling me that there's no way
Click to expand...
Click to collapse
Yes I'm saying that without a proper kernel then there will be things that just can't be fixed. Normally things like the camera and wifi radios. You might be able to hack your way through it but it will take weeks of searching through the code.
The kernel source code is the base code that is required by law to be published for any device that runs a Linux kernel (any android device) the issue with that chip set is they are based in China and dont respect copyright laws or the GPL.
rabin69x said:
My phone is Symphony h150. Its mediatek mt6582 chipset.
I don't know about any source file. But i think not.
So ur telling me that there's no way
Click to expand...
Click to collapse
If it's still actual for you (2 years, but still...), mediatek has laid off some kernel and AOSP sources for mt65xx series. Also check out this repo: github.com /bq/aquaris-E5, it has some code for your chip and other Mediatek stuff.
Also you have few other options:
Build your ROM around existing (official) kernel, adding more drivers as .ko's. I've had certain success adding some USB drivers like that.
Use some .so's from your original ROM. Sometimes manufacturers don't provide sources for libcamera.so/libcamera_client.so (camera), libhardware.so/libhardware_legacy.so (wifi and some minor stuff, like vibromotor)
Related
Hi!
I just want to vent my anger
Has anybody noticed that there are a minimum of four "parties" that work on an android kernel tree?
First there is the android open source project.
Then there is the CodeArora project.
There is also a kernel tree at Cyanogenmod.
And last but not least we have the "manufacturer" kernel tree.
AOSP has got a common tree and an individual tree for each architecture- just like Cyanogenmod.
CodeAurora has got multiple(!) trees for a single architecture.
The manufacturer seems to use some of CodeAurora's trees in the majority of cases.
Ah- I forgot the "original" linux kernel tree
This way we never get the most efficient and most stable kernel.
Just my two cents
you're right, but not only the kernel is used. LG takes code from codeaurora project - have seen this in code from the frameworks base tree^^
but on the other side: better they use community code as own code that didn't works perfect
WTF? LG really takes his sources from CodeAurora?!?!?
Well since code aurora is dedicated to qualcomm SoCs if i were a kernel developer i wud start with that tree..one question though does codeaurora contain gb kernel (.35) source for our msm7227 ??? u guys checked it out ???even if they theres a lot of other hardware that are going to need proprietary drivers i guess... THird world peripherals make porting tougher.. its just my take correct me if i m wrong
sarfaraz1989 said:
Well since code aurora is dedicated to qualcomm SoCs if i were a kernel developer i wud start with that tree..one question though does codeaurora contain gb kernel (.35) source for our msm7227 ??? u guys checked it out ???even if they theres a lot of other hardware that are going to need proprietary drivers i guess... THird world peripherals make porting tougher.. its just my take correct me if i m wrong
Click to expand...
Click to collapse
my kernel patches are taken from the codeaurora .35 source, but i can't adopt the complete kernel. there is a "must understand" and "must have many time" to do that
andy572 said:
my kernel patches are taken from the codeaurora .35 source, but i can't adopt the complete kernel. there is a "must understand" and "must have many time" to do that
Click to expand...
Click to collapse
That is exactly the problem!
I cannot really judge which patch from which tree is good- because I have not the time to read through Qualcomm's manuals (if they are public at all) and the kernel source.
If they would concentrate on one tree everything would be fine (ok- if you look at the "chaos commits" in the git repositories you become sick )
@caveman u working on a P500 kernel ??? how is porting so friggin easy for HTC devices..Do they have open source driver /generic hardware or what i mean a few of em even got a honeycomb partial port forget 2.3 ....
sarfaraz1989 said:
@caveman u working on a P500 kernel ??? how is porting so friggin easy for HTC devices..Do they have open source driver /generic hardware or what i mean a few of em even got a honeycomb partial port forget 2.3 ....
Click to expand...
Click to collapse
LG have some specific (old) hardware - they are using qualcomm hardware, but it's to old for newer kernel sources. the other problem is low cost hardware like the display - ms6000 is never used today, new devices are using samsung displays.
look at the wlan/smd chip - bcm4325 is never supported, bcm4329 is newer and is in kernel .38 too ... do you know, what i mean?
old hardware drivers are rare in kernels - never used drivers gets removed from tree, so there is no chance to bring it back.
ofcourse that's why it's called EVOLUTION
so it looks like u were right about getting a new phone
ciolnadu said:
ofcourse that's why it's called EVOLUTION
so it looks like u were right about getting a new phone
Click to expand...
Click to collapse
yes, it's marketing strategy and its ok - but why should i buy me a new device, when my is doing a good job?
andy572 said:
but why should i buy me a new device, when my is doing a good job?
Click to expand...
Click to collapse
+1 agreed 100% with andy.
andy572 said:
LG have some specific (old) hardware - they are using qualcomm hardware, but it's to old for newer kernel sources. the other problem is low cost hardware like the display - ms6000 is never used today, new devices are using samsung displays.
look at the wlan/smd chip - bcm4325 is never supported, bcm4329 is newer and is in kernel .38 too ... do you know, what i mean?
old hardware drivers are rare in kernels - never used drivers gets removed from tree, so there is no chance to bring it back.
Click to expand...
Click to collapse
Do you mean the drivers sources were in the old kernel and are removed in the new one? If so, I mean we have the old sources, why is it so difficult to port them to the new kernel sources? I am not a kernel developer so probably I am missing something
rivett said:
Do you mean the drivers sources were in the old kernel and are removed in the new one? If so, I mean we have the old sources, why is it so difficult to port them to the new kernel sources? I am not a kernel developer so probably I am missing something
Click to expand...
Click to collapse
code isn't moved but deleted.
Has anybody found out the CodeAurora git commit on which LG's V10r is based on?
Hello Everybody,
I want to know that how can i get the kernel from stock rom or any other method for rom development especially for ICS development for our Device i.e. Micromax A85 a re-branded model of K-Touch w700/Cherry Magnum 2x it is an Tegra-2 Dual-Core Device and still running on Gingerbread and now we want ICS :crying: . But the only thing which we are not having is kernel source and Micromax is not giving it to us as well .So people please help us.Please!!!!!!!
And if you can help us in any different way like helping as porting rom from any device to on our device, Please let me know!!!! :cyclops:
Micromax is ****.
We fought long enough for kernel source...got nothing..
My A70 has Froyo...we couldn't get touch to work in CM7...it booted though..
I don't think there's any hope in the kernel source matter.
akshaybz said:
Micromax is ****.
We fought long enough for kernel source...got nothing..
My A70 has Froyo...we couldn't get touch to work in CM7...it booted though..
I don't think there's any hope in the kernel source matter.
Click to expand...
Click to collapse
Well Bro. You are right i have fought for those kernel too but we didn't get anything at last and they kept deleting our posts from their fb page.
And for your device i found this on Xda while surfing a long time ago and thinks that you might want to give it a try........
" Micromax uses qualcomm chipsets. You can find their kernel here. Just look at your device's build.prop for ro.product.board. For example, my Micromax A57 uses msm7627a chipset. "
akshaybz said:
Micromax is ****.
We fought long enough for kernel source...got nothing..
My A70 has Froyo...we couldn't get touch to work in CM7...it booted though..
I don't think there's any hope in the kernel source matter.
Click to expand...
Click to collapse
Oppss my fault.....
I can't post link so here's the link
www . codeaurora . org / xwiki / bin / QAEP /
Just remove the spaces
Just Search in Qualcomm's website. It should be there.
http://forum.xda-developers.com/showthread.php?t=1808167
coolsandie said:
Just Search in Qualcomm's website. It should be there.
http://forum.xda-developers.com/showthread.php?t=1808167
Click to expand...
Click to collapse
Bro. My device is Nvidia Tegra 2 so i think i have to find the kernel in nvidia site and i wasn't able to find them.
Hi thanks
Sent from my HTC Desire HD using xda premium
vishvajeet.me said:
Bro. My device is Nvidia Tegra 2 so i think i have to find the kernel in nvidia site and i wasn't able to find them.
Click to expand...
Click to collapse
I was referring about Micromax models that uses Qualcomm chipsets, as most of them nowadays release Qualcomm based CPU.
Regarding, Nvidia Tegra 2, search for a similar device (maybe Samsung/Sony/Motorola etc.) that uses this CPU, and see whether they have got any custom kernel. Maybe it helps regarding directing to actual sources.
coolsandie said:
I was referring about Micromax models that uses Qualcomm chipsets, as most of them nowadays release Qualcomm based CPU.
Regarding, Nvidia Tegra 2, search for a similar device (maybe Samsung/Sony/Motorola etc.) that uses this CPU, and see whether they have got any custom kernel. Maybe it helps regarding directing to actual sources.
Click to expand...
Click to collapse
Thnx Man, I will try to find the source.
The HTC Desire 310 runs on a MediaTek SoC, and HTC only has the source code for the kernel. Is it possible to build a Custom ROM like CM for the device? And what are the drawbacks of doing this?
Lynuxen said:
The HTC Desire 310 runs on a MediaTek SoC, and HTC only has the source code for the kernel. Is it possible to build a Custom ROM like CM for the device? And what are the drawbacks of doing this?
Click to expand...
Click to collapse
Basically all a ROM development takes is a kernel source ,a device tree(how the source has to build your ROM {resolution,kernel source command lines....etc are set here}) , a vendor tree( usually proprietary shared libraries got from stock ROM ). Once you've got all these all you have to so is type make bacon. But since its mediatek its pretty hard to build anything since mediatek ril/libraries are not open source.
So doing this blindfolded won't work.
Lynuxen said:
So doing this blindfolded won't work.
Click to expand...
Click to collapse
Won't work, unless you set up a device tree for your SoC. MT6589 device tree may work for building only recovery but nothing further.
Yes, as @MasterAwesome said you need actually 3 components: Vendor tree, kernel source and device tree. Making vendor and device tree from scratch is hard.
GeekyDroid said:
Yes, as @MasterAwesome said you need actually 3 components: Vendor tree, kernel source and device tree. Making vendor and device tree from scratch is hard.
Click to expand...
Click to collapse
Hard, but not impossible? I really want to invest my time in something like this. Pretty long shot, will something like a method for reversed engineering the vendor and device tree work?
Lynuxen said:
Hard, but not impossible? I really want to invest my time in something like this. Pretty long shot, will something like a method for reversed engineering the vendor and device tree work?
Click to expand...
Click to collapse
Vendor tree is pretty easy to setup. You'd want to start with the CyanogenMod version which is similar your current android version. If your device has kitkat download cm11 sources. Read their docs about setting up a device tree(its not that hard). Vendor tree is basically just your stock ROM use it as a base to get your libs which are required for your ROM to start(logcats are helpful here). Since you have a similar SoC, you can use my device tree as a reference https://github.com/MasterAwesome/a210_device_tree/tree/master/micromax/a210. Initially just build a kernel and check if it works. And I have guides for kernel and ROM building,you could check it out.
MasterAwesome said:
Vendor tree is pretty easy to setup. You'd want to start with the CyanogenMod version which is similar your current android version. If your device has kitkat download cm11 sources. Read their docs about setting up a device tree(its not that hard). Vendor tree is basically just your stock ROM use it as a base to get your libs which are required for your ROM to start(logcats are helpful here). Since you have a similar SoC, you can use my device tree as a reference https://github.com/MasterAwesome/a210_device_tree/tree/master/micromax/a210. Initially just build a kernel and check if it works. And I have guides for kernel and ROM building,you could check it out.
Click to expand...
Click to collapse
Massive thanks MasterAwesome. :highfive:
Hi
Please build or port an Aosp rom to our great devices.
If somebody agree with me, please strengthen in it.
Thanks
zsolt
There are people working on CM and AICP ports. You can see here: http://en.miui.com/thread-407842-1-1.html
prismk said:
There are people working on CM and AICP ports. You can see here: http://en.miui.com/thread-407842-1-1.html
Click to expand...
Click to collapse
yes i know, i have seen these posts
thanks
If you already knew then why did you start a new thread?
Why do some people think that asking for a ROM will make it magically happen faster or something?
Sent from my Redmi Note 4 using Tapatalk
Do you use AOSP rom if that rom don't have fingerprint function (because RMN4 use FPC1035 with MTK TrustSonic enabled, it's so hard to port it unless Xiaomi release kernel source code) ?
Most people asking for porting rom from other devices but also demand porting rom have full functions working like original rom which impossible to make it happen...
longnt2007 said:
Do you use AOSP rom if that rom don't have fingerprint function (because RMN4 use FPC1035 with MTK TrustSonic enabled, it's so hard to port it unless Xiaomi release kernel source code) ?
Most people asking for porting rom from other devices but also demand porting rom have full functions working like original rom which impossible to make it happen...
Click to expand...
Click to collapse
Yep. As I said in the X20 kernel thread, it's only just the beginning because that's only generic X20 kernel source. ODM's *always* add their own hardware that is not covered by the original kernel source.
Typically, Camera and Sensor drivers were the most difficult to port (with blobs and reverse-engineering stock firmware). But TrustSonic sounds like it will be the biggest task.
Since I have nothing to do, I want to get into this ROM development stuff with my older device, hopefully I will learn something.
My trouble is that I can't build any ROM for that device(Lenovo Yoga B6000-F), because I can't find the device tree for it or anything related...
How can I get it/make it by myself?
BTW, this is a Tablet - Lenovo Yoga 8; B6000-F (WiFi version, there is a 3G one)
DarkAlpha.Sete said:
Since I have nothing to do, I want to get into this ROM development stuff with my older device, hopefully I will learn something.
My trouble is that I can't build any ROM for that device(Lenovo Yoga B6000-F), because I can't find the device tree for it or anything related...
How can I get it/make it by myself?
Click to expand...
Click to collapse
You can make it yourself, but you won't find any tutorial how to make device tree, trust me I've been there. Also I see that you have device with mediatek chipset so I doubt you will succed because well "mediatek" however you can build device tree if there is device tree for device with same chipset and there is common tree for mt8125 chipset and then you edit just some part of tree to suit your phone, I've done same thing but never get to bulding rom because anything can be flashed on phone because of some "protection" so I didn't bother.
Professor Woland said:
You can make it yourself, but you won't find any tutorial how to make device tree, trust me I've been there. Also I see that you have device with mediatek chipset so I doubt you will succed because well "mediatek" however you can build device tree if there is device tree for device with same chipset and there is common tree for mt8125 chipset and then you edit just some part of tree to suit your phone, I've done same thing but never get to bulding rom because anything can be flashed on phone because of some "protection" so I didn't bother.
Click to expand...
Click to collapse
Uh ok I will do some searches, probably ending by giving up ... Probably all my next devices won't be this MediaTek stuff...(still don't know why it heats so much)
Btw, where do you find those trees? I can't find any for this chipset...
DarkAlpha.Sete said:
Uh ok I will do some searches, probably ending by giving up ... Probably all my next devices won't be this MediaTek stuff...(still don't know why it heats so much)
Btw, where do you find those trees? I can't find any for this chipset...
Click to expand...
Click to collapse
On github. Device tree's are named "android_device_*manufacturer*_*model*"
Well first look for list of devices using that chipset, and try finding trees for that models, I don't say you will find any but you can try.