yashsingh1/xdaforums huggingface dataset:
[Android] NepoRood:
I don't know then, you can continue to search for Lineage commits that might be linked to the one I showed you. Or, wait for the Viper team to update their sources...
[Android] cpt_Sherman:
Stock

Device: galaxy grand prime (g530h xxu)

Android version:5.0.2

Port

Device:galaxy J5

Android version:5.1.1

I'm porting android 5.1.1 from galaxy J5 to g530h. Everything work but I have several problems:

Heating

Battery drain

Green shade in camera in high light conditions.

(First two bugs are fixed with executing script every time after booting. Does somebody know how to make script running automatically after boot?)

And how to fix green shade or to port stock camera?
[Android] FSadino:
Search about "init.d" support and add it to your lernel
[Android] cpt_Sherman:
I've already added it. What should I do next?
[Android] coachcrey:
Hey everybody been awhile since ive built a rom and i am getting this here error. any suggested action that may help me?

https://hastebin.com/jutufuyefu.sql
[Android] FSadino:
Did you "breakfast device"?
[Android] coachcrey:
I used lunch. Then mka bacon
[Android] Alviss2108:
Hi NepoRood, i built a rom for Samsung E500H but when i port rom to my device it stuck at Cyanogenmod Logo.

I don't know what problem is. But when i used rom Cyanogenmod 13 by Jackeagle and i replace boot.img by my boot.img the rom still boot successfully. Do you know what problem in my rom?
[Android] FSadino:
You need to "breakfast" first to sync your device repositories or you can do "brunch device" that is a combo (breakfast+lunch)
[Android] coachcrey:
I'm using a custom roomservice to pull my device stuff because I'm porting it over sense there isnt a build yet offically.
[Android] NepoRood:
Your overlays are outdated, look at or fork my tree Here (I also build for Angler)
[Android] coachcrey:
Awesome thank you!
[Android] SanketMohapatra:
Do you have any kind of porper instructions for development for the Snapdragon 210 because we are a community having the phone with the same same chip but we are unsuccessful in an attempt to Port a custom rom as well as a custom recovery for our phone.

Actually we discovered the thing that the bootloader is locked and the fastboot command are not working for our phone as it is a kind of Lock by the company.

We spoke to the developers of the redmi note 3 mobile phone and they told us that if there is no way to unlock the bootloader then please try to edit the emmc_appsboot.mbn but they could not tell us which are the values to be modified because they all are in hex and we don't have any idea about that.

So I am requesting all the members of this forum to please guide us in our development to unlock bootloader so that we can continue our development.

Cooperation is highly appreciated.
[Android] panmrmiki:
Hello,

I tried to build AOKP , nougat. I don't really know, if i can build 7.1.2 on older device/kernel/vendor, I haven't found answer. First, i thought "no, impossible, i can't do anything", but i also have historical Tab 10.1 P7500, p4 on github with 7.1.2 AOKP rom. There is no device tree for 7.1.2 or something like that, so i decide to try with xcover 2. It is not something important, i just wanted to gain some experience with linux etc. and have fun. Can I even build that kind of rom for unsupported device? 7.1.2 doesn't need so much ram etc. and works very smooth on another old devices, so i thought in can be helpful. For this device I have official VanirAOSP 4.4 ROM. Can it be helpful? Should i try to build on VanirAOSP source? Thanks for help, sorry for noob questions and english ;)
[Android] FSadino:
There are 3 things you need to compile especific device (Kernel, Vendor and Device tree). If you have AOKP 7.1.2 rom for your device you have all you need. You can use kernel/device/vendor to build, for example, Lineageos or any other custom you find. This 3 repositories may have (it will for sure) to be adapted to other roms expecialy device tree.

I suggest you to try build this VanirAOSP first so you can understand the process and then you can "jump" to other challenges

We are all noobs here and my english is not so good as you can read :p
[Android] Michael24884:
So I at last compiled my ROM using Google Cloud, however when I tried booting it (Lineage 13) I got stick in the Samsung S4 splash logo. I took a logcat it would be nice for some help. Thanks!

https://pastebin.com/CAywkx66
[Android] aoleary:
Bundling local changes into a commit

Hi all.

I have made some changes locally on my build, and I want to be able to bundle them into a commit, so if I do a "repo sync" I can reload them back again easily.

How do I do that?

The changes are in:

/frameworks/base/...

/packages/apps/Settings/....

Since the original commit doesn't exactly match up with my ROM, I did the changes manually, instead of "cherry-picking".

