[CUSTOM ROM][OFFICIAL] LineageOS 18.1 for XPERIA X (suzu) - Sony Xperia X ROMs, Kernels, Recoveries, & Other D

{
"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

Related

[ROM]Bootleggers-4.0-Shishufied][CEDRIC][OFFICIAL][PIE][STABLE]

{
"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 Features​QS 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

[ROM][8.1][UNOFFICIAL] Android Ice Cold Project v13.1

Removed
moto actions?
the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly
KamiGooDz said:
moto actions?
Click to expand...
Click to collapse
Yes, it's available
snapchat don't work, how fix?
Update
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
FpX said:
the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly
Click to expand...
Click to collapse
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
KamiGooDz said:
snapchat don't work, how fix?
Click to expand...
Click to collapse
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.
AsD Monio said:
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.
Click to expand...
Click to collapse
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)
anybody tested nin moto g5S xt1795 indian edition
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:28 AM ---------- Previous post was at 07:26 AM ----------
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
anybody tested in moto g5S xt1795 indian edition ?
FpX said:
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)
Click to expand...
Click to collapse
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.
AsD Monio said:
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.
Click to expand...
Click to collapse
I was using the previous build, now it's working perfectly, thanks!
Update
aicp_montana_o-13.1-UNOFFICIAL-20190121
Changes
Enforcing SELinux
Download: http://www.mediafire.com/file/hquz82ge8werfgf/aicp_montana_o-13.1-UNOFFICIAL-20190121.zip/file
Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
newinnov said:
Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
Click to expand...
Click to collapse
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
AsD Monio said:
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
Click to expand...
Click to collapse
Yes, It was indeed! Actually I flashed the custom kernel on top of that , somehow that was causing trouble. Thanks again.
Flashed it om my wifes phone yesterday, she's very happy, less battery drain and wifi is better, which was the main reason to try a custom rom.
Thanks guys!
Hi, is Fingerprint, camera photo/video recording, and Moto display notifications working good ?
Thank´s
One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"
SvenHee said:
One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"
Click to expand...
Click to collapse
I had that happen to me as well, it's not the ROM's fault. Either fastboot or the stock recovery store some data in the /misc partition. That tells the bootloader/kernel to boot to recovery by default. It's probably meant to ensure that a partially upgraded system does not get booted while flashing a stock ROM. To fix it just wipe the /misc partition, I recommend making a backup first. I used dd in the terminal in TWRP for both operations (adb shell will work as well but it has some problems with displaying some characters in the Windows command prompt). To back up the partition:
Code:
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/misc.img
^ (replace "external_sd" with "data/media/0" to save it in the internal storage instead of the external microSD card)
To wipe /misc:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
It may also work using fastboot, though I have not tried this way:
Code:
fastboot erase misc
Thanks!
That is slightly intimidating to execute but I'll give it a go!
aicp_montana_o-13.1-UNOFFICIAL-20190116
My device : xt1799-2
64bit os.
VoLte works for my xt1799-2.
Bugs:
1. Can't copy any file from the device to my PC. The same bug in crDroid 8.1.0 rom. And lineageos. This happens in all the third party rom between 8.1.0-9.0. Date at least before 2019-09-23. But can copy the folder from the device. But also can send file to the device, so weird.
________________________________________________
I see the lineageos 15.1 changelog:
2019-09-23:
September security patch
Optimized SEPolicy
Fixed MTP (thanks to @wiktorek140)
We're back to LTE
________________________________________________
But can copy the folder from the device. But also can send file to the device, so weird.
2. Front camera doesn't work.
3. Fingerprint doesn't work.
4. Delay a lot when you scroll the page, or move the app icon. The same bug in crDroid 8.1.0.
5. Call recorder. If you don't open the speaker, the inner voice recorded from the other side is too small, unable to hear it clearly.

[ROM][Pie][OFFICIAL] COSP [9.0.0][harpia]

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.

Tutorial: Gear S for Tab Active 2

