Develop Bugs

[UPDATE 18.12.10] Shared Homebrew projects

let me start a thread where you all can drop your shared homebrew app's.
For homebrew app's we first need to unlock:
iridium21 said:
As people may know, Chevron have removed their unlocker download for WP7 so I thought I'd archive it and make it available for everyone here still:
http://www.megaupload.com/?d=Q1T7WQMK
EDIT: Thanks to Cendaryn we also have the required security certificate - the easiest way (thanks to Talys) to install the cert and unlock your WP7 is to do as follows:
1. Unzip file, and attach chevronwp7.cer (see below for file) to an e-mail to yourself
2. Open email in WP7
3. Tap attachment once, turns it into a shield, tap it again, goes to install certificate screen with white letters on black screen
4. Click install at the bottom
5. Make sure registry is modified:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsPhone\ProxyPorts]“DeviceReg”=dword:000069C5
I think the WP7 developer tools from MS does this, but you can add it in manually (it's a 32bit DWORD)
6. Plug in phone and leave Zune running
7. Run chevronwp7.exe, click both checkboxes
8. Click unlock
Excellent video tutorial here thanks to Jaxbot
[Edit 8th Dec 2010]
Worried that Microsoft has relocked your phone? They haven't, look here
Hope this helps someone.
Click to expand...
Click to collapse
Or unlock using a modded version by hounsell .
hounsell said:
Been able to remove the sideload limit, I was able to install 11 apps by my count, though I'd appreciate a third-party confirmation to be honest.
http://thounsell.co.uk/2010/12/chevronwp7-now-without-the-sideload-limit/
Click to expand...
Click to collapse
After unlocking we want some custom ringtones ofcourse:
ShadowLegion said:
I didnt see a thread so i just thought i would let people who did already know that ChevronWP7 released their Custom Ringtone Manager Today
you can Find It Here http://www.chevronwp7.com/
download: http://walshie.me/ChevronWP7.RingtoneInstaller.zip
Source code:http://blog.walshie.me/2010/12/source-code-to-the-chevronwp7-ringtone-editor/
Click to expand...
Click to collapse
Lets look at the file system:
hounsell said:
FileBrowser
Source
Still very basic, not the most stable either, but at least you can browse the Windows folder, and read text files.
I'll probably put more effort in once I've got further with my SevenIRC App.
Click to expand...
Click to collapse
We need a .reg viewer to:
(nico) said:
I've managed to create a basic Registry Viewer, readonly for the moment.
For now, I didn't manage to get access to root path, so the first 2 levels are hardcoded.
Download it here: (link removed, see below)
Edit:
Updated version here: http://bit.ly/ed1Sz1
and a direct link:http://www.xda-developers.ch/download/?a=d&i=4227279264
Click to expand...
Click to collapse
And to get this all on the phone a nice way:
tom_codon said:
Hi all !
For all devices unlocked with ChevronWP7 Unlocker , we're can easy install custom ringtones or applications .XAP format via Application Deployment , but everytimes need open start menu --> Application Deployment then browser .xap to tool for install take too much times and almost make some in us crazy
That why i decided to write Tom XAP installer , basicly Tom XAP installer and Application Deployment are the same ( Alow install custom .xap to device and emulator windows phone 7 ) But Tom XAP installer a lot convenience , it's alow you install .xap with double click to file or simple just right click --> install xap
How to :
Download exe and put it somewhere in PC, run it , it will automatic add registry path of application and add menu , icon to .XAP files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then just close it and now double click to custom ringtones , or any .xap format files , the Tom XAP installer will automatic open and give you some details ( App name , Version , Author , Size , Description of XAP ) then select where you will install xap ( device or emulator )
Press Install and wait it finish.
Notices :
1. Tom XAP installer Requires .NET 4.0 Framework and Windows Phone 7 SDK
2. If you install xap to device
- Please make sure your device was unlocked with ChevronWP7 Unlocker ( Here is guide how to unlock )
- Make sure your device was connected with PC and Zune lauched
- Make sure your device not in sleep mode
3. If you move Tom XAP installer.exe to other location in PC , you should run it again one time for registry again location of application
4. If you don't like this software , just run Tom XAP installer.exe and uncheck " Enable Tom XAP installer" it will uninstall all registry of Tom XAP installer in your PC
Download: http://forum.xda-developers.com/attachment.php?attachmentid=456249&d=1291493842
Cheers !
Tom
Click to expand...
Click to collapse
Man I need a webserver on my phone.
davux said:
I've extended jmorrill's code to include the Winsock functions to listen. The example proves that one may listen on port 80.
One problem with this library right now is that it is IPv4 only. I tried to make things generic but that was quite hard, I'm also really not very familiar with native Winsock anyway.
dl.dropbox.com/u/12359/PhoneNetworkingSample_with_listen.zip
[edit] and here's a really simple (and really hacked together - you've been warned) webserver!
dl.dropbox.com/u/12359/wp7_webserver.zip
The code is definitely *preview quality* - I pulled it together just now because I don't think I'll be able to work on this for a few days, so it'd be a starting point but I'm sure it's buggy.
Click to expand...
Click to collapse
davux said:
I've enhanced my Webserver sample to support reading from the device (where allowed), as well as reading/writing IsolatedStorage
//dl.dropbox.com/u/12359/WP7Homebrew_Webserver.zip
The XAP is located in the Webserver project.
I am not finished, there are several issues:
- I have not implemented support for getting the local endpoint, so you need to know your phones IP address
- There is a bug somewhere that causes a problem when uploading larger files.
- There is no UI
- No authentication!
To access the webserver, open the app on your phone (it will disable the idle timer and run behind the lock screen)
//phone_ip/IsolatedStorage
//phone_ip/Windows
IsolatedStorage is a special case (virtual directory that uses the SDK IsolatedStore APIs), the filesystem is mounted at the root of the webserver. Note that if you navigate to //phone_ip/, you will not see anything, as we are not able to list the contents of the root directory.
I am working to create a real socket library that mimics System.Net/.Sockets, and System.IO for file access. TcpClient and TcpListener are in a mostly functional state already.
I'll add in registry and other capabilities once those two components are stable.
Most of the code came from jmorrill.
Click to expand...
Click to collapse

