Database Info

[APP][IR] ONE To Remote Them All [4000+ User Codes][45'000+ preloaded Codes]

Hi guys,
i'm developing an universal IR remote control. ATM its only working on the HTC ONE and i'm trying to port it to the Galaxy S4 (except the learning function).
The original thread is here:
ONE to remote them all
Got some confirms that it works on the S4 and the Galaxy Tab 8.0.
Please use this APK
http://otrta.nibdev.com/beta/ONEtoRemoteThemAllV2.apk
And follow the thread in the HTC ONE forum if you are interested in updates.

antifish said:
Hi guys,
i'm developing an universal IR remote control. ATM its only working on the HTC ONE and i'm trying to port it to the Galaxy S4 (except the learning function).
The original thread is here:
ONE to remote them all
If you are interessted to try an .APK which should support the S4 (and other Samsung IR enabled devices), send me a PM.
When its confirmed working i'll publish an update and rename the thread correct
Click to expand...
Click to collapse
is this app going to have IR learning skills? i ask so because there are many devices which are not listed and there are also a few million devices from china which are not listed. IR learning would me great. Maybe some hardware tweak with IR receivers and using USB OTG or learning the IR codes via the camera or something similar?

francisdsa said:
is this app going to have IR learning skills? i ask so because there are many devices which are not listed and there are also a few million devices from china which are not listed. IR learning would me great. Maybe some hardware tweak with IR receivers and using USB OTG or learning the IR codes via the camera or something similar?
Click to expand...
Click to collapse
I dont think IR learning is support for the Galaxy S4, at least not until someone finds out how. As i dont have a S4, i cant to any reverse enigneering.
Which devices / brands are missing? Did you tried the new DB with 45'000 codes and had a look if they are listed there?
On the other side, that Database would actually have been bigger, but i cut out all brands which i could not read (chinese, arabic, etc).
There are codes for chinese cableboxes i think, at least brands like:
惠州
珠江
东莞
东莞
黑龙江
山东
(+ a lot of others)
as i dont have any clue what these signs should mean, i delted them out

I9500 test
Not working

haririan said:
Not working
Click to expand...
Click to collapse
You dont have the right apk if you dont send me a PM..

antifish said:
I dont think IR learning is support for the Galaxy S4, at least not until someone finds out how. As i dont have a S4, i cant to any reverse enigneering.
Which devices / brands are missing? Did you tried the new DB with 45'000 codes and had a look if they are listed there?
On the other side, that Database would actually have been bigger, but i cut out all brands which i could not read (chinese, arabic, etc).
There are codes for chinese cableboxes i think, at least brands like:
惠州
珠江
东莞
东莞
黑龙江
山东
(+ a lot of others)
as i dont have any clue what these signs should mean, i delted them out
Click to expand...
Click to collapse
That's nice. But there are cheap chinese DVD players, media players, televisions, etc that work on IR remotes and the codes will not match all of them. Maybe if a simple interface for most uses like next, back, menu, volume, play, pause, forward, reverse, stop, power and mute are the must have buttons.
well i shall try the app and let you know if i am haveing issues.
Thanks for the reply though

francisdsa said:
That's nice. But there are cheap chinese DVD players, media players, televisions, etc that work on IR remotes and the codes will not match all of them. Maybe if a simple interface for most uses like next, back, menu, volume, play, pause, forward, reverse, stop, power and mute are the must have buttons.
well i shall try the app and let you know if i am haveing issues.
Thanks for the reply though
Click to expand...
Click to collapse
I send you the link to the APK for testing.
Again, the APK in the HTC ONE forum will force close immediatly on the S4

antifish said:
I send you the link to the APK for testing.
Again, the APK in the HTC ONE forum will force close immediatly on the S4
Click to expand...
Click to collapse
I did not get any link for the app.
can you resend it?
thanks

francisdsa said:
I did not get any link for the app.
can you resend it?
thanks
Click to expand...
Click to collapse
Sent again

antifish said:
Sent again
Click to expand...
Click to collapse
Did not get any error message. the app started and showed me a complete tabular list of the brand names. no error so far. but have nothing to test it on. Am at work. will go home and try on devices at home. will get back tomorrow
thanks
is there any other skinned layout for the buttons. this one seems very hectic

francisdsa said:
Did not get any error message. the app started and showed me a complete tabular list of the brand names. no error so far. but have nothing to test it on. Am at work. will go home and try on devices at home. will get back tomorrow
thanks
is there any other skinned layout for the buttons. this one seems very hectic
Click to expand...
Click to collapse
If it works, please thest the DB2 Browser (its a new database i got with 45000+ codes, had not the time to correctly sort and implement it yet).
Not at the moment, tell me what you like as layout and try to implement it?
What you can do at the moment is to place a widget on your homescreen for most-used functions, and soon there will be possibilty to create custom layouts (again, was already in an earlier beta version)

antifish said:
If it works, please thest the DB2 Browser (its a new database i got with 45000+ codes, had not the time to correctly sort and implement it yet).
Not at the moment, tell me what you like as layout and try to implement it?
What you can do at the moment is to place a widget on your homescreen for most-used functions, and soon there will be possibilty to create custom layouts (again, was already in an earlier beta version)
Click to expand...
Click to collapse
What i had in mind was a simple remote control skin with most used buttons over it. the rest of the buttons like the numbers, other minimal used functions, etc to be placed in a drawer or pull-down menu.
Anyways, i shall try the new database and get back.
How (or is there one) do i use the TV B-Gone code? can this block all IR frequencies?

francisdsa said:
What i had in mind was a simple remote control skin with most used buttons over it. the rest of the buttons like the numbers, other minimal used functions, etc to be placed in a drawer or pull-down menu.
Anyways, i shall try the new database and get back.
How (or is there one) do i use the TV B-Gone code? can this block all IR frequencies?
Click to expand...
Click to collapse
You will be able to define your layout with only your used buttons in a next version, event the buttons will be very simple (you can arrange, resize, add, delete default android buttons and assing a code).
Maybe i find a good "default" remote layout which i could use, with power, ch+/- etc, just the basic functions.
Yeah you can use the "All-off" function in the navigation menue, it will send all know power keys (the ones other users uploaded, not yet the ones form the new DB)

antifish said:
You will be able to define your layout with only your used buttons in a next version, event the buttons will be very simple (you can arrange, resize, add, delete default android buttons and assing a code).
Maybe i find a good "default" remote layout which i could use, with power, ch+/- etc, just the basic functions.
Yeah you can use the "All-off" function in the navigation menue, it will send all know power keys (the ones other users uploaded, not yet the ones form the new DB)
Click to expand...
Click to collapse
Thanks dude
Maybe this common remote (jpg image) will help you make a simple useful skin
{
"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"
}
OR

Got some confirmations that it works on the S4 and the Galaxy Tab 8.0.
Please check the OT for a download link and use the Thread in the HTC ONE forum for bugs / etc.

help page doesn't open

If I press the settings key on my device an then want to open the help page nothing happens.
I'm using the free version so there are ads shown at the bottom of the device so it might be that the device doesn't know whether I clicked the ad or the help button and just does nothing. (if I click the settings key the settings will open at the bottom of the screen instead of at the top)
At least if I click the settings button on the top right of the screen (3 dots) then the help page will open just fine.

Dj_Fex said:
If I press the settings key on my device an then want to open the help page nothing happens.
I'm using the free version so there are ads shown at the bottom of the device so it might be that the device doesn't know whether I clicked the ad or the help button and just does nothing. (if I click the settings key the settings will open at the bottom of the screen instead of at the top)
At least if I click the settings button on the top right of the screen (3 dots) then the help page will open just fine.
Click to expand...
Click to collapse
This might be device and ROM specific, as this is typically handled by the system. Have you asked on the support forum for your ROM?

No I haven't asked in the ROM Forum, yet.
I'm using the Carbon ROM for my Sony Ericsson Xperia Arc S.
I'm not using the current version right now but I'm planning to update soon.
The ROM is kinda based on Cynogenmod or at least has a lot of features from it.
I'm not sure what I should post in the thread because it only happens in this app.
And it's not like I cannot access the help. It's just that pressing help in the list doesn't do anything if the list appears at the bottom of the screen.
Every other button in the list works fine.
I have tested it on another device as well:
Samsung Galaxy S1
Mackay Rom (Cyanogenmod+device specific tweaks)
Same behavior so I don't think it is ROM specific
if I deactivate my wifi then there is no ad at the bottom of the screen but the help window still doesn't appear if I press help
Are you able to reproduce this issue?
Do I need to upload screenshots to get better across what I'm talking about?

Screenshots would be helpful!
@bleu8888 please take a look.

Ok here as promised the screenshots:
1. pressing the menu key of the device:
{
"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"
}
2. pressing the menu button of the interface:
The first way doesn't allow me to access the help page/window, but the second does.
Weird...
Hopefully you can reproduce this issue and find a solution :good: :victory:
EDIT: by "only gray background" I mean: the only thing that indicates that the button is pressed is that the background of "help/Hilfe" turns into a darker gray

Dj_Fex said:
Ok here as promised the screenshots:
1. pressing the menu key of the device:
2. pressing the menu button of the interface:
The first way doesn't allow me to access the help page/window, but the second does.
Weird...
Hopefully you can reproduce this issue and find a solution :good: :victory:
EDIT: by "only gray background" I mean: the only thing that indicates that the button is pressed is that the background of "help/Hilfe" turns into a darker gray
Click to expand...
Click to collapse
I can't reproduce the issue in my S5.
Can you give the details of your device ingo like manufacturer, model, Android Version & Custom Rom details if your not in stock.
If it possible can you collect the logs immediately after problem?
(Can be collected with mx log collector by opening immediately after the problem.)

ktsamy said:
I can't reproduce the issue in my S5.
Can you give the details of your device ingo like manufacturer, model, Android Version & Custom Rom details if your not in stock.
If it possible can you collect the logs immediately after problem?
(Can be collected with mx log collector by opening immediately after the problem.)
Click to expand...
Click to collapse
This:
Dj_Fex said:
No I haven't asked in the ROM Forum, yet.
I'm using the Carbon ROM for my Sony Ericsson Xperia Arc S.
I'm not using the current version right now but I'm planning to update soon.
The ROM is kinda based on Cynogenmod or at least has a lot of features from it.
I'm not sure what I should post in the thread because it only happens in this app.
And it's not like I cannot access the help. It's just that pressing help in the list doesn't do anything if the list appears at the bottom of the screen.
Every other button in the list works fine.
I have tested it on another device as well:
Samsung Galaxy S1
Mackay Rom (Cyanogenmod+device specific tweaks)
Same behavior so I don't think it is ROM specific
if I deactivate my wifi then there is no ad at the bottom of the screen but the help window still doesn't appear if I press help
Are you able to reproduce this issue?
Do I need to upload screenshots to get better across what I'm talking about?
Click to expand...
Click to collapse

@ktsamy what are you trying to show with that screenshot?
it doesn't show the help page (What's new? Features etc.)
Content of the E-Mail that the MX Log Collector generates (without the "how to reproduce" part)
Code:
=========================
Hersteller: SEMC
Modell: Xperia Arc S
Marke: SEMC
Version: 4.4.2 (REL)
Build: SEMC/LT18i_1254-2184/LT18i:4.0.4/4.1.B.0.587/tL1_3w:user/release-keys
Kernel: Linux version 3.4.82-nAa+ ([email protected]) (gcc version 4.7 (GCC) ) #1 PREEMPT Wed Apr 23 11:08:33 EDT 2014
CPU: 1 core(s) 1,4 GHz (family:1 features:63)
CPU-Architektur: 7
CPU-Merkmale: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls
Board-Plattform: msm7x30
Befehlssatz: armeabi-v7a (+armeabi)
Auflösung: 480 x 854
Verfügbare Bildschirmgröße (DIP): 320 x 544 (smallest: 320)
Tablet: false
Bildschirmgröße: Normal
Dichte: 1.5 (240)
Schriftgröße: 1.0
Haupt-Hardwaretaste: true
Gebietsschema: de_DE
Speicherkapazität: 376112 kB
Verfügbarer Speicher: 7968 kB
=========================
See attachments for log, app settings and build.prop

