i noticed elocity is not using the native ar6000 driver , so if they included the patched wpa_supplicant, then yes.. but i have not tested it.
Yeah pretty much!... did you not have the SU issues with version 1.0? If not I'll just update to that. I can't get Bank of America or Tasker to install even using the build.prop from the ROM, there's something other than the fingerprint in this ROM making the magic happen.
Here's the link for 1.0 with full gapps and working SU: http://dext3r.komodin.org/ElocityA7/ElocityModv10.zip
And build.prop if you still want it: http://xdaforums.com/attachment.php?attachmentid=474471&d=1293480448
im a little confused..
i added the "su" command to the build, it never was there...
I've been using "su" since it came out of the box. Not sure what you mean by "it never was there".
Dexter... i did a full wipe and still had the su issue. I installed version 1.0 and added the superuser application from the market and it works perfectly. I dunno, but seeing this device never needed su out of the box maybe something with the way you added it to the rom in 1.0a.
I've been using "su" since it came out of the box. Not sure what you mean by "it never was there".
ok, something crossed my mind now.. i put "su" always in /system/bin and im quite sure your "su" is located in /system/xbin now, so thats why my superuser.apk also fails as its made for this version and your su is not. or simply the su in /system/xbin has no suid 0 set.
edit:
ok, i was right. in xbin folder another SU was found, so that one is not compatible with this superuser.apk..
its fixed and im uploading a hopefully perfect 1.0b now.
ok, something crossed my mind now.. i put "su" always in /system/bin and im quite sure your "su" is located in /system/xbin now, so thats why my superuser.apk also fails as its made for this version and your su is not. or simply the su in /system/xbin has no suid 0 set.
edit:
ok, i was right. in xbin folder another SU was found, so that one is not compatible with this superuser.apk..
its fixed and im uploading a hopefully perfect 1.0b now.
Thanks and great to hear you feel the 1.0b works out great.
maybe the downloaded zip is corrupted? , but i think you should try another "wipe/factory reset" again after zip update installation?Hi Dexter. I followed instructions, did a factory reset before installing your Update.zip 1.0b, everything seems to be fine, I get the "Updated the device: Reboot the device... Reboot now!" message, and then the a7 gets stuck in the elocity splash screen, displaying it again and again..
What could I be doing wrong?
Hi Dexter. I followed instructions, did a factory reset before installing your Update.zip 1.0b, everything seems to be fine, I get the "Updated the device: Reboot the device... Reboot now!" message, and then the a7 gets stuck in the elocity splash screen, displaying it again and again..
What could I be doing wrong?
Thanks!
Any idea why the Sirius XM app just hangs out at initial "Cheking for Upgrades" after the sign-in screen? I see that some other tablets are having similiar issues with the 1.1.0 version from Google Market that was suppose to address Froyo issues
sounds really strange.. as our Tegra2 tablets has no "verification" process added, you might just have a corrupt zip.. that sounds really like the problem here..I had that happen when I upgraded from the stock version (with the update from Elocity) to the first version of this rom. I didn't wipe the cache first.
I will report back on an update very soon.
I've been using "su" since it came out of the box. Not sure what you mean by "it never was there".