Develop Bugs

Need Help Accessing com_broadcom_bt_service_fm_FmReceiverService

Hi,
I'm tracing through the HTCFMRadio app on my EVO to figure out how it works. I eventually want to create a program that records radio without having to use the mic. From my tracing I can see taht the program continually calls:
com_broadcom_bt_service_fm_FmReceiverService.cpp
Here's logcat:
07-14 10:20:33.769: VERBOSE/FmReceiverEventLoop(94): onRadioRdsUpdateEvent() WOSU 89.7 : station website
07-14 10:20:33.769: VERBOSE/FmReceiverService(94): onRadioRdsUpdateEvent(0,9,42,WOSU 89.7 : station website )
07-14 10:20:33.769: WARN/FmReceiverService(94): Handling OPERATION_RDS_DATA_EVENT_CALLBACK: calls sendRdsDataEventCallback
07-14 10:20:33.769: INFO/BTL_IFC(94): btl_ifc_ctrl_rx: [BTL_IFC CTRL] recv BTLIF_FM_RDS_UPDATE (FM) 79 pbytes (hdl 189)
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): decodePendingEvent: Event ID: 4370
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): decodePendingEvent: RDS UPDATE EVENT
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: event ID: 9, ATTACHING THREAD
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: THREAD ATTACHED OK
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): [JNI] - TRANSMITTING EVENT UP : event = 9
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, 0x 6d4fb8
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, previous_rdsWOSU 89.7 : station website
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, new_rdsWOSU 89.7 : station website
07-14 10:20:33.769: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, memcmp 0x 20
07-14 10:20:33.769: VERBOSE/FmReceiverEventLoop(94): onRadioRdsUpdateEvent() WOSU 89.7 : station website
07-14 10:20:33.769: VERBOSE/FmReceiverService(94): onRadioRdsUpdateEvent(0,9,42,WOSU 89.7 : station website)
07-14 10:20:33.779: WARN/FmReceiverService(94): Handling OPERATION_RDS_DATA_EVENT_CALLBACK: calls sendRdsDataEventCallback
07-14 10:20:33.779: INFO/BTL_IFC(94): btl_ifc_ctrl_rx: [BTL_IFC CTRL] recv BTLIF_FM_RDS_UPDATE (FM) 79 pbytes (hdl 189)
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): decodePendingEvent: Event ID: 4370
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): decodePendingEvent: RDS UPDATE EVENT
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: event ID: 9, ATTACHING THREAD
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: THREAD ATTACHED OK
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): [JNI] - TRANSMITTING EVENT UP : event = 9
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, 0x 6d4fb8
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, previous_rdsWOSU 89.7 : station website
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, new_rdsWOSU 89.7 : station webstie
07-14 10:20:33.779: INFO/com_broadcom_bt_service_fm_FmReceiverService.cpp(94): enqueuePendingEvent: BTA_FM_RDS_UPD_EVT, memcmp 0x 0
07-14 10:20:34.316: INFO//system/bin/btld(10221): ##### USerial_Ioctl: BT_Sleep, 0x8004 ####
07-14 10:20:35.020: INFO//system/bin/btld(10221): ##### USerial_Ioctl: BT_Wake, 0x8003 ####
07-14 10:20:35.049: INFO/BTAPP_FM(10222): BTAPP_FM: btui_fm_cback: 10
07-14 10:20:35.049: INFO/BTAPP_FM(10222): BTAPP_FM: BTA_FM_AUD_DATA_EVT
07-14 10:20:35.049: INFO/BTL-IFS(10222): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_FM_GET_AUDIO_QUALITY (FM) 12 pbytes (hdl 15)
Can someone explain to me how I can access the music stream created by this file? or at least give me direction in how to figure this out? Thanks!
Respectfully,
Jerry Balderas

solved
file in question is called by com.broadcom.bt.service.fm.FmReceiverService which can be extracted from framework.odex
copy framework.odex to same directory as HtcFMRadio.odex then:
baksmali -d <framework directory> -x framework.odex

[Req/Help]Need someone that can help me debug smali

Hey,
Trying to mod the Sense Camera.apk. As you know, when you click on the thumbnails in the camera app it always launches the stock HTC gallery app (HTCAlbum.apk).
I actually succeeded 50% in that task, and since I'm still rather new to smali editing I could use some help from someone that might know how to fix it.
My change was actually pretty simple:
There was 1 method that calls the HTC gallery app, I simply changed it to call the general view image intent.
Now it seems to work, when I click the thumbnail I get the picker to choose what app to open the image with, but once I pick one it doesn't work.
The odd thing is, once I took a single picture with the camera app, it works as intended, app picker comes up and it opens the last image I took.
It then even works when I delete a few recently taken pics (to verify that it doesn't just work with new pictures).
However when I force stop the camera and launch it again it bugs again until I take a single picture.
The smali change I did:
Code:
HTCCamera.smali line 24165
.line 5638
.end local v0 #action:Ljava/lang/String;
:cond_1
const-string v0, "com.htc.album.action.VIEW_PHOTO_FROM_CAMERA"
changed to
.line 5638
.end local v0 #action:Ljava/lang/String;
:cond_1
const-string v0, "android.intent.action.VIEW"
Doing a logcat didn't give me any useful information :/
Way too much text for such a small problem
Thanks in advance for anyone that can help.

I still don't understand this :/
Log of Gallery crashing:
Code:
E/AndroidRuntime(26385): FATAL EXCEPTION: main
E/AndroidRuntime(26385): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.gallery3d/com.android.gallery3d.app.Gallery}: java.lang.RuntimeException: cannot find data for: /local/image/item/13958
E/AndroidRuntime(26385): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2202)
E/AndroidRuntime(26385): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2237)
E/AndroidRuntime(26385): at android.app.ActivityThread.access$600(ActivityThread.java:139)
E/AndroidRuntime(26385): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1262)
E/AndroidRuntime(26385): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(26385): at android.os.Looper.loop(Looper.java:154)
E/AndroidRuntime(26385): at android.app.ActivityThread.main(ActivityThread.java:4974)
E/AndroidRuntime(26385): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(26385): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(26385): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
E/AndroidRuntime(26385): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
E/AndroidRuntime(26385): at dalvik.system.NativeStart.main(Native Method)

[PORT][TEST][4.1+] FM Radio Beta - Testers needed

