yashsingh1/xdaforums huggingface dataset:
[A7 Android Development] rfisher1968:
Well i tried modifying init.rc, but after rebooting it always looked like init.rc was never changed/edited. I just thought it wasn't possible, but if it is i would surely like to know how to edit init.rc and keep it changed even after rebooting.

Right now all that i'm doing is done in install-recovery.sh which happens towards the end of init.rc, way to late.
[A7 Android Development] Dexter_nlb:
i agree, its probably far too late, when services are already started..

the init.rc is part of the boot.img you need to make a new boot.img with mkbootimg read more on this wiki here

this is the command to create the new boot.img

mkbootimg --kernel boot.img-kernel --ramdisk newramdisk.cpio.gz -o boot.img.out --cmdline '' --base 0x10000000
[A7 Android Development] Bjake:
Dexter, first and foremost, thank you for all of your work on this rom. You have made it incredibly easy for elocity owners to get the most out of what i now think is the best 7 inch tab on the market. Only have one issue...since installing the ad hoc patch for the folio, which works perfectly, wifi no longer automatically reconnects when waking up the A7. Any thoughts on how to remedy this issue?
[A7 Android Development] slowtoappworld:
Dexter - I got anxious so I tried to install the 1.0c received an error. Then I thought maybe I need to install the 1.0 so I tried to apply the 1.0 file but again it failed. Actually, the opening screen in the recovery notes: E:recovery.c Can't open /cache/recovery/command

Formatting MISC:.....

When I try to wipe all data - Yes--delete all user data then it says Prepare to delete user data, Please reboot via menu to complete (actually I haven't executed this part) but when i try to apply the sdcard:update.zip (lower case "u") I see.

Install from sdcard...

Finding update package...

E:can't mount SDCARD /dev/block/mmcblk1p1

(no such file or directory)

E:Can't mount SDCARD:update.zip

Installation aborted.

Formatting MISC:...

*************************8

Formatting MISC:....

I'm preparing to install your v1.0c but need to clarify a couple of things.

1. I downloaded 1.0c to a SD card using PC.

Now how do I get to the recovery menu?

Do I hit the factory reset button while in the recovery menu before download?

Once i download your file to the A7 - do i hit the factory reset button again - if yes, at what point do I do this? I'm thinking that if I do this then I will lose your 1.0c.

How do I boot to the recovery menu?

What is Quadrant?

What will ad hoc wifi do for me? Is it good to have?

Will I see screen shots as defined below by one of your followers. I'm excited to do this but also nervous - was thinking of sending the A7 back but if this works i will definately keep it.

After I do this then all is completed? Also, I did the dec 24 update as requested by elocity. Thanks for all of your assistance.

Ok.. here are the steps Im taking (I've verified the zip opens fine on my pc and looks good)

1) Boot into recovery

2) do a wipe data/factory reset

3) apply sdcard:update.zip (having renamed 1.0b to Update.zip - capital U)

4) after the yellow message "Reboot via menu to complete installation And power on again. Formatting MISC:..., I select "reboot system now" from menu..

5) I get the "Writing images to be updated" menu, and then the update screen with the rotating "/"

6) After a minute, I get the "Updated the device. Reboot the device.. Reboot now!"

7) After reboot, went back to recovery menu.. wiped data/factory reset again (per your suggestion)..

8) Reboot system now..
[A7 Android Development] slowtoappworld:
Desperus- I'm the noob you are referring to. I can't upload the file. What file do I initially try to upload. Any help would be appreciated.
[A7 Android Development] bazbob:
Not that it's been a priority with me, but now that I'm running fairly well on 1.0c ROM I too see that the Calendar app crashes with a force close message when launched.

Is there another set of calander apk's that work with the elocity A7?
[A7 Android Development] RojasTKD:
FYI: I've been using "Calander Pad" as my calander. It syscs with the Google calander on my A7 even though I can't open Google calander.

might be a useful work around.
[A7 Android Development] Desperus:
I will repost the set of instructions, including the link to the file you need to sideload..

1)You need to get Dexter's ElocityMod v1.0c from here.

2)Once you have downloaded this file to your computer, rename it from /DOWNLOAD LOCATION/ElocityModv10c.zip to Update.zip

3)Copy the newly renamed Update.zip it to the root of your external SD card, then insert sd card into A7.

