Related
LineageOS 14.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* 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.
*/
Prerequisites
Bootloader unlock > HERE
Recovery twrp > squid2 or sevenmaxs
What works
RIL (dual sim, volte)
WIFI
Tethering
Camera
Bluetooth
Sensors
MTP
Sound
Fingerprint
NFC
MotoActions
- - SELinux: enforcing
Todo
Fix "Enable on-screen nav-bar" toggling option.
Download
https://www.androidfilehost.com/?w=files&flid=251047 AFH LOS7 Files
https://opengapps.org/ OpenGApps - Choose ARM/7.1/PICO or NANO
Source
Device: https://github.com/kayesk/android_device_motorola_montana
Vendor: https://github.com/kayesk/android_vendor_motorola_montana
Branch: cm-14.1
How to install the rom ?
Copy the rom to your G5S.
Restart in recovery (squid or Sevenmaxs)
Take a backup of existing ROM.
Wipe clean (Cache, Data, Dalvik/ART, System)
Install ROM.
Make a wipe cache.
Reboot System.
Initial load would take time.
Contributions :
@GoldeneyeS2 for fixing OEM bloatware, NFC and releasetools script.
THANKS TO :
@squid2 for twrp
@SevenMaxs for twrp
All other users who provided support, valuable suggestions and productive comments.
Report bugs with proper logcat details.
Device is unrooted. Root using Magisk works.
Thanks
KS
Nice,happy new year!
customs on g5s incomming
Thanks, HAPPY NEW YEAR
good job my friend and thank you for your work
Happy new year .
Video recording - FIXED
FIXED another issue with MTP.
NFC selinux rules are added - SOMEONE PLEASE VERIFY IF IT WORKS.
NEW BUILD: lineage-14.1-20171231_060004-UNOFFICIAL-montana.zip
Link: Same as in topic.
Thanks
KS
Awesome work! Works fine, no bugs until right now, BUT
one thing about the moto devices that i love, is the moto actions and the moto display, how to keep them?
Have some flashable lib from stock? Can you Add or teach how to use it? I need one hand navigation on the fingerprint sensor.
Thx
Great work...i was trying for this but failed...now u can expect Oreo ROMs too
kalyansundhar said:
Video recording - FIXED
FIXED another issue with MTP.
NFC selinux rules are added - SOMEONE PLEASE VERIFY IF IT WORKS.
NEW BUILD: lineage-14.1-20171231_060004-UNOFFICIAL-montana.zip
Link: Same as in topic.
Thanks
KS
Click to expand...
Click to collapse
can u please push kernel sources...i can help fixing moto acions
Happy new year.
NFC is not working. I don't see it in the settings.
Tomorrow more time....
Anyone drop screenshots
govind1233 said:
Anyone drop screenshots
Click to expand...
Click to collapse
Tomorrow I will do. But its just lineage 14.1.
The ROM is based on the stock version. Some services are still from Motorola.
Following bug I found:
The first time you watch a full screen video. You will get a message about it. Portrait modes there is no problem but in landscape you will see a weird thing happening with the message and the video.
Thanks so much for developping a rom for this device, because not a lot a developper make something for this device contrary to the dev arround the moto g5s plus. And happy new year.
govind1233 said:
Anyone drop screenshots
Click to expand...
Click to collapse
Done.
GoldeneyeS2 said:
Tomorrow I will do. But its just lineage 14.1.
The ROM is based on the stock version. Some services are still from Motorola.
Following bug I found:
The first time you watch a full screen video. You will get a message about it. Portrait modes there is no problem but in landscape you will see a weird thing happening with the message and the video.
Click to expand...
Click to collapse
Thank you very much for making a rom for the Moto G5S. Are you aware of the bug in the developer options and Moto Actios does not work? Sorry for any mistake in English.
Doug.97 said:
Thank you very much for making a rom for the Moto G5S. Are you aware of the bug in the developer options and Moto Actios does not work? Sorry for any mistake in English.
Click to expand...
Click to collapse
Yes. I am aware of the issues you mentioned.
@govind1233, I have published kernel code as well https://github.com/kayesk/android_kernel_motorola_msm8937.
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
Also I have one confusion. If I add MotoActions apk to code, will it interfere with CMActions?
Thanks
KS
Please release kernel sources
kalyansundhar said:
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
KS
Click to expand...
Click to collapse
I have the XT1794 with NFC. I dont see the nfc in settings.
I also try to get it working.
Maybe its something with settings.apk??? Did you also copy that from the G5???
@kalyansundhar
Are now working building or still copying and pasting? you can better upload your system.img and boot.img to github(extract).
kalyansundhar said:
Yes. I am aware of the issues you mentioned.
@govind1233, I have published kernel code as well https://github.com/kayesk/android_kernel_motorola_msm8937.
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
Also I have one confusion. If I add MotoActions apk to code, will it interfere with CMActions?
Thanks
KS
Click to expand...
Click to collapse
Thanks bro
---------- Post added at 04:35 PM ---------- Previous post was at 03:35 PM ----------
kalyansundhar said:
Yes. I am aware of the issues you mentioned.
@govind1233, I have published kernel code as well https://github.com/kayesk/android_kernel_motorola_msm8937.
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
Also I have one confusion. If I add MotoActions apk to code, will it interfere with CMActions?
Thanks
KS
Click to expand...
Click to collapse
For Moto actions to work u need proper commits for cmactions
GoldeneyeS2 said:
I have the XT1794 with NFC. I dont see the nfc in settings.
I also try to get it working.
Maybe its something with settings.apk??? Did you also copy that from the G5???
@kalyansundhar
Are now working building or still copying and pasting? you can better upload your system.img and boot.img to github(extract).
Click to expand...
Click to collapse
Well, I am doing little bit here and there with whatever limited experience I have.
My main concern now is my lack of understanding on how everything fits in the big picture. And without knowing it if I make some change that shouldn't be screwing up something which works fine.
I think it is better for me to stop here, so that good developers could take it further. Anyway the repositories are public.
I cannot push system.img to github because of file size limitation. File size is 900MB and allowed limit is 100MB.
I would share it in my onedrive account and publish the link.
Bugs so far:
1) Developer options - Getting selinux permission issue which is blocked by global rule. I don't know how to override a global rule.
2) Moto Actions - Not working.
3) NFC - Getting zygote error related to seapp_context.
Code:
01-02 21:32:58.857 1534 1593 E ActivityManager: android.util.Log$TerribleFailure: Removing process that hasn't been killed: ProcessRecord{ffc4c99 8487:com.android.nfc/1027}
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.util.Log.wtf(Log.java:295)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.util.Slog.wtfStack(Slog.java:98)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService.removeLruProcessLocked(ActivityManagerService.java:3419)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService.processStartTimedOutLocked(ActivityManagerService.java:6611)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService.-wrap13(ActivityManagerService.java)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService$MainHandler.handleMessage(ActivityManagerService.java:1895)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.os.Handler.dispatchMessage(Handler.java:102)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.os.Looper.loop(Looper.java:154)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.os.HandlerThread.run(HandlerThread.java:61)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.ServiceThread.run(ServiceThread.java:46)
01-02 21:32:58.872 8500 8500 E SELinux : seapp_context_lookup: No match for app with uid 1027, seinfo default, name com.android.nfc
01-02 21:32:58.873 8500 8500 E SELinux : selinux_android_setcontext: Error setting context for app with uid 1027, seinfo default: No such file or directory
01-02 21:32:58.873 8500 8500 E Zygote : selinux_android_setcontext(1027, 0, "default", "com.android.nfc") failed
01-02 21:32:58.873 8500 8500 F art : art/runtime/jni_internal.cc:492] JNI FatalError called: frameworks/base/core/jni/com_android_internal_os_Zygote.cpp:631: selinux_android_setcontext failed
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] Runtime aborting...
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] Aborting thread:
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] "main" prio=5 tid=1 Native
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | group="" sCount=0 dsCount=0 obj=0x73784268 self=0xa5a05400
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | sysTid=555 nice=0 cgrp=default sched=0/0 handle=0xa86de534
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | state=? schedstat=( 0 0 0 ) utm=0 stm=0 core=0 HZ=100
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | stack=0xbe70f000-0xbe711000 stackSize=8MB
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | held mutexes= "abort lock"
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] kernel: (couldn't read /proc/self/task/555/stack)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] native: (backtrace::Unwind failed for thread 555: Thread doesn't exist)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.Zygote.nativeForkAndSpecialize(Native method)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.Zygote.forkAndSpecialize(Zygote.java:95)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.ZygoteConnection.runOnce(ZygoteConnection.java:225)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.ZygoteInit.runSelectLoop(ZygoteInit.java:853)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:775)
Looks like all 3 issues boils down to selinux, file contexts, uevent permissions.
Thanks,
KS
GoldeneyeS2 said:
I have the XT1794 with NFC. I dont see the nfc in settings.
I also try to get it working.
Maybe its something with settings.apk??? Did you also copy that from the G5???
@kalyansundhar
Are now working building or still copying and pasting? you can better upload your system.img and boot.img to github(extract).
Click to expand...
Click to collapse
Uploaded boot-20180102.img and system-20180102.img to onedrive. https://1drv.ms/f/s!Ahq68S0B7zYZjmVhmIHwvYGoz3gq. Please find it within build_images subdirectory.
Thanks
KS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://img.xda-cdn.com/TNu3mia_OH11Njq-YZ8f1paMBGE=/https%3A%2F%2Fraw.githubuser
content.com%2FBootleggersROM%2FExtraStuff%2Fpasta%2Fthreadfiles%2F01-intro.png
Bootleggers ROM is an aftermarket firmware based on AOSP with some patches and fixes from LineageOS and various other projects. The idea is to bring custom features and some of the most useful apps on your device, with the goal of Making you feel like 家.
With an almost stable source, this ROM is also packed with some custom wallpapers (avaliable on ShishuWalls), ringtones, fonts, and themes to bring to your device into a more fresh look and give you always a good experience.
Also, we got our Telegram Group to talk about the ROM, share some love, ideas or even have fun with !
ROM FeaturesQS Rows and Colums
Volume Keys: Wake up, skip tracks and switch according to rotation
Show song album cover, visualizer and battery info on Lockscreen
Power Menu Items
Battery LED light settings
Suspend Actions: Make your device disable GPS and switch to 2G when you're not using it
AppOps: Manage your apps permissions in an advanced way
Recent Styles: Dig the new Pie Quickstep recents, go back to the classic layout or use the Android Go layout
Network icons: Show or hide the cross, switch between 4G or LTE, use the classic icon layout before Pie or toggle roaming icon too!
Small things that are added but we put it here so we can make this list a bit bigger and impress some people
Show app package at the bottom of app info
Sort apps by size
StatusbarTuner: Set icons to show in statusbar
Network Traffic
Show/Hide QS Tiles titles
LockscreenTuner: Change left/right shortcuts
Double Tap to Sleep on QS
Screen recording added on powermenu
Snooze Headsup notifications by sliding the popup up
App icon on Toast Messages
Disable summary/suggestions on Settings app
Allow 5 Display sizes instead of 3
Night Light settings
Roboto Condensed as Default Font
GoBold Light as Lockscreen font
Screen off animation
Custom clock and date tweaks
Light/Dark/Black/Shishu Themes
Custom QS tile background
System Animations
Log it for all your logging emergencies (needs root) and also, a copy log from an app FC
Clock customizations
App data/wifi restriction
THANKS! * Shishu (For being there)
* Ground Zero ROMs Team
* AOSPExtended
* ABC ROMs
* NitrogenOS
* AICP
* DirtyUnicorns
* Lukas Koller (Camera Roll dev)
* fxckingdeathwish (for the amazing photos for wallpaper/headers)
* OmniROM
* CyanogenMod/LineageOS
* PixelExperience
* PureNexus
* merothh
* Resurrection Remix
* AOSiP
* CrDroid
* CypherOS
* PureKat
* theimpulson
* MatiHalperin
* Project Xtended
* Pixeldust Project
* AquariOS
* Alejandro Ponce (Quetzal/Calypso dev)
* PixysOS
* The Memedo Testers team
* Every maintainer who decided to give our project a shot
* You for your interest on our project
Downloads GoogleDrive
GApps:[ARM 64 9.0] OpenGapps
Device Sources: Device Tree
Vendor
Kernel Rom Source: Source
BOOTLEGGERS Information
R0M OS Version:9.X PIE
byhenriquetc
hey man,
how is it going the battery life and camera?
Safenet is working?
zebruno said:
hey man,
how is it going the battery life and camera?
Safenet is working?
Click to expand...
Click to collapse
since recently devs have been using the stock oreo base for building roms, which means the camera works pretty well. as for the battery life, pie has a new battery saving system which adapts to your phone, so at first your battery won't be good, but after a week or so it'll be ok
What is the difference of the other rom you upload?
Thanks
Cricamju said:
What is the difference of the other rom you upload?
Thanks
Click to expand...
Click to collapse
and it's official is this patch with jan é volte fixed
Good ROM , exlent , good baterry life e customization , thanks @HenriqueCt
What about camera and usb tethering?
freeZbies said:
What about camera and usb tethering?
Click to expand...
Click to collapse
the camera is usable is the usb to detect just enter the twrp they still n Silves
allanph said:
Good ROM , exlent , good baterry life e customization , thanks @HenriqueCt
Click to expand...
Click to collapse
Thanks =)
luffyhhuu said:
the camera is usable is the usb to detect just enter the twrp they still n Silves
Click to expand...
Click to collapse
Usb tethering hasn't anything to do with twrp, I think you didn't get my point.
About the camera I'd like to know how "usable" it is. Any bugs so far?
hey i have a question, although the 3 random boot animation feature is kinda neat, i dont like it, can i simply flash my own boot animation and use just that?
freeZbies said:
Usb tethering hasn't anything to do with twrp, I think you didn't get my point.
About the camera I'd like to know how "usable" it is. Any bugs so far?
Click to expand...
Click to collapse
camera seems to work fine for me, nothing much to complain about
If this rom is Oficial, why it isn´t on the bootleggers site?
Why this ROM supported no root?
Exanneon said:
camera seems to work fine for me, nothing much to complain about
Click to expand...
Click to collapse
Video recording doesn't- no error in stock Camera app but file is not saved. The same for Google Camera. MotoCamera can be installed but doesn't work- crash when taking a picture or when switching to video mode
EDIT:
OoenCamera reports camera error when trying to record a video
gen_scheisskopf said:
Video recording doesn't- no error in stock Camera app but file is not saved. The same for Google Camera. MotoCamera can be installed but doesn't work- crash when taking a picture or when switching to video mode
EDIT:
OoenCamera reports camera error when trying to record a video
Click to expand...
Click to collapse
surprisingly, it also doesnt work on footej. have any ideas on how to fix it?
Not yet, I didn't have time to dig in the issue yet.
But at least camera is usable in WhatsApp (both camera and we code scanning)
Edit:
Got logcat (attached) from Snap when recording a video. Unfortunately there are some quite serious (IMHO) errors:
Code:
01-13 14:45:22.927 27454 27454 W System.err: java.lang.IllegalArgumentException: Could not find tag for key 'org.quic.camera2.customhfrfps.info.CustomHFRFpsTable')
01-13 14:45:22.927 27454 27454 W System.err: at android.hardware.camera2.impl.CameraMetadataNative.nativeGetTagFromKeyLocal(Native Method)[...]
Panorama mode may not work also:
Code:
1-13 14:45:22.939 27454 27454 E PanoramaCapture: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/system/priv-app/Snap/Snap.apk"],nativeLibraryDirectories=[/system/priv-app/Snap/lib/arm64, /system/lib64, /system/vendor/lib64, /system/lib64, /system/vendor/lib64]]] couldn't find "libjni_panorama.so"
01-13 14:45:22.939 27454 27454 D ChromaflashFilter: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/system/priv-app/Snap/Snap.apk"],nativeLibraryDirectories=[/system/priv-app/Snap/lib/arm64, /system/lib64, /system/vendor/lib64, /system/lib64, /system/vendor/lib64]]] couldn't find "libjni_chromaflash.so"
01-13 14:45:22.940 27454 27454 D BlurbusterFilter: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/system/priv-app/Snap/Snap.apk"],nativeLibraryDirectories=[/system/priv-app/Snap/lib/arm64, /system/lib64, /system/vendor/lib64, /system/lib64, /system/vendor/lib64]]] couldn't find "libjni_blurbuster.so"
And it looks that Snap has only access to low resolution codecs:
Code:
01-13 14:45:22.957 27454 27454 W SnapCam_SettingsManager: HFR is not supported for this resolution java.lang.IllegalArgumentException: Size 1920x1080 does not support high speed video recording
01-13 14:45:22.966 27454 27454 E SnapCam_SettingsManager: Codec = 1, capabilities: mMinFrameWidth = 176 , mMinFrameHeight = 144 , mMaxFrameWidth = 352 , mMaxFrameHeight = 288
01-13 14:45:22.966 27454 27454 E SnapCam_SettingsManager: Codec = 3, capabilities: mMinFrameWidth = 176 , mMinFrameHeight = 144 , mMaxFrameWidth = 352 , mMaxFrameHeight = 288
And it seems that mp4 can't be created:
Code:
01-13 14:45:23.008 27454 27454 D SnapCam_CaptureModule: init
01-13 14:45:23.015 27454 27454 D SnapCam_SettingsManager: isZslSupported=true
01-13 14:45:23.023 27454 27454 D RenderScript HIDL Adaptation: IRenderScriptDevice::getService()
01-13 14:45:23.031 27454 27454 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-13 14:45:23.063 27454 27454 D RenderScript HIDL Adaptation: IRenderScriptDevice::getService() returned 0x7579743200
01-13 14:45:23.063 27454 27454 D RenderScript HIDL Adaptation: HIDL successfully loaded.
01-13 14:45:23.087 683 27240 W CameraSource: camera recording proxy is gone
01-13 14:45:23.088 683 2722 D MPEG4Writer: Video track stopping. Stop source
01-13 14:45:23.088 683 2722 D MPEG4Writer: Video track source stopping
01-13 14:45:23.089 683 27256 I MPEG4Writer: Received total/0-length (307/0) buffers and encoded 306 frames. - Audio
01-13 14:45:23.089 683 27256 I MPEG4Writer: Audio track drift time: 0 us
01-13 14:45:23.098 683 27253 E MPEG4Writer: The number of recorded samples is 0
01-13 14:45:23.099 683 27253 E MPEG4Writer: Dumping Video track's last 10 frames timestamp and frame type
01-13 14:45:23.099 683 27253 E MPEG4Writer:
01-13 14:45:23.099 683 27253 W MPEG4Writer: 0-duration samples found: 1
01-13 14:45:23.099 683 27253 W MPEG4Writer: 0-duration samples found: 1
01-13 14:45:23.099 683 27253 I MPEG4Writer: Received total/0-length (0/0) buffers and encoded 0 frames. - Video
01-13 14:45:23.102 27454 27454 I .lineageos.snap: type=1400 audit(0.0:28621): avc: denied { open } for uid=10043 path="/dev/kgsl-3d0" dev="tmpfs" ino=13063 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
It's ben a while since last time I dug into logcat, if I'm not right please correct me.
Full logcat from ~6sec video recording is attached
gen_scheisskopf said:
Not yet, I didn't have time to dig in the issue yet.
But at least camera is usable in WhatsApp (both camera and we code scanning)
Edit:
Got logcat (attached) from Snap when recording a video. Unfortunately there are some quite serious (IMHO) errors:
Panorama mode may not work also:
And it looks that Snap has only access to low resolution codecs:
And it seems that mp4 can't be created:
It's ben a while since last time I dug into logcat, if I'm not right please correct me.
Full logcat from ~6sec video recording is attached
Click to expand...
Click to collapse
Thanks
lucki1000 said:
Why this ROM supported no root?
Click to expand...
Click to collapse
support yes
Googuis said:
If this rom is Oficial, why it isn´t on the bootleggers site?
Click to expand...
Click to collapse
will still be
COSP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
Welcome to COSP, your new future Android Operating System.
Our goal is to have an Pixel-like android ROM that isn't spying on you and uses as few system space as possible. Also, we provide the option to go completely without GApps using MicroG support.
Why us?
We are focusing on stability and performance, having an debloated ROM is essential for that. Also, we want Users to decide what kind of Store they want to use, either F-Droid or the Play Store.
Also, we take User requests serious. To suggest something, contact us on telegram.
Features:
1) All systemUI tuning elements
2) An handy Network indicator
3) Charging Information
4) Lawnchair and Quickstep as default
5) Quick Settings mods
6) Signature spoofing
7) OP gestures
8) Navbar tuner
9) Rootless Substratum (with fixes to theme system correctly)
10) Screenshot/screenrecord tile
11) Advanced power menu
12) Double tap to sleep on statusbar
13) Option to disable quick settings/power menu on secure lockscreen
OTA Updating for official devices enables Users to get the newest version with ease.
DOWNLOADS:
COSP-190207-OFFICIAL-harpia.zip
MD5SUM: 5b906e96dd6de389838f86954894f0c3
Sources:
ROM Source: https://github.com/cosp-project/
Kernel Source code: https://github.com/Harpia-development/kernel_motorola_msm8916 (on branch pie_upstream_cust)
Device tree: harpia (on branch cosp_9) and common (on branch 9), using the following manifest.
facuarmo said:
COSP
Code:
**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
Welcome to COSP, your new future Android Operating System.
Our goal is to have an Pixel-like android ROM that isn't spying on you and uses as few system space as possible. Also, we provide the option to go completely without GApps using MicroG support.
Why us?
We are focusing on stability and performance, having an debloated ROM is essential for that. Also, we want Users to decide what kind of Store they want to use, either F-Droid or the Play Store.
Also, we take User requests serious. To suggest something, contact us on telegram.
Features:
1) All systemUI tuning elements
2) An handy Network indicator
3) Charging Information
4) Lawnchair and Quickstep as default
5) Quick Settings mods
6) Signature spoofing
7) OP gestures
8) Navbar tuner
9) Rootless Substratum (with fixes to theme system correctly)
10) Screenshot/screenrecord tile
11) Advanced power menu
12) Double tap to sleep on statusbar
13) Option to disable quick settings/power menu on secure lockscreen
OTA Updating for official devices enables Users to get the newest version with ease.
DOWNLOADS:
COSP-190207-OFFICIAL-harpia.zip
MD5SUM: 5b906e96dd6de389838f86954894f0c3
Sources:
ROM Source: https://github.com/cosp-project/
Kernel Source code: https://github.com/Harpia-development/kernel_motorola_msm8916 (on branch pie_upstream_cust)
Device tree: harpia (on branch cosp_9) and common (on branch 9), using the following manifest.
Click to expand...
Click to collapse
What Is working? Bugs?
Volte Is working?
Liked your work.
Nice rom.
I flashed magisk zip file several times still it's not showing in the app list
Moto_g4_play said:
Liked your work.
Nice rom.
I flashed magisk zip file several times still it's not showing in the app list
Click to expand...
Click to collapse
Install it once, reboot to system and after booting to system reboot again, it should appear.
Sent from my Redmi Note 5 using Tapatalk
Sakul1994 said:
What Is working? Bugs?
Volte Is working?
Click to expand...
Click to collapse
Everything is working. VoLTE isn't supported yet for this device on none of the ROMs because of source changes introduced in Pie that broke it. Some devs are working on it, while I can't, just because of the fact that my carrier hasn't implemented it yet.
Moto_g4_play said:
Liked your work.
Nice rom.
I flashed magisk zip file several times still it's not showing in the app list
Click to expand...
Click to collapse
I'm glad you like this ROM, although you might want to thank @edi194 a bit more about this since he's the owner of the project lol. I'm just a maintainer.
About rooting, that's a bug in Magisk. Simply unpack the Magisk zip and manually install magisk.apk from the common folder.
Moto_g4_play said:
Liked your work.
Nice rom.
I flashed magisk zip file several times still it's not showing in the app list
Click to expand...
Click to collapse
Install apk for that coz sometimes it shows bt if not try to install apk n download it from google
Thank you EDI194 and facuarmo for this ROM development and maintenance, thanks look.akash18 for the help.
Hi, after following the standard procedure to install this rom (wipe cache, system, dalvik, data), I found that the initial setup is broken if no gapps are installed, the Pixel setup crashes as soon as I hit Continue, I re-downloaded the rome to check if maybe my download was corrupt, had no luck, also checked with md5sum and the file was fine
Re-installing the rom and installing gapps before the first boot allows me to complete the initial setup
---------- Post added at 03:17 PM ---------- Previous post was at 03:00 PM ----------
Hi, I have encountered another *minor* bug, enabling triple tap zoom on accessibility settings disables any kind of input on the device, the power button still works, although the only thing that can be done is forcing the device to restart long-pressing the power button
I can confirm the device does not completely hangs, as animations going on in the screen are still displaying, and plugging an external mouse thru OTG moves the cursor (but clicking and pressing keys don't do anything)
steps to reproduce:
-Install rom with nano gapps package (from OpenGapps)
-finish initial setup
-enable triple tap zoom
-enjoy (??)
EDIT: I should clarify that only *enabling* triple tap zoom hangs the phone, after forcing the device to reboot, it works normally (and even triple tap zoom works)
---------- Post added at 04:13 PM ---------- Previous post was at 03:17 PM ----------
2ND UPDATE:
Well, seems like everything hangs, the rom is actually pretty cool and "smooth", but I've reinstalled it 3 times, only on the last try I was able to finish the initial setup, then it was all downhill, launching certain settings for the first time hang the phone for about 1 minute (example: opening mobile data settings, app permissions), trying to uninstall an app didn't work, and trying to force the uninstall thru adb froze the phone completely, although after a (forced) reboot, uninstalling apps seems to work correctly, it seems that doing *anything* for the first time hangs the phone, after trying to do something for the first time and rebooting (or letting the phone un-freeze itself, although that could take some serious time)
I'm (almost) pretty sure that this is not a problem with just my device/phone, as everything worked perfectly on past roms.
However, I'll continue to use this rom to see if it stops hanging, after the last forced reboot (after trying to uninstall an app), everything seems to be working perfectly
AngeelGod said:
Hi, after following the standard procedure to install this rom (wipe cache, system, dalvik, data), I found that the initial setup is broken if no gapps are installed, the Pixel setup crashes as soon as I hit Continue
Click to expand...
Click to collapse
That's something really strange, because rom doesn't have any "SetupWizard" or "Initial setup" included, if gapps not installed then you just boot up to home screen
Sent from my Redmi Note 5 using Tapatalk
It's awesome that my device can now run Android 9!
What works
Camera, including video recording
Phone calls
Mobile data (LTE), after adding my carrier's APN
SafetyNet passes out of the box
Bugs/issues I've faced (device-specific)
Updater crashes with
Code:
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.updates.models.Update.getDownload()' on a null object reference
at com.updates.fragments.OTAFragment$2.onResponse(OTAFragment.java:105)
at retrofit2.ExecutorCallAdapterFactory$ExecutorCallbackCall$1$1.run(ExecutorCallAdapterFactory.java:71)
Google's Sounds app crashes so I can't change ringtone or message tone (If you install Gapps don't install this!). It seems to be a graphics issue:
Relevant (think so) logcat output:
Code:
03-04 18:26:40.466 5081 5105 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 17:57:45.158 31215 32483 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8916.so from current namespace instead of sphal namespace.
03-04 18:26:40.486 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.492 5081 5114 I chatty : uid=10080(com.google.android.soundpicker) GLThread 1090 identical 44 lines
03-04 18:26:40.492 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.492 5081 5114 W GL2JNIView: creating OpenGL ES 2.0 context
03-04 18:26:40.492 5081 5114 E GL2JNIView: Before eglCreateContext 2: EGL error: 0x3004
03-04 18:26:40.501 5081 5114 W GL2JNIView: Returning a GLES 2 context
03-04 18:26:40.502 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.505 5081 5114 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8916.so from current namespace instead of sphal namespace.
03-04 18:26:40.517 5081 5114 I GL2 : all initialized 2
03-04 18:26:40.518 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.518 5081 5114 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
03-04 18:26:40.534 5081 5114 E Adreno-SC: <CPPErrorToInfoLog:852>: GLSL line 1: Error: #version number unsupported
03-04 18:26:40.538 5081 5114 E Adreno-SC: <CPPErrorToInfoLog:852>: GLSL line 1: Error: #version is followed by spurious tokens
03-04 18:26:40.542 5081 5114 E Adreno-SC: <CPPErrorToInfoLog:852>: GLSL line 1: Error: #version number unsupported
03-04 18:26:40.542 5081 5114 E Adreno-SC: <CPPErrorToInfoLog:852>: GLSL line 1: Error: #version is followed by spurious tokens
03-04 18:26:40.560 5081 5114 E AndroidRuntime: FATAL EXCEPTION: GLThread 1090
03-04 17:57:45.231 31215 32483 E AndroidRuntime: Process: com.google.android.soundpicker, PID: 31215
03-04 17:57:45.231 31215 32483 E AndroidRuntime: java.lang.RuntimeException: Vertex shader
03-04 17:57:45.231 31215 32483 E AndroidRuntime: OpenGL ES #version <number> is not supported.
03-04 17:57:45.231 31215 32483 E AndroidRuntime: ERROR: 0:1: '' : GLSL compile error: #version number unsupported
03-04 17:57:45.231 31215 32483 E AndroidRuntime: ERROR: 0:1: '' : GLSL compile error: #version is followed by spurious tokens
03-04 17:57:45.231 31215 32483 E AndroidRuntime: ERROR: 0:3: 'in' : Syntax error: syntax error
03-04 17:57:45.231 31215 32483 E AndroidRuntime: ERROR: 3 compilation errors. No code generated.
// ...
03-04 17:57:45.231 31215 32483 E AndroidRuntime: at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1555)
03-04 17:57:45.231 31215 32483 E AndroidRuntime: at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1270)
Sometimes my screen turns black (I'll update this when I'm able to reproduce it again when logging)
More bugs and feature requests (ROM-specific)
Icons on the notification shade are gray, they have no colors
There's no option to make the phone rotate too when it's upside down (this is included in LineageOS, not sure if the Pie one includes it)
There are no shortcuts in the lock screen to access Phone and Camera (this could be a device or Gapps bug)
Volume buttons adjust media volume all the time (Pie issue, an option to change this would be nice)
Updated ROM DL Link
Well I tried to post the updated ROM link since the first one is no longer active, but I'm a FNG, so...
Also, flashed most recent version along with 9.0 micro GAPPS. Phone kept restarting getting a little further each time. Now she's stuck on loading.
And now we're bootlooping again. Did the same with Pixel Experience 9.0. Seems I can only get Oreo to run.
Cookster128 said:
Well I tried to post the updated ROM link since the first one is no longer active, but I'm a FNG, so...
Also, flashed most recent version along with 9.0 micro GAPPS. Phone kept restarting getting a little further each time. Now she's stuck on loading.
And now we're bootlooping again. Did the same with Pixel Experience 9.0. Seems I can only get Oreo to run.
Click to expand...
Click to collapse
Same problem here
xMotoDA said:
[*] Sometimes my screen turns black (I'll update this when I'm able to reproduce it again when logging)
Click to expand...
Click to collapse
I've ran logcat just after the freeze with black screen (pressing Power doesn't turn on the screen):
https://ghostbin.com/paste/3etfc
https://ghostbin.com/paste/h6k3x
Another bug in this ROM is that every 2-4 boots Wi-Fi and mobile data don't work, and the phone gets stuck showing "Android is starting" after unlocking.
Any update on volte ?
Linus2 said:
Any update on volte ?
Click to expand...
Click to collapse
Apparently, the developer hasn't posted in a while
Still, can't you make calls without VoLTE (either using regular calls or your carrier's app)?
xMotoDA said:
Apparently, the developer hasn't posted in a while
Still, can't you make calls without VoLTE (either using regular calls or your carrier's app)?
Click to expand...
Click to collapse
NO unfortunately our carrier dosenot support calls without VoLTES CALLS are muted .
New update for harpia pushed
https://mirror.codebucket.de/cosp/harpia/COSP-190406-OFFICIAL-harpia.zip
https://mirror.codebucket.de/cosp/harpia/Changelog.txt
Hi! Obs.: I'm new in the forum, só, if i err something obvious, please, say it ,-,...
I've tested the ROM published and i loved how it's fast in boot. The problem related with boot and wifi looks not appearing more. This ROM was some personals and best performance. The camera isn't work. I rebooted 3 times and nothing. That's the unique error that i found.
I've switched so many ROM's, searching to find a ROM like these features.
The ROM is so much fluid and faster.
Good work!
w.rony said:
Hi! Obs.: I'm new in the forum, só, if i err something obvious, please, say it ,-,...
I've tested the ROM published and i loved how it's fast in boot. The problem related with boot and wifi looks not appearing more. This ROM was some personals and best performance. The camera isn't work. I rebooted 3 times and nothing. That's the unique error that i found.
I've switched so many ROM's, searching to find a ROM like these features.
The ROM is so much fluid and faster.
Good work!
Click to expand...
Click to collapse
Hi! I'm glad you liked the ROM, and yeah, the camera issues are really frequent on this device. I can't promise anything but I'll be taking a look at what's wrong and try to fix it by the late night of today (UTC -03:00).
For me, it worked, then it wasn't working, rebooted, working again.
UPDATE: Solved the issue. Click here to see the solution.
I have no clue what happened, but every time I try to load the camera, the system freezes. The camera can't be opened anywhere.
I've used TWRP, etc, for a long time, no problems. I decided to try the LOS17 ROM, and now I can't get the camera to load no matter what I do. I've even reset the phone using LGUP and installing the KDZs, to no avail.
Currently, it's showing Kernel Version 4.4.78 on Software US99820a. Regardless of where I try to use the camera, it freezes the entire phone completely. About to have a panic attack. Any way I can get this back?
hellodmo said:
I have no clue what happened.
I've used TWRP, etc, for a long time, no problems. I decided to try the LOS17 ROM, and now I can't get the camera to load no matter what I do. I've even reset the phone using LGUP and installing the KDZs, to no avail.
Currently, it's showing Kernel Version 4.4.78 on Software US99820a. Regardless of where I try to use the camera, it freezes the entire phone completely. About to have a panic attack. Any way I can get this back?
Click to expand...
Click to collapse
You've Master Reset and used REFURBISH mode using the new Dev Patched LGUP?
Why 20a? Why not 20h, most recent?
ChazzMatt said:
You've Master Reset and used REFURBISH mode using the new Dev Patched LGUP?
Why 20a? Why not 20h, most recent?
Click to expand...
Click to collapse
I originally tried 20h, and it locked the phone up when trying to load the camera. Originally, I had all sorts of LG IMS has stopped errors after using the standard TWRP restore, AND the camera didn't load, so I decided to restore 20h. I tried that, and the LG IMS issue went away, but the camera didn't work. So now I'm doing 20a->20f->20h in order to see if that restores. I'll be done with that in a few minutes.
I have no idea why this would have happened, and why the TWRP restore didn't work immediately. The TWRP install of LOS17 changed something that doesn't seem to be recoverable, and I have no clue how....
Still not working. Just freezes. Every. Single. Time.
20a->20f->20h with master resets all around, etc. I'm stumped.
hellodmo said:
Still not working. Just freezes. Every. Single. Time.
20a->20f->20h with master resets all around, etc. I'm stumped.
Click to expand...
Click to collapse
You updated to Pie blobs and now are trying to downgrade back to Oreo.
Are you trying to use TWRP flashable zips?
You need to use Refurbish mode KDZ. Then Master Reset. You can use 20h.
Which dev patched LGUP are you using? Use the newer one from the Pie KDZ threads, like here:
https://forum.xda-developers.com/showpost.php?p=79971595&postcount=3
You will still have unlocked bootloader, but you'll lose TWRP. You'll need to then reinstall TWRP and the three root files. For that go by these instructions, even though you are back on Oreo. Ignore that it says you are on Pie. Use those newer encryption disabler files and the newer root check files.
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500/post79972584#post79972584
Still doesnt work. Wondering if the rom somehow fried the hardware....
hellodmo said:
Still doesnt work. Wondering if the rom somehow fried the hardware....
Click to expand...
Click to collapse
Then try Partition DL with all partitions.
Please answer the question -- are you using the new Dev Patched LGUP?
Don't try to reinstall TWRP and root yet. Make sure the camera is back working on full stock firmware first.
Yes. Patched LGUP. Got some company over, but ill try the DL partitions later
hellodmo said:
Yes. Patched LGUP. Got some company over, but ill try the DL partitions later
Click to expand...
Click to collapse
Okay, did the DL Partitions (our low-maintenance friends are awesome), but it still didn't do much. I'll hook it up to ADB soon. Looks like there may be a problem accessing some SQLite Log database, and I'm wondering if it's related....
If you have any other ideas at the moment, let me know. The same behavior persisted. The camera won't open and load.
hellodmo said:
Okay, did the DL Partitions (our low-maintenance friends are awesome), but it still didn't do much. I'll hook it up to ADB soon. Looks like there may be a problem accessing some SQLite Log database, and I'm wondering if it's related....
If you have any other ideas at the moment, let me know. The same behavior persisted. The camera won't open and load.
Click to expand...
Click to collapse
Should I master reset after doing DL partitions?
@SGCMarkus Curious if you have any clue what's going on here. Did a search for one of the issues I was having and came across your github.
https://gist.github.com/SGCMarkus/baf1ee39715259489c02243c97598f9f
Noticing alot of missing libraries, it seems like. Wondering if there's a way to replace them....
HTML:
09-22 18:59:35.349 1704 1734 I CameraManagerGlobal: Connecting to camera service
09-22 18:59:35.349 1704 1734 E CameraManagerGlobal: Camera service is unavailable
09-22 18:59:35.349 25917 25917 I mm-camera: <ISP ><I> 4069: isp_resource_get_isp_hw_limit: isp hw limit 0
09-22 18:59:35.405 25917 25917 I mm-camera: <ISP ><I> 4069: isp_resource_get_isp_hw_limit: isp hw limit 0
09-22 18:59:35.435 25917 25917 I mm-camera: <ISP ><I> 960: module_isp_init: module 0xdea98a60
09-22 18:59:35.454 25917 25917 I mm-camera: <CPP ><I> 174: cpp_module_init: info: CPP module_init successful
09-22 18:59:35.465 25917 25917 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_llvd.so error dlopen failed: library "libllvd_smore.so" not found
09-22 18:59:35.465 25917 25917 E mm-camera: <IMGLIB><E> 1214: frameproc_comp_load: frameproc_comp_load:1214] cannot load libmmcamera_llvd.so
09-22 18:59:35.465 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: llvd] Error rc -7
09-22 18:59:35.468 25917 25917 E mm-camera: <IMGLIB><E> 2023: multi_frameproc_core_reload_lib: Error opening multi_frameproc library libmmcamera_sac_lib.so error dlopen failed: library "libmmcamera_sac_lib.so" not found
09-22 18:59:35.468 25917 25917 E mm-camera: <IMGLIB><E> 2153: multi_frameproc_core_load: cannot load libmmcamera_sac_lib.so status -7
09-22 18:59:35.468 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: sat] Error rc -7
09-22 18:59:35.468 25917 25917 E mm-camera: <IMGLIB><E> 4056: module_qdc_common_init: mct module 0x0
09-22 18:59:35.469 25917 25917 E mm-camera: <IMGLIB><E> 2023: multi_frameproc_core_reload_lib: Error opening multi_frameproc library libmmcamera_bokeh_oem.so error dlopen failed: library "libmmcamera_bokeh_oem.so" not found
09-22 18:59:35.470 25917 25917 E mm-camera: <IMGLIB><E> 2153: multi_frameproc_core_load: cannot load libmmcamera_bokeh_oem.so status -7
09-22 18:59:35.470 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: sac] Error rc -7
09-22 18:59:35.470 25917 25917 E mm-camera: <IMGLIB><E> 4056: module_qdc_common_init: mct module 0x0
09-22 18:59:35.471 25917 25917 E mm-camera: <IMGLIB><E> 4082: module_qdc_common_init: Algo Capabilities Crop caps 0,core type 0, access mode 0, exec mode 0
09-22 18:59:35.480 25917 25917 E mm-camera: <IMGLIB><E> 4082: module_qdc_common_init: Algo Capabilities Crop caps 2,core type 1, access mode 1, exec mode 3
09-22 18:59:35.486 25917 25917 I mm-camera: <IMGLIB><I> 2157: faceproc_sw_wrapper_load: Loading faceproc library
09-22 18:59:35.491 25917 25917 W mm-camera: <IMGLIB><W> 1235: faceproc_dsp_comp_load: face detection dsp disabled , enable by set property
09-22 18:59:35.521 25917 25917 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
09-22 18:59:35.521 25917 25917 E mm-camera: <IMGLIB><E> 1214: frameproc_comp_load: frameproc_comp_load:1214] cannot load libmmcamera_ubifocus_lib.so
09-22 18:59:35.521 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: imglib_ubifocus] Error rc -7
09-22 18:59:35.522 25917 25917 W mm-camera: <IMGLIB><W> 748: module_imglib_create_topology: Can not init the module imglib_ubifocus
09-22 18:59:35.522 25917 25917 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
09-22 18:59:35.522 25917 25917 E mm-camera: <IMGLIB><E> 1214: frameproc_comp_load: frameproc_comp_load:1214] cannot load libmmcamera_ubifocus_lib.so
09-22 18:59:35.522 25917 25917 E mm-camera: <IMGLIB><E> 3542: module_imgbase_init: imglib_refocus] Error rc -7
09-22 18:59:35.522 25917 25917 W mm-camera: <IMGLIB><W> 748: module_imglib_create_topology: Can not init the module imglib_refocus
09-22 18:59:35.543 25917 25917 W mm-camera: <IMGLIB><W> 748: module_imglib_create_topology: Can not init the module imglib_oem1
hellodmo said:
Should I master reset after doing DL partitions?
Click to expand...
Click to collapse
Doesn't hurt, may help.
It seems like there's some kind of vendor file that might be corrupted. I may be asking for a file or two in a bit. I'll likely root it so I can access the file system properly in a non-readonly mode. Can't hurt it any worse at this point, unfortunately.
A master reset following Partition DL didn't do anything.
So it looks like I'm missing a few files.
Code:
09-22 21:12:30.213 3763 3763 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_llvd.so error dlopen failed: library "libllvd_smore.so" not found
09-22 21:12:30.216 3763 3763 E mm-camera: <IMGLIB><E> 2023: multi_frameproc_core_reload_lib: Error opening multi_frameproc library libmmcamera_sac_lib.so error dlopen failed: library "libmmcamera_sac_lib.so" not found
09-22 21:12:30.217 3763 3763 E mm-camera: <IMGLIB><E> 2023: multi_frameproc_core_reload_lib: Error opening multi_frameproc library libmmcamera_bokeh_oem.so error dlopen failed: library "libmmcamera_bokeh_oem.so" not found
09-22 21:12:30.266 3763 3763 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
09-22 21:12:30.267 3763 3763 E mm-camera: <IMGLIB><E> 1348: frameproc_comp_reload_lib: Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
@ChazzMatt Would it be possible to extract those and attach them here? I'm thinking if I add them to the lib folder, perhaps it'll maybe, possibly, fix the underlying issue....
It looks like they're located under /system/vendor/lib....
Okay, managed to get it working again. My guess is that there's something in the Nougat KDZ that sets up the camera, that might have been affected by something in the LOS17 ROM. tldr; I had to restore the US99810c KDZ file to get the camera to work again, and then I finished the rest of the steps to get everything in order again. Here's the complete breakdown of what I did, step by step. Some of these may be redundant to fix the issue, but I'm including them anyways.
Flash US99810C through Patched LGUP. <-- This is what gave me the camera back. The camera worked in Nougat, so I started flashing the oreo roms.
Flashed US99820A through Patched LGUP. <-- Did this for unlock and TWRP install.
Boot into system. Unlock developer tools. Turn on USB Debugging, and start debugging.
adb reboot bootloader
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Swipe to allow modifications.
Wipe/Format.
Reboot to Recovery.
Restore previous working backup.
Boot to system - No sound. (I've been here before.)
Flash US99820F to fix sound.
Wipe.
Boot to system. Go through the setup. Verify sound capabilities.
Restore to previous working backup.
Clear Cache and Dalvik.
Boot into system. Verify camera and sound. Rock and Roll.
Say I'll never install another custom ROM again, but know I'm lying to myself, and I'll probably take this not as a warning, but as a confidence builder, which explains why I'm a software developer to begin with.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 restore 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.
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.
*/
SUPPORTED DEVICES
- SONY XPERIA X (suzu)
TODO:
Code:
- Nothing
Changelog:
Code:
05/04/2022:
- Initial build
07/04/2022:
- Add some missing graphics blobs
13/04/2022:
- Fix fingerprint at all
3rd PARTY ADDONS/MODS
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
HOW TO INSTALL LINEAGEOS
- Boot into TWRP.
- Format Data, Wipe System, Cache, Dalvick Cache
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
DOWNLOADS
Lineage 18.1 v1: https://www.androidfilehost.com/?fid=14655340768118449381
Lineage 18.1 v2: https://androidfilehost.com/?fid=14655340768118450233
LineageOS 18.1 v3: https://androidfilehost.com/?fid=14655340768118454166
Official releases: https://download.lineageos.org/suzu
Google Apps: http://opengapps.org/
HOW TO CONTRIBUTE?
Send your patches up for review: https://review.lineageos.org/
SOURCES:
Common tree: https://github.com/sony-msm8956-dev/android_device_sony_loire-common
Device tree: https://github.com/sony-msm8956-dev/android_device_sony_suzu
Kernel source: https://github.com/sony-msm8956-dev/android_kernel_sony_msm8956
Vendor blobs: https://github.com/sony-msm8956-dev/proprietary_vendor_sony
Done by:
- @ud4
- @jmpf_bmx (me)
Thanks to:
- @TeamMex
- Panda
- @Chippa_a
- @tarkzim
SONY MSM8956 TG group:
https://t.me/sonyMSM8956
Donation:
https://www.paypal.com/paypalme/jmpfbmx
Reserved!
once again thanks for your work
this rom also seems to be working fine, it's just great!
but i'm not able to pass SafetyNet check, there's something missing about the trusted environment (which worked on 17.1).
i'm attaching a screenshot (you can find the app here: https://github.com/vvb2060/KeyAttestation/releases if it's useful)
57op said:
once again thanks for your work
this rom also seems to be working fine, it's just great!
but i'm not able to pass SafetyNet check, there's something missing about the trusted environment (which worked on 17.1).
i'm attaching a screenshot (you can find the app here: https://github.com/vvb2060/KeyAttestation/releases if it's useful)
View attachment 5580895
Click to expand...
Click to collapse
We will take a look at it asap
Thanks
Regards Jose
New build is up!
i think there's a problem with fingerprint sensor, or at least with how apps interact with it.
it works perfectly fine for screen unlocking, but some (banking mostly) apps fail to recognize its presence or don't interact with it correctly.
moreover, i was messing around and added another fingerprint in system settings which is now impossible to delete.
i'm attaching some logs if it can be useful:
Code:
04-07 22:08:45.403 3023 3023 D [email protected]: Removing finger 1037772870 for gid 0
04-07 22:08:45.407 12456 12474 D OpenGLRenderer: endAllActiveAnimators on 0x7863ceabc0 (RippleDrawable) with handle 0x7783c42fb0
04-07 22:08:45.416 3023 3023 D FingerprintWorkerThread: moveToState: Setting state to Idle
04-07 22:08:45.416 3023 3023 E [email protected]: An unknown error returned from fingerprint vendor library: -8
04-07 22:08:45.416 3023 3144 D FingerprintWorkerThread: RunThread: Switched to state Idle
04-07 22:08:45.416 3023 3144 D [email protected]: IdleAsync
04-07 22:08:45.416 3177 3177 W FingerprintService: startRemove with id = 1037772870 failed, result=1
04-07 22:08:45.416 3177 3177 V BiometricStats: Error latency: -1
04-07 22:08:45.417 3177 3177 W BiometricStats: found a negative latency : -1
04-07 22:08:45.417 3177 3177 V BiometricStats: Error latency: -1
04-07 22:08:45.417 3177 3177 W BiometricStats: found a negative latency : -1
04-07 22:08:45.418 3177 3177 V FingerprintService: Done with client: [email protected]
04-07 22:08:45.418 3177 3177 V FingerprintService: handleError(client=null, error = 6)
57op said:
i think there's a problem with fingerprint sensor, or at least with how apps interact with it.
it works perfectly fine for screen unlocking, but some (banking mostly) apps fail to recognize its presence or don't interact with it correctly.
moreover, i was messing around and added another fingerprint in system settings which is now impossible to delete.
i'm attaching some logs if it can be useful:
Code:
04-07 22:08:45.403 3023 3023 D [email protected]: Removing finger 1037772870 for gid 0
04-07 22:08:45.407 12456 12474 D OpenGLRenderer: endAllActiveAnimators on 0x7863ceabc0 (RippleDrawable) with handle 0x7783c42fb0
04-07 22:08:45.416 3023 3023 D FingerprintWorkerThread: moveToState: Setting state to Idle
04-07 22:08:45.416 3023 3023 E [email protected]: An unknown error returned from fingerprint vendor library: -8
04-07 22:08:45.416 3023 3144 D FingerprintWorkerThread: RunThread: Switched to state Idle
04-07 22:08:45.416 3023 3144 D [email protected]: IdleAsync
04-07 22:08:45.416 3177 3177 W FingerprintService: startRemove with id = 1037772870 failed, result=1
04-07 22:08:45.416 3177 3177 V BiometricStats: Error latency: -1
04-07 22:08:45.417 3177 3177 W BiometricStats: found a negative latency : -1
04-07 22:08:45.417 3177 3177 V BiometricStats: Error latency: -1
04-07 22:08:45.417 3177 3177 W BiometricStats: found a negative latency : -1
04-07 22:08:45.418 3177 3177 V FingerprintService: Done with client: [email protected]
04-07 22:08:45.418 3177 3177 V FingerprintService: handleError(client=null, error = 6)
Click to expand...
Click to collapse
Thanks for reporting the issue
We will take a look today/tomorrow.
Thanks
Regards Jose
Nice Rom. It runs smooth. Only Fingerprint has Problems.
New build up with fingerprint fixed!!!
Hi,
First thanks a lot for the roms.
I do have a strange problem, sometimes app become suddently uresponsive, and the only possible thing to do to get them back run is to reboot.
But i if do this, screen goes black like the phone is off, but actually it's not, because if i connect the charger, the charge light doesn't power on.
I have to wait some hour that the phone get the battery empty, after this if i connect the charger power light power on, and i can power on the phone.
I don't have gapps installed, and all of my application come from fdroid (except protonmail which come from protonapps website and signal from signal website), that's the same application list i have installed when on official roms (Maybe ten in total).
Bug appeared first time on Bromite, then Signal, and last time Protonmail.
Last time i tried to wait some hour to see if the bug disapear, and not to be locked multiple hour without phone (time to wait for complete discharge on black screen), but protonmail remained uresponsive.
I don't have log to provide actually, but will try to get one when possible.
Ski-lleR said:
Hi,
First thanks a lot for the roms.
I do have a strange problem, sometimes app become suddently uresponsive, and the only possible thing to do to get them back run is to reboot.
But i if do this, screen goes black like the phone is off, but actually it's not, because if i connect the charger, the charge light doesn't power on.
I have to wait some hour that the phone get the battery empty, after this if i connect the charger power light power on, and i can power on the phone.
I don't have gapps installed, and all of my application come from fdroid (except protonmail which come from protonapps website and signal from signal website), that's the same application list i have installed when on official roms (Maybe ten in total).
Bug appeared first time on Bromite, then Signal, and last time Protonmail.
Last time i tried to wait some hour to see if the bug disapear, and not to be locked multiple hour without phone (time to wait for complete discharge on black screen), but protonmail remained uresponsive.
I don't have log to provide actually, but will try to get one when possible.
Click to expand...
Click to collapse
Oooh, I had that problem happen to me as well. I was gonna reboot the phone into recovery mode (from power menu) and then the screen turned off and the phone stopped responding. I thought it got bricked but after trying every key combination it suddenly powered up again. I don't remember exactly which one got me out of that state but I think it was vol up or vol up + power.
tomy1802 said:
Oooh, I had that problem as well. I was gonna reboot the phone into recovery mode (from power menu) and then the screen turned off and the phone stopped responding. I thought it got bricked but after trying every key combination it suddenly powered up again. I don't remember exactly which one got me out of that state but I think it was vol up or vol up + power.
Click to expand...
Click to collapse
First time it happened i tought i bricked too (seeing the phone not charging at all)
Will try the key combination if that happened again, and give a log if possible.
Edit:
Any problem with microsd formatted as extfat ? I remember i encountered very slow speed on another lineageos of another phone.
Because i saw a long delay for starting download with browser, i thinked it was the allocation of the file that took time.
After this i tried to copy from internal to sd, it was very very slow.
So i decided to test sd throughput, and here the result :
An average of 3 MB/s with a sandisk ultra, who worked far far more fast on official roms.
Edit 2:
So after backing up my sd, i formatted to fat32, and the very slow speed remain the same...well i got 4.59 MB/s, but still very slow when i compare to troughtput i got on pc.
is it just me or proximity sensor doesn't seem to work?
while calling or listening to audio messages, placing the phone near the ear, the screen stays on
also auto-rotation isn't working
The lock of app happened again this morning, i was streaming with shadow, i switched to signal, and app lock.
I tried all my apps, signal protonmail and keepassdx was uresponsive and not possible to re-run them until i restart the phone.
The good thing is the trick power + volup force the phone to restart and not stay blocked in a loop until the battery was empty.
Those "locks of app" you're talking about: do you mean that you open an app and the whole screen goes black? If that's the case the issue already exists in LOS 16.0 which I'm currently using and comes from the Sony (graphics?) drivers in that old kernel which I guess is in use in this ROM also (?). In my case I just set the back-button so that when you hold it it will force close the "blacked out" app. You just have to find the back button blindly of course, but that should be no problem. Btw the option to set the hold on back-button to force close is in the developer option. At least LOS 16.0 offers it.
I think I also reduced the issue happening by disabling landscape display rotation. The issue occurs most often when switching directly from an internet browser to another app.
I hope the issue I described is the one you guys were talking about & the kernel is the one I suspected since otherwise my comment is totally superfluous ;-)
Ski-lleR said:
The lock of app happened again this morning, i was streaming with shadow, i switched to signal, and app lock.
I tried all my apps, signal protonmail and keepassdx was uresponsive and not possible to re-run them until i restart the phone.
The good thing is the trick power + volup force the phone to restart and not stay blocked in a loop until the battery was empty.
Click to expand...
Click to collapse
Oh
I didn't experienced that problem, do you have any video or something?
So i can try to replicate that and fix it
Thanks
Btw now we are into OFFICIAL Lineage, I would recommend you to clean flash OFFICIAL version!!
jmpf_bmx said:
jmpf_bmx said:
Btw now we are into OFFICIAL Lineage, I would recommend you to clean flash OFFICIAL version!!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This rom definitely deserves to be called official. It's even smoother than LineageOS 16.1 by Chippa_a. Thank you for your hard work. One question.
Is this
suzu
is your build too?
Hi
Those aren't my builds.
Thanks
Regards Jose