[HELP] Device tree problem in AOSP 8.1 ( Galaxy Grand Prime) - Galaxy Grand Prime Android Development

I am facing problem in building AOSP 18.1 i added the device tree given by remelia but i am facing error when i lunch.
Code:
$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_mips-eng
4. aosp_mips64-eng
5. aosp_x86-eng
6. aosp_x86_64-eng
7. full_fugu-userdebug
8. aosp_fugu-userdebug
9. aosp_car_emu_arm-userdebug
10. aosp_car_emu_arm64-userdebug
11. aosp_car_emu_x86-userdebug
12. aosp_car_emu_x86_64-userdebug
13. mini_emulator_arm64-userdebug
14. m_e_arm-userdebug
15. m_e_mips64-eng
16. m_e_mips-userdebug
17. mini_emulator_x86_64-userdebug
18. mini_emulator_x86-userdebug
19. uml-userdebug
20. aosp_dragon-userdebug
21. aosp_dragon-eng
22. aosp_marlin-userdebug
23. aosp_marlin_svelte-userdebug
24. aosp_sailfish-userdebug
25. aosp_walleye-userdebug
26. aosp_walleye_test-userdebug
27. aosp_taimen-userdebug
28. aosp_angler-userdebug
29. aosp_bullhead-userdebug
30. aosp_bullhead_svelte-userdebug
31. hikey-userdebug
32. hikey960-userdebug
33. lineage_grandprimeve3g-userdebug
34. aosp_grandprimeve3g-userdebug
35. cos_grandprimeve3g-userdebug
36. omni_grandprimeve3g-userdebug
37. du_grandprimeve3h-userdebug
38. aos_grandprimeve3g-userdebug
Which would you like? [aosp_arm-eng] 34
build/core/product_config.mk:232: *** _nic.PRODUCTS.[[device/samsung/grandprimeve3g/aosp_grandprimeve3g.mk]]: "vendor/aosp/common.mk" does not exist. Stop.

@remilia15 @naimrlet
Help him , please

I think this thread is on wrong section now . Actually you need to post this in Q&A section

herawais said:
Code:
33. lineage_grandprimeve3g-userdebug
34. aosp_grandprimeve3g-userdebug
35. cos_grandprimeve3g-userdebug
36. omni_grandprimeve3g-userdebug
37. du_grandprimeve3h-userdebug
38. aos_grandprimeve3g-userdebug
Click to expand...
Click to collapse
LOL, my device tree doesn't have too many recipes for lunch like this
Are you sure you didn't copy-pasta'd somewhere else?

remilia15 said:
LOL, my device tree doesn't have too many recipes for lunch like this
Are you sure you didn't copy-pasta'd somewhere else?
Click to expand...
Click to collapse
Yes i copy pasted someone's but how to delete other's recepies? can you please guide me as i am new in this work. what is the solution to the error showing .
Thanks

remilia15 said:
LOL, my device tree doesn't have too many recipes for lunch like this
Are you sure you didn't copy-pasta'd somewhere else?
Click to expand...
Click to collapse
these are new recipes and new error occurred.
Code:
33. aosp_grandprimeve3g-eng
34. aosp_grandprimeve3g-user
35. aosp_grandprimeve3g-userdebug
Which would you like? [aosp_arm-eng] 35
build/core/product_config.mk:232: *** _nic.PRODUCTS.[[device/samsung/grandprimeve3g/aosp_grandprimeve3g.mk]]: "/build/target/product/aosp_base_telephony.mk" does not exist. Stop.

@herawis
Ask any one of moderators to move the thread to Q&A section

unknown said:
I think this thread is on wrong section now . Actually you need to post this in Q&A section
Click to expand...
Click to collapse
respected member would you please move this post to Q&A section..