I'm thinking we could do with somewhere to place an open-source collection of homebrew apps.
Also, with the Chevron WP7 unlocker, you might want to include the version with the sideload limit removed

hounsell said:
I'm thinking we could do with somewhere to place an open-source collection of homebrew apps.
Also, with the Chevron WP7 unlocker, you might want to include the version with the sideload limit removed
Click to expand...
Click to collapse
good idea do you have some ideas
can you gif me the link of the unlocker you modded ?

The regviewer zip file contained projects not possible to open in VS2008 or VS2010. Could you check this?

ajhvdb said:
The regviewer zip file contained projects not possible to open in VS2008 or VS2010. Could you check this?
Click to expand...
Click to collapse
I will ask the maker of the regviewer.

What to you mean by not possible ?
The source contains multiple project:
- COM: Visual Studio 2008 C++ project using Windows Mobile 6 SDK
- Native : Visual Studio 2010 Solution containing the .Net / COM interface
- Registry Viewer: Visual studio 2010 Project containing the registry viewer app and also referencing Native project.
Everything works on my machine. You may need to fixe path to make it works on yours.

(nico) said:
What to you mean by not possible ?
The source contains multiple project:
- COM: Visual Studio 2008 C++ project using Windows Mobile 6 SDK
- Native : Visual Studio 2010 Solution containing the .Net / COM interface
- Registry Viewer: Visual studio 2010 Project containing the registry viewer app and also referencing Native project.
Everything works on my machine. You may need to fixe path to make it works on yours.
Click to expand...
Click to collapse
Sorry, most of the time when i rebuild a project all files are relative to the project, the references are not of course and i need to set the correct path. Could you give me a hint?
I download the 002 file. In this there is a native.zip. I unzipped it and got 2 folders:
1. COM
Renamed it to COM2008 and opened this in VS2008, did a rebuild. below is the output.
1>Compiling resources...
1>Microsoft (R) Windows (R) Resource Compiler Version 6.1.6723.1
1>Copyright (C) Microsoft Corporation. All rights reserved.
1>Linking...
1> Creating library Windows Mobile 6 Professional SDK (ARMV4I)\Release/Native.lib and object Windows Mobile 6 Professional SDK (ARMV4I)\Release/Native.exp
1>Performing Post-Build Event...
1> 1 file(s) copied.
1>The system cannot find the path specified.
1> 0 file(s) copied.
1>The system cannot find the path specified.
1> 0 file(s) copied.
1>The system cannot find the path specified.
1> 0 file(s) copied.
1>Project : error PRJ0019: A tool returned an error code from "Performing Post-Build Event..."
1>Build log was saved at "file://e:\_PROJECT\WP7\_Source\_Homebrew\RegistryViewer002\Native\Native\COM2008\Native\Windows Mobile 6 Professional SDK (ARMV4I)\Release\BuildLog.htm"
1>Native - 1 error(s), 0 warning(s)
Im not sure where to find this "path".
2. Nativelibrary

In the post build event of the COM project, I copy the output file to several projects of mine. Just remove post build events and copy the file manually to your own project.

(nico) said:
In the post build event of the COM project, I copy the output file to several projects of mine. Just remove post build events and copy the file manually to your own project.
Click to expand...
Click to collapse
Yup, it's working now.
In the registry viewer I only needed to change the project folder to the nativelibrary.

ceesheim, thanks..excellent

Updated the first post with a newer/better webserver

[TOOL] [14th Dec] | AIOlog - All in One Android Logger v0.5