TIA
[Android] DiamondJohn:
Me too! I have not done it myself, but from my understand, you follow the procedures for "forking" a repository. https://help.github.com/articles/fork-a-repo/ and https://guides.github.com/activities/forking/ or http://bitdrift.com/post/4534738938/fork-your-own-project-on-github

Hopefully I haven't blocked someone who knows more, from giving a better/clearer resolution :o because it would help me too.

================================================

Now for my question.

I have currently built A non-official device (xt897) of ResurrectionRemix 6.0.1. The ROM boots and appears to work fine, apart from one thing. A feature of the ROM is optional lock screen blur/see-through which is on by default BUT cannot be turned off. Turning it off in the settings simply appears to set the blur parameters to some default, but not off :mad:

I tried editing the code to remove the option. I succeeded in removing it from the menu, but now the lockscreen simply shows a black background. Obviously I went a little too far...:o

My question is if anyone else has built this ROM (ie RR 6.0.1) and is experiencing the same behavior? or is it just me? and if so, is there a fix?:confused:
[Android] NepoRood:
If you're building a specific ROM "your way", and you are not committing to the original repo, then [MENTION=5417899]DiamondJohn[/MENTION] has it correct. Fork the said repo to your own git, then make your changes to the fork. You will then use a local manifest to remove the original repository and replace it with the one you modified for your needs.

You will most likely have to keep an eye on the original, so you can cherry-pick or add the changes, fixes and updates you want ;)

[MENTION=5417899]DiamondJohn[/MENTION], RR code can be finicky, lol, they like to have their "options". Have you tried just setting a lockscreen wallpaper? You can always use git to checkout the original files, then try reverting the blur commits...
[Android] DiamondJohn:
Thats how I thought I was going to have to do it, but in my skim reading of the various fork explanations, they didn't seem to mention that specifically. I assumed the git commands handled that maybe.

