Sd card access fails for many apps - Galaxy S3 Neo Q&A, Help & Troubleshooting
Hi,
I rooted my device and used a sd fix app but some apps cannot access the sd card (tapatalk, whatsapp,and many more)
Has someone an Idea?
It seems that there is a problem with the correct path
Could someone post a correctly working platform.xml?
And a mount listing?
Here is mine.
?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2008 The Android Open Source Project
Copyright (C) 2013 Broadcom Corporation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This file is used to define the mappings between lower-level system
user and group IDs and the higher-level permission names managed
by the platform.
Be VERY careful when editing this file! Mistakes made here can open
big security holes.
-->
<permissions>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are associating low-level group IDs with
permission names. By specifying such a mapping, you are saying
that any application process granted the given permission will
also be running with the given group ID attached to its process,
so it can perform any filesystem (read, write, execute) operations
allowed for that group. -->
<permission name="android.permission.BLUETOOTH_ADMIN" >
<group gid="net_bt_admin" />
</permission>
<permission name="android.permission.BLUETOOTH" >
<group gid="net_bt" />
</permission>
<permission name="android.permission.BLUETOOTH_STACK" >
<group gid="net_bt_stack" />
</permission>
<permission name="android.permission.NET_TUNNELING" >
<group gid="vpn" />
</permission>
<permission name="android.permission.SYSTEM_GROUP_INTERNAL" >
<group gid="system" />
</permission>
<permission name="android.permission.INTERNET" >
<group gid="inet" />
</permission>
<permission name="com.sec.android.permission.CAMERA" >
<group gid="camera" />
</permission>
<permission name="android.permission.READ_LOGS" >
<group gid="log" />
</permission>
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_MTP" >
<group gid="mtp" />
</permission>
<permission name="android.permission.NET_ADMIN" >
<group gid="net_admin" />
</permission>
<!-- The group that /cache belongs to, linked to the permission
set on the applications that can access /cache -->
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM" >
<group gid="cache" />
</permission>
<!-- RW permissions to any system resources owned by group 'diag'.
This is for carrier and manufacture diagnostics tools that must be
installable from the framework. Be careful. -->
<permission name="android.permission.DIAGNOSTIC" >
<group gid="input" />
<group gid="diag" />
</permission>
<!-- Group that can read detailed network usage statistics -->
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY">
<group gid="net_bw_stats" />
</permission>
<!-- Group that can modify how network statistics are accounted -->
<permission name="android.permission.MODIFY_NETWORK_ACCOUNTING">
<group gid="net_bw_acct" />
</permission>
<permission name="android.permission.LOOP_RADIO" >
<group gid="loop_radio" />
</permission>
<!-- The group that releated with VPN -->
<permission name="android.permission.SAMSUNG_MODIFY_ROUTE" >
<group gid="net_admin" />
</permission>
<permission name="android.permission.SAMSUNG_TUNTAP" >
<group gid="vpn" />
</permission>
<permission name="android.permission.SAMSUNG_MODIFY_IPTABLES" >
<group gid="net_raw" />
</permission>
<!-- The group that releated with VPN -->
<permission name="com.sec.android.SAMSUNG_MODIFY_ROUTE" >
<group gid="net_admin" />
</permission>
<permission name="com.sec.android.SAMSUNG_TUNTAP" >
<group gid="vpn" />
</permission>
<permission name="com.sec.android.SAMSUNG_MODIFY_IPTABLES" >
<group gid="net_raw" />
</permission>
<!-- The group that releated with URL -->
<permission name="com.sec.android.SAMSUNG_GET_URL" >
<group gid="secnetfilter" />
</permission>
<!-- Group that can use gscaler -->
<permission name="com.sec.android.permission.USE_GSCALER" >
<group gid="graphics" />
</permission>
<!-- Except for SysScope, DO NOT USE this permission. -->
<permission name="com.sec.android.app.sysscope.permission.ACCESS_SYSTEM_INFO_SYSSCOPE_ONLY" >
<group gid="radio" />
</permission>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are assigning high-level permissions to specific
user IDs. These are used to allow specific core system users to
perform the given operations with the higher-level framework. For
example, we give a wide variety of permissions to the shell user
since that is the user the adb shell runs under and developers and
others should have a fairly open environment in which to
interact with the system. -->
<assign-permission name="android.permission.MODIFY_AUDIO_SETTINGS" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="media" />
<assign-permission name="android.permission.WAKE_LOCK" uid="media" />
<assign-permission name="android.permission.UPDATE_DEVICE_STATS" uid="media" />
<assign-permission name="android.permission.UPDATE_APP_OPS_STATS" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="graphics" />
<!-- This is a list of all the libraries available for application
code to link against. -->
<library name="android.test.runner"
file="/system/framework/android.test.runner.jar" />
<library name="javax.obex"
file="/system/framework/javax.obex.jar"/>
<!--
<library name="javax.btobex"
file="/system/framework/javax.btobex.jar"/>
-->
</permissions>
Click to expand...
Click to collapse
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=697168k,nr_inodes=130216,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=750,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=697168k,nr_inodes=130216,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware-modem vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/hidden /preload ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/dev/block/vold/179:65 /mnt/media_rw/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
/mnt/media_rw/extSdCard /storage/extSdCard sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=unified 0 0
/dev/block/dm-0 /mnt/asec/com.google.android.apps.docs.editors.docs-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,errors=continue
Click to expand...
Click to collapse
Related
[Q] sd card write fix applied, now apps keep crashing
Running 4.4.2 on ATT 1337 with NC1. Ran towelroot and SuperSU so I could use TB to get all my stuff from my Note 3 to my S4 (company downgrade, don't ask). Edited the platform.xml to this: <permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission> <permission name="android.permission.WRITE_MEDIA_STORAGE" > <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission> Now I get "email has stopped working", "Flipboard has stopped working" popups every 3 seconds. I "ok" them and they come right back. Many other apps do this as well randomly. Playstore will not work either. I assume the platform.xml change FUBARED things. But even with ES file explorer set to "root explorer" it will not save the changes again. How can I restore the platform.xml file?!?! Also ran root checker, says "Sorry this device has no root." WTF is going on?
Galaxy s4 i9500 lollipop problem
Hey guys my s4 was on stock 4.2.2 jellybean firmware but when i heard that lollipop was finally available for my device it was tthen i decided to update to 5.0.1 After updating i have been facing ISSUES with my phone's sd card writing operations I cannot copy files from pc using usb cable neither can i transfer files from pc using superbeam No new folder can be created in sd card and and i can create folders in phone storage but it shows connection error everytime I would be very thankful to anyone who can help me sort this problem P.s Please try to suggest methods which dont require rooting
Kitkat and Lollipop changed the way Android used the SD card - http://www.androidcentral.com/kitkat-sdcard-changes You can fix this, but you'll need to be rooted. Not heard of any non rooted solutions personally.
dave106 said: Kitkat and Lollipop changed the way Android used the SD card - http://www.androidcentral.com/kitkat-sdcard-changes You can fix this, but you'll need to be rooted. Not heard of any non rooted solutions personally. Click to expand... Click to collapse I really need to fix this so i will even root I will use towelroot for the purpose can you tell that what would i need to do further to restore full sd card access
Once rooted, goto system/etc/permissions and edit 'platform.xml' Find this section - <permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> <group gid="sdcard_rw" /> </permission> And add another line so it looks like this - <permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission> Save and reboot
dave106 said: Once rooted, goto system/etc/permissions and edit 'platform.xml' Find this section - <permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> <group gid="sdcard_rw" /> </permission> And add another line so it looks like this - <permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission> Save and reboot Click to expand... Click to collapse thanx for help bro
[MOD] [GUIDE] [ 5.0.2 ] How Fix backup app on SD Card in Sony Lollipop 5.0.2
Hi Will show you how to fix the problem of reading and writing to the SD card in Sony Lollipop 5.0.2 Request: -Sony Lollipop 5.0.2 -ROOT -Text editor ( I use notepad ++ ) 1.On your phone, find the file platform.xml ROOT / system / etc / permission / Copy it to your computer using a text editor, open and add these lines : Code: <permission name="android.permission.READ_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> </permission> <permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> <group gid="sdcard_rw" /> [COLOR="red"] <group gid="media_rw" />[/COLOR] </permission> <permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> <group gid="sdcard_rw" /> <group gid="sdcard_all" /> </permission> <permission name="android.permission.WRITE_MEDIA_STORAGE" > <group gid="sdcard_rw" /> [COLOR="Red"] <group gid="media_rw" /> [/COLOR] </permission> <permission name="android.permission.ACCESS_MTP" > <group gid="mtp" /> </permission> 2.Save and copy the phone 3. Using Root Explorer Important -Copy file To System -Set Permission Using Root Explorer ( rw- r-- r-- ) -Move The platform.xml To /system/etc/permission/ Folder -Reboot The Phone. 4. Enjoy Creadits: RXS MoonBreakers Team Be aware that you can damage your phone. I do not take responsibility for damage to your phone. You do so at your own risk. everything works on Titanium Backup
res
Good one bro @Ambor ^^
Pandemic said: Good one bro @Ambor ^^ Click to expand... Click to collapse Thanks
Thanks Bro @Ambor ??
Ambor said: Thanks Click to expand... Click to collapse Nice tutorial bro @Ambor
Thanks, marvelous post indeed.
dsa88 said: Thanks, marvelous post indeed. Click to expand... Click to collapse Thanks
Recon Jet Basic Info
So, I just got my Recon Jet (the self-declared "most powerful wearable computer" running Android 4.1, without Google services), and started doing some basic poking around. What would people like to know? So far my basic impression is that I feel like I'm using a flagship smartphone running feature-phone software. All the specs are awesome, but the device does almost nothing out of the box, and there are no apps yet. The entire time I'm wearing it, it's like the device is screaming SOMEONE PLEASE MAKE A CUSTOM ROM WITH GOOGLE GLASSWARE SUPPORT. Anywho, on to the nerdy stuff. I didn't have the guts to try a fastboot oem unlock, so I didn't get very far in fastboot: Code: >fastboot -i 0x2523 getvar all (bootloader) product: Jet_Fastboot (bootloader) cpu: OMAP4430 (bootloader) cpurev: ES2.3 (bootloader) secure: GP (bootloader) serialno: **redacted** (bootloader) userdata_size: 6501231 KB (bootloader) Flash Slot: EMMC(1) all: finished. total time: 0.031s >fastboot -i 0x2523 oem ? ... FAILED (remote failure) finished. total time: 0.016s >fastboot -i 0x2523 reboot rebooting... finished. total time: 0.000s In ADB, without root, also didn't find too much interesting, but then again wasn't looking for anything in particular. Code: [email protected]:/ $ df df Filesystem Size Used Free Blksize /dev 306M 32K 306M 4096 /mnt/asec 306M 0K 306M 4096 /mnt/obb 306M 0K 306M 4096 /system 503M 237M 266M 4096 /data 6G 255M 5G 4096 /cache 251M 24M 227M 4096 /factory 314M 179M 135M 4096 /storage/sdcard0 6G 255M 5G 4096 [email protected]:/ $ cat /proc/partitions cat /proc/partitions major minor #blocks name 179 0 7634944 mmcblk0 179 1 128 mmcblk0p1 179 2 2048 mmcblk0p2 179 3 128 mmcblk0p3 179 4 384 mmcblk0p4 179 5 327680 mmcblk0p5 179 6 16 mmcblk0p6 179 7 8192 mmcblk0p7 259 0 8192 mmcblk0p8 259 1 524288 mmcblk0p9 259 2 262144 mmcblk0p10 259 3 6501232 mmcblk0p11 [email protected]:/ $ ls -al /dev/block/platform/omap/omap_hsmmc.1/by-name block/platform/omap/omap_hsmmc.1/by-name < lrwxrwxrwx root root 2015-04-18 21:04 boot -> /dev/block/mmcblk0p8 lrwxrwxrwx root root 2015-04-18 21:04 bootloader -> /dev/block/mmcblk0p2 lrwxrwxrwx root root 2015-04-18 21:04 cache -> /dev/block/mmcblk0p10 lrwxrwxrwx root root 2015-04-18 21:04 crypto -> /dev/block/mmcblk0p6 lrwxrwxrwx root root 2015-04-18 21:04 efs -> /dev/block/mmcblk0p5 lrwxrwxrwx root root 2015-04-18 21:04 misc -> /dev/block/mmcblk0p4 lrwxrwxrwx root root 2015-04-18 21:04 recovery -> /dev/block/mmcblk0p7 lrwxrwxrwx root root 2015-04-18 21:04 system -> /dev/block/mmcblk0p9 lrwxrwxrwx root root 2015-04-18 21:04 ubootenv -> /dev/block/mmcblk0p3 lrwxrwxrwx root root 2015-04-18 21:04 userdata -> /dev/block/mmcblk0p11 lrwxrwxrwx root root 2015-04-18 21:04 xloader -> /dev/block/mmcblk0p1 [email protected]:/ $ ls ls acct cache charger config d data default.prop dev etc factory init init.goldfish.rc init.omap4jetboard.rc init.omap4jetboard.usb.rc init.rc init.trace.rc init.usb.rc mnt proc res root sbin sdcard storage sys system ueventd.goldfish.rc ueventd.omap4jetboard.rc ueventd.rc vendor Note that Recon devices do not use a VendorID recognized by standard adb and fastboot, so you will have to take extra steps to use these tools. Specifically, to use ADB, you will need to modify (or create) an adb_usb.ini file containing 0x2523, and fastboot will have to use the -i option. Users on the sparsely-used Recon forums (addressing almost exclusively Recon's previous generation of products) report being able to sideload APKs, but I can't think of any apps I would like on my face that don't rely on Google Play Services. Any suggestions? Mods, please feel free to move this to the appropriate forum for Recon Jet, as soon as one exists. Until then, this seemed to me like the best place.
System app listing Code: <?xml version="1.0" encoding="utf-8"?> <installed-packages> <package name="android" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.backupconfirm" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.bluetooth" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150211.201015" /> <package name="com.android.certinstaller" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.defcontainer" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.htmlviewer" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.inputdevices" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.keychain" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.packageinstaller" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.applications" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.calendar" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.contacts" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.downloads" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.downloads.ui" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.drm" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.media" versionCode="509" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.settings" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.telephony" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.providers.userdictionary" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.provision" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.settings" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.sharedstoragebackup" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.smspush" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.systemui" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.android.vpndialogs" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.dsi.ant.plugins.antplus" versionCode="30100" versionName="3.1.0" /> <package name="com.dsi.ant.service.socket" versionCode="40700" versionName="4.7.0" /> <package name="com.dsi.ant.stonestreetoneantservice" versionCode="1" versionName="1.0" /> <package name="com.reconinstruments.QuickstartGuide" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.agps" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.appinstaller" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.applauncher" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.battery.logger" versionCode="1" versionName="1.0" /> <package name="com.reconinstruments.ble_ss1" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.camera" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.compass" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.dashboard" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.dashcompass" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.dashlauncherredux" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.dashlivestats" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.dashwarning" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.geodataservice" versionCode="1" versionName="1.0" /> <package name="com.reconinstruments.heading" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.hfpservicess1" versionCode="1" versionName="1.0" /> <package name="com.reconinstruments.hudserver" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> <package name="com.reconinstruments.hudservice" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.itemhost" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.jetapplauncher" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.jetconnectdevice" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.jetmusic" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.jetsensorconnect" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.jetunpairdevice" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.lispxml" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.lockdown" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.maps" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.mapservicess1" versionCode="1" versionName="1.0" /> <package name="com.reconinstruments.messagecenter" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.mfitester" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.myactivities" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.nativetest" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.offsetkeyboard" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.passcodelock" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.phone" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.power" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.quickactions" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.socialsharing" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.symptomchecker" versionCode="7047" versionName="4.1.1" /> <package name="com.reconinstruments.systemui" versionCode="7047" versionName="4.1.1" /> <package name="com.rxnetworks.rxnservicesxybrid" versionCode="7047" versionName="4.1.1" /> <package name="com.svox.pico" versionCode="1" versionName="1.0" /> <package name="jp.co.omronsoft.openwnn" versionCode="16" versionName="4.1.2-eng.linux-jenkins.20150414.021802" /> </installed-packages>
That would be awesome to see a google glass ROM port over. I would love to use these for navigation when I am on my motorcycle! The forums that Recon has is dismal to say the least. Hopefully there will be more support as people get their hands on them.
Common someone please help us out!!
well, this is now available on some sites, but most of the major sites like amazon still have the Jet for preorder for July 1st. Hopefully, when this gets in the hands of the mod gods, great things will happen. alot of potential here, with the open sdk and all.
Just picked up a pair of Recon Snow2 goggles, which is fundamentally the same thing as Jet, according the build.props. Would be great to get a section dedicated to Recon products.
has anyone tried rooting the Jet yet? I got my hands on one and would really like to be able to root it!
Hello everyone, I got the recon jet and I think the on board gps is not working. I'm hoping it's a software issue and not hardware. I'm new here and I'm no hacker but I can follow instructions. If any one can help me find the solution I'd greatly appreciate it.
I have my recon jet..... what to do with it the recon instruments site is dead. My recon jet asks for activation. is there any chance to use it somehow?
Anyone with an Idea?
You can still activate it on the website (it says password not accepted or smtp issue but it still works) Dev part of the website is down so there is no way to access the sdk to develop any new app but basic usage is working.
Lost my recon jet adb drivers anyone happen to have them?
Did you get the ADB driver? I have a copy if you still need it. More generally, with Recon now gone, and the JET/Snow2 products no longer supported, it makes sense to try make a useful custom image that can be community supported. Is anyone looking at this?
Activating Recon Jet in 2020 Angelbast said: You can still activate it on the website (it says password not accepted or smtp issue but it still works) Dev part of the website is down so there is no way to access the sdk to develop any new app but basic usage is working. Click to expand... Click to collapse I am trying to activate Recon Jet but both the application and website do not work. The display on he glasses is stuck on the 'connect to a PC via USB and activate' screen. The device is detected by the operating system as an MTP device. I tried to connect with the ADB driver included within the glasses and accessed using via MTP, one obtained from recon website (using the web archive) and ADB installed on Ubuntu via apt. None can detect the device connected via USB. Does anyone know a way to get past the activation screen or to get ADB to connect to the device? Thank you.
dxxb2020 said: Activating Recon Jet in 2020 I am trying to activate Recon Jet but both the application and website do not work. The display on he glasses is stuck on the 'connect to a PC via USB and activate' screen. The device is detected by the operating system as an MTP device. I tried to connect with the ADB driver included within the glasses and accessed using via MTP, one obtained from recon website (using the web archive) and ADB installed on Ubuntu via apt. None can detect the device connected via USB. Does anyone know a way to get past the activation screen or to get ADB to connect to the device? Thank you. Click to expand... Click to collapse I have the same problem been trying for two days still can't get it to activate.
gpatech said: Did you get the ADB driver? I have a copy if you still need it. More generally, with Recon now gone, and the JET/Snow2 products no longer supported, it makes sense to try make a useful custom image that can be community supported. Is anyone looking at this? Click to expand... Click to collapse Hi Can i try it to see if it works. link please
Just pulled out my old Snow2 goggles. Seem to boot up fine and are working. Anyone still using Jets or Snow2? Anyone doing anything interesting with them?
I am hoping to get some Reconjet glasses up and working when they arrive this week, for paragliding , to display flightdata. But it appears all the support has gone awol. I have been trying for ages to find an archive with the Recon SDK to let me do it but without luck. Can anyone assist?. I think the glass is basically the same as the snow2 , snow2 looks a better helmet frendly configuration for my application to be fair. regards
PLease help. Does anyone have the Recon Uplink Desktop App for windows can seen to fine it anywhere.
Some how I factory reset my Snow2 to a very old version. Anyone know how to get back to the latest?
SD card r/w
I'm using an sd card from my old s5 on a rooted nvidia shield 16 gb and it now let me made edits to that sd card. Is there a fix to this or what? It's usually fixed through root but I am drawing a blank for this.
You need to edit external storage r w permissions, I believe if you download foldermount it does this automatically. I don't have the exact file that you edit in mind yet but will update soon with directions, unless someone else can get here first?
This would be extremely helpful. Sent from my SM-G925V using Tapatalk
To fix external drive r/w I did the following (root required): Go to /system/etc/permissions/ with a file manager. Locate platform.xml file. Open it with an editor. Find: Code: <permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> <group gid="sdcard_rw" /> </permission> and add the line <group gid="media_rw" /> You will have in the end: Code: <permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_r" /> <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission> Reboot.
Thank you for this!! Sent from my SM-G925V using Tapatalk