[Q] FM Radio on SLimKat - Galaxy S II Q&A, Help & Troubleshooting

I have installed the SlimKat 4.4.2 rom on my s2. Is there any possibility to get my radio back in this phone? if i install the radio app or something?

Yes, buy the Spirit1 or Spirit2 app by Mike Reid.

cowbutt said:
Yes, buy the Spirit1 or Spirit2 app by Mike Reid.
Click to expand...
Click to collapse
cant i get my samsung radio in this?

The Samsung radio uses Samsung's 'closed source' code....
As such, anybody who includes a working Samsung radio in a custom ROM is likely to incur Samsung's 'wrath'.....
Basically it ain't ever gonna happen.......
My wife says I'm a phone geek....She's probably right

kunalsaddar said:
cant i get my samsung radio in this?
Click to expand...
Click to collapse
My understanding is that Samsung's radio app requires changes and additions to Android frameworks for which corresponding source code isn't released. So, no.

keithross39 said:
The Samsung radio uses Samsung's 'closed source' code....
As such, anybody who includes a working Samsung radio in a custom ROM is likely to incur Samsung's 'wrath'.....
Basically it ain't ever gonna happen.......
My wife says I'm a phone geek....She's probably right
Click to expand...
Click to collapse
That's just sad. Thought everything was a open source framework here. Anyhow I just installed spirit FM. It worked. But it has a lot of disturbances. Even the audio output is very less
I wonder to go back to stock just for the stock radio.

I am also looking for stock FM radio in 4.4.4 or 4.4.2, got used to it. listen to it rarely but it completes as Smart phone

Didn't you even read the earlier replies?
Ain't EVER gonna happen.
My wife says I'm a phone geek....She's probably right

kunalsaddar said:
That's just sad. Thought everything was a open source framework here. Anyhow I just installed spirit FM. It worked. But it has a lot of disturbances. Even the audio output is very less
I wonder to go back to stock just for the stock radio.
Click to expand...
Click to collapse
I know there are some audio issues with Spirit in recent Slim ROMs.
I was looking into this when I tried to fix my no serial number problem with the wrong bootloader. LOL, not... Not sure if it's a permanent brick yet.
But GT-I9100 is an important phone for me to support, still in 2nd place in Spirit sales stats. So I got another off EBay and hope to see it later this week.
If I have the time I can try Slim on my GT-N7000, where it may have the same issues.

@mikereidis.....thanks for your continued support of the S2 fella....it's viewed by many devs as old tech now......
And thanks too for your hard work on spirit FM........it's much appreciated....
My wife says I'm a phone geek....She's probably right

keithross39 said:
@mikereidis.....thanks for your continued support of the S2 fella....it's viewed by many devs as old tech now......
And thanks too for your hard work on spirit FM........it's much appreciated....
Click to expand...
Click to collapse
Most ROM devs do it for free, or paltry donations, so they tend to go for the latest.
Spirit is my fulltime+ job, so I go where the sales stats (or antipated stats for new phones) tell me to go. It's nice that Google provides devs sales info that includes device IDs.

Related

FM Radio

anyone know where a guy could get the htc fm radio app???
Aldo101t said:
anyone know where a guy could get the htc fm radio app???
Click to expand...
Click to collapse
I tried installing the FM Radio app from my original Dinc, and it installed just fine, opened, showed the radio screen, and then crashed, and won't go any further than that now. Could be because that ROM was de-odexed, but I doubt it.
Have you tried pulling it from the Dinc 2 or Evo 4G Shift? I'm going to try to pull it from a HTC One S ROM if I can find one, since it's so similar to the Dinc 4G.
IceDragon59 said:
I tried installing the FM Radio app from my original Dinc, and it installed just fine, opened, showed the radio screen, and then crashed, and won't go any further than that now. Could be because that ROM was de-odexed, but I doubt it.
Have you tried pulling it from the Dinc 2 or Evo 4G Shift? I'm going to try to pull it from a HTC One S ROM if I can find one, since it's so similar to the Dinc 4G.
Click to expand...
Click to collapse
IC TAZZ rom is a one s rom but a custom rom, it was ported to the inc2
they are all system apps, thats the problem
maybe this phone doesn't have the hardware to run it
I tested FM radio and it does not work.
blazingwolf said:
I tested FM radio and it does not work.
Click to expand...
Click to collapse
The FM Radio on the HTC One S ROM I found didn't work, either.
Makes me wonder if the hardware is in place to run something like this. It uses your headset as an antenna which would seem like some hardware would need to be implemented and with the phone not having the software as stock just makes me wonder.
*Madmoose* said:
Makes me wonder if the hardware is in place to run something like this. It uses your headset as an antenna which would seem like some hardware would need to be implemented and with the phone not having the software as stock just makes me wonder.
Click to expand...
Click to collapse
Quite the possibility. I don't ever listen to the radio, but I noticed it was missing when I got the phone.
anyone try that spirit fm app, looks like it's for rooted phones, but is supposed to work on stock.
IceDragon59 said:
Quite the possibility. I don't ever listen to the radio, but I noticed it was missing when I got the phone.
Click to expand...
Click to collapse
i used it all the time on the inc2, i miss it now
*Madmoose* said:
Makes me wonder if the hardware is in place to run something like this. It uses your headset as an antenna which would seem like some hardware would need to be implemented and with the phone not having the software as stock just makes me wonder.
Click to expand...
Click to collapse
As far as I can tell this is correct.
blazingwolf said:
As far as I can tell this is correct.
Click to expand...
Click to collapse
i don't know, i think nits rom has fm radio,i think, so the hardware must be there.it's based on stock
Aldo101t said:
i don't know, i think nits rom has fm radio,i think, so the hardware must be there.it's based on stock
Click to expand...
Click to collapse
It was there because he added it. It's one of the ways that I tested FM radio.
However, if you want to mess with it have at it.
blazingwolf said:
It was there because he added it. It's one of the ways that I tested FM radio.
Click to expand...
Click to collapse
ok, you mean the app didn't work on nits rom, well then i'd say the hardware is not there then
blazingwolf said:
It was there because he added it. It's one of the ways that I tested FM radio.
However, if you want to mess with it have at it.
Click to expand...
Click to collapse
i can't i'm still locked up
So, anyone have any luck getting fm radio to work? It sounds like the hardware isn't there, but I'm still holding out hope.
Sent from my ADR6410LVW using xda app-developers app
There is definitely hardware for FM radio. Whether there is any software that can utilize it is still unknown (at least to me).
I don't have root yet but when I do that's one of my goals - to get the FM tuner working.
xdadevelopers-user said:
There is definitely hardware for FM radio. Whether there is any software that can utilize it is still unknown (at least to me).
I don't have root yet but when I do that's one of my goals - to get the FM tuner working.
Click to expand...
Click to collapse
Yes, the chip is capable of FM. However, everything else seems to be missing. As noted in this thread I tried several things to get it working and it didn't.
Aldo101t said:
anyone try that spirit fm app, looks like it's for rooted phones, but is supposed to work on stock.
Click to expand...
Click to collapse
Spirit Free is here: http://d-h.st/P5Y .
I've had debug logs from two un-rooted users, but nobody has ever sent one from a rooted device, and I'd be interested to see. My sales stats actually show 6 people with this phone, but it seems many people don't even get in touch with me if it doesn't work. I may disable this device in Play and see if anyone notices.
Use Menu-> Test-> Email-> Logs and after 20 seconds or so press Send.
AFAICT, the FM/Bt/WiFi combo chip is the same WCN3660 on the AT&T OneX / OneXL LTE/ OneS / Evo 4G LTE and some new Motorolas.
AFAIK, nobody knows if the FM antenna pin(s) are connected to the wired headset circuitry for use as the FM antenna. If so, then software may be able to enable FM.
BUT, like the new Motorola's (Razr HD, M ?) it appears that the firmware/ROM is not set up to enable FM, perhaps via some config option that Qualcomm provides.
So I think a custom kernel and/or ROM will be required to even see if FM is hardware possible.
Or, with SU/root we may get lucky and be able to load the radio-iris loadable kernel driver and get it working. Getting it loaded at least is the main thing needed to get further info.
mikereidis said:
Spirit Free is here: http://d-h.st/P5Y .
I've had debug logs from two un-rooted users, but nobody has ever sent one from a rooted device, and I'd be interested to see. My sales stats actually show 6 people with this phone, but it seems many people don't even get in touch with me if it doesn't work. I may disable this device in Play and see if anyone notices.
Use Menu-> Test-> Email-> Logs and after 20 seconds or so press Send.
AFAICT, the FM/Bt/WiFi combo chip is the same WCN3660 on the AT&T OneX / OneXL LTE/ OneS / Evo 4G LTE and some new Motorolas.
AFAIK, nobody knows if the FM antenna pin(s) are connected to the wired headset circuitry for use as the FM antenna. If so, then software may be able to enable FM.
BUT, like the new Motorola's (Razr HD, M ?) it appears that the firmware/ROM is not set up to enable FM, perhaps via some config option that Qualcomm provides.
So I think a custom kernel and/or ROM will be required to even see if FM is hardware possible.
Or, with SU/root we may get lucky and be able to load the radio-iris loadable kernel driver and get it working. Getting it loaded at least is the main thing needed to get further info.
Click to expand...
Click to collapse
Log sent. No luck on anything working though. There is no sound of static even so I can't tell if it is even trying. I have also tried other FM apps from HTC with no luck. I have no idea how to tell if the antenna pins are connected though I would be happy to try if told how.
Let me know if the logs help.
blazingwolf said:
Log sent. No luck on anything working though. There is no sound of static even so I can't tell if it is even trying. I have also tried other FM apps from HTC with no luck. I have no idea how to tell if the antenna pins are connected though I would be happy to try if told how.
Let me know if the logs help.
Click to expand...
Click to collapse
Thanks ! Nice to finally see with SU.
With SU your radio-iris-transport FM driver is successfully loaded.
Spirit detect and uses the HTC OEM Proprietary FM API. The problem there is that RSSI values are 0 or -128, a bad sign.
But there is still hope with the low level API.
Set Menu-> Settings-> FM API to "Low Level" and restart Spirit.
For audio, the default setting (Auto) of Audio-> Method is translated to "HTC", which is for stock HTC devices. That seems to be getting translated to the proper audio ALSA control settings. But if you lack any audio, setting Audio-> Method to "HTC OneX ALSA" or even "HTC OneX QCom" might help.

