I have only had my G-Tablet for about a week and I already ROM it to 2.2 Vegan. This is probably a simple issue and easily fixed. I know Windows very well but the Android OS is totally new to me, sorry.
I have kids and installed a 16GB MicroSD card for movies. I have played with format and such for a few days and finally found that ACC audio at high volume settings and Mpeg4 Video seem to work the best. I use Total Video Converter and it works for everything i have, the G-Tab, Xbox360, my wifes iPhone, and even my Blackberry.
Anyway the issue is when I turn the Tablet off and then back on it keeps re-formating the MicroSD and I can't figure out how to make it stop doing this. I converted 8 movies (7.39Gb) and after the first shutdown of the day it formatted the card.
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Also double check which version of Vegan you are running. Vegan Froyo is up to 5.1.1, but has been discontinued. It's now called Mountain Laurel and is hosted on Slatedroid. It requires the 1.2 bootloader. I'm running CalkClem V6 http://forum.xda-developers.com/showthread.php?t=1024120 as a daily driver and it's amazing.
brettdwagner said:
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Click to expand...
Click to collapse
Thank you I will give it a shot here in a few minutes. If it works my kids will be most greatful.
brettdwagner said:
Also double check which version of Vegan you are running. Vegan Froyo is up to 5.1.1, but has been discontinued. It's now called Mountain Laurel and is hosted on Slatedroid. It requires the 1.2 bootloader. I'm running CalkClem V6 http://forum.xda-developers.com/showthread.php?t=1024120 as a daily driver and it's amazing.
Click to expand...
Click to collapse
I may need to change anyway. I am now getting a pop-up error, 3 and 4 times when i first boot. SORRY! the application Google Services Framework (proccess com.google.process.gapps) has stopped unexpectedly. Please try again. < Force Close >
Not sure what I did?
I am actually surpriced no one has come out with a fully functional Honeycomb OS for this tablet yet. I keep reading and they are still have wireless issues or some other small issues. Personally I want to try and upgrade it to a working 2.3 Gingerbread version.
Question, what Android version is CalkClem V6 build on?
Your force close issue will be solved by formatting the sd card. This will delete everything on your internal SD so beware! Instructions are in this tutorial http://forum.xda-developers.com/showthread.php?t=865245
CalkClem V6 is running Froyo, which is the only version of android which is fully operational on the gtab (full hardware acceleration). Gingerbread and Honeycomb roms work pretty well, but for me Froyo is perfect. Give CalkClem v6 (or5) a try if you have some time, it's based on the stock OS, but it's blazing fast (and overclocked to 1.5Ghz by default). Battery life is excellent.
Make sure you pay attention to your bootloader when selecting a new ROM. To read up on your bootloader and why it's important check out goodintention's site: http://viewsonic-gtablet-for-dummies.webs.com/
Good luck!
woody213 said:
I may need to change anyway. I am now getting a pop-up error, 3 and 4 times when i first boot. SORRY! the application Google Services Framework (proccess com.google.process.gapps) has stopped unexpectedly. Please try again. < Force Close >
Not sure what I did?
I am actually surpriced no one has come out with a fully functional Honeycomb OS for this tablet yet. I keep reading and they are still have wireless issues or some other small issues. Personally I want to try and upgrade it to a working 2.3 Gingerbread version.
Question, what Android version is CalkClem V6 build on?
Click to expand...
Click to collapse
Froyo, 2.2
And don't be surprised with not having a fully functional HC rom yet. In fact, the GB roms are also not "fully" functional. Nvidea has not released drivers for those OSs for our hardware. If they never do, then we'll never have fully functional versions of those firmwares. It also appears that HC runs on a different kernel base. From what I've read, the kernels we have available now are .32 kernels, and HC needs a .36 kernel. the numbers don't mean much to me, but kernel devs saying that it's a difficult hurdle eto jump does. If Pershoot and Clemsyn aree leary about developing .36 kernels, then it must be pretty difficult.
brettdwagner said:
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Click to expand...
Click to collapse
Well it is still deleting the movies. I read your post and tried to create a folder called .nomedia on the MicroSd card and windows will not allow the . in the folder name so I tried just nomedia as a folder name and surprising the folder stayed but the media with in the folder was deleted.
brettdwagner said:
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Click to expand...
Click to collapse
Disregard the last post. I must really be having a bad day. Windows can't make that folder but the tablet itself can. when I did that I moved my sons movie "Planet Hulk" and it stayed in the folder no issues. Thanks again.
You just saved me A LOT of headaches and frustration!!! Scanning another thread for a solution about my external microSD causing my gTab to lock up, doing what you suggested, adding a file named .nomedia, worked perfectly!! 3 system reboots in a row anyway. When I use it tomorrow we'll see if it still works
My gTab would hang for as long as I let it whenever I would insert any of my microSD cards into the slot. Scanning SD Card would NEVER go away, gTab would lock up, simply hitting the power button would shut it down. But not like holding it down to shut it off normally, hitting like you want to put it into sleep mode, that type of hit would just shut it down. Take the card out - gTab would work perfect...........
Now I can leave the darn thing in there instead of using the USB adapter I bought for it and it's one more "annoyance" I've managed to overcome.
THANKS!!!!!!!!!!!!!!
BTW, stock operating system....yes, the god awful tap n tap 1.2 crap..... I only watch mp4 movies on it and that works great, so I'm not messing with ROM's.....yet.......
brettdwagner said:
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Click to expand...
Click to collapse
Related
Do the android development builds work on the T-MOBILE US version of the hd2? When i boot up haret from the sd card, I see the linux bootloader but it says failed to load rootrs or something of that nature. Then it blackscreens and if i press a button it advances the bootloader line. Sooo I'm not quite sure if it works for the US version of hd2. Anyone know?
i got it working on mine. using the non-sense (see what i did there) version. i have the same issues others have, though. not quite ready for daily usage, but it's quite usable for what it's worth at this point.
Ahh non-sense version (lol), I can't seem to get it to work, I download the file and extract directly to the sd card, then i use file explorer to run haret.exe and it just doesn't load correctly like the videos on youtube. Wasn't sure if i was doing anything wrong. (sense version 3 from darkforce)
MaspaniQ said:
Ahh non-sense version (lol), I can't seem to get it to work, I download the file and extract directly to the sd card, then i use file explorer to run haret.exe and it just doesn't load correctly like the videos on youtube. Wasn't sure if i was doing anything wrong. (sense version 3 from darkforce)
Click to expand...
Click to collapse
i tried that. the sense version consistently gave me a bsod.
Perhaps your radio version!
Do not match?
Quite awesome, I got it working. I accidentally had the haret and android files in a folder in my sd card rather than on the root sd. haha this is awesome
the OP should have posted this thread in HD2 general section ... please check next time.
Very Important Information For Beginners
/Introduction to Android for SD Cards
Okay, firstly I made this thread because pretty much every new person to this section of the forums is completely lost and unsure what things are or what to even do. We are also sick and tired of threads saying 'how do I get stared' or 'which is the most stable' etc.
----------------------
Download your files from here:
You will be accessing these websites quite often so it might pay to bookmark them
Kernel downloads, almost always download the top one, they are updated often (needs extracting): http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Rootfs downloads, download the top one, they aren't updated as often as the kernels above but still quite regularly (also needs extracting): http://files.xdandroid.com/rootfs/
Initrd downloads, rarely updated (don't extract, just rename to initrd.gz) http://files.xdandroid.com/initramfs/ People almost never need to download one of these separately.
----------------------------------
Basic need-to-knows:
Kernel: Your modules/zImage. Your zImage always needs be in the root (first folder) of your android folder on your SD and ALWAYS named zImage, your modules should also be in the root of your android folder named modules-LOTSofNUMBERSandLETTERS.tar.gz never rename your modules. It should always be in .tar.gz EG: modules-2.6.27.46-01276-g6a6a1c1-dirty.tar.gz
Rootfs: Must be in the root of your android folder named rootfs.img
Initrd: Needs to be in the root of your android folder named initrd.gz
Data.img: Generated on the first boot of android and placed in root of android folder. Is a virtual memory file that acts as the phones internal memory for android. Holds all your settings etc. May have to be recreated some times (just by deleting it)
Haret.exe: the file executed by your Windows ROM to kick Windows out of memory and boot android.
system.ext2: Main android file, must be in the root of your android folder. Holds all of your build.
startup.txt: File that instructs android how to start up. Needs to be in the root of your SD. (I will cover this further down)
ts-calibration: A file in the android folder that holds calibration information of the touch screen.
Various Folders: You will see/have/need other various folders created in the root of your SD and in the root of the android folder, such as conf, cache, data, media etc. You usually don't want to delete these.
Root: The root folder of any partition is the "highest" folder in the hierarchy. The root folder contains all other folders and can also contain files. For example, the root folder of the main partition on your computer is probably C:\. The root folder of your DVD or CD drive might be D:\.
Also Known As: "the root"
RIL: Radio interface layer: basically controls your radio (GSM/CDMA network)
------------------------------------------------
startup.txt
VERY IMPORTANT, your startup.txt must be customized to your device. (mine is a rhod110). You can find your model number under your battery. This file belongs in the folder with your android.
My startup.txt looks like this
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 rel_path=FRX07 physkeyboard=rhod100_uk acpuclock.oc_freq_khz=710000"
boot
Now I believe you should be able to copy and use this as yours with a few slight modifications. Change rel_path= to wherever your android is stored on your sd, for example when I go to my sd inside the folder frx07 (the root of my android folder) all my android files are there. If your folder was called andboot it would be rel_path=andboot. (without that full stop) Now change your physkeyboard= to your model of your phone, mine is rhod110 but the rhod100_uk keymap is EXACTLY THE SAME AS THE RHOD110 so that's why I use rhod100_uk instead of rhod110 (rhod110 isn't recognised by frx07), this is important to make sure your keys are assigned properly.
------------------------------------------------
Models of rhod:
From what I know that exists. If you find one not listed, make sure you tell me so I can update the list
rhod110 uses rhod100_uk and it works as it should
These can be used for physkeyboard= in startup.txt (needs updating, some may no longet be supported because F22 hasn't commited old changes)
rhod100_de
rhod100_es
rhod100_fr
rhod100_it
rhod100_nl
rhod100_nordic
rhod100_uk
rhod210
rhod300 (tilt2)
rhod400
rhod500
Getting set up:
Go to http://forum.xda-developers.com/showthread.php?t=1171052 and download the FULL BUNDLE
Other builds exist such as gingerbread but this guide only covers froyo frx07.
Replace/add the Kernel from the downloaded build with the latest one (remember this is the zImage and modules-NUMBERS.tar.gz). Updating is as simple as this, do it often - there is no data loss. See links mentioned above for links. Making sure that the (if there were) old kernel files are all deleted and the new ones are called zImage and modules-NEWdifferentNUMBERS.tar.gz
Replace/add the rootfs.img with the latest one from the link above it should be named rootfs.img.
Remember that the rootfs and kernel are updated quite often and that you should check and update every few days.
Make sure your startup.txt is correct and make sure everything is where it should be in a folder on your computer, then copy the folder to the root of your sd card.
Navigate to this folder using the file explorer in your Windows ROM (YOUR PHONE) and run the Haret.exe
It will then have some writing running down a black screen before booting android (it's just preparation to booting) read it if you want
Android will start and you should leave it about 2-5 minutes before touching anything, it has things running in the background and it will be slow, still setting itself up. Navigate to settings and set up your phone. If anything goes too badly wrong you can always delete data.img and start again! Data.img is the internal memory of the phone, remember? Well, until we get android working on the real internal memory...
---------------------------
Structure:
My SD card. (with android on it)
I'm running:
kernel: 20110819_183957 http://glemsom.users.anapnea.net/android2/htc-msm-linux/
build: Froyo FRX07http://forum.xda-developers.com/showthread.php?t=1171052
rootfs: rootfs-20110816-7e04198.zip from http://files.xdandroid.com/rootfs/
Code:
EncFiltLog.menc
kbd_info
Android
cache
download
tmp
Private
Games
Installs
DCIM
Others
Videos
Images
Sounds
media
frx07
rhodimg.nbh
My android is in frx07
inside my frx07:
Code:
data.img
ts-calibration
startup.txt
modules-2.6.27.46-01348-g9de837f.tar.gz
zImage
haret.exe
initrd.gz
system.ext2
AndroidApps
conf
media
rootfs.img
-----------------------------------------
Backup/Restore
when you have the need to backup and restore data, look for an app called Titanium Backup. I have never used it but heard it works brilliantly, even backing up your apps! There is a 'donation' version and a free version with not many differences. I suggest you go check it out!
-----------------------------
USB CONNECTIVITY
When your phone is in Android you can not use it like a USB, HTC's drivers will not work and you have to use certain programs until this is implemented.
Windows: Install DroidExplorer this lets you open a terminal (like command prompt) on the phone, lets you browse device adding/deleting files, among other features that are very useful. If that DroidExplorer doesn't pick up your phone (when picked up it will be called 0000000000) install PDAnet on your phone and pc. PDAnet provides the drivers needed to connect the phone. It also lets you use your phone as a modem and you can send SMSs using your computer. Do NOT run PDANET at the same time as DroidExplorer. When PDANET is connected it WILL use your phone for data connections - this is the only warning. The phone is not used for any networking when DroidExplorer is connected.
Mac: Unknown to me (can someone post?)
Linux: Never tried, it is easier than windows (can someone post a method?)
---------------------
Overclocking
Do NOT overclock WINMO.
If you want to overclock your device do so at your own risk.
it is as simple as adding "acpuclock.oc_freq_khz=710000" without quotes to your startup.txt cmdline. 710000 (approx 710 mhz) can be swapped for any number but this is practically the highest stable speed achievable. I use 710000, works fine for me.
-------------------------
Known problems across ALL BUILDS:
Media Player Some tracks might have playing issues. FIX: HERE
Bluetooth is experiemental
Speakerphone static : seemingly random issue
USB plugging the device into a computer, it will be recognised, but not by HTC drivers. FIX: You must use something like DroidExplorer and PDAnet to browse the device and ADB (android debug bridge). See above ^^ (USB tethering is being fixed/has been fixed)
FN LED On keyboard the caps LED works but the FN LED currently does not. FN still works fine
No deep sleep: FIX: disable GPS (or kill the running app causing phone to not sleep)
Failure booting Android: Phone fails to enter android after running haret.exe FIX: Make sure your winmo is NOT overclocked before booting android.
Booting or SD Card related problems: Make sure your card is formatted as FAT32 (reformat as Full Format if it is not working)
More information is available on the wiki, there is also information there if you want to get into development. There is a pretty good FAQ on that wiki too
Remember XDAndroid is not just for this device.
If any of this is wrong or you think something should be updated/changed, please tell me
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
AkumaX said:
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
Click to expand...
Click to collapse
Indeed, there is no "is_gsm" command .
arrrghhh said:
Indeed, there is no "is_gsm" command .
Click to expand...
Click to collapse
Thanks to both of you, not bad considering I don't even have a cdma phone eh?
anything I need to add? I will tidy it all up soon
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
the.decoy said:
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
Click to expand...
Click to collapse
I thought this was squashed in recent kernels?
arrrghh said:
saneksem said:
add that to startup,helped me on 2 gb card
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
You don't need this if you're on a newer kernel!!!!
Just update your kernel folks, no need for this in the startup!
Click to expand...
Click to collapse
Oh, ok. I must have missed that. I only needed it on my older SD which I haven't tried using for a month or so.
I guess the only thing I would suggest (all minor things) would be maybe to bold/underline keywords, like "kernel", "rootfs", etc.. to differentiate things that may change over time; ex: I'm running FRX05 system.ext2, 3/1/11 rootfs from F22, 3/1/11 zImage/modules (kernel) from arrgghh, etc... And, I guess you "could" be nice and show people what they could edit in the startup.txt, depending on their phone; ex: I'm Sprint, so I would do kb=rhod400, cdma=1, etc..., but for each phone.
I would probably have to do all the different startup.txt's in a different thread, unless I just provide a quick table... I will think about it however I do like the idea about bolding key words.
Most new people don't realize if they have their call/end/windows/back buttons on in winmo, they will stay on while on android and never go off. Might want to put that in your first post before telling them to run haret...
at the end where you say you can just delete the data.img and startover its probably a better idea to say to be patient and reboot the phone once or twice before ditching your data.img ! and creating it is the bulk of the first boot, the linux black screen with the scrolling words section.
you can talk about saving your data.img just incase something goes wrong.
titanium backup is a must
having an app that can save sms when you switch builds (not a big deal for everyone but important to some.)
also let new users know android isn't perfect, things randomly completely mess themselves all the time, don't get discouraged just start fresh with a format and new files when deleting the data.img doesn't work and you'll be just fine.
All I want to know now is if I have helped anyone yet and if they had any problems with any part of it or want me to clarify anything I will be quite happy with such replies ^-^
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
ryannathans said:
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
Click to expand...
Click to collapse
There's never an ETA for anything getting fixed - BT seems close, but who knows the exact date it will be done? As CyanogenMod says, the only rule is don't ask for release dates / ETA. It'll be ready when it's ready.
Some problems are being looked into more than others, but I wouldn't say one in particular has been left out to rot. jb is fixing up BT, entropy is working on GPS fixes, wistilt2 on the RIL of late... Basically devs pickup things that are of an interest to them to fix. There's a lot still to fix/cleanup, so taking it all on alone is a little daunting. Gotta break it down into smaller pieces so it's at least somewhat manageable.
Thanks and a question...
First, thanks for the awesome post - quite helpful...
Second: I haven't mussed with my phone for about a year, for various reasons, the main one being that I was happy with my previous phone and the ROM I finally settled on, the secondary one being that phone died, and I now have a (blech) Sprint TouchPro2 (RHOD400), and am on my sixth (yes, sixth!) brand new TP2 - they keep giving me a new one because of problems (things, like... oh... say, not being able to answer calls... kind of a basic function in a mobile phone, nah?!) And, I've had no interest in futzing with what is already a frustrating and non-functional phone. I was hoping I could upgrade instead of getting another TP2 the last time I brought it in for probs, but they would only downgrade me to worse phones. So... here I am, wanting to put Android on my phone and see if there is any improvement. Or, at the least, be able to utilize some of the decent progz/gamez for Android. I mean, if I can't answer calls, at least I can use it as a handheld gaming system, right?!
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
PS: one of my friends said "Tell 'em you're a hawt babe - then they'll help for sure!" (ROFL)
And, thanks, again!
Tynkrrbell said:
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
And, thanks, again!
Click to expand...
Click to collapse
Well the reason you can't find any info on it, is that it's not required .
These builds run entirely off of the SD (currently - I wouldn't try NAND yet, it's in its infancy) so there's no need to do any HardSPL or anything really to prep - just drop the bundle on your SD card - if it's at the root, run haret.exe and gogogo!
Oi. I get the stupidcard of the day!
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
My gf suffices for that .
Hope you enjoy Android!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
Not to burst any bubbles here, but if you are saying you are a "hawt babe" and give boobpr0n mumbo jumba, you are prolly not one and won't give it anyways.. so nobody will most likely believe you here..
Good luck though~
Below,I will list the steps I do to setup my webtop,I am using webtop2sd on a 32GB PNY Class 10 card, and used a 2GB Transcend (not sure on class,im sure its old) card to test with, same results with both pretty much,so I think something im doing is causing it to stop working.
What happends when it stops, is it just wont come up anymore. When I plug the phone into my lapdock, I either get a bluebox with an HDMI not found error (I'm assuming from the dock itself), or the red moto logo that just moves around. I would try resetting the phone, and reinstalling the executable through the webtop2sd app, and it still wont launch. This has happened about 5 times so far, I would get it setup how I would want it to be,then it stops working.
So here is what I would do (there is a phone reboot between each step pretty much)
1. Use my PC to partiton the SD card, ~22 GB FAT32 followed by an ~8GB ext3
2. Use webtop2sd to create the webtop, default settings, aside from the missing dock fix, which I only used 2-3 out of the 5 times I ran it
3. Once I am in the new webtop, I would install terminal and synaptic,then reboot.
4. Then I would run the webtop scripts, version 1.4, hitting yes to everything, then a reboot
5. I would check to see if synaptic is installed, the last time i did this, I had to use aptitude to install it.
6. Once I got synaptic up,I would use it to install the xfce4 package. Just about everytime I would go to install it,I would get an error on the "tzdata" package, the only way I could get past it,would be to uninstall tzdata, then most of the time,whatever I would go to install would reinstall it anyway. This does concern me, because when I remove tzdata, it appears to be tied to a critical package, which may be the source of my problem,but I am not sure.
7. Once I would get xfce4 installed,I would add xfdesktop and xfce-panel to the startup list (those may not be the exact package names,there is another thread I reference for that, can't remember atm, nor can I remember the exact name of that startup file, but its on this forum somewhere). I would also comment out the awmdock one and the webtop desktop one as well.
8. I would reboot,and it would actually boot up xfce4 just fine, the only gripe I have,is that I would usually get an error on the trash service needing thunar, when it is already installed. The one time,I was able to install open office, and test out some youtube videos.
9. At about this time, I would reboot my phone to see if it still works, then I would get the "bouncing moto logo of death" on my lapdock screen, and would have to start over.
One other unrelated note,about every other time I would reboot my phone, it would come up saying SIM card not installed, so I would reboot it again to fix the problem. So there were normally 2 reboots when a reboot is required.
So,I guess I would ask a few direct questions about my problem
1. Has anyone else had a problem with the tzdata package? Is there a way around it without uninstalling it?
2. Could the full xfce4 package be breaking the webtop? Do I only need certain packages out of it?
3. Even though I tested this on 2 different SD cards, could my problem be that the files are just getting corrupted on the card? Its pretty consistant though, I canpretty much say "Look,my awesome webtop is now setup how I want it to be, now watch me reboot my phone to see it not work anymore" everytime I go to set it up.
Info on my phone:
Stock firmware, unlocked bootloader, cwm installed (I thought I needed it,but not for webtop2sd) and rooted running latest webtop2sd. I havent messed with the stock webtop on the phone itself, i rather not since I like having it as a backup.
Btw, I am a bit of a linux n00b, I've pretty much just been reading what other people have been doing. Any help would be appreciated, thanx
You sure like to mod the webtop. Lol jk.
I have no issues and I have webtop with the Lapdock with the Ninja ROM. My phone is bootloader unlocked and rooted. I personally think you modded too much if that's possible. If I were you, I would start over and try webtop with stock firmware or a ROM with a fresh sd card. That way you can know if your phone has a hardware issue or if you modded too much. Hope this helps.
Sent from my Atrix XDA Premium App
I can assure you that your phone is more modded than mine is, since im running stock firmware. What I'm doing is really not that much modding, I'm just trying to get a better interface running on the webtop, which people have posted saying they have the same one working on theirs. Its also not that I can't get it working, its really not hard, just time consuming, I just need to know why it keeps breaking on phone reboots...
teeth_03 said:
I can assure you that your phone is more modded than mine is, since im running stock firmware. What I'm doing is really not that much modding, I'm just trying to get a better interface running on the webtop, which people have posted saying they have the same one working on theirs. Its also not that I can't get it working, its really not hard, just time consuming, I just need to know why it keeps breaking on phone reboots...
Click to expand...
Click to collapse
I honestly think you should try some of my suggestions. I think starting fresh is your best option. When something doesn't wok right or something goes wrong. Starting fresh can fix your issues.
Sent from my Atrix XDA Premium App
I've formatted the SD card about 6-8 times nowsince I got my lapdock 3 days ago
teeth_03 said:
I've formatted the SD card about 6-8 times nowsince I got my lapdock 3 days ago
Click to expand...
Click to collapse
Have you tried reflashing the phone yet with new firmwares or ROMS?
Sent from my Atrix XDA Premium App
why would I do that when the issue has something to do with the files on the SD card?
webtop2sd copies the webtop files from the phone, to the SD card,so the files on the phone are basically out of the equation at that point. So its not a problem with android,but with the other linux files from webtop on the SD card
Oh ok. Well have you tried an all new sd card yet?
Sent from my Atrix XDA Premium App
teeth_03 said:
Below,I will list the steps I do to setup my webtop,I am using webtop2sd on a 32GB PNY Class 10 card, and used a 2GB Transcend (not sure on class,im sure its old) card to test with, same results with both pretty much,so I think something im doing is causing it to stop working.
Click to expand...
Click to collapse
yeah......
I think I fixed it. by finding this little piece of info
http://forum.xda-developers.com/showpost.php?p=18465066&postcount=3
I believe tzdata has been my problem for he past like 3 days I've been messing with this
It has been running great for the past day. XFCE4 is a large improvement over the standard webtop.
Of course, I ran into another snag, I need to access windows network shares, and Samba doesn't seem to be functioning, specifically, the samba-common package wont install correctly.
This user was able to fix it:
http://forum.xda-developers.com/showpost.php?p=19132707&postcount=19
But I have no idea how to fix the read/sym links. Can any linux gurus here explain how that is fixed? Thanx guys!
teeth_03 said:
It has been running great for the past day. XFCE4 is a large improvement over the standard webtop.
Of course, I ran into another snag, I need to access windows network shares, and Samba doesn't seem to be functioning, specifically, the samba-common package wont install correctly.
This user was able to fix it:
http://forum.xda-developers.com/showpost.php?p=19132707&postcount=19
Click to expand...
Click to collapse
Yeah his post was kind of light on the details.
What it looks like is that when the /var/lib/dpkg/samba-common.postinst script is run by dpkg --configure -a it calls a program named ucf that in turn wants to run the symbolic link of "readlink" located in /usr/bin.
This is where i got stuck. I am by no means a linux guru.
I tried deleting the symlink to force ucf to use the "readlink" in the path, tried setting the symlink to point to the "readlink" located in /system/bin and in /system/xbin, and set the symlink to the busybox in /system/bin and to the custom busybox webtop2sd uses in /system/etc/webtop2sd but it did not help.
The output of dpkg changed slightly depending on which "readlink" ucf used but still the same error, "readlink: invalid option", and no samba-common.
Btw my busybox is 1.19.3
2.3.5 webtop on sdcard with fixed dependencies
A little help would be appreciated.
I was told on IRC that the actual problem is that the stock kernel does not include CIPs support, which is what is required for connectivity
but I still dont like the fact that samba package is still broken...
I'm using faux123's 0.2.3 kernel though, which might have CIPs support. Its hard to tell from the changelog and features listed in his kernel thread. Btw the 0.2.3 kernel fixes the broken top panel.
I've got the Telstra RHOD110 and I've tried to install every Android build since about the first stable Froyo release. Every single one of them hangs during the Linux boot sequence.
It seems to be memory related, but past that I've got no clue - I'm an IT professional, but I'm in operations, not development so I'm a little out of my depth with this stuff.
I have NOT done HardSPL yet, but I was under the impression this wasn't necessary for the SD card method (which I wanted to test out before potentially bricking a ~$1000 phone). In theory it's just the standard Telstra WinMo 6.5 ROM...
It's getting a bit frustrating after years of trying this and seeing everyone else talking about how easy it is. I'm using F22's rootfs and TotalCommander isn't showing up any *.csv files in the \windows directory, so I can't even try the GBX0C (2.3.7) test build. Anyone know why my phone seems to be different?
Hi Nukkels lets focus on getting GBX0C running since
Nukkels said:
I have NOT done HardSPL yet,
Click to expand...
Click to collapse
First things first: Format the MicroSD you plan to use using the HP USB Disk Storage Format Tool. Just use google to find it. I use version 2.1.8. Perform a FULL format, FAT32.
Now download the package from here: http://files.xdandroid.com/GBX0C_Full_Bundle_2012.04.24.zip and extract all of the files to the root of your SD card
Nukkels said:
I've got the Telstra RHOD110
Click to expand...
Click to collapse
This device is identical to the RHOD100_UK so pull the startup.txt out of the STARTUPS\RHOD\RHOD100\ and place it on the root of your storage card.
Nukkels said:
I'm using F22's rootfs
Click to expand...
Click to collapse
I think I understand why you are trying to use that rootfs since it has some stuff tailor made for Rhod110/Telstra but I don't think it is necessary. Just leave the existing rootfs.img from the GBX0C package, it should work for you.
Nukkels said:
TotalCommander isn't showing up any *.csv files in the \windows directory
Click to expand...
Click to collapse
I haven't used TotalCommander for a while, but it seems to me that there is an option like "Hide Files in ROM" or "Show Hidden Files" or something like that which is probably preventing you from seeing the .csv's in /Windows/. So find that option and find those files and copy them to the root of your storage card.
If you can't find them I think that GBX0C should still boot as I have booted without any .csv's, there was just no sound in the build. But at least you can see that it is working. In case you absolutely cannot find them, here are my .csv's from rhod100uk: View attachment RHOD100_CSV.zip, unzip to your storage card, which hopefully will get you going.
Okay, now all you need is a touch screen calibration file. If you do not have one here is mine:View attachment ts-calibration.zip
Unzip it to the storage card.
Now you have everything in place on the card, please at this point do not try to edit the startup.txt or anything in /conf/. Lets just get this baby working.
Before you run anything I would set WM to airplane mode, set your backlight control to any level but auto (ie low), and make sure that you are not overclocking your processor in WM.
Now run HaRET.exe from the root of the storage card and cross your fingers mate!
Be patient, first boot can take ~10 minutes sometimes.
EDIT: Also there is a fairly good chance that your thread will get moved to the Android section... if it does and you aren't able to post in it anymore you can PM me.
I just wrote up a huge post and lost it all :crying:
Basically I followed your sintructions step by step and it worked!
I'd never done a FULL format before - that takes hours! I'm guessing this might have been the main issue.
I'll play around over the next few days with F22s rootfs and rhod110 startup parameter, Airplane mode turned on, etc to see if any of that had an impact. I never thought to set backlight to manual or use Airplane mode.
Hopefully I can help find the crucial step I missed, so it can be included in the installation instructions (or at the very least someone might stumble on this thread).
Anyway thanks a tonne for your help, it got me up and running!:good:
Thread moved to the appropriate section.
I genuinely hope you didn't pay ~$1000 for this phone... wow.
Caldair said:
Hi Nukkels lets focus on getting GBX0C running since
First things first: Format the MicroSD you plan to use using the HP USB Disk Storage Format Tool. Just use google to find it. I use version 2.1.8. Perform a FULL format, FAT32.
Now download the package from here: http://files.xdandroid.com/GBX0C_Full_Bundle_2012.04.24.zip and extract all of the files to the root of your SD card
This device is identical to the RHOD100_UK so pull the startup.txt out of the STARTUPS\RHOD\RHOD100\ and place it on the root of your storage card.
I think I understand why you are trying to use that rootfs since it has some stuff tailor made for Rhod110/Telstra but I don't think it is necessary. Just leave the existing rootfs.img from the GBX0C package, it should work for you.
I haven't used TotalCommander for a while, but it seems to me that there is an option like "Hide Files in ROM" or "Show Hidden Files" or something like that which is probably preventing you from seeing the .csv's in /Windows/. So find that option and find those files and copy them to the root of your storage card.
If you can't find them I think that GBX0C should still boot as I have booted without any .csv's, there was just no sound in the build. But at least you can see that it is working. In case you absolutely cannot find them, here are my .csv's from rhod100uk: View attachment 1184798, unzip to your storage card, which hopefully will get you going.
Okay, now all you need is a touch screen calibration file. If you do not have one here is mine:View attachment 1184808
Unzip it to the storage card.
Now you have everything in place on the card, please at this point do not try to edit the startup.txt or anything in /conf/. Lets just get this baby working.
Before you run anything I would set WM to airplane mode, set your backlight control to any level but auto (ie low), and make sure that you are not overclocking your processor in WM.
Now run HaRET.exe from the root of the storage card and cross your fingers mate!
Be patient, first boot can take ~10 minutes sometimes.
EDIT: Also there is a fairly good chance that your thread will get moved to the Android section... if it does and you aren't able to post in it anymore you can PM me.
Click to expand...
Click to collapse
I tired this on my TILT 2 it wouldnt work...
tru209 said:
I tired this on my TILT 2 it wouldnt work...
Click to expand...
Click to collapse
So... what's broken with it? Where does it stop?
Edit - basically, you've gotta give us more to go on. We can't help you with "wouldn't work" - it's simply not enough info. Provide as much as you can - what did you try, what happens when it boots, did anything semi-work, etc etc. Details!
tru209 said:
I tired this on my TILT 2 it wouldnt work...
Click to expand...
Click to collapse
Did you bite your tounge just right while dancing backwards to the wizard of OZ soundtrack? That always does it for me when it 'wouldnt work'.
My experience was that the full format using the HP tool is a crucial step. I did a full format using other tools but I had no joy until I did it with the HP tool.
I WANT TO START OFF BY SAYING THAT THIS IS THE FIRST TIME I HAVE MADE A THREAD ON THIS SITE.
I FEEL MY ISSUE IS UNIQUE AND ALL HELP WILL BE MUCH APPRECIATED. THANK YOU
Click to expand...
Click to collapse
The tablet that I am dealing with is a "Cruz Velocity Mini Tablet" running android 2.0 and no means of installing apk's.
Currently this is the situation:
A friend of mine lent me her Chinese reader tablet.
I told her that I could probably flash a newer version of Android on it, thinking that I could finally try my hand at making a ROM because I know for a fact that there aren't many ROMs if any at all out there for a chinese off brand reader like this.
After rooting the tablet I deleted the pre installed bloatware via ADB commands (shell) including a file manager (Astro) that I believe was the only way that you could browse files on the tablet, as well as some other pre installed applications that must have been necessary in retrospect. There is no existing vending capability or market application.
I am looking to make a custom ROM (Using android Kitchen and Cywign) through following this tutorial by lokeshsaini94 yet I feel like following that tutorial won't even get me where I need to be.
Click to expand...
Click to collapse
Things that I have tried at this point include:
Attempting to connect the tablet to my computer with the SD inserted (with and without debugging turned on) [Failed to show up on my computer as a device or anything]
Downloading the APK that I need from a file sharing website [Downloads fail]
Uploading the APK that I need to my Google drive and downloading it from the tablet [Says waiting for data connection and doesn't download even though connected to our WiFi]
Inserting the SD card into my computer, copying the APK I need over to it, then inserting the SD card back into the tablet, going into the browser and typing "File:///sdcard/<name here>.apk" to install an APK but getting an error in the installer after pushing 'install' -> 'Application not installed'
Trying to perform a factory reset; this simply makes the tablet reboot with everything the same as it was before.
Essentially guys and gals, my tablet here is running Android 2.0, I want to update it by making my own rom for it to something at least >4.0, and it seems that I've made things worse and have no way out of this mess. I think I've essentially bricked it even though it still works. :silly:
What do I need to do to make a custom ROM let alone flash/wipe this tablet?
All help will be incredibly valuable
There should be plenty of info here http://www.slatedroid.com/forum/93-velocity-micro-cruz-reader/ to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Still no paddles
es0tericcha0s said:
There should be plenty of info here < > to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Click to expand...
Click to collapse
Thank you very much for your response. It looks like on that website I've already found multiple useful roms!
In fact I already downloaded one and put it onto the SD card. Apparently for these tablets you're supposed to, while powered off, turn it back on by holding the power button and the volume up button but all this seems to do as a whole load of nothing.
I fear that what I've done to it by deleting potentially sensitive programs previously, I have somehow managed to make this process impossible.
Is there some kind of way that I can plug this tablet into my computer and be able to completely wipe it so I can, at the very least, have a functional tablet that will work at all? I've done approximately 5 factory data resets yet the background image that my friend has on the tablet as well as seemingly every single setting and application is remaining untouched..
Try the ones here that also install a custom recovery: http://www.slatedroid.com/topic/33586-a-clockworkmod-rom-compendium-for-the-cruz-reader/
You'll want to make sure and rename the file exactly as mentioned there on the OP. Install instructions are included too. I don't think there is a way to reload via the PC. The right zip should get everything working properly.