Database Develop

[APP] Moto Phone Portal for Hero (v2)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recently some of the system dumps from the upcoming Motorola Sholes/Tao/Droid hit the Developer community, and they have been trying to piece the puzzle together of what the Motorola Sholes/Tao/Droid is all about. We got our hands on a new app which looks like it will be front and center when the device finally hits the shelves, Motorola Phone Portal.
Those that remember using the Motorola Phone Tools app to hack their Motorola’s back in the day (I’m getting all “Ahmad – Back in the Day” about my v600, v810, and RAZR) will instantly recognize this little gem, but it’s been updated for Android and provides some pretty cool functionality. Basically, Motorola Phone Tools (MPP) serves as an all-in-one phone manager that allows users to easily view, edit, create, delete, and play their contacts, ringtones, photos, wallpaper, and media. The key difference now is, the app is web-based and you log into your phone from directly from your browser! No installing “modems” and drivers on your Windows machine (painful), just fire up the app and press the “Connect with Wi-Fi button. When you press the button, the app prompts you to either turn on Wi-Fi, or connect over USB. For this experiment, I chose Wi-Fi.
MPP lets you add/edit/delete/browse your contacts, photos, bookmarks, browser history, and media in an easy-to-use interface. Playing media directly from the device in the browser worked very well, and the picture viewer/slideshow feature is pretty damn cool. So with MPP you’ll be able to play/show-off your media anywhere from any browser. If Moto adds a Social/Sharing aspect to this, they will have a winner on their hands.
So there you have it kids, a little taste of what’s to come with the Sholes/Tao/Droid. The original Moto Phone Tools was a pretty handy app (when it worked), and the new MPP looks to be just as functional, if not more so. I am sure it will help a lot of users manage their contacts/media/content when it gets released, and the ability to do slideshows and play media from your device directly from your browser is pretty slick. I hope Moto adds more features and functionality to it as time goes on, but this seems like a sign of good things to come. Grab the .apk file below and play away!
Click to expand...
Click to collapse
This is a cool little phone manager app that works really well with Hero and G1. It's an app that runs a webserver from your phone that you can access over Wifi from any browser on the same network.
It allows you to:
* view/add media on your phone
* view your call log
* read and send sms from the browser
* and more!
Works with any OS - anything with a browser should work. Only works over wifi with Hero, no USB connection is possible it seems.
I replaced as much Motorola branding as I could and replaced it with HTC stuff to make it a nicer experience for HTC fanboys
Download HTCportalv2:
http://www.sendspace.com/file/vpbxzo
Changelog
v2 - Changed more Moto references to HTC

Now if only this would let me control music playback.
Still, looks super, and nice to be able to manage over wi-fi instead of usb

You mean playback music on your pc from your phone? Hmm, I think it does allow that!
But I'm at work at the moment without wi-fi so can't confirm..

I think it lets you pull files, so you could listen on your pc, but I want to control my phone from my pc.
Basically, my stereo is the other side of my room from my desktop, and I'm lazy so if I could just play music from my pc, through the phone, into my amp, then I wouldn't have to get up
Also, I wonder if this means we can send files over wi-fi to web-enabled phones?

Have you tried it out yet? I can't give it another go until I'm home, but I thought that was possible. Look at the quote:
So with MPP you’ll be able to play/show-off your media anywhere from any browser.
Click to expand...
Click to collapse
You can certainly run a slideshow on your pc, from the photos on your phone. Pretty sure music is playable too. Give it a go
As for sending files, yes you can, but I think you might be restricted to media files.

How can I get it work with usb?

Not sure if that's possible, I was trying too. If you turn off wifi and try to connect it says it can connect over usb too, but I couldn't get it to connect. That might only work on a Motorola phone. Everything works over wifi though

That is awesome!!

This app is awesome!!!
Everyone should check it out!!!!
Nice work Pookie!

Cool, glad you like it!
I checked out the music thing, it lets you browse the music you have on your SD card, and you can click to play, but it plays the music on your phone instead of on the computer. That's what you wanted right Branwen?
Here's another screenshot:

Looks like a great app but I can't conect in my browser, anybody els having troble

Works Great good Job
Working really well looks good to well happy

dieseldk said:
Looks like a great app but I can't conect in my browser, anybody els having troble
Click to expand...
Click to collapse
Hmm can't really think what could be going wrong - you are on the same network with phone and pc I take it?

pookie1 said:
Hmm can't really think what could be going wrong - you are on the same network with phone and pc I take it?
Click to expand...
Click to collapse
same network, can see phone and pc in the ip list in my router.
Tryed to disable my firewall and got the same thing.
Runing modaco 2.5.1 core

I really can't think what could be causing it apart from some kind of issue with your network/ports/firewalls

For mine, at the initial setup it would not work at all when I clicked the start for wifi connection. It was only after I unplug my usb cable did it work...or I might had a huge lag.

dieseldk said:
same network, can see phone and pc in the ip list in my router.
Tryed to disable my firewall and got the same thing.
Runing modaco 2.5.1 core
Click to expand...
Click to collapse
I'm using 2.5.1 too and it works fine...
Are you sure you're wifi is enabled?
Have you tried pinging the IP address from your PC's command prompt?
If you can't even ping it you'll know it's a firewall/port issue...