Hello XDA!
I am trying to port the FM radio for CM10/AOKP. (From the latest Jelly Bean leak: XXLSJ)
Because I'm running an XXLSJ based rom, I can't really try if the port is successful or not.
I'm trying to run it on an emulator.
Status:
Fixed a lot of UI related issues, missing resources, hardcoded resource ids.
The app loads the needed lib on start:
12-01 07:58:45.104: I/FmRadioController(840): Calling JNI_OnLoad
12-01 07:58:45.104: I/FmRadioController(840): Calling register_FMPlayer
12-01 07:58:45.136: I/System.out(840): FMRadio lib loaded
12-01 07:58:45.294: I/System.out(840): mAirPlaneEnabled flag :false
12-01 07:58:45.364: I/FMRadioService(840): platform :
12-01 07:58:45.364: I/FMPlayer(840): Player created :[email protected]
Managed to add FMRadioService to the application (as non-system service). Now it starts as a new instance.
Managed to copy lot of missing classes to the apk from framework2.jar, twframework.jar and sechardware.jar.
Missing layout elements are copied to the apk.
Apk compiles and installs without error.
Known issues
Force close upon exiting: Unable to start receiver com.gyebro.android.app.fm.widget.FMRadioProvider: android.content.ReceiverCallNotAllowedException: IntentReceiver components are not allowed to register to receive intents
Since the app instantiates a new FMRadioService, and abandons it upon exiting, it is possible, that it causes some memory leak.
Samsung's AudioManager has a separate audio stream for the fm radio. Now I'm using the Music stream (STREAM_MUSIC), so it is possible, that the app can conflict with music players in the background. (So shut down all the music players before trying this)
Again Samsung's AudioManager has a function for checking whether the radio stream is playing via the speakers (or via headset), this function (isRadioSpeakerOn) is replaced by the standard isSpeakerphoneOn. So it is possible, that the listening via speaker/headset option will misbehave.
Some screenshots from the emulator
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the current version:
signed_FmRadio_XXLSJ.apk
libfmradio_jni.so
libsecmediarecorder_jni.so
Installation:
Copy the apk to system/app
Copy the two so files to system/lib
What I'm asking:
Again I'm asking you to provide LogCat logs, when connecting the headset and pressing the ON button.
Important notice
However I'm pretty sure, that this app could not damage your phone, I'm not responsible for any temporary or permanent hardware related damage happening with your device thanks to this application. So, please keep in mind, that you are trying this at your own risk.

D/widget ( 5921): [MSC_HERO_Accu]>>> WC:866 [0:0] onResume :: fU = true cEUi
= true
D/widget ( 5921): [MSC_HERO_Accu]>>> WC:1916 [0:0] AR_S_T : 0
D/widget ( 5921): [MSC_HERO_Accu]>>> WC:903 [0:0] onResume :: mFAR = false, cC
= false, cEUI = true
D/widget ( 5921): [MSC_HERO_Accu]>>> WC:1135 [0:0] cUI : cnt = 1, mRC = true
E/Launcher( 5921): Error finding setting, default accessibility to not found: ac
cessibility_enabled
D/Launcher.HomeFragment( 5921): onResume
D/widget ( 5921): [MSC_HERO_Accu]>>> WC:1104 [0:0] fireOR
E/widget ( 5921): [MSC_HERO_Accu]>>> SM:281 [0:0] IR : false, IPR : false
D/MenuAppsGridFragment( 5921): onResume
E/ActivityThread( 5921): Failed to find provider info for com.samsung.helphub.pr
ovider
D/widget ( 5921): [MSC_HERO_Accu]>>> WC:601 [0:0] ===== mSetUIDataHandler(): da
y = 7:29 AM, night=4:24 PM
E/widget ( 5921): [MSC_HERO_Accu]>>> SM:281 [0:0] IR : false, IPR : false
D/FMApp (11428): onDestroy -----------
W/System.err(11428): java.lang.NullPointerException
W/System.err(11428): at com.gyebro.android.app.fm.MainActivity.onDestroy(Main
Activity.java:4477)
W/System.err(11428): at android.app.Activity.performDestroy(Activity.java:517
2)
W/System.err(11428): at android.app.Instrumentation.callActivityOnDestroy(Ins
trumentation.java:1109)
W/System.err(11428): at android.app.ActivityThread.performDestroyActivity(Act
ivityThread.java:3429)
W/System.err(11428): at android.app.ActivityThread.handleDestroyActivity(Acti
vityThread.java:3460)
W/System.err(11428): at android.app.ActivityThread.access$1200(ActivityThread
.java:145)
W/System.err(11428): at android.app.ActivityThread$H.handleMessage(ActivityTh
read.java:1264)
W/System.err(11428): at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err(11428): at android.os.Looper.loop(Looper.java:137)
W/System.err(11428): at android.app.ActivityThread.main(ActivityThread.java:4
978)
W/System.err(11428): at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err(11428): at java.lang.reflect.Method.invoke(Method.java:511)
W/System.err(11428): at com.android.internal.os.ZygoteInit$MethodAndArgsCalle
r.run(ZygoteInit.java:791)
W/System.err(11428): at com.android.internal.os.ZygoteInit.main(ZygoteInit.ja
va:558)
W/System.err(11428): at dalvik.system.NativeStart.main(Native Method)
this is what happens

Hey really very nice work! It seems it cannot find "FMRadio Service". Here is my logcat I hope it helps
Code:
D/FMApp (11531): oncreate -------------------
D/FMApp (11531): FMRadio Service Is NULL. Exit FMRadio
D/FMApp (11531): onDestroy -----------
W/System.err(11531): java.lang.NullPointerException
W/System.err(11531): at com.gyebro.android.app.fm.MainActivity.onDestroy(MainActivity.java:4477)
W/System.err(11531): at android.app.Activity.performDestroy(Activity.java:5172)
W/System.err(11531): at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1109)
W/System.err(11531): at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3429)
W/System.err(11531): at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3460)
W/System.err(11531): at android.app.ActivityThread.access$1200(ActivityThread.java:145)
W/System.err(11531): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1264)
W/System.err(11531): at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err(11531): at android.os.Looper.loop(Looper.java:137)
W/System.err(11531): at android.app.ActivityThread.main(ActivityThread.java:4978)
W/System.err(11531): at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err(11531): at java.lang.reflect.Method.invoke(Method.java:511)
W/System.err(11531): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
W/System.err(11531): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
W/System.err(11531): at dalvik.system.NativeStart.main(Native Method)
D/dalvikvm(11531): GC_EXPLICIT freed 18K, 90% free 2594K/24576K, paused 2ms?, total 20ms
ROM: ParanoidAndroid 2.54
Kernel: Dorimanx 7.23
Sent from my GT-I9100 using xda app-developers app

