Develop Bugs

[DEV] Can't compile CM 6.2 for HERO?¿?

Hi all,
Does anyone managed to compile latest CM 6.2 (froyo) sources?¿?¿. I get errors when compiling CMParts and if I choose not to compile CMParts, I get a package that gets me in to crash loops on first start.....
Many Thanks in Advance,
Perdita2000

perdita2000 said:
Hi all,
Does anyone managed to compile latest CM 6.2 (froyo) sources?¿?¿. I get errors when compiling CMParts and if I choose not to compile CMParts, I get a package that gets me in to crash loops on first start.....
Many Thanks in Advance,
Perdita2000
Click to expand...
Click to collapse
You need CMParts. Can you post the compilation errors?

These are my compile errors...
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:72: cannot find symbol
symbol : variable config_enableScreenOffAnimation
location: class com.android.internal.R.bool
getResources().getBoolean(com.android.internal.R.bool.config_enableScreenOffAnimation) ? 1 : 0) == 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:83: cannot find symbol
symbol : variable ACCELEROMETER_ROTATE_180
location: class android.provider.Settings.System
Settings.System.ACCELEROMETER_ROTATE_180, 0) == 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:96: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_ON
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_ON, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:102: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_OFF
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_OFF, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:108: cannot find symbol
symbol : variable ACCELEROMETER_ROTATE_180
location: class android.provider.Settings.System
Settings.System.ACCELEROMETER_ROTATE_180, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:125: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.OVERSCROLL_EFFECT, 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:196: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.putInt(getContentResolver(), Settings.System.OVERSCROLL_EFFECT,
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
11 errors
make: *** [out/target/common/obj/APPS/CMParts_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Many Thanks for you Help!!!
Perdita2000

I'm not modifyng any code because first compilation of any CM sources I always use source as is, then I try this created CM-untouched-sources rom and start to make changes (I am developing on CM7 and would like to have my own CM6.2 too...)
Many Thanks,
Perdita2000

I would check two things:
A. That you updated all the repositories. Do another "repo sync" to make sure everything is up to date. If you are using some repositories which you forked (or someone else) they also need to be updated "manually".
B. Do a clean build, by totally removing the "out" directory and then try to recompile it.
If you are still having trouble I can try to look into it, maybe even tonight.

Download froyo_stable CMParts,then it is no problem to compile,or I upload my modified CMParts 6.2.0 with setcpu etc... if you want that

This should fix the issue:
Code:
cd packages/apps/CMParts && git checkout 69613a248519fed7d971bd6292013d36097d0107
- taken from http://forum.cyanogenmod.com/topic/15353-froyo-compile-cannot-find-symbol-error/
At least, that fixed the issue for me.

erasmux said:
I would check two things:
A. That you updated all the repositories. Do another "repo sync" to make sure everything is up to date. If you are using some repositories which you forked (or someone else) they also need to be updated "manually".
B. Do a clean build, by totally removing the "out" directory and then try to recompile it.
If you are still having trouble I can try to look into it, maybe even tonight.
Click to expand...
Click to collapse
I have done A and B yet a few days ago, but nothing was solved and I found k0ner solution too, but It seems to solved compilation issue (can't find what patch 69613a248519fed7d971bd6292013d36097d0107 do?¿?¿, don't know how to search this code on git...) but ROM compiled doesn't boot (boot loop, but don't have error now, I will reproduce it and send logcat...).
Where can I find CMParts stable?¿?¿
Many Thanks to ALL,
Perdita2000

Elelinux, do you mean use froyo-stable branch for CMParts??
Many Thanks,
Perdits2000

perdita2000 said:
Where can I find CMParts stable?¿?¿
Many Thanks to ALL,
Perdita2000
Click to expand...
Click to collapse
Here https://github.com/CyanogenMod/android_packages_apps_CMParts/tree/froyo-stable

perdita2000 said:
Elelinux, do you mean use froyo-stable branch for CMParts??
Many Thanks,
Perdits2000
Click to expand...
Click to collapse
Yes as you see in post above,download it and replace it with that CMParts you have now.

A fully up to date CM6 ROM? I sincerely hope this works out! I think this would be the ideal ROM for our HTC Hero. Gingerbread's a bit slow on the Hero, but Froyo has always worked well.
I'm just writing this to let you know I'd be hugely appreciative of any ROM that you end up producing here!

I am getting same boot loop as when I applied mentioned patch....
I have synced CMParts git with froyo-stable brunch and compile again (clean before new compile) and no errors (typical VM cores from out of memory .... I always get one or two during compilation on CM7 but everything works fine... not enough memory for compilations ( ), but after flash new rom it loops on HTC HERO with following errors...
I/dalvikvm( 161): System server process 164 has been created
I/Zygote ( 161): Accepting command socket connections
I/dalvikvm( 164): Unable to dlopen(/system/lib/libandroid_servers.so): Cannot load library: link_image[2033]: failed to link libandroid_servers.so
I/dalvikvm( 164):
D/AndroidRuntime( 164): Shutting down VM
W/dalvikvm( 164): threadid=1: thread exiting with uncaught exception (group=0x400207e0)
E/AndroidRuntime( 164): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 164): java.lang.UnsatisfiedLinkError: Library android_servers not found
E/AndroidRuntime( 164): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 164): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 164): at com.android.server.SystemServer.main(SystemServer.java:592)
E/AndroidRuntime( 164): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 164): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 164): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 164): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 164): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 164): Error reporting crash
E/AndroidRuntime( 164): java.lang.NullPointerException
E/AndroidRuntime( 164): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 164): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:887)
E/AndroidRuntime( 164): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:884)
E/AndroidRuntime( 164): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 164): Sending signal. PID: 164 SIG: 9
I/Zygote ( 161): Exit zygote because system server (164) has terminated
D/AndroidRuntime( 172):
D/AndroidRuntime( 172): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 172): Heap size: -Xmx16m
D/AndroidRuntime( 172): CheckJNI is OFF
D/AndroidRuntime( 172): --- registering native functions ---
I/SamplingProfilerIntegration( 172): Profiler is disabled.
I/Zygote ( 172): Preloading classes...
D/dalvikvm( 172): GC_EXPLICIT freed 824 objects / 47648 bytes in 7ms
D/dalvikvm( 172): GC_EXPLICIT freed 368 objects / 19104 bytes in 7ms
I/bluetooth_ScoSocket.cpp( 172): Entry name = MY-CAR ScoTypes = 0x7f
I/bluetooth_ScoSocket.cpp( 172): Entry name = Motorola HF850 ScoTypes = 0x7
D/dalvikvm( 172): GC_EXPLICIT freed 319 objects / 18080 bytes in 8ms
D/dalvikvm( 172): GC_EXPLICIT freed 464 objects / 28864 bytes in 9ms
D/dalvikvm( 172): GC_EXPLICIT freed 2096 objects / 108592 bytes in 13ms
I'm going to take a look at /system/lib/libandroid_servers.so compilation because I think is the problem...
Many Thanks to All,
Perdita2000

