Speakers Device Dont Show This Dialog Again
[ROM][testing][suez] Lineage-16.0 [13 April 2022]
- Thread starter ggow
- First engagement
ggow
Recognized Developer
- February 28, 2014
- 4,073
- 10,866
- #1
/* * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the warning app failed. * Please do some research if you take any concerns well-nigh features included * in the products you discover here before flashing it! * Yous are choosing to brand these modifications. */ - EVEN More than IMPORTANT: This ROM only works on devices using the bootloader hack. See <<< Hither >>> to unlock your devices.
- IMPORTANT: Practice not update Magisk via the Magisk Director App, your device will enter a bootloop if y'all do. Instead update Magisk via TWRP only. If yous do this by accident and then information technology is recoverable past just flashing the latest version of the ROM again (with gapps etc as required). This volition be stock-still in a later update.
Rules
- Please search the thread before asking questions
- Please endeavour to stay on topic, I know it's not always possible
- When reporting bugs please postal service a logcat and/or dmesg where possible
Lastest TWRP version
- 3.half dozen.1-ix.0
Downloads
- Google Drive
Source Lawmaking
Thanks
- @k4y0z and @xyz` for the bootloader hack
- @k4y0z for the initial kernel
- LineageOS
ggow
Recognized Programmer
- Feb 28, 2014
- iv,073
- ten,866
- #2
TBC
- [ fixed ] USB-OTG Ethernet
- [ fixed ] TWRP: MTP access
- [ fixed ] TWRP: Stock-still USB-OTG
- [ info ] Added android.hardware.opengles.aep.xml permissions
thirteen April 2022
- [ fixed ] Terminal input via apps and adb beat out
12 April 2022
- [ kernel ] Up-streamed to 3.eighteen.140
- [ kernel ] Enable per user storage quota
- [ kernel ] Optimized build flags for Cortex-a53
- [ kernel ] Boeffla Wakelock Blocker Commuter v1.ane.0
- [ kernel ] Enable some TCP congestion algorithms
- [ kernel ] Westwood Default TCP congestion algorithm
- [ kernel ] Sdcardfs v2.0
- [ info ] Remove aptX bluetooth libraries for now
- [ info ] Mount /system sectionalisation early-mountain style
- [ info ] Add vendor security patch
06 April 2022
- [ stock-still ] Set up KernelUidCpuTimeReader errors
- [ info ] Revert audio HIDL from 2.0 to 4.0 back to ii.0 - our drivers aren't ready for this
- [ info ] Put storage permissions strength close on the todo listing
- [ info ] Chrome browser works
- [ info ] Jelly browser works
- [ info ] WeDo lego app works
Show Further History
ggow
Recognized Developer
- Feb 28, 2014
- four,073
- 10,866
- #3
- [ fixed ] Bluetooth works
- [ fixed ] Audio works
- [ fixed ] Internal storage isn't attainable from any app
- [ done ] Sensors working
- [ stock-still ] Touch on sounds are working
- [ done ] Examination audio format playback - mp3 working
- [ done ] Tested video playback with NewPipe which is working
- [ fixed] WiFi betoken forcefulness not working
- [ washed ] Back up aptX-HD encoder for bluetooth
- [ fixed ] No adb during kicking
- [ fixed ] WiFi working
- [ fixed ] Navbar icon abuse
- [ stock-still ] Wallpaper abuse
- [ fixed ] Laggy graphics
- [ fixed ] High cpu usage
- [ fixed ] DRM non working
- [ stock-still ] Hardware OMX (for the most office)
- [ stock-still ] Wired headphones not working
- [ done ] Enable OTG USB for ethernet
- [ stock-still ] Youtube black screen with audio
- [ stock-still ] MtkOmxCore crash
- [ stock-still ] Battery showing wrong capacity - reported here
- [ fixed ] "There'south an internal problem with your device." dialog
- [ stock-still ] SIM menu prompt
- [ fixed ] Chrome cannot admission internal storage
- [ stock-still ] Poor WiFi throughput (potential cause of choppy video playback)
- [ fixed ] Disney app crashing (more info hither)
- [ fixed ] Speakers standing to play while headphones are plugged in
- [ fixed ] Cannot switch wifi on after storage encryption enabled
- [ concord ] Bluetooth not working properly - can't see outcome here
- [ fixed ] Magisk update by app
- [ fixed ] Storage permission issues (cause of some apps crashing)
- [ done ] Upstreamed kernel
- [ todo ] Gapps > pico causing non enough infinite error
- [ todo ] Youtube black screen with audio
- [ todo ] LiveDisplay not working
- [ todo ] Mirrorcast not working
- [ todo ] Voice help MIC not working
- [ todo ] Multi-user not working
- [ todo ] TWRP: USB-OTG non working
- [ todo ] Navbar trouble when keyboard is in horizontal style
- [ todo ] Playing videos over SMB failure later on thirty min (more info here)
- [ todo ] Can't connect to hidden WiFi networks
- [ todo ] Lego app not working (more info here)
- [ todo ] Cameras not working (more info here)
- [ todo ] SELinux
- [ todo ] Intermittent high idle cpu usage
- [ todo ] Investigate L1 widevine back up (L3 currently)
- [ todo ] Pass safetynet
- [ todo ] Device build fingerprinting
- [ todo ] Enable zram
- [ todo ] Device encryption (TWRP)
- [ todo ] Battery idle way
- [ todo ] Offline charging mode
- [ todo ] Low speaker volume
ggow
Recognized Developer
- Feb 28, 2014
- 4,073
- 10,866
- #4
12 Feb 2021
- Initial Release
- Post #2 contains change log
- Post #3 contains task listing
- Clean installation is required
- #5
But a few questions on build 12.february.2021:
DRM non working -> So netflix, amazon prime etc. isn´t working yet?
clean install required -> coming from lineage 12, manufactory reset and flashing subsequently will work? Or practice i have to wipe anything specific?
Cameras non working -> both of them ? Or perhaps just camcorder like in the early on versions of your Los12?
Wired headphones not working -> i approximate the headphone set from previous versions (Los-12,Los-14) does +not+ work on Lineage 16?
ggow
Recognized Developer
- Feb 28, 2014
- iv,073
- 10,866
- #6
Thanks for your great piece of work! Can´t await to try the new rom!But a few questions on build 12.february.2021:
DRM not working -> So netflix, amazon prime number etc. isn´t working all the same?
clean install required -> coming from lineage 12, factory reset and flashing later will work? Or do i have to wipe anything specific?
Cameras not working -> both of them ? Or perchance just camcorder like in the early versions of your Los12?
Wired headphones not working -> i guess the headphone set from previous versions (Los-12,Los-xiv) does +non+ piece of work on Lineage 16?
Try netflix and amazon and let me know if anything needs looking into, I have started a tasklist so we tin can add items there.
Manufacturing plant reset should suffice for make clean installation.
Cameras not working at all, more to come on this. I empathize why they are not working and it'due south not great news I know. I'll do a more detailed postal service on this.
The headphone set up from cm-14.1 might work or be adjustable to work on this rom. I am looking into a permanent solution for this.
- #7
i) Direct after get-go kicking, i get the error message "Your device encountered a problem. Please contact the manufacturer". Anyways, I can proceed after borer on OK.
ii) I can only flash pico Gapps, any parcel larger than that throw error 70 (Insufficient system space). In older builds, i was able to flash the nano package. The system partition (ane.v GB) should exist large enough to fit Gapps packages larger than pico.
three) The starting time banana prompts me to insert a SIM bill of fare, although this device does not have a SIM card slot.
4) The three softbuttons are cleaved, as shown in the film
Attachments
ggow
Recognized Developer
- Feb 28, 2014
- four,073
- 10,866
- #eight
I have faced these issues so far1) Directly afterwards offset boot, i go the error message "Your device encountered a trouble. Please contact the manufacturer". Anyways, I tin can proceed later tapping on OK.
two) I can simply flash pico Gapps, whatever bundle larger than that throw error 70 (Insufficient organisation infinite). In older builds, i was able to flash the nano bundle. The system partition (one.5 GB) should be big enough to fit Gapps packages larger than pico.
3) The start banana prompts me to insert a SIM card, although this device does not have a SIM bill of fare slot.
four) The three softbuttons are broken, as shown in the picture
Betoken 1: I forgot to mention this initial bulletin afterwards boot. This is due to fixing the persistent and repeated camera hal crash and the way in which I had to terminate that from happening, hopefully every bit a temporary measure out. I'll add this to the OP so everyone is aware.
Point 2 and iii: I'll add to the list
Point iv: already on the list todo
- #9
i) Hd videos in Youtube app are not working. The video either stops or i'thou just getting a blackscreen. 480p works.
2) The graphics is not very fluent and a bit laggy, peculiarly when opening apps and scrolling within them. Information technology seems that there's no graphics dispatch.
- #12
OMG, never e'er expected to see this on a 7th Gen HD10
Big thank you to ggow for bringing new life to our quondam "crap". The tablet isn't bad at all, so definitely worth to receive an update. Have to have a potable commencement to celebrate this, maybe will try the update next week. (I'm all the same on Amazon stock version, so I'll have to unlock first)
- #13
In regards to supersu, I take figured out why information technology will not agree root access. For some reason it fails to obtain a root user account.
Error stderr: null, stdout: aught, exit_value: 1 according to root checker, that is the only issue now. I have managed, I think, to rewrite or remove the scripts or lines of script in the files that lineage superuser uses. I'm non certain why information technology's doing this though. Flashing in twrp but causes a neverending boot animation. @ggow that's where I came beyond the camera logs, because after rebooting from flashing, I still get an adb connexion and then I ran a logcat, but aside from the camera, I didn't find anything useful. I made sure the files have possessor root:root. I do know KingoRoot doesn't take an issue rooting. So the investigation continues.
- #fourteen
- #15
- #16
the issue for gapps is the system partition size later installing los 16, is set incorrectly, non a mounting issue. supersu dont work considering its non compatible and wont be, utilise magisk. the camera dont work due to a lack of proper drivers not to mention the coding is completly missing from xiv.1 and sixteen so dont bother trying to gear up information technology yourself unless your compiling a new rom. this is merely the start release and will get meliorate in fourth dimension. information technology boots and thats a beginning.I think the lack of infinite for gapps has to do with mounts. It sems things are confused to an extent because technically zip is where it should exist. For example, on the lin14 rom, SuperSU won't work and that'south considering information technology tin't detect the kicking.img (information technology's looking in the spot where the img was prior to the unlock hack). I don't know why it won't work as a system install though.I got init.d to finally work (lineage uses their own so you take to write a script in /organization/etc/init and modify a line in init.cm.rc (in root directory) considering lineage disables androids init.d I recollect that's where some of the issues are and part of why SuperSU doesn't work (superuser.rc).
ggow
Recognized Developer
- Feb 28, 2014
- 4,073
- 10,866
- #17
@daniel_hk fabricated a good mail service on understanding this:
REF : https://forum.xda-developers.com/t/rom-7-1-2_r36-27jan2018-lineageos-xiv-1-custom-roms.3513466/
Relevant Excerpt of the data
III. The Camera
Afterwards my first ROM was out, the most eye catching in the log would be the stack corruption in libcam.halsensor.and so.
11-24 21:53:55.967 490 490 F DEBUG : #08 pc 00017459 /system/lib/libcam.halsensor.so (_ZN12ImgSensorDrv13getResolutionEPP34ACDK_SENSOR_RESOLUTION_INFO_STRUCT+60) After some digging, I was pretty certain it was caused by the alignment (address sanitize) of struct addresses. The latest blob from Lenovo dev.1631 (also the latest for mt6752 devices) were congenital with gcc iv.9 Clang 3.six. Nougat now apply Clang 3.8 by default. Those blob already have alignment support in Clang 3.6 might have issues with the new Clang three.eight.
What is address alignment? In brusque, a 32 fleck processor can handle 32 bit at a time. It would be a easier for the annals to locate memories in 32 bits (iv bytes) cells (aligned). If the head or tail for a block of memory is non aligned, extra code would required to separately handle those loose ends. The new clang compiler would fill leading bytes with its own algorithm to brand the pointer or variable aligned. Why is ImgSensorDrv::getResolution() being "affected"? The statement of it is a pointer to ACDK_SENSOR_RESOLUTION_INFO_STRUCT. Its definition can exist found in the kernel. It is a struct of an array of pointers to another struct. The source from Mediatek use straight reference to the address of struct variables all the time. This is inappropriate in sense of address alignment. Early compilers didn't handle alignments and won't accept problem with that. Newer compiler would employ its own algorithm to marshal the structs and pointers. I guess Clang iii.6 didn't handle the above circuitous struct every bit statement well. Nougat linker and loader are all built with Clang 3.8. Local variables are allocated at load time which might exist handled differently. Thus a call to ImgSensorDrv::getResolution() would cause the stack abuse.
** Those interested may read this article for detail. **
1. Work around
Using older blobs built by gcc 4.eight or earlier might work. Jiayu S3'south AOSP were using those erstwhile blobs. I'grand new to K3-note. I don't think I have the patience and experience to test all the existing blobs. That's the chief reason I uploaded the terminal ii test ROM. Trying blobs and hoping some combination would piece of work is passive. Stlport is also obsolete for some time now. I rather deal with the problem direct. 
2. The solution
Without the source, building the whole hulk is impossible. Even if we take the source from other devices, those custom parameters are unique to each image sensor. It'due south impossible to guess or back engineer...
If we tin change the mode ImgSensorDrv::getResolution() is beingness called or didn't affect the argument inside the function. It would avoid the crash. Unfortunately, the function need to fill a local struct within the ImgSensorDrv class. That means it is not seen outside ImgSensorDrv. The just mode is to supervene upon the whole ImgSensorDrv form. Fortunately, it is self contained. Nosotros can write a wrapper to supersede the ImgSensorDrv class only. The source from mt6735 or mt6595 are a chip different and obviously can't exist used straight. Most of the struct can exist cross referenced to the kernel source. There are two local sturct left unknown. I is for the commands sent to the kernel. The other is some info. nerveless from the kernel.
With the wrapper, the crash was gone but still no preview. I wrote a test HAL to dump the values in stock ROM. Guessing the values confronting the names was non a decent job. Fortunately, there were only a few differences. After nights of trial and mistake, I finally pulled everything together. Camera is working now! Video recording is still not working. Seems codec related. Some say information technology'due south not a problem "again". Hoping at that place will be some real solutions and helps shortly...
- #18
Understanding the Camera Issue :@daniel_hk made a good post on understanding this:
REF : https://forum.xda-developers.com/t/rom-7-1-2_r36-27jan2018-lineageos-fourteen-i-custom-roms.3513466/
Relevant Extract of the data
III. The Photographic camera
After my first ROM was out, the well-nigh eye catching in the log would be the stack corruption in libcam.halsensor.and then.Later report the source for mt6735, I found it was chosen inside the hulk libcam.halsensor.and so. In the function ImgSensorDrv::getResolution(), an ioctl() phone call was passed to the kernel. I was thinking it was caused past user space data handling in the kernel. After a serial of trials and dumping, I remarked that part of code from the kernel. The crash persisted. That means information technology was from the blob itself. I tried a shim library to supplant the role ImgSensorDrv::getResolution() but the event is the same. That means the callee was responsible.11-24 21:53:55.967 490 490 F DEBUG : #08 pc 00017459 /system/lib/libcam.halsensor.and so (_ZN12ImgSensorDrv13getResolutionEPP34ACDK_SENSOR_RESOLUTION_INFO_STRUCT+60)Later some digging, I was pretty sure it was acquired past the alignment (accost sanitize) of struct addresses. The latest blob from Lenovo dev.1631 (also the latest for mt6752 devices) were built with gcc iv.9 Clang 3.6. Nougat at present use Clang 3.8 by default. Those blob already have alignment support in Clang 3.half-dozen might accept issues with the new Clang three.8.
What is address alignment? In short, a 32 bit processor tin handle 32 fleck at a time. Information technology would be a easier for the register to locate memories in 32 bits (iv bytes) cells (aligned). If the head or tail for a cake of retentiveness is non aligned, extra lawmaking would required to separately handle those loose ends. The new clang compiler would fill up leading bytes with its ain algorithm to make the pointer or variable aligned. Why is ImgSensorDrv::getResolution() being "affected"? The argument of it is a pointer to ACDK_SENSOR_RESOLUTION_INFO_STRUCT. Its definition can be found in the kernel. Information technology is a struct of an assortment of pointers to some other struct. The source from Mediatek use directly reference to the address of struct variables all the time. This is inappropriate in sense of address alignment. Early compilers didn't handle alignments and won't take problem with that. Newer compiler would utilise its own algorithm to align the structs and pointers. I guess Clang 3.6 didn't handle the to a higher place complex struct as statement well. Nougat linker and loader are all built with Clang 3.8. Local variables are allocated at load time which might be handled differently. Thus a call to ImgSensorDrv::getResolution() would cause the stack corruption.
** Those interested may read this article for detail. **1. Work effectually
Using older blobs built by gcc 4.8 or earlier might piece of work. Jiayu S3's AOSP were using those one-time blobs. I'm new to K3-note. I don't call up I have the patience and experience to examination all the existing blobs. That's the main reason I uploaded the concluding ii test ROM. Trying blobs and hoping some combination would work is passive. Stlport is also obsolete for some time now. I rather deal with the trouble straight.2. The solution
Without the source, building the whole hulk is impossible. Even if we have the source from other devices, those custom parameters are unique to each image sensor. It's impossible to guess or back engineer...If nosotros tin change the mode ImgSensorDrv::getResolution() is being called or didn't touch the argument within the part. It would avoid the crash. Unfortunately, the function need to fill a local struct within the ImgSensorDrv grade. That means it is not seen outside ImgSensorDrv. The only style is to supplant the whole ImgSensorDrv class. Fortunately, it is self contained. Nosotros tin write a wrapper to replace the ImgSensorDrv class merely. The source from mt6735 or mt6595 are a scrap dissimilar and obviously can't be used directly. Near of the struct can be cross referenced to the kernel source. There are 2 local sturct left unknown. One is for the commands sent to the kernel. The other is some info. collected from the kernel.
With the wrapper, the crash was gone but still no preview. I wrote a test HAL to dump the values in stock ROM. Guessing the values against the names was not a decent job. Fortunately, in that location were only a few differences. After nights of trial and error, I finally pulled everything together. Camera is working now! Video recording is still not working. Seems codec related. Some say it's not a problem "once again". Hoping there volition be some real solutions and helps soon...
Yes after you set up that you'll get mediaserver libc fatal crashes equally I do in douglas.
TNSMANI
Senior Moderator / RC-RT Committee
- #19
Thread cleaned. Friends, please do non lose the focus of the thread. Discussions about other issues and multiple persons posting multiple ways of solving such bug etc make the thread cluttered. The OP is in that location and answering queries. Thank yous for understanding!
Similar threads
gregoryhatereast57.blogspot.com
Source: https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-06-apr-2022.4232785/
0 Response to "Speakers Device Dont Show This Dialog Again"
Post a Comment