Database Users

App Discussion: Adding Infrared Remote Capabilities via Audio

Basically, I'd like to get the ball rolling with making a low cost (Free, Open Source would be best) IR Universal Remote application for the Android Platform.
I wrote up this wiki to help establish current info:
Slatedroid Wiki - Adding IR output to Android Devices
Please see the wiki for all the details, but essentially, the hardware involved is trivial. As far as coding, the following needs to be written or ported from other projects:
A GUI to manage the buttons and selection of devices
A parsing function to read info from pre-made remote control code text files
An audio signal/waveform generator
A database to store the information
All of this stuff has been done before, it's just a matter of bringing it all together into one android-based project.
If the project really took off, future development might include:
Support of LIRC, Pronto, CCF, and/or other IR remote file protocols
Integrated controlling of WiFi and Bluetooth devices
A pre-parsed central database stored "on the cloud" for all major devices
Possibly supporting the "learning" of a new device (would need a IR sensor/decoder attached to microphone input)
Feel free to discuss, correct any errors, bounce new ideas around, etc.

With google tv most of plumbing code and the UI will be available, albeit for a small set of machines and via bluetooth. (google remote)

They used to do this actually.
I remember a long time ago, it was with remote software. It would store the IR signals as WAV files recorded via a 3.5mm headphone IR sensor.
I think you could even make one. All you need to receive and send IR signals is a audio recorder/player. Map certain software buttons to each audio file to make a "Remote Controller" type of device".
Edit:
{
"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"
}

Yes, all that info is already in the wiki. It's been done a million times, which makes me wonder why there is no one around with an android version yet.
britoso said:
With google tv most of plumbing code and the UI will be available, albeit for a small set of machines and via bluetooth. (google remote)
Click to expand...
Click to collapse
Google TV will be WiFi controlled though, not IR, right? If the source code for the gui was available, that would be a good start.

Anybody else having NFC tag issues?

I realize mifare tags can't be written with S4, but I should still be able to read the tag and use nfc task launcher or at least nfctaginfo to read the tag. Both apps give the error "these tags are not supported". I'm using tagsfordroid tags btw. The developers have been helpful but still no answers as to why I can't read a tag.

Maybe this article will help...
http://www.androidauthority.com/samsung-galaxy-s4-tectiles-2-198892/
It seems this information is difficult to come by and I hate it when they change a phones tech to the point you have to get new accessories for it. However, they claim it was done to help bring the NFC Galaxy technology into compliance. I just wish they would make it backward compatible as well. Oh well, enjoy buying new tags.

Like OP mentioned, the Mifare Classic tags should still be read-able by the S4, which sports a similar Broadcom controller as the Nexus 4.
For reference sake, what does NXP TagInfo show when you read the Mifare tag? For my Nexus 4 with Broadcom controller it shows the following:
{
"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"
}
However even with the above output, I'm still about to perform (i.e. read) tasks off the Mifare tag with my N4.
Couple questions for troubleshooting:
- Have you just gone ahead and tried to use the tags while ignoring the error messages? It should still work if they are simple tasks such as toggling WiFi or launching a URL
- Which tasks do you think are written on the tag that the S4 cannot perform?

NFC Taginfo won't even read the tag... I get the same error "tag not supported". Yes I have tried to use the tags I programmed with the S3 (simple wifi on/bluetooth off) still same error "tag not supported". Thid is crazy nfc Taginfo should be able to just read a mifare tag.

So it looks like that the NFC tags that you have (same with me) are the MiFare tags that are no longer compatible. tagsfordroid does have the new tags (NTAG203) and it does even say in the product description that the MiFare ones will not work. Unfortunately they are pretty much useless now.

Yea, i found this out the hard way. I had just bought some mifare tags to find out they don't work...oh well.

Sailfish OS On Nokia N9

