Hello,
I´m searching for a way to be able to use the T-Mobile myWallet NFC Payment with paranoid-android Rom (togari).
I´ve analyzed the logfiles and noticed that there is a libary missing...
Unfortunately the simalliance openmobile api for NFC sims is not included in paranoid android.
Any Idea how to get that stuff to work?
Related
hello guys. im currently looking for a solution to light my official rom. i've used the "desamsungnizer" (script) wich deletes almost every samsung stuff in the phone. But since i did that my mobile is not being recognized as online in the samsung find my mobile website. so i flashed the rom again to see wich modules are the one that controls that especific funtionality.
So in the running apps by the apps manager i i've seen this ones in ejecution wile i was tracking my phone.
1- XDM service - com.wssyncmldm
2- Smartcardservice - org.simalliance.openmobileapi.service:remote
3 - Remote Controls - XDMservice - com.fmm.dm
But seems like there is no apks with that name in the system. so does any of you guys knows wich apk modules controls the phone tracking?
Hi,
any experienced Developers out there with RTSP or other Streaming Protocol knowledge?
Hoping to get some insight in this field.
I am currently in the process of having an App developed, that will connect to the WiFi network of a camera, which has a WiFi module built in.
You could say it is similar to GoPro's App, as it includes functions such as remote controlling the camera (record/stop), switching between 4 recording modes, as well as reviewing the footage of the camera directly on the phone through the App.
On top of that, the App live-streams while the camera is recording, using RTSP.
How hard is it to maintain the App to constantly be compatible with the latest Android version? Are there fundamental parts of the code that would need to be changed from Android 4.3 to 4.4.2 for example?
First of all, forgive me if this is not the right forum to ask this question, because I'm not sure what is.
Hi everyone,
So the company that provides the TV channels in my country (like the cable companies in the US) has a streaming service that streams most of these channels online to phones, tablets, computers.
The problem is that their app is, according to them "not supported on hacked devices". Just so we're clear, we're talking about Android here, and hacked = root/custom rom, which this stupid company considers illegal. In some devices, they check both root and custom rom, in some only one of them, and in some the app will work even if you have both. For example, on my Nexus 4 the app worked with stock rom that was rooted. Now that I am running a custom rom, trying to hide root using various apps does not work. So obviously the problem, with my device at least, is running the custom rom.
I'm currently learning Java & Android development and have decided to use the little knowledge that I have to try to find the lines of code responsible for this idiotic check.
I looked up many tools for decompiling apps and have finally found a good one, called JadX.
http://androidcracking.blogspot.co.i...ler.html#links
This decompiler is excellent, but gives me a scary amount of code files to look. Even so, trying to search all of them (JadX has that functionality) for the code that checks for root/custom rom has turned up nothing. I have also tried to search for the message they give me when I open the app (about hacked devices not working) but I found nothing, again.
One more thing - a developer that also tried to solve this problem said he traced the problem back to DxDrmDlcCore. I searched it, found it a some class, but not sure what to do now (delete the entire class and recompile?)
Can someone here direct me towards what I need to be looking for?
OR
Is the solution really simple, such as editing my build.prop? Someone suggested it once, but did not know what lines to edit.
If someone is ready to step up to the challenge, I can upload the apk.
Thank you!
Want to start some research about this board. I know that JTC uses it in its TV sets, but its probably widely spread among OEM TVs.
To discover firmware I unpacked a update and found a file: CtvUpgrade.bin that starts with a list of partitions that are in its ROM.
Anyone knows more about the format or want to join me here?
Hi.
The board is a cultraview they like to have a custom OS from Zeasn on it.
To be recognized by the launcher cultraview_open_launcher.
This is built into cheap models.
You get to the hidden tv menu through input / source and then 2580.
I myself have a device from kb-elements with cultraview board and custom OS.
Oh, well - good to have a bro here
I could figure our already some thing in the Service Menu (Overscan, Reduce backlight further more).
But sill I just have quite a few questions:
Does your board allow record broadcast?
Could you get rid of the annoying "Energy waste" pop-ups if you increase volume?
Did you get root access to it?
A german bro.
No root is only possible with a root OS version which then has to be flashed Via USB.
This will void the guarantee.
Especially since at least for me it is an OS adapted by Zeasn.
I suspect that JTC is similar to kb-elements.
The file ctvupdate is only firmware for the board.
I would avoid the ctv mode at least when the backlight is deactivated.
Yeah, where are you from? I am not so afraid of guarantie. But I need to know more about. It would be cool to have a real Android, so where all apps will work. Widevine would be cool.
I've seen different update files for same TV with different serial numbers. Guess it is just the different panel. Would be great to separate android from the HW-specific stuff.
Does your TV allows recording?
Lower Saxony.
The cultraview board is often built into cheap devices.
Jtc / Jay tech, TCL, Hisens, KB elements.
Unfortunately, widevine is not on it and the Android is also an adapted "not Google" version.
Playstore ect are installed, if at all, which sometimes leads to problems.
Root access is also not possible. Unless you have an update for the USB stick and modefiert it for root access.
But that is beyond my knowledge.
Yes PVR works, even on a USB stick which sometimes does not work.
If necessary, it could also be activated in the service menu.
For me Playstore isn't working anymore. Although all other apps does have network it complains not to have it.
I manually updated to latest gsf and gms (Service Framework and Playservices for Android 9+) and also to the latest Playstore. I found that I have to install the Playstore for Android TV [8]. Installing the normal one [0] works, but after starting it complains with: This version is not compatible to device.
Nevertheless it keeps non operational with "no network". Help!
I am wondering what can prevent Playstore from working? Is it because of Android TV?
I am pretty sure the Android on this TV is far from perfect, but hey - why no PlayStore. I think once it worked.
I've done a lot of searches and not come up with much on this topic. I have gleaned that currently only GPay and Samsung Pay support nfc Credit/Debit cards on WearOS smartwatches, but neither support NFC emulation of loyalty cards, room keys... etc. Is this a restriction that is programmed into WearOS or has it just not been done?
I'm not a developer. I know some programming basics, but not enough to create an app. I started looking into this because I'm going to disney world soon. Disney adds your disney pass card as part of magic mobile to your Gpay account, but only as an nfc enabled loyalty card. Gpay on WearOS only allows you to use nfc enabled Credit/Debit cards from your watch. It seems the disney pass simply refers to a url that disney then uses to validate your account and reference it for tickets, room key, payment methods...etc. I think if I could emulate the nfc id number/url from my watch it would work.
I thought I might try sideloading a phone app that will emulate nfc cards also, but haven't tried that yet.
Hello! Have you find any?