something I noticed in the log which might be interesting as well:
Code:
06-30 15:09:34.407 18644 18644 I Ads : Received log message: <"string": "<Google:HTML> You are using version 6.4.1 of the AdMob SDK which is non-compliant with the Google Play Ad Policy (http://goo.gl/6OZelH). On August 1st, 2014, Google Play will stop accepting updates to apps using this SDK. Upgrade to Google Play services now to avoid this deadline.", "afmaNotifyDt": "null">
it has nothing to do with this issue/thread but you won't be able to send updates to the Play Store after August 1st.

Dj_Fex said:
@ktsamy what are you trying to show with that screenshot?
it doesn't show the help page (What's new? Features etc.)
Click to expand...
Click to collapse
What I wanted to say was I am getting menu the items only on the top right corner even with the harware button.
That's why I have asked you to post the logs. So that the developer can identify the problem.
By the way, I have managed to produce the menu at the bottom using hardware keys on my friend's mobile. But, still I can't reproduce the problem. The help menu opens normally without any problem.
@bleu8888
Can you look at the logs submitted?

Dj_Fex said:
If I press the settings key on my device an then want to open the help page nothing happens.
I'm using the free version so there are ads shown at the bottom of the device so it might be that the device doesn't know whether I clicked the ad or the help button and just does nothing. (if I click the settings key the settings will open at the bottom of the screen instead of at the top)
At least if I click the settings button on the top right of the screen (3 dots) then the help page will open just fine.
Click to expand...
Click to collapse
Hi,
Sorry for late reply. Here is my analysis;
First, MX Player does nothing to open Menu but just send a simple .xml file to API describing menu entity, such as text to be displayed, command id to be received when menu is selected, keyboard shortcut and that's it, no coding involves here. So if it is placed on the bottom side, it is the Android system which places the menu on the bottom side.
Second, About screen is actually a web page just like ad banner image. Advertisement module is made by ad.network companies such as Google, InMobi, etc.
I don't think I and they did exactly same mistake on displaying web page.
It is defintely issue of your ROM.
Thanks.

