yashsingh1/xdaforums huggingface dataset:
[Android Software Development] laperry1:
DespairFactor, thanks for your help. i resynced & compiled for an hour & got the following message:

prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-ar: error while loading shared libraries: /usr/lib/x86_64-linux-gnu/libfl.so.2: invalid ELF header

a bit more data:

target StaticLib: libc_bionic (/home/samadhi/los13/out/target/product/oneplus3/obj/STATIC_LIBRARIES/libc_bionic_intermediates/libc_bionic.a)

prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-ar: error while loading shared libraries: /usr/lib/x86_64-linux-gnu/libfl.so.2: invalid ELF header

build/core/static_library_internal.mk:33: recipe for target '/home/samadhi/los13/out/target/product/oneplus3/obj/STATIC_LIBRARIES/libc_bionic_intermediates/libc_bionic.a' failed

make: *** [/home/samadhi/los13/out/target/product/oneplus3/obj/STATIC_LIBRARIES/libc_bionic_intermediates/libc_bionic.a] Error 127

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

target StaticLib: libc_bionic_ndk (/home/samadhi/los13/out/target/product/oneplus3/obj/STATIC_LIBRARIES/libc_bionic_ndk_intermediates/libc_bionic_ndk.a)

prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-ar: error while loading shared libraries: /usr/lib/x86_64-linux-gnu/libfl.so.2: invalid ELF header

build/core/static_library_internal.mk:33: recipe for target '/home/samadhi/los13/out/target/product/oneplus3/obj/STATIC_LIBRARIES/libc_bionic_ndk_intermediates/libc_bionic_ndk.a' failed

make: *** [/home/samadhi/los13/out/target/product/oneplus3/obj/STATIC_LIBRARIES/libc_bionic_ndk_intermediates/libc_bionic_ndk.a] Error 127

target StaticLib: libc_cxa (/home/samadhi/los13/out/target/product/oneplus3/obj/STATIC_LIBRARIES/libc_cxa_intermediates/libc_cxa.a)

prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-ar: error while loading shared libraries: /usr/lib/x86_64-linux-gnu/libfl.so.2: invalid ELF header

build/core/static_library_internal.mk:33: recipe for target '/home/samadhi/los13/out/target/product/oneplus3/obj/STATIC_LIBRARIES/libc_cxa_intermediates/libc_cxa.a' failed

make: *** [/home/samadhi/los13/out/target/product/oneplus3/obj/STATIC_LIBRARIES/libc_cxa_intermediates/libc_cxa.a] Error 127

make: Leaving directory '/home/samadhi/los13'
[Android Software Development] DespairFactor:
Delete repo completely and sync please
[Android Software Development] KuranKaname:
Try this:

Download this lib: https://drive.google.com/file/d/0B0LnTbgUOuxYMHJCcl9RTEJXUjA/edit?usp=sharing

Then

sudo su

cp /home/user/Downloads/libfl.so.2.0.0 /usr/lib/

chmod 755 /usr/lib/libfl.so.2.0.0

ln -s /usr/lib/libfl.so.2.0.0 /usr/lib/libfl.so

ln -s /usr/lib/libfl.so.2.0.0 /usr/lib/libfl.so.2

ln -s /usr/lib/libfl.so.2.0.0 /usr/lib/x86_64-linux-gnu/libfl.so.2

---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------

Nah don't worry I knot you didn't want to be rude :). Thanks a lot, I've searched it before but didn't find anything. Now it works and I compiled the rom
[Android Software Development] storm119:
[MENTION=5169465]DespairFactor[/MENTION]

You are awesome man...thanks for sharing the prebuilts gcc. Using another TC's for the first time ever to brewing my home made ROMs with UberTC 4.9 and worked beautifully.

Btw...i like to hear from the folks here...which gcc (UberTC) are best on their past experienced for baking ROMs...performance wise etc ?