Hi all,
I have tried a couple of times with no luck, can't find if there is some problem with repos or just a code error, because it compiles without any error...
Have tried to sync froyo-stable but no luck too....
Syncing work tree: 4% (9/210) error: revision master in CyanogenMod/android_device_advent_vega not found
Perdita2000

perdita2000 said:
Hi all,
I have tried a couple of times with no luck, can't find if there is some problem with repos or just a code error, because it compiles without any error...
Have tried to sync froyo-stable but no luck too....
Syncing work tree: 4% (9/210) error: revision master in CyanogenMod/android_device_advent_vega not found
Perdita2000
Click to expand...
Click to collapse
In your /android/system/.repo/manifest/ you find default.xml edit the file and remove the path for advent_vega then run repo sync again

Many Thanks Elelinux ... and sorry about "my newbie questions" .... I'm starting to use github today (more than repo init/sync ... etc)..
Perdita2000

Checked out the "froyo" branch, did a "repo sync", added HTC proprietary files and ROM Manager and started the compile.
Ran into the same compilation error from the start of this thread.
Then applied bjk's fix from here (added the diff files there so you can apply then automatically with "git apply"), then compilation completed smoothly. Boots up just fine here.
What exactly is the error you are getting?

Boot error is posted thread . Did you tried stable or current branch?
Many thanks,
Sent from my Hero using XDA App