4) Boot into recovery (Power off the A7, power it back on.. after a second or so after the light turns green, hold down the power button again, you will see a message about going into recovery boot.. when the golden ANDROID letters come up, let go of the power button.. when the install image with the arrow and the Android shows up, press the home button.. this will take you into recovery menu).

5) do a wipe data/factory reset

6) apply sdcard:update.zip (We renamed 1.0c to Update.zip on step 2, but this is fine)

7) after the yellow message "Reboot via menu to complete installation And power on again. Formatting MISC:..., I select "reboot system now" from menu..

8) I get the "Writing images to be updated" menu, and then the update screen with the rotating "/"

9) After a minute, I get the "Updated the device. Reboot the device.. Reboot now!"

10) After reboot, went back to recovery menu.. wiped data/factory reset again (per Dexter's suggestion)..

11) Reboot system now..

System loads into initial android setup screen... and Dexter's 1.0c mod is installed!

I hope this is useful to you.. good luck!
[A7 Android Development] jimmcghee:
1.0c Patch?

Thanks.

Do we need to then do the same thing to load the ElocityMod v1.0b - 1.0c(200KB patch) patch?
[A7 Android Development] jimmcghee:
Is there a way to tell which version we have installed?

Mine shows the Build Number as 'ElocityA7 Dexter Mod'.

Is this 1.0?

Thanks
[A7 Android Development] durango99:
lol masterfred...you just gave me a good laugh today... thanks ;)
[A7 Android Development] ecpirates:
Can't boot recovery on A7 after 1.41

eLocity A7, w/ Dexter's mod 1.41.

With Update.zip the only item on a 2GB microSD, cannot boot into recovery.

Device boots fine with 1.41, but external keyboard does not work, FC for display, etc. - the reported issues with 1.41. Cannot apply the ad hoc patch or the updated mod.

I'm not a coder, but I work a lot with firmware and OS upgrades for many devices. I'm not opposed/afraid to get my hands a bit dirty to resolve this issue.

Suggestions?
[A7 Android Development] bestialbub:
factory reset in recovery should give your tablet a fresh start w dexters rom present.
[A7 Android Development] ecpirates:
Thanks Beast, but Im not able to get to that menu. On recovery boot, I get the open box and 'droid logo, and there the tablet hangs . . .
[A7 Android Development] Dexter_nlb:
remember to press "HOME" key to make menu visible :-)
[A7 Android Development] masterfred:
I need honeycomb on this so I can sell it for an extra 50$ ! :)
[A7 Android Development] JLPDA:
1.42 Patch

Just got my A7 and am ready for Dexter's 1.41 Mod + 1.42 Patch. Have read every post in this thread, just want to be clear that the 1.42 patch get's installed the same way as a "mod" using "Recovery Menu" and doing a "wipe/factory reset".

Have installed many custom ROMs on my Windows Mobile phone (HTC Touch) and not sure how a "patch" would update if doing a "wipe/factory reset". Just don't want to "f" it up and brick it.
[A7 Android Development] JLPDA:
20 minutes of animated Hexagons after updating to 1.41 and reboot...now what? :eek:

NEVERMIND!!!
[A7 Android Development] droidflix:
The only reason for the wipe was that we had been using 1.41 for awhile and

the wipe was just to get it back to a clean state,but if you install 141 and then 142 patch right behind it you should be fine.

After you install the new mod (Rom) that is what the A7 reverts back to when you do

a wipe.So you should be ok, if you have any problems just follow the instructions

Dexter put at the front of the post and you will be fine.
[A7 Android Development] hextor_dark:
Press and hold botton power por 15 - 20 seg.
[A7 Android Development] Marbieskarb:
Hello Dexter.

I was wondering in your next mod could you add the back, menu, and home soft buttons in the top status bar?

I use button savior but that can still be a task sometimes. I recently played around with the CM7 mod on one of my other tablets and the soft buttons in the status bar was really convenient.
[A7 Android Development] Dexter_nlb:
never been in the status bar, and not part of a stock android, so sorry, thats a no go.. you need a advent vega for that function.
[A7 Android Development] Hogarth:
Dextor 1st thank you for all your work so far. I have a question for you. On the honeycomb rom when i put it on (very nice) it allowed my a7 screen to rotate 360, so i was woundering if that feature could be added to this rom in a future update. Thank you again for your work.
[A7 Android Development] JLPDA:
Bluetooth won't turn on w/1.41

Have been running 1.41 ROM with great success, so didn't update to 1.42.