herawais said:
respected member would you please move this post to Q&A section..
Click to expand...
Click to collapse
Ask a moderator to do it
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
herawais said:
these are new recipes and new error occurred.
Code:
33. aosp_grandprimeve3g-eng
34. aosp_grandprimeve3g-user
35. aosp_grandprimeve3g-userdebug
Which would you like? [aosp_arm-eng] 35
build/core/product_config.mk:232: *** _nic.PRODUCTS.[[device/samsung/grandprimeve3g/aosp_grandprimeve3g.mk]]: "/build/target/product/aosp_base_telephony.mk" does not exist. Stop.
Click to expand...
Click to collapse
Edit that .mk file
maybe change it to full_base_telephony
And aosp has aosp_base_telephony , are you sure that you have synced the source completely ?? @herawais

If you are trying to build vanilla aosp with cm (or cm-based) device trees, you are very likely going to have to edit the device tree just to get it to build.

Synthetic.Nightmare said:
If you are trying to build vanilla aosp with cm (or cm-based) device trees, you are very likely going to have to edit the device tree just to get it to build.
Click to expand...
Click to collapse
I dont know how to edit the the files and which file should edit? This is the device tree for aosp 8.0 and i am using it for aosp 8.1

herawais said:
I dont know how to edit the the files and which file should edit? This is the device tree for aosp 8.0 and i am using it for aosp 8.1
Click to expand...
Click to collapse
I wouldnt know what all youd have to modify, but based on your build errors, id start with the Makefiles.
With that in consideration, id recommend you try building something based on lineage (or just lineage, itself) and start modifying that, just so you can start getting an idea of how aosp is compiled. Theres a lot to take in.

herawais said:
I dont know how to edit the the files and which file should edit? This is the device tree for aosp 8.0 and i am using it for aosp 8.1
Click to expand...
Click to collapse
Just use 8.1 kernel to build it

Related

Error on envsetup.sh

hi guys . i wanna build omfgb for galaxy ace .. but i have some problem :
this terminal log :
[email protected]:~/omfgb/omfgb$ . build/envsetup.sh
including device/samsung/android_device_samsung_cooper/vendorsetup.sh
including vendor/omfgb/vendorsetup.sh
[email protected]:~/omfgb/omfgb$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
2. cooper-eng
3. cooper-userdebug
4. OMFGB_ace-eng
5. OMFGB_desirec-eng
6. OMFGB_heroc-eng
7. OMFGB_inc-eng
8. OMFGB_mecha-eng
9. OMFGB_sholes-eng
10. OMFGB_supersonic-eng
11. OMFGB_fascinatemtd-eng
12. OMFGB_mesmerizemtd-eng
13. OMFGB_showcasemtd-eng
14. OMFGB_vibrantmtd-eng
15. OMFGB_vivow-eng
16. OMFGB_shadow-eng
17. OMFGB_p999-eng
Which would you like? [full-eng] 3
build/core/config.mk:136: *** No config file found for cooper . Stop.
** Don't have a product spec for: 'cooper'
** Do you have the right repo manifest?
[email protected]:~/omfgb/omfgb$
Click to expand...
Click to collapse
any people can help me ?
thanks before btw sorry for my bad english
No config file present...
I got transformed into a potato while writing this post..
Prawesome said:
No config file present...
I got transformed into a potato while writing this post..
Click to expand...
Click to collapse
can you help to find config file ??

[RECOVERY] TWRP Recovery 2.6.3.0 | MoltenMotherBoard

FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!​
Credits:
MoltenMotherBoard team!
Downloads:
TWRP Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Fixed partition table
Code updates from TWRP, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0
Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/twrp.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/twrp.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------
I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources.
Anyway, it would be appreciated if you report bugs here, so that I can check them!
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
EB20XY said:
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
Click to expand...
Click to collapse
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
negativman said:
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
Click to expand...
Click to collapse
Don't understand. What are you meaning?
mackief said:
Don't understand. What are you meaning?
Click to expand...
Click to collapse
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
negativman said:
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
Click to expand...
Click to collapse
OK. I'll check!
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
mackief said:
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Click to expand...
Click to collapse
what is exactly is the difference for kitkat ? Are the partitions different ?
EB20XY said:
what is exactly is the difference for kitkat ? Are the partitions different ?
Click to expand...
Click to collapse
Nope. At recovery-level, the biggest differencies are in the binary commands, then in Edify scripts.
Nothing relevant, but if you wanna flash a KitKat rom, you HAVE to use a 'KitKat' recovery!
mackief said:
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
Click to expand...
Click to collapse
And where can I download it? Discovered the mistake about which I spoke to you?
negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
It should be a still-working-on broken feature by team.
It's a early recovery port, as the team is still making its own modifies on 4.4 code.
BTW, today I should release newer build
negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
Ok, I was wrong. That's an issue caused by the fact that TWRP doesn't support fstab v2 - the partition table - and, as our device tree is using this version of table, TWRP didn't load our partition and couldn't backup anything.
Just released new build of CWM.
Changelog:
Fixed partition table
Code updates from TWRP, Google
Follow us on Google+, Facebook & Twitter!
Cheers.
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Adam77Root said:
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Click to expand...
Click to collapse
Actually, they're based on 4.4 . No new features, nothing new.
Then, my device tree with CM9 has nothing to do with these recoveries; of course I'll add kernel sources and so on.
---------- Post added at 08:57 PM ---------- Previous post was at 08:46 PM ----------
Just updated OP and sources. Thanks for the report.
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
laufersteppenwolf said:
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
Click to expand...
Click to collapse
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
mackief said:
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
Click to expand...
Click to collapse
You know, that's exactly the problem/difficulty of being a mod in his own section
I personally do not have a problem with it, but if someone wants to, he can see it as spamming, which could get you in trouble some time.
So I usually try to avoid such situations as soon as possible
So all in all it's your call. I have no problem giving you access to my thread, so we both can keep on deving on it, but it would be less work for both of us if we'd share it. (which I actually could use ATM )
So you tell me what you want to do

[TUTORIAL] How to compile Lollipop roms for Zenfone 5 (x86 chip)