perdita2000 said:
Boot error is posted thread . Did you tried stable or current branch?
Many thanks,
Sent from my Hero using XDA App
Click to expand...
Click to collapse
Ok, sorry didn't see it. Doesn't make much sense to me. I used the "froyo" branch (not "froyo-stable"). But this shouldn't matter.
From where did you take your proprietary libs? Try taking them from here: https://github.com/koush/proprietary_vendor_htc/tree/froyo (notice the froyo branch).

I always use device propietary files from device itself. Do you mean they could be wrong?, in fact extract-files.sh didn't pull every needed file (I thought it was wrong because haven't got any issue compiling CM7?¿?¿?).
I will try device files from koush and let you know!!!
Many Thanks to Everyone!!!
Perdita2000

[MOD]Modified DSP Manager with BEATS audio. For CM9, MIUI & AOKP.(6.25.12)

{
"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"
}
​
I have Modded DSPManager to use the libs & Audio files from BEATS to work with AOKP & CM9 ONLY!!!
Flashing this will not mess up your other Equalizers!!​
V.1
Had a bunch of FC for alot of devices
v.2
Fixed the FC issue
v.3
Added MUSICFX so settings work for CM9
Added Awesome Control Panel
Re-built Awesome BEATS
Download: AwesomeBEATS™ v.3
Just FLASH and enjoy!!
Make sure to change in SETTINGS/SOUND/MUSIC EFFECTS to AWESOME BEATS.
Thanks to:
spc_hicks09 (with Permission to use his modded DSP manager)
Sckyboy78 (For the find )
nik3r (For all the help getting it to work on other devices)
mwalt2 (Helping fix the MOD to work on CM9 based Roms)
Confirmed Devices working:
MyTouch 4G
Desire HD
Desire S
Inspire 4G
Desire
GalaxyTab Plus
Sensation
Amaze 4G
Galaxy S2
Nexus
SSII
SI
Sensation XL
Donations Received:
*Dgardner425
*La_Blu_Eyez
*Tornado234
*WhiteMambaB
*Fabio Battisti
*Chris Miller
*Mike Cruz
*Liz Aguilar​MAKE SURE YOU GUYS HIT THAT THANK BUTTON IF THIS MOD WORKED FOR YOU!!!​

