Hi there. Been using the Z3C all week and really enjoying it, but I've found one persistent problem with one of the built-in apps and am hoping someone here might be able to point me in the right direction for getting a fix.
I'm unable to get the Live On YouTube camera app (v 01.00.21) to sign in to my Google account. Firing up the app, I get the page requiring me to read and accept the terms and conditions of use. Fine, accepted. I then get the popup outlining the permissions - no problem, accepted. After this message disappears, I get a few seconds of the "loading" animation and then a popup tells me "Your YouTube account does not have the necessary permissions to create a live stream. Want to change your permissions now? ||No|Yes||".
When the error first occurred it was right enough - logging into YouTube on desktop I was able to establish that I didn't have live streaming enabled but despite now having enabled it, the camera app still returns the error saying my account doesn't have the necessary permissions. If I hit "Yes" it loads a YouTube URL and now when I land on the site there's a popup saying "You are already enabled for this feature".
I've tried wiping all the Live On YouTube application data via settings, I've tried uninstalling the app and reinstalling, but I keep getting hit with this error.
Can anyone suggest anything else I might want to try to get this feature working? Or does anyone have a suggestion of a better place to ask the question if it doesn't belong in this forum?
I can get mine working or at least set up ok, however, upon trying to run the option I just get a 'Creating Live Event' dialogue that stays on forever.
Its rather annoying I can do a share to my social media network of choice, so people can get to the right web page to see my live event, I just can't seem to get the phone to actually start streaming, despite setting up youtube ok. Has anyone yet managed to do a youtube live broadcast from their phone, and if so, can they detail what they did please.
I had this issue too. It was because I had 2 youtube profiles on my google account, so I enabled Live permissions on both profiles, and it worked.
Burlingtonrox said:
I had this issue too. It was because I had 2 youtube profiles on my google account, so I enabled Live permissions on both profiles, and it worked.
Click to expand...
Click to collapse
We have a winner!
I was using YT under my original username, not realising that this meant my G+ identity had a whole separate profile on YT. Switched over to the "real name" profile and found live streaming wasn't enabled there. Enabled it and Robert is now my father's brother.
Fixed! Thanks very much.
How about the 'Creating Live Event' dialogue that stays on forever. Do you have that or does your stream ok.
techguyone said:
How about the 'Creating Live Event' dialogue that stays on forever. Do you have that or does your stream ok.
Click to expand...
Click to collapse
Hi techguyone, the first time I tried it I got your message for a few seconds before it came back with an error message saying "unable to create live event". When I retried I got your message again for another few seconds before it appeared to work. I'm still waiting on the processing, but both the "failed" event and the longer test are now visible in my uploads, even if I can only currently view the (very short) failed one.
It looks like it's going to work for me.
Have you tried the old clearing-out-the-app-data-via-settings trick already?
Mine worked eventually, but its still kinda clunky, interestingly enough I found the other live app (Facebook one) to work straight away, and was a lot easier. I think I'll be using Facebook over Youtube in the future for any impromptu streaming.
This worked for me...
What I did is that I clicked on the avatar in the upper left corner of the screen,and scrolled down and signed out,and the signed in again with one of my two existing youtube accounts,and accepted all the terms and everything again from the beggining....Then I pressed the record button, it took a while to create an event,but it actually started the live streaming!!!!! :
In addition to the well known AppRadio Unchained mod of the Pioneer AppRadio app, a completely Pioneer-less app was developed.
It's called AppRadio Unchained Reloaded and its available from the Play store here: AppRadio Unchained Reloaded
If you don't want to root your phone and have Android 7 or higher there's AppRadio Unchained Rootless
Video of AppRadio Unchained Reloaded in use by Alexei Andreyev: Pioneer AVH-X8600BT & LG G3 with ARUnchained
Another video by Alecion420: STI GR 2012 with ARUnchained+Note 3+pioneer 8000nex+Rockford Fosgate+Boyo backup Cam+SMY keyless
Video by Rubn: Appradio 3 - ARUR
AppRadio Unchained Reloaded allows full mirroring of your phone from your AppRadio. This means that any app can be controlled from the head unit screen and not just a few that are specially adapted.
For this app to work ROOT is required. Do not ignore this requirement and blame the app for not working!
V0.17 and up work with SELinux in enforcing mode.
Important
The 'Smartphone setup' on the head unit needs to be set correctly for Android as by default it's configured for Iphone. Go to Settings->System->Input/Output Settings->SmartphoneSetup and set Device to 'Others' and Connection to 'HDMI'. See this video: Smarthphone setup
Any other AppRadio related app needs to be uninstalled as this blocks the connection to AppRadio Unchained Reloaded.
AppRadio mode requires that your device is connected to the HDMI input of the head unit. Depending on the device this can be done with a MHL / Slimport / Miracast / Chromecast adapter.
Because this app may not work for your setup there's an extended trial period of 48 hours. In order to claim this simply request a refund within 48 hours after purchase by emailing the order number to the support email address.
Two versions
When your device has Android 4.3 or higher you will get version 0.31 which has support for automatic connection to wireless casting devices.
The user's manual is available here: Version 0.31 user's manual
Please read it as it contains all details about setting up a wireless screencasting connection.
When your device has Android version lower than 4.3 you will get version 0.29 without support for wireless casting devices
The user's manual is here: AppRadio Unchained Reloaded User's manual
Supported head units: any AppRadio that supports Android AppMode via HDMI.
For example: SPH-DA100, SPH-DA110, SPH-DA210, SPH-DA120, AVH-X8500BHS, AVH-4000NEX, AVH-4100NEX, AVH-4200NEX, AVIC-X850BT, AVIC-X950BH, AVIC-Z150BH, AVIC-6000NEX, AVIC-6100NEX, AVIC-6200NEX, AVIC-7000NEX, AVIC-7100NEX, AVIC-7200NEX, AVIC-8000NEX, AVIC-8100NEX, AVIC-8200NEX
Units that have AppRadio mode via USB (a.k.a. AppRadio One) are not supported.
Beta test version
The beta test version has the latest features but can also contain bugs.
You need to become a tester of the AppRadio Unchained Reloaded app to be able to get it.
Please apply here: https://play.google.com/apps/testing/mars.area51.arunchained
The following features are supported:
- Multitouch
- AppRadio buttons
- Steering wheel controls
- GPS data transfer via mock locations (only works with head units that have a GPS receiver AND do not have built-in navigation)
- Auto enables mock locations on connection (if app is converted to a system app)
- Wake lock
- Rotation locker (to put any app in landscape mode)
- Real calibration
- Start at boot (for use with Android sticks)
- Start on HDMI detection (for use with phones and HDMI adapters)
- Notifications to indicate connection state
- Widget for returning to head unit home screen
- Diagnostics
- Automatic Bluetooth toggle for improved connection
- Assign system app rights without the need to move files
For Reloaded to be able to switch Mock locations automatically, it needs to have system app rights. These can be assigned as following:
In the menu select the entry 'System app enable'. Once the rights are assigned the entry will change to 'System app disable'. When executed the system app rights will be revoked. When 'System app enable' is activated, the diagnostics will show 'Can switch mock locations' ticked. However it will not show 'Installed as system app' as technically it's not installed as a system app but nonetheless it has system app rights and the Mock locations can be switched.
When the app is still installed as a system app (by moving the files) the menu entry is disabled as it makes no sense. In order to enable the functionality remove the files that were moved to make it a system app first and then install the latest version.
AppRadio is a registered trademark of Pioneer.
Disclaimer: You are solely responsible for using this app in such a way that it does not impair your ability to drive.
Beta
Beta test release notes
0.39
- Alternate menu. Long press the background of the app to show this menu.
0.38
- Support key layout for TV boxes
- Improve screencast autoconnect support
0.37
- Fix crash at connection time when getPort not found
- Fix for LG V20 screen offset
Moved across from the other thread as it will no doubt be an FAQ.
Method for getting ARUR working on Lollipop (in this case the Nexus 5)
Update your phone to Lollipop using Wugfresh Toolkit. This allows you to flash the factory image LRX210 (which it will download for you)
Use the same toolkit to root the phone including your choice of recovery (TWRP etc).
Set SELinux to permissive with SELinux Mode Changer.
Check the phone still reports it has the right sized storage (16Gb/32Gb). If it is reporting it is half the size it should be, boot into recovery and wipe the data partition and it will get restored.
Install ARUR from the Play Store
Move the Installed application into /system/priv-app using Root Browser and set the permissions to read write execute
Alternative way to flash and root:
Install with the factory image LRX21O (not with an OTA update zip).
Root with CF Auto-Root.
If you get it installed and still have problems, Try:
Delete your Bluetooth connection on both your Nexus and your HU, perhaps a full reset on the HU, then re-add the Bluetooth connection.
Ensure the HU configuration is set to "Other" and not iPhone
Check ARUR has SU permissions in SuperSU application (or whichever app you have installed)
Check that your solution works to a standard TV (won't allow touch but will check the HDMI output)
New version released by Area51 which should mean there is no need to set SELinux mode to permissive.
Good news for those with locked boot loaders as his should now work for them with just root.
Is the nexus 6 supported, yet? If so, which cable is required?
Sent from my Nexus 6 using Tapatalk
just bought ARUR because of the newest update, but touch control still isn't working on my S5.
for my diagnostics, the only things not checked are:
no app interfernce
installed as system app
can switch mock locations.
do these need to be checked for touch controls to work? Thanks.
blackcompany said:
just bought ARUR because of the newest update, but touch control still isn't working on my S5.
for my diagnostics, the only things not checked are:
no app interfernce
installed as system app
can switch mock locations.
do these need to be checked for touch controls to work? Thanks.
Click to expand...
Click to collapse
No. The one for touch control to work would be "Event injection". I had it reported working by some people with an S5 but maybe they used a different root method. It looks like there might be still some work to do. Would it be possible for you to make a logcat dump and email it to the support email from the Play store? It can be done with an app called "Catlog". Please first start Catlog first, force close ARUR and then start it, then connect to your HU.
Edit: No app interference, do you still have ARU/Pioneer app installed? If so uninstall it first. If frozen with titanium backup it doesn't matter.
Area51© said:
No. The one for touch control to work would be "Event injection". I had it reported working by some people with an S5 but maybe they used a different root method. It looks like there might be still some work to do. Would it be possible for you to make a logcat dump and email it to the support email from the Play store? It can be done with an app called "Catlog". Please first start Catlog first, force close ARUR and then start it, then connect to your HU.
Edit: No app interference, do you still have ARU/Pioneer app installed? If so uninstall it first. If frozen with titanium backup it doesn't matter.
Click to expand...
Click to collapse
I didn't reailze it before, but because ARU was still installed, ARUR kept saying Listening for Connection. Once I uninstalled ARU it finally connected. But I still don't have touch controls. I uninstalled it and now my app interference box is checked. the other two boxes are still unchecked.
I started catlog, forced closed ARUR, and then connected to the HU. Now how do i get to the log info so I can send it to you? I've never used catlog.
blackcompany said:
I didn't reailze it before, but because ARU was still installed, ARUR kept saying Listening for Connection. Once I uninstalled ARU it finally connected. But I still don't have touch controls. I uninstalled it and now my app interference box is checked. the other two boxes are still unchecked.
I started catlog, forced closed ARUR, and then connected to the HU. Now how do i get to the log info so I can send it to you? I've never used catlog.
Click to expand...
Click to collapse
How to make a logcat using an app called Catlog
Start Catlog logcat through app menu and select record.
Select home button so you leave Catlog app running.
Go through process to start ARUR and connect to AR.
Once you know the bug was created, open the Catlog app from notification bar (this stops recording).
Select the recording, which is named by date-timestamp...from action selection pick share by email...this zips the logcat and system info txt files into one zip.
Email to self and share the zip with dev by email or any other method you want.
Area51© said:
How to make a logcat using an app called Catlog
Start Catlog logcat through app menu and select record.
Select home button so you leave Catlog app running.
Go through process to start ARUR and connect to AR.
Once you know the bug was created, open the Catlog app from notification bar (this stops recording).
Select the recording, which is named by date-timestamp...from action selection pick share by email...this zips the logcat and system info txt files into one zip.
Email to self and share the zip with dev by email or any other method you want.
Click to expand...
Click to collapse
So I didn't see any options to share the recording in the catlog app. There's only a search function, pause button, a sort button, and a refresh button and then all the log info in a long scroll. I transferred the files from my phone to my computer and sent it to the email on the play store. If there's anything else I got to do let me know. Thank you.
supernewf said:
Is the nexus 6 supported, yet? If so, which cable is required?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Nexus 6 does not support HDMI out, so there will not be a cable. You may be able to get it to work with Chromecast though, it does not support Mirrorcast either.
blackcompany said:
just bought ARUR because of the newest update, but touch control still isn't working on my S5.
for my diagnostics, the only things not checked are:
no app interfernce
installed as system app
can switch mock locations.
do these need to be checked for touch controls to work? Thanks.
Click to expand...
Click to collapse
I heard via email from blackcompany that it's working now. The thing that fixed it was to update to the latest SuperSU version.
Is Note 3 supported yet?
ixo- said:
Is Note 3 supported yet?
Click to expand...
Click to collapse
Note 3 has always been supported.
If you mean can you use a device with a locked boot loader and SELinux in enforcing mode, then the latest version is looking good so far for supporting that configuration. You still need the device rooted and the latest SuperSU application installed.
i wish i had more thumbs, so i could give this app four thumbs up
Phone: OnePlus One
ROM: Paranoid Android 4.6 (using ART instead of Dalvik)
HeadUnit: SPH-DA210
Connection: WiFi hotspot and Chromecast (tried Amazon FireStick but it was cumbersome to initiate the screen casting, it worked though)
I have the service running all the time and use NFC tags and the Trigger app to turn on/off bluetooth, wifi, hotspot, etc. I'm not sure of the battery usage so far with the service running all the time (just bought the app about 12hrs ago). This stand alone app has really sped up the time it takes to get connected and on the road. I also am not using ARUR as a system app and have mock locations on at all times. My initial impressions have been so outstanding that I have uninstalled Tasker, Secure Settings, AppRadio Unchained & AppRadio Unchained GPS Injector.
couple of quirks...
1) when i check "Do not switch Mock locations", gps injection will not work. I have mock locations on already so its my understanding there is no need to "switch" and ARUR is not a system app.
2) during my testing i stopped the app when it was already connected to my appradio and restarted. it says connected but the touches do not register. on the old unchained app you could on/off bluetooth and reconnect with the headunit to get the touches back, this method did not work.
feature request...
i'm not sure if you are familiar with the screen standby app, but if you could have such a feature as an option would be awesome! one less app to have.
question for anyone...
if anybody knows a way to automatically start casting my screen upon successful connection to my appradio, i would greatly appreciate the advice.
400ixl said:
Method for getting ARUR working on Lollipop (in this case the Nexus 5)
...
Move the Installed application into /system/priv-app using Root Browser{/URL] and set the permissions to read write execute
Click to expand...
Click to collapse
Are you sure that's all that is required for converting to a system priv-app? Last time I did it, a library file needed to be transferred as well. Also, there are multiple permissions to set (owner, group, and other), so you may want to edit it the sentence to be more explicit. Finally, was the typo using a brace intentional? The Play Store link does not work as a result.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
ddash97 said:
Phone: OnePlus One
ROM: Paranoid Android 4.6 (using ART instead of Dalvik)
HeadUnit: SPH-DA210
Connection: WiFi hotspot and Chromecast (tried Amazon FireStick but it was cumbersome to initiate the screen casting, it worked though)
I have the service running all the time and use NFC tags and the Trigger app to turn on/off bluetooth, wifi, hotspot, etc. I'm not sure of the battery usage so far with the service running all the time (just bought the app about 12hrs ago). This stand alone app has really sped up the time it takes to get connected and on the road. I also am not using ARUR as a system app and have mock locations on at all times. My initial impressions have been so outstanding that I have uninstalled Tasker, Secure Settings, AppRadio Unchained & AppRadio Unchained GPS Injector.
couple of quirks...
1) when i check "Do not switch Mock locations", gps injection will not work. I have mock locations on already so its my understanding there is no need to "switch" and ARUR is not a system app.
2) during my testing i stopped the app when it was already connected to my appradio and restarted. it says connected but the touches do not register. on the old unchained app you could on/off bluetooth and reconnect with the headunit to get the touches back, this method did not work.
feature request...
i'm not sure if you are familiar with the screen standby app, but if you could have such a feature as an option would be awesome! one less app to have.
question for anyone...
if anybody knows a way to automatically start casting my screen upon successful connection to my appradio, i would greatly appreciate the advice.
Click to expand...
Click to collapse
Are you using a 2nd phone to control the mirroring, or did you get around it by ignoring the warning in the Chromecast application? What does it do to your audio quality?
stargate125645 said:
Are you using a 2nd phone to control the mirroring, or did you get around it by ignoring the warning in the Chromecast application? What does it do to your audio quality?
Click to expand...
Click to collapse
I see no Chromecast warnings. The only warnings I do see are from the Pioneer AppRadio itself. Also, I have to use an app called "#MirrorEnabler" in order to get the "Cast screen" option in the Chromecast app as the OnePlus is not an officially supported device.
As far as the audio is concerned, I would say the quality is equal to bluetooth 2.0. I listen to sport talk about 95% of the time i'm in my car so its not enough to out weigh all the other benefits. you can stop here or...
you can read this if you want a bit more information about my opinion with regards to audio quality...
i have factory speakers with an external amp & sub connected to the appradio. Also, my vehicle is performance oriented so my cabin noise is above average. With all that said, there is still a discernible difference in the below scenarios and I would rate the "cast screen" audio as on par with bluetooth 2.0
#audio and video compression over wifi with phone as the source
appradio + chromecast cast screen + oneplus = good
#audio and/or video compression over wifi with chromecast as the source
appradio + individual app casting (ie Netflix, Play Music) = better
#potentially no compression depending on the source
appradio + directly connected media (ie dvd, cd,usb,hdmi) = best
Now, replace the appradio with my home theater system in the above scenarios and I would rate all three higher.
ddash97 said:
I see no Chromecast warnings. The only warnings I do see are from the Pioneer AppRadio itself. Also, I have to use an app called "#MirrorEnabler" in order to get the "Cast screen" option in the Chromecast app as the OnePlus is not an officially supported device.
As far as the audio is concerned, I would say the quality is equal to bluetooth 2.0. I listen to sport talk about 95% of the time i'm in my car so its not enough to out weigh all the other benefits. you can stop here or...
you can read this if you want a bit more information about my opinion with regards to audio quality...
i have factory speakers with an external amp & sub connected to the appradio. Also, my vehicle is performance oriented so my cabin noise is above average. With all that said, there is still a discernible difference in the below scenarios and I would rate the "cast screen" audio as on par with bluetooth 2.0
#audio and video compression over wifi with phone as the source
appradio + chromecast cast screen + oneplus = good
#audio and/or video compression over wifi with chromecast as the source
appradio + individual app casting (ie Netflix, Play Music) = better
#potentially no compression depending on the source
appradio + directly connected media (ie dvd, cd,usb,hdmi) = best
Now, replace the appradio with my home theater system in the above scenarios and I would rate all three higher.
Click to expand...
Click to collapse
That pretty much seals the deal for me to stick with a wired setup. As far as the warning goes, it is the one that pops up on the phone when the editing the Chromecast application options for the Chromecast device that is connected to your phone's WiFi tether. Chromecast doesn't like to cast a screen from the same device to which it is tethered, in my experience. So, I was inquiring if you found a way around this without getting such a device warning, and without having to use a 2nd phone.
DDash,
I'm very interested in your use of the AppRadio and the OnePlus.
Would you be willing to write up a short 'how to', and if any other equipment/cables, etc are necessary?
Thank you for the prededing information.
stargate125645 said:
That pretty much seals the deal for me to stick with a wired setup. As far as the warning goes, it is the one that pops up on the phone when the editing the Chromecast application options for the Chromecast device that is connected to your phone's WiFi tether. Chromecast doesn't like to cast a screen from the same device to which it is tethered, in my experience. So, I was inquiring if you found a way around this without getting such a device warning, and without having to use a 2nd phone.
Click to expand...
Click to collapse
oh yeah, without a doubt stay wired. i was perfectly happy with my previous nexus 4 hard wired setup. My original nexus 4 never had an overheating issue, it just decided not to turn on one morning so every "repaired" nexus since (4 of them now) ,overheats to the point of powering off,when connected to my appradio over hdmi. So now i have a oneplus and only kept it because it was good enough over chromecast or firetv stick.
---------- Post added at 09:31 PM ---------- Previous post was at 09:24 PM ----------
JeffDC said:
DDash,
I'm very interested in your use of the AppRadio and the OnePlus.
Would you be willing to write up a short 'how to', and if any other equipment/cables, etc are necessary?
Thank you for the prededing information.
Click to expand...
Click to collapse
Sure, i can write something up. I'll do it in the OnePlus forum and send you a link.
Hello folks. I've been reading a lot to fix this issue but no luck yet so I come to you. I have a Pixel 4XL running android 11, and a smartwatch brand Haylou Ls05, with the apk Haylou Fit.
The thing is I cant set the proper permissions to use the location services in the background. Mi GF has a android 10 phone and no problem.
I already tested everything I founded over the internet and nothing works. When I start running, the app goes good until the screens is off and the tracking of the running gets lost.
Any suggestion? Thanks in advance!!
Are you running without your phone? This watch doesn't have any GPS chip or functionality, so it is not going to track your location or track your your route by itself. Sorry if this was obvious already but I don't know what your use case is. On Android 10/11 you can control the location use on a per-app basis. If your watch app uses the newest API and supports this function, you will see under the Haylou Fit app permissions>>location the following: (Allow all the time/Allow only when using the app/Ask every time/ Deny). If you don't see this option in your app settings then the app itself needs to be updated. It's not the phone that is the issue, but the app. See the screenshot attached. Android 10 has this same functionality, so I'm not sure why your GF's is working correctly and yours is not. You may try removing and re-installing? Please post a screenshot of what you are seeing under location permissions for this app. Cheers.
Thanks very much for your answer. Yes, I run with the cellphone to use the gps of it because the watch does not have gps. Sorry i'm not very familiar with API, but I understand now that it is a problem of the app itself and not of android. My screenshot doesn't show the "allow all the time" item, as i would like to.
Any way to force it? like patching the app o magisk or something I could do? I like this watch very much , its small and light, and would really like to be able to use it..
Thanks you for the answer.
Agustín.
agucasta said:
Thanks very much for your answer. Yes, I run with the cellphone to use the gps of it because the watch does not have gps. Sorry i'm not very familiar with API, but I understand now that it is a problem of the app itself and not of android. My screenshot doesn't show the "allow all the time" item, as i would like to.
Any way to force it? like patching the app o magisk or something I could do? I like this watch very much , its small and light, and would really like to be able to use it..
Thanks you for the answer. Agustín.
Click to expand...
Click to collapse
Not that I know of. I still would like to know why the app it works on your GF's phone (10) and not yours (11) because they both have the same location security options. Is the "always" option available on hers, or is it working on the "when app is running"? Running the same version? This may be related to the API used by the app and until the dev updates it, it will not work. Try contacting the dev? Contact info is available on the Google Play Store.