hi all:
i download aosp kitkat4.4 source codes from google website. i compiled the code. i got the ROM.but when i flash the ROM to my device nexus 7(deb). it cannot boot.
from the log. i found that following error log. the sentence "couldn't find an OpenGL ES implementation" maybe cause the fatal question.
any advices is welcomed !
thank
brian
02-10 08:37:07.375: E/QCOMKeyMaster(17633): failed to load qseecom library
02-10 08:37:07.375: E/keystore(17633): could not open keymaster device in keystore (Operation not permitted)
02-10 08:37:07.375: E/keystore(17633): keystore keymaster could not be initialized; exiting
02-10 08:37:07.405: A/libEGL(17630): couldn't find an OpenGL ES implementation
02-10 08:37:07.405: A/libc(17630): Fatal signal 6 (SIGABRT) at 0x000044de (code=-6), thread 17630 (surfaceflinger)
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libacdbloader.so
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libcsd-client.so
02-10 08:37:07.575: E/MonoPipe(17632): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
Related
It seems that prelink error when compile. How to fixed it? Need prelink-linux-ds.map?
~/dream_sapphire $ adb logcat |grep prelink
- waiting for device -
E/HAL ( 143): Cannot load library: link_image[1962]: 104 could not load needed library 'libgps.so' for 'gps.sapphire.so' (reserve_mem_region[831]: OOPS: 104 prelinked library 'libgps.so' mapped at 0x45fb8000, not at 0xa9700000)
E/QualcommCameraHardware( 105): FATAL ERROR: could not dlopen liboemcamera.so: Cannot load library: reserve_mem_region[831]: OOPS: 105 prelinked library 'liboemcamera.so' mapped at 0x40c0c000, not at 0xa9400000
Dear All,
I am porting JB for QCom's msm8960 architecture (specifically for APQ8060A boards). I have downloaded several MSM8960
specific Code aurora releases and compiled them for msm8960. I have also downloaded Adreno user space drivers binaries.
After successful compilation when I run the Android image on the board, But a graphics related issue occurs.
'/system/bin/bootanimation' is not able to display anything on the screen and receives error while executing
eglSwapBuffers. Following are the Android 'main' logs for the error.
...
E/libEGL ( 515): eglApi.cpp : [eglSwapBuffers] dp->disp.dpy:1, s->surface:1
W/Adreno200-EGLSUB( 515): <GetBackBuffer:2172>: handle base address is NULL
W/Adreno200-ES20( 515): <gl2_surface_swap:43>: GL_OUT_OF_MEMORY
W/Adreno200-EGL( 515): <qeglDrvAPI_eglSwapBuffers:3477>: EGL_BAD_ALLOC
E/libEGL ( 515): [eglSwapBuffers] result = 0
...
W/Adreno200-EGLSUB( 515): <GetBackBuffer:2172>: handle base address is NULL
W/Adreno200-EGL( 515): <qeglDrvAPI_eglSwapBuffers:3477>: EGL_BAD_ALLOC
E/BootAnimation( 515): [BootAnimation.cpp][android] retval of eglSwapBuffers = 0
W/Adreno200-GSL( 515): <gsl_ldd_control:225>: ioctl code 0x40040921 (IOCTL_KGSL_SHAREDMEM_FREE) failed: errno 22 Invalid argument
...
Please let me know if any one of you has faced such problem.
I was doubting that Adreno user space drivers which I downloaded explicilty from QCom's website are not compatible with
the Android release, Therefore I tried with several Android releases but nothing works and shows the same error always.
Regards,
Nitin
Hi,
First of all looks like there isn't anyone started building Android Lollipop for i9500
So lets make this thread for discussing about all Lollipop ROMS
I wanted to say, i built for i9500 already
There are bugs
If i can see anything on screen, probably it will be the lockscreen.
AOSP Lollipop Recovery (recovery.img) - OK!
AOSP Lollipop Kernel+ramdisk (boot.img) - OK!
AOSP Lollipop System - [PVRSRV PROBLEM : PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address)]
Probably something related about including vendor files on build(because of AOSP)
doesn't load graphics/display driver
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: Couldn't connect to services
E/dex2oat ( 2811): Failed to open writable oat file /data/dalvik-cache/arm/[email protected]@boot.oat for /data/dalvik-cache/arm/[email protected]@boot.oat: File size of 0 bytes not large enough to contain ELF header of 52 bytes: '/data/dalvik-cache/arm/[email protected]@boot.oat'
E/dex2oat ( 2811): Failed to create image file /data/dalvik-cache/arm/[email protected]@boot.art
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 3929): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/hwcomposer( 3929): failed to open gralloc
E/SurfaceFlinger( 3929): composer device failed to initialize (Invalid argument)
E/SurfaceFlinger( 3929): ERROR: failed to open framebuffer (Not a typewriter), aborting
F/libc ( 3929): Fatal signal 6 (SIGABRT), code -6 in tid 3929 (surfaceflinger)
@intervigilium @Alberto96 @alvin14
doga.ozkaraca said:
Hi,
First of all looks like there isn't anyone started building Android Lollipop for i9500
So lets make this thread for discussing about all Lollipop ROMS
I wanted to say, i built for i9500 already
There are bugs
If i can see anything on screen, probably it will be the lockscreen.
AOSP Lollipop Recovery (recovery.img) - OK!
AOSP Lollipop Kernel+ramdisk (boot.img) - OK!
AOSP Lollipop System - [PVRSRV PROBLEM : PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address)]
Probably something related about including vendor files on build(because of AOSP)
doesn't load graphics/display driver
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: Couldn't connect to services
E/dex2oat ( 2811): Failed to open writable oat file /data/dalvik-cache/arm/[email protected]@boot.oat for /data/dalvik-cache/arm/[email protected]@boot.oat: File size of 0 bytes not large enough to contain ELF header of 52 bytes: '/data/dalvik-cache/arm/[email protected]@boot.oat'
E/dex2oat ( 2811): Failed to create image file /data/dalvik-cache/arm/[email protected]@boot.art
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 3929): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/hwcomposer( 3929): failed to open gralloc
E/SurfaceFlinger( 3929): composer device failed to initialize (Invalid argument)
E/SurfaceFlinger( 3929): ERROR: failed to open framebuffer (Not a typewriter), aborting
F/libc ( 3929): Fatal signal 6 (SIGABRT), code -6 in tid 3929 (surfaceflinger)
Click to expand...
Click to collapse
Maybe Alberto96 can help u?
I don't have time to work on a whole new android version. School is killing me.
Alberto96 said:
I don't have time to work on a whole new android version. School is killing me.
Click to expand...
Click to collapse
same.. :highfive:
i was sick and stayed home today, and that was my only free-time for building Android L
there should be a way to solve that :crying:
Thanks for all the effort that somehow have contributed or are contributing.
Does the issue at hand will be resolved only get if Samsung release the source code with the Lollipop? Or some work of developers already can fix (no need to be based on source code from Samsung)?
Too bad it's not 9505
Ill keep tabs on this tho. I'm mainly looking for a kernel+ramdisk for 5.0 on 9505 or similar S4s.
Maybe we can get some help from here or here ?
and it seems @BlaqueDroid is also trying to boot lollipop on i9500
@doga.ozkaraca long time man! You had disappeared from our forum for a very long time! Good to see you man!
As @Arch9 said, @BlaqueDroid needed help building it too! Maybe y'all can figure it out together!
Happy compiling ?
Sent from my GT-I9500 using Tapatalk
Hey man which kernel are u using to compile coz the CM one is throwing errors for
---------- Post added at 06:33 AM ---------- Previous post was at 06:31 AM ----------
rgshah3 said:
@doga.ozkaraca long time man! You had disappeared from our forum for a very long time! Good to see you man!
As @Arch9 said, @BlaqueDroid needed help building it too! Maybe y'all can figure it out together!
Happy compiling ?
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Hey man which Kernel are u using coz i tried the CM 11 one and the damn thing keeps throwing errors. Plz link me with the github Url
https://twitter.com/Antares__One this guy is doing some great stuff for our phone! Follow him for more updates #ThumbsUp
tkruijer said:
https://twitter.com/Antares__One this guy is doing some great stuff for our phone! Follow him for more updates #ThumbsUp
Click to expand...
Click to collapse
unfortunately it is for the I9505, I think the problem we have is different to boot
Even @gekkehenkie11 can help! He has done a lot of stuff recently to improve CM on our device! Maybe he can help boot CM12 on our device
Sent from my GT-I9500 using Tapatalk
@doga.ozkaraca
Welcome back buddy
Check this post
http://forum.xda-developers.com/showthread.php?p=56752819
Sent from my GT-I9500 using Tapatalk
I'm just found someone already build 5.0 for odroidxu in here, does we can do something with that? i'm trying to port it to i9500 but the result is nothing (stuck at boot)
Re-port a port is not a gold way ...
feraay said:
Re-port a port is not a gold way ...
Click to expand...
Click to collapse
Wut? re-port a port? what do you mean?
When can we expect fully working Android 5.0 based ROM?
ncenter said:
When can we expect fully working Android 5.0 based ROM?
Click to expand...
Click to collapse
31st Feb 2015
Sent from my GT-I9500 using Tapatalk
Yep, but unoficcial clean Lollipop ROM I mean.
ncenter said:
When can we expect fully working Android 5.0 based ROM?
Click to expand...
Click to collapse
How about you build it. And let us know? I heard its easy.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Download Links
CyanogenMod: download.crpalmer.org
Google apps addon:
Download: http://d-h.st/users/dhacker29/?fld_id=27426 (use latest lpmr1 gapps)
XDA:DevDB Information
CyanogenMod 12.1 for MondrianLTE (Unofficial), ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
ROM OS Version: 5.1.x Lollipop
Version Information
Status: No Longer Updated
Created 2015-04-18
Last Updated 2016-02-13
Reserved
Works fine
ROM works fine, made a dirty flash from CM12.
No problems at all.
http://review.cyanogenmod.org/#/c/95004/2
hopefully merged soon (already in cm12 since late march..just noticed recently in cm12 builds in mms.apk...should have known by looking at the history for the cm12 version)
EDIt
One thing though
Email exchange (hotmail etc) app has a repeated error popup during sync..this is from 4/17 build and also today's 4/18...was not the case till 4/16..noticed the apk file size has changed (not sure what..but it starts giving error popups during sync...pretty irritating as have to somehow get it to stop the sync to stop the popup...using the cm12.1 email apk 5.82mb from 4/16 or earlier fixes the issue)
cm12 not having such issues,.at least from 4.16 to 4/18 no email.apk file size changes..no sync issues
Edit attached mixer file to address earpiece echo for other caller not speakerphone echo for other caller.. change zip in extension to xml.. not a zip file..put in system etc folder permissions 644
Does miracast work with this build? I know CM started enabling the feature, but it didn't work when I last tried it with my SM-T315. Thank you for your answer.
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
TWRP 2.8.5.0 here. Any later version will work as well.
Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP
vrl13 said:
Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP
Click to expand...
Click to collapse
Thanks!
There's a donate link in my profile but I prefer not to clutter up useful information with extra donate links...
My PayPal is [email protected].
Beer uploaded: 7UG08116JF1461945
Thanks again!
Sent from my SM-T325 using Tapatalk
Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app
mackenzie121 said:
Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Hello,
I'm having no issue with both 2.4 and 5ghz wifi in my home.
Sounds like a router problem though.. can your other devices pick your wifi without a hitch?
Maybe it would help using a fixed IP, in case you are using DHCP now.
Regards.
Sent from my SM-T325 using Tapatalk
RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
I used TWRP 2.8.6.0. I already flashed several nightlies on this tablet, no issues.
---------- Post added at 10:41 PM ---------- Previous post was at 10:26 PM ----------
Is the changelog the same of the nightlies for "MONDRIANWIFI"? Thanks
Is it support cifs ?
Device encryption doesn't work. Build 20150507
Log:
Code:
D/Cryptfs ( 247): unmounting /data succeeded
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 247): Loading keymaster app failed
E/Cryptfs ( 247): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 247): Failed to init keymaster
F/libc ( 247): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 316 (vold)
F/libc ( 247): Unable to open connection to debuggerd: Connection refused
W/vold ( 316): type=1400 audit(0.0:190): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:190): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:190): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:190): item=0 name="/vendor/firmware/keymaster/keymaster.mdt"
W/auditd ( 314): type=1320 audit(0.0:190):
W/vold ( 316): type=1400 audit(0.0:191): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:191): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:191): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:191): item=0 name="/firmware/image/keymaste.mdt"
W/auditd ( 314): type=1320 audit(0.0:191):
W/vold ( 316): type=1701 audit(0.0:192): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=u:r:vold:s0 reason="memory violation" sig=11
I/Vold ( 8391): Vold 2.1 (the revenge) firing up
D/Vold ( 8391): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 8391): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 8391): Check if PFE is activated on Boot
E/Cryptfs ( 8391): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 8391): Error getting crypt footer and key
I see, that file /vendor/firmware/keymaster/keymaster.mdt exists:
# ls -la /system/vendor/firmware/keymaster/keymaster.mdt
lrw-r--r-- root root 2015-05-07 07:04 keymaster.mdt -> /firmware/image/keymaste.mdt
# ls -la /firmware/image/keymaste.mdt <
-r--r----- system drmrpc 12892 2014-11-13 05:32 keymaste.mdt
Any ideas how to fix it? Thanks.
crpalmer said:
CyanogenMod
Click to expand...
Click to collapse
f2fs support?
I am waiting for 10 minutes, hanging on the logo
Alexey71 said:
f2fs support?
I am waiting for 10 minutes, hanging on the logo
Click to expand...
Click to collapse
Try again with today's build and let me know.
crpalmer said:
Try again with today's build and let me know.
Click to expand...
Click to collapse
For me :
cm-12.1-20150523-UNOFFICIAL-mondrianlte.zip work fine but
cm-12.1-20150527-UNOFFICIAL-mondrianlte.zip and cm-12.1-20150528-UNOFFICIAL-mondrianlte.zip don't work : hanging on the logo
27-28 build not work (ext4-f2fs)
26 build work ext4
Builds 0527 and 0528 does not boot; instead, causes shutdown of the tab.
[msm8939][meizu][camera]dlopen failed: could not load library "libcam.meiyan.so" need
Hello,
Could you please help me?
Platform:meizu m1note msm8939
I ported from flyme to miui.
The camera has problem.
I got the error:
dlopen failed: could not load library "libcam.meiyan.so" needed by "camera.msm8916.so";
caused by cannot locate symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl" referenced by "libcam.meiyan.so"...
About symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl",
I found it at:
m463c/rom/update/system $ g CBeautyShot
Binary file ./lib/libarcsoft_beauty_shot.so matches
Binary file ./lib/libcam.meiyan.so matches
And I push them to my phone.
But I still get the error.
Who can help me? Thank you very much.
I have been debugging for several days.
01-02 08:17:52.901 I/libmdmdetect( 351): Found internal modem: modem
01-02 08:17:52.901 E/QC-QMI ( 272): qmi_client [272]: unable to connect to server, errno=[2:No such file or directory], attempt=1
01-02 08:17:52.901 E/QC-QMI ( 351): qmi_client [351]: unable to connect to server, errno=[2:No such file or directory], attempt=1
01-02 08:17:52.901 I/ThermalEngine( 288): Sensor:tsens_tz_sensor3:80000 mC
01-02 08:17:52.941 E/HAL ( 276): load: module=/system/lib/hw/camera.msm8916.so
01-02 08:17:52.941 E/HAL ( 276): dlopen failed: could not load library "libcam.meiyan.so" needed by "camera.msm8916.so"; caused by cannot locate symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl" referenced by "libcam.meiyan.so"...
01-02 08:17:52.941 E/CameraService( 276): Could not load camera HAL module
01-02 08:17:52.941 I/mediaserver( 276): ListenService instantiated
01-02 08:17:52.941 V/ListenService( 276): instantiate entered
01-02 08:17:52.941 V/ListenService( 276): getInstance entered, mNumInstances currently 0
Eismog
my-mail:[email protected]
Is there anyone who can help me?