And thats why I want to build it. I currently use a personal LOS build that has been Xposed to the hilt, to basically implement a lot of the features of RR. My Nougat build of RR crashes, as does any Nougat build for my device :( There is no official Nougat for my device (xt905 basically an XT907, for which I use a slightly modified xt897 device tree)

Yes, and that worked, however, I have a snazzy paid-for Live Wall paper (Celestial Bodies), while setting a lock-screen wallpaper can only be a static iamge. Already thought of that and tried, and was upset when I realised it was only a static image option.

I found a commit (2 related commits actually) and tried using that as a guide, but the commit was sooo old, it was maybe not going to be that simple. For example, the commit added an include that was specific to adding lock-screen blur at the time, but the include has since been used for other features, and so is also required in the current commit. I guess, i will need to start again and try just changing the lines specifically in the commit, and then make the reverted code fit into the latest commit. I think on my last attempt I was obviously a little more aggressive than need be. Maybe I will go back to before the commit and then try selectively merging back code for missing but wanted features. I was just wondering if it was only me experiencing the specific bug/issue in my build
[Android] aoleary:
Thanks [MENTION=5417899]DiamondJohn[/MENTION] and [MENTION=7237874]NepoRood[/MENTION] for your replies :good:

I was thinking that I would have to fork the repos to achieve what I want to do..

Which would be better, sync my forked repo, or, sync the original repo and then cherry-pick my commits after each repo-sync ?
[Android] NepoRood:
I really don't know anyone still using Marshmallow, lol, heck I'm on Oreo :p

(Note: I do have an Angler/Nexus 6P)

Picking from your own repo could eventually lead to problems, like the ones you faced when adding your commits initially. If it was me, I'd just sync the fork. Unless the original repository does something that interferes with your changes, merging pull requests from it, to keep yours up-to-date, will be easy :good:
[Android] DJKristy:
Is there an easy way to find required git commit.

The repo I checked has 600+ commits
[Android] aoleary:
In the search box at the top in the repo you want to find the commit, type your query with quotes around it and then go to the commits tab of the search results..
[Android] Michael24884:
Is there any solution to my problem? My phone gets stuck at the static Samsung logo and starts to "decay"

https://pastebin.com/CAywkx66
[Android] xenreon:
Adding to what was already said, you can also search for the commits in your local clone using grep

git log --grep=*whatever you're searching for*
[Android] DiamondJohn:
I am trying to get a working Nougat ROM for my phone, so have tried building a few different ROMs. Usually when I have tried a LOS based ROM it will boot ok; not surprising since I am using a LOS device tree; but dies with constant FC's.

However, I gave DirtyUnicorns a try:fingers-crossed:, and after a few build fixes, I end up with a flashable ROM :highfive:, that bootloops before it gets to the boot animation:( So, I am building AOSP using a LOS based device tree (renaming files and changing the odd internal naming):cool:

I have attached a last_kmsg log which I think clearly shows it in a loop cycle, that if I am reading it correctly happens just before the bootanim, and may hinge off of the failure of "surfaceflinger".

I have built the ROM with a permissive kernel, so the few SELinux denials shouldnt be causing an issue.

https://www.hastebin.com/raw/oraxaluxaj

Has anyone got any ideas about where I should start looking into this? Are there any hints in the log that I am just not seeing?
[Android] TheReaper1:
Hello, guys! I tried to compile PureFusion for d855 but I need some help... https://hastebin.com/ijukozozuq.vbs

Anyone can help me to solve that?
[Android] FSadino:
Are you on x86 machine?
[Android] TheReaper1:
No, is x64
[Android] FSadino:
Try to downgrade Clang version
[Android] facoco:
How can I keep the source from overwriting my local manifest? I'm trying to build AOSCP for athene, the official device tree is not ready yet, so I have my own device tree, every time i use the brunch command my local manifest is overwritten with the location of the official device tree and synced.
[Android] FSadino:
Try to use "mka" instead "brunch"
[Android] Vaughnn:
anyone have a solution for this? building Lineage 15 https://pastebin.com/RqAV0RFV
[Android] FSadino:
Try to use hardware_ril from other custom ROM
[Android] DiamondJohn:
Strange app behavior

Im trying to build crDroid Nougat for an un-official device, using a LOS sourced device tree, and coming across some very strange behavior.

The ROM builds, flashes and boots (although best to not install GApps, more on that later). If I build it ODEX'd then it is pretty rock stable. However, as soon as I install any other apps (no matter if via adb or the play store etc) the installed app will normally work for a little while, and then start to FC.

Some things I have tested, which make it even more weird

1. So they usually initially work after installing, but start failing after 5 or so minutes (never tried to time it)

2. I can exit the app, clear it from recents, try loading many other apps (to force it out of memory), if its withing the time window, it starts up fine.

3. Some apps, but not many, are immune to this behavior. eg an old version og ES File Explorer (which is very handy)

4. If I go into (lets take "Kernel Adiutor" as an example) /data/app/APP_NAME/odex/arm/ and delete the odex file, and then also check and delete any related files in /data/dalvik-cache , the app will be back to good again (ie starts without error) To me that says the compiler is doing ok.

5. If i manually recreate the ODEX file (and I think delete the dalvik-cache, but Kernel Adiutor has nothing there anyway) using a command in adb. Again, the app returns to fully non crashing functionality

mkdir -p /data/app/com.grarak.kerneladiutor-1/oat/arm/;
rm /data/app/com.grarak.kerneladiutor-1/oat/arm/base.odex;

/system/bin/dex2oat --runtime-arg -classpath --runtime-arg --instruction-set=arm --instruction-set-features=default --runtime-arg -Xrelocate --boot-image=/system/framework/boot.art --runtime-arg -Xms64m --runtime-arg -Xmx512m --instruction-set-variant=krait --dex-file=/sata/app/com.grarak.kerneladiutor-1/base.apk --oat-file=/data/app/com.grarak.kerneladiutor-1/oat/arm/base.odex;

I am building an "eng", with the following flags

# ODEX the ROM
ifeq ($(HOST_OS),linux)
WITH_DEXPREOPT := true
WITH_DEXPREOPT_PIC := false
USE_DEX2OAT_DEBUG := false
DONT_DEXPREOPT_PREBUILTS := true
endif

So, its a case of it appearing that the compilation is good, but it just "forgets" how it works? I think it would be something in the device/vendor tree's, as I get this same behavior in other LOS based Nougat ROM's (AICP, RR, ColtOS and LOS itself); Marshmallow is good. Also, compiling for another (official) device is good.

A logcat of the crash pattern is at : https://www.hastebin.com/onikaminum.hs

Does anyone have ANY idea of what is causing the above behavior and even better, how to fix it. This ROM is so close, and there is no Nougat currently for our device.:(

Anyone have any ideas? please? anything?

signed frustrated :mad:

PS: if I don't odex the ROM, this happens with all ROM apps. Its not app specific.
[Android] Alviss2108:
i built a rom for Samsung E500H but when i port rom to my device it stuck at Cyanogenmod Logo.

I don't know what problem is. But when i used rom Cyanogenmod 13 by Jackeagle and i replace boot.img by my boot.img the rom still boot successfully. Do you know what problem in my rom?
[Android] genesixxbf3:
Repo sync and make clean we fixed it
[Android] saintxseiya:
So, managed to build my first ROM with custom kernel, cherry picks, own tools etc. :)

Thanks a lot to you guys! You helped a lot and this guide is awesome!!! :)

Now i would love to know where those features like gestureAnywhere come from and how to integrate that ones in the rom ?

Any clue?

Cheers,

Francesco
[Android] DSA:
Cherrypicking
[Android] saintxseiya:
[MENTION=4097982]DSA[/MENTION]

yes, but where? the gerrit of cm12 shows nothing like that. Could you point me in a direction ? :)