Awesome I have been looking for something like this for a long time
(Need nandroid first I'm in a middle of testing something)

nik3r said:
Awesome I have been looking for something like this for a long time
Click to expand...
Click to collapse
Test and report plz and repost what rom your on thanks.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2

Can it work with aokp b39?
Sent from my Desire Z using XDA

Steven How said:
Can it work with aokp b39?
Sent from my Desire Z using XDA
Click to expand...
Click to collapse
Test it! Worked fine on my end and report back thanks.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2

Testing...
Flash ... OK
Boot ... OK
Settings - Sound - Effects entry ... OK
Switched engine ... OK
Control app ... FAILED
Rebooting for second try ...
...
...
Engine persisted ... OK
Control app ... FAILED
It FC's on me and I don't hear a difference, sorry

nik3r said:
Testing...
Flash ... OK
Boot ... OK
Settings - Sound - Effects entry ... OK
Switched engine ... OK
Control app ... FAILED
Rebooting for second try ...
...
...
Engine persisted ... OK
Control app ... FAILED
It FC's on me and I don't hear a difference, sorry
Click to expand...
Click to collapse
What rom so I can flash it and test thanks.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2

EliteMod (= basically AOKPb39 + EliteKernel)

confirmed that on nik3r's elitemod rom the control app does not work. It force closes everytime. exactly as described above.

LogCat
Code:
I/ActivityManager( 1421): START {act=android.intent.action.MAIN cat=[android.int
ent.category.LAUNCHER] flg=0x10200000 cmp=com.bel.android.dspmanager/.activity.D
SPManager} from pid 1950
I/ActivityManager( 1421): Start proc com.bel.android.dspmanager for activity com
.bel.android.dspmanager/.activity.DSPManager: pid=4034 uid=10043 gids={3002}
D/OpenGLRenderer( 1950): Flushing caches (mode 1)
W/AssetRedirectionManager( 1421): Unable to attach target package assets for com
.bel.android.awesome
E/dalvikvm( 4034): Dex cache directory isn't writable: /data/dalvik-cache
I/dalvikvm( 4034): Unable to open or create cache for /system/app/Awesome BEATS.
apk (/data/dalvik-cache/[email protected]@Awesome [EMAIL="[email protected]"][email protected][/EMAIL])
D/AndroidRuntime( 4034): Shutting down VM
W/dalvikvm( 4034): threadid=1: thread exiting with uncaught exception (group=0x4
0a591f8)
E/AndroidRuntime( 4034): FATAL EXCEPTION: main
E/AndroidRuntime( 4034): java.lang.RuntimeException: Unable to instantiate activ
ity ComponentInfo{com.bel.android.dspmanager/com.bel.android.dspmanager.activity
.DSPManager}: java.lang.ClassNotFoundException: com.bel.android.dspmanager.activ
ity.DSPManager
E/AndroidRuntime( 4034): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:1993)
E/AndroidRuntime( 4034): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2104)
E/AndroidRuntime( 4034): at android.app.ActivityThread.access$600(Activit
yThread.java:132)
E/AndroidRuntime( 4034): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1157)
E/AndroidRuntime( 4034): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 4034): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 4034): at android.app.ActivityThread.main(ActivityThrea
d.java:4575)
E/AndroidRuntime( 4034): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 4034): at java.lang.reflect.Method.invoke(Method.java:5
11)
E/AndroidRuntime( 4034): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 4034): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:553)
E/AndroidRuntime( 4034): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4034): Caused by: java.lang.ClassNotFoundException: com.bel.an
droid.dspmanager.activity.DSPManager
E/AndroidRuntime( 4034): at dalvik.system.BaseDexClassLoader.findClass(Ba
seDexClassLoader.java:61)
E/AndroidRuntime( 4034): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:501)
E/AndroidRuntime( 4034): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:461)
E/AndroidRuntime( 4034): at android.app.Instrumentation.newActivity(Instr
umentation.java:1023)
E/AndroidRuntime( 4034): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:1984)
E/AndroidRuntime( 4034): ... 11 more
W/ActivityManager( 1421): Force finishing activity com.bel.android.dspmanager/
.activity.DSPManager
D/OpenGLRenderer( 1950): Flushing caches (mode 0)
Should be easy to figure out.
I'll try to wipe dalvik cache for one..
EDIT: No such luck, DSP manager from CM9 was working fine.
EDIT2: Doesn't work from /data/app either

Ok i figured it out hopefully it works now please reply if you dont get the FC anymore
Instructions please make sure u deleted the AwesomeBEATS.apk first from system/apps before flashing.
Thanks guys for testing again for me.
This is what your suppose to get.

Is it just me or is there a space in that filename... linux hates that you know..
EDIT: Doesn't work either, I think this bit is the problem:
I/dalvikvm( 3312): Unable to open or create cache for /system/app/Awesome BEATS.apk (/data/dalvik-cache/[email protected]@Awesome [email protected])
There's a space in that dex class filename, I don't think that's allowed
Renamed the apk file and trying to regenerate dalvik cache.
---------- Post added at 03:07 AM ---------- Previous post was at 02:46 AM ----------
Yup got it working by renaming the apk file, but I hear no changes in sound when I move the EQ, the engine is selected and I even rebooted.

nik3r said:
Is it just me or is there a space in that filename... linux hates that you know..
EDIT: Doesn't work either, I think this bit is the problem:
I/dalvikvm( 3312): Unable to open or create cache for /system/app/Awesome BEATS.apk (/data/dalvik-cache/[email protected]@Awesome [email protected])
There's a space in that dex class filename, I don't think that's allowed
Renamed the apk file and trying to regenerate dalvik cache.
---------- Post added at 03:07 AM ---------- Previous post was at 02:46 AM ----------
Yup got it working by renaming the apk file, but I hear no changes in sound when I move the EQ, the engine is selected and I even rebooted.
Click to expand...
Click to collapse
Can you pm me the one you got working so I can look at it thanks.
Edit: What app were u using to listen to music? Apollo? Theirs a big difference with Apollo.
Edit: All you did was rename the App from Awesome Beats.apk to AwesomeBeats.apk?
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2

