Cyanogen Mod Axon 7 Commit - ZTE Axon 7 Questions & Answers

Hello community...
So I used to have an OPO until the Axon 7 came out and jumped ship. However, from time to time my buddies and I still discuss what's new with the OPO. The other night my buddy sent me this picture. As you can see it's a commit log for the Bacon [OPO] version of CM 13 but right in the middle there's a commit that reads "Add pictures resolution for Axon 7." Does anyone here know what this means? Is the dev for CM13 on Bacon also working on the Axon 7?
I know Udev and a couple other devs here have been working on an unofficial CM version for the Axon 7 and I was surprised to see that commit on an official CM log.
The address is https://review.cyanogenmod.org/#/c/164039 in case someone wants to check it out for themselves.
Edit: Sorry if I posted in the wrong section but please do feel free to move to appropriate section.

It only means Its a commit for snap (CM Camera) by c457 to make the Snap Camera work on the "work-in-progress" CyanogenMod for the Axon-7.
Android sources work with repositories. Just because its listed in Bacons change logs (BTW cmxlog is not an official CM log website) doesn't mean the dev is working on the Axon7.
It's just a change for the snap camera.
If you click on the link you will be taken to gerrit which shows the author and the commiter.

Related

Omni for i9505

I found it strange there is no thread for Omni in development forum? There was a thread but abandoned since there was no maintainer for the device. But since then unified builds happened, and i9505 /jfltexx has been mentioned as a device supported by the updater script:
https://github.com/omnirom/android_device_samsung_jflte/blob/android-4.4/BoardConfig.mk#L129
Is here anyone who uses the ROM as a daily driver, or anyone who has checked it in the last time, to share experience with us? I'm downloading it right now, and will try to find time tomorrow to check it.
The reason is that the thread is under 'Unified' subforum, where also other AOSP ROMs like Octo, Nameless, PA are. Strange CM isn't there too...

[NOTICE][HELP] Porting MiUI 7 to the Moto X 2013

Hello,
I'm happy to announce that I'm working on a port of MiUI 7 for our Motorola Moto X 2013 ("ghost").
Some people might already know that someone already made this port which of course it's true, you can see it here. The problem is that this ROM is no longer available for download and it had issues like it wasn't using the latest CyanogenMod 11 ROM and the Stagefright bug wasn't patched. Furthermore, the original author seems to be no longer present on XDA.
I'm using this tutorial in order to make the port. After a lot of days of tries and restart, I managed to compile a fully working and updated CyanogenMod 11 ROM that can be used as a base and I've started to fix some of the rejects caused by the PatchROM.
In order for this port to see the light, I would like some contributions from the community, I'm not an Android expert, it's my first port and I have other projects and real life stuff that gets in my way. So if you wish to help me, all you need to do is clone this repository, fix the rejects (one commit per reject please) and make a pull request. Of course, you will be in the credits.
Thank you for your interest and the support in this project.
Link?
I have been doing the same with lollipop CM
MIUI lollipop

Need help wrapping my head around building AOSP for HTC One M9

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!

Build LineageOS verizon note 4

I want to try and build my own form of LINEAGEOS for my verizon note 4. I am looking for a unicorn, which seems to be ""roomservice.xml"". Can ANYONE please share or direct me in the directon to get this. I am working of this thread https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885. I have posted an asked for help and even to @hsbadr.
See my repos on my GitHub profile. Link to my build folder in my signature below.

Obsolete

..
Reserved.....
Hello... 'been using this phone for over a year now here is a clean build.prop from 6055B variant!
Also i'd like to help somehow, but I don't know how... I have zero Android dev experience (not really... last phone I ever modded was OT-918D *eons* ago, so it might as well be zero) but i'd be happy to test-drive anything as long as UI & RILd works.
I'll chime-in on Telegram too :good:
PizzaG said:
This will be the release thread for LineageOS 14.1
***LineageOS 14.1 Test Build for the 6055K is now live on Telegram with Download Link. Bluetooth and Camera aren't working yet***
If you want it to install on other variants, you will need to modify the installer script inside the zip. I'm not going to take the time to modify every Test Build to support every model. I'm running it on 6055U. If you do want to run it on another variant of 6055 and it's not installing, contact me on Telegram and I'll run you through how to modify the installer script to install on your device.
If you have anything to offer or just want to chat, you can find us here: https://t.me/Idol4Homies
Please don't report bugs here, we'd much rather you report any issues on our Telegram Group where the Dev will be able to see. I''m helping where I can and modifying little things but LimitedPython is doing the bulk of the Developing for this phone, please show your support and stop by the group to chat and say thanks.
5-13-2019- LOS 14.1 is currently booting to ADB but not posting yet. Sorting out some GPU issues and hopefully it'll be fully booting sometime this week.
5-14-2019- LOS 14.1 booting to OS. LTE Data and phone service works. Audio and most everything else is still broken currently but being worked on. If anybody has a clue what they are doing or how to help move this along to a public release, please join us on Telegram. I have a test image for people who can lend a hand but I'm not releasing anything publicly yet.
5-17-2019- LOS 14.1 working great so far. The only things not working at this point are Camera and BlueTooth, which hopefully will both be working very soon. I'll release a test build in the next day or so, so others can test. I'll be releasing TWRP and LOS 14.1 for the 6055U and 6055K variants. If you have another model you want supported from the 6055 line, PM me.
5-19-2019- This will work on every 6055 Model guys. That means 6055K, 6055B, 6055U, 6055R and 6055P will all work with this and future roms. No need to worry about "Bricking", as I have released Alcatel Stock Flashing software which will bring most, if not all the Alcatel Qualcomm devices back from the dead.
5-20-2019- Bluetooth fixed and working
Click to expand...
Click to collapse
I tried to go to your Telegram link for the LOS 14.1 6055U download, but it won't work. Idk why... Could you post a link to it here or something? Thanks in advance!
**scratch that I found it on the donate page**
Hello everyone.
I possess an Alcatel Idol 4 6055K, I would be very much interested in installing Lineage OS on this smartphone but I can't find any other source on the web on how to do it except for this thread.
I understand it should be possible with a release you're posting on Telegram, but if I click on the link it seems I can't acceed to the group.
Do you have any advice on how to try this OS on this marvellous phone?
So, no chance to ever see Lineage released for Alcatel Idol 4?
museovivo said:
So, no chance to ever see Lineage released for Alcatel Idol 4?
Click to expand...
Click to collapse
Yes, 14.1 has been out for a while now and 15.1 works too, I was told that a few days ago by the Dev. Come vist us on Telegram: https://t.me/Android_General_Chat
The Dev is in there and should be able to provide you download links for Los 14.1 or 15.1
We also still need donations as the Dev has lost his Idol 4 and needs a new one to continue making Idol 4 Fully Treble

Categories

Resources