Thnx mate!
[Android] DSA:
Gerrit is the perfect place to cherry pick

If you are using the new view, click on the download button on the right side, and choose the cherry pick option
[Android] tobitege:
You need to look in other ROM's repositories like OmniRom, Vanir etc.
[Android] DSA:
Plus you can also cherry pick in github
[Android] desalesouche:
it seems harder for my pc to compile your rom than another one, may be because of all optimizations?

one time i am stuck editing settings or contacts apk, and another time pc is stuck at compiling libwebchromium.so.

any suggestion?

edit: i just did fresh repo sync, will clone the new toolchains and compile again. will feed back.

thanks for all
[Android] ##W4TCH0UT##:
Some modules like libwebviewchromium break using sm graphite flags. You need to disable it.

Regards
[Android] desalesouche:
thank you, it seems it is already disabled in SaberSunset. besides i was compiling with that tag to get prebuilt chromium.

PRODUCT_PREBUILT_WEBVIEWCHROMIUM := true.

now i am trying without that tag.

may be prebuilt chromium need that fix?

https://github.com/OptiPop/build/commit/16206fce03848bfae5005d61caf8fb59baace9d
[Android] rahul8040:
I did repo sync! and tried make clean and after this error came :?
[Android] ##W4TCH0UT##:
Since SS is specifically using sabermod toolchains, no problem during any module compilation should occur. And yeah, do remove that tag, it's not needed, since SS should have libwebviewchromium disabled.

Regards
[Android] genesixxbf3:
but try now with a new repo sync
[Android] desalesouche:
i am stuck ath tis since 20 mn now.

warning: string 'wifi_secured_first_item' has no default translation.

warning: string 'wifi_secured_second_item' has no default translation.

warning: string 'wimax_settings_summary' has no default translation.

Install: /home/desalesouche/saber/out/target/product/u8860/system/priv-app/Settings/Settings.apk

what to do? :rolleyes:
[Android] ##W4TCH0UT##:
Settings doesn't seem a problem, is there any module compiling? Go up in terminal and see if any libs of modules are getting compiled.
[Android] desalesouche:
i don't know how to detect this.

here is pastebin (not all output, xD) http://pastebin.com/MP3hj9Yx
[Android] saintxseiya:
[MENTION=4097982]DSA[/MENTION] and [MENTION=4877142]tobitege[/MENTION]

I found the gestureanywhere in the gerrit of pacman, now my problem, after cherrypicking those i have some issues afterwards, i think there are then other dependencies.

How do i get all the dependencies, the commit relies on and not integrated in that pick ?

Sorry for those maybe noobish questions!

Cheers

Saint
[Android] tobitege:
I guess there's no easy, automatic way other than browsing/comparing repo's on github and looking at gerrit entries and following the dependencies there.

Example: http://review.cyanogenmod.org/#/c/89627/

There you can see "Depends On" and "Needed by" as references. Sibbling entries you might either find in commit description or by commit title or filtering by clicking on "Project" or "branch" etc.

If the rom you found does not offer a Gerrit page, than it might be even more difficult.

I'd like to know more about easier ways, too.
[Android] katinatez:
The gestures anywhere are here

https://github.com/temasek?tab=repositories

I believe they are in build repo and packages/apps/settings. I know there are multiple commits for it to work.

Cherry-pick and fix conflicts, then compile.
[Android] tobitege:
[MENTION=1060692]saintxseiya[/MENTION]: Once one knows the repo (thanks [MENTION=3814731]katinatez[/MENTION]), use the search bar at top of github page to e.g. search for gestures, resulting in URL like this:

https://github.com/temasek/android_packages_apps_Settings/search?utf8=✓&q=gestures
[Android] Vaughnn:
Wheres da logcat mate? We cant help you if you just tell us "oh my rom wont boot"

---------- Post added at 08:35 AM ---------- Previous post was at 08:34 AM ----------