Yup just rename it without space, the dex class is named after the apk file. Notice how nobody uses spaces in their filenames for that very reason, the convention is xx.domain.appname.apk for a reason, there's no space in URL either
I use poweramp and I disabled all internal postprocessing to hear it better.
Oh it works fine with google music. I'll see if I can get it to work with poweramp too
Yup if I disable direct volume control it works well, just takes a while to take effect, poweramp has nice large buffers
Nice work, just change the filename and here's your certificate for my ROM:
Code:
[** NIKER APPROVED **]

nik3r said:
Yup just rename it without space, the dex class is named after the apk file. Notice how nobody uses spaces in their filenames for that very reason, the convention is xx.domain.appname.apk for a reason, there's no space in URL either
I use poweramp and I disabled all internal postprocessing to hear it better.
Oh it works fine with google music. I'll see if I can get it to work with poweramp too
Yup if I disable direct volume control it works well, just takes a while to take effect, poweramp has nice large buffers
Nice work, just change the filename and here's your certificate for my ROM:
Code:
[** NIKER APPROVED **]
Click to expand...
Click to collapse
Thanks man I appreciate it! Gave u thanks in the OP!.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2

So doesn't work with apollo?

XxhTcG2uSERxX said:
So doesn't work with apollo?
Click to expand...
Click to collapse
I does work with Apollo hit settings and equalizer and it will bring up the Awesome Control by default it used Apollo for your audio files.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2

The preset are all 0.0+,running mimicry

XxhTcG2uSERxX said:
The preset are all 0.0+,running mimicry
Click to expand...
Click to collapse
In equalizer? I set the equalizer at 0.0 but even without the equalizer u can see a huge improvement and if u wanna add anything else thru the equalizer or use a different app like Power Amp it will now use the beats audio files.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2

Oh,because in ur screenshot it has them high

[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??

MIUI 7 Porting [WIP, Need Help]

Hello guys.
I'm working on porting MIUI 7 on our devices.
I'm totally fixed all bootloop problems except one.
Here is logcat:
Code:
W/dalvikvm( 489): Unable to register: not native: Lcom/google/android/gles_jni/EGLImpl;.eglDestroyContext:(Ljavax/microedition/khronos/egl/EGLDisplay;Ljavax/microedition/khronos/egl/EGLContext;)Z
E/dalvikvm( 489): JNI posting fatal error: RegisterNatives failed for 'com/google/android/gles_jni/EGLImpl'; aborting...
Here is no EGLImpl.smali in framework.jar of miui / cm, as "com" folder too.
I have found old smali code, but it is not compiling.
Anybody have any ideas how to make it work?
Thanks for all replies.

EGLImpl error fixed.
New problem:
Code:
dlopen failed: library "/system/lib/libnetcmdiface.so" not found
Full logcat: https://www.dropbox.com/s/1k5sm79g7gf67jp/miui runtime.txt?dl=0
If you have any ideas how to fix it - reply pls.

wielski said:
EGLImpl error fixed.
New problem:
Code:
dlopen failed: library "/system/lib/libnetcmdiface.so" not found
Full logcat: https://www.dropbox.com/s/1k5sm79g7gf67jp/miui runtime.txt?dl=0
If you have any ideas how to fix it - reply pls.
Click to expand...
Click to collapse
Which Device do you port from?

YSH ALSAGER said:
Which Device do you port from?
Click to expand...
Click to collapse
Xiaomi Redmi 2 && Xiaomi Mi3 + Patchrom smali.
IDK about ril, but everything other should work. Maybe I could port CM11 ril, let's see
Maybe you know better donor for our phone ?
But first I need to fix boot problems.

wielski said:
Code:
W/dalvikvm( 489): Unable to register: not native: Lcom/google/android/gles_jni/EGLImpl;.eglDestroyContext:(Ljavax/microedition/khronos/egl/EGLDisplay;Ljavax/microedition/khronos/egl/EGLContext;)Z
E/dalvikvm( 489): JNI posting fatal error: RegisterNatives failed for 'com/google/android/gles_jni/EGLImpl'; aborting...
Click to expand...
Click to collapse
EGLImpl error fixed, restored android_runtime.so because of it can cause problems in future.
Who have the same problem, here is solution:
1) Download MIUI framework source code http://www.java2s.com/Open-Source/J...rk/Download_miui_framework_Free_Java_Code.htm
2) Smali it with Smali v1
3) Baksmali with Smali v2
4) Paste com/google and javax folders in your framework
5) That's it!
Click to expand...
Click to collapse
Working on porting, have A LOT of bootlop bugs, but it's quite easy to fix.

