[Help] Sim not detecting on my compiled rom - Moto G 2015 Q&A, Help & Troubleshooting

HELP ME !!!
I'm new to ROM development.
Compiled AOSiP 6.2 ROM for Motorola Moto G 2015(osprey)
But after flashing Sim card not detecting. About Section shows Baseband to Unknown and IMEI also not showing.
Restored TWRP backup of old ROM and everything working, again flashed AOSiP ROM and same No Sim Problem.
Also Camera app shows blank screen but Pic click working (I think it's a kernel Bug)(SOLVED)
Though every other things working fine(like wifi)
Help me in solving these bugs.
Here is the link of file: https://drive.google.com/open?id=0B2QocKy9AyYVOEVUMlM2eHNDUmc
I'm also attaching all source link (may be i'm using wrong source)
Device Tree: https://github.com/AOSiP-Devices/device_motorola_osprey/tree/nougat
MSM Device Tree: https://github.com/AOSiP-Devices/device_motorola_msm8916-common/tree/nougat
Vendor: https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-14.1 (only msm8916-common & osprey folder )
Kernel: https://github.com/desaishivam26/android_kernel_motorola_msm8916/tree/cm-14.1

nikhilpal2705 said:
HELP ME !!!
I'm new to ROM development.
Compiled AOSiP 6.2 ROM for Motorola Moto G 2015(osprey)
But after flashing Sim card not detecting. About Section shows Baseband to Unknown and IMEI also not showing.
Restored TWRP backup of old ROM and everything working, again flashed AOSiP ROM and same No Sim Problem.
Also Camera app shows blank screen but Pic click working (I think it's a kernel Bug)(SOLVED)
Though every other things working fine(like wifi)
Help me in solving these bugs.
Here is the link of file: https://drive.google.com/open?id=0B2QocKy9AyYVOEVUMlM2eHNDUmc
I'm also attaching all source link (may be i'm using wrong source)
Device Tree: https://github.com/AOSiP-Devices/device_motorola_osprey/tree/nougat
MSM Device Tree: https://github.com/AOSiP-Devices/device_motorola_msm8916-common/tree/nougat
Vendor: https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-14.1 (only msm8916-common & osprey folder )
Kernel: https://github.com/desaishivam26/android_kernel_motorola_msm8916/tree/cm-14.1
Click to expand...
Click to collapse
Contact @ishubhamsingh on xda or telegram
EDIT: @ishubhamsingh says you are using wrong device trees he has advice to use aosp extended device trees as it and aosip both based on jdc
Sent from my Moto G 2015 using XDA Labs

Thanks ? it's now working by using aex device tree.

nikhilpal2705 said:
Thanks ? it's now working by using aex device tree.
Click to expand...
Click to collapse
Yes I know I am using it
Thanks for compiling
Sent from my Moto G 2015 using XDA Labs