Just updated my ROM and tested it again today. It is still the Carbon ROM, but they have fixed it now:
the menu is shown at the top of the screen now and the help window opens.
Thanks for your support though. It's a really great app and the best working video player I know for Android.
The only player I could think of that might get better in the future is VLC because they have a lot of knowledge and working, highly-optimized code and codecs. But right now VLC is still beta and has some issues to it and I will stick to MX as long as possible

[APP][Material] Screen Shift - Update - Per-app Profiles

Screen Shift
Change the screen resolution, density and overscan of your Android device
Update v2.0 : Switch profiles automatically based on current app!
{
"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"
}
Test your apps in a variety of screen resolutions using a single device
Improve gaming performance by playing at lower resolutions
Material design interface
In-built profiles of popular devices; more can be added manually
Per-app profiles - Switch profiles automatically based on current app
_
Requirements
Android Gingerbread or higher
Requires root in JellyBean 4.3 and higher
Overscan available only in JellyBean 4.3 and higher
_
Screenshots
_
Downloads
All features of the app are available for free, without any ads. If this app has been helpful, there's an option to donate via an in-app purchase. This does NOT unlock any new features. Thank you for your support.
Please do not mirror without permission. Link to this thread or play store page if you want to share this app elsewhere. So that users will know where to check for updates and get support from.
_
Important Information
A nandroid/Ti backup is recommended before trying the app.
Some devices/ROMs face a soft reboot when density is changed. There's a test in the app to check this. If density change indeed causes reboot, density is ignored in per-app profiles.
If your screen becomes unusable after setting a resolution, wait for ~15 seconds. It should revert to your default resolution.
If that does not work, reboot -> wait for 2 min (for the service to start) -> reboot again -> wait for service to start.
If that too does not work (I certainly hope that you won't have to do this), issue the following commands in adb shell (using a pc):
For JB 4.3 and above:​
Code:
wm size reset
wm density reset
wm overscan reset
Below JB 4.3:​
Code:
am display-size reset
am display-density reset
Also please note that uninstalling the app won't restore default display settings. So please switch the service off first, if you want to uninstall. Also tell me why you uninstalled it.
_
Source code
Source code is distributed under Apache v2 license. Source repository: https://github.com/aravindsagar/ScreenShift
_
Change log
v2.0: Per-app profiles
v1.2: App startup reboot fix
_
Developed by
Aravind Sagar
Find me in G+​

Thank you all for the amazing response! 10000 downloads at the end of 1 week! (XDA + bitly link)
Thanks to XDA Portal and Phone Arena, and other tech blogs, for featuring the app. It means a lot, to get this kind of exposure for one of the first apps of mine.
A bit of background
I have a Nexus 4, and it's display started to develop problems a few months back. The nav bar area stopped registering touches at all (though ghost-touches were experienced quite frequently). I managed with pie controls and similar apps for a while. But more recently, this area began to increase, and almost 50% of my screen doesn't respond to touch now. I was looking for a software solution to make the phone usable till I can replace the digitizer and screen of my phone. Then I stumbled upon an adb shell command, wm, which could do a temporary fix for my touch screen issues. I thought I'd make a GUI for the functionality offered by the wm command, and the end result is what you see in this thread.
What Next?
I'm planning to implement per-app profiles, and automatic density calculation for the next major version of the app.
Suggestions are welcome.
Some credits
https://github.com/matrixxun/ProductTour for the initial tutorial/product tour shown in the app.
http://romannurik.github.io/AndroidAssetStudio/ has been of great help as well.
As always, big thanks to the stack overflow community, as well as http://developer.android.com/index.html

This is great! Could it work on Lollipop and Android M?

Piereligio said:
This is great! Could it work on Lollipop and Android M?
Click to expand...
Click to collapse
It does work in Lollipop. You can see that the screenshots are in fact taken in 5.1 Lollipop.
It should work with M too. I don't have a device to check that right now. Maybe I'll test it out in M emulator as soon as possible.

great app, helpful for me!

thedimzone said:
great app, helpful for me!
Click to expand...
Click to collapse
Thank you!

forgive my ignorance but is this just an easy way to change the (or what was) "ro.sf.lcd_density=XX" in the build.prop or is there something special to this? I realize there's more to it vs the build.prop edit, but it does kinda/sorta the same type of thing? not discrediting the feature...Just curious Thanks again!

tucstwo said:
forgive my ignorance but is this just an easy way to change the (or what was) "ro.sf.lcd_density=XX" in the build.prop or is there something special to this? I realize there's more to it vs the build.prop edit, but it does kinda/sorta the same type of thing? not discrediting the feature...Just curious Thanks again!
Click to expand...
Click to collapse
Actually, it's an easy way to issue the adb command wm (or am before JB 4.3).
Check this SO question for more details on wm command: http://stackoverflow.com/questions/18500611/android-how-to-use-adb-shell-wm-to-simulate-other-devices.
I started building this app because parts of my screen stopped working, actually. Then I thought, it could be useful more generally.

@aravindsagar how can i get back to default settings?

thahim said:
@aravindsagar how can i get back to default settings?
Click to expand...
Click to collapse
Just switch the service off using the switch in action bar. If your display has somehow become unusable, follow instructions in OP, under the heading "Important Information". If you have uninstalled the app, resetting can be done using the adb commands mentioned there.

First of all, Avast Mobile Security detects your app as suspicious and advises uninstalling it immediately. I hope there are no malwares
Btw, about the app, as soon as I gave it root access, my device hot-rebooted and got stuck in a bootloop. Then I switched it off and restarted it, device started optimizing all the apps (just like after fresh rom install). Everytime I open the app my device reboots
Device - Note 2 N7100
ROM - CM12.1

tj_droid said:
First of all, Avast Mobile Security detects your app as suspicious and advises uninstalling it immediately. I hope there are no malwares
Btw, about the app, as soon as I gave it root access, my device hot-rebooted and got stuck in a bootloop. Then I switched it off and restarted it, device started optimizing all the apps (just like after fresh rom install). Everytime I open the app my device reboots
Device - Note 2 N7100
ROM - CM12.1
Click to expand...
Click to collapse
Um that's bad. Well, you are free to examine the source if there's any doubt. It could be because app requests root, or permission to get to know call state changes, so that when a call comes, display can be adjusted to default resolution (this behavior can be configured in settings).
As for the hot-reboot, I wonder what the problem is... Can you uninstall the app and try issuing these commands directly using adb, and see whether reboot happens then?
Code:
wm size WIDTHxHEIGHT
wm overscan LEFT,TOP,RIGHT,BOTTOM
wm density DENSITY
Replace the Upper caps words with required values.

aravindsagar said:
.
Click to expand...
Click to collapse
Please add Russian language

pavik62 said:
Please add Russian language
Click to expand...
Click to collapse
Hey thanks for that! I'll definitely add this. Meanwhile, there are still some hard-coded strings in the app (like button texts etc), which I'll move to strings.xml, and update the project soon. Will it be asking too much to provide translations for those as well?

aravindsagar said:
Hey thanks for that! I'll definitely add this. Meanwhile, there are still some hard-coded strings in the app (like button texts etc), which I'll move to strings.xml, and update the project soon. Will it be asking too much to provide translations for those as well?
Click to expand...
Click to collapse
I'd be in for german translation

T.E.C.H.N.O said:
I'd be in for german translation
Click to expand...
Click to collapse
Awesome! I'll post here as soon as I update strings.xml.

aravindsagar said:
Awesome! I'll post here as soon as I update strings.xml.
Click to expand...
Click to collapse
Great, when this will be?

T.E.C.H.N.O said:
Great, when this will be?
Click to expand...
Click to collapse
I'm having some work right now, but I should be able to do this after a few hours. Maybe in 4-5 hours I'll update the source.

aravindsagar said:
I'm having some work right now, but I should be able to do this after a few hours. Maybe in 4-5 hours I'll update the source.
Click to expand...
Click to collapse
Ok thanks I'll stay tuned

Hello
This app is amazing, on my lg g3 works like a charm. But on my Xperia P doesn't work.
My xperia P is. 540x960 and I tried 480x800 works but i have the following problem on the pictures. How can i solve it? My screen is reduced.
Thanks for ur attention.

[MOD] DAB+ App for Klyde module (serial, rear, not USB) - reworked

Update 2021-05-14:
A new version, a bit of cross-promotion for annother variant (USB DAB modules) - and some interesting new insights ...
I have managed to build a new app with the same UI concept, but this time for USB DAB receivers. I know there is already the excellent DAB-Z, and I want in no way compete with it.
I just like simplicity; that's why I transferred the UI part of the "old" app to the one for USB.
In the process, I also added some improvements to this one, so there is a version "2.0.0" now.
To help with future updates and statistics, I published it on Google Play:
DAB+ Radio for Klyde Headunit - Apps on Google Play
Control serial DAB+ module by Klyde - only for special hardware, NOT for USB !!
play.google.com
Changes included against the old version here:
- Some UI changes, nothing fundamental
- Now up to three text chunks are displayed, eliminating the frequent change
- Station lists are ordered alphabetically
We are MONO !!
At some point I realized that there was definitely no Stereo audio when listening on the DAB+ app. First I suspected misconfiguration, maybe the wrong MCU firmware. However there were no changes, whatever I tried. What's suspicious though is that there is signal on both speakers. That implies that the distribution to both channels must be done deliberately at some point, else only one speaker would get a signal.
Anyway, for the new development, I pulled the headunit out of the car and set it on my desk. This allowed me to run hands-on experiments. And voilà: I managed to stick some thin cables into the output plug of the module - and got regular Stereo sound out of it immediately!
It turned out the cable of one of those channels was CUT right before the HU plug !!!
It seems that there was a lack of pins in that plug/socket, so only one channel goes into the HU and is obviously routed to both speakers internally ...
<To be continued >
----------------------------
Original post:
With my new headunit (PX5 Oreo from Autojeta, based on Klyde KD-7602), I had ordered an external DAB+ module which is connected with a proprietary cable to the rear socket panel. It has a serial control connection, power and likely a TOS audio wire.
The app for operating the module which was offered for download is incomplete, to say the least. Presets weren't working at all, it was not even possible to save any.
So I did a bit of re-engineering and built a DAB+ controller how I imagined it.
{
"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"
}
Changes against the original:
- Many, total rewrite
- Infotext is complete (the last character was always missing before)
- New layout, eye- and finger-friendly
- No more ugly images and buttons
- Plenty of room for long infotexts
- Presets are working
- Setup window for less-used options
- Unnecessary permissions and resources removed
- German translation included
Update 2019-01-30:
- extended compatibility down to Android KitKat (4.4)
- empty preset entries can be clicked anywhere to set; no need to hit the edit button
- attempt to make layout independent from resolution
If anybody is interested, I can provide the "strings" files so that more translations are possible.
Enjoy!
Current version: 1.2 (obsolete, see 2.0.x on Google Play)

JFDee said:
With my new headunit (PX5 Oreo from Autojeta), I had ordered an external DAB+ module which is connected with a proprietary cable to the rear socket panel. It has a serial control connection, power and likely a TOS audio wire.
The app for operating the module which was offered for download is incomplete, to say the least. Presets weren't working at all, it was not even possible to save any.
So I did a bit of re-engineering and built a DAB+ controller how I imagined it.
View attachment 4657027
Changes against the original:
- Many, total rewrite
- Infotext is complete (the last character was always missing before)
- New layout, eye- and finger-friendly
- No more ugly images and buttons
- Plenty of room for long infotexts
- Presets are working
- Setup window for less-used options
- Unnecessary permissions and resources removed
- German translation included
If anybody is interested, I can provide the "strings" files so that more translations are possible.
Enjoy!
Download: View attachment 4657026
.
Click to expand...
Click to collapse
Great work, plays nice

JFDee said:
With my new headunit (PX5 Oreo from Autojeta), I had ordered an external DAB+ module which is connected with a proprietary cable to the rear socket panel. It has a serial control connection, power and likely a TOS audio wire.
The app for operating the module which was offered for download is incomplete, to say the least. Presets weren't working at all, it was not even possible to save any.
So I did a bit of re-engineering and built a DAB+ controller how I imagined it.
View attachment 4657027
Changes against the original:
- Many, total rewrite
- Infotext is complete (the last character was always missing before)
- New layout, eye- and finger-friendly
- No more ugly images and buttons
- Plenty of room for long infotexts
- Presets are working
- Setup window for less-used options
- Unnecessary permissions and resources removed
- German translation included
If anybody is interested, I can provide the "strings" files so that more translations are possible.
Enjoy!
Download: View attachment 4657026
.
Click to expand...
Click to collapse
Nice work. It is compatible also with the USB receiver version ?

royalhawk2002 said:
Nice work. It is compatible also with the USB receiver version ?
Click to expand...
Click to collapse
No, I don't have such a device.
This version is hard-wired to use /dev/ttyV3, a serial port that is related to the firmware. It will only communicate if "com.microntek.CarManager" is instantiated in the Java code.
I suspect that the USB version may be very similar though. Can you point to an app that DOES work with it? I could have a look.
.

@JFDee
It seems well done, congratulations!
can you enter the link to buy that form dab?
* I do not want to occupy my usb sockets.
P.S. does anyone know a dab module that fuses with an external antenna and has better reception?
* because with the internal adhesive antenna I do not feel well, in fact I have mounted it on a truck and often happens to have to replace the glass, due to small scratches, which would not allow to pass the review ... with the adhesive antenna I would have to replace the antenna every time ... for now I stuck it with transparent scotch but it is quite disgusting and also the reception is poor.

JFDee said:
No, I don't have such a device.
This version is hard-wired to use /dev/ttyV3, a serial port that is related to the firmware. It will only communicate if "com.microntek.CarManager" is instantiated in the Java code.
I suspect that the USB version may be very similar though. Can you point to an app that DOES work with it? I could have a look.
.
Click to expand...
Click to collapse
you can take a look to dab-z from realzouzu...here on the forum
Inviato dal mio SM-N960F utilizzando Tapatalk

fur0n said:
can you enter the link to buy that form dab?
* I do not want to occupy my usb sockets.
Click to expand...
Click to collapse
Here are two links:
https://www.aliexpress.com/item/KLY...ouch-Control-For-Android-6-0/32848949738.html
https://www.aliexpress.com/item/Ext...l-For-Android-Car-DVD-Player/32826477767.html
However, you need the matching socket at the rear of the HU. On the photo, it's the 6-pin socket below the hole named IPOD.
.
.

Great job; finally klyde dab work very good...
if you could add station logos it would be great

pakoner said:
if you could add station logos it would be great
Click to expand...
Click to collapse
I can't say if the DAB+ module can provide these. It's basically a "black box" that accepts serial control commands and returns station parameters and infotext updates. The sound seems to come out as a digital stream over some of the cables in the proprietary connector.
So far, I'm using the unchanged control commands from the original program because there is no documentation of what they do. It's obvious which ones start the station scan or change the station, but there may be others that provide further functions.
The module inside the housing is a shielded circuit, which I suspect can be found in many car and stationary radios. It says SHINWA on the shield.
Edit: This is the module in the box:
http://www.shinwa.com.cn/product/meBroadcast/backdab/DB-MF03.html
I'm sure the documentation of the commands is available for purchase ...
.

Parsing Problems
Thanks for your work,but I can't install your dab. apk.file.Message is : parsing problem .I have a mtcb unit with the latest malaysk Android rk3188 4.4.4 800x480 rom.At the moment,i have the same DAB + reciever like you,working with the redesigned dab+ app of Oberbergler.Any idea?

Strike03 said:
apk.file.Message is : parsing problem .I have a mtcb unit with the latest malaysk Android rk3188 4.4.4 800x480 rom.
Click to expand...
Click to collapse
I only tested with Android 8 here. I will test again in an emulator with Android 4.4.

JFDee said:
I only tested with Android 8 here. I will test again in an emulator with Android 4.4.
Click to expand...
Click to collapse
This would be very kind,thank you.I hate the normal interface and your one looks very good.

JFDee said:
Here are two links:
https://www.aliexpress.com/item/KLY...ouch-Control-For-Android-6-0/32848949738.html
https://www.aliexpress.com/item/Ext...l-For-Android-Car-DVD-Player/32826477767.html
However, you need the matching socket at the rear of the HU. On the photo, it's the 6-pin socket below the hole named IPOD.
.
View attachment 4661961
.
Click to expand...
Click to collapse
M8 great work you did here.
I own a pumpkin 8core android 8 mtcd KLD so i suppose it's same klyde like yours and then the rear serial interface must work right?
Lol I will not tell anything if it doesn't work but seems to me it will work... I attach a rear image of Myne where i see that plug

BlueChris said:
I own a pumpkin 8core android 8 mtcd KLD so i suppose it's same klyde like yours and then the rear serial interface must work right?
Click to expand...
Click to collapse
I don't see why it shouldn't. The hardware layout looks identical.
The app also works fine with Hal9k.

Strike03 said:
Thanks for your work,but I can't install your dab. apk.file.Message is : parsing problem .I have a mtcb unit with the latest malaysk Android rk3188 4.4.4 800x480 rom.
Click to expand...
Click to collapse
The app was definitely not compatible with KitKat. I have changed that so it should at least install and open.
I'm not sure it will fully work as I can test for Kitkat only on an emulator. Also, I did not check the layout for issues on 800x480 yet.
If you get any layout distortion, it would be helpful if you could post a screenshot.
Edit: just did annother update after streamlining and testing the layout on 800x480.
See top post for the update.
.

JFDee said:
The app was definitely not compatible with KitKat. I have changed that so it should at least install and open.
I'm not sure it will fully work as I can test for Kitkat only on an emulator. Also, I did not check the layout for issues on 800x480 yet.
If you get any layout distortion, it would be helpful if you could post a screenshot.
Edit: just did annother update after streamlining and testing the layout on 800x480.
See top post for the update.
.
Click to expand...
Click to collapse
Thank you very much for your work.
Installing was no problem with your updated app and layout with 800x480 looks very good. But it´s stuck in initialization mode.If i press a button, nothing happens or it shuts down.
https://www.bilder-upload.eu/bild-b1849c-1548867502.jpg.html
https://www.bilder-upload.eu/bild-2c1fe9-1548868034.jpg.html

Strike03 said:
it´s stuck in initialization mode.If i press a button, nothing happens or it shuts down.
Click to expand...
Click to collapse
The hardware setup is probably different from the one used in the MTCD version.
Do you have an "official" app that works, at least with selecting channels?

JFDee said:
The hardware setup is probably different from the one used in the MTCD version.
Do you have an "official" app that works, at least with selecting channels?
Click to expand...
Click to collapse
I use the app of Oberbergler and in former times the one of treibstoff. Both work, but the layout of your one looks better.
Here is the link of the mtcb software section with the working dab APP 1.5 Modded apk.You have written there about your new designed app some days ago.
https://forum.xda-developers.com/an...development/klyde-dab-app-1-5-modded-t3484902

Strike03 said:
Here is the link of the mtcb software section with the working dab APP 1.5 Modded apk.
Click to expand...
Click to collapse
Thanks, got it. The appearance of the original ('official') app seems to be identical to mine, but something inside must be different.
I will reverse engineer that app. Please stand by ...
.

JFDee said:
I will reverse engineer that app. Please stand by ...
.
Click to expand...
Click to collapse
Ok:good:

[PX5][How To] Finally possible to change CANBUS Keys in Android 9

Hi there,
just wanted to let you know, that Android 9 (August version or newer is needed) has an option included within the advanced settings (to access with password 126) to be able to change all CANBUS keys via the steering wheel assign app.
Go to the advanced settings -> other -> steering wheel keys assign and select "Can Key" there.
After that change, you can use the already known and included steering wheel key assign app to assign short an long press actions to each key.
Please be aware, that after changing that setting, you MUST assign all keys you'd like to use as none of the standard assignments will be left.
{
"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"
}
Best whishes,
Christian

gforums said:
Hi there,
just wanted to let you know, that Android 9 (August version or newer is needed) has an option included within the advanced settings (to access with password 126) to be able to change all CANBUS keys via the steering wheel assign app.
Go to the advanced settings -> other -> steering wheel keys assign and select "Can Key" there.
After that change, you can use the already known and included steering wheel key assign app to assign short an long press actions to each key.
Please be aware, that after changing that setting, you MUST assign all keys you'd like to use as none of the standard assignments will be left.
Best whishes,
Christian
Click to expand...
Click to collapse
It seems, you got a Citroen C4 II too. Do you also got a "MX" MCU version?
With my new DS5, I noticed that keys can no longer be assigned if I have assigned a certain number of keys.

retromann said:
It seems, you got a Citroen C4 II too. Do you also got a "MX" MCU version?
With my new DS5, I noticed that keys can no longer be assigned if I have assigned a certain number of keys.
Click to expand...
Click to collapse
Indeed I own a C4 II, have MX MCU Version 3.30 installed.
How many keys could you assign? I didn't fully complete my setup yet, but I already have assigned roughly 10 keys with no issues.
Will try finishing tomorrow.
-Christian

Hello
I have an android 9 - MTCE_MX_V3.30_1 (opel Astra J)
I can assign up to 20 buttons.
Unfortunately, this is not enough, so I left the default settings

I was able to assign 23 buttons but I have to agree - with that limitation, tue function won't make happy all of us.
I wonder where the assigned keys are stored and whether it could be possible to modify that file directly. Or have a mofidied steering wheel key apk without those limitations.
So if anyone gets some deeper insights here, please share with us.
thanks,
Christian

Guys I don't understand. Why are 23 buttons to assign not enough? How many buttons do you have on the steering wheel?

matrixx1 said:
Guys I don't understand. Why are 23 buttons to assign not enough? How many buttons do you have on the steering wheel?
Click to expand...
Click to collapse
other than the app name is indicating, we can use this app to assign ALL can bus keys, not only the ones on the steering while.
Our radios do not have any hardware buttons but the original car buttons are used.
I agree that assigning 23 of them should be fine in most cases - but my C4 II also has more than 23 physical buttons.
I don't know how deodexing in android 9 is working. we have vdex + odex files. Would like to see how the app is working or where the assigned keys are beeing stored.
anyone has an idea?
Additionally, I have troubles assigning my volume knob. It's nearly impossible to get the steering wheel app to recognize a "short press" when turning the volume wheel.
Despite that, I am happy with the functionality.

I deodexed the HCTWheelStudy app and was able to decompile inkl. smali code files, but I can't find a limitation on how many keys can be assigned.
Furthermore I wonder where the assigned keys are stored - any idea? I hoped to find a path or some files in der user data of wheelstudy or canbus app, but I didn't get further.
Hope someone will soon get deeper into canbus keys in Android 9.

gforums said:
I deodexed the HCTWheelStudy app and was able to decompile inkl. smali code files, but I can't find a limitation on how many keys can be assigned.
Furthermore I wonder where the assigned keys are stored - any idea? I hoped to find a path or some files in der user data of wheelstudy or canbus app, but I didn't get further.
Hope someone will soon get deeper into canbus keys in Android 9.
Click to expand...
Click to collapse
Probably stored in MCU and/or canbus controller if separate to headunit.

oxygen2222 said:
Hello
I have an android 9 - MTCE_MX_V3.30_1 (opel Astra J)
I can assign up to 20 buttons.
Unfortunately, this is not enough, so I left the default settings
https://imgbb.com/
Click to expand...
Click to collapse
cześć and hello,
was you able to revert back to original assigned keys or did you just not save?
I am currently struggling how to revert back the original key functionality.
I can change the steering wheel app back to control swc keys, but that will keep the functionality I programmed to the canbus keys.
Might reflashing the MCU file help?
Best whishes,
Christian

I changed "Can Key" and pressed the reset button.

gforums said:
I deodexed the HCTWheelStudy app and was able to decompile inkl. smali code files, but I can't find a limitation on how many keys can be assigned.
Furthermore I wonder where the assigned keys are stored - any idea? I hoped to find a path or some files in der user data of wheelstudy or canbus app, but I didn't get further.
Hope someone will soon get deeper into canbus keys in Android 9.
Click to expand...
Click to collapse
Hello.
I am developer of "MyMTCService" -> https://play.google.com/store/apps/details?id=rabbity.com.service
Can i know how to deodex the apk in android 9.
Because I need to decompile MTC moudules for developer of "MyMTCService".
Thanks.

rabbity417 said:
Hello.
I am developer of "MyMTCService" -> https://play.google.com/store/apps/details?id=rabbity.com.service
Can i know how to deodex the apk in android 9.
Because I need to decompile MTC moudules for developer of "MyMTCService".
Thanks.
Click to expand...
Click to collapse
Hi,
This is what I made in short:
* Took system.new.dat.br from room, convertet to normal system.new.dat with brotli.exe tool
* Unpacked system.new.dat (together with system.new.patch and system.new.files I think) with one of the Android Unpacking Tools
* Used TOAD Tool from XDA to deodex the apps and framework.
But not all apps, especially most in priv-app could get deodexed.
BR Christian

gforums said:
Hi,
This is what I made in short:
* Took system.new.dat.br from room, convertet to normal system.new.dat with brotli.exe tool
* Unpacked system.new.dat (together with system.new.patch and system.new.files I think) with one of the Android Unpacking Tools
* Used TOAD Tool from XDA to deodex the apps and framework.
But not all apps, especially most in priv-app could get deodexed.
BR Christian
Click to expand...
Click to collapse
thanks, I will try it.

gforums said:
Hi there,
just wanted to let you know, that Android 9 (August version or newer is needed) has an option included within the advanced settings (to access with password 126) to be able to change all CANBUS keys via the steering wheel assign app.
Go to the advanced settings -> other -> steering wheel keys assign and select "Can Key" there.
After that change, you can use the already known and included steering wheel key assign app to assign short an long press actions to each key.
Please be aware, that after changing that setting, you MUST assign all keys you'd like to use as none of the standard assignments will be left.
Best whishes,
Christian
Click to expand...
Click to collapse
thank you! I was frustrated, but i changed a button to play/pause but it is working as "next song button", any ideas about that?

hey guys. I own a px6 unit for peugeot 207 with decoder.
I want to ask If I will able to edit the can bus messages / information - font or layout - design - color - e.t.c.
Also I want to change the text of the messages and translate it to greek.
Is that doable?

This worked for me. After selecting can key in the settings the “ steering wheel key assign app” appeared in my apps list. Was able to assign the keys and tested it working on stock and 3rd party apps.
Perfect. Thank you.

Guys on Android 10, the only options I get are enable and disable. No Can key option. I dont have the stereo in the car atm and i dont have the canbus box connected either. Could this be the issue?
EDIT: Fixed. I just had to update the MCU.

Hey there, long time lurker first time poster...
Has anyone been able to solve the 23 button re-mapping limit? I’ve got more than 23 buttons across my dash and they need re-mapping!