[ROM][7.1.1][XT16xx][Moto G4/Plus] OmniROM Bringup

UPDATE
Initial OmniROM release for Athene out now:
omni-7.1.1-20170219-athene-HOMEMADE.zip
--- Original OP below ---
Hi guys, I have started the bringup for OmniROM on Athene:
Device
Kernel
It starts to boot up, but gets stuck in the bootanimation and restarts soon after. According to dmesg / logcat, the modem does not come up (see attached files). I compared init.rc files and blobs being used with other roms (lineage / aex), but couldn't identify the root cause for that error at this early stage:
Code:
[ 7.022888,0] Fatal error on the modem.
[ 7.022913,0] modem subsystem failure reason: fs_device_efs_rmts.c:175:Invalid shared ram address from Apps.
@rahulsnair, @Silesh.Nair (or anybody else): Can you guys please help out here, is that something you have come across in any of your bringups? Really would like to bring Omni to life on Athene.
Thanks in advance :good:

Looks like rmt_storage can't load the needed modem firmware :
Code:
09-21 03:07:13.861 342 342 D rmt_storage: GZFSG open /fsg/athene_dsds_emea.img.gz
09-21 03:07:13.861 342 342 E rmt_storage: Couldn't open /fsg/athene_dsds_emea.img.gz, trying default for product-radio
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/athene_emea.img.gz, trying default for radio
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/emea.img.gz, trying default
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/0.img.gz
09-21 03:07:13.862 342 342 I rmt_storage: rmt_storage_open_cb: Unable to open /boot/modem_fsg
Check that /fsg partition is mounted (can't check that in logs cause it's not full logs) and files are there.
You can also try to "strace" rmt-storage process :
Code:
strace -fF -s 1000 rmt_storage > /sdcard/rmt_storage_strace.txt

vache said:
Looks like rmt_storage can't load the needed modem firmware :
Check that /fsg partition is mounted (can't check that in logs cause it's not full logs) and files are there.
You can also try to "strace" rmt-storage process :
Click to expand...
Click to collapse
Good point, thanks. Haven't checked the mounts on boot yet. Eventually, fstab.qcom does not get parsed.

Making some progress: There is an issue with the ramdisk of the inline-built kernel: It is not picking up the correct .rc files. I don't get where these references to "recovery" are coming from:
Code:
<13>[ 3.022567,0] init: init second stage started!
<11>[ 3.207517,0] init: waitpid failed: No child processes
<11>[ 3.209434,0] init: property_set("ro.com.google.clientidbase", "android-motorola") failed
<11>[ 3.209584,0] init: property_set("ro.config.notification_sound", "Argon.ogg") failed
<11>[ 3.209599,0] init: property_set("ro.config.alarm_alert", "Helium.ogg") failed
<11>[ 3.209710,0] init: property_set("ro.config.ringtone", "Orion.ogg") failed
<13>[ 3.209803,0] init: (Loading properties from /default.prop took 0.00s.)
<11>[ 3.210260,0] init: /init.rc: 12: invalid command 'setcon'
<11>[ 3.210326,0] init: /init.rc: 62: invalid command 'load_all_props'
<11>[ 3.210406,0] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
<13>[ 3.210688,0] init: (Parsing /init.recovery.usb.rc took 0.00s.)
<13>[ 3.210735,0] init: (Parsing /init.recovery.service.rc took 0.00s.)
<11>[ 3.210812,0] init: could not import file 'init.target.recovery.rc' from '/init.recovery.qcom.rc'
<13>[ 3.210827,0] init: (Parsing /init.recovery.qcom.rc took 0.00s.)
However, having flashed a Lineage kernel, it's booting up now.
@vache: /fsg indeed was not mounted. I think there is an issue with the mkdir, will amend that now.

