Related
Hi all,
I have tried to build CM 10.1 based Ubuntu Touch for Samsung Tab 2 10.1 but all version will be boot looping only. I have not much Android background but I have read about logcat and reading last kernel messages that could reveal reasons for boot looping. Currently I can seen login screen for a few seconds.
Ubuntu Touch has a limited version of Cyanogenmod so it probably requires different ways to debug, track down the kernel fault. If you have been porting Ubuntu to some other Samsung Tablet what ways you have used? Or would you have some handy tip in your sleeve?
/data/ubuntu/var/log contains some informations but none seems to be directly relating to kernal fault.
Thank you for all suggestions how to proceed with fault determination.
simosays said:
Hi all,
I have tried to build CM 10.1 based Ubuntu Touch for Samsung Tab 2 10.1 but all version will be boot looping only. I have not much Android background but I have read about logcat and reading last kernel messages that could reveal reasons for boot looping. Currently I can seen login screen for a few seconds.
Ubuntu Touch has a limited version of Cyanogenmod so it probably requires different ways to debug, track down the kernel fault. If you have been porting Ubuntu to some other Samsung Tablet what ways you have used? Or would you have some handy tip in your sleeve?
/data/ubuntu/var/log contains some informations but none seems to be directly relating to kernal fault.
Thank you for all suggestions how to proceed with fault determination.
Click to expand...
Click to collapse
Succesfully compiled (@ the other thread), see my github for modifications (only forked 2 repos, kernel + device tree, both from Kumajaya's hub)
For the debugging things, isn't the documentation enough ? You should know how to work your way out
- https://wiki.ubuntu.com/Touch
- https://wiki.ubuntu.com/Touch/Testing
- http://developer.ubuntu.com/packaging/html/fixing-a-bug-example.html
Debugging errors in P5100
Sympnotic said:
Succesfully compiled (@ the other thread), see my github for modifications (only forked 2 repos, kernel + device tree, both from Kumajaya's hub)
For the debugging things, isn't the documentation enough ? You should know how to work your way out
- <removed>
- <removed>
- <removed>
Click to expand...
Click to collapse
Thank you Symptonic!
I am finally debugging ...would you happened to see any similar messages when making porting to other Samsung devices?
E/linker ( 690): ics/linker.c:1598| WARNING: Skipping libc.so
...
E/linker ( 690): ics/linker.c:1072| ERROR: Library 'libOpenVG.so' not found
...
E/linker ( 690): ics/linker.c:1072| ERROR: Library 'libPVROGL.so' not found
E/linker ( 690): ics/linker.c:1072| ERROR: Library 'libPVROCL.so' not found
D/libEGL ( 690): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 690): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
Click to expand...
Click to collapse
As far as I understand that relates to device/samsung/omap4-common/ and to device (p5100) which does not support libOpenVG.so. Anyway when those errors are shown couple of times in logcat device will reboot itself see "pastebin". Would you have any suggestions how to configure device settings or track down the error?
Thank you for all comments and ideas!
Entire logcat in pastebin: /J2mNneYw
Hi all. Time to open new Lollipop thread for honor.
http://forum.xda-developers.com/and...u8860-legacyhuawei-roms-t3032641#post58893010
[/COLOR]Huawei Honor u8860 Development
HI all. after many of you asked me to open a thread about my cm11 builds for honor, i finally decided to do it...
so here is my latest build of cm11 and i will provide also some others kitkat flavour as beanstalk and mokee os and many others....
bugs, wifi tether not working but ok with third party app.
U8800pro users: read post 3
Mini How-to compile 4.4.2 for Huawei honor (u8860) : http://forum.xda-developers.com/showpost.php?p=52922053&postcount=897
see here for wifi tethering
http://forum.xda-developers.com/showpost.php?p=50156494&postcount=3710 (i attached tethering apk)
B919 stock rom base
http://www.mediafire.com/download/z136402ocabf4t6/b919.rar
TWRP-2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55266722&postcount=1444
TeamWin recovery 2.7.1.0-u8860 update= fixed usb storage and file manager http://forum.xda-developers.com/showpost.php?p=54552750&postcount=1282
older : http://forum.xda-developers.com/showpost.php?p=53376000&postcount=1046
TeamWin recovery 2.7.1.0-u8800pro
http://forum.xda-developers.com/showpost.php?p=53378089&postcount=1047
TeamWin recovery 2.7.0.0
http://www.mediafire.com/download/hre1fd1czaq88gw/TWRP2.7-HUAWEIU8860-recovery.img
TeamWin recovery 2.6.0.0
http://www.mediafire.com/download/gi1ng2tp5rd0d8e/recovery-twrp-2.6.0.0-u8860.img
Changelog
http://forum.xda-developers.com/showpost.php?p=51510415&postcount=284
Downloads:
4.4.4
NEW!=Dirty_Unicorn: http://www.mediafire.com/download/kww6t63nbm1rnan/DU_u8860_4.4.4_20140901-1128.v7.9-UNOFFICIAL.zip
new=AOSB http://www.mediafire.com/download/x6m3aqx74nbpc71/aosb_kk_1.3.7_u8860.zip
NEW!=SOKP : http://www.mediafire.com/download/aklta4l3yb6qauk/SOKP-KK444-V-01-20140808-u8860.zip
PacMAn : http://www.mediafire.com/download/yspcsrir7aii7ec/pac_u8860_4.4.4.Beta-1.0_20140702-140013.zip
BeanStalk: http://www.mediafire.com/download/bby7bfpurifbx41/BeanStalk-4.4.4001-20140701-u8860.zip
http://www.mediafire.com/download/36zs4gx3pmc3o2o/BeanStalk-4.4.4001-20140621-u8860.zip
CyanogenMod: http://www.mediafire.com/download/9o8zl2cv8x9ephx/cm-11-testApps2SD-u8860-DAZ.zip --->Apps 2 Sd fixed
older: http://www.mediafire.com/download/1ukim9k4wx55vto/cm-11-444-20140621-UNOFFICIAL-u8860.zip
BlueLightning: http://www.mediafire.com/download/10wzaqvylq6zzx5/BlueLightning-444-20140620-u8860.zip
MokeeOs: http://www.mediafire.com/download/eihlpupd11hz949/MK44.4-u8860-201406201753-UNOFFICIAL.zip
NamelessRom: To come... ^^
Before 4.4.4:http://forum.xda-developers.com/showpost.php?p=53626292&postcount=1142
kernel source: https://github.com/desalesouche/Project-X5pro-Kernel-u8860-u8800pro
TeamWin recovery 2.6.0.0 http://www.mediafire.com/download/gi....0.0-u8860.img
Thread for gamers : http://forum.xda-developers.com/showthread.php?t=2615514
Credits:
- @CrysisLTU
- @Rittick
- @herna
- @gold-concert
- @h33x
- @j.Moihack
-Dazzozo
-ShenduOs
-Fredvj
and many others that i will add as soon as i remember.
thread about google now : http://forum.xda-developers.com/showthread.php?t=2649349
op in construction........
to mods, move that thread to devdb if needed...
in devdb thread my device is not represented .
HOW TO INSTALL
Make sure you're running a proper working ClockworkMod-Recovery/TWRP and that you are on B919 stock rom
Copy Gapps and CM11 ZIPs to your SDCard
Boot into Recovery
Wipe data/factory reset
Wipe Cache and Dalvik Cache
Format System
Flash CM11 zip from SDCard
Reboot
HOW TO COMPILE 4.4.2 ROM FOR HUAWEI HONOR------> http://forum.xda-developers.com/showpost.php?p=52922053&postcount=897
u8800pro users: how-to port rom from u8860 to u8800pro
U8800 pro more to come...
4.4.3 cm11 for u8800pro : http://www.mediafire.com/download/1one0utzb198uh2/cm-11-20140605-UNOFFICIAL-u8800pro.zip
mokee: http://www.mediafire.com/download/jcwcjacnonq32qq/MK44.2-u8800pro-201403150029-UNOFFICIAL.zip
cm11 m3 : http://www.mediafire.com/download/8ikou81fswnkli8/cm-11-m3-20140225-u8800pro-DynamiVSync2.zip
edit: i uploaded here for u8800pro user the bcm4329 wifi module in case some have problem with wifi...
see here how-to port rom from u8860 to u8800pro:
http://forum.xda-developers.com/showpost.php?p=53176802&postcount=961
NEW!our member @Lihis is porting all news rom for u8800pro follow the link...
don't forget to thank him
http://forum.xda-developers.com/showpost.php?p=53520636&postcount=1092
hello, des. thx for great work. i have some ideas, what need the rom:
1. sound for kernel is bad (bass not clear, angel's kernel have good sound)
2. poor sensitivity of the microphone, I was hard to hear. not only me, many users 4pda ask, how to up sensity of micro.
3. if u have time and desire, pls, build for us CarbonROM.
4. pls, need changlog in upper post
thx
for the tether app, what should i put in settings for it to work ?
Sent from my U8860 using Tapatalk
bublz654 said:
for the tether app, what should i put in settings for it to work ?
Sent from my U8860 using Tapatalk
Click to expand...
Click to collapse
link is on op
--
finr0d said:
does the cm11.0m3 include gapps? if not, could you link it in the OP?
Click to expand...
Click to collapse
cm does not support gapps. and here is the link gapps = http://www.mediafire.com/download/79s75mdbmb9bx0l/12-14_GApps_Standard_4.4.2_signed.zip
Sent from my U8860 using Tapatalk
bublz654 said:
cm does not support gapps. and here is the link gapps = http://www.mediafire.com/download/79s75mdbmb9bx0l/12-14_GApps_Standard_4.4.2_signed.zip
Sent from my U8860 using Tapatalk
Click to expand...
Click to collapse
Better to use gapps core for this device due low /system free space.
Here is an xda thread for all 4.4 gapps packages: http://forum.xda-developers.com/showthread.php?t=2012857
Here you will find gapps core and calendar/browser sync (not included in rom/gapps).
Sent from my U8860
that was gapps core, it says standard but all it includes is Google play
Sent from my U8860 using Tapatalk
Could you reupload the recovery image?
T3K0 said:
Could you reupload the recovery image?
Click to expand...
Click to collapse
cwm one?
Just have to paste the link to TWRP again.
I think something went wrong when you copied it. (It tries to open the link with the dots in it)
T3K0 said:
Just have to paste the link to TWRP again.
I think something went wrong when you copied it. (It tries to open the link with the dots in it)
Click to expand...
Click to collapse
Yep. That link on OP is corrupted. I think that was copied from here: http://forum.xda-developers.com/showpost.php?p=50136545&postcount=3703
@desalesouche , in OP should be mentioned that before flashing we need to be on b919 ROM.
I duplicate my message from main thread and in future continue posting here.
---------------START QUOTE--------------------
desalesouche said:
hello camera record doesn't work on 720P , but work on 480P . do you think that not enough ram might be cause for 720P video record? or is there other cause?...
Click to expand...
Click to collapse
Not sure, that I continue test and find this:
1) free memory size in settings apk and /proc/meminfo not equal. In settings i view, that I have 150MB free mem. In meminfo size is 64MB.
2) After record start I found in logs this errors:
Code:
E/OMXCodec( 125): [OMX.qcom.video.encoder.avc] Found supported color format: 21
E/OMX-VENC-720p( 125): get_parameter: OMX_IndexParamVideoProfileLevelQuerySupported for Input port returned Profile:1, Level:512
E/OMX-VENC-720p( 125):
E/OMX-VENC-720p( 125): venc_set_intra_period: nPFrames = 29 nBFrames = 0
I/str_params( 125): key: 'tunneled-input-formats' value: 'get'
D/AudioHardware7x30( 125): AudioHardware::openInputStream devices 8000000 format 1 channels 16 samplerate 48000
D/AudioSource( 125): Start autoramp from 108000
D/AudioHardware7x30( 125): AudioStreamInMSM72xx::standby()
D/AudioHardware7x30( 125): AudioStreamInMSM72xx::standby()
I/MPEG4Writer( 125): limits: 702779264/0 bytes/us, bit rate: 8156000 bps and the estimated moov size 405000 bytes
I/MPEG4Writer( 125): Start time offset: 1000000 us
E/OMX-VENC-720p( 125):
[COLOR="Red"][B]E/OMX-VENC-720p( 125): ERROR: MMAP_FAILED in o/p alloc buffer[/B][/COLOR]
E/OMXNodeInstance( 125): OMX_AllocateBuffer failed with error -2147479552 (0x80001000)
E/OMXCodec( 125): allocate_buffer_with_backup failed
E/OMXCodec( 125): [OMX.qcom.video.encoder.avc] Allocate Buffer failed - error = -2147483648
E/OMXCodec( 125): [OMX.qcom.video.encoder.avc] init failed: -2147483648
E/MediaRecorder( 3770): start failed: -2147483648
E/CAM_VideoModule( 3770): Could not start media recorder.
E/CAM_VideoModule( 3770): java.lang.RuntimeException: start failed.
E/CAM_VideoModule( 3770): at android.media.MediaRecorder.start(Native Method)
E/CAM_VideoModule( 3770): at com.android.camera.VideoModule.startVideoRecording(VideoModule.java:1194)
E/CAM_VideoModule( 3770): at com.android.camera.VideoModule.onShutterButtonClick(VideoModule.java:532)
E/CAM_VideoModule( 3770): at com.android.camera.ShutterButton.performClick(ShutterButton.java:126)
E/CAM_VideoModule( 3770): at android.view.View$PerformClick.run(View.java:18429)
E/CAM_VideoModule( 3770): at android.os.Handler.handleCallback(Handler.java:733)
E/CAM_VideoModule( 3770): at android.os.Handler.dispatchMessage(Handler.java:95)
E/CAM_VideoModule( 3770): at android.os.Looper.loop(Looper.java:136)
E/CAM_VideoModule( 3770): at android.app.ActivityThread.main(ActivityThread.java:5081)
E/CAM_VideoModule( 3770): at java.lang.reflect.Method.invokeNative(Native Method)
E/CAM_VideoModule( 3770): at java.lang.reflect.Method.invoke(Method.java:515)
E/CAM_VideoModule( 3770): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
E/CAM_VideoModule( 3770): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
E/CAM_VideoModule( 3770): at dalvik.system.NativeStart.main(Native Method)
V/CAM_VideoModule( 3770): Releasing media recorder.
this error really caused memory deficit.
I view current codecs and profiles, they identical with official firmware.
I try install and start old Huawei camera app and report about this.
------------------END QUOTE-----------------
I install stock camera application and have same error. symbol-to-symbol.
when I find information about qualcomm SoC hardware decoder I find this post.
Braccoz said:
hey guys, i would like to share some of my findings about the 1080p camera issue
prologue: scverhagen's 1080p hack works but only with the m4v encoder which puts out an h263 file (basically, divx quality). i also found out that the stock rom encodes both 720p and 1080p @h264 baseline lvl 4.0 while CM only encodes h264 baseline level 3.2
the findings: when you try to record 1080p h264 the camera app crashes and this is the logcat:
.....
some log code listing delete. h33x
.....
after some digging i found out that basically every phone (soc) has specific video hardware encoding capabilities and that there is a "standard" layer much like Direct3D/OpenGL for that, and is called OpenMAX (OMX).
it seems that omx implementation for every soc is, of course, closed source, but fortunately there is enough open source stuff to be able to use proprietary binary blobs (i may not be correct here, i am making educated guesses taking the info i found as a base)
so what i'm thinking currently is that the libOmxVenc.so that is provided with CM (seems like qualcomm donated/helped with the code) is intentionally limited to 720p max (and probably level 3.2 too, this would explain why the media_profiles.xml setting has no effect) and it just crashes when trying to encode anything >720p
so what i would like to try is take libOmxVenc.so from an ICS sensation stock rom and see if that is capable of encoding 1080p without modifications to the code (unlikely... 50% probability maybe but still worth a try)
Click to expand...
Click to collapse
Any ideas?
PS. I download official codec samples and documentation and try find answer inside.
jopsinas said:
Yep. That link on OP is corrupted. I think that was copied from here: http://forum.xda-developers.com/showpost.php?p=50136545&postcount=3703
@desalesouche , in OP should be mentioned that before flashing we need to be on b919 ROM.
Click to expand...
Click to collapse
I have updated to the official ICS and nothing else installed.
What are the steps to install this?
Do I have have to install b919 before I can install TWRP?
I dont have the phone here right now so I would like to download everything now so I dont have to when I install everything next week.
hmm i'm not sure what we're talking about here but since that post of mine was quoted i think you'd find the followup helpful.
the real issue was the camera outputting 31 fps while the encoder supported max 30. hacks have gone into the framework to trick the camera to tell it outputs 30 fps so the encoder was happy. you can browse through commits on my github to see what was done. but that is for doubleshot so it may not have anything to do with your huawei...
h33x said:
I duplicate my message from main thread and in future continue posting here
Any ideas?
PS. I download official codec samples and documentation and try find answer inside.
Click to expand...
Click to collapse
the only clue i have is that our media-codecs and media profiles are not good...
desalesouche said:
the only clue i have is that our media-codecs and media profiles are not good...
Click to expand...
Click to collapse
I think, that error reason in kernel code.
if grep "vidc_720p_mp4_enc_mc.fw" in official kernel code, found "./drivers/video/msm/vidc/720p/resource_tracker/vcd_res_tracker.c" file. this file and it top source files should be load proprietary blobs in memory and provides interfaces for using some functions.
I try find this in 3.4 kernel.
T3K0 said:
I have updated to the official ICS and nothing else installed.
What are the steps to install this?
Do I have have to install b919 before I can install TWRP?
I dont have the phone here right now so I would like to download everything now so I dont have to when I install everything next week.
Click to expand...
Click to collapse
first install b919 stock rom.
then go in pink screen and install cmw.
then you can flash the rom following second op post
Hi all,
I currently have an Android application connecting to a device via USB OTG.
The communication is done using the libusb 1.0.9 and it's working pretty well for other devices with api level < 21.
When running the app under Android L, I get the following error from libusb_init(NULL):
type=1400 audit(0.0:107): avc: denied { read } for name="usb" dev="tmpfs" ino=24433 scontext=u:r:untrusted_app:s0 tcontext=u: object_r:usb_device:s0 tclass=dir
A/libc(12605): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 12605 (mapp.sdk.sample)
Click to expand...
Click to collapse
I'm compiling libusb 1.0.9 using latest NDK 10c.
I don't think it's ART runtime issue as the app works on Android 4.4.4 with ART enabled instead of Dalvik.
Anyone familiar with this issue?
Can this be related to PIE?
Thank you.
SELinux problem
Hi all,
I've installed "SELinuxModeChanger" on my nexus 5 and changed the SELinux mode to Permissive and it seems to fix the problem.
The question is how to make my app work under the default Enforcing mode.
This thread is meant to share informations about trying to build a custom rom (CM, Omnirom...) for Lenovo Tab2 A7-10F
I'm currently trying to build CM12.1 using source
Any comment, hint, link, collaboration is welcome
Previously...
Previously...
[email protected] said:
Now time for new rom , i think you should try out building any cm based rom , omni is 75% Aosp so there might be some issues.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
pix106 said:
How can AOSP be an issue ? I always choose opensource when possible.
Click to expand...
Click to collapse
[email protected] said:
For mediatek open sources are not totally compatible with aosp's . every mtk chipset has same issue. So you can try out other others.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
pix106 said:
Ok, i may try some other rom though.
Thanks for your advice.
Do you have any info/link to mediatek sources ?
Click to expand...
Click to collapse
MaRtYy01 said:
Yep,agreed.With the years cyanogenmod went on its own and its not really based on aosp right now,while omni is more aosp based rom.
Click to expand...
Click to collapse
[email protected] said:
You can try out official sources with stock kernel , i have only links for mt6582 and mt6592 sources for now.
Sent from my A311 using XDA-Developers mobile app
---------- Post added at 03:31 AM ---------- Previous post was at 02:52 AM ----------
Can you link me any device/vendor tree . I'll try to compile cm12.1.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
pix106 said:
A few month ago, with a friend we did this for omnirom, we got boot (prebuilt kernel), graphics, but no wifi etc... : https://github.com/PixNDom/android_device_lenovo_Tab2A710F https://github.com/PixNDom/android_vendor_lenovo_Tab2A710F (other repos https://github.com/PixNDom).
We stopped as we did not know how to go on.
Yesterday after your advice i started a cm12.1 branch on my github (https://github.com/pix106/android_device_lenovo_Tab2A710F/blob/cm12.1), and got TWRP running using cm12.1 sources (with wrong device id, but it does not matter now).
I tried building the kernel again using lenovo sources (https://github.com/pix106/android_kernel_lenovo_Tab2A710F/tree/lenovo_osc_201511), with cm12, i got the same result than i got with omnirom : no graphics, "GTP Reset", i2C errors...
Thanks for your help
Click to expand...
Click to collapse
pix106 said:
Previously...
Click to expand...
Click to collapse
Try compiling with stock kernel ,
Sent from my A311 using XDA-Developers mobile app
That's what i do, i use prebuilt stock kernel.
But i would like to use kernel sources to build kernel with rom
If cm12 has the same problems as omni its most likely a kernel issue.Or there is something wrong with the sources.
I have worked on building CM12.1 today, and updated the first post
System is booting, adb and logcat work.
I added a few mali and hw related blobs, and a script to extract blobs from a file system dump instead of using adb to extract them from a running stock rom.
Any comment, hint, link, collaboration is welcome
pix106 said:
I have worked on building CM12.1 today, and updated the first post
System is booting, adb and logcat work.
I added a few mali and hw related blobs, and a script to extract blobs from a file system dump instead of using adb to extract them from a running stock rom.
Any comment, hint, link, collaboration is welcome
Click to expand...
Click to collapse
Cm12.1 booted succesfully. Then what are issues.
Sent from my A311 using XDA-Developers mobile app
[email protected] said:
Cm12.1 booted succesfully. Then what are issues.
Click to expand...
Click to collapse
Yesterday only adb and logcat were working.
Today, with a few MTK related flags, and a fresh build while i was at work, bootanimation starts
I'm going to add the missing files i detect from logcat and see what happens next...
After adding libxlog to PRODUCT_PACKAGES and providing a source for it, to avoid : cannot locate symbol "__xlog_buf_printf" referenced by "libdpframework.so", I got bootanimation.
I then added a few missing files as blobs.
Here are some errors i get :
Code:
E/audit_rules( 135): Could not read audit rules /data/misc/audit/audit.rules: No such file or directory
I/Vold ( 131): Vold 2.1 (the revenge) firing up
D/Vold ( 131): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume usbotg state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 131): Check if PFE is activated on Boot
E/Cryptfs ( 131): Bad magic for real block device /[email protected]
E/Cryptfs ( 131): Error getting crypt footer and key
W/DirectVolume( 131): Deprecated implied prefix pattern detected, please use '/devices/platform/mtk-msdc.0/mmc_host*' instead
I/[MALI][Gralloc]( 132): dlopen libtz_uree.so fail
E/HAL ( 132): dlopen failed: library "libtz_uree.so" not found
I/[MALI][Gralloc]( 207): dlopen libtz_uree.so fail
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/default/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb1/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ip6tnl0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/lo/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/android.os.Debug( 522): failed to load memtrack module: -2
E/MediaPlayerFactory(15733): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15733): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/CameraService(15733): setUpVendorTags: Vendor tag operations not fully defined. Ignoring definitions.
E/HAL (15733): load: module=/system/lib/hw/audio.primary.mt8127.so
E/HAL (15733): dlopen failed: cannot locate symbol "_ZN7android11AudioSystem24getVoiceUnlockDLInstanceEv" referenced by "audio.primary.mt8127.so"...
E/AudioFlinger(15733): int android::load_audio_interface(const char*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
E/MonoPipe(15733): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/AudioPolicyManager(15733): Default device 00000002 is unreachable
E/AudioPolicyManager(15733): Failed to open primary output
If add libtz_uree.so, hwcomposer (blob) fails, bootanimation does not start anymore.
I also tried adding libdashplayer to PRODUCT_PACKAGES, but it didn't help. And i have no source.
During a previous omnirom 5.1 build with a friend (https://github.com/PixNDom/android_device_lenovo_Tab2A710F), we used https://github.com/aomp/android_mediatek_frameworks
It allowed to build some libs, but it's rather old, i think.
Does anyone have a recent repository for mediatek sources, so hwcomposer (and other files that are blobs for now) could be built ?
pix106 said:
After adding libxlog to PRODUCT_PACKAGES and providing a source for it, to avoid : cannot locate symbol "__xlog_buf_printf" referenced by "libdpframework.so", I got bootanimation.
I then added a few missing files as blobs.
Here are some errors i get :
Code:
E/audit_rules( 135): Could not read audit rules /data/misc/audit/audit.rules: No such file or directory
I/Vold ( 131): Vold 2.1 (the revenge) firing up
D/Vold ( 131): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume usbotg state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 131): Check if PFE is activated on Boot
E/Cryptfs ( 131): Bad magic for real block device /[email protected]
E/Cryptfs ( 131): Error getting crypt footer and key
W/DirectVolume( 131): Deprecated implied prefix pattern detected, please use '/devices/platform/mtk-msdc.0/mmc_host*' instead
I/[MALI][Gralloc]( 132): dlopen libtz_uree.so fail
E/HAL ( 132): dlopen failed: library "libtz_uree.so" not found
I/[MALI][Gralloc]( 207): dlopen libtz_uree.so fail
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/default/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb1/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ip6tnl0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/lo/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/android.os.Debug( 522): failed to load memtrack module: -2
E/MediaPlayerFactory(15733): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15733): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/CameraService(15733): setUpVendorTags: Vendor tag operations not fully defined. Ignoring definitions.
E/HAL (15733): load: module=/system/lib/hw/audio.primary.mt8127.so
E/HAL (15733): dlopen failed: cannot locate symbol "_ZN7android11AudioSystem24getVoiceUnlockDLInstanceEv" referenced by "audio.primary.mt8127.so"...
E/AudioFlinger(15733): int android::load_audio_interface(const char*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
E/MonoPipe(15733): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/AudioPolicyManager(15733): Default device 00000002 is unreachable
E/AudioPolicyManager(15733): Failed to open primary output
If add libtz_uree.so, hwcomposer (blob) fails, bootanimation does not start anymore.
I also tried adding libdashplayer to PRODUCT_PACKAGES, but it didn't help. And i have no source.
During a previous omnirom 5.1 build with a friend (https://github.com/PixNDom/android_device_lenovo_Tab2A710F), we used https://github.com/aomp/android_mediatek_frameworks
It allowed to build some libs, but it's rather old, i think.
Does anyone have a recent repository for mediatek sources, so hwcomposer (and other files that are blobs for now) could be built ?
Click to expand...
Click to collapse
Can't you use something from the fire 2015 device tree?Its fully complete,the cm12.1 for it is bugless.Not sure if building roms works like that,but if you are missing drivers or something since it has the same chipset and kernel the stuff from it might work,I guess.
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford
BTW as far as I know mediatek has no official source like qualcomm,thats why building roms for it is an issue.
MaRtYy01 said:
Can't you use something from the fire 2015 device tree?Its fully complete,the cm12.1 for it is bugless.Not sure if building roms works like that,but if you are missing drivers or something since it has the same chipset and kernel the stuff from it might work,I guess.
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford
BTW as far as I know mediatek has no official source like qualcomm,thats why building roms for it is an issue.
Click to expand...
Click to collapse
Thanks, i'll have a look at this.
Either try to build it changing hardware related stuff, or pick a few things from it... or both.
I had already looked on fire 2015 source on github in 2015, it has changed since then too.
At the moment, i'm trying to build with some other mt8127 github repo (https://github.com/neporood/android_device_viking_mt8127), changing hardware stuff.
Thanks
pix106 said:
During a previous omnirom 5.1 build with a friend (https://github.com/PixNDom/android_device_lenovo_Tab2A710F), we used https://github.com/aomp/android_mediatek_frameworks
It allowed to build some libs, but it's rather old, i think.
Click to expand...
Click to collapse
sorry, i actualy wanted to mention https://github.com/aomp/android_mediatek_hardware
pix106 said:
sorry, i actualy wanted to mention https://github.com/aomp/android_mediatek_hardware
Click to expand...
Click to collapse
I'm now trying to build using this hardware/mediatek repo, it should provide libs that are blobs for now.
After adding a few .h files, it builds fine, but i don't get all the libs that should be built from this repo, although i added them to PRODUCT_PACKAGES.
I'll push these changes to github.
Even with a linux and python dev experience, i'm quite new to building roms, i may have missed a few things.
I made some ROMs for my Nexus4 and even there, you needed some closed source libs from LG which was not so easy to obtain.. On a damn nexus device..
Some people mentioned that an Amazon Fire tablet is mostly the same tablet..
The CPU looks the same for the Fire HD 7" (4th gen - 2014) and the GPU is the same from FireHD 8.9" (2.5th Gen) and Fire HD 7 (3rd Gen).
Does CM and/or other Custom ROMs work with Amazon-Fire tablets?
thE_29 said:
I made some ROMs for my Nexus4 and even there, you needed some closed source libs from LG which was not so easy to obtain.. On a damn nexus device..
Some people mentioned that an Amazon Fire tablet is mostly the same tablet..
The CPU looks the same for the Fire HD 7" (4th gen - 2014) and the GPU is the same from FireHD 8.9" (2.5th Gen) and Fire HD 7 (3rd Gen).
Does CM and/or other Custom ROMs work with Amazon-Fire tablets?
Click to expand...
Click to collapse
apparently it does, so there's hope.
I tried building using a mt8127 device tree and vendor from github, with my device tree and his vendor.
I have also made a "noblob" build (before using the hardware/mediatek repo) so that blobs can be pushed.
pix106 said:
apparently it does, so there's hope.
I tried building using a mt8127 device tree and vendor from github, with my device tree and his vendor.
I have also made a "noblob" build (before using the hardware/mediatek repo) so that blobs can be pushed.
Click to expand...
Click to collapse
Can you provide cm12.1 meta inf folder and boot.img?I feel like the one from the amazon fire is superpatched because of fire os crap and cant be ported and Im trying to make a flashable version of your modified stock rom but I dont have meta inf folder(tried one from cm12.0 from one mt6582 device,it did boot but it got stuck at the first boot loading screen).
MaRtYy01 said:
Can you provide cm12.1 meta inf folder and boot.img?I feel like the one from the amazon fire is superpatched because of fire os crap and cant be ported and Im trying to make a flashable version of your modified stock rom but I dont have meta inf folder(tried one from cm12.0 from one mt6582 device,it did boot but it got stuck at the first boot loading screen).
Click to expand...
Click to collapse
I tried too a few months ago, neither did it boot.
The "noblobs" build i did a few days ago : https://mega.nz/#F!i5h23AKY!jnsxiU8Ob0WiDt1YnSabLg
I'm quite sure a few needed init scripts are missing from this build, and from the device tree in general.
Happy testing .
pix106 said:
I tried too a few months ago, neither did it boot.
The "noblobs" build i did a few days ago : https://mega.nz/#F!i5h23AKY!jnsxiU8Ob0WiDt1YnSabLg
I'm quite sure a few needed init scripts are missing from this build, and from the device tree in general.
Happy testing .
Click to expand...
Click to collapse
is this build boots or not . (just asking) by the way :good::good:
[email protected] said:
is this build boots or not . (just asking) by the way :good::good:
Click to expand...
Click to collapse
Its stuck on the bootlogo,since it has no blobs.
BTW the results of my "testing"
-changing the boot.img didnt help,the frecking amazon fire cm12.1 refuses to boot no matter what I do
-the updater script seemed useless,since the system folder in the roms built from source is in just one file
Anyway,got another idea.If I do a backup of system via twrp I probably can use the updater script with it.
[email protected] said:
is this build boots or not . (just asking) by the way :good::good:
Click to expand...
Click to collapse
MaRtYy01 said:
Its stuck on the bootlogo,since it has no blobs.
Click to expand...
Click to collapse
Exactly. It boots, adb and logcat work, but nothing more.
Missing files can be looking for errors in logcat, and be pushed "live" from stock rom dump.
MaRtYy01 said:
BTW the results of my "testing"
-changing the boot.img didnt help,the frecking amazon fire cm12.1 refuses to boot no matter what I do
Click to expand...
Click to collapse
no adb nor logcat ?
MaRtYy01 said:
-the updater script seemed useless,since the system folder in the roms built from source is in just one file
Click to expand...
Click to collapse
is /system mounted ?
MaRtYy01 said:
Anyway,got another idea.If I do a backup of system via twrp I probably can use the updater script with it.
Click to expand...
Click to collapse
i did not understand what you are planning to do... anyway good luck with it
One of my favorite features of the S8 is the Dex feature, that lets me use the phone as a basic computer. I was very disappointed when I saw that the Linux on Dex (LoD) beta is only available for the Note 9 and Tab S4.
This is a stupid software limitation, I don't see any other reason why the S8 - even with Android Pie - wouldn't run LoD. It was even used for the first demos (around one year ago)!
The aim of this thread is to try to remove this limitation and run Linux on Dex on our Galaxy S8.
We already managed to remove the limitation for the need of the Dex dock, hope this will also be a success!
As I'm not an experienced Java developer, I won't be able to solve this thing alone. Hope that other developers will also join this project!
Ok, here are my first steps:
- Downloaded, installed and ran the latest APK (1.0.49): https://forum.xda-developers.com/showpost.php?p=78734115&postcount=226
Error message: Your device is not supported. Please visit www.linuxondex.com for more details.
- Modified the model in build.prop to SM-N960
Error message: Linux on DeX requires your device to have the latest software to support some features.
So there is a change, but not enough.
Now, I decompiled the APK with apktool. The source is in smali bytecode format, but it can be transformed to java.
The device detection code is in the file smali/com/samsung/android/lxd/a/i.smali. It checks the device name for TABS4, CROWN (Note9), STAR2 (S9+*), WINNER (Fold), BEYOND (S10). Can someone add the DREAMLTE/DREAM2LTE and recompile?
* Why only the S9+ (star2) and not the S9 (star)? This is just stupid.
I am using customs rom, with Android PIE
I can load into the apps and while i click the "create" button to build .img file, it just shows me "please wait" and no response.
alan9820 said:
I am using customs rom, with Android PIE
I can load into the apps and while i click the "create" button to build .img file, it just shows me "please wait" and no response.
Click to expand...
Click to collapse
What custom ROM and LoD version are you using?
BTW, you can find prebuilt IMG files in the Note9 LinuxOnDex thread.
kbarni said:
Ok, here are my first steps:
- Downloaded, installed and ran the latest APK (1.0.49): https://forum.xda-developers.com/showpost.php?p=78734115&postcount=226
Error message: Your device is not supported. Please visit www.linuxondex.com for more details.
- Modified the model in build.prop to SM-N960
Error message: Linux on DeX requires your device to have the latest software to support some features.
So there is a change, but not enough.
Now, I decompiled the APK with apktool. The source is in smali bytecode format, but it can be transformed to java.
The device detection code is in the file smali/com/samsung/android/lxd/a/i.smali. It checks the device name for TABS4, CROWN (Note9), STAR2 (S9+*), WINNER (Fold), BEYOND (S10). Can someone add the DREAMLTE/DREAM2LTE and recompile?
* Why only the S9+ (star2) and not the S9 (star)? This is just stupid.
Click to expand...
Click to collapse
I've tried to modify i.smali to return "STAR2" (for any device) but it fails on another check and returns:
Error message: Linux on DeX requires your device to have the latest software to support some features.
3mpty said:
I've tried to modify i.smali to return "STAR2" (for any device) but it fails on another check and returns:
Error message: Linux on DeX requires your device to have the latest software to support some features.
Click to expand...
Click to collapse
Yep...it seems that there are other limitations too. This "latest software" is just stupid; for example the S8 Pie has newer software than the Note9 had when the first LoD beta was released (1.0.38, in last November), still it complains for old software. I wonder if it will work when devs will integrate S10 APKs in S8 rom...
kbarni said:
Yep...it seems that there are other limitations too. This "latest software" is just stupid; for example the S8 Pie has newer software than the Note9 had when the first LoD beta was released (1.0.38, in last November), still it complains for old software. I wonder if it will work when devs will integrate S10 APKs in S8 rom...
Click to expand...
Click to collapse
This 'latest software' may be caused by other issue - SELinux. After running self build & signed version my logcat is full of such entries:
Code:
2019-02-27 13:19:32.590 5156-5156/? E/audit: type=1400 audit(1551269972.589:3628): avc: denied { read } for pid=6318 comm="ung.android.lxd" name="u:object_r:lxd_prop:s0" dev="tmpfs" ino=3505 scontext=u:r:untrusted_app:s0:c168,c258,c512,c768 tcontext=u:object_r:lxd_prop:s0 tclass=file permissive=0 SEPF_SM-G950F_9_0001 audit_filtered
2019-02-27 13:19:32.590 5156-5156/? E/audit: type=1300 audit(1551269972.589:3628): arch=c00000b7 syscall=56 success=no exit=-13 a0=ffffff9c a1=7fe33851f8 a2=88000 a3=0 items=0 ppid=5167 pid=6318 auid=4294967295 uid=10680 gid=10680 euid=10680 suid=10680 fsuid=10680 egid=10680 sgid=10680 fsgid=10680 tty=(none) ses=4294967295 comm="ung.android.lxd" exe="/system/bin/app_process64" subj=u:r:untrusted_app:s0:c168,c258,c512,c768 key=(null)
2019-02-27 13:19:32.590 5156-5156/? E/audit: type=1327 audit(1551269972.589:3628): proctitle="com.samsung.android.lxd"
2019-02-27 13:19:32.591 6318-6318/? E/libc: Access denied finding property "lxd.vmdebugmode"
And because those properties cannot be read it fallbacks to default values.
Unfortunately I'm using official Pie rom for S8 without root etc.
3mpty said:
This 'latest software' may be caused by other issue - SELinux. After running self build & signed version my logcat is full of such entries:
Unfortunately I'm using official Pie rom for S8 without root etc.
Click to expand...
Click to collapse
I'm not sure it's SELinux. It should run on stock rom. In the message you posted, it complains also for untrusted app.
I tried LoD 1.0.38, which also stops with "Update your software", and didn't find anything similar in Logcat.
Can you share your modded LoD APK, so I can test it? I have rooted S8 with Pie and Alexis 7.4 rom.
kbarni said:
I'm not sure it's SELinux. It should run on stock rom. In the message you posted, it complains also for untrusted app.
I tried LoD 1.0.38, which also stops with "Update your software", and didn't find anything similar in Logcat.
Can you share your modded LoD APK, so I can test it? I have rooted S8 with Pie and Alexis 7.4 rom.
Click to expand...
Click to collapse
I'm also not sure if it was SELinux but orginal apk doesn't throw such logs into logcat. Checkout attached apk.
3mpty said:
I'm also not sure if it was SELinux but orginal apk doesn't throw such logs into logcat. Checkout attached apk.
Click to expand...
Click to collapse
Thanks!
I checked it, I don't have the untrusted app message, I have several of these:
Code:
libc [E] Access denied finding property "lxd_vmdebugmode"
However I find this part of the logcat more interesting:
Code:
LxD_o [I] isSupportedBinary: binary version: 1, required version: 4
LxDEntryActivity [E] NonSupportedBinary:
Taking a look at o.smali, the "binary version" is given by the function: com.samsung.android.lxd.processor.utils.Utils.getNstVersion ( );
This points to Utils.smali where it returns android.os.SemSystemProperties .getInt ( "linux_on_dex_version",1); if I understand correctly.
And that leads us to the kernel, probably related to /include/linux/linux_on_dex.h
Can you check this? Do you agree?
I'll investigate the kernel part. I suspect that the kernel has LoD support, but it reports LoD version 1, and the beta won't start unless this number is higher or equal to 4. I don't know if there are other kernel differences, have to dig myself in the Note9 kernel too.
Can you check what happens if you modify the o.smali file, to compare the result of getNstVersion with 1 (set v2 to 0x01 in .line 634)? If you can do this, rebuild the APK, repost it and report back please!
I feel we are getting closer to soething!
I've changed `getNstVersion` default result to 4 instead 1 and it will allow to continue. This method is called later in o.smali:
Code:
/**
* This method checks if device supports LoD, it compares linux_on_dex_version system var with
* 5 (tablet) and 4 (phone). If linux_on_dex_version value is smaller than 5 or 4 this device
* will not support LoD.
*
* @return true if device is supported
*/
public static boolean isSupportedBinary() {
boolean isAlreadyAuthorized = g();
boolean isSupportedBinary = true;
if (isAlreadyAuthorized) {
return true;
} else {
int deviceNstVersion = Utils.getNstVersion();
byte requiredNst;
if (isTablet()) {
requiredNst = 5;
} else {
requiredNst = 4;
}
String var4 = a;
StringBuilder var5 = new StringBuilder();
var5.append("isSupportedBinary: binary version: ");
var5.append(deviceNstVersion);
var5.append(", required version: ");
var5.append(requiredNst);
Log.i(var4, var5.toString());
if (deviceNstVersion < requiredNst) {
isSupportedBinary = false;
}
return isSupportedBinary;
}
}
Unfortunately is not enough. App crashes in few moments when it tries to modify system properties:
Code:
Caused by: java.lang.RuntimeException: failed to set system property
at android.os.SystemProperties.native_set(Native Method)
at android.os.SystemProperties.set(SystemProperties.java:183)
at android.os.SemSystemProperties.set(SemSystemProperties.java:111)
at com.samsung.android.lxd.EntryActivity.R(EntryActivity.java:294)
at com.samsung.android.lxd.EntryActivity.P(EntryActivity.java:183)
at com.samsung.android.lxd.EntryActivity.S(EntryActivity.java:329)
at com.samsung.android.lxd.EntryActivity.onCreate(EntryActivity.java:150)
at android.app.Activity.performCreate(Activity.java:7327)
at android.app.Activity.performCreate(Activity.java:7318)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3088)
Looks like it's the same issue that doesn't allow to read those properties first (at least it's my guess). I've attached apk after 2nd modification.
3mpty said:
Looks like it's the same issue that doesn't allow to read those properties first (at least it's my guess). I've attached apk after 2nd modification.
Click to expand...
Click to collapse
I confirm, I have the same error.
I think it wants to set a system property in file EntryActivity.smali (linux_on_dex.LoD_image and linux_on_dex.LoD_image_P_initial) that's not implemented (maybe in kernel?).
BTW, I'm really curious about reports of LoD working on S8/Note8 etc; @alan9820 and others: what ROM/kernel/LoD version are you using?
Hey guys! I made some interesting progress!
Installing the NX 22.1 kernel allowed me to start the (modified) app! After the welcome page, I could get to the "Create container" page, but when I select the .IMG file, it stays blocked at the "Please wait..." screen. So I guess I'm stuck in the same position as alan9820 (post #3 in the topic).
If I restart the creation of the container, it gives "Unexpected error: Something went wrong. Please close Linux on Dex and try again".
The only LoD related error messages from logcat are:
Code:
LxD_NstControlChannelV1 [E] Failed to connect to server!
LxD_NstControlChannelV1 [E] ControlThread: com.samsung.lxd.processor.LxdEception: Failed to connect to server!, socket status: false
kbarni said:
BTW, I'm really curious about reports of LoD working on S8/Note8 etc; @alan9820 and others: what ROM/kernel/LoD version are you using?
Click to expand...
Click to collapse
I used S8 exynos version G950F
With android customs rom of Hades PIE ROM v3.0
I just google linux on dex apk from apkmirror and download
Repeat that i am able to open the app and choose image
But i am failed to create image just giving me "please wait" msg.
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
kbarni said:
What custom ROM and LoD version are you using?
BTW, you can find prebuilt IMG files in the Note9 LinuxOnDex thread.
Click to expand...
Click to collapse
I alrrady flashed back to Oreo rom, PIE rom is not as smooth as 8.0 currently ... haha
Some more progress: There is a switch in the kernel parameters cooncerning LinuxOnDex: CONFIG_LOD_SEC. I enabled it and recompiled the NX kernel.
Unfortunately it's the same error, the container cannot be built, it gives only an unspecified error. Nothing in Logcat.
I checked the Note9 kernels, but there is no important difference (especially in LoD part).
The unpatched APK files still give the Unsupported software error.
I wonder if the error occurs because of insufficient RAM for building the container??? The main difference between the S9+, Note9, Tab S4 vs. S8 and S9 is that the first group has 6GB of RAM.
[edit] Tried to increase the memory size by 2GB by adding swap, still doesn't work.
kbarni said:
Some more progress: There is a switch in the kernel parameters cooncerning LinuxOnDex: CONFIG_LOD_SEC. I enabled it and recompiled the NX kernel.
Unfortunately it's the same error, the container cannot be built, it gives only an unspecified error. Nothing in Logcat.
I checked the Note9 kernels, but there is no important difference (especially in LoD part).
The unpatched APK files still give the Unsupported software error.
I wonder if the error occurs because of insufficient RAM for building the container??? The main difference between the S9+, Note9, Tab S4 vs. S8 and S9 is that the first group has 6GB of RAM.
[edit] Tried to increase the memory size by 2GB by adding swap, still doesn't work.
Click to expand...
Click to collapse
I have a S8+ Korean version (with 6gb ram) willing to test your modified version to see if it works.
brick5492 said:
I have a S8+ Korean version (with 6gb ram) willing to test your modified version to see if it works.
Click to expand...
Click to collapse
You can install the kernel below (modified NX 22.1) and the apk from 3mpty's post (the modified_v2).
The app should start, the question is if you can create the container or if it gives an unspecified error.
Thanks for testing and please report back your results!
kbarni said:
You can install the kernel below (modified NX 22.1) and the apk from 3mpty's post (the modified_v2).
The app should start, the question is if you can create the container or if it gives an unspecified error.
Thanks for testing and please report back your results!
Click to expand...
Click to collapse
I'm really sorry, but my S8+ is not rooted and on the factory image (still Oreo, didnt recieve Pie yet) and I wish to leave it stock since it's my primary (work) device. I guess I can't install that kernel with the locked bootloader on Oreo right? And I do need the kernel for that modified Dex to work?
I did install the apk and after it granting permissions, it just force closes. I'm on the October security patch.
brick5492 said:
I'm really sorry, but my S8+ is not rooted and on the factory image (still Oreo, didnt recieve Pie yet) and I wish to leave it stock since it's my primary (work) device. I guess I can't install that kernel with the locked bootloader on Oreo right? And I do need the kernel for that modified Dex to work?
I did install the apk and after it granting permissions, it just force closes. I'm on the October security patch.
Click to expand...
Click to collapse
LoD related changes were introduced in Pie kernel, so this won't work on Oreo.