This was cool! Thanks for your effort!

dieseldk said:
same network, can see phone and pc in the ip list in my router.
Tryed to disable my firewall and got the same thing.
Runing modaco 2.5.1 core
Click to expand...
Click to collapse
im having the same issues in general with my hero: my laptop and the hero are connected to the same wifi network, both work fine, but they don't see each other. no ping, no ssh, no http no nothing. from my cable connected (to the wifi router) pc, everything works just splendid. i actually blame either my router (fritzbox, but some lowend version) or my laptop/ubuntu on my laptop for this behaviour, but i actually never investigated in that. whenever i want to connect from my laptop to my phone i hop via my pc, works fine.

It looks like quite a good contact manager also.
And yeah this is just what I wanted for music playback!

ChromeCast Linux + hacking

Hi all,
I'm going to start hacking on the ChromeCast... to boot or run a tiny Linux distro, and also to run homebrew apps without the necessity of the whitelisting process, etc. I'll be keeping a log of my work at chromecastdev.com. Collaboration is welcome.
The first thing I'm going to play with is trying to dump the bootloader (resides in the little NAND on the Marvell SOC?).
milesc

I wish you luck in your conquest!
Hopefully developers on this forum can do some cool stuff with Chromecast!

Port it to Raspberry Pi. *fingers crossed*
Wait, it's an enclosed system, how do you plan to snoop it?

Ethernet over HDMI or the USB port could provide a path. Also there is a header inside it looks like that isn't listed as a spec so it could be a serial/JTAG point. High hopes for this getting hacked and running an XBMC or Plex client, although I guess Plex web might be fine.
Sent from my XT912 using Tapatalk 4 Beta

I don't know if you've already found it, but there are various source files available here. Bootloader sources are in the "sdk" repo. A cursory glance at them makes it seem like you can boot from a USB device by holding down the button on boot, but the image needs to be signed by Google.

any chance you can take some high-res photos of the pcb? The marvell chip isn't listed on the marvell website yet, would be great if we could find a block diagram.

I would sink porting Android would be the best step right now as this is an android forum and is younger brother ran android
Just my opinion.
Sent from my SCH-I535 using Tapatalk 2

Thanks tchebb!!! And here I thought I was finally going to have a reason to play with a logic analyzer to try to dump the bootloader off the bus.
Edit: Well, maybe it's not that simple after all. They didn't include everything... for instance, pin_settings.h is missing.

hajj_3 said:
any chance you can take some high-res photos of the pcb? The marvell chip isn't listed on the marvell website yet, would be great if we could find a block diagram.
Click to expand...
Click to collapse
Just found this on the chromecastdev.com site - http://chromecastdev.com/ccdev/viewtopic.php?f=15&t=7