TIA
[Android Software Development] DespairFactor:
Honestly, I use 4.9 because it is most stable.
[Android Software Development] storm119:
Gotcha.....and thx
[Android Software Development] quake73:
but really, in the end, what, in theory, should be the benefit of using newr toolchains (6, 7, 8)? Is it worth all the trouble, do you get shorter compilation time, better performance or battery? Or it's just they are more intelligent and catch more 'warnings'? I have managed to finish builds with even 8.x but is it worth it, the additional work and time spent? Or is it better to play around with different optimization switches and stick to an older version of the toolchains? I'd really love to hear the opinion of the maker himself :)
[Android Software Development] DespairFactor:
Wait a second, that is GCC 8 on an OP5? Do you see any issues with frequencies stuck at max? I was seeing that on GCC 6+ on this same device.

I personally prefer stability, higher versions can benefit performance. I personally think it is hit and miss, others may disagree, but that's the whole beauty of open source. I share these just because I enjoy contributing to our community and want to push our technology forward as much as I can.
[Android Software Development] quake73:
it was set at 'performance' but yes, now that you mentioned it, i tried different governors, even 'powersave', it seems that all the cores are stuck at 'on' and at max freq. (thats what kernel adiutor says)

honestly, with this device, cpu governors dont really matter, you get excellent battery anyway....i guess in the near future, the cpu governors issue will become totally obsolete, just run the cpu at max, like a boss :)
[Android Software Development] DespairFactor:
I am not so sure where this breaks though, I wish we could figure it out as Samsung devices at this time do not have this issue.
[Android Software Development] laperry1:
tried the above links, however, the final command (ln -s /usr/lib/libfl.so.2.0.0 /usr/lib/x86_64-linux-gnu/libfl.so.2) failed... tried to build & it failed

unlinked /usr/lib/x86_64-linux-gnu/libfl.so.2, did some yard work came back to a successful build!!!

wheww, thanks! so, in the future how do i determine this as being the source of my build error?
[Android Software Development] KuranKaname:
/usr/lib/x86_64-linux-gnu/libfl.so.2: invalid ELF header

You can see it's pointing to the lib on your PC, not in the rom folder

---------- Post added at 01:10 PM ---------- Previous post was at 01:06 PM ----------

Actually, I have a problem with frequencies stuck at max but it's not related to GCC 6, many roms on my device have this problem and they're compiled with the stock toolchain. Any idea? :confused::confused:
[Android Software Development] KuranKaname:
[MENTION=5169465]DespairFactor[/MENTION] Stupid question but where do you set android-eabi? Aarch64-linux-androideabi and Arm-linux-androideabi I know in build/core but what to do with android-eabi
[Android Software Development] DespairFactor:
You mean arm-eabi? That is used for compiling kernels for arm targets. The AArch64 targets have a combined toolchain for ROM and kernel.
[Android Software Development] KuranKaname:
Oh ok thanks. P. S. Managed to compile with gcc 7 all working good
[Android Software Development] DespairFactor:
You have no frequency sticking issues on it?
[Android Software Development] KuranKaname:
Nope and I saw other developers adapting GCC 7 too. Is it really worth it?
[Android Software Development] quake73:
I very very rarely ask questions before first extensively search google and this is one such occasion...this error is giving me headaches:

/usr/bin/ld.gold: fatal error: /home/blaze/sdclang-3.8/bin/../lib/clang/3.8.8/lib/linux-propri_rt/libclang_rt.ae-aarch64-android.a(crtae.c.o): unsupported ELF machine number 183

The custom sdclang is not the problem (tried without it already)...its obviously linker problem, the integrated one is called, /usr/bin/ld.gold instead of the one from the toolchains....

If I do this 'nasty hack' (copy ld.gold from toolchains to 'integrated'): sudo cp ~/toolchains/aarch64-linux-android-8.x/bin/aarch64-linux-android-ld.gold /usr/bin/ld.gold...the build continues but fails later anyway.