Still a nope, but i'll try defining the missing variables in the .cpp file itself
[Android] Alviss2108:
i build rom cyanogenmod 13 for Samsung E500H and using source from https://github.com/MSM8916-Samsung . I can't get log from dmesg. This case is so hard.
[Android] Vaughnn:
That wont help, we need your logcat from your device when you build the cm yourself. Search how to get logcat. If you dont know about this stuff well ..
[Android] Alviss2108:
This rom is built sucessfully. No error when i built this rom. And i cant get logcat from "adb logcat" because device boot not complete.
[Android] DiamondJohn:
Then you would get your last_kmsg file, and post the contents on hastebin
[Android] Alviss2108:
Where does the last_kmsg is stored? i cant see it on /proc/last_kmsg.
[Android] Ravi Kumawat:
Do an eng build and flash it then try getting logs via adb!
[Android] matteo0026:
Hi guys, I'm trying to boot oreo on galaxy s2 plus. I'm making -eng builds, with selinux permissive. I reach only bootlogo, after some fixes to logcat, that I got it building AEX. But now, building LineageOS 15 my device isn't recognised on adb. Why this difference?
[Android] Albe96:
Better to do userdebug builds.So it can be more debugable!And booting lineage 15 is not easy stuff.Hope you've patched oreo selinux/binder patches correctly which needs for the device..

Good Luck!

---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------

What's the main problem? are you trying to port a Aosp(in your case,CyanogenMod) rom to a touchwiz/manufactured rom? If you are,it's not possible I think!
[Android] Alviss2108:
I port CyanogenMod rom, it's possible 'cause Jackeagle built a rom for this device succesfully.

Thank you, I will try it.
[Android] Albe96:
Hahaha.This is the funniest comment I've ever read.Listen Jackeagle is good developer.He created initial device,kernel,vendor etc trees for E5 to make cyanogenmod rom boot.It can't be ported to manufactured rom.The trees are on github page of jackeagle if you wnt to build a cm rom,clone his trees and build rom from that.I think you didn't read the OP.Read OP how to build rom first!
[Android] Alviss2108:
Sorry for my bad English. I use source from Github page of Jackeagle and get this problem. And what is the OP? I read "Android Embedded" of Karim Yaghmour.

Thank for your advice.
[Android] NepoRood:
Many, many members here that don't use English as a first language. Sometimes things just get lost in translation :D

OP =

O

riginal

P

ost

For your "ADB issue", you could try adding some flags to your "system.prop" file, if they're not already there:

service.adb.root=1
ro.adb.secure=0
ro.sys.usb.charging.only=no
persist.sys.usb.config=mtp,adb
[Android] Alviss2108:
Well, thank a lot for your help NepoRood,Albe96 and Ravi Kumawat.

I have just get the log from logcat. This is in https://hastebin.com/wovugasiyu.vbs.

Can anyone know what problem is?
[Android] aoleary:
Logcat for Data Cellular issues

Hi guys.

I have built the last Nougat version of Citrus-CAF for my D855, however, I have a few issues:

1. No data conecction

2. Play store keeps crashing

What do I look for in my logcat to find the data connection issues

Also, with my logcat app, I can trace one specific app at a time. Anyone know which one I should select between Google Play Services and Google Play Store ?

TIA
[Android] alphamale:
keeping getting this error trying to build resurrection remix from source.

Building with Jack: /home/android/rr/out/target/common/obj/APPS/Dialer_intermediates/with-local/classes.dex

ERROR: /home/android/rr/packages/apps/Dialer/src/com/android/dialer/dialpad/SmartDialPrefix.java:125: The method getT9SearchInputLocale(Context) is undefined for the type SettingsUtil

ERROR: /home/android/rr/packages/apps/Dialer/src/com/android/dialer/dialpad/DialpadFragment.java:738: The method refreshKeypad() is undefined for the type DialpadView

ERROR: /home/android/rr/packages/apps/Dialer/src/com/android/dialer/DialtactsActivity.java:571: The method getT9SearchInputLocale(DialtactsActivity) is undefined for the type SettingsUtil

build/core/java.mk:730: recipe for target '/home/android/rr/out/target/common/obj/APPS/Dialer_intermediates/with-local/classes.dex' failed

make: *** [/home/android/rr/out/target/common/obj/APPS/Dialer_intermediates/with-local/classes.dex] Error 41

make: *** Waiting for unfinished jobs....

make: Leaving directory '/home/android/rr'
[Android] HritikSH:
Guys I am trying to build cm-11 for my Micromax Canvas Xpress (Codename- A99) but I am unable to get device tree hence I need to build one for my device . I followed this guide: https://developerswork.github.io/works/GUIDES/AndrodDeviceTree/ but it's not working. Please guide me
[Android] Albe96:
Make it from scratch!
[Android] MZO:
What's not working?