Looking to try VCOrganizer... vecal.biz/vcoIndex.htm. Sync Software for MS Outook (doesn't require MS Exchange and syncs notes). However, when starting Sync Center, it defaults to Bluetooth and won't turn on the A7 Bluetooth. Looking to use WiFi sync but the Sync Center won't allow me to choose...wants to turn on Bluetooth. Tried to turn on in Settings and same thing. I thought the Bluetooth problem from 1.31 was fixed.

Any suggestions?
[A7 Android Development] Dexter_nlb:
bluetooth was fix early on, and the reason was found..

if you have new issue getting apps to enable your bluetooth, and it originally worked when you installed the rom.. i would look into if any information was changed with some apps that maybe modify something..

i have not seen problems with bluetooth my self, but i admin i have not used or enabled it daily, but just to test some gps and so on..
[A7 Android Development] JLPDA:
I can't say this is a new issue as this is the first time I've had a need to try anything bluetooth on the A7, either before flashing or after 1.41. I'll check to see if any other apps are an issue with BT. Thanx and keep up the great work.
[A7 Android Development] JLPDA:
adhoc fix - obtaining ip address

Trying to connect to my HTC Touch Pro while running Wifi Router . Works fine with my laptops. Performed the adhoc fix update (w/Dexter 1.41) so the A7 could see and connect but it just hangs on "obtaining ip address".

Any ideas on how to get this to work?
[A7 Android Development] jtodaro:
While this doesn't entirely add value to resolving your problem, I have seen this same issue with multiple commercial WIFI routers and my A7 + 1.42. Once I updated the WIFI routers firmware to the lastest, it resolved the issue. So, I'm not entirely sure the issue is on the A7 + 1.42 side of things (oddly enough, I have also experienced other phones issues connecting to these same WIFI routers until the firmware was upgraded).
[A7 Android Development] Marbieskarb:
The fix for the A7 seems to have troubles connecting to encrypted adhoc networks. I have a touch pro 2 and use an older version of wifi router that doesn't make you encrypt the connection on the phone and I have no issues connecting.

I also posted earlier in this forum a pretty nifty software to overcome the wifi reconnect issue after the tablet wakes from sleep.
[A7 Android Development] michaelviner:
setting up wmwifirouter (unencrypted version)

Had you used xda wifisharing application at all before using the unencrypted version of wmwifirouter ? I installed the free version of wmwifirouter and couldnt see it listed as a network to connect to. (A7 does see the XDA wifisharing adhoc) Im wondering if the xda wifisharing app. somehow changed settings that the wmwifirouter can't overcome. Really want to connect my A7 to my touch pro 2. Didnt work for me to just uninstall XDA wifi sharing on the phone.
[A7 Android Development] Marbieskarb:
Yes, I've used the xda wifisharing application but the A7 doesn't connect to it because of the encryption. I can post the version of wmwifirouter that I'm using on my TP2 but as a caveat, it doesn't allow you to uninstall it.
[A7 Android Development] michaelviner:
great !!

I would love to get the wmwifirouter version you have working for my equipment. I have realized what you said about XDA application. I see it as an adhoc on my A7 but wont connect to encrypted network. I have had many problems with friends encrypted LANs as well. Wish it could be fixed on Android side. Please give me any additional changes I need for Touch Pro 2 or A7 i.e. changing settings that were changed during XDA wifi installation. I am excited that you may be able to help me get my A7 connected through my TP2. Also I dont care if I cant uninstall it as long as it will work for my A7 and my windows laptop. Thanks so much.
[A7 Android Development] JLPDA:
XDA WiFi Router vs. WMWifiRouter

I may switch from XDA/HTC WiFi Router to WMWifiRouter, and pay for WMWifi.

http://wmpoweruser.com/new-htc-wifi-router-software-makes-wmwifirouter-obsolete/
[A7 Android Development] Marbieskarb:
Here you go...http://db.tt/gPGcLWE
[A7 Android Development] michaelviner:
getting closer

Thanks,

I installed it and it works for my laptop. When I try to connect with A7, I get an error message "Android does not support connecting to Adhoc (IBSS) type networks" Do I need a particular adhocfix file ? almost there. thanks.
[A7 Android Development] michaelviner:
Thanks so much Marbieskarb

Hey I answered my own question and found the adhoc fix on the front page. I am so glad to be able to connect now with my windows mobile phone. I owe all of you including dexter a great deal of gratitude. Anywhere I can contribute $, let me know.
[A7 Android Development] netstat_EVO:
Dexter has a "Donate" button right under his name...
[A7 Android Development] ifitwasnt4u:
Nooooooo Dexter. Please continue to support! Will you be on any other site?????
[A7 Android Development] JLPDA:
Dexter Gone?!

What a shame to see Dexter go...at least from here and the A7. The ONLY reason why I eventually decided to purchase the A7 was because I could get Google Market on the device. Your knowledge and great work is appreciated.
[A7 Android Development] ytain:
Don't worry about Dexter leaving, it's his choice.

I will eventually make time to build a gingerbread build for eLocity A7, but the present conditions don't allow me to use my laptop for kernel building (too much heat in the room that makes the laptop turn off early), so better be patient till after my move elsewhere where the conditions are better (in two/three month's time). That's the reason I wanted to have gingerbread on this tablet. And to share the gingerbread kernel to the community and for any rom modder.

