Related
Hey,
because my internal GPS doesn't work anymore I bought a external GPS reciver for navigation.
In CM9 there was a option to select an external GPS source in the location options menu.
Is this feature coming to CM10 anytime soon?
I'm currently running *804 vers. of Pawitps CM10 Alpha.
Or is there an app that could help me?
Thank you in advance
Sauerbraten
I might come, check the development section thread and the CM10 change log for it:
http://changelog.bbqdroid.org/#/cm10/galaxysmtd
You can see the current list of issues here:
http://code.google.com/p/sgscm10/issues/list
Check for Bluetooth GPS provider - it was working for me well before we got the "external GPS source" in CM9.
Sent from my GT-I9000 using xda app-developers app
Thank you very much.
I'm going to try the app
j0ep0 and I are currently working to get the mirroring that we were promised working with Drivelink and the Galaxy S III. Currently we have mirroring working successfully but there are a few bugs with the Drivelink app getting wiped and restarted. Here is a list of everything so far:
Full Mirroring without the drive link app resurfacing - Working (random restarts due to memory cleanup in android)
Work with Any Launcher - Currently Nova and Apex work
Reassigning the Home button -
Bypassing the two warning Messages -
Compatibility with Non-touchwiz Roms-
Compatibility with Other Devices -
Dim or turn off Phone screen when mirroring-
Automatically go into launcher (minimizing drivelink) -
Currently the setup we have is working for the following devices:
GSM Galaxy S III
CDMA Galaxy S III (No Data)
If it is working on your device please post, or PM me with the Following:
Carrier
Phone Model
Any Bugs
Rom/Kernel (If custom)
Installation Instructions:
Code:
Non-root:
Go into Settings and Enable "Install from Unknown sources"
Install the APK and run it.
Plug into your head unit and pray.
This method has worked for some (including myself) and not for others.
It will give you the standard Drivelink app and
no custom code by us, you need root for that.
Rooted users:
Download the TMServer zip to your Phone
Reboot into recovery and install (Like a ROM)
No need to wipe anything, you're just replacing
a system APK which is why you need root.
Install the Drivelink APK after enabling Unknown sources.
Run the Drivelink app and plug your phone into the head unit,
After accepting prompts you should see the drive link app.
There are several ways to get to your stock home screen but the easiest for me is to hold your home button down the bring up task manager, Click on another open app, when it opens hit the home button and viola, you're at your home screen. We are trying to find a way to bypass this but drivelink puts the phone into car mode and that disables the home button. Car mode is required to get the audio to route correctly to the head unit.
Here are the Links:
TM Server- Must be flashed in a custom recovery:
TMServer
Drivelink- Remove all versions, allow unknown sources and install this apk:
DriveLink
Both j0ep0 and myself have full time jobs and families so we are working very hard to get this working on our own time. So please be patient. We will get this working fully!
Nice description write up by Olywa123, Thanks
What is it
Drivelink is Samsung's application used to facilitate ‘Mirrorlink’ connectivity with supported car headunits. Currently their are several aftermarket car stereos by Sony, Alpine, and JVC that support this technology. The majority of users here have the Sony XAV-601BT headunit but it is believed the protocol for connection is the same for each. This standard is known as Mirrorlink (formerly Terminal Mode) and uses the VNC RFB3.8 protocol allowing for two-way communication between the smartphone and headunit over a usb connection for both display duplication and key-inputs and uses Bluetooth A2DP for Audio.
Videos
The following videos best provide a summary of this technology
Mirrorlink Overview: http://www.youtube.com/watch?v=sWNpK...eature=related
Example of MirrorLink on XAV-601BT: http://www.youtube.com/watch?v=BsT1l8bLOfU (shows Nokia and Samsung phone support)
Example of Drivelink App: http://www.youtube.com/watch?v=CHVmogapY9U
Why The Drive Link App needs Modification
Although Samsung have released the Drivelink application, this is not only very limited but also compatible only with the Galaxy SIII currently. It provides a ‘dashboard’ interface allowing for the use of only stock Music, Phone and Navigation (limited to Google maps) functionality. You cannot get back to your phones home screen or run any other apps while Drivelink is running/mirrored on the headunit and killing Drivelink kills the interface meaning the stereo no longer sees and mirrors the phones display. This appears to be a restriction coded into the Drivelink software as the video above shows that the Nokia interface allows for full phone control in addition to just the Nokia released Mirrorlink app on Symbian (Car Mode).
what is this actually
Sent from my GT-I9300 using xda premium
I haven't been following my other thread lately but you mention here you have CDMA version working without data. I'm in verizon gs3. How do I get this baby running even without data? I tried flashing that tmservice.zip abiut a week ago with no luck. Is this one a revised version ? I will try again anyways thanks
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
kp.nikhil said:
what is this actually
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Something like this. Except the goal here is to have full mirroring of the launcher and everything that's on the phone http://www.youtube.com/watch?v=CHVmogapY9U&feature=youtube_gdata_player
Sent from my SCH-I535 using xda app-developers app
Checking in for updates as the U.S. siii gets more progress (especially with cm10).
Verizon galaxy SIII with CM10 nightlies, and this is my result.
Updated OP with more information
Question... do you have to flash tmserver if you are using a rooted touchwiz rom?
Sent from my DROID3 using Tapatalk 2
If you use Touchwiz based Rom, first check in /system/tmserverapp.apk exists. If it is there, just install the DriveLink apk. If it's not, install this TMServer: http://www.mediafire.com/download.php?3926b2kuewyn84i.
(the one in OP is a test version).
So can I use Sony XAV601BT with a Verizon running CM10 nightly on 4.1.2
Sent from my SCH-I535 using xda app-developers app
Drive Link works on CM10, but the screen mirroring app doesn't.
3 weeks or so and I should have my Verizon Note 2 and will be back in this for some testing. assuming it doesnt just work right off.
it works! thanks!
but if I run Temple Run game, the USB link will fail.
I guess the memory killer may kill the tm server that cause USB link fail.
BTW,
I remember the USB link requires the CDC/NCM support in kernel or the mirrorlink cannot be activated, correct?
chinlin0924 said:
it works! thanks!
but if I run Temple Run game, the USB link will fail.
I guess the memory killer may kill the tm server that cause USB link fail.
BTW,
I remember the USB link requires the CDC/NCM support in kernel or the mirrorlink cannot be activated, correct?
Click to expand...
Click to collapse
What phone, carrier, rom are you using?
Sent from my SCH-I535 using xda app-developers app
Eureka!
Installed the DriveLink APK from the first post.
Carrier: Verizon
Phone Model: Samsung Galaxy SIII SCH-I535
Any Bugs: None that I could tell. I only played with it lightly for 15 minutes
Rom/Kernel: JellyWiz Stock [VZW LEAK] http://forum.xda-developers.com/showthread.php?t=1853337
Results:
So what does the leaked VZW have that CM10 doesn't? Because I can't stand TouchWiz anymore after months with CM10.
mrjoshzombie said:
Eureka!
So what does the leaked VZW have that CM10 doesn't? Because I can't stand TouchWiz anymore after months with CM10.
Click to expand...
Click to collapse
Nice to see that my mod is working for you
You're answering your own question, VZW is Samung based and has the Touchwiz framework. You can always switch launcher to Trebuchet or Nova to get a less "Touchwiz" sensation.
mrjoshzombie said:
Eureka!
Installed the DriveLink APK from the first post.
Carrier: Verizon
Phone Model: Samsung Galaxy SIII SCH-I535
Any Bugs: None that I could tell. I only played with it lightly for 15 minutes
Rom/Kernel: JellyWiz Stock [VZW LEAK] http://forum.xda-developers.com/showthread.php?t=1853337
Results:
So what does the leaked VZW have that CM10 doesn't? Because I can't stand TouchWiz anymore after months with CM10.
Click to expand...
Click to collapse
Strange... there must be something with that rom. I could never get my VZ S3 to work, but i never tried a jellybean rom.
read the sony thread. seems the device authentication is by key. i'm assuming the mysterious device identifier component is in that key. but i'm also assuming that the key code is closed on both the client and server. but just wondering if you've looked at that yet, j0e0p? if i recall you don't even have the deck?
shirazdindar said:
read the sony thread. seems the device authentication is by key. i'm assuming the mysterious device identifier component is in that key. but i'm also assuming that the key code is closed on both the client and server. but just wondering if you've looked at that yet, j0e0p? if i recall you don't even have the deck?
Click to expand...
Click to collapse
To do a little braindump, I've checked in /system/security/security/cacerts but can't find much differences between the several ROMs. In the code of the Drive Link app there are some checks in build.prop to identify the device but if that's really restricted the app shouldn't work on the Verizon as that device id isn't in the code. Finally I've found some references to the bootloader/kernel. That might be the cause.
I don't have the deck, the keying part isn't published in the source code from Sony and mirrorlink doesn't seem to be working on the latest XXDLJ4 (rooted) for i9300 which I'm running as my daily driver. Maybe someone could confirm that?
j0ep0 said:
To do a little braindump, I've checked in /system/security/security/cacerts but can't find much differences between the several ROMs. In the code of the Drive Link app there are some checks in build.prop to identify the device but if that's really restricted the app shouldn't work on the Verizon as that device id isn't in the code. Finally I've found some references to the bootloader/kernel. That might be the cause.
I don't have the deck, the keying part isn't published in the source code from Sony and mirrorlink doesn't seem to be working on the latest XXDLJ4 (rooted) for i9300 which I'm running as my daily driver. Maybe someone could confirm that?
Click to expand...
Click to collapse
I'm on xxdlj4 rooted as well and my works and connects perfectly.
Sent from my GT-I9300 using xda app-developers app
Is it possible to pull the framework from JellyWiz and insert it into CM10?
Unofficial, no warranty, express or implied. Not final, nothing to do with the CM people, not backed by them, not made by them, may cause corruption of innocent kittens if used irresponsibly. I am posting this only because the main CM sources are not perfect right now for building for Qualcomm devices just yet, and need some tweaks in new branches.
CM 10.2 Android 4.3 built for, and working on Pollux_Windy, once again thanks to Sony using such nice, open-source-friendly devices.
Working:
WiFi
Compass + sensors
Sound
Bluetooth
Front + Rear Camera
External SD (including ExFAT)
Not Working:
GPS
This is for the Pollux_Windy (SGP311) Wifi ONLY tablet. It should work on the SGP312 (32 GB wifi only) as well, but will NOT work on the Pollux (with LTE).
http://goo.im/devs/pulser/TabletZSGP311/CM10.2/cm-10.2-20130810-UNOFFICIAL-pollux_windy.zip
Tried to flash this but i'm getting an error about device build prop not matching requirements. I had a 312 rom on first, and flashed a 311 stock rom, but still get the error. My device is 311 by default.
Do i need to edit my build.prop? Even though my device shows as SGP311?
EDIT: Ah nevermind, i had the stock bootloader still installed. Doh!
If anyone needs Gapps I found them here:
http://forum.xda-developers.com/showthread.php?t=2378992
Sent from my SGP311 using xda app-developers app
Updated to 30 July build - includes the new Focal camera app. Yes, it has a few bugs with tablets and orientation. It's known.
Is root possible yet? I tried the supersu zip that was attached in op, but still needs the binary according to the supersu app. Do we need to adb push the binary?
Edit: Nevermind, just tried the latest supersu and works fine.
I can't get a restricted user to work for the life of me. All kinds of processes are force stopping and I couldn't pick trebuchet from the list on setup either, though I did manage to work around that with Apex eventually, though Apex kept crashing too.
I assume apps might have to support this (or at least launchers?) But core processes?
I did dirty flash so it's possible that has something to do with it.
Still digging around. I'll clean flash later to retry restricted users too.
C
cjdalessio said:
I can't get a restricted user to work for the life of me. All kinds of processes are force stopping and I couldn't pick trebuchet from the list on setup either, though I did manage to work around that with Apex eventually, though Apex kept crashing too.
I assume apps might have to support this (or at least launchers?) But core processes?
I did dirty flash so it's possible that has something to do with it.
Still digging around. I'll clean flash later to retry restricted users too.
C
Click to expand...
Click to collapse
Restricted profiles are not tested or a priority right now in CM I believe.
Got this working on my xtz SGP311 seems really quick so far recovery plays nice, only real issues I've encountered is that the screen flickers black every now and then using the aosp browser and MX player pro doesn't work as android 4.3 isn't supported yet which has nothing to do with the rom.
WiFi and GPS seem to working used google maps to find a location and navigate there had no issues with those yet.
Definitely something different over the Sony ui and less cluttered just need the sony remote
Gonna have a play with it and see how I get on with it lots of options to play with hehe
Sent from my SGP311 using XDA Premium HD app
andymg350 said:
Got this working on my xtz SGP311 seems really quick so far recovery plays nice, only real issues I've encountered is that the screen flickers black every now and then using the aosp browser and MX player pro doesn't work as android 4.3 isn't supported yet which has nothing to do with the rom.
WiFi and GPS seem to working used google maps to find a location and navigate there had no issues with those yet.
Definitely something different over the Sony ui and less cluttered just need the sony remote
Gonna have a play with it and see how I get on with it lots of options to play with hehe
Sent from my SGP311 using XDA Premium HD app
Click to expand...
Click to collapse
Check out the project by @Apache14 that brings infrared remote control support to non Sony ROMs!
Are you sure gps is working? I don't think it should be in this ROM...
I had a go at the open source IR by apache but had no luck getting it to work, but I'm not sure if I installed it right.
I'll have another play with GPS today as I've got more time and let you know I could have jumped the gun on this one lol. I quickly downloaded an app called GPS test and although it says the GPS is on it doesn't show anything else like coordinates or location I'll keep playing for now though.
Sent from my SGP311 using XDA Premium HD app
Updated 3rd August
Updated 7th August.
Thanks a lot for throwing this together... everything seems to be working great, I'm impressed by focal.
I'm still struggling with is the absence of tablet UI (trying to hit the home softkey in landscape is impossible, so I've been forced to full!screen, which is working well), but it's a small price to pay for the jump from Sony's 4.1.2 to a functional 4.3 Rom.
zylstrajs said:
Thanks a lot for throwing this together... everything seems to be working great, I'm impressed by focal.
I'm still struggling with is the absence of tablet UI (trying to hit the home softkey in landscape is impossible, so I've been forced to full!screen, which is working well), but it's a small price to pay for the jump from Sony's 4.1.2 to a functional 4.3 Rom.
Click to expand...
Click to collapse
Interesting. Out of interest, how do you use your tablet ? I'm just trying to work out if there is any link or difference - personally I thought the same, that tablet was good, until I used my Nexus 10... Then I was "sold" - tablet UI was sub-optimal. I tend to use the tablet with 2 hands - one holding it, another free across the top for use. I find keeping navigation to the centre more logical personally, and more ergonomic. It also keeps the notification tray at the top, consistent with the phone. At other times, I use the tablet as a "monitor" and type with a Bluetooth keyboard, where I do not interact with the touchscreen much (except at arm's length), and find phablet UI quite convenient. Moreso than I felt with tablet UI.
It's intriguing though. I am sure I can look at readding it some time, but I'm fairly busy so it will take a while. I noticed Sony seem to be moving to phablet UI for 4.2 as well though...
I hold mine on the sides and mostly interact with my thumbs, thus central on screen controls are hard to reach. But, to each his own. I also use Thumb Keyboard exclusively on my tablets, much more natural than trying to type with one hand holding with the other.
so yeah i finally got around to testing the GPS navigation and it just says "Searching for GPS" the whole time so confirmed its not working.
i also found a issue with the swipe to type on the AOSP keyboard as soon as i tried to use swiping it force closed the keyboard, not a big issue just thought id mention it.
i noticed you've done a couple of updates as well whats the best way to update the rom just flash as usual using the file in op?
andymg350 said:
so yeah i finally got around to testing the GPS navigation and it just says "Searching for GPS" the whole time so confirmed its not working.
i also found a issue with the swipe to type on the AOSP keyboard as soon as i tried to use swiping it force closed the keyboard, not a big issue just thought id mention it.
i noticed you've done a couple of updates as well whats the best way to update the rom just flash as usual using the file in op?
Click to expand...
Click to collapse
Just like with CM nightlies, just flash the latest update right over whatever you have.
In rare cases other changes will be needed, maintainers will usually let you know in these cases.
I'm investigating GPS on 10.1 on the windy - it's proving to be a bit of a headscratcher, although it has many of the hallmarks of the same problem we had with the modem on mint (Xperia T) months ago. Unfortunately, we can't use the same fix/workaround we used on mint.
pulser, may want to check the CM10.1 thread for my SMD debugging patch, might give some useful info - although what I need to do is get a build environment together for stock kernels so I can apply that patch to .370 for comparison.
i hate to sound like a noob but i am still learning lol is it safe to just flash the updates with cwm or is it best to do it with the flash tool?
it seems like gps has got a lot of people scratching their heads at the moment but im sure with so many looking into it there is sure to be a solution soon
Edit: its OK I went ahead and flashed the update using cwm and it worked, I'm to impatient to wait lol but at least I've learned something
Updated to 10th August build
Will you continue to tweak now that official nightlies are out?
Hello there!
Anybody knows, if it is possible to configure the HTC One to connect to Cisco LEAP WiFi network? (EAP 802.11x security).
I read that Android has a general problem with it, but there is a workaround for rooted users, unfortunately nobody mentioned details (except for some wifi_supplicant file).
Do you have any ideas how to resolve this issue?
I'm rooted of course.
Thanks!
davebugyi said:
Hello there!
Anybody knows, if it is possible to configure the HTC One to connect to Cisco LEAP WiFi network? (EAP 802.11x security).
I read that Android has a general problem with it, but there is a workaround for rooted users, unfortunately nobody mentioned details (except for some wifi_supplicant file).
Do you have any ideas how to resolve this issue?
I'm rooted of course.
Thanks!
Click to expand...
Click to collapse
If you're on Android 4.2.2 (I'm on AOKP 4.2.2 for Nexus 4) then Advanced LEAP Wifi from the Play Store works just fine. However, the same app does not work on Android 4.3 - It force closes.
I have not tested this myself but it seems possible to edit the wifi_supplicant.conf file and be done with it, but to do that you must be rooted. If you're also a fellow IBMer, send me a PM and we can continue this over Sametime
Quiksilver78 said:
If you're on Android 4.2.2 (I'm on AOKP 4.2.2 for Nexus 4) then Advanced LEAP Wifi from the Play Store works just fine. However, the same app does not work on Android 4.3 - It force closes.
I have not tested this myself but it seems possible to edit the wifi_supplicant.conf file and be done with it, but to do that you must be rooted. If you're also a fellow IBMer, send me a PM and we can continue this over Sametime
Click to expand...
Click to collapse
Great to see that a fellow IBMer saw this post I sent a PM just now. I hope there can be something done in this issue. :good:
Hey guys Dave Here,
I'm trying to find a Screen Recorder that works for the Sprint HTC One. All of the apps I've tried that are free on the play store are not working for my phone. I can give more details about my run and so forth but I've done it on a different roms and versions of android to still have the same issues. If you know of a fix or an app that you use please let me know. Thanks for your help.
ssdave said:
Hey guys Dave Here,
I'm trying to find a Screen Recorder that works for the Sprint HTC One. All of the apps I've tried that are free on the play store are not working for my phone. I can give more details about my run and so forth but I've done it on a different roms and versions of android to still have the same issues. If you know of a fix or an app that you use please let me know. Thanks for your help.
Click to expand...
Click to collapse
What does it do when u try to record?
Sent from my HTCONE using xda premium
luigi311 said:
What does it do when u try to record?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
SCR Screen Recorder Free - gives me an error 139 (I think) each time I ran it. I've changed every setting I could and if it didn't give me that error it gave me another.
Screen Recorder Trial - It would save it in a format that was unable to view on the device or my windows 8 laptop (says its mp4)
Z screen recorder - Does record but the video is very very blurry with multiple colors and no options to adjust it.
So is it just me or are others having the same issue with their HTC one?
Screen cast worked on my HTC One..Never tried it since the 4.3 update because i moved on to a different device.
i believe i had to Make sure HW Overlay is disabled and "Force GPU Rendering" is enabled from the device's developer options menu
https://play.google.com/store/apps/details?id=com.ms.screencastfree&hl=en