Related
ᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖᗖ
I just saw a Thread on XDA saying about Cyanogen for Mediatek MTK6577 Chipsets.....So thought it would be helpful for Varun and other kernel developers to make CM9...
The OP of the THREAD is bucefal82
Visit the Original Thread over : HERE
THREAD CONTENT
ᗊᗊᗊᗊᗊᗊᗊᗊ
Hey guys, We are going to try something new for our china phones - cyanogenmod.
But we need some more devs to get everything going.
For now we have:
-Github tree for Lenovo P700i(mediatek 6577, android 4.0.4, kernel 3.0.8)
-Lens_flare - original port author(may work with system folder and configs)
-some kernel source from other devices like liquid gallant
The main problem is getting adb to work that could help a lot on remaining development. For now even zygote not starting, but all partitions seems mounted successfully.
We need more devs (especially that could assemble working kernel for device), working with p700i may lead to following porting for other mtk devices, as sources are nearly the same.
ᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗᗗ
and this, PS: its the same phone as the cynus , there is the JB sources
http://wikogeek.com/
momohal said:
and this, PS: its the same phone as the cynus , there is the JB sources
http://wikogeek.com/
Click to expand...
Click to collapse
We got it already but,that isnt good
You got me broda! I was already aware of this but didn't got an idea to post here! Already Working on it!
ROGER THAT
TheDemiGod said:
You got me broda! I was already aware of this but didn't got an idea to post here! Already Working on it!
ROGER THAT
Click to expand...
Click to collapse
Bro,You too working on the CM kernel?? Best of Luck.....Thought it would help Others for getting Cm soon :cyclops: :cyclops:
Well that source in the OP is ICS... JB sources are still a mess... Nothing more that a Cyanogen 9 is possible I believe!
People make their own device tree's also! Instead of consuming that Nothing other than CM9 is possible instead help or GTFO! We will make it possible one day I believe!
@varun.chitre15: The Github Organization is ready! I already forked a few repo's! So, Start Working
---------- Post added at 12:21 PM ---------- Previous post was at 12:13 PM ----------
Dark4Droid said:
Bro,You too working on the CM kernel?? Best of Luck.....Thought it would help Others for getting Cm soon :cyclops: :cyclops:
Click to expand...
Click to collapse
Nopes! I am not making a CM Kernel instead directly building CM9! The Prebuilt Kernel will boot CM9! Though.... @DanceOff was also working to get CM10.1 Booting :cyclops: Now, That he knows about already available CM9 Sources we could get CM9 Booted first then think about fixing bugs etc. Plus, Most of the people are ready to sacrifice 1 sim to get a Working CM on their MTK Device
TheDemiGod said:
People make their own device tree's also! Instead of consuming that Nothing other than CM9 is possible instead help or GTFO! We will make it possible one day I believe!
@varun.chitre15: The Github Organization is ready! I already forked a few repo's! So, Start Working
---------- Post added at 12:21 PM ---------- Previous post was at 12:13 PM ----------
Nopes! I am not making a CM Kernel instead directly building CM9! The Prebuilt Kernel will boot CM9! Though.... @DanceOff was also working to get CM10.1 Booting :cyclops: Now, That he knows about already available CM9 Sources we could get CM9 Booted first then think about fixing bugs etc. Plus, Most of the people are ready to sacrifice 1 sim to get a Working CM on their MTK Device
Click to expand...
Click to collapse
Mate, hold your horses you don't get to use abusing slangs and expect help from anybody...
If you are interested then dive into what you think is possible and do it, there is no harm in expecting better!
Its time to united whole developers... support and help cyanogen dev., instead of developing so-called ROMs..(everything is same features... so boared)
Skyrazor said:
Mate, hold your horses you don't get to use abusing slangs and expect help from anybody...
If you are interested then dive into what you think is possible and do it, there is no harm in expecting better!
Click to expand...
Click to collapse
Dude dont spam this thread also. Y u always discourages dev or other people in other thread and u started this **** here too. Can't u be positive. Don't start with ur ego attitude here too. Keep the thread clean.
NO OFFENSE
skdmech94 said:
Dude dont spam this thread also. Y u always discourages dev or other people in other thread and u started this **** here too. Can't u be positive. Don't start with ur ego attitude here too. Keep the thread clean.
NO OFFENSE
Click to expand...
Click to collapse
None taken!
But I am not the one using slangs GTF***O
Hi Everyone,
CyanogenMOD would be an awesome accomplishment for these devices. Please try to stay on topic and not engage in petty disagreements. It is incredibly easy for a community effort to get derailed or fall apart. Remember, if you see something you don't like or disagree with, you can always ignore it or report it.
Thanks!
@TheDemiGod
yeah I was working on it, but then i abandoned the project because they already have a wonderful rom which i dont need to mention
TheDemiGod said:
Most of the people are ready to sacrifice 1 sim to get a Working CM on their MTK Device
Click to expand...
Click to collapse
Count me in for that sim sacrifice! All the best for ur work :thumbup:
This might help guys:
http://www.modaco.com/topic/355903-devrom81-cyanogenmod-10-android-412/
Ak****banta said:
This might help guys:
http://www.modaco.com/topic/355903-devrom81-cyanogenmod-10-android-412/
Click to expand...
Click to collapse
FYI: ZTE Blade is not a mediatek device :angry: Don't spam!
DEVS See This: (N00B's Not Allowed)
We can kang libs from Stock ICS Rom We first have to get it booting! Bug fixes will be given importance later :cyclops
yeah. i have used zte blade. it is not a mediatek device. no use of it
Sent from my Micromax A110
DanceOff said:
@TheDemiGod
yeah I was working on it, but then i abandoned the project because they already have a wonderful rom which i dont need to mention
Click to expand...
Click to collapse
@DanceOff u can do it !!
u r a true dev unlike other (i don't want to mention name everyone knows !)pls continue ur work !
Respect developers. Dont compare ..
Sent from my Micromax A110
Well I am still working upon this matter in the background. Somehow I messed up my build environment and god knows why, my recovery builds aren't booting as seen on the thread even though my device trees are untouched. Will be starting cleanly once I finish my exams on 16 May.
And regarding CyanogenMod, I have made a pretty good progress here. I have been studying the android ICS sources since they were discovered. Till now I have succeeded to frontport the MTK Gemini support, FEATUREOPTION builder, MTK GPS, MTK Camera HAL to the AOSP 4.2. But all of them are untested because I don't have the device,everyone knows. For this purpose I am going to buy the upcoming Xperia C3, which upon using as a medium for testing I can do this stuff a bit faster which will be beneficial to all MTK devices throughout. I have more than 30 commit patchsets lying on my machine which I will outsource soon.
I will suggest to use AOSP as base for these experiments because its always good to understand the pure upstream code. Once we have done noticable progress here, we can diff and merge them in projects like CM.
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.
Hello everybody,
Here is a custom cm13 port for the Oppo f1f, it is unofficial and unsupported as far as I'm aware.
Thanks go out to uberlaggydarwin for doing all the work on the F1f so far.
(Edit: I can't post links on new account. Pm me for link)
So far bugs are many including no sim card working.
We all need to get together and test and develop for this device and not leave it to one person. Make sure you all thank BrinlyAus aka Uberlaggydarwin for his dev efforts so far.
r3ndr4g said:
Hello everybody,
Here is a custom cm13 port for the Oppo f1f, it is unofficial and unsupported as far as I'm aware.
Thanks go out to uberlaggydarwin for doing all the work on the F1f so far.
(Edit: I can't post links on new account. Pm me for link)
So far bugs are many including no sim card working.
We all need to get together and test and develop for this device and not leave it to one person. Make sure you all thank BrinlyAus aka Uberlaggydarwin for his dev efforts so far.
Click to expand...
Click to collapse
I'll be starting to build cm13 for f1f next week. I'll be using @uberlaggydarwin work as a starting point so again thanks to him. I have already had a quick look and don't think it will take to much to get it usable, so hopefully I'll have a build up pretty quick.
r3ndr4g said:
Hello everybody,
Here is a custom cm13 port for the Oppo f1f, it is unofficial and unsupported as far as I'm aware.
Thanks go out to uberlaggydarwin for doing all the work on the F1f so far.
(Edit: I can't post links on new account. Pm me for link)
So far bugs are many including no sim card working.
We all need to get together and test and develop for this device and not leave it to one person. Make sure you all thank BrinlyAus aka Uberlaggydarwin for his dev efforts so far.
Click to expand...
Click to collapse
I appreciate your enthusiasm but I'd rather you not post my work here yet. It still needs some work and I'm busy doing a rebase..
Thanxx a lot, you guys are osm i am nt a developer but ill surely suport by testing out the builds u release
Anxious!!
I cant wait until the first build comes out! Willing to test anything beta.
OMG i just loaded this onto the phone, wow this is everything the F1F should be!
Sadly the Simcard isnt working at the moment but Awesome work to all involved especially uberlaggydarwin
If you really want a taste of a working marshmallow I suggest you try the Project Spectrum Beta:
http://www.oppomobile.vn/forum/t/rom-beta-6-0-cho-oppo-f1-kem-root.24792/
I haven't tested it but I have read the bugs are minors.
yes project spectrum beta v1.0 is worth the try m usin it on my phone installed it todaih itself, very minor bugs, me no dveloper . the bug i noticed is 1) black border at bottom of snapchat app (resolution issue maybe) , and sometimes SD card doesnt detect ( reboot fixes it easily) others thngs just fine
How to install this spectrum beta rom... Should we change also from stock recovery to twrp ?
I suppose that it doesn't include color os ?
Thanks
DekkerP6 said:
If you really want a taste of a working marshmallow I suggest you try the Project Spectrum Beta:
http://www.oppomobile.vn/forum/t/rom-beta-6-0-cho-oppo-f1-kem-root.24792/
I haven't tested it but I have read the bugs are minors.
Click to expand...
Click to collapse
This isn't helpful.
[email protected] said:
yes project spectrum beta v1.0 is worth the try m usin it on my phone installed it todaih itself, very minor bugs, me no dveloper . the bug i noticed is 1) black border at bottom of snapchat app (resolution issue maybe) , and sometimes SD card doesnt detect ( reboot fixes it easily) others thngs just fine
Click to expand...
Click to collapse
Mchasard said:
How to install this spectrum beta rom... Should we change also from stock recovery to twrp ?
I suppose that it doesn't include color os ?
Thanks
Click to expand...
Click to collapse
Wouldn't it be a good idea to a make a new Project Spectrum thread and put your comments there?
uberlaggydarwin said:
Wouldn't it be a good idea to a make a new Project Spectrum thread and put your comments there?
Click to expand...
Click to collapse
Sorry for polluting this topic, I agree. But since I haven't tried it myself I was not going to make the topic and I though that making aware the people that were so impatient about a marshmallow rom about it could help.
WE ARE ALL OPPO F1f !!
You Are right, We all need to get together and test and develop for this device and not leave it to one person, it's an amazing smartphone with a powerful abilities ... .
aaitzaouit said:
You Are right, We all need to get together and test and develop for this device and not leave it to one person, it's an amazing smartphone with a powerful abilities ... .
Click to expand...
Click to collapse
True. I am trying to assist with cm13. But in the mean time I did cm12.1 build, and apart from WiFi and camera not working everything else I tried works great. Better than ColourOS, so if I can fix those it will be my daily driver untill we get cm13.
MiniBlu said:
True. I am trying to assist with cm13. But in the mean time I did cm12.1 build, and apart from WiFi and camera not working everything else I tried works great. Better than ColourOS, so if I can fix those it will be my daily driver untill we get cm13.
Click to expand...
Click to collapse
Hey how do u make cyanogen builds fr our device? any link to refer regardin d steps?
thanks and infos
MiniBlu said:
True. I am trying to assist with cm13. But in the mean time I did cm12.1 build, and apart from WiFi and camera not working everything else I tried works great. Better than ColourOS, so if I can fix those it will be my daily driver untill we get cm13.
Click to expand...
Click to collapse
Thank you miniBlu for your efforts, personnaly I've tried Android M 6.0.1 based Project spectrum beta on my Oppo F1f, and it was sooo desapointed by the springboards, and SIM cards management.. Still waiting for better.
Keep going bro !!
Thread closed. Please do not post ROMs without links or without the author's permission.
Nathan
Forum Moderator
First question does Osprey's hardware support Android O ?
Prob does but we'll prob not be able to have some features
Osprey's hardware didn't supported android N too but we got it with custom rom... I think this will happened with android O too
Our device is in list to get los 15 ie. android O
androidbaba said:
Our device is in list to get los 15 ie. android O
Click to expand...
Click to collapse
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
adityak1303 said:
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
Click to expand...
Click to collapse
Just for fyi, lineageosdownloads.com is not the official site (download links are redirected to actual linageos.org (org, not com)). So information they give cannot be verified unless the official linageos blog posts something about it.
It's still a long way. Source code hasn't been out yet. After AOSP code is pushed, linageos team will work on it, but considering the limited resources (unlike CyanogenMod), it can take a while. After the base is ready, then devs will focus on building device specific images and fix bugs. Only then android o will be roaster ready. Other derivative ROMs will take more time obviously.
We can't be sure if 8.0 will be fully compatible with our device. We don't have official Nougat kernel sources and proprietary blobs (AFAIK), also from what I've observed so far, the farther apart the last official firmware and target firmware are, the harder it is to keep a ROM unmodified and yet stable & functional.
Our device shouldn't die that easy though, as newer Moto devices with similar hardware as osprey and Merlin have been released.
Broadcasted from Zeta Reticuli
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Hopefully we get O, and hopefully O comes default with the pixel nav because redacting that would take effort thats not worth it now that nexus is dead .
Nikos dima said:
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Click to expand...
Click to collapse
Our device does support Nougat, it is evident by the presence of custom ROMs (and even a stock port). The only reason we didn't get a OTA was because the company didn't provide us. The Moto ROM and these custom ROMs all are based on AOSP code.( Technically, if the company released the full source of their ROM and features, then we could build stock ROMs too)
And yes, you are right, it may take a little while but eventually we should see the ROMs coming
But the absence of latest device specific proprietary stuff and official kernel sources forces devs to look for other branches to fill the gaps and get newer thingies working. In some places it's not possible to implement a certain feature and an older feature is modded to make it work, for example before the official marshmallow OTA was out, we already got marshmallow ROMs but it had some hacky workarounds for radio (I don't know if it was updated after that), same goes for early Nougat when camera was becoming a problem. The camera is still not perfect (check linageos thread), working correctly on some apps and glitching on others. Newer software, newer challenges.
But codes are not exactly like food though, mixture of old and new ones is not always bad. But the blobs and drivers sometime give headache
Broadcasted from Zeta Reticuli
Have faith on our awsome developer we will surely have android O
Well, Android Oreo is out. I really hope that Osprey will get it soon.
https://source.android.com/devices/architecture/treble
according to this website,
"With Treble, a new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework—without any additional work required from the silicon manufacturers"
Does this mean if someone gets Lineage OS 15 or OTA of Stock Android 8.0, they will receive all the updates from google from security patch to new Android versions (If the hardware is capable of running that version obviously!)?
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
If that so, Manufacturers can just update all the devices which theoretically can run android O , it will be a onetime work, after that it'll be easy to update the devices
That would be amazing. Let's wait for a developer opinion.
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
android1111 said:
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
Click to expand...
Click to collapse
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
adityak1303 said:
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
Click to expand...
Click to collapse
Wow.. nice to hear this.. dude how do you know about this
rahul9999 said:
Wow.. nice to hear this.. dude how do you know about this
Click to expand...
Click to collapse
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
adityak1303 said:
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
Click to expand...
Click to collapse
Thanks For the information
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Abhishek17599 said:
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Click to expand...
Click to collapse
Hello,
There is no confirmation yet about this from official maintainer
Yes it should be get as Osprey already successfully booted it.. but don't ask for ETA
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
GuyInDogSuit said:
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
Click to expand...
Click to collapse
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
I wouldn't mind even if the best ROM available is a 6.0 Marshmallow one. Anything that gives AOSP on a stable base for the Fire HD10 is going to be awesome.
DragonFire1024 said:
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
They will likely need some patches to work with newer versions, but it's a good start I'd say.
It's the most recent version amazon has published.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Sent from my MotoG3 using XDA Labs
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
The one I have and provided is a source to 7.0. looks nicely stocked.
Sent from my MotoG3 using XDA Labs
bibikalka said:
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
Click to expand...
Click to collapse
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
I have fixed the upload, please use amonet-suez-v1.1.1.zip
DragonFire1024 said:
The one I have and provided is a source to 7.0. looks nicely stocked.
Click to expand...
Click to collapse
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
k4y0z said:
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
I have fixed the upload, please use amonet-suez-v1.1.1.zip
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
Click to expand...
Click to collapse
I'll provide a link in a few. Trying your fix now.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Rortiz2 said:
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Click to expand...
Click to collapse
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
bibikalka said:
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
Click to expand...
Click to collapse
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
This is great news! I am eagerly awaiting more info about this AOSP ROM
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
ffstudios said:
This is great news! I am eagerly awaiting more info about this AOSP ROM
Click to expand...
Click to collapse
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
bibikalka said:
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
Click to expand...
Click to collapse
If my testing on ROMs caused my brick, we have to be careful. I've been testing and flashing test ROMs for months now and never bricked like this. I think I may know what happened and if I'm right, I'm not sure what effect if any this will have on flashing a rom. According to the fstab.mt8173 file in the root directory, the partitions we flash for a rom, aren't part of the EMMC: data, system, cache are all ext4. All other partitions are however EMMC. So if I recall correctly, I did list the system as EMMC in the build script, but did intend to remove it. I made a last minute adjustment to the script and didn't change that part though.
https://forum.xda-developers.com/showpost.php?p=78542898&postcount=618
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
I too am willing to test. Just let me know and I'll be sure to wear my best testing pants. [emoji41]
Sent from my SM-G9650/DS running stang5litre Pie ROM
AOSP ROM TEST 1 (suez)
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: Removed
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Click to expand...
Click to collapse
Sounds good to me. Won't have a chance till later this afternoon/evening to give it a whirl, but when I do I'll definitely share my results and any information that may be useful. Thank you!
Sent from my SM-G9650/DS running stang5litre Pie ROM
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
...
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Click to expand...
Click to collapse
Which AOSP version is this? Could you try that Oreo Lineage stuff from @wangyiling at some point as well?
One of these days we'll have a ROM developer and a tester within the same person Too bad we've lost @DragonFire1024 since his tablet got bricked