{
"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"
}
Sailfish OS running on the Nokia N9.
To Install, follow this guide: http://wiki.maemo.org/Sailfish#Installation_Guide
Bugs And Known Issues
No Android capability as of present.
Camera does not work.
Volume buttons do not work.
Accelerometer does not work.
GPS does not work.
Notifications and Gestures rotated 90 degrees clockwise.
You must manually configure you internet access point. Long-press on the AP in Settings to enter your operator's configuration.
Full list available at https://github.com/romu70/sailfish-for-other/issues?q=is:open

metalci melek said:
https://www.youtube.com/watch?v=u5ii7k-OYM8
The community port of Sailfish OS (version 1.0.1.10) running on the Nokia N9.
To Install, follow this: https://wiki.merproject.org/wiki/Nemo/Installing
Replacing the nemo tar.bz2 file with one from here: http://n9.araya.su/images/mic_images/
Click to expand...
Click to collapse
Thanks for your your post. I have an N9 and hope to try this for fun if I ever get the time... My preference would be to port it to my Note 2 which is also collecting dust (currently using Note 3). Sailfish OS has some nice aspects and the fact that it is gnu linux based and handles multitasking in a more native way than android might draw some folks to it. I think it would really fly high on these threads if someone can come up with a decent port to a high end android device. Until then it may be stuck in the doldrums. for awhile...
btw. I find it ironic that we're talking about a port to a device (N9) which does not have its own section on XDA. (please correct me if I'm wrong here!)

Yes it doesnt have its own section

My SIL uses a Nokia N9... will give it a go when I get some free time.

thread updated

I have made a custom android 6.0 port
I'm still working on it. I just finished my high school and am busy with exams. But I hope to have it on by end of this year or early next year. It has lots of bugs as of now. I can't seem to begin fixing the problem no matter how much I tweak. Main issue still remains with the telemetry and hardware drivers. The camera works without flash. The moment you turn on Flash or leave Flash Auto and snap a pic. The moment the flash goes off, the phone will die immediately. Then Bluetooth doesn't work as of now. So you can only share files via a USB connection or through FTP on common network using a File Explorer with such capabilities. The cellular connection just won't work. I don't have the knowledge to build drivers for it to work. I can't get it to work from extracting the drivers from Sailfish Jolla port. Wifi works but let's be honest it's 2.4 GHz only. It works choppy. At times it'll disconnect automatically for no reason at all. But at least it works. It works well for me. Battery drain is one problem that cannot be fixed. A 1650 mAh battery isn't exactly enough even if you run Android 4.4. So it lasts for 4-5 hrs on standby. It's just for fun. I just wanted to see what it was capable of. And I may decide not to complete this project if the bugs can't be fixed.

Toggle NFC with tasker...

I'm not sure if this is the right forum to put this question in so please forgive me and move it where it belongs and I would greatly appreciate it.
I can't find an NFC option in tasker and I'm thinking because maybe since NFC is relatively new, then it might be awhile before we see it in there. Or maybe I'm just blind and overlooking the thing.
What I want tasker to do is turn on NFC when a program named Isis wallet is opened and turn it back off when it is closed. Since this is the only thing I use NFC for, I don't want to drain battery.
If anyone can help me I would appreciate it, but thanks either way.
Later,
M. Walden
Sent from my Samsung Galaxy Note III
with the XDA Android app

