As the thread says I'm using Task's 10.5 AOKP build on my i777. I'm trying to listen to music in my car using the official Samsung car dock and Google Play Music. I've tried using the Settings->Device options->Dock->Use Dock USB Audio checked or unchecked but it didn't make a difference. Settings->System->Dock->Audio is always grayed out for me, even when docked.
I've posted in Task's thread but I expect it to get burried
Has anyone used any AOKP ICS/Jellybean ROM with a dock and gotten the audio to go out the USB port?
Thanks,
GFunk
This issue is not specific to the Galaxy S2 nor Task's ROMs, it seems this is common with ALL AOKP/AOSP/CM ROMs I don't know the specifics but I would guess that since these ROMs are based on original android source code and not off of ROMs written for the phone, there is no Samsung coding written in for the docks.
I have an S3 and would really like to get dock support for it too, but I'm not sure the mentioned ROMs will ever have support for it. You could always request it in the Rootwiki's (home of AOKP) website and see what they say.
Thanks, Risingsunn. I was starting to gather it was an AOSP issue. I was hoping it'd be some easy xml or sql setting that could be set from false to true or something similar. But I've been scouring with root explorer and haven't found anything promising. If it's ROM-based as opposed to Kernel-based I would expect it to be a setting rather than baked into a launcher or music app.
It's just interesting that there's a Dock Audio setting in the device options, and my phone goes into "Car Mode" when docked...but the audio never goes to the dock via the USB port. So I'm convincing myself it's a setting somewhere and will continue to dig .
Edit: Looks like they were playing with this issue over at CM:
https://github.com/CyanogenMod/android_frameworks_base/blob/e91a2373758b2302370c826b56cc022d2eb04b5d/services/java/com/android/server/WiredAccessoryObserver.java
If you search for "dock" you can run across a few instances where extra code was apparently added to be able to use dock audio on Samsung devices. I've never tried a CM ROM to see if this is actually implemented correctly, have you? You mentioned CM in your post, that's why I ask.
AOKP Dock Issues
Risingsunn said:
This issue is not specific to the Galaxy S2 nor Task's ROMs, it seems this is common with ALL AOKP/AOSP/CM ROMs I don't know the specifics but I would guess that since these ROMs are based on original android source code and not off of ROMs written for the phone, there is no Samsung coding written in for the docks.
I have an S3 and would really like to get dock support for it too, but I'm not sure the mentioned ROMs will ever have support for it. You could always request it in the Rootwiki's (home of AOKP) website and see what they say.
Click to expand...
Click to collapse
...AFAIK this is an issue only with AOKP based ROMs. :crying:
AOSP based ones don't have this problem; I have SlimRoms since version 2.7.0 (AOSP based) perfectly working with my docks...
Hope this clarifies the matter...
Related
I found a site that says they figured out how to get a PS3 controller working on Android devices. I found out that it is not compatible with my device with my current ROM. According to the page i was reading it says that cyanogenmod is compatible because it uses the bluetooth protocol that the program needs. As far a I know cyanogenmod is not available on the EVO 3D. I was wondering if there is a way to put the bluetooth protocol that cyanogenmod uses into one of the custom roms we have available. I do not know anything about creating ROM's but i am attempting to learn what i can.
The site i found is at Dancing Pixel Studios. can not post a link yet sorry
Well your going to need to change your roms source and since we don't have sense source its impossible. Unless you know what files cm uses for this Bluetooth protocol it should be as simple as drag and drop
Sent from my PG86100 using XDA App
On cyanogenmod barebones wiki page i only find two apk's that deal with bluetooth. they are Bluetooth.apk and MediaUploader.apk. would the bluetooth protocols be in the bluetooth.apk?
push !!!!!!!!!!
duke8804 said:
I found a site that says they figured out how to get a PS3 controller working on Android devices. I found out that it is not compatible with my device with my current ROM. According to the page i was reading it says that cyanogenmod is compatible because it uses the bluetooth protocol that the program needs. As far a I know cyanogenmod is not available on the EVO 3D. I was wondering if there is a way to put the bluetooth protocol that cyanogenmod uses into one of the custom roms we have available. I do not know anything about creating ROM's but i am attempting to learn what i can.
The site i found is at Dancing Pixel Studios. can not post a link yet sorry
Click to expand...
Click to collapse
You need aosp with those hid profiles in order for that to work. Wait for an official build of cm7. That will be exciting, all 17 buttons are remapable
Remember, Remember, the 5th of November. Thanks for support!
Hi all,
I have just installed lightning rom 2.5 and I have noticed that under both Phone and Contacts, there are missing tabs.
e.g.
Under Phone, the contacts tab is missing. I used to be able to slide to the right for more tabs.
How do I go about adding more tabs?
I tried searching but every time I add the word "tab" I get the Samsung Galaxy Tablet threads instead.
Also, under Security, the "SIM Change Alert" and "Remote controls" doesn't seem to be working, every time I tried checking the box, it freezes for awhile and then it says the setup has stopped working.
I wanted to post this in the lightning rom thread, but there's a 10 post restriction, and as such, I am posting here.
I hope someone can kindly help me.
Thanks in advance.
D
I don't know about remote control or sim change alert, but it is a well known change in ICS that those tabs are removed purposely, in their infinite wisdom. I don't agree with it, but it is what it is. One of the many reasons I'm staying on Gingerbread until find an overwhelming reason to go to ICS.
So if this ROM is ICS based, that's your answer.
ctomgee said:
I don't know about remote control or sim change alert, but it is a well known change in ICS that those tabs are removed purposely, in their infinite wisdom. I don't agree with it, but it is what it is. One of the many reasons I'm staying on Gingerbread until find an overwhelming reason to go to ICS.
So if this ROM is ICS based, that's your answer.
Click to expand...
Click to collapse
Ah ic, do you know if anyone has managed to enable these tabs again in ICS?
derrace said:
Ah ic, do you know if anyone has managed to enable these tabs again in ICS?
Click to expand...
Click to collapse
Not off the top of my head. Search for it.
ctomgee said:
Not off the top of my head. Search for it.
Click to expand...
Click to collapse
Ya, will do.
Interestingly enough, My Samsung Nexus S is on ICS as well, but it has contacts in the phone app.
derrace said:
Ya, will do.
Interestingly enough, My Samsung Nexus S is on ICS as well, but it has contacts in the phone app.
Click to expand...
Click to collapse
That's cause Nexus S is running AOSP android, and Galaxy S series (including the GS2) runs TouchWiz, which Samsung, in their infinite wisdom, have modded to their liking.
Edit to add: Lite'ning ROM is based on Samsung stock, so it uses the same system apps. This will hold true for any ROM based on Samsung stock, unless the ROM chef changes out specific apps, like the phone in this case.
ctomgee said:
That's cause Nexus S is running AOSP android, and Galaxy S series (including the GS2) runs TouchWiz, which Samsung, in their infinite wisdom, have modded to their liking.
Edit to add: Lite'ning ROM is based on Samsung stock, so it uses the same system apps. This will hold true for any ROM based on Samsung stock, unless the ROM chef changes out specific apps, like the phone in this case.
Click to expand...
Click to collapse
Thanks for the clarification. I am new to android and have been reading up on how to root/flash custom Rom on my TF201, SG2 and NS one by one. Took me several hours of reading and searching, but I have managed to get them all rooted/flashed without bricking any of them
This forum is loaded with heaps of info, but sometimes it's a bit hard to search for some specific stuff;the 10 post limitation on custom rom threads make it hard for me to ask for help from the author.
Just wondering... if S2's lite'ning ROM is based on Samsung stock (non AOSP), how do people change out specific apps?
derrace said:
Thanks for the clarification. I am new to android and have been reading up on how to root/flash custom Rom on my TF201, SG2 and NS one by one. Took me several hours of reading and searching, but I have managed to get them all rooted/flashed without bricking any of them
This forum is loaded with heaps of info, but sometimes it's a bit hard to search for some specific stuff;the 10 post limitation on custom rom threads make it hard for me to ask for help from the author.
Just wondering... if S2's lite'ning ROM is based on Samsung stock (non AOSP), how do people change out specific apps?
Click to expand...
Click to collapse
You need to be rooted, and you replace certain apk files in the /system/app folder. But you need to be certain to use files compatible with your particular build of Android.
Remote controls
derrace said:
Hi all,
Also, under Security, the "SIM Change Alert" and "Remote controls" doesn't seem to be working, every time I tried checking the box, it freezes for awhile and then it says the setup has stopped working.
D
Click to expand...
Click to collapse
I also had this problem. Found the fix on the Litening rom forum under Problems and questions.
I would link the page to you but since i am a new user, i am unable to lol.
Basically there is a zip file that u can flash which lets u add a samsung account and enables the remote settings features. ive tried it on litening rom 2.5 and it worked for me
dsingh300 said:
I also had this problem. Found the fix on the Litening rom forum under Problems and questions.
I would link the page to you but since i am a new user, i am unable to lol.
Basically there is a zip file that u can flash which lets u add a samsung account and enables the remote settings features. ive tried it on litening rom 2.5 and it worked for me
Click to expand...
Click to collapse
Ah, cool, thanks for the link.
Going to flash to 2.7 first. I hope I don't have to do clear it to factor settings again.
So I've been searching the development thread for the best ICS build for an extended trip that's going to require longer battery life. My daily driver is CM10 from epinter, and while it's a great ROM, it has some battery life issues, especially how I use it (heavy streaming music coupled with Nav use). So for the past week, I've been playing with various ROMs from from other developers, and the stuff coming from Th3Bill seems to be head and shoulders above the rest, with one caveat. I can't get Google Search to work on ANY of his ROMs that I've tried. More specifically, whenever I launch Google Search (to access Now and the info cards), it immediately shuts down, on both Liquid Smooth as well as the MIUI port that he hosts. While it's not a deal breaker, Search does work on epinter's ROM, and it's one of those features that I've really grown to utilize a lot. I've done the requisite searching, but I'm not finding anything that points to a way to resolve this issue (which probably means that I'm searching incorrectly). Is this a standard issue with Google Search? Does anyone have any recommendations about how to resolve the issue? Thanks for your help.
BigdogBTS (loooooongtime lurker, infrequent poster)
bigdogbts said:
So I've been searching the development thread for the best ICS build for an extended trip that's going to require longer battery life. My daily driver is CM10 from epinter, and while it's a great ROM, it has some battery life issues, especially how I use it (heavy streaming music coupled with Nav use). So for the past week, I've been playing with various ROMs from from other developers, and the stuff coming from Th3Bill seems to be head and shoulders above the rest, with one caveat. I can't get Google Search to work on ANY of his ROMs that I've tried. More specifically, whenever I launch Google Search (to access Now and the info cards), it immediately shuts down, on both Liquid Smooth as well as the MIUI port that he hosts. While it's not a deal breaker, Search does work on epinter's ROM, and it's one of those features that I've really grown to utilize a lot. I've done the requisite searching, but I'm not finding anything that points to a way to resolve this issue (which probably means that I'm searching incorrectly). Is this a standard issue with Google Search? Does anyone have any recommendations about how to resolve the issue? Thanks for your help.
BigdogBTS (loooooongtime lurker, infrequent poster)
Click to expand...
Click to collapse
What works on the Th3Bill's CM10 based Photon Roms is to go into your System Settings/Language & Input. Go to the bottom and click on Voice Search and uncheck "Hotword Detection". That should fix you up.
In the unlikely case that doesn't work, you'll need an older version of the Search .apk.
runningslow said:
What works on the Th3Bill's CM10 based Photon Roms is to go into your System Settings/Language & Input. Go to the bottom and click on Voice Search and uncheck "Hotword Detection". That should fix you up.
In the unlikely case that doesn't work, you'll need an older version of the Search .apk.
Click to expand...
Click to collapse
This advice was right on the nose. Hotword Detection was borking the whole thing up. Much appreciated. :good:
I just recently started using custom roms thanks to a friend of mine. I'm currently using Cyanogenmod, I believe the most recent one (flashed to the one released today) but I noticed a few things were missing. The biggest concern of mine is that I don't seem to have Google Now on my phone, and I seem to have lost S-Voice (which I assume Google Now replaces). Voice search also doesn't seem to be working either. Whenever I try using voice search, it immediately crashes. Lastly, I don't get 4g HSPA+ anymore. I'm not in an LTE area but we do get H+ here. I noticed that I am on 3g all the time. Just wondering if there were any fixes for these problems. Not a huge issue, just an inconvenience I'd like to see fixed if possible.
adambueller said:
I just recently started using custom roms thanks to a friend of mine. I'm currently using Cyanogenmod, I believe the most recent one (flashed to the one released today) but I noticed a few things were missing. The biggest concern of mine is that I don't seem to have Google Now on my phone, and I seem to have lost S-Voice (which I assume Google Now replaces). Voice search also doesn't seem to be working either. Whenever I try using voice search, it immediately crashes. Lastly, I don't get 4g HSPA+ anymore. I'm not in an LTE area but we do get H+ here. I noticed that I am on 3g all the time. Just wondering if there were any fixes for these problems. Not a huge issue, just an inconvenience I'd like to see fixed if possible.
Click to expand...
Click to collapse
Cyanogenmod has a discussion thread in the general section.
http://forum.xda-developers.com/showthread.php?t=2035141
you're best to go there and ask - but before you do, a quote from the cm10.1 thread you downloaded the rom from
- Camera: Recording effects broken
- Camera: Touch 2 focus issues with enabled flashlight
- Bluetooth: audio streaming sometimes becomes laggy or stops at a distance > 1m
- FM Radio: unsupported
- TV Out: unsupported, will never work (proprietary, undocumented)
- Lots of missing and yet unimplemented features
- and a lot more
these are known issues.
Actually we have two kind of roms. Based on Stock Samsung Rom and based on AOSP (Android Open Source Project). It isn't the same and AOSP roms mostly are missing much things added by Samsung, for example Smart Stay, Samsung Apps etc. CyanogenMod is based on AOSP.
If you ask me I'd stick with roms based on Samsung, mostly because I believe it's much more compatible than "clean" AOSP itself. But it's up to you, I'd suggest flashing some stock rom (f.e. Android Revolution HD) and make a decision which one you prefer.
JustArchi said:
Actually we have two kind of roms. Based on Stock Samsung Rom and based on AOSP (Android Open Source Project). It isn't the same and AOSP roms mostly are missing much things added by Samsung, for example Smart Stay, Samsung Apps etc. CyanogenMod is based on AOSP.
If you ask me I'd stick with roms based on Samsung, mostly because I believe it's much more compatible than "clean" AOSP itself. But it's up to you, I'd suggest flashing some stock rom (f.e. Android Revolution HD) and make a decision which one you prefer.
Click to expand...
Click to collapse
I'll try the Android Revolution rom and I'll try posting in the Cyanogenmod forum. Thank you for the information everyone.
R: [Q] New to using custom roms, couple of questions
adambueller said:
I'll try the Android Revolution rom and I'll try posting in the Cyanogenmod forum. Thank you for the information everyone.
Click to expand...
Click to collapse
Might i suggest you look into other top roms as well....after all, as long as you got a nandroid backup u can flash roms in a jiffy!
foxhound rom(most packed rom you can find!)
Rootbox(some nifty features plus it's very light and handles performance very well. Was also a very speedy performance rom on the s2)
Sent from my GT-I9300 using xda app-developers app
adambueller said:
I'll try the Android Revolution rom and I'll try posting in the Cyanogenmod forum. Thank you for the information everyone.
Click to expand...
Click to collapse
You can use other roms AOSP like
MIUI http://forum.xda-developers.com/showthread.php?t=1859716 (I'm using this one, it's beautifull and super smooth)
Vanilla RootBox: http://forum.xda-developers.com/showthread.php?t=1898798
Or Samsung based like
UltimaROM http://forum.xda-developers.com/showthread.php?t=1911572
Omega http://forum.xda-developers.com/showthread.php?t=1663656
R: [Q] New to using custom roms, couple of questions
jmlugo90 said:
MIUI http://forum.xda-developers.com/showthread.php?t=1859716 (I'm using this one, it's beautifull and super smooth)
Click to expand...
Click to collapse
I agree on the others, but i HAVE to disagree on the ios looking pretty-not rom miui. It's not that beautiful....:sigh: i never will get miui fans...
Sent from my GT-I9300 using xda app-developers app
I bought two Kenzos, one normal and one "Prime". On the first one I installed Mokee, that's the daily driver for my wife. On the second one I tried some ROMs, and I got two bugs that are annoying to me. If some of you would please try to reproduce them, so that we know for sure that they are bugs and report them. I have tested on "ResurrectionRemix-M-v5.7.3-20160807" and "aicp_kenzo_mm-11.0-NIGHTLY-20160812", both of them first with stock kernel and after that with "Radon-V2.1-Kenzo".
1. Kenzo has a magnetic switch, for the "smart covers" to put the phone to sleep when the flip-cover is closed and wake it up when it opens. It works on Mokee, but it doesn't work neither on RR nor AICP. If you don't have a Smart Cover you can use two small (and not powerful!) magnets. In the attached picture I have marked the zone where the two magnets in the cover are. If you put your two magnets floating over the screen (without touching it, use eventually some paper) in the corresponding area (~1 and 2 centimeters below the camera) the screen should go off, and if you remove them the screen should go on. I've looked at the live logs, and in RR and AICP no events are triggered, but they appear under Mokee ("PowerManagerService( 1261): Going to sleep due to lid switch (uid 1000)... ", etc). I have attached the logs in flip2016-08-13_23.05.zip.
2. I noticed that under RR and AICP I can not access the phone trough ADB. I can switch it to MTP mode, I see it, I can transfer files, but after switching to USB debugging "adb devices" gives me no device, and in the Device Manager I have only a unknown device. In fastboot mode it's woking. I don't think it's a driver issue, because under Mokee it's working as expected. I've attached logs captured under AICP with the Radon kernel.
3. Under Settings -> Security, check "Unknown sources", exit, and go again. The setting is not saved.
Off-topic: why isn't the Ambient Display working as expected? I remember that my former MotoE under CM12 got waked up when I took it out of my pocket, and so was the MotoG under CM13. Why can Kenzo do the same thing?
Flip Covers do not work with most Custom ROMs. It may be a driver issue or maybe just the code is missing. So, if you really want that to work, you can make a request to the maintainer of your favourite Custom ROM to add support for flip covers or simply you can use those ROMs that do have support for them.
For the ADB missing device, force your "unknown device" in Device Manager to update drivers and it should work fine from thereon. I have faced this many number of times on many different devices. ADB drivers, once installed, would work fine while the phone is on one ROM but would display as "unknown device" once the ROM is changed on the phone. Thankfully, updating drivers for that device almost always does the trick.
In the meantime I've tested also the official CM13 Nightly (without Radon). As, for what I know, RR and AICP are CM-based, and I thought the problems could originate from there. And they are, under CM13 the behavior is the same.
ayush3051 said:
Flip Covers do not work with most Custom ROMs.
Click to expand...
Click to collapse
But it works under CM13 (and should work on ROMs based on it), just on other devices, not on Kenzo - just tested it on a Falcon and it works. The feature is there, it should work.
ayush3051 said:
For the ADB missing device
Click to expand...
Click to collapse
I see in your profile that you own a Kenzo. If you have any of the above ROMs please try to reproduce the adb and unknown sources issues and post your results.
Best regards.
paul_damian said:
In the meantime I've tested also the official CM13 Nightly (without Radon). As, for what I know, RR and AICP are CM-based, and I thought the problems could originate from there. And they are, under CM13 the behavior is the same.
But it works under CM13 (and should work on ROMs based on it), just on other devices, not on Kenzo - just tested it on a Falcon and it works. The feature is there, it should work.
I see in your profile that you own a Kenzo. If you have any of the above ROMs please try to reproduce the adb and unknown sources issues and post your results.
Best regards.
Click to expand...
Click to collapse
Hi,
Most likely the code to have that feature is not yet included because of the custom roms are CM based including AICP and RR and the CM's official build for Kenzo just got out. A lot of devs will test and keep working on it. Meanwhile you can submit a request to CM via their site and they will include it or post it on the CM thread by the The Strix.
last but not the least use an app from the play store they surely do work in most of the cases.
Thank you for your reply, dwaipayanray95. I wanted first to have confirmation that these are really bugs, before submitting them. That's why I asked other users for help. I've tested them on CM13 only last night, I think that I will post them on TheStrix's thread.
paul_damian said:
In the meantime I've tested also the official CM13 Nightly (without Radon). As, for what I know, RR and AICP are CM-based, and I thought the problems could originate from there. And they are, under CM13 the behavior is the same.
But it works under CM13 (and should work on ROMs based on it), just on other devices, not on Kenzo - just tested it on a Falcon and it works. The feature is there, it should work.
I see in your profile that you own a Kenzo. If you have any of the above ROMs please try to reproduce the adb and unknown sources issues and post your results.
Best regards.
Click to expand...
Click to collapse
I could have tested it, but I am travelling for the next 30 or so days. So I cannot really test a new ROM like right now. I will be happy to do so once I reach home back, though I should tell you that I do not personally own a Flip Cover or have at my hands any small magnets.
But the thing is, even though the ROMs are CM based, they do not incorporate the whole CM base and hence are not capable of doing everything the base ROM does. Hope you understand this. On the other hand, the derived ROM may have some other feature which is not even present in the base ROM.
Let me give you an example in terms of AICP and RR, themselves.
Both AICP and RR do not implement CM's onscreen Navigation Bar, instead they have opted for DUI with pulse(which I personally love).
Similar may have been the case with the Flip cover code. If you want to you can make a device specific request at AICP and RR's Google+ pages. The developers are quite active there and can guide you much better than I can.
Regards and Thanks
If you still face the unkown device adb problem install the adb driver installer its around 9 mb.it can install drivers for all phones but you will have to disable driver signature enforcement in windows first.you will be good to go by this
and can i have proxisensor flip cover? cause i use a normal one not the official plastic one. i only want flip cover where the phone is in a tpu case. but its kinda anoying that the screen doesnt turn off. and i have tried some apps but they use more battery then they help...
First one isn't working in the most roms i tried which are commonly used some features of CM/Lineage, the second one you are also right. I had to remove RR so I can't check the third one, hope to solve my problems soon because I miss my RR
these issues are also not in aosp extended. but has in most of lineage based roms.