CD Switcher requires [root].
{
"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"
}
If you are into IT or cautious or ever had a drive die, you know that sometimes you can't trust a hard drive. Need to resize a partition but can't do it while the system is running? Want a clean virus scan? We all need a good boot disk sometimes and now you can carry a bunch on your phone !
Like DriveDroid and similar products, this uses the gadget driver in the Linux kernel. This updated version should work on more devices and custom ROMs, but has had very little testing. It's Alpha-ware and I'll add more features later.
Install CD Switcher APK (yes, I wrote it) from here:
https://drive.google.com/file/d/1ZdSYIhs7pq8IrOZ4NBX4dzPSYP5tdeIh/view?usp=drivesdk
Now tap on any ISO file. It can be inside an email or on the web and it will download it. (Unfortunately, this is how it works with the OOS file manager, meaning it makes an extra copy, so using FX, pictured, is recommended). The system will ask how to open it. Select CD switcher and 'Always' and grant root when it asks.
The DriveDroid APK doesn't work on stock OOS. I've booted many CDs with this tool. You can change CDs with just a tap. Have fun with your 128GB!
EDIT: New version using better methods doesn't rely on OOS init.
Sweet! I have always wanted to be able to do this but I have not been able to ever get drivedroid to work! I can't wait to try it out and not have to carry around more than my phone and a usb cable
knightrider64 said:
Sweet! I have always wanted to be able to do this but I have not been able to ever get drivedroid to work! I can't wait to try it out and not have to carry around more than my phone and a usb cable
Click to expand...
Click to collapse
I've heard drivedroid works with other kernels but the UI is a nightmare so I would still rather use this. Let me know if you have any issues with it.
Sent from my ONEPLUS A3000 using Tapatalk
Great app, works fine. But how do you umount the iso?
Any chance to get vhd's to work? I have an external hard drive that boots CDs and vhd's. Would be great to have it all on my phone :good:
thomas_pieps said:
Great app, works fine. But how do you umount the iso?
Click to expand...
Click to collapse
You can't. Not really any need to since it mounts read only. You can unplug it at any time.
Sent from my ONEPLUS A3000 using Tapatalk
domsch1988 said:
Any chance to get vhd's to work? I have an external hard drive that boots CDs and vhd's. Would be great to have it all on my phone :good:
Click to expand...
Click to collapse
You could do a raw disk image such as created by "dd" (and name it with an ISO extension even though it isn't), but I'd have to do more work to enable write access. All the work is done by the kernel which wants a raw disk image.
Sent from my ONEPLUS A3000 using Tapatalk
Can whatever it writes to the system be unwritten? Would I be able to take and OTA update after using this if I removed it and the ISO files?
stevenswall said:
Can whatever it writes to the system be unwritten? Would I be able to take and OTA update after using this if I removed it and the ISO files?
Click to expand...
Click to collapse
No! Full OTA only. Its not about the changes made. Your /system partition is on an ext4 filesystem which is journalled. Every write changes metadata and the journal. Incremental OTAs generally will change data block by block, and there is no telling what blocks it will change. The ISO files and APK aren't on the system partition and won't affect anything.
There is an older version of this that doesn't write to the system partition at all, but you have to set the ISO with the cable unplugged and then plug in your USB. The moment you change USB in any way, such as turning on MTP, the oneplus init scripts will revert the configuration back to the default USB drivers. Turning the USB drivers ISO into a symlink is what lets it survive MTP being turned on and is minimally invasive and revertable, but it still modfies blocks in the filesystem. If you want the older/safe one I can put up the link, just know that MTP and this can't be on at once with the old one since OnePlus has a bug that keeps turning off MTP (same thing that reverts the ISO).
I'm actually pretty sure it will be safe, but I personally wouldn't chance it and am recommending against it. The best bet would be to make a Magisk module, but I'm planning on replacing Magisk with something of my own, so I can't really spend time on such a solution. Since you've already rooted, using full OTAs over incremental is generally the method most people use anyway and will be totally safe. A system update will set your ISO back to USB drivers, just set your new ISO with the app again and it will be fine.
Sent from my ONEPLUS A3000 using Tapatalk
Thanks! Why not publish it as open source on github and put it on F-Droid?
Is it possible to have a windows 10 iso to boot in uefi mode with this tool?
installed the app but can't see it in app drawer can't open it!
my mistake.
i tested it and it works but without boot option. can u enable the option to write on the image? not read only?
and i tried to mount a windows installation iso and it doesnt work properly. i want to connect the phone to usb and boot from it to install
windows and other operating systems... and use disk tools etc
what can i\u do? thanks!!!
How can I use this on AOSPA Because you say it only works with the OnePlus File Manager. I got the apk for that but I cant install it because it conflicts with the current file explorer from AOSPA built in, I cant remove it with System App Uninstaller. Any solutions?
lindahl85 said:
Is it possible to have a windows 10 iso to boot in uefi mode with this tool?
Click to expand...
Click to collapse
Yes
DJArielLB said:
my mistake.
i tested it and it works but without boot option. can u enable the option to write on the image? not read only?
and i tried to mount a windows installation iso and it doesnt work properly. i want to connect the phone to usb and boot from it to install
windows and other operating systems... and use disk tools etc
what can i\u do? thanks!!!
Click to expand...
Click to collapse
An ISO is read only. It can't be written to. I have mounted a Windows install ISO just fine. What was the error?
R3dRacer said:
How can I use this on AOSPA Because you say it only works with the OnePlus File Manager. I got the apk for that but I cant install it because it conflicts with the current file explorer from AOSPA built in, I cant remove it with System App Uninstaller. Any solutions?
Click to expand...
Click to collapse
Actually, it only worked on OnePlus phones because it needed the USB setup used on OnePlus.
Somehow this thread got unmarked and I missed all the responded. Sorry! The good news is that I have a new Alpha version that should work on non-OnePlus devices and ROM's. This one doesn't touch the system partition either.
https://drive.google.com/file/d/1ZdSYIhs7pq8IrOZ4NBX4dzPSYP5tdeIh/view?usp=drivesdk
j03x2 said:
Thanks! Why not publish it as open source on github and put it on F-Droid?
Click to expand...
Click to collapse
Source is on my Github
Wait so how do I use this? I selected to open the ISO with the app, and I granted root, and it said iso location, etc.
I plugged it into my PC via USB but I'm not seeing a bootable option...
Edit now I see a usb item but it tells me grub incorrect filesystem or something
I'm trying an Ubuntu iso
NateDev said:
Wait so how do I use this? I selected to open the ISO with the app, and I granted root, and it said iso location, etc.
I plugged it into my PC via USB but I'm not seeing a bootable option...
Edit now I see a usb item but it tells me grub incorrect filesystem or something
I'm trying an Ubuntu iso
Click to expand...
Click to collapse
If you got to rub that it's actually booting off of the phone. It's up to the iso manufacturer to make sure that you can boot off a USB CD-ROM. So the phone is working, it's something in the iso that's messed up. Try a different ISO image
It doesn't seem to work on OOS beta 25 - app opens, reads something, tries to change usb mode (I can hear disconnect and connect sounds on Windows), returns to MTP and then closes itself.
Is this because of system being beta or custom kernel?
Code:
04-24 18:22:07.049 5923 9743 I ActivityManager: START u0 {act=android.intent.action.VIEW dat=content://pl.solidexplorer2.files/storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso typ=application/x-iso9660-image flg=0x10000001 cmp=systems.eddon.android.cdromswitcher/.MainActivity (has extras)} from uid 10091 pid 11517
04-24 18:22:07.065 560 560 E ANDR-PERF-MPCTL: hint lookup failed
04-24 18:22:07.067 5923 9743 E ANDR-PERF-JNI: com_qualcomm_qtiperformance_native_perf_io_prefetch_start
04-24 18:22:07.079 5923 9743 E ANDR-PERF-JNI: gIOPHAl initialized
04-24 18:22:07.079 5923 9743 E ANDR-PERF-JNI: gIOPHAl calling iopstart
04-24 18:22:07.079 559 559 E ANDR-IOP: IOP HAL: Received pkg_name = systems.eddon.android.cdromswitcher pid = -1
04-24 18:22:07.094 5923 6352 D RestartProcessManager: Duration is too short, ignore : 861 in pl.solidexplorer2
04-24 18:22:07.097 560 560 E ANDR-PERF-MPCTL: hint lookup failed
04-24 18:22:07.097 5923 6352 D RestartProcessManager: Update Total Launch Times :systems.eddon.android.cdromswitcher
04-24 18:22:07.097 5923 6352 D RestartProcessManager: updateSelf : systems.eddon.android.cdromswitcher, size : 13
04-24 18:22:07.098 5923 6352 D RestartProcessManager: Increase Total Launch Time : systems.eddon.android.cdromswitcher, times : 6, index : 12
04-24 18:22:07.098 5923 6352 D RestartProcessManager: Last Running Package : systems.eddon.android.cdromswitcher , start time 1524586927097
04-24 18:22:07.132 11826 12327 D TextDisplay: URL: /storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso
04-24 18:22:07.132 11826 12327 D TextDisplay: Using scheme content
04-24 18:22:07.133 11826 12327 D TextDisplay: Using filename: /storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso
04-24 18:22:07.133 11826 12327 I writeToSystem: Starting root commands
04-24 18:22:07.137 11826 12327 I suwait : Aquiring root!
04-24 18:22:07.162 468 12330 D Magisk : su: request from client: 22
04-24 18:22:07.162 468 12330 D Magisk : su: request from uid=[10176] (#1)
04-24 18:22:07.163 468 12330 D Magisk : su_db: query policy=[2]
04-24 18:22:07.164 468 12330 D Magisk : su: waiting child: [12331]
04-24 18:22:07.164 12331 12331 D Magisk : su: child process started
04-24 18:22:07.166 12331 12331 D Magisk : su: argc=[3]
04-24 18:22:07.166 12331 12331 D Magisk : su: argv[0]=[su]
04-24 18:22:07.166 12331 12331 D Magisk : su: argv[1]=[-]
04-24 18:22:07.166 12331 12331 D Magisk : su: argv[2]=[root]
04-24 18:22:07.166 12331 12331 D Magisk : su: pts_slave=[]
04-24 18:22:07.167 12331 12331 D Magisk : su: use namespace of pid=[12328]
04-24 18:22:07.186 11517 11535 D OpenGLRenderer: endAllActiveAnimators on 0xbb759b00 (SEGridView) with handle 0xd1a199a0
04-24 18:22:07.200 6682 6682 I GoogleInputMethod: onFinishInput() : Dummy InputConnection bound
04-24 18:22:07.200 6682 6682 I GoogleInputMethod: onStartInput() : Dummy InputConnection bound
04-24 18:22:07.204 5923 6361 I ActivityManager: Displayed systems.eddon.android.cdromswitcher/.MainActivity: +99ms
04-24 18:22:07.394 12332 12332 W ADebug : Failed to get property persist.sys.media.traces
04-24 18:22:07.405 12332 12332 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
04-24 18:22:07.580 12189 12262 I NetworkController.MobileSignalController(2): showDisableIcon:false
04-24 18:22:07.798 5923 6541 I SettingsState: [PERSIST START]
04-24 18:22:07.850 5923 7879 I OpenGLRenderer: Initialized EGL, version 1.4
04-24 18:22:07.850 5923 7879 D OpenGLRenderer: Swap behavior 2
04-24 18:22:08.069 12332 12332 D AndroidRuntime: Calling main entry com.android.commands.am.Am
04-24 18:22:08.099 12332 12332 D AndroidRuntime: Shutting down VM
04-24 18:22:08.138 11826 12327 I suwait : I am root
04-24 18:22:08.138 11826 12327 D powrite-send: cat /sys/class/android_usb/android0/functions
04-24 18:22:08.158 5923 6524 D DebugKeepScreenOn: Acquiring screen wakelock due to Window{a0aa7c u0 Toast}
04-24 18:22:08.340 11826 12327 I powrite#: mtp,mass_storage,hid
04-24 18:22:08.340 11826 12327 D powrite-send: echo 0 >/sys/class/android_usb/android0/enable
04-24 18:22:08.441 7726 12141 E MtpServer: request read returned -1, errno: 5
04-24 18:22:09.077 560 625 E ANDR-PERF-OPTSHANDLER: perf_lock_rel: updated /sys/class/scsi_host/host0/../../../clkscale_enable with 1
04-24 18:22:09.077 560 625 E ANDR-PERF-OPTSHANDLER: return value 2
04-24 18:22:09.541 11826 12327 D powrite-send: echo '/storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso' >/sys/class/android_usb/android0/f_mass_storage/lun/file
04-24 18:22:09.743 11826 12327 D powrite-send: cat /sys/class/android_usb/android0/f_mass_storage/lun/file
04-24 18:22:09.945 11826 12327 D powrite-send: echo 1 >/sys/class/android_usb/android0/enable
04-24 18:22:10.123 5923 5923 W WindowManager: removeWindowToken: Attempted to remove non-existing token: [email protected]
04-24 18:22:10.146 6665 6665 D HeadsetPhoneState: Enter onSignalStrengthsChanged
04-24 18:22:10.146 11826 12327 I writeToSystem: All DONE! SUCCESS!
04-24 18:22:10.146 6665 6665 D HeadsetPhoneState: Exit onSignalStrengthsChanged
04-24 18:22:10.150 5923 6549 V UsbDeviceManager: USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=22690, ACTION=change, USB_STATE=DISCONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
04-24 18:22:10.151 12189 12262 I NetworkController.MobileSignalController(1): showDisableIcon:false
04-24 18:22:10.238 5923 6549 V UsbDeviceManager: USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=22691, ACTION=change, USB_STATE=CONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
04-24 18:22:10.240 5923 6359 D UsbDeviceManager: broadcasting Intent { act=android.hardware.usb.action.USB_STATE flg=0x31000000 (has extras) } extras: Bundle[{host_connected=false, connected=true, unlocked=false, config_changed=false, mtp=true, configured=false}]
04-24 18:22:10.263 7726 7726 W libc : Unable to set property "sys.usb.ffs.mtp.ready" to "1": error code: 0x18
04-24 18:22:10.264 5923 9743 I UsbDeviceManager: isUsbDataUnlocked: 0
04-24 18:22:10.310 5923 6549 V UsbDeviceManager: USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=22692, ACTION=change, USB_STATE=CONFIGURED, DEVPATH=/devices/virtual/android_usb/android0}
04-24 18:22:10.311 5923 6359 D UsbDeviceManager: broadcasting Intent { act=android.hardware.usb.action.USB_STATE flg=0x31000000 (has extras) } extras: Bundle[{host_connected=false, connected=true, unlocked=false, config_changed=false, mtp=true, configured=true}]
04-24 18:22:10.338 7726 7726 D MtpService: starting MTP server in MTP mode
04-24 18:22:10.534 5923 6524 D DebugKeepScreenOn: Releasing screen wakelock, obscured by Window{e3dd695 u0 systems.eddon.android.cdromswitcher/systems.eddon.android.cdromswitcher.MainActivity}
04-24 18:22:10.581 14627 14735 I PlayCommon: [373] com.google.android.play.b.h.e(263): Preparing logs for uploading
04-24 18:22:10.582 14627 14735 I PlayCommon: [373] com.google.android.play.b.h.e(267): No file ready to send
04-24 18:22:12.194 5923 6352 D RestartProcessManager: increase duration : 5090 for systems.eddon.android.cdromswitcher
04-24 18:22:12.196 560 560 E ANDR-PERF-MPCTL: hint lookup failed
04-24 18:22:12.196 5923 6352 D RestartProcessManager: Update Total Launch Times :pl.solidexplorer2
04-24 18:22:12.196 5923 6352 D RestartProcessManager: updateSelf : pl.solidexplorer2, size : 13
04-24 18:22:12.196 5923 6352 D RestartProcessManager: Increase Total Launch Time : pl.solidexplorer2, times : 14, index : 12
04-24 18:22:12.196 5923 6352 D RestartProcessManager: Last Running Package : pl.solidexplorer2 , start time 1524586932196
Related
On my Sony Xperia Z5 Compact, when trying to make the adb backup with shared option enabled it displays forever the message "Shared storage" on the screen for more than an hour. Finally I cancelled it because I guessed out it was wrong. This is a fragment of adb logcat:
----------------------------------------------------
1402 3109 V BackupManagerService: Requesting full backup: apks=true obb=true shared=true all=true system=false pkgs=[Ljava.lang.String;@874481f
[...]
1402 22074 D BackupManagerService: Binding to full backup agent : com.android.sharedstoragebackup
1402 22074 D BackupManagerService: awaiting agent for ApplicationInfo{c76bf85 com.android.sharedstoragebackup}
1402 1412 D BackupManagerService: agentConnected pkg=com.android.sharedstoragebackup [email protected]
1402 22074 I BackupManagerService: got agent [email protected]
1402 22074 I BackupRestoreController: Getting widget state for user: 0
1402 23361 D BackupManagerService: Calling doFullBackup() on com.android.sharedstoragebackup
22075 22086 I SharedStorageAgent: Backing up 1 shared volumes
22075 22086 I FullBackup: Unrecognized domain shared/0
22075 22075 I Process : Sending signal. PID: 22075 SIG: 9
[Porting] CANNOT LINK EXECUTABLE < /system/bin/ file>: cannot locate symbol < ... >
Hi.
I encountered a problem while trying to port AOSP Extended v. 4.1 (Android 7.1.2, kernel 3.10.65+, MTK 6753) on my device (VOYO Q101, 2GB/32GB, kernel 3.10.65+, MTK 6753).
After successfully started the booting process (after one week of research, and a stupid line in /system/build.prop: ro.setupwizard.enterprise_mode=1 which caused stucking at logo), I have managed to get a logcat via adb. LOG (it's 8MB)
It is booting.. and booting... forever. It is not stucked, nor bootlooping. It is just booting (the "Google dots" animations running forever).
I have attached the log. There are a lot of CANNOT LINK EXECUTABLE <....> cannot locate symbol < ... > referenced by <...> and also a lot of:
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Write 56 bytes to slot 0, CCCI_H(0x0)(0x38)(0x801D000F)(0x0)
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from FS device
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from slot 0, CCCI_H(0x0)(0x80)(0x801E000E)(0x0)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): CMPT File name:Z:/NVRAM/NVD_DATA/ULMH_000 opid_map:0x00000013 Flag:0x00000100 Offset:34 Whence:-229154332 Length:16384
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): O: [1010103F282D2C35](0x00000100): (7 1)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): F: 1: 1906 0
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): C: 1: 0
[What I did]
- just copying the kernel from stock ROM (tried also: stock kernel + stock ueventd.rc +/- stock fstab): all caused bootloop or even stucked at logo. Just kernel change works good (at least till the actual stage) .
- compared with old .rc files. No replaces needed (in my opinion)
- From system/build.prop file I have DELETED all lines from ADDITIONAL_BUILD_PROPERTIES section (especially ro.setupwizard.enterprise_mode=1) - which took me 4 DAYS !!! to understand why it was stucked at logo .
- tried with and without patching with init.d (from porting ROM's website)
- tried to put the stock binaries mentioned in errors <CANNOT LINK ...> (/system/bin/mtk_agpsd, xlog) - not booting at all (it even stucks at logo...). Should I try with stock linker.so lib(64) ? But I think it will not boot at all (It really can't).
I hope for your help . Thanks!
up
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.
{
"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.
{
"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