Hi, I'm pretty sure this is a unique or rare situation I've experienced, so I'm starting a new thread, but will endeavour to find similar issue threads.
On my motorcycle I have mounted a Brodit powered cradle for my Xperia Z. I figured it would be the ideal way of providing power to the phone while I travelled, and would allow me to use the phone as a Sat-Nav, utilising one of the many sat-nav apps (Google's offering, mapquest, copilot etc etc). Using the Brodit allows full use of the waterproof attribute of the phone - no socket ports need to be opened, and the phone doesn't need to be in a transparent case in inclement weather to prevent damage. I chose the Xperia Z (over other phones eg HTC) with this usage in mind.
It's worth nothing that I had a previous similar setup for my HTC Desire HD: without the powered mount, but using the charging socket and a transparent case over the phone for rainy days. It worked perfectly.
However - I currently am experiencing the following issues with the Xperia Z setup:
Firstly - The Brodit mount is 'not' weatherproof. (this is not Brodit's fault - it's not marketed as weatherproof) It provides power to the phone perfectly, until the first bit of rain, and then it starts to fail - either cutting out completely, or not providing enough current to keep the phone charged while the GPS / Mobile Data / Sat-Nav-App systems are turned on. (Previously it would provide enough power to increase the battery charge even while all the navigation systems were active). This is something I shall look into but I'm not really aggrieved about it - the cradle is NOT sold as an outdoor item so I'm not going to blame Brodit for this. I suspect that the issue is water getting into the 'spring-stud' connections and reducing the current flow. I'm going to see if I can adapt these connectors. If anyone has any further ideas or suggestions for better powered cradles too - I'd greatly appreciate it!
Secondly - and this is the main issue - when the power supply fluctuates (see above) the Sat-Nav Apps behave in a highly irritating manner : They instantly kill the viewport (it goes black), and also forget the current GPS location coordinates, and forget the viewport display setting: ie - show my current location in top down or perspective viewpoint and viewpoint relative to 'North'. When the power returns, the viewport, depending on how the app is being used, either returns to the start of the journey, or to a point in the journey where it remembers, but always loses the current location viewpoint settings.
This is obviously highly distracting, firstly you instantly lose your whereabouts which is dis-orienting, and secondly you then have to stop and reset all the settings so that the sat-nav display is back to doing what you want it to do. On a motorcycle this is further aggravated with the need to remove a glove in order to control the phone. On a recent trip to France I had this happen no less than 5 times in as many minutes right at the start of the journey.
It should be noted that I wasn't using the GoogleNav system in full directions mode. I find this mode misbehaves terribly if you're trying to use a customised route (see below for more info), and so I tend to load up my customised route so that it displays over the maptiles, and then I either just center my viewpoint on my location, or utilise the 'Preview' mode and again, center the viewpoint on my location (this mode displays a useful 'current direction of travel' arrow on your location).
Has anyone experienced issues like this, and if so - did you solve them? Or does anyone have any ideas for how to get into the configuration settings so that I can turn off the screen blanking and signal losses when the power fluctuates?
Thanks
Notes on Customised routes in Google Nav:
As I noted in this Google Product forums thread (just in case anyone else is involved) : https://productforums.google.com/d/msg/maps/DwPoT0pklas/sG0-sFYozT4J :
When in full 'Directions' mode, Google Maps a) doesn't poll your location accurately or often enough when slip-roads (off-ramps) are involved, and re-calculates the route to the next/final destination every time this happens - thus abandoning your carefully planned route.
So - I take it no-one has seen a similar issue or knows of a way to stop Google Maps losing all it's signals when the power is cut off?
Now I know Google has a lot of very smart people, but you would be hard pressed to prove that to me based on some of the rather inexplicable design decisions made for Android Auto, especially when you consider that one of its primary goals is to minimize distraction when interacting with Android.
Let's start with the voice button. I know it is in the top right corner of our phones and tablets, but that is a lousy reason to locate it in the same place on your car's display. For US drivers, it seems the most inconvenient place for it.
Moving on to how messages are handled, it feels as though Google wants your right hand off the wheel, and your eyes off the road. Consider that when a message comes in, Android Auto interrupts your audio to inform you of that. Does it read it to you, or offer to read it to you at that point? No. It expects you to touch the top of the screen, but you better do it quickly as it will be gone in a few seconds. Then you will most likely have to make several taps on the screen to have Android Auto read you the message, and return to the screen you were previously on.
And when it does read you a message, it tells you can reply by tapping the voice button (that one at the far right corner of the screen). Why doesn't it just ask you if I want to reply instead of requiring more physical interaction with the screen?
There are other distractions as well, albeit fairly minor when compared to the above. For instance, when my phone is connected solely via Bluetooth and I am listening to something, when I exit and then return to my vehicle, playback resumes. But if I'm connected to Android Auto, again I am required to interact with the screen. It is the same with navigation... turn off the car for any reason and you will have to reestablish your route again when you startup.
Now maybe it's just me, but having Android Auto for just a week or so, these seem like pretty big potholes on the road of usability, and some seemingly so obvious that I'm was surprised to experience them.
So, is it really just me? How do you feel about Android Auto's workflow? Do you find it unnecessarily distracting? Does it require more of your attention than it should?
AA has many issues that need to be fixed.
But I feel confident that Google WILL fix these things.
Connected cars are and will be BIG business and Google will not abandon it as they've done with some other things.
Consider how much was fixed and improved in Android itself from v1 through to 5.1.
Note that we've all been waiting for decades for something like AA in our cars. Google has been working on AA for years, and it will take years more to work out the kinks.
Plugging a phone into an AA head unit is a model that has problems but is somewhat temporary. Googles goal is to have Android itself running in the car or HU* and this solution will be superior. I think we will hear more about this at I/O; Android 6 allegedly has AA "baked in".
*Many HUs (Pioneer, Chinese) are already running Android and I think Honda is working on this now.
AFAICT, most people who have seen AA and Apple CarPlay prefer AA, so Google has the advantage here.
mikereidis said:
Consider how much was fixed and improved in Android itself from v1 through to 5.1
Click to expand...
Click to collapse
I have... which is a big reason why I bit the bullet. For me, Android was way too rough 'till JB (which is when I switched from iOS). I am hopeful AA's path will be on road with a much higher speed limit.
Have just returned my Xtrons unit due to various issues, and looking to change it for a proper Android Auto unit.
Had a look at the Pioneer AVH-X8700BT and quite disappointed, horrible buttons and a creaky flexy facia, and the onscreen menus etc are cluttered and unintuitive. This is a shame as I could have got 20%/£100 off in Halfords.
So interested to hear from anyone who has tried the others. I keep seeing comments about a JBL unit but it seems the launch date keeps getting shoved back. Kenwood - I've not found much about these but not hugely impressed by the look of the on screen menus in the static photos.
The one that has really got my attention is the Sony XAV-AX100 that has supposedly just been released. The unit looks smart and doesn't appear to need neon footwell lamps and extra boost gauges to complement it, (!) and the Sony menus have similar clean/uncluttered look like the Android Auto section. Apparently its only available via Sony Centres and both my local stores haven't come back yet with availability
I agree with your analysis of the options but i don't think the Sony product is released until December:
https://www.amazon.co.uk/exec/obidos/ASIN/B01LY8222N/geizhals07-21/ref=nosim?m=A3P5ROKL5A1OLE
I personally got the Pioneer F88DAB (which is a european model) and I like the way it works. the menu is working quite well and I like the fact that I am able to adjust the screen tilt.
Android Auto works great at the device and I will upload a video of the device with android auto, so you can see how the menu and all the functions look like.
amazon
that JBL has been pushed back so many times, I would not have any faith in it. The top of the line Kenwood is over a grand, but I have seen some really good reviews on it and few bad reviews. That was my backup plan if I didn't like my Joying, but I love my Joying
Sir_Nomad49 said:
I personally got the Pioneer F88DAB ...amazon
Click to expand...
Click to collapse
At £850, it's poor value - you could professionally install a tablet for a lot less. I think I'll wait for the Sony for x-mas
kc1 said:
At £850, it's poor value - you could professionally install a tablet for a lot less. I think I'll wait for the Sony for x-mas
Click to expand...
Click to collapse
That is true, but it was easier to install and I personally like the interface of it.
The Sony is a good choice. With a pioneer device you can use appradio or mirra cast.
When I am home, I will upload a video on how it is usable.
Sent from my SM-N9005 using XDA Free mobile app
kc1 said:
I agree with your analysis of the options but i don't think the Sony product is released until December:
https://www.amazon.co.uk/exec/obidos/ASIN/B01LY8222N/geizhals07-21/ref=nosim?m=A3P5ROKL5A1OLE
Click to expand...
Click to collapse
I'm also looking forward to getting the Sony unit later this year. :good:
CayenneGTS said:
I'm also looking forward to getting the Sony unit later this year. :good:
Click to expand...
Click to collapse
Looks like it's available to order now
http://amzn.eu/1V2elbz
http://a.co/byhPOFu
Sir_Nomad49 said:
I personally got the Pioneer F88DAB (which is a european model) and I like the way it works. the menu is working quite well and I like the fact that I am able to adjust the screen tilt.
Android Auto works great at the device and I will upload a video of the device with android auto, so you can see how the menu and all the functions look like.
amazon
Click to expand...
Click to collapse
I have the previous model the Pioneer F77 DAB. Works very well. Back in the day halfords had it for something over £800 then by accident halfords listed at £600 so reserved one sharpish. Couple of days later it was back at its original price. I think someone had cocked up.
Far as android auto is concerned it works faultlessly. It's pretty quick booting up from off and reverse camera works straight away, not having to wait for unit to boot. Occasionally when turning vehicle key to on unit comes on as normal but if you then hesitate to start engine it seems to crash and take maybe a minute to boot again. Even reverse camera does not work when this happens. Unit comes on when key is turned to power but cranking engine robs power from unit so it turns off and on again. The crash is something to do with the stage of boot when power drops. In all the time I've had it, it has only happened maybe half a dozen times. Other than this it works faultlessly. Pioneer want stupid money for mapping updates for the built in satnav on the downside but half the time I use Google maps in AA for quickness. Pioneer has an app to connect the phone to on board sat navigation - AVICSYNC. It works but is very clunky. Waiting for Waze to become AA compatible but not holding my breath on that one.
Well after failing miserably with two local Sony centres and also Sony online, I managed to find the unit for sale on Amazon! I'd set my heart on it and after three months with a gaping hole in the dashboard, its finally fitted!
First of all, its single DIN behind the facia so plenty of room for wiring looms, and simply slides in unlike the Android units that would need 30 minutes of trying to pull the cables around and still failing to get the facia flush. Also, as expected, it comes with a cage and standard mounting brackets so no bodging needed. Once fitted the unit sits neatly within the existing double din facia.
It starts up fast, works with my factory fitted reversing camera (unlike the Android units) and is simple to navigate. I was concerned about the 'cheap' resistive screen, but its actually very responsive and only needs a light touch.
The only issues I have so far;
1) The volume control knob needs a fair bit of spinning, it needs two or three goes to crank the volume down. I need to check the settings again to see if you can make the adjustment less fine.
2) If I connect the phone and play music on Spotify, and then start the engine, the unit powers down as normal during engine start. When it resumes, the music starts playing on the phone...I have to swipe across to a second screen and press a '+' speaker button to get the audio back through the vehicle speakers. A bug with my phone, or the radio? Something to look in to.
3) There is a limit to how many menu presses you can navigate, and unlike running Android Auto on the phone, instead of a momentary warning, it sticks until you navigate back home. Thats fine, although really irritating if your passenger is trying to find some tunes. But it does the same when stationary...I'm sure my handbrake is wired correctly but regardless, I'll be over-riding that feature as its in a campervan and I normally have a passenger!
4) Just to answer my own questions about the unit; No, the facia is not removable. No, it doesn't come with a remote control (a shame for a campervan!) And unlike the Android units, everything works seamlessly. i.e it doesn't freeze or get laggy, you don't need to wait ages for the unit to boot or Google Maps to load, and if you start the radio, Spotify etc will stop, rather than having two lots of audio competing for your attention
Spooky_b329 said:
3) There is a limit to how many menu presses you can navigate, and unlike running Android Auto on the phone, instead of a momentary warning, it sticks until you navigate back home. Thats fine, although really irritating if your passenger is trying to find some tunes. But it does the same when stationary...I'm sure my handbrake is wired correctly but regardless, I'll be over-riding that feature as its in a campervan and I normally have a passenger!
Click to expand...
Click to collapse
Android Auto uses the phones GPS and maybe accelerometer to know when you've stopped.
On my Kenwood unit the handbrake sensor is grounded all the time and I still get that message.
Spooky_b329 said:
Well after failing miserably with two local Sony centres and also Sony online, I managed to find the unit for sale on Amazon! I'd set my heart on it and after three months with a gaping hole in the dashboard, its finally fitted!
First of all, its single DIN behind the facia so plenty of room for wiring looms, and simply slides in unlike the Android units that would need 30 minutes of trying to pull the cables around and still failing to get the facia flush. Also, as expected, it comes with a cage and standard mounting brackets so no bodging needed. Once fitted the unit sits neatly within the existing double din facia.
It starts up fast, works with my factory fitted reversing camera (unlike the Android units) and is simple to navigate. I was concerned about the 'cheap' resistive screen, but its actually very responsive and only needs a light touch.
The only issues I have so far;
1) The volume control knob needs a fair bit of spinning, it needs two or three goes to crank the volume down. I need to check the settings again to see if you can make the adjustment less fine.
2) If I connect the phone and play music on Spotify, and then start the engine, the unit powers down as normal during engine start. When it resumes, the music starts playing on the phone...I have to swipe across to a second screen and press a '+' speaker button to get the audio back through the vehicle speakers. A bug with my phone, or the radio? Something to look in to.
3) There is a limit to how many menu presses you can navigate, and unlike running Android Auto on the phone, instead of a momentary warning, it sticks until you navigate back home. Thats fine, although really irritating if your passenger is trying to find some tunes. But it does the same when stationary...I'm sure my handbrake is wired correctly but regardless, I'll be over-riding that feature as its in a campervan and I normally have a passenger!
4) Just to answer my own questions about the unit; No, the facia is not removable. No, it doesn't come with a remote control (a shame for a campervan!) And unlike the Android units, everything works seamlessly. i.e it doesn't freeze or get laggy, you don't need to wait ages for the unit to boot or Google Maps to load, and if you start the radio, Spotify etc will stop, rather than having two lots of audio competing for your attention
Click to expand...
Click to collapse
Re "And unlike the Android units, everything works seamlessly", not true - please see your points 1 and 2 !!
Re "unlike the Android units . . . it doesn't freeze or get laggy, you don't need to wait ages for the unit to boot or Google Maps to load", Android units per se dont have this problem, one particular type, with only 1GB RAM, Lollipop and a later version of Google Maps does, this can easily be sorted.
Glad youre happy with your new unit, enjoy.
Spooky_b329 said:
Well after failing miserably with two local Sony centres and also Sony online, I managed to find the unit for sale on Amazon! I'd set my heart on it and after three months with a gaping hole in the dashboard, its finally fitted!
First of all, its single DIN behind the facia so plenty of room for wiring looms, and simply slides in unlike the Android units that would need 30 minutes of trying to pull the cables around and still failing to get the facia flush. Also, as expected, it comes with a cage and standard mounting brackets so no bodging needed. Once fitted the unit sits neatly within the existing double din facia.
It starts up fast, works with my factory fitted reversing camera (unlike the Android units) and is simple to navigate. I was concerned about the 'cheap' resistive screen, but its actually very responsive and only needs a light touch.
The only issues I have so far;
1) The volume control knob needs a fair bit of spinning, it needs two or three goes to crank the volume down. I need to check the settings again to see if you can make the adjustment less fine.
2) If I connect the phone and play music on Spotify, and then start the engine, the unit powers down as normal during engine start. When it resumes, the music starts playing on the phone...I have to swipe across to a second screen and press a '+' speaker button to get the audio back through the vehicle speakers. A bug with my phone, or the radio? Something to look in to.
3) There is a limit to how many menu presses you can navigate, and unlike running Android Auto on the phone, instead of a momentary warning, it sticks until you navigate back home. Thats fine, although really irritating if your passenger is trying to find some tunes. But it does the same when stationary...I'm sure my handbrake is wired correctly but regardless, I'll be over-riding that feature as its in a campervan and I normally have a passenger!
4) Just to answer my own questions about the unit; No, the facia is not removable. No, it doesn't come with a remote control (a shame for a campervan!) And unlike the Android units, everything works seamlessly. i.e it doesn't freeze or get laggy, you don't need to wait ages for the unit to boot or Google Maps to load, and if you start the radio, Spotify etc will stop, rather than having two lots of audio competing for your attention
Click to expand...
Click to collapse
My unit came with a remote. I also find what I believe is a software bug, if you turn on the dimmer the maps will always be in night mode.
leonkernan said:
Android Auto uses the phones GPS and maybe accelerometer to know when you've stopped.
On my Kenwood unit the handbrake sensor is grounded all the time and I still get that message.
Click to expand...
Click to collapse
I've got the same issue. As of 2.0 Android Auto uses the head units' GPS data. If your head unit doesn't have built in navigation (GPS), it won't remove the limitation even if stationary.
Link: https://productforums.google.com/d/msg/android-auto/8mvJEDnJUpU/pmejOMunAgAJ
terre08 said:
My unit came with a remote. I also find what I believe is a software bug, if you turn on the dimmer the maps will always be in night mode.
Click to expand...
Click to collapse
I found out it's by design by reading the user manual a bit better. The dimmer is connected to the headlights and when you turn on the lights it will go into night mode, unfortunately I use the lights 24/7 so I will install a toggle switch instead to turn on/off the daylight and the night mode. Pioneer has a a similar setting using the headlights but they also have a setting where you can set the time for night mode, hopefully Sony will have something similar in a future update.
Thanks for the replies!
I've worked out that the unit is detecting the handbrake as the video playback from an SD card is interrupted. I see the comment about the Sony not having built in GPS causing Android Auto to keep the 6 press limit, thats annoying, lets hope its fixed in an update. Surely it can use my phones GPS signal to work out when I'm stopped!
Terre08, I'll send you a PM regarding your remote...interesting!
I used Android Auto for the first time yesterday in a rental 2016 VW Jetta. The Phone and Music interfaces look nearly identical to what I get when pairing bluetooth and using the Car's native interface. I'm not seeing much added functionality. As for Navigation, it is nice be able to see it on the car's display. However, since it is landscape mode, only half the screen actually displays the map since there not enough height. When comparing it to what I see on my phone, it is nearly the exact same size. The other half displays the same info I would see on the phone, actually a little less. I suppose the buttons are a little bigger. One small issue is that my phone supports Qualcomm Quick Charge 2 but since I Android auto must use USB, I am left with whatever power the car ouputs. It seemed to be enough to slowly charge my phone even with Nav,Music, Phone, Bluetooth. Is it actually necessary to keep bluetooth on since the USB cable is connected? Another minor nag is that it seems to trigger night mode if I turn on the headlights which got annoying. I'd much rather it uses the light sensor.
I'm not really seeing the advantage. Am I missing some big features?
It seems its about the same to just use my phone and by doing that, I get access to more notifications and all my apps and can see my Nav plus music/phone at the same time.
Youve posted in the wrong section - this is the Android head unit forum, you want the Android Auto forum.
I think the main advantage is you don't have to mount your phone, and you can use the steering wheel to initiate choice controls. I understand what you are saying though. There is nothing life changing
Sent from my SM-G935T using Tapatalk
I've used it a bit longer. I think the major issue I have found is that it is buggy and slow, at least for me. There were probably maybe 3 major issues I found.
1. From sitting down in my car til when it was fully connected and working with nav took way too long.
2. It was very buggy. When the Nav needs to talk, it lowers the volume of the music temporarily. However sometimes, it just completely stops the music with no way to restart it other than unplugging and plugging in again (which would be very distracting while driving). Even then, often it wont reconnect correctly sometimes even causing the car part to reboot
3. It blocks my ability to text. Even on the phone. I can get it to work by going to recent apps and switching but it makes it harder to do it. They shouldn't be deciding what is "safe" and what isnt. If I'm stopped at a red light, I feel it is safe enough to send a txt, but with the blocking it makes it harder. Also it doesnt consider that I may have a passenger in the car that might want to use my phone to send or read a txt. Also, it didnt seem to read google voice or show gmail notificaitons.
It could be so much better
"safe"
eng3 said:
I've used it a bit longer. I think the major issue I have found is that it is buggy and slow, at least for me. There were probably maybe 3 major issues I found.
1. From sitting down in my car til when it was fully connected and working with nav took way too long.
2. It was very buggy. When the Nav needs to talk, it lowers the volume of the music temporarily. However sometimes, it just completely stops the music with no way to restart it other than unplugging and plugging in again (which would be very distracting while driving). Even then, often it wont reconnect correctly sometimes even causing the car part to reboot
3. It blocks my ability to text. Even on the phone. I can get it to work by going to recent apps and switching but it makes it harder to do it. They shouldn't be deciding what is "safe" and what isnt. If I'm stopped at a red light, I feel it is safe enough to send a txt, but with the blocking it makes it harder. Also it doesnt consider that I may have a passenger in the car that might want to use my phone to send or read a txt. Also, it didnt seem to read google voice or show gmail notificaitons.
It could be so much better
Click to expand...
Click to collapse
I understand you may feel it is safe to text at a stop light, but most people fell this too and get caught up in the use of their devices in a car. Texting from a car should be outlawed PERIOD! Even stopped, you need to pay attention to your surroundings while in a vehicle. This is the only way to drive safely. Technological advantages like Android Auto help us band-aid the problem by getting people to look up and away from their screen to hopefully see what is going on around you. Too many people have lost their lives to others not being fully aware of what is happening on the road. I am a tech junkie, but I know it needs to be moderated to keep everyone safe. I see someone on their phone at a light and I feel they are a danger to me and everyone around. Please, stop texting all together from the car. Trust me, if you are important enough......they will wait.
That being said....Sorry (very emotional today). Android Auto does have its advantages with offering Nav in a vehicle without paying for the upgraded interior or having to pay for OnStar Nav. Plus, it keeps heads pointed in the right direction. Up. It would be nice to have it be wireless and not be tethered with a USB cable, but I understand with the amount of data that needs to be passed. Soon all features from the phone could be hands free with inventions like Android Auto paving the way.
Thank you for listening to me rant.
The advantages are:
1. Phone gets GPS signal and speed data from car head unit antenna. This is much accurate than phone.
2. AA integrates with car multimedia and you can control it with steering wheel buttons
3. You can launch Google voice control and read some notifications.
Potentially AA could be much better, but Google had capped most of the good functions:
1. Driving GPS applications are limited to online apps (Gmaps and Waze) which are not offering the capabilities of good apps like Sygic TomTom or iGo.
2. Notification reading of all notifications.
3. Integration of email.
4. Video when not moving.
Brgds
Sent from my LG-H870 using Tapatalk
jisenberg said:
I understand you may feel it is safe to text at a stop light, but most people fell this too and get caught up in the use of their devices in a car. Texting from a car should be outlawed PERIOD! ...
Click to expand...
Click to collapse
Sorry, that is a bit ridiculous. One could argue that being on a call (on a hands free phone) is more distracting. What about people that eat while they drive. Maybe we should outlaw having conversations with passengers too. Alot of distractions are dangerous, it is the driver's responsibility to behave safely. I haven't even mentioned that the driver isnt necessarily the one interacting with android auto. The passenger might be the one that wants to use the device but they are blocked out too.
Oh and guess what, a nag message isnt going to stop someone from doing what they need to do. It just makes it harder and even more distracting.
ypsmav said:
The advantages are:
1. Phone gets GPS signal and speed data from car head unit antenna. This is much accurate than phone. ...
Click to expand...
Click to collapse
I didn't realize this, good point, my phone's GPS reception isnt so great.
ypsmav said:
...
2. AA integrates with car multimedia and you can control it with steering wheel buttons
3. You can launch Google voice control and read some notifications.
Click to expand...
Click to collapse
I don't need AA. If I connect bluetooth, I can control my media with the steering wheel buttons. At least the basic stuff (play/stop, prev, next, vol)
On some cars, I found that hitting the voice button will trigger it on my phone, otherwise, its fairly easy to press the button on the screen. I can also swipe down to read notificaitons. (ofcourse everything looks smaller)
TASKER can do so, so, so much, but the same time, there are some very grey, very hazy limitations to what Tasker can do. What you can do varies from phone to phone and some of the cooler examples you'll see require a rooted phone. Beyond devices, the biggest limitation Tasker can face is your time — how much of it are you willing to spend to do this stuff? I've spent weeks fine-tuning my precious alarm after I switch phones, but that alarm also gives me something nothing else on Android can.
That's the heart of Tasker. It can work Android magic, if you're willing to take the time to understand the logistics and the programming behind it. That magic tests the limits of Android and the limits of user ingenuity, and if you're willing to suspend your disbelief, it can leave you in awe.
Bummed out
Tasker allows you to create an apk that can supposedly be run on another device. Besides most projects not working on any other device, the most limiting thing about Tasker is it's scene building ability. I can't believe that after this many years, scenes are still broken. Go ahead and spend a few days laying out your perfectly placed elements just to destroy all of your hard work with an accidental touch and not having an undo button. Better yet, try experimenting with a simple resolution change and your scene will never be the same again. So much for sharing your awesome project with anyone else. At least it will give you plenty to do the next time you accidentally change your resolution on your device. Tasker is great for doing tiny things with your phone, but you should look elsewhere if you plan on creating a full fledged App.