mcw801 said:
I'm not sure if this is the right forum to put this question in so please forgive me and move it where it belongs and I would greatly appreciate it.
I can't find an NFC option in tasker and I'm thinking because maybe since NFC is relatively new, then it might be awhile before we see it in there. Or maybe I'm just blind and overlooking the thing.
What I want tasker to do is turn on NFC when a program named Isis wallet is opened and turn it back off when it is closed. Since this is the only thing I use NFC for, I don't want to drain battery.
If anyone can help me I would appreciate it, but thanks either way.
Later,
M. Walden
Sent from my Samsung Galaxy Note III
with the XDA Android app
Click to expand...
Click to collapse
Great idea, after seeing this I wanted to get it setup for myself. You're right, I didn't see a setting within Tasker to control the NFC state, however using the Secure Settings plug in, available in the Play Store I was able to get this working. You will also need to enable System+ within secure settings. Here are some screens of my setup...Tasker allows a lot of different implementations for the same actions so YMMV
{
"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"
}
Task- NFC On
Select Plug - in
Select Configuration
Scroll down to NFC and select, then select the 'NFC on' radial button and save... save Task
New Task- NFC Off, same process for NFC On, just select the 'NFC off' radial button this time and save Task
Set up new Profile for ISIS that will use the NFC on and NFC off tasks... Assuming that your already familiar with Tasker some quick screens should be enough.
I will probably add new Applications to this profile, or change the setup completely should I need to. But this should definitely work for your description.
Sent from my SM-N900V using Tapatalk

All man, thanks so much. I've been searching for a way to do this for awhile now. I really appreciate this. I owe you one.
Later,
M. Walden
Sent from my Samsung Galaxy Note III
with the XDA Android app

Great thread! One minor note on this. Your device must be rooted to set this up since you need to enable system+ within secure settings app

Android / Samsunsg regress

Hi there,
So I have been using N7000 quite a while now - 2 years or so. And I discovered one, very annoying thing about new versions of android - each one seems to be worse in terms of usability and desktop space usage then the previous one...
Lets start with GB roms - there was 5x5 launcher in home screen and 6x5 in app menu + very useful bottom app dock that visible from desktop (home screen) and app screen. Also - each screen had a number that was shown in the bottom, so you knew where you were.
See picture: gb.jpg taken from http://forum.xda-developers.com/showthread.php?t=1424401 here
Next version - ICS has cut some rows of icons in the app menu and completely deleted bottom app dock. And where the hell is screen number gone? Why??
The good thing about ICS was decent performance and quite good battery life. - Actually, the best one so far on n7000
See picture ics.jpg taken from http://forum.xda-developers.com/showthread.php?t=1923817
JellyBean - same story less apps rows, everything seems to have more room for itself but it causes more screens and more swyping gestures. 4x4 in home screen is a joke. Having so big screen and using so little of it is pointless. I do not know what were they thinking designing the layout! And how did they manage to release so bugged software causing all kernel wakelocks destroying our batteries?
And finally - KitKat which follows the same direction - less icons in the screen, more touches to get you where you want.
Now regarding AOKP that everybody seems to love here - there is no support of very 'basic' apps that Samsung offers in stock TW roms:
- fm radio
- video calls via 3g
- s note
I can understand that s-note is the samsung specific app, but video calls and fm radio not being supported in 2014 AOKP KitKat roms is regress...
I recon that the next version of Android will have 1 icon and 1 icon for 1 screen - containing 12 screens.
We are putting ourselves in the custody of trying simplify things which are simple enough. Many other examples would be some of the google apps - Talk regressed to Hangouts, Maps regressed to new maps, and simple search app regressed to google now that everybody hates. And did I mention it takes 1 home screen when you swipe left on several devices?
I do not want be involved in the discussion of every single mistake google / samsung / communicy have made. I just wanted to point that the way, we are being directed is clearly a wrong way ahead!
Roll on
{
"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"
}
Show me what you got!

Wow what an analysis. Yes ur right about everything u have said. Each new version of android shows so low mininum hardware requirement, which is not true because once the rom is released its much bigger in size than the previous one. I would like android to get updates like linux. Each edition getting a parallel update. Newer devices gets the newer edition and older devices should get the update of the edition they are already on.
The best performance my note showed was
Sent from my GT-N7000 using xda app-developers app

To an already brilliant post the only thing missing was this statement based on a razor-sharp mind and an unmatched intellectual spirit.

brilliant post. brilliant analysis. plus there are now more non responsive google. same goes for force closing of apps