needme said:
Hey really very nice work! It seems it cannot find "FMRadio Service". Here is my logcat I hope it helps
ROM: ParanoidAndroid 2.54
Kernel: Dorimanx 7.23
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I've tried to add the FMRadio system service, but it can't be done on the emulator (I should patch the services.jar and framework.jar to make the ServiceManager add the FMRadio service to the system)
However it seems, that CyanogenMod offers a comfortable way to add system services:
Allow loading of vendor specific services from compiled jar files.
So I will try to load the FMRadioService this way...
(Fortunately all the code of the service is present in a nice separated way, so it won't be hard to make a jar containing it)

Now I need testers again!
I need some testers again! What I'm curious about is, that can you turn the radio on, with earphones connected? Then what are you hearing? (Please create a log while doing this).
Thanks!
See the first post for a lot of new info and download links.

Gyebro said:
I need some testers again! What I'm curious about is, that can you turn the radio on, with earphones connected? Then what are you hearing? (Please create a log while doing this).
Thanks!
See the first post for a lot of new info and download links.
Click to expand...
Click to collapse
Hey
Nice to see progress!You are doing a great job!
The app starts, but when I push the button to turn FM radio on, nothing happens except in the Title shortly stands "Turning on".
Logcat line 175:
Code:
D/FMApp (15454): com.samsung.media.fmradio.FMPlayerException: Unable to turn on FM Radio
D/FMApp (15454): exception occurred during turning on
W/System.err(15454): com.samsung.media.fmradio.FMPlayerException: Unable to turn on FM Radio
W/System.err(15454): at com.gyebro.android.app.fm.MainActivity.on(MainActivity.java:3259)
W/System.err(15454): at com.gyebro.android.app.fm.MainActivity$MyHandler.handleMessage(MainActivity.java:293)
W/System.err(15454): at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err(15454): at android.os.Looper.loop(Looper.java:137)
W/System.err(15454): at android.app.ActivityThread.main(ActivityThread.java:4978)
W/System.err(15454): at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err(15454): at java.lang.reflect.Method.invoke(Method.java:511)
W/System.err(15454): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
W/System.err(15454): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
W/System.err(15454): at dalvik.system.NativeStart.main(Native Method)
It had some force closes when leaving main activity and change volume within the app (right upper button).Whole Logcat is attached.
Thank you for your work

needme said:
Hey
Nice to see progress!You are doing a great job!
The app starts, but when I push the button to turn FM radio on, nothing happens except in the Title shortly stands "Turning on".
Logcat line 175:
Code:
D/FMApp (15454): com.samsung.media.fmradio.FMPlayerException: Unable to turn on FM Radio
D/FMApp (15454): exception occurred during turning on
It had some force closes when leaving main activity and change volume within the app (right upper button).Whole Logcat is attached.
Thank you for your work
Click to expand...
Click to collapse
I've decompiled the libfmradio_jni.so, and it seems it is using a file called fmradio (without extension) in the dev folder. Do you have this file? (dev/fmradio)
If yes, could you please send it to me?
If no, please create an empty file called fmradio, and copy it to /dev

Gyebro said:
I've decompiled the libfmradio_jni.so, and it seems it is using a file called fmradio (without extension) in the dev folder. Do you have this file? (dev/fmradio)
If yes, could you please send it to me?
If no, please create an empty file called fmradio, and copy it to /dev
Click to expand...
Click to collapse
This file exists but it is completely empty Permissions are 660. Do you need any further information?
Sent from my GT-I9100 using xda premium

needme said:
This file exists but it is completely empty Permissions are 660. Do you need any further information?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
That's enough for now... I think the problem is kernel related -> the kernel must support the use of fm radio hardware.

Gyebro said:
That's enough for now... I think the problem is kernel related -> the kernel must support the use of fm radio hardware.
Click to expand...
Click to collapse
I am now running Siyah 5.0.1 and if it had no FM support then FM should not run even on stock ROM with custom kernel but it does. So I think it is ROM related. There may be dependencies which are just damn hard to find because Samsung has integrated FM too deep in system and log doesn't show what is needed. Damn if Samsung would be open source my phone would be so much better As I see you can't do anything now or? Thank you very much, although it's still not working
If we never try we will never see Keep up your great work!
Sent from my GT-I9100 using xda premium

needme said:
I am now running Siyah 5.0.1 and if it had no FM support then FM should not run even on stock ROM with custom kernel but it does. So I think it is ROM related. There may be dependencies which are just damn hard to find because Samsung has integrated FM too deep in system and log doesn't show what is needed. Damn if Samsung would be open source my phone would be so much better As I see you can't do anything now or? Thank you very much, although it's still not working
If we never try we will never see Keep up your great work!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yesterday I've found a thread (this one) which reports something about "loading kernel modules". But I did not have much time to go after that... I thought that on stock ROM, the kernel loads additional modules (.ko files, defined in init.rc) upon boot, while on non-stock roms, there is nothing to load...
Today I've installed the ported FMradio on my stock samsung rom, because I wanted to know, how it looks in logcat, if the FMRadioController can initialize itself. The logcat shown, that there are some other classes, which are related to the FMradio hardware, and some of these are packed in .so libs. (For example AudioPolicyManagerBase seems to have been modified by Samsung, and there are some native code, for example AudioHardwareYamaha -> AudioHardware, which is also different in Samsung ROMs, than in AOSP/CM10/AOKP...)
So the next task is to decompile all the .so libs (from CM10 and XXLSJ), and find out which of them are different... (libmediayamaha_jni.so?),
find out which of the libs are needed (for example there is a libaudiopolicy_sec.so in Samsung roms) and find out which of the classes in framework are missing (for example framework/com.yamaha.android.media.jar is not present in CM10)
EDIT: I've found the line in init.rc which loads the driver for the fmradio.
Code:
# ko files for FM Radio
insmod /lib/modules/Si4709_driver.ko

So finally my questions:
Do you have the Si4709_driver.ko in lib/modules OR in system/lib/modules?
Do you have the command in your init.rc to load this module?

Gyebro said:
So finally my questions:
Do you have the Si4709_driver.ko in lib/modules OR in system/lib/modules?
Do you have the command in your init.rc to load this module?
Click to expand...
Click to collapse
Hey There is the problem.
Module is there, but it's not loaded in init.rc . tried to add the command but it got reset on reboot. Any suggestions? Thank you again
Sent from my GT-I9100 using xda premium

needme said:
Hey There is the problem.
Module is there, but it's not loaded in init.rc . tried to add the command but it got reset on reboot. Any suggestions? Thank you again
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Can you send me your init.rc, and those files which are imported in the beginning of your init.rc
In stock init.rc, there are 3 imports:
Code:
import /init.${ro.hardware}.rc
import /init.usb.rc
import /init.trace.rc
And the fm module is loaded in init.smdk4210.rc (guess its init.${ro.hardware}.rc)
Code:
on init
# ko files for FM Radio
insmod /lib/modules/Si4709_driver.ko

needme said:
Hey There is the problem.
Module is there, but it's not loaded in init.rc . tried to add the command but it got reset on reboot. Any suggestions? Thank you again
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
You can try to load it with ADB: (Assuming that your driver is at system/lib/modules)
Code:
adb root
adb remount
adb insmod /system/lib/modules/Si4709_driver.ko

Gyebro said:
Can you send me your init.rc, and those files which are imported in the beginning of your init.rc
In stock init.rc, there are 3 imports:
Code:
import /init.${ro.hardware}.rc
import /init.usb.rc
import /init.trace.rc
And the fm module is loaded in init.smdk4210.rc (guess its init.${ro.hardware}.rc)
Code:
on init
# ko files for FM Radio
insmod /lib/modules/Si4709_driver.ko
Click to expand...
Click to collapse
OK i did not looked in init,smdk4210,rc. The command is written there and trying to add with adb gives "can't insert Si4709_driver.ko: File exists". So i guess it is loaded. Damn -.- this is not the problem either. Do you still need the files?

needme said:
OK i did not looked in init,smdk4210,rc. The command is written there and trying to add with adb gives "can't insert Si4709_driver.ko: File exists". So i guess it is loaded. Damn -.- this is not the problem either. Do you still need the files?
Click to expand...
Click to collapse
Can you run the following command to make sure, that the module is active?
Code:
adb shell lsmod
No I don't need the .rc files.

Gyebro said:
Can you run the following command to make sure, that the module is active?
Code:
adb shell lsmod
No I don't need the .rc files.
Click to expand...
Click to collapse
Outpout: Si4709_driver 24484 0 - Live 0xbf015000. I guess it is active.

needme said:
Outpout: Si4709_driver 24484 0 - Live 0xbf015000. I guess it is active.
Click to expand...
Click to collapse
Yes, it is active, so the solution is not *that* easy...
Another question: Do you have the file wakeup_keys at /sys/class/sec/sec_key/?
The file is probably there, but in your init.rc (or init.smdk4210.rc) only the following values are written into it:
Code:
# Permissions for gpio_keys.
chown system radio /sys/class/sec/sec_key/wakeup_keys
write /sys/class/sec/sec_key/wakeup_keys 102,116
While in the stock samsung init.rc
Code:
# Permissions for gpio_keys
chown radio system /sys/class/sec/sec_key/wakeup_keys
write /sys/class/sec/sec_key/wakeup_keys 102,116,172
And see what happens in the FMRadioService.smali when the FMRadioService is initializing itself:
Code:
.line 191
const-string v2, "/sys/class/sec/sec_key/"
iput-object v2, p0, Lcom/android/server/FMRadioService;->mWakeUpKeyFilePath:Ljava/lang/String;
.line 192
const-string v2, "wakeup_keys"
iput-object v2, p0, Lcom/android/server/FMRadioService;->mWakeUpKeyFileName:Ljava/lang/String;
.line 193
const-string v2, "102,114,115,116,172"
iput-object v2, p0, Lcom/android/server/FMRadioService;->mFmOn:Ljava/lang/String;
.line 194
const-string v2, "102,116,172"
iput-object v2, p0, Lcom/android/server/FMRadioService;->mFmOff:Ljava/lang/String;
Those nasty "172" key is used (along with 114 and 115 which have no sign in both rc files)!
EDIT: It seems these code part only sets the keys which are waking up the service and the 172 is the HOME key. So this is not essential...

what happened to this application??

[BUILDING][OMNI9]Help building omni 9 for daisy

I need help Building omnirom9.0 for daisy, got it to compile and boot (bootlooping bootanimation, logs can be found below) but need help in interpreting the logs.
Sources:
Kernel mi kernel with disabled verity and FEC
Devie combined msm8953-common and daisy (branch los15) from lineage build and adjusted to omni
Vendor took vendor from v10.0.1.0.PDLMIFJ, added everything to copy files, adjusted with apps and missing files from system and deleted the obsolete
OMNIROM
Logcat
Saw that some libraries are missing, will search them in vendor/system from stock and add them when i have time. If someone finds a solution for an error please copy&paste the line(s) in logcat leading to the solution, so me (and probably others) can learn from it and be of more use next time.
@ada12
@reujea0
@Hakkinan
ada12 and me made a Telegram group for mi a2 lite developing, who wants to join can pm me or ada12.

I've never compiled for a treble device but as i know vendor tree is useless because all needed blobs are in vendor partition, you shouldn't take things from stock system.
In fact GSI works at 100% with only vendor libraries (ok, code is patched but that's not the point).
I think we should target GSI instead, researching and giving fixes for roms that have litte issues and compiling new ones (also for the joy of others device's owners).
If you don't think so please explain why, i'm open to dialog

It is clear from the log that there is an issue with gnss(Global Navigation Satellite System). SO location won't most likely work, for the time being try to disable/remove everything related to gnss, this should let you at least boot or go further in the boot process. I will investigate further.
---------- Post added at 05:35 PM ---------- Previous post was at 05:18 PM ----------
I think we might have to patchelf https://github.com/NixOS/patchelf to replace the dependencieng, like this https://github.com/LineageOS/androi...mmit/369faf695b355d1d341a09082272ef25d3ad3e7a . I don't really have the time, but try to patchelf this with some of the values in the logcat.

reujea0 said:
It is clear from the log that there is an issue with gnss(Global Navigation Satellite System). SO location won't most likely work, for the time being try to disable/remove everything related to gnss, this should let you at least boot or go further in the boot process. I will investigate further.
---------- Post added at 05:35 PM ---------- Previous post was at 05:18 PM ----------
I think we might have to patchelf https://github.com/NixOS/patchelf to replace the dependencieng, like this https://github.com/LineageOS/androi...mmit/369faf695b355d1d341a09082272ef25d3ad3e7a . I don't really have the time, but try to patchelf this with some of the values in the logcat.
Click to expand...
Click to collapse
Whoa, thanks a lot i already have an idea on how to fix gnss and i will try to patch elf when i have time (tomorrow or so)

mac12m99 said:
I've never compiled for a treble device but as i know vendor tree is useless because all needed blobs are in vendor partition, you shouldn't take things from stock system.
In fact GSI works at 100% with only vendor libraries (ok, code is patched but that's not the point).
I think we should target GSI instead, researching and giving fixes for roms that have litte issues and compiling new ones (also for the joy of others device's owners).
If you don't think so please explain why, i'm open to dialog
Click to expand...
Click to collapse
Yes, you are right, all blobs needed for a gsi are in vendor partition. Many of those blobs are however, not needed or can be compiled open source with customisations like improved battery life/performance and an open source code.
Also, to add new features which our hardware supports but xiaomi did not build into they'r software for license or other reasons, we need a completely source built kernel and an adapted rom. Additionally, a properly built and optimized rom with as much open source code as possible and improved from a ****load of developers around the world will always perform better than an overlay rom depending on features built from oem and therefore optimized for theyr stock rom.
Also, you need files from system for a proper full vendor because you need some configuration files for the rom itself to adapt to the vendor blobs. Sometimes you can also fix a gsi by copying the right file (look logcat) from stock system to the gsi system partition .

wertus33333 said:
Yes, you are right, all blobs needed for a gsi are in vendor partition. Many of those blobs are however, not needed or can be compiled open source with customisations like improved battery life/performance and an open source code.
Click to expand...
Click to collapse
Ok, i got it,
so you are trying to create a ROM that don't use vendor partition and have all needed blobs into /system?
wertus33333 said:
Also, to add new features which our hardware supports but xiaomi did not build into they'r software for license or other reasons, we need a completely source built kernel and an adapted rom. Additionally, a properly built and optimized rom with as much open source code as possible and improved from a ****load of developers around the world will always perform better than an overlay rom depending on features built from oem and therefore optimized for theyr stock rom.
Click to expand...
Click to collapse
Which features do you mean?
As i know all hardware features have to be implemented in kernel (like dt2w and fingerprint gestures) and all software features have to be implemented in ROM (like long press for flashlight, dt2s in statustbar ecc..).
Am i wrong?
wertus33333 said:
Also, you need files from system for a proper full vendor because you need some configuration files for the rom itself to adapt to the vendor blobs. Sometimes you can also fix a gsi by copying the right file (look logcat) from stock system to the gsi system partition .
Click to expand...
Click to collapse
This happens when OEM forgot to move something vendor, as i know .
EDIT: looking at your logcat i found this:
Code:
F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
This is a fatal issue and probably the cause of bootloop, copying libaudiopolicymanagerdefault.so from stock may help but i think it could be built.

mac12m99 said:
EDIT: looking at your logcat i found this:
Code:
F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
This is a fatal issue and probably the cause of bootloop, copying libaudiopolicymanagerdefault.so from stock may help but I think it could be built.
Click to expand...
Click to collapse
I saw this one as well in the logcat, I do agree that it seems like it can't find the audioserver file, which would probably cause no audio. But I do not think that it causes the bootloop, not only can most roms cope with not finding some executables, but also it is not the one coming up forever towards the end of the logcat. This is an error it does not try to fix, in the logcat, the rom is trying to start the GPS over and over, which makes it bootloop, stuck at the omni logo. We either have to kill it in the boot.rc files temporarily to boot or to find a way to fix it.

reujea0 said:
I saw this one as well in the logcat, I do agree that it seems like it can't find the audioserver file, which would probably cause no audio. But I do not think that it causes the bootloop, not only can most roms cope with not finding some executables, but also it is not the one coming up forever towards the end of the logcat. This is an error it does not try to fix, in the logcat, the rom is trying to start the GPS over and over, which makes it bootloop, stuck at the omni logo. We either have to kill it in the boot.rc files temporarily to boot or to find a way to fix it.
Click to expand...
Click to collapse
Ok i got it, i hope you succeed

log interpretation
the interpretation is need globally to fix vendor error and issue with gnss(Global Navigation Satellite System). the source is no good .
I think the solution to speak regularry in work omni rom daisy , is create group Mi a2 lite dev in Telegram app . For exemple group telegram for Redmi note 5a( my secondary device ), have many help dev and good community .
you can see error here for your logcat :
1-08 15:44:04.528 463 463 E DrmLibFs: Error: Invalid config file
01-08 15:44:04.528 463 463 E DrmLibFs: Data path not parsed: Using default data path: /data/vendor/tzstorage/
01-08 15:44:04.528 463 463 E DrmLibFs: Persist path not parsed: Using default persist path: /mnt/vendor/persist/data/
01-08 15:44:04.740 479 479 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
01-08 15:44:04.750 479 483 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare /data/system/users/0: No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare user 0 storage
01-08 15:44:05.583 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IHealth/default in either framework or device manifest.
1-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter64.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
01-08 15:44:05.703 570 570 D QSEECOMAPI: App is not loaded in QSEE
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 E SoterUtils: QSEECom_start_app failed
01-08 15:44:05.704 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IGnss/default in either framework or device manifest.
01-08 15:44:45.509 708 708 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:44:50.519 718 718 W [email protected]: Failed to register IGnss 1.1 service: 1, try IGnss 1.0
01-08 15:45:05.518 729 729 E [email protected]: Could not get passthrough implementation for [email protected]::IVr/default.
01-08 15:45:15.550 751 751 E [email protected]: Error while registering gnss vendor hal service: 1
01-08 15:45:30.536 769 769 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:45:30.542 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IVr/default in either framework or device manifest.
01-08 15:45:30.543 771 771 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-08 15:45:30.544 771 771 E VrService: hw_get_module vr failed: -2
01-08 15:47:30.685 906 906 E [email protected]: Could not get passthrough implementation for [email protected]::ILocHidlGnss/gnss_vendor.
01-08 15:47:30.685 906 906 E [email protected]: Error while registering gnss vendor hal service: 1
wertus33333 said:
I need help Building omnirom9.0 for daisy, got it to compile and boot (bootlooping bootanimation, logs can be found below) but need help in interpreting the logs.
Sources:
Kernel mi kernel with disabled verity and FEC
Devie combined msm8953-common and daisy (branch los15) from lineage build and adjusted to omni
Vendor took vendor from v10.0.1.0.PDLMIFJ, added everything to copy files, adjusted with apps and missing files from system and deleted the obsolete
OMNIROM
Logcat
Saw that some libraries are missing, will search them in vendor/system from stock and add them when i have time. If someone finds a solution for an error please copy&paste the line(s) in logcat leading to the solution, so me (and probably others) can learn from it and be of more use next time.
@ada12
@reujea0
@Hakkinan
Click to expand...
Click to collapse
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
+ I see Vendor took vendor from v10.0.1.0.PDLMIFJ , is a beta rom pie for Daisy . I recommand change to vendor from v10.0.2.0 + fix after in source the other bug

Thanks for the answer, last time i could not find the v10.0.2.0 vendor anywhere but if it is officially avaiable now i'll defenitely switch.
A telegram group would defenitely be of help and easier to communicate than here. More people reviewing/contributing to the code on github (i don't always really know what i am doing ) would also be useful (i'd be happy to add more people, just pm me if u want to).
I dont have that much time for continuing with the rom in the next 1-2 weeks but i'll defenitely continue as soon as possible.
ada12 said:
the interpretation is need globally to fix vendor error and issue with gnss(Global Navigation Satellite System). the source is no good .
I think the solution to speak regularry in work omni rom daisy , is create group Mi a2 lite dev in Telegram app . For exemple group telegram for Redmi note 5a( my secondary device ), have many help dev and good community .
you can see error here for your logcat :
1-08 15:44:04.528 463 463 E DrmLibFs: Error: Invalid config file
01-08 15:44:04.528 463 463 E DrmLibFs: Data path not parsed: Using default data path: /data/vendor/tzstorage/
01-08 15:44:04.528 463 463 E DrmLibFs: Persist path not parsed: Using default persist path: /mnt/vendor/persist/data/
01-08 15:44:04.740 479 479 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
01-08 15:44:04.750 479 483 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare /data/system/users/0: No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare user 0 storage
01-08 15:44:05.583 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IHealth/default in either framework or device manifest.
1-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter64.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
01-08 15:44:05.703 570 570 D QSEECOMAPI: App is not loaded in QSEE
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 E SoterUtils: QSEECom_start_app failed
01-08 15:44:05.704 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IGnss/default in either framework or device manifest.
01-08 15:44:45.509 708 708 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:44:50.519 718 718 W [email protected]: Failed to register IGnss 1.1 service: 1, try IGnss 1.0
01-08 15:45:05.518 729 729 E [email protected]: Could not get passthrough implementation for [email protected]::IVr/default.
01-08 15:45:15.550 751 751 E [email protected]: Error while registering gnss vendor hal service: 1
01-08 15:45:30.536 769 769 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:45:30.542 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IVr/default in either framework or device manifest.
01-08 15:45:30.543 771 771 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-08 15:45:30.544 771 771 E VrService: hw_get_module vr failed: -2
01-08 15:47:30.685 906 906 E [email protected]: Could not get passthrough implementation for [email protected]::ILocHidlGnss/gnss_vendor.
01-08 15:47:30.685 906 906 E [email protected]: Error while registering gnss vendor hal service: 1
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
+ I see Vendor took vendor from v10.0.1.0.PDLMIFJ , is a beta rom pie for Daisy . I recommand change to vendor from v10.0.2.0 + fix after in source the other bug
Click to expand...
Click to collapse

[ROM][UNOFFICIAL] LineageOS 14.1 for SM-T113NU

This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Offline charging
Prerequisites:
TWRP version 3.0.2 (https://drive.google.com/file/d/1Hcc1T1-iUEo1ATpPf_Kcu3vXqGR3Boq_/view)
Galaxy Tab E SM-T113NU (reported by some users that works on T116 models, but this is not guaranteed)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Latest Image build:
https://drive.google.com/file/d/1xEq9lttRw752KqIwXnk5ccUFmLJe4BSJ/view
Source links:
# Local manifest
https://github.com/pstglia/local_manifests/tree/T113NU_COM_A_MAO_NO_BOLSO
# Framework-native
https://github.com/pstglia/frameworks-native/tree/T113NU_COM_A_MAO_NO_BOLSO
# Kernel
https://github.com/pstglia/linux/tree/T113NU_COM_A_MAO_NO_BOLSO
# device/vendor
https://github.com/pstglia/android_device_samsung_scx35-common/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_vendor_samsung_scx30g-common/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_device_samsung_scx30g-common/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_vendor_samsung_core33g/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_device_samsung_core33g/tree/T113NU_COM_A_MAO_NO_BOLSO
# frameworks/base (the commit that hacks camera count return to 0 is here)
https://github.com/pstglia/platform_frameworks_base/tree/T113NU_COM_A_MAO_NO_BOLSO
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
(My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note 1:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Note 2:
If you face a bootloop, you can try formatting your efs partition as described bellow (AT YOUR OWN RISK!)
https://forum.xda-developers.com/showpost.php?p=79995765&postcount=42
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17

What do you need to get a working camera? I have an actual Samsung SM-T113NU
pstglia said:
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Prerequisites:
TWRP version 3.0.2
Galaxy Tab E SM-T113NU (similar models were not tested)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Will update this thread with links when my user reaches the required points (new on xda)
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
stephenpump (My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
Click to expand...
Click to collapse

MrLinDowsMac said:
What do you need to get a working camera? I have an actual Samsung SM-T113NU
Click to expand...
Click to collapse
Hi,
1) I'd need spare time to find a way to make it work.
2) more knowledge would be needed. To build this image, I had basically to adapt Samsung kernel to met 7.1 requirements (I basically cherry-picked commits from remilia15 - SM-G360H) and some other minor changes.
Camera probably requires advanced coding, which is a bit far from my current skills. Enabling it causes crashes during components startup (see bellow):
Code:
04-19 22:37:01.036 227 769 I SprdCameraHardware: getPropertyAtv:0
04-19 22:37:01.036 227 769 I SprdCameraHardware: getNumberOfCameras:2
04-19 22:37:01.036 227 769 I CameraService: disconnect: Disconnected client for camera 0 for PID 227
04-19 22:37:01.036 227 769 E CameraService: initializeShimMetadata: Error initializing shim metadata: Status(-8): '3: connectHelper:928: Illegal argument to HAL module for camera "0"'
04-19 22:37:01.038 585 585 E System : ******************************************
04-19 22:37:01.038 227 909 E isp-video: ISP_RAW: id:0x00, 00927 line, ispserver_thread : ISP_TOOL:isp-video server version 1.0
04-19 22:37:01.039 227 909 E isp-video: ISP_RAW: id:0x00, 00965 line, ispserver_thread : ISP_TOOL:log server waiting client dail in...
04-19 22:37:01.040 585 585 E System : ************ Failure starting system services
04-19 22:37:01.040 585 585 E System : java.lang.RuntimeException: Failed to boot service com.android.server.retaildemo.RetailDemoModeService: onBootPhase threw an exception during phase 600
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServiceManager.startBootPhase(SystemServiceManager.java:145)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer$2.run(SystemServer.java:1538)
04-19 22:37:01.040 585 585 E System : at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:13591)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer.startOtherServices(SystemServer.java:1466)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer.run(SystemServer.java:368)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer.main(SystemServer.java:237)
04-19 22:37:01.040 585 585 E System : at java.lang.reflect.Method.invoke(Native Method)
04-19 22:37:01.040 585 585 E System : at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
04-19 22:37:01.040 585 585 E System : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
04-19 22:37:01.040 585 585 E System : Caused by: java.lang.IllegalArgumentException: connectHelper:928: Illegal argument to HAL module for camera "0"
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.throwAsPublicException(CameraManager.java:694)
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:778)
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.getCameraIdList(CameraManager.java:140)
04-19 22:37:01.040 585 585 E System : at com.android.server.retaildemo.RetailDemoModeService.getCameraIdsWithFlash(RetailDemoModeService.java:492)
04-19 22:37:01.040 585 585 E System : at com.android.server.retaildemo.RetailDemoModeService.onBootPhase(RetailDemoModeService.java:569)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServiceManager.startBootPhase(SystemServiceManager.java:143)
04-19 22:37:01.040 585 585 E System : ... 8 more
04-19 22:37:01.040 585 585 E System : Caused by: android.os.ServiceSpecificException: connectHelper:928: Illegal argument to HAL module for camera "0"
04-19 22:37:01.040 585 585 E System : at android.os.Parcel.readException(Parcel.java:1706)
04-19 22:37:01.040 585 585 E System : at android.os.Parcel.readException(Parcel.java:1645)
04-19 22:37:01.040 585 585 E System : at android.hardware.ICameraService$Stub$Proxy.getCameraCharacteristics(ICameraService.java:404)
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:765)
Maybe sources under hardware/sprd/libcamera should be changed in order to make it work...
3) A device to test. The one I was using was borrowed from a friend, but already returned.
In any case, all source code I changed is available on github (check for pstglia on github - repository "local_manifests" maps all the changes (except platform_frameworks_base, which requires the last 2 commits from branch "T113NU_COM_A_MAO_NO_BOLSO".

Muito obrigado pela ROM
Falei com vc lá pelo YouTube e agradeço novamente pela rom. O tablet ficou novo em folha. Continue com seu ótimo trabalho ?

Heyyy, how you've made this custom rom?
I'm trying to build that for my sm-t280, and all instructions doesn't ever exist. if you gimme instructions to build, you'll doing a huge help.
email: [email protected]
pstglia said:
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Prerequisites:
TWRP version 3.0.2
Galaxy Tab E SM-T113NU (similar models were not tested)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Will update this thread with links when my user reaches the required points (new on xda)
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
stephenpump (My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
Click to expand...
Click to collapse

YggH said:
I'm trying to build that for my sm-t280, and all instructions doesn't ever exist. if you gimme instructions to build, you'll doing a huge help.
email: [email protected]
Click to expand...
Click to collapse
Hi,
Tried to write a simplified procedure to compile the custom ROM for T113NU. See the 8 steps bellow:
I) Assuming you already have a build environment set up (see [1] as reference), download lineage sources using repo commands (repo init, repo sync)
Note: Use branch cm-14.1 (nougat)
II) After syncing, download core33g.xml from my github ( repo local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO) and copy to .repo/local_manifests (create it if doesn't exists)
III) execute "repo sync" again. The files/sources I modified will be downloaded and updated on source tree
IV) Edit vendor/cm/vendorsetup.sh and add this lunch combo:
Code:
add_lunch_combo lineage_core33g-userdebug
This will allow you to select a target compatible with T113NU when running "brunch"
V) As pointed previous posts, camera was avoiding Android to start. To allow booting, cameras were disabled (forced returned number of cameras to 0).
So, for T113NU, commit "0acc7879a9794aacdff85ef1563807d051114917 - frameworks/base - HACK - Disable cameras" will be needed. This commit is on my github, repository platform_frameworks_base, branch T113NU_COM_A_MAO_NO_BOLSO)
VI) Before compiling, export these environment variables:
Code:
export USE_CCACHE=1
ccache -M 50G
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export LC_ALL=C
I suggest you to include these on a file in your home dir (ex: ~/.android_profile) and include it every time you want to create a new build:
Code:
source ~/.android_profile
VII) Include build/envsetup.sh to config Android environment
Code:
source build/envsetup.sh
VIII) Compile the ISO using brunch (select lineage_core33g-userdebug option)
This should do it.
For your device (T280) you'll probably want to replace kernel by the one provided by samsung opensource.
Download it from Samsung Opensource Release Center (see [2]) and unpack it to kernel/samsung/core33g (clean previous files first)
Also:
A) After unpacking, cd to kernel/samsung/core33g and execute a "make mrproper" to remove any temp files under the source tree;
B) cd to kernel/samsung/core33g/arch/arm/configs and rename/copy one of the config files there to "cyanogen_core33g_defconfig" (select one that matches your device - in my case was goyavewifi-dt_hw04_defconfig)
C) You'll probably will need commits to make your kernel compatible with Android 7.1. Try cherry-picking the commits I used, starting from 8c97f3624701f53843b7b2da40185cdcd1c7a422
Play around with config/fw files and have lots of pacience. Creating a working image is not always a funny (consumes lots of time and requires much pacience, logging/debugging )
Good luck!
[1] - https wiki DOT lineageos DOT org/devices /bacon/buildcon/build
[2] - opensource DOT samsung DOT com
ps: Does your device uses Spreadtrum SOC, right?
ps2: Except for kernel, most of changes were minor. Most of this commits were based on remilia15 work. Kudos for who really deserve it!

