Just wondering about if this rom is available for my Galaxy J7
I will give you some questions back:
1. What is the exact devicename (codename) ? We use the devicenames for building (eg. shamu for Nexus 6) and I don't know what exactly every device on the word has what codename, so I need this to answer your question
2. Is your device supported by cm-12.1 ?
My Device information
Baseband Version is J700HXXU1AOJ5
Kernel Version is 3.10.61-755431
Build Number is LMY48BJ700HXXU1AOJ5
SE for Android Status is SEPF_SM-J700H_5.1.1_0018
And about cm 12.1 my device is not supported
I writed all these things because i don't know my device devicename(codename)
http://www.gsmarena.com/samsung_galaxy_j7
J700h/f/*
No CM builds for it, no xda device forum for it.
Ferenczy68 said:
http://www.gsmarena.com/samsung_galaxy_j7
J700h/f/*
No CM builds for it, no xda device forum for it.
Click to expand...
Click to collapse
Sorry, aber if CM doesn't build, we will not be able to, too because we rely on their device and hardware trees.
We are only a very small team and don't have the capacity to develope complete new device trees
Cm12 is being developed for samsung j7h&f models follow this thread
http://forum.xda-developers.com/general/help/samsung-galaxy-j7-custom-rom-t3185983/post62524400
For more information
Well it's okay
I can wait for your rom :good:
Martin_Ro said:
Sorry, aber if CM doesn't build, we will not be able to, too because we rely on their device and hardware trees.
We are only a very small team and don't have the capacity to develope complete new device trees
Click to expand...
Click to collapse
Well, I have time for that
I would be awesome
Related
Hi everyone! I've been wondering if there will be ever a port of cm or any other aosp rom to our m9+. I think sense doesnt do this device justice.
I read in some other thread that this wasnt posible due to the fact that mediatek had not release the source code-, then i stumble on to this
http://forum.xda-developers.com/meizu-mx/orig-development/helio-x10-kernel-source-code-released-t3225886
I dont know if this has anything to do with our device. But it would be nice to have an aosp ROM.
eoscylla said:
Hi everyone! I've been wondering if there will be ever a port of cm or any other aosp rom to our m9+. I think sense doesnt do this device justice.
I read in some other thread that this wasnt posible due to the fact that mediatek had not release the source code-, then i stumble on to this
http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886
I dont know if this has anything to do with our device. But it would be nice to have an aosp ROM.
Click to expand...
Click to collapse
But with this source code I would like prefer to have many features in the kernel development instead of aosp rom development.
This may be a stupid question, but I'm a new guy around here and I have something I'd like to know:
Why is every? Cyanogenmod version for Galaxy S3 Neo Unofficial ? Is it because the Cyanogenmod team is not making them or because it has some things unstable or something like that?
P.S: Sorry if you see some language mistakes, English isn't my main language and I'm trying my best
Because cyanogenmod team is not making them for galaxy s3 neo
DeivisBiceps said:
Because cyanogenmod team is not making them for galaxy s3 neo
Click to expand...
Click to collapse
Thank you very much for the response
To be official it must meet some requirements like for instance to have all functions that are orginaly represent on & working to have a good developer as a maintainer behind it (as CM don't actually provide you anything nor they culd). When all request are met then request can be failed for making it official.
We will probably be able to do that in some time from now as Nikola did a second restart of the work on kernel(as we were not satisfied), we managed to identify BMC NFC chip & driver for it so hopefully we will have it working. That is if we menage to do it all right & if he wants to be maintainer.
Zola III said:
To be official it must meet some requirements like for instance to have all functions that are orginaly represent on & working to have a good developer as a maintainer behind it (as CM don't actually provide you anything nor they culd). When all request are met then request can be failed for making it official.
We will probably be able to do that in some time from now as Nikola did a second restart of the work on kernel(as we were not satisfied), we managed to identify BMC NFC chip & driver for it so hopefully we will have it working. That is if we menage to do it all right & if he wants to be maintainer.
Click to expand...
Click to collapse
Thank you very much for taking your time explaining it to me
Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique
Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.
So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?
I can't help you, but that is a very good idea! Hope you can solve this issue.
Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk
Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).
Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it
Any news @vivremetrique ? Or did you drop the project?
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand
can't help, but my hopes are so high for this one!
Hello agin !
Did someone spoke that what I found on Google ?
Someone already started working on Lineage OS 14.1 to bring it to Axon 7
Link: http://www.cyanogenmods.org/forums/topic/zte-axon-7-lineage-14-1-nougat-7-1-rom/
Someone know that guy ?
Oh man my axon is coming in the mail this would be awesome if it works
Sent from my Le X522 using Tapatalk
Check here
://forum.xda-developers.com/axon-7/help/14-1-afh-t3529552
Looks very interesting, thanks!
The build is very experimental and nowhere near ready. Some bugs include, Sound, Camera, Wifi however it boots. I dont have a cyanogenmod account so i didn't post it there
What Gapps are you guys using for this?
reV17 said:
The build is very experimental and nowhere near ready. Some bugs include, Sound, Camera, Wifi however it boots. I dont have a cyanogenmod account so i didn't post it there
Click to expand...
Click to collapse
definitely not bad at all for a first build. I really can't wait for a fully working version! Thanks!
reV17 said:
The build is very experimental and nowhere near ready. Some bugs include, Sound, Camera, Wifi however it boots. I dont have a cyanogenmod account so i didn't post it there
Click to expand...
Click to collapse
Can you post your tree or sources? Any way we could help?
lordpipa said:
Can you post your tree or sources? Any way we could help?
Click to expand...
Click to collapse
You seem to be under the impression that I built that. I did not.
reV17 said:
The build is very experimental and nowhere near ready. Some bugs include, Sound, Camera, Wifi however it boots. I dont have a cyanogenmod account so i didn't post it there
Click to expand...
Click to collapse
Gives that impression. Either way, whoever did, it might be helpful.
reV17 said:
You seem to be under the impression that I built that. I did not.
Click to expand...
Click to collapse
ZTE said that they were going to do everything they could to help officially support Cyanogenmod on the Axon 7. Well, that project is now called Lineage OS. It would make me feel better if we could get an official response from ZTE. Otherwise, I'm just going to assume that they're just like every other Chinese manufacturer, and only care about releasing new phones instead of supporting older ones (I'm looking at you Huawei).
T3kB0i said:
ZTE said that they were going to do everything they could to help officially support Cyanogenmod on the Axon 7. Well, that project is now called Lineage OS. It would make me feel better if we could get an official response from ZTE. Otherwise, I'm just going to assume that they're just like every other Chinese manufacturer, and only care about releasing new phones instead of supporting older ones (I'm looking at you Huawei).
Click to expand...
Click to collapse
From what I recall, the agreement ZTE made was with an employee of Cyanogen. That person (who provided backing & assistance to the Cyanogenmod project) has since left the company, and Cyanogen Inc. has gotten out of the whole "community OS" aspect of the company, and closed Cyanogenmod up. The community that operates Lineage has no sort of ties to ZTE, nor business ties to another company (like Cyanogenmod was to Cyanogen Inc.).
ZTE did, however, send some files to the volunteer community team working on CM13. iirc, it wasn't all that helpful, but it was something at least...
LineageOS will officially support the Axon 7. Now only an early alpha is available with the typical problems of early versions, however an official support means a commitment. I contacted them to let them know that the ROM in the official page was for another device. They fixed it after a few hours with the LineageOS 14.1 v2016.12.30, they also told me that there will be more news on this device very soon.
Fingers crossed that very soon means this week. I can't believe the amount of love the one+ receives over our A7. We have dual speakers & an SD slot!!!
Oki said:
LineageOS will officially support the Axon 7. Now only an early alpha is available with the typical problems of early versions, however an official support means a commitment. I contacted them to let them know that the ROM in the official page was for another device. They fixed it after a few hours with the LineageOS 14.1 v2016.12.30, they also told me that there will be more news on this device very soon.
Click to expand...
Click to collapse
I doubt ZTE has anything to do with LineageOS.
bornlivedie said:
I doubt ZTE has anything to do with LineageOS.
Click to expand...
Click to collapse
They don't...our Lineage support was done by a team member not even by me. Support for 14.1 is not true though. I'm the only person at the moment who has 14.1 in development. Although ZTE has nothing to do with Lineage support they have provided me code to help bringup N development.
Nice to hear that they are helping.
bornlivedie said:
I doubt ZTE has anything to do with LineageOS.
Click to expand...
Click to collapse
LineageOS officially supporting the ZTE Axon 7 doesn't mean ZTE is supporting LineageOS. There are dozens of devices supported by LineageOS without official support from their manufacturers. However the success of Nougat for this device will depend on the release of the kernel code by ZTE to everyone.
Unjustified Dev said:
They don't...our Lineage support was done by a team member not even by me. Support for 14.1 is not true though. I'm the only person at the moment who has 14.1 in development. Although ZTE has nothing to do with Lineage support they have provided me code to help bringup N development.
Click to expand...
Click to collapse
These are good, very good news. If ZTE is willing to share their code, even before the official release, custom ROMs will have a much quicker development time, less buggy, and more people will purchase this excellent device. ZTE seems to be learning the lesson.
I am looking forward to the development for this device and the ZTE Axon 7 mini.
Hope there will be a lot of alternative ROMs ... :good:
Thanks in advance to @Unjustified Dev
ChickNrippR said:
I am looking forward to the development for this device and the ZTE Axon 7 mini.
Hope there will be a lot of alternative ROMs ... :good:
Thanks in advance to @Unjustified Dev
Click to expand...
Click to collapse
They is a ROM in dev section already. LinageOS 14.1. Released yesterday.
Hi everyone, I decided to develop LineageOS 17.1 and OrangeFox recovery for Nokia 6 for personal use. Anyone interested?
EDIT:
Hi guys, I apologize for my absence but I have been busy with my life and work. The project is going well, I have removed several errors due to the source code of the device
LineageOS build will be 18 with Android 11, get ready! I need your support to continue
sure, why not I was waiting to someone to make custom rom (A10+) for this device for so long. glad that your developing this for us. thank you very much! goodluck~ ?
Yeah. We are waiting for custom roms for this device. Good luck. Happy compiling. ?
I'd love to have android 10 on my Nokia 6! Are you targeting the 2017 Nokia 6, or the newer 6.1? I'd love to help but I don't know much about android roms/rom porting. I have a TA-1033 as my daily driver, so I could test builds on that (if they don't brick my phone :^) ). Good luck!
yes of course we're interested with your initiative! looking forward on your progress & good luck!
Count me in!
Nokia 6 TA-1025 (2017) and I'm all in!
Count me in too, can't wait for the first beta version, im using Nokia 7 TA-1021.
Of course, OP! In the EOL of device, what would be better than a custom ROM support. Good luck in your development, OP.
P.S.: I suggest checking pirrat25's PLE device tree to start. They got things already working there.
biffidusactiregularis said:
Hi everyone, I decided to develop LineageOS 17.1 and OrangeFox recovery for Nokia 6 for personal use. Anyone interested?
Click to expand...
Click to collapse
Yes, Waiting for custom ROM
Yes, very much interested. Looking forward to your custom ROM! Please keep us posted always.
Hello, during the lockdown I've tried to port Lineage OS 17.1 to our device, unfortunately after the build process I wasn't able to make it boot successfully.
The source trees that I used are on Github.
Device tree: https://github.com/sguerrini97/android_device_nokia_PLE
Vendor tree: https://github.com/sguerrini97/android_vendor_nokia_PLE
Kernel tree: https://github.com/sguerrini97/android_kernel_nokia_msm8937
This was my first attempt ever to port a custom ROM on a device so I may have done some simple mistakes that some more experienced developer can spot
I cannot dedicate too much time on this project right now but I will be glad to help if somebody wants to keep this going.
biffidusactiregularis said:
Hi everyone, I decided to develop LineageOS 17.1 and OrangeFox recovery for Nokia 6 for personal use. Anyone interested?
Click to expand...
Click to collapse
This made my day. Thanks in advance for your work.
I saw a forum post where an old version of LOS was ported to Nokia 6.
http s:/ /4pda. ru/forum/index.php?showtopic=839094&st=4260#entry79721383
Remove the extra space(s) from the link. I'm not yet allowed to post external links.
Google Translate is your friend here
xaedoplay.modder.xda said:
Of course, OP! In the EOL of device, what would be better than a custom ROM support. Good luck in your development, OP.
P.S.: I suggest checking pirrat25's PLE device tree to start. They got things already working there.
Click to expand...
Click to collapse
Does it supports Android Pie.
Sharashchandra said:
Does it supports Android Pie.
Click to expand...
Click to collapse
its lineage 15.1 device tree
nokia ta-1033 için uzun süredir custom rom bekliyorum. Bu çalışma için çok teşekkür ederim sabırsızlıkla bekliyorum
jojojobani said:
I saw a forum post where an old version of LOS was ported to Nokia 6.
http s:/ /4pda. ru/forum/index.php?showtopic=839094&st=4260#entry79721383
Remove the extra space(s) from the link. I'm not yet allowed to post external links.
Google Translate is your friend here
Click to expand...
Click to collapse
FYI: 4PDA links are prohibited on XDA forums
If I'm being honest, the Nokia 6 2017 is one of the best mid range phones out there and it is sad that only one developer is taking interest in this phone. I think it's because of the robust bootloader and more. Yes, Nokia messed up so bad on the Android Pie update. WE NEED MORE DEVELOPERS ON THIS DEVELOPMENT.
Any updates about project?