Work in progress to make it work on a samsung tablet running android 7.1.1
Can get the watch to be seen by gear manager but it fails during set up.
This is a list of trial and errors at the moment - please add any ideas you have.
Install magisk /root
Install Magiskhide props config
Install terminal emulator
install busybox via magisk downloads
terminal emulator -> props
Add new custom value
ro.product.model
Was SM-T395
Set to GT-N7105 (note 2)
1. default (current)
y
Boots OK
Safetynet pass
download wear
download amaze file manager
navigate to /data/data/com.samsung.android.app.watchmanager/files/rules.xml
edit to allow tablets=true
set it read only(!)
restart
Safetynet pass
run gear wearables & connect
--------------Beyond this it's a bit of a guess. Trying gearmanagerstub.apk but no luck yet.
--------------Currently fails after 5-10 seconds of 'connecting to gear', which displays on phone and watch.
Sees watch and connects also shows connecting on the watch but then the app bombs back to a list of devices. So it passes the initial device checks at least, but gear2splugin is failing somehow
Maybe I need gearmanagerstub Will try downloading Note 8 7.1.1 firmware see if there is a gearmanagerstub. Yes it has one.
& use magisk app systemiser module....
terminal -> systemize
option 3
enter path of gearmanagerstub.apk e.g. /sdcard/GearManagerStub.apk (where I put mine)
where to install? 1. /system/app
Nothing shows in /system/app... watchmanager bombs again
try restart
Interesting it keep updating rules.xml now.... it is back to supports tablet=false. Both after restart, and then after starting watchmanager. (I edited it after boot then checked again)
fix is set rules.xml to read only.
So perhaps an older version of gearmanagerstub would do the trick.. (I'm using the oldest note 8 one)
run terminal ->systemize
revert app - select 1- (null??)
install note 3 5.0 gearmanagerstub.apk same process
After another failure to connect it got further to ELUA screen before bombing.
I see it thinks my watch is installed now...
It connects for maybe 10 seconds hits "back up and restore" and immediately bombs. The app acts like it is working but the gear says it's not "failed to connect"
Suddenly pops up "error your gear is disconnected" on the restore page.
Now it's back to failing after 5 seconds / 10 spins.
tried copying gearmanagerstub to /system/app and reinstalling all, no difference
This did not trigger safetynet.
Try setting to SM-950F... no change.
Try setting fingerprint to note 8 (SM-950F) (8.0 although I am running 7.1.1)
try ro.build.characteristics=phone,emulator (currently tablet,emulator)
This gives a different list of devices (watches not just earphones) when I reinstalled gear manager.
Still bombs, also the icon is still a tablet when connecting, not a phone.
If anyone has figured this out already I'm all ears
could try non samsung next
https://forum.xda-developers.com/showpost.php?p=79230009
or other ideas
https://www.youtube.com/watch?v=nKH1ykQR4iQ
Update- bluetooth crash in logcat
Looking at logcat and the apks it appears that watchmanager only checks to see if the watch is 'non samsung'. How it decides that an GT-N7105 magically makes it a samsung product but a T395 is not, I can't figure it out.
Interestingly modifying rules.xml and simply adding supportsnonsamsung = true seems to work.
In any case logcat shows a bluetooth error/crash. Why it crashes I don't know.
It looks like the trigger is
11-14 13:35:56.237 4853 4853 E SACalendarProvider::Service: CALENDAR_HOSTMANAGER_CONNECT
Shortly after this a lot of data seems to be sent over bluetooth. A few seconds later the data stops, and 200ms later an error:
11-14 13:35:59.786 3525 3609 E bt_hci : command_timed_out [BT_CORE] hci layer timeout waiting for response to a command. opcode: 0xffff
Nothing interesting happens in logcat in the 2 seconds of data transfer.
A while later the app detects that the watch is disconnected
and eventually bombs. A few seconds after that the watch reports setup fail.
Here is a list of interesting error codes
11-12 12:18:58.417 31815 31832 E BluetoothDataManager: getUartErrorInfo 000 000 000 000
11-12 12:18:58.417 31815 31832 E BluetoothDataManager: "LO_MFN":"29","LO_LMP":"8","LO_SUB":"602","LO_FWV":"BTFM.TF.1.3-00036-QCATFSWPZ-1","ERROR_REASON":"225","UART":"000 000 000 000"
11-12 12:18:58.599 22777 31958 E SABtServerListener: SA_ERROR: IOexception in UUID xxx-xxx-xxx-xxx-xxx ::Exiting Now
11-12 12:18:58.601 3600 4901 I ActivityManager: Process com.android.bluetooth (pid 31815) has died(68,798)
Here is a list of things that crashed
11-12 12:18:58.611 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.btservice.AdapterService in 1000ms
11-12 12:18:58.612 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.hdp.HealthService in 11000ms
11-12 12:18:58.614 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.hid.HidService in 10997ms
11-12 12:18:58.617 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.map.BluetoothMapService in 10994ms
11-12 12:18:58.618 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.a2dp.A2dpService in 10993ms
11-12 12:18:58.619 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.gatt.GattService in 10992ms
11-12 12:18:58.619 22777 22808 D SADiscoveryCore: handling msg: DEVICE_ACCESSORY_LOST...
11-12 12:18:58.619 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/com.samsung.ble.BleAutoConnectService in 20992ms
11-12 12:18:58.619 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.hid.HidDevService in 30992ms
11-12 12:18:58.620 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.opp.BluetoothOppService in 30991ms
11-12 12:18:58.620 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.sap.SapService in 30991ms
I am not sure what causes this error.
I tried many versions of gear2plugin which contains the apks such as SAproviders / SAcalendarprovider code..
It seems that the bluetooth process under hostmanager-connectionmanager-databuilder works for "single chunk" but with fragmented data it receives 12 chunks of 61k (or so) before dying.
any ideas?
Just FYI
The same T395 tab-phone works pairing a Gear S3 which uses a different plugin 'gearoplugin', with rules.xml edited to say support tablet = true and set to read only. No other tricks are needed I think as supportnonsamsung is already true, all connected to the internet etc. Obviously you need root to edit rules.xml.
= Gear S plugin V2.2.03.19032541N
= Galaxy Wearable V2.2.27.19083061
The gear s uses gear2smodule. I tried the latest version I could find 2118120361, which didn't work.
aka GearModule Version 2.2.02.18120361
Does anyone have a later version?

[KERNEL][3.18.140+][EOL for now] SwanKernel for the LG V20

{
"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"
}
A custom kernel for (most) V20 variants​
SwanKernel is an android kernel based on the latest Lineage OS 18.1 sources for the LG MSM8996 phones, aiming to bring those features and updates and improve them with some extra tuning, fixing and external features tailored specifically for the LG V20's performance characteristics and feature set, while trying to maximize the battery life and responsiveness of the device at the same time.​
This kernel is based on Linux 3.18.140, and has become EOL with the last commit, as i don't think there's anything else that can be optimized for the V20 on this source anymore.
​Which phone variants/models does this kernel support?​
The kernel currently supports the following variants:
H910/H915
H918
H990
LS997
US996
VS995
Support for other special variants like the US996Santa might come at a later date if needed.
What does this kernel intend to achieve?​
The main goal here is to have a kernel that not only has extra features and improvements, but is also clean and concise, having only features that are truly needed from a kernel that will run alongside a Android 11-based ROM. One example of that is Kcal display control, a feature that is unnecessary here since most, if not all Android 11 ROMs have LiveDisplay for that exact same purpose and without the need to root. This helps the kernel have a smaller file size and lower processing overhead, as well as promote better maintainability.
This kernel does have a battery life bias, but will still scale up to maximum performance when needed. No Overclocking is done for now.
Does it have any features over stock?​
Yes, a lot. The kernel is divided into two variants, here are the features both variants have over stock:
AdrenoBoost for improved GPU performance.
GPU and CPU/Cache Undervolt for better power efficiency on load.
CPU governors tuned for better battery life and thermal stability without impacting performance all that much.
Almost no unnecessary debug flags on the kernel for better kernel performance.
Westwood TCP Congestion Algorithm set as default in order to have better network performance and consistency.
AutoSMP CPU Hotplug to shutdown the big cores when their stronger performance isn't needed, slightly improving battery life on light loads and idle.
Disabled CPU Boost when a finger is detected on screen, preventing unnecessary frequency boosts when no meaningful action is done other than tapping on screen and slightly scrolling around. We have Schedutil to keep it smooth anyways.
USB Fast Charge.
Multiple cherry-picks from different msm8996 sources with fixes and improvements to the kernel.
Configurable wakelock blocker (boeffla) for roms that have some "unneeded" wakelocks enabled by default and/or users that know which wakelocks can be blocked for better battery life.
Anxiety IO Scheduler enabled by default, offering a read bias and lower latency in IO operations.
Kernel updated to Linux 3.18.140 with some extra patches from Googlesource.
Wireguard support, improving VPN performance.
Cryptographic functions optimizations, slightly improving the phone's performance when calculating hashes and so on.
The Extreme variant has some extra features over the Stable one, those being:
Stronger Undervolts (i'm talking about borderline unstable undervolts here, so i really recommend that you flash the Stable one first).
CPU Voltage Control if you need to setup a custom undervolt to keep it more stable and have no need to compile the kernel from source just to change the values... and that's assuming your phone even boots with this variant of the kernel.
Disabled Battery BCL which eliminates the power throttling caused by the battery, just be careful when running demanding tasks while having almost no battery left.
Are there any bugs?​
Right now, there's the dreaded Infrared Blaster, and it... kinda works? The IR is able to send the very first command i give to my LG TV without any problems after every reboot, but refuses to send anything else after that first command. The IR Blaster's light still works all the time though despite having some big delays between on/off states.
Download & Installation​
The folders containing each kernel variant can be found here:
Stable Version
Extreme Version
To install the kernel, it's the standard procedure:
Download the kernel you want for your device
Place it into the phone
Boot into recovery, select it and then flash
Wipe Dalvik Cache (optional, you only need to wipe it if you face random Force Closes, but it is a good practice anyway)
Reboot.
Open any app that can check the device info and look for "kernel", where it will show "... 3.18.xxx-Swan" if it installed correctly. I personally use SmartPack for that, but it requires root.
Enjoy the experience!
Performance and Battery metrics​
Spoiler: outdated (done in v1.00), performance has improved since then:
And now to the kernel's real world performance. But before delving in, keep in mind that my refurbished H910 is apparently a Snapdragon 821 prototype, that's why you will see higher than normal performance and clock values on cpu matters even with the LITTLE cores underclocked to 1785MHz instead of 2188MHz, the snapdragon 820 ones should not have any underclock applied and will reach the max of 1593MHz on them. I also took the liberty of testing those on the Extreme variant as BCL often interferes with the performance results and the extra undervolt doesn't increase performance in any substantial way, 5-7% at most on Geekbench.
Battery life:
Screen SOT test (Youtube looping through a massive playlist of songs with some scrolling to change between them):
Not very impressive, until you consider the battery currently powering it:
CPU/GPU Performance:
CPU performance according to Geekbench 5.4.1 (there is some minor variance of about 15-21 points in multithread):
CPU sustained performance on CPU Throttling Test(running it for 15+ minutes barely changes the curve, as it stabilizes at around 80-82 Celsius, i suppose a Snap 820 will fare better here due to the lower clocks):
GPU general performance on GFXBench 5:
No copper shim replacement or thermal pad change was made, the phone's internal structure is still the same from when i bought it.
Storage Performance:
General IO performance in Androbench 5(Not very accurate, but welp, if anyone has a more in-depth one feel free to share):
And there we go, everything i could benchmark so far. This will not be the best kernel on every front so the stock kernel on Lineage 18.1, Lighthouse's kernel or mk2000 might suit you better depending on your needs.
Changelog​
Spoiler: Changes done in recent versions:
*********** Swankernel V1.09+ [Maintenance release] ***********​
CPU/Cache/GPU Voltages have basically reached the optimum point on both stable and extreme.
Some performance commits were cherry-picked from newer kernels for other devices
Dynamic FSync was disabled since it could cause data loss on some edge cases involving reboots.
Improved some string routines and memory access functions, about 4% or so improvement on geekbench.
*********** Swankernel V1.09 [Last 3.18 version, i think] ***********​
Minor performance and power-saving optimizations throughout the kernel
CPU M4M cache undervolting (not really a big difference, but nice to have anyway).
A few cherry-picked fixes for the 3.18 msm8996 kernel tree.
Crypto function optimizations and HW acceleration for CRC32 Enabled.
Not actually a kernel change but: Can now be flashed on android versions lower than 11.
*********** Swankernel V1.08 ***********​
Small performance optimizations related to the voltage curves, especially in the GPU.
PC USB Charging has been fixed and the phone can now be charged over it again.
*********** Swankernel V1.06 ***********​
Upstreamed kernel to 3.18.140 + some extra patches, with more coming later.​
Added Wireguard support for better VPN performance compared to IPSec.​
Smaller fixes to the kernel zip files, improving compatibility with some models.​
Minor performance optimizations, shouldn't be noticeable to the end user.​
Now stable enough (at least the Stable version is) to be used as a daily driver.​
*********** Swankernel V1.00 ***********​Initial release. Has the features from 1 to 12 on both versions, and from 1 to 3 on the Extreme version.​​
Closing notes​
With V1.09, the kernel can now be flashed on basically any android version and should work out-of-the-box, although i didn't test it on stock roms at all and there are no reports of it working there, so it might not work on them.
From what i could gather during the multiple Pre-Beta tests, the battery life improved considerably over the kernel shipped by default with Lighthouse V20 and even more when compared to Lineage's stock kernel.
If you have any suggestion or idea that can possibly improve the kernel, do not hesitate to share, i will try to implement it when my time allows it. If there are any problems that only happen on this kernel, submit a log and i'll try to look at it.
The kernel's source code can be found here.
And last but not least, a special thanks for those that helped me even if indirectly:
@xxseva44
@npjohnson
@askermk2000
@lybxlpsv
@flar2
@osm0sis
And many, many others
The ir is most likely consumer ir related so, we'll have to tweak it until it starts working
xxseva44 said:
The ir is most likely consumer ir related so, we'll have to tweak it until it starts working
Click to expand...
Click to collapse
I was discussing the same thing with @askermk2000 a while ago and that seems to be the case, as not even gamma kernel had a working IR on the branch he tested, and neither the IR files or the git log of it shows any relevant difference on the IR when compared to Lineage's sources. I will keep the disclaimer about it for now because it makes things clearer as there is some confusion about the IR being a kernel problem, so the less convoluted it is to the user for the time being, the better.
Edit: Also, if you need any logs about the infrared while testing it, i can help (i even have some older ones describing the behaviour). Just hit me up when needed since my device will be mostly used as a development phone for the time being.
AShiningRay said:
I was discussing the same thing with @askermk2000 a while ago and that seems to be the case, as not even gamma kernel had a working IR on the branch he tested, and neither the IR files or the git log of it shows any relevant difference on the IR when compared to Lineage's sources. I will keep the disclaimer about it for now because it makes things clearer as there is some confusion about the IR being a kernel problem, so the less convoluted it is to the user for the time being, the better.
Edit: Also, if you need any logs about the infrared while testing it, i can help (i even have some older ones describing the behaviour). Just hit me up when needed since my device will be mostly used as a development phone for the time being.
Click to expand...
Click to collapse
It's more likely an issue with the implementation of the ir drivers not playing well with consumerIR or vise versa. Atm ir only works on the older versions of gamma as they weren't upstreamed like los 18
Hello when I try to flash Swan-H918-Stable.zip on an h918 I get "Unsupported device. Aborting..."
Aethera said:
Hello when I try to flash Swan-H918-Stable.zip on an h918 I get "Unsupported device. Aborting..."
Click to expand...
Click to collapse
Huh... that's strange. I must have messed something up during the anykernel zipping procedure on that model. I'm almost pushing an update to the kernel, so i'll be back in a while with a fix for that.
Edit: Yeah, it was something in the script file, i forgot to change the H910 to H918 on that specific variant flashable. Sorry for that.
I just pushed the file with the fixed script for all the models i checked. If you could test that, i would appreciate it.
AShiningRay said:
Huh... that's strange. I must have messed something up during the anykernel zipping procedure on that model. I'm almost pushing an update to the kernel, so i'll be back in a while with a fix for that.
Edit: Yeah, it was something in the script file, i forgot to change the H910 to H918 on that specific variant flashable. Sorry for that.
I just pushed the file with the fixed script for all the models i checked. If you could test that, i would appreciate it.
Click to expand...
Click to collapse
Just successfully flashed the new Swan-H918-Stable.zip thank you!
Code:
$ uname -a
Linux localhost 3.18.113-Swan-g24ffa95cf1b3-dirty #1 SMP PREEMPT Wed Oct 20 00:18:37 -03 2021 aarch64
Aethera said:
Just successfully flashed the new Swan-H918-Stable.zip thank you!
Click to expand...
Click to collapse
No worries, glad to help.
Here is some output from 'logcat *:E' in case it is of interest:
10-31 16:19:38.753 5926 5926 E ActivityThread: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-31 16:19:40.586 905 937 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-31 16:19:41.778 959 1031 E QC-time-services: Lib:time_genoff_operation: Connection failed !!
10-31 16:19:41.783 959 1031 E QC-time-services: Lib:time_genoff_operation: Connection failed !!
10-31 16:19:42.002 10005 10005 E receiver.modul: Not starting debugger since process cannot load the jdwp agent.
10-31 16:19:42.143 455 455 E lowmemorykiller: Error writing /proc/7941/oom_score_adj; errno=22
10-31 16:19:43.218 10025 10025 E hbox:interacto: Not starting debugger since process cannot load the jdwp agent.
10-31 16:19:44.391 455 455 E lowmemorykiller: Error writing /proc/9412/oom_score_adj; errno=22
10-31 16:19:44.658 1144 1217 E KernelCpuSpeedReader: Failed to read cpu-freq: /sys/devices/system/cpu/cpu2/cpufreq/stats/time_in_state: open failed: ENOENT (No such file or directory)
10-31 16:19:44.675 1144 1214 E libprocessgroup: Error encountered killing process cgroup uid 99005 pid 9572: Permission denied
10-31 16:19:46.683 1144 1550 E LightsService: Light requested not available on this device. 2
10-31 16:19:47.629 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
10-31 16:19:51.008 1144 4213 E WifiService: Permission violation - getScanResults not allowed for uid=10086, packageName=com.google.android.gms, reason=java.lang.SecurityException: Location mode is disabled for the device
10-31 16:19:56.216 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-31 16:19:56.216 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-31 16:20:09.541 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4404, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -481
10-31 16:20:09.541 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
10-31 16:20:09.541 0 0 E vote : name[BATT_FCC], client[LGE_POWER_CLASS_FCC_VOTER,1], enabled[1], val[1000]
10-31 16:20:09.541 0 0 E vote : name[BATTCHG_SUSPEND], client[LGCC_EN_VOTER,1], enabled[0], val[0]
10-31 16:20:09.541 0 0 E vote : name[BATTCHG_SUSPEND], client[STORE_MODE_EN_VOTER,2], enabled[0], val[0]
10-31 16:20:09.541 0 0 E vote : name[USB_SUSPEND], client[STORE_MODE_USB_EN_VOTER,2], enabled[0], val[0]
10-31 16:20:29.221 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
Here is some more:
10-31 16:21:38.622 10126 10148 E libEGL : Driver indicates EGL 1.5 support, but does not have a critical API
10-31 16:21:38.739 905 937 E ANDR-PERF-RESOURCEQS: Failed to reset optimization [2, 1]
10-31 16:21:38.740 905 937 E ANDR-PERF-RESOURCEQS: Failed to reset optimization [2, 1]
10-31 16:21:43.557 905 937 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-31 16:21:43.558 905 937 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [2, 2, 0]
10-31 16:22:09.540 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4408, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -358
10-31 16:22:09.541 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
10-31 16:22:22.518 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-31 16:22:22.518 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-31 16:22:37.783 0 0 E rmt_storage: INFO:rmt_storage_rw_iovec_cb: Write iovec request received for /boot/modem_fs1
10-31 16:22:37.783 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Calling Write [offset=0, size=2097152]for /boot/modem_fs1!
10-31 16:22:37.814 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Done Write (bytes = 2097152) for /boot/modem_fs1!
10-31 16:23:00.530 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
10-31 16:23:09.540 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4408, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -324
10-31 16:23:09.540 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
Aethera said:
Here is some output from 'logcat *:E' in case it is of interest:
10-31 16:19:38.753 5926 5926 E ActivityThread: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-31 16:19:40.586 905 937 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-31 16:19:41.778 959 1031 E QC-time-services: Lib:time_genoff_operation: Connection failed !!
10-31 16:19:41.783 959 1031 E QC-time-services: Lib:time_genoff_operation: Connection failed !!
10-31 16:19:42.002 10005 10005 E receiver.modul: Not starting debugger since process cannot load the jdwp agent.
10-31 16:19:42.143 455 455 E lowmemorykiller: Error writing /proc/7941/oom_score_adj; errno=22
10-31 16:19:43.218 10025 10025 E hbox:interacto: Not starting debugger since process cannot load the jdwp agent.
10-31 16:19:44.391 455 455 E lowmemorykiller: Error writing /proc/9412/oom_score_adj; errno=22
10-31 16:19:44.658 1144 1217 E KernelCpuSpeedReader: Failed to read cpu-freq: /sys/devices/system/cpu/cpu2/cpufreq/stats/time_in_state: open failed: ENOENT (No such file or directory)
10-31 16:19:44.675 1144 1214 E libprocessgroup: Error encountered killing process cgroup uid 99005 pid 9572: Permission denied
10-31 16:19:46.683 1144 1550 E LightsService: Light requested not available on this device. 2
10-31 16:19:47.629 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
10-31 16:19:51.008 1144 4213 E WifiService: Permission violation - getScanResults not allowed for uid=10086, packageName=com.google.android.gms, reason=java.lang.SecurityException: Location mode is disabled for the device
10-31 16:19:56.216 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-31 16:19:56.216 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-31 16:20:09.541 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4404, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -481
10-31 16:20:09.541 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
10-31 16:20:09.541 0 0 E vote : name[BATT_FCC], client[LGE_POWER_CLASS_FCC_VOTER,1], enabled[1], val[1000]
10-31 16:20:09.541 0 0 E vote : name[BATTCHG_SUSPEND], client[LGCC_EN_VOTER,1], enabled[0], val[0]
10-31 16:20:09.541 0 0 E vote : name[BATTCHG_SUSPEND], client[STORE_MODE_EN_VOTER,2], enabled[0], val[0]
10-31 16:20:09.541 0 0 E vote : name[USB_SUSPEND], client[STORE_MODE_USB_EN_VOTER,2], enabled[0], val[0]
10-31 16:20:29.221 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
Here is some more:
10-31 16:21:38.622 10126 10148 E libEGL : Driver indicates EGL 1.5 support, but does not have a critical API
10-31 16:21:38.739 905 937 E ANDR-PERF-RESOURCEQS: Failed to reset optimization [2, 1]
10-31 16:21:38.740 905 937 E ANDR-PERF-RESOURCEQS: Failed to reset optimization [2, 1]
10-31 16:21:43.557 905 937 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-31 16:21:43.558 905 937 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [2, 2, 0]
10-31 16:22:09.540 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4408, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -358
10-31 16:22:09.541 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
10-31 16:22:22.518 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-31 16:22:22.518 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-31 16:22:37.783 0 0 E rmt_storage: INFO:rmt_storage_rw_iovec_cb: Write iovec request received for /boot/modem_fs1
10-31 16:22:37.783 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Calling Write [offset=0, size=2097152]for /boot/modem_fs1!
10-31 16:22:37.814 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Done Write (bytes = 2097152) for /boot/modem_fs1!
10-31 16:23:00.530 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
10-31 16:23:09.540 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4408, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -324
10-31 16:23:09.540 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
Click to expand...
Click to collapse
Some of those errors are due to the massive amount of debug flags i disabled in the kernel (it still tries to load many of them up for some reason). Are you facing any bugs on the device so far? My H910 also prints many "errors" similar to these but it works just as fine as when it used Lineage's stock kernel, but i didn't test other variants so i don't know if this kernel works fine on them as well.
AShiningRay said:
Some of those errors are due to the massive amount of debug flags i disabled in the kernel (it still tries to load many of them up for some reason). Are you facing any bugs on the device so far? My H910 also prints many "errors" similar to these but it works just as fine as when it used Lineage's stock kernel, but i didn't test other variants so i don't know if this kernel works fine on them as well.
Click to expand...
Click to collapse
One thing I'm noticing is that the adb USB connection keeps breaking. I run 'adb shell' and it connects then after a few seconds disconnects. It never did this before.
EDIT: Now it stopped doing it. For a while it kept disconnecting but now it is staying connected.
Aethera said:
One thing I'm noticing is that the adb USB connection keeps breaking.
Click to expand...
Click to collapse
That's weird, some time ago when i started taking logs to debug the IR i managed keep running the adb logcat for quite a while with no problems whatsoever. Is there a certain amount of time that it takes to happen?
Edit: Oh, ok then. Might have been some random issue with adb's connection. If any other problem arises, do tell.
Unfortunately the phone is still crashing at random intervals (was happening before using this kernel).
10-31 19:17:56.642 0 0 E : Fatal error on the modem.
10-31 19:17:56.642 0 0 E : modem subsystem failure reason: sleep_target.c:305:.
10-31 19:17:56.647 0 0 E M-Notify: General: 8
Aethera said:
Unfortunately the phone is still crashing at random intervals (was happening before using this kernel).
10-31 19:17:56.642 0 0 E : Fatal error on the modem.
10-31 19:17:56.642 0 0 E : modem subsystem failure reason: sleep_target.c:305:.
10-31 19:17:56.647 0 0 E M-Notify: General: 8
Click to expand...
Click to collapse
I see.. well, i tried searching this sleep_target.c that seems to be related in some manner to the problem in the kernel directory but there is no file with such a name. It could be something ROM-related, but i can't rule that out yet. Are there any other logs with more info about it?
AShiningRay said:
I see.. well, i tried searching this sleep_target.c that seems to be related in some manner to the problem in the kernel directory but there is no file with such a name. It could be something ROM-related, but i can't rule that out yet. Are there any other logs with more info about it?
Click to expand...
Click to collapse
I will try to do some various types of log filtering over the next day or so to see if I can get more information.
AShiningRay said:
I see.. well, i tried searching this sleep_target.c that seems to be related in some manner to the problem in the kernel directory but there is no file with such a name. It could be something ROM-related, but i can't rule that out yet. Are there any other logs with more info about it?
Click to expand...
Click to collapse
Looks like most if not all info about sleep_target.c is in Chinese. For example:
https://cloud-tencent-com.translate...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui
This one appears to have more detail: https://www-cnblogs-com.translate.g...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui
Aethera said:
Looks like most if not all info about sleep_target.c is in Chinese. For example:
https://cloud-tencent-com.translate...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui
This one appears to have more detail: https://www-cnblogs-com.translate.g...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui
Click to expand...
Click to collapse
Yeah, and the problem is... none of the files the article talks about are present in the kernel's source. tlmm_bsp for example also returns no results here. The fact that you log referenced a specific line from the file means it actually is present somewhere, but i'm not able to ascertain where exactly it is. I'll have to look at it in more details later.
AShiningRay said:
Yeah, and the problem is... none of the files the article talks about are present in the kernel's source. tlmm_bsp for example also returns no results here. The fact that you log referenced a specific line from the file means it actually is present somewhere, but i'm not able to ascertain where exactly it is. I'll have to look at it in more details later.
Click to expand...
Click to collapse
It is related to the Qualcomm MSM8996 system-on-chip. Perhaps it is embedded in the firmware. It appears there's some way to enable a debug mode for the modem and access various flags and voltage levels. This would explain why the error seems to be power-related. The device is trying to throttle the voltage to a "bottom current" which is a minimal current when the device is sleeping and for whatever reason it's crashing.
FYI here is a tool which can extract a MSM8996 modem image.
Aethera said:
Unfortunately the phone is still crashing at random intervals (was happening before using this kernel).
10-31 19:17:56.642 0 0 E : Fatal error on the modem.
10-31 19:17:56.642 0 0 E : modem subsystem failure reason: sleep_target.c:305:.
10-31 19:17:56.647 0 0 E M-Notify: General: 8
Click to expand...
Click to collapse
What variant? And did you ever crossflash?
Aethera said:
It is related to the Qualcomm MSM8996 system-on-chip. Perhaps it is embedded in the firmware. It appears there's some way to enable a debug mode for the modem and access various flags and voltage levels. This would explain why the error seems to be power-related. The device is trying to throttle the voltage to a "bottom current" which is a minimal current when the device is sleeping and for whatever reason it's crashing.
FYI here is a tool which can extract a MSM8996 modem image.
Click to expand...
Click to collapse
Ok, so it means that those files might actually be located inside the modem partition? I can see how a improper voltage can lead to kernel crashes (Undervolting the SoC's Kryo cores themselves too hard does the same thing, crashing the phone into either a black screen or a green one with some tracing info about the files that caused the problem), but how do we even go about testing if the modem is the one causing the problem? I'm not familiar with the modem images and structures at all so i doubt i would be able to fix those things, especially the voltages since we probably have no voltage table to determine which voltages are acceptable, too high, or too low.

Categories

Resources