Related
I owned an Archos and returned it. Aside from the 256MB of RAM really bothering me about the potential upgrades, the deal breaker was on the Froyo update, the "Android_ID" field was left blank (NULL).
There are several apps. that require the Android_ID to be set and one of them is the Siruis/XM app. I rooted the system and attempted to modify several sqlite3 tables to include the ID but nothing worked properly. (Confirmed by others at Slatedroid).
Anyway, can somebody tell me whether the Android_ID field is properly filled out on the Elocity A7 ? There is a free app, in Google Market (yes I had added the Market to the Archos, as well) called ID. It will tell you the Android_ID and several other fields. Even the Android emulator, has all the various fields filled out.
Thanks in advance,
JR
My A7 has an Android ID.
Sim Serial, Device ID, and Subscriber ID all say "null"
rosenbj said:
I owned an Archos and returned it. Aside from the 256MB of RAM really bothering me about the potential upgrades, the deal breaker was on the Froyo update, the "Android_ID" field was left blank (NULL).
There are several apps. that require the Android_ID to be set and one of them is the Siruis/XM app. I rooted the system and attempted to modify several sqlite3 tables to include the ID but nothing worked properly. (Confirmed by others at Slatedroid).
Anyway, can somebody tell me whether the Android_ID field is properly filled out on the Elocity A7 ? There is a free app, in Google Market (yes I had added the Market to the Archos, as well) called ID. It will tell you the Android_ID and several other fields. Even the Android emulator, has all the various fields filled out.
Thanks in advance,
JR
Click to expand...
Click to collapse
If you have market working, download an app called android info. Once downloaded, expand the information under OS, there you will find the android ID. If you have market working you have an android ID.
Rapcon,
Actually, my Archos tablet had the Android market hack installed and fully functional. However, the Android_ID was NULL. I installed the Sirius App from Google Market Place and it didn't work (stuck at checking for updates) due to the non-existant Android_ID. I verified this with the "ID" app as well as SQLITE3 commands against the table in the DB on the rooted Archos Android OS. Most of the other Apps I installed worked fine.
Jazzbone,
Thanks so much for verifying the Android ID field is not null on the A7. One more reason to buy the A7.
One other concern:
Now I only wish it could connect to the PC as a USB device. Using Websharing, ADB via Wifi, or constantly swapping the MicroSD card is a real pain. Anybody know whether the new series of 7" A71, A72, A73 will have both USB Host mode and USB Slave mode capabilities?
Thanks,
Jeff
I found additional info about AndroidID when it's NULL
In instructions are some various methods...
Did you try this?
0. Do all things to create androidid with emulator and SDK...
1. Copy gls.db from /data/data/com.google.android.googleapps/databases/ to root of sd-card
2. With SQLite modify gls.db
Code:
- Browse data
- Choose Table:meta
name strvalue intvalue
1. AndroidID *insert value of androidid here*
- Save
3. Add Google-account
4. Place modified gls.db in fodler /data/data/com.google.android.googleapps/databases/
5. Reboot
Strogino,
Yeah. I tried updating the databases themselves using SQLite (which I took from the emulator) since it wasn't available in the Archos build. After reboot, that DB was reverted back to the original settings. I eventually gave up but with the A7 shouldn't be an issue.
All,
Still want to hear from people about the lack of USB Slave support. Do people use ADB over Wifi, Web Sharing, or just remove and add the MicroSD over and over again. Biggest concern is transferring MP3s and Video without this USB slave support. Wondering is the new line (A10, A71-A73) will support USB slave and it is worth waiting a few months.....
Thoughts?
Thanks,
JR
bluetooth
Swapping the microsd card is very simple for me since my laptop has a slot builtin.
For the occasional file, I'll use bluetooth file transfer.
rosenbj said:
Strogino,
Yeah. I tried updating the databases themselves using SQLite (which I took from the emulator) since it wasn't available in the Archos build. After reboot, that DB was reverted back to the original settings. I eventually gave up but with the A7 shouldn't be an issue.
All,
Still want to hear from people about the lack of USB Slave support. Do people use ADB over Wifi, Web Sharing, or just remove and add the MicroSD over and over again. Biggest concern is transferring MP3s and Video without this USB slave support. Wondering is the new line (A10, A71-A73) will support USB slave and it is worth waiting a few months.....
Thoughts?
Thanks,
JR
Click to expand...
Click to collapse
(this is a sw development question but I'm a noob and not allowed to post in the development forum)
I'm trying to communicate with a usb device, using an acer iconia a500 upgraded to android 3.2 (kernel 2.6.36.3+, not rooted, I just used the regular update feature). In a nutshell, what happens is that after I get the UsbManager, getDeviceList returns an empty map. The same happens with the adbtest sample from google:
mManager = (UsbManager)getSystemService(Context.USB_SERVICE);
// check for existing devices
for (UsbDevice device : mManager.getDeviceList().values()) {
// I get nothing here, the values() list is empty
I've tried several devices (various usb solid state disks, an hard drive, a mouse, a garmin watch, etc). nothing. Some devices (disks, mouse) are indeed recognized by the OS (they work: I see the filesystem, the mouse works fine, etc), but they don't get reflected at the API level.
Googling around, some people say that mouse and keyboard don't get enumerated but disks do, but they're using 3.1 while I'm using 3.2. I don't get the disk either, or anything else I've plugged in.
The code above should enumerate all devices. Anyway, I also tried the intent + xml file approach as documented in the google samples. Still nothing.
The manifest seems ok, and as I said, the adbtest sample straight from the sdk shows the same problem.
Given the paucity of the API, I don't really know what to try next. Has anybody succesfully used host mode on an iconia a500 with android 3.2? I mean "used" at the API level. As I said, "standard" devices gets recognized at the OS level and works, but aren't visible through the API.
In the end I need to communicate with a non-standard device in host mode, so I really need to get it through the API. Also, my (potential) users are just regular users, they won't root their device, install custom roms, etc. I need to make it working with a "standard" 3.1 / 3.2 tablet. I got the iconia after reading it works in host mode, but can't make it work :-(
The only thing that comes to mind is that you missed declaring that you would use usb features in the manifest. Happens to me all the time when using internet in my apps . Check this (you probably already have): http://developer.android.com/guide/topics/usb/host.html#usage
Sent from my A500 using XDA Premium App
Unfortunately no, that's not the case (I triple-checked). I thought I may have made some mistake in the manifest etc, so as I said I've also tried the adbtest sample from google - same problem.
I've also found a free app in the marketplace ("usb device info") which is supposed to show connected devices - I get no devices. I see you have an A500, which android version are you running?
vic ripa said:
Unfortunately no, that's not the case (I triple-checked). I thought I may have made some mistake in the manifest etc, so as I said I've also tried the adbtest sample from google - same problem.
I've also found a free app in the marketplace ("usb device info") which is supposed to show connected devices - I get no devices. I see you have an A500, which android version are you running?
Click to expand...
Click to collapse
3.2 pre-rooted near-stock. Will try later with the app you mentioned and post the results (my daughter is watching a movie from my external hdd hooked to the BD player, so can't try it right now)
EDIT: my 500 GB HDD shows up in usb device info app
Sent from my A500 using XDA Premium App
: (( so it works on a rooted device. Or perhaps there is just something wrong with mine :-((. Maybe someone else with a non-rooted 3.2 will help me sort this out.
I don't want to abuse your kindness, but which kernel version do you have? Same as mine (2.6.36.3+)?
Thanks
Vic
vic ripa said:
: (( so it works on a rooted device. Or perhaps there is just something wrong with mine :-((. Maybe someone else with a non-rooted 3.2 will help me sort this out.
I don't want to abuse your kindness, but which kernel version do you have? Same as mine (2.6.36.3+)?
Thanks
Vic
Click to expand...
Click to collapse
It shouldn't have anything to do with root since the app hasn't requested root access. I have the exact same kernel version. The fact that the disks connect to your tab and you can see the file system, but not the devices themselves is really weird...
Sent from my A500 using XDA Premium App
yes, and sort of sad : (((((((((((
vic ripa said:
yes, and sort of sad : (((((((((((
Click to expand...
Click to collapse
Maybe if someone with stock unrooted 3.2 has the same problem, it would make sense for you to root and flash the near-stock prerooted ROM... or you may always try factory resetting your tablet if you don't have anything essential on it. Also you may try with a usb memory stick just to eliminate the possibility of the port not supplying the needed amperage to power the hdds (though you shouldn't see them in the file explorer if that was the case...)
Sent from my A500 using XDA Premium App
I did try the memory stick - just like the HD and mouse, it is recognized by the OS, I can use the file system, yet get no devices from the API.
Unless someone else comes up with a good idea, I'll go with the factory reset. Unfortunately, rooting is not really an option, I need to develop something that works for the average guy...
Thanks a bunch!
packard bell liberty-iconia tab a500 ROOTING
prejudice would like to know if there is a way to make the root to my tablet having upgraded to 3.2 .... I used when I was gingerbreack 3.1 1.2 no longer works, but obviously I need to change the way ..... can you help?
lollo21 said:
prejudice would like to know if there is a way to make the root to my tablet having upgraded to 3.2 .... I used when I was gingerbreack 3.1 1.2 no longer works, but obviously I need to change the way ..... can you help?
Click to expand...
Click to collapse
Right here. It's no longer as easy as it was on 3.1, but it can still be done.
http://forum.xda-developers.com/showthread.php?t=1307539
lollo21 said:
prejudice would like to know if there is a way to make the root to my tablet having upgraded to 3.2 .... I used when I was gingerbreack 3.1 1.2 no longer works, but obviously I need to change the way ..... can you help?
Click to expand...
Click to collapse
Can you please install the above mentioned app and try to see if a usb device shows up in the list? I see that you have a non rooted 3.2 just like the OP.
Sent from my A500 using XDA Premium App
"AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit [ROOTED]
"AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit
To avoid confusion, below is a picture of the unit this thread relates to.
I am aware of a previous unit using the same design, but it runs an older version of Android. This thread is for the unit running 4.1 as standard.
{
"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"
}
Specification / Features
Hardware
CPU: ARM Cortex A9 MST786 Dual Core 1GHz
GPU: Mali-400 MP
RAM: SKHYNIX 1G DDR3 RAM H5TQ4G83AFR
iNAND: SanDisk 8GB SD1N5C2-8G (1GB system storage, 6GB internal USB storage)
MCU: STM8AH ST
Bluetooth: BlueCore5 CSR
Screen: Capacitive 800*480
GPS: SiRF Atlas V GPS Processor
Radio: Philips TEF6624
Sound Effect Processor: BD37534 ROHM
Outputs: 4x 45w outputs, Toshiba TB2929
Additional Outputs: 1x Subwoofer, 4x pre-outs
Microphone: Built in microphone
Supported Features
Bluetooth connection to phone for calls.
WiFi and 3G dongles. These must be plugged in before turning the device on, and are not hot-swappable.
Compatible 3G Dongles
ZTE MF190 Clone (Qualcomm MSM6280 + RTR6280)
Huawei E171 (Qualcomm MSM6290)
Huawei E180
Huawei E261
Huawei E1752
Non-Compatible 3G Dongles
Generic Orange/Black eBay dongle (Qualcomm MSM6280 + RTR6275)
Huawei E220
Huawei E352
Huawei E367
Connection of multiple USB devices through a USB hub, including wireless keyboards, USB memory sticks, and wireless dongles. These types of devices are hot-swappable.
Multiple USB memory sticks can be plugged in. They mount at "mnt/usb/sda1", "mnt/usb/sdb1", and so on. The limit is not known, three have been tested at once.
Wiki Page
This unit has a very useful Wiki page with a lot of good information.
Tonghai Create AN-21 U Wiki
It would be really appreciated if before posting any questions, you take a read of it, this main post, watch the video review, or do a search of this thread to avoid any repeats.
Video Review
Other videos showing specific features are also available on my channel.
News
2014.01.20Download links and bugs section updated.
2013.12.05Root is now possible.
Previous News
2013.11.16The manufacturer intends to add new features to the unit, they are currently developing an OBD II system, I assume this would be via USB. They say it will require additional hardware.
Sooner than that, they plan to release wireless mirror link for Android phones.
I asked about Bluetooth compatibility, they said my request would be sent to their engineer to include Bluetooth modules. Whether this actually gets included or not, we will have to see.
File Repository
This site has links to most of the files in this thread, including firmware and MCUs.
Android 4.1 Car Stereo File Repository
All files are of course used at your own risk.
Firmware Updates
To update the unit, extract the update files from the downloaded RAR and copy them to a MicroSD Card, insert the card, go to Settings -> General Settings -> System Update or turn the unit on whilst holding down the 'Menu' and 'Volume' buttons until the update starts.
System Version 2.7.29
Mirror 1 - Click here
Previous Versions
System Version 2.7.28
Mirror 1 - Click here
System Version 2.7.11
Mirror 1 - Click here
System Version 2.7.9
Mirror 1 - Click here
System Version 2.7.4
Mirror 1 - Click here
System Version 2.6.96
Mirror 1 - Click here
System Version 2.6.93
Mirror 1 - Click here
System Version 2.6.77-2
Mirror 1 - Click here
System Version 2.6.77
Mirror 1 - Click here
System Version 2.6.73
Mirror 1 - Click here
System Version 2.6.70
Mirror 1 - Click here
Mirror 2 - Click here
System Version 2.6.68
*WARNING* This update appears to cause issues with GPS *WARNING*
Mirror 1 - Click here
Mirror 2 - Click here
Password
System Version 2.6.62
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here
System Version 2.6.60-2
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here
System Version 2.6.60
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here
System Version 2.6.40
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here
System Version 2.6.23
*WARNING* This update appears to cause unrecoverable bricking of the unit when changing model or MCU. *WARNING*
Mirror 1 - Click here
Mirror 2 - Click here
Password
"4.2.2" Versions
Please note that these are actually Android 4.1, but the menu text has been changed to "4.2.2"
System Version 2.7.11
Mirror 1 - Click here
System Version 2.7.22
Mirror 1 - Click here
System Version 2.7.26
Mirror 1 - Click here
System Version 2.7.26-2
Mirror 1 - Click here
System Version 2.7.26-3
Mirror 1 - Click here
Changelog (Unofficial)
System Version 2.7.29
Unknown
Previous Versions
System Version 2.7.28
Unknown
System Version 2.7.11
Unknown
System Version 2.7.9
Unknown
System Version 2.7.4
Unknown
System Version 2.6.96
Unknown
System Version 2.6.93
Unknown
System Version 2.6.77-2
Unknown
System Version 2.6.77
Unknown
System Version 2.6.73
Unknown
System Version 2.6.70
When changing panel keys or steering wheel controls, the notification bar is still displayed
New menu option for backing up and restoring both panel key and steering wheel control mappings
System Version 2.6.68
Homescreen design reverted back to four large widgets per page
App icon for SWC settings
Setting in "Extra Settings" to force USB1.1
Factory reset is password protected (See FAQ)
Developer options are password protected (See FAQ)
System Version 2.6.62
Bluetooth icon in notification bar (appears Bluetooth is turned on by default now, cannot turn it off)
Bluetooth menu, accessed via an app, has "SEARCH FOR DEVICES" and visibility option, however nothing functions when pressed
All extra applications removed (ES File Explorer, GPS Test Plus, QuickPic)
WiFi Hotspot can be activated without re-plugging the 3G dongle in
Background is winter-themed
System Version 2.6.60-2
New home screen design
System Version 2.6.60
Default applications changed back to original theme
APK Installer application install by default
Bluetooth renamed back to Phone
Screenshot feature now fixed and works correctly
System Version 2.6.40
Larger notification bar
GPS icon removed from notification bar
Home, back, menu, and screen off buttons added to notification bar
Default applications changed to red theme (music player, radio, video player, phone)
Phone application renamed to Bluetooth
ES File Explorer installed by default
GPS Test Plus installed by default
QuickPic installed by default
Non-functioning screenshot featured added in settings menu
Bugs / Issues
KeyUnresolved
Workaround
Resolved
Updated 2014.01.20Newest issues will be put at the top, solved issues, or issues with workarounds will be moved to the bottom.
Unable to remove applications that are device administrators without factory reset due to security menu being disabled.
Many applications are unable to "see" the MicroSD card, so the choice of music players is limited. The mount point is "mnt/usb/mmcblk1p1".
Despite selecting "Front Speakers Only" for navigation sound, the sound comes out of the rear speakers too. Setting to "Front Right" appears to work correctly.
Bluetooth is restricted to phones only. (Unsure if this is hardware or software related, talking to manufacturer suggests hardware limitation).
Bluetooth dongles do not work.
There is a "pop" from the speakers sometimes when changing applications that control sound, this is extremely obvious if you have a subwoofer installed. It happens when the unit is turned on, and when going from mute, to a volume level.
Screen brightness when buttons illuminated is not user-configurable. This means it may be too bright or dark depending on the conditions. For example, when it is only mildly dark outside, and you have your lights on, the screen is very hard to see.
Workaround: Enable constant illumination from the "Extra Settings" menu by setting the option to "CLOSE", this will set the keys to always illuminate. Then use an application such as Twlight to control the screen brightness based on sunset and sunrise.
Random issue when downloading large applications. The progress will usually get to more than 50%, and then no progress is made.
Workaround: The only fix I have found so far is to stop the download, reboot the unit, start the download, and repeat until download continues. It should download from where you cancelled. This appears to be caused by a limited download cache size.
Steering wheel controls only work with default applications.
Resolved: Open the radio (this does not appear to work with the music app), then hold the back arrow in the bottom right hand corner, the app will close, allowing steering wheel controls to function with other apps.
Most recent default application always opens on boot and continues to play, even if paused. This includes the radio, music, video, and iPod applications.
Resolved: Open the radio (this does not appear to work with the music app), then hold the back arrow in the bottom right hand corner, the app will close, and no default app will open on boot.
USB Debugging is password protected.
Resolved: The password is "[email protected]". Credit to @nikko82
Screenshot feature does not work, when trying to save the screenshot, a save error appears.
Resolved: This is solved in system version 2.6.60.
Root
Root is now possible thanks to help from some great XDA members.
Credits to @WonderEkin for the Root My AN-21 U app and @bmj67 for supplying SettingsProvider.apk
2014.06.06 - A new rooting tool named Baidu Root has been added to the repository. You can use this tool as an alternative to following the guide below.
Files required
Root My AN-21 U - [ Mirror1 | Mirror2 ]
Root My AN-21 U has been updated since this video was taken, the app should now correctly show "Step 2".
Download the required files above.
Install Android Terminal Emulator on your unit.
Open the AUX application and close it.
Install Root My AN-21 U and create a link on the homescreen.
Run Root My AN-21 U and press the "Step 1" button.
Reboot the unit.
Once the unit has rebooted the screen will likely be black, press the Home button to display the homescreen.
Run Root My AN-21 U and press the "Step 2" button.
Reboot the unit.
Open Android Terminal Emulator and run the following commands.
Code:
su
rm /data/local.prop
Reboot the unit.
FAQ
Can I root this unit?
Please see the "Root" section above.
HELP! My unit is stuck in a boot-loop!
Place the update files on your MicroSD card (see "Firmware Updates" section). Then turn the unit on whilst holding down the volume knob and home button. This should start the update process.
Can I use Bluetooth OBD devices with Torque?
Not at the moment, Bluetooth is only for phones and Bluetooth dongles do not work.
Does it have the full Play Store?
Yes, it has the Play Store and all compatible applications are available for download.
What is the boot time?
18 seconds to home screen, 22 seconds until music application starts. If you use the radio application rather than the music player, the radio sounds as soon as the unit receives power.
Where can I buy one?
There are many listings on eBay/AliExpress under the search term "android 4.1 car", some have resistive, and some have capacitive screens. There is also the mention of a faster 1.2GHz dual core, however the unit actually has a 1GHz dual core CPU.
How good is the radio?
The radio reception seems fine, as does the sound quality.
Is there a Wiki page?
Yes.
Tonghai Create AN-21 U Wiki
What is the USB Debugging password?
[email protected]
What is the Factory Reset / Developer Options password?
7890
What is the Extra Settings password?
123456
Orisai said:
Android doesn't have NTFS support, let alone EFS which is built on top of Microsoft's filesystem, but it's capable of using the same cypher algorithms as EFS (AES, SHA, DES) though. The only thing Android needs to be able to decrypt them during the upgrade process, is the manufacturer's or firmware developer's public key, which I believe is stored among the system root certificates.
This, providing EFS or a compatible file encryption mechanism was used to encrypt those files.
Click to expand...
Click to collapse
If we think about it, Android isn't even part of the equation reading those files really, just a bootloader or the unit's firmware. So the decription layer would have to be built into the bootloader or the raw firmware (read assembly or whatever)... I highly doubt it would be EFS.
As another observation, all filenames remain the same across the two updates and only one file has changed (and it's name remains the same. There goes the hash/sum/md5 like naming theory)...
Code:
diff android-4.1-2.6.40/ android-4.1-2.6.60/
Binary files android-4.1-2.6.40/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 and android-4.1-2.6.60/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 differ
That I'm guessing is our system file
@tin2001 @Orisai @chris.r.r <- in case you missed the switch to new thread
sciallo said:
If we think about it, Android isn't even part of the equation reading those files really, just a bootloader or the unit's firmware. So the decription layer would have to be built into the bootloader or the raw firmware (read assembly or whatever)... I highly doubt it would be EFS.
As another observation, all filenames remain the same across the two updates and only one file has changed (and it's name remains the same. There goes the hash/sum/md5 like naming theory)...
Code:
diff android-4.1-2.6.40/ android-4.1-2.6.60/
Binary files android-4.1-2.6.40/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 and android-4.1-2.6.60/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 differ
That I'm guessing is our system file
@tin2001 @Orisai @chris.r.r <- in case you missed the switch to new thread
Click to expand...
Click to collapse
Yes, as you say, it is the only file that changes between the updates, and it is also the largest file so I think we can assume this contains the data we want.
Looking at the third update I have, it seems that file is again the only one changed. I will be testing this update out and uploading it shortly.
The file names must have some importance, as otherwise they could just call them "system.img", or something simple, but still encrypt them.
KID52 said:
Many applications are unable to "see" the MicroSD card, so the choice of music players is limited.
Click to expand...
Click to collapse
Have you tried to see if it will read an external mass storage attached to usb? (usb stick, card reader, 2.5" portable hard drive)?
sciallo said:
Have you tried to see if it will read an external mass storage attached to usb? (usb stick, card reader, 2.5" portable hard drive)?
Click to expand...
Click to collapse
The default application yes, although I did not try what happens with multiple USB drives. The doubleTwist music player was unable to read a USB memory stick, or the MicroSD card. The actual unit seems to be able to cope with multiple memory sticks, I have tried three, and all were accessible using the ES File Explorer application.
The internal storage is mounted at "mnt/sdcard".
The MicroSD card is mounted at "mnt/usb/mmcblk1p1".
USB memory sticks are mounted at "mnt/usb/sda1", "mnt/usb/sdb1" etc.
KID52 said:
Many applications are unable to "see" the MicroSD card, so the choice of music players is limited. The mount point is "mnt/usb/mmcblk1p1".
Click to expand...
Click to collapse
Have you checked for the presence of a hidden file called, ".nomedia" in the MicroSD card? The presence of this file will let most media players to skip this path for scanning for multimedia files.
donaldta said:
Have you checked for the presence of a hidden file called, ".nomedia" in the MicroSD card? The presence of this file will let most media players to skip this path for scanning for multimedia files.
Click to expand...
Click to collapse
Yes, this file is not present.
KID52 said:
The default application yes, although I did not try what happens with multiple USB drives. The doubleTwist music player was unable to read a USB memory stick, or the MicroSD card. The actual unit seems to be able to cope with multiple memory sticks, I have tried three, and all were accessible using the ES File Explorer application.
The internal storage is mounted at "mnt/sdcard".
The MicroSD card is mounted at "mnt/usb/mmcblk1p1".
USB memory sticks are mounted at "mnt/usb/sda1", "mnt/usb/sdb1" etc.
Click to expand...
Click to collapse
You might want to try a few different players to see if it's the unit or the player...
From http://www.doubletwist.com/help/question/how-do-i-switch-from-internal-storage-to-sd-card/
We recommend only using one volume to store your media. If you choose the memory card, please do not store media files on the internal storage location.
Also, there is not standardized way of implementing SD card support so each manufacturer implements SD card supportly differently. This is why doubleTwist may not always support the SD card on your device.
Devices reported by users to not work includes the following devices:
LG Motion 4G
LG Optimus L5
LG Optimus LTE2
LG Optimus 4X HD
Motorla Razr i
Motorla Razr M
Click to expand...
Click to collapse
I don't know if you can without root but you should be able to as normal user in a virtual terminal link /mnt/sdcard to /sdcard
Code:
ln -s /mnt/sdcard /sdcard
... Something to try. I think it won't survive reboot, but if it works you can possibly make a script for it to happen on boot.
sciallo said:
You might want to try a few different players to see if it's the unit or the player...
From http://www.doubletwist.com/help/question/how-do-i-switch-from-internal-storage-to-sd-card/
I don't know if you can without root but you should be able to as normal user in a virtual terminal link /mnt/sdcard to /sdcard
Code:
ln -s /mnt/sdcard /sdcard
... Something to try. I think it won't survive reboot, but if it works you can possibly make a script for it to happen on boot.
Click to expand...
Click to collapse
It depends on the player.
All file explorer applications such as ES File Explorer, and Astro, have no issues seeing the files. In fact, if you choose an MP3 file and select the player of your choice to open the file, it will indeed open and play, however it does not show up in the list of available songs.
One example of a player than can see the files is Poweramp.
"/mnt/sdcard" is already linked to "/sdcard", but this is the internal USB storage, not external. Perhaps it can be unlinked, and the MicroSD card, "mnt/usb/mmcblk1p1" linked there instead.
Orisai said:
Peter's listing on eBay mentions the headunit supports wireless keyboards, which are bluetooth devices. Also, being it Android 4.1, it should support USB OBD2 scanners like this one on Amazon:
http://www.amazon.com/OBDLink-OBD-II-Interface-Adapter-425101/dp/B002M07XHO
This one is pretty expensive compared to the bluetooth ones, but I've seen it used by dealers to diagnose their cars during repairs.
Click to expand...
Click to collapse
Best to keep discussion for the 4.1 unit in this thread now.
My keyboard is not Bluetooth, it has a small receiver that is probably 2.4GHz, and it works fine.
Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...
I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.
Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.
Orisai said:
Have you tried a Linux compatible bluetooth dongle yet? I believe, if the headunit supports external wireless keypads, then BT dongles should work, as well as anything connected through them.
Click to expand...
Click to collapse
Yes, I've tried a couple that I had lying around.
If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
KID52 said:
Best to keep discussion for the 4.1 unit in this thread now.
My keyboard is not Bluetooth, it has a small receiver that is probably 2.4GHz, and it works fine.
Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...
I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.
Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.
Yes, I've tried a couple that I had lying around.
If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
Click to expand...
Click to collapse
KEEP IN MIND ALL MY EXPERIENCE IS WITH THE 2.3 OUKU but this might help:
Usb Keyboard is natively supported on all of them, if it's wireless with its own dongle (not bluetooth) that's just all it is, a usb keyboard.
For the bluetooth menu install Quick Bluetooth Lite from Market. I was lucky enough one of the dongles I had lying around worked (one didn't) mine sais "KINIVO" on it.
There is a similar app on the market to use bluetooth keyboards.
...but with both of the above it all depends on the ability to add a BT dongle, the internal one is not visible to android as I understand it (and as it was with the other units OUKU, winCE etc.
I have that exact ODBII reader mainly because I wanted a reliable one that could get the most codes... off topic here, but there is differences. Torque forums are a good resource. I haven't tried USB with it yet. There is cheap usb only out there, but I guess there is two different kinds of usb-to-serial chips... you MIGHT have one of the two installed if they included it....
Bottom line, it doesn't matter what Android supports. What matters is what modules the chinese manufacturer compiled in the kernel or included as a loadable module...
You could get a hint looking at the /home/rick/OUKU/stock/4.1/test/lib/modules/ folder...
sciallo said:
KEEP IN MIND ALL MY EXPERIENCE IS WITH THE 2.3 OUKU but this might help:
Usb Keyboard is natively supported on all of them, if it's wireless with its own dongle (not bluetooth) that's just all it is, a usb keyboard.
Click to expand...
Click to collapse
Yes, exactly my thoughts.
sciallo said:
For the bluetooth menu install Quick Bluetooth Lite from Market. I was lucky enough one of the dongles I had lying around worked (one didn't) mine sais "KINIVO" on it.
There is a similar app on the market to use bluetooth keyboards.
Click to expand...
Click to collapse
Thank you for the advice, I will try it out soon, see what happens.
The info you have regarding the OUKU unit may well be relevant to this new one too.
KID52 said:
Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.
Click to expand...
Click to collapse
No, you don't have to buy such devices just for testing purposes. I have plans on buying one for my Santa Fe i45, because USB OBD2 scanners are faster and way more reliable that BT ones, and I'll need it to plug directly into my laptop or the OTG adapter in my SGS4.
KID52 said:
Yes, I've tried a couple that I had lying around.
If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
Click to expand...
Click to collapse
Try to plug them when your stereo is turned off. I recall someone saying that you have to plug in WiFi and 3G dongles with the headunit turned off, so they get detected by Android when it boots up. Perhaps this is the case with BT dongles too.
Orisai said:
Try to plug them when your stereo is turned off. I recall someone saying that you have to plug in WiFi and 3G dongles with the headunit turned off, so they get detected by Android when it boots up. Perhaps this is the case with BT dongles too.
Click to expand...
Click to collapse
Hmm, I said that. I put it in the main post too. Maybe someone said it about OUKU too, I don't know.
But yes, I do usually turn off the stereo and plug the device in before booting.
Then it must be like sciallo said, kernel has to be compiled with the required modules to make bluetooth dongles work, much like Hal9k's firmware.
KID52 said:
Yes, I've tried a couple that I had lying around.
If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
Click to expand...
Click to collapse
Might want to get a terminal for android, like Android Terminal Emulator. Then you can check to see what sort of linux modules/drivers are pre-installed. For example:
Code:
$ lsmod
lsmod
blackberry 1084 0 - Live 0xbf10a000
cdc_acm 15311 0 - Live 0xbf100000
sierra 9201 0 - Live 0xbf0f7000
option 13120 0 - Live 0xbf0ea000
usb_wwan 8010 1 option, Live 0xbf0e2000
hso 29290 0 - Live 0xbf0d3000
tnx_mxt_ts 15886 0 - Live 0xbf0c9000
cp210x 10931 2 - Live 0xbf0c0000
pl2303 10925 0 - Live 0xbf0b7000
usbserial 26415 8 blackberry,sierra,option,usb_wwan,cp210x,pl2303, Live 0xbf0a8000
88w8688_wlan 362475 1 - Live 0xbf041000
tun 13189 2 - Live 0xbf037000
omap3_isp 97716 0 - Live 0xbf014000
omap_hsmmc 14041 0 - Live 0xbf000000
$
This will give you an example of modules installed. In the above example is from the Parrot Asteroid Smart. The output gives you an idea of the sort of devices that you'll be able to use with the unit. For example, there are the cp210x and pl2303 drivers for Serial UART to USB devices. So, for example one could use a USB ODB2 cable as long as they use either a Prolific or Silcon Labs UART.
KID52 said:
I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.
Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.
Click to expand...
Click to collapse
Something that is not well known is that Torque Pro supports USB ODB2 cables. The product linked earlier from Amazon is an ODB2 scanner by Scantool which is a professional model. (Analagous to buying a Fluke Multimeter vs an Innova) They do have another model that costs a little bit more and supports USB and Bluetooth or even WiFi if you prefer. But, there are some less expensive knock offs that you can get for less a fraction of the price. So, if you know the AN-21 U supports a particular Serial to USB driver then you might be able to use one with Torque Pro. The nice thing about USB ODB2 cables over Bluetooth ones is that the data stream is closer to real time and has less lag than a BT ODB2 adapter around the same price.
KID52 said:
Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...
Click to expand...
Click to collapse
Some places hide various menus from the settings control panel, but you can often them bring them up using intents through Activity Manager. However, finding the available intents sometimes requires root but you do not need to be root to execute them. For example:
Code:
$ su
su
# dumpsys package com.android.settings | grep BluetoothSettings
dumpsys package com.android.settings | grep BluetoothSettings
4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068bc48
4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068ba78
4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068ba78
# exit
exit
$ am start -n com.android.settings/.bluetooth.BluetoothSettings
am start -n com.android.settings/.bluetooth.BluetoothSettings
Starting: Intent { cmp=com.android.settings/.bluetooth.BluetoothSettings }
$
However, not all Bluetooth software conforms to the Android standards and will force close if it doesn't. In most cases if a Bluetooth driver is installed then a good app to get is Bluetooth Auto-Pair. It allows the manual settings to pair various devices even if the manufacturer implements an artificial limitation on the devices that they will support.
donaldta said:
Snip.
Click to expand...
Click to collapse
You definitely seem to know your stuff!
That is an extremely informative post, thank you.
I'll take another read tomorrow and do some tests on the unit, see what I can find out.
Orisai said:
Android doesn't have NTFS support,
Click to expand...
Click to collapse
This is actually a pretty bad blanket statement. It actually depends on the Linux modules included with the Android device. And in fact, I played with an Android TV device that had fuse.ko modules installed and supported NTFS partitions. The best way to tell what sort of filesystem that your Android device supports is through "/proc/filesystems".
Code:
$ cat /proc/filesystems
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev devpts
cramfs
squashfs
nodev ramfs
vfat
msdos
nodev mqueue
nodev mtd_inodefs
nodev oprofilefs
nodev ubifs
$
The first column signifies whether or not the filesystem is currently present on your android device and the second column shows all the various types that it supports.
---------- Post added at 11:06 PM ---------- Previous post was at 10:49 PM ----------
KID52 said:
I'll take another read tomorrow and do some tests on the unit, see what I can find out.
Click to expand...
Click to collapse
While you're at it, you might consider installing SRT AppScanner. If the device is vulnerable to Master Key either exploit bug 8219321 and/or 9695860 then there's a good chance that Cydia Impactor can root your device.
donaldta said:
While you're at it, you might consider installing SRT AppScanner. If the device is vulnerable to Master Key either exploit bug 8219321 and/or 9695860 then there's a good chance that Cydia Impactor can root your device.
Click to expand...
Click to collapse
I thought you needed to connect your device to a PC to use Cydia Impactor? Also, not sure if it would be required, but USB debugging is password protected.
KID52 said:
I thought you needed to connect your device to a PC to use Cydia Impactor? Also, not sure if it would be required, but USB debugging is password protected.
Click to expand...
Click to collapse
Well, technically you don't have too. It works off of Android Debug Bridge and can work over WiFi or USB. However, it does need debugging to be enabled. I missed the part that it is password protected. However, the masterkey scripts might still be able to help gain access to root if it hasn't been patched on the device.
Since there is no Forum for the Mi Band ...
After receiving my Mi Band yesterday I started digging inside the sourcecode of the Mi Band App to find out interesting stuff.
It works with all BLE device, not only Xiaomi ones
It uses an unsecure protocoll which can be reverse engineered, so you could build an API out of it or port it to other mobile OS.
I will update algorithms & the protocol asap, but there is already a lot of usefull stuff on the protocol inside my blog: http://allmydroids.blogspot.de/2014/12/xiaomi-mi-band-ble-protocol-reverse.html
If someone is interested in writing an API, contact me.
Great! But some questions:
1) when you say "I started digging inside the sourcecode" you mean the smali decompiled from the app apk, right? Or is there some open code I missed?
2) if we create an apk which exposes the API (for example via android intents) can it connect to the device at the same time with the original Mi app? Or is the pairing exclusive to an app so we have to hack the app itself (for example via an Xposed module)? (Note: I'm extremely ignorant about bluetooth LE).
Thank you!
bitblaster said:
Great! But some questions:
1) when you say "I started digging inside the sourcecode" you mean the smali decompiled from the app apk, right? Or is there some open code I missed?
Click to expand...
Click to collapse
Decompiled and looked at smali + java from smali (which skips stuff so make sure to check original smali, too)
bitblaster said:
if we create an apk which exposes the API (for example via android intents) can it connect to the device at the same time with the original Mi app? Or is the pairing exclusive to an app so we have to hack the app itself (for example via an Xposed module)? (Note: I'm extremely ignorant about bluetooth LE).
Click to expand...
Click to collapse
We are currently developing a BLE app to a customer and I agree that it is horrible. Android has really messed up everything they could when it comes to BLE.
Other apps could access at the same time. Pairing is done through the Android not the app itself. Although it could be that the band itself limits this somehow. I will check that soon.
Awesome...I'm glad I found this. I just got my band and didn't realize it only worked with the app from XIAOMI. Very disappointed. Also, I can't even set mine up right now. I set up an account and when I go to sign in it says I have the wrong password! When I go to reset the password it has to SMS me a verification code and it NEVER COMES. Total waste.
I hope you guys get this working soon and we can use it with apps that won't send our data back to mainland China. Do you know if this will work with 'Sleep as Android'? That's what I got this for. I thought it was a basic bluetooth device, not some proprietary POS.
NeoMatrixJR said:
Do you know if this will work with 'Sleep as Android'? That's what I got this for. I thought it was a basic bluetooth device, not some proprietary POS.
Click to expand...
Click to collapse
I uploaded a very first Android App today but it can do only very few things yet - but currently it doesn't do the setup. I don't know that app so I don't know if it can interact with other devices and if, how good. But the Miband can detect sleep phases (pretty good for me) and can wake you, so I guess it could be possible.
motioncoding said:
I uploaded a very first Android App today but it can do only very few things yet - but currently it doesn't do the setup. I don't know that app so I don't know if it can interact with other devices and if, how good. But the Miband can detect sleep phases (pretty good for me) and can wake you, so I guess it could be possible.
Click to expand...
Click to collapse
Downloaded and tried to install your app. Unfortunately gave me an error. Looking forward to a new version.
Thanks for your effort [emoji106]
andbroe said:
Downloaded and tried to install your app. Unfortunately gave me an error. Looking forward to a new version.
Click to expand...
Click to collapse
Does your device support Bluetooth LE and is Bluetooth enabled?
motioncoding said:
Does your device support Bluetooth LE and is Bluetooth enabled?
Click to expand...
Click to collapse
Yes and yes. The problem is during installation. "Error parsing the package"
My phone is a Samsung Note 3
Cheers from Switzerland
andbroe said:
Yes and yes. The problem is during installation. "Error parsing the package"
Click to expand...
Click to collapse
Ah you tried the .apk from /bin? Thats not working. You have to compile it. I will upload a working one when it has some more features.
Hello again,
downloaded and installed Android Studio. Compiled your project, all went quite smooth. Unfortunatly the app still does not quite work. Without the band close it quickly complains that there is no band around (good). With my miband close, it scans for ever (not good). Somehow it does not communicate with it.
The BLE Device Monitor detects it well.
Regards
andbroe said:
Hello again,
downloaded and installed Android Studio. Compiled your project, all went quite smooth. Unfortunatly the app still does not quite work. Without the band close it quickly complains that there is no band around (good). With my miband close, it scans for ever (not good). Somehow it does not communicate with it.
The BLE Device Monitor detects it well.
Regards
Click to expand...
Click to collapse
Hi,
I tried the same actions. Seems problem with discovering.
According to google:
startLeScan: Added in API level 18 This method was deprecated in API level 21.
Changed API from default 21 to 18 - nothing has changed.
MI device is visible in other BLE apps, in Bluetooth settings as well. Original translated app working well.
Nexus 4, android 4.4.4
Android Studio 1.0.1
Regards,
Klym
yeah, I commented out the code that actually loads data. Will fix that.
Could you get the Mi Band to sync with Google Fit?
---------- Post added at 09:45 PM ---------- Previous post was at 08:49 PM ----------
motioncoding said:
I uploaded a very first Android App today but it can do only very few things yet - but currently it doesn't do the setup. I don't know that app so I don't know if it can interact with other devices and if, how good. But the Miband can detect sleep phases (pretty good for me) and can wake you, so I guess it could be possible.
Click to expand...
Click to collapse
There is an api for Sleep as Android.
https://sites.google.com/site/sleepasandroid/doc/sleepcloud-api
How about accelerometer raw data or sleep data, is it available?
Hi,
i try to connect my miBand with my laptop.
I found this site with some source code:
https://bitbucket.org/OscarAcena/mibanda
I installed all dependencies and run this as sudo python miband.py:
Code:
from gattlib import DiscoveryService
service = DiscoveryService("hci0")
devices = service.discover(2)
for address, name in devices.items():
print("name: {}, address: {}".format(name, address))
But after 10 seconds, I get an empty result.
My hciconfig shows this:
Code:
[email protected]:~$ hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:C2:C6:59:91:73 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:1475 acl:0 sco:0 events:71 errors:0
TX bytes:1723 acl:0 sco:0 commands:47 errors:0
Does anyone know, what to do?
I'd happily swing a few bucks for an app where it can link with google fit.
reconchrist said:
I'd happily swing a few bucks for an app where it can link with google fit.
Click to expand...
Click to collapse
Well...
I just have a quick questions about the possible functionality of the MiBand and what has been discovered thus far. Can the LEDs be individually controlled? Also, I know you can dismiss an alarm by touching the MiBand, does it detect this touch through motion or is there a capacitive switch in the MiBand?
I don't know how much help I can be, but I'm just curious about the technologies that they've been able to pack into the band.
Devo7v said:
I know you can dismiss an alarm by touching the MiBand, does it detect this touch through motion or is there a capacitive switch in the MiBand?
Click to expand...
Click to collapse
Seems there is no "touchpad", when needed (alarm and pairing) bracelet just detect vibrations from finger knocks.
Very likely it's internal firmware function and can't be accessed outside.
Also some advertising: useful additions for Mi Band
@motioncoding
Can you please tell me what Bluetooth profiles are supported by Mi Band ?
For this:
1. Go to the Bluetooth settings on your phone
2. There you will see the names of Bluetooth devices listed including the Mi Band
3. There will be a gear (or options) icon beside the name... tap on that and please post a screenshot of the screen that appears.
Thank You
{
"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"
}
Samsung Gear 360 Manager ported for use on (almost) all devices
LAST UPDATED: 26th April 2023, Version 1.5.00.1-1
Requirements:
- A Gear 360 2016 or 2017 (BOTH work with the same app)
- Android 5.0 or above
- A phone newer than like 2014. The Live View will not work on any phones with the equivalent or lower power than a Galaxy S5, but try it anyway
Latest Version Download:
Download
Important:
After installing, grant the app permission to access location in the background, in App Info > Permissions > Location > Allow all the time. This allows it to access the current WiFi network name while the app is not open, such as when you are actually connecting to the camera's WiFi.
If updating from an older version:
Please uninstall the old version first, since 1.5.00-1 needs a clean state for the phone gallery fix to work.
Firmware updates and Firmware source code
As of January 2021, Samsung have taken down the server that contained the firmware update config files for both models of the camera. Through the use of the Wayback Machine and some reverse engineering of the XML syntax read by the app, I was able to fully reproduce the firmware XMLs on GitHub. There is a new version (1.4.00.4-FW or above) of the app which can use these XMLs and download the binary files of the update from this forum post and install them on the camera. You need to set the firmware you want to use (or latest) in the settings (after connecting your camera) before the app will be able to download an update.
The Source Code is no longer available on Samsung's website, so has been mirrored on the same forum post. More info on what the files contain can be found on the GitHub repository linked above.
Screenshots:
Click a screenshot to enlarge it
Main Menu
Live View (camera is covered)
Gallery View
Image View
360 Image viewer
360 Video viewer (there's steam in this shot, that's not the camera quality!)
Settings
Mod Settings
Connecting to the camera
A longstanding "issue" with this app is its tendency to get stuck on a "Loading" screen when Gallery or Camera is selected. This can usually be resolved as follows:
1. Disable WiFi direct in the mod settings, since it is buggy. Restart the app. Verify you have granted the app background location (see above).
2. Open the app and verify the camera is connected with Bluetooth (if the Connect button appears on the main screen, tap it)
3. Disable mobile data, any VPNs and disconnect from the camera's WiFi if it is already connected
4. Open Camera or Gallery. The loading screen will show, and the WiFi settings will open (if you have that option disabled, open them now)
5. Wait for the camera's WiFi to appear. Connect to it. Return to the app.
6. The loading screen should disappear after a few seconds. If it doesn't, repeat from step 1 (it sometimes takes two attempts)
If the camera's WiFi automatically disconnects due to lack of internet, then read on...
Fixing WiFi automatically disconnecting
On some devices the camera's WiFi network will automatically be disconnected by the phone as it doesn't have internet. This can be resolved in one of three ways:
1. If a notification appears asking you if you want to stay connected, tap it and say yes. This decision will be remembered and it will no longer disconnect.
2. If you are running Android 8.0 or above, run
Code:
adb shell settings put global captive_portal_mode 0
3. If you are running Android 7.x or below, run
Code:
adb shell settings put global captive_portal_detection_enabled 0
Please note that options 2 and 3 will disable Captive Portal detection, if you wish to re-enable this then run the same command but with 1 in place of 0.
Known Issues:
- Live Broadcast doesn't work on 2016 camera or when using Soft AP. Cannot be fixed.
- WiFi Direct is buggy. Probably down to the app's mode being made for Samsung's modified WiFi direct, unlikely to be fixed
FAQ:
Q: What's the difference between WiFi direct/non WiFi Direct (Soft AP) mode?
A: WiFi Direct uses an experimental modification for enabling the Samsung WiFi Direct mode for all devices. It's quite buggy right now, but in theory allows you to update the camera's firmware (known to be dangerous, be careful). It also means you don't disconnect from the internet when using the app
Q: It's stuck on "Installing Samsung accessory service"
A: Install it manually
Q: I'm trying to use Live View/Gallery but the app gets stuck on loading
A: See the Connecting to the camera section above
Q: I have a 2017 camera and don't know the password for its WiFi!
A: Switch your camera to iOS mode (on the camera itself, using the menu). It will display a password, write that down. Switch back to the normal mode and continue as normal, entering the WiFi password you wrote down when prompted
Q: Does Live Broadcast work?
A: On the 2017 camera, when in WiFi direct mode apparently so. I've not tested it, and it doesn't work on any other configuration however
Q: What do the mod settings do?
A: See the "Mod Settings" section below
Q: There's a new version of the app on the Play Store, when will you update?
A: Check the last few pages of the thread. If the original APK has been posted already, the mod will be updated soon™. If it hasn't been, and you have a Samsung device compatible with the original app, please grab the APK and post it (the original APK is hard to get hold of)
Q: I found a crash!
A: Please post it in the thread, WITH A LOGCAT (don't know how to logcat? See here)
Mod Settings:
Since version 1.0.00.18, the mod has built in settings to allow a single unified APK. They can be found in the app's settings, under Mod Settings
WiFi Direct
Enable WiFi direct mode. Disabled by default as it's fairly buggy
Override Camera Recognition
Force your camera to appear to the app as a certain model. This isn't actually that useful, as it just causes crashes because of incompatible settings (default: don't override)
Always Show Live Broadcast
This is NOT aimed at allowing broadcast on 2016 cameras (they can't do it), but at countries where Live Broadcast is hidden. Enable this to always show it (disabled by default)
Automatically Open Settings
Automatically open the WiFi Settings/WiFi Direct settings when connecting to save you time (enabled by default)
Enable 4K
Enables 4K stitching and streaming from the camera, which may crash on very slow devices (enabled by default)
Porting Guide:
I don't plan to stop updating the mod any time soon, but if you want to port it yourself I have a rough guide available Here
Old Versions:
You probably shouldn't use these, they have bugs
1.5.00.1-1
1.4.00.4-FW
1.4.00.4 (without the firmware mirror, firmware updates will not work)
1.1.00.5
1.0.00.18
"Test" build 190617
1.0.00-2: WiFi Direct, Soft AP
Even older, pre-2017 camera app:
1.0.18-39
1.0.18-34: 4K, 2K
Thanks to:
- Bin4ry for the original port
Tools used:
- Apktool
- V10 Studio/Notepad++ for smali editing
- JEB for viewing Java code in APK
Disclaimer: You are responsible for your Gear 360 when using this app. Updating the firmware, whilst possible in WiFi Direct mode, may brick your device. It's recommended you find a compatible Samsung device and use that to update
Thanks to @Bin4ry for the original port, this is his OP from before work was transferred to me:
Deprecated archived post:
Hi all,
in the last days i was working on a port of the Gear 360 Manager app.
You should be able to use the app now even with non-Galaxy devices, or older Galaxy devices which are not officially supported by Samsung. I myself use it with a Sony Xperia Z5 without problems now
Mods:
1.) Removed device lock
2.) Forced 4K Video support, this way the app does NOT downgrade videos to 2k for other devices than Galaxy S7!
3.) Several Mods needed to get the app running on non-galaxy devices!
Requirements:
1.) You need to be on Android 5.0 or higher (App depends on API Level 21!)
2.) You need to install Samsung Accessory Service from playstore Link (they come preinstalled on many Samsung phones and the playstore may tell you incompatible )
Download the modified version (currently based on original Samsung Gear360 Manager version 1.0.4) here:
Update:
Version 1.0.10:
Force 2k Version : http://ul.to/5zsfz9mr
Force 4k Version: http://ul.to/kysjk5c8
IF YOU ARE RUNNING NOUGAT see this post of User Quinny899, he modded the new Nougat app:
https://forum.xda-developers.com/showpost.php?p=70377990&postcount=418
Known problem for this verison 1.0.10:
Make sure you allow the permissions (on my devices the permission are not requested automatically). To do that go to:
Settings -> Apps -> Gear 360 Manager -> Permissions -> Allow everything there.
Google-Drive Link:
https://drive.google.com/drive/folders/0B3l36qXIC0HddDlJc3lTaEZPbEk?usp=sharing
Old Verson 1.0.4:
Update 20.06.2016: Even longer videos can now be stiched in 4k [tested on Xperia Z5] and some more bugfixes!
Force 4k Version : http://ul.to/i8ieooet
Force 2k Version: http://ul.to/uznv4asf
Drive Links:
Force 4k Version : https://drive.google.com/open?id=0B3l36qXIC0HdaWxxT3g1TU1sMFU
Force 2k Version: https://drive.google.com/open?id=0B3l36qXIC0HdNXI4aF9SbEtWVFk
Make sure to download the file correctly, if you have any issues while installing make sure you are on Android 5 or higher!
Known issues:
1.) When switching to LiveView and Device browsing sometimes the app shows only "loading..." without doing something!
--> Please check if you phone is connected to the Cameras Wifi (normally Called "AP_GEAR360..."). If you are still connected to you homenetwork etc. please just manually connect to the gear's wifi and switch back to the gear manager app
2.) Sometimes the Samsung Accessory Service force closes while using the app!
--> If that happens go to Android Settings -> Apps -> choose the Samsung Accessory Service and click "Stop now", also go to the Gear 360 Manager and click "Stop now" here too! After that just open the Gear 360 manager again and continue working.
3.) Overlayicons in the Liveview are low-res and look crappy, i will try to fix that in a future release.
4.) On some phones the stiching of videos > 10 seconds will take very long time. In this case please use the Force 2k Version, 4k maybe too much for your phone to handle!
5.) Problably more, i don't use share to social media or stuff like that, so these points are still untested.
X.) If your phone seem not to support Live view you can try this mod by RostoVisualFX http://forum.xda-developers.com/showthread.php?t=3471526
That's it for now. If you have any issue please make sure to include a logcat output for me. Without an log i cannot help you.
Disclaimer: I am not responsible for anything that happens to your hardware.
Best Regards
My Note 4 completely died today. No power, not even with USB cable connected. Not sure if the installation of the app has caused this but I thought I'd mention it. I haven't had any issues with the phone before. Could be a total coincidence, of course. Will have to send the phone in for repair
I have attempted to use this software with the Note 3, but I am running into some issues.
Whenever I click on live view it seems to freeze up and I keep viewing a black screen with the camera options. After about 10 seconds, the screen turns black and then returns to the app after 10 more seconds. I am unsure if I am connecting through wifi direct.
When I try to share a gear 360 pic or video from my phone, it takes me to the flipboard share screen.
I can't view images or videos from the camera. Whenever I click on the media it attempts to stitch the images together, but only gets about 60% done.
I am able to view images and videos which have already been stitched and transferred from the computer, but it is pretty glitchy and doesn't always work.
Thanks for your work thus far, Bin4ry. This will be amazing if it works on many different phones.
efassbender said:
My Note 4 completely died today. No power, not even with USB cable connected. Not sure if the installation of the app has caused this but I thought I'd mention it. I haven't had any issues with the phone before. Could be a total coincidence, of course. Will have to send the phone in for repair
Click to expand...
Click to collapse
Hey,
that sounds very strange. But i cannot imagine how the app can cause such problems, because this is a normal userspace app and it does not have any access to relevant system files, bootloader or such. I can only think of a strange coincidence. Hope you will get your phone repaired soon. Maybe you some things, this guy tells a few tricks about the issue:
http://thedroidguy.com/2015/07/how-...hat-wont-turn-on-troubleshooting-guide-108854
billford22 said:
I have attempted to use this software with the Note 3, but I am running into some issues.
Whenever I click on live view it seems to freeze up and I keep viewing a black screen with the camera options. After about 10 seconds, the screen turns black and then returns to the app after 10 more seconds. I am unsure if I am connecting through wifi direct.
When I try to share a gear 360 pic or video from my phone, it takes me to the flipboard share screen.
I can't view images or videos from the camera. Whenever I click on the media it attempts to stitch the images together, but only gets about 60% done.
I am able to view images and videos which have already been stitched and transferred from the computer, but it is pretty glitchy and doesn't always work.
Thanks for your work thus far, Bin4ry. This will be amazing if it works on many different phones.
Click to expand...
Click to collapse
Hey, thanks for the feedback. Can you please provide me a logcat of the problems, like mentioned in the first post i really need such thing to be able to help.
Best Regards
I just tested on a nexus 4, it connect ok, but I can't see 360 folders or anything, I'll try to upload the log later.
Bluetooth settings crash
After installing the modded app everything worked fine. But now everytime i try to access the android bluetooth settings it crashes. Has anyone experienced the same problem?
blacksrv said:
I just tested on a nexus 4, it connect ok, but I can't see 360 folders or anything, I'll try to upload the log later.
Click to expand...
Click to collapse
Please provide the log ☺
Hasmax78 said:
After installing the modded app everything worked fine. But now everytime i try to access the android bluetooth settings it crashes. Has anyone experienced the same problem?
Click to expand...
Click to collapse
Strange thing. Try to uninstall the app and Samsung accessory service. This should not really happen!
The 2K versions opens on a Motorola X (2014), it connects to the Gear 360. Clicking on live view begins to load the gui with all the buttons and then the screen goes black.
The log is from the app aLogcat, hope it helps:
Code:
--------- beginning of main
W/InputEventReceiver(26907): Attempted to finish an input event but the input event receiver has already been disposed.
I/WebViewFactory(26907): Loading com.google.android.webview version 51.0.2704.81 (code 270408100)
I/cr_LibraryLoader(26907): Time to load native libraries: 15 ms (timestamps 5548-5563)
I/cr_LibraryLoader(26907): Expected native library version number "51.0.2704.81", actual native library version number "51.0.2704.81"
V/WebViewChromiumFactoryProvider(26907): Binding Chromium to main looper Looper (main, tid 1) {3448aa18}
I/cr_LibraryLoader(26907): Expected native library version number "51.0.2704.81", actual native library version number "51.0.2704.81"
I/chromium(26907): [INFO:library_loader_hooks.cc(143)] Chromium logging enabled: level = 0, default verbosity = 0
I/cr_BrowserStartup(26907): Initializing chromium process, singleProcess=true
E/ApkAssets(26907): Error while loading asset assets/natives_blob_64.bin: java.io.FileNotFoundException: assets/natives_blob_64.bin
E/ApkAssets(26907): Error while loading asset assets/snapshot_blob_64.bin: java.io.FileNotFoundException: assets/snapshot_blob_64.bin
I/Adreno-EGL(26907): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.00.02.006.020_msm8960_LA.AF.1.1_RB1__release_AU ()
I/Adreno-EGL(26907): OpenGL ES Shader Compiler Version: E031.25.03.06
I/Adreno-EGL(26907): Build Date: 03/30/15 Mon
I/Adreno-EGL(26907): Local Branch: mybranch8688311
I/Adreno-EGL(26907): Remote Branch: quic/LA.AF.1.1_rb1.16
I/Adreno-EGL(26907): Local Patches: NONE
I/Adreno-EGL(26907): Reconstruct Branch: AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.00.02.006.020 + 9b2699f + 2215637 + 60aa592 + f2362e6 + 5c64f59 + 82411a1 + 1f36e07 + NOTHING
W/cr_media(26907): Requires BLUETOOTH permission
ThomasKru said:
The 2K versions opens on a Motorola X (2014), it connects to the Gear 360. Clicking on live view begins to load the gui with all the buttons and then the screen goes black.
The log is from the app aLogcat, hope it helps:
Code:
--------- beginning of main
W/InputEventReceiver(26907): Attempted to finish an input event but the input event receiver has already been disposed.
I/WebViewFactory(26907): Loading com.google.android.webview version 51.0.2704.81 (code 270408100)
I/cr_LibraryLoader(26907): Time to load native libraries: 15 ms (timestamps 5548-5563)
I/cr_LibraryLoader(26907): Expected native library version number "51.0.2704.81", actual native library version number "51.0.2704.81"
V/WebViewChromiumFactoryProvider(26907): Binding Chromium to main looper Looper (main, tid 1) {3448aa18}
I/cr_LibraryLoader(26907): Expected native library version number "51.0.2704.81", actual native library version number "51.0.2704.81"
I/chromium(26907): [INFO:library_loader_hooks.cc(143)] Chromium logging enabled: level = 0, default verbosity = 0
I/cr_BrowserStartup(26907): Initializing chromium process, singleProcess=true
E/ApkAssets(26907): Error while loading asset assets/natives_blob_64.bin: java.io.FileNotFoundException: assets/natives_blob_64.bin
E/ApkAssets(26907): Error while loading asset assets/snapshot_blob_64.bin: java.io.FileNotFoundException: assets/snapshot_blob_64.bin
I/Adreno-EGL(26907): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.00.02.006.020_msm8960_LA.AF.1.1_RB1__release_AU ()
I/Adreno-EGL(26907): OpenGL ES Shader Compiler Version: E031.25.03.06
I/Adreno-EGL(26907): Build Date: 03/30/15 Mon
I/Adreno-EGL(26907): Local Branch: mybranch8688311
I/Adreno-EGL(26907): Remote Branch: quic/LA.AF.1.1_rb1.16
I/Adreno-EGL(26907): Local Patches: NONE
I/Adreno-EGL(26907): Reconstruct Branch: AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.00.02.006.020 + 9b2699f + 2215637 + 60aa592 + f2362e6 + 5c64f59 + 82411a1 + 1f36e07 + NOTHING
W/cr_media(26907): Requires BLUETOOTH permission
Click to expand...
Click to collapse
Thanks. But the logcat is not complete it is cut after the first startup lines. I need a full one where the error of the gear360 manager is shown.
If alogcat don't give you a full one please use adb logcat and reroute output to a file.
Adb logcat > mylog.txt
This creates the log file in your current directory.
Thanks and best regards
could it work on a tablet ?
(like the NVIDIA SHIELD Tablet K1 ?)
Thanks !
- sorry for my english, a french guy
VicTH said:
could it work on a tablet ?
(like the NVIDIA SHIELD Tablet K1 ?)
Thanks !
- sorry for my english, a french guy
Click to expand...
Click to collapse
Could be you need to test, i really cannot tell you.
Best Regards
It works on Galaxy Tab S.
such you go with the theme of passing the videos to mobile and able to share editarles and from the phone?
I have the note 4 (sm-n910C) and trying to get photos and videos closes.
angila said:
such you go with the theme of passing the videos to mobile and able to share editarles and from the phone?
I have the note 4 (sm-n910C) and trying to get photos and videos closes.
Click to expand...
Click to collapse
Saving and sharing stitched photos works. I do find that after viewing a few photos it won't complete the stitch or transfer. It almost seems like a buffer or memory issue of some sort. Restarting the app makes it work again. Video transfer still doesn't work (yet).
I have updated to version today (20.06.2016), please test and report back WITH logcats in case of problems.
With this version i am able to fully download and stich 4k Videos on my Xperia Z5, the stiching is as fast as on a Galaxy S7, i cannot see any difference there.
Also i cannot find any more bugs which are important
If on your device bugs occur please report them and DO A LOGCAT!
Without the logcat i cannot fix it!
Best Regards
Firmware-Update
Hello,
it is running on my nvidia shield. Thank you! But I have problems to use it to update the firmware of the gear 360. I can download the update from the net, put trying to intsall results only in endless "searching for update". Is there a solution?
Best regards
Caulius
i have heard that people are having some issues until the update starts, make sure that you are properly connected in wifi and bt to the camera.
Best Regards
Installed your latest June 20th 2k version on my Note 4 (Marshmallow).
When I save a video from the Gear 360 to my device, it crashes at 100% and nothing shows up in My Device tab after app restart.
However, if I browse to DCIM/Gear 360/ in file manager, I see the newly stitched video there. Now if I 'open with' and select Samsung Gear 360 Manager app, it opens and plays the 360 video in all its glory.
And then after a little while, when I reopen the app, it finally shows it there in the My Device tab.
There was one instance where in file manager, the final stitched video was appended with ".MP4.TEMP". I removed the .TEMP and "open with: Samsung Gear 360 Manager" and it worked.
logcat:
https://drive.google.com/open?id=0B-lAyfkO-k_GNWkwVGVBS3J5Mkk
Thanks!