Good afternoon, guys, I created a tutorial how to compile roms for Zenfone 5 (x86 chip).
NOTE:
I will use my AOSP device tree but also this tutorial can be used for CM building with another devide tree.
Lets begin.
STEP #1
I recommend you to use this device tree:
(for AOSP)
https://github.com/tank0412/aosp_device_asus_a500cg
https://github.com/tank0412/android_vendor_asus_a500cg
(for CM)
https://github.com/tank0412/android_device_asus_a500cg-1
https://github.com/tank0412/android_vendor_asus_a500cg
Put device folder here:
*AndroidSource-folder*/device/asus
full path:
*AndroidSource-folder*/device/asus/a500cg
Put vendor folder here:
*AndroidSource-folder*/vendor/asus
full path:
*AndroidSource-folder*/vendor/asus/a500cg
STEP #2
Go to *AndroidSource-folder*/hardware and delete intel folder.
Add there this folder:
https://github.com/tank0412/android_hardware_intel-1
Rename it to Intel.
STEP #3
open Terminal
cd *AndroidSource-folder*
. build/envsetup.sh
lunch cm_a500cg-userdebug
make -j6
ERROR 1:
If you get errors due to inline kernel building, you should disable it.
ERROR 2:
If you use device tree by quanganh2627 and you got errors due to device/intel/common folder or due to this:
linux/modules/PRIVATE/fm/broadcom/bt_protocol_driver/AndroidBt.mk
In this case you should open BoardConfig.mk file in the device folder and comment needed lines like here:
#include device/intel/common/gps/GpsBoardConfig.mk
Credits:
@dgadelha (becuase he published his intel/hardware folder)
XDA:DevDB Information
How to compile roms for Zenfone 5 (x86 chip), Tool/Utility for the Asus Zenfone 5
Contributors
tank0412
Version Information
Status: Testing
Created 2016-02-11
Last Updated 2016-07-08
to add the device tree, I need to do git clone https://github.com/quanganh2627/android_vendor_asus_a500cg.git in intel common folder?
TecnoTailsPlays said:
to add the device tree, I need to do git clone https://github.com/quanganh2627/android_vendor_asus_a500cg.git in intel common folder?
Click to expand...
Click to collapse
What? NO no and no.
Wait. I will add more info.
UPD^ More info is added.
tank0412 said:
What? NO no and no.
Wait. I will add more info.
UPD^ More info is added.
Click to expand...
Click to collapse
ok, so what I need to do to add the device tree in a500cg folder? git clone? what command?
---------- Post added at 12:03 ---------- Previous post was at 12:02 ----------
tank0412 said:
What? NO no and no.
Wait. I will add more info.
UPD^ More info is added.
Click to expand...
Click to collapse
and can you add more information about step 4?
TecnoTailsPlays said:
ok, so what I need to do to add the device tree in a500cg folder? git clone? what command?
---------- Post added at 12:03 ---------- Previous post was at 12:02 ----------
and can you add more information about step 4?
Click to expand...
Click to collapse
I think that it is enough. What is your problem?
tank0412 said:
I think that it is enough. What is your problem?
Click to expand...
Click to collapse
what is comment? and what command I tipe to add the device tree?
TecnoTailsPlays said:
what is comment? and what command I tipe to add the device tree?
Click to expand...
Click to collapse
Just unpack archive with device folder and put it in the path above.
To comment just add this symbol "#" to every string.(line)
I provided an example.
You will get something like this:
Code:
#ifeq ($(INTEL_VA),true)
#
#include $(call all-subdir-makefiles)
#
#endif
It was:
Code:
ifeq ($(INTEL_VA),true)
include $(call all-subdir-makefiles)
endif
tank0412 said:
Just unpack archive with device folder and put it in the path above.
To comment just add this symbol "#" to every string.(line)
I provided an example.
You will get something like this:
Code:
#ifeq ($(INTEL_VA),true)
#
#include $(call all-subdir-makefiles)
#
#endif
It was:
Code:
ifeq ($(INTEL_VA),true)
include $(call all-subdir-makefiles)
endif
Click to expand...
Click to collapse
to build I need to choose cm_a500cg-userdebug?
---------- Post added at 13:13 ---------- Previous post was at 13:08 ----------
tank0412 said:
Just unpack archive with device folder and put it in the path above.
To comment just add this symbol "#" to every string.(line)
I provided an example.
You will get something like this:
Code:
#ifeq ($(INTEL_VA),true)
#
#include $(call all-subdir-makefiles)
#
#endif
It was:
Code:
ifeq ($(INTEL_VA),true)
include $(call all-subdir-makefiles)
endif
Click to expand...
Click to collapse
I got this error when building https://drive.google.com/file/d/0B8e62vKMKobRWjBNUllkLXBSRDA/view?usp=sharing
TecnoTailsPlays said:
to build I need to choose cm_a500cg-userdebug?
---------- Post added at 13:13 ---------- Previous post was at 13:08 ----------
I got this error when building https://drive.google.com/file/d/0B8e62vKMKobRWjBNUllkLXBSRDA/view?usp=sharing
Click to expand...
Click to collapse
No.
One config is missing in your kernel sources:
https://github.com/quanganh2627/Kernel-fo-Zenfone-6-by-BORETS24/blob/master/arch/x86/configs/cm_a500cg_defconfig
tank0412 said:
No.
One config is missing in your kernel sources:
https://github.com/quanganh2627/Kernel-fo-Zenfone-6-by-BORETS24/blob/master/arch/x86/configs/cm_a500cg_defconfig
Click to expand...
Click to collapse
so what I do?
TecnoTailsPlays said:
to build I need to choose cm_a500cg-userdebug?
---------- Post added at 13:13 ---------- Previous post was at 13:08 ----------
I got this error when building https://drive.google.com/file/d/0B8e62vKMKobRWjBNUllkLXBSRDA/view?usp=sharing
Click to expand...
Click to collapse
TecnoTailsPlays said:
so what I do?
Click to expand...
Click to collapse
Disable inline kernel building.
Check OP.
tank0412 said:
Disable inline kernel building.
Check OP.
Click to expand...
Click to collapse
how I do that? it is not on the thread
TecnoTailsPlays said:
how I do that? it is not on the thread
Click to expand...
Click to collapse
Oops.
Try to use BoardConfig.mk from AOSP:
https://github.com/tank0412/aosp_device_asus_a500cg/blob/master/BoardConfig.mk
And delete linux folder with kernel sources. (if you have it)
tank0412 said:
Oops.
Try to use BoardConfig.mk from AOSP:
https://github.com/tank0412/aosp_device_asus_a500cg/blob/master/BoardConfig.mk
And delete linux folder with kernel sources. (if you have it)
Click to expand...
Click to collapse
I just need to change the code inside of boardconfig.mk to that one you gived me? and I don't know what linux folder to delete, I searched in search bar and I found more than 20 linux folders
TecnoTailsPlays said:
I just need to change the code inside of boardconfig.mk to that one you gived me? and I don't know what linux folder to delete, I searched in search bar and I found more than 20 linux folders
Click to expand...
Click to collapse
OMG, And i though that i am a noob....
Do you use device tree by Tran Huu Tin?
Note:
Linux folder is a fodler with kernel sources. You could add it manually.
tank0412 said:
OMG, And i though that i am a noob....
Do you use device tree by Tran Huu Tin?
Note:
Linux folder is a fodler with kernel sources. You could add it manually.
Click to expand...
Click to collapse
yes I used it, I am a noob, Its my first time compiling a rom from source
TecnoTailsPlays said:
yes I used it, I am a noob, Its my first time compiling a rom from source
Click to expand...
Click to collapse
STOP.
OMG. You wrote an incorrect command.....
Use this:
Code:
. build/envsetup.sh
lunch cm_a500cg-userdebug
make -j4
tank0412 said:
STOP.
OMG. You wrote an incorrect command.....
Use this:
Code:
. build/envsetup.sh
lunch cm_a500cg-userdebug
make -j4
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B8e62vKMKobRT3FzREt0R3lZalE/view?usp=sharing
TecnoTailsPlays said:
https://drive.google.com/file/d/0B8e62vKMKobRT3FzREt0R3lZalE/view?usp=sharing
Click to expand...
Click to collapse
Try to wipe your trash folder.
And i hope that you really used devcie tree by Tran Huu Tin.
Or you can try to delete healthd folder from devcie tree.
tank0412 said:
Try to wipe your trash folder.
And i hope that you really used devcie tree by Tran Huu Tin.
Or you can try to delete healthd folder from devcie tree.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B8e62vKMKobRQUI1N01OUEg5Qnc/view?usp=sharing
I did what you said

