• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Fm transmitter

Oh, my mistake! I was thinking the Warp you dissected was dead. If it's not, then there is in fact no use in making it so! lol

I agree, the RAM seems easily upgradable since it all is of the same family, but the only thing is that I believe ZTE stacked the RAM on top of the Snapdragon core, and I have no idea how one would separate the two. I found the whole "stacking" notion unlikely until I saw Hynix has a page on it. They mention offering a package combining an applications processor stacked with RAM, both of which can be mixed and matched by the customer, being ZTE in this case.

I did find that analysis page, however I didn't feel like spending the $400+ they want for their report. lol I'm sure it would be incredibly useful though.

Also, links fixed. Thanks for the heads-up!


Regarding the chipset lawsuit, I see on that page that both the WCN1312 and the QTR8601 were mentioned in this suit and yet our phone still has a fully-developed WiFi feature as provided by the WCN131... why wouldn't they do the same for the QTR8601? Mysterious, to be sure...

I'm sure the necessary functionality coiuld be enabled in the system, but it would have to be done from within the kernel. Also, there's the question of how to activate it. I'm not aware of any phone with similar hardware to the Warp which had the FM radio feature, but if one existed, it could prove to be a major step in getting this feature on our devices. If one does not exist... well... let's just say the job gets a bit harder. There's a good chance custom code would have to be added to the kernel which would address the IO pins of the QTR8601 to access, configure and control the feature.

Yeah, I was more referring to the small amount of information they provided on the page. I was a little blownback by the ~500 dollar thing XD
 
Yeesh. Sounds difficult to say the least. Is it worth it?

Difficult for us? Definitely. But for the likes of DM and Jet? Nahhhh :D

I'd say the next thing to do would be to try to find a phone which has hardware similar to the Warp (namely the same processor and the QTR8601) and which has the FM radio feature. Hopefully one can be found and the device's kernel can be picked apart to provide the needed info.
 
Difficult for us? Definitely. But for the likes of DM and Jet? Nahhhh :D

I'd say the next thing to do would be to try to find a phone which has hardware similar to the Warp (namely the same processor and the QTR8601) and which has the FM radio feature. Hopefully one can be found and the device's kernel can be picked apart to provide the needed info.

(Queue Dm's entrance) :D
 
This may be a good place to start.

Edit: I see the HTC Evo 4G is Snapdragon based (albeit a different model) and has a built-in FM radio. If this proves useful, my roommate has an old one laying around which I may be able to disassemble and analyze.
 
Yeah, I just went down the entire list and there is no phone with *known* fm capabilities that also has our model of processor. Maybe the HTC will work out!
 
Yeah, I just went down the entire list and there is no phone with *known* fm capabilities that also has our model of processor. Maybe the HTC will work out!

I found it!! The Huawei Mercury runs on the Snapdragon MSM8655 and has FM transmit and receive. Perfect!

Big coincidence on the name, huh? The Huawei Mercury lol
 
Not to burst any bubbles... But I distinctly remember someone stating that while the chip supports it... Our board wasn't built to do so if you know what I mean... Don't know how credible that user is... I mean it was waaaayy back.... But anyway... Bleh! It would be awesome if that guy was full of crap :thumbup::thumbup::thumbup:
 
Not to burst any bubbles... But I distinctly remember someone stating that while the chip supports it... Our board wasn't built to do so if you know what I mean... Don't know how credible that user is... I mean it was waaaayy back.... But anyway... Bleh! It would be awesome if that guy was full of crap :thumbup::thumbup::thumbup:

I agree it would be! I was reading through that thread, it was from back in july of 2012...no body thought we had the chip in our phones to begin with. However, the Huawei Mercury has the same model processor and quite probably the same chipset. Chances are that if it functions on that phone, it will function on ours. There are a few other indications that it will work as well, so my hopes are high. But, if it doesn't...ah well! I hope it does! :)
 
Not to burst any bubbles... But I distinctly remember someone stating that while the chip supports it... Our board wasn't built to do so if you know what I mean... Don't know how credible that user is... I mean it was waaaayy back.... But anyway... Bleh! It would be awesome if that guy was full of crap :thumbup::thumbup::thumbup:

Yeah, I was thinking that may be the case. Just because our board has the chip doesn't mean all the chips' connections were routed to the other necessary components to make this happen. If that's the case, a data sheet for the QTR8601 would almost be required to make the needed changes to the board. But hopefully it's just a matter of enabling it and altering the audio routing to actually let the FM output flow to the speaker... that would be awesome! :)
 
