Related
I flashed it yesterday.
I got a network problem
I'm using WiFi, it didn't work,
anybody same as me?
It's for developmental purposes only, and many features don't work yet. So, if you are looking to use it as a daily use ROM, don't do it.
Interesting though, since the dev seems to have WiFi working on his device.
3xeno said:
It's for developmental purposes only, and many features don't work yet. So, if you are looking to use it as a daily use ROM, don't do it.
Interesting though, since the dev seems to have WiFi working on his device.
Click to expand...
Click to collapse
Maybe it is my own problem,thanks
Seeing the latest reply, it probably isn't. Apparently, WiFi works, but, it won't connect to the internet.
Anyhow, as I said, this is a experimental release, not meant for daily use.
Right, I go back to CM7 ,thank you
Hi,
I had an old desire and a car head unit that didn't support BT streaming via ad2p, so when I got my new OneX, I quickly sold the old head unit on ebay and replaced it with a newer model that supported streaming. I am now able to stream over BT which is fantastic as my plays are now recorded on the phone (i use player pro & mediamonkey desktop pc to organise my collection). Plus now I can also scrobble to last.fm, which is something i've not been able to do since time began (in the car).
but now there's one thing that's quite annoying, the lack of info being sent to the head unit (track ID, etc). I did a bit of research and it turns out that the BT stack used in base android doesn't support AVRCP 1.3, which is the version of the protocol that supports track ID. Then I found that cyanogen started supporting this....
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
Is it possible for this to be included in the custom roms? I'm asking this in general first before asking a specific ROM dev to attempt to implement. Will this need an entire cyanogen base?
I'd love to see this implemented if at all possible
EDIT: oops, i think i've posted this in the wrong place as it's a question?
did u manage to find more info about this? Anybody else knows some more details? 10q
zombiefly said:
Hi,
I had an old desire and a car head unit that didn't support BT streaming via ad2p, so when I got my new OneX, I quickly sold the old head unit on ebay and replaced it with a newer model that supported streaming. I am now able to stream over BT which is fantastic as my plays are now recorded on the phone (i use player pro & mediamonkey desktop pc to organise my collection). Plus now I can also scrobble to last.fm, which is something i've not been able to do since time began (in the car).
but now there's one thing that's quite annoying, the lack of info being sent to the head unit (track ID, etc). I did a bit of research and it turns out that the BT stack used in base android doesn't support AVRCP 1.3, which is the version of the protocol that supports track ID. Then I found that cyanogen started supporting this....
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
Is it possible for this to be included in the custom roms? I'm asking this in general first before asking a specific ROM dev to attempt to implement. Will this need an entire cyanogen base?
I'd love to see this implemented if at all possible
EDIT: oops, i think i've posted this in the wrong place as it's a question?
Click to expand...
Click to collapse
I'll have a quick go at answering, If anything is wrong then please correct me
HTC have written their own Bluetooth stack that doesn't support AVRCP 1.3 (stupid really if you ask me). This stack will be found in the stock rom, as well as all sensed based custom rom's and possibly in some unofficial AOSP roms.
The Official CM roms should have the standard BT stack with AVRCP 1.3 drafted into it, meaning that it should push the track ID's to all receivers that support it.
To answer your question: Unless HTC's BT stack can be dissected and modded to support AVRCP 1.3, or the CM BT stack can be ported over to sensed based roms (both highly un-likely as HTC's BT stack is closed, and CM's BT stack wont work on sensed based roms) then this is not possible, unless you flash a CM rom on your One X
teky.co.uk has it covered above.
the htc BT stack is (as you would expect) half complete and doesn't support anything but basic connectivity and streaming. The cyanogen mod team added this functionality around cm7 (i think). so for phones that are supported by CM, you can flash a rom built around Cyanogen and you will have track ID.
Because we cant get S-OFF, we cant flash a pure CM mod, which presumably explains why there isn't one available. There is a port in the works by TripNRaver, however the last time I checked the BT streaming was on the issues list as not working, so regardless of it using AVRCP 1.3 or not, it wouldn't work anyway.
I'm quite frustrated by this. I bought the One X thinking it would be the best (and most up to date) Android phone available. Instead i'm stuck half way to removing the HTC crap from the phone for the first 3 months of owning it. I was able to get this functionality on my ageing HTC Desire (with custom rom)...
If you can get something to work, the music player pro application has recently added support for AVRCP 1.3 on phones that support it. So when we eventually get someone to implement a new BT stack in a custom ROM, or when HTC decide to support 1.3, we can actually use the feature!
This has been bothering me for some time; I actually sent an email technical support request to HTC for followup regarding this issue.
Maybe this will be fixed by the time Jelly Bean comes out? Or possibly that could be too adventurous.
I will reply back to this thread when I hear anything from the other side. I actually submitted a link to teky's great informative post in the ticket.
This is the response from HTC when I contacted them about it.
Thanks for your patience.
I can sadly confirm, after a long discussion with a senior technical agent, that Google have not yet implimented AVRCP in there Android O/S. It would seem to be avaiable for Windows based devices, possibly due to the amount of time Microsoft have been in the mobile firmware market. But, sorry to say, it is not yet part of Android.
The only advice I can offer, would be to post on the Google official forums about this as I'm sure you will not be alone with your requirement.
Thanks for your time and for contacting HTC.
Click to expand...
Click to collapse
Sent from my HTC One X using xda premium
help us cm9, you are are only hope.... bzzzzzzt
maybe a ROM developer could help re: porting the BT stack to a custom rom?
Here's what HTC sent to me, I have since followed up.
Thank you for contacting HTC.
With reference to your query, currenty we AVRCP 1.3 is not supported by One X. If you see that some of the function on your bluetooth is not working its because of the compatibilty of the phone and the bluetooth.
Sincerely,
Sammy
HTC
This is the best I could get out of them.
Thank you for contacting HTC.
With reference to your query, yes, HTC is looking forward to this. However, we cannot provide any definite detail at this time when will this be available to the phone. That is the reason why as well we are creating new and improve phone here for our customer. Plese refer to our website for any update to our product and service and we do apologize for the inconvinience.
So, anyone know how to porting the BT stack to stock rom? or any package to do that feature?
Tks All!
trungvn1790us said:
So, anyone know how to porting the BT stack to stock rom? or any package to do that feature?
Tks All!
Click to expand...
Click to collapse
if someone created a universal zip file to flash to any android phone, that would be awesome. How in the world did cyanogenmod do it? maybe if someone asks, they can tell you how to code it into any device's rom.
some further info on this.
tbalden's CM9 port works with avrcp 1.3
http://forum.xda-developers.com/showthread.php?t=1706001 this rom is reasonably stable (battery drain is quite bad so far, the worst rom i've tried) BUT! it works fully with ACRCP 1.3
the CM10 port by tbalden does not work. I've posted many times in the thread and even messaged him directly, but nobody ever responds to my questions.
Given that Cyanogen mod supports 1.3, i'd expect this functionality to be added soon as the rom develops. I hope so as it's a fantastic rom but it's a bit flaky at the moment (as it's alpha)... if you really need avrcp 1.3, the the above linked CM9 is a decent compromise.
I'd still like an answer on how this works? is it a driver? can it be packaged and added to any rom? I think not to be honest but would still like to know.
Really can't wait for this feature!
zombiefly said:
some further info on this.
tbalden's CM9 port works with avrcp 1.3
http://forum.xda-developers.com/showthread.php?t=1706001 this rom is reasonably stable (battery drain is quite bad so far, the worst rom i've tried) BUT! it works fully with ACRCP 1.3
the CM10 port by tbalden does not work. I've posted many times in the thread and even messaged him directly, but nobody ever responds to my questions.
Given that Cyanogen mod supports 1.3, i'd expect this functionality to be added soon as the rom develops. I hope so as it's a fantastic rom but it's a bit flaky at the moment (as it's alpha)... if you really need avrcp 1.3, the the above linked CM9 is a decent compromise.
I'd still like an answer on how this works? is it a driver? can it be packaged and added to any rom? I think not to be honest but would still like to know.
Click to expand...
Click to collapse
Yes, agree with u guys and really need a package that supported to install to stock ROM
Tks and appreciate for any Hero help to do this!
this functionality is now in CM10. i dont think it can be ported to other roms as i think it has some dependency on the kernel? (but what do i know?)
I've been running tbaldens CM10 for some weeks now and it's very stable
I also would like to have AVCRP 1.3.
As far as i understood the bluetooth stack must be compiled with the kernel. The blueZ stack does support AVCRP 1.3.
But we need a custom kernel compiled with it?
I now also wrote a support inquery to HTC. Perhaps they will implement the complete bluetooth stack if enough customers ask for it.
Regards
Kai
+1
need this feature, please...
makes2068 said:
+1
need this feature, please...
Click to expand...
Click to collapse
its in the main CM10 roms now.
Sorry to dig such an old topic. But has anybody been able to find some patch to get this feature on sense 5. I feel sense 5 is awesome, (sorry to sound selfish) cannot switch over to CM10.. is there anyway I can get it .
on ARHD 31.2
If HTC has been blaming google due to this feature not being available in android itself, I feel cheated.. because have seen this same feature on all other android devices.
Also this feature is there in HTC one , the current flagship with sense 5.. One of my friend has it. If only some dev can compare files and bring out some patch for OneX.
Is this a good idea? as it causes fragmented discussion, eg. dt-apps2sd is something that works across devices but I see it discussed under one particular device meaning generally only owners of that device will take part in that discussion. BLN is another example.
chrcol said:
Is this a good idea? as it causes fragmented discussion, eg. dt-apps2sd is something that works across devices but I see it discussed under one particular device meaning generally only owners of that device will take part in that discussion. BLN is another example.
Click to expand...
Click to collapse
BLN though can be pretty device specific... Even down to the actual kernel you're using... I think there's always going to be a need for device-specific discussion of these things tbh - I doubt that would change
Or a mod for a Sense ROM, wont work on different Sense ROMs and non Sense ROMs etc.
yeah roms make sense of course that doesnt bother me, was just a thought tho
So I have this problem where when I am running Cyanogen Mod (currently 128 of ICS) on an R800x and the data will randomly just stop working, and the only way to fix it is to reboot the phone. Everything else appears to be working perfectly. I am running the latest firmware from that stickied thread in the developer's section. Any ideas why this is happening and how i can fix it? Btw as far as I can tell it's only the data that stops working, not sending/receiving calls/texts or wifi.
xrishox said:
So I have this problem where when I am running Cyanogen Mod (currently 128 of ICS) on an R800x and the data will randomly just stop working, and the only way to fix it is to reboot the phone. Everything else appears to be working perfectly. I am running the latest firmware from that stickied thread in the developer's section. Any ideas why this is happening and how i can fix it? Btw as far as I can tell it's only the data that stops working, not sending/receiving calls/texts or wifi.
Click to expand...
Click to collapse
Yeah, It's like that with all us cdma users. I've brought it up and fxp doesn't even acknowledge it. All you need to do is turn the mobile data off then on again. It's annoying, but until a decent dev looks into it it's the only workaround
ive tried putting it into airplane mode, and taking it back out, but that doesn't fix the problem. how do you do it?
and is there a way we can politely point this out to them, without acting completely entitled? like if its effecting all cdma users that's a pretty large group.
xrishox said:
ive tried putting it into airplane mode, and taking it back out, but that doesn't fix the problem. how do you do it?
and is there a way we can politely point this out to them, without acting completely entitled? like if its effecting all cdma users that's a pretty large group.
Click to expand...
Click to collapse
Well nobody on the fxp team has an r800x, I think two of them have gsm versions. So they can't test it out, and with my history with fxp himself he doesn't seem to really care about cdma at all (doesn't least show he does). People have mentioned it before and nothing comes from it. So it's a lack of caring about our type of issues, they don't have time, or it's beyond their comprehension. Your best bet is to mention it to Pax, since he does a lot of things for cdma. Here's a link to his profile
http://forum.xda-developers.com/member.php?u=4234200
Here is Keiran's profile also (he's on the fxp team)
http://forum.xda-developers.com/member.php?u=4344506
Oh, and the way I do it is: setttings>more..>mobile networks> Check data enabled off (wait 5sec) then check it back on. If that doesn't help then you can try a fresh install to see if it does anything
agraceful said:
Well nobody on the fxp team has an r800x, I think two of them have gsm versions. So they can't test it out, and with my history with fxp himself he doesn't seem to really care about cdma at all (doesn't least show he does). People have mentioned it before and nothing comes from it. So it's a lack of caring about our type of issues, they don't have time, or it's beyond their comprehension. Your best bet is to mention it to Pax, since he does a lot of things for cdma. Here's a link to his profile
http://forum.xda-developers.com/member.php?u=4234200
Here is Keiran's profile also (he's on the fxp team)
http://forum.xda-developers.com/member.php?u=4344506
Oh, and the way I do it is: setttings>more..>mobile networks> Check data enabled off (wait 5sec) then check it back on. If that doesn't help then you can try a fresh install to see if it does anything
Click to expand...
Click to collapse
thanks for the quick fix. worst case scenario that isn't too inconvenient of a fix. i tried sending both of them a polite message, and we'll see if anything comes of it, though probably not.
Hey,
Although I'm not on FXP team anymore (working with AOKP now <3 unicorns haha) I looked into this issue once.
Any AOSP based ROM (CM, AOKP) for zeus and zeusc use prebuilt radio interface layer libraries, which is a problem, because the ones we are using in CM9 are gingerbread, not made for ICS.
I tried reverse engineering it once but I seriously need to work more on that kinda stuff
I'll tell jerpelea (FXP) of this issue and what he wants to do about it, its not really in my power now. Although if I do find a fix then I will be sure to push it to gerrit, regardless of FXP's opinion on the issue.
J is the only one I know with an R800x (he has whole 2011 line + S + P + x10)
Hope I could be of any help,
Keiran
KeiranFTW said:
Hey,
Although I'm not on FXP team anymore (working with AOKP now <3 unicorns haha) I looked into this issue once.
Any AOSP based ROM (CM, AOKP) for zeus and zeusc use prebuilt radio interface layer libraries, which is a problem, because the ones we are using in CM9 are gingerbread, not made for ICS.
I tried reverse engineering it once but I seriously need to work more on that kinda stuff
I'll tell jerpelea (FXP) of this issue and what he wants to do about it, its not really in my power now. Although if I do find a fix then I will be sure to push it to gerrit, regardless of FXP's opinion on the issue.
J is the only one I know with an R800x (he has whole 2011 line + S + P + x10)
Hope I could be of any help,
Keiran
Click to expand...
Click to collapse
Ah ok I can see the issue now, I honestly never even considered that. I deved on gb for many years and I'm still not use to ics yet lol. I seriously thank you for responding. From what I can tell gsm users don't have this issue (maybe they do but the ones I've talked to don't) and even though it's not major to me it'd be nice to be on the same level you know? Since you're on aokp I may jump onto that soon, but thanks again Keiran, I hope you stick with developing you got a knack for it that most people don't.
Hi all,
I've tried several passes at Google searching and haven't found these answers. I'm sure this community can help.
I've already rooted my Kindle Fire and put the stock JB ROM on there, good experience and it gave my KF new life.
So I am thinking about rooting and romming my T-Mobile Galaxy S3, but I have a few concerns and questions.
- What TMobile and Samsung features will I lose if I rom? Obviously for the most part none of their apps matter. But I heard that I would lose the ability to call/text over my Wifi connection, which would be a deal breaker considering the cellular connection quality in my house. Is that true? Are there any other features I might care about, that I'd lose?
- Will the face buttons on the S3 still work as they do now?
- Is the "Google Experience" ROM the same as the "stock" ROM? I heard about the "Google Experience ROM" on a podcast but cannot find this ROM in the forums.
- Anything else to consider? This is my first time rooting a phone - S3 was my first smart phone.
Thanks!
Dave
Just because you rooted, won't make you loose any of these features you do actually use. On the contrary you get to remove crap you don't care for. Without Root, your were previously prevented from removing some of the pre-installed apps.
Here's a good link for you to see what can be safely removed.
Now if you chose to install custom Rom, you stand to potentially loose Fabled Wi-Fi Calling. Face Unlock will still be there on other Roms.
Something else you need to know. There are 2 types of Roms. One that Samsung provides is called Touchwiz or TW Rom based on the framework of the same name. The others as you referred to as "Google Experience" Roms. These are commonly called as AOSP Roms. These roms don't have the Touchwiz framwork so won't support features such as Wi-Fi calling, since those only work on Touchwiz. There are other Non-Samsung Touchwiz roms. You will see a list of those and the AOSP Roms in my second link bellow for the Bible.
Since this is your First time on a Smart phone, here's few links you can read.
Welcome to your S3
Galaxy S3 Resource Bible
Hope this helps.
Please read ALL our sticky threads before doing anything to your device!
Sent from my SGH-T999 using Tapatalk
Thanks for the info. OK from your comments and the links you provided, I gather that any ROM that is a TouchWiz based ROM will still contain WiFi calling. Is that correct? So theoretically I could load one of these ROMs and still be good to go. I have a couple more questions though.
- I've seen a few references to "stock" ROMs. Does the term stock refer to the base Android build (so there is only one of these per release of Android), or does it refer to the software that came with each phone (so there is one per phone)? If it is the latter then would I be able to load the TMobile stock ROM if I did not like the custom ROM I chose?
- Also curious about TouchWiz in terms of Android architecture, which I am still learning about. I was under the impression this is some kind of loader or launcher specific to Samsung. I did not realize it would inherently contain Wifi calling. Does this layer also provide for the face buttons of the S3? What is TouchWiz specifically - a layer that sits on top of base Android? Trying to understand how this layer fits into the grand scheme, and are there comparable layers created by other manufacturers?
In any case, I guess I'm not getting AOSP or CM anytime soon. The TouchWiz ROMs are less-known so I am less inclined to chance it. At the very least I could root and get rid of some of these apps.
Thanks!
STOCK = base Android build from that Device's Manufacturer. So there's only one per Android Release.
Yes you can revert back to T-Mo Version if you don't like custom Roms.
(Small verbiage correction. We call Flashing a Rom not "Loading" a rom. This is to distinguish from system firmware such as Bootloader and Recovery.)
Touchwiz is a framework, that's specific to Samsung. Read here for more on Touchwiz and rest of your questions. It doesn't contain Wi-Fi calling but T-mo's feature of Wi-Fi calling needs to have this framework on your phone to work. There are other T-mo features such as Caller Name ID that needs this framework as well. What do you mean by Face buttons ? Face recognition ?
I had a question to tack on to OP's question, since it seems relevant here.
Ive noticed through looking at the "bible" stickied post that there seem to be 3 major types of roms: CM-based roms (roms that took CM10 code for the GS3 and used it to achieve AOSP compatibility, then rolled their own features), Rootbox based roms (dont know what this is or what it does), and Stock based roms.
Right now, I wanted to try out a Stock rom, as from my understanding, a Stock rom is one in which the developer starts with a stock firmware image from samsung, does things such as root, deodex, zipalign, debloat, etc, and then releases. The advantage of the stock rom, from my understanding, is that it is incredibly stable (assuming no kernel tweaks and similar) compared to the bugs we may experience on roms that are CM based.
I'm experiencing issues with CM roms that are not deal breakers by any means, but definitely make me want to look for greener (less buggy) pastures.
Is there a more up-to date version of the stock rom list? Is there a good way to search for stock-based roms?
shrimants said:
I had a question to tack on to OP's question, since it seems relevant here.
Ive noticed through looking at the "bible" stickied post that there seem to be 3 major types of roms: CM-based roms (roms that took CM10 code for the GS3 and used it to achieve AOSP compatibility, then rolled their own features), Rootbox based roms (dont know what this is or what it does), and Stock based roms.
Right now, I wanted to try out a Stock rom, as from my understanding, a Stock rom is one in which the developer starts with a stock firmware image from samsung, does things such as root, deodex, zipalign, debloat, etc, and then releases. The advantage of the stock rom, from my understanding, is that it is incredibly stable (assuming no kernel tweaks and similar) compared to the bugs we may experience on roms that are CM based.
I'm experiencing issues with CM roms that are not deal breakers by any means, but definitely make me want to look for greener (less buggy) pastures.
Is there a more up-to date version of the stock rom list? Is there a good way to search for stock-based roms?
Click to expand...
Click to collapse
All of the stock Touchwiz based roms are in Android Development, so start there. A dead giveaway is if a build number is in the title. For example if you see UVDMD5, or just MD5 in the title, it is based on the latest official release. Anything older is buried by now. We do have a couple of 4.3 leaked builds. UVUEMJ4 and UVUEMJC. MJC is the newest. Anyway, there is almost always a clue in the title. But if you are not sure, just open and look over the OP and screenshots.
Ill try to PM the OP of the list to see if he plans on updating it. I would not expect him to until after our next official release though, which is right around the corner. TBH, aside from a few roms, it should be pretty well up to date.
No I meant the lower left and lower right buttons on the face of the phone, the ones that light up on either side of the Home button.
OK so a custom TouchWiz ROM then may or may not contain the T-Mobile feature of Wifi Calling, since it is again a layer on top of TouchWiz? Just trying to make sure, because that is the single feature I am worried about retaining.
Thanks for the help!
Perseus71 said:
What do you mean by Face buttons ? Face recognition ?
Click to expand...
Click to collapse
squiddog said:
No I meant the lower left and lower right buttons on the face of the phone, the ones that light up on either side of the Home button.
Click to expand...
Click to collapse
What is your specific question regarding those lighted buttons? Do you want to remap them to make them do something other than what is intended or do you simply want to know if they work as advertised.
squiddog said:
OK so a custom TouchWiz ROM then may or may not contain the T-Mobile feature of Wifi Calling, since it is again a layer on top of TouchWiz? Just trying to make sure, because that is the single feature I am worried about retaining.
Thanks for the help!
Click to expand...
Click to collapse
Think of TWiz along the same lines as your KF. The Kindle (and Nook for that matter) uses Android as its base. Then it is skinned with features that Amazon (or B&N) think that you would like, overlay their own launchers, custom applications, locked bootloader ... Touchwiz is the very same thing. It is Samsung's version of what you have on your KF. An Android base with manufacturer's preferential skin and extra "goodies". Sense (HTC) and the now defunct Blur (Motorola) are other examples of this.
If you want Wifi Calling, then you should have no problem with any of the Touchwiz ROMs that are out there. Please note that Wifi Calling is not and will never be working on any AOSP ROMs.
***************
What I suggest is that your Root your phone, install a custom recovery, make sure that you back up your IMEI if you plan on going to and fro TWiz and AOSP. Before you flash anything, boot into your custom recovery and make a Nandroid backup of your ROM as it is right here and now. Then copy* that off your phone and put a copy on your PC. I say copy because you will want to leave one on your phone and one on your PC as a last resort backup (I still have mine from the ICS days). Then flash a ROM. Check it out for a few days. Not your cup of tea? Flash another. If something goes horribly wrong or you don't like some of the features of X ROM, then just restore your Nandroid that you made and you are right back where you started.
Yes I just noticed that the S3 had these buttons and many other phones do not. Therefore there is probably a TouchWiz requirement to get these buttons to work as advertised. The question is sort of moot now anyway - as I want a TouchWiz ROM.
Woody said:
What is your specific question regarding those lighted buttons? Do you want to remap them to make them do something other than what is intended or do you simply want to know if they work as advertised.
Click to expand...
Click to collapse
squiddog said:
Yes I just noticed that the S3 had these buttons and many other phones do not. Therefore there is probably a TouchWiz requirement to get these buttons to work as advertised. The question is sort of moot now anyway - as I want a TouchWiz ROM.
Click to expand...
Click to collapse
Yes I am aware you have decided to stick with Touchwiz roms. Just so you know, these two buttons work just fine in AOSP as well. In fact, on AOSP you have an option of assigning additional actions to Long Pressing of these two.