Related
Hi,
I thought this was not yet possible to port Cyanogenmod on Dual Sim devices, at least not properly, but then I saw this post:
http://forum.xda-developers.com/showthread.php?t=2246874
It gave me a real hope for the generic MT6589 device I am currently using.
I am new to all of this, so I hope I don't bother everyone.
Also, my device uses obviously different hardware, but uses the same processor, so I managed to install the above ROM and got it working but without any screen display.
In other words, it was working, and I could see everything as far as the installation wizzard was concerned, so I thought I was fine, but then when I was done and it rebooted, I could not see anything on the display anymore, but the phone was still working working.
So I am assuming some obvious hardware drivers differences, and that the old drivers were still working till I restarted?
Is there a way to modify the rom to make it work?
What files would I need to pull from my device to add/replace in the posted ROM to make it worlk, if that is possible?
Or does cynanogenmod have to compile with the files of my device to work, even though the processor bit had already been done?
If so, I have no problem in trying to compile cyanogenmod from scratch, but I will still get the dual SIM problem, and I thought this has been fixed in this ROM.
So what modifications would need to be done to incorporate the DUAL SIM issue, and make it work, or has this already been resolved upstream?
Is there a github or such of the modifications and alterations that were done to Cyanogenmod for this posted ROM in order to get it working?
I am willing to use those files and port it to my device, but without these modifications, I will not be able to do anything, even though the kernel sources for MT6589 are openly available now.
Sorry for asking this question here, but I tried to reply to the original post and it did not let me.
Is it okay to ask this here?
If not, please excuse me, and if you can forward me to the right place.
Thanks and regards
noobworld said:
Hi,
I thought this was not yet possible to port Cyanogenmod on Dual Sim devices, at least not properly, but then I saw this post:
http://forum.xda-developers.com/show....php?t=2246874
It gave me a real hope for the generic MT6589 device I am currently using.
I am new to all of this, so I hope I don't bother everyone.
Also, my device uses obviously different hardware, but uses the same processor, so I managed to install the above ROM and got it working but without any screen display.
In other words, it was working, and I could see everything as far as the installation wizzard was concerned, so I thought I was fine, but then when I was done and it rebooted, I could not see anything on the display anymore, but the phone was still working working.
So I am assuming some obvious hardware drivers differences, and that the old drivers were still working till I restarted?
Is there a way to modify the rom to make it work?
What files would I need to pull from my device to add/replace in the posted ROM to make it worlk, if that is possible?
Or does cynanogenmod have to compile with the files of my device to work, even though the processor bit had already been done?
If so, I have no problem in trying to compile cyanogenmod from scratch, but I will still get the dual SIM problem, and I thought this has been fixed in this ROM.
So what modifications would need to be done to incorporate the DUAL SIM issue, and make it work, or has this already been resolved upstream?
Is there a github or such of the modifications and alterations that were done to Cyanogenmod for this posted ROM in order to get it working?
I am willing to use those files and port it to my device, but without these modifications, I will not be able to do anything, even though the kernel sources for MT6589 are openly available now.
Sorry for asking this question here, but I tried to reply to the original post and it did not let me.
Is it okay to ask this here?
If not, please excuse me, and if you can forward me to the right place.
Thanks and regards
Click to expand...
Click to collapse
link is dead.
who is the dev.
prantoroy said:
link is dead.
who is the dev.
Click to expand...
Click to collapse
Thanks for the headsup.
I placed in an incomplete link, here is the complete link:
http://forum.xda-developers.com/showthread.php?t=2246874
I also updated the post.
The developper seems to be:
bgcngm
Thanks
noobworld said:
Thanks for the headup.
I placed in an incomplete link, here is the complete link:
http://forum.xda-developers.com/showthread.php?t=2246874
I also updated the post.
The developper seems to be:
bgcngm
Thanks
Click to expand...
Click to collapse
give sme time.will try
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
prantoroy said:
give sme time.will try
Click to expand...
Click to collapse
just as I thought.the kernel.
its not fr u. ask dev to create a kernel fr u!
Thank you for your fast reply.
Where do I ask?
Also, I was hoping to learn how to do it, and have the sources if possible, or at least how to modify the sources, because I have about three of these chinese devices, all using the same processor, but with different hardware.
Thanks
prantoroy said:
give sme time.will try
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
just as I thought.the kernel.
its not fr u. ask dev to create a kernel fr u!
Click to expand...
Click to collapse
noobworld said:
Thank you for your fast reply.
Where do I ask?
Also, I was hoping to learn how to do it, and have the sources if possible, or at least how to modify the sources, because I have about three of these chinese devices, all using the same processor, but with different hardware.
Thanks
Click to expand...
Click to collapse
Ask The dev
And Its not that easy
prantoroy said:
Ask The dev
And Its not that easy
Click to expand...
Click to collapse
Well, I tried posting on the original thread, but couldn't.
Then tried to send a private message, but couldn't.
So I started this thread.
You said:
And Its not that easy
Click to expand...
Click to collapse
Did you mean it is not easy to contact the dev, or not easy to compile the sources for my devices?
Just wanted to be sure.
Thanks again
noobworld said:
Well, I tried posting on the original thread, but couldn't.
Then tried to send a private message, but couldn't.
So I started this thread.
You said:
Did you mean it is not easy to contact the dev, or not easy to compile the sources for my devices?
Just wanted to be sure.
Thanks again
Click to expand...
Click to collapse
no you cant post until u have 10 posts
and its not easy to develop rom
prantoroy said:
no you cant post until u have 10 posts
and its not easy to develop rom
Click to expand...
Click to collapse
I can see that, but I think with some patience I can do it.
Also, I have been using Linux for years now, and it seems I just need to figure out how things are laid out in Android.
And once I get used to that, then things become easier.
I am assuming that the linux kernel needs to be compiled with the specific drivers related to my hardware, right?
However, that would still not take into account:
- The changes made in Android/Cyanogenmod that take into account Dual SIM functionality
- How Cyanogenmod is actually laid-out, such as are changes done directly to stock android, or applied as patches?
I was thinking of the following:
1) Checking for the difference between stock Android and Cyanogenmod, and save aside the diff changes to make a patch file.
2) Then hope to find the sources of the stock android that has already been modified to work with MT6589, since these devices obviously use Android on them with some modifications
3) Then apply the patch made in (1) on these sources
Thus, I also need one important question answered:
If I were to download the sources for Cyanogenmod (which I already did), are the patches to the stock Android already applied, or are they placed in a separate folder, and applied on compilation?
I have this feeling that the above patches will probably not work out, because there will probably be extra functions, code that the patch will not be able to take into account, and will have some type of non-working or broken system, until I figure out what is missing.
I might get it to boot to a certain point (most probably shell like), and it would stop there.
Well, in either case, after writing all this down, I started to visualize more the hard part you are talking about, and this would require good knowledge of Android Code and structure.
Thus, if anyone can give me the required Cyanogenmod sources that have already been modified to work on an MT6589, or the diff patches between the normal and modified Cynogenmod, then that would be amazing.
Then I will have to only figure out at that point the propriety files I need to pull from the device, and specific vendor modifications.
Of course, I am just speculating, as this depends on how Android/Cyanogenmod is structured, and I could be completely off the mark, and have no idea what I am talking about.
Thanks
noobworld said:
I can see that, but I think with some patience I can do it.
Also, I have been using Linux for years now, and it seems I just need to figure out how things are laid out in Android.
And once I get used to that, then things become easier.
I am assuming that the linux kernel needs to be compiled with the specific drivers related to my hardware, right?
However, that would still not take into account:
- The changes made in Android/Cyanogenmod that take into account Dual SIM functionality
- How Cyanogenmod is actually laid-out, such as are changes done directly to stock android, or applied as patches?
I was thinking of the following:
1) Checking for the difference between stock Android and Cyanogenmod, and save aside the diff changes to make a patch file.
2) Then hope to find the sources of the stock android that has already been modified to work with MT6589, since these devices obviously use Android on them with some modifications
3) Then apply the patch made in (1) on these sources
Thus, I also need one important question answered:
If I were to download the sources for Cyanogenmod (which I already did), are the patches to the stock Android already applied, or are they placed in a separate folder, and applied on compilation?
I have this feeling that the above patches will probably not work out, because there will probably be extra functions, code that the patch will not be able to take into account, and will have some type of non-working or broken system, until I figure out what is missing.
I might get it to boot to a certain point (most probably shell like), and it would stop there.
Well, in either case, after writing all this down, I started to visualize more the hard part you are talking about, and this would require good knowledge of Android Code and structure.
Thus, if anyone can give me the required Cyanogenmod sources that have already been modified to work on an MT6589, or the diff patches between the normal and modified Cynogenmod, then that would be amazing.
Then I will have to only figure out at that point the propriety files I need to pull from the device, and specific vendor modifications.
Of course, I am just speculating, as this depends on how Android/Cyanogenmod is structured, and I could be completely off the mark, and have no idea what I am talking about.
Thanks
Click to expand...
Click to collapse
ok I will help u.
go here
http://forum.xda-developers.com/forumdisplay.php?f=613
prantoroy said:
ok I will help u.
go here
http://forum.xda-developers.com/forumdisplay.php?f=613
Click to expand...
Click to collapse
Wow... Even though I searched for so long, I did not find this.
I guess I did not know what to search for.
I thank you a lot.
I will probably take a while to learn how to use this, so I will disappear until I figure it out.
If I managed to do anything, then will come back and post my status.
Thanks again
noobworld said:
Wow... Even though I searched for so long, I did not find this.
I guess I did not know what to search for.
I thank you a lot.
I will probably take a while to learn how to use this, so I will disappear until I figure it out.
If I managed to do anything, then will come back and post my status.
Thanks again
Click to expand...
Click to collapse
glad I could help.
and don't bother .its my job to help new.
and pm me if u need smthing.
and please close thread.
Hi All,
I have a Symbol/Motorola MC7090 it's currently running Windows Mobile 5.0 with messaging and security feature pack.
I cannot connect via Wifi and I cannot get the barcode scanner to work.
It was used by a developer to test there apps, I was told that it was reset back to factory specs.
Has anyone got a ROM so that I can put Android on this??
Best Regards
slyfoxbrewery
I hate to revive this post, but I have the same sort of question. Please let me know if I need to start a new thread. In my case, I have two ROMs from "Zebra" (who seems to have taken over this part of that company). Mine is also the MC40, but the question I have is what do I need to do to essentially convert this from a Windows 7 CE device, to an Android device. I have the drivers for both the Win version and the Android version. I also have 3 of the Android devices and 2 of the Win devices. The model numbers are exactly the same, only the OS is different. Im doing this for the company I work for. Any help would be greatly appreciated. Thanks in advance.
Hello All,
I am trying to re-vive the Ubuntu Touch port for Galaxy S3. In which of the many areas of XDA this would be placed?
- Its no official or unofficial Android ROM
- its rather like Sailfish OS
How to name the thread correctly according to [ROM] etc flags?
BR Florian
Flohack said:
Hello All,
I am trying to re-vive the Ubuntu Touch port for Galaxy S3. In which of the many areas of XDA this would be placed?
- Its no official or unofficial Android ROM
- its rather like Sailfish OS
How to name the thread correctly according to [ROM] etc flags?
BR Florian
Click to expand...
Click to collapse
Well, that should be the least of your problems!
Option58 said:
Well, that should be the least of your problems!
Click to expand...
Click to collapse
The other problems I manage locally - but I want to start a discussion thread soon, since I am convinced to be able to push out a test build soon. I want to involve more people into this, thereby generating more possible solutions for problems.
In case you are interested, the phone boots already correctly, kernel is fine without errors, Android container starts also without errors. Ubuntu´s init/upstart is mounting all necessary partitions, and brings up most of the basic services. Currently stuck with GUI since mir/libhybris/unity8 cannot paint on framebuffer or hw composer
BR Florian
Flohack said:
The other problems I manage locally - but I want to start a discussion thread soon, since I am convinced to be able to push out a test build soon. I want to involve more people into this, thereby generating more possible solutions for problems.
In case you are interested, the phone boots already correctly, kernel is fine without errors, Android container starts also without errors. Ubuntu´s init/upstart is mounting all necessary partitions, and brings up most of the basic services. Currently stuck with GUI since mir/libhybris/unity8 cannot paint on framebuffer or hw composer
BR Florian
Click to expand...
Click to collapse
I don't own your device. But if that's the case...good luck :good: :fingers-crossed:
Flohack said:
The other problems I manage locally - but I want to start a discussion thread soon, since I am convinced to be able to push out a test build soon. I want to involve more people into this, thereby generating more possible solutions for problems.
In case you are interested, the phone boots already correctly, kernel is fine without errors, Android container starts also without errors. Ubuntu´s init/upstart is mounting all necessary partitions, and brings up most of the basic services. Currently stuck with GUI since mir/libhybris/unity8 cannot paint on framebuffer or hw composer
BR Florian
Click to expand...
Click to collapse
Bro.. I own a s3 at&t.. And would love to help out on testing ROMs. This task of yours seems promising.
Meanwhile, I installed a Linux OS in my system of which am still trying to wrap my head around (If its of any help). So just call out anytime u need me.
holysaint1 said:
Bro.. I own a s3 at&t.. And would love to help out on testing ROMs. This task of yours seems promising.
Meanwhile, I installed a Linux OS in my system of which am still trying to wrap my head around (If its of any help). So just call out anytime u need me.
Click to expand...
Click to collapse
Hi,
good to know. We just need to make sure AT&T version does not have too much difference from the international one. Can you dedicate it for testing? It does not need data to be wiped normally, since Ubuntu runs off a container in the data partition but you never know...
I am currently stuck with the GUI and tbh I have no idea when and how this will be resolved. Samsung has done a great job with their GPU and Exynos, but our libhybris part does not want to play with it nicely.
Keep you updated!
BR
Actually I use it as my DD but wouldn't mind testing a few ROMs for the gd of the comm.
Aiite then. Patiently waiting for the update.
I have the international version of S3 GT-i9300. It is currently without a working rom, so I need to find time to see if it will boot with an official rom flashed with odin, it currently has an old clockwork mod recovery installed and a lineage os rom that wont boot..
If I get it working again, then I could dedicate it to testing... I would love to have a phone that was pure linux with phone capabilities... then I would no longer need to use google's linux abomination known as android
Hi,
sorry to say but I stopped now every porting activity, since Canonical dropped Ubuntu Touch and we are struggling on all other frontlines to get the community together for continuing the OS.
There will be no new hardware ports in the near future, which I think will be up to 1 year or 2. By that time, also S-III etc are end of life, since its hard to support multiple generations of smartphones with different kernels properly. Im afraid we are too late...
Anyway, contact me if you want to help in other areas of Ubuntu Touch going UBports community
BR
Anyone can post link for ubuntu touch note 2 n7100 please?all links are dead
laharl_22 said:
Anyone can post link for ubuntu touch note 2 n7100 please?all links are dead
Click to expand...
Click to collapse
same here ! I am also trying to find from so long, tried a lot but no luck !!
Please somebody post it
Hi there,
Florian from UBports. The active devices that we support can be found here: https://devices.ubports.com/#/ - that being said, you wont find the Note 2 there as an active device. What happened in the past I can´t say, but currently we have no ETA to work on new devices.
BR Florian
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Alando123 said:
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Click to expand...
Click to collapse
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with an assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
First of all, it depends on whether the stock source code is available for your device, if there is no stock source code available to the public(no, I'm not talking about the stock firmware file), then you will not be able to build a custom ROM from source for your device, which means that you won't be able to build anything like LineageOS because setting up the device tree requires the stock source code. No source code=no device tree, no device tree=no LineageOS or AOSP ROMs. Devices that do not have a source code available can only get ROMs if someone chooses to port a ROM from a similar device with similar hardware, that is the only way to get a ROM without stock source code. The stock firmware would be required in order to port a ROM from a similar device, if the stock firmware is not available, you can't port a ROM.
Sent from my LGL84VL using Tapatalk
Droidriven said:
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Alando123 said:
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Click to expand...
Click to collapse
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery such as TWRP(which you'd probably have to build for yourself, which is yet another task to learn in development along with learning to build a ROM, not to mention learning how to get the kernel right) in order to flash a LineageOS custom ROM or any other ROM that is not based on stock, TWRP is easier to learn how to build than a ROM, but still a task in itself. Modified stock ROMs can be customized and flashed without root or custom recovery but they aren't "true" custom ROMs, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Droidriven said:
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery in order to flash a LineageOS custom ROM or any other ROM that is not based on stock. Modified stock ROMs can be customized and flashed, but they aren't custom, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Alando123 said:
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Click to expand...
Click to collapse
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools. I also just stumbled upon the link to the LineageOS page about blobs right before you replied ?
Alando123 said:
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools
Click to expand...
Click to collapse
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Alando123 said:
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Click to expand...
Click to collapse
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Alando123 said:
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Click to expand...
Click to collapse
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I don't think that any camera app would have helped.. I replaced libcameracustom.so from a different device, and front camera works, but no both cameras have a blue hue on them
I am having problems with building lineageOS for my "Unsupported" Device I have made themed ROMS, Themes for cyanogenmod, Themes for substratum, basic apps for my ROM, and customized recovery and ported ROMS to my device but I need a small headstart to actually "Build" lineageOS for my device. Thats It
Regards
Manav Harsana
Hello all!
First time poster, just getting into rom porting and android dev.
making this thread, due to the serious lack of information / boards about these tiny china phones that are flooding wish/aliexpress and are stuck on android 6.0/7.0.
I've tried to use a few different roms as ports (where i patch select files from etc/lib and all that good stuff) using a guide found here specifically for mtk chipsets. I've only tried x32 to x32 same SoC, and patching kernel from stock rom in. This was without any kernel changes, still patching in my 3.18.19+ kernel over mostly 7.1.2 roms built for 3.18.19. I'm guessing the + makes it completely different like mt6737 vs 6737t or 6737m.
My goal is to port an MTK kernel to my current device (soyes s10, mt6737m android 6.0 kernel 3.18.19+ 3/32gb model) that supports android 7.1.2. I've found what I believe to be an almost the same version device tree, and I have ubuntu and windows and am rather well versed in both.
I'm not sure how to discern the kernel version (linux ver) of this download, but my "custom build version" is looking very similar, alps-mp-m0.mp1-V2.84_bd6737m.35g.b.m0_P81.
I'm mainly wondering:
1. Who else has some of these tiny china phones (only band 41 us support!) melrose, ifosa, soyes, unbranded, etc? I've ported over TWRP for this device also if anyone is interested. root was simple enough with mtk-su. It flashes zips but it wont boot roms. it's TWRP 3.2.1.0 or 3.1.2.0 I'm not 100%.
1a) could my whole problem be solved by porting a newer version of TWRP for the device?
2. can I port newer kernel 3.18.35 from source above?
3.MTK's whack implementation of fast charging, PE+ 2.0 support for my mt6737, they send 15w (5v3a) motorola branded charging brick with phone. but it seems to charge at random rates, not fast charging. Not sure if it's even worth it to try and find a brick that is listed as MTK PE+ compatible. anybody have any advice there? it would be a dope phone if the fast charge was reliable. maybe I can mod the kernel to force enable it in the future.
4. why won't any of my ported roms boot? I can't find a modules folder in my stock fw's lib image(s) where it should be in order to port. are these maybe just located in the root of /lib and very specific files I have to cherry pick and port over? i'm thinking android -all modules = no booting. not really sure where i'm going wrong but it's a million questions in one so if you can answer any of them, please chime in
I forgot I can't post any links, but like I have links to stuff
Thanks guys, I've been lurking these forums for near a decade.
It's nice to meet all of you, looking forward to some good learning
Nick
Hi mate.
First off, I'm really sorry -but I can't answer any of your questions...
I'm looking at the Servo S10 for myself, though ; how did you go with everything -any progress?
Also, how is the battery life? Sounds like it's not a deal-breaker. Sorry again that this isn't an answer to your questions, but I'd appreciate the feedback.
-anew