AIOlog - All in One Android Logger​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
Display and output Logcat
Last_kmsg
Dmesg
Kmsg
Kernel Version
Click to expand...
Click to collapse
Latest Version:
1. AIOlog for Windows: http://aiolog.googlecode.com/files/aiolog_win_v0.5.zip
2. AIOlog for Linux 32bit: http://aiolog.googlecode.com/files/aiolog_linux_32_v0.5.tar
3. AIOlog for Linux 64bit: http://aiolog.googlecode.com/files/aiolog_linux_64_v0.5.tar
4. AIOlog for Mac 32bit: http://aiolog.googlecode.com/files/aiolog_mac_32_v0.5.tar
5. AIOlog for Mac 64bit: http://aiolog.googlecode.com/files/aiolog_mac_64_v0.5.tar
Click to expand...
Click to collapse
NOTE: If you have this error "Cannot execute binary files" while using the AIOlog for linux, please download the 32bit version.
If you've downloaded the AIOlog v0.3 generic, please use the following file:
Either the aiolog_32bit or aiolog_generic_32bit
If this is your first time doing a log, you may need this file(Windows only):
http://code.google.com/p/aiolog/downloads/detail?name=aiolog_adb_fastboot_win_v0.1.zip
New features:
Added log push to phone and phone directory creation(log will be available at the computer, and the .aiolog, aiolog and root folder of your phone)
Added log archiving(unix)
Added log cid version
Added ADB files for Windows
Fixed a bug to auto detect device id when there is only one device
Click to expand...
Click to collapse
Full Changelog: https://github.com/wcypierre/AIOlog/commits/master​
Hi, I'm now in the look for users who can provide me with some data(non-private and non-confidential ones) in order to improve AIOlog as a big amount of data is needed for AIOlog in order to success.
If you're interested, please pm me and state your device name or you can email me via [email protected]
Basic Howto:
1. At your phone, go to Settings -> Developer Options
2. Tick the "Android Debugging"
3. Connect your phone to your computer(desktop/laptop)
Windows:
1. Navigate to the location where the aiolog is located
2. Extract it and place it to a folder
3. Open aiolog.exe by clicking at it
4. The menu will appear
5. Just enter the number(1,2,3 ...) of the function that you wanted to do
Linux:
NOTE: For AIOlog version 0.4 onwards, the binary file is called either aiolog_32bit or aiolog_64bit so please change it accordingly (The steps for the filename is used in Step #3)
1. Open your terminal
2. Navigate to where aiolog is located. Example, "cd ~/Downloads/" (Assuming that the file is saved at Downloads folder)
3. Type "./aiolog" and press enter
4. The menu will appear
5. Just enter the number(1,2,3 ...) of the function that you wanted to do
Click to expand...
Click to collapse
Advanced Howto:
1. At your phone, go to Settings -> Developer Options
2. Tick the "Android Debugging"
3. Connect your phone to your computer(desktop/laptop)
Windows:
1. Open the cmd
2. Navigate to the folder where aiolog is located
3. Type "aiolog -h" and press enter
4. Search for the functions that you wanted to do and type its command(refer to the examples below)
Examples:
1. To log all logs, type "aiolog.exe -a"
2. To get the logcat, type "aiolog.exe -l"
3. To get the last_kmsg, type "aiolog.exe -lk"
4. To specify a device that is to be used(use it when you have a lot of devices connected) and to get a dmesg, "aiolog.exe -id SH<yourdeviceid> -d"
Linux:
1. Open your terminal
2. Navigate to where aiolog is located. Example, "cd ~/Downloads/" (Assuming that the file is saved at Downloads folder)
3. Type "./aiolog -h" and press enter
4. Search for the functions that you wanted to do and type its command(refer to the examples below).
Examples:
1. To log all logs, type "aiolog.exe -a"
2. To get the logcat, type "./aiolog -l"
3. To get the last_kmsg, type "./aiolog -lk"
4. To specify a device that is to be used(use it when you have a lot of devices connected) and to get a dmesg, "./aiolog -id SH<yourdeviceid> -d"
Click to expand...
Click to collapse
Compatibility:
1. Full support on Windows
2. Partial support on Linux
3. Partial support on Mac(Version 0.5 onwards)
Issues:
1. May not work on mac yet(but it should be).
2. AIOlog will not work if the adb is not started for a 30 seconds to 1 minute in advance
Found a bug?
1. Go to here: http://code.google.com/p/aiolog/issues/list
2. Click New issue
3. Fill in the details
4. Report
5. Wait for it to be resolved :good:
Changelog:
Version 0.4
1. Added Auto Device Id detection
2. Logging support when there are more than 2 devices connected
3. Added logcat clear and dmesg clear
Version 0.3
1. Added logcat radio(to debug for radio issues)
2. Added log essential(logcat, dmesg, kmsg and last_kmsg)
3. Disable reprompt of device id after it has been entered
4. Misc Fixes
Version 0.2
1. Logcat, kmsg continuous(the normal logcat, kmsg way instead of log, stop and save method) added
2. Added additional checking on device id
3. Removed debug code
Version 0.1
1. Core functions(logcat, last_kmsg, dmesg, last_kmsg) implemented
2. Outputs the log to the current directory of AIOlog
3. kernel version output is implemented
Click to expand...
Click to collapse
To do list:
1. To archive the logs into an archive(zip, rar, tar)
2. To include mac support
3. To include log essential (Done )
4. To log other details
5. Fix any existing bugs

Building from Source
Prerequisite:
- Command Line Git(be it from any OS)
Instructions:
To clone the AIOlog(one time process):
git clone git://github.com/wcypierre/AIOlog.git
To update the existing AIOlog:
git remote update
git rebase origin/master
g++ main.cpp log.cpp -o aiolog.exe (for windows) / g++ main.cpp log.cpp -o aiolog (for mac/linux)

Building from Source
Prerequisite:
- Command Line Git(be it from any OS)
Instructions:
To clone the AIOlog(one time process):
git clone git://github.com/wcypierre/AIOlog.git
To update the existing AIOlog:
git remote update
git rebase origin/master
To compile AIOlog:
g++ main.cpp log.cpp -o aiolog.exe (for windows) / g++ main.cpp log.cpp -o aiolog (for mac/linux)

Build from source instructions is added

Not to be nitpicky, but you are calling this Noob Proof. I noticed that both here, as well as in the wiki, you never said to plug the phone to the computer via USB cable.

post-mortem said:
Not to be nitpicky, but you are calling this Noob Proof. I noticed that both here, as well as in the wiki, you never said to plug the phone to the computer via USB cable.
Click to expand...
Click to collapse
Well, assuming someone knows how to flash a custom ROM and/or kernel, I reckon someone would know naturally to use the USB cable. Same as, with Linux, one may need to edit udev rules etc, to get Linux to talk to the phone, or Windows (and Linux), download the appropriate files/drivers, but people should know this already when flashing a ROM or kernel due to s-off issues most users face of our phone. This knowledge should be 'already known', but doing logging is not part of parcel with flashing rom/kernel, being able to connect to a PC for s-on phones, is.
At least that's how I see the developers 'idea' of this, the wiki etc. On topic, thanks, will look at the Linux side of it, probably similar to how I run my personal script for flashing/logging, assuming it's 'just' (ba)sh/shell stuff, haven't looked yet of course.

post-mortem said:
Not to be nitpicky, but you are calling this Noob Proof. I noticed that both here, as well as in the wiki, you never said to plug the phone to the computer via USB cable.
Click to expand...
Click to collapse
Sorry for the late reply as I was having class just now. And thanks for the constructive feedback . What I actually mean by noob proof is that you can choose among the selections to get the log without having to type the commands itself but still I do feel that what you've mentioned is correct as well :good:.
I didn't add an indepth tutorial on how to setup the phone and device as I cater for the 2 major OS(unix and windows, mac os soon to be), which makes the tutorial writing process quite troublesome as there are multiple issues here and there(like some had reported that they had issues when they use windows 8 with adb, to check whether legacy OS like win98 has any issues or not, only ubuntu and its variants needs udev to be set up(based on cyanogenmod's wiki) and etc) which I need to sort out before I can start writing.
However, since you suggested so, I may add some tutorials on how to setup both your device and computer as soon as I have time to make it slightly exclusive to HOX
If you have noticed, I provided a developer version as well in which you can get logs by providing the command line arguments so that any developer who wanted to log a bug, they can just call the exe file with the given argument and the logs will be created.
It is easier and shorter to call my program with the appropriate command line argument than to call the shell code individually(aiolog.exe -a to log logcat, dmesg, kmsg, and last_kmsg vs adb shell logcat > logcat.txt, adb shell dmesg > dmesg.txt and .....).
waz675 said:
Well, assuming someone knows how to flash a custom ROM and/or kernel, I reckon someone would know naturally to use the USB cable. Same as, with Linux, one may need to edit udev rules etc, to get Linux to talk to the phone, or Windows (and Linux), download the appropriate files/drivers, but people should know this already when flashing a ROM or kernel due to s-off issues most users face of our phone. This knowledge should be 'already known', but doing logging is not part of parcel with flashing rom/kernel, being able to connect to a PC for s-on phones, is.
At least that's how I see the developers 'idea' of this, the wiki etc. On topic, thanks, will look at the Linux side of it, probably similar to how I run my personal script for flashing/logging, assuming it's 'just' (ba)sh/shell stuff, haven't looked yet of course.
Click to expand...
Click to collapse
For the tutorial part, that's what I've assumed as well, as writing the tutorials would take quite some time(read above for my reasoning) but hopefully I can get it sorted out as soon as possible
Apparently, it IS just some 'shell' stuff(), but I want to make it not just a 'shell' stuff
If you had noticed, my code is made to be cross compatible(although you have to compile it manually depending on your OS) to allow me to implement some OS specific features and I need the power of the community to do that
More features will be added in the future to make my program even more suitable for bug reporting
p/s: This is a logging tool, not a flashing tool so there won't be any flashing commands.