Unhandled fsg_file security context on the fstab /fsg entry was the root cause for not mounting /fsg. Omni kernel booting up now.

golden-guy said:
Unhandled fsg_file security context on the fstab /fsg entry was the root cause for not mounting /fsg. Omni kernel booting up now.
Click to expand...
Click to collapse
Well done
To get RIL working, you need to add android_system_qcom from Lineage in your manifest and rebuilt.
Or you can push libqsap_sdk.so manually.

vache said:
Well done
To get RIL working, you need to add android_system_qcom from Lineage in your manifest and rebuilt.
Or you can push libqsap_sdk.so manually.
Click to expand...
Click to collapse
Thanks mate, I have done that yesterday to get RIL working (radio logcat showed that rild was complaining about that missing libqsap_sdk.so lib). All fine there already.
But I am still struggling with at least three things atm: Sensors, media playback and camcorder.
Sensors: I can see them initialized, but they don't return any values. According to logcat, e.g proximity gets disabled on screen on (sic!) Which sounds weird tbh
Media playback: Acodec cannot instantiate decoders upon ringtone playback and when music is to be played via bluetooth. mp3/mpeg playback does work when played via phone' speaker though. It could be a codec issue, but it could be audio policy / routing related. We are using a custom policy, aren't we?
Camcorder - didn't look into that yet. But is very likely related to media codec issue.
Will add some logs to further explain.
EDIT: Logs are added now.
PS: Device repo updated

Will cross-check with LineageOS, but the lack of sensor data might be permission related after all. All sensors seem to be up and configured, with their /dev and /sys entries being populated. Unfortunately, there is no error to be seen in the logs, giving no indication of the root cause...

Got the sensor issue sorted. It was selinux related again - what else. :silly:
Anyhow, one issue less.

Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:

vinylmeister said:
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
Click to expand...
Click to collapse
He is courteous enough to give us status updates on what is happening and what he is currently fixing.
I dont think he would appreciate the ETA-ish question.
It will be released when he is done. Im sure he is not on this full time. Have patience.
Sent from my Moto G4 Plus using Tapatalk

vinylmeister said:
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
Click to expand...
Click to collapse
+1

1chrome said:
He is courteous enough to give us status updates on what is happening and what he is currently fixing.
I dont think he would appreciate the ETA-ish question.
It will be released when he is done. Im sure he is not on this full time. Have patience.
Click to expand...
Click to collapse
Didn't you realize that the issue related sentence was just ironic? The high-five smiley should indicate that, followed by seriously...

vinylmeister said:
Didn't you realize that the issue related sentence was just ironic? The high-five smiley should indicate that, followed by seriously...
Click to expand...
Click to collapse
Sorry man my bad... smileys didn't show up on my Tapatalk!
Sent from my Moto G4 Plus using Tapatalk

Vorbis decoder and camcorder are still open.
I'd love to have a fully working Omni build up by now, but time-wise this is a best-effort activity.
It is ready when it's done.

golden-guy said:
Vorbis decoder and camcorder are still open.
I'd love to have a fully working Omni build up by now, but time-wise this is a best-effort activity.
It is ready when it's done.
Click to expand...
Click to collapse
Could you grab fresh logs after trying to record a video ? Can't find traces in current logs.
Also, did you try with different camera apps ?

vache said:
Could you grab fresh logs after trying to record a video ? Can't find traces in current logs.
Also, did you try with different camera apps ?
Click to expand...
Click to collapse
I tried with Snap and SnapDragonCamera. I wanted to do that with a fresh build. After having synched sources, mm-camera daemon keeps crashing and causing bootloops. Omni has updated their manifest to r14, also, lineage seems to have merged in fresh caf sources causing issues with qcom blobs. If I had known that earlier, I wouldn't have synched anew.

I see u uploaded to afh is it ready for testing I'm excited

joeeboogz said:
I see u uploaded to afh is it ready for testing I'm excited
Click to expand...
Click to collapse
????!!

Good catch! ?
Yes, it's up for testing now: https://www.androidfilehost.com/?fid=457095661767137952
Please note that this is an early ALPHA build: Media playback (ogg/mp4) and camcorder are still broken. But apart from that it seems to work just fine.