I have a gut feeling that the project was snubbed very late into the game and that the chip is definitely connected the way it needs to be. Especially since code was started, and the chip was built for the purpose of FM transmission. For some reason, I highly doubt that the motherboard isn't connected to the chip in the way it needs to be, maybe since from a business standpoint it doesn't make sense to design the phone to not function as intended. They probably just had a deadline that they couldn't reach, and subsequently threw the code into a background task. I believe that if they started coding, that means that everything is in place, especially since they have a GUI for the phone. I don't know, I could be wrong, but my gut says otherwise!
 
Curious, what does that mean?

Basically the HAL is what aggregates all the various hardware functions into one seamless, hopefully easy to use set of routines that can be called from other pieces of code. The old VESA standard is a fairly good example of this. Back in the day, many different brands of video cards were sold with equally many different ways of constructing an image on the screen. Now, if you're a programmer, you don't want to have to write code to detect what kind of video card the user has and then implement all the different varieties and their associated methods yourself. You want to be able to write your code once and have it be able to make an image regardless of the underlying hardware in any given user's PC. That's where VESA came in. It provided one unified standard which programmers could adhere to, and the resultant code would run on anything that supported the VESA interface. That way, you don't have to concern yourself with what manufacturer uses what base address and what card uses what resolutions - VESA handles all the details for you. Usually these helpful little interfaces are compiled into libraries and named accordingly, thus LibFM is the library for use with FM radio hardware. I'm betting this could be pulled from the Mercury and inserted into the Warp's kernel, and hopefully magic would happen...

[/novel] :)
 
Basically the HAL is what aggregates all the various hardware functions into one seamless, hopefully easy to use set of routines that can be called from other pieces of code. The old VESA standard is a fairly good example of this. Back in the day, many different brands of video cards were sold with equally many different ways of constructing an image on the screen. Now, if you're a programmer, you don't want to have to write code to detect what kind of video card the user has and then implement all the different varieties and their associated methods yourself. You want to be able to write your code once and have it be able to make an image regardless of the underlying hardware in any given user's PC. That's where VESA came in. It provided one unified standard which programmers could adhere to, and the resultant code would run on anything that supported the VESA interface. That way, you don't have to concern yourself with what manufacturer uses what base address and what card uses what resolutions - VESA handles all the details for you. Usually these helpful little interfaces are compiled into libraries and named accordingly, thus LibFM is the library for use with FM radio hardware. I'm betting this could be pulled from the Mercury and inserted into the Warp's kernel, and hopefully magic would happen...

[/novel] :)

You sir... Are learning O.o

Nice thorough explanation... Lol
 
Game changer for the Warp? Time will tell!! This phone still has some major potential to develop!!
 
I had a Evo 4g with FM radio; it was cool but drained the battery like mad and reception was poor most of the time.

Would still be cool to have on the warp
 
I had a Evo 4g with FM radio; it was cool but drained the battery like mad and reception was poor most of the time.

Would still be cool to have on the warp


Biggest thing here is the FM transmit. Receiving radio is cool, but playing music over the radio is cooler! Haha
 
Biggest thing here is the FM transmit. Receiving radio is cool, but playing music over the radio is cooler! Haha

That would be nice as long as it can put out strong enough signal that the phone doesn't need to be touching the radio antenna to work.
I has a FM transmitter that was that way lol.
 
That would be nice as long as it can put out strong enough signal that the phone doesn't need to be touching the radio antenna to work.
I has a FM transmitter that was that way lol.


Lol yeah...me too xD hopefully it's not like that
 
Back
Top Bottom