Ytain
[A7 Android Development] TheZedo:
Well the next big thing for us A7 users will be the release of Gingerbread.

http://www.elocitynow.com/support_faqs.shtml#System

Quote:

Q: Will Android 2.3 Gingerbread be supported on the Tablet?

A: We anticipate that the Tegra 2 processor should have the ability to support the future Android release, but we cannot confirm it until Gingerbread has been officially released.

I sent an email to support asking for an approximate timeframe, and called to asked a rep to escalate to the dev team so they can update the webpage, since Gingerbread is already being released on other tablets. No reply yet.

Some folks are pointing out that Gingerbread may not be a great deal for everyone, in fact saying some prefer froyo instead. :confused: See here:

http://www.knowyourmobile.in/news/983498/gingerbread_vs_honeycomb_not_a_culinary_debate.html

So it sounds like a lot will depend on your own personal preferences, as well as how much, if any, Elocity spruces Gingerbread up for us.

On a similar note, a potential product to keep your eye on is here:

http://www.onskreen.com/cornerstone/

Combining a nice multitasking interface, with the prowess of gingerbread, might turn out to be one sweet ticket :D ...time will tell.
[A7 Android Development] tumpy:
Elocity people have no clue about their own product. I would takeup ytain on his offer in the mean time froyo will do because honeycomb lockup to much. As for the poster above me none of you link mean anything just people opinion..
[A7 Android Development] ifitwasnt4u:
Did you clear your cache before flashing from honeycomb to 1.41? Might want to start there, clear your cache(s) 3 or 4 times, they re-flash 1.41 fresh.
[A7 Android Development] ironhead65:
Thanks for the suggestion...I'll say no...since I am not sure what that is.

Is that something done in the boot menu, where you choose to actually "load" the update.zip file?

--Ironhead
[A7 Android Development] ifitwasnt4u:
When you are in the recovery menu before flashing. There is a clear cache selection. Select that 3 times then flash 1.41 again.
[A7 Android Development] ironhead65:
ok, after re-installing, I know what you are talking about...yes I did do that.

After messing around for a bit, I called Elocity...apparently this is an issue that CAN happen. They said some time today or tomorrow someone from "advanced" technical help will call me back to try to see if we can figure out what is going on.

If not, they said they can swap me for a refurb (at my cost of course).

Thanks for the help!

--Ironhead
[A7 Android Development] drassray:
A7+

does anyone know if this is compatible with the A7+?
[A7 Android Development] DroidxRage:
1.0c is the final build. The patch was if you installed 1.0b, and needed to patch that version to be the same as 1.0c

1.0c = 1.0b + 1.0c patch
[A7 Android Development] DroidxRage:
No, he didn't code it into Build.prop with the different minor versions
[A7 Android Development] rfisher1968:
Dexter,

Is the output from cpio like the following normal?

cpio: default.prop: function not implemented

cpio: init: function not implemented

cpio: init.goldfish.rc: function not implemented

cpio: init.rc: function not implemented

cpio: init_recovery.rc.prop: function not implemented

cpio: sbin/adbd: function not implemented

I'm using GNUWIN32 exe for windows gunzip and cpio versions

Also if i extract the ramdisk and not change anything and re-create the ramdisk should it be the same size of the original? I started with a 162kb file and now have a 163kb file without changing anything.

I also made a windows mkbootimg.exe, but have not tried it yet.
[A7 Android Development] durango99:
Please refer to the post I wrote here for working google calendar:

http://xdaforums.com/showpost.php?p=10105712&postcount=781