[Q] FM radio on roms

any hope of getting FM radio support on roms (I'm mainly using cyanogenmod, usually sportsstar's). I've tried the port of the apk for the fm radio (wouldn't run) and some spirit radio apk (loud static all channels). Thanks.
I'm using spirit and it works fine. You do need to have a headset plugged in though for an antenna
Sent from my HTC_Amaze_4G using xda app-developers app
yeah. ok thanks, I guess I will try again.
your welcome
reebokhcfr said:
yeah. ok thanks, I guess I will try again.
Click to expand...
Click to collapse
Are you using the feb 3rd beta version of spirit?
The stock FM radio is probably going to need to be rebuilt to make it work. Or there is just some strange file that is missing or not configured right.
chevycowboyusa said:
Are you using the feb 3rd beta version of spirit?
The stock FM radio is probably going to need to be rebuilt to make it work. Or there is just some strange file that is missing or not configured right.
Click to expand...
Click to collapse
Sense Apps do not work on AOSP roms. And can't be made to work...
FM Radio
dcacklam said:
Sense Apps do not work on AOSP roms. And can't be made to work...
Click to expand...
Click to collapse
Hi Dave! Thanks for the response
I thought there was an FM radio app in the CM Builds??
There are people using Spirit on CM10 (other devices) and I have got Spirit working on Sense 4 (even though the built in one doesn't work)
I have tried my darndest to get Spirit radio to work. All I get is white noise.
What am I missing or not configured? I did search the site, but wasn't able to
find the answer.
Thanks.
mgp53 said:
I have tried my darndest to get Spirit radio to work. All I get is white noise.
What am I missing or not configured? I did search the site, but wasn't able to
find the answer.
Thanks.
Click to expand...
Click to collapse
I couldn't get it to work either on the PacMan rom
I just flashed SpeedRom 9.0 Beta 1 and the FM Radio app works because SpeedROM is still a sense based ROM but looks like JellyBean.
Viper Radio
chevycowboyusa said:
I'm using spirit and it works fine. You do need to have a headset plugged in though for an antenna
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have used viper from version 1.6.6, 1.7.0.1 and 1.7.0.2, the fm radio never worked. even when i used spirit FM it only just make noise as if no station is working.
kodunmit said:
I have used viper from version 1.6.6, 1.7.0.1 and 1.7.0.2, the fm radio never worked. even when i used spirit FM it only just make noise as if no station is working.
Click to expand...
Click to collapse
That's strange. Where are you located?
I'm in California.
Not much proof, but this is it working.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
That's strange. Where are you located?
I'm in California.
Not much proof, but this is it working.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have the same issue with Sportsstar's CM10.1. Sprit FM just gives me static (though I can occasionally hear the slightest bit of an actual station). I think I read in his thread that radio firmware is missing from CM10.1. Is that something one can flash after the fact?
Firmware
JimDandy68 said:
I have the same issue with Sportsstar's CM10.1. Sprit FM just gives me static (though I can occasionally hear the slightest bit of an actual station). I think I read in his thread that radio firmware is missing from CM10.1. Is that something one can flash after the fact?
Click to expand...
Click to collapse
There is a difference Between the Radio firmware for the hardware (flashed thru hboot) and possibly radio drivers in the ROM.
You can flash the ICS Radio update, link in my Viper thread or ARHD thread, that will update you to the most recent radio "Firmware"
You do need to have an antenna (wired headset) and you have to manually tune the radio station.
I'll test it on CM10.1 later this weekend and I'll let you know what I can figure out!
chevycowboyusa said:
There is a difference Between the Radio firmware for the hardware (flashed thru hboot) and possibly radio drivers in the ROM.
You can flash the ICS Radio update, link in my Viper thread or ARHD thread, that will update you to the most recent radio "Firmware"
You do need to have an antenna (wired headset) and you have to manually tune the radio station.
I'll test it on CM10.1 later this weekend and I'll let you know what I can figure out!
Click to expand...
Click to collapse
Thanks, Chevy
I can't find the reference I was talking about, but here's a reference to missing drivers: http://forum.xda-developers.com/showthread.php?t=2010901
And if this is what you're talking about for a radio update - http://forum.xda-developers.com/showthread.php?p=42317972&highlight=radio+update#post42317972 - that matches my current baseband version.
FM radio works on ICS ROMs, like ARHD and SpeedRom, I know. I also know I need a headset attached - only way it ever worked. I've seen other threads about Spirit FM just producing static, so I don't know if it's that app and this device. Anyway, thanks for whatever you can figure out. My thought was that flashing anything ICS on JB wouldn't work, but I don't know.
JimDandy68 said:
Thanks, Chevy
I can't find the reference I was talking about, but here's a reference to missing drivers: http://forum.xda-developers.com/showthread.php?t=2010901
And if this is what you're talking about for a radio update - http://forum.xda-developers.com/showthread.php?p=42317972&highlight=radio+update#post42317972 - that matches my current baseband version.
FM radio works on ICS ROMs, like ARHD and SpeedRom, I know. I also know I need a headset attached - only way it ever worked. I've seen other threads about Spirit FM just producing static, so I don't know if it's that app and this device. Anyway, thanks for whatever you can figure out. My thought was that flashing anything ICS on JB wouldn't work, but I don't know.
Click to expand...
Click to collapse
Just want to ask again on this thread, has anyone ever gotten Spirit FM or another FM radio apk to work on a JB ROM (non-sense-based)? Chevy mentioned the Spirit FM 3rd beta, but not sure whether he was talking about having it work on a JB ROM or on Viper. ICS ROMs mostly have the stock radio app working, so not an issue there.
Thanks.
There is code in the CM base sources allowing for radio apps like spirit FM, now whether the devs working on it here have enabled it or gone through the task of debugging to ensure it works is a different story. Tytung has it working well in his CM ROMs for the HD2. I purchased it (spirit) to use on his ROMs so I do know it can work with CM if the developer chooses to. Frankly, for me this capability isn't as important as resolving the other outstanding issues which are keeping JellyBean from being fully functional and truly stable on our devices.
Odysseus1962 said:
There is code in the CM base sources allowing for radio apps like spirit FM, now whether the devs working on it here have enabled it or gone through the task of debugging to ensure it works is a different story. Tytung has it working well in his CM ROMs for the HD2. I purchased it (spirit) to use on his ROMs so I do know it can work with CM if the developer chooses to. Frankly, for me this capability isn't as important as resolving the other outstanding issues which are keeping JellyBean from being fully functional and truly stable on our devices.
Click to expand...
Click to collapse
Yeah, I'm really just trying to find out if anyone has gotten something working on the Amaze, not any other device. For me, the showstoppers on CM10.1 were uncontrolled in-call volume (evidently working in Evervolv), audio drop-outs when listening to music, and lack of FM radio. Otherwise, it seemed really solid. I'm kinda tired of laggy ICS ROMS, but everything works.
Thanks
JimDandy68 said:
Yeah, I'm really just trying to find out if anyone has gotten something working on the Amaze, not any other device. For me, the showstoppers on CM10.1 were uncontrolled in-call volume (evidently working in Evervolv), audio drop-outs when listening to music, and lack of FM radio. Otherwise, it seemed really solid. I'm kinda tired of laggy ICS ROMS, but everything works.
Thanks
Click to expand...
Click to collapse
I know what you're talking about. I think many here, myself included, wish that development was further along. Frankly, I find it sad and ironic that my old HD2, which was a Windows phone, has had fully functional usable stable Jellybean ROMs for a well over a year and it never had any sources released to develop from.
The sad truth is that the Amaze is a great device that wasn't marketed well, so few units were sold. Too few at least for it to have developed a devoted loyal following. If you follow the threads you see that there was never a large volume of development for it and that most of the early adopters have long since moved on to other devices. I'm just glad that we're now experiencing a second wave with new folks stepping up and trying.
I'm optimistic that the issues currently afflicting these builds can be resolved and that our Amazes will get a new lease on life. We just need to have a bit more patience, they're getting closer to nailing it. Once one gets it right the others will learn and use in their development. Then we'll have all kinds of jellybean and KitKat flavors to choose from.
Odysseus1962 said:
I'm optimistic that the issues currently afflicting these builds can be resolved and that our Amazes will get a new lease on life. We just need to have a bit more patience, they're getting closer to nailing it. Once one gets it right the others will learn and use in their development. Then we'll have all kinds of jellybean and KitKat flavors to choose from.
Click to expand...
Click to collapse
Hope your optimism proves right. It's amazing (no pun intended) that anyone spends there time doing this kind of dev work at all. Pretty sure I'll never buy another HTC device, too.
JimDandy68 said:
Hope your optimism proves right. It's amazing (no pun intended) that anyone spends there time doing this kind of dev work at all. Pretty sure I'll never buy another HTC device, too.
Click to expand...
Click to collapse
I wouldn't be so down on HTC. They may not have been the most supportive manufacturer when it comes to outside development, but they've also produced some of the most groundbreaking innovative products. They're in financial trouble now, as their market share has eroded, and haven't had a breakout device in some time. They realize this and have begun making incremental improvements within the development community in an attempt to improve it's perception. The thing is who are you going to jump ship to? Samsung is already undermining android by developing Its own market place for apps that can only run on their devices and has announced It's developing its own proprietary OS. Since they're the biggest player in this device market, they could easily splinter Android and force other manufacturers to do the same to compete.
The point is, if there's one thing I've learned from my 50 years on this planet is to never say never about anything.
Odysseus1962 said:
The point is, if there's one thing I've learned from my 50 years on this planet is to never say never about anything.
Click to expand...
Click to collapse
Point taken. I'm 45 and evidently haven't learned anything. :cyclops:
Time to go back to a landline.

[Q] Issue with Stock Samsung 4.1.2 ROM (I9100XWLSW)

Hi,
Search everywhere and still stuck!
This is issue that I have bee trying to solve on the 'android-rsap' forum, but am completely stuck, so by posting here I am hoping that someone can shed some light on what is going on.
Link: forum.android-rsap.com/viewtopic.php?f=32&t=871
In short, the device is a Samsung Galaxy 2 (XEU), and the bluetooth rsap functionality works fine with 4.0.4 (I9100XWLPT) but when I upgrade to 4.1.2 (I9100XWLSW) it no longer works at all. What is most weird is that it seems to be only my handset that is affected, it does not seem to be a universal issue. :roll eyes: What could be specific to my handset that stops this functionality working as it should?
I have been going back to 4.0.4 and upgraded to 4.1.2. many times now, via OTA, Kies and Odin, same result every time, sadly. 4.0.4 works every time, 4.1.2 has never worked with rsap and my car
What could be specific to my handset that stops this functionality working as it should? I have tried root'ing the handset to do more testing and to try the rsap app from Google App Store, but that has the same issue. Could some of the radio software be wrong? or?
Picture shows Kies upgrade screen and the 4.0.4 and 4.1.2 versions I am getting.
Any hints would be appreciated.
Regards,
J.
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
gastonw said:
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
Click to expand...
Click to collapse
Ok, so with an XEU handset - what version would you recommend?
realist42 said:
Ok, so with an XEU handset - what version would you recommend?
Click to expand...
Click to collapse
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
..
realist42 said:
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
Click to expand...
Click to collapse
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
realist42 said:
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
Click to expand...
Click to collapse
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Repporte Redan
king_below_my_lord said:
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
HI,
Took a little time to get the phone back in order and then to go an do the trace.
Not knowing what I am really looking for, but it strikes me that the bluetooth stack looks to just be giving up...
Regards,
J.
Hi all,
Well, today I managers to briefly borrow another S2 handset with JB on it. This other handset has the same issues that I have, so this must be something in the packaging of the Bluetooth that Samsung did - but I am guessing here.
Any clues would be appreciated, although I think I am fighting a loosing battle here... (works with an S3, so I should go and upgrade! at least chapter now that there is the S4 - but I like the form factor of the S2 better)
Regards,
J
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Well, thanks for looking anyway...
My thinking on this is now that as it works with newer cars and only the older ones that now have issues, it must be a version issue, i.e. the version of the bluetooth stack is not the one it should be. It would be interesting to know if there is a difference in the version of the bluetooth stack and the rsap daemon between the S3 (which works on JB) and the S2 (which does not). Would that tell me anything interesting?
Regards,
J.
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
djshotty said:
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
Click to expand...
Click to collapse
HI,
I was not aware of this, and are you saying this is specific to the S2, so the fact that is works with an S3 on 4.1.2 is irrelevant?
J.
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
djshotty said:
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
Click to expand...
Click to collapse
Well, my issues are with specifically with rsap, not really A2DP, but if it affects the whole stack, this could be an issue.
To illustrate: I have 2 cars, one older, one newer. With the newer car all is well, and it works at is should (as far as I know) The older car was working pretty much with out issues on 4.0.4, but refuses to work with 4.1.2. Both cars rely on rsap.
Not sure this helps, just wanted to illustrate the problem that I am trying to solve.
Regards,
J.
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
djshotty said:
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
Click to expand...
Click to collapse
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
realist42 said:
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
Click to expand...
Click to collapse
That's why I suggested you look at the forum I provided the link for, there are plenty with the 'Phone calls via Bluetooth into car stereo' issue, including myself...

Rooted! Thinking About Un Rooting And Updating to 4.4.2! Did Not Trip Knox! Help?

I have rooted my Sprint Note 3 a few times now without tripping KNOX. I am currently rooted and thinking about un-rooting and going back to stock via update of KitKat 4.4.2.
I have un-rooted without tripping KNOX either.
My main reason I want to do this is because I got a new car stereo that has Bluetooth audio and voice. Everything works perfectly and connects excepts that sometimes while listening to music something cuts out for like a split second. The phone is right next to the car stereo.
The car stereo unit is the Jensen VX4010
Sprint Note 3
I do not think the Jensen VX4010 has a bios update or will ever.
The only think I can think of is that the Bluetooth software on 4.3 is a little dated.
If I update to the latest Android software I am thinking this might fix the issue. I think the latest android update has Bluetooth AVRCP and 4.3 does not. I could be wrong.
Options:
1. Do you think this is a possible problem?
2. Has Google fixed all the problems with KitKat or is it still a nightmare? Like Battery Drain issues?
3. Should I just wait and deal with this Bluetooth issue?
4. Is there a way to just update to the latest Bluetooth technology and just stick with 4.3?
Thank you for reading and I look forward to your comments.
Ill be pretty straight forward here..
Jensen is known for budget low cost ( low feature) equipment in the car audio world. Its not total junk and its gotten alot better in recent years compared to how they were before Audiovox bought them out, but you get what you pay for. That head unit retails for around $240 compared to other brands that start at $350-400. You sacrifice features and build quality. ( its like comparing your Galaxy Note 3 to a galaxy S2 Mini)
The clipping you are getting I will put money on is your deck.
I don't think updating your phone will improve it, I would test another device and see if you can duplicate the cutting out.. And also try connecting to a different bluetooth device on your Note 3 and see if you experience it.. then you can rule out if its the deck or the phone.
My money is on the deck though as the problem.
Astrongtower said:
I have rooted my Sprint Note 3 a few times now without tripping KNOX. I am currently rooted and thinking about un-rooting and going back to stock via update of KitKat 4.4.2.
I have un-rooted without tripping KNOX either.
My main reason I want to do this is because I got a new car stereo that has Bluetooth audio and voice. Everything works perfectly and connects excepts that sometimes while listening to music something cuts out for like a split second. The phone is right next to the car stereo.
The car stereo unit is the Jensen VX4010
Sprint Note 3
I do not think the Jensen VX4010 has a bios update or will ever.
The only think I can think of is that the Bluetooth software on 4.3 is a little dated.
If I update to the latest Android software I am thinking this might fix the issue. I think the latest android update has Bluetooth AVRCP and 4.3 does not. I could be wrong.
Options:
1.Do you think this is a possible problem?
2.Has Google fixed all the problems with KitKat or is it still a nightmare? Like Battery Drain issues?
3.Should I just wait and deal with this Bluetooth issue?
4.Is there a way to just update to the latest Bluetooth technology and just stick with 4.3?
Thank you for reading and I look forward to your comments.
Click to expand...
Click to collapse
Closest thing I can find that may give you hope. Most definitely an issue for those enjoying this feature, but looks that the update fixed the issue...
http://forum.xda-developers.com/showthread.php?t=2473555&page=6
Sent from my SM-N900P using Tapatalk
chaosrecords said:
Ill be pretty straight forward here..
Jensen is known for budget low cost ( low feature) equipment in the car audio world. Its not total junk and its gotten alot better in recent years compared to how they were before Audiovox bought them out, but you get what you pay for. That head unit retails for around $240 compared to other brands that start at $350-400. You sacrifice features and build quality. ( its like comparing your Galaxy Note 3 to a galaxy S2 Mini)
The clipping you are getting I will put money on is your deck.
I don't think updating your phone will improve it, I would test another device and see if you can duplicate the cutting out.. And also try connecting to a different bluetooth device on your Note 3 and see if you experience it.. then you can rule out if its the deck or the phone.
My money is on the deck though as the problem.
Click to expand...
Click to collapse
Not that I think of it. I have paired this in a Scion before and this never happened. and I have paired it with a JBL Charge and played Disc Golf for hours without a single hiccup.
So it must be the deck. Or bad connection between Android and Jensen VX4010.
Please advice because if this is true I am going back to the place where I got it installed and return it and get a pioneer. This is going to be a major hassle and I am sure they are going to give me a hard time but will do it.
micmars said:
Closest thing I can find that may give you hope. Most definitely an issue for those enjoying this feature, but looks that the update fixed the issue...
http://forum.xda-developers.com/showthread.php?t=2473555&page=6
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Ok I have read the thread. Not seeing an exact correction but it does appear that if you update it will run better. Do you know if the blue tooth will drain battery or if they fixed the battery drain because once I update I can not go back unless something new has come out since last time I checked.
Please advise and read above post because I will be in a major jam tomorrow in order to return my stereo unit and or upgrade to 4.4.2 permanently and I never really had to in the first place.
Astrongtower said:
Not that I think of it. I have paired this in a Scion before and this never happened. and I have paired it with a JBL Charge and played Disc Golf for hours without a single hiccup.
So it must be the deck. Or bad connection between Android and Jensen VX4010.
Please advice because if this is true I am going back to the place where I got it installed and return it and get a pioneer. This is going to be a major hassle and I am sure they are going to give me a hard time but will do it.
Ok I have read the thread. Not seeing an exact correction but it does appear that if you update it will run better. Do you know if the blue tooth will drain battery or if they fixed the battery drain because once I update I can not go back unless something new has come out since last time I checked.
Please advise and read above post because I will be in a major jam tomorrow in order to return my stereo unit and or upgrade to 4.4.2 permanently and I never really had to in the first place.
Click to expand...
Click to collapse
I am unclear on many of the issues to which you refer with relation to the specific device you're using, as I don't use them.
I linked the thread due to your specific reference to Bluetooth and AVRCP.
That page to which I linked mentioned it being compatible with the AT&T Note 3 running KitKat.
As to Bluetooth drain being an issue that's been resolved or no on TouchWiz KitKat, I cannot answer, since I use a Bluetooth headset only, and have had zero issues. Others have reported Bluetooth battery drain since this phone was first released.
As to your choice to upgrade or no, I, unfortunately, cannot provide such a definitive answer as you seem to need.
If you wish to play it safe, then I suppose your safest bet is to not upgrade. The alternative has too many ifs and little certainty.
Sent from my SM-N900P using Tapatalk
chaosrecords said:
Ill be pretty straight forward here..
Jensen is known for budget low cost ( low feature) equipment in the car audio world. Its not total junk and its gotten alot better in recent years compared to how they were before Audiovox bought them out, but you get what you pay for. That head unit retails for around $240 compared to other brands that start at $350-400. You sacrifice features and build quality. ( its like comparing your Galaxy Note 3 to a galaxy S2 Mini)
The clipping you are getting I will put money on is your deck.
I don't think updating your phone will improve it, I would test another device and see if you can duplicate the cutting out.. And also try connecting to a different bluetooth device on your Note 3 and see if you experience it.. then you can rule out if its the deck or the phone.
My money is on the deck though as the problem.
Click to expand...
Click to collapse
Update!
Ok so I returned the Jensen and got the Pioneer AVH-X7500BT!
Looks like this was a good idea. Bluetooth is great! Much more options.
The only question I have is …
Pandora all of the information shows up like what song it is and who is singing. But for Bluetooth neither this unit nor the other unit displayed information. I am just surprised that these decks can’t show that for 2013/2014 Decks.
I still have not un-rooted my phone and nor do I think I will now. I am just still thinking that if I update to 4.4.2 and get the new updated BT Software on my phone maybe it will transfer song information.
Can anyone verify this?
Other than the song information everything is working great on the pioneer.
Astrongtower said:
Update!
Ok so I returned the Jensen and got the Pioneer AVH-X7500BT!
Looks like this was a good idea. Bluetooth is great! Much more options.
The only question I have is …
Pandora all of the information shows up like what song it is and who is singing. But for Bluetooth neither this unit nor the other unit displayed information. I am just surprised that these decks can’t show that for 2013/2014 Decks.
I still have not un-rooted my phone and nor do I think I will now. I am just still thinking that if I update to 4.4.2 and get the new updated BT Software on my phone maybe it will transfer song information.
Can anyone verify this?
Other than the song information everything is working great on the pioneer.
Click to expand...
Click to collapse
Try a different note with 4.4.2 before you update because once you do update there is no going back to 4.3 .... so try and see if it will work before doing the update and maybe messing something else up
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Try a different note with 4.4.2 before you update because once you do update there is no going back to 4.3 .... so try and see if it will work before doing the update and maybe messing something else up
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Man that is a brilliant idea. I can stop by the Sprint Store or something and have one of the Tech's come out with their note 3 or something. See if it works and if it does I will update and if it doesn't Ill just keep what I have.
Great Idea!
Astrongtower said:
Update!
Ok so I returned the Jensen and got the Pioneer AVH-X7500BT!
Looks like this was a good idea. Bluetooth is great! Much more options.
The only question I have is …
Pandora all of the information shows up like what song it is and who is singing. But for Bluetooth neither this unit nor the other unit displayed information. I am just surprised that these decks can’t show that for 2013/2014 Decks.
I still have not un-rooted my phone and nor do I think I will now. I am just still thinking that if I update to 4.4.2 and get the new updated BT Software on my phone maybe it will transfer song information.
Can anyone verify this?
Other than the song information everything is working great on the pioneer.
Click to expand...
Click to collapse
Bluetooth wont usually sync the picture and album art with most radios.
Pioneer is a good choice!
The radio itself has to have its own Pandora app to display what you are looking for... Bluetooth just streams the audio through with third party apps.. and when you use the music apps it sends the song information from the file its playing. There may be a pioneer app on the play store to do this for you with pandora/etc.. I still use my Pioneer Premier radio from 2006 ( Premier line was amazing then) I know pioneer has a thing called "Appradio" which uses MHL connection to your phone to use the phone display as the headunit so all your apps/etc work on the screen.
That may be the direction you want to go in.. if that matters the most to you.
Also- Rooting wont affect anything with your bluetooth- Everything will work just like it did before if you root. You just void warranty if you trip knox.. you only need root if you want to install roms, remove system apps, or install apps that require root access ( being able to write to your /system directory) like Titanium Backup, Tethering Apps, Flashlights.. etc..
Ive rooted every device ive ever gotten my hands on- I go through phones every 6-9 months, and I rent cars and use bluetooth with every model out there and they all work great with my note 3 regardless what rom i have. Only time i ever had a problem was when the phone was overheating..
chaosrecords said:
Bluetooth wont usually sync the picture and album art with most radios.
Pioneer is a good choice!
The radio itself has to have its own Pandora app to display what you are looking for... Bluetooth just streams the audio through with third party apps.. and when you use the music apps it sends the song information from the file its playing. There may be a pioneer app on the play store to do this for you with pandora/etc.. I still use my Pioneer Premier radio from 2006 ( Premier line was amazing then) I know pioneer has a thing called "Appradio" which uses MHL connection to your phone to use the phone display as the headunit so all your apps/etc work on the screen.
That may be the direction you want to go in.. if that matters the most to you.
Also- Rooting wont affect anything with your bluetooth- Everything will work just like it did before if you root. You just void warranty if you trip knox.. you only need root if you want to install roms, remove system apps, or install apps that require root access ( being able to write to your /system directory) like Titanium Backup, Tethering Apps, Flashlights.. etc..
Ive rooted every device ive ever gotten my hands on- I go through phones every 6-9 months, and I rent cars and use bluetooth with every model out there and they all work great with my note 3 regardless what rom i have. Only time i ever had a problem was when the phone was overheating..
Click to expand...
Click to collapse
Thank you so much for all this valuable information. I will try to do everything you have suggested and you let you know how it goes. I am so glad I got rid of that Jensen. I did like how the USB and the Audio Out was right on the Dash but I can get over that.
Again Thank You! Will be trying all this out!
Astrongtower said:
Thank you so much for all this valuable information. I will try to do everything you have suggested and you let you know how it goes. I am so glad I got rid of that Jensen. I did like how the USB and the Audio Out was right on the Dash but I can get over that.
Again Thank You! Will be trying all this out!
Click to expand...
Click to collapse
You can definitely get rooted again on the latest firmware.
I just did an Odin One Click to the latest version ( Nc5 Firmware) with WiFi Calling
-used CF Auto Root to root again with Odin
-installed TWRP recovery with Odin-
-installed Freeza's Fre3 rom 2.1, flashed the 400mb update to 2.6, then flashed the theme pack thats in the thread there and my phone works great.
I also changed my LCD Density to 320 so my phones UI fits alot more on the screen like I do with most of my roms I flash.
As far as bluetooth goes I didnt notice any differences... The only problem I ever have when dealing with roms is when I use Cyanogenmod roms, or anything AOSP based I have issues with the volume being too low.. but lately Ive been on Freeza's rom and sometimes switch to Josh Beach's roms ( kitkatkiller) both are highly recommended and are based on stock samsung firmware thats themed and de-bloated.
chaosrecords said:
You can definitely get rooted again on the latest firmware.
I just did an Odin One Click to the latest version ( Nc5 Firmware) with WiFi Calling
-used CF Auto Root to root again with Odin
-installed TWRP recovery with Odin-
-installed Freeza's Fre3 rom 2.1, flashed the 400mb update to 2.6, then flashed the theme pack thats in the thread there and my phone works great.
I also changed my LCD Density to 320 so my phones UI fits alot more on the screen like I do with most of my roms I flash.
As far as bluetooth goes I didnt notice any differences... The only problem I ever have when dealing with roms is when I use Cyanogenmod roms, or anything AOSP based I have issues with the volume being too low.. but lately Ive been on Freeza's rom and sometimes switch to Josh Beach's roms ( kitkatkiller) both are highly recommended and are based on stock samsung firmware thats themed and de-bloated.
Click to expand...
Click to collapse
Awesome I will check all that as well. I kept my phone rooted so far on 4.3. I might just flash all your stuff now that Chainfire has come out with a reset flash counter not that its a big deal anyways anymore. Note 3 is getting a little dated and the newness is wearing off so I am not worried about it. Works great.
I tried AppRaido with little luck. Everything works perfect but it does not show any song information on the screen.
What I would love to have is a Music Player that plays FOLDERS and shows SONG INFORMATION on the DECK. I am doubting that this is probably impossible.
If you have any other great ideas please shoot.
Looking forward to searching for more cool apps on Android to see if they are compatible. Just wish their was an App that can force the information on the screen.
I did use the built in Pandora function and everything shows up including the song information. That is awesome. Why can't there be an App that pushing the Song Information to the Deck.
Thanks!
Astrongtower said:
Awesome I will check all that as well. I kept my phone rooted so far on 4.3. I might just flash all your stuff now that Chainfire has come out with a reset flash counter not that its a big deal anyways anymore. Note 3 is getting a little dated and the newness is wearing off so I am not worried about it. Works great.
I tried AppRaido with little luck. Everything works perfect but it does not show any song information on the screen.
What I would love to have is a Music Player that plays FOLDERS and shows SONG INFORMATION on the DECK. I am doubting that this is probably impossible.
If you have any other great ideas please shoot.
Looking forward to searching for more cool apps on Android to see if they are compatible. Just wish their was an App that can force the information on the screen.
I did use the built in Pandora function and everything shows up including the song information. That is awesome. Why can't there be an App that pushing the Song Information to the Deck.
Okay so I think I read the question wrong. But I recently rooted my phone sprint note 3 using the towelroot method without Knox being tripped. I unrooted my phone or broke my root purposely by deleting the .su binaries from the system bin using ESfile explorer. Look up that technique on YouTube for more directions. It worked for me. Flixster works just fine. And the root checker did not see that my phone was rooted after I used this technique. http://m.youtube.com/watch?v=vYz4E9nO2kM . Now if you have a custom recovery or a custom rom then this method can be a hassle. And I suggest you search for a Odin technique.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
kaice30 said:
Astrongtower said:
Awesome I will check all that as well. I kept my phone rooted so far on 4.3. I might just flash all your stuff now that Chainfire has come out with a reset flash counter not that its a big deal anyways anymore. Note 3 is getting a little dated and the newness is wearing off so I am not worried about it. Works great.
I tried AppRaido with little luck. Everything works perfect but it does not show any song information on the screen.
What I would love to have is a Music Player that plays FOLDERS and shows SONG INFORMATION on the DECK. I am doubting that this is probably impossible.
If you have any other great ideas please shoot.
Looking forward to searching for more cool apps on Android to see if they are compatible. Just wish their was an App that can force the information on the screen.
I did use the built in Pandora function and everything shows up including the song information. That is awesome. Why can't there be an App that pushing the Song Information to the Deck.
Okay so I think I read the question wrong. But I recently rooted my phone sprint note 3 using the towelroot method without Knox being tripped. I unrooted my phone or broke my root purposely by deleting the .su binaries from the system bin using ESfile explorer. Look up that technique on YouTube for more directions. It worked for me. Flixster works just fine. And the root checker did not see that my phone was rooted after I used this technique. http://m.youtube.com/watch?v=vYz4E9nO2kM . Now if you have a custom recovery or a custom rom then this method can be a hassle. And I suggest you search for a Odin technique.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
I apologize. But I am unsure what you are trying to explain.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
I would definitely try another phone with 4.4 before updating. I for one truly hate 4.4. So much so, that I'm considering trading my gn3 for a gn2 just to get rid of it.
Skunk Ape1 said:
I would definitely try another phone with 4.4 before updating. I for one truly hate 4.4. So much so, that I'm considering trading my gn3 for a gn2 just to get rid of it.
Click to expand...
Click to collapse
Could you please tell me why you hate it so much?
Here is the deal I just went to the Sprint Store and tried a Galaxy S4 with 4.4.2 on it and it showed all song data on any app that was used to my car stereo deck.
So then I thought hey maybe its the app.
Well ... Come to find out. The default apps do play the song data to my car stereo deck but Mort Player the player that I like does not. It does how ever play on 4.4.2.
Mort Player - Song data comes over to deck
4.3 = No
4.4 = Yes
Defult Music Players
4.3 = Yes
4.4 = Yes
Now I can keep my 4.3 and find a player that can push music information and display information over current settings via 4.3 like the default players do. Or upgrade to 4.4.2 and enjoy my music player with song information listed. Then I would just have to deal with everything else that everyone hates though.
Please list what you hate so I can decide which avenue to take please.
chaosrecords said:
You can definitely get rooted again on the latest firmware.
I just did an Odin One Click to the latest version ( Nc5 Firmware) with WiFi Calling
-used CF Auto Root to root again with Odin
-installed TWRP recovery with Odin-
-installed Freeza's Fre3 rom 2.1, flashed the 400mb update to 2.6, then flashed the theme pack thats in the thread there and my phone works great.
I also changed my LCD Density to 320 so my phones UI fits alot more on the screen like I do with most of my roms I flash.
As far as bluetooth goes I didnt notice any differences... The only problem I ever have when dealing with roms is when I use Cyanogenmod roms, or anything AOSP based I have issues with the volume being too low.. but lately Ive been on Freeza's rom and sometimes switch to Josh Beach's roms ( kitkatkiller) both are highly recommended and are based on stock samsung firmware thats themed and de-bloated.
Click to expand...
Click to collapse
Please let me know how awesome 4.4.2 is and if I should upgrade and not worry about it. I went to the Sprint Store and found out that on every application on Android on 4.4.2 and a Sprint Galaxy S4 every song information played on my stereo deck. The Pioneer. I am thinking about just upgrading so I have the latest security, towers, and Bluetooth software installed on my phone.
Please read my last post to get you updated on my findings.
Also read the below quote. Many people hate 4.4.2 and I do not want to upgrade and become one of those people who are stuck.
Skunk Ape1 said:
I would definitely try another phone with 4.4 before updating. I for one truly hate 4.4. So much so, that I'm considering trading my gn3 for a gn2 just to get rid of it.
Click to expand...
Click to collapse
Astrongtower said:
Could you please tell me why you hate it so much?
Here is the deal I just went to the Sprint Store and tried a Galaxy S4 with 4.4.2 on it and it showed all song data on any app that was used to my car stereo deck.
So then I thought hey maybe its the app.
Well ... Come to find out. The default apps do play the song data to my car stereo deck but Mort Player the player that I like does not. It does how ever play on 4.4.2.
Mort Player - Song data comes over to deck
4.3 = No
4.4 = Yes
Defult Music Players
4.3 = Yes
4.4 = Yes
Now I can keep my 4.3 and find a player that can push music information and display information over current settings via 4.3 like the default players do. Or upgrade to 4.4.2 and enjoy my music player with song information listed. Then I would just have to deal with everything else that everyone hates though.
Please list what you hate so I can decide which avenue to take please.
Click to expand...
Click to collapse
What I hate has little to do with features and more to do with how much harder it is to do things as a themer. It is ass ugly and harder to theme properly. I want to tell Google and Samsung to _______themselves as they are attempting to stop us from changing things. Say what you want about how great Android platform is. Within a few years it will be locked down as tight as the iPhone. 4.4 is step 1 in that process and therefore bad.
chaosrecords said:
You can definitely get rooted again on the latest firmware.
I just did an Odin One Click to the latest version ( Nc5 Firmware) with WiFi Calling
-used CF Auto Root to root again with Odin
-installed TWRP recovery with Odin-
-installed Freeza's Fre3 rom 2.1, flashed the 400mb update to 2.6, then flashed the theme pack thats in the thread there and my phone works great.
I also changed my LCD Density to 320 so my phones UI fits alot more on the screen like I do with most of my roms I flash.
As far as bluetooth goes I didnt notice any differences... The only problem I ever have when dealing with roms is when I use Cyanogenmod roms, or anything AOSP based I have issues with the volume being too low.. but lately Ive been on Freeza's rom and sometimes switch to Josh Beach's roms ( kitkatkiller) both are highly recommended and are based on stock samsung firmware thats themed and de-bloated.
Click to expand...
Click to collapse
kaice30 said:
Astrongtower said:
Awesome I will check all that as well. I kept my phone rooted so far on 4.3. I might just flash all your stuff now that Chainfire has come out with a reset flash counter not that its a big deal anyways anymore. Note 3 is getting a little dated and the newness is wearing off so I am not worried about it. Works great.
I tried AppRaido with little luck. Everything works perfect but it does not show any song information on the screen.
What I would love to have is a Music Player that plays FOLDERS and shows SONG INFORMATION on the DECK. I am doubting that this is probably impossible.
If you have any other great ideas please shoot.
Looking forward to searching for more cool apps on Android to see if they are compatible. Just wish their was an App that can force the information on the screen.
I did use the built in Pandora function and everything shows up including the song information. That is awesome. Why can't there be an App that pushing the Song Information to the Deck.
Okay so I think I read the question wrong. But I recently rooted my phone sprint note 3 using the towelroot method without Knox being tripped. I unrooted my phone or broke my root purposely by deleting the .su binaries from the system bin using ESfile explorer. Look up that technique on YouTube for more directions. It worked for me. Flixster works just fine. And the root checker did not see that my phone was rooted after I used this technique. http://m.youtube.com/watch?v=vYz4E9nO2kM . Now if you have a custom recovery or a custom rom then this method can be a hassle. And I suggest you search for a Odin technique.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Skunk Ape1 said:
What I hate has little to do with features and more to do with how much harder it is to do things as a themer. It is ass ugly and harder to theme properly. I want to tell Google and Samsung to _______themselves as they are attempting to stop us from changing things. Say what you want about how great Android platform is. Within a few years it will be locked down as tight as the iPhone. 4.4 is step 1 in that process and therefore bad.
Click to expand...
Click to collapse
Update Update Update!
I just couldn’t believe that no App would show the music data on my deck. After seeing it work on 4.4.2 and watching different Apps work I thought I would try a ton of Apps.
To my amazement these two Apps play music folders like I want and show all music data to my car stereo deck:
Folder Player
Rocket Player
These Apps I tried play music but do not transmit any music data to my car stereo deck:
Mortplayer
KAmMa’s Folder Player
Music Folder Player Free
EX Folder Player
MFPlayer
I have no idea why the how Folder Player and Rocket Player transmit the information. But it seems I get the best of both worlds for now. I can use Rocket Player via Bluetooth and see all my folder information and keep my Note 3 rooted on 4.3. Party!
I am just wondering if I should upgrade for latest security, tower information and perks but at least I have time to think about it now.
Thanks for everyone’s help!
Click to expand...
Click to collapse
Remember that you are doing this of your own free will and if anything happens negatively including Vader going back to the dark side it's your fault.
This is what I did to go from rooted, Knox reading not tripped to 4.4.2 Knox counter still untripped.
1)You would want to back up anything onto a computer and your SD card including nandroid if possible if you don't know what a nandroid is you may not yet have the technical ability to make one.
1a) download the latest stock version of 4.4.2 use this
http://forum.xda-developers.com/showthread.php?t=2712205
2)go here
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
Print it out
3) download the Odin from here
4)the above has links to Odin and step by step instructions with pictures
5) download towelroot from http://towelroot.com
Put it on your SD card
5) pull your SD card safely and reset your phone with factory data reset or if your running a custom recovery through it.
6) follow the steps from
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
you should of printed it out....
7) after it says pass and is booting put your SD card in.
8) side load/install towelroot
8a) run towelroot and make it rain
9) install root checker verify it worked and then a superuser program.
At this point you will have a rooted 4.4.2 stock rom.
For the latest stock version of 4.4.2 use this
http://forum.xda-developers.com/showthread.php?t=2712205
And yes the Odin listed in the unroot website flashes that rom on my sprint phone without a problem.
Worked for me.
Sent from my SM-N900P using Tapatalk 2

