I am by no means an expert, i just dove into this project 4 days ago, and since then, I've had to reformat my SD card about 8 times before I figured out how to get it stable. But now I have it running pretty stable, there are some issues still, but it at least runs linux pretty well. I'm mainly posting this because this would have saved me a lot of digging 4 days ago, and I figured I would help out any n00bs that just got a lapdock and just started playing with webtop.
*Disclaimer* I am not an expert, if you have a problem with any of these steps, please do not post them here, but in their respective threads. I take no credit for developing any of this, im just posting a list of steps from multiple sources. Also, if you break something, its not my fault*
The Guide
By the end of this guide, you will have a more functional linux as your webtop, with the XFCE4 interface. This uses webtop2sd, so if you break anything, you should be able to start over.
You will need a rooted Atrix, a lapdock (or other external device for using webtop on), and a microSD card, I suggest 2GB or bigger. I have a 32GB PNY class 10 card, for example.
1. Lets format/partition the SD card. Sogarth explains here how to do that. I highly suggest NOT doing this on your phone,and use a PC instead.
http://forum.xda-developers.com/showpost.php?p=15109152&postcount=5
2. Here, he explains how to install it after you partition your SD card. The app you need is in the bottom of the first post.
http://forum.xda-developers.com/showpost.php?p=15109140&postcount=4
3. Now plug it in to your lapdock, and it should boot up into the new webtop. You should see 2 icons in the middle, the awn-dock config tool, and the webtop config tool. We just need to focus on the latter one. Open that up, click on Administration on the left,and click on Install by lxterminal. Try clicking on the terminal icon on the dock, if it comes up, you are gold. If it acts funky, like your screen goes black but doesn't open the terminal, open up the webtop config tool again, and the button to install it should be lit up again. You know its installed if you click install,close out the config tool, and reopen it to see Install grayed out.
4. If all goes well, you should be at a terminal. The first thing we want to do, is fix a really annoying and OS breaking bug, regarding the tzdata package. It seems to be corrupted, so we want to make sure it doesn't get in the way of installing other packages. This issue was the bane of my existence for 3 days.
following these steps, we will fix it
http://forum.xda-developers.com/showpost.php?p=18465066&postcount=3
type this into the terminal to bring up the said file so you can edit it
Code:
sudo leafpad /var/lib/dpkg/info/tzdata.postinst
then put exit 0 on the 3rd empty line
I would reboot your phone after doing this, just for good measure
5. When you get back into the webtop, lets run the Webtop Scripts, the files and instructions are here for that. This will fix many broken dependencies. Arvati did a great job with these fixes!
http://forum.xda-developers.com/showthread.php?t=1192488
just put that file in your downloads folder, then run the commands from that first code box, and I just said yes everytime it asked you what you wanted to do. I would reboot your phone again after this.
6. Now lets start installing stuff! Lets start with synaptic, which works a lot better if you install via command line instead of the webtop config tool.
So run this from the terminal:
Code:
sudo aptitude install synaptic
7. Open up synaptic by typing 'sudo synaptic' into the terminal. Lets install XFCE4 now, just search for that there,and install the XFCE4 package, it should install all of the other required packages to run the new interface.
8. Once it is installed,we need to disable the webtop interface,and enable xfce4. I referenced this thread to do that:
http://forum.xda-developers.com/showthread.php?t=1054213
Type this into the terminal to edit the right file
Code:
sudo leafpad /osh/usr/local/bin/start-oshwt-2.sh
put a # in front of
sfalv -i "awm-autostart"
sfalv -i "webtop-wallpaper"
so it looks like
#sfalv -i "awm-autostart"
#sfalv -i "webtop-wallpaper"
then add these 2 lines
sfalv -i "xfce4-session"
sfalv -i "xfce4-panel"
save it then reboot your phone. Hopefully you should be in XFCE4 now!
OPTIONAL:
*To fix an issue with mounting USB storage devices:
I had the same problem, got it to work by adding this to /etc/PolicyKit/PolicyKit.conf
Code:
<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<match user="myaccountnamehere">
<return result="yes"/>
</match>
</match>
</config>
Click to expand...
Click to collapse
http://www.linuxquestions.org/quest...b-storages-debian-squeeze-723251/#post3537149
* To Fix mounting Windows network shares
Chimpdaddy has posted a way to get Samba file shares to work, this requires having a custom kernel though:
http://forum.xda-developers.com/showpost.php?p=22018703&postcount=67
Chimpdaddy said:
Firstly you need to have a kernal, like Faux's, that supports CIFS.
Then install Samba4, via synaptic package manager if you like.
Probably an idea to reboot.
Then create a folder (using terminal) where you want yr share, 'sudo mkdir /media/SHARE' for eg..
then run this;
sudo mount -t cifs -o username=guest //YOURSHAREIP/SHARE /media/SHARE
if you get no errors yr golden
If you want it to mount on startup edit /etc/fstab to include
//YOURSHAREIP/SHARE /media/SHARE cifs username=guest,_netdev 0 0
check this with 'mount -a'
That should do you.
Click to expand...
Click to collapse
OR
You could use an app like ESFileExplorer on your phone to drag and drop files, this is what I have been using,and it works pretty well for both direct windows shares and FTP. The Mobile View is great for having a window open for secondary tasks like this.
EXPERIMENTAL:
This can be buggy,so use at your own risk!
To install chromium browser, follow these steps. This is said to have better performance than the built in firefox, but for me, it crashed a lot, I went back to firefox
http://forum.xda-developers.com/showthread.php?t=1374567
ISSUES STILL PENDING:
*currently no major issues*
LIST OF SUGGESTED APPS:
OpenOffice.org
Qalculator
XChat IRC
This looks good. I just got my lapdock on Thursday and I have been putting togther all of the Docs to get it the way I want, but this is pretty much the results I wanted. I will try your instructions and get back with you.
Thanks.
Which ROM are you running on?
stock ROM.....
Thanks for the guide.
There is one link that appears to be broken though,
On step 5, the thread goes nowhere. That's where I'm stuck right now
my bad,fixed
i actually managed to do all this on my own, but just recently came into a unexpected problem. i'm kind of a linux noob, and it seems like the file manager button on xfce4-panel doesn't lead to the stock file manager i was using before (doesn't lead to anything), does anyone have any suggestions for a good file manager to replace it with?
Thanks for the fix, I've completed all steps and it was working for about an hour. Until I installed chromium.
I have a weird problem where the lapdock doesn't detect webtop and says no hdmi input detected. Not sure if you know anything about that, but just wanted to let you guys know (might be a defect on my lapdock). I'm trying to figure out a fix for that now.
I would suggest starting over if that happened,sounds like something broke
as for an XFCE4 file manager, it should install Thunar by default
teeth_03 said:
I would suggest starting over if that happened,sounds like something broke
as for an XFCE4 file manager, it should install Thunar by default
Click to expand...
Click to collapse
sudo apt-get thunar fixed the problem for me, thanks though
followed your steps and it works great ,i've been messing with this for over a week trying to get this to work ,that ztdata bug fix did the job.. THANK YOU.....
toe451 said:
followed your steps and it works great ,i've been messing with this for over a week trying to get this to work ,that ztdata bug fix did the job.. THANK YOU.....
Click to expand...
Click to collapse
dont thank me, thank the guy who figured out how to fix it
webtop2sd app crashes on first run...any ideas?
Here's the answer
http://forum.xda-developers.com/showpost.php?p=19993891&postcount=671
bigworm50 said:
webtop2sd app crashes on first run...any ideas?
Click to expand...
Click to collapse
To the point of installing XFCE4, and synaptic just sits on preparing packages forever... I let it sit for 30+ minutes last night and going on almost 60 minutes currently...is something wrong or does it take that long?
you might want to cancel that, reboot your phone and try again, it should not take that long
can you do one on how to install Chrome instead of Firefox for a noob like myself. Thank you.
there is already a link to the chromium browser thread in the OT
I would caution that its kind of experimental, I installed it and it kept on crashing for me, so when I re-did my webtop after that,I just decided to use firefox
For step 1, can we partition this as ext4 as faux kernels support it?
added info on fixing an issue with mounting USB drives, and a note about chrome
Hi all XDA members,
I have been installing the Ubuntu Phone daily updates since it started but today I got a message that I have never got before:
Device detected as grouper
Storage requirements in /data satisfied
Download set to http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current
Starting new HTTP connection (1): cdimage.ubuntu.com
--Jenkins data format has changed, incompatible--
The Jenkins bit is new to me. I am unsure how to proceed updating to the new release. Has anyone else installed the daily update today and/or knows why this error may occur and how to get it to update??
Any help appreciated as I want to continue my development on the latest install.
I will manually try and download the files and see if that helps, I will post the result once I know whether it works or not
Okay, it works when you download the images from the repo and save them in a folder.
Then open a Terminal and type:
sudo phablet-flash -b -p='/home/elvito/Downloads/phablet' -> replace path to the folder the images are stored in.
The above will do a full bootstrap however if you dont want this just remove the -b bit of the above.
I have notice tho that this error is not fixed by doing this but it helps you to install the latest image. Maybe Ubuntu are updating the repo and thats why this error comes... Fashing to the original 95 still works so I think its something that will sort itself out.
elgunvo said:
Okay, it works when you download the images from the repo and save them in a folder.
Then open a Terminal and type:
sudo phablet-flash -b -p='/home/elvito/Downloads/phablet' -> replace path to the folder the images are stored in.
The above will do a full bootstrap however if you dont want this just remove the -b bit of the above.
I have notice tho that this error is not fixed by doing this but it helps you to install the latest image. Maybe Ubuntu are updating the repo and thats why this error comes... Fashing to the original 95 still works so I think its something that will sort itself out.
Click to expand...
Click to collapse
This will fix the error locally:
https://bugs.launchpad.net/phablet-tools/+bug/1154595
You need to be super user to edit the file though.
sudo gedit /usr/bin/phablet-flash
You can probably also just wait for them to update phablet-tools with the fix.
Thanks for the info. At least it is a bug and nothing I did to corrupt my Ubuntu installation
Im building cyanogenmod 11 for the htc dna, this is my first attemt into building my own rom however I seemed unable to get a bootable zip until now.
I captured a screen.log to scan for any errors later (NO clue what im looking for in here)
So I searched the log for "waiting for unfinished jobs" because this is always what seems to happen to me and this time i was ready to find the errors. Well lucky for me every job finished so what I am wondering is does this mean that my build compiled correctly even though i have warnings like crazy in the 140000+ lines of the screen.log
as for the second question. Is there any easier eay to scan a screen.log for where the build errors are or do i just have to run through all the line blind because im not exactly sure what to look for yet (one day i plane to have more of an understanding this is just early in my rom building career.)
EDIT~!~!~!~!~!~!~
Okay new problem. When i originally synced my repo to cm11 i was on python 2.7.4 and thats how i tried the first build on this ubuntu and it failed. I updated to python 2.7.6 because every time i grabbed 2.7.5 i kept getting unsuspected End Of File errors. So I installed 2.7.6 with (sudo make install) instead of (sudo make altinstall) like some guides read (This is because when i used altinstall brunch always gets to waiting for unfinished jobs.)
What i was getting at was now that im on python 2.7.6 when i try to initialize another repo to another folder I receive this error.
fatal: Cannot get https://gerrit.googlesource.com/git-repo/clone.bundle
fatal: error unknown url type: https
Click to expand...
Click to collapse
However I can repo sync my cm11 repo still just can not initialize a new repo to another directory
Any help is appreciated
hipsh0t said:
Im building cyanogenmod 11 for the htc dna, this is my first attemt into building my own rom however I seemed unable to get a bootable zip until now.
I captured a screen.log to scan for any errors later (NO clue what im looking for in here)
So I searched the log for "waiting for unfinished jobs" because this is always what seems to happen to me and this time i was ready to find the errors. Well lucky for me every job finished so what I am wondering is does this mean that my build compiled correctly even though i have warnings like crazy in the 140000+ lines of the screen.log
as for the second question. Is there any easier eay to scan a screen.log for where the build errors are or do i just have to run through all the line blind because im not exactly sure what to look for yet (one day i plane to have more of an understanding this is just early in my rom building career.)
Click to expand...
Click to collapse
There are a ton of warnings, one error (failing to build modules, which you can ignore). The last thing printed is the path to the zip. If it printed that, the build completed successfully.
To find the errors, try searching from the end for Error (capital E).
@crpalmer
Yea I just found the zip its booting as we speak.
Thanks
So excited this is finally working I been messing with Ubuntu for like 2 weeks
hipsh0t said:
Okay new problem. When i originally synced my repo to cm11 i was on python 2.7.4 and thats how i tried the first build on this ubuntu and it failed. I updated to python 2.7.6 because every time i grabbed 2.7.5 i kept getting unsuspected End Of File errors. So I installed 2.7.6 with (sudo make install) instead of (sudo make altinstall) like some guides read (This is because when i used altinstall brunch always gets to waiting for unfinished jobs.)
What i was getting at was now that im on python 2.7.6 when i try to initialize another repo to another folder I receive this error.
However I can repo sync my cm11 repo still just can not initialize a new repo to another directory
Click to expand...
Click to collapse
I'm not expert so crpalmer or someone may be able to tell you more directly. But here is a few things:
Did you install SSL for python?
Code:
$ sudo apt-get install libssl1.0.0=1.0.1-4ubuntu5.3
$ sudo apt-get install libssl-dev
Try reinstalling Python. I installed it the simple way and its working fine for my builds.
Code:
$ sudo apt-get install python
What repo were you trying to initialize?
tes4p00ner said:
I'm not expert so crpalmer or someone may be able to tell you more directly. But here is a few things:
Did you install SSL for python?
Code:
$ sudo apt-get install libssl1.0.0=1.0.1-4ubuntu5.3
$ sudo apt-get install libssl-dev
Try reinstalling Python. I installed it the simple way and its working fine for my builds.
Code:
$ sudo apt-get install python
What repo were you trying to initialize?
Click to expand...
Click to collapse
It was every repo and I tried the normal way I must have started from a fresh Ubuntu install once every few days figuring out where I went wrong. I'm going to check on the ssl for Python. So far this is the furthest I've made it. One built cm11 rom and I'm only learning more every day I research
EDIT------------
[email protected]:~$ sudo apt-get install libssl1.0.0=1.0.1-4ubuntu5.3
[sudo] password for jk:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '1.0.1-4ubuntu5.3' for 'libssl1.0.0' was not found
Click to expand...
Click to collapse
Im trying to make sure my precise repos are in place for apt-get however im still getting this message.
okay so trying to build from source FFOS for the ZTE Open C and keep getting the same error even tried switching Ubuntu Distro to 14.04.1 from 14.10 tried google and didnt come up with much of anything on the subject short of many people experiance this issue it seems but nobody gets it resolved and if they do they dont post on how they did it
Pulling "trace_util"
cp: cannot stat ‘../../../backup-flame/system/bin/trace_util’: No such file or directory
Failed to pull trace_util. Giving up.
> Build failed! <
above is the error i get any help is appreciated
Franzferdinan51 said:
okay so trying to build from source FFOS for the ZTE Open C and keep getting the same error even tried switching Ubuntu Distro to 14.04.1 from 14.10 tried google and didnt come up with much of anything on the subject short of many people experiance this issue it seems but nobody gets it resolved and if they do they dont post on how they did it
Pulling "trace_util"
cp: cannot stat ‘../../../backup-flame/system/bin/trace_util’: No such file or directory
Failed to pull trace_util. Giving up.
> Build failed! <
above is the error i get any help is appreciated
Click to expand...
Click to collapse
Follow up to this ive did a little searching my self and included in the init.target.rc is a NFC area that seems to be the "Root" of the problem but unfortunatly thats all the information ive come across so please anyone that has information how to bypass this error or fix it , i whould be very greatful
fixxed but still issues
Franzferdinan51 said:
Follow up to this ive did a little searching my self and included in the init.target.rc is a NFC area that seems to be the "Root" of the problem but unfortunatly thats all the information ive come across so please anyone that has information how to bypass this error or fix it , i whould be very greatful
Click to expand...
Click to collapse
okay so for those of you who ever run into this issue this is how to bypass unforunatly after flashing i still run into errors on ./flash.sh fails to erase userdata but well start from the top and leave that for others since im almost positive that error is due to me not doing something correct
okay so basically its pretty simple go too the link and copy openc.xml at the link below and attached for easy access
https://bugzilla.mozilla.org/attachment.cgi?id=8429932
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C
then follow the directions listed but to keep it simple for those of you whom dont want to look to far
Clean up the B2G directory, removing the unneeded directories:
rm -rf objdir-gecko/ out/ backup-flame/
Now configure Firefox OS with the following command: (Note that the path cannot contain spaces, otherwise it won't work).
./config.sh flame /PATH/TO/openc.xml
You can then build the Gecko component and Flash it to your phone using the following:
./build.sh gecko
./flash.sh gecko
You should now upgrade Gaia as well, so the upgraded version of Gecko works with the version of Gaia on the device:
cd gaia
make reset-gaia
and thats how i fixxed it unfortunatly like i said when i got to ./flash.sh the whole build it fails at user data
but once again pretty sure thats only me if anyone has information on this let me know please
all credit from this goes to mozilla i just decided to post it in an easy location for everyone who runs into this
thank you mozilla developers
I've been using CM12.1 for couple of months, love it. Found some bugs and waited a few nightlies (few weeks per "nightly") and after that tried to make a bug report.... not accepted, because CM12.1 is not developed anymore. CM13 is not available for Z2, so I tried to build CM13 myself, following the guide found on cyanogenmod site. Sorry, as a new member, can't link that URL here... It fails... I have gone past that point to extract the proprietary "blobs" from my phone (running the mentioned CM12.1) and tried again the breakfast sirius command. I'm unable to paste results here, because being a new member... look the result from pastebin com with /mwBfxHEL behind the URL...
The reason seems obvious, missing that msm8974-common-vendor.mk file. Can't find it on my computer using "locate". Can't find it using google. Don't know how to fix this or get past this... Any help appreciated!
Nobody has build CM13 for Z2???
The issue you are describing likely results from the blob extraction for msm8974-common not operating correcty: Please execute (or re-execute) the extraction scrip in this folder of the device tree as well (should be device/sony/msm8974-common). Could you paste the output after running that script, please?
Diewi said:
The issue you are describing likely results from the blob extraction for msm8974-common not operating correcty: Please execute (or re-execute) the extraction scrip in this folder of the device tree as well (should be device/sony/msm8974-common). Could you paste the output after running that script, please?
Click to expand...
Click to collapse
OK, that advice helped. Tried 'breakfast sirius' again, it went longer, complained about something missing in shinano-common folder. Used your approach again and got past that one too. After that, 'breakfast sirius' succeeded. I tried 'brunch sirius' and it failed. Tried it again, it got longer before failing again... did "while [ $? -ne 0 ]; do !! done" to try building until it succeeds. After quite a while, I stopped it, ran brunch sirius command and copied the output to pastebin.
Take a look at pastebin.com/Qz4hq1aZ
Something about libta.so?
Flexy75 said:
OK, that advice helped. Tried 'breakfast sirius' again, it went longer, complained about something missing in shinano-common folder. Used your approach again and got past that one too. After that, 'breakfast sirius' succeeded. I tried 'brunch sirius' and it failed. Tried it again, it got longer before failing again... did "while [ $? -ne 0 ]; do !! done" to try building until it succeeds. After quite a while, I stopped it, ran brunch sirius command and copied the output to pastebin.
Take a look at pastebin.com/Qz4hq1aZ
Something about libta.so?
Click to expand...
Click to collapse
Should I extract the blobs from a Z2 with OEM firmware? I vaguely remember that TA refers to something to do with DRMs that you lose when you unlock the phone to be able to install other firmwares...
Sorry for the delay.
This is an issue with the vendor files. I think that th extrction scripts are somewhat outdated, or didn't the extraction script didn't find some files. There should be a repo on github which should provide you with the needed files. Another possibility would be to extract and mount the system image of a stock and let the script process these files (there is a cmdline switch for pointing the script to it: please have a look into this script for the according switch).
Hope this helps.
Diewi said:
Sorry for the delay.
This is an issue with the vendor files. I think that th extrction scripts are somewhat outdated, or didn't the extraction script didn't find some files. There should be a repo on github which should provide you with the needed files. Another possibility would be to extract and mount the system image of a stock and let the script process these files (there is a cmdline switch for pointing the script to it: please have a look into this script for the according switch).
Hope this helps.
Click to expand...
Click to collapse
OK, found the repo. Got all the files, got the build to succeed! Thank you very much! Just few more questions... There is not just one zip file in the directory... which one to install? How do I install the zip file the build created? Perhaps via booting to recovery and installing it from there? And how does it behave? Like a upgrade, or a clean install?