Related
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up. Thank you to Dexter and everyone else who posted such informative and useful instructions on the A7 forum. I am perplexed as to why I was not successful in accomplishing the update and modification. I really do like the A7 and hate to return it, but whats the sense of owning a Android device if you can't utilize the Marketplace. Duh! I would even be willing to pay a nominal fee to a honest, tech-savvy individual to modify/update my A7 for me. Thanks again everyone, looks like I'll be shopping for a tablet thats a little more user-friendly.
Just my 2 cents... There is not eLocity (Stream TV Network) problem
Google denied Market at some tablets. G considered that their OS version 2.X is not compatible with tablets.
These tablets do not have Market "out-of-box":
Viewsonic G Tablet
Malata ZPad
Advent Vega
Archos (all versions)
etc...
Idk why Galaxy Tab has market "out-of-box". May be Samsung proved Google that it's big phone)))
StarBriteK said:
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up
Click to expand...
Click to collapse
Try nameing the file Update. Do not add the.dot zip, holding down the power button until the third line of text is seen then release will get you into program mode.. selling a tegra tablet to get anything other than another tegra is like going backwards...
StarBriteK said:
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up. Thank you to Dexter and everyone else who posted such informative and useful instructions on the A7 forum. I am perplexed as to why I was not successful in accomplishing the update and modification. I really do like the A7 and hate to return it, but whats the sense of owning a Android device if you can't utilize the Marketplace. Duh! I would even be willing to pay a nominal fee to a honest, tech-savvy individual to modify/update my A7 for me. Thanks again everyone, looks like I'll be shopping for a tablet thats a little more user-friendly.
Click to expand...
Click to collapse
Where are you located? I'm. Sure if there is a member here local to you, they'd be willing to help you out.
I'm enjoying my A7 but, I do have to give a certain amount of blame to Stream for the lack of user friendliness the device presents. There are all sorts of documentation out there for companies to reference when designing an Android device, giving them an outline of what will work. The choice to implement a code structure or hardware features that do not work or require a work-around is directly the fault of Stream, as testing should have revealed the issues.
Take a look at how long Dexter has been working on the mod many of us are using, the feedback people give after putting it through the "real world" challenge and then the subsequent updates from Dexter...if Stream did the testing and verifications on this product from concept to creation to now...someone needs to be fired or doesn't care. Without detracting from Dexter's efforts or anyone else contributing on this board but, if the customer base can put so many fixes in place:Why can't the OEM? Why are they so slow in comparison on responses? Why don't their updates fix the most common issues? How did they allow themselves to release a tablet without a proper OS and fail to do better funtionality testing?
I'm glad their are folks like Dexter out here and forums like XDA otherwise decent hardware like this would allow companies to seperate us from our dollars on inflated claims of fuctionality and force us to jump through hoops to get a remedy.
problem with A7
StarBriteK said:
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up. Thank you to Dexter and everyone else who posted such informative and useful instructions on the A7 forum. I am perplexed as to why I was not successful in accomplishing the update and modification. I really do like the A7 and hate to return it, but whats the sense of owning a Android device if you can't utilize the Marketplace. Duh! I would even be willing to pay a nominal fee to a honest, tech-savvy individual to modify/update my A7 for me. Thanks again everyone, looks like I'll be shopping for a tablet thats a little more user-friendly.
Click to expand...
Click to collapse
\
email me at [email protected] and I will do what I can to help.
A7 Towel
Here are some quick things to know/try that work for me -
1. SD card must be formatted as FAT format, FAT32 is fine
2. Mod file is named update.zip in sd card, do not put it in any folder in the SD card
3. When you are powered down, if you hold the power button in for about 15 seconds and then release and then hold in again for a few seconds you will see, hold in for another 5 seconds to go to boot menu, immediately hold in for another 5 seconds and then release, you should see a android character, tap on home icon on right and it should go into a boot menu
4. Use the buttons on the tablet (home, etc on the right) to page down and up the list of selections. Top 2 buttons on the right are up and down. Second to bottom icon is select.
5. Scroll to "apply sdcard:update.zip"
6. Select that option (second to bottom icon on right of screen)
it should now apply the update.zip on your sd card. It could take a while.
If there are any errors then the update.zip file may be corrupted. All updates are over 90MB in size except for the patch that Dexter sent recently which is around 3MB.
Let us know if this works.
Thanks for the responses
I have done several times the instructions some of you have responded back with and watched several posts on YouTube also. Yes my card is formatted to Fat32 and yes I used a capital U on Update.zip. I have followed the instructions to a "t" for installing DexMod and Elocity's own instructions on their website in regards to the 2/24/11 update. My A7 simply would not recognize and open the SD card file and would then abort the program. I'm simply at a point where how much more of my time do I want to spend spinning my wheels on the A7 tablet in order to have access to the Android Marketplace. Thanks again everyone.
Please see my response at bottom.
A7 issue
sorry to hear that. I suspect your update.zip file is probably not being recognized as a zip file. mine is named update.zip, no uppercase anything. Sometimes there can be a hidden extension of another .zip so the system sees it as update.zip.zip
I downloaded the mod and renamed mine on my pc and then copied it directly to the microsd card. Sorry to hear about the time its taken you so far. As I said earlier I would be happy to work with you if you wish.
just to clarify, you can't really install the latest feb 24 update from elocity AND dexters elocitymod rom. Unless, that is, you take the mods that dexter has done and apply them to the latest elocity update and regression test it, debug it, etc... elocity did a fair job of putting out a cheap android tablet. they made some sacrifices on the hardware side - no multitouch and no hi res screen, but for the price, it's hard to beat. and dexter's mod makes the a7 infinitely more useful. have you tried other microsd cards? you can get cheap 2gb and 4gb ones at target or bestbuy. if those don't work, you can just return them. lots of people have been using dexter's elocitymod successfully. without it, i probably would have returned the a7 also. if you're looking for something a bit more polished, get ready to spend a bit more. samsung galaxy tab goes for about $600-$800 motorola xoom about the same price as well.
Did you check your sd card for bad sectors or tried a different sd card? Just curious.
Same problem adding Dexter Mod
I've just got the A7 and I'm following the threads about the Dexter Mod. I'm a little confused about 1- what to name the file...some say with a capital U and some not...2- with or without .zip...again same thing 3- can you use the 1.2 Mod after Elocity's latest firware update...the reason I ask this is because the link for 1.3 is down and I do have 1.2 on my pc for some reason.
On my sdcard it doesn't have a directory "ROOT" do i just copy it to the open card. So may questions...sorry about that, been at it for 3 hours and no success. Have to laugh tho....
BTW I have a file named LOST.DIR on the sdcard
file name
The file when you download it is already in zip form. All you need to do is rename it to ( update ).
Dexter Mod 1.3
Thank you. Just installed on 1 of my A7's but the 1.3 Mod...Was able to download it this morning, the site is back up again.
Now to do the bluetooth fix...life is all go...lol
Ok, lets clear this up once and for all...
For everyone that is getting confused about update.zip, Update.zip, Update.zip.zip, and whatever other additional permutations of combinations that people have been able to come up with.
The answer: although some people have reported success with a lower case "u", the best way is to simply follow the directions layed out for you and name it "Update.zip"
Here's the simple truth of the matter, the file you download is <Dexter's_webspace>/ElocityModv13.zip ... or if you are going after eLocity's updates it would be
<elocity's_webspace>/update.zip
Notice that both files have ".zip" at the end. No question about it, no chance that this is not true, no chance that as I actually saw someone post on here "elocity never named it .zip".
Now, here's where people have the opportunity to get confused and do something wrong...
PC Users:
A default out of the box Windows installation is set to HIDE file extensions of known file types (zip files included). So, when you look at your download it will appear to be just "ElocityModv13" or just "Update" even though the file extension (.zip) is actually there. So when you try to rename it to "Update.zip" you are changing only the information BEFORE the file extension, thereby making it "Update.zip.zip"... This is no one else's fault. Please don't blame eLocity, please don't blame Dexter, please don't blame the Android OS itself.
The Solution!:
Open Windows Explorer, go to the "Tools" drop down menu, go to "Folder Options", click on the "View" tab on the window that just popped up, uncheck the "Hide extensions for known file types" checkbox, click "OK", profit.
MAC Users:
I am guessing that this applies to most of the "What do I do with all these folders from the zip file" type of posts. The most probable issue here is that Mac's have a rather annoying habit of unzipping zip files as soon as it finishes downloading them, leaving you with just a folder (in this case either named "ElocityModv13" or "update" with no file extension (its a folder).
Mac Solution:
To keep Safari from automatically unzipping your files, the fix is easy.
Open Safari, open Safari's preferences, Click on the "General" tab, uncheck the "open safe files" box, close preferences. Now download either the mod or the stock update again, and you'll have the actual zip file instead of just a folder with the contents of the original file.
Hopefully this helps a lot of people figure this out.
Now...
My Disclaimer:
I already am prepared for the inevitable "stop being rude", "somebody call me a wahmublance", "I'm new to this" type of response that I seem to get more often then not on here. So, before any of that happens let me explain my standpoint.
Anyone trying to go down this route and put a custom rom on their device is attempting to modify it. This SHOULD require at very least a working knowledge of the device or software you are trying to modify. I am not saying everyone here should be on Dexter's level, but at least a little computer know how would be very beneficial. Next, before just diving in to changing things on this little chunk of technology that you just spent a few hundred on, read. Simple as that, educate yourself on the toy you just bough. Creating many many duplicates of threads asking the same extremely basic questions does not help anyone. It clutters up the forums, makes the people that actually have the answers so sick of saying the same thing over and over that they just don't answer any more, makes it harder to navigate the actual different topics, and makes it harder for everyone else to find the answers they are looking for. There should be no "which one of the 15 bluetooth not working threads was that post in?"
I apologize for my complete lack of patience with people that can not search for information and need to be spoon fed. But 99% of the time the question has already been asked and answered. And lets be serious here, the A7 forum only has FOUR SECTIONS, really not a lot of reading. And in the other cases where it is a user error like not knowing how to rename a file or yesterday's hilarious "My SD card doesn't have a folder called ROOT", you really need to ask yourself if this is really something you are up to. If you lack the basic knowledge to perform the easy steps of the process, is it really worth it to risk creating a $300 paperweight to say "look at the cool thing I did" to your friends?
If something I said here seems like it was taken from your post/story, don't take it personal, it was only listed as an example.
I'm sorry I opened such a can of worms on this subject for some "TECHNOLOGICALLY-ADVANCED" individuals who seem to have nothing better to do but respond with condescending remarks on this forum. FYI: I recently purchased a new Samsung Galaxy tablet on eBay for $360.00, hence my A7 has been shipped back to the retailer for a refund. I still think the A7 is a great device, I simply do not have the time to repeatedly attempt to update it so I can have access to the Android Marketplace, nor the patience to tolerate the attitude of certain posters to this forum. I thought the purpose for this forum was to help each other out on issues, not to repeatedly "Beat Dead Horses" which some individuals tend to be doing. Thanks again everyone and GOOD LUCK!
StarBriteK said:
I'm sorry I opened such a can of worms on this subject for some "TECHNOLOGICALLY-ADVANCED" individuals who seem to have nothing better to do but respond with condescending remarks on this forum. FYI: I recently purchased a new Samsung Galaxy tablet on eBay for $360.00, hence my A7 has been shipped back to the retailer for a refund. I still think the A7 is a great device, I simply do not have the time to repeatedly attempt to update it so I can have access to the Android Marketplace, nor the patience to tolerate the attitude of certain posters to this forum. I thought the purpose for this forum was to help each other out on issues, not to repeatedly "Beat Dead Horses" which some individuals tend to be doing. Thanks again everyone and GOOD LUCK!
Click to expand...
Click to collapse
You didn't open a can of worms, it was just a coincidence that the misinforming post that sent the fingers of fury flying happened to be on your thread. and trust me, I have plenty of better things to do, this is just filler.
Seems like you got a hell of a good deal on the G Tab, Congrats.
And yes, the point of a forum is to help other people, which I do. By correcting bad advice, and trying to get people to ask for and give help in a more collaborative way instead of the same questions being asked over and over again. I'm sorry if you find my presence on the internet grating, just be glad that you haven't had to endure my vocabulary in person (apparently it is pretty similar to that of a drunken sailor with tourette's syndrome with the same measure of sarcasm that I treat the net to)
Back at you on the good luck. Expecting a review on the g tab, pro's and con's vs the A7 hopefully
LOL
LOL, you guys are just hilarious
Hi, thank you very much bestialbud , for your contribution now enjoy factory firmware and all functions work perfectly in A7. and also I have the Market.
thanks for the positive confirmation.
i'll try and throw out some more stuff for you the a7 users this weekend to accompany the gapps fix; some build prop improvements to get you access to more apps.
i'll try and throw out some more stuff for the rom chefs to kick up the activity in rom and mod development for the a7; map out all the files, permissions and uid/gid's, and then MAYBE if i have the time this weekend go experimental and package the factory rom into what i consider a normal update zip; zipped up rom instead of a system image w/ a script that sets all the roms permissions, symbolic links and busybox install. once its in a more manageable format like that you'll get more would be chef's and themer's contributing.
been thinkin' about it all week, i just don't have a tablet of my own (i'm the misses android fixit tech), so my works restricted to weekend mornings.
would be great, that within your improvements we have an ad-hoc connection to work properly.
the market does not have all the permissions, but wiht the permissions you indicate the fix the problem.
I'm anxious to see your improvements. Thanks again.
i'm sorry my english.
genialor; yeah, i never had any success w the adhoc wifi fixes myself. adhoc limitations are pretty common for mobile devices, not just android. i actually picked up a dsl connection due to this limitation, quite reluctantly i might add.
there is some 25 other similar tegra tablets. a portable solution could still present itself. i wouldnt count on any manufacturer adding adhoc connectity if they didnt provide it in the initial release.
i can say the usual passion finger, or release keys added to the stock one didnt make any difference. but im only using skyfire for an app name to search.
if folks could list other apps they dont see, it may help to make some gradual steps.
otherwise as far as savey folks looking at direct manipulation; the fingerprint that the market app reads after being copied from build prop is stored in /data/data/com.android.vending along w the characteristics your device supports. im a compare the tabs to my phone for fun to see if i can manipulate the data, because fingerprint replacement, w this gapps package in the rom isnt working. if that works, i can post instructions for the savvy, and MAYBE dig up some way to creatively automate adding those details.
Sent from my X10a using Tapatalk
Thanks buddy install UPDATE04-16 market + google apps and it works perfectly.
Bestialbud excellent job. Full Market yes, yes, yes ...
What is the latest market app, on Dexter mod I am running 2.3.6..
if folks could list other apps they dont see, it may help to make some gradual steps.
Click to expand...
Click to collapse
Hey, Tested your update and it seems to work fine except for some game apps. These aren't crucial but may indicate some permission issues: "crazy snowboards" seems to have a orientation problem.( only work in portrait mode.) "mau mau"intermittent FC.
*** note these apps worked in Dexter's latest mode ***
Otherwise Good Job!!
I find the installation notes for gapps mod in original thread extremely confusing.
I just installed official firmware (BTW the installation notes on official site were crystal clear). What should I do now?
A video of the entire process would be great.
P.S: NP, I just did not understand that to navigate between recovery menu items I must use "back" button.
Looks like gapps works now
sorry, i didnt provide step by step details for recovery use. i wont update that information either, as recovery is likely to change soon w lightly different instructions..
Sent from my X10i using Tapatalk
Some market applications can't see sdcard...
Looks like it is mounted as /storage/sdcard-disk0 while these apps expect it to be at /sdcard. Also /sdcard is mounted somewhere on internal memory, same place as /storage actually . Is there any way to change it?
Some market applications can't see sdcard...
Looks like it is mounted as /storage/sdcard-disk0 while these apps expect it to be at /sdcard. Also /sdcard is mounted somewhere on internal memory, same place as /storage actually . Is there any way to change it?
Ummm, there's so much information on this...please do a search in these threads on SD card and you will understand why no one wants to answer that question............
okantomi said:
Some market applications can't see sdcard...
Ummm, there's so much information on this...please do a search in these threads on SD card and you will understand why no one wants to answer that question............
Click to expand...
Click to collapse
I did search and could not find any comprehensible information.
I didn't say it would be comprehensible.
The external sd card is mounted as /storage/sdcard-disk0. The A7 can read from it but not write apps to it, or at least the market doesn't and I don't think you can run apps from it, just install from it. There is an internal sd card 4GB total, but with 1+GB available for apps, and we can also add our own sd card (up to 32GB) stuffed with our music, videos, jpgs, documents, etc....that way we can access them through gallery and media players, etc, without having to download a bunch of junk onto our internal memory.
1GB is a huge amount of internal space for the kind of apps that I suspect most of us are using. Sorry if I'm not clear, but in truth this topic has been done to death.
Maybe our intrepid developers can find a way to rewrite the way this thing works now that they have the kernel source but maybe not.
there are ways and roms that may change the sdcard mount location. the apps may com thru the google market, but their ability to run is another function of the rom.
this is only a google apps addon.
you'll have to wait a lil bit longer til you see a rom from me. i'm interested in recovery and themeing for this device right now..
Sent from my X10i using Tapatalk
muxecoid said:
Some market applications can't see sdcard...
Looks like it is mounted as /storage/sdcard-disk0 while these apps expect it to be at /sdcard. Also /sdcard is mounted somewhere on internal memory, same place as /storage actually . Is there any way to change it?
Click to expand...
Click to collapse
This is an on going problem with the sd card and the way its mounted by elocity's implementation of Android 2.2. To male a long story short, Elocity's android version is 2.2 compatible not a true implementation of Android 2.2. As far as I know no one has been able to work around this problem. Dexter tried starting with mod 1.3 but people started having problems with sd and usb detection. I'm waiting for Stream Tv to finally decide to fix this problem.
rphilippe777 said:
This is an on going problem with the sd card and the way its mounted by elocity's implementation of Android 2.2. To male a long story short, Elocity's android version is 2.2 compatible not a true implementation of Android 2.2. As far as I know no one has been able to work around this problem. Dexter tried starting with mod 1.3 but people started having problems with sd and usb detection. I'm waiting for Stream Tv to finally decide to fix this problem.
Click to expand...
Click to collapse
Drugs are bad mm'kay
Why on earth do people feel the need to disseminate misinformation on here on such a regular basis.
Go back and re-read Dexter's posts on the subject. There is a reason, a real reason, not made up like "its not true android 2.2". This is not a phone, it has larger internal storage and thus relies less on the external media. To have it the way you people want it (like a monstrous phone) the external storage would end up being the default, making it difficult to use the internal storage, and also REQUIRING that you have a decent size microSD just to make the tablet usable.
BTW, I am still laughing that I am apparently using an Android knock off lolololol
netstat_EVO said:
Drugs are bad mm'kay
Why on earth do people feel the need to disseminate misinformation on here on such a regular basis.
Go back and re-read Dexter's posts on the subject. There is a reason, a real reason, not made up like "its not true android 2.2".
This is not a phone, it has larger internal storage and thus relies less on the external media. To have it the way you people want it (like a monstrous phone) the external storage would end up being the default, making it difficult to use the internal storage, and also REQUIRING that you have a decent size microSD just to make the tablet usable.
Click to expand...
Click to collapse
BTW, I am still laughing that I am apparently using an Android knock off lolololol
Click to expand...
Click to collapse
I don't understand your response. I read Dexter's post on the subject. You need to re-read it. OS's in general have standards. If I run a windows, linux or mac system to name a few, you expect your hardware and software to run a certain way. For example, when you to read, write or print a file, any software you run for that OS should allow you to this on any computer that you run that particular OS on the same way. This isn't rocket science for a typical consumer. If you want to prove to me that I don't know what I'm talking about or worse yet that I
"disseminate misinformation on here on such a regular basis
Click to expand...
Click to collapse
. , please show specifically where what I said concerning Android 2.2 is wrong other then that you may have read dexter's post.
This is not a phone, it has larger internal storage and thus relies less on the external media. To have it the way you people want it (like a monstrous phone) the external storage would end up being the default, making it difficult to use the internal storage, and also REQUIRING that you have a decent size microSD just to make the tablet usable.
Click to expand...
Click to collapse
. That's irrelevant. The standard is not about what you want but the way it was decided that the OS should work plus I believe this is or will be addressed in Android 3.0. This constitutes and opinion rather than a fact. I didn't spend $299 on your opinion which BTW I don't agree with.
I understand XDA is developers site and you guys are use to thinking outside the box, which is fine by me, but we aren't all here for the same reasons and when I purchase something and it says I'm getting a certain thing, as a consumer, I expect the minimum of what if I'm purchasing. The box days "Android 2.2" not "Android 2.2 compatible" or "Android 2.2 features" or "Android 2.2 clone."
The question is:
- What is "Android 2.2"
- How does this relate to software and hardware issues with the A7?
- Is there a work around?
- Is there a firmware update?
and If your replying to a post, do can you contribute anything helpeful because telling me to search all of Dexter's post because you think you say a post concerning this already without reference that to that post is a waste of everyone time.
rphilippe777 said:
I don't understand your response. I read Dexter's post on the subject. You need to re-read it. OS's in general have standards. If I run a windows, linux or mac system to name a few, you expect your hardware and software to run a certain way. For example, when you to read, write or print a file, any software you run for that OS should allow you to this on any computer that you run that particular OS on the same way. This isn't rocket science for a typical consumer. If you want to prove to me that I don't know what I'm talking about or worse yet that I . , please show specifically where what I said concerning Android 2.2 is wrong other then that you may have read dexter's post. . That's irrelevant. The standard is not about what you want but the way it was decided that the OS should work plus I believe this is or will be addressed in Android 3.0. This constitutes and opinion rather than a fact. I didn't spend $299 on your opinion which BTW I don't agree with.
I understand XDA is developers site and you guys are use to thinking outside the box, which is fine by me, but we aren't all here for the same reasons and when I purchase something and it says I'm getting a certain thing, as a consumer, I expect the minimum of what if I'm purchasing. The box days "Android 2.2" not "Android 2.2 compatible" or "Android 2.2 features" or "Android 2.2 clone."
The question is:
- What is "Android 2.2"
- How does this relate to software and hardware issues with the A7?
- Is there a work around?
- Is there a firmware update?
and If your replying to a post, do can you contribute anything helpeful because telling me to search all of Dexter's post because you think you say a post concerning this already without reference that to that post is a waste of everyone time.
Click to expand...
Click to collapse
----------------------------------------------
Dexter_nlb said:
this is all a misunderstanding of how tablets are supposed to work, and caused by the fact that android 2.2 is made for a phone with external memory cards, and less to nothing of internal memory.
the current installation where apps are "moved" to internal storage is actually how vendors are trying to implement 2 types of storage.
comparing this to a mobile with just sdcard, and android 2.2 only supporting one storage type, the preferred storage becomes the "internal" and sdcard handling as you notice is now pointing to a location with the internal storage location.
the mountpoint at the internal storage location is planned based on the fact that users coming from an android based mobile knows alot about where to find data, which is in the storage location, so its put as mount at the storage so its easy to access, and not actually any bug at all.
so until better handling is presented (hopefully 3.0) people will continue to think that the handling is wrong or something is not wright here, but it is correct.
your internal storage of "just" 1.5GB is the preferred location, as tablets are not meant to have sdcards as preferred storage, if you chose not to put a sdcard into the tablet. so the choice was easy, use internal storage for android so ppl didnt need to buy additional cards.
but the lack of storage internally is a vendor decision, not a bug or not "the android way" a problem in any way..
imagine, those users without any sdcard, being unable to use the feature of android to a storage, and needed to use data storage for all files, that would look strange, if you didnt have the option available..
it could have been planned differently but vendors (all of the tegra2 vendors) has chosen this path, which could have been done differently but its all relate to apps and how they expect your device to work..
a long explanation, but remember 2.2 is not made for tablets, it made for small devices with external memory cards, which is long overdue and is followed up with the new android 3.0 which hopefully solves your problem.
conclusion,
Nvidia could have chosen a different way of using android, but they're still rather new to the platform and their design is not without problems yet (honeycomb will show that too), so if they used real planning and organized memory and sdcard handling like 2.2 was made for, you would have no problems at all. Remember Nvidia designed it this way, and they are the reason you have problems..Lack of knowledge of design and functionality, like BMW trying to make graphics card for a pc, coming from designing cars, their work would not be in a class like nvidia graphics, but probably ok..but far from good..
Click to expand...
Click to collapse
There was no button to make the important text blink and slap you in the face at the same time, so I hope bold and red will suffice.
Don't get pissy with me because you are putting out misinformation and got called on it. There are people who come on here to learn and someone might have actually believed your BS about "Android 2.2 compatible" or "Android 2.2 features" or "Android 2.2 clone."
I have contributed. You on the other hand have not. Spreading crap like this is merely tantamount to telling people the sky is purple.
Edit: by the way, the "on a regular basis" part was not directed at you or any other individual person. I was pointing out how often this happens, not keeping score of who has done it the most.
Another Edit: Of course it will be addressed in Android 3.0 ... 3.0 IS FOR TABLETS!
Yet Another Edit: No, you are right, you didn't spend $299 on my opinion. You spent $299 on a bottom of the line Android 2.2 tablet hoping for the best, just like the rest of us... And since you seem so hung up on what the box said, did your box say "Powered by Android 2.2" or did it say "Powered by some guy named Rob's opinion"? I am willing to bet it said the first. However if you decide that you are willing to pay for my "opinion", there happens to be a donate button right under my name on the left. Thanks for playing.
so, yeah. mount locations a rom issue.
'piss' somewhere else?
Sent from my X10i using Tapatalk
Okay--this might be a stupid question, but am I supposed to install this and Dexter's mod over the firmware?
If so, should I do them in a particular order?
Thanks for all that you guys do!
The following is a direct copy paste from somewhere else Enjoy! The wait is over for Alpha!
___________________________________
CyanogenMod for TouchPad
ALPHA 1
"LOWER YOUR EXPECTATIONS" EDITION
* READ THIS COMPLETELY *
Sweet, sweet Internet,
You waited more-or-less patiently for over a month, so at long last, here it is-- an alpha version of CyanogenMod 7.1.0 (an enhanced version of Google's Android 2.3) for the TouchPad.
Understand, this version is definitely an alpha, with all that implies. Those expecting perfection will be sorely disappointed. Many things won't work as well as they will eventually. But you wanted it ASAP, and hopefully, this version should be somewhat useable and gives a sense of progress.
With that said, let's answer some questions, FAQ style.
WHAT KIND OF WARRANTY DOES THIS SOFTWARE COME WITH, IF ANY?
THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Got it? Good.
WHAT IS CYANOGENMOD FOR TOUCHPAD?
CyanogenMod is a community-developed and supported Android distribution for over 60 tablets and phones. This ported version is for the recently discontinued HP TouchPad tablet.
In truth, this "alpha" version is not intended for the general public. Rather, those technically competent hobbyists and developers who are interested in testing an early development version and fully understand the risks of doing so may find interest in it. But there are many bugs and problems in this alpha version. There will be MANY app compatibility issues as well.
WHAT IS THE "ALPHA 1" VERSION AND HOW DO I INSTALL IT?
*** This early version represents the start of a process, not the end, and as such will not be sufficiently awesome, so take any expectations you have and lower them. Now lower them about five feet below that. ***
To be clear, you are encouraged NOT to install this software, as the alpha is only a test version and as stated above, there is no claim that it is fit for any purpose. You may experience issues ranging from the benign to the very serious, including potential data leakage, and/or permanent loss of data, and even the possible "bricking" or permanent disabling of your device. Or worse. It can't be emphasized enough how risky its use may be. Try it entirely at your own risk and with full understanding of the potential for problems and acceptance of any consequences that may result.
That said, if you do understand, acknowlege, and accept these risks and still want to continue, there are installation instructions (and additional exciting caveats and warnings) bundled with ACME Installer.
DOES INSTALLING CYANOGENMOD VOID MY WARRANTY WITH HP?
While HP has expressed moral support for the project ("For those of you in the development community actively working to port Android to the Touchpad, we applaud your efforts"), other HP representatives have also stated that "anyone who loads Android on their Touchpad voids their warranty."
Therefore, it may be prudent to assume that installing (or attempting to install) Android or any other OS besides the stock WebOS would result in the voiding of your manufacturer's warranty. Generally speaking, you must assume any and all risk when experimenting with this software.
SO WHAT WORKS AND WHAT DOESN'T WORK?
Most hardware features of the Tablet should now be supported, although not 100%. There may be issues with sound, camera, wifi, etc. As stated previously, it is definitely an alpha build.
Here is a helpful list of features that are near-completion. Thanks to DarkRedFlame for compiling this.
* Booting into Android
* ADB commands via ADB
* Power, back/home and volume button layout
* Touchscreen support (Multi-touch, 10 fingers)
* GPU Acceleration (2D Acceleration doesn't work, but not a release blocker)
* Dual core processing
* Bluetooth
* Sound
* Accelerometer
* Power Management
* Battery Reporting
* Camera(only video chat, no recording or snapshots)
* Vibration
* Backlight
* LED
* Multiboot (via moboot)
* ClockworkMod Recovery
* Fast Switch Boot
* Fake SD card Mount
* Light Sensor(need to check "Enable Light Decrease" in cyanogenmod settings->display->automatic backlight
* Accessing webOS files from Android and vice versa
* Touchstone Support
* Softkeys
* Wifi
* And much, much more!
As far as what *doesn't* work, that list is probably too long for a FAQ.
* Many apps will have compatibility issues. Many. Including possibly your favorite app.
* Phone-related items (such as the dialer and text messenger) are left in the build. These apps consume minimal energy and can largely be ignored.
* Speaking of energy-- power management has not been the focus of the port thus far. Battery life is not as good as it might be, and you can probably expect improvement in this area over time.
DOES ROM MANAGER WORK?
Not completely. It can't be used to install or update ClockworkMod Recovery for example. Developer Koush will first need to add TouchPad compatibility to Rom Manager.
ONCE THE ALPHA IS INSTALLED, HOW DO I UPDATE FROM THERE?
Once CM is installed, you can use the original ACME installer to install most (but not all) subsequent "update...zip" files you come across.
Or, if you have installed and are familiar with ClockworkMod Recovery, you can also use it to install "update...zip" files as you would for other CyanogenMod devices.
WHAT IS THIS "CLOCKWORKMOD RECOVERY" EXACTLY?
ClockworkMod Recovery, which you can start into from the boot menu, is a special "Recovery" mode-- often used in emergencies when your regular system doesn't load for some reason. Once you have started ClockWorkMod, you are presented with a series of menus and can chose to reset your installation of CyanogenMod to factory settings or load or format individual areas (called "partitions") of your installation.
Additionally, ClockworkMod can be used to back up or restore your entire Cyanogenmod installation to your SD Card. It can also install updates from special "update files" (which are usually named update-some-name.zip).
Since ClockworkMod Recovery is part of CyanogenMod, it is only "aware" of your Cyanogenmod installation. It can not back up or install updates to WebOS or any other operating system.
THE TOUCHPAD DOESN'T HAVE AN SD CARD SLOT. YET CLOCKWORKMOD RECOVERY AND OTHER APPS IN CYANOGENMOD MAY REQUIRE ME TO USE AN SD CARD. WHAT NOW?
If you've used WebOS, you may be familiar with the user-accessible "media" partition that can be mounted to your computer via USB. Well, that "media" partition is now also shared with ClockworkMod Recovery and CyanogenMod, both of whom now identify it as the SD Card (or /sdcard or /mnt/sdcard). So think of this area as a "fake" SD Card, which can be accessed from WebOS, ClockworkMod Recovery, AND CyanogenMod. You can therefore use it as a common area to share files between different operating systems as well as mount it to your PC (again, from different boots). Neat, huh?
I KEEP SEEING REFERENCES TO "MOBOOT". WHAT'S THAT?
MoBoot is a project separate from CyanogenMod, lead by jcsullins and tmzt and based on the "lk" project, which allows the TouchPad to boot into multiple operating systems or recovery images. Technically speaking, it loads just after the "bootie" bootloader that comes with the TouchPad, and displays a menu for the user to select whether they'd like to boot into the stock WebOS or Cyanogenmod, or something else.
You can install the latest version of moboot using ACME Installer. It can NOT yet be installed from ClockworkMod Recovery.
More information about using moboot can be found on IRC (freenode server) in the #moboot channel.
Or, you can learn more about the project at:
http://code.google.com/p/moboot
SO WHERE DO I REPORT BUGS?
The issue list is currently at http://code.google.com/p/cmtouchpad/issues/list
To avoid duplication, do not submit a new issue until you have thoroughly read the existing issues.
OH NOES! I SCREWED EVERYTHING UP! WHAT DO I DO IF I "BRICK" OR SOMEHOW MY TABLET STOPS WORKING?
After you freak out and regret having tried this, you can attempt to hold down the "home" button and the power button together for about 30 seconds.
DIDN'T WORK
Still nothing? Or maybe you have a dreaded triangle-with-an-exclamation-mark on the screen?
Another "emergency" idea (for advanced folks only) is to boot ClockWorkMod Recovery *directly* from your computer via USB cable rather than from the TouchPad's internal storage. To try this, find an "update...zip" file that contains ClockWorkMod. Inside this zip file is a file called something like "uImage.ClockWorkMod". Extract/unzip that file to your computer, then use novacom (which you used with ACME installer) to "inject" ClockworkMod into your TouchPad.
This process should be familiar to you-- very similar in fact to using ACME Installer. It's done by starting the tablet with the up-volume key held down. When you see the USB icon, connect your computer to the TouchPad via USB, then, in a Terminal, navigate on your computer to where the uImage.ClockWorkmod file is, and type:
novacom boot mem:// < uImage.ClockworkMod
Assuming everything went well and ClockworkMod did start up, you may now use CWM to re-install "update...zip" files, restore from backups, format partitions, or reset everything to factory settings. Or use ADB (search online for "ADB" if you're not familiar with this fantastic Android tool) to figure out what's wrong.
I DON'T UNDERSTAND ANY OF WHAT YOU JUST SAID. CAN'T I JUST START OVER?
Sounds like you should give the "WebOS Doctor" a shot. The WebOS Doctor is a program from HP that is used, effectively, to wipe your TouchPad and reinstall the WebOS software so you can begin anew. Get more info here:
http://ws.hpwebos.com/webosdoctor/sorry.htm
The very helpful homebrew site WebOS-Internals.org also has a page that talks about how to use it:
http://www.webos-internals.org/wiki/How_To_Recover
DO I HAVE ANY OTHER OPTIONS FOR HELP?
If none of the above ideas helped, you'll have to go online for assistance.
Browse to http://webchat.freenode.net/ and fill out the web form. Under "Channels", put #cyanogenmod-touchpad and hopefully someone there will have some helpful advice. It is usually not necessary to preface your question with "Can I ask a question?"-- just go ahead and ask.
You may also try one of the many support forums at www.rootzwiki.com or www.xda-developers.com or another Android site.
To a large extent, the Android community will have to help each other as this is an unofficial, buggy release with no corporate, official, or really *any* support. Now you know the reason for all the caveats and warnings.
WHERE IS THE SOURCE CODE FOR THIS RELEASE?
Some of the Android code licensed under the Apache and other Open Source licenses for this alpha test version is not yet available to the general public. However, all GNU Public Licensed software that comprises CyanogenMod, including the kernel, is available at http://www.github.com/cyanogenmod. The kernel for TouchPad used by this project is available at https://github.com/CyanogenMod/hp-kernel-tenderloin .
When appropriate (hopefully sooner rather than later), CyanogenMod will open the code, and patches/fixes can then be submitted by developers via Gerrit at:
http://review.cyanogenmod.com
IS THIS ALPHA OVERCLOCKED?
Overclocking is optional and can be done with an app like SetCPU. Keep in mind it can cause additional instability!
HOW CAN I DONATE TO THIS PROJECT?
To be clear, the key developers of CyanogenMod for TouchPad are not interested in monetary donations for this effort. This is a project motivated by the challenge and satisfaction of working on the port itself, not by financial reward. The developers have previously announced that any "bounty" won for completing this port to TouchPad will be donated to charity.
That said, there are some who have insisted on making some kind of donation to express their support and gratitude. It should therefore be noted that the official CyanogenMod Web site does have a "donation" area in the bottom right-hand corner of the front page.
http://www.cyanogenmod.com/
Also, the CM for TP developers recommend you learn about the Electronic Frontier Foundation ( http://www.eff.org ), which is an organization fighting to preserve and protect the legal rights of the common citizen in this rapidly changing digital age. As large companies and governments try to limit or narrow your rights, the EFF is on the front lines defending the public interest. A contribution to the EFF is also tax-deductible for United States citizens. As supporters, the developers invite you to visit the EFF web site and learn more about their activities and goals.
http://www.eff.org
I AM A "KANGER" WHO WANTS TO TAKE CYANOGENMOD, MODIFY SOME MINOR FEATURE SUCH AS FONTS OR THEMES, THEN OFFER IT UNDER A NEW NAME AND ASK FOR DONATIONS (OR SELL IT) AS IF THIS IS ALL MY WORK. CAN YOU HELP ME?
Absolutely not. One of the concerns about releasing an early alpha is the sad fact that unscrupulous parasites will creep from the shadows of the Internet, slap their name on this port, then try to sell it for an inflated and unwarranted profit. This has been the case for CM on other devices, and we expect, unfortunately, the same thing will likely happen here.
While the GPL and Apache licenses certainly allow CyanogenMod and Android to be sold, and while there may be legitimate occasions where installation or support expenses may warrant or justify charging money, the CM for Touchpad developers are unified in disgust for those who prey upon the uninformed by simply not telling them that a free version of the software is available or by claiming in their advertisements or to the media (who should know better) that they have created or designed the port themselves.
To be clear now-- mods, themes, remixes, and hacks are great- it's the life blood of open source. And there's nothing at all wrong with asking for donations or even charging for something of value you've contributed. But skimming off the free work of others is plain douchy. And not in a good way.
So the developers ask YOU, beloved Internet, to do your part in keeping an eye out for each other's welfare, and enlighten those, including in the media, who might otherwise be taken in by unscrupulous hucksters.
SO WHAT ABOUT YOU? WHO DO YOU WANT TO THANK?
Shout-outs, yeah! Let's start with Hewlett Packard/Palm -- for creating a wonderful tablet, then making it affordable. We are inspired and encouraged by their commitment to Open Source (and do hope this kernel source kerfuffle is resolved quickly). Generally speaking, we really like WebOS and especially the WebOS community, and wanted to made sure that WebOS would continue to be accessible along with CM7, so that users can have the best of all worlds. While thanking HP, it's appropriate to also thank their technical partner Qualcomm, whose Code Aurora project makes CM7 possible not only on the TouchPad, but many other devices as well.
Thanks to Rootzwiki for hosting a forum where people could have meta-conversations about what was appropriate for the forum, as well as meta-meta-conversations and meta-meta-meta conversations... to degrees extending into meta-oblivion. Similarly, thanks to the residents of the freenode IRC channel #cyanogenmod-touchpad for never, ever asking for an ETA. Again, big ups to the WebOS homebrew community for their participation and willingness to offer all kinds of technical insights into how things worked. Particularly we'd like to recognize http://www.webos-internals.org as a source of enlightenment for anyone who's interested in WebOS. If you haven't installed their excellent Preware by now, you have no excuse. Go do it.
A special moment of recognition goes to the members of Team TouchDroid. Wow, that was some drama, huh?
There are countless others who deserve buku credit-- Google, Github, Kernel.org, the wider CyanogenMod and Android community, the thread-that-never-ended on slickdeals.net, those who contributed TouchPads to developers, our teachers, parents, wives, husbands, children, pets, Newton, Tesla, Turing, etc. But this isn't the Grammys, so we'll stop here. The general point is to recognize that all developers stand on the shoulders of giants.
So thanks, everyone, for your help and support so far. And if anyone was missed, sorry.
WHAT HAPPENS WHEN ICE CREAM SANDWICH COMES OUT?
You mean the next version of Android expected from Google sometime in November '11? Well, if the transition from Froyo (2.2) to Gingerbread (2.3) is a model, it may take several months from the release of the Ice Cream Sandwich source code before a viable port to TouchPad is available.
Or not. Ya never know.
WHERE IS THE SOURCE CODE?
Source code can be found at http://www.github.com/cyanogenmod
As of alpha 1 the kernel source is open. The rest of the source will be opened
as soon as some code can be merged into mainline CM7. This expected to happen
very soon.
DOWNLOADS
Initial install will require multiple files to download. Download the installer README first
and be sure you understand the directions.
Note: Please do not link directly to files. Link only to this thread.
Alpha1:
Note: Alpha1 is an extremely rough build. Expect more crashes than you can count. Many many things do not work yet.
Mirror 1:
REAMDE: http://mirror.dal.tdrevolution.net/kmobs/ACMEInstaller README.txt
Installer: http://mirror.dal.tdrevolution.net/kmobs/ACMEInstaller
CM7: http://mirror.dal.tdrevolution.net/kmobs/update-cm-7.1.0-tenderloin-a1-fullofbugs.zip
Clockwork Recovery: http://goo-inside.me/roms/cmtouchpad/alpha1/update-cwm_tenderloin-1012.zip
Mirror 2:
README and Installer: http://goo-inside.me/roms/cmtouchpad...EInstaller.zip
CM7: http://goo-inside.me/roms/cmtouchpad...fullofbugs.zip
Clockwork Recovery http://goo-inside.me/roms/cmtouchpad...rloin-1012.zip
Please keep the conversations civil!
First video: http://www.youtube.com/watch?v=c20yOVKm5UM
Second video: http://youtu.be/fsZXe-_v9uQ
Third video: http://youtu.be/8IVkj_vdY6s
Fourth video: http://www.youtube.com/watch?v=ApfeSj4Ql6Q
Alpha video: http://tinyurl.com/43gwjlo
Show Your Support
To receive notifications regarding updates -> Click to Mark as Installed.
If you like this modification -> Click to Nominate for Modification of the Month.
If you like to thank the author -> Click Here
This modification may not be copied, reproduced or published elsewhere without author's permission.
CM7 Alpha Released 10/13
CM7 Alpha Released [10/13]
CyanogenMod - (A Project that goal is to be able to dual-boot android and webOS)
What currently works:
COMPLETE Wifi (Fixed 10/9)
COMPLETE Camera (Fixed 10/7)
COMPLETE Touchstone Support (Fixed 10/6)
COMPLETE Power Management (Fixed 10/4)
COMPLETE Clockwork Recovery (Fixed 9/30)
COMPLETE Battery Reporting (Fixed 9/29)
COMPLETE Fake SD card Mount (Fixed 9/26)
COMPLETE Vibration (Fixed 9/26)
COMPLETE Bluetooth (Fixed 9/24)
COMPLETE Dual CPU Processor (Fixed 9/23)
COMPLETE Fast Switch Boot (Appears fixed to me Video Update 9/23)
COMPLETE Booting into Android
COMPLETE ADB commands via ADB
COMPLETE Power, back/home and volume button layout
COMPLETE Touchscreen support (Multi-touch, 10 fingers)
COMPLETE GPU Acceleration (50/50 2D Accel support, just like any other gingerbread device out there)
COMPLETE Sound http://www.youtube.com/watch?v=ApfeSj4Ql6Q
COMPLETE Accelerometer http://www.youtube.com/watch?v=8IVkj_vdY6s
COMPLETE Backlight (Confirmed in IRC)
COMPLETE LED (Confirmed in IRC)
COMPLETE Multiboot (Confirmed in IRC)
COMPLETE Light Sensor (Confirmed in IRC)
COMPLETE Accessing webOS files from Android and vice versa
COMPLETE Softkeys
PARTIALLY Compass (Bugs need to be worked out)
What does not currently work:
See issues below
What's currently being worked on:
Gyroscope
Beating Metal Gear Solid 4 under 5 hours.
Bugs and Issues, see below.
What can possibly work:
HDMI through Micro USB (The System-on-a-Chip has the required hardware, have to find which pin #) (webOS 3.0.4 may have HDMI support, and if so we can reverse engineer the process, stay tuned)
GPS (Does not seem possible to implement because hardware seems to be lacking GPS functionality)
Issues:
High Priority Cannot record sound, unless sound is already playing [Accepted]
High Priority Battery Drains while sleeping and active [Accepted]
High Priority Plugging in headphones does not mute external speakers [Accepted]
Medium Priority Apps in market are being filtered [Accepted]
Medium Priority Battery does not shut down device at critical battery level [Reported]
Medium Priority Camera does not take pictures [Accepted]
Low Priority Reboot and Shutdown can take a long time [Accepted]
Low Priority LED light turns off while sleeping [Accepted]
Low Priority Light Sensor does not work automatically, needs to be turned on manually [Accepted]
Low Priority No audio support for BT headsets [Accepted]
Low Priority Add divx codecs for video support [Started]
Low Priority GPS apps crashes because apps assume for valid GPS [Accepted]
Fixed Reboot to Android from webOS app (Fixed 10/12)
Fixed msm_rotator does not work correctly. Screen may rotate for video, but becomes distorted. (Fixed 10/11)
Fixed Sleep Issues (Fixed 10/11)
Fixed Touchscreen has feedback issues (Fixed 10/11)
Fixed Camera fails to save to disk, does not rotate (Fixed 10/11)
Fixed Airplane mode stays on once turned on, happens because the touchpad doesn't have a real radio interface layer. (Fixed 10/10)
Fixed Screen stays blank for 10 second before boot animation appears (Fixed 10/9) (Confirmed in IRC)
Fixed Wifi Issues (Fixed 10/9)
Fixed Sh exceeds the open file limit (Fixed 10/9)
Fixed Sleep Issues for Wifi (Fixed 10/9)
Fixed CPU stays on max frequency (Fixed 10/8)
Fixed Touchscreen turns off when accelerometer is disabled (Fixed 10/7)
Fixed Touchstone works and charges, but no event is raised to show you it's charging (Fixed 10/6)
Fixed Touchscreen events (touches) are ignored after sleep (Fixed 10/5)
Fixed Protect certain partitions in the kernel (Fixed 10/5)
Fixed Root for bluetooth cmattach (Fixed 10/5)
Fixed Touchscreen stays on at all times, even when screen is turned off (Fixed 10/4)
Fixed Touchscreen has issues with pinch gestures (Fixed 10/3)
Fixed No root access (Fixed 9/30)
Way to double post there ace...man these forums are a joke now. Ill stick to rootz from now on.
Nice... installed perfectly anyone pushed Market.apk to theirs yet....?
Scratch that... Installed "gapps gb 20110815 signed.zip"
Been waiting for this.. Thanks to all the devs working on this project.
Any feedback from the early installers?
At work, so I won't be able to try this for a good 10-11 hours.
Missing G-Apps still trying to find an update that will install them, other than that the device is very snappy touchscreen it so much more responsive a few minor bugs (one of which it wont connect to my work's wireless) other than that i am very impressed.
Just Me said:
Any feedback from the early installers?
At work, so I won't be able to try this for a good 10-11 hours.
Click to expand...
Click to collapse
I watched the install vid. but i need to install from a windows computer. anyone with a walkthrough?
jdmtsx said:
I watched the install vid. but i need to install from a windows computer. anyone with a walkthrough?
Click to expand...
Click to collapse
I've written a "somewhat" easier tutorial here
Question at all: is it normal there is no marketplace?
(I'm not that android-guru ^^ )
so two questions to the early addopters: will it delete/modify the custom kernel in webos and will it **** up the partition layout on the touchpad?
mendel129 said:
I've written a "somewhat" easier tutorial here
Question at all: is it normal there is no marketplace?
(I'm not that android-guru ^^ )
Click to expand...
Click to collapse
Thanks for your tutorial!
However step 5 is vague.
could you please elaborate on:
grab the cmd, browse to the place where you’ve downloaded the acmeinstaller file, and type “C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
How do I "browse to the place I've downloaded the acme installer?
Lets say for example it is in: C:\Users\Zak\Desktop\cm7touchpad\ACMEinstaller
How do I browse there in CMD.exe ?
Thanks!
zgroten said:
Thanks for your tutorial!
However step 5 is vague.
could you please elaborate on:
grab the cmd, browse to the place where you’ve downloaded the acmeinstaller file, and type “C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
How do I "browse to the place I've downloaded the acme installer?
Lets say for example it is in: C:\Users\Zak\Desktop\cm7touchpad\ACMEinstaller
How do I browse there in CMD.exe ?
Thanks!
Click to expand...
Click to collapse
cd \Desktop
cd \cm7touchpad
or just cd C:\Users\Zak\Desktop\cm7touchpad\
(you can autocomplete with tab )
mendel129 said:
cd \Desktop
cd \cm7touchpad
or just cd C:\Users\Zak\Desktop\cm7touchpad\
(you can autocomplete with tab )
Click to expand...
Click to collapse
Thanks!!
Sorry for bugging you, one more question...
I am getting "Access is denied" after typing:
C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
zgroten said:
Thanks!!
Sorry for bugging you, one more question...
I am getting "Access is denied" after typing:
C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
Click to expand...
Click to collapse
1) are you running cmd in elevated permissions?
2) do you have novacom installed in the first place?
mendel129 said:
1) are you running cmd in elevated permissions?
2) do you have novacom installed in the first place?
Click to expand...
Click to collapse
Yes, and Yes.
It shows up in my programs list as "Novacomd"
Well mine installed ok but it seems to wipe your WebOS install (at least it did for me) so I had to restore my palm profile!
Not had much time to play with android yet but im impressed so far!
Loving this! xD
Sent from my HP Touchpad using Tapatalk
Can't imagine why it wasn't released here.
/sarcasm
My problem is actually that I cannot get it to mount.
mendel129 said:
Question at all: is it normal there is no marketplace?
(I'm not that android-guru ^^ )
Click to expand...
Click to collapse
download the google apps package from here: http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps
put in on your touchpad
boot clockwork recovery using novacom (same as for installing cm7, but instead of using "ACMEInstaller" use "uImage.ClockworkMod", go to install, install from zip on sd card, choose the google apps package
done =)
and you have a functional marketplace
Does anyone know the mechanics of the exploits used on the Transformer? They tend to come as .exe files without source code. If we can figure out what they used to break HC on another device, it'd be our first step for the same on the TPT.
I ask this because the prior exploits not working on HC seems to indicate that many of the normal vectors were patched out of HC.
I'm pretty sure I've read somewhere that it uses Asus' backup app.
But it seems like that Lenovo's Mobility Manager has root-privileges to set up the device remotely. I think there could be an exploit for our tablets.
Or somebody finds an exploit inside the Honeycomb source code and provides an universal root mechanism.
Sadly I'm no dev, so chances are high that the text above is just bullsh*t
Hmmm, that's an interesting idea...I haven't paid much attention to the mobility manager. Also, there are a lot of Lenovo tools that would need root(their configuration manager when you activate it)....I wonder if it has any exposed undocumented interfaces...
won't have time for the next few days(holiday hectic period), but I'll do some decompiling on the lenovo apps to see what I can find expose in those goodies. Hopefully, I'll get the accursed Windows OS to recognize debug mode properly(or give up an VM linux).
Yes they use the backup tool.
All the preinstalled apk's reside in /mnt/pia, which itself is on an own partition: /dev/block/mmcblk0p6
realyst2k said:
Hmmm, that's an interesting idea...I haven't paid much attention to the mobility manager. Also, there are a lot of Lenovo tools that would need root(their configuration manager when you activate it)....I wonder if it has any exposed undocumented interfaces...
Click to expand...
Click to collapse
I don't think the mobility manager has any privileges beyond standard android permissions like android.permission.CHANGE_NETWORK_STATE or android.permission.CHANGE_WIFI_STATE.
There is also the McAfee Enterprise Mobility Management; I don't know exactly what it does but it seems like not much. You can shell over what is presumably a lot of $$$ so McAffee's app gives you a button to show the apps that you have to install yourself
Of course Lenovo saved itself the trouble of providing a backup solution, so there is no backup. In the strange Lenovo parallel universe, this is apparently acceptable for a business device.
Moved to general
I did not move this straight away because i thought it might become a development thread. Its not gone that way.
So because it is a question, i will move it to general.
Take it easy
O_G
Honeycomb exploit u
Yes I know the the Honeycomb exploit used on the Transformer . you contact me from the contact information or visit our website mobiloitte.com.
So for those of you wondering if a Hardware Level Modification can be made to the US-VZW 3G+WiFi Xoom to enable the Native Tethering capabilities of the Xoom...Similar to the one used on the Droid 3, X2 and other Motorola Devices (Thanks To Team RedHat and CellZealot)...There IS!!!
Last night, while working on another project on the Xoom, I had an idea. Here is the result.
NOW, I am saying this up front! IF you decide to make this modification, you do so at your own risk. Both the risk to your device (possible completely bricked Xoom) and to the possible violation of your Terms of Service with your specific provider. Please know and understand the risks, and don't blame me if it goes horribly wrong and you end up with a Xoom shaped paper-weight.
I do need some willing volunteers to test the system on their Xooms and make sure that others are:
A) Able to follow the directions and clarify any points I may be vague on describing.
B) Verify my results of making the native WiFi Tethering work on the Xoom.
I will be gone most of the weekend, but please PM me if you are willing to give this a try.
Items you will need:
Latest Motorola Drivers WITH Moto-Helper. Download the latest version from here: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
RadioComm 11.12.1 (Could be that 11.11.11 works. I will try that over the weekend and verify)
Micro USB Cable
Windows (RadioComm application is for Windows, sorry Linux Ladies and Gentlemen)
A LOT of Patience
Notepad or similar note program to copy/paste original information
Ability to follow directions Without skipping steps.
Able to Document all your steps.
A good grasp of copy/paste and right-click function
A willingness to push the envelope on your device to prove a concept.
Again, this is a proof of concept. I do not condone or encourage violation of your terms of service with your provider.
I do NOT yet know if this works on the 4G upgraded Xoom tablets. Volunteers appreciated. Otherwise I will be sending mine in for upgrade soon and can test the following: If the mod survives the upgrade process, and if it works after the upgrade to 4G (There is no reason it shouldn't unless changes are made at the NvRAM level with the 4G upgrade, AND those changes include these values)
It is very similar to the Version for the Droid 3, but the parameters are different for the 3G Xoom. It has also been setup to block some of the features that we used to so easily make the changes to the Droid 3. The first item you will note, when making the change, is that the characters are no longer visible in the field where you will be copying and pasting your values.
The other change is that it will only ACCEPT 256 bits when storing back information. If you export the Existing values, it will add 128 bits of 0s to the output. Read as a huge pain to make sure you delete exactly 128 of them.
The Field for the Radio Session Information is in a different Tab of the RadioComm application as well. Read Element Length is Greyed out, so you get what you get for an output. No more can you dictate that value.
Essentially, it means that this Mod IS possible. CAN be done WITHOUT root as it is a Hardware Level modification below the operating system. Similar to Team RedHat's Awesome Explaination HERE
So, that being said. PM me today and tomorrow if you want me to send you directions on trying the procedure Sunday night, and I will take care of getting those PMd back to you.
Thanks to CellZealot for the 11.12.1 version of Radiocomm. And Thanks to TBH for finding the vulnerability to seek out and test on the Xoom.
If you like what I do, or have helped you; please consider Donating. All Donations in February are forwarded to a DEV that has helped me and many others in the Eris forums; Workshed. (Thanks Shed, for everything on the Eris! 2 still running GSB 4.4)
You will also need contortionist fingers (joke) to be able to put your xoom into BP linux-cold boot in order to get the NV to read properly and allow the mod.
If not returned to original via RadioComm, this appears to be a permanent WiFi Tether enablement for the VZW-US-3G Xoom.
AGAIN, I take NO responsibility for you damaging your device or violating your Carrier's TOS. This is proof of concept ONLY. Use at your own risk.
IF I get too many volunteers, I WILL let you know the trial is MAXed out, and will post the final findings in the next posting that I will reserve for the Directions and Layout.
I'm thinking that 10 will be the Max for this week. If all goes well, I will have directions posted by the end of next week. Let's hope!!
Thanks, and please consider making a Donation for the "Give to Shed" fund.
Reserved for Directions
Reserved for Current Findings Updates
Moved to proper forum.