Related
Hey all your friendly neighborhood tinkerer here.
I have ported and flashed 4.3 from the S4 leak to the I605. So far, the flash went successful using Vramc3 root odexed as a base.
Watching the logcat during install everything goes fine then i run into this:
Code:
I/DEBUG ( 1972):
I/DEBUG ( 1972): memory map around fault addr deadd00d:
I/DEBUG ( 1972): bedf2000-bee13000 [stack]
I/DEBUG ( 1972): (no map for address)
I/DEBUG ( 1972): ffff0000-ffff1000 [vectors]
I/DEBUG ( 1972): [email protected] -k -t -z -d -o /data/log/dumpstate_app_native -m 7340
I/dumpstate( 7458): begin
D/MDnsDS ( 7338): MDnsSdListener::Hander starting up
D/MDnsDS ( 7338): MDnsSdListener starting to monitor
D/MDnsDS ( 7338): Going to poll with pollCount 1
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
^[I/ServiceManager( 7339): Waiting for service sensorservice...
I/VPNCStarter( 1996): Message channel file directory does not exist
D/VoldCmdListener( 1967): asec list
I/ServiceManager( 7339): Waiting for service sensorservice...
I/dumpstate( 7458): done
The android dev guide doesn't really help out. Just says that its trying to start the device sensor service. Here starts the issue. Which service? Barometer, gyroscope, compass ??????? Anybody seen this before could shed some light on this I would be greatly appreciative.
Or is it that the framework is just not compatible with this phone yet? Let me know what you think.
dragonstalker said:
Hey all your friendly neighborhood tinkerer here.
I have ported and flashed 4.3 from the S4 leak to the I605. So far, the flash went successful using Vramc3 root odexed as a base.
Watching the logcat during install everything goes fine then i run into this:
Code:
I/DEBUG ( 1972):
I/DEBUG ( 1972): memory map around fault addr deadd00d:
I/DEBUG ( 1972): bedf2000-bee13000 [stack]
I/DEBUG ( 1972): (no map for address)
I/DEBUG ( 1972): ffff0000-ffff1000 [vectors]
I/DEBUG ( 1972): [email protected] -k -t -z -d -o /data/log/dumpstate_app_native -m 7340
I/dumpstate( 7458): begin
D/MDnsDS ( 7338): MDnsSdListener::Hander starting up
D/MDnsDS ( 7338): MDnsSdListener starting to monitor
D/MDnsDS ( 7338): Going to poll with pollCount 1
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
^[I/ServiceManager( 7339): Waiting for service sensorservice...
I/VPNCStarter( 1996): Message channel file directory does not exist
D/VoldCmdListener( 1967): asec list
I/ServiceManager( 7339): Waiting for service sensorservice...
I/dumpstate( 7458): done
The android dev guide doesn't really help out. Just says that its trying to start the device sensor service. Here starts the issue. Which service? Barometer, gyroscope, compass ??????? Anybody seen this before could shed some light on this I would be greatly appreciative.
Or is it that the framework is just not compatible with this phone yet? Let me know what you think.
Click to expand...
Click to collapse
Would it have anything to do with the s4 having sensors the note 2 doesn't? Such as temperature and humidity?
Sent from my SCH-I605 using xda premium
dragonstalker said:
Hey all your friendly neighborhood tinkerer here.
I have ported and flashed 4.3 from the S4 leak to the I605. So far, the flash went successful using Vramc3 root odexed as a base.
Watching the logcat during install everything goes fine then i run into this:
Code:
I/DEBUG ( 1972):
I/DEBUG ( 1972): memory map around fault addr deadd00d:
I/DEBUG ( 1972): bedf2000-bee13000 [stack]
I/DEBUG ( 1972): (no map for address)
I/DEBUG ( 1972): ffff0000-ffff1000 [vectors]
I/DEBUG ( 1972): [email protected] -k -t -z -d -o /data/log/dumpstate_app_native -m 7340
I/dumpstate( 7458): begin
D/MDnsDS ( 7338): MDnsSdListener::Hander starting up
D/MDnsDS ( 7338): MDnsSdListener starting to monitor
D/MDnsDS ( 7338): Going to poll with pollCount 1
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
I/ServiceManager( 7339): Waiting for service sensorservice...
^[I/ServiceManager( 7339): Waiting for service sensorservice...
I/VPNCStarter( 1996): Message channel file directory does not exist
D/VoldCmdListener( 1967): asec list
I/ServiceManager( 7339): Waiting for service sensorservice...
I/dumpstate( 7458): done
The android dev guide doesn't really help out. Just says that its trying to start the device sensor service. Here starts the issue. Which service? Barometer, gyroscope, compass ??????? Anybody seen this before could shed some light on this I would be greatly appreciative.
Or is it that the framework is just not compatible with this phone yet? Let me know what you think.
Click to expand...
Click to collapse
Not sure what you did to port it, but there is an app called sensorservifes in the stock s4. Try deleting it to get it booting
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Not sure what you did to port it, but there is an app called sensorservifes in the stock s4. Try deleting it to get it booting
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Ok. i'll try that. I know there is also a libsensorservice.so and a sensorservice file in the bin directory. So didn't know if it was as simple as deleting an apk.
No sensor.apk in the 4.3 download I have. Redownloading it.
Update. replaced sensorservice.apk , reflashed, and still getting same logcat . Clean install, does the dump, then keeps looping saying waiting for service sensorservice.
dragonstalker said:
Ok. i'll try that. I know there is also a libsensorservice.so and a sensorservice file in the bin directory. So didn't know if it was as simple as deleting an apk.
No sensor.apk in the 4.3 download I have. Redownloading it.
Update. replaced sensorservice.apk , reflashed, and still getting same logcat . Clean install, does the dump, then keeps looping saying waiting for service sensorservice.
Click to expand...
Click to collapse
Make sure you add your sensor libs to system/lib/hw
Sent from my SPH-L710 using xda app-developers app
Bimo!
Sent from my SCH-I605 using Tapatalk 2
theres a sensorhubservice and sensor service file in the note 2's /system/bin and libsersorhubservice.so and libsensorservice.so in /system/lib, copy these into your ported rom.
thanks for all the help it if I so far. if anybody is good at coding the link to what I've done so far is posted below.
I605VRAMC3-4.3test3.zip https://www.dropbox.com/s/t1k3p6anae3nvs7/I605VRAMC3-4.3test3.zip
dragonstalker said:
thanks for all the help it if I so far. if anybody is good at coding the link to what I've done so far is posted below.
I605VRAMC3-4.3test3.zip https://www.dropbox.com/s/t1k3p6anae3nvs7/I605VRAMC3-4.3test3.zip
Click to expand...
Click to collapse
Is your source from S4? can you port it to Note II N 7100?
dynamic503 said:
Is your source from S4? can you port it to Note II N 7100?
Click to expand...
Click to collapse
Its the s4 ported using i605vramc3 odexed rooted as a base.
Sent from my SCH-I605 using xda premium
dragonstalker said:
Its the s4 ported using i605vramc3 odexed rooted as a base.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Any update on your progress? I would love to get a stable stock 4.3 or 4.2 on my note 2...
Abrasher said:
Any update on your progress? I would love to get a stable stock 4.3 or 4.2 on my note 2...
Click to expand...
Click to collapse
4.2? There are stable 4.2.2 roms.. I use tegraowners 4.2.2 rom, based on CM. No bugs, faster than a N4 and better batterylife than stock sammy roms.
Gonna be cool when our Note 2 gets 4.3 though.
dragonstalker said:
Its the s4 ported using i605vramc3 odexed rooted as a base.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
I'm trying to do the same thing on my I747 (S3) using the mako 4.3 rip, but I can't get the kernel to finish booting (I'm using CM 10.1 nightly as a base and attempting to use its kernel)
I've pulled the last_kmsg but I don't see anything as obvious as your log. (Can't get ADB to connect during boot, so I'd assume the kernel isn't making it far enough to start up adbd) I've posted the kmsg here: [link] Any tips?
dragonstalker said:
thanks for all the help it if I so far. if anybody is good at coding the link to what I've done so far is posted below.
I605VRAMC3-4.3test3.zip https://www.dropbox.com/s/t1k3p6anae3nvs7/I605VRAMC3-4.3test3.zip
Click to expand...
Click to collapse
most likely I'm wrong here but it sounds like a smiliar issue we had with 4.2.2 in the beginning or am I wrong. Aren't we probably missing the correct files for the sensorhub?
If I'm recalling right it prevented us from booting 4.2.2 too until someone came up with a dirty hacky way and lateron it was done properly by somebody else. (just a far memory though)
dstruct2k said:
I'm trying to do the same thing on my I747 (S3) using the mako 4.3 rip, but I can't get the kernel to finish booting (I'm using CM 10.1 nightly as a base and attempting to use its kernel)
I've pulled the last_kmsg but I don't see anything as obvious as your log. (Can't get ADB to connect during boot, so I'd assume the kernel isn't making it far enough to start up adbd) I've posted the kmsg here: [link] Any tips?
Click to expand...
Click to collapse
doesn't that sound similiar: [ 299.419929] [1: recovery: 111] Sensors unset: 7fff ?
lolmensch said:
most likely I'm wrong here but it sounds like a smiliar issue we had with 4.2.2 in the beginning or am I wrong. Aren't we probably missing the correct files for the sensorhub?
If I'm recalling right it prevented us from booting 4.2.2 too until someone came up with a dirty hacky way and lateron it was done properly by somebody else. (just a far memory though)
doesn't that sound similiar: [ 299.419929] [1: recovery: 111] Sensors unset: 7fff ?
Click to expand...
Click to collapse
That line is just the system unloading the sensors after I issued a hard-reboot command by holding down the power button. I gave it 5 minutes to try and boot (299 seconds according to the kernel, not bad for estimating ) and then rebooted back to recovery to pull the kmsg. The touch event a few lines up was me showing where the reboot command was sent.
The I/DEBUG lines will give you a traceback to where the original error occurred.
Sent from my buttered S3
CNexus said:
The I/DEBUG lines will give you a traceback to where the original error occurred.
Sent from my buttered S3
Click to expand...
Click to collapse
you should check your build.prop as im sure that is part of your problem. You should use the one that came with 4.3 and just change the lines you need
A tip, if not referred to already. You should use an AOSP base not a CM base. It'll be much easier.
emwno said:
A tip, if not referred to already. You should use an AOSP base not a CM base. It'll be much easier.
Click to expand...
Click to collapse
CM is AOSP......
CNexus said:
CM is AOSP......
Click to expand...
Click to collapse
I agree. But you clearly misunderstood what I am saying....
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
I try to port Sense from HTC One SV on our Xperia L.
I replaced BOOTCLASSPATCH in Extended stock kernel v2 from original sense kernel. Also I little edited ROM.
But my port freezes on bootanimation.
I need your help...
Last log - http://forum.xda-developers.com/showpost.php?p=47577503&postcount=22
Rom (last build) - https://drive.google.com/file/d/0B5kucJeEvGrGcFFqRmlqSG1uQ0E/edit?usp=sharing
Modified kernel - https://docs.google.com/file/d/0B5kucJeEvGrGTVNCVWhEdVNwYUE/edit
Original ROM - http://fs1.d-h.st/download/00053/hDK/k2u_JB_2.14.401.107_stock_odexed_01_06_13.zip
Logcat Logcat Logcat!!!
The-Superman said:
Logcat Logcat Logcat!!!
Click to expand...
Click to collapse
I know it, but I have some problems with adb, than help needed
like81 said:
I know it, but I have some problems with adb, than help needed
Click to expand...
Click to collapse
Sorry but no one can tell your problem without logcat. We cannot see what causes you to stay on bootlogo just by looking at the image. Try Advanced Logcat Viewer as it includes working adb and an advanced logcat viewer ( http://forum.xda-developers.com/showthread.php?t=2454610)
Sent from my E10i using xda premium
pongnamu said:
Sorry but no one can tell your problem without logcat. We cannot see what causes you to stay on bootlogo just by looking at the image. Try Advanced Logcat Viewer as it includes working adb and an advanced logcat viewer ( http://forum.xda-developers.com/showthread.php?t=2454610)
Click to expand...
Click to collapse
Thanks, i will try to do it.
Okay, I got logs!
It's my logs.
I'm thinking how to fix it...
I really hope to see this rom on our xl
Sent from my C2104
Keeping an eye on this! :good:
Firstly I must fix fatal errors....
F/libc (13914): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 13914 (zygote)
F/libc (13777): Failed while talking to debuggerd: Connection reset by peer
F/libc (13914): Failed while talking to debuggerd: Connection reset by peer
F/libc (13929): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 13929 (zygote)
F/libc (14062): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 14062 (mediaserver)
F/libc (14062): Unable to open connection to debuggerd: Connection refused
Click to expand...
Click to collapse
It's all fatal errors. This problems take place in libc.so, I think...
After few fixes, some errors have disappeared.
New log.
like81 said:
After few fixes, some errors have disappeared.
New log.
Click to expand...
Click to collapse
is it sense 5? If it is, u need ion kernel right?
Tausif Ahmed said:
is it sense 5? If it is, u need ion kernel right?
Click to expand...
Click to collapse
No, it's sense 4+. It doesn't need ION.
P.S. HTC One SV hasn't sense 5
P.P.S. And I have HTC Explorer too)))
As of what I saw in the logcat ,, There are some libs missing..Try to add them or fix them if they exist
Sparksys said:
As of what I saw in the logcat ,, There are some libs missing..Try to add them or fix them if they exist
Click to expand...
Click to collapse
Missing libs... Okay, thanks.
F/libc (12893): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 12893 (zygote)
And what is this error? What is fatal signal?
The new fixes. And a new log
Don't watch to errors with camera and audio_policy, I'll fix it later.
I was thinking few days and I understand that this errors are linked together!!!
E/JNIHelp (10516): Native registration unable to find class 'com/android/internal/os/RuntimeInit', aborting
F/libc (10516): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 10516 (zygote)
Click to expand...
Click to collapse
I think android can't find this class in services.jar. And I think that if I add it to services.jar, errors dissapear!
But I'm not sure...
may be changing in drivers fix some problems
Its not working broo...
Sent by using xda premium
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
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