Active Topics

 


Reply
Thread Tools
Posts: 54 | Thanked: 6 times | Joined on Jun 2010
#31
it is impossible. they use different frequency and wave.
That's it.
And must build special hardware to do that. Mobile device is No NO No

Last edited by knownothing; 2010-06-07 at 07:37.
 
Posts: 2,225 | Thanked: 3,822 times | Joined on Jun 2010 @ Florida
#32
@ qwerty12: Oooh... Ok. Thanks.

Could the same principle be applied to permanently forcing the daemon to allow enabling of the transmitter? It seems like it would just from what I know, but what I know is not a lot, so perhaps that's just not doable without seriously screwing with the N900.

- Edit -

Heh, I totally had no idea you wrote FMTX Faker, lol. After posting the original part of this post I went off to go look around since it seemed like the appropriate time to go research the matter instead of getting spoon-fed. And then half way through the "How to enable FM transmitter? (Solution in thread)" thread you just come in with a fix. I mean, I've seen your name enough around here while lurking since I got my N900 a month or so ago (and for close to a year, with increasing frequency, as my opinion solidified that I wanted one), that I knew you must be knowledgeable and good, but damn. Of course, maybe that's far less impressive than it seems to me... (to be fair I'm impressed by frals for fMMS and Titan + everyone-else-that-works-on-kernels too...) I have little frame of reference other than how much more or less daunting anything seems to me.

That said though, every wiki page that turned up for "FMTX" (I got only three - I believe I was in the "fremantle" category; perhaps there are others that would turn up if I searched everything else?) had nothing that answered my above question. Currently finishing reading the aforementioned enabling FM transmitter thread, so maybe that will cover it. But if you know an answer to my original question in this post that would be appreciated.

Last edited by Mentalist Traceur; 2010-06-07 at 08:45. Reason: Newfound knowledge courtesy of searching the wiki...
 

The Following User Says Thank You to Mentalist Traceur For This Useful Post:
qwerty12's Avatar
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#33
Originally Posted by Mentalist Traceur View Post
[...]Of course, maybe that's far less impressive than it seems to me... (to be fair I'm impressed by frals for fMMS and Titan + everyone-else-that-works-on-kernels too...) I have little frame of reference other than how much more or less daunting anything seems to me.
What?! You doubted Qwerty the Pimp?! I must get my revenge by coming up with a hack to this problem!

Prerequisite:
fmtxd patched: fmtxd, using http://maemo.org/api_refs/5.0/5.0-fi...5a46afdad43a94, checks to see if you're in a call. So open up /usr/sbin/fmtxd in a hex-editor (I used vi on the tablet itself) and replace "sig_call_state_ind" with "sig_call_sttte_ind". Make sure that the transmitter isn't on whilst doing this and that fmtxd is not running.

1. Install http://talk.maemo.org/showthread.php?t=43395 (the fm_boost variant may be better, depends) (not required but you'll find it easier)
2. Unzip the attached somewhere.
3. Make a call, hit Speaker and turn on the FM Transmitter (you'll see why 1. makes this easier...)
4. As root, run "alsactl -f /speaker_fmtx_on restore" with "/speaker_fmtx_on" being wherever you placed that file.

Oh, the interference is a *****. I may write a daemon to make this easier.
Attached Files
File Type: zip speaker_fmtx_on.zip (1.4 KB, 140 views)
 

The Following 4 Users Say Thank You to qwerty12 For This Useful Post:
Posts: 2,225 | Thanked: 3,822 times | Joined on Jun 2010 @ Florida
#34
Sorry for delay, I was writing up a detailed review for the current extras-devel release of the universal portrait mode virtual keyboard.

Anyway, on the one hand, the complexity and lack of a .exe in a friendly Windows formal scares me. On the other hand, fear is for the weak, and the N900 does not accept the weak as it's users (but seriously I got this device planning to use it as leverage to make myself learn stuff like this, so I'll dive right in).

Actually, I just read it again and though about and and it seems relatively simple. Override the proprietary FM Transmitter applet with yours, get a random program/script thing, which somehow is tied to the speaker being on, and then call/get-called -> speaker -> fancy script.

Couple of questions: firmware updates - would they override the FM transmitter applet, requiring overriding it again?

Does it matter what I change sig_call_state_ind to? It seems like I'm just changing state to sttte in that example just to force FMTXD not to recognize that particular line (or rather not have anything to reference when it gets that particular 'command'/whatever), and that the sttte is just a change meant to make it easy to remember, find, and and fix that line of the fmtxd later. Correct?

Anyway, I will try this soon, most likely. By the way, what do alsactl and -f mean in the alsactl -f (filepath to that attached unarchived file) command/script? Because I would remember it better on-the-fly if I could attach a meaning to that command.

At any rate, thanks. I hope it helps the poster before me, though.
 

The Following User Says Thank You to Mentalist Traceur For This Useful Post:
qwerty12's Avatar
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#35
Originally Posted by Mentalist Traceur View Post
Anyway, on the one hand, the complexity and lack of a .exe in a friendly Windows formal scares me. On the other hand, fear is for the weak, and the N900 does not accept the weak as it's users (but seriously I got this device planning to use it as leverage to make myself learn stuff like this, so I'll dive right in).
Oh, I'm working on a DEB but with the amount of hacks that are gonna be in it, I can't promise it'll be good...

Originally Posted by Mentalist Traceur View Post
Couple of questions: firmware updates - would they override the FM transmitter applet, requiring overriding it again?
Yes, but it's unlikely that it will get an update - it was not updated in PR 1.2, e.g.