@sasi2006166 @dhruvpatel_9880 Also works with T116!!

MegaStormBR said:
@[email protected]_9880 Also works with T116!!
Click to expand...
Click to collapse
I will try it today ?

@pstglia Thank you soo much For This ROM..I will try this ROM Today on my SM-T116NY.

Going to fix camera gimme sources
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
Also pm me on Telegram @sasi2006166

pstglia said:
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Prerequisites:
TWRP version 3.0.2
Galaxy Tab E SM-T113NU (similar models were not tested)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Will update this thread with links when my user reaches the required points (new on xda)
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
stephenpump (My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
Click to expand...
Click to collapse
Bro I installed twrp 3.0.2 and Wiped Data, Chache,Dalvik and system..And I flashed the ROM.. It showed "Unknown Command [log]" BUT FLASHING WAS SUCCESSFUL..So I Botted the tab and now it's showing the Lineage OS boot animation from 15 mins..Ik it takes a hell lot of time for the first boot but 15 mins?!??
I'll update if something happens..

Shreyas.ĒXĒ said:
Bro I installed twrp 3.0.2 and Wiped Data, Chache,Dalvik and system..And I flashed the ROM.. It showed "Unknown Command [log]" BUT FLASHING WAS SUCCESSFUL..So I Botted the tab and now it's showing the Lineage OS boot animation from 15 mins..Ik it takes a hell lot of time for the first boot but 15 mins?!
I'll update if something happens..
Click to expand...
Click to collapse
Hi
5 minutes is the maximum time. 15 minutes can be threated as a bootloop.
Some users reported this on youtube (for T113NU models).
Try pluging USB and check if you have adb connection. If so, check logcat/dmesg

sasi2006166 said:
Going to fix camera gimme sources
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
Also pm me on Telegram @sasi2006166
Click to expand...
Click to collapse
Hi, this manifest has all the repositories changed (except framework-native, which also can be pushed from my github, branch T113NU_COM_A_MAO_NO_BOLSO)
# Local manifest
https://github.com/pstglia/local_manifests/tree/T113NU_COM_A_MAO_NO_BOLSO
# Framework-Native
https://github.com/pstglia/frameworks-native/tree/T113NU_COM_A_MAO_NO_BOLSO

pstglia said:
Hi
5 minutes is the maximum time. 15 minutes can be threated as a bootloop.
Some users reported this on youtube (for T113NU models).
Try pluging USB and check if you have adb connection. If so, check logcat/dmesg
Click to expand...
Click to collapse
I took a Logcat file.But I am not able to attach it to this post it's showing"Bad Request"I think you are right my Tab is Bootlooped..Any solutions??
Edit: I have uploaded a Google drive link for the logcat.log file..pls see it..
https://drive.google.com/file/d/15491N45mEhIb-MZU72ef83VESCEK_WGi/view?usp=drivesdk

Thanks for the rom! I am using this ROM whit gapps pico and works everything so good! !!
Enviado desde mi Nexus 5X mediante Tapatalk

dhruvpatel_9880 said:
I will try it today
Click to expand...
Click to collapse
Hey man, I think something is wrong, T116NY and T116BU are identical. Here's what I've done:
- Made a Nandroid backup
- Downloaded Opengapps 7.1 ARM Pico
- Downloaded the ROM
- Downloaded TWRP 3.0.2 from dl.twrp.me/goyave
- Wiped System, Data, Cache and Dalvik
- Flashed the ROM, OpenGApps, then TWRP, in this order.
You should try it this way.
---------- Post added at 08:51 PM ---------- Previous post was at 08:47 PM ----------
dhruvpatel_9880 said:
I will try it today
Click to expand...
Click to collapse
If it still doesn't work, check if your using the correct version of TWRP (3.0.2) Download it at the link I gave you.
---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------
PS: I wasn't able to reply the private message
---------- Post added at 09:38 PM ---------- Previous post was at 08:57 PM ----------
When I flashed the ROM, I noticed that it was running on a lower resolution than the normal (480p instead of 720p). If anyone else have this issue, just go to build.prop and change lcd_density to stock value (In my case is 160). Hope this helps!

Shreyas.ĒXĒ said:
I took a Logcat file.But I am not able to attach it to this post it's showing"Bad Request"I think you are right my Tab is Bootlooped..Any solutions?
Edit: I have uploaded a Google drive link for the logcat.log file..pls see it..
https://drive.google.com/file/d/15491N45mEhIb-MZU72ef83VESCEK_WGi/view?usp=drivesdk
Click to expand...
Click to collapse
Hi,
Unfortunatelly couldn't get any clue by logcat output. Can you post dmesg as well?
@All
Anyone with experience in LineageOS ROMS could give a clue?
Some user with identical device models I had in hand (T113NU) reported the same issue. In these cases, logcat stops logging at the beginning and I couldn't figure out any related message on dmesg?
I'm discarding hw failure because stock ROM works in these cases (based on reports from users)
Regards
pstglia

This rom technically should work if the device code name is " goyave ".mine was sm-t116 and code name is "goyave3g".And working perfectly .

pstglia said:
Hi,
Unfortunatelly couldn't get any clue by logcat output. Can you post dmesg as well?
@All
Anyone with experience in LineageOS ROMS could give a clue?
Some user with identical device models I had in hand (T113NU) reported the same issue. In these cases, logcat stops logging at the beginning and I couldn't figure out any related message on dmesg?
I'm discarding hw failure because stock ROM works in these cases (based on reports from users)
Regards
pstglia
Click to expand...
Click to collapse
Sorry lol..I forgot to add dmesg..
I have given the LATEST logcat and Dmesg file in the link below..pls see it..
https://drive.google.com/folderview?id=1-8xJgzLeSE8TJxv5gh_ZXTLyXbB-0IcK
---------- Post added at 05:24 AM ---------- Previous post was at 05:21 AM ----------
MegaStormBR said:
Hey man, I think something is wrong, T116NY and T116BU are identical. Here's what I've done:
- Made a Nandroid backup
- Downloaded Opengapps 7.1 ARM Pico
- Downloaded the ROM
- Downloaded TWRP 3.0.2 from dl.twrp.me/goyave
- Wiped System, Data, Cache and Dalvik
- Flashed the ROM, OpenGApps, then TWRP, in this order.
You should try it this way.
---------- Post added at 08:51 PM ---------- Previous post was at 08:47 PM ----------
If it still doesn't work, check if your using the correct version of TWRP (3.0.2) Download it at the link I gave you.
---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------
PS: I wasn't able to reply the private message
---------- Post added at 09:38 PM ---------- Previous post was at 08:57 PM ----------
When I flashed the ROM, I noticed that it was running on a lower resolution than the normal (480p instead of 720p). If anyone else have this issue, just go to build.prop and change lcd_density to stock value (In my case is 160). Hope this helps!
Click to expand...
Click to collapse
Bro I tried your method but still It's Bootlooping(stuck on Lineage OS boot animation)
P.s: I have already installed Twrp version (3.0.2)..

Shreyas.ĒXĒ said:
Sorry lol..I forgot to add dmesg..
I have given the LATEST logcat and Dmesg file in the link below..pls see it..
https://drive.google.com/folderview?id=1-8xJgzLeSE8TJxv5gh_ZXTLyXbB-0IcK
---------- Post added at 05:24 AM ---------- Previous post was at 05:21 AM ----------
Bro I tried your method but still It's Bootlooping(stuck on Lineage OS boot animation)
P.s: I have already installed Twrp version (3.0.2)..
Click to expand...
Click to collapse
Huh, thats weird. T116BU working.