My question is: where in bionic or compiler_rt is the path to the linker set? any clues about "unsupported ELF machine number 183"? where should i look for the culprit?
[Android Software Development] DespairFactor:
You are trying to build android with GCC 8?
[Android Software Development] quake73:
im giving a try with a LOT of roms for OnePlus5, trying different combinations (i know it is still relatively new device, not all the repos/trees are fixed etc.)...but I was getting this same ELF error previously, too, so, its not tied to any rom or device in particular...funny thing, it began today...previously i did many successful builds (non-bootable, but it doesnt matter)...im asking for a clue, where to look for, what to change, what could be the offender. I need to add this, too. It began happening after switching toolchain versions (6/7/8), I did a clean of the out folder and that didnt help either.

EDIT:

a note for the others getting similar ELF error..... I dont like this solution but putting the location of your toolchain in the PATH helps, at the terminal prompt or in bash.rc, like this:

export PATH=/home/blaze/toolchains/aarch64-linux-android-6.x/bin/:$PATH

(the error actually began manifesting itself after I removed that line from bashrc :) it means I had that error previously and had it 'fixed' that way. I suspect I messed my setup somewhere but I have no idea where)

My question is still open, how do I tell the build system to use the correct LD for bionic/compiler-rt? why does it even use the one from /usr/bin? What might be wrong with my ubuntu? Some variable used by the .mk files?
[Android Software Development] KuranKaname:
Edit: Stupid question. Sorry
[Android Software Development] storm119:
[MENTION=5169465]DespairFactor[/MENTION]

After so many trial and errors and fixing stuffs on my working tree (it's really pain in arse and i once banging my head onto wall, pulled my hairs and with no sleep for more than 24 hours juz to get this stuff worked :D)....but the last few days finally i managed to compiled my ROMs with higher/newer than gcc 4.9 and clang 3.8 (my current setup gcc 6.X + clang 5.0) it is a really good experience and worth it to learnt this stuffs . Anyway I have few questions/requests tho....

1- While comparing between yours vs UberRoms and few other bitbucket (prebuilts which i can find)...yours is smaller in file size comparing to others. Any insight on this...i'm juz curios ?

2- Any chance you can update/publish the prebuilts clang 3.9 and 5.0...coz i forked from the UberRoms (bb) but it's never update since Feb 2017...?

3- Any secret recipe (code optimisations) you would like to share with us (for baking ROMs with kernel)...currently i'm using the one from UberRoms and the ROMs are fly and stable without any issue but still i would like to push to its limit without sacrifice the ROMs usability/stability..?

Thank you once again for sharing yours awesome works....really appreciated :good:
[Android Software Development] DespairFactor:
I strip my toolchains of all debugging and stuff. I never did the clang stuff, that was Chad. The optimizations I use on kernel are here: https://github.com/matthewdalex/oneplus5/blob/min/Makefile#L366 and rom is here: https://github.com/matthewdalex/build/commit/c1c6e75737c32bbc9585b3191d5cd4f50b147952
[Android Software Development] ppajdek:
Got this error when compiling with arm-eabi-4.9-uber:

ERROR: modpost: Found 13 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
To build the kernel despite the mismatches, build with:
'make CONFIG_NO_ERROR_ON_MISMATCH=y'
(NOTE: This is not recommended)
/home/pajdek/kernel/android_kernel_lge_g3/scripts/Makefile.modpost:98: recipe for target 'vmlinux.o' failed
make[1]: *** [vmlinux.o] Error 1
Makefile:938: recipe for target 'vmlinux.o' failed
make: *** [vmlinux.o] Error 2

With CONFIG_DEBUG_SECTION_MISMATCH=y i got some debeg info like

WARNING: vmlinux.o(.data+0x1c088): Section mismatch in reference from the variable gdsc_driver to the (unknown reference) .init.data:(unknown)
The variable gdsc_driver references
the (unknown reference) __initdata (unknown)
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

With CONFIG_NO_ERROR_ON_MISMATCH=y it builds ok, but i dont know if it safe and make kernel unstable.

With standard gcc 4.9 no mismatch errors.

Any thoughts?
[Android Software Development] DespairFactor:
We now have a telegram channel:

https://t.me/darkroomdev
[Android Software Development] KuranKaname:
[MENTION=5169465]DespairFactor[/MENTION] When trying to build with uber higher than 6.x:

arch/arm64/kernel/io.c: In function ‘__memcpy_fromio’:

arch/arm64/kernel/io.c:51:1: internal compiler error: Segmentation fault

}
[Android Software Development] idprophecy:
[MENTION=5591612]laperry1[/MENTION],