milesc22 said:
Thanks tchebb!!! And here I thought I was finally going to have a reason to play with a logic analyzer to try to dump the bootloader off the bus.
Edit: Well, maybe it's not that simple after all. They didn't include everything... for instance, pin_settings.h is missing.
Click to expand...
Click to collapse
Yeah, the source doesn't seem to be in a buildable state. I was thinking there might be something like an Android repo manifest.xml to bring all those git repos together into one source tree, but I couldn't find anything like that. Also, like you said, there are lots of missing files referenced in the build scripts.
I found the link to the source after downloading the Chromecast app (my device hasn't arrived yet) and letting it scan and fail to find anything. It directed me here, which has the Google Code link in the "What's Under the Hood?" entry.
The other interesting documentation I found is here, specifically the part about pressing "Apps" seven times to enable developer mode (very reminiscent of dev mode on new Android versions). It's unclear whether that just exposes additional info in the desktop app or actually sends a packet to the Chromecast to enable some sort of on-device dev mode.
Once I get mine, the first thing I want to do is get a full packet capture of the setup and update process, and some sample network traffic generated by normal use.

http://arstechnica.com/gadgets/2013...ongle-is-left-a-little-too-open-to-hijacking/
https://plus.google.com/117916055521642810655/posts/Md6py81N2Ag
DIAL server (developed by netflix/google)
http://www.dial-multiscreen.org/
FAQ for developers (about app on 2nd screen(aka app on your phone/PC), and 1st screen(on the chromecast)
http://www.dial-multiscreen.org/details-for-developers
there is example source code available
supported apps:http://www.dial-multiscreen.org/dial-registry/namespace-database
looks like there should be hulu, BBC, Time Warner, Yahoo, SLing support soon

nmap scan.
Here is my nmap scan of the dongle.
Code:
Starting Nmap 6.25 ( _REMOVED_URL ) at 2013-07-26 20:01 CDT
Nmap scan report for 192.168.1.90
Host is up (0.015s latency).
Not shown: 998 closed ports
PORT STATE SERVICE VERSION
8008/tcp open http?
9080/tcp open http Mongoose httpd
1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at
_REMOVED_URL:
SF-Port8008-TCP:V=6.25%I=7%D=7/26%Time=51F31BE8%P=x86_64-apple-darwin12.4.
SF:0%r(GetRequest,32,"HTTP/1\.1\x20501\x20\r\nContent-Type:\r\nContent-Len
SF:gth:0\r\n\r\n")%r(FourOhFourRequest,32,"HTTP/1\.1\x20501\x20\r\nContent
SF:-Type:\r\nContent-Length:0\r\n\r\n")%r(HTTPOptions,32,"HTTP/1\.1\x20501
SF:\x20\r\nContent-Type:\r\nContent-Length:0\r\n\r\n")%r(RTSPRequest,32,"H
SF:TTP/1\.1\x20501\x20\r\nContent-Type:\r\nContent-Length:0\r\n\r\n")%r(SI
SF:POptions,32,"HTTP/1\.1\x20501\x20\r\nContent-Type:\r\nContent-Length:0\
SF:r\n\r\n");
Service detection performed. Please report any incorrect results at _REMOVED_URL.
Nmap done: 1 IP address (1 host up) scanned in 150.36 seconds
I will run more scans but I thought I would point out that it appears to be running a web server on two ports 8008 & 9080. One of which is listed as Mongoose.
I am too new to post links so I removed all outside URLs. Mongoose can be found on Google Code.

https://github.com/dz0ny/leapcast
Does this do anything for you?
Sent from my SPH-D700 using xda premium

moocow1452 said:
https://github.com/dz0ny/leapcast
Does this do anything for you?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Nice find man. This is for sure the beginning of good things to come.

oh my...it runs Android!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SSH/Telnet access is now possible! All we need now is the unlocked bootloader image and a powered MicroUSB OTG cable.

Nooter said:
SSH/Telnet access is now possible! All we need now is the unlocked bootloader image and a powered MicroUSB OTG cable.
Click to expand...
Click to collapse
they did it! http://blog.gtvhacker.com/2013/chromecast-exploiting-the-newest-device-by-google/

moocow1452 said:
https://github.com/dz0ny/leapcast
Does this do anything for you?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
The only thing that works for me is starting a youtube video from the Android youtube app.
No controls yet, it is not implemented.
Tab casting from Chrome spawns an empty chrome window.
Other Chromecast apps (Play Music) do not detect leapcast yet, or more precisely detects it but do not show the cast button.

bubbleguuum said:
The only thing that works for me is starting a youtube video from the Android youtube app.
No controls yet, it is not implemented.
Tab casting from Chrome spawns an empty chrome window.
Other Chromecast apps (Play Music) do not detect leapcast yet, or more precisely detects it but do not show the cast button.
Click to expand...
Click to collapse
We may want to keep any eye on this project too.
https://github.com/taterbase/hello-chromecast-sender

ROM for Android Auto

Is there any ROM that works with Android Auto for the smartphone samsung galaxy slll (i9300)?

AN17 said:
Is there any ROM that works with Android Auto for the smartphone samsung galaxy slll (i9300)?
Click to expand...
Click to collapse
Last I checked a few months ago no, at least among popular Android 5.1 ROMs, which I think are mostly derived from CM.
I've never checked some Ancient 5.0 ROMs though, and 5.0 is the minimum for AA.
Basically, the H.264 video encoder does not work, and the CM dev did not expect that to ever be fixed or even fixable.
Same for GT-N7100, GS2/Note1 and even GT-I9000.

Android Auto working on i9300 custom ROM
Hi all, well this is my first post on XDA but not my first visit, I hope you find it helpfull... (and sorry for the long post)
I recently fond myself unable to use the Android Auto car projection on my i9300, I did a little googling and came across this post, but the answer of mikereidis did not convince me, since I found in my logcat the following line:
FFmpegExtractor: suppoted codec(h264) by official Stagefright
Click to expand...
Click to collapse
I don't know if that means that the encoder is working but I found no errors or warnings pointing to h.264 (again, I did not check it thoughtfully). What I did found, when I started the AA app, was the following:
01-16 13:38:10.575 15461 15461 I FsmController: fireEvent(EVENT_VANAGON_MODE_STARTED)
01-16 13:38:10.595 15461 15461 D FsmController: State stack (size=1)
01-16 13:38:10.595 15461 15461 D FsmController: 0: com.google.android.projection.gearhead.frx.SetupFsm$VanagonCapabilityCheckState
01-16 13:38:10.625 15461 15496 W CAR.SERVICE: Not supported: total mem 867790848 is lower than minimum 891289600
01-16 13:38:10.625 15461 15496 I CAR.SERVICE: check device capability result false iframe interval -
Click to expand...
Click to collapse
Even if there where a codec problem, the first problem was RAM... But wait, i9300 has 1GB RAM of which only 827 MB are aviable to user, we where only 23552 KB away.
Where is my precious RAM going? The answer to that question came with the help of [1]. Sadly there is no app or customizable kernel that supports editing the reserved device memory, so I had to recompile the whole kernel (First time doing that too =D ).
After a few days, I downloaded the LineageOS 14.1 code and came across its configuration parameters, which are the following:
#
# Reserved memory configurations
#
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=62464
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=15360
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=0
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC3=0
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC_SECURE=50176
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC_NORMAL=4096
CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=0
CONFIG_VIDEO_SAMSUNG_MEMSIZE_TVOUT=0
CONFIG_VIDEO_EXYNOS=y
CONFIG_VIDEO_EXYNOS_MEMSIZE_FIMC_IS=12080
#
# Reserved memory configurations
#
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FLITE0=10240
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FLITE1=10240
# CONFIG_VIDEO_EXYNOS_MIPI_CSIS is not set
# CONFIG_VIDEO_EXYNOS_TV is not set
# CONFIG_VIDEO_EXYNOS_ROTATOR is not set
CONFIG_VIDEO_EXYNOS_FIMC_IS=y
# CONFIG_VIDEO_EXYNOS_FIMC_IS_BAYER is not set
CONFIG_MEDIA_EXYNOS=y
CONFIG_V4L_MEM2MEM_DRIVERS=y
# CONFIG_VIDEO_MEM2MEM_TESTDEV is not set
#
# Graphics support
#
# CONFIG_DRM is not set
CONFIG_ION=y
CONFIG_ION_EXYNOS=y
CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE=71680
# CONFIG_ION_EXYNOS_CONTIGHEAP_DEBUG is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
Click to expand...
Click to collapse
This are the things that take most of our RAM, but modifying them has its cost, lowering the FIMCx makes the camera crash, but lowering the "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" has a more mild effect. I changed it from 71680 to 48128, and compiled. The result is the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(drive link if this method does not work: https://drive.google.com/file/d/0BzImZDCU_wKFRDRmcVc0VmpEZUE/view?usp=sharing)
It works! I have not tested the ROM a lot, but camera (photos and video) is working, video playback from youtube is also working. I do not play any 3D games on my phone, so I cannot tell if there is any horrible consequence there. The new ROM has 850 MB of RAM aviable to user and is AA fully compatible.
I hope you find it useful!
[1] -- https://forum.xda-developers.com/ga...t/discussion-kernel-space-dma-device-t1856133

RawthiL said:
Hi all, well this is my first post on XDA but not my first visit, I hope you find it helpfull... (and sorry for the long post)
I recently fond myself unable to use the Android Auto car projection on my i9300, I did a little googling and came across this post, but the answer of mikereidis did not convince me, since I found in my logcat the following line:
I don't know if that means that the encoder is working but I found no errors or warnings pointing to h.264 (again, I did not check it thoughtfully). What I did found, when I started the AA app, was the following:
Even if there where a codec problem, the first problem was RAM... But wait, i9300 has 1GB RAM of which only 827 MB are aviable to user, we where only 23552 KB away.
Where is my precious RAM going? The answer to that question came with the help of [1]. Sadly there is no app or customizable kernel that supports editing the reserved device memory, so I had to recompile the whole kernel (First time doing that too =D ).
After a few days, I downloaded the LineageOS 14.1 code and came across its configuration parameters, which are the following:
This are the things that take most of our RAM, but modifying them has its cost, lowering the FIMCx makes the camera crash, but lowering the "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" has a more mild effect. I changed it from 71680 to 48128, and compiled. The result is the following:
(drive link if this method does not work: https://drive.google.com/file/d/0BzImZDCU_wKFRDRmcVc0VmpEZUE/view?usp=sharing)
It works! I have not tested the ROM a lot, but camera (photos and video) is working, video playback from youtube is also working. I do not play any 3D games on my phone, so I cannot tell if there is any horrible consequence there. The new ROM has 850 MB of RAM aviable to user and is AA fully compatible.
I hope you find it useful!
[1] -- https://forum.xda-developers.com/ga...t/discussion-kernel-space-dma-device-t1856133
Click to expand...
Click to collapse
Hey RawthiL,
I am sitting with the same problem on my Samsung S3 with Lineage OS 14.1 trying to run AA with my car display.
Do you have a compiled ROM with the changed settings that you can share. I am a layman at this and would appreciate the help.
Thanks.

RawthiL said:
Hi all, well this is my first post on XDA but not my first visit, I hope you find it helpfull... (and sorry for the long post)
I recently fond myself unable to use the Android Auto car projection on my i9300, I did a little googling and came across this post, but the answer of mikereidis did not convince me, since I found in my logcat the following line:
I don't know if that means that the encoder is working but I found no errors or warnings pointing to h.264 (again, I did not check it thoughtfully). What I did found, when I started the AA app, was the following:
Even if there where a codec problem, the first problem was RAM... But wait, i9300 has 1GB RAM of which only 827 MB are aviable to user, we where only 23552 KB away.
Where is my precious RAM going? The answer to that question came with the help of [1]. Sadly there is no app or customizable kernel that supports editing the reserved device memory, so I had to recompile the whole kernel (First time doing that too =D ).
After a few days, I downloaded the LineageOS 14.1 code and came across its configuration parameters, which are the following:
This are the things that take most of our RAM, but modifying them has its cost, lowering the FIMCx makes the camera crash, but lowering the "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" has a more mild effect. I changed it from 71680 to 48128, and compiled. The result is the following:
(drive link if this method does not work: https://drive.google.com/file/d/0BzImZDCU_wKFRDRmcVc0VmpEZUE/view?usp=sharing)
It works! I have not tested the ROM a lot, but camera (photos and video) is working, video playback from youtube is also working. I do not play any 3D games on my phone, so I cannot tell if there is any horrible consequence there. The new ROM has 850 MB of RAM aviable to user and is AA fully compatible.
I hope you find it useful!
[1] -- https://forum.xda-developers.com/ga...t/discussion-kernel-space-dma-device-t1856133
Click to expand...
Click to collapse
Could you make this release available? Tks.
---------- Post added at 06:52 PM ---------- Previous post was at 06:47 PM ----------
avidsukhoi said:
Hey RawthiL,
I am sitting with the same problem on my Samsung S3 with Lineage OS 14.1 trying to run AA with my car display.
Do you have a compiled ROM with the changed settings that you can share. I am a layman at this and would appreciate the help.
Thanks.
Click to expand...
Click to collapse
Did you get any version that supports Android Auto for Galaxy S3?

AN17 said:
Is there any ROM that works with Android Auto for the smartphone samsung galaxy slll (i9300)?
Click to expand...
Click to collapse
I'm using one S3 as AAGateway Slave with android 5.0.1 so I think this version can run Android Auto.

JRFabbi said:
I'm using one S3 as AAGateway Slave with android 5.0.1 so I think this version can run Android Auto.
Click to expand...
Click to collapse
But, do you can connect, with this ROM, to your car multimedia? I'm asking this cause I have a ROM that supports Android Auto, but the car multimedia doesn't accept the connection.
Tks.

Sadly I do not use the i9300 anymore so I cannot tell you if it is working with the latest AA updates. I worked back then just beacuse I was able to squeeze a little more RAM into the user pool. If they raised the minimum RAM requirements of AA it wont work...
Nevertheless I will search for the ROM in my backups and try to upload it for you (give me a couple of days). If you want to build it yourself you will have to download the lineageOS code and edit the kernel config, using a text editor or the "make menuconfig" command (if I remember well). As I said in the post, you only have to reduce the video heap size which is under the option name "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" .

RawthiL said:
Sadly I do not use the i9300 anymore so I cannot tell you if it is working with the latest AA updates. I worked back then just beacuse I was able to squeeze a little more RAM into the user pool. If they raised the minimum RAM requirements of AA it wont work...
Nevertheless I will search for the ROM in my backups and try to upload it for you (give me a couple of days). If you want to build it yourself you will have to download the lineageOS code and edit the kernel config, using a text editor or the "make menuconfig" command (if I remember well). As I said in the post, you only have to reduce the video heap size which is under the option name "CONFIG_ION_EXYNOS_CONTIGHEAP_SIZE" .
Click to expand...
Click to collapse
Thank you so much. If you find in your backup and upload I really appreciated. Tks.

Hi @RawthiL,
I'm also interested in making AA work on my S3, could you please explain how you managed to get the error log when launching the app ? I'd like to check if requirement changed in recent version. If not, I'll be interested in your custom ROM (if you still have it)
@RRvello if @RawthiL sent it to you privately, I'm interested in getting it too
Thanks Guys

I sent the ROM to @RRvello, but I don't know if it is working, maybe he can give us some feedback on that. I will send the link to you via PM @lenuisible2 so you can try it.
I think that I used the adb logcat command while launching the android auto app. have you checked that?

RawthiL said:
I sent the ROM to @RRvello, but I don't know if it is working, maybe he can give us some feedback on that. I will send the link to you via PM @lenuisible2 so you can try it.
I think that I used the adb logcat command while launching the android auto app. have you checked that?
Click to expand...
Click to collapse
Thanks @RawthiL for the file and the command, I'll try them and let you know !

really
very useful and helpful thread
thanks

It does work, Thanks @RawthiL !
I used to have "Your Device is not compatible ..." with all CM and Lineage version I tried, and now the connection to the car is established. Didn't make much tests, but it looks laggy, nothing surprising for a 7 years old device.
Next I will try the mirroring hack, not sure it will be usable because of the under powered phone, but I'll give it a try.

AA mirror works, without much lag !
I just followed the usual tutorial, no need to downgrade Google Play Services or anything else:
- root GS3
- install AA unlock/AA mirror
- launch unlock, grant root access, unlock, reboot
- launch AA mirror, configure settings you need
- connect phone to the car, go to speedo icon, choose AA mirror
Sound and video are working great, I don't have a touchscreen on my car (Audi A4 B9), so I have to navigate with the phone touchscreen (I enabled the Show Taps dev option to see where my finger is).
Of course it's not safe to play with phone / stare at screen while driving...
Thanks again to @RawthiL for making this test a success on my old unused GS3 !

Great to hear that!
Thanks for sharing how to enable the screen mirroring, I was not aware that you could do that. The lag issue is indeed annoying in AA...

lenuisible2 said:
AA mirror works, without much lag !
Click to expand...
Click to collapse
Hi,
Someone can confirm is still works?
I have an old S3, and want to give it a way to use it with my android car (soon to own that).
If so, what ROM, kernel, and root do you use?
Thank you

[CLOSED][APP][5.1+] VPN/Sentry - Virtual private network with firewall [DISCONTINUED]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
VPN/Sentry
Virtual private network with firewall
Encrypt the internet traffic of all your apps
Allow or block internet traffic per app or address
Mix your internet traffic with that of others for increased privacy
Simple to use while still offering advanced features
Blocking access to the internet can help to:
reduce data usage
save on battery usage
increase your privacy
VPN/Sentry is designed for minimum battery usage and maximum network speed. It does not require root permissions.
VPN/Sentry supports all IP protocols. You'll even have IPv6 connectivity when you normally don't have.
There is a free data allowance of 50 MB per day to try the app. Unlimited data usage is available with a subscription.
This app is in beta testing stage, but seems to be pretty stable so far.
Download:
https://play.google.com/apps/testing/eu.faircode.vpnsentry
Website:
https://www.vpnsentry.net/
Terms of service (draft):
https://www.vpnsentry.net/tos/
Privacy policy (draft):
https://www.vpnsentry.net/privacy/
Frequently asked questions:
https://www.vpnsentry.net/faq/

Hi What's the difference with NetGuard?
Inviato dal mio ASUS_Z00LD utilizzando Tapatalk

steakhutzeee said:
Hi What's the difference with NetGuard?
Click to expand...
Click to collapse
I was prepared for this question
See here: https://www.vpnsentry.net/faq/#FAQ16

Hi Marcel,
VPN/Sentry does not auto-start on reboot. Is this by design?
device: Nexus 6P/Oreo
- set VPN/Sentry as Alway-on VPN
- Upon reboot, VPN/Sentry is not auto connected.
- has to touch the VPN/Sentry icon in the Status bar to manually connect.

hiaig said:
Hi Marcel,
VPN/Sentry does not auto-start on reboot. Is this by design?
device: Nexus 6P/Oreo
- set VPN/Sentry as Alway-on VPN
- Upon reboot, VPN/Sentry is not auto connected.
- has to touch the VPN/Sentry icon in the Status bar to manually connect.
Click to expand...
Click to collapse
Start on boot works properly, but I can reproduce your problem if I set VPN/Sentry as always on VPN like you did. I will look into this tomorrow.
Thanks for reporting this.
Edit: correction: if I wait long enough, it works. Android starts VPN/Sentry soon after boot, but it takes some time until Android reports "boot completed" to VPN/Sentry.
Can you please check what happens if you wait a little longer?

M66B said:
Start on boot works properly, but I can reproduce your problem if I set VPN/Sentry as always on VPN like you did. I will look into this tomorrow.
Thanks for reporting this.
Edit: correction: if I wait long enough, it works. Android starts VPN/Sentry soon after boot, but it takes some time until Android reports "boot completed" to VPN/Sentry.
Can you please check what happens if you wait a little longer?
Click to expand...
Click to collapse
Yes, you are correct. If I wait long enough, VPN/Sentry will auto connect.
Thanks

hiaig said:
Yes, you are correct. If I wait long enough, VPN/Sentry will auto connect.
Thanks
Click to expand...
Click to collapse
I have just released beta version 0.18 which will start the VPN earlier when VPN/Sentry has been set to always-on VPN.
It may take a few hours until this release is available in the Play store.
Edit: the release type has been changed from alpha to beta, since recent releases seems to be pretty stable.

Will speed be impaired?
Sent from my SM-J730GM using Tapatalk

sulasno said:
Will speed be impaired?
Click to expand...
Click to collapse
VPN/Sentry was designed for minimal battery usage and maximum speed. The server bandwidth, currently 100 Mbit/sec, is shared though. See the terms of service (menu, help, about) for more information.

This looks like a great app! I do wish you would reconsider your position on releasing the source code, both for the Android VPN client and the server. If I could, I would love to run my own, private server instance, even if this means sacrificing some anonymity. I also have to imagine that if this app takes off (which I hope it does), server bandwidth costs would become prohibitively expensive for you to maintain yourself, which means you will start having to charge users for bandwidth. I also think it doesn't make sense to always route everything through France when the majority of the time I'm at home, on my own local WiFi network.

Cannot run alongside with Blokada*
Sent from my SM-J730GM using Tapatalk

hackel said:
This looks like a great app! I do wish you would reconsider your position on releasing the source code, both for the Android VPN client and the server. If I could, I would love to run my own, private server instance, even if this means sacrificing some anonymity. I also have to imagine that if this app takes off (which I hope it does), server bandwidth costs would become prohibitively expensive for you to maintain yourself, which means you will start having to charge users for bandwidth. I also think it doesn't make sense to always route everything through France when the majority of the time I'm at home, on my own local WiFi network.
Click to expand...
Click to collapse
I have no plans to open source VPN/Sentry at this moment. One of the reasons is that I don't want to support running own serves, since this will inevitably result in all kind of questions I don't want / can't put time into at this moment.
Related FAQ: https://www.vpnsentry.net/faq/#FAQ8
This thread is for a reason in the XDA paid apps main forum. Data usage is free at this moment and will stay free up to a limit (to be determined), but will / need to be paid later on.
If you would run your own server, your internet traffic has to pass through your local Wi-Fi network as well, so this is not really an argument. I will add a server in Canada soon, also to have a proper backup, if you are worried about latency.
If you are concerned about your privacy, this is what I wrote in the NetGuard forum:
"I can imagine people asking themselves if I am trustworthy and they should. Therefore a little about my motives: developing VPN/Sentry is mainly a technical challenge to me (although the app looks simple, it is in fact a lot more complex than NetGuard under the hood). VPN/Sentry is something I want to use myself to reduce battery usage while still having full filtering capabilities. VPN/Sentry already has profiles and will have wildcard and global filtering (including ad blocking) in the near future.
I am just a independent developer and not a big company. IMHO you should be more worried about big companies anyway. Run the Android Booking.com app with NetGuard with filtering enabled or with VPN/Sentry enabled and take a look at what is being accessed for an example.
I have no interest in your data and not even the time to analyze your data. I might take a look at your data in the testing phase, but this will be just to debug problems.
Anyway, you have to make up your own mind about this, but I hope this helps."
https://forum.xda-developers.com/showpost.php?p=73943716&postcount=5493

sulasno said:
Cannot run alongside with Blokada*
Click to expand...
Click to collapse
Only one app can use the Android VPN service at the same time, so this is not surprising.
VPN/Sentry will have it's own ad blocker in the near future.

The server data (rules/conditions) will be backed up daily from now.

Possible to trigger VPN with apps without using 3rd party tools?
Sent from my SM-J730GM using Tapatalk

sulasno said:
Possible to trigger VPN with apps without using 3rd party tools?
Click to expand...
Click to collapse
I am not sure what you mean, so can you explain in more detail what you want?
What do you mean by "trigger" ?

Turn on VPN when I use Facebook. Off when I shut down FB
Sent from my Samsung SM-J730GM using XDA Labs

sulasno said:
Turn on VPN when I use Facebook. Off when I shut down FB
Click to expand...
Click to collapse
Without root permissions it is not possible to monitor the state (active or not) of other apps, so what you want is not possible. Note that VPN/Sentry was designed to not require root permissions.
I don't see the added value either, since the VPN is there to secure all connections, not only those of Facebook. If you really want, you can enable the VPN and exclude all apps except Facebook from using the VPN.

I'm very excited to see you working on another privacy app, thankyou M. - I will be happy to assist by testing as far as my time allows.
Is there any public repository of issues where to check before asking stupid questions or reporting duplicate 'bugs' ?
At my first trials, I noticed odd app behaviour regarding defaults of blocking/permitting. Are you aware of any issues in that area?

Gerolianis said:
I'm very excited to see you working on another privacy app, thankyou M. - I will be happy to assist by testing as far as my time allows.
Is there any public repository of issues where to check before asking stupid questions or reporting duplicate 'bugs' ?
At my first trials, I noticed odd app behaviour regarding defaults of blocking/permitting. Are you aware of any issues in that area?
Click to expand...
Click to collapse
Thanks for helping.
Just comment here if you have any question or remark. Everything is still deliberately low profile.
What odd app behavior did you notice?

[APP][5.0+][Alpha] AA Passenger - Stream audio, control nav, show pics

AA Passenger
https://github.com/martoreto/aapassenger
What's this
With this app you can have two phones: one is the driver's phone, running Android Auto as usual.
Then you can have another one, e.g. handled by passenger. Passenger can then do 3 things:
play any music via car speakers (for now this requires root on passenger's device)
find some destination in Google Maps or another maps app and send it to Android Auto to navigate there
display pictures on the Android Auto screen (e.g. display how the hotel you're driving to looks like)
What's new
1.9-alpha9
AA Passenger: fixed Oreo crash
AA Passenger: fixed casting volume
1.9-alpha8
audio streaming, without root! (experimental)
audio streaming, without passenger app! (experimental)
works also with Hotspot active on the driver's device
AA Passenger now also available from Play Store
driver's app renamed to AA 2nd Seat
now compatible with Android 5.0 Lollipop
many bugs squashed
support for an NFC tag which launches or installs AA Passenger app
note that both driver's and passenger's apps must be updated to work together
Installation
https://github.com/martoreto/aapassenger/blob/master/README.md#installation
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can you describe some more what exactly you can do with this and how?
Can we install this android auto sdk somehow and use this?
Is it possible to have android navigation eg navigon running to a smartphone to display in android auto screen?
Thanks,
Sent from my SM-T700 using XDA-Developers Legacy app

Thanks for bringing additional functionality to AA!
I hope your SDK will bring more devs support for AA apps

sosimple said:
Can you describe some more what exactly you can do with this and how?
Click to expand...
Click to collapse
You mean this app or SDK? I assume app.
With this app you can have two phones: one is the driver's phone, running Android Auto as usual.
Then you can have another one, e.g. handled by passenger. Passenger can then do 3 things:
find some destination in Google Maps or another maps app and send it to Android Auto to navigate there
display pictures on the Android Auto screen (e.g. display how the hotel they're driving to looks like so the driver would easily find it)
play any music via car speakers (for now this requires root on passenger's device)
sosimple said:
Can we install this android auto sdk somehow and use this?
Click to expand...
Click to collapse
The SDK itself is for developers. It allows writing new Android Auto apps.
It rather won't help much in modifying existing apps to run on AA, as the logic behind AA apps is quite different than for normal apps.
The SDK is used like any other Android library.
I published an example demo project (linked in README) which shows how.
sosimple said:
Is it possible to have android navigation eg navigon running to a smartphone to display in android auto screen?
Click to expand...
Click to collapse
It is somewhat possible, for example by creating a new Andoid Auto app which mirrors the screen of the phone on the car screen and then somehow circumvents the fact that Android Auto displays its own graphics on the phone screen.
It's also possible to modify an open-source navigation app (I'm experimenting with OsmAnd recently) and implement the Android Auto functionality.

Many thanks for description. Very good. I would pay for an app mirroring passenger screen to android auto screen.. (showing anything passengers screen shows, video, navigation, etc).
I think many others would like this, if anyone could implement it..
Sent from my SM-T700 using XDA-Developers Legacy app

Any ideas for what other things than navigation, watching videos while stopped and dangerously distracting the driver while driving would this be useful?

Hi Martoreto
Thank you for your work and for the SDK. I tried to you your passenger app now. But I have to say I failed. I don't have rooted my phones yet, but you wrote to send (push) pictures should be possible right? Currently for me it is just possible to send a point in maps. Other than that if I try to send a picture with printscreen it shows "sent to Android Auto" but in Android Auto happens nothing than 1 second of black mirror. I think to push pictures no root is needed right?
Thanks for replay

Sissi1991 said:
Hi Martoreto
Thank you for your work and for the SDK. I tried to you your passenger app now. But I have to say I failed. I don't have rooted my phones yet, but you wrote to send (push) pictures should be possible right? Currently for me it is just possible to send a point in maps. Other than that if I try to send a picture with printscreen it shows "sent to Android Auto" but in Android Auto happens nothing than 1 second of black mirror. I think to push pictures no root is needed right?
Thanks for replay
Click to expand...
Click to collapse
Hi @Sissi1991, thanks for trying the app.
I see good news that you established the wireless connection successfully, which was one of the major concerns I had with the app.
You're right, sending photos should work without root. I saw another report in the SDK thread, when the example app could behave similarly.
Just to make sure it's the same: when you take the screenshot, the screen on Android Auto becomes black for about a second, and then appears the AA home sceen?
Also, does the same happen when trying to send some other picture than a screenshot (like Gallery -> <some photo> -> Share -> Send to Android Auto)?
A note about rooting: it's required only on passenger's device (to make audio work).

@Sissi1991, feel free to try the new release:
https://github.com/martoreto/aapassenger/releases/tag/0.9-alpha2

Couldnt make it work also, same problem as Sissi (tested the previous 0.9 alpha 1 version only)
If sending a picture from gallery, it gives an error 'error resizing image'

Kill Me said:
Couldnt make it work also, same problem as Sissi (tested the previous 0.9 alpha 1 version only)
If sending a picture from gallery, it gives an error 'error resizing image'
Click to expand...
Click to collapse
Ok, this looks like another issue and alpha 2 rather won't make any difference here.
This error shows on the passenger's device, right?
If possible, please PM me links to:
- Android bugreport captured after this error (Settings -> Developer options -> Take bug report)
- The picture which failed to send
Thanks for trying this out.

Thanks for developing such a great idea
Don't know what I am missing, I can't pair my two phones, even though they are connected through wifi direct, the app apparently can't see this connection :s
Enviado de meu Nexus 6P usando Tapatalk

@Sissi1991, @Kill Me, here's 0.9-alpha3 with "error resizing image" fixed. Give it a try!
https://github.com/martoreto/aapassenger/releases

bladerj said:
Don't know what I am missing, I can't pair my two phones, even though they are connected through wifi direct, the app apparently can't see this connection :s
Click to expand...
Click to collapse
Yeah, I expected that Wifi Direct may have some connection issues. Nevertheless, please do this:
On driver's device open "AA Remote Settings" -> "Enable discovery".
On passenger's device open "AA Passenger"; if the setup wizard shows up, go to the "Pairing" page.
Wait 5 minutes.
On both devices, capture Android bug reports, upload them somewhere and PM me the links.

Thank you, ill give it a try.
Pairing through Wifi direct isnt indeed ideal and it takes a while to get connected, i get why using 'passenger' smartphone, but as the driver is driving the passenger could use the connected AA phone i think

@martoreto installed and tested new version! Works perfect. Keep on your good work!

Kill Me said:
but as the driver is driving the passenger could use the connected AA phone i think
Click to expand...
Click to collapse
Just my 3 cents on this idea: some things can be done with this AA-connected phone, and this doesn't need any special app mostly.
I don't know how it is on other phones, but on my HTC One M8 I can open any app even when AA is connected using tricks like opening notifications drawer, going to Settings, Apps etc.
But even then Maps can't be open on both AA and the screen. It can't render at the same time to 2 destinations.
Then, fiddling with the cable can easily disconnect the nav.
That's why I go with the idea of using the passenger's phone, with his/her music library, maps favourites, bookmarks, whatever context etc., to make car travel a more "together" experience.

Let me announce a new major release: 1.9-alpha8
It has two new main features, namely:
Audio streaming without root, as rooting was rather a major blocker for
this feature to be useful.
Hotspot mode. Now the apps don't rely on Wi-fi Direct only (but it's still supported).
They will work also if the passenger's device is connected to the hotspot started
on the driver's device.
Full release notes:
audio streaming, without root! (experimental)
audio streaming, without passenger app! (experimental)
works also with Hotspot active on the driver's device
AA Passenger now also available from Play Store
driver's app renamed to AA 2nd Seat
now compatible with Android 5.0 Lollipop
many bugs squashed
support for an NFC tag which launches or installs AA Passenger app
Note that both driver's and passenger's apps must be updated to work together.
Enjoy!

1.9-alpha9
AA Passenger: fixed Oreo crash
AA Passenger: fixed casting volume

Deleted