Database Develop

Many Questions in 1 Thread

1) I just got Ubuntu on my computer. How do I use adb on it? I have already put the file in that udev folder and debugging is on already. What files do I need and what do I run in terminal?
2) Adb&fastboot do not work for me anymore. It always says "waiting for device" but nothing happens
3) Are there any alternates to applying your nandroid backups other than fastboot?
4) I just got LucidREM's new JFv1.51 but whenever I receive a call my phone vibrates then just loses all connection and has me input my 4 digit sim card key to unlock it. Anyone else get this problem?
5) What is the latest system recovery utility build? Mine is JFv1.42

First, make sure you have set up the adb compatibility for your distribution:
http://telyas.com/wordpress2/2009/04/29/ubuntu-jaunty-and-android-adb/
Note this is for jaunty.
do you have the android SDK? you need to download it, then run adb from the tools folder, or add it to your .bashrc profile so that you can type "adb" from anywhere.
http://developer.android.com/sdk/download.html?v=android-sdk-linux_x86-1.5_r2.zip
http://developer.android.com/sdk/1.5_r2/installing.html
There are no "image all" alternates to fastboot. If you need a compiled for linux fastboot (32 bit), here:
http://yochai.dyndns.org:8888/android/fastboot
I can't help you with the last one.

yochaigal said:
First, make sure you have set up the adb compatibility for your distribution:
http://telyas.com/wordpress2/2009/04/29/ubuntu-jaunty-and-android-adb/
Note this is for jaunty.
do you have the android SDK? you need to download it, then run adb from the tools folder, or add it to your .bashrc profile so that you can type "adb" from anywhere.
http://developer.android.com/sdk/download.html?v=android-sdk-linux_x86-1.5_r2.zip
http://developer.android.com/sdk/1.5_r2/installing.html
There are no "image all" alternates to fastboot. If you need a compiled for linux fastboot (32 bit), here:
http://yochai.dyndns.org:8888/android/fastboot
I can't help you with the last one.
Click to expand...
Click to collapse
So I installed the adb. It is in /android/tools/
How do I get to it

either use
Code:
cd /android/tools
./adb devices
or
Code:
sudo cp /android/tools/adb /usr/bin/adb
adb devices
either one will work. if you use the second one you can use adb from any directory. Also the latest recovery image for the G1 is 1.43 but i still use 1.42 since i don't think there is a differnce

tubaking182 said:
either use
Code:
cd /android/tools
./adb devices
or
Code:
sudo cp /android/tools/adb /usr/bin/adb
adb devices
either one will work. if you use the second one you can use adb from any directory. Also the latest recovery image for the G1 is 1.43 but i still use 1.42 since i don't think there is a differnce
Click to expand...
Click to collapse
Thanks ill try that out later.
Also, how can I restore my boot.img, system.img, data.img without fastboot?

Abolfazl said:
Thanks ill try that out later.
Also, how can I restore my boot.img, system.img, data.img without fastboot?
Click to expand...
Click to collapse
you can't

tubaking182 said:
you can't
Click to expand...
Click to collapse
Ok I have fastboot and I put it in /android/tools
I did sudo cp /android/tools/fastboot /usr/bin/fastboot
But when I run "fastboot" I get "bash: /usr/bin/fastboot: Permission denied"
Any help?

Abolfazl said:
Ok I have fastboot and I put it in /android/tools
I did sudo cp /android/tools/fastboot /usr/bin/fastboot
But when I run "fastboot" I get "bash: /usr/bin/fastboot: Permission denied"
Any help?
Click to expand...
Click to collapse
use: sudo fastboot

korndub said:
use: sudo fastboot
Click to expand...
Click to collapse
sudo: fastboot: command not found
Fastboot is in /usr/bin :\

use the path
either try specifying the full path to fastboot in your sudo command, or ensure that sudo is installed, which should obtain, since Ubuntu installs it by default

arqueware said:
either try specifying the full path to fastboot in your sudo command, or ensure that sudo is installed, which should obtain, since Ubuntu installs it by default
Click to expand...
Click to collapse
Alright I got fastboot working.
Now my only problem is that whenever I use fastboot to restore the 3 .img's my phone just goes to the android image and it keeps on cycling the boot

FaceBook not installed. Market thinks it is. Need a fix.

So, I had facebook for android installed and recently update to cyanogens latest ad somehow it got deleted. Could have been a theme that removed it, as I didn't notice it until after I applied a theme. The icon was still on my home screen, but not in the app tray and the widget is gone.
Anyway I when into the market and it says its installed, its not and the option to uninstall or open is grayed out.
Any way to fix this?