for (most) everything I collected prior to dex's 1.0c mod refer to:

http://xdaforums.com/showpost.php?p=10078653&postcount=682

Hope that helps,

dan
[A7 Android Development] bft305:
I just want to thank Dex for his mod v1.0c, it is awesome that he took the time to make is simple for a Noob like me! The one thing I can't see to get working though is my micro sd. I just bought a 16gb micro sdhc card. I hooked it up to my computer and downloaded a bunch of pics to it. Then I inserted it into my tablet and I can't seem to find any of the data on it. The A7 does recognize that the sd card is inserted but all I see it the option to eject it. Maybe it is something stupid I am not doing but anyone have any ideas?
[A7 Android Development] durango99:
Refer to the link list I posted here:

http://xdaforums.com/showpost.php?p=10078653&postcount=682

Check the link saying "might need to format microsd"
[A7 Android Development] babydumplinz:
Thanks Dexter

Hello Dexter how is the next update coming along for fixing the bluetooth issue and thanks for your help wish google would give you the honeycomb so you could start updating it for us.
[A7 Android Development] Dexter_nlb:
I have looked into ordering one from Ebay, so i might get one which makes patching/testing much easier...

can you refresh, what was the BT issue?
[A7 Android Development] sagggas:
Hey Durango,

I've got the same problem that bft305 has. I just installed a brand new 16gb class10 card into my A7, but the system only sees 2gb of it.

The only thing I did to the card prior to sticking it into the A7 was drop dexter's 1.0c mod (named Update.zip). While it was in my Windows 7 machine, Explorer showed 16gb. I then turned off the A7, inserted the SD card, booted into recovery, wiped everything, and flashed Update.zip.

The update went great (no boot loop), wiped the cache again, rebooted. Various utilities including a clock widget, system settings, and titanium all show that the card has < 2gb on it. Those same utilities also show that the total system ram is only 1.6gb and available ram is 1.5gb. Any idea why this is happening? I posted another comment about the system ram in the general comments section... I formatted the SD card via the settings menu as indicated in your link post, but nothing changed.

I don't have a USB A to A cable, so I can't plug the A7 directly into my PC yet to see if Windows still sees all 16gb.

Additional info that might be helpful:

I used titanium to move Angry Birds to the SD, however, when I check the same titanium menu, it the button to move it to SD is still available, and the button to move it back to device is greyed out. Apps2sd reports it as being on the sd, but the options to move it back don't exist (I guess it links to settings>> ... >>manage applications which doesn't have the option available).

Using ROM manager, I looked into installing clockword recovery which (according to what I've been reading) allows the system to repartion the SD (add ext partition [up to 512mb] and cache partition [up to 256mb]). Clockword identified the tablet as an Advent Vega (whatever that is). I figured what the hell, I can just wipe it again if it fails, and I installed. Nothing happened, and a reboot to recovery didn't indicate a recovery image was there.

Anyway, I just want all the memory to be where it should be. I'm not too concernced about installing items to the SD yet, but the system still needs to identify and report the correct memory values.

Thanks in advance for your help!
[A7 Android Development] hoagm:
I'm just guessing here, but my bet is that most apps are looking at /sdcard (the Android "standard") when evaluating storage space available on the uSD card. As we're painfully aware, eLocity jacked up the mount points with the 12/24 update and /sdcard is not your removable uSD card at all.
[A7 Android Development] rfisher1968:
Just remove the sd card and turn it on. The contents of /sdcard are still there, its mounted to the internal memory. The sd card is mounted to /sdcard/sdcard-disk0

I would love to try and fix this problem but i was waiting for some of my questions to be answered, because i was trying to work just in windows enviroment, but not having much luck.

Using rootexplorer you can view the files init.rc and init_recovery.rc, init_recovery.rc mounts the sdcard correctly and init.rc doesn't. I would like to edit the init.rc but its in the boot.img file and can not edited. What can be done is extract the ramdisk from the boot.img and inserting a edited version back that fixes the problem. My problem is what enviroment to do this in, windows or linux? Do i need to install the SDK?
[A7 Android Development] Dexter_nlb:
im trying to fix your storage problem, and i just noticed there is no mounting of external sdcard, don't elocitya7 have sdcard slot?

according to the system, its not mounting it when found?

secondly,

im removing Fring and Flash to free some space in /system, and ill make "flash" available for as a reguar app, so i have space for changes..