Version 0.2 is out!
1. AIOlog for Windows: http://aiolog.googlecode.com/files/aiolog_win_v0.2.zip
2. AIOlog for Linux: http://aiolog.googlecode.com/files/aiolog_linux_v0.2.tar
3. AIOlog for Mac: Coming soon.......
New features:
Version 0.2
1. Logcat, kmsg continuous(the normal logcat, kmsg way instead of log, stop and save method) added
2. Added additional checking on device id
3. Removed debug code

For those who build from source, v0.3a is out(but the program still shows it as 0.2)
- logcat radio is added
- Menu is restructured

Thanks
Sent from my HTC One X using xda premium

joewong1991 said:
Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks for the support Please do report back if you have any suggestions or issues eh

Version 0.3 is out
New Features
Version 0.3
1. Added logcat radio(to debug for radio issues)
2. Added log essential(logcat, dmesg, kmsg and last_kmsg)
3. Disable reprompt of device id after it has been entered
4. Misc Fixes

For those who builds from source, version 0.4 is out!
New features:
- Added Auto Device Id detection
- Logging support when there are more than 2 devices connected
- Added logcat clear and dmesg clear
Full changelog: https://github.com/wcypierre/AIOlog/commits/master

@all, Version 0.4 is out!
New features:
- Added Auto Device Id detection
- Logging support when there are more than 2 devices connected
- Added logcat clear and dmesg clear
For those who are using linux based OS, please download the AIOlog according to your OS architecture(32bit or 64bit)
Full changelog: https://github.com/wcypierre/AIOlog/commits/master

Never noticed this one. Ultimate tool for the lazy users. Keep up the good work.
Sent from my HTC One X using xda app-developers app

Braindamage1989 said:
Never noticed this one. Ultimate tool for the lazy users. Keep up the good work.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks . Please do report back if you find any problems or you have any new suggestions to suggest me of

@Source Builders, new functions are added into version 0.5.
New feature:
- Added device auto detection when there is only one device
- Added adb files for Windows users
- Log archive(grouping all logs into a tar file) for Linux feature is done(but not implemented, will be implemented into each logging functions in Version 0.6)

Hi, I'm now in the look for users who can provide me with some data(non-private and non-confidential ones) in order to improve AIOlog as a big amount of data is needed for AIOlog in order to success.
If you're interested, please pm me and state your device name or you can email me via [email protected]

Version 0.5 is out!
Changelog:
Added log push to phone and phone directory creation(log will be available at the computer, and the .aiolog, aiolog and root folder of your phone)
Added log archiving(unix)
Added log cid version
Added ADB files for Windows
Fixed a bug to auto detect device id when there is only one device
Full Changelog: https://github.com/wcypierre/AIOlog/commits/master

For those who builds from source, please rebuild your source as there's some changes in the repo

[Mod] for (Archidroid Rom) {Pocket Ubuntu 14.10/13.10/13.04} (2014/7/4 Updated)

