because I have the following error
11-23 10:16:55.077: I / SurfaceFlinger (1246): SurfaceFlinger's main thread ready to run. Initializing graphics H / W. ..
11-23 10:16:55.077: E / HAL (1246): load: module = / system / lib / hw / gralloc.delta.so
11-23 10:16:55.077: E / HAL (1246): Can not load library: reloc_library [1285]: 1159 can not locate 'android_atomic_cmpxchg' ...
and looked on some websites and they say they have to compile the lib implementing this function.
it would help me to solve the problem of distorted screen I'm having with mini Xperia X10 ICS
This is hard work man...Im trying to create this driver but it fails
thank iTupTu
if you have trouble compiling, post your error, so we can solve, I can not compile, but at least I do research on the subject and try to help.
It worked well before .13 OTA update, after that I thought it was some bugs in .13 so I wait till .14 but still not being able to play a single RMVB file ....
I have tried to store it in different locations including micro-SD , SD card, USB drive and internal storage. None of it work for me...
I use MX Player and Mobo player in this case.
one thing I notice, when I turn on my prime (not from sleep) and immediately get into file manager and play the RMVB file, then it's working again until I leave the program and back to home, it won't play again...
wondering if anyone has the same problem as I do.
here is the picture when I encounter the error message
please help if u know how to fix that~ thx in advance
anyone has the same question?
Can you upload a sample?
very nice of u replying me =D
I am out and could not get a sample yet, but will upload more details of what rmvb I tried to play.....
I have a whole library in rmvb including animations, documentations and dramas which can't be play smoothly on my old laptop
wish that I can fix this problem asap
and thx very much for replying~
One of the rmvb file I use has this property which I copied from GOM player on my laptop~
*** VIDEO INFO ***
Input Type : YV12(RAW)
Input Size : 700 x 396
Output Type : YV12
Output Size : 700 x 396
FrameRate(Frame/sec) : 0.00 (25.00)
*** AUDIO INFO ***
SampleRate(Sample/sec) : 44100
BitRate(Bit/sample) : 16
Channels : 2
KBitRate(KBit/sec) : 0
another file I got this:
*** DIRECTSHOW FILTER LIST ***
1. Default DirectSound Device
2. VMR9 - Renderless mode
3. Gretech Audio
4. Gretech Video
5. MPC - RealVideo Decoder
6. MPC - RealAudio Decoder
7. MPC - RealMedia Splitter
8. Gretech File Stream
*** VIDEO INFO ***
Input Type : YV12(RAW)
Input Size : 720 x 408
Output Type : YV12
Output Size : 720 x 408
FrameRate(Frame/sec) : 11.89 (23.98)
*** AUDIO INFO ***
SampleRate(Sample/sec) : 44100
BitRate(Bit/sample) : 16
Channels : 2
KBitRate(KBit/sec) : 0
thank you for inspecting my problems! and hope this piece of info would help
I have the same problem. MX player simply cannot play any rmvb files. Mobo Player can only play some of my rmvb files.
Those are the same rmvb files that my Prime used to play perfectly on MX player.
Any help please?
hey!
I found a way to fix this ~
try move your rmvb files to yr prime's internal storage under /video
MX Player will automatically search these files and I manage to play those file just like what I can do before .13 update
but it only works when those file under /video .... this is kinda annoying but I can still watch some of my fav movie on prime for now... lol
Hello everybody!
i tried the CM7 on tassve and copperve devices and i noticed that both have the same bluetooth problem: it can send and receive files, it can connect to handfree devices, it can be controlled by BT devices (like car audio) but no audio streams via BT. Maybe is a common CM7 problem.. and maybe you already hear about that
Here some logcat
Code:
D/A2dpAudioInterface( 1404): A2dpAudioStreamOut::a2dp_start
D/A2dpAudioInterface( 1404): Trying to connect to BTLD (23)
D/A2dpAudioInterface( 1404): A2dpAudioStreamOut::a2dp_start: failed to connect
E/A2dpAudioInterface( 1404): a2dp_write socket not ready
E/bluetooth_ScoSocket.cpp( 1837): accept_work socket() failed: Protocol not supported
E/bluetooth_ScoSocket.cpp( 1837): accept_work socket() failed: Protocol not supported
...
E/bluetooth_ScoSocket.cpp( 1837): accept_work socket() failed: Protocol not supported
I tried to search some error reference, but i didn't find it..
Is there some docs about logcat error? or some docs about porting original module to CM ones?
I know there isn't a ready-solution, but i'm trying to dig for it..
thanks in advance
Fabrizio
Hi @darkholokaust, I am fairly new in Android world , so i might be wrong mate.
a2dp doesn't work with cm7, the reason is that drivers required were never published i guess. and no work-around as far as i know for cooperve devices,,,
Yes, but it seems strange to me that you can't use original one..
In fact on CM11 BT work perfect
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://img.xda-cdn.com/TNu3mia_OH11Njq-YZ8f1paMBGE=/https%3A%2F%2Fraw.githubuser
content.com%2FBootleggersROM%2FExtraStuff%2Fpasta%2Fthreadfiles%2F01-intro.png
Bootleggers ROM is an aftermarket firmware based on AOSP with some patches and fixes from LineageOS and various other projects. The idea is to bring custom features and some of the most useful apps on your device, with the goal of Making you feel like 家.
With an almost stable source, this ROM is also packed with some custom wallpapers (avaliable on ShishuWalls), ringtones, fonts, and themes to bring to your device into a more fresh look and give you always a good experience.
Also, we got our Telegram Group to talk about the ROM, share some love, ideas or even have fun with !
ROM FeaturesQS Rows and Colums
Volume Keys: Wake up, skip tracks and switch according to rotation
Show song album cover, visualizer and battery info on Lockscreen
Power Menu Items
Battery LED light settings
Suspend Actions: Make your device disable GPS and switch to 2G when you're not using it
AppOps: Manage your apps permissions in an advanced way
Recent Styles: Dig the new Pie Quickstep recents, go back to the classic layout or use the Android Go layout
Network icons: Show or hide the cross, switch between 4G or LTE, use the classic icon layout before Pie or toggle roaming icon too!
Small things that are added but we put it here so we can make this list a bit bigger and impress some people
Show app package at the bottom of app info
Sort apps by size
StatusbarTuner: Set icons to show in statusbar
Network Traffic
Show/Hide QS Tiles titles
LockscreenTuner: Change left/right shortcuts
Double Tap to Sleep on QS
Screen recording added on powermenu
Snooze Headsup notifications by sliding the popup up
App icon on Toast Messages
Disable summary/suggestions on Settings app
Allow 5 Display sizes instead of 3
Night Light settings
Roboto Condensed as Default Font
GoBold Light as Lockscreen font
Screen off animation
Custom clock and date tweaks
Light/Dark/Black/Shishu Themes
Custom QS tile background
System Animations
Log it for all your logging emergencies (needs root) and also, a copy log from an app FC
Clock customizations
App data/wifi restriction
THANKS! * Shishu (For being there)
* Ground Zero ROMs Team
* AOSPExtended
* ABC ROMs
* NitrogenOS
* AICP
* DirtyUnicorns
* Lukas Koller (Camera Roll dev)
* fxckingdeathwish (for the amazing photos for wallpaper/headers)
* OmniROM
* CyanogenMod/LineageOS
* PixelExperience
* PureNexus
* merothh
* Resurrection Remix
* AOSiP
* CrDroid
* CypherOS
* PureKat
* theimpulson
* MatiHalperin
* Project Xtended
* Pixeldust Project
* AquariOS
* Alejandro Ponce (Quetzal/Calypso dev)
* PixysOS
* The Memedo Testers team
* Every maintainer who decided to give our project a shot
* You for your interest on our project
Downloads GoogleDrive
GApps:[ARM 64 9.0] OpenGapps
Device Sources: Device Tree
Vendor
Kernel Rom Source: Source
BOOTLEGGERS Information
R0M OS Version:9.X PIE
byhenriquetc
hey man,
how is it going the battery life and camera?
Safenet is working?
zebruno said:
hey man,
how is it going the battery life and camera?
Safenet is working?
Click to expand...
Click to collapse
since recently devs have been using the stock oreo base for building roms, which means the camera works pretty well. as for the battery life, pie has a new battery saving system which adapts to your phone, so at first your battery won't be good, but after a week or so it'll be ok
What is the difference of the other rom you upload?
Thanks
Cricamju said:
What is the difference of the other rom you upload?
Thanks
Click to expand...
Click to collapse
and it's official is this patch with jan é volte fixed
Good ROM , exlent , good baterry life e customization , thanks @HenriqueCt
What about camera and usb tethering?
freeZbies said:
What about camera and usb tethering?
Click to expand...
Click to collapse
the camera is usable is the usb to detect just enter the twrp they still n Silves
allanph said:
Good ROM , exlent , good baterry life e customization , thanks @HenriqueCt
Click to expand...
Click to collapse
Thanks =)
luffyhhuu said:
the camera is usable is the usb to detect just enter the twrp they still n Silves
Click to expand...
Click to collapse
Usb tethering hasn't anything to do with twrp, I think you didn't get my point.
About the camera I'd like to know how "usable" it is. Any bugs so far?
hey i have a question, although the 3 random boot animation feature is kinda neat, i dont like it, can i simply flash my own boot animation and use just that?
freeZbies said:
Usb tethering hasn't anything to do with twrp, I think you didn't get my point.
About the camera I'd like to know how "usable" it is. Any bugs so far?
Click to expand...
Click to collapse
camera seems to work fine for me, nothing much to complain about
If this rom is Oficial, why it isn´t on the bootleggers site?
Why this ROM supported no root?
Exanneon said:
camera seems to work fine for me, nothing much to complain about
Click to expand...
Click to collapse
Video recording doesn't- no error in stock Camera app but file is not saved. The same for Google Camera. MotoCamera can be installed but doesn't work- crash when taking a picture or when switching to video mode
EDIT:
OoenCamera reports camera error when trying to record a video
gen_scheisskopf said:
Video recording doesn't- no error in stock Camera app but file is not saved. The same for Google Camera. MotoCamera can be installed but doesn't work- crash when taking a picture or when switching to video mode
EDIT:
OoenCamera reports camera error when trying to record a video
Click to expand...
Click to collapse
surprisingly, it also doesnt work on footej. have any ideas on how to fix it?
Not yet, I didn't have time to dig in the issue yet.
But at least camera is usable in WhatsApp (both camera and we code scanning)
Edit:
Got logcat (attached) from Snap when recording a video. Unfortunately there are some quite serious (IMHO) errors:
Code:
01-13 14:45:22.927 27454 27454 W System.err: java.lang.IllegalArgumentException: Could not find tag for key 'org.quic.camera2.customhfrfps.info.CustomHFRFpsTable')
01-13 14:45:22.927 27454 27454 W System.err: at android.hardware.camera2.impl.CameraMetadataNative.nativeGetTagFromKeyLocal(Native Method)[...]
Panorama mode may not work also:
Code:
1-13 14:45:22.939 27454 27454 E PanoramaCapture: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/system/priv-app/Snap/Snap.apk"],nativeLibraryDirectories=[/system/priv-app/Snap/lib/arm64, /system/lib64, /system/vendor/lib64, /system/lib64, /system/vendor/lib64]]] couldn't find "libjni_panorama.so"
01-13 14:45:22.939 27454 27454 D ChromaflashFilter: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/system/priv-app/Snap/Snap.apk"],nativeLibraryDirectories=[/system/priv-app/Snap/lib/arm64, /system/lib64, /system/vendor/lib64, /system/lib64, /system/vendor/lib64]]] couldn't find "libjni_chromaflash.so"
01-13 14:45:22.940 27454 27454 D BlurbusterFilter: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/system/priv-app/Snap/Snap.apk"],nativeLibraryDirectories=[/system/priv-app/Snap/lib/arm64, /system/lib64, /system/vendor/lib64, /system/lib64, /system/vendor/lib64]]] couldn't find "libjni_blurbuster.so"
And it looks that Snap has only access to low resolution codecs:
Code:
01-13 14:45:22.957 27454 27454 W SnapCam_SettingsManager: HFR is not supported for this resolution java.lang.IllegalArgumentException: Size 1920x1080 does not support high speed video recording
01-13 14:45:22.966 27454 27454 E SnapCam_SettingsManager: Codec = 1, capabilities: mMinFrameWidth = 176 , mMinFrameHeight = 144 , mMaxFrameWidth = 352 , mMaxFrameHeight = 288
01-13 14:45:22.966 27454 27454 E SnapCam_SettingsManager: Codec = 3, capabilities: mMinFrameWidth = 176 , mMinFrameHeight = 144 , mMaxFrameWidth = 352 , mMaxFrameHeight = 288
And it seems that mp4 can't be created:
Code:
01-13 14:45:23.008 27454 27454 D SnapCam_CaptureModule: init
01-13 14:45:23.015 27454 27454 D SnapCam_SettingsManager: isZslSupported=true
01-13 14:45:23.023 27454 27454 D RenderScript HIDL Adaptation: IRenderScriptDevice::getService()
01-13 14:45:23.031 27454 27454 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-13 14:45:23.063 27454 27454 D RenderScript HIDL Adaptation: IRenderScriptDevice::getService() returned 0x7579743200
01-13 14:45:23.063 27454 27454 D RenderScript HIDL Adaptation: HIDL successfully loaded.
01-13 14:45:23.087 683 27240 W CameraSource: camera recording proxy is gone
01-13 14:45:23.088 683 2722 D MPEG4Writer: Video track stopping. Stop source
01-13 14:45:23.088 683 2722 D MPEG4Writer: Video track source stopping
01-13 14:45:23.089 683 27256 I MPEG4Writer: Received total/0-length (307/0) buffers and encoded 306 frames. - Audio
01-13 14:45:23.089 683 27256 I MPEG4Writer: Audio track drift time: 0 us
01-13 14:45:23.098 683 27253 E MPEG4Writer: The number of recorded samples is 0
01-13 14:45:23.099 683 27253 E MPEG4Writer: Dumping Video track's last 10 frames timestamp and frame type
01-13 14:45:23.099 683 27253 E MPEG4Writer:
01-13 14:45:23.099 683 27253 W MPEG4Writer: 0-duration samples found: 1
01-13 14:45:23.099 683 27253 W MPEG4Writer: 0-duration samples found: 1
01-13 14:45:23.099 683 27253 I MPEG4Writer: Received total/0-length (0/0) buffers and encoded 0 frames. - Video
01-13 14:45:23.102 27454 27454 I .lineageos.snap: type=1400 audit(0.0:28621): avc: denied { open } for uid=10043 path="/dev/kgsl-3d0" dev="tmpfs" ino=13063 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
It's ben a while since last time I dug into logcat, if I'm not right please correct me.
Full logcat from ~6sec video recording is attached
gen_scheisskopf said:
Not yet, I didn't have time to dig in the issue yet.
But at least camera is usable in WhatsApp (both camera and we code scanning)
Edit:
Got logcat (attached) from Snap when recording a video. Unfortunately there are some quite serious (IMHO) errors:
Panorama mode may not work also:
And it looks that Snap has only access to low resolution codecs:
And it seems that mp4 can't be created:
It's ben a while since last time I dug into logcat, if I'm not right please correct me.
Full logcat from ~6sec video recording is attached
Click to expand...
Click to collapse
Thanks
lucki1000 said:
Why this ROM supported no root?
Click to expand...
Click to collapse
support yes
Googuis said:
If this rom is Oficial, why it isn´t on the bootleggers site?
Click to expand...
Click to collapse
will still be
Hello, everyone
I'm trying to understand what's the problem with my mi pad 5 pro. There are a couple of problems which I'm trying to resolve.
First of all I can't install any firmware except V12.5.14.0.RKYCNXM. I was trying to install it using fastboot and recovery, official way. Everytime my tablet is freezed on miui logo and nothing more.
I don't know why but it works only on V12.5.14.0.RKYCNXM.
I also tried to install custom lineageOS 20.0 and it works but audio problem still exists.
The second problem is with audio. Everything is associated with audio (speakers, microphone, bluetooth) doesn't work. Recorder app crashes. Video in camera crashes. Video in browser is playing without sound. I can suppose that because of audio problem other firmwares can't be installed correctly.
I have some logs from tablet but google didn't help me with that
03-06 19:26:49.104 1805 7040 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
03-06 19:26:49.104 1805 7040 W AudioManager: updateAudioPortCache: listAudioPorts failed
03-06 19:26:49.143 689 10575 E sscrpcd : vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:596:Error 0xffffffff: apps_std getenv failed: ADSP_LIBRARY_PATH Unknown error -1
03-06 19:26:49.143 689 10575 W sscrpcd : vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:805: Warning: apps_std_fopen_with_env failed with 0x2 for /mnt/vendor/persist/sensors/registry/registry (No such file or directory)
03-06 19:26:49.143 689 10575 E sscrpcd : vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:1126::Error: 201: 0 == (nOpenErr = apps_std_fopen_with_env(ADSP_LIBRARY_PATH, ";", name, "r", &ps))
03-06 19:26:49.143 689 10575 E sscrpcd : vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:1145:Error 0x201: apps_std_stat: failed to stat /mnt/vendor/persist/sensors/registry/registry, file open returned 0x2 (No such file or directory)
If you have some thought about it please respond me. Thanks in advance
Hello @Vlady_32
Try factory reset after flashing them. Your device should be able to flash all Stock ROM for your device model. IMO if the issue persists, you should return the device.
How could you install recovery ROM? Does elish have custom recovery like TWRP? I found only AOSP recovery for elish which cannot flash recovery Stock ROMs.
I've successfully installed the last version of DEV firmware MIUI V13.1.22.11.21.DEV using Magisc and three dots way. But audio still doesn't work and the same errors in the log
AudioSystem::listAudioPorts error -19
Got any leads on how to solve the issue? I'm facing this exact problem too