Originally Posted by Mentalist Traceur View Post
Does it matter what I change sig_call_state_ind to? It seems like I'm just changing state to sttte in that example just to force FMTXD not to recognize that particular line (or rather not have anything to reference when it gets that particular 'command'/whatever), and that the sttte is just a change meant to make it easy to remember, find, and and fix that line of the fmtxd later. Correct?
Correct. Make sure you're changing it to something of the same length, however!

Originally Posted by Mentalist Traceur View Post
Anyway, I will try this soon, most likely. By the way, what do alsactl and -f mean in the alsactl -f (filepath to that attached unarchived file) command/script? Because I would remember it better on-the-fly if I could attach a meaning to that command.
It loads the sound settings from that file. It's pretty much the key to it all: By enabling the speaker and the FMTX control, we can make the sound go to the FM transmitter.
 

The Following 4 Users Say Thank You to qwerty12 For This Useful Post:
Posts: 7 | Thanked: 0 times | Joined on May 2010
#36
Great that you are working on this, would be very helpful at work. One question though, will this work (if you build a "app" for it) when I listen to fm-transmitter (beacause I always do at work), then if there is a call I just answer or do I have to push the "widget button" and then answer the call?

I have yet not used xterminal or extras-devel (well sixaxis I tried) for that matter, and I think xterminal is way out of my league. But if this will show up in extras-devel I have reason to at least try that out.

One more question turned up. Will this work with 1.1?
I'm far to happy with my n900 to try 1.2 out.

Thanks for all answers guys and sorry for my poor english!
I will keep my eyes open for this!

/applehorn
 
Posts: 2,225 | Thanked: 3,822 times | Joined on Jun 2010 @ Florida
#37
Well, I'd do the non deb way because it seems more fun (IE challenging), but I'm guessing if I want to make the updates that the deb would get if it's officially run through here I'd have to then download and install the deb?

Yay to me being correct. I would ask why it has to be the same length but perhaps seeing it in the file itself would make that make more sense.

Anyway, thanks for answering all my questions.

Applehorn: I am pretty sure that this should work fine in PR1.1. Honestly, though, I personally recommend updating to PR1.2. Up to you of course, and it depends on what your needs are, but so far I'm a fan of PR1.2, with my only real annoyances being minor (app manager and tiny disagreement with a specific browser detail). For me PR1.2 has been an essentially positive update. That said as far as I know this method should work the same with PR1.1.
 

The Following User Says Thank You to Mentalist Traceur For This Useful Post:
Posts: 22 | Thanked: 53 times | Joined on Apr 2010 @ Amsterdam
#38
Originally Posted by qwerty12 View Post
What?! You doubted Qwerty the Pimp?! I must get my revenge by coming up with a hack to this problem!

Prerequisite:
fmtxd patched: fmtxd, using http://maemo.org/api_refs/5.0/5.0-fi...5a46afdad43a94, checks to see if you're in a call. So open up /usr/sbin/fmtxd in a hex-editor (I used vi on the tablet itself) and replace "sig_call_state_ind" with "sig_call_sttte_ind". Make sure that the transmitter isn't on whilst doing this and that fmtxd is not running.

1. Install http://talk.maemo.org/showthread.php?t=43395 (the fm_boost variant may be better, depends) (not required but you'll find it easier)
2. Unzip the attached somewhere.
3. Make a call, hit Speaker and turn on the FM Transmitter (you'll see why 1. makes this easier...)
4. As root, run "alsactl -f /speaker_fmtx_on restore" with "/speaker_fmtx_on" being wherever you placed that file.

Oh, the interference is a *****. I may write a daemon to make this easier.
I was looking for exactly this, and based on the instructions above I created a small program to make this work while driving the car.

What is does:

1. Start the program (source attached)
2. If call state changes to active the fm transmitter is started
3. Enable your speaker manualy
4. Press the camera button, the sound is routed to fm-transmitter.
5. If the call is ended the sound is set to its original state: ("alsactl -f /var/lib/alsa/asound.state restore")

ATTENTION: The program is totally modified for my own phone and configuration, e.g. the paths in the file are hardcoded.

What should be nice:
- Store the original sound settings before routing the sound, this saved state file can be restored after ending the call.
- Nice desktop widget, or phone profile (silent, general, fm-carkit)
- dbus signal to check for enabled speaker (then the camera button signal is not needed anymore)

The code isn't great at all, but it works for me and maybe someone can use it or extend it.

Thanks to user Qwerty12, I found also some dbus integration of him in another topic.
Attached Files
File Type: gz fm-carkit.tar.gz (1.4 KB, 117 views)
 

The Following 3 Users Say Thank You to Roeland For This Useful Post:
HtheB's Avatar
Moderator | Posts: 3,718 | Thanked: 7,420 times | Joined on Dec 2009 @ Bize Her Yer Trabzon
#39
This should be in the repositories!

Love this concept. Would be nice if there was a gui so we can change some settings like you said Roeland
__________________
www.HtheB.com
Please donate if you think I'm doing a good job.
 
Posts: 323 | Thanked: 116 times | Joined on Jul 2010
#40
Some features requested:

Phone number can be transmitted by RDS to the radio BEFORE accepting the call.

So you can choose if you want to respond.

(Other features of the "RDS Notify" Widget could also be implemented.
In addititon there could be a notification for emails or social services.)
 

The Following User Says Thank You to gerdich For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 08:56.