Related
ok well i was doing the android install and my girl unplugged my laptop which didnt have the battery so i didnt finish the install and after a day the touchpad died and then i charged and started back up and stuff was missing so i checked system info and out of the 32 gigs there was only 1.6 available...wtf..i need any help available to get those 30+ gigs back thanks
You're gonna have to go see the doctor. Sounds like your partition tables got messed up. Just search there are tons of threads on how to run the WebOS Doctor on the Touchpad.
I have the same problem except mine shows 25gb as max instead of 32gb. I tried wiping it and doctoring it and it still shows 25gb. What else can I do?
Make sure you have the newest files from CM downloaded. You should have a file called ACMEUninstaller. run it by booting your Touchpad while holding down the volume up key till you see the big USB symbol. Open a command prompt in the folder where you installed novacom and places the ACMEInstaller and AMCEUninstaller files and type in "novacom boot mem:// < ACMEUninstaller" you should see a bunch of code on the screen after it reboots your partitions should be reset.
I followed your directions and uninstalled Android, which got me to 27GB, but no where near 32GB. I am trying to wipe it and doctor it again to see if it makes a difference.
27GB is about right. You have to remember that is it 32GB raw once you format it an load an OS on it 27GB is about what you should have.
Oh really? I never knew it took that much memory. Thanks for the help.
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.
So, I actually own an Atrix 2, but I figured I'd post this here as webtop/linux development is much more active. I've gotten my device set up with a custom linux installation, but it seems the OS could run much faster were it not hampered by the phone running its own OS at the same time. Would it be possible to, say, modify the android boot scripts to launch webtop instead if it detects a dock? Just have the phone with a blank screen fully powering the /osh environment on the lapdock. Once undocked, you'd have to manually reboot so the system could actually boot up android again.
It seems like there's no reason why this shouldn't be possible. Just a simple boot script that uses the phone's ability to detect whether or not it is docked; if it is, boot into webtop, if not, run android. Once, my phone had a forced reboot while I was in webtop mode. However, instead of webtop going down with the phone, I opened the mobile view and actually watched the phone's boot animation and boot process, with webtop still running. Maybe there could be a script that runs android until webtop is fully "hooked", then shuts down android and continues running webtop?
Secondary question, is it possible to upgrade the linux install itself with the sudo dist-upgrade command?
I think it is actually quite possible to do this. The reason I say that is because I have seen the Android component of the phone reboot whilst being docked into the Lapdock. The whole Android environment is then reloaded once again meaning that Ubuntu is running as the host OS.
The challenge is if you can get it to boot directly into the Ubuntu shell primarily as opposed to going directly into Dalvik.
bchliu said:
I think it is actually quite possible to do this. The reason I say that is because I have seen the Android component of the phone reboot whilst being docked into the Lapdock. The whole Android environment is then reloaded once again meaning that Ubuntu is running as the host OS.
The challenge is if you can get it to boot directly into the Ubuntu shell primarily as opposed to going directly into Dalvik.
Click to expand...
Click to collapse
That's exactly what happened to me! Te webtop environment stayed booted, but just ran the boot script again. All you'd have to do would be to edit the android boot script to check if RM_IS_DOCKED, right? Or does the webtop rely on certain android components to run?
Secondary question, if I were to go the route of letting it load android, then webtop, then unload android, how would I send a command to android to shut down without *actually* shutting down?
Sent from my ATRIX 2 using Tapatalk 2
I dont know enough about the technical details of the boot scripts to do this. But just as a observation, it does look plausible from the Dalvik rebooting separate to the Jaunty instance I have running.
I would like to know how to do this as well
Sorry guys, this is technically not possible.
At boot, the Linux kernel starts first. It is a custom kernel with Android patches - that implies, as far as I know, some extra security (only users with uid of 3000something have IP access) and something that breaks udev. The latter thing messing up init scripts of most modern Linux distros.
Then the Dalvik VM is started - which is the one that sucks the RAM.
Then the mountosh command is started, which takes care of mounting the webtop partition.
Then ubuntu.sh is started, which takes care of initializing the webtop environment.
The "docked" event launches a script in /etc/init.d (don't remember the name, probably stg like StartWebtop.sh) which starts the Moto's customized Xorg and some other software for the trackpad.
I think that what you have seen rebooting is probably the Dalvik VM - not sure why, I've seen it too at times.
IMHO webtop is slow because the Linux apps in Ubuntu are memory-hungry and not optimized for ARM.
I think Moto was hoping that HTML5 apps would take off sooner - so to make webtop useful just with the bundled firefox - but that never happened.
In the meanwhile, android tablet apps are getting more and more mature, and they are optimized for lower memory and less CPU than Ubuntu apps (eg Quickoffice vs Libreoffice, maildroid vs thunderbird). Hence Moto killing the webtop the way we know it and replacing it with TabletUI ICS.
Sent from my MB860 using xda premium
Interesting thread. I have always been amazed by the Atrix with webtop (only had it for a few days, until I hard bricked it ).
Actually, from what I was able to see, it was not Android as host OS, then running Ubuntu. It was 1 kernel (the Linux kernel for Android, as we always have on an Android phone), and on top of that kernel, two different OSes: "Android" and "Webtop (ubuntu based)". It was especially visible when running ps from one or the other, you could see there was actually no distinction, no isolation between both. From Android you could see all the webtop processes, and from webtop the android processes as well. It was amazing!
(confirmed in https://books.google.nl/books?id=E9...btop a second OS on same linux kernel&f=false, Figure 6.8)
Technically it 's the once and only time I have seen this happen actually. Never before, and never since.
So, yes, it was very possible to "soft reboot" any of the two OSes and keep the other one running, as long as the kernel was kept running (not rebooting the phone). That would mean restarting the Android zigote or Ubuntu/Webtop init (or whatever was doing that function).
Good day guys!
I know this topic (of duel and triple booting) have been handled from a couple of different angles already but I am struggling to find any relating specifically to my issue I am having.
I started with an Acerone (that had 'good' ol' 1.6 preloaded with windows) and reformatted and repartitioned. Windows 7 Pro is installed and running fine. I then installed ICS and that also works great.
Unfortunately I've come across much needed apps that had not been developed to work in ICS or Android-x86 yet so I needed Honeycomb. I've been using 7 and ICS together for a while so I've done quite a bit on it. I then tried following the similar installation procedure for honeycomb (dont install grub, etc) and for some reason I could not get the grub (legacy) from ICS to open the Honeycomb install. I tried all the usual (editing menu.lst using ex2explorer within windows etc etc with all the right hd,xx values etc) but it just kept telling me that it could not find the files.
I thought it may be due to that sda not being mounted at the time grub comes up (which also didnt make too much sense since nowhere did I see it mount the Windows partition but yet I can boot to windows quite fine). So I ended up reinstalling Honeycomb with its own grub (which as you can expect done away with the ICS one). So Honeycomb works great with Windows - but again the same predicament (if not slightly worse since the honeycomb is fresh install and now I cant access my ICS which is wel run in with apps etc).
I can see all the partitions from within windows with the ext2 mounter and both the partitions with droid on have grub folders. I've tried setting different partitions active etc but to no avail. I've even now tried loading GAG bootloader and added the OS's, pointing them to the right partitions, but only the Windows one works from within gag.
My next step (since almost ALL the forums with posts regarding triple boots relates to having android, windows and ubuntu) is to install ubuntu and use ITS grub to control everything. Seems like a simpler way out, but quadruple boot? I've been called indecisive before but this is pushing it! lol.
So basically - either if someone can direct as to whats going wrong and why I can add the entry into the grub legacy's but when I select it, it says files not found.....OR how I can get GAG to successfully access those OS's.
Your site has been a really GREAT help...these my search tems in google include "xda-developers"...
You can quadruple boot. It's really not a big deal. I'm not sure about the grub for android x86 (I've only started playing with it a couple of days back) but if it's grub legacy, it can become a pain to set up other OSes other than the defaults. On the other hand, with grub2 (which comes with all standard linux distros) is very efficient at finding and loading the OSes so that would be the simplest way.
If it reassures you, I triple boot nearly all the time (Currently have Win7, Fedora 17 and Mint 13)
If you don't want to, you can perhaps try GRUB4DOS http://sourceforge.net/projects/grub4dos/
I haven't used it though so you'll need to go through it properly though. I'm sure you already know but just in case: make sure you keep another computer or at least some access to the internet while you are playing with GRUB in case of errors.
Hello,
I'm having an odd issue with Remix OS for PC, and wanted to see if anyone else experienced this and hopefully found a resolution. Please see the bottom of the thread for info on my PC setup. My laptop is definitely more than powerful enough to handle remix, and it used to run fine, but now I seem to have the following issues after not booting into Remix for a while:
***Wifi does not automatically connect, it only connects if I click the wifi icon in the tray (then it connects to my network automatically)
***Nearly all apps will not open, including the Settings app. I'll click on an icon on the desktop, and the icon lights up, registering my click, but the app never opens and the icon stays lit as if something froze. However, I can still "swipe" from the left desktop to the right one, and vice versa.
***When attempting to install an app (Eventually, without any rhyme or reason that I've noticed, I can open the Play Store and maybe the settings app), the app hangs on Installing after it downloads. I've tried waiting a good 20 minutes, but I know the apps install much quicker on this laptop, and I've tried this with small apps.
***Similarly to the above, clicking the Remix OS menu button does nothing as well.
With those symptoms in mind, it seems like there's something holding the system back, but the actual GUI performance is fine. For example, there's no lag or hesitation when an app finally eventually opens or when I click around through the Settings app (when it finally opens). It doesn't seem to only be with graphic intensive apps either, as I tried a simple text/memo app and when that one eventually opens, the desktop background is black and the app window is black with only a menu near the top.
My attempts to fix it
So far, I've tried running an e2fsck -f data.img command to repair the data.img file. It didn't appear to report any issues and the problem did not go away. I've rebooted the thing about a billion times, no luck! Getting into the Settings app is hit or miss and I haven't really had any idea of what setting might help, and installing third party apps appears to not be an option either.
The only other option I could think of would be to backup my data.img and reinstall the OS, and then restore the data.img file, but this seems like it will restore the problem with it. Also, I haven't experienced any problems in Windows, so I don't think there is any issue with the drive. Sorry for such a long thread, just wanted to be detailed!
Any ideas are much appreciated!
My PC: Lenovo Ideapad y510p
Windows OS: Windows 10 64-Bit
Remix OS for PC: 3.0.207 dual booted with the above Windows 10 installation
Hard Drive: 500GB SSD drive
RAM: 16GB
I don't have any of those issues. My issues are a bit different...
I can't seem to find a copy of RemixOS 3.xx that actually has "true" root access. I know there is a method you can use to remount the volume as r/w, but since I am running it from a flash drive, I apparently cannot access any of the system files in Windows with hidden files and folders visible. And, after first boot the USB drive running the OS will somehow end up with a corrupted "REMIXOSDATA" partition.
Good luck on your quest.
ViolentNeurosis said:
I don't have any of those issues. My issues are a bit different...
I can't seem to find a copy of RemixOS 3.xx that actually has "true" root access. I know there is a method you can use to remount the volume as r/w, but since I am running it from a flash drive, I apparently cannot access any of the system files in Windows with hidden files and folders visible. And, after first boot the USB drive running the OS will somehow end up with a corrupted "REMIXOSDATA" partition.
Good luck on your quest.
Click to expand...
Click to collapse
Thank you for the response! In reading the issue you're having, I'm wondering Remix OS for PC, in its current state, is more susceptible to corruption issues in under some circumstances rather than others. When I first installed it, I installed the 64-bit version and I kept having issues where I'd boot it up and it suddenly would not start. I found somewhere on a forum where someone recommended to just use the 32-bit version and the issue went away for a long time, until I had the issue described in my original post. I'm wondering if it just isn't stable enough yet to be run from a flash drive, as it seems to me like it has issues with being easily corrupted.
This brings me to my next comment, I was able to fix my issue! I tried a couple things that didn't work, reinstalling Remix and then choosing YES to erase the entire virtual drive, then copying a backup of my original data.img back into the directory so I don't have to reinstall everything. This didn't fix the issue, so instead I downloaded the 64-bit version and installed it, but this time I chose NO on the prompt to erase my data.
Upon booting into Remix, it gave the standard Android message about optimizing apps and is now running good. I wish I did this workflow with the 32-bit version, as I'm wondering if it would have worked. I suspect I'll experience the same issues I originally experienced with the 64-bit version.
Anyway, I hope this may shed any light on how you can try to resolve your issue. Good luck!