Hello, everyone, since nobody is building CM14.1(based on Android 7.1) for our beloved flo yet, i decided to build it. This is an unofficial build, built straight from CM14.1 sources with no modifications. Post any bugs you find since this is a relatively new build. I have a cron script building everyday and will post it when I visit the forum.Have fun.
Downloads:cm-14.1-20161111-UNOFFICIAL-flo.zip
Downloading it and giving it a go. Nano gapps won't work as the partition is too small so I get to try Pico...
I occasionally got a force close on the settings app and the camera crashes on startup. Everything else is real fast.
ming3r said:
Downloading it and giving it a go. Nano gapps won't work as the partition is too small so I get to try Pico...
Click to expand...
Click to collapse
yea, flo has a small system partition, i used pico gapps and installed whatever i need from the play store.
Looks like we should be able to fit opengapps nano with this
https://review.cyanogenmod.org/#/c/170475/
There has been a bit of activity today
https://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_asus_flo
Might be building officially soon (read comments for more details)
https://review.cyanogenmod.org/#/c/170481/
Hello, there are big bugs? Or the rom is it stable?
Will it be regularly updated?
hisname said:
Hello, everyone, since nobody is building CM14.1(based on Android 7.1) for our beloved flo yet, i decided to build it. This is an unofficial build, built straight from CM14.1 sources with no modifications. Post any bugs you find since this is a relatively new build. I have a cron script building everyday and will post it when I visit the forum.Have fun.
Downloads:cm-14.1-20161111-UNOFFICIAL-flo.zip
Click to expand...
Click to collapse
I just flashed your CM14.1 build on my flo.
And i found that camera does not work. It is not very important for me but it is a fact that it does not work.
I grabbed logcat.
Code:
E mm-camera-intf: mm_camera_open: dev name = /dev/video1, cam_idx = 1
I chatty : uid=1006(camera) mm-qcamera-daem expire 44 lines
W Binder:218_1: type=1400 audit(0.0:65): avc: denied { write } for name="cam_socket1" dev="mmcblk0p30" ino=15 scontext=u:r:cameraserver:s0 tcontext=u:object_r:camera_socket:s0 tclass=sock_file permissive=0
I chatty : uid=1006(camera) mm-qcamera-daem expire 2 lines
I chatty : uid=1006(camera) mm-qcamera-daem expire 3 lines
E mm-camera-intf: mm_camera_open: opened, break out while loop
E mm-camera-intf: mm_camera_socket_create: socket_fd=-1 Permission denied
W Binder:218_1: type=1400 audit(0.0:66): avc: denied { write } for name="cam_socket1" dev="mmcblk0p30" ino=15 scontext=u:r:cameraserver:s0 tcontext=u:object_r:camera_socket:s0 tclass=sock_file permissive=0
E mm-camera-intf: mm_camera_socket_create: socket_fd=-1 Permission denied
E mm-camera-intf: mm_camera_open: cannot open domain socket fd of '/dev/video1'(Permission denied)
I chatty : uid=1006(camera) mm-qcamera-daem expire 2 lines
E mm-camera-intf: camera_open: mm_camera_open err = -1
E QCamera3HWI: static int qcamera::QCamera3HardwareInterface::initCapabilities(int): camera_open failed
I think that something wrong with a selinux.
tank0412 said:
I just flashed your CM14.1 build on my flo.
And i found that camera does not work. It is not very important for me but it is a fact that it does not work.
I grabbed logcat.
Code:
E mm-camera-intf: mm_camera_open: dev name = /dev/video1, cam_idx = 1
I chatty : uid=1006(camera) mm-qcamera-daem expire 44 lines
W Binder:218_1: type=1400 audit(0.0:65): avc: denied { write } for name="cam_socket1" dev="mmcblk0p30" ino=15 scontext=u:r:cameraserver:s0 tcontext=u:object_r:camera_socket:s0 tclass=sock_file permissive=0
I chatty : uid=1006(camera) mm-qcamera-daem expire 2 lines
I chatty : uid=1006(camera) mm-qcamera-daem expire 3 lines
E mm-camera-intf: mm_camera_open: opened, break out while loop
E mm-camera-intf: mm_camera_socket_create: socket_fd=-1 Permission denied
W Binder:218_1: type=1400 audit(0.0:66): avc: denied { write } for name="cam_socket1" dev="mmcblk0p30" ino=15 scontext=u:r:cameraserver:s0 tcontext=u:object_r:camera_socket:s0 tclass=sock_file permissive=0
E mm-camera-intf: mm_camera_socket_create: socket_fd=-1 Permission denied
E mm-camera-intf: mm_camera_open: cannot open domain socket fd of '/dev/video1'(Permission denied)
I chatty : uid=1006(camera) mm-qcamera-daem expire 2 lines
E mm-camera-intf: camera_open: mm_camera_open err = -1
E QCamera3HWI: static int qcamera::QCamera3HardwareInterface::initCapabilities(int): camera_open failed
I think that something wrong with a selinux.
Click to expand...
Click to collapse
interesting...but hey, CM has fixed the issue.
hisname said:
interesting...but hey, CM has fixed the issue.
Click to expand...
Click to collapse
Yeah but it was 2 hours ago.
I think that you built CM14 build more than 2 hours ago so your device tree does not have latest version of this commit.
flo will have an official CM 14.1 build soon, courtesy of forkbomb (Simon Shields). He took the rebased trees and brought it up to 7.1.
Camera work or no?
Byooxyde said:
Camera work or no?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=69579022&postcount=2
ming3r said:
http://forum.xda-developers.com/showpost.php?p=69579022&postcount=2
Click to expand...
Click to collapse
I don't understand your link
Nougat nightly was just posted!
Byooxyde said:
I don't understand your link
Click to expand...
Click to collapse
You don't understand the link? You click on it and it shows his post stating that camera doesn't work. How isn't that not understandable ?
Just installed the official nightly, works like a charm. Only two things I've noticed:
- during the i installation got an error "unknown command "LOG". The installation continues without issue however.
- CM Bug reporter daemon crashes during initial configuration.
Locke_G said:
Just installed the official nightly, works like a charm. Only two things I've noticed:
- during the i installation got an error "unknown command "LOG". The installation continues without issue however.
- CM Bug reporter daemon crashes during initial configuration.
Click to expand...
Click to collapse
Same for me and tape recorder don't work
bbernardini said:
Nougat nightly was just posted!
Click to expand...
Click to collapse
Do you mean on the CM website?
Thanks.
bbernardini said:
Nougat nightly was just posted!
Click to expand...
Click to collapse
Could you provide the link? Thanks!
Enviado desde mi LG-D855 mediante Tapatalk
https://download.cyanogenmod.org/?device=flo
Sent from my SM-G900V using Tapatalk
Enviado desde mi LG-D855 mediante Tapatalk
Related
Original thread from WaylandAce click here (also for changelog)
All credits to WaylandAce for his fantastic work!
Click here to download nightlies from our buildserver!!
Updated every two days, allways synced with latest CM + androidarmv6 sources.
Changelogs: Click here to follow our reviewsite! Changes in nightlies you can find in merged!
Please no non-dev talk in this thread. Her you find, a more general, discussion thread
CM-10.1: How to install the extra packages in extradir in zip
(DSP Manager, Apollo, Email and Exchange reside in an extra folder on zip and are not installed by default)
Changelog: Second post.
If you are on a pre 07.01 release: Please full wipe because of systemwide resizing!!
Development can be followed here
Many thanks to Dark Passenger and Francesco Colella for their ldpi fixing!
Older releases:
02-04 build: cm-10.1
http://www.androidfilehost.com/?fid=22897186102575334
md5: 8b32f7bd494185a4301394dd38ae75cd
cm-9
http://www.androidfilehost.com/?fid=22897186102575333
md5: 22c5e747b86c8836ada9ae1b9940220a
cm-10.1-20130309-NIGHTLY-beni
md5: 40582d4e5b09f2382395bc3edb02912c
cm-10.1-20130224-NIGHTLY-beni
md5: f88c71482f29364ee4040fc8ef92a2c0
cm-10.1-20130216-NIGHTLY-beni
cm-10.1-20130117-NIGHTLY-beni
cm-10.1-20130108-UNOFFICIAL-beni
cm-10.1-20130107-UNOFFICIAL-beni.zip
cm-10.1-20130106-UNOFFICIAL-beni
cm-10.1-20121231-UNOFFICIAL-beni.zip
Please keep in mind, we donot have the device, so we are going a little blind on this.
Please no mirrorring!
Changelog
02-04-2013 CM-10.1
implemented FM support, still wip, NOT(!) operational yet.
new kernel. Still 2.6.35, but based on stock Samsung sources source here
Fixed battery stats
Improved memory management (Reintroduced. Based on an idea from Lagloose in Jellaxy. Testing stage)
Some extra ringtones
Latest CM sources
02-04-2013 CM-9
Initial release
Known "bug" double gallery. Will fix that later, I am lazy for now
09.03.2013
Fixed layout for ldpi by Dark Passenger (many thanx to him)
systemUI FC fixed (AOKP)
kernelfix for BT tethering (Thanx for suggestion to my old pal TheWhisp)
various changes from AOKP (AOKP release)
various changes from CM (CM release)
Added exhange and email
CM: Added Apollo and DSP Manager
24.02.2013
Stable
Ringtone loop fixed
CRT animation fixed
Expirimental (need confirmation!)
SystemUI layout
Fixed 1 on dialpad???
16.02.2013
Upgraded to 4.2.2 by CM
some kernel enhancements
17.01.2013
yesterday my son Luuk was born (most important change!)
GPS Fix (Wayland Ace)
Re-organized vendor samsung, added device specific files (psyke83)
Disabled Triple FrameBuffer and some other kernelchanges (optimize memory)
CM Changes
Wifi allways on in sleep (reconnecting problems)
Applications added: Google Talk, chrome bookmarks sync, Setup wizard
OMX libs fixed: Youtube controls bug fixed, camera crash fixed, camcoder works in HW mode
BLN enabled by default
Might have forgotten some things been very busy past two days
08.01.2013
more resizing work (still work in progress!)
camera improved (panorama works)
data usage border fix
kernelfix for spontanious reboots on certain occasions
CM updates / improvements
07.01.2013
Please full wipe because of systemwide resizing!!
changed dl link for bandwith reasons
boot issue from 06.01.2013 (confirmed)
fixed overscroll
fixed clock on lockscreen
06.01.2013
I tried to solve some ldpi overlay size issues. As I cannot test, please let me know if I screwed up, or what was solved and what still needs to be solved. Thanx in advance!
Applications added: Google Talk, chrome bookmarks sync, Setup wizard
OMX libs fixed: Youtube controls bug fixed, camera crash fixed, camcoder works in HW mode
Source based liblight with BLN support, BLN enabled by default
Superuser settings crash fixed
Added lagloose's force repeat ringtone hack
Other fixes
Latest CM and androidarmv6 sources
Minor kernel bug
If you kindly allow me to know the changes u did to beni rather from the device config and the repos in the androidarmv6 please kindly letme know as i am trying hard to make it boot but stuck in many things..
yajnab said:
If you kindly allow me to know the changes u did to beni rather from the device config and the repos in the androidarmv6 please kindly letme know as i am trying hard to make it boot but stuck in many things..
Click to expand...
Click to collapse
Download link added. bootproblem is caused by kernel. Kernel should boot now. If not I have a job to do. Or you should try to use whisps kernelsources form mini for ICS
When did you last sync sources?
Verstuurd van mijn GT-N8010 met Tapatalk
erikcas said:
Original thread from WaylandAce click here (also for changelog)
All credits to WaylandAce for his fantastic work!
Development can be followed here
Download here
Please keep in mind, we donot have the device, so we are going a little blind on this.
Click to expand...
Click to collapse
Wow...nice job sir...and Happy new year..!!
Sent from my GT-S5670 using xda premium
droider007 said:
Wow...nice job sir...and Happy new year..!!
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Not too early
Does it boot?
Verstuurd van mijn GT-N8010 met Tapatalk
erikcas said:
Not too early
Does it boot?
Verstuurd van mijn GT-N8010 met Tapatalk
Click to expand...
Click to collapse
gimme five minutes....
EDIT= BOOTED!!!
camera working....wifi working.....video camera buggy....everything working....awesome!!
droider007 said:
gimme five minutes....
EDIT= BOOTED!!!
camera working....wifi working.....video camera buggy....everything working....awesome!!
Click to expand...
Click to collapse
Camera takes picz or force close on taking picz? Camera needs some more attention on Gio..
USB tethering works? Wifi tethering works?
Please test as many as you can
Verstuurd van mijn GT-N8010 met Tapatalk
droider007 said:
gimme five minutes....
EDIT= BOOTED!!!
camera working....wifi working.....video camera buggy....everything working....awesome!!
Click to expand...
Click to collapse
Cud u test Data connection,gapps plz
MajinSaiyan4 said:
Cud u test Data connection,gapps plz
Click to expand...
Click to collapse
Maybe test yourself? Only you can test your own needs
Verstuurd van mijn GT-S5660 met Tapatalk
MajinSaiyan4 said:
Cud u test Data connection,gapps plz
Click to expand...
Click to collapse
Data connection wrking....where to find gapps..?? Lol
Will try usb tethering asap...!!
Edit: sometyms after clicking pic it fcs saying "gallery fc's"....but its very rare......
Sent from my GT-S5670 using xda premium
erikcas said:
Maybe test yourself? Only you can test your own needs
Verstuurd van mijn GT-S5660 met Tapatalk
Click to expand...
Click to collapse
With all pleasure but i dont have pc with me n my data connection sucks...thats y im asking..i will sure test it n report here :thumbup:
erikcas said:
Download link added. bootproblem is caused by kernel. Kernel should boot now. If not I have a job to do. Or you should try to use whisps kernelsources form mini for ICS
When did you last sync sources?
Verstuurd van mijn GT-N8010 met Tapatalk
Click to expand...
Click to collapse
I am using the CM10 Kernel of whisp.. THe boot.img is also same... i synced the last sources yesterday.. WIll send u a complete report tomorrow
droider007 said:
Data connection wrking....where to find gapps..?? Lol
Will try usb tethering asap...!!
Edit: sometyms after clicking pic it fcs saying "gallery fc's"....but its very rare......
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Cam still has some issues. Gapps are partly included (playstore is but no voice search)
Wifi tethering works but has issue with secure connection
Verstuurd van mijn GT-N8010 met Tapatalk
yajnab said:
I am using the CM10 Kernel of whisp.. THe boot.img is also same... i synced the last sources yesterday.. WIll send u a complete report tomorrow
Click to expand...
Click to collapse
Kernel is fixed, confirmed booting by droider here
Verstuurd van mijn GT-N8010 met Tapatalk
erikcas said:
Cam still has some issues. Gapps are partly included (playstore is but no voice search)
Wifi tethering works but has issue with secure connection
Verstuurd van mijn GT-N8010 met Tapatalk
Click to expand...
Click to collapse
usb tethering also working.....gapps also working great.....almost as stable as cm10
erikcas said:
Kernel is fixed, confirmed booting by droider here
Verstuurd van mijn GT-N8010 met Tapatalk
Click to expand...
Click to collapse
I waited for about 20 min.. Nothing more is coming in my logcat.. Checked two comp but same logcat.. Its getting stuck here
[email protected]:~/sdk/platform-tools$ ./adb logcat
--------- beginning of /dev/log/main
I/cm ( 99): ____ _ _ ____ _ _ ____ ____ ____ _ _ _ _ ____ ___
I/cm ( 100): | \_/ |__| |\ | | | | __ |___ |\ | |\/| | | | \
I/cm ( 101): |___ | | | | \| |__| |__] |___ | \| | | |__| |__/
I/cm ( 104): Welcome to Android 4.2.1 / CyanogenMod-10.1-20121220-UNOFFICIAL-beni
I/run-parts( 96): Setting permissions for brcm_patchram_plus! (dirty hack, I know :/)
I/DEBUG ( 117): debuggerd: Dec 20 2012 10:49:53
I/installd( 124): installd firing up
E/cutils ( 124): Failed to read /data/.layout_version: No such file or directory
D/installd( 124): Upgrading /data/media for multi-user
D/installd( 124): Upgrading to shared /data/media/obb
I/SurfaceFlinger( 119): SurfaceFlinger is starting
I/SurfaceFlinger( 119): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 119): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 119): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 119): loaded /system/lib/egl/libGLESv2_adreno200.so
I/gralloc ( 119): using (fd=15)
I/gralloc ( 119): id = msmfb30_30001
I/gralloc ( 119): xres = 240 px
I/gralloc ( 119): yres = 320 px
I/gralloc ( 119): xres_virtual = 240 px
I/gralloc ( 119): yres_virtual = 960 px
I/gralloc ( 119): bpp = 32
I/gralloc ( 119): r = 24:8
I/gralloc ( 119): g = 16:8
I/gralloc ( 119): b = 8:8
I/gralloc ( 119): width = 38 mm (160.421051 dpi)
I/gralloc ( 119): height = 51 mm (159.372543 dpi)
I/gralloc ( 119): refresh rate = 1986356224.00 Hz
D/CALCFPS ( 119): DEBUG_CALC_FPS: 0
D/CALCFPS ( 119): period: 10
D/CALCFPS ( 119): ignorethresh_us: 500000
D/CALCFPS ( 119): DEBUG_CALC_FPS: 0
D/CALCFPS ( 119): period: 10
D/CALCFPS ( 119): ignorethresh_us: 500000
I/hwcomposer( 119): Initializing Qualcomm Hardware Composer
I/hwcomposer( 119): MDP version: 300
I/hwcomposer( 119): hwc_device_open: Hardware VSYNC not supported
I/SurfaceFlinger( 119): Using composer version 0.0
I/hwcomposer( 119): Initializing UEvent Listener Thread
W/SurfaceFlinger( 119): getting VSYNC period from fb HAL: 0
W/SurfaceFlinger( 119): getting VSYNC period from thin air: 16666666
E/Adreno200-EGL( 119): <qeglDrvAPI_eglChooseConfig:757>: EGL_BAD_ATTRIBUTE
W/SurfaceFlinger( 119): no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
W/SurfaceFlinger( 119): no suitable EGLConfig found, trying without EGL_RECORDABLE_ANDROID
E/Trace ( 119): error opening trace file: No such file or directory (2)
I/SurfaceFlinger( 119): EGL informations:
I/SurfaceFlinger( 119): vendor : Android
I/SurfaceFlinger( 119): version : 1.4 Android META-EGL
I/SurfaceFlinger( 119): extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer
I/SurfaceFlinger( 119): Client API: OpenGL_ES
I/SurfaceFlinger( 119): EGLSurface: 8-8-8-8, config=0x4
I/SurfaceFlinger( 119): OpenGL ES informations:
I/SurfaceFlinger( 119): vendor : Qualcomm
I/SurfaceFlinger( 119): renderer : Adreno (TM) 200
I/SurfaceFlinger( 119): version : OpenGL ES-CM 1.1
I/SurfaceFlinger( 119): extensions: GL_EXT_debug_marker GL_AMD_compressed_ATC_texture GL_AMD_performance_monitor GL_APPLE_texture_2D_limited_npot GL_ARB_vertex_buffer_object GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_type_2_10_10_10_REV GL_OES_blend_equation_separate GL_OES_blend_func_separate GL_OES_blend_subtract GL_OES_compressed_ETC1_RGB8_texture GL_OES_compressed_paletted_texture GL_OES_depth_texture GL_OES_depth24 GL_OES_draw_texture GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_framebuffer_object GL_OES_matrix_palette GL_OES_packed_depth_stencil GL_OES_point_size_array GL_OES_point_sprite GL_OES_read_format GL_OES_rgb8_rgba8 GL_OES_stencil_wrap GL_OES_texture_cube_map GL_OES_texture_env_crossbar GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_texture_mirrored_repeat GL_QCOM_binning_control GL_QCOM_extended_get GL_QCOM_tiled_rendering GL_AMD_compressed_3DC_texture
I/SurfaceFlinger( 119): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger( 119): GL_MAX_VIEWPORT_DIMS = 4096 x 4096
D/SurfaceFlinger( 119): Screen acquired, type=0 flinger=0xe318
E/bdaddr ( 157): Can't open /data/.nvmac_bt.info
Please post logcats on pastebin
Which rom is this?
Verstuurd van mijn GT-N8010 met Tapatalk
droider007 said:
usb tethering also working.....gapps also working great.....almost as stable as cm10
Click to expand...
Click to collapse
On Gio it is better then CM10
Verstuurd van mijn GT-N8010 met Tapatalk
erikcas said:
Not too early
Does it boot?
Verstuurd van mijn GT-N8010 met Tapatalk
Click to expand...
Click to collapse
In India is New Year.
About the kernel:
This is an almost "stock" kernel for Android 4.2.2 and Sense 5.
Since we don't have any kernel source, i ported One XL 4.2.2 kernel to One S.
I tested it with MaximusHD and everything is working like stock orignal closed-source kernel, so this is a base for future custom kernels
Source:
https://github.com/anoane/ville-4.2.2-sense5-evitaul_porting
Donation:
http://forum.xda-developers.com/donatetome.php?u=2351000
Help me to buy an original HTC MHL Cable and an original HTC One X+ 2100mha battery, i'll try to add full battery support for One S and video-out at [email protected], i read somewhere that FullHD support is crappy
Changelog and dowload:
v0.2: first public version:
http://www.4shared.com/zip/prUybCsg/fabane_ville_13_09_13.html
v0.3: updated all ville-board-* files, fixed usb detection, usb charge and adb are working now
http://www.4shared.com/zip/eHUJyZe8/fabane_ville_13_09_13_v03.html
v0.6: wifi fixed using cyanogenmod/zarboz prima_wlan (compiled from source, now on a new branch)
http://www.4shared.com/zip/y1rp6zNK/fabane_ville_17_09_13_v06.html
v1.0: wifi fixed using flar2 patch (using stock prima_wlan from MaximusHD)
http://www.4shared.com/zip/1brHpu0i/fabane_ville_04_10_13_v10.html
v1.1: fixed incoming call quality issue
http://www.4shared.com/zip/NUW_ieLg/fabane_ville_14_10_13_v11.html
https://mega.co.nz/#!oVdSyJaY!LCxmKX3e6_UOYCIPUgHqJkHcM8pagVvgZTbb6nv8vrc
Did signal break in the process? Or was it already not working?
When I booted it it had no signal, so I guess it's not your fault
usaff22 said:
Did signal break in the process? Or was it already not working?
When I booted it it had no signal, so I guess it's not your fault
Click to expand...
Click to collapse
i'll try to check dmesg and logcat with some app, since usb/adb it's not working
but i have very little spare time now, so i posted my work until now, so someone can continue it
Oh yes, finally!
Great job here..
So you used stock sense 4+ kernel, and patched it with Evita kernel update?
Sent from my One S using Tapatalk 2
Thanks a lot Guy !!!
I'm very happy to see that! :good::good::good:
yes + some ville-board-* files (following evita-board changes) to compile it without errors
Wow ! That's good news
Envoyé depuis mon HTC One S avec Tapatalk 4
Does this mean htc 4.2.2 is not far away? And we will have sense 5 with it? Or it's just experimenting?
Thank you! If you need a tester I'm here for you..
Sent from my HTC One S using xda app-developers app
Good job, cant wait to use Sense 5 + 4.2.2 on my HoS!
good news, usb is detected now, battery charge and adb are working now, so i can get logcat and dmesg and fix problems easily
i think i finished to update board-ville-* files
i'll update git source and post a v0.3 test kernel soon
pirlano said:
good news, usb is detected now, battery charge and adb are working now, so i can get logcat and dmesg and fix problems easily
i think i finished to update board-ville-* files
i'll update git source and post a v0.3 test kernel soon
Click to expand...
Click to collapse
Any idea about the current buglist?
Sent from my One S using Tapatalk 2
RockR172 said:
Any idea about the current buglist?
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
i think we need a ported 4.2.2 rom to check them...
dmesg is pretty good
logcat show errors and crash, maybe rom related, maybe not
pirlano said:
i think we need a ported 4.2.2 rom to check them...
dmesg is pretty good
logcat show errors and crash, maybe rom related, maybe not
Click to expand...
Click to collapse
If you have been following the zenROM thread, me and usaff22 were trying to do the same, but the kernel never booted past the boot animation(technically it did, but nvm) and so we put it on hold until we had a booting kernel..
Now I don't have much time, since I got exams.. So maybe @usaff22 could help in the port of 4.2.2 based Sense..
Sent from my One S using Tapatalk 2
RockR172 said:
If you have been following the zenROM thread, me and usaff22 were trying to do the same, but the kernel never booted past the boot animation(technically it did, but nvm) and so we put it on hold until we had a booting kernel..
Now I don't have much time, since I got exams.. So maybe @usaff22 could help in the port of 4.2.2 based Sense..
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
me too, ****ing exams
btw, cannot use rom because of this error (phone is unusable), error is repeated thousand times:
Code:
E/AndroidRuntime(21591): FATAL EXCEPTION: main
E/AndroidRuntime(21591): java.lang.ExceptionInInitializerError
E/AndroidRuntime(21591): at com.android.providers.telephony.MmsSmsDatabaseHelper.<init>(MmsSmsDatabaseHelper.java:1063)
E/AndroidRuntime(21591): at com.android.providers.telephony.MmsSmsDatabaseHelper.getInstance(MmsSmsDatabaseHelper.java:1072)
E/AndroidRuntime(21591): at com.android.providers.telephony.SearchdbProvider.onCreate(SearchdbProvider.java:93)
E/AndroidRuntime(21591): at android.content.ContentProvider.attachInfo(ContentProvider.java:1085)
E/AndroidRuntime(21591): at android.app.ActivityThread.installProvider(ActivityThread.java:5516)
E/AndroidRuntime(21591): at android.app.ActivityThread.installContentProviders(ActivityThread.java:5097)
E/AndroidRuntime(21591): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5034)
E/AndroidRuntime(21591): at android.app.ActivityThread.access$1300(ActivityThread.java:162)
E/AndroidRuntime(21591): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1432)
E/AndroidRuntime(21591): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(21591): at android.os.Looper.loop(Looper.java:158)
E/AndroidRuntime(21591): at android.app.ActivityThread.main(ActivityThread.java:5751)
E/AndroidRuntime(21591): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(21591): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(21591): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1083)
E/AndroidRuntime(21591): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:850)
E/AndroidRuntime(21591): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(21591): Caused by: java.lang.NoClassDefFoundError: android.provider.Telephony$MmsSms
E/AndroidRuntime(21591): at com.android.providers.telephony.util.DatabaseMonitor.<clinit>(DatabaseMonitor.java:22)
E/AndroidRuntime(21591): ... 17 more
I/ActivityManager( 792): Start proc com.android.nfc for restart com.android.nfc: pid=21603 uid=1027 gids={41027, 3002, 3001, 1015, 1028}
W/ActivityManager( 792): Process com.android.phone has crashed too many times: killing!
I/ActivityManager( 792): Recipient 21591
I/ActivityManager( 792): Process com.android.phone (pid 21591) has died.
I/ActivityManager( 792): Start proc com.android.phone for restart com.android.phone: pid=21616 uid=1001 gids={41001, 3002, 3001, 3003, 5012, 1026, 5006, 5011, 1028}
D/PhoneStatusBar( 1253): updateIcon slot=nfc index=13 viewIndex=0 old=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=false num=0 ) icon=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=true num=0 ) compareIcon= name=bottom_divider_glow vis=false >> true
D/PhoneStatusBar( 1253): updateIcon slot=nfc index=13 viewIndex=0 old=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=true num=0 ) icon=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=false num=0 ) compareIcon= name=bottom_divider_glow vis=true >> false
basically com.android.phone problem and nfc (we don't have nfc)
maybe @usaff22 already know the problem...how i can fix network signal and remove nfc stuff?
btw v0.3 uploaded on second post
EDIT: commit done
EDIT2: maybe i found the most important problem: sd cards (internal partition of course) seems not mounted, it will not save picture (camera and camcorder should be working): "Unable to save file to storage card due to insufficient file permissions", and i think it's a kernel problem, since i have the same behaviour with Sense 4+ too
I will post logcat and dmesg and try to fix sdcard mount
did you do anything to rom? like any kind of porting?
pirlano said:
EDIT2: maybe i found the most important problem: sd cards (internal partition of course) seems not mounted, it will not save picture (camera and camcorder should be working): "Unable to save file to storage card due to insufficient file permissions", and i think it's a kernel problem, since i have the same behaviour with Sense 4+ too
I will post logcat and dmesg and try to fix sdcard mount
Click to expand...
Click to collapse
The mount error might be from the Rom
I'm going to try with the kernel and stock 4.2.2 to see if I can help in any way nice work
Sent from my HTC VLE_U using Tapatalk 2
Flashalot said:
The mount error might be from the Rom
I'm going to try with the kernel and stock 4.2.2 to see if I can help in any way nice work
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
you left out a bunch of the fuse_sdcard stuff and other things fuse uses
but we dont need to emulate SDcard like other devices do since we have partiiton
rc420head said:
did you do anything to rom? like any kind of porting?
Click to expand...
Click to collapse
no, zero, untouched :silly:
Flashalot said:
The mount error might be from the Rom
I'm going to try with the kernel and stock 4.2.2 to see if I can help in any way nice work
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
i checked with adb and sdcard is mounted correctly, so maybe it's rom related
**This OP is still a stub.**
Download link: http://www6.zippyshare.com/v/53583730/file.html
-More to come.-
-Suggestions for editing are welcome!-
XDA:DevDB Information
Project Equilibrium i9103, a ROM for the Samsung Galaxy R i9103
Contributors
Adam77Root, Grarak, Disturbed™, Tha TechnoCrat, CallMeVentus
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Stock ICS 4.0.4 (preferably Indian XWLP8)
Based On: CyanogenMod 10.2
Version Information
Status: Alpha
Created 2013-09-24
Last Updated 2013-10-15
Reserved
--reserved--
Great.. Seems u are trying to get the most out of our Galaxy R!!! Thank u on behalf of the whole SGR community!!!
Sent from my Galaxy!
Great Adam SGR is alive again
Will download and report ^^
Grarak said:
Great Adam SGR is alive again
Will download and report ^^
Click to expand...
Click to collapse
LoL buddy, you compiled one for your S4.
Ho Hoo... Dude.. You Rock...
Once again my Galaxy R is alive.. :thumbup::thumbup::thumbup:
Sent from the future...
First Impression : Great Rom (Screenshots attached)
Thank you @Adam77Root for this Rom.
This Rom like PAC MAN and other custom roms is having the same problem which we also have in CM 10.2 too i.e. After Reboot, it stuck at Galaxy R Screen. no matter what we do, the device doesnt boots up again.
this is the only thing that is keeping many users from using 4.3.
I know you dont own Galaxy R anymore and it is difficult to do development but is there any chance that you could solve this "Stuck at Galaxy R Screen" problem?
Nikhil said:
First Impression : Great Rom (Screenshots attached)
Thank you @Adam77Root for this Rom.
This Rom like PAC MAN and other custom roms is having the same problem which we also have in CM 10.2 too i.e. After Reboot, it stuck at Galaxy R Screen. no matter what we do, the device doesnt boots up again.
this is the only thing that is keeping many users from using 4.3.
I know you dont own Galaxy R anymore and it is difficult to do development but is there any chance that you could solve this "Stuck at Galaxy R Screen" problem?
Click to expand...
Click to collapse
As its a new project of Team Equilibrium. If possible, try to Provide Log-cat to Team Equilibrium. BTW, Grarak, callmeventus & Tha Technocrat can also help in this regard, if you will provide Log-Cat.
BTW, thanks for the screenies.. Really liked that..
@Nikhil whenever your phone is stuck at the galaxy logo. Press the power button for 10 seconds. Hard reboot is a workaround until we can find a reason for this problem . If that doesn't then take out the battery and restart the phone.
I am doing the same
Sent from my GT-I9103 using
xda app-developers app
Can somebody link me to the Gapps we should use with this. Thanks in advance.
maheepmaurya said:
Can somebody link me to the Gapps we should use with this. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2378992
Sent from my GT-I9103 using xda app-developers app
Potential Bug: Clock is stopping every time when I try to set alarm. Getting error "Unfortunately, Clock has stopped".
Tha TechnoCrat said:
@Nikhil whenever your phone is stuck at the galaxy logo. Press the power button for 10 seconds. Hard reboot is a workaround until we can find a reason for this problem . If that doesn't then take out the battery and restart the phone.
I am doing the same
Sent from my GT-I9103 using
xda app-developers app
Click to expand...
Click to collapse
Not working for me.
tried hard reboot many times.
tried removing battery
tried clearing dalvik caches
tried rebooting from recovery
tried normal shut down and manually booting.
nothing works for me.
i wonder how it is working for you.
pdesai said:
Potential Bug: Clock is stopping every time when I try to set alarm. Getting error "Unfortunately, Clock has stopped".
Click to expand...
Click to collapse
Can we have a logcat please?
CallMeVentus said:
Can we have a logcat please?
Click to expand...
Click to collapse
Here you go. Logcat attached. Hope this help.
pdesai said:
Here you go. Logcat attached. Hope this help.
Click to expand...
Click to collapse
Code:
09-24 20:04:12.366 W/ActivityManager( 405): Permission denied: checkComponentPermission() owningUid=10014
09-24 20:04:12.366
W/BroadcastQueue( 405): Permission Denial: broadcasting Intent { act=notif_in_use_cancel flg=0x10 } from com.google.android.deskclock (pid=7027, uid=10055) is not exported from uid 10014 due to receiver com.android.deskclock/.timer.TimerReceiver
09-24 20:04:16.406 W/ActivityManager( 405): Permission denied: checkComponentPermission() owningUid=10014
09-24 20:04:16.406 W/BroadcastQueue( 405): Permission Denial: broadcasting Intent { act=notif_in_use_show flg=0x10 } from com.google.android.deskclock (pid=7027, uid=10055) is not exported from uid 10014 due to receiver com.android.deskclock/.timer.TimerReceiver
09-24 20:04:16.496 W/ActivityManager( 405): Permission denied: checkComponentPermission() owningUid=10014
09-24 20:04:16.496 W/ActivityManager( 405): Permission denied: checkComponentPermission() owningUid=10014
09-24 20:04:16.496 W/dalvikvm( 7027): threadid=12: thread exiting with uncaught exception (group=0x41def700)
09-24 20:04:16.496 W/ActivityManager( 405): Permission Denial: opening provider com.android.deskclock.AlarmProvider from ProcessRecord{422b45f0 7027:com.google.android.deskclock/u0a10055} (pid=7027, uid=10055) that is not exported from uid 10014
The clock alarm service has been denied permission from the start, we'll look into it.
Nikhil said:
Not working for me.
tried hard reboot many times.
tried removing battery
tried clearing dalvik caches
tried rebooting from recovery
tried normal shut down and manually booting.
nothing works for me.
i wonder how it is working for you.
Click to expand...
Click to collapse
Which baseband? I have XXLQ3
"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"
Nikhil said:
Not working for me.
tried hard reboot many times.
tried removing battery
tried clearing dalvik caches
tried rebooting from recovery
tried normal shut down and manually booting.
nothing works for me.
i wonder how it is working for you.
Click to expand...
Click to collapse
Have you tried mounting /system and /data prior to installation?
You wouldn't care where I sent this message from.
Tha TechnoCrat said:
Which baseband? I have XXLQ3
Click to expand...
Click to collapse
DDLP3.
currently I'm shuffling between 10.1 and 10.2.
i'll give logcat, the next time i flash this rom.
FOR EVERYONE:
The ROM IS NOT BOOTING YET. This thread is for DEVELOPERS ONLY, if you can't help me, don't post here,
and NO, I WON'T GIVE UP UNTIL WE HAVE A WORKING MIUI ROM.
Status: STUCK ON BOOTANIMATION
You can find more info on MIUI ROM right here: http://en.miui.com/
Changelog:
20140726: Ported from LG / Google Nexus 4
Based on MK4.44 20140726 nightly
20140705 #2: Based on latest 20140705 nightly
20140705: MIUI Patch ROM
20140704 #2: Base updated to "cm-11-20140704-NIGHLTY-falcon"
20140704: Some kernel changes
20140703: First build
Downloads:
20140726: http://www.androidfilehost.com/?fid=23578570567718880
20140705 #2: http://www.androidfilehost.com/?fid=23501681358557999
20140705: http://www.androidfilehost.com/?fid=23501681358557706
20140704 #2: https://www.dropbox.com/s/ws8ioh1kwdelhw6/miui_falcon_4.6.27_20140704_2.zip
20140704: https://www.dropbox.com/s/7blu7jpcvfp7xw1/miui_falcon_4.6.27_20140704.zip
20140703: https://www.dropbox.com/s/vql0c0yp50v4i9p/miui_falcon_4.6.27_20140703.zip
Working:
-
Not working:
-
Instructions:
1. Update recovery
2. Wipe Data / Factory Reset (Format /system if you want)
3. Install the ROM
4. Install GApps
5. Reboot
ROM Review (thanks to TechJunkieReviews):
Credits:
Google / AOSP
@kromuch
dhacker29
Cyanogenmod
MIUI (Xiaomi)
If you help me, your name will be here!
Did you build this, or did you just copy and paste files into a working rom? It'll be hard for a dev to help you if it wasn't built. (to my knowledge at least)
YoshiShaPow said:
Did you build this, or did you just copy and paste files into a working rom? It'll be hard for a dev to help you if it wasn't built. (to my knowledge at least)
Click to expand...
Click to collapse
Yes he ported according to me taking cm as base
And @K3VYNC did u port the kernel?
cant help unless the OP states what steps he / she has taken. we will know what files are missing and what framework needs modification
I working in the port of this from Patch_rom source .----. If any can help send me PM [DEV only and who have knowledge about this.]
EDIT:
did you make changes in bootclaspath in the ramdisk? because you need add directives of MIUI in the ramdisk
Cheers.
TeamMex said:
did you make changes in bootclaspath in the ramdisk? because you need add directives of MIUI in the ramdisk
Click to expand...
Click to collapse
Here is my kernel with shelld in ramdisk, recently I've ported MIUI to Moto G, but it had many software bugs, so, I deleted ROM and now have only ported kernel.
Flash this manually, it's not a flashable ZIP.
Pff we need work a lot xD
Code:
E/qdhwcomposer( 240): hwc_set_primary: display commit fail for 0 dpy!
E/qdhwcomposer( 240): configure: No pipes available to configure fb for dpy 0
E/qdhwcomposer( 240): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Function not implemented
E/qdhwcomposer( 240): hwc_sync: acq_fen_fd_cnt=1 flags=16 fd=16 dpy=0 numHwLayers=2
E/qdoverlay( 240): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Function not implemented
E/qdoverlay( 240): static bool overlay::eek:verlay::displayCommit(const int&, const overlay::utils::Dim&): commit failed
E/qdhwcomposer( 240): hwc_set_primary: display commit fail for 0 dpy!
E/qdhwcomposer( 240): configure: No pipes available to configure fb for dpy 0
E/qdhwcomposer( 240): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Function not implemented
E/qdhwcomposer( 240): hwc_sync: acq_fen_fd_cnt=1 flags=16 fd=16 dpy=0 numHwLayers=2
E/qdoverlay( 240): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Function not implemented
E/qdoverlay( 240): static bool overlay::eek:verlay::displayCommit(const int&,
TeamMex said:
Pff we need work a lot xD
Click to expand...
Click to collapse
@K3VYNC how you make mistakes? My port was successful with one try! However, some sensors and phone app did not work, but the phone worked. @K3VYNC, from which device you ported it?
im waiting for this YOHOO !! MIUI in MOTO G
i hope this will be avaialble on xt1033 variant
kromuch said:
@K3VYNC how you make mistakes? My port was successful with one try! However, some sensors and phone app did not work, but the phone worked. @K3VYNC, from which device you ported it?
Click to expand...
Click to collapse
Your port was from what device ?
it's more EASY make it from source
kromuch said:
@K3VYNC how you make mistakes? My port was successful with one try! However, some sensors and phone app did not work, but the phone worked. @K3VYNC, from which device you ported it?
Click to expand...
Click to collapse
instead of bashing, why dont you post your build or help the guy porting it?
TeamMex said:
Your port was from what device ?
it's more EASY make it from source
Click to expand...
Click to collapse
From the official Nexus 5 (adding to the OP)
Sent from my Moto G using XDA Free mobile app
K3VYNC said:
From the official Nexus 5 (adding to the OP)
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
maybe is better to port it from xiaomi mi2 due to the screen resolution
http://en.miui.com/download-2.html
kromuch said:
Here is my kernel with shelld in ramdisk, recently I've ported MIUI to Moto G, but it had many software bugs, so, I deleted ROM and now have only ported kernel.
Flash this manually, it's not a flashable ZIP.
Click to expand...
Click to collapse
I've added to the ROM
Sent from my Moto G using XDA Free mobile app
TeamMex said:
Your port was from what device ?
Click to expand...
Click to collapse
From Nexus 5 too.
K3VYNC said:
I've added to the ROM, I'm uploading later today
Click to expand...
Click to collapse
Does ROM boot now?
Important! Forgot to say that this kernel is from GPE ROM, so you must flash GPE before flashing MIUI, because Motorola ROM and GPE ROM use different file systems. If anyone give me last Moto-stock kernel (from backup or by another way), I'll add required files to it too. But for Moto-stock kernel must be Moto-stock based port, the same for GPE kernel.
kromuch said:
Yes, from Nexus 5 too.
Does ROM boot now?
Important! Forgot to say that this kernel is from GPE ROM, so you must flash GPE before flashing MIUI, because Motorola ROM and GPE ROM use different file systems.
Click to expand...
Click to collapse
Okay, thanks bro (added to the OP) and no, I couldn't test it.
And yes, I can send you the stock kernel
Sent from my Moto G using XDA Free mobile app
K3VYNC said:
Okay, thanks bro (added to the OP) and no, I couldn't test it, but it's uploading (almost DONE), can you test it?
And yes, I can send you the stock kernel
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
will download it and report...
Edit: download gets canceled at end moment.
The latest build gets an error 509
antarix said:
will download it and report...
Edit: download gets canceled at end moment.
The latest build gets an error 509
Click to expand...
Click to collapse
Try the latest one, tell me if something is changed.
Now I have dev acess to AndroidFileHost! :victory:
Sent from my Moto G using XDA Free mobile app
Cooooll, i watiiiing
i managed to get L builded and have the first bootlog =D
http://pastebin.com/u30kDNhd
changes yet made:
L device tree
hardware/ti/omap4xxx
kernel
Kernel build script
i attached my working boot.img because asop seems not build the kernel from source.
Hmm, from the logs it looks like graphics issues, might need some new cflags.
Sent from my GT-i8190 using XDA Free mobile app
01-01 13:50:02.825: E/HAL(115): dlopen failed: could not load library "liblgehdmi.so" needed by "hwcomposer.omap4.so"; caused by could not load library "libhdcp.so" needed by "liblgehdmi.so"; caused by can't unprotect loadable segments for "libhdcp.so": Permission denied
Click to expand...
Click to collapse
i dont know, i think it has something todo with sepolicy for surfaceflinger
Then we need to add it to device tree
Sent from my GT-i8190 using XDA Free mobile app
Sources still downloading. I'm glad we are getting an early start on this. Don't want to get caught behind again like with kitkat:thumbup:
Sent from my GT-i8190 using XDA Free mobile app
seems our hwc is outdated again..^^
im trying to build that one from ti with latest ddk driver
troopii said:
seems our hwc is outdated again..^^
im trying to build that one from ti with latest ddk driver
Click to expand...
Click to collapse
Sweet, im working on another kernel and im running in to errors in driver/video/omap2.somthing to do with enabling s3d.can you believe my sources still downloading.lol
Sent from my LG-D620 using XDA Free mobile app
that egl stuff is getting crazy, but gralloc is up...
Code:
11-08 09:00:20.650: I/SurfaceFlinger(114): SurfaceFlinger is starting
11-08 09:00:20.651: I/SurfaceFlinger(114): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
11-08 09:00:20.758: D/libEGL(114): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
11-08 09:00:20.922: D/libEGL(114): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
11-08 09:00:21.019: D/libEGL(114): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
11-08 09:00:21.125: W/surfaceflinger(114): type=1400 audit(0.0:21): avc: denied { read } for name="gralloc.omap4.so" dev=mmcblk0p7 ino=1355 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:unlabeled:s0 tclass=file
11-08 09:00:21.134: W/libEGL(114): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
11-08 09:00:21.166: I/gralloc(114): using (fd=11)
11-08 09:00:21.166: I/gralloc(114): id = omapfb
11-08 09:00:21.166: I/gralloc(114): xres = 480 px
11-08 09:00:21.166: I/gralloc(114): yres = 800 px
11-08 09:00:21.166: I/gralloc(114): xres_virtual = 480 px
11-08 09:00:21.166: I/gralloc(114): yres_virtual = 1600 px
11-08 09:00:21.166: I/gralloc(114): bpp = 32
11-08 09:00:21.166: I/gralloc(114): r = 16:8
11-08 09:00:21.166: I/gralloc(114): g = 8:8
11-08 09:00:21.166: I/gralloc(114): b = 0:8
11-08 09:00:21.166: I/gralloc(114): width = 57 mm (213.894730 dpi)
11-08 09:00:21.166: I/gralloc(114): height = 94 mm (216.170212 dpi)
11-08 09:00:21.166: I/gralloc(114): refresh rate = 60.00 Hz
11-08 09:00:21.187: W/surfaceflinger(114): type=1400 audit(0.0:22): avc: denied { read } for name="gralloc.omap4.so" dev=mmcblk0p7 ino=1355 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:unlabeled:s0 tclass=file
11-08 09:00:21.200: E/ti_hwc(114): Composer HAL failed to load compatible Graphics HAL
11-08 09:00:21.200: E/SurfaceFlinger(114): composer device failed to initialize (Invalid argument)
11-08 09:00:21.200: W/SurfaceFlinger(114): no suitable EGLConfig found, trying a simpler query
11-08 09:00:21.200: A/SurfaceFlinger(114): no suitable EGLConfig found, giving up
11-08 09:00:21.200: A/SurfaceFlinger(114): --------- beginning of crash
11-08 09:00:21.200: A/libc(114): Fatal signal 6 (SIGABRT), code -6 in tid 114 (surfaceflinger)
Some guys iplemented it in p760,p769. Maybe you can ask how they did it.
Sent from my LG-D620 using XDA Free mobile app
what ive seen they all stay on [email protected]
maybe its enough just to update gralloc and the hwcomposer.
Hi troopii, this guy did it for l9, may checkout his github. http://forum.xda-developers.com/showthread.php?t=2728404
[KANG][4.4.4][P760/P765/P768/P769] CyanogenMod 11 for LG Optimus L9 - 20141012
Sent from my LG-D620 using XDA Free mobile app
Inits everything up to the hwcomposer.
tryed it now on nameless with the ti hwc and got this:
Code:
11-09 08:13:55.625: E/ti_hwc(127): failed to get display info (22): m
11-09 08:13:55.625: E/SurfaceFlinger(127): composer device failed to initialize (Invalid argument)
11-09 08:13:55.625: I/SurfaceFlinger(127): Using composer version 1.0
11-09 08:13:55.625: W/SurfaceFlinger(127): getting VSYNC period from fb HAL: 14705882
11-09 08:13:55.625: W/SurfaceFlinger(127): no suitable EGLConfig found, trying a simpler query
11-09 08:13:55.625: A/SurfaceFlinger(127): no suitable EGLConfig found, giving up
11-09 08:13:55.625: A/libc(127): Fatal signal 6 (SIGABRT) at 0x0000007f (code=-6), thread 127 (surfaceflinger)
whats going wrong?
Im now trying to get hwc_ti working on nameless
My sources finished this morning, I'm struggling with kernel. Got most compile errors sorted but it won't build the submodules for WiFi. I don't know why
Sent from my GT-i8190 using XDA Free mobile app
Disable kernel building in your boardconfig.mk.
you have to build the kernel and modules manual or use that from your cm11.
If yiu have the zImage copy it to out/target/product/p920 and rename it to kernel.
Also you have to copy your modules to system/lib/modules in your out folder
Sent from my LG-D855 using XDA Free mobile app
OK, I have put the kernel aside for now to start on 5.0, what I did find thou is that in the kernel there a 3main folders for display. Drivers/video/omap2, include/video has most of the header files for the drivers there and include/Linux .with the kernel I was testing, a lot of the s3d compiler warnings can be sorted through these folders. I wish I knew some programming languages, so that I can tackle it. Some where in there can may also set the 1.9 GPU binaries. The omaplfb folder in drivers/video/omap2 has a lot to do with the implementation of the PVR stuff it seems.
Sent from my GT-i8190 using XDA Free mobile app
I cant believe our O3D will go far this way looking further to try this. Hopefully it will be a success. Cheers mate! I wish i could help you guys.
@berni987654321 any news? i hope you have it booted =D
@troopii, @bernie9876t4321 any news?any logs we can do research on?
I havent started with 5.0 yet trying to get video working for cm and nameless.
Sent from my LG-D620 using XDA Free mobile app
shaqfu786 said:
@troopii, @bernie9876t4321 any news?any logs we can do research on?
I havent started with 5.0 yet trying to get video working for cm and nameless.
Sent from my LG-D620 using XDA Free mobile app
Click to expand...
Click to collapse
About Video Recording i remember that i fix it once by copy some Missing files.
i make compare between cm10 and PacMan 4.2.2 rom and copy the missing files in bin etc lib vendor etc... and make them as flashzip and flash it
and video recording work.
u should try it maybe it will work also with cm or nameless.
@tropii I had to reset my vm because I ****ed the hard disk image some how I'll build tomorrow a new build when the download of the sources are done.
Sent from my LG-P920 using xda app-developers app