Xposed error when compiling app_process_xposed.

Hi everyone,
I wanna build old version of Xposed, for Android SDK 16-19, then have tried to compile Xposed fw for hundreds time but still failed.
Environment: Ubuntu 15.10 x64 | tools: JDK 1.6, libc6 ....
AOSP: JZO54L / android-4.1.2_r2 /Jelly Bean ("make app_process" have been run successfully).
My steps:
- Download AOSP into /opt/android/aosp
- XposedBridge.jar: Download Xposed Installer here repo[dot]xposed[dot]info/module/de.robv.android.xposed.installer and detach jar from apk. Put it to /opt/out/java
- Download XposedTools source from github into /opt/xposed/ then make build.conf file:
[General]
outdir = /opt/out
[Build]
# Please keep the base version number and add your custom suffix
version = 58
# makeflags = -j4
[GPG]
sign = release
user = 852109AA!
# Root directories of the AOSP source tree per SDK version
[AospDir]
16 = /opt/android/aosp
# SDKs to be used for compiling BusyBox
# Needs github[dot]com/rovo89/android_external_busybox
[BusyBox]
Click to expand...
Click to collapse
- To integrate Xposed to AOSP, I tried following 2 ways in the instruction (local manifest and manual cloning)
+ local manifest: link [XposedTools]/local_manifests/xposed_sdk16.xml to [aosp]/.repo/local_manifests/ then run repo sync.
+ manual cloning: remove [aosp]/build; clone github[dot]com/rovo89/platform_build/ to replace; clone github[dot]com/rovo89/Xposed into [aosp]/framework/base/cmds/xposed
- Go back to [XposedTools] and run ./build -t x86:16
>>output: cd /opt/android/aosp && . build/envsetup.sh >/dev/null && lunch full_x86-user >/dev/null && make -j8 TARGET_CPU_SMP=true xposed
Click to expand...
Click to collapse
The result I received is a big "app_process_xposed" file (~ 270-350 KBs), it size is as many times as the origin app_process file (~20 KBs). I think there are somethings wrong. I open them by 7z and see some differences:
i.imgur.com/PU80vSV.png
Click to expand...
Click to collapse
I may did some mistakes in these steps. Could you please give me any advice?
Thank so much!
Help me Pls...
Did you actually try the app_process_xposed you got, or did you just assume it was wrong because it was bigger? If you did try it, what did it do?
josephcsible said:
Did you actually try the app_process_xposed you got, or did you just assume it was wrong because it was bigger? If you did try it, what did it do?
Click to expand...
Click to collapse
Thank for your reply. I tried rename app_process_xposed to app_process_sdk16 then push new file to assets folder of XposedInstaller project. When XposedInstaller.apk file installed, i had receive messages not compatible with my sdk 19...
hahalulu said:
When XposedInstaller.apk file installed, i had receive messages not compatible with my sdk 19...
Click to expand...
Click to collapse
What was the exact message that you got? Can you post a screenshot of it?
josephcsible said:
What was the exact message that you got? Can you post a screenshot of it?
Click to expand...
Click to collapse
My message i had received
Update: sdk16.zip file
I'm still stuck at this problem :crying:
hahalulu said:
I'm still stuck at this problem :crying:
Click to expand...
Click to collapse
build duoc chua ban. minh cung dang bi giong ban. khong biet giai quyet the nao
hellboy211 said:
build duoc chua ban. minh cung dang bi giong ban. khong biet giai quyet the nao
Click to expand...
Click to collapse
Please post in English, I have translated this one for you
Regards
Sawdoctor
Build is not acid. You are also welcome. Not the right time