[ROM][Official] CyanogenMod 12.1 Nightlies for the Verizon Galaxy S4 (jfltevzw)

IMPORTANT INFO:
-You must be on the VRUAMDK bootloader or you aren't going to be able to use this ROM. I'm sorry =(
(run this in a terminal to find out: getprop ro.bootloader )
-We have de-unified the Galaxy S4 line. This is for the Verizon variant (SCH-I545) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=jfltevzw&type=nightly
We have de-unified the Galaxy S4 line. Too many issues with having them all in one and a maintainer's nightmare. Look for jfltevzw builds now as opposed to the jflte builds you previously used.
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][Official] CyanogenMod 12.1 Nightlies for the Verizon Galaxy S4 (jfltevzw), ROM for the Verizon Samsung Galaxy S 4
Contributors
invisiblek
Source Code: http://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: VRUAMDK bootloader
Version Information
Status: Nightly
Created 2015-04-20
Last Updated 2015-04-19
I guess I'll post first.
Up and running on 4/20 (flashed a few hours ago). So far I have noticed:
As soon as you open the stock messaging app a notification appears saying a message could not be sent. Choosing "Discard" from the menu of the unsent message does not discard it.
The compass is not working properly. Orientation is slow to respond and is off by 180 degrees. This only happens when stationary. When viewing the sensors using Advanced Sensor Tester the magnetic sensor is showing some changes, the gyroscope sensor shows very little changes, and the orientation sensor shows one line out of three showing very little change. Don't know if it means anything.
Not sure if I am using the correct term here, but, Adaptive brightness does not seem to be responding well and overall the lower brightness setting of the display seem to be too dark. In an outdoor environment any brightness setting below 50% is pretty much unusable and the brightness when in direct light doesn't increase enough. (May not have described that correctly).
BT seems good with a Jabra earpiece. I have yet to test it with something like music play over Ford's Sync and vehicle BT.
Not sure if it is an Android 5.1 issue or not but I have had to reinstall several third party apps since going to CM12.1. Opening them results in a force close. If I navigate to the APK using root explorer, selecting it, and choosing install (to reinstall it) the app works correctly afterwards.
So far everything else seems to be working.
Logcat attached:
https://www.dropbox.com/s/khdo1uicmj8l7j8/Log_2015-04-20_14-07-16.txt?dl=0
ran the 4/18 and 4/19 build. BT works, connects but won't stream anything. First my "Music" app was force closing every time it tried to play, it kept trying so it was a loop of force closes from it. I disabled the Music app, i then started getting bluetooth share has forced closed errors.
im flashing the 4/20 build but won't be able to test bluetooth playback to my car until tomorrow.
i also have the damn #in my status bar all day long. can't get rid of it, have no idea what its doing up there. even stays through reboots.
Ok, I have come across another issue. I disconnected my Jabra BT earpiece earlier. Now it will not reconnect. BT has turned off and will not turn back on. Cycling airplane mode does not help.
Logcat:
https://www.dropbox.com/s/h86esc88wmth8pd/Log_2015-04-20_17-55-16.txt?dl=0
---------- Post added at 09:01 PM ---------- Previous post was at 08:57 PM ----------
Ok, a reboot seems to have straightened BT out for now. It is on and I can connect my earpiece.
BT was not playing nicely with my car, tried rebooting with no change. BT would connect, but I would get a "Bluetooth share has stopped" message
Sent from my SCH-I545 using Tapatalk
gmp029 said:
BT was not playing nicely with my car, tried rebooting with no change. BT would connect, but I would get a "Bluetooth share has stopped" message
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
get the same error. welcome to the club, looks like more bluetooth issues.
dansan382 said:
get the same error. welcome to the club, looks like more bluetooth issues.
Click to expand...
Click to collapse
I actually expected it, happens after every version change.
FernBch said:
I actually expected it, happens after every version change.
Click to expand...
Click to collapse
yup, i didn't think it would be any better but was worth on a shot. can tell you on the 4/20 build it connects to my car (with a little convincing) but only recognizes the hands free profile. won't push any audio across. also turning on bluetooth is super buggy, it never really turns on and just switches the slider back to off.
I've heard euroskank builds have it working but i really dont want to full wipe my device again for the 3rd time in a week lol. i signed up for a motorola credit account, waiting for the account number to come in the mail and then ordering my 64GB nexus 6. my nano sim card came yesterday which I know verizon will give me a hard time activating. I also have a sim card cutter, some cases and a screen protector coming tomorrow so either way this is happening.
dansan382 said:
yup, i didn't think it would be any better but was worth on a shot. can tell you on the 4/20 build it connects to my car (with a little convincing) but only recognizes the hands free profile. won't push any audio across. also turning on bluetooth is super buggy, it never really turns on and just switches the slider back to off.
I've heard euroskank builds have it working but i really dont want to full wipe my device again for the 3rd time in a week lol
Click to expand...
Click to collapse
I was on skank's 12.1 build until 4.17 version and BT did not stream in my car at all. It would connect, then i'd go to play music and DoubleTwist would just keep skipping to the next song without playing any audio. Then BT would be wierd and wouldnt connect/reconnect after that until a reboot.
So far I'm seeing the same funcionality on this ROM so it seems like something with the 12.1 base to me
vanberge said:
I was on skank's 12.1 build until 4.17 version and BT did not stream in my car at all. It would connect, then i'd go to play music and DoubleTwist would just keep skipping to the next song without playing any audio. Then BT would be wierd and wouldnt connect/reconnect after that until a reboot.
So far I'm seeing the same funcionality on this ROM so it seems like something with the 12.1 base to me
Click to expand...
Click to collapse
good to know. there is a never ending battle with this phone on bluetooth, the compass and MMS lol
dansan382 said:
good to know. there is a never ending battle with this phone on bluetooth, the compass and MMS lol
Click to expand...
Click to collapse
MMS was the easy fix. I made a few APN edits and it has worked ever since. What I did is in either the official thread or euroskanks thread. BT they will eventually fix. The compass, as we all know all too well, is a whole different story.
FernBch said:
MMS was the easy fix. I made a few APN edits and it has worked ever since. What I did is in either the official thread or euroskanks thread. BT they will eventually fix. The compass, as we all know all too well, is a whole different story.
Click to expand...
Click to collapse
Yea I followed your APN edits awhile back, still was hit or miss. the MMS would eventually come in but wasn't 100%. great roms though, i'm really liking lollipop
I started a bounty for the compass - http://forum.xda-developers.com/galaxy-s4-verizon/general/bounty-make-compass-cm-12-1-t3088991
Hello,
Thanks for you working on this ROM. My issue is I can't install it.
So I was running JFLTE-GPE 5.0.1 for a while now by Danvdh. I noticed that at one point the Model Number changed to the GPE and device was jltegpe (or something like that). It didn't bother anything until I tried to install this ROM when I received an error in TWRP that I can't install the ROM because it is only for the jfltevzw. Does anyone know how to fix this issue. I am now running Hyperdrive and build.prop is back to jfltevzw but I am still getting the same error message in TWRP.
I am on the Verizon model of the S4 running MDK, loki'ed the bootloader, and installed TWRP.
Thanks in advance.
Otakulad said:
Hello,
Thanks for you working on this ROM. My issue is I can't install it.
So I was running JFLTE-GPE 5.0.1 for a while now by Danvdh. I noticed that at one point the Model Number changed to the GPE and device was jltegpe (or something like that). It didn't bother anything until I tried to install this ROM when I received an error in TWRP that I can't install the ROM because it is only for the jfltevzw. Does anyone know how to fix this issue. I am now running Hyperdrive and build.prop is back to jfltevzw but I am still getting the same error message in TWRP.
I am on the Verizon model of the S4 running MDK, loki'ed the bootloader, and installed TWRP.
Thanks in advance.
Click to expand...
Click to collapse
You may have to go back to stock first (either by nandroid restore or via Odin).
FernBch said:
You may have to go back to stock first (either by nandroid restore or via Odin).
Click to expand...
Click to collapse
Thanks. I was thinking about that but since they are only nightlies and not everything is working, I'll wait.
well its been fun boys..
just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol
dansan382 said:
well its been fun boys..
just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol
Click to expand...
Click to collapse
another one bites the dust - first rajones19 and now you. I might follow soon. Too bad considering the jfltexx variant has no issues.
I am test running a Nexus 6. Next weekend is the final return date. It is big but I am getting used to it. Let's see if I want to keep it.
My decision will also depend on Google's wireless network announcement. If it sounds good, I will return this Nexus 6 and buy one from the play store and leave Verizon.
dansan382 said:
well its been fun boys..
just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol
Click to expand...
Click to collapse
Well, you'll be missed here but you gotta do what you gotta do......
I've talked jumpin ship before but I'll probably hang on till the bitter lonely end. I'm just hardheaded like that. [emoji14]
Seriously though, if I want decent coverage across my work area (10K sq miles in eastern AZ and western NM) Big Red is the only real choice. Who knows, maybe when I do decide on a new device it will be rootable and possibly even exploited.
phonedawg said:
another one bites the dust - first rajones19 and now you. I might follow soon. Too bad considering the jfltexx variant has no issues.
I am test running a Nexus 6. Next weekend is the final return date. It is big but I am getting used to it. Let's see if I want to keep it.
My decision will also depend on Google's wireless network announcement. If it sounds good, I will return this Nexus 6 and buy one from the play store and leave Verizon.
Click to expand...
Click to collapse
FernBch said:
Well, you'll be missed here but you gotta do what you gotta do......
I've talked jumpin ship before but I'll probably hang on till the bitter lonely end. I'm just hardheaded like that. [emoji14]
Seriously though, if I want decent coverage across my work area (10K sq miles in eastern AZ and western NM) Big Red is the only real choice. Who knows, maybe when I do decide on a new device it will be rootable and possibly even exploited.
Click to expand...
Click to collapse
well its time to move on, i really love the GS4 even more than my galaxy nexus but its been 2 years. I had this GS4 since launch date, actually had it 3 days early. she served me well and i honestly could have gone a little longer with it but I got tired of dealing with flashing stock roms on my phone just for certain key things not to work right. Got tired of having to explain to people when something didn't work it was because of custom software. Plus looking at my GS4 it just feels small now. Honestly would have preferred a 5.5inch phone but I dont see this thing being a problem once i get use to it. I'll probably keep the GS4 around as a mess around device so I'll probably still flash some roms with it. Don't think there is much of a demand in the resale space for a 2 year old phone like this. I've learned my lesson though, and I should have learned it from having a galaxy nexus but from now on out I'll only be using nexus devices.
I debated switching to T-Mobile and honestly I'm still very interested in doing so. Like others, coverage is a big concern and even though here in Southern PA (right outside of Philly) I get great T-Mobile coverage, I'm still worried about the one time to go somewhere that has 0 coverage. I drive back and forth to Long Island, NY where I'm originally from every few weeks and T-Mobile coverage is outstanding that entire trip so that would be nice. If I was still on the island I would switch in a heartbeat. Being in PA now, 75% of this state is a blackhole for T-Mobile coverage which very much worries me, even though I never really go that far. Maybe by the end of the year I might make the switch but for now I'm sticking with big red, unfortunately.

Categories

Resources