kernel:
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937
device:
https://github.com/yangyangnau/android_device_xiaomi_land
local_manifests and patchs:
https://github.com/yangyangnau/redmi3s-misc
Reserved
STATUS REPORT:
boot: almost OK
random freezing
random reboot
Reserved
Does it mean xiaomi hasn't release the kernel yet?
Sent from my Redmi 3 using Tapatalk
h4fiz said:
Does it mean xiaomi hasn't release the kernel yet?
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
Yeah! I'm porting linux kernel for redmi3s.
http://forum.xda-developers.com/redmi-3/development/port-linux-kernel-source-xiaomi-redmi3s-t3469965
yangyangnau said:
Yeah! I'm porting linux kernel for redmi3s.
http://forum.xda-developers.com/redmi-3/development/port-linux-kernel-source-xiaomi-redmi3s-t3469965
Click to expand...
Click to collapse
Wow, keep working on dev ?? so you do have a redmi 3s?? Cause i have a plan to buy redmi 3x in near future, so maybe i can help you testing the kernel
Sent from my Redmi 3 using Tapatalk
h4fiz said:
Wow, keep working on dev so you do have a redmi 3s?? Cause i have a plan to buy redmi 3x in near future, so maybe i can help you testing the kernel
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
Oh, NO, It's HELL.
If you think it's important to get sourcecode, don't jump to redmi3s/3x yet.
If you insist it, you are wellcome.
yangyangnau said:
Oh, NO, It's HELL.
If you think it's important to get sourcecode, don't jump to redmi3s/3x yet.
If you insist it, you are wellcome.
Click to expand...
Click to collapse
I'm not that hurry to get the source code, i can live with miui though, but if there is a faster rom builded from source then i'll move there ??? cause i really need fingerprint on it, and the the design that different from any other redmi 3 varian ???
Sent from my Redmi 3 using Tapatalk
@yangyangnau pm sent.
Very interesting! I've been away from Xiaomi for about 2 years... but decided to get the Redmi 3S as backup phone. Now running some Chinese CM 13 rom, but this looks promising.
Totally forgot about Xiaomi and the trouble surround kernel sources. I remember with the Mi2S we used a kernel build from scratch too for development. But it seems they do release stuff nowadays? Only not directly?
Robin>Hood said:
Very interesting! I've been away from Xiaomi for about 2 years... but decided to get the Redmi 3S as backup phone. Now running some Chinese CM 13 rom, but this looks promising.
Totally forgot about Xiaomi and the trouble surround kernel sources. I remember with the Mi2S we used a kernel build from scratch too for development. But it seems they do release stuff nowadays? Only not directly?
Click to expand...
Click to collapse
Xiaomi released some source, but redmi 3s doesn't get luck.
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
You're the best,
I also wrote a complaint letter today to them
Hi, I've used your device source code as base for my own port, but I updated most of the HAL drivers from stock QC files.
But I can't boot. I get stuck with an error "Too many open files". Did you ever had this bug ?
I also did my own kernel based of the LA.UM.5.3_RB1.1 It seam to be the most up to date for MSM8937.
You can have a look at my port here :
Kernel : https://github.com/supercairos/android_kernel_xiaomi_msm8937
Device : https://github.com/supercairos/android_device_xiaomi_land
Supercairos said:
Hi, I've used your device source code as base for my own port, but I updated most of the HAL drivers from stock QC files.
But I can't boot. I get stuck with an error "Too many open files". Did you ever had this bug ?
I also did my own kernel based of the LA.UM.5.3_RB1.1 It seam to be the most up to date for MSM8937.
You can have a look at my port here :
Kernel : https://github.com/supercairos/android_kernel_xiaomi_msm8937
Device : https://github.com/supercairos/android_device_xiaomi_land
Click to expand...
Click to collapse
copy from porting kernel thread:
About LA.UM.5.3-01110-8x37.0:
I just try to find a QAEP release which match the release date of Redmi 3S as much as possible. Nothing more.
About "too many open files":
My repo #deccaf5 (9.21.2016) can boot cm, but it need force reboot several times.
After that commit, the error same as yours. Sorry for my bad.
https://github.com/yangyangnau/andro...ce_xiaomi_land
A few of days ago, I'm try using my kernel and proprietary-files.txt with the repo below.
https://github.com/Silentlys/android_device_xiaomi_land
Clean the fake kernel header tree. Clean the malware (2345 stuff). Clean TWRP stuffs.
No luck. Just get black screen. Can't remember the error messages. Could be "too many open files".
I guess the proprietary-files.txt is a problem.
Thanks!
Might be
I will investigate more soon. I've tried to raise the Open file limit but doesn't seams to fix the issue.
About the Kernel Xiaomi based his SW on, it's probably LA.UM.5.1_rb1.4 (not sure what manifest exactly quite hard to test ) as it's the branch that Ardreno was build on (you can check the logs and see that at each app boot). I based mine on the lastest branch that support msm8937_64.
Supercairos said:
Might be
I will investigate more soon. I've tried to raise the Open file limit but doesn't seams to fix the issue.
About the Kernel Xiaomi based his SW on, it's probably LA.UM.5.1_rb1.4 (not sure what manifest exactly quite hard to test ) as it's the branch that Ardreno was build on (you can check the logs and see that at each app boot). I based mine on the lastest branch that support msm8937_64.
Click to expand...
Click to collapse
I don't think the kernel version is a big issue, but i will check it.
yangyangnau said:
I don't think the kernel version is a big issue, but i will check it.
Click to expand...
Click to collapse
Agreed
update:
https://github.com/Silentlys/android_device_xiaomi_land/issues/3
https://github.com/Silentlys/proprietary_vendor_xiaomi
we can update the proprietary-files.txt, and try to build CM soon.
Still can't boot CM-13.
[ 12.092118] surfaceflinger[425]: unhandled input address range fault (11) at 0x6e5f6570697012, esr 0x92000044
[ 12.092131] pgd = ffffffc07679f000
[ 12.092138] [6e5f6570697012] *pgd=0000000000000000, *pud=0000000000000000
[ 12.092148]
[ 12.092159] CPU: 7 PID: 425 Comm: surfaceflinger Tainted: G W 3.18.20-g5d5fa78-dirty #1
[ 12.092165] Hardware name: Qualcomm Technologies, Inc. MSM8937-PMI8950 QRD SKU1 (DT)
[ 12.092172] task: ffffffc078c6be80 ti: ffffffc075820000 task.ti: ffffffc075820000
[ 12.092180] PC is at 0x7fb5294fc8
[ 12.092186] LR is at 0x7fb5294fac
[ 12.092193] pc : [<0000007fb5294fc8>] lr : [<0000007fb5294fac>] pstate: 80000000
[ 12.092198] sp : 0000007ff6cb01b0
[ 12.092204] x29: 0000007ff6cb01d0 x28: 0000000000000000
[ 12.092213] x27: 0000000000000000 x26: 0000007fb5354048
[ 12.092223] x25: 0000007fb52f8060 x24: 00000055cbc274c9
[ 12.092232] x23: 00000055cbc26fb0 x22: 00000055cbc273e0
[ 12.092241] x21: 0000000000000004 x20: 00000055cbc273e0
[ 12.092250] x19: 00000055cbc27ea0 x18: 0000000000000000
[ 12.092260] x17: 0000000000000000 x16: 0000007fb7340a58
[ 12.092269] x15: 0000000000000007 x14: 0000000000000043
[ 12.092280] x13: 0000000000000004 x12: 0000000000000072
[ 12.092289] x11: 0000000000000007 x10: 7069702030313a6d
[ 12.092298] x9 : 00000055cbc27e40 x8 : 00000055cbc27fec
[ 12.092307] x7 : 0000000000000040 x6 : 0000000000000000
[ 12.092316] x5 : 0000000000000001 x4 : 0000000000000000
[ 12.092325] x3 : 0000000000000004 x2 : 0000000000000001
[ 12.092334] x1 : 0000007fb7347eb4 x0 : 756e5f6570697012
[ 12.092342]
[ 12.096796] init: Service 'surfaceflinger' (pid 425) killed by signal 11
[ 12.096828] init: Service 'surfaceflinger' (pid 425) killing any children in process group
Click to expand...
Click to collapse
If I do crazy thing as below, the backlight flashes.
Code:
chmod -R 777 /dev
and get logcat:
01-12 04:26:01.870 1738 1738 I gralloc : using (fd=19)
01-12 04:26:01.870 1738 1738 I gralloc : id = mdssfb_80000
01-12 04:26:01.870 1738 1738 I gralloc : xres = 720 px
01-12 04:26:01.870 1738 1738 I gralloc : yres = 1280 px
01-12 04:26:01.870 1738 1738 I gralloc : xres_virtual = 720 px
01-12 04:26:01.870 1738 1738 I gralloc : yres_virtual = 2560 px
01-12 04:26:01.870 1738 1738 I gralloc : bpp = 32
01-12 04:26:01.870 1738 1738 I gralloc : r = 0:8
01-12 04:26:01.870 1738 1738 I gralloc : g = 8:8
01-12 04:26:01.870 1738 1738 I gralloc : b = 16:8
01-12 04:26:01.871 1738 1738 I gralloc : width = 62 mm (294.967743 dpi)
01-12 04:26:01.871 1738 1738 I gralloc : height = 110 mm (295.563629 dpi)
01-12 04:26:01.871 1738 1738 I gralloc : refresh rate = 369.50 Hz
01-12 04:26:01.876 1738 1738 E SurfaceFlinger: hwcomposer module not found
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: EGL information:
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: vendor : Android
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: version : 1.4 Android META-EGL
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_swap_buffers_with_damage EGL_KHR_image EGL_KHR_image_base EGL_KHR_lock_surface EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_create_context EGL_KHR_surfaceless_context EGL_EXT_create_context_robustness EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable EGL_KHR_partial_update EGL_KHR_create_context_no_error
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: Client API: OpenGL_ES
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: EGLSurface: 8-8-8-8, config=0x55b063d2a0
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: OpenGL ES informations:
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: vendor : Qualcomm
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: renderer : Adreno (TM) 505
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: version : OpenGL ES 3.1 [email protected] ([email protected])
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: extensions: GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_half_float GL_OES_framebuffer_object GL_OES_rgb8_rgba8 GL_OES_compressed_ETC1_RGB8_texture GL_AMD_compressed_ATC_texture GL_KHR_texture_compression_astc_ldr GL_KHR_texture_compression_astc_hdr GL_OES_texture_compression_astc GL_OES_texture_npot GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_OES_texture_3D GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_QCOM_alpha_test GL_OES_depth24 GL_OES_packed_depth_stencil GL_OES_depth_texture GL_OES_depth_texture_cube_map GL_EXT_sRGB GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_EXT_texture_type_2_10_10_10_REV GL_EXT_texture_sRGB_decode GL_OES_element_index_uint GL_EXT_copy_image GL_EXT_geometry_shader GL_EXT_tessellation_shader GL_OES_texture_stencil8 GL_EXT_shader_io_blocks GL_OES_shader_image_atomic GL_OES_sample_variables GL_EXT_texture_border_clamp GL_EXT_multisampled_render_to_texture
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: GL_MAX_TEXTURE_SIZE = 16384
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: GL_MAX_VIEWPORT_DIMS = 16384
01-12 04:26:01.887 1738 1738 W GraphicBufferAllocator: alloc(720, 1280, 1, 20001a00, ...) failed -12 (Out of memory)
01-12 04:26:01.887 1738 1738 D GraphicBufferAllocator: Allocated buffers:
01-12 04:26:01.887 1738 1738 D GraphicBufferAllocator: 0x55b071f040: 3600.00 KiB | 720 ( 720) x 1280 | 1 | 0x20001a00
01-12 04:26:01.887 1738 1738 D GraphicBufferAllocator: 0x55b071f290: 3600.00 KiB | 720 ( 720) x 1280 | 1 | 0x20001a00
01-12 04:26:01.887 1738 1738 D GraphicBufferAllocator: Total allocated (estimate): 7200.00 KB
01-12 04:26:01.887 1738 1738 E : GraphicBufferAlloc::createGraphicBuffer(w=720, h=1280) failed (Out of memory), handle=0x0
01-12 04:26:01.887 1738 1738 E BufferQueueProducer: [FramebufferSurface] allocateBuffers: failed to allocate buffer (0 x 0, format 1, usage 536877568)
01-12 04:26:01.889 1738 1738 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x55b05b2550
01-12 04:26:01.931 501 501 I ServiceManager: Waiting for service AtCmdFwd...
01-12 04:26:01.962 1743 1743 I Dpps : static DppsServer *DppsServer::GetInstance(): DppsServer ref count increased to 1
01-12 04:26:01.962 1742 1742 F appproc : app_process: Unable to determine ABI list from property ro.product.cpu.abilist64.
01-12 04:26:01.962 1742 1742 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 1742 (app_process64)
01-12 04:26:01.962 1743 1743 I Dpps : InitPrimaryContextFeatures():265 Dpps feature enable properties are false, skipping primary feature context init
01-12 04:26:01.963 452 452 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
01-12 04:26:01.963 452 452 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
01-12 04:26:01.963 452 452 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
01-12 04:26:02.014 452 452 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-12 04:26:02.014 452 452 F DEBUG : CM Version: '13.0-20161007-UNOFFICIAL-land'
01-12 04:26:02.014 452 452 F DEBUG : Build fingerprint: 'Xiaomi/land/land:6.0.1/MMB29M/V7.5.9.0.MALCNDE:user/release-keys'
01-12 04:26:02.014 452 452 F DEBUG : Revision: '0'
01-12 04:26:02.014 452 452 F DEBUG : ABI: 'arm64'
01-12 04:26:02.014 452 452 F DEBUG : pid: 1742, tid: 1742, name: app_process64 >>> /system/bin/app_process64 <<<
01-12 04:26:02.014 452 452 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-12 04:26:02.023 452 452 F DEBUG : Abort message: 'app_process: Unable to determine ABI list from property ro.product.cpu.abilist64.'
Click to expand...
Click to collapse
Related
Ok so I was glancing through the logs and noticed the following. I'm assuming I'm not the only person with this issue so has anyone else noticed that opengl was not being initialized? Perhaps this would explain our strong reliance on optimizing Hero to run smoothly as opposed to letting the onboard graphics chip help do the rendering
I/SurfaceFlinger( 77): SurfaceFlinger is starting
I/SurfaceFlinger( 77): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/SurfaceFlinger( 77): pid 77 requesting gpu core (owner = -1)
W/SurfaceFlinger( 77): couldn't grant gpu core to pid 77
D/EGL ( 77): requestGPU returned -1
E/GLLogger( 77): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
I/SurfaceFlinger( 77): EGL informations:
I/SurfaceFlinger( 77): # of configs : 6
I/SurfaceFlinger( 77): vendor : Android
I/SurfaceFlinger( 77): version : 1.31 Android META-EGL
I/SurfaceFlinger( 77): extensions:
I/SurfaceFlinger( 77): Client API: OpenGL ES
I/EGLDisplaySurface( 77): using (fd=23)
I/EGLDisplaySurface( 77): id = msmfb
I/EGLDisplaySurface( 77): xres = 320 px
I/EGLDisplaySurface( 77): yres = 480 px
I/EGLDisplaySurface( 77): xres_virtual = 320 px
I/EGLDisplaySurface( 77): yres_virtual = 960 px
I/EGLDisplaySurface( 77): bpp = 16
I/EGLDisplaySurface( 77): r = 11:5
I/EGLDisplaySurface( 77): g = 5:6
I/EGLDisplaySurface( 77): b = 0:5
I/EGLDisplaySurface( 77): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 77): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 77): refresh rate = 60.00 Hz
shafty023 said:
Ok so I was glancing through the logs and noticed the following. I'm assuming I'm not the only person with this issue so has anyone else noticed that opengl was not being initialized? Perhaps this would explain our strong reliance on optimizing Hero to run smoothly as opposed to letting the onboard graphics chip help do the rendering
I/SurfaceFlinger( 77): SurfaceFlinger is starting
I/SurfaceFlinger( 77): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/SurfaceFlinger( 77): pid 77 requesting gpu core (owner = -1)
W/SurfaceFlinger( 77): couldn't grant gpu core to pid 77
D/EGL ( 77): requestGPU returned -1
E/GLLogger( 77): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
I/SurfaceFlinger( 77): EGL informations:
I/SurfaceFlinger( 77): # of configs : 6
I/SurfaceFlinger( 77): vendor : Android
I/SurfaceFlinger( 77): version : 1.31 Android META-EGL
I/SurfaceFlinger( 77): extensions:
I/SurfaceFlinger( 77): Client API: OpenGL ES
I/EGLDisplaySurface( 77): using (fd=23)
I/EGLDisplaySurface( 77): id = msmfb
I/EGLDisplaySurface( 77): xres = 320 px
I/EGLDisplaySurface( 77): yres = 480 px
I/EGLDisplaySurface( 77): xres_virtual = 320 px
I/EGLDisplaySurface( 77): yres_virtual = 960 px
I/EGLDisplaySurface( 77): bpp = 16
I/EGLDisplaySurface( 77): r = 11:5
I/EGLDisplaySurface( 77): g = 5:6
I/EGLDisplaySurface( 77): b = 0:5
I/EGLDisplaySurface( 77): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 77): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 77): refresh rate = 60.00 Hz
Click to expand...
Click to collapse
Very interesting point, I'd really like to see one of the more informed devs look at this. +1
this would definitelly help rosie if its not working already with all the effects in the widgets
RaiderX303 said:
this would definitelly help rosie if its not working already with all the effects in the widgets
Click to expand...
Click to collapse
I think its using software based rendering which means more cpu power to do the effects
shafty023 said:
I think its using software based rendering which means more cpu power to do the effects
Click to expand...
Click to collapse
but if opengl aint working then the cpu is doing all gpu work making the cpu do twice as much
Hmm, couldn't you test this by running an OpenGL or GPU intensive app (Doom?) on the Hero build. See if it differs significantly from the other builds.
KyleK29 said:
Hmm, couldn't you test this by running an OpenGL or GPU intensive app (Doom?) on the Hero build. See if it differs significantly from the other builds.
Click to expand...
Click to collapse
Maybe but you can't benchmark performance by saying "this seems faster" but that makes me wonder what the OGL logs are showing when you launch Doom, for instance.
Where are the logs saved?
Sirus20x6 said:
Where are the logs saved?
Click to expand...
Click to collapse
He's either using log collector or ddms (SDK tool)
uberingram said:
Maybe but you can't benchmark performance by saying "this seems faster" but that makes me wonder what the OGL logs are showing when you launch Doom, for instance.
Click to expand...
Click to collapse
Well, if OpenGL isn't running correctly, I'm sure the difference may just very well be noticeable.
Ever tried to play a game in software mode? Not pretty.
Wow. This could be why it's always been pretty slow. Hmmm, someone should PM JustAnotherCrowd and inform him about this, just in case he doesn't know.
So is I guess the question is, is there an easy way of enabling this.
maydaysos said:
So is I guess the question is, is there an easy way of enabling this.
Click to expand...
Click to collapse
good way of putting it
ccyrowski said:
He's either using log collector or ddms (SDK tool)
Click to expand...
Click to collapse
Ya I was using "adb logcat". So to find the error do this:
1) adb shell reboot
2) adb logcat
It will say waiting for device. Soon as the phone starts booting you'll see logs coming at you like there's no tomorrow. One of which will be that section that shows opengl not loading.
Sirus20x6 said:
Where are the logs saved?
Click to expand...
Click to collapse
The logs are not saved anywhere, they are sent to the console (linux term meaning if you connect to the syslog server you'll see debug messages scrolling like an IRC chatroom). You can view them with "adb logcat" but you'll have to have downloaded the free android 1.5 sdk in order to use that command. Once you download it, it's in the tools/ directory along with a bunch of other useful executables that anybody who wants to hack their phone will need.
ok well is there more to the log? when i look this up in google the explination for the error is just after the 60.00 Hz part
http://osdir.com/ml/android-porting/2009-04/msg00245.html
Sirus20x6 said:
ok well is there more to the log? when i look this up in google the explination for the error is just after the 60.00 Hz part
http://osdir.com/ml/android-porting/2009-04/msg00245.html
Click to expand...
Click to collapse
I have copybit.trout.so loaded so that is not the cause of the problem. Those modules are located at /system/lib/hw/
Here is what I have in my logs starting at the 60Hz part and down a couple lines
Code:
I/EGLDisplaySurface( 77): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 77): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 77): refresh rate = 60.00 Hz
I/SurfaceFlinger( 77): OpenGL informations:
I/SurfaceFlinger( 77): vendor : Android
I/SurfaceFlinger( 77): renderer : Android PixelFlinger 1.0
I/SurfaceFlinger( 77): version : OpenGL ES-CM 1.0
I/SurfaceFlinger( 77): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_direct_texture GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
W/HAL ( 77): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.msm7k.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.default.so error=Cannot find library
I don't believe overlay.*.so was ever compiled for the HTC Hero as it is not in the build. But since HAL is complaining about it AFTER opengl failed I don't think the two are related. Just my guess though
shafty023 said:
I have copybit.trout.so loaded so that is not the cause of the problem. Those modules are located at /system/lib/hw/
Here is what I have in my logs starting at the 60Hz part and down a couple lines
Code:
I/EGLDisplaySurface( 77): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 77): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 77): refresh rate = 60.00 Hz
I/SurfaceFlinger( 77): OpenGL informations:
I/SurfaceFlinger( 77): vendor : Android
I/SurfaceFlinger( 77): renderer : Android PixelFlinger 1.0
I/SurfaceFlinger( 77): version : OpenGL ES-CM 1.0
I/SurfaceFlinger( 77): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_direct_texture GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
W/HAL ( 77): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.msm7k.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.default.so error=Cannot find library
I don't believe overlay.*.so was ever compiled for the HTC Hero as it is not in the build. But since HAL is complaining about it AFTER opengl failed I don't think the two are related. Just my guess though
Click to expand...
Click to collapse
looking through my phone i don't see the overlays at all so i guess they weren't compiled. couldn't a developer take the missing overlays from a build that works and rebuild them to work on hero?
sorry to potentially burst your bubble, but here's my logcat from cyanogenized rogers (which runs ridiculously smooth, said to be comparable to ion):
Code:
I/SurfaceFlinger( 68): SurfaceFlinger is starting
I/SurfaceFlinger( 68): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/SurfaceFlinger( 68): pid 68 requesting gpu core (owner = -1)
W/SurfaceFlinger( 68): couldn't grant gpu core to pid 68
D/EGL ( 68): requestGPU returned -1
E/GLLogger( 68): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
I/SurfaceFlinger( 68): EGL informations:
I/SurfaceFlinger( 68): # of configs : 6
I/SurfaceFlinger( 68): vendor : Android
I/SurfaceFlinger( 68): version : 1.31 Android META-EGL
I/SurfaceFlinger( 68): extensions:
I/SurfaceFlinger( 68): Client API: OpenGL ES
I/EGLDisplaySurface( 68): using (fd=24)
I/EGLDisplaySurface( 68): id = msmfb
I/EGLDisplaySurface( 68): xres = 320 px
I/EGLDisplaySurface( 68): yres = 480 px
I/EGLDisplaySurface( 68): xres_virtual = 320 px
I/EGLDisplaySurface( 68): yres_virtual = 960 px
I/EGLDisplaySurface( 68): bpp = 16
I/EGLDisplaySurface( 68): r = 11:5
I/EGLDisplaySurface( 68): g = 5:6
I/EGLDisplaySurface( 68): b = 0:5
I/EGLDisplaySurface( 68): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 68): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 68): refresh rate = 60.00 Hz
W/HAL ( 68): load: module=/system/lib/hw/copybit.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/copybit.trout.so error=Cannot find library
I/SurfaceFlinger( 68): OpenGL informations:
I/SurfaceFlinger( 68): vendor : Android
I/SurfaceFlinger( 68): renderer : Android PixelFlinger 1.0
I/SurfaceFlinger( 68): version : OpenGL ES-CM 1.0
I/SurfaceFlinger( 68): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_direct_texture GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
W/HAL ( 68): load: module=/system/lib/hw/copybit.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/copybit.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/overlay.msm7k.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/overlay.default.so error=Cannot find library
I/sysproc ( 68): System server: starting Android runtime.
I/sysproc ( 68): System server: starting Android services.
I/SystemServer( 68): Entered the Android system server!
I/sysproc ( 68): System server: entering thread pool.
I/HtcBootAnimation( 68): mGifPath = /system/media/boot.gif
I/SystemServer( 68): Starting Power Manager.
I/SystemServer( 68): Starting Activity Manager.
I/SystemServer( 68): Starting telephony registry
I/SystemServer( 68): Starting Package Manager.
looks similar to me. even the parts with the copybit and overlay not found.
the interesting part is after the 60hz it does identify OpenGL ES-EM 1.0 along with the extensions available. does it show the same on Hero?
i dont think i can remember the article where i read it, but due to the limitations of portable devices, android does not initialize opengl at the gpu until an app specifically requests it, this is both for gpu and cpu gl rendering. the display elements are all software rendered through a simple frame buffer to conserve battery life, so having opengl on all the time would still yield no advantage, quite the opposite actually, as you'd be draining your battery for nothing.
Developers here :
deepss1
Aceximix
Requested developers to join the topic :
1) Karandeepdps
2) aj1234josh
3) prateek1992
4) Christianvari
Beta testers :
Yet to set beta testers.
PM me if you want to be a beta tester.
Only two beta testers.
Number of GB roms : 9
Number of ICS roms : 3 (camera not working)
Number of JB roms : 1 (with many bugs)
Aim - To solve ICS camera bug
Bugs solved -
Yet to solve any bugs.
Note :
1) Developers please do reserve posts for your contribution.
2) Also write your contribution for LG P690
3) For non P690 devs - If you want to develop for P690 make pm to me and get involved in development of P690.
There are many testers for ONet.
If you want you can buy us a beer
Contact me by mail or pm.
Email id - [email protected]
Reserved!!
Reserved!!
Direct to topic..:silly:
AS OF MY THIS LOG..I GUESS>>WE HAVE CAMERA HAL WORKING.. ANY FURTHUR IDEAS FROM YOU??
V/CameraHolder( 2101): open camera 0
I/CameraHAL( 2330): CameraHAL_GetCam_Info:
D/CameraHAL( 2330): CameraHAL_GetNum_Cameras: loading libcamera at 0xb000e5a8
I/CameraService( 2330): Opening camera 0
D/CameraHAL( 2330): qcamera_device_open: name:0 device:0x13e0c cameraId:0
D/CameraHAL( 2330): loading libcamera at 0xb000e5a8
D/QualcommCameraHardware( 2330): createInstance: E
I/QualcommCameraHardware( 2330): startCamera: camsensor name s5k5caga, flash 0
I/DEBUG ( 1482): #00 pc 0000b2f2 /system/lib/liboemcamera.so (isp3a_exit)
I/DEBUG ( 1482): #01 pc 000086f6 /system/lib/liboemcamera.so
I/DEBUG ( 1482): #02 pc 00008824 /system/lib/liboemcamera.so (cam_conf)
I/DEBUG ( 1482): 41628a28 a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a30 a771dc71 /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a3c a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a7c a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a8c a77086fb /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a94 a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a9c a7708829 /system/lib/liboemcamera.so
E/CameraHolder( 2101): fail to connect Camera
E/CameraHolder( 2101): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 2101): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 2101): at android.hardware.Camera.<init>(Camera.java:320)
E/CameraHolder( 2101): at android.hardware.Camera.open(Camera.java:280)
E/CameraHolder( 2101): at com.android.camera.CameraHolder.open(CameraHolder. java:131)
E/CameraHolder( 2101): at com.android.camera.Util.openCamera(Util.java:313)
E/CameraHolder( 2101): at com.android.camera.Camera$4.run(Camera.java:1246)
E/CameraHolder( 2101): at java.lang.Thread.run(Thread.java:856)
I/ServiceManager( 1477): service 'media.camera' died
W/Camera ( 2101): Camera server died!
V/camera ( 2101): surfaceChanged. w=320. h=427
I/ActivityManager( 1598): Displayed com.android.camera/.Camera: +2s851ms
I/CameraService( 2514): CameraService started (pid=2514)
E/CameraHAL( 2514): CameraHAL_GetNum_Cameras:
D/CameraHAL( 2514): CameraHAL_GetNum_Cameras: loading libcamera at 0xb000e5a8
D/CameraHAL( 2514): CameraHAL_GetNum_Cameras: numCameras:1
Click to expand...
Click to collapse
Samsung galaxy pop have camera working and also p500 which is almost same configured to our p690
Hope we developers will solve this camera bug early.
Just little guidance from p500 and galaxy pop developers may solve our camera bug. So looking forward to camera bug and that too without any donations
Something good....
Now you can find lg optimus net forum in this website ----->>
http://www.fesilo.com/forum/lg-optimus-net-p690
So from now ask developers to post ROMs here so its easy to find ROMs for Optimus Net....
Any news? Hope they help Onet p690, please samsung pop and p500 developers
Sent from my LG-P690 using xda app-developers app
Does somebody know where to find CUSTOM ROM for this tablet ?? http://t3.gstatic.com/images?q=tbn:ANd9GcTJMYTIWWdsgvZCPrAmGWqo4iLR2D6aYp3o1zBlKn8NL1gXgDJ2cg
Send you a PM.
For further help just ask me cause I have experience with those generic crap tablets
Sent from my shooteru using Xparent Green Tapatalk 2
gesange said:
ask me cause I have experience
Click to expand...
Click to collapse
EGLconfig cannot find config to draw on surface. I have got error:
D/AndroidRuntime( 83): CheckJNI is OFF
I/SurfaceFlinger( 82): SurfaceFlinger is starting
I/SurfaceFlinger( 82): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
I/gralloc ( 82): using (fd=10)
I/gralloc ( 82): id =
I/gralloc ( 82): xres = 800 px
I/gralloc ( 82): yres = 480 px
I/gralloc ( 82): xres_virtual = 800 px
I/gralloc ( 82): yres_virtual = 960 px
I/gralloc ( 82): bpp = 32
I/gralloc ( 82): r = 16:8
I/gralloc ( 82): g = 8:8
I/gralloc ( 82): b = 0:8
I/gralloc ( 82): width = 127 mm (160.000000 dpi)
I/gralloc ( 82): height = 76 mm (160.421051 dpi)
I/gralloc ( 82): refresh rate = 59.75 Hz
D/libEGL ( 82): loaded /system/lib/egl/libGLES_android.so
I/dalvikvm( 83): DexOpt: source file mod time mismatch (40fbbd60 vs 41115696)
D/dalvikvm( 83): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/libEGL ( 82): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 82): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 82): loaded /system/lib/egl/libGLESv2_mali.so
D/Kernel ( 0): <7>[ 6.270000] UMP<2>: New session opened
E/SurfaceFlinger( 82): couldn't find an EGLConfig matching the screen format
D/dalvikvm( 83): DexOpt: --- BEGIN 'core.jar' (bootstrap=1) ---
E/ ( 82): mali_surface* __egl_platform_create_surface_from_native_buffer(android_native_buffer_t*, egl_surface*, mali_base_ctx_type*):488 [EGL-ERROR] invalid buffer handle given (0x10110)
E/ ( 82): void __egl_platform_dequeue_buffer(egl_surface*):1234 [EGL-ERROR] Failed to create a surface from native buffer (0x10078)
F/libc ( 82): Fatal signal 11 (SIGSEGV) at 0x00000023 (code=1)
What to do with it?
Problem with EGL bpp=32bits does not match eglSurface: 5-6-5-0 = 16bits.
How to insert 8-8-8-8 to EGLconfig?
can you help me ?
gesange said:
Send you a PM.
For further help just ask me cause I have experience with those generic crap tablets
Sent from my shooteru using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
allwinner a13 softwinerEvb 4.0.4 7" MID
model number : softwinerEvb
android version : 4.0.4
baseband version : 1.5
kernel version : 3.0.8+ [email protected] #1 TueFeb 26 14:49:51 CST 2013
Build number : 713B7.V2.00.TZX.R01.eng.dan0308.0304
anyone help to upgrade?
peetyj said:
allwinner a13 softwinerEvb 4.0.4 7" MID
model number : softwinerEvb
android version : 4.0.4
baseband version : 1.5
kernel version : 3.0.8+ [email protected] #1 TueFeb 26 14:49:51 CST 2013
Build number : 713B7.V2.00.TZX.R01.eng.dan0308.0304
Click to expand...
Click to collapse
just curious to know any upgrade for this tablet?
because it can't connect when browsing sometimes
my tablet detail here:
MODE Q8 (A-1)
P:Q8-4.04-CZY-TZX0309-YY-8.0
ROHS
MODEL NUMBER Q8
ANDROID 4.04
BASEBAND VER 1.5
KERNEL VER 3.0.8 + [email protected] #1 Tue Feb 26 14:49:51 CST 2013
BUILD NUMBER 713B7.V2.00. TZX.R01.eng.gc0309.20130308
BOARD ID FIRMWARE TZX_713_83-16B
CHIPSET ALLWINNER A13 D2195CA-23C1
256 memory 1 camera
thanks
email ksuwanto8ksd gmail com
When I try to activate NFC it turns off again after 4 seconds.
Can someone tell me if this is software or hardware related?
Here is my logcat:
12-17 07:38:34.325 I/NfcService(1078): Enabling NFC
12-17 07:38:34.325 E/NfcAdaptation(1078): NfcAdaptation::Initialize: ver=NFCDROID_MI_422.10.0.15 nfa=NFA_MI_1.03.62+
12-17 07:38:34.325 I/BrcmNfcNfa(1078): NFC_TASK started.
12-17 07:38:34.325 E/NfcNciHal(1078): HaiInitializeLibrary: ver=NFCDROID_MI_422.10.0.15 nfa=NFA_MI_1.03.62+
12-17 07:38:34.325 I/USERIAL_LINUX(1078): USERIAL_Init
12-17 07:38:34.325 I/NfcNciHal(1078): HAL_NfcInitialize (): NFC_HAL_TASK id=0
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_dm_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=1, enable_cplt_mask=0x0
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=3, enable_cplt_mask=0x8
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_rw_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=6, enable_cplt_mask=0x48
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_ce_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=7, enable_cplt_mask=0xc8
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_ee_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=2, enable_cplt_mask=0xcc
12-17 07:38:34.325 I/BrcmNfcNfa(1078): LLCP - llcp_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): num_rx_buff = 9, rx_congest_start = 6, rx_congest_end = 4, max_num_ll_rx_buff = 2
12-17 07:38:34.325 I/BrcmNfcNfa(1078): max_num_tx_buff = 21, max_num_ll_tx_buff = 6
12-17 07:38:34.325 I/BrcmNfcNfa(1078): LLCP_RegisterServer (): SAP:0x1, link_type:0x2, ServiceName:<urn:nfc:sn:sdp>
12-17 07:38:34.325 I/BrcmNfcNfa(1078): LLCP_RegisterServer (): Registered SAP = 0x01
12-17 07:38:34.325 I/BrcmNfcNfa(1078): NFA_Enable ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): NFC_SetTraceLevel () new_level = 1
12-17 07:38:34.325 I/USERIAL_LINUX(1078): USERIAL_Open(): enter
12-17 07:38:34.325 I/USERIAL_LINUX(1078): USERIAL_Open() device: /dev/bcm2079x port=5, uart_port=0 WAKE_DELAY(20) WRITE_DELAY(20) POWER_ON_DELAY(0) PRE_POWER_OFF_DELAY(10) POST_POWER_OFF_DELAY(0)
12-17 07:38:34.345 I/USERIAL_LINUX(1078): USERIAL_Open(): exit
12-17 07:38:35.195 V/PanelView(900): animationTick called with dtms=0; nothing to do (h=858.0 v=-6750.0)
12-17 07:38:35.355 E/USERIAL_LINUX(1078): USERIAL_Write len = 4, ret = -1, errno = 5
12-17 07:38:35.425 W/InputMethodManagerService(772): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
12-17 07:38:35.435 V/PhoneStatusBar(900): setLightsOn(true)
12-17 07:38:37.365 E/BrcmNfcJni(1078): nfcManager_doInitialize: fail nfa enable; error=0x0
12-17 07:38:38.275 I/BrcmNfcNfa(1078): GKI TASK_DEAD received. exit thread 3...
12-17 07:38:38.475 W/NfcService(1078): Error enabling NFC
I have a same problem on S4 mini with the same error since 19-DEC:
BrcmNfcJni
nfcManager_doInitialize: fail nfa enable; error=0x0
Hello everyone,
Xiaomi hasn't released Redmi 3s land kernel to us. It's SHAME.(2016.09.28)
I want to run normal GNU/Linux OS on Xiaomi Redmi 3S.
So I am porting Linux kernel base on QAEP kernel and Redmi3 drivers.
My porting kernel version is 3.18.20.
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937
BASE ON:
* QAEP for msm8937:
Code:
lynx -dump -width 120 https://wiki.codeaurora.org/xwiki/bin/QAEP/release | grep msm8937
06.23.2016 LA.UM.5.3.1-01010-89xx.0 msm8937_64 LA.UM.5.3.1-01010-89xx.0.xml 06.00.01
06.10.2016 LA.UM.5.3-04410-89xx.0 msm8937_64 LA.UM.5.3-04410-89xx.0.xml 06.00.01
06.09.2016 LA.UM.5.3.1-00610-89xx.0 msm8937_64 LA.UM.5.3.1-00610-89xx.0.xml 06.00.01
06.07.2016 LA.UM.5.1-04210-8x37.0 msm8937_64 LA.UM.5.1-04210-8x37.0.xml 06.00.01
06.06.2016 LA.UM.5.3.1-00610-89xx.0 msm8937_64 LA.UM.5.3.1-00610-89xx.0.xml 06.00.01
05.31.2016 LA.UM.5.3-03710-89xx.0 msm8937_64 LA.UM.5.3-03710-89xx.0.xml 06.00.01
05.24.2016 LA.UM.5.3.1-00310-89xx.0 msm8937_64 LA.UM.5.3.1-00310-89xx.0.xml 06.00.01
05.15.2016 LA.UM.5.1-04010-8x37.0 msm8937_64 LA.UM.5.1-04010-8x37.0.xml 06.00.01
04.29.2016 LA.UM.5.1-03810-8x37.0 msm8937_64 LA.UM.5.1-03810-8x37.0.xml 06.00.01
04.14.2016 LA.UM.5.1-03610-8x37.0 msm8937_64 LA.UM.5.1-03610-8x37.0.xml 06.00.01
03.30.2016 LA.UM.5.1-03210-8x37.0 msm8937_32 LA.UM.5.1-03210-8x37.0.xml 06.00.01
03.22.2016 LA.UM.5.3-01410-8x37.0 msm8937_64 LA.UM.5.3-01410-8x37.0.xml 06.00.01
03.15.2016 LA.UM.5.1-02910-8x37.0 msm8937_64 LA.UM.5.1-02910-8x37.0.xml 06.00.01
02.28.2016 LA.UM.5.1-02410-8x37.0 msm8937_64 LA.UM.5.1-02410-8x37.0.xml 06.00.01
02.25.2016 LA.UM.5.3-01110-8x37.0 msm8937_64 LA.UM.5.3-01110-8x37.0.xml 06.00.01
02.12.2016 LA.UM.5.1-02110-8x37.0 msm8937_64 LA.UM.5.1-02110-8x37.0.xml 06.00.01
02.12.2016 LA.UM.5.3-00610-8x37.0 msm8937_64 LA.UM.5.3-00610-8x37.0.xml 06.00.01
01.29.2016 LA.UM.5.1-01910-8x37.0 msm8937_64 LA.UM.5.1-01910-8x37.0.xml 06.00.01
01.21.2016 LA.UM.5.1-01610-8x37.0 msm8937_64 LA.UM.5.1-01610-8x37.0.xml 06.00.01
01.11.2016 LA.UM.5.1-01310-8x37.0 msm8937_64 LA.UM.5.1-01310-8x37.0.xml 06.00.01
12.21.2015 LA.UM.5.1-03700-8x37.0 msm8937_64 LA.UM.5.1-03700-8x37.0.xml 06.00.00
12.04.2015 LA.UM.5.1-01400-8x37.0 msm8937_64 LA.UM.5.1-01400-8x37.0.xml 06.00.00
11.21.2015 LA.UM.5.1-01010-8x37.0 msm8937_64 LA.UM.5.1-01010-8x37.0.xml 06.00.00
Click to expand...
Click to collapse
* QAEP kernel for msm8937:
Code:
mkdir -p android-source/qaep
cd android-source/qaep
repo init -u git://codeaurora.org/platform/manifest.git -b release -m LA.UM.5.3-01110-8x37.0.xml --repo-url=git://codeaurora.org/tools/repo.git
grep kernel/msm-3.18 .repo/manifest.xml
<project name="kernel/msm-3.18" path="kernel" revision="985da67f18431ac30e2c2d46b68067b71ebf8688" upstream="LA.UM.5.3_rb1.1"/>
<project name="kernel/msm-3.18" path="kernel" revision="a199af79618518255f6eb6656e1ba6fcb6b1e7ff" upstream="LA.UM.5.1_rb1.4"/>
Click to expand...
Click to collapse
git://codeaurora.org/kernel/msm-3.18 branchs:
LA.UM.5.1_rb1.3
LA.UM.5.1_rb1.4
LA.UM.5.3.1_rb1
LA.UM.5.3_rb1.1
06.23.2016 LA.UM.5.3.1-01010-89xx.0 msm-3.18 df25fdbbe93e8f1c16268faed04a065bf1cd7d89 LA.UM.5.3.1_rb1
06.10.2016 LA.UM.5.3-04410-89xx.0 msm-3.18 8235259992248adedca456006c027a938cc0f9d3 LA.UM.5.3_rb1.1
06.09.2016 LA.UM.5.3.1-00610-89xx.0 msm-3.18 235372e1f95010f66f4d353ac15402a4c314607f LA.UM.5.3.1_rb1
06.07.2016 LA.UM.5.1-04210-8x37.0 msm-3.18 a199af79618518255f6eb6656e1ba6fcb6b1e7ff LA.UM.5.1_rb1.4
06.06.2016 LA.UM.5.3.1-00610-89xx.0 msm-3.18 235372e1f95010f66f4d353ac15402a4c314607f LA.UM.5.3.1_rb1
05.31.2016 LA.UM.5.3-03710-89xx.0 msm-3.18 e4bd98b39aee92bd6f838c4c14189de51a16a258 LA.UM.5.3_rb1.1
05.24.2016 LA.UM.5.3.1-00310-89xx.0 msm-3.18 289277d0980d8075c20244d8aa8cfde3b4b57737 LA.UM.5.3.1_rb1
05.15.2016 LA.UM.5.1-04010-8x37.0 msm-3.18 67ea3027ee587c3cddc0c51024257816c0972312 LA.UM.5.1_rb1.4
04.29.2016 LA.UM.5.1-03810-8x37.0 msm-3.18 a9e54d65f9005af4075c24063ad2558260254dc5 LA.UM.5.1_rb1.4
04.14.2016 LA.UM.5.1-03610-8x37.0 msm-3.18 5b0c3e43afaa6639f6d41a6379e713382b220c5e LA.UM.5.1_rb1.4
03.30.2016 LA.UM.5.1-03210-8x37.0 msm-3.18 5f11194935c418e32e5308ae397227afc5797fed LA.UM.5.1_rb1.4
03.22.2016 LA.UM.5.3-01410-8x37.0 msm-3.18 261ac07c6a00d352d42fe412595beaa70d55c7ab LA.UM.5.3_rb1.1
03.15.2016 LA.UM.5.1-02910-8x37.0 msm-3.18 38a946316417e48534169a0e8174286f52d78685 LA.UM.5.1_rb1.4
02.28.2016 LA.UM.5.1-02410-8x37.0 msm-3.18 7d15cd5c720f21b63f269539edbec896d7e233f6 LA.UM.5.1_rb1.4
02.25.2016 LA.UM.5.3-01110-8x37.0 msm-3.18 985da67f18431ac30e2c2d46b68067b71ebf8688 LA.UM.5.3_rb1.1
02.12.2016 LA.UM.5.1-02110-8x37.0 msm-3.18 488a89d43651383c957f75a628534a7ad5d7eea0 LA.UM.5.1_rb1.4
02.12.2016 LA.UM.5.3-00610-8x37.0 msm-3.18 eef5da9a9bbc138fc7ee42f804b957a7758f8a78 LA.UM.5.3_rb1.1
01.29.2016 LA.UM.5.1-01910-8x37.0 msm-3.18 fb35f3c795229950ddf63280800b2390eafcb135 LA.UM.5.1_rb1.4
01.21.2016 LA.UM.5.1-01610-8x37.0 msm-3.18 1aa11b594d7ac1dfab73a86119998b4c4e80b506 LA.UM.5.1_rb1.4
01.11.2016 LA.UM.5.1-01310-8x37.0 msm-3.18 39d6e2eee46004ada9e72eb273b028986651d6dc LA.UM.5.1_rb1.4
12.21.2015 LA.UM.5.1-03700-8x37.0 msm-3.18 4e90549c8f8d5feb88e92c24dde4f15e1f94a616 rel/msm-3.18
12.04.2015 LA.UM.5.1-01400-8x37.0 msm-3.18 e70ad0cd5efdd9dc91a77dcdac31d6132e1315c1 rel/msm-3.18
11.21.2015 LA.UM.5.1-01010-8x37.0 msm-3.18 122fe9b172bd14c1c5dffa45fc4389da0c187461 LA.UM.5.1_rb1.3
Click to expand...
Click to collapse
* redmi 3 kernel:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource branch ido-l-oss
STATUS REPORT:
Tested with my kernel #5d5fa78 + stock ROM MIUI V7.5.9.0. Stable enough.
boot: OK
panel: OK
vol+ vol- power key: OK
touchscreen: OK
eMMC: OK
mic: OK
phone: OK
external speaker: OK
sensors: OK
vibrator: OK
cameras: could be OK (QR code scan work, but can't get a photo)
fingerprint: need more work
wifi: OK
dial: OK
PREBUILT KERNEL:
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937/releases/download/v0.9-beta/kernel
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937/releases/download/v0.9-beta/wlan.ko
touchscreen firmware issue:
Perhaps we can just ignore this issue. The touchscreen works fine.
dmesg from my kernel #39aa441. striped non opensorce bin form lib*.a files from the redmi 3 ft5x06 driver.
Code:
[ 0.969584] input: ft5x06_720p as /devices/soc/78b7000.i2c/i2c-3/3-003e/input/input1
[ 1.210325] i2c-msm-v2 78b7000.i2c: msm_bus_scale_register_client(mstr-id:86):0xd (ok)
[ 1.210825] ft5x06_720p 3-003e: Device ID = 0x14
[ 1.211455] ft5x06_720p 3-003e: report rate = 90Hz
[ 1.213175] ft5x06_720p 3-003e: Firmware version = 8.0.0
[ 1.213624] FT5X06-TP-TAG INFO:boardid_info_tp:S88537AA1:bo
[ 1.213624]
[ 1.670057] ft5x06_720p 3-003e: Lockdown info: 34 35 32 31 00 A9 00 00
[ 1.731395] FT5X06-TP-TAG ERROR:Error Board ID.
[ 1.732698] FT5X06-TP-TAG ERROR:Error Board ID.
[ 1.733998] FT5X06-TP-TAG ERROR:Error Board ID.
[ 1.734068] [ TSP ] ist30xx_init()
dmesg from stock kernel MIUI V7.9.5.0.
Code:
[ 0.970901] input: ft5x06_720p as /devices/soc/78b7000.i2c/i2c-3/3-003e/input/input1
[ 1.210327] i2c-msm-v2 78b7000.i2c: msm_bus_scale_register_client(mstr-id:86):0xd (ok)
[ 1.210827] ft5x06_720p 3-003e: Device ID = 0x14
[ 1.211459] ft5x06_720p 3-003e: report rate = 90Hz
[ 1.213186] ft5x06_720p 3-003e: Firmware version = 8.0.0
[ 1.670059] ft5x06_720p 3-003e: Lockdown info: 34 35 32 31 00 A9 00 00
[ 1.670127] ft5x06_720p 3-003e: has no androidboot.mode
[ 1.670136] ft5x06_720p 3-003e: upgrade
[ 1.670144] FT5X06-TP-TAG DEBUG:[3148]********************Enter CTP Auto Upgrade********************
[ 1.670144]
[ 1.731401] FT5X06-TP-TAG DEBUG:[1342]Vendor ID:0xF3, TP FW:0x08, IC TYPE:20
[ 1.731409] FT5X06-TP-TAG DEBUG:[1370]OUFEI+BOE
[ 1.731417] FT5X06-TP-TAG DEBUG:[1396]update firmware size:28883
[ 1.731425] FT5X06-TP-TAG DEBUG:[1416][FTS] uc_tp_fm_ver = 8.
[ 1.731425]
[ 1.731433] FT5X06-TP-TAG DEBUG:[1417][FTS] uc_host_fm_ver = 8.
[ 1.731433]
[ 1.731516] [ TSP ] ist30xx_init()
[ 1.731912] [ TSP ] ### IMAGIS probe(ver:2.3.0.0, protocol:B, addr:0x50) ###
[ 1.732238] IST30XX 3-0050: irq gpio request failed
[ 1.732262] [ TSP ] Error, ist30xx init driver
FT5X06-TP-TAG DEBUG:[1342]Vendor ID:0xF3, TP FW:0x08, IC TYPE:20
FT5X06-TP-TAG DEBUG:[1370]OUFEI+BOE
FT5X06-TP-TAG DEBUG:[1396]update firmware size:28883
Click to expand...
Click to collapse
external speaker PA BUG: fixed. #5d5fa78
dmesg from my kernel #39aa441.
Code:
[ 3.179313] input: gpio-keys as /devices/soc/soc:gpio_keys/input/input2
[ 3.179650] qcom,qpnp-rtc qpnp-rtc-ffffffc079767000: setting system clock to 1970-01-03 02:20:00 UTC (181200)
[ 3.190542] qcom,qpnp-flash-led qpnp-flash-led-ffffffc079793400: Unable to acquire pinctrl
[ 3.195190] qcom,cc-debug-8952 1874000.qcom,cc-debug: Registered Debug Mux successfully
[ 3.201419] msm8952-asoc-wcd c051000.sound: default codec configured
[ 3.201790] msm8952_populate_dai_link_component_of_node: codec dai msm-stub-codec.1 failed
[ 3.201867] msm8952_populate_dai_link_component_of_node: codec dai msm-stub-codec.1 failed
dmesg from stock kernel (MIUI V7.5.9.0)
Code:
[ 3.277300] input: gpio-keys as /devices/soc/soc:gpio_keys/input/input4
[ 3.277650] qcom,qpnp-rtc qpnp-rtc-ffffffc079776c00: setting system clock to 1970-01-03 02:09:35 UTC (180575)
[ 3.288617] qcom,qpnp-flash-led qpnp-flash-led-ffffffc0797aac00: Unable to acquire pinctrl
[ 3.293341] qcom,cc-debug-8952 1874000.qcom,cc-debug: Registered Debug Mux successfully
[ 3.297473] msm8952_asoc_machine_probe: [hjf] request spk_pa_gpio is 124!
[ 3.297490] msm8952_asoc_machine_probe: [hjf] request headset_gpio is 129!
[ 3.299584] msm8952-asoc-wcd c051000.sound: default codec configured
[ 3.299947] msm8952_populate_dai_link_component_of_node: codec dai msm-stub-codec.1 failed
[ 3.300053] msm8952_populate_dai_link_component_of_node: codec dai msm-stub-codec.1 failed
spk_pa_gpio is 124 = 0x7c
headset_gpio is 129 = 0x7f
Click to expand...
Click to collapse
Just debug info? Or Xiaomi did some nasty work in function msm8952_asoc_machine_probe.
Code:
grep msm8952_asoc_machine_probe sound/ -ir
sound/soc/msm/msm8952-slimbus.c:static int msm8952_asoc_machine_probe(struct platform_device *pdev)
sound/soc/msm/msm8952-slimbus.c: .probe = msm8952_asoc_machine_probe,
sound/soc/msm/msm8952.c:static int msm8952_asoc_machine_probe(struct platform_device *pdev)
sound/soc/msm/msm8952.c: .probe = msm8952_asoc_machine_probe,
Redmi3s main dts file is arch/arm64/boot/dts/qcom/redmi3s-msm8937-38.dts.
Code:
9604 sound {
9605 status = "okay";
9607 qcom,model = "msm8952-sku1-snd-card";
9610 qcom,msm-ext-pa = "primary";
9615 ext-spk-amp-gpio = <0x97 0x7c 0x0>;
9616 headset-gpio = <0x97 0x81 0x0>;
ext-spk-amp-gpio = <0x97 0x7c 0x0>
headset-gpio = <0x97 0x81 0x0>
Click to expand...
Click to collapse
dial BUG: FALSE alarm
Amazing work bro, I'm following the thread to see your progress
I always want to try make custom ROMs (I'm developer but no experience about ROM development) but I don't know where to start xD.
Regards!
Keep up the good work man!!!!
The external speaker PA BUG has fixed. See #5d5fa78.
The fix isn't elegant, but it works.
Hi, why did you choose "LA.UM.5.3-01110-8x37.0" ?
i did the same as you, but i'm getting a Too many open files when I boot CM
If you have any ideas : https://github.com/supercairos/android_kernel_xiaomi_msm8937
Supercairos said:
Hi, why did you choose "LA.UM.5.3-01110-8x37.0" ?
i did the same as you, but i'm getting a Too many open files when I boot CM
If you have any ideas : https://github.com/supercairos/android_kernel_xiaomi_msm8937
Click to expand...
Click to collapse
About LA.UM.5.3-01110-8x37.0:
I just try to find a QAEP release which match the release date of Redmi 3S as much as possible. Nothing more.
About "too many open files":
My repo #deccaf5 (9.21.2016) can boot cm, but it need force reboot several times.
After that commit, the error same as yours. Sorry for my bad.
https://github.com/yangyangnau/android_device_xiaomi_land
A few of days ago, I'm try using my kernel and proprietary-files.txt with the repo below.
https://github.com/Silentlys/android_device_xiaomi_land
Clean the fake kernel header tree. Clean the malware (2345 stuff). Clean TWRP stuffs.
No luck. Just get black screen. Can't remember the error messages. Could be "too many open files".
I guess the proprietary-files.txt is a problem.
Please post CM issue at my thread below.
http://forum.xda-developers.com/redmi-3/development/port-cm-13-0-xiaomi-redmi3s-land-t3469996
QAEP for msm8937
Code:
lynx -dump -width 120 https://wiki.codeaurora.org/xwiki/bin/QAEP/release | grep msm8937
June 23, 2016 LA.UM.5.3.1-01010-89xx.0 msm8937_64 LA.UM.5.3.1-01010-89xx.0.xml 06.00.01
June 10, 2016 LA.UM.5.3-04410-89xx.0 msm8937_64 LA.UM.5.3-04410-89xx.0.xml 06.00.01
June 09, 2016 LA.UM.5.3.1-00610-89xx.0 msm8937_64 LA.UM.5.3.1-00610-89xx.0.xml 06.00.01
June 07, 2016 LA.UM.5.1-04210-8x37.0 msm8937_64 LA.UM.5.1-04210-8x37.0.xml 06.00.01
June 06, 2016 LA.UM.5.3.1-00610-89xx.0 msm8937_64 LA.UM.5.3.1-00610-89xx.0.xml 06.00.01
May 31, 2016 LA.UM.5.3-03710-89xx.0 msm8937_64 LA.UM.5.3-03710-89xx.0.xml 06.00.01
May 24, 2016 LA.UM.5.3.1-00310-89xx.0 msm8937_64 LA.UM.5.3.1-00310-89xx.0.xml 06.00.01
May 15, 2016 LA.UM.5.1-04010-8x37.0 msm8937_64 LA.UM.5.1-04010-8x37.0.xml 06.00.01
April 29, 2016 LA.UM.5.1-03810-8x37.0 msm8937_64 LA.UM.5.1-03810-8x37.0.xml 06.00.01
April 14, 2016 LA.UM.5.1-03610-8x37.0 msm8937_64 LA.UM.5.1-03610-8x37.0.xml 06.00.01
March 30, 2016 LA.UM.5.1-03210-8x37.0 msm8937_32 LA.UM.5.1-03210-8x37.0.xml 06.00.01
March 22, 2016 LA.UM.5.3-01410-8x37.0 msm8937_64 LA.UM.5.3-01410-8x37.0.xml 06.00.01
March 15, 2016 LA.UM.5.1-02910-8x37.0 msm8937_64 LA.UM.5.1-02910-8x37.0.xml 06.00.01
February 28, 2016 LA.UM.5.1-02410-8x37.0 msm8937_64 LA.UM.5.1-02410-8x37.0.xml 06.00.01
February 25, 2016 LA.UM.5.3-01110-8x37.0 msm8937_64 LA.UM.5.3-01110-8x37.0.xml 06.00.01
February 12, 2016 LA.UM.5.1-02110-8x37.0 msm8937_64 LA.UM.5.1-02110-8x37.0.xml 06.00.01
February 12, 2016 LA.UM.5.3-00610-8x37.0 msm8937_64 LA.UM.5.3-00610-8x37.0.xml 06.00.01
January 29, 2016 LA.UM.5.1-01910-8x37.0 msm8937_64 LA.UM.5.1-01910-8x37.0.xml 06.00.01
January 21, 2016 LA.UM.5.1-01610-8x37.0 msm8937_64 LA.UM.5.1-01610-8x37.0.xml 06.00.01
January 11, 2016 LA.UM.5.1-01310-8x37.0 msm8937_64 LA.UM.5.1-01310-8x37.0.xml 06.00.01
December 21, 2015 LA.UM.5.1-03700-8x37.0 msm8937_64 LA.UM.5.1-03700-8x37.0.xml 06.00.00
December 04, 2015 LA.UM.5.1-01400-8x37.0 msm8937_64 LA.UM.5.1-01400-8x37.0.xml 06.00.00
November 21, 2015 LA.UM.5.1-01010-8x37.0 msm8937_64 LA.UM.5.1-01010-8x37.0.xml 06.00.00
Click to expand...
Click to collapse
fingerprint:
stock kernel
Code:
ls -l /dev/goodix_fp /dev/input/event5
crw-r--r-- system system 225, 0 /dev/goodix_fp
crw-rw---- root input 13, 69 /dev/input/event5
The above dev nodes are missing with my kernel #5d5fa78.
Code:
cat /sys/devices/soc/soc:fpc1020/uevent
OF_NAME=fpc1020
OF_FULLNAME=/soc/fpc1020
OF_COMPATIBLE_0=soc:fpc1020
OF_COMPATIBLE_N=1
MODALIAS=of:Nfpc1020T<NULL>Csoc:fpc1020
Code:
cat /sys/devices/soc/soc:goodix_fp/uevent
OF_NAME=goodix_fp
OF_FULLNAME=/soc/goodix_fp
OF_COMPATIBLE_0=goodix,fingerprint
OF_COMPATIBLE_N=1
MODALIAS=of:Ngoodix_fpT<NULL>Cgoodix,fingerprint
fingerprint:
logcat from CM-13 with my kernel #5d5fa78.
01-12 02:44:46.021 456 456 E QSEECOMAPI: Error::Cannot open the file /system/etc/firmware/goodixfp.mdt errno = 2
01-12 02:44:46.021 456 456 E QSEECOMAPI: Error::Loading image failed with ret = -1
Click to expand...
Click to collapse
Code:
ls -l /firmware/image/goodixfp*
-r--r--r-- 1 root root 276 2016-08-16 21:18 /firmware/image/goodixfp.b00
-r--r--r-- 1 root root 6664 2016-08-16 21:18 /firmware/image/goodixfp.b01
-r--r--r-- 1 root root 397050 2016-08-16 21:18 /firmware/image/goodixfp.b02
-r--r--r-- 1 root root 397604 2016-08-16 21:18 /firmware/image/goodixfp.b03
-r--r--r-- 1 root root 392 2016-08-16 21:18 /firmware/image/goodixfp.b04
-r--r--r-- 1 root root 88 2016-08-16 21:18 /firmware/image/goodixfp.b05
-r--r--r-- 1 root root 832 2016-08-16 21:18 /firmware/image/goodixfp.b06
-r--r--r-- 1 root root 6940 2016-08-16 21:18 /firmware/image/goodixfp.mdt
Wow you're so far, and fast. I'm ultra impressed, thank you so much
Keep up the good work dev
You seem to be the only hope as Xiaomi is too lazy to release kernel sources.
Hopefully someone can build CyanogenMod 14 unofficial based on this kernel...
Edit: So I heard the dev is working on a cm13 bootable... If this is true, please work on cm14 as well! Thank you for your work.
Good work Dev !!!
Ptmaroct said:
Keep up the good work dev
You seem to be the only hope as Xiaomi is too lazy to release kernel sources.
Click to expand...
Click to collapse
Not lazy, rather caught up on releasing phones... Redmi 3S Plus, Mi 5s, Mi 5c... I just wish they'd stop and focus on the main thing here.
Speaking of which, almost everyone in India is buying a Lenovo lol... If I had the chance I'd kill all these weirdo Chinese companies because of their stupid skins...
I just wanted to say, that your work is very very impressive and we can be very thankful for guys like you, who make things possible on their own!!!
THANKS
My GF and I staying tuned...
So any updates?
ZelectroKarZ said:
So any updates?
Click to expand...
Click to collapse
Chill brother, here at XDA this is not very welcome.