Android Go Edition for Titan

Is anyone developing Android Go for Moto G 2014 model ?
A request to the developers, please develop it for this device . It is much needed. I have tried many ROMs but almost all of them starts lagging after a week of using it.
Thanks.
Yes please someone make GO EDITION for titan
It's done. @LuK1337 has done it. Check out his Lineage os 15 thread
CMKdaGreat said:
It's done. @LuK1337 has done it. Check out his Lineage os 15 thread
Click to expand...
Click to collapse
Is that Go Edition ??
I am using it presently, its normal Oreo its not Go Edition.
gauravchy08 said:
Is that Go Edition ??
I am using it presently, its normal Oreo its not Go Edition.
Click to expand...
Click to collapse
There is a Go edition in one of the last @LuK1337 comments
CMKdaGreat said:
It's done. @LuK1337 has done it. Check out his Lineage os 15 thread
Click to expand...
Click to collapse
joaomiguelsm said:
There is a Go edition in one of the last @LuK1337 comments
Click to expand...
Click to collapse
Good luck with that has its just a poll asking if he should start building Lineage 15 with Go Edition config instead of regular config. So far more people have voted against Go Edition. There is no actual Go Edition builds for titan.
MobileHD said:
Good luck with that has its just a poll asking if he should start building Lineage 15 with Go Edition config instead of regular config. So far more people have voted against Go Edition. There is no actual Go Edition builds for titan.
Click to expand...
Click to collapse
Go check the post carefully. Download link is there
CMKdaGreat said:
Go check the post carefully. Download link is there
Click to expand...
Click to collapse
I see it now, apparently it is not labeled as Go Edition (as one would expect), thus the confusion. Here's the link so that others wont get confused: lineage-15.1-20171209_143404-UNOFFICIAL-titan.zip
MobileHD said:
Good luck with that has its just a poll asking if he should start building Lineage 15 with Go Edition config instead of regular config. So far more people have voted against Go Edition. There is no actual Go Edition builds for titan.
Click to expand...
Click to collapse
Next time, read the comment carefully
joaomiguelsm said:
Next time, read the comment carefully
Click to expand...
Click to collapse
Would have been better if you had linked to it in the first place instead of just saying that its in another thread but okay.
MobileHD said:
Would have been better if you had linked to it in the first place instead of just saying that its in another thread but okay.
Click to expand...
Click to collapse
I assumed that you had already read the message that I mentioned before speaking but ok
Now you know that Moto G2 has a Android Go version in development
MobileHD said:
I see it now, apparently it is not labeled as Go Edition (as one would expect), thus the confusion. Here's the link so that others wont get confused: lineage-15.1-20171209_143404-UNOFFICIAL-titan.zip
Click to expand...
Click to collapse
Is it really a go edition ?
Pixel experience 8.1 official is out ?
Um unnoficial Pixel Experience 8.1.0
I m still looking for the related thread for the Go Edition.
I have been able to find the repo on AFH and there are two folders 15.0 and 15.1. The last build of 15.0 is on 4th of DEC 2017. After that only 15.1. Not sure if 15.1 is the Go edition or regular as the file size is almost close.
This is the link for 15.1 Builds.
The build shared in previous page (lineage-15.1-20171209_143404-UNOFFICIAL-titan.zip) is available in this folder and it has beed mentioned previously it is GO version without the GO naming.
---------- Post added at 10:38 AM ---------- Previous post was at 10:11 AM ----------
Ok, this is the thread by the developer and he is referencing to the same folder. Go has not been explicitly mentioned there.
[ROM][UNOFFICIAL][TITAN][8.1] LineageOS 15.1 [UNIFIED]
itsallaboutu007 said:
I m still looking for the related thread for the Go Edition.
I have been able to find the repo on AFH and there are two folders 15.0 and 15.1. The last build of 15.0 is on 4th of DEC 2017. After that only 15.1. Not sure if 15.1 is the Go edition or regular as the file size is almost close.
This is the link for 15.1 Builds.
The build shared in previous page (lineage-15.1-20171209_143404-UNOFFICIAL-titan.zip) is available in this folder and it has beed mentioned previously it is GO version without the GO naming.
---------- Post added at 10:38 AM ---------- Previous post was at 10:11 AM ----------
Ok, this is the thread by the developer and he is referencing to the same folder. Go has not been explicitly mentioned there.
[ROM][UNOFFICIAL][TITAN][8.1] LineageOS 15.1 [UNIFIED]
Click to expand...
Click to collapse
https://forum.xda-developers.com/mo...ment/rom-lineageos-15-0-t3669082/post74788556
Check Luk1337's post. It has 2 links. One is AFH and the other is poll. Go version might still be in the AFH link if you're not too late already.
Android Go version is named this
"lineage-15.1-20171209_143404-UNOFFICIAL-titan.zip"
And how do i know systemu is it go edition?? I see normal android 8.1 -15.1 lineage, i download what you post, version
20171209_143404
I only saw 3 posts of people who have tried the go build of LOS15.1. Its sad that its been seen as not feasible. So there was one guy complaining how animation looked worse and made the phone cheap. By todays standards its already a cheap low end phone. I would not care as this is not my daily driver anyway. I just need an optimized OS for the simplest tasks without any lagging.
those who want Oreo GO version just download the latest version of LineageOS 15.1 titan oreo rom after that flash oreo addon file thats it guyz all the link given.......follow the LINK = https://forum.xda-developers.com/showpost.php?p=73900030&postcount=408
how good is this go version? I just got a moto g2014 non lte. and wanted to install some custom roms, how about this rom bugs?

Categories

Resources