NOTES: IT INSTALLS FINE ON THE LATEST FIRMWARE. *ONLY FOR THE LATEST APRIL2011 FIRMWARE DUE TO BUILD PROP CHANGES*
THERE ARE NO SIGNATURE PROBLEMS; ALL APK'S AS FOUND FROM CYANOGENMOD. USED ORIGINAL CONTAINER FOR VENDING.APK TO AVOID SIGNATURE ISSUES.
ALSO ADDED CALENDAR AND TEXT MESSAGING APPLICATIONS.
download:
Code:
http://www.multiupload.com/HCVHTF0QHM
--
instructions: FACTORY RESET FIRST w/ latest firmware (april 17th)
1
boot to recovery
1A
power on, let go, hold power until it says starting recovery kernel, then let go of power
1B
press the "home" button, and use the menu to wipe cache, factory reset, flash the factory rom, and wait for first boot w/ ac power plugged in.
2
after first boot, turn unit off, and turn back on and boot into recovery again.
2A
flash the a7-gapps zip provided (remember to rename it to update.zip to work w/ recovery).
2B
CHOOSE FACTORY RESET (this wipes existing data that may conflict with install)
2C
REBOOT
congradulations, you should now have a FULLY WORKING MARKET PLACE.
UPDATED NOTES; this is the the 1.82 market that comes w/ the latest gapps for tegra from cyanogenmod (gapps-mdpi-tegra-20101020-signed). i patched it using the same smali patches applied in the patched market found in dexter's 1.2 rom, minus the androidmanifest.xml. this may account for it not autoupdating the market itself, but for today i'll take full market access on the old interface than limited access on the new market.
i tested this patched market to show "skyfire" and "qik" video players, and i added further build prop and permission settings that provided more search results; searching for 'gps' and 'video' results went up from 3300 to about 4500.
i intentionally did not provide larger apps like youtube, maps and twitter as they are downloadable from the market.
----
This is the google apps, libs and permissions that i extracted from cyanogenmod's gapps package and provided as a standalone update.zip for those wishing to have the google android market on their tablet, but not wanting to deal w/ a third party experimental rom requiring regular updates and wipes.
I hope you enjoy using the google market and applications with the latest stock rom. My wife does, and can now enjoy her working tablet w/ farmville.
--
Please, hit the lil' DONATE button under my name if i helped to make your life a lil' easier, or your android device more enjoyable. Thank you!
--
new firmware available here: eLocity Customer Support
i dont think it will install on a new update from elocity, as they use a different test signature than i do. and the signature check fails..
did you test on top of original stock?
if you check logs you will see framework fails to install, as signature does not match, and package will be ignored.
so basically why i release a full image, as all apk + framework needs to be signed correctly.
but maybe you did something extra? different?
kinda covered all the details in the op. the gapps update i made flashed on the misses phone okay after flashing the latest firmware available from the elocity support site in the link at the bottom of my post.
i did also detail that prior to that i had manually wiped the cache partition and flashed the latest recovery image from said update using the nvflash tools from nvidia. i did this due to the device being bricked w the common recovery error about recovery.c and the cache partition. i was able to adb into the device tho, and upon seeing all the random apks and files having radio user or group permissions told me somethings wrong w the rom. when i reflashed said rom, i still observed odd permissions,group settings (ive been finding and fixing these in modroms lately), so i went to the latest stock, got my usb/sd functioning as intended, checked that the permissions didnt look screwey in stock (all apks and general files set to root,root where expected instead of root,radio, which were coincidently mostly your gapps) then decided to make my own gapps w your files by comparing the gapps package for my x10, since you must be building the rom instead of modifying to get/repair fc's in the settings apk.
no surprise gapps works on this tablet like an aosp addon, as the stock rom fits the same definition of being a rom free of google apps.
i do believe the latest firmware update has binary different/newer files than whats in your rom. the recovery image is a different size too. not sure if thats resulted from changes you had made, or just reflects that the update from elocity is newer than whats in your rom.
let me know if theres any other details i can help w. otherwise, regarding signatures; thats never been an issue for me and android. the elocity recovery appears to have no problem flashing w test keys, and ive never had to resign a modified apk for an android rom.
now if we were talking symbian, then i would have to resign. android doesnt care that i'm supplyin new apk's. maybe only if i'd modified an existing apk that android had already cached the keys for, or had exclusively modified an apk in an existing updatezip w/ out resigning the zip.
Sent from my X10i using Tapatalk
btw - thanks for the great rom for the misses tablet, mister dexter. also, analyzing your updates gave me the idea to redudantly assign permissions for every file in the install script, even tho one would assume all the files copied would be 644 by default, but sometimes being redudant is better than assuming.
EDIT: doublechecked, you did use a dated (1-07) recovery.img instead of the factory one provided w/ the newer rom you would have modded [original files dated 2-10, your modified files dated 3-20(boot.img) and 3-21(system.img)].
Sent from my X10i using Tapatalk
bestialbub said:
EDIT: doublechecked, you did use a dated (1-07) recovery.img instead of the factory one provided w/ the newer rom you would have modded [original files dated 2-10, your modified files dated 3-20(boot.img) and 3-21(system.img)].
Click to expand...
Click to collapse
- as elocitya7 uses non-visible mmc partition for boot/recovery and only loong road solution with apx mode will enable it, i did not bother trying the new recovery..
- i suspect them to start using signed updates like folio100, and that means locked devices( for users without apx).
on the gapps-mdpi install,
i tried this on several models, and it always fail signature check for framework pack and network location provider at install.
the mdpi is made for cm7 with test-keys and somehow that seems to go wrong, maybe the framework failure is ignored and not crashing anything, but i do know they had some issues on gtab with it crashing like i just wrote, but it worked.
next, you got the stupid MAC address issue, which is fixed in the build of the framework..
i just used the gapps being present, fuctioning and allowing me to install some 30 apps and not breaking after reboot confirmation that they worked. hadnt checked logs, just eyeballed permissions were as they should be. root,root,644. market, mail and contacts worked offhand, start but couldnt complete google voice setup during the wizard where its suppose to change the tablets voicemail settings, but since those settings arent present in a tablet w out internal telephoney services i wasnt too concerned.
generally dont require resigning of apks in my dailey themeing/modding. read the general assumption is youre suppose to, but when thats required the system usually crashes and shows in logcat. i've only had the a7 work in adb mode while it was bricked/not booting to interface. havent been able to see the tablet under adb devices since, but hadnt tried before. was surprised the shell was full color w working ls -aFl options working, instead of just ls -l.
Sent from my X10i using Tapatalk
probably not relevant to point out that all testing was done over a wifi connection at home to a new 2wire wifi router on an att dsl connection. since you mentioned network connectivity.
the google account used is the same one used for another att android device. was interesting to see the tablet thru the android market on the web listed as a tmobile a7-040 device or something to that effect.
Sent from my X10i using Tapatalk
i might further update that sms text messaging services do work great on the tablet using google services w google voice even tho the setup wizard for google voice does not let you complete w/out the device having its own phone number.
i was able to text the misses and vice versa w no probs, even on fresh boot of the device. text messaging appears to work w internal text messaging activity in the contacts app, which you can text to a contact in the contacts menu.
tip; i created shortcuts on the home screen to text message using anycut to create a direct text message shortcut for the misses to conveniently text message me or her friend to our phones w ease, for free.
note; i could not use a third party text messaging app like handcent, and could not locate a messaging shortcut for message history.
Sent from my X10i using Tapatalk
Just so I can understand clearly.
What benefit does this provide over elocitymod?
How reliable is microsd/USB mounting/unmounting?
netstat_EVO; the current firmware from the manufacture is reasonably stable. in every experience, the manufactures software generally tends to demonstrate more stability than any rom developers, as they're providing your drivers and software written specifically for your hardware peripherals, instead of generic ones, or modified generic ones fixed to work the best they can for your devices.
my wife has experienced no usb/sdcard issues w/ the manufactures current firmware, and the biggest benefit experience from a third party rom (market/gapps addons) is still available to take advantage of the android market, as thats one of the main reasons folks see to using an android device. i can also say that she uses her tablet daily now (i'll have to post screenshots), and she hasn't had any wifi issues either. wifi resumes w/in 5 seconds from waking on newest firmware. some1 else didn't fix that(some folks reported problems in the past), it was already fixed, at least for my wifes device.
folks may have other opinions, but the primary reason i see for folks modifying roms on android devices (at least 3g ones tied to service providers) is that the service providers your buy your products from molest the firmware and load it up with unwanted software and restrictions.
this reason does not apply to the a7 tablet. the best route, for someone that doesn't want to read forums everyday and apply updates and patches every week would be to stick with the manufactures dependable firmware as a base, and run simple modifications and addons to that base.
..i still haven't had the time to disect the 3rd party rom the way i want to understand how much is based on manufacture software. i may do that this weekend and map out instructions for creating said rom based on binary comparisons to the manufactures rom, just for funziez. (its inevitable if it comes my way, i'm extracting and decompiling and mapping it out, because i have to know what changed. i do this to every rom i download.)
Nice, your wife is justification for just making gapps work
i like your reasoning here...
ayup. the misses made the effort after i got her the tablet to load her own rom, since she seen me doing the same for our other devices and noticed they tended to improve the quality of the devices we're running. i tend to have a preference for picking roms based on their stability, which generally tends to be roms based on the manufactures firmware, w the manufacture's drivers. sure, if it was a 2.1 rom, there'd be room for improvements in performance w/ froyo modifications.
catch is, its already a fast device w/ froyo on it plus a disappointing lack of a regular android market interface.
now, for someone who's happy with their tablet out of the box, and already enjoy using the android market, and all the apps they have to offer on their other android devices, this lacking feature is a serious let down for any android owner.
now, to add this feature, she discovers theres 3rd party roms that can do this, but as we know, they come without warranties. so the users get a support thread where they get to wait on a busy dev for their assistance w/ troubleshooting the various ins and outs of their rom or wade thru hundreds of support messages to fix their problem. whatta frustrating solution.
so, yes, i think my misses deserves to be able to enjoy her android device, and not have to be what i call a "romhead"; someone that has to flash a rom every other day in an effort to gain improvements and fixes over the last rom they just flashed.
i think that kinda stuffs great when theres a variety of roms and mods for your device to choose from, to see the various gains and differences in peoples software offers. i think its kinda sad when you just have to do it because you have no other options.
i've been getting some positive feedback, both in threads, pm's, and emails thanking me for providing those options. those are the other justifications for releasing a standalone gapps package. all relatable folks that appreciated another option, some thanking me for not having to run any more patches or fixes to keep their device going the way they'd like to enjoy it.
--
i might note, i hope you don't mind that i borrowed the gapps from your rom. i know all gapps get 'borrowed' from somewhere else.
thanks htc and google!
--
ps- thanks again mister dexter for your work. i appreciate any mods, roms, themes or apps folks can release that i can learn from. as i've stated, i reverse engineer everything i download thats posted freely online. if i make use of anything you've done for the device, i'm always happy to let folks know.
XDA is for sharing, i dont mind at all!
i wish i had personal reasons for this tablet, i just have the wishes of users, but its ok for me
On folio100 it was original a personal interest to make it better, and indeed it got better..
for those wanting a little more than gapps, the market is always open for graphics mod, hardware fixes etc..
Nvidia tegra2 platform is not as you say not worth fixing.. we lack proper rotation support although some new games are trying to read sensors correct now..
we need proper sdcard handling.. we need latest drivers from nvidia. and lastly all our early tablets lack better audio..
lastly: Android 3.0 is needed..
i think there's alot of room for improvement on top of stock firmwares. but not all users know its fixable or even need it if they are new to the platform..
Dexter; haha, I thought so. Seems most the popular rom devs are usually developing for devices they dont own themselves. pretty commendable.
Sent from my X10i using Tapatalk
Regardless of the whos or whys...a BIG thanks to both of you for all your dedication and effort.
ditto...
Regards
FURTHER UPDATE: tried the mahimahi fingerprint, w/ the gapps from dex's rom provided in my first release + marketaccess, this does not work for full market access. i do have a gapps package w/ same fixes that will work. i'll try to get this out by tomorrow. i got yard work to do first today.
correction; this solution tests GREAT w my gappsv2 update. i'll update this later today. this does NOT work with my first upload/gapps provided in dexters rom. it may also be a combination of the build prop update WITH this app that gave me full access on my tablet.
theres an update in the original post w/ the link to the author's website of marketaccess.apk for access to the rest of the applications in the market.
okay, bumped for market patch. this update includes calender and text messaging applications. see first post.
Can the april firmware be flashed over elocitymod and then this patch applied? Im dying to get full market access!!
Edit: Just read your post on modmymobile and all my questions were answered!
for those more technical types; you can extract the vending.apk file from this update and install the market individually. suggested troubleshooting instructions to do this; dont ask for more details or expect positive results without a wipe, but its possible;
1
goto settings, applications, running services and stop all google framework services including the genie.
2
delete /data/data/com.android.vending*
3
replace old vending.apk w new vending.apk
4
reboot
those suggestions come w no guarantees or expectations beyond bricks and bootloops. if you need more details, then you dont need this on dexters rom until someone provides you a flash update to automate cleanup instructions before market update.
Sent from my X10i using Tapatalk
Hey all so I flashed from stock to LiquidSmooth recently and am just wondering if there are any apps left over that I can remove using TIBU? I see a huuuuuuuuuuge list of apps with a gray name and line through them, should I just leave those there?
I already read this thread on apps to remove but that's for a stock GS3 and the apps on that list are the same as I mentioned above with the gray line/name.
I'm sorry in advanced if this is a pointless question or if I was just too lazy and missed a thread that answers this question(I tried to look!)
EDIT: One more question, for some reason I can't receive MMS, everytime I get one sent to me it tells me "message could not be downloaded", anyone have an idea?
sevenpioverthree said:
Hey all so I flashed from stock to LiquidSmooth recently and am just wondering if there are any apps left over that I can remove using TIBU? I see a huuuuuuuuuuge list of apps with a gray name and line through them, should I just leave those there?
I already read this thread on apps to remove but that's for a stock GS3 and the apps on that list are the same as I mentioned above with the gray line/name.
I'm sorry in advanced if this is a pointless question or if I was just too lazy and missed a thread that answers this question(I tried to look!)
EDIT: One more question, for some reason I can't receive MMS, everytime I get one sent to me it tells me "message could not be downloaded", anyone have an idea?
Click to expand...
Click to collapse
there are some apps that u can remve if not needed
butdo not remve files u dnt knoe what it is like bluetioth...it will give u a force close evrytme
for 2nd question ask ur service provider to send u the necessary settings related to mms
sevenpioverthree said:
Hey all so I flashed from stock to LiquidSmooth recently and am just wondering if there are any apps left over that I can remove using TIBU? I see a huuuuuuuuuuge list of apps with a gray name and line through them, should I just leave those there?
I already read this thread on apps to remove but that's for a stock GS3 and the apps on that list are the same as I mentioned above with the gray line/name.
I'm sorry in advanced if this is a pointless question or if I was just too lazy and missed a thread that answers this question(I tried to look!)
EDIT: One more question, for some reason I can't receive MMS, everytime I get one sent to me it tells me "message could not be downloaded", anyone have an idea?
Click to expand...
Click to collapse
Titanium Backup holds all your backups in it's database (that's kind of the point). Below is a summary of the various types of backups:
RED TEXT: These are system apps currently installed. These are items that you probably don't want to backup/restore across various ROMs, as they will most-likely have inconsistent formats and might cause issues.
GREEN/YELLOW TEXT: These are Titanium-Backup controlled system settings. You most-likely will be ok backing-up/restoring most of these across ROMs. I honestly don't know the difference between green and yellow, but be careful when restoring a 4.1.x settings to a 4.2.x ROM.
WHITE TEXT: These are non-system apps that are currently installed. For the most part, you shouldn't have any problem restoring these backups to a new ROM.
CROSSED-OUT APPS: These are apps that you had installed and backup up on a previous ROM, but now do not have installed. This is what you're seeing and asking about freezing.
As a summary of the above: The gray crossed-out apps are not currently installed in Liquidsmooth. You don't have to freeze them, because they're not there. In fact, you probably shouldn't restore most of them, because Liquidsmooth is not running Touchwiz and any Samsung apps that you've backed-up will not work on the AOSP framework.
Now, in terms of MMS sending/receiving. This is a known bug in 4.2.2 ROMs, but a solution has worked for some (myself included). The method includes re-installing the APN file in your phone. In my thread (so many replies!), I share my fix of it, as well as two other APN files that people have had success with. The original fix is found in this thread (I linked it in my post). Just follow those instructions and it should (hopefully) work with your mms woes.
Hope this helps!
topherk said:
Now, in terms of MMS sending/receiving. This is a known bug in 4.2.2 ROMs, but a solution has worked for some (myself included). The method includes re-installing the APN file in your phone. In my thread (so many replies!), I share my fix of it, as well as two other APN files that people have had success with. The original fix is found in this thread (I linked it in my post). Just follow those instructions and it should (hopefully) work with your mms woes.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the TIBU info it helped a lot
As for your mms fix, I had already given the other methods a go and just now tried yours but to no avail, nothing is working for me. Just now I tried the Go SMS fix and it works(hardly a fix in my opinion) but I don't want to use go sms so this continues to frustrate me
EDIT: I'd like to add I also tried to use mms.apk from blackbean7 but that didn't work either. Could it be on sprints end? I'm scared to call since I'm not on stock. I guess there's no use in talking about it here
EDIT 2: I switched my mobile networks to cdma/evdo from LTE/cdma/evdo and my mms started to send..I hate technology sometimes