I have hcl me u1 tab with vimicro cortex A8 cpu;stock ICS 4.0.3,1ghz,1gb ddr3 ram,vivante Gc400 gpu,800*480 resolution,arm v7. can i used allwinnere A10 cortex A8 cpu cm x rom as base???
I am getting this error in logcat
couldnt find an eglconfig matching the screen format;egl querysurface :352 error 300d
call to opengl es api with no correct context(logged once per thread)
I solved this then.
after patching egl.cfg i got this error
"E/libegl eglgetdisplay 121 error 300c egl bad parameter
eglinitialize 137 error 3008 egl bad display
validate display 209 error 3008 egl bad display"
can anyone help with this??
full logcat http://pastebin.com/6thwJUXG
Sent from my GT-I5800 using Tapatalk 2
how did you patched egl.cfg?
Related
Please give me some hints. What I'm trying to accomplish is to port CM10 and 10.1 and kernel 3.4 to LG E400. E400 has CM9 but the kernel is old - 2.6. I'm using kernel 3.4 for LG L3 II which has the same hardware.
I've compiled CM 10 but when I boot it with 3.4 kernel, I have a blank screen. I looked at dmesg and logcat, but I didn't figure what went wrong. I tried to boot CM 10 with 2.6 kernel but I have the same issue. I even try to test the 3.4 kernel with CM9 and it's the same story.
Can you give me some tips, how to figure out what went wrong?
dmesg for CM 10 using kernel 3.4: http://pastebin.com/M4R5tixn
logcat for CM 10 using kernel 3.4: http://pastebin.com/qRKttGTY
dmesg for CM 9 using kernel 3.4: http://pastebin.com/nppGkKB0
Thanks.
Here are some logcats for CM 10, kernel 3.4:
a. with blobs extracted from phone running CM9: http://pastebin.com/NKeYgEBw
b. with some blobs from LG L5 and adreno drivers for JB 4.1 from qualcomm site: http://pastebin.com/6D4VQDRa
c. with software renderer: http://pastebin.com/rtfiZi5s
d. with some blobs from LG L5 and latest adreno drivers from qualcomm site: http://pastebin.com/bcC6KCwj
In b. it seems adreno libs are loaded, surfaceflinger is running, so why I can't see android boot logo? All I'm able to see is a white background.
Using software renderer I see nothing but a blank display too.
dmesg says: init: could not import file /system/etc/init.local.rc, might this be relevant? Init.rc and init.board.rc are from CM 9.
edit1:
Since it didn't boot after I flashed the rom, I used ramdisk from CM9 and kernel 3.4 packing that into a boot.img and using that to boot.
Maybe using the ramdisk from CM9 with CM10 is why I am having problems?
edit2:
It seems zygote is crashing and restarting. Probably because of faulty init.rc.
edit3:
I fixed zygote crashing, now I have this:
Code:
E/memalloc( 128): /dev/pmem: Failed to open pmem device: No such file or directory
E/memalloc( 128): /dev/pmem: failed to initialize pmem area
E/gralloc ( 128): gralloc failed err=No such file or directory
It's weird there's no /dev/pmem because I've compiled the kernel with CONFIG_ANDROID_PMEM=y.
edit 4:
in board-xxx.c there's this comment:
Code:
/*LGE_CHANGE_S[[email protected]]20121102:
*Migrating QCT patch to remove pmem and fmem support*/
Also, there's no other reference to pmem in the file. It seems LG removed support for pmem. How do I get around this? gralloc needs /dev/pmem and there's no /dev/pmem because LG patched the kernel...
Code:
E/memalloc( 130): /dev/pmem: Failed to open pmem device: No such file or directory
E/memalloc( 130): /dev/pmem: failed to initialize pmem area
E/gralloc ( 130): gralloc failed err=No such file or directory
W/GraphicBufferAllocator( 130): alloc(240, 320, 2, 00000b03, 0 ...) failed -2 (No such file or directory)
E/SurfaceFlinger( 130): GraphicBufferAlloc::createGraphicBuffer(w=240, h=320) failed (No such file or directory), handle=0x0
E/BufferQueue( 130): [<pid_249>] dequeueBuffer: SurfaceComposer::createGraphicBuffer failed
Should I try to patch board-xxx.c to use pmem or should I try to compile CM10 with ION support? If so, how do I enable ION support before compiling CM10? adreno drivers support ION?
It's enough to add TARGET_USES_ION := true to BoardConfigCommon.mk ?
I think hardware/qcom/display/* might use only pmem in CM10. For CM10.1 I had to replace hardware/qcom/display with the one in CM10 since I had tons of compile errors...
I really wish i knw watever u r saying above... i would lke to help. By d way thnx for such great work. I knw u ll solve out eventually.
Sent from my LG-E400 using xda app-developers app
Your kernel is the problem.
I run an acer iconia a500 dual-core 1ghz 1gb ram tegra 2 cpu. Gta sa doesn't work, it closes after social club screen. I heard only tegra 3 and above cpu is supported, true? If not, any solution? I'm running paid version also.
Anyone?
Her'es more info for anybody who can help, it looks like an error log file?
Code:
closing device handle (0x%x)
CUHL::WatchdogAddDeviceHandle: Out of memory
CUHL::WatchdogAddDeviceHandle: added (0x%x), size: %d
CUHL::WatchdogRemoveDeviceHandle: removed (0x%x)
CUHL::WatchdogRemoveDeviceHandle: could not find (0x%x)
/../lib/libImmEmulatorJ.soCUHL::Watchdog path to libImmEmulatorJ.so: %sCUHL::Watchdog tsp_version: %dCUHL::Watchdog tsp_version: %d is unknown. Exiting...Cannot open libImmEmulatorJ.so. Error: %sCUHLInitializeFromWatchdogCannot load CUHLInitializeFromWatchdog function. Error: %sImmVibeTerminate2Cannot load ImmVibeTerminate2 functionImmVibeCloseDeviceCannot load ImmVibeCloseDevice functionImmVibeGetDeviceCapabilityInt32Cannot load ImmVibeGetDeviceCapabilityInt32 function/proc/self/exe%s/CUHLpipeCUHL::WatchdogApp: Failed to Initialize ImmVibe
CUHL::WatchdogApp: Failed to get API version
CUHL::WatchdogApp: found TSP version=0x%x
CUHL::WatchdogApp: error parsing pipe data
VibeTonz����������������埧�皡槄H� X�
p葎@JS`h,� 4� <�! ��o<�4�,�D�瓑$��浴魻鼣魯鞌垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎垎GCC: (GNU) 4.6 20120106 (prerelease) GNUgold 1.10A,aeabi"5TE
,.shstrtab.interp.dynsym.dynstr.hash.rel.dyn.rel.plt.text.note.android.ident.ARM.exidx.ARM.extab.rodata.fini_array.init_array.preinit_array.ctors.dynamic.got.data.bss.comment.note.gnu.gold-version.ARM.attributes
[email protected]_x86_x64: / #
how can i fix it I'm using vga Nvidia geforce gtx 950m (4gb) and chip intel core i7, screen resolution is 1920x1080 :crying::crying::crying:
Try adding "nouveau.modeset=0" at the end of the "kernel ..." line in the menu.lst file inside the RemixOS folder via Windows or some other OS. (Assuming that you used the official installer)
Sent from my iPhone using Tapatalk
Hello guys, I have a problem with this box: the system partition was tempered with (they tried to remove root) and I want to flash a new rom to fix it.
I opened it to check the hardware but the manufacturer have shielded the wifi chipset so I can't read the numbers on it.
Dmesg says:
Code:
dhd_conf_set_chiprev: chip=0x4334, chiprev=3
And I found these files in etc/wifi/
p2p_supplicant_overlay.conf
wpa_supplicant.conf
Folder 40183
config.txt
fw_bcm40183b2.bin
fw_bcm40183b2_apsta.bin
fw_bcm40183b2_p2p.bin
fw_bcm4334b1_ag.bin
fw_bcm4334b1_ag_apsta.bin
fw_bcm4334b1_apsta.bin
fw_bcm4334b1_p2p.bin
nvram.txt
So it's a broadcom4334, right? Too bad I haven't found any rom that clearly states bcm 4334 or 40183 and s905x, except this
Full specification as read from the amazon page @ https://www.amazon.it/gp/product/B0788MX52X/
OS: Android 7.1.2
Bluetooth: 4.0
CPU: AmlogicS905X Quad Core Cortex A53 a 1.5 GHz 64 bit
GPU: Penta-core Mali-450MP
RAM: 2 GB DDR
ROM: 16 GB EMMC
Wifi: IEEE 802.11 a / b / g / n, Dual-Band 2.4G/5G
LAN: 10 / 100M, standard RJ-45
The Motherboard (Aida says it's p212) doesn't have an hidden button, unlike other boxes, but I can boot into recovery using a terminal emulator
Of course I tried reaching to goobangdoo but they haven't replied.
Edit: typos
Edit: updates
I want at least root the box, I found
deamonsu, su, su.bak in system/xbin
su in sbin
Rootchecker says root is not installed properly.
I have the UPDATE&BACKUP and I used it to install:
UPDATE-unSU-signed.zip > deletes nothing
SuperSU-v2.82-201705271822 > bad recovery error
Magisk-v16.0 > failed to find meta-inf/com/android/metadata in update package
Everything failed and I tried from recovery, same thing.
I can still return the box so I'm trying not to install twrp since I don't have the stock recovery.
I'm stuck.
I'm not sure if this is the right place for such an issue. I'm asking here because it seems like an issue with my device rather than the app, since I could not find similar issues being reported among people I know.
After a recent update to the game, it crashes randomly without any messages (not even "app has stopped working" message). I checked logcat and here is what I found. This is the last log I received using the CODM process id filter in logcat:
Code:
06-12 12:14:22.512 11132 12328 E memtrack: Couldn't load memtrack module
06-12 12:14:22.512 11132 12328 W android.os.Debug: failed to get memory consumption info: -1
I can provide a detailed logcat if anyone can help me find the issue.
What I have already tried:
Clear data & cache.
Change graphics settings in the app.
Reinstall the game (took the pain and did it twice already).
Had an OS update pending so did that too. Also, did the OS update using the full package and not an incremental package, just to be sure.
Any suggestions are welcome.
@nitheeshas
Minimum Requirements to Play Call of Duty Mobile on Android
OS: Android 4.3+.,
CPU: At least Snapdragon 625,
GPU: Adreno 506, and
RAM: 3 GB.
jwoegerbauer said:
@nitheeshas
Minimum Requirements to Play Call of Duty Mobile on Android
OS: Android 4.3+.,
CPU: At least Snapdragon 625,
GPU: Adreno 506, and
RAM: 3 GB.
Click to expand...
Click to collapse
As mentioned, I'm using a OnePlus 6T which already fulfil the requirements.