In order to get it fixed for me I had to go into adb and
Code:
adb shell
rm -r /system/app/com.facebook.katana
rm -r /data/data/com.facebook.katana
exit
adp push Facebook.apk /system/sd/app
The app still didn't work but I was then able to uninstall it in the market and reinstall the market version and it has worked fine.

jairomeo said:
In order to get it fixed for me I had to go into adb and
Code:
adb shell
rm -r /system/app/com.facebook.katana
rm -r /data/data/com.facebook.katana
exit
adp push Facebook.apk /system/sd/app
The app still didn't work but I was then able to uninstall it in the market and reinstall the market version and it has worked fine.
Click to expand...
Click to collapse
I get "can not remove /system/app/com.facebook.katana"

The reason you're getting that, is because it doesn't exist in that directory, try the second command, and see if it gives you the same error.

put the apk on sd and try this :
1. Open a Terminal Window:
2. Type the following:
- su
- mount /system -o remount,rw
- cd /sdcard
- cp "appname".apk /system/app

rp1783 said:
The reason you're getting that, is because it doesn't exist in that directory, try the second command, and see if it gives you the same error.
Click to expand...
Click to collapse
Thats what I thought and I get the same error with the other command.
yozpalang said:
put the apk on sd and try this :
1. Open a Terminal Window:
2. Type the following:
- su
- mount /system -o remount,rw
- cd /sdcard
- cp "appname".apk /system/app
Click to expand...
Click to collapse
This was my next step, but, don't have the apk. Anyone care to upload it or send me a link?

http://www.androidspin.com/downloads...e=Facebook.apk

yozpalang said:
http://www.androidspin.com/downloads...e=Facebook.apk
Click to expand...
Click to collapse
Not Found
The requested URL /downloads...e=Facebook.apk was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

this is where i got it http://forum.xda-developers.com/showthread.php?t=582302

Got it! Thanks all for the help. Installed and working now.

[Q] Kindle Fire HD - wireless will not turn on

In an attempt to install TWRP to my TATE device, I seemed to have broken the ability to enable wireless (it is toggled off, grayed out, and cannot be enabled).
I followed the steps from here (http://forum.xda-developers.com/showthread.php?t=2128848) but did not want to install CWM. Wireless did work on my rooted Kindle before these steps were taken.
The steps that were taken causing it to no longer work are:
1. Install the stack override in /system:
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
2. Stop the auto recovery update script:
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "mount -o remount,ro ext4 /system"
3. Flashing uncorrupted bootloader, boot, recovery:
Code:
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.6.img
fastboot -i 0x1949 flash recovery kfhd7-twrp-2.6.3.1-recovery.img
fastboot -i 0x1949 reboot
The recovery did install correctly as I could boot into TWRP and create a backup. I also created a backup before the entire process using adb. What should I do to enable wireless? Thank you.

JArch3r said:
The recovery did install correctly as I could boot into TWRP and create a backup. I also created a backup before the entire process using adb. What should I do to enable wireless? Thank you.
Click to expand...
Click to collapse
If it were me I would factory reset and try again. You can use the nandroid backup you made beforehand as well. When ever wifi goes hinky a factory reset seems to be the best solution.

LinearEquation said:
If it were me I would factory reset and try again. You can use the nandroid backup you made beforehand as well. When ever wifi goes hinky a factory reset seems to be the best solution.
Click to expand...
Click to collapse
Thank you for the solid advice. I discovered the issue arose from blindly following the instructions in the thread -- it said to use kfhd7-freedom-boot-7.4.6.img instead of the applicable version. I googled and found the 7.2.3 version on HashCode's goo.im page, repeated all of the steps using it, and wireless works perfectly now.
In my searches of trying to solve the problem, I discovered users with the same issue. Kindle Fire (HD) users unavailable to connect to wifi and "MAC address unavailable." Running idme /? in a terminal on the device states "Could not open /dev/block/mmcb1k0! Can't read the idme." I believe they would benefit from reading this.

JArch3r said:
Thank you for the solid advice. I discovered the issue arose from blindly following the instructions in the thread -- it said to use kfhd7-freedom-boot-7.4.6.img instead of the applicable version. I googled and found the 7.2.3 version on HashCode's goo.im page, repeated all of the steps using it, and wireless works perfectly now.
In my searches of trying to solve the problem, I discovered users with the same issue. Kindle Fire (HD) users unavailable to connect to wifi and "MAC address unavailable." Running idme /? in a terminal on the device states "Could not open /dev/block/mmcb1k0! Can't read the idme." I believe they would benefit from reading this.
Click to expand...
Click to collapse
I am having the same exact problem. can you post a link to repair info you are referring to above. Thanks

crustysmooth said:
I am having the same exact problem. can you post a link to repair info you are referring to above. Thanks
Click to expand...
Click to collapse
One page where the files are available: https://www.androidfilehost.com/?w=files&flid=34232
You can also just google "kfhd7-freedom-boot-7.2.3.img" or the name of the file you need.

Excuse me, but can you provide download link for kfhd7-freedom-boot-7.2.3.img ?
google didn't help

Guide: How To Build AOSP 4.4.3 From Source With Linux Mint 16 - Nexus 5 KTU84M

Guide: How To Build AOSP 4.4.3 From Source With Linux Mint 16 - Nexus 5 KTU84M
Important Note: Do not use Linux Mint 16 KDE to do this guide. Removing the old Java will seriously mess up your desktop and programs menu. This guide has been tested with Linux Mint 16 Cinnamon and Linux Mint 16 Mate.
Link to PA Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Link To SuperSu: http://download.chainfire.eu/supersu
Link to zip of completely unaltered build of AOSP 4.4.3. https://drive.google.com/file/d/0ByOOg6Qw8gHZMXBWVDRyVmVuRWc/edit?usp=sharing
I started this guide as I could not find a step by step detailed guide to build a stock AOSP from source with Linux Mint 16.
All the steps should work in Ubuntu but I haven't tried so not 100% sure of that.
All this assumes your phone is already unlocked.
Here goes:
Important note: Anything that is bolded text other then section titles are command line entries that are done in Terminal in Linux Mint. I thought it would be simpler to do it this way then say 'in Terminal' for every entry.
First we need to remove Icedtea Java or OpenJDK.
In Terminal: sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*
Then in Terminal: sudo add-apt-repository ppa:webupd8team/java
Next: sudo apt-get update && sudo apt-get install oracle-java6-installer
Be sure to accept the licence agreement to install java when it prompts you.
Next: sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.8-dev python
Follow this with: sudo apt-get install -f
This should fix any dependency errors.
Now: sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Next download the SDK Tools For Linux x64 from this link. https://developer.android.com/sdk/index.html
Then: cd ~/Downloads
And: tar -xvf android-sdk_r22.6.2-linux.tgz
or tab the latest 'android-sdk_xxx.tgz file it they update it and it is a newer version then the one I downloaded to do this.
You can rename the android.sdk_xxx.tgz folder you extracted to SDK.
Then: cd ~/Downloads/SDK/tools
Next: ./android sdk
It will show you the tools that can be installed, just install the highest version API of 'Platform Tools' and 'Tools' for the latest android version '4.4.x' it shows.
Make sure you install the repo tool, in Terminal: mkdir ~/bin
Then: curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
And: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Now: sudo chmod a+x ~/bin/repo
Now sudo nano ~/.bashrc
Add this to the bottom of the text: export PATH=~/bin:$PATH
Then hit Ctrl-O and enter, it should say it saved the file followed by Ctrl-X to exit.
Then restart bash: source ~/.bashrc
Now lets Initialize the Repository for GIT configuration
First : git config --global user.name {Your Name}
Then: git config --global user.email {[email protected]}
If you have not registered with the GitHub website just doing these two steps works fine.
If you have registered with the GitHub website create a file called .netrc in your home directory, add your GitHub password to it with no spaces on the first line and change the permissions to '600' or you will have to continually authenticate when building the source.
In Terminal:nano ~/.netrc
Then add just your GitHub password (like I said you only need to do this if you have registered with GitHub).
Then 'Ctrl-O' and enter and it'll say it saved it, then 'Ctrl-X' to exit nano.
And: chmod 0600 ~/.netrc
Now: mkdir ~/AOSP
Then: cd ~/AOSP
Now you get the source code etc: repo init -u https://android.googlesource.com/platform/manifest -b android-4.4.3_r1.1
Followed by: repo sync -j12
Use repo sync -j12 for a quad core CPU or Intel I5 or if you have say an quad core I7 with 8 threads you can use repo sync -j24 to speed things up etc.
I have a I7 3930k with 12 threads so I used repo sync -j36. This gives you three threads per logical CPU and speeds things along quite well.
It may take several hours for the sync to finish.
After the sync finishes go to https://developers.google.com/android/nexus/drivers#hammerheadktu84m and download the KTU84Mdrivers (binaries) for the Nexus 5.
If you have closed the Terminal after the sync remember to first do this when you reopen it: cd ~/AOSP
when you open Terminal again before doing the cp and tar commands.
In Terminal: cp ~/Downloads/broadcom-hammerhead-ktu84m-175c1204.tgz ~/AOSP
Then: cp ~/Downloads/lge-hammerhead-ktu84m-716c9c42.tgz ~/AOSP
And: cp ~/Downloads/qcom-hammerhead-ktu84m-06019566.tgz ~/AOSP
In Terminal: tar -xvf broadcom-hammerhead-ktu84m-175c1204.tgz
And: tar -xvf lge-hammerhead-ktu84m-716c9c42.tgz
then: tar -xvf qcom-hammerhead-ktu84m-06019566.tgz
They should be the file names of the binaries for KTU84M that you are extracting but if for any reason the file names are different use the Tab key and tab the correct names in after 'tar -xvf'.
If the names ARE different I'd really check to make sure you downloaded the correct hammerhead binaries.
Now also in Terminal: ./extract-broadcom-hammerhead.sh
Then: ./extract-lge-hammerhead.sh
And: ./extract-qcom-hammerhead.sh
Hint: It will show you a really long licence agreement for each binary that you scroll by hitting the Enter key that takes forever to scroll one line at a time, it has 8 sections and several subsections. Hold the Enter key until you just get past Part 8, section D of the licence and stop there. Now hit enter a few more time one key stroke at a time until you finish Part 8 section E and see the 'Type 'I ACCEPT' to agree to the licence.' and type I ACCEPT If you just scroll by holding the Enter key all the way to the bottom of the licence you'll get an error you never accepted the licence. Then close Terminal.
Building the Sources
Now open Terminal: cd ~/AOSP
Then: . ./build/envsetup.sh
Now to select the type of device we give the following command: lunch
Choose: 9. aosp_hammerhead-userdebug
by entering '9' or whatever number aosp_hammerhead is after your enter the 'lunch' command (it was number 9 on mine).
Now: make -j12 for a quad core cpu or I5 or make -j24 for an I7 etc.
With your phone connected to your USB cable and the PC: adb root
Then: adb reboot bootloader
And: cd out/target/product/hammerhead
Lastly: fastboot -w flashall
If you get an error on the 'adb' and 'fastboot' commands do these first:
sudo apt-get install android-tools-adb
And: sudo apt-get install android-tools-fastboot
If you get an error when you fastboot -w flashall to do with a '-p' flag needed or 'android-info.txt' is missing it means you forgot to to the 'lunch' command before building the source. Go back to the 'Building The Sources' section.
If you already have a custom recovery installed like TWRP and would rather build a zip file to install with the recovery rather Then flash it in adb instead of make -j12 do: make -j12 otapackage
In the /home/"yourusername"/AOSP/out/target/product/hammerhead you have an aosp_hammerhead-ota-eng.___.zip file to flash in your custom recovery.
You will need to wipe/reset data in recovery before flashing it and re-install all your apps etc.
Installing Custom Recovery, Rooting and Google Apps
If you want to install a custom recovery download TWRP http://techerrata.com/browse/twrp2/hammerhead
Rename the file in Downloads to recovery.img
Then in Terminal with your phone connected by USB to your PC: adb root
And: adb reboot bootloader
Then: cd ~/Downloads
And: fastboot flash recovery recovery.img
Use the volume buttons on your phone to scroll onto "Restart Bootloader" and hit the powerbutton to select it. After the bootloader reloads, use the volume buttons to scroll to "Recovery Mode" and hit power button again to select it. You should then be in your custom recovery.
If for any reason you get a red android and no recovery just boot into fastboot mode again and reinstall the recovery.img.
And finally, to root your phone download SuperSu http://download.chainfire.eu/supersu and install the supersu.zip in recovery mode.
Download PA GAPPS from here http://forum.xda-developers.com/showthread.php?t=2397942 if you want the zip to install Google Apps in recovery.
You now have your own rooted vanilla AOSP you compiled yourself, congrats!
P.S. Very likely a good idea wipe/reset data in recovery and start with a clean install, you'll need to install all your programs and stuff anyways I'm sure.
P.P.S. I also installed the Xposed Framwork apk from this link http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401/post24267797 so I could install the Advanced Reboot Menu and some other useful mods.

Hi man great tutorial.
I followed your tutorial exactly and it compiles very good and everything works great with flashing it to device to.
I start the rom and everything is working but then if i reboot i get wrong date and time for 20sec and it goes back to current time and date.
but i get like 10 notifications from all my google apps and it very anoying. and google now dont work till it gets synced.
i thougt it was my build that had issues but i flashed your rom that you had compiled and it has the same issues.
Did y have that issue?

bariz143 said:
Hi man great tutorial.
I followed your tutorial exactly and it compiles very good and everything works great with flashing it to device to.
I start the rom and everything is working but then if i reboot i get wrong date and time for 20sec and it goes back to current time and date.
but i get like 10 notifications from all my google apps and it very anoying. and google now dont work till it gets synced.
i thougt it was my build that had issues but i flashed your rom that you had compiled and it has the same issues.
Did y have that issue?
Click to expand...
Click to collapse
No, I've never had that issue. Did you wipe/reset data in recovery. If you never you need to do that. If you did I would try and do it again, it might fix the issue. You'll have to re-install all your apps etc. when you do though.
Also you can try to flash the zip I have to download in the OP, it is a completely unaltered stock AOSP build. DO wipe/reset in recovery before you do and you'll have to install the recovery in the guide to flash the zip.
https://docs.google.com/file/d/0ByOOg6Qw8gHZZjZXTmRXU05Ed1E/edit
If you want to install a custom recovery download TWRP http://techerrata.com/browse/twrp2/hammerhead
Rename the file in Downloads to recovery.img
Then in Terminal with your phone connected by USB to your PC: adb root
And: adb reboot bootloader
Then: cd ~/Downloads
And: fastboot flash recovery recovery.img
Use the volume buttons on your phone to scroll onto "Restart Bootloader" and hit the powerbutton to select it. After the bootloader reloads, use the volume buttons to scroll to "Recovery Mode" and hit power button again to select it. You should then be in your custom recovery.
If for any reason you get a red android and no recovery just boot into fastboot mode again and reinstall the recovery.img.
Edit: Sorry, just now saw you flashed my ROM. The wipe data should fix it though.

KedarWolf said:
No, I've never had that issue. Did you wipe/reset data in recovery. If you never you need to do that. If you did I would try and do it again, it might fix the issue. You'll have to re-install all your apps etc. when you do though.
Also you can try to flash the zip I have to download in the OP, it is a completely unaltered stock AOSP build. DO wipe/reset in recovery before you do and you'll have to install the recovery in the guide to flash the zip.
https://docs.google.com/file/d/0ByOOg6Qw8gHZZjZXTmRXU05Ed1E/edit
If you want to install a custom recovery download TWRP http://techerrata.com/browse/twrp2/hammerhead
Rename the file in Downloads to recovery.img
Then in Terminal with your phone connected by USB to your PC: adb root
And: adb reboot bootloader
Then: cd ~/Downloads
And: fastboot flash recovery recovery.img
Use the volume buttons on your phone to scroll onto "Restart Bootloader" and hit the powerbutton to select it. After the bootloader reloads, use the volume buttons to scroll to "Recovery Mode" and hit power button again to select it. You should then be in your custom recovery.
If for any reason you get a red android and no recovery just boot into fastboot mode again and reinstall the recovery.img.
Edit: Sorry, just now saw you flashed my ROM. The wipe data should fix it though.
Click to expand...
Click to collapse
Of course i wiped before flashing. The thing is it works on first boot. time and everything no notifications from google apps but as soon as i reboot time and date resets and i get 10 notifications from my google apps sayin time and date error and syncing problem.
I decided to make a clean repo sync again by removing everything and start from the begining. Let ypu know how it goes.

bariz143 said:
Of course i wiped before flashing. The thing is it works on first boot. time and everything no notifications from google apps but as soon as i reboot time and date resets and i get 10 notifications from my google apps sayin time and date error and syncing problem.
I decided to make a clean repo sync again by removing everything and start from the begining. Let ypu know how it goes.
Click to expand...
Click to collapse
I'd try wipe data again and I checked the Date/Time settings, I have 'Automatic date & time' and 'Automatic time zone' enabled. If it does it with my zip and your sync I doubt it is the build that is the trouble. You also might want to try disabling the auto time and date and setting it manually, it might be it is taking a minute to sync with your cell provider, hence the errors. Manually setting the auto time zone as well.
Also you might want to try a different Google Apps package from the link I provided. I use the micro one then if I have to add anything I just do it by Google Play.
Found this link, I'd try the flashable zip a few posts down or manually editing like one guy suggests.
http://forum.xda-developers.com/showthread.php?t=2580974

KedarWolf said:
I'd try wipe data again and I checked the Date/Time settings, I have 'Automatic date & time' and 'Automatic time zone' enabled. If it does it with my zip and your sync I doubt it is the build that is the trouble. You also might want to try disabling the auto time and date and setting it manually, it might be it is taking a minute to sync with your cell provider, hence the errors. Manually setting the auto time zone as well.
Also you might want to try a different Google Apps package from the link I provided. I use the micro one then if I have to add anything I just do it by Google Play.
Found this link, I'd try the flashable zip a few posts down or manually editing like one guy suggests.
http://forum.xda-developers.com/showthread.php?t=2580974
Click to expand...
Click to collapse
Thank you for that. But its just a patch to fix. How come its broken if it comes from google repo ? :S
i compiled CM11 and no time issues there.

This is a perfect guide. Thank you VERY much.
The Nexus 5 advocate (Team Inferno)

TheLastSidekick said:
This is a perfect guide. Thank you VERY much.
The Nexus 5 advocate (Team Inferno)
Click to expand...
Click to collapse
Have you the time issue there phone resets to year 1970 upon reboot?

Really nice great tutorial

bariz143 said:
Thank you for that. But its just a patch to fix. How come its broken if it comes from google repo ? :S
i compiled CM11 and no time issues there.
Click to expand...
Click to collapse
Not sure, I've had no trouble that way.

Guide Updated
bariz143 said:
Hi man great tutorial.
I followed your tutorial exactly and it compiles very good and everything works great with flashing it to device to.
I start the rom and everything is working but then if i reboot i get wrong date and time for 20sec and it goes back to current time and date.
but i get like 10 notifications from all my google apps and it very anoying. and google now dont work till it gets synced.
i thougt it was my build that had issues but i flashed your rom that you had compiled and it has the same issues.
Did y have that issue?
Click to expand...
Click to collapse
The guide has been updated to the KTV49L build which has several bug fixes from the old build. I'm not sure if the date issue has been fixed but if you want to try to build AOSP again just letting you know it is an option.

KedarWolf said:
The guide has been updated to the KTV49L build which has several bug fixes from the old build. I'm not sure if the date issue has been fixed but if you want to try to build AOSP again just letting you know it is an option.
Click to expand...
Click to collapse
Great news so if I followed your guide before the KVT update where do I start. Do I have to do all again from scratch?

KedarWolf said:
The guide has been updated to the KTV49L build which has several bug fixes from the old build. I'm not sure if the date issue has been fixed but if you want to try to build AOSP again just letting you know it is an option.
Click to expand...
Click to collapse
You need to delete your /home/yourusername/AOSP and /home/yourusername/bin folders you made.
So do: rm -rf ~/AOSP
And: rm -rf ~/bin
Then just:
Make sure you install the repo tool, in Terminal: mkdir ~/bin
Then: curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
And: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Now: sudo chmod a+x ~/bin/repo
Now: mkdir ~/AOSP
Then: cd ~/AOSP
Now you get the source code etc: repo init -u https://android.googlesource.com/platform/manifest -b android-4.4.2_r2
Followed by: repo sync -j12
Use repo sync -j12 for a quad core CPU or Intel I5 or if you have say an quad core I7 with 8 threads you can use repo sync -j24 to speed things up etc.
I have a I7 3930k with 12 threads so I used repo sync -j36. This gives you three threads per logical CPU and speeds things along quite well.
And the rest following that. You do not need to do the other steps though, but the recompiling and build you do so it takes some time.

KedarWolf said:
You need to delete your /home/yourusername/AOSP and /home/yourusername/bin folders you made.
So do: rm -rf ~/AOSP
And: rm -rf ~/bin
Then just:
Make sure you install the repo tool, in Terminal: mkdir ~/bin
Then: curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
And: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Now: sudo chmod a+x ~/bin/repo
Now: mkdir ~/AOSP
Then: cd ~/AOSP
Now you get the source code etc: repo init -u https://android.googlesource.com/platform/manifest -b android-4.4.2_r2
Followed by: repo sync -j12
Use repo sync -j12 for a quad core CPU or Intel I5 or if you have say an quad core I7 with 8 threads you can use repo sync -j24 to speed things up etc.
I have a I7 3930k with 12 threads so I used repo sync -j36. This gives you three threads per logical CPU and speeds things along quite well.
And the rest following that. You do not need to do the other steps though, but the recompiling and build you do so it takes some time.
Click to expand...
Click to collapse
Thanks alot my friend. Just did as you said. And i can see in settings that it KVT build but the time issue is still there. I dont get it at all.
im pissed.
its like building a car and the wipers don't work.

bariz143 said:
Thanks alot my friend. Just did as you said. And i can see in settings that it KVT build but the time issue is still there. I dont get it at all.
im pissed.
its like building a car and the wipers don't work.
Click to expand...
Click to collapse
Sorry, only fix I know is the patch in the link I provided earlier. I have read of other people with the AOSP build have that issue, it's in that link. I don't why it never affected me, might be the settings I use for Time/Date but I've had zero issues that way.

KedarWolf said:
Sorry, only fix I know is the patch in the link I provided earlier. I have read of other people with the AOSP build have that issue, it's in that link. I don't why it never affected me, might be the settings I use for Time/Date but I've had zero issues that way.
Click to expand...
Click to collapse
Yeah i would like to share the rom with friend and it would not be nice if the time resets and getting those notifications error all the time.
Thx alot

i've downloaded this(http://forum.xda-developers.com/showthread.php?t=2585828) build environment from xda so i can start building a rom for my phone and, if i'm not mistaken, i can start your tutorial from the github part right?
thanks

jv.batista said:
i've downloaded this(http://forum.xda-developers.com/showthread.php?t=2585828) build environment from xda so i can start building a rom for my phone and, if i'm not mistaken, i can start your tutorial from the github part right?
thanks
Click to expand...
Click to collapse
I'm not 100% sure t'll work in Xubuntu. I know when I removed the old java in Linux Mint KDE it really messed up the programs menu, even Terminal itself was removed from it. But if it doesn't mess anything up it should work I believe. or just install Linux Mint 16 Cinnamon or MATE in the virtual box instead of Xubuntu, then it'll work I'm sure. Might build much slower though running in a virtual box. You'd have to do everything from the start of the guide, the linux installed in a virtual box is just a clean fresh install of any linux just like a regular new install on any PC.
Hope that helps.

KedarWolf said:
I'm not 100% sure t'll work in Xubuntu. I know when I removed the old java in Linux Mint KDE it really messed up the programs menu, even Terminal itself was removed from it. But if it doesn't mess anything up it should work I believe. or just install Linux Mint 16 Cinnamon or MATE in the virtual box instead of Xubuntu, then it'll work I'm sure. Might build much slower though running in a virtual box. You'd have to do everything from the start of the guide, the linux installed in a virtual box is just a clean fresh install of any linux just like a regular new install on any PC.
Hope that helps.
Click to expand...
Click to collapse
when I had the galaxy s I tried to create a buildmachine but even following every step, there was always something missing, that's why i gave the vm sugestion.
i'll try with the vm but if it doesn't work i'll start from scratch...
thanks
ps: it's a virtual machine but it is running in a i7 with 4 cores and 8gb of ram dedicated to it(if needed i can go for 10gb)

jv.batista said:
when I had the galaxy s I tried to create a buildmachine but even following every step, there was always something missing, that's why i gave the vm sugestion.
i'll try with the vm but if it doesn't work i'll start from scratch...
thanks
ps: it's a virtual machine but it is running in a i7 with 4 cores and 8gb of ram dedicated to it(if needed i can go for 10gb)
Click to expand...
Click to collapse
By start from scratch I mean you just do all the steps in the guide on the fresh virtual machine install. The only time you don't need to do all the steps is if you've done a build and need to do a second build like I did for my Nexus 7 after my Nexus 5 or when the repos update to a new version after you've done a build already. In post #13 it says what to do if you're doing a second build. If it's your first build or a new install of linux or a new virtual box install of linux do all the steps right from the beginning of the guide. Hope that clarifies things.
P.S. Should be pretty fast with your virtual machine but it takes me close to an hour to download the source from the repo then another hour to actually build AOSP with a 6 core 12 thread I7 3930k and 32 gigs of ram.
P.P.S. Sorry for the late night responses, I get home from work around 11 p.m. EST and like to game and stuff a bit before I do other things. Really busy at work, not much time to check here very often.

[HOW-TO] Install Ubuntu Touch as Primary ROM (Internal)

I have seen many people asking how to install it without dual booting, so I'll make things a bit easier...
You need Ubuntu on your PC!
Warning:
I'm not responsible for anything that might ever happen to your device, you must know what you are doing!
This is a beta port and it have bugs
It'll wipe all your data
STEPS:
1. Install the ubuntu-device-flash package
open terminal (ctrl+alt+t) and type:
sudo add-apt-repository "deb http://us.archive.ubuntu.com/ubuntu/ saucy universe multiverse"
sudo add-apt-repository "deb http://us.archive.ubuntu.com/ubuntu/ saucy-updates universe multiverse"
2. Add phablet tools PPAs (not needed for 14.04)
sudo add-apt-repository ppahablet-team/tools
3. Install the ubuntu-device-flash package
sudo apt-get install ubuntu-device-flash
4. Install phablet-tools package
sudo apt-get install phablet-tools
5. NOW BACKUP YOUR PHONE AND SAVE IT IN A SAFE PLACE
6. Reboot into bootloader
7. Unlock bootloader (if it's already unlocked just ignore)
sudo fastboot oem unlock
8. Reboot and then go back to bootloader
9. Installation, type in terminal
ubuntu-device-flash --channel="ubuntu-touch/devel-proposed" --bootstrap --server="http://system-image.tasemnice.eu"
10. Don't touch anything, it'll boot into a cwm-based recovery but it's still runing the script, wait until it completely boots into system
And thats it, enjoy!
FYI, I changed the script to install the most recent version
CREDITS:
https://wiki.ubuntu.com/Touch/Devices
http://developer.ubuntu.com/start/ubuntu-for-devices/installing-ubuntu-for-devices/
Greetings from Brazil

Reserved

You can always change the channel in the script as your preference. Now, the last version is the Vivid Vervet, channel /vivid-proposed

Known issues?

does it work? make calls? texts? lte data?

Everything is on the link in the credits, the only known bugs are the bluetooth that doesn't work and power management. The g+ forum is here: https://plus.google.com/communities/107225355463332672169
It works great (except bluetooth) :good:

Does this work with lollipop bootloader?

shane582 said:
Does this work with lollipop bootloader?
Click to expand...
Click to collapse
It's the same thing
Sent from my Nexus 5 using XDA Free mobile app

Thanks for the list! Will do this laster this day, because right now I´m running dualboot and it´s a pain in the as...

Do you guys know of a good way to use whatsapp on ubuntu? I looked and only found old stuff...
Threema would also be nice

4I-I said:
Do you guys know of a good way to use whatsapp on ubuntu? I looked and only found old stuff...
Threema would also be nice
Click to expand...
Click to collapse
There used to be a third-party app called whosthere, but I think it's not supported anymore, considering that they're banning users for using third-party apps

slayer of worlds said:
There used to be a third-party app called whosthere, but I think it's not supported anymore, considering that they're banning users for using third-party apps
Click to expand...
Click to collapse
Oh i didnt know that! Why are they doing that? Sounds Kind of stupid....
But i guess ill have to wait untill whatsapp is available for ubuntu or ppl are using cooler apps...

slayer of worlds said:
I have seen many people asking how to install it without dual booting, so I'll make things a bit easier...
You need Ubuntu on your PC!
Warning:
I'm not responsible for anything that might ever happen to your device, you must know what you are doing!
This is a beta port and it have bugs
It'll wipe all your data
STEPS:
1. Install the ubuntu-device-flash package
open terminal (ctrl+alt+t) and type:
sudo add-apt-repository "deb http://us.archive.ubuntu.com/ubuntu/ saucy universe multiverse"
sudo add-apt-repository "deb http://us.archive.ubuntu.com/ubuntu/ saucy-updates universe multiverse"
2. Add phablet tools PPAs (not needed for 14.04)
sudo add-apt-repository ppahablet-team/tools
3. Install the ubuntu-device-flash package
sudo apt-get install ubuntu-device-flash
4. Install phablet-tools package
sudo apt-get install phablet-tools
5. NOW BACKUP YOUR PHONE AND SAVE IT IN A SAFE PLACE
6. Reboot into bootloader
7. Unlock bootloader (if it's already unlocked just ignore)
sudo fastboot oem unlock
8. Reboot and then go back to bootloader
9. Installation, type in terminal
ubuntu-device-flash --channel="ubuntu-touch/devel-proposed" --bootstrap --server="http://system-image.tasemnice.eu"
10. Don't touch anything, it'll boot into a cwm-based recovery but it's still runing the script, wait until it completely boots into system
And thats it, enjoy!
FYI, I changed the script to install the most recent version
CREDITS:
https://wiki.ubuntu.com/Touch/Devices
http://developer.ubuntu.com/start/ubuntu-for-devices/installing-ubuntu-for-devices/
Greetings from Brazil
Click to expand...
Click to collapse
Hey, is this for every Android device?
Sent from my GT-S7580 using XDA Free mobile app

SlimShady08 said:
Hey, is this for every Android device?
Sent from my GT-S7580 using XDA Free mobile app
Click to expand...
Click to collapse
No. I gave instructions for nexus 5. You have to see if your device is compatible at ubuntu site and follow its instructions if so.