Ye thanks! I was having the same issue until I switched to the AEX Osprey tree (I wasn't using the same trees as OP)

Related

[M.A.D.] [ROM] [6.0.1] Unofficial CyanogenMod 13 - Elephone Vowney Lite

CyanogenMod 13 is a free, community built distribution of Android 6.0.1 (Marshmallow) which greatly extends the capabilities of your phone.
This is the unofficial build of CM 13 for Elephone Vowney Lite made by the M.A.D. team.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation Instructions:
Download rom from here: https://www.facebook.com/MediatekAndroidDevelopers/
OR from xda DevDB (DOWNLOAD Tab)
Download Gapps from OpenGapps: http://opengapps.org/, choose ARM and Android 6.0
boot to recovery
wipe data if you are not coming from CM13.0 already
install rom and gapps
Reboot
XDA:DevDB Information
Unofficial CyanogenMod 13 - Elephone Vowney Lite, ROM for all devices (see above for details)
Contributors
fire855, superdragonpt, DerTeufel1980
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock 5.1
Based On: CyanogenMod
Version Information
Status: Stable
Created 2016-08-23
Last Updated 2016-08-26
Reserved
Minimal F.A.Q
Q: After ROM boot up, I'm getting SetUP wizard errors / other Gapps FC / Black screen on first boot, why ?
A: On marshmallow based Roms, you need to flash ROM and gapps at the same time
TWRP even allows you to flash multiple .zip files
Q: Why no Mediatek Engineering Menu?
A: Its Mediatek proprietary, ugly , not needed on our builds.
Relevant features used on Mediatek E. Menu have been ported to our builds already using aosp / our implementations ( Sensors calibration , Band Mode, etc)
Q: App "x" is not working, why?
A: First make sure the app works under Marshmallow
Q: Something wrong with my Bluetooth, can't connect /pair with my "x" device , car-BT
A: Bluetooth should be backwards compatible , some OEMs don't also follow some guidelines , surely can be improved.
Post your BT model, Car model and year to help us out determining compatibility issues
Nice job!
what is guide to port this to other device working also by mt6795 bro ?
Thanks team M.A.D we need for mt6580 lp kernel
Bencoderus said:
Thanks team M.A.D we need for mt6580
Click to expand...
Click to collapse
Doogee X5 (mt6580) got a CM build from us.
- The M.A.D. team -
Thanks MAD team and FIRE
Pls we need cm13 for mt6580 lp kernel 3.10.72 for Walton primo rm2mini and the likes... Please help us out
@fire855 sir, is the device tree for Dogee x5 from the M.A.D team use stock untouched prebuilt kernel? if yes, then can we use this device tree as a refernce for compiling cm 13 for mt6582 lp kernel?? Thanks...
dark heart said:
@fire855 sir, is the device tree for Dogee x5 from the M.A.D team use stock untouched prebuilt kernel? if yes, then can we use this device tree as a refernce for compiling cm 13 for mt6582 lp kernel?? Thanks...
Click to expand...
Click to collapse
Yes, I'm using stock prebuilt kernel on doogee. But it's a MM (3.18) kernel and the device tree is made for the MM kernel. You can still use it as base but you also need to do changes.
- The M.A.D. team -
fire855 said:
Yes, I'm using stock prebuilt kernel on doogee. But it's a MM (3.18) kernel and the device tree is made for the MM kernel. You can still use it as base but you also need to do changes.
- The M.A.D. team -
Click to expand...
Click to collapse
sir, I am pretty much sure about changing blobs and ramdisk. But I am concerned about sepolicy changes. do I need to update those as well? this device tree don't have mediatekril we used to use for kk and lp kernel. So, how can we mtk ril?
This is no support thread for other devices and platforms
And surely NOT a porting q&a thread.
Thanks
Iam ported this ROM to my device with same CPU but settings sometimes flicking with black color is this issue from porting the ROM or this happene also in vowney lite ??
Thank you very much for Rom . Only a couple of modifications would ask .. 1 - Camara only 13 MP (21 MP Stock ) .No slow motion recording . 2nd - Light notification does not work ( in Stock , loading, messages, missed calls , low battery )
Hi, can you Port this ROM on Xiaomi Redmi Note 2? This will help a lot all maintainers of this phone(or even of all mt6795 devices) like @lokjianming @danielpinto8zz6 @bemolx @vova.vafin etc.
@fire855,
C O G R A T U L A T I O N S !!
A Nice Job !!
Could you. rom update:
- The camera only 13 Mpx without SlowMotion.
- The notification light stops working.
- It does not work well in 4G mode.
- You can not change the internal memory to SD.
- Waking up the screen with fingerprint is not possible.
It would be great !!!
llopbal
@fire855, thanx for the ROM. Works much better than stock. Just one question - is it possible to make LED notification work? (talking about Vowney Lite).
Agree with llopbal
1. The camera only 13 Mpx instead of 21 Mpx
2. The notification light stops working. This's very sad.
others problems not so important.
BR, akadimka
First of all, thanks for that great ROM! We really need it.
Question... If I backup my current /system/lib/hw/camera.mt6795.so and /system/lib/hw/libcam* and replace it on the new ROM, would the camera work on full resolution (21.5MP)? What else should I do?
I'd like to add camera specs if it's any help:
Back/Primary: imx230mipiraw (21.5 MP Sensor Sony IMX 230 Exmor RS)
Front/Secondary: ov8858mipiraw
Thanks again!
Llopbal said:
@fire855,
C O G R A T U L A T I O N S !!
A Nice Job !!
Could you. rom update:
- The camera only 13 Mpx without SlowMotion.
- The notification light stops working.
- It does not work well in 4G mode.
- You can not change the internal memory to SD.
- Waking up the screen with fingerprint is not possible.
It would be great !!!
llopbal
Click to expand...
Click to collapse
1. Slow motion is a proprietary feature from mtk. I will look into the mpx issue. Very busy currently.
2. Can someone try to replace lights.mt6795.so with the stock lights blob?
3. What doesn't work well with 4G?
4. You can use your sdcard as second internal storage. But you can't switch your internal storage and sdcard.
5. I missed to add off screen detection. I will look into it.
- The M.A.D. team -
Elepone vowney Lite CM13 by @fire855 (M.A.D. Team)
fire855 said:
1. Slow motion is a proprietary feature from mtk. I will look into the mpx issue. Very busy currently.
2. Can someone try to replace lights.mt6795.so with the stock lights blob?
3. What doesn't work well with 4G?
4. You can use your sdcard as second internal storage. But you can't switch your internal storage and sdcard.
5. I missed to add off screen detection. I will look into it.
- The M.A.D. team -
Click to expand...
Click to collapse
@fire855 / The MAD Team
- On 4G, maybe there was not enough coverage in my test.
- The LED notification is not important at this time.
- So will remain pending update:
- The camera 21 MPX
- Add the detection screen with fingerprint.
* Again thanks for a nice job !!!
:good:
Llopbal.

[Completed] Can You Port CM 12.1 To Device With Kernel Version 3.10 Without Device Tree File?

I have a BLU Energy X 2 running the MT6580 chipset, with kernel version 3.10. I was looking into porting CyanogenMod12.1, however there is no device tree, as the kernel version is not updated enough. Is it still possible to port the ROM? I also don't have the vendor tree, how would I get that?
Thanks, Nate
NateDev473 said:
I have a BLU Energy X 2 running the MT6580 chipset, with kernel version 3.10. I was looking into porting CyanogenMod12.1, however there is no device tree, as the kernel version is not updated enough. Is it still possible to port the ROM? I also don't have the vendor tree, how would I get that?
Thanks, Nate
Click to expand...
Click to collapse
Hello,
You need to generate the blobs for the vendor. Also you need a working device tree and kernel for it.
You can refer here Guide to Port MTK Roms for more information.
Regards
Vatsal,
Forum Moderator.

[ROM][TREBLE][MI-A1] COMPLETE LIST OF A/B GSIs [DOWNLOAD LINKS]

Here is a Collection of A/B GSIs ,ie, system.img links for treblized mi a1:
1. AICP-mordiford by @AndroPlus: https://drive.google.com/open?id=1LtPNR6R4dxJslXFIjpF9FhyfEfhBTCOa
2. AOSIP by @noobstyle1337: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/aosip-t3792494
3. AOSP 8.1 by @phhusson: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
4. AOSP Extended by @AryanPatidar : https://androidfilehost.com/?w=files&flid=271118
5. AOKP by @sixohtew : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/aokp-t3772379
6. CosmicOS by @noobstyle1337: https://forum.xda-developers.com/pr...ment/cosmic-ospulsar8-1-0201805243-2-t3794806
7. dotOS by @kubersharma : https://forum.xda-developers.com/p...ment/official-droidontime-dotos-2-x-t3794338
8. Omni by @sooti : https://drive.google.com/file/d/12j76r3XVr0SFodFx2qhltVjueaI8Hz0h/view?usp=drivesdk
9. Resurrection Remix by @phhusson : https://forum.xda-developers.com/p...opment/resurrection-remix-phh-treble-t3767688
10. LineageOS 15.1 by @phhusson : https://forum.xda-developers.com/p...vice-development/lineage-phh-treble-t3767690
11. Pixel Experience by @jhenrique09 : https://forum.xda-developers.com/p...-development/8-1-0-pixel-experience-t3796011
Instructions to enable Treble on Mi A1:
https://forum.xda-developers.com/mi-a1/how-to/treble-stock-to-treble-everything-to-t3793734
Credits:
All the mentioned developers for their work on treble devices
@phhusson for his contributions towards treble device development
@CosmicDan @ghpranav for their hard work on enabling Treble for Mi A1
@brajesh.sharma87 for his support
@yshalsager for compiling and maintaining the list on GitHub
Links to respective threads added
Update:
AOSIP is working now
Created on: 2018-06-04
Last Updated on: 2018-06-04
In AICP the Google Assistant doesn't work for me and AOSIP doesn't boot.
The Omni ROM link is dead
AnnePunk said:
In AICP the Google Assistant doesn't work for me and AOSIP doesn't boot.
The Omni ROM link is dead
Click to expand...
Click to collapse
Try flashing different GAPPS if google assistant doesn't work.
Did you download the correct img got AOSIP?
if yes, flash the img again, boot to twrp and perform a factory reset and try rebooting the phone
Also flash magisk and try if it doesn't work again.
Thanks for letting me knw that omni link is dead, will update as soon as dev updates the link
You probably should link to the threads too, so people can know about updates and see if there are any issues or special information about the GSI.
wmfanboy25 said:
Did you download the correct img got AOSIP?
if yes, flash the img again, boot to twrp and perform a factory reset and try rebooting the phone
Also flash magisk and try if it doesn't work again.
Click to expand...
Click to collapse
AOSIP isn't compatible with the Mi A1 at the moment
jigs4wkiller said:
AOSIP isn't compatible with the Mi A1 at the moment
Click to expand...
Click to collapse
Didn't know that
It says phh-lineage isn't working, but it's working fine for me
@wmfanboy25
That omni link from sooti is dead. Is there any xda thread he announced it?
CosmicDan said:
You probably should link to the threads too, so people can know about updates and see if there are any issues or special information about the GSI.
Click to expand...
Click to collapse
Agreed. Will update the links to the respective threads
varben said:
@wmfanboy25
That omni link from sooti is dead. Is there any xda thread he announced it?
Click to expand...
Click to collapse
Nope there is no thread yet. We can try asking him to post one
Thanks, @wmfanboy25, for your contribution
Does anyone know if that "A/B" AEX 5.7 Rom is working?
Don't know why it has an "xz" extension, instead of "zip".
Thanks again!
Treble build for Mi A1!!!
Instructions to flash GSI will also be most welcomed like which vendor,boot,kernel and Gapps
I Installed DotOs and it booted but after flashing nano gapps I get error google play services stop repeatedly,Tried to clear cache in gp services but it did not fix the problem.

[ROM][8.1.0][THEA] Unofficial LineageOS 15.1 [ALPHA][UNIFIED]

WARNING: Broken RIL. THIS ROM IS NOT A DAILY DRIVER AND IS TOTALLY OBSOLETE. EMERGENCY CALLS ARE NOT POSSIBLE.
Use gothicVI's ROM which includes a working RIL and the latest O security patches.
If you want a daily driver Oreo ROM, flash LuK1337's LineageOS 15.1, which is the only alternative right now.
Because our thea deserves to be loved too!
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restores the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This is an unofficial LineageOS 15.1 build made from LuK1337 et al's source trees for the Motorola Moto G 2014 LTE, synced to the latest Lineage codebase with some changes. I have to fix a lot of stuff to make it a stable ROM and therefore development help is wanted and welcome. This ROM is a work in progress and it's purpose is to serve as a reliable base to port over other ROMs to the device, or just to be a smooth daily driver for Lineage fans.
Working: Those features are stable.
Boot
Sensors
WiFi
Bluetooth
Media
Camera: Photos
Status & Flash LED
Touchscreen
Broken: Feedback is wanted.
Video Recording
RIL: telephone calls, SIM, SMS, VoLTE, mobile data, emergency calling.
SELinux is permissive for now.
How to report issues:
Please follow this template. If you don't follow this template you will be ignored. Also feedback MUST be posted here and not as private messages unless I explicitly say so. And don't report issues that already appear here.
Code:
What is your...
* Phone model (XT107*):
* ROM version (0x**):
* GApps version if you use them:
* Xposed or Magisk:
* Kernel:
logcat:
* Link to Pastebin or similar
dmesg:
* Link to Pastebin or similar
Download:
Get the ROM here
Changelog:
Code:
## 20180619: release 0x01 ##
* Initial release.
## 20180627: release 0x02 ##
* Built against OPM6.171019.030.B1
* Fixed vendor image mismatch errors
XDA:DevDB Information
LineageOS 15.1 for Moto G 2014 LTE , ROM for the Moto G 2014 LTE
Contributors
Wattsensi, the Moto G 2014 Dev Team
Source Code: http://github.com/motog2014devteam
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Bootloader 0x4821 or higher, unlocked.
Based On: LineageOS
Version Information
Status: Alpha
Current Stable Version: 0x02
Created 2018-06-20
Last Updated 2018-06-28
Any progress?
Hi @Wattsensi how did you fix the vendor image mismatch? There was no push to the repo you list as sources.
---------- Post added at 18:39 ---------- Previous post was at 18:38 ----------
Hi @Wattsensi how did you fix the vendor image mismatch? There was no push to the repo you list as sources.
gothicVI said:
Hi @Wattsensi how did you fix the vendor image mismatch? There was no push to the repo you list as sources.
---------- Post added at 18:39 ---------- Previous post was at 18:38 ----------
Hi @Wattsensi how did you fix the vendor image mismatch? There was no push to the repo you list as sources.
Click to expand...
Click to collapse
Oh, hi there. I didn't know that there was somebody still interested in developing for this device. I switched to a Huawei P9 my father gave me, but I still have my Thea saved. That said I tried everything but I couldn't get the RIL to work.
I fixed the vendor image problems by getting the vendor image strings in a terminal emulator in the phone, then going back to my PC and changing the init_thea.cpp file in the init folder of the thea device tree. Check RenanQueiroz' titan device tree, go to init_titan.cpp and get a guidance. I made a dual_override() function too to save space.
I am not a ROM cook though. Just a builder.
Wattsensi said:
Oh, hi there. I didn't know that there was somebody still interested in developing for this device. I switched to a Huawei P9 my father gave me, but I still have my Thea saved. That said I tried everything but I couldn't get the RIL to work.
I fixed the vendor image problems by getting the vendor image strings in a terminal emulator in the phone, then going back to my PC and changing the init_thea.cpp file in the init folder of the thea device tree. Check RenanQueiroz' titan device tree, go to init_titan.cpp and get a guidance. I made a dual_override() function too to save space.
I am not a ROM cook though. Just a builder.
Click to expand...
Click to collapse
Would you mind sharing the file you changed?
I'm just building myself - not much experience in Android development (yet).
Gesendet von meinem Moto G (5) Plus mit Tapatalk
gothicVI said:
Would you mind sharing the file you changed?
I'm just building myself - not much experience in Android development (yet).
Gesendet von meinem Moto G (5) Plus mit Tapatalk
Click to expand...
Click to collapse
Please share with us a build with basic functions working
Eddy Stark said:
Please share with us a build with basic functions working
Click to expand...
Click to collapse
Here you go. Any feedback on what is working and what not would be highly appreciated!
This ROM is officially discontinued. Please close the thread mods.

Development [ROM][UNOFFICIAL] LineageOS 17.1 for Lenovo PHAB Plus

Important information:
This thread is for LineageOS 17.1 opensource builds for Lenovo PHAB Plus, marketed as Lenovo PHAB Plus by Lenovo. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
Camera (except front camera)
Installation:
If you are on the stock OS, you will first need a custom recovery.
If you are coming from stock or other ROMs, you need to do a factory reset.
As always, make sure to backup before installing this ROM.
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Changelog:
Changes for phoenix
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to TipzTeam
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@nicknitewolf, @TipzTeam, Lineage Team
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N/A
Based On: LineageOS
About Video Recording
If you really need to use a 2015 device to record videos, you may use Camera Go to do so.
Reserved.
i cant flash gapps it says cant mount /system
i am using your twrp latest version opengapps gives error 10 and the one you provided says /system cannot mount
it worked it said installed on gapps now lineageos is booting!
lineageos stuck on booting whyyyY!!!!!!!!!!!!!!!!!
upddate still not booting after so long just stuck on lineage os animation
click factory reset in twrp still same thing !!!!!!!!!!!!!!!!!!!!
New Update!
20210813
Changelog:
Updated EGL blobs to LA.BR.1.2.9_rb1.18
Correct GPS week rollover timestamps (from Jason Laskowski)
Update SEPolicy allows
Copy prebuilt qcril.db files
Download
New Update!
20210815
Changelog:
Fix incorrect Bluetooth MAC address
Update fluence props
Download
Hello, thank you for creating a custom ROM. My wife uses Lenovo Phab Plus with stock ROM 5.1.1, but it is laggy even after a factory reset. How is the smoothness of this custom ROM? Can it be used as a daily driver? (Sorry, I cannot just try it because it is not mine)
zainullahk123411 said:
i am using your twrp latest version opengapps gives error 10 and the one you provided says /system cannot mount
Click to expand...
Click to collapse
i have the exact same problem! cant have both the rom installed and gapps! if i install gapps the recommned one i will get stuck on boot and cant install from open gapps either! i have a lineage os now without gapps! plz help
BABAKPERSIA said:
i have the exact same problem! cant have both the rom installed and gapps! if i install gapps the recommned one i will get stuck on boot and cant install from open gapps either! i have a lineage os now without gapps! plz help
Click to expand...
Click to collapse
i fouund a fix in magisk install this module https://github.com/wacko1805/MagiskGapps
tttservice said:
Hello, thank you for creating a custom ROM. My wife uses Lenovo Phab Plus with stock ROM 5.1.1, but it is laggy even after a factory reset. How is the smoothness of this custom ROM? Can it be used as a daily driver? (Sorry, I cannot just try it because it is not mine)
Click to expand...
Click to collapse
Sorry for the late reply, everything works fine except for Camera, GPS seems to be funky. It is pretty smooth, much better than the stock ROM.
tipzrickycheung said:
Important information:
This thread is for LineageOS 17.1 opensource builds for Lenovo PHAB Plus, marketed as Lenovo PHAB Plus by Lenovo. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
Camera
Installation:
If you are on the stock OS, you will first need a custom recovery.
If you are coming from stock or other ROMs, you need to do a factory reset.
As always, make sure to backup before installing this ROM.
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Changelog:
Changes for phoenix
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to TipzTeam
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@nicknitewolf, @TipzTeam, Lineage Team
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N/A
Based On: LineageOS
Click to expand...
Click to collapse
any fix for camera? only thing that is bugging me right now
Zainullahk1234 said:
any fix for camera? only thing that is bugging me right now
Click to expand...
Click to collapse
I haven't had the opportunity to work on my phoenix since I don't have a battery.
New Update!
20220305
Changelog:
Latest security patches
Download
tipzrickycheung said:
Important information:
This thread is for LineageOS 17.1 opensource builds for Lenovo PHAB Plus, marketed as Lenovo PHAB Plus by Lenovo. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
Camera
Installation:
If you are on the stock OS, you will first need a custom recovery.
If you are coming from stock or other ROMs, you need to do a factory reset.
As always, make sure to backup before installing this ROM.
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Changelog:
Changes for phoenix
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to TipzTeam
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@nicknitewolf, @TipzTeam, Lineage Team
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N/A
Based On: LineageOS
Click to expand...
Click to collapse
could you try making the device treble supported like people have done for other devices?
cause in a gsi its possible camera might work
Zainullahk1234 said:
could you try making the device treble supported like people have done for other devices?
cause in a gsi its possible camera might work
Click to expand...
Click to collapse
No it won't, it needs the vendor implementation to work too.

Categories

Resources