Archidroid is a excellent&wonderful rom for SGS3,
provides flexible,fast,fancy android environment.
With its built in Pocket Debian,you can use"adflash" to upgrade your Archidroid everyday via OTA from git source, USE "adlinux" to boot into Debian. a lot of useful functions....etc
**This built in chroot brings you more stability than mounting a downloaded img from "complete linux installer"**
But in the rom Devoloping concept, the size of pocket debian is limited to 50MB(in case of being included in a rom) &it is not going to support Pocket Ubuutu
Update log:
2014/07/04 added Ubuntu 14.10 Utopic
*14.04LTS is the first build that promised to long term support on arm architecture*(which brings more stability on everything)
*ubuntu now replace "Upstart" with "Systemd" in 14.10, we can avoid a lot of "upstart error" in chroot with 14.10
*screenshot of the update with 14.10 Mate-Desktop Environment(Now it has arm for 14.10){with Archidroid 2.5.0 stable)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why Pocket Ubuntu?
If you want to install more,more,more,but you found a lot of Repositories are not avaliable for Debian testing(Binary-armhf)(cinnamon,chromium?orphaned?..etc),only for ubuntu
Or....you want to get something from ubuntu-backport,ubuntu mutiverse........or ....Maybe you just prefer ubuntu more than debian?
###we know that simply adding ubuntu repositories to debian causes problems,due to the difference of libraries between two distro###we need a pocket ubuntu:angel:
------------------------------------------------------------------------
so I made my own Pocket Ubuntu by myself, and included a little more ingridients I prefer to replace the built in debian....
The acceptable size for me is 60~100MB,
Features
*All the necessary function in Pocket Debian works(exmple...adflash,vnc,ssh...etc)
*Ubuntu Repository main restricted universe mutiverse
*Ubuntu Utopic 14.10(new added) /Saucy 13.10 /Rariing 13.04 with security updates
*size of current release is 86MB
*you can set your own vnc password at first boot
*Nothing....I just like ubuntu more than debian....AND I PREFER THE CONVIENT "ADLINUX" COMMAND IN Archihdroid
Known Issues
Upstart function dont work! you see [start: Unable to connect to Upstart:.....]
THIS IS NOT A BUG,THIS IS CHROOT'S PROBLEM, Upstart will ever not work in chroot....
there are some ways to hide the error message via command:
Code:
dpkg-divert --local --rename --add /sbin/initctl
ln -s /bin/true /sbin/initctl
but this does not fix the problem but hide the error(I didn't hide the error in this Pocket Ubuntu)
HOW TO USE IT?
simply open a filemanager(need root access),rename the downloaded tar.gz file(ubuntu13.10-archi****.tar.gz) to "debian.tar.gz" and replace
/system/archidroid/system/debian.tar.gz
*note:if you have booted up Pocket debian before you have to run "adlinux clean" again after replacing the original tar.gz
Download:
All versions of pocket ubuntu are all in the same download link:
File names& build versions & last updated date
ubuntu14.10archi-20140704.tar.gz | Ubuntu 14.10 Utopic (2014/07/04)
ubuntu13.10archi-20140223.tar.gz | Ubuntu 13.10 Saucy (2014/02/23)
ubuntu13.04archi-20140223.tar.gz | Ubuntu 13.04 Raring (2014/02/23)
https://www.dropbox.com/sh/by61jvmtxqcptm2/rP6rFFAP1e
BUT OF COURSE:THANKS FOR JUSTARCHI FOR CREATING THIS WONDERFUL ROM!:good::good::good:

download now..
evilhawk00 said:
Archidroid is a excellent&wonderful rom for SGS3,
provides flexible,fast,fancy android environment.
With its built in Pocket Debian,you can use"adflash" to upgrade your Archidroid everyday via OTA from git source, USE "adlinux" to boot into Debian. a lot of useful functions....etc
**This built in chroot brings you more stability than mounting a downloaded img from "complete linux installer"**
But in the rom Devoloping concept, the size of pocket debian is limited to 50MB(in case of being included in a rom) &it is not going to support Pocket Ubuutu
Why Pocket Ubuntu?
If you want to install more,more,more,but you found a lot of Repositories are not avaliable for Debian testing(Binary-armhf)(cinnamon,chromium?orphaned?..etc),only for ubuntu
Or....you want to get something from ubuntu-backport,ubuntu mutiverse........or ....Maybe you just prefer ubuntu more than debian?
###we know that simply adding ubuntu repositories to debian causes problems,due to the difference of libraries between two distro###we need a pocket ubuntu:angel:
------------------------------------------------------------------------
so I made my own Pocket Ubuntu by myself, and included a little more ingridients I prefer to replace the built in debian....
The acceptable size for me is 60~100MB,
*All the necessary function in Pocket Debian works(exmple...adflash,vnc,ssh...etc)
*Ubuntu Repository main restricted universe mutiverse
*Ubuntu Saucy 13.10 /Rariing 13.04 with security updates
*size of current release is 86MB
*Nothing....I nust like ubuntu more than debian....AND I PREFER THE CONVIENT "ADLINUX" COMMAND IN Archihdroid
Known Issues
Upstart function dont work! you see [start: Unable to connect to Upstart:.....]
THIS IS NOT A BUG,THIS IS CHROOT'S PROBLEM, Upstart will ever not work in chroot....
there are some ways to hide the error message via command:
Code:
dpkg-divert --local --rename --add /sbin/initctl
ln -s /bin/true /sbin/initctl
but this does not fix the problem but hide the error(I didn't hide the error in this Pocket Ubuntu)
View attachment 2594296View attachment 2594295
HOW TO USE IT?
simply open a filemanager(need root access),rename the downloaded tar.gz file(ubuntu13.10-archi****.tar.gz) to "debian.tar.gz" and replace
/system/archidroid/system/debian.tar.gz
*note:if you have booted up Pocket debian before you have to run "adlinux clean" again after replacing the original tar.gz
Download:
https://www.dropbox.com/sh/by61jvmtxqcptm2/rP6rFFAP1e
BUT OF COURSE:THANKS FOR JUSTARCHI FOR CREATING THIS WONDERFUL ROM!:good::good::good:
Click to expand...
Click to collapse
give u feed back soon

Hello,i have done the procedure correct,and hide the Upstart Error,but i don't know how to initialize the UI; can you help me? thanks :good:

install Gui
QUOTE=Niko99ITA;51947564]Hello,i have done the procedure correct,and hide the Upstart Error,but i don't know how to initialize the UI; can you help me? thanks :good:[/QUOTE]
Originally Posted by*JustArchi*
1. 127.0.0.1:5901 password archidroid.
Remember that before starting VNC you probably want to install some GUI as well, so adlinux default -> debian -> apt-get update -> apt-get install xfce4 (for example)
2. If u successfully installed xfce4 u better run this in terminal:
exec ck-launch-session startxfce4
and for ur sake do a reboot ur phone... and run again adlinux-default or ur choice - vnc and connect again**u then will have a fully working gui*

Didn't notice this thread, nice job .

Niko99ITA said:
Hello,i have done the procedure correct,and hide the Upstart Error,but i don't know how to initialize the UI; can you help me? thanks :good:
Click to expand...
Click to collapse
Just fellow my steps simply
Hello! To launch the GUI , First you need to install newest desktop environment, I suggest XFCE4 or Mate-Desktop(with 14.04)
when you first boot into Ubuntu, you might set a vnc password
after chroot ,terminal type:
apt-get update
apt-get install mate-desktop-environment or apt-get install xfce4
now you need to restart the vncserver, terminal type:
tightvncserver -kill :1
exit
now chroot back again,terminal type:
adlinux
default
vnc
debian
And now the GUI should already launched in the background.
(*if you finished installing these desktop environments, but tightvncserver can't launch it correctly, you have to edit /root/.vnc/xstartup ,edit the correct command to make it works*)
Second,use any vnc viewer app to connect to 127.0.0.1:5901 with your own password set at first boot
I suggest using Pocketclound Pro as vnc viewer App

evilhawk00 said:
Just fellow my steps simply
Hello! To launch the GUI , First you need to install newest desktop environment, I suggest XFCE4 or Mate-Desktop(with 14.04)
when you first boot into Ubuntu, you might set a vnc password
after chroot ,terminal type:
apt-get update
apt-get install mate-desktop-environment or apt-get install xfce4
now you need to restart the vncserver, terminal type:
tightvncserver -kill :1
exit
now chroot back again,terminal type:
adlinux
default
vnc
debian
And now the GUI should already launched in the background.
(*if you finished installing these desktop environments, but tightvncserver can't launch it correctly, you have to edit /root/.vnc/xstartup ,edit the correct command to make it works*)
Second,use any vnc viewer app to connect to 127.0.0.1:5901 with your own password set at first boot
I suggest using Pocketclound Pro as vnc viewer App
Click to expand...
Click to collapse
Ehi Thanks bro
it workeed
finally developing as well as my pc does with an useful interface :victory:
you have all my respect! Good job :good:
---------- Post added at 11:53 AM ---------- Previous post was at 11:52 AM ----------
AMUK0110 said:
QUOTE=Niko99ITA;51947564]Hello,i have done the procedure correct,and hide the Upstart Error,but i don't know how to initialize the UI; can you help me? thanks :good:
Click to expand...
Click to collapse
Originally Posted by*JustArchi*
1. 127.0.0.1:5901 password archidroid.
Remember that before starting VNC you probably want to install some GUI as well, so adlinux default -> debian -> apt-get update -> apt-get install xfce4 (for example)
2. If u successfully installed xfce4 u better run this in terminal:
exec ck-launch-session startxfce4
and for ur sake do a reboot ur phone... and run again adlinux-default or ur choice - vnc and connect again**u then will have a fully working gui*[/QUOTE]
Ah,and you also
thanks you two,i appreciate that

Can anyone guide me step by step starting from scratch? (clean install?)
I can't boot it, get lots of errors.
_________________________________________
Edit:
I reinstalled archidroid, at the last step. I have installed mate desktop. Gui doesn't loads up, please help!

eatsleep said:
Can anyone guide me step by step starting from scratch? (clean install?)
I can't boot it, get lots of errors.
_________________________________________
Edit:
I reinstalled archidroid, at the last step. I have installed mate desktop. Gui doesn't loads up, please help!
Click to expand...
Click to collapse
Hello , first of all, make sure u use the newest 14.10 utopic build
After the installation of mate desktop u only need to try the las two steps to fix any error could happen
YOU SHOULD GOOGLE ABOUT HOW TO EDIT XSTARTUP FILE
if you connect via vnc viewer client and found that the gui does not load, this only means the tightvncserver did not execute mate desktop by default
So, you need to edit tightvncserver's settings. This is what you can do, please edit the file /root/.vnc/xstartup and find something like this:
"exec /etc/X11/xinit/xinitrc" this is the default setting....please add # in front of this line
so it becomes "#exec /etc/X11/xinit/xinitrc"
(u can use vim comand "vim /root/.vnc/xstartup" in terminal to edit the file in terminal...)
After disabling the default setting, u now need to add mate desktop as default
please add the line below into /root/.vnc/xstartup
/usr/bin/mate-session&
and this edit means it will excute this binary file"/usr/bin/mate-session&" before starting vnc server....
now save the file and restart
it should work!
DONE!
Cheers

One Plus One Toolkit v1.3.2 BETA + ADB/python library - UPDATED 12/30/2014

i present to you the latest release from my secret underground laboratory.......
THE HALF-ASSED ONE PLUS ONE TOOLKIT v1.3.2 BETA!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
old screenshots because i'm lazy
UPDATED 12/30/2014
NOW ON GITHUB:
https://github.com/eudemonics/1plus1toolkit
NOW WITH MORE UNIVERSAL FEATURES TO SUPPORT ALL ANDROID DEVICES!
THERE IS A REASON THIS IS CALLED THE HALF-ASSED ONEPLUS ONE TOOLKIT. don't expect frequent regular updates. i respond to support queries when i receive them, which means whenever i check my email or log onto xda-dev, which is not very often. though i do update it every now and then. now that it's on github, you can actually get updates without me having to go update the threads on every forum to make the announcement about it being updated.
USE AT YOUR OWN RISK. i'm not responsible for anything that might happen to your device as a result of using the toolkit. if you use the correct files in the package and follow the toolkit directions onscreen, your device should be just fine. i assume if you have the technical know-how to install python, the android SDK, and run the script, then you've got a pretty good idea of what you're doing already. if you need help, send me a message. the best way to reach me, to get the quickest response, is probably on facebook, as i do not log onto xda-developers or my email accounts regularly:
http://www.facebook.com/dreamcorporation
[***this project was originally posted in the Oneplus One "General" forum, as i'd assumed "Original Android Development" was restricted to ROMs, apps, and themes. i finally read the rules, though, so i hope my toolkit is useful/creative enough to qualify to be here. i could use some beta testers if anyone's brave enough to volunteer - doesn't have to be on the oneplus one, as i am adding more and more functionality to support all android devices. am also open to ideas and suggestions - if you want any features built, just ask. maybe i'll code it for you, and give you credit for the idea too.]
REQUIREMENTS: python 2.7, android SDK, opotoolkit.py, opointro.py pyadb.py. and of course, a machine running ANY OS that supports python and the android SDK (OSX, Windows, Linux, maybe even Chromium OS?)
installation:
download and install python 2.7: https://www.python.org/downloads/
download and install android SDK: https://developer.android.com/sdk/
download toolkit package using GIT:
git clone https://github.com/eudemonics/1plus1toolkit.git 1plus1toolkit
to run from there:
cd 1plus1toolkit
python opotoolkit.py
to update:
git pull https://github.com/eudemonics/1plus1toolkit.git
it should work with the adb and fastboot binaries provided in the github project (*****if on linux rename adb to adb-mac, fastboot to fastboot-mac, adb-linux to adb, and fastboot-linux to fastboot*****), but if not, you should install the android SDK. i recommend even MORE that you create an environmental path variable to the android SDK so you can run the commands from any directory.
setting up an environmental path variable (optional - recommended):
if you're on windows you can go to my pastebin, find the only powershell script on there, and steal/adapt the code to create your own environment path variable. but it's much easier to configure in system properties - i'm not on windows right now so these may not be exact instructions, but you should be able to right click on "my computer", select "properties", go to the "environment" tab in system settings, and add the environment path there. linux and OSX users just need to add the android SDK directory to their ~/.bash_profile or ~/.bashsrc or wherever environment paths are defined. if you still don't understand environmental path variables or symbolic links, i highly recommend google (or startpage.com, the private version).
if you don't want to go to the trouble of creating the environmental path variables, and you want to use the android SDK on your computer, then just extract all the files from the ZIP into your android SDK directory.
how to run the toolkit:
plug phone to computer via USB, turn on android debugging.
open command prompt or terminal window to scripts directory. start toolkit by entering:
"python opotoolkit.py"
if everything is installed and in the right places, you should see a menu like the attached screenshot. if for some reason you get a permission denied error, try launching the command prompt or terminal as administrator or superuser.
i'll continue working on it and adding more when i can so keep checking this space. everything's open source; use, share, steal whatever you want from the code. some credit would be nice, though.
you can use the pyadb.py library to incorporate adb/fastboot commands into your own python projects. i'll be adding more features to that, but for now most of the common features are covered.
here's the github link - it still won't acknowledge my repository exists, and if i try to create it again locally it gives me a fatal error. [[email protected]#[email protected]#] let's just say github and i are not exactly BFF's. you can check to see if the files ever manage to appear: https://github.com/eudemonics/1plus1toolkit
i've been working to expand this so it can be used with all android devices, though it'll require people to supply their own device files to use with it! just because the toolkit can flash device firmware DOES NOT MEAN that the included files meant for the oneplus one will work on a NON oneplus one device! hopefully that's not something i needed to emphasize. if there is enough positive feedback and support i'll create a GUI since people like to click things more than type into a terminal window
not gonna bug you for donations - all my code is open source - if you'd like to donate, please do so by purchasing my EP. hey, you might even like the music, too:
buy it here: http://dreamcorp.bandcamp.com
or search for it on itunes, google play, amazon, spotify, last.fm, cdbaby, and so on.
there are also links in the description for my video:
https://www.youtube.com/watch?v=2i-F4jiKtGg
special thanks to chainfire for superSU, cyanogenmod for CM11S, geohot for the towelroot exploit, team win recovery project for the TWRP recovery, the developers of philz recovery, clockworkmod for the CWM recovery, OnePlus for giving us such an excellent and affordable product, and everyone here on xda-developers for growing and developing the android community into the vital and creative force it is today!
XDA:DevDB Information
Half-Assed OnePlusOne Toolkit in Python/ADB-python library - now on github!!!, Tool/Utility for the ONEPLUS ONE
Contributors
eudemonics
Source Code: https://github.com/eudemonics/1plus1toolkit
Version Information
Status: Stable
Current Stable Version: 1.3.1 STABLE
Stable Release Date: 2014-11-13
Current Beta Version: 1.3.2 BETA
Beta Release Date: 2014-12-30
Created 2014-08-19
Last Updated 2014-12-30

How work sync
mENU 5 HAS SYNC... hOW WORK ? wHAT SYNC ?

I get a "SyntaxError: invalid token" when trying to launch. Did I miss something?

You guys have really tried using the 'half-assed' toolkit???!! Wow - brave.

Mr Woolf said:
You guys have really tried using the 'half-assed' toolkit???!! Wow - brave.
Click to expand...
Click to collapse
It's also quite nice to understand how the Python works as everything is open-sourced in Python without privatized code. Good for educational purposes.
But yeah, I get why you'd say that, haha!

I tranfered files to /sdcard it showed transfer progress and finished but files are nowhere to be found on phone???

nedooo said:
I tranfered files to /sdcard it showed transfer progress and finished but files are nowhere to be found on phone???
Click to expand...
Click to collapse
did you copy multiple files at once? what did you use for the destination? (syntax)

Single .zip file and syntax : /sdcard
Edit: I needed this tool to transfer files from PC on XP without administrator privileges (MTP was mission impossible), at the end I did it with Airdroid.
Thanks for replay.

Nice, I don't use it, but it has passed my tests

[Guide] Build Your Own [UNOFFICIAL][9] LineageOS4Microg 16.0 (by Bernie_nix)

In the spirit of open-source, if there's one ROM that deserves to be "home-brewed" in addition to AOSP and Lineage, it's LineageOS4Microg. This guide will explain how to do so using Docker. LineageOS and Microg are explained below followed by the guide.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/​
Click to expand...
Click to collapse
Rom Built by Bernie_nix​Known issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Building Requirements
1. A fast PC or VPS account such as Google Compute Engine. Minimum PC recommended requirements are Intel i5 or equivalent, 4 cores 8 threads minimum (more cores and better CPU recommended), 16GB ram, SSD and 300GB free drive space minimum, fast internet connection (you will download over 30GB of sources).
2. Ubuntu 18.04 is supported here. If you use Windows or another version of Linux, let others know of your tweaks and workarounds.
3. Patience and time. Downloading sources, setting up and building a rom will take hours if not days (depending on your PC hardware and internet speed).
Environment Setup & Build​1. Install Docker on Ubuntu (run each command once in terminal)
Code:
sudo apt-get update
sudo apt install docker.io
sudo systemctl start docker
sudo systemctl enable docker
2. Test that docker is running (run command in terminal)
Code:
docker run hello-world
You should see something like this, "docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world ca4f61b1923c: Pull complete Digest: sha256:ca0eeb6fb05351dfc8759c20733c91def84cb8007aa89a5bf606bc8b315b9fc7 Status: Downloaded newer image for hello-world:latest Hello from Docker! This message shows that your installation appears to be working correctly. ..."
3. Pull lineageos4microg docker onto your pc (run command in terminal)
Code:
docker pull lineageos4microg/docker-lineage-cicd
4. After pull is complete, create the following directories in your home/YOURUSERNAME directory
lineageos4microg
lineageos4microg/src
lineageos4microg/ccache
lineageos4microg/local_manifests
lineageos4microg/keys
lineageos4microg/logs
lineageos4microg/zips
So it might look something like this: home/JoeAndroid/lineageos4microg
5. Copy the 4 attached xml files (bottom of this post) to your local_manifests folder
These are: ocean.xml, include_proprietary.xml, proprietary.xml, and custom_packages.xml
6. In terminal, cd into the lineage4microg folder, and copy and paste the following commands all at once after changing YOURUSERNAME to your username in ubuntu. For an explanation of options, see the link at bottom of post. This code will download sources, sync your repos with newest updates and start your build. This step could take hours. It is downloading sources, syncing repos and building your rom!
Code:
sudo docker run \
-e "BRANCH_NAME=lineage-16.0" \
-e "DEVICE_LIST=ocean" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "WITH_SU=true" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension " \
-e "INCLUDE_PROPRIETARY=false" \
-v "/home/YOURUSERNAME/lineageos4microg/lineage:/srv/src" \
-v "/home/YOURUSERNAME/lineageos4microg/zips:/srv/zips" \
-v "/home/YOURUSERNAME/lineageos4microg/logs:/srv/logs" \
-v "/home/YOURUSERNAME/lineageos4microg/cache:/srv/ccache" \
-v "/home/YOURUSERNAME/lineageos4microg/keys:/srv/keys" \
-v "/home/YOURUSERNAME/lineageos4microg/manifests:/srv/local_manifests" \
lineageos4microg/docker-lineage-cicd
7. Your build should be in the zips folder when complete! Flash in twrp/ofox.
8. If your build fails, check the log in lineageos4microg/logs/ocean folder. If you receive the following error, "Can not locate config makefile for product "lineage_ocean"" you will need to copy the 4 xmls from lineageos4microg/local_manifests to lineageos4microg/manifests.​
References and links:
https://phoenixnap.com/kb/how-to-install-docker-on-ubuntu-18-04
https://github.com/lineageos4microg/docker-lineage-cicd
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Thanks to Dark98, Electimon, Barry and many others for initial help and repos when building this rom.

Reserved #1

Reserved #2

Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?

skalnas said:
Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?
Click to expand...
Click to collapse
Can you take a picture of the screenshot including how you typed in the commands? Need a bit more info

I just pasted the code changing username screenshot attached

skalnas said:
I just pasted the code changing username screenshot attached
Click to expand...
Click to collapse
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?

Bernie_nix said:
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?
Click to expand...
Click to collapse
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.

skalnas said:
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.
Click to expand...
Click to collapse
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script

Bernie_nix said:
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script
Click to expand...
Click to collapse
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again

skalnas said:
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again
Click to expand...
Click to collapse
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.

Bernie_nix said:
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.
Click to expand...
Click to collapse
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks

skalnas said:
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks
Click to expand...
Click to collapse
Awww... Well I had that happen before. Even if you have an old platter hdd (not ssd) as long as it's got the GBs of space it will take a little longer to build but for these purposes will do just fine. I use both SSD and hdds to build.

Got my dual boot set up. First tried Ubuntu but it kept locking up, went with Linux mint. Got a 250 GB partition, going to give it another go tommorow.

View attachment 4980819well, after switching from VM to dual boot, I gave it another go, and i got a msg in linux mint that i ran out of space about 3 1/2 hrs into build. I had set up 250gb partition as you suggested. I did 30gb root, 220 GB home,4 GB swap.
Can you take a look at the logs, i'm not clear looking at logs how much of build completed.
There was the zip file about 604 mb in the zips folder, which I could open(along with an sha and md5 files, which i dont know anything about.) I'm thinking possibly the build completed despite the warning in linux about running of free space.
I shrank the /root partition in gparted to 20gb and tried to extend the extra 10gb to home, but i couldn't.
Is it possible to specify 25gb ccache in the docker script somehow so that instead of the 50 it seems to allocate, maybe that will solve the space issue?
Thanks again, looks like progress.

Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?

skalnas said:
Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?
Click to expand...
Click to collapse
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
boot.img already exists, no need to overwrite...
dtbo.img already exists, no need to overwrite...
system.img already exists, no need to overwrite...
vendor.img already exists, no need to overwrite...
Total of 704512 4096-byte output blocks in 23 input chunks.
Total of 147456 4096-byte output blocks in 13 input chunks.
done.
Click to expand...
Click to collapse
Where is "Missing "vendor/lineage", aborting." appearing?

Bernie_nix said:
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
Where is "Missing "vendor/lineage", aborting." appearing?
Click to expand...
Click to collapse
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.

skalnas said:
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.
Click to expand...
Click to collapse
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?

Bernie_nix said:
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?
Click to expand...
Click to collapse
The zip was 604mb, i did successfully flash it, thanks again for your help and guide building my first rom!
so the xml file should be edited to:
<project name="bernie-nix/android_device_motorola_sdm632-common-1" path="device/motorola/sdm632-common" remote="github"/>
?
btw, i don't see your repos on github anymore.