I had to deal with this error long time ago, but I think it might have been due to binutils 2.27. Recompile uber with this patch applied to binutils. It should work.

https://git.linaro.org/toolchain/bi.../?id=3d3424e9a8d6ad56160b98bf6e223c0346164468
[Android Software Development] laperry1:
hey, thanks for your response! though i was able to compile the toolchain, i also noticed i missed some of the error code.

ultimately, i applied this https://xdaforums.com/showpost.php?p=73205454&postcount=34 & was able to get a successful build of LAOS 14.1
[Android Software Development] :
https://github.com/UBERTC/ broken?

Is anybody currently able to build ANY version from source? First it bails out because of the mismatch of directories and scripts (script want i.e. binutils/binutils-uber, but manifest installs to binutils/binutils-common.

After corrwcting this, it stops on configuring libatomic:

/usr/local/src/UBERTC/build/binutils-uber/gold/ld-new: error: cannot open crt1.o: No such file or directory
/usr/local/src/UBERTC/build/binutils-uber/gold/ld-new: error: cannot open crti.o: No such file or directory
/usr/local/src/UBERTC/build/binutils-uber/gold/ld-new: error: cannot open crtn.o: No such file or directory
collect2: error: ld returned 1 exit status

I tried to contact the developer: no response. I made a pull request for fixing the mismatch errors: no response. Is anybody able to build with the current repo?

Sadly, I can't switch back to the privious running repo status, because most gits were hard reset...

It's nice to have uber - this saves one from fiddeling with linaro, but over the last three years the build tree gets regulary hard reset, so I can't see, what has broken building.

BTW: I'm on gentoo.

EDIT: Why are your prebuilts recide in aarch64-linux-android-6.x, but the scripts are build in aarch64-linux-android-6.x-kernel? On my old (hard resetted away) version it was aarch64-linux-android-6.x, too.
[Android Software Development] DespairFactor:
Where did you reach out to me? I will look at what happened to my scripts. The source trees do not get reset at all, only the prebuilts.
[Android Software Development] :
To the email of one of the commits.

Anyway,

https://github.com/UBERTC/linaro-manifest/pull/1

because:

https://github.com/UBERTC/linaro-scripts/blob/master/aarch64-linux-android-6.x#L70

I can't imagine how the current status should work for anybody, if manifest installs to dirs ending on *-common, but the scripts call configure assuming *-uber should be found.

An other work around are symlinks - but they surely blow up sooner or later if the path names in manifest change again.

I investigated further: If I come from a clean sync and checkout c2451a9 from linaro-scripts, aarch64 6x builds fine (at least - most probably the others as well) and produces a working UBER toolchain (for a heavily patched, eas enabled los kernel - again: most probably...).

I belive it's just the configure calls does not match for my gentoo installation.

Thanx for your work and your response! I really appriciate not to need to fiddle with linaro. I completely understand the need to hard reset sometimes to keep it readable and manageble. I was in a hurry and just wanted to build 7.x to test something else... ...perhaps I could have been more polite regarding the hard reset, sorry.

EDIT: nearly forgot: Yes, it's about the prebuilts are not found by configure, the way the linaro-scripts call configure.
[Android Software Development] DespairFactor:
Ahhh those linaro repos aren't maintained honestly:P only the actual UBER repos are. The reset on Linaro was to make sure it was up to date with the proper branches. The right repo for UBER is https://github.com/UBERTC/uber-manifest.
[Android Software Development] :
Thanx. I didn't have realized getting the wrong manifest... The REAEME.md did the rest... Rule of thumb: first match isn't a good choice when selecting manifests. Perhaps - for noobs like me - it would make sense to add to the linaro-manifest's README.md:

The linaro-manifest and linaro-scripts git repositories exists for documentary purpuse and reference. If you want to build UBER ToolChain make sure you select the uber-manifest:

repo init -u https://github.com/UBERTC/uber-manifest.git -b master

Just an idea (I'm one of these old ass bastards, not only reading manuals, but also check for changes - perhaps I overestimate the meaning of written words nowadays...).

Thanx again.
[Android Software Development] laperry1:
hey guys, i get the following error compiling w/UBERTC-8.x for OP3:

error: no matching function for call to 'android::Vector<TYPE>::operator=(const android::VectorImpl&) const'

ROM - LineageOS-14.1 compiles fine w/UBERTC-6.x...

i noticed the bug report - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853312 - reflecting the same error but i have tracked down a solution...

can anyone here help?
[Android Software Development] Hlcpereira:
Guys I've got this while using Uber arm-eabi-4.9. Any ideas for a solution?
[Android Software Development] KuranKaname:
Try adding -Wno-aggressive-loop-optimizations in kernel makefile, KBUILD_CFLAGS
[Android Software Development] psndna88:
hey any updates for the pre-builts...
[Android Software Development] palaych:
Hi. Do you plan to update further? or support is over?
[Android Software Development] NATO66613:
[MENTION=8203960]palaych[/MENTION] [MENTION=4365701]psndna88[/MENTION] I have compiled aarch64-linux-android-7.x-uber if thats helps And i uploaded updated gcc & binutils to my git to so you can use it to compile uber gcc you need https://github.com/kondors1995/aarch64-linux-android-7.x
[Android Software Development] psndna88:
can u do for gcc 8 ?
[Android Software Development] NATO66613:
i can try
[Android Software Development] psndna88:
errors:

make sure this supports stack protector regular and strong

and

aarch64-linux-android-7.x/bin/../libexec/gcc/aarch64-linux-android/7.3.1/cc1: error while loading shared libraries: libmpfr.so.6: cannot open shared object file: No such file or directory
[Android Software Development] NATO66613:
i build gcc 8
[Android Software Development] NATO66613:
Works good on arch Linux need some help regarding stack protector
[Android Software Development] palaych:
Can you do for gcc 6? :confused:
[Android Software Development] 6h0st:
Good job!
[ZTE Axon 7 Questions & Answers] Raccroc:
Coming from Samsung's line of phones…

While on a call, the screen would turn off while near your head, then back on as it sensed being pulled away. Same with the Axon 7.

If you wanted to disable the feature (at least for the remainder of that call), you could manually turn off the screen with the power button. That would cause it to say off till you hit the power button or ended the call. Not the same with Axon 7.

The Axon 7 will turn the screen back on as soon as it senses you have put it up to your head, then pulled away again.

This is driving me crazy and I want to find a way to either mimic Samsung behavior, or disable the proximity sensor completely.

Suggestions?
[ZTE Axon 7 Questions & Answers] Batsy0219:
I'm having the same issue. The placement of the sensor sucks so it turns the screen off initially but a while later the screen turns on again and other buttons get pressed by my cheek.
[Xiaomi Mi Max Questions & Answers] jimpatrick:
Hey Mi Lovers

I bought Mi Max with 16GB Internal Memory with 2GB Ram, Is it Helium or Hydrogen Edition?!??!?

and suggest a TWRP for that.

Send Link Page(s)

Best Regards

:fingers-crossed:
[Xiaomi Mi Max Questions & Answers] pierro78:
2/16 is hydrogen, check the wiki : http://xdaforums.com/wiki/Xiaomi_Mi_Max#Variants - regards to you too !
[Xiaomi Mi Max Questions & Answers] nijel8:
My ears hurts from this question already...
[Xiaomi Mi Max Questions & Answers] jimpatrick:
EveryBody Is Not Expert Like U Dude!
[Xiaomi Mi Max Questions & Answers] jimpatrick:
Good News Is : (Cynogenmod 14.1 release Version Port 4 Mi Max Hydrogen Edition)

Go to the Official Web site to Download Rom.
[Xiaomi Mi Max Questions & Answers] nijel8:
EveryBody can do simple Google search and read I suppose...

How do you think I became an expert without asking questions...

See my avatar?
[Xiaomi Mi Max Questions & Answers] jimpatrick:
I was search in google and i cant find any useful info about that!

Dont care buddy
[Xiaomi Mi Max Questions & Answers] man2106:
the sd650 is hydrogen sd652 is helium

---------- Post added at 01:06 PM ---------- Previous post was at 01:05 PM ----------

you can flash hydrogen rom or any related thing on the 16gb version
[Windows Mobile Development and Hacking General] aaronsmckee:
The free version is pretty good, the premium services includes flight schedules (which is huge for me) all in all a decent app (though the weather updates are not a big deal with HTC home available) thought I would post link to it

http://www.mobimate.com/ppc_business.shtml
[Android Q&A, Help & Troubleshooting] imranbasha5019:
Guys Could anybody please tell me the best bug free custom rom for lenovo a6000+ (MM/N)? Any suggestion please? :good:
[Android Q&A, Help & Troubleshooting] pkrishna1987:
Hi,

I'm using Iball Andi 4.5m enigma Plus mobile. From past few days, I'm getting an error message saying "Unfortunately Google Play Services has Stopped". To resolve this problem, uninstalled the Google Play Services, Google Play Store and Google Framework Services and re-installed them. But the problem din't get resolved.

I tried to flash the Custom ROM . Used Smart Phone Flash Tool (SP Falsh Tool) to flash the stock rom. Even after this procedure, the problem seems to chasing me. After the reboot, the Google Apps started upgrading and the Google Play Services got upgraded and the whole mess is back again.

To get rid of this problem, I would like to unlock the boot-loader and flash custom rom (lollipop) verison.

Could someone help me,

1) Where can I download the custom rom for my mobile model

2) If I can flash lollipop rom

3) If any another custom rom or available and try them

4) How to unlock the bootloader of this device.

Thanks,
[Moto G4 Plus Questions & Answers] Darkvastin:
Guys after I updated to official nougat yesterday, I am not able to install or update apps from Google play store when I am in roaming, but I can use my mobile Internet for other regular purposes, the same problem has also persisted in nexus devices. Please help.
[Moto G4 Plus Questions & Answers] Iqbal Ansari:
Its a new feature in google and already mentioned everywhere.

Why did you open a new thread for such a common question.
[Moto G4 Plus Questions & Answers] Darkvastin:
I am sorry for being a noob, but is there a work around? Because I am at place where I don't have WiFi facilities and also I won't be returning to my home network anytime soon.
[Moto G4 Plus Questions & Answers] daverobinson88:
No sorry. It's a known issue with no current work around that I know of.
[Moto G4 Plus Questions & Answers] Iqbal Ansari:
No workaround yet as exposed is not yet available for nougat.
[Samsung Galaxy J7 Questions & Answers] AshTechsoft:
I have a galaxy j7 (SM-J7008), I searches everywhere but can't find its custom recovery there is only given custom recovery of j7 (SM-J700F/H.....) but I want custom recovery of j7 (SM-J7008)

Please help me.......