Related
Hi,
I created a custom Phone.apk, I changed a bit the behavior, the Dialpad etc.etc so this works great, I compiled it against the Platform and it works on the Emulator.
But now I'm trying to put it on the Wildfire (I did an adb pull from the Emulator) and I've now the Phone.apk, I tried to put it with adb rm and then adb push.
So the Problem is not the installation, the Problem is that I can't get it to work.... on the Wildfire...what's wrong?
Any Ideas would be highly appreciated
Thanks
Does really no-one has clue? In which Direction should I go? What can I try?
Please help-me also if I've not 1000 Posts :-(
I've no logged with adb what happens on the Device, the following Error I get, but this make's no sense for me :-(
FATAL EXCEPTION: main
E/AndroidRuntime( 413): android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.CALL_PRIVILEGED dat=tel:123 flg=0x10000000 }
Any Ideas?
I tried now to flash the Phone.apk with several strategies...
-> update.zip
-> adb & cat
-> custom Rom (cooked)
But i really don't now why it fails...omg...
Upload the file and I will try and install it.
Thanks already, I will do it, but maybe I've found the Error...
I now recompiled the Phone.apk...
And tried it with adb install and terminal was saying that I've an OLD SDK...
Failure [INSTALL_FAILED_OLDER_SDK]
So, on the Device there's running Froyo...so it can't be OLD?
But when I'm compiling it, I'm doing a source envsetup.sh and then a lunch 1.
Could it be that I've to compile it some how different???
Thanks for EVERY reply!
Update:
I'm building with this config:
PLATFORM_VERSION_CODENAME=AOSP
PLATFORM_VERSION=AOSP
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=user
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=darwin
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
So I really don't now why I'm getting the OLDER_SDK message...I was looking in the make files and there's the SDK 8....
So I've uploaded it, maybe someone could help me to go a step further
link to Phone.apk
Problem solved...I updated the use-sdk Version in the AndroidManifest.xml of the Phone app.
Can be closed
link dead. do you have any screenshot of your new phone.apk, what do you change? when you say behavior
It's changed relatively static for my Phone Number and my Voicemail Number...so it isn't handy for others...but I will keep up my Work and try several things and If I've something to give to the XDA-Users I will do it.
Thanks for you interest
I want to port cyanogenmod to archos
Are there any developers who know how to download the source of cnm and archos firmware
I'm a game developer and I have no experience with drivers but we can compare are achos devices with other cnm supported devices, the nexus s has the same processor, so we don't have to create a driver for that
Compare list (Update 24 June)
processor is the same as in the droid 2
touchscreen = ?
sound hardware =
screen hardware =
You should take a look at the [DEVELOPEMENT] Cyanogen thread on the Dev subforum - think they'll be pretty happy to see you over there!
fisha21 said:
You should take a look at the [DEVELOPEMENT] Cyanogen thread on the Dev subforum - think they'll be pretty happy to see you over there!
Click to expand...
Click to collapse
Yes, but I'm a newcomer and I can't post a replay there
coen22 said:
Yes, but I'm a newcomer and I can't post a replay there
Click to expand...
Click to collapse
im the thread starter at the post above
Just post 6 posts and you can post at dev section
Lennb said:
im the thread starter at the post above
Just post 6 posts and you can post at dev section
Click to expand...
Click to collapse
Thx, but what do think of my idea
coen22 said:
Thx, but what do think from my idea
Click to expand...
Click to collapse
Im happy, if anyone want to help, but
we need a guy who really have android developement knowledge
Anyone?
I still can't reply to the main thread of cyanogenmod [DEV]
The first thing we have to do is a hardware research
the archos gen8 devices have a
First
Processor: Arm cortex-A8 <-- same as galaxy s, and nexus s
Screen: <--- ?
Then
Touchscreen: <--- ?
Later
Camera: <--- ?
Camera A43: <--- ?
WiFi: <--- ?
Sound: <--- ?
Software buttons
I think we should first make the processor and the screen working, then we are able to debug the device using adb
And we are able to view debug codes on archos
Because all drivers are included in the kernel, what would be the outcome of running say AOSP gingerbread on top of the current kernel?
Archos didn't make much changes to the kernel and the system compared to other manufactures like HTC and it's Sense ROM.
Sorry for this rant, but I cant help myself.
Guys, stop the nonsense regarding not being an android dev and thusnot being able to get anything done. Are you not capable of learning? Please dont reply with negative until you ve tried.
I'm a linuxadmin. It took me 2 hours to get a CM build just by following the instructions. How much longer would it take to rip the drivers ad add them to the image? My guess is that if you start with CM 6 (froyo?) you ll be done in a few days.
So please stop begging for an android dev and all the idle talk of how you think you might get things to work. Just get started with the cyanogenmod build guide already!
Again sorry for the rant
wvl0 said:
Sorry for this rant, but I cant help myself.
Guys, stop the nonsense regarding not being an android dev and thusnot being able to get anything done. Are you not capable of learning? Please dont reply with negative until you ve tried.
I'm a linuxadmin. It took me 2 hours to get a CM build just by following the instructions. How much longer would it take to rip the drivers ad add them to the image? My guess is that if you start with CM 6 (froyo?) you ll be done in a few days.
So please stop begging for an android dev and all the idle talk of how you think you might get things to work. Just get started with the cyanogenmod build guide already!
Again sorry for the rant
Click to expand...
Click to collapse
Ho year sure, downloading sources for a supported device and building the entire thing is not rocket science and can be easily done by following the wiki.
But building one for an unsupported device is an other story.
It requires a good knowledge and a lot of spare time.
The knowledge can be learned online but it requires a lot more spare time too and many of us don't have that spare time, unfortunately.
do you?
I'm not here to lecture people on how they spend their time. I simply want to point out that waiting for a dev to come along to fix your woes isn't the right way to get a project started. Besides, all the time spent on forum posts will nicely accumulate into a plentiful amount of time that can be spent on learning.
If there is an dev interested in building a rom, they will. No need to create some kind of placeholder containing information you think someone might want.
The open source way is to scratch your own itch.
Just on the technical side of things. If you port the cyanogen froyo version, you should simply be able to use the same drivers archos uses. So there isn't going to be any development involved, just compiling stuff.
As to your last question, I surely don't have to reply.
wvl0 said:
I'm not here to lecture people on how they spend their time.
Click to expand...
Click to collapse
I see , what are you here for ?
I simply want to point out that waiting for a dev to come along to fix your woes isn't the right way to get a project started. Besides, all the time spent on forum posts will nicely accumulate into a plentiful amount of time that can be spent on learning.
If there is an dev interested in building a rom, they will. No need to create some kind of placeholder containing information you think someone might want.
The open source way is to scratch your own itch.
Just on the technical side of things. If you port the cyanogen froyo version, you should simply be able to use the same drivers archos uses. So there isn't going to be any development involved, just compiling stuff.
As to your last question, I surely don't have to reply.
Click to expand...
Click to collapse
Well that was one of the useless posts found on this thread. Thank you for adding yours to the list
Hey guys, please join us at the Developer Thread.]
Its better to have only one thread
sibere said:
I see , what are you here for ?
Well that was one of the useless posts found on this thread. Thank you for adding yours to the list
Click to expand...
Click to collapse
Touché. I guess I'll just add what I learned then.
How to get your buildsystem up and running on Ubuntu Oneiric 64bit.
Before following this guide: http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Sholes
Do this first, just to avoid having to install individual packages later on:
Code:
add-apt-repository "deb http://archive.canonical.com/ maverick partner"
Code:
apt-get install bison build-essential curl flex g++-4.3-multilib gcc-4.3-multilib git-core g++-multilib gnupg gperf lib32ncurses5-dev lib32readline5-dev lib32z1-dev libc6-dev-i386 libesd0-dev libncurses5-dev libsdl1.2-dev libsdl-dev libwxgtk2.6-dev ncurses-dev pngcrush schedtool squashfs-tools sun-java6-jdk zip zlib1g-dev
I think I ran into compile issues with gcc-4.6, so I switched over to 4.4
Code:
rm /usr/bin/gcc
ln -s /usr/bin/gcc-4.4 /usr/bin/gcc
rm /usr/bin/g++
ln -s /usr/bin/g++-4.4 /usr/bin/g++
Then following this guide to get ADB running with your tablet:
http://forum.xda-developers.com/archive/index.php/t-892847.html
Now you can follow the Sholes build guide.
You might run into compile issues. This bug report includes a fix:
http://code.google.com/p/cyanogenmod/issues/detail?id=2455
and in case you run into this one:
frameworks/base/core/java/android/widget/ListView.java:3631: warning 13: Method android.widget.ListView.getCheckItemIds: (at)Deprecated annotation and (at)deprecated doc tag do not match
Checking API: checkapi-last
(unknown): error 17: Field org.apache.http.protocol.HTTP.EXPECT_CONTINUE has changed value from "100-Continue" to "100-continue"
Solve it by:
The error here is that someone needs to change the "100-continue" line on line 63 of file external/apache-http/src/org/apache/http/protocol/HTTP.java to "100-Continue"
And there's this one too:
Code:
host Executable: acp (out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp)
host SharedLib: libneo_cs (out/host/linux-x86/obj/lib/libneo_cs.so)
host C++: libutils <= frameworks/base/libs/utils/RefBase.cpp
frameworks/base/libs/utils/RefBase.cpp: In member function ‘void android::RefBase::weakref_type::trackMe(bool, bool)’:
frameworks/base/libs/utils/RefBase.cpp:483:67: error: passing ‘const android::RefBase::weakref_impl’ as ‘this’ argument of ‘void android::RefBase::weakref_impl::trackMe(bool, bool)’ discards qualifiers [-fpermissive]
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libutils_intermediates/RefBase.o] Error 1
make: *** Waiting for unfinished jobs....
Which can be fixed by edditing frameworks/base/libs/utils/Android.mk
Change the line:
Code:
LOCAL_CFLAGS += -DLIBUTILS_NATIVE=1 $(TOOL_CFLAGS)
To:
Code:
LOCAL_CFLAGS += -DLIBUTILS_NATIVE=1 $(TOOL_CFLAGS) -fpermissive
This should give you a few files that possibly can be flashed to our tablets:
Code:
Install system fs image: out/target/product/generic/system.img
Target ram disk: out/target/product/generic/ramdisk.img
Target userdata fs image: out/target/product/generic/userdata.img
Happy Hacking.
[edit]
Here's the result, just in case anyone is brave enough to flash it.
http://www.megaupload.com/?d=7PCNF69Z
[/edit]
[edit 2]
I guess the next step would be editing the img files to order to add the necessary drivers.
You need YAFFS2 support to mount these files. YAFFS2 isn't included in this version of ubuntu however.
So get yaffs2:
Code:
git clone ssh://www.aleph1.co.uk/home/aleph1/git/yaffs2
..and get a nice old kernel, considering the current version in git doesn't support 2.6.39 cleanly.
Code:
wget http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.35/linux-2.6.35.13.tar.bz2
untar your kernel sources.
then follow the instructions included with YAFFS:
Code:
cd yaffs-dir
./patch-ker.sh c m linux-tree
complains that linux-tree/fs/yaffs2 already exists
rm -rf linuux-tree/fs/yaffs2
./patch-ker.sh c m linux-tree
Copy your /boot/config-XXX to the directory you unpacked your kernel tarball.
run a:
Code:
make oldconfig
Now add YAFFS to your config using
Code:
make menuconfig
(Filesystems->Miscellaneous filesystems->yaffs)
..compile and reboot ubuntu into your own kernel containing yaffs2 support
mount your img files with
Code:
mount -o loop -t yaffs2 filename mountpoint
[/edit 2]
[edit 3]
So apparently building cyanogenmod doesn't mean you're building a full rom, you have to do the kernel seperately (as far as I can tell ATM):
http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source
there was no /proc/config.gz, so i ripped the urkdroid kernel .config file instead
also getting an arm toolchain working seemed tedious, so I followed the advice in on the wiki and got one from:
http://www.codesourcery.com/sgpp/lite/arm/portal/subscription3053
Had to tell the compile process where to find the arm compiler. Think I'm actually using one I downloaded from Ubuntu's repository instead of the one from the above link - oh well.
Code:
[email protected]:~/android/kernel/cm-kernel# make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -j`grep 'processor' /proc/cpuinfo | wc -l`
[/edit 3]
wvl0 said:
Touché. I guess I'll just add what I learned then.
How to get your buildsystem up and running on Ubuntu Oneiric 64bit.
Before following this guide: http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Sholes
Do this first, just to avoid having to install individual packages later on:
Code:
add-apt-repository "deb http://archive.canonical.com/ maverick partner"
Code:
apt-get install bison build-essential curl flex g++-4.3-multilib gcc-4.3-multilib git-core g++-multilib gnupg gperf lib32ncurses5-dev lib32readline5-dev lib32z1-dev libc6-dev-i386 libesd0-dev libncurses5-dev libsdl1.2-dev libsdl-dev libwxgtk2.6-dev ncurses-dev pngcrush schedtool squashfs-tools sun-java6-jdk zip zlib1g-dev
I think I ran into compile issues with gcc-4.6, so I switched over to 4.4
Code:
rm /usr/bin/gcc
ln -s /usr/bin/gcc-4.4 /usr/bin/gcc
rm /usr/bin/g++
ln -s /usr/bin/g++-4.4 /usr/bin/g++
Then following this guide to get ADB running with your tablet:
http://forum.xda-developers.com/archive/index.php/t-892847.html
Now you can follow the Sholes build guide.
You might run into compile issues. This bug report includes a fix:
http://code.google.com/p/cyanogenmod/issues/detail?id=2455
and in case you run into this one:
frameworks/base/core/java/android/widget/ListView.java:3631: warning 13: Method android.widget.ListView.getCheckItemIds: (at)Deprecated annotation and (at)deprecated doc tag do not match
Checking API: checkapi-last
(unknown): error 17: Field org.apache.http.protocol.HTTP.EXPECT_CONTINUE has changed value from "100-Continue" to "100-continue"
Solve it by:
The error here is that someone needs to change the "100-continue" line on line 63 of file external/apache-http/src/org/apache/http/protocol/HTTP.java to "100-Continue"
And there's this one too:
Code:
host Executable: acp (out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp)
host SharedLib: libneo_cs (out/host/linux-x86/obj/lib/libneo_cs.so)
host C++: libutils <= frameworks/base/libs/utils/RefBase.cpp
frameworks/base/libs/utils/RefBase.cpp: In member function ‘void android::RefBase::weakref_type::trackMe(bool, bool)’:
frameworks/base/libs/utils/RefBase.cpp:483:67: error: passing ‘const android::RefBase::weakref_impl’ as ‘this’ argument of ‘void android::RefBase::weakref_impl::trackMe(bool, bool)’ discards qualifiers [-fpermissive]
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libutils_intermediates/RefBase.o] Error 1
make: *** Waiting for unfinished jobs....
Which can be fixed by edditing frameworks/base/libs/utils/Android.mk
Change the line:
Code:
LOCAL_CFLAGS += -DLIBUTILS_NATIVE=1 $(TOOL_CFLAGS)
To:
Code:
LOCAL_CFLAGS += -DLIBUTILS_NATIVE=1 $(TOOL_CFLAGS) -fpermissive
This should give you a few files that possibly can be flashed to our tablets:
Code:
Install system fs image: out/target/product/generic/system.img
Target ram disk: out/target/product/generic/ramdisk.img
Target userdata fs image: out/target/product/generic/userdata.img
Happy Hacking.
[edit]
Here's the result, just in case anyone is brave enough to flash it.
http://www.megaupload.com/?d=7PCNF69Z
[/edit]
[edit 2]
I guess the next step would be editing the img files to order to add the necessary drivers.
You need YAFFS2 support to mount these files. YAFFS2 isn't included in this version of ubuntu however.
So get yaffs2:
Code:
git clone ssh://www.aleph1.co.uk/home/aleph1/git/yaffs2
..and get a nice old kernel, considering the current version in git doesn't support 2.6.39 cleanly.
Code:
wget http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.35/linux-2.6.35.13.tar.bz2
untar your kernel sources.
then follow the instructions included with YAFFS:
Code:
cd yaffs-dir
./patch-ker.sh c m linux-tree
complains that linux-tree/fs/yaffs2 already exists
rm -rf linuux-tree/fs/yaffs2
./patch-ker.sh c m linux-tree
Copy your /boot/config-XXX to the directory you unpacked your kernel tarball.
run a:
Code:
make oldconfig
Now add YAFFS to your config using
Code:
make menuconfig
(Filesystems->Miscellaneous filesystems->yaffs)
..compile and reboot ubuntu into your own kernel containing yaffs2 support
mount your img files with
Code:
mount -o loop -t yaffs2 filename mountpoint
[/edit 2]
[edit 3]
So apparently building cyanogenmod doesn't mean you're building a full rom, you have to do the kernel seperately (as far as I can tell ATM):
http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source
there was no /proc/config.gz, so i ripped the urkdroid kernel .config file instead
also getting an arm toolchain working seemed tedious, so I followed the advice in on the wiki and got one from:
http://www.codesourcery.com/sgpp/lite/arm/portal/subscription3053
Had to tell the compile process where to find the arm compiler. Think I'm actually using one I downloaded from Ubuntu's repository instead of the one from the above link - oh well.
Code:
[email protected]:~/android/kernel/cm-kernel# make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -j`grep 'processor' /proc/cpuinfo | wc -l`
[/edit 3]
Click to expand...
Click to collapse
That looks very good
wvl0 said:
Touché. I guess I'll just add what I learned then.
How to get your buildsystem up and running on Ubuntu Oneiric 64bit.
Before following this guide: http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Sholes
Click to expand...
Click to collapse
This may be my misunderstanding but I thought this guide only teaches you how to compile your own cyanogen build for the Motorola Sholes. It even states that you need a sholes with a working copy of cyanogenmod installed. This guide will only work for devices which are already supported by the cyanogenmod team, and is not a guide to build for unsupported devices. At least, that was my understanding from spending most of a day crawling around the cyanogenmod wiki.
Part of the build process involves pulling proprietary system files from the device. I guess one starting point would be to work out which files these are, then obtain the files from the archos. However, this stuff takes time to learn and I have very little to spare, like most. But then, neither am I asking someone else to do it, or sitting waiting for it.
If it comes, it comes...
Building for a compatible CPU architecture should at least give you a semi bootable ROM, after that you have to get the drivers in.
Considering we have the source and are using the same kernel versions, we can just recompile the drivers for our kernel.
wvl0 said:
Building for a compatible CPU architecture should at least give you a semi bootable ROM, after that you have to get the drivers in.
Considering we have the source and are using the same kernel versions, we can just recompile the drivers for our kernel.
Click to expand...
Click to collapse
Thank, you guys!
Could you please joyn my Thread for CM Developement, so other guys could help?
One thread is better than two
Finally, guys with Knowledge work on a CM, how can i help?
You could help by completely taking over, 'cause I don't want a cyanogen rom per se, I just want to show people that you don't have to be a developer to compile a rom.
wvl0 said:
You could help by completely taking over, 'cause I don't want a cyanogen rom per se, I just want to show people that you don't have to be a developer to compile a rom.
Click to expand...
Click to collapse
Okey, i understand^^
Could you tell me a few steps to compile the CM ?, i think the drivers we'll do later
Hi guys.
I'm getting problems when I try a make for my aosp build (for my p3113)
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1762641
and I git clone git://github.com/AOKP/android_device_samsung_espressowifi.git -b jb espressowifi
then ./extract-files.sh
when I'm extracting, I get some errors like
remote object '/system/lib/hw/lights.omap4.so' does not exist
341 KB/s (31320 bytes in 0.089s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
Is this normal?
Btw.. I continue with . build/envsetup.sh which is done successfully
and a lunch done successfully too..
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=full_espressowifi
TARGET_BUILD_VARIANT=userdebug
...
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=out
Finally I try a make -j4 otapackage and I got way too much errors and it stops
Can i have help please?
rainfalls said:
Hi guys.
I'm getting problems when I try a make for my aosp build (for my p3113)
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1762641
and I git clone git://github.com/AOKP/android_device_samsung_espressowifi.git -b jb espressowifi
then ./extract-files.sh
when I'm extracting, I get some errors like
remote object '/system/lib/hw/lights.omap4.so' does not exist
341 KB/s (31320 bytes in 0.089s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
Is this normal?
Btw.. I continue with . build/envsetup.sh which is done successfully
and a lunch done successfully too..
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=full_espressowifi
TARGET_BUILD_VARIANT=userdebug
...
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=out
Finally I try a make -j4 otapackage and I got way too much errors and it stops
Can i have help please?
Click to expand...
Click to collapse
To build it proper you need...
https://github.com/AOKP/android_device_samsung_p3100
https://github.com/AOKP/android_device_samsung_p3113
And:
https://github.com/AOKP/vendor_samsung
for the p31xx blobs
That should get you going.
cmenard said:
To build it proper you need...
github.com/AOKP/android_device_samsung_p3100
github.com/AOKP/android_device_samsung_p3113
And:
github.com/AOKP/vendor_samsung
for the p31xx blobs
That should get you going.
Click to expand...
Click to collapse
Thanks for the reply. So if I understand correctly, the samsung_espressowifi isn't the right one I need? so i went into device/samsung/ then I git clone p3100 and p3113 there am I right?
I was wondering where do I have to clone the vendor? directly into the samsung folder?
Thanks again for your help! Greatly appreciated
rainfalls said:
Thanks for the reply. So if I understand correctly, the samsung_espressowifi isn't the right one I need? so i went into device/samsung/ then I git clone p3100 and p3113 there am I right?
I was wondering where do I have to clone the vendor? directly into the samsung folder?
Thanks again for your help! Greatly appreciated
Click to expand...
Click to collapse
Yup. Just use the links I provided and you should be able to build just fine.
cmenard said:
Yup. Just use the links I provided and you should be able to build just fine.
Click to expand...
Click to collapse
Ok. I've started from scratch, deleted all the things in the samsung folders. i git clone p3113, p3100 and vendor. So now I have p3113,p3100 and samsung_vendor folders. Do I have to pull the p31xx folders from vendor and paste it directly into the samsung one?
when I do a ./extract-files.sh, i don't have any error until there ->
180 KB/s (14268 bytes in 0.077s)
453 KB/s (45380 bytes in 0.097s)
remote object '/system/lib/libsec-ril.so' does not exist
120 KB/s (9620 bytes in 0.077s)
172 KB/s (13768 bytes in 0.077s)
My p3113 is connected with usb debugging and appears correctly in adb devices.
Plus, nothing as been added into the p3113 folders at the end of the extract-files. At the end of the extract, should a vendorsetup.sh file supposed to be created?
Sorry but I'm a noob looking to learn something
thanks
EDIT: ok I found what was wrong with the vendor.. it's not going into /device/samsung folder but /vendor/samsung/p31xx right? still having the libsec-ril issue tho..
Do you have any hint cmenard?
You have two problems. One, you need to manually add a vendorsetup.sh file to the p3113 folder. Copy one from one of the other devices, and change its only line to read something like ADD_LUNCH_COMBO_p3113. Also, if extract-files.sh gave any errors, it didn't work. I've never had any luck with the default file, I always change the two lines that have adb pull to read cp /<romlocation>/system $file and extract a JB ROM to a folder on the disk.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
You have two problems. One, you need to manually add a vendorsetup.sh file to the p3113 folder. Copy one from one of the other devices, and change its only line to read something like ADD_LUNCH_COMBO_p3113. Also, if extract-files.sh gave any errors, it didn't work. I've never had any luck with the default file, I always change the two lines that have adb pull to read cp /<romlocation>/system $file and extract a JB ROM to a folder on the disk.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Yeah I already added the vendor setup file manually. I'll resync my jb tonight maybe something went wrong. I'll have to figure out the extract file problem too. All this when I'll get back from work lol
Why are you using extract-files.sh? The reason to use it is if you don't have the vendor files for the device already downloaded, and if you look at the vendor_samsung folder, it has all the stuff you need already. All you need to do is specify the device and build after you have the source downloaded.
imnuts said:
Why are you using extract-files.sh? The reason to use it is if you don't have the vendor files for the device already downloaded, and if you look at the vendor_samsung folder, it has all the stuff you need already. All you need to do is specify the device and build after you have the source downloaded.
Click to expand...
Click to collapse
I was using it because I've followed the guide step by step but I was asking the same question myself. I'll retry again as soon as I go back home
I'm getting a bit farther now. Not compiling yet but.. will do soon.. when I'm trying to do a make -j4 otapackage, I'm getting a series and I wrote them in pastebin
http://pastebin.com/f3UP50ku
I'm using:
[email protected]:~/android$ java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
I'm kinda lost
thanks for your help!
You have java virtual machine, but not java development kit. It's a bit difficult to find for Linux, but you can get it from http://www.cyberciti.biz/faq/howto-ubuntu-linux-install-configure-jdk-jre/
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
You have java virtual machine, but not java development kit. It's a bit difficult to find for Linux, but you can get it from http://www.cyberciti.biz/faq/howto-ubuntu-linux-install-configure-jdk-jre/
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Well.. this is what I've done so far
1. I downloaded java there http://www.oracle.com/technetwork/java/javase/downloads/jdk6-downloads-1637591.html (jdk-6u34-linux-x64.bin)
2. Went to terminal chmod +x jdk-6u34-linux-x64.bin
3. Then /.jdk-6u34-linux-x64.bin == install successfull
4. sudo update-alternatives --config java -> to choose the last jdk I've installed (by default, OpenJDK is installed with ubuntu instead of java jdk)
still having the same output with java -version
still having same issues
I got the same problem too when I'm trying to compile.
pastebin.co m/wcSZq6wq
it stops there and nothing.
I'm using p3113, p3110 and p3100 folder from /github.co m/AOKP/
Any idea someone?
Thanks
Finally I've been able to compile it through the end. Now time for debugging... I got a bootloop (surprising eh!?)
http ://pastebin.co m/e6STwe0E
Any help will be appreciated!
thanks!
EDIT: I've uploaded my work so far right there:
https ://docs.google.c om/file/d/0B6GzemNaw2dRY3BTT0tPWDdKYnM/edit
REMEMBER it's bootloading!
Nobody have a clue?
Building CM12 from source for the Nexus 6 Shamu!
Thanks goes to @scrosler and @GROGG88 and @sykopompos for their amazing guide
[Guide][1/19/2015] Buulding AOSP for the Nexus 6!
This guide will walk you through, how to build CM12 for the Nexus 6 from source. To complete this, you will need a PC with either virtual box setup and Ubuntu or duel boot Windows and Ubuntu. I recommend duel booting as it gets better results.
Ideally your PC will need a minimum of an I5 processor and 8GB of ram. I won't go into too much detail on how to setup Ubuntu on your PC. For this guide, you do need to know the basic commands and how to use Ubuntu.
This guide is very similar in process to @scrosler and @GROGG88 and @sykopompos amazing guide here: [Guide][1/19/2015] Building AOSP for the Nexus 6! Through the use of their guide and asking a lot of questions on their thread, I was able to learn how to build AOSP from source. My guide is to complement their guide and show you how to build CM12, I found switching from AOSP to CM12 fairly easy, but there were a few changes in the process.
For my guide I will be using CM12 build guide as reference for the commands. How To Build CyanogenMod Android for Google Nexus 6 ("shamu") Even their guide is not 100% up to date, so I had to make a few changes.
Disclaimer:
I am not responsible for any damage done to your device, thermal nuclear war etc. Please use at your own risk. Your warranty may be affected if you install a custom rom. I am also not responsible if you go over your payment plan when downloading the source code. It is large over 16gb so be careful!
Click to expand...
Click to collapse
So assuming you have Ubuntu 14.* set up, you will need to now set up your build environment:
First on their guide it talks about installing the SDK tools. You do not need these to build the ROM. You only really need ADB commands. I installed fastboot as well.
Install ADB command
Code:
sudo apt-get install android-tools-adb
Install Fastboot command
Code:
sudo apt-get install android-tools-fastboot
Install Java
Code:
sudo apt-get install openjdk-7-jdk
Setting up the build enviroment
Code:
bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev
If you have a 64bit PC install the following:
Code:
g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev
Setting your build directory - This can be any folder you want. for my example I will use android as my root folder. Remember that Ubuntu is case sensitive when switching folders.
Code:
mkdir -p ~/bin
mkdir -p ~/android
Install Repo
Code:
curl [URL]https://storage.googleapis.com/git-repo-downloads/repo[/URL] > ~/bin/repo
chmod a+x ~/bin/repo
Put the ~/bin directory in your path of execution - In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):
Code:
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
Now for the good bit! We are about to download the source for cm12. Warning: The download is large and will take a long time to download. I have a 38mb fiber connection and unlimited data plan, so it is ok for me to download. I believe the download is 16gb+ in size, so you will have to take this into consideration. Note: I will not be held responsible if you go over your payment plan with your service provider. This is were I have had to start changing the guide a bit as CM's document is for building CM11. It has not been updated to CM12 yet.
Identify Yourself to the Repo
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Initialize the CyanogenMod source repository
Code:
cd ~/android [B]- this is your root folder[/B]
repo init -u [URL]https://github.com/CyanogenMod/android.git[/URL] -b cm-12.0
Download the source code - Note this will take a while, as mentioned it is over 16gb in size. Even with my connection it takes about an hour and a half to download, so time for coffee!
Code:
repo sync
If repo sync errors and stops during download, don't worry you can simply run the command again and it will pick up were it left off. If you get a lot of errors during download, I recommend using
Code:
repo sync -j1
This seems to download the source better. When you have completed the download run it again, to make sure it completes with out any errors. This way you know you have downloaded the full source code.
Backup your home directory
Also at this point, what I do is make a backup using the inbuilt backup software in ubuntu. This backs up my entire home directory to a secondary hard drive I have set up in my PC. This way if I have any issues and need to start from scratch, I can simply delete my android directory, then restore from backup. I then have a fresh working copy and don't have to spend time downloading source from CM12 again. I would also recommend this as part of scrosler's guide as well, when you have finished downloading AOSP source.
Vendor and device specific files
Now this is were the cm12 guide starts to differ a bit from AOSP. AOSP you have to download the vendor files and extract them and then add in missing ones as well. CM12 differs here. At this point I would recommend having CM12 on your Nexus 6. It uses ADB to pull files from your phone and set up the device specific files and the vendor files. I found having CM12 on the phone made life easier at this point. You can use my ROM as an example here: [ROM][5.0.2][CM12 - Android L][LRX22G] Version 1.0.0 - [8/03/2015] - Native LED's
Code:
cd ~/android
source build/envsetup.sh
breakfast shamu
Extract proprietary blobs
Now ensure that your Nexus 6 is connected to your computer via the USB cable and that you are in the ~/android/device/moto/shamu directory, then run the extract-files.sh script
Code:
cd ~/android/device/moto/shamu
./extract-files.sh
Turn on caching to speed up build
You can speed up subsequent builds by adding: the following command to your to your .bashrc file To do this close your terminal window and then reopen and type ./.bashrc - A text editor will open. Add this line to the bottom of the page.
Code:
export USE_CCACHE=1
Close the text editor and save the file
Then in the command window type the following. CM12 recommend 50GB, but you can change to what ever you want.
Code:
prebuilts/misc/linux-x86/ccache/ccache -M 50G
Building CM12!!!!
Now you are all set to start building CM12. You have everything you need. So run the following commands:
Code:
cd ~\android
source build/envsetup.sh
brunch shamu
Thats it! CM12 is now building. This will take some time to build. I do recommend a duel boot PC as it works better than in Virtual Box. Even in my PC it takes about an hour and a half to do a fresh build and about 15 minutes to do a dirty build.
So once the build finishes you now have a flash-able version of CM12 from their latest source that you can flash on your Nexus 6 - Congratulations - you are now among the elite who can build their own ROM from source
The zip file is stored in the following directory:
Code:
cd ~/android/out/target/product/shamu/cm-12-20150308-UNOFFICIAL-shamu.zip
The file name will depend on the day you build the ROM, so it may be slightly different.
Here is an example output of a successful build of CM12!
{
"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"
}
Note of caution here:
Now that you have built CM12 as in AOSP I would not recommend flashing at this stage, it will make the following changes to your phone:
Install stock recovery
Encrypt your phone
To get around these we will need to make the following changes. See post 2 on how to make the changes.
As mentioned in post 1, after building CM12 you dont really want to flash it yet. It will:
Install stock recovery
Encrypt your phone - This is optional you can leave it to encrypt, but it is best to give the user the choice to do so or not.
In this post, I will also show you how to make other changes, eg: changing default wallpaper etc. I have a GitHub setup for this and all you need to do, is cherry-pick the commands into your folder, then compile the rom. My main source for all my changes are located here: https://github.com/StephenRJ - you are free to use these changes, but please give credit if you do.
Disable recovery.
Code:
cd ~/android/system/core/rootdir
git init
git fetch https://github.com/StephenRJ/cm12_system_core_rootdir.git
git cherry-pick f413ac907961c07f07f767ceb568deb4881e9f57
This next cherry-pick command will all the user the option of setting encryption on the phone, rather than it being automaticly encrypted.
Disable encryption
Code:
cd ~/android/device/moto/shamu
git init
git fetch https://github.com/StephenRJ/cm12_device_moto_shamu.git
git cherry-pick 7459b0d54102fbee27f363e7612b83f614a0f8c4
Now you have both of these disabled, you will need to do a fresh build again. To do this, I simply delete the out folder. Open file manager and go to android - then delete the folder out. This will let you make a full build again.
Close your terminal window and reopen.
Start a fresh build
Code:
cd ~/android
source build/envsetup.sh
brunch shamu
Now you can flash CM12 on your Nexus 6 Shamu Congratulations!!!!!
I will continue to add more fixes here has I find them.
Here are a couple of video tutorials I have found on setting up a basic Ubuntu enviroment.
Virtual Box: https://www.virtualbox.org/wiki/Downloads
Ubuntu ISO: http://www.ubuntu.com/download/desktop
Tutorial on setting up Virtual box on Windows 7 / 8
Duel boot Windows 8 and Ubuntu - Prefered method
Disclaimer
I am not responsable for anything that happens to your PC during the install of Ubuntu. I recommend taking a full backup first before installing a second operating system. Do this at your own risk. If your are not sure about installing different oprating systems, use the first method as it is safer
Click to expand...
Click to collapse
Change Log
Version 1.0.0
- Initial release
Please feel free to share here and help each other. I hope this guide is as useful to users as scrosler's has been. With out his help and guide, I would have never have been able to learn how to build AOSP for this amazing phone. I hope this guide gives more users the chance to build CM12 as well.
Using this guide, I have built and released a ROM. Please have a look here: [ROM][5.0.2][CM12 - Android L][LRX22G] Version 1.0.0 - [8/03/2015] - Native LED's
Please feel free to try it and report back!
I would suggest using a local manifest and getting your vendor files from TheMuppets repo. That way you stay up to date on any changes that are made.
Thanks for the tip. Could you explain a bit more on how to do that? I had installed an existing stock CM12 rom on the phone and then used the commands to remotely pull the files from it.
Stephen said:
Thanks for the tip. Could you explain a bit more on how to do that? I had installed an existing stock CM12 rom on the phone and then used the commands to remotely pull the files from it.
Click to expand...
Click to collapse
CM's wiki has a pretty good guide.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests#The_local_manifest
Also, not sure the recovery thing mentioned is an issue. I've been building CM for this device for nearly 2 months and have had no issues with TWRP being replaced.
Excellent guide! Now I just need a Nexus 6... :silly:
I love seeing useful tutorials being posted. That's why I got involved in @scrosler's thread. Nice job!!
akellar said:
Also, not sure the recovery thing mentioned is an issue. I've been building CM for this device for nearly 2 months and have had no issues with TWRP being replaced.
Click to expand...
Click to collapse
Agreed. I was just about to post that too. Most custom ROMs remove the stock recovery so custom recoveries don't get overwritten.
Very cool ill try this tomorrow! Can you maybe add a section on how to find and add nice cherrypicks?
Regarding the recovery I added that in on the safe side. I know if you download the full stock cm12 from their website it does change the recovery and encrypt the device.
I will be adding a few more cherry picks at some stage, I am working on something rather cool at the minute.
Thanks for doing this. I've followed a few guides but every one wasn't quite correct. I can't wait to test this out soon.
- Aaron
Very well done Stephen! I read as many of these as I can and always learn something new. This is very well written and I hope all of us can add and help each other as we progress with the N6!:good:
Hey,
I have built AOSP for Nexus devices for a long time, but have yet to run into this issue.
When I run "brunch shamu", it fails, referancing generic "goldfish"? is that just a generic device name?
Here is the build process:
[email protected]:~/android$ source build/envsetup.sh
including device/moto/shamu/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
[email protected]:~/android$ brunch shamu
including vendor/cm/vendorsetup.sh
Looking for dependencies
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.0.2
CM_VERSION=12-20150315-UNOFFICIAL-shamu
TARGET_PRODUCT=cm_shamu
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.16.0-31-generic-x86_64-with-Ubuntu-14.10-utopic
HOST_BUILD_TYPE=release
BUILD_ID=LRX22G
OUT_DIR=/home/npjohnson/android/out
============================================
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.0.2
CM_VERSION=12-20150315-UNOFFICIAL-shamu
TARGET_PRODUCT=cm_shamu
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.16.0-31-generic-x86_64-with-Ubuntu-14.10-utopic
HOST_BUILD_TYPE=release
BUILD_ID=LRX22G
OUT_DIR=/home/npjohnson/android/out
============================================
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
"ebtables is disabled on this build"
find: `dummy': No such file or directory
build/core/base_rules.mk:154: *** system/device/generic/goldfish/audio: MODULE.TARGET.SHARED_LIBRARIES.audio.primary.goldfish already defined by device/generic/goldfish/audio. Stop.
Not sure, haven't seen that error before. Have you added any extra mods into the rom? One of those could be causing the issue. It could also be an issue with CM12 its self. Some times they do add code in and it can cause errors.
I would try downloading source again and see if there is any difference.
Stephen said:
Not sure, haven't seen that error before. Have you added any extra mods into the rom? One of those could be causing the issue. It could also be an issue with CM12 its self. Some times they do add code in and it can cause errors.
I would try downloading source again and see if there is any difference.
Click to expand...
Click to collapse
Will do. I am building on Ubuntu 14.10. That should be OK to use correct? Fresh install, then followed steps in the OP.
npjohnson said:
Will do. I am building on Ubuntu 14.10. That should be OK to use correct? Fresh install, then followed steps in the OP.
Click to expand...
Click to collapse
Yes. Oh what setup are you using. Virtual Box or duel boot. I did have problems with Virtual box and switched to duel boot. Found it to be more stable.
Stephen said:
Yes. Oh what setup are you using. Virtual Box or duel boot. I did have problems with Virtual box and switched to duel boot. Found it to be more stable.
Click to expand...
Click to collapse
Dual boot.
Any idea why my builds come in at around 387MB but the official nightlies are ~443MB?
Posting here because the general forums are down currently.
So for the past week or so, both me and J0SH1X have been working on an Android Oreo 8.1 port for the HD2,
So far we have gotten to a point where the ROM will start booting and you can log it via ADB which was step 1 of things we had to fix however soon we encountered a bug with the display which seems unfixable, the issue here being to do with the Adreno 200 blobs we are using. So far we have fixed the display HAL and tried many combinations of blobs with source side patches on top just to end up in the same position. The issue seems to stem from GL_OUT_OF_MEMORY errors or surfaceflinger dequeuing 2 buffers when our GPU will only support 1, despite many patches this same issue still seems to exist on our blobs from macs18max on Nougat.
We haven't given up yet so this is a call out to other devs who are much more knowledgeable on this kind of stuff than we are. Our trees and patches are fully public and some may have noticed that we have been actively developing at https://github.com/qsd8k-legacy for the HD2. If you are a dev who knows more about this then attached I have posted some logs from our progress so far, feel free to PM me either here on XDA (slow replies though) or on Telegram (@TheOGLunarixus).
To install ROM's made from our trees you will need to repartition the SD card still and use blackClK + the TWRP image attached (repartition your SD card in macs TWRP first) (devs only)
TWRP download link: https://drive.google.com/open?id=139hIx_oBBGLXfdMyJdZc63Ma_zgShnnH
Credit goes to rINanDO and macs18max (+ his team) for the kernel 3.0 and HTC HD2 work they've been doing and Renan Queiroz for helping with the initial bring-up.
Hopefully soon we can follow this project up with good news.
Log for oom error: https://hastebin.com/ugenalesuv.pl
Full boot log with display issue (omx crash has since been fixed): https://hastebin.com/sisugukaqi.bash
WOW!!! i wish you guys best of luck... I still have my HD2 running, its my backup phone. If there is anything I can do for you guys, hit me up!
I have 2 HD2 up and running. One has broken USB port though. These phones are so cheap now on eBay currently glad to see someone else trying to get a newer Android build running on this phone. Bookmarked your sources I am installing Ubuntu 14.04 to compile a build right now.
Great to see activity again on the HD2 forums ! The HD2 lovers are all here to help I'm sure ?
I currently have sources for Lineage 15.1 Android 8.1 synced but am currently battling through local_manifest.xml and adding lineage_leo as a device to lunch. If anyone wants to lend a hand message me.
build/core/product_config.mk:238: *** Can not locate config makefile for product "leo". Stop.
Device leo not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_htc_leo
Default revision: lineage-15.1
Checking branch info
Using fallback branch: cm-7.1.0
Checking if device/htc/leo is fetched from android_device_htc_leo
Adding dependency: LineageOS/android_device_htc_leo -> device/htc/leo
Using fallback branch cm-7.1.0 for android_device_htc_leo
Syncing repository to retrieve project.
repo: warning: Python 2 is no longer supported; Please upgrade to Python 3.6+.
error: info is different in /home/chronic/android/lineage/.repo/projects/device/htc/leo.git vs /home/chronic/android/lineage/.repo/project-objects/LineageOS/android_device_htc_leo.git
Retrying clone after deleting /home/chronic/android/lineage/.repo/projects/device/htc/leo.git
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
Server does not provide clone.bundle; ignoring.
fatal: Couldn't find remote ref refs/heads/cm-7.1.0
fatal: Couldn't find remote ref refs/heads/cm-7.1.0
error: Cannot fetch LineageOS/android_device_htc_leo from https://github.com/LineageOS/android_device_htc_leo
Fetching projects: 100% (1/1), done.
error: Cannot checkout LineageOS/android_device_htc_leo: ManifestInvalidRevisionError: revision cm-7.1.0 in LineageOS/android_device_htc_leo not found
error: in `sync --force-sync device/htc/leo`: revision cm-7.1.0 in LineageOS/android_device_htc_leo not found
Repository synced!
Looking for dependencies in device/htc/leo
device/htc/leo has no additional dependencies.
Done
build/core/product_config.mk:238: *** Can not locate config makefile for product "leo". Stop.
build/core/product_config.mk:238: *** Can not locate config makefile for product "leo". Stop.
** Don't have a product spec for: 'leo'
** Do you have the right repo manifest?
Well I got a bit further in the build.......
[email protected]:~/android/lineage$ brunch htcleo
including vendor/lineage/vendorsetup.sh
Trying dependencies-only mode on a non-existing device tree?
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=8.1.0
LINEAGE_VERSION=15.1-20200224-UNOFFICIAL-htcleo
TARGET_PRODUCT=lineage_htcleo
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_PLATFORM_VERSION=OPM1
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.15.0-45-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=OPM7.181205.001
OUT_DIR=/home/chronic/android/lineage/out
AUX_OS_VARIANT_LIST=
============================================
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=8.1.0
TARGET_PRODUCT=lineage_htcleo
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.15.0-45-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=OPM7.181205.001
OUT_DIR=/home/chronic/android/lineage/out
============================================
ninja: no work to do.
ninja: no work to do.
/home/chronic/android/lineage/out/build-lineage_htcleo.ninja is missing, regenerating...
[742/1071] including ./system/sepolicy/Android.mk ...
./system/sepolicy/Android.mk:99: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[1071/1071] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
[ 99% 1276/1277] glob vendor/qcom/opensource/interfaces/wifi/supplicant/1.0/Android.bp
ninja: error: 'frameworks/native/data/etc/go_handheld_core_hardware.xml', needed by '/home/chronic/android/lineage/out/target/product/htcleo/system/etc/permissions/handheld_core_hardware.xml', missing and no known rule to make it
09:46:19 ninja failed with: exit status 1
#### failed to build some targets (02:31 (mm:ss)) ####
chronic8000 said:
Well I got a bit further in the build.......
[email protected]:~/android/lineage$ brunch htcleo
including vendor/lineage/vendorsetup.sh
Trying dependencies-only mode on a non-existing device tree?
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=8.1.0
LINEAGE_VERSION=15.1-20200224-UNOFFICIAL-htcleo
TARGET_PRODUCT=lineage_htcleo
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_PLATFORM_VERSION=OPM1
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.15.0-45-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=OPM7.181205.001
OUT_DIR=/home/chronic/android/lineage/out
AUX_OS_VARIANT_LIST=
============================================
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=8.1.0
TARGET_PRODUCT=lineage_htcleo
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.15.0-45-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=OPM7.181205.001
OUT_DIR=/home/chronic/android/lineage/out
============================================
ninja: no work to do.
ninja: no work to do.
/home/chronic/android/lineage/out/build-lineage_htcleo.ninja is missing, regenerating...
[742/1071] including ./system/sepolicy/Android.mk ...
./system/sepolicy/Android.mk:99: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[1071/1071] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
[ 99% 1276/1277] glob vendor/qcom/opensource/interfaces/wifi/supplicant/1.0/Android.bp
ninja: error: 'frameworks/native/data/etc/go_handheld_core_hardware.xml', needed by '/home/chronic/android/lineage/out/target/product/htcleo/system/etc/permissions/handheld_core_hardware.xml', missing and no known rule to make it
09:46:19 ninja failed with: exit status 1
#### failed to build some targets (02:31 (mm:ss)) ####
Click to expand...
Click to collapse
remove go_ from go_handheld_core in device.mk so it will be handheld_core
Well LineageOS 15.1 has just completed compiling. If anyone is actually here with an HD2 and wants to test here is the ZIP file. https://1drv.ms/u/s!Am0vXJlBysw-k8dZxT9zuRErlGUY1g?e=fQjRz0
Bear in mind I haven't even tried this on my device yet it literally finished compiling 5 minutes ago so it is at your own risk.
---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------
Sorted it out anyway now. Completed and completely untested ROM is above.
J0SH1X said:
remove go_ from go_handheld_core in device.mk so it will be handheld_core
Click to expand...
Click to collapse
am I right in thinking this is run solely from the sd card on 2 ext4 partitions? It looks that way from the updater script
Thank you chronic8000
hello , i have try but no succes !
i have two ext4 partitions on my sdcard .
it's a long time without my hd2 and perhaps i 'm wrong
Robbie P said:
am I right in thinking this is run solely from the sd card on 2 ext4 partitions? It looks that way from the updater script
Thank you chronic8000
Click to expand...
Click to collapse
I think so yes. I don't even know if this ROM actually works yet this is just the first build and I am yet to get recovery to flash it. Been too busy to test but when I first tried to flash using cLK black and TWRP it said "This rom is meant for htcleo and this device is . - failed" but there is a workaround for that using terminal in TWRP according to the XDA bible. I changed my TWRP before I discovered that though and now I can't flash anything till I change it back as it can't access any partitions for some reason I am yet to figure out. Getting used to the HD2 again after all these years lol.
ROM forum:
https://forum.xda-developers.com/hd2-android/nand-dev/lineageos-15-1-android-8-1-htc-hd2-t4058163.
---------- Post added at 02:50 PM ---------- Previous post was at 02:47 PM ----------
Robbie P said:
Thank you chronic8000
Click to expand...
Click to collapse
Don't thank me yet not even got it flashed on a phone yet
philipped346 said:
hello , i have try but no succes !
i have two ext4 partitions on my sdcard .
it's a long time without my hd2 and perhaps i 'm wrong
Click to expand...
Click to collapse
That is the same error I got working on a fix now...
sorry, looking at fstab, the rom is loaded from emmc. However the Leo uses mtd so we either need to edit fstab to load from mtdblock0p1 etc. or preferably edit fstab to use sdcard ext4 partitions. And edit the updater script to suit
Robbie P said:
sorry, looking at fstab, the rom is loaded from emmc. However the Leo uses mtd so we either need to edit fstab to load from mtdblock0p1 etc. or preferably edit fstab to use sdcard ext4 partitions. And edit the updater script to suit
Click to expand...
Click to collapse
Cool we are getting somewhere I can edit and recompile if needed. I am really new to Android ROM development but nice to see someone willing to help get this working. Better to edit the ZIP directly or edit and recompile?
chronic8000 said:
That is the same error I got working on a fix now...
Click to expand...
Click to collapse
"# ro.build.product is obsolete; use ro.product.device" from the build.prop, so changing the updater script (in META-INF\com\google\android\) should fix this
---------- Post added at 04:31 PM ---------- Previous post was at 04:28 PM ----------
chronic8000 said:
Cool we are getting somewhere I can edit and recompile if needed. I am really new to Android ROM development but nice to see someone willing to help get this working. Better to edit the ZIP directly or edit and recompile?
Click to expand...
Click to collapse
I can try and edit the zip, but will take a bit of time as I need to get magldr on phone to use a script to edit the ramdisk. Also need to tidy up before the missus gets back and revise for a sort of exam on Monday. But am excited, so might give it a go
---------- Post added at 04:34 PM ---------- Previous post was at 04:31 PM ----------
how long does recompiling take?
this is the way i developed the rom and flashed and tested it on my own hd2
chronic8000 said:
Well LineageOS 15.1 has just completed compiling. If anyone is actually here with an HD2 and wants to test here is the ZIP file. https://1drv.ms/u/s!Am0vXJlBysw-k8dZxT9zuRErlGUY1g?e=fQjRz0
Bear in mind I haven't even tried this on my device yet it literally finished compiling 5 minutes ago so it is at your own risk.
---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------
Sorted it out anyway now. Completed and completely untested ROM is above.
Click to expand...
Click to collapse
well this is not likely to pass the htc logo at all also no adb will work , it needs multiple patches also graphic stack (adreno gpu firmware) is badly broken and leaks thus it will always report out of memory , i wasnt able to fix this even tho trying multiple patches with lunarixus.
also adb needs a patch to work on los if you want better compatibility use android unlegacy project thats what lunarixus and i used for our last tests and it seemed to have slightly better compatibility with older devices then los
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
chronic8000 said:
I think so yes. I don't even know if this ROM actually works yet this is just the first build and I am yet to get recovery to flash it. Been too busy to test but when I first tried to flash using cLK black and TWRP it said "This rom is meant for htcleo and this device is . - failed" but there is a workaround for that using terminal in TWRP according to the XDA bible. I changed my TWRP before I discovered that though and now I can't flash anything till I change it back as it can't access any partitions for some reason I am yet to figure out. Getting used to the HD2 again after all these years lol.
ROM forum:
https://forum.xda-developers.com/hd2-android/nand-dev/lineageos-15-1-android-8-1-htc-hd2-t4058163.
---------- Post added at 02:50 PM ---------- Previous post was at 02:47 PM ----------
Don't thank me yet not even got it flashed on a phone yet
Click to expand...
Click to collapse
comment out the otapackage device stuff in device/htc/htcleo/BoardConfig.mk then it will flash properly
---------- Post added at 05:26 PM ---------- Previous post was at 05:18 PM ----------
1. flash blackCLK with embedded twrp
2. in blackCLK settings make mtd as following BOOT: 15MB RECOVERY: 15MB the rest doesnt matter
3. push this twrp to the sdcard while booted into blackCLK embedded twrp open a shell by typing adb shell and type there "erase_image recovery && flash_image recovery /sdcard/twrp.img"
4.shut down your hd2 and insert the sdcard into your pc partition it as following i used a 16gb card so set this as you need but keep system 1024 my partition layout is 8192MB FAT32 SD-Data;6656MB EXT4 DATA;1024MB EXT4 SYSTEM;512MB EXT4 CACHE
5. reinsert the sd and boot into twrp you will see it changed now , wipe data cache and system by using change fs/repair function of wipe menu
6. reboot twrp
7. remove the top line and the line writing boot.img of updater-script and save
8. copy the rom over to your phone and flash it
9. extract boot.img from the zip and push it to sdcard in updated twrp, open a shell with adb shell and type "erase_image boot && flash_image boot /sdcard/boot.img
I'd like to clarify
There is a reason I didn't release the zips for this ROM, because it does not boot at all, it gets ADB with some hacks and that's it, this thread is a callout for developers to help us with the display stack, we have not announced that this is working at all.
Can you make android 9 and 10 custom rom for HTC HD2
What's the lightest and most stable version of Android that the HD2 can run atm? It might be worth it to go back and improve something, since current versions are so demanding.
Kovaelin said:
What's the lightest and most stable version of Android that the HD2 can run atm? It might be worth it to go back and improve something, since current versions are so demanding.
Click to expand...
Click to collapse
The android version that ran at its peak (in terms of stability and speed) was gingerbread (GB)... after that, kitkat was good, but not as fast as GB.