yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] happyta5:
Love this thread.......

Thanks [MENTION=5431488]sysKin[/MENTION]., have you try diffrenent toolchain ?
[Galaxy S 4 Mini Android Development] sysKin:
Not yet, not on this build. I did use a different toolchain when I compiled CM 10.2 but without any knowledge about how repo works it was just one huge mess. Many guides here only deepened my misunderstandings by showing me how to replace kernel toolchain (ie what builds the kernel) saying nothing about rest-of-android toolchain (and I don't even remember some details of that anymore...).

Also, I never managed to successfully compile CM 10.2 with contemporary GCC 4.9 - too many weird internal compiler errors and other strangeness. Do you have any information about successes with current tools? There wouldn't be much point using different toolchains if GCC/clang/etc remain the same (well, GCC 4.8.4 was released on 19th of December, might be worth trying).
[Galaxy S 4 Mini Android Development] happyta5:
With some pointers from this thread, I'm able to build CM12 using ArchiDroid linaro 4.8 and 4.9 ToolChain with -O3 Optimized. CM seems run faster. I'm using [MENTION=3261191]F4k[/MENTION] kernel for the moment since I like the undervolt alot. May be I'll try SaberMod ToolChain later .....

Cheers ...
[Galaxy S 4 Mini Android Development] sysKin:
Could you share more about what you did? In particular, did you change the "android-eabi" toolchain or the "arm-eabi" toolchain?

The only instructions I've seen which explain how to use linaro toolchain refer to the "android-eabi" one, and if my understanding is correct, that's used only for building the kernel...
[Galaxy S 4 Mini Android Development] sysKin:
Just a heads-up, a build I made two days ago is not compatible with current (pre4) F4k's kernel. When I tried I had no radios (wifi nor phone). When I left the kernel unchanged it all worked fine.

Looking forward to the next kernel update :)
[Galaxy S 4 Mini Android Development] happyta5:
There are 2 files you have to edit for switching toolchain for ROM and Kernel. The default gcc version is 4.8. I tried 4.9. It compiled successful but can't boot up. So I just stick to 4.8

1. (source)/build/envsetup.sh

The following is my envsetup.sh.

The first modification(color red) is for ROM.

2nd modification(color red) is for kernel.

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

case $ARCH in

x86) toolchaindir=x86/x86_64-linux-android-$targetgccversion/bin

;;

x86_64) toolchaindir=x86/x86_64-linux-android-$targetgccversion/bin

;;

arm) toolchaindir=arm/Toolchain-linaro-$targetgccversion/bin

;;

arm64) toolchaindir=aarch64/aarch64-linux-android-$targetgccversion/bin;

toolchaindir2=arm/arm-linux-androideabi-$targetgccversion2/bin

;;

mips|mips64) toolchaindir=mips/mips64el-linux-android-$targetgccversion/bin

;;

*)

echo "Can't find toolchain for unknown architecture: $ARCH"

toolchaindir=xxxxxxxxx

;;

esac

if [ -d "$gccprebuiltdir/$toolchaindir" ]; then

export ANDROID_TOOLCHAIN=$gccprebuiltdir/$toolchaindir

fi

if [ -d "$gccprebuiltdir/$toolchaindir2" ]; then

export ANDROID_TOOLCHAIN_2ND_ARCH=$gccprebuiltdir/$toolchaindir2

fi

unset ANDROID_KERNEL_TOOLCHAIN_PATH

case $ARCH in

arm)

# Legacy toolchain configuration used for ARM kernel compilation

toolchaindir=arm/Toolchain-linaro-$targetgccversion/bin

if [ -d "$gccprebuiltdir/$toolchaindir" ]; then

export ARM_EABI_TOOLCHAIN="$gccprebuiltdir/$toolchaindir"

ANDROID_KERNEL_TOOLCHAIN_PATH="$ARM_EABI_TOOLCHAIN":

fi

;;

*)

# No need to set ARM_EABI_TOOLCHAIN for other ARCHs

;;

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

2. (source)/build/core/combo/TARGET_linux-arm.mk

modification as follow (color red)

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

# You can set TARGET_TOOLS_PREFIX to get gcc from somewhere else

ifeq ($(strip $($(combo_2nd_arch_prefix)TARGET_TOOLS_PREFIX)),)

$(combo_2nd_arch_prefix)TARGET_TOOLCHAIN_ROOT := prebuilts/gcc/$(HOST_PREBUILT_TAG)/arm/Toolchain-linaro-$($(combo_2nd_arch_prefix)TARGET_GCC_VERSION)

$(combo_2nd_arch_prefix)TARGET_TOOLS_PREFIX := $($(combo_2nd_arch_prefix)TARGET_TOOLCHAIN_ROOT)/bin/arm-linux-androideabi-

endif

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

*** Note my toolchain is (source)/prebuilts/gcc/linux-x86/arm/Toolchain-linaro-4.8

*** androideabi and eabi are under the same directory.

Hope it help .......
[Galaxy S 4 Mini Android Development] sysKin:
Hi, thanks for that. After spending a couple of hours I still can't make it build - compiler complains about various undefined symbols like time64_t.

Could you say what is it that you have under Toolchain-linaro-4.8? Ideally a link or exact local_manifest entry? I probably have something else (what I found is Christopher's arm-cortex_a15-linux-gnueabihf-linaro_4.8.4-2014.11-build_2014_11_25.tar.xz; more changes were needed to make that seemingly-work).
[Galaxy S 4 Mini Android Development] happyta5:
yep, i have errors compiling late nighties
[Galaxy S 4 Mini Android Development] sysKin:
Ahh, yes I wondered about that, I never know if it's the environment or the current code :)
[Galaxy S 4 Mini Android Development] sysKin:
Another random placebo-quality optimisation for you

Activate neon vector extensions, for real this time

In the file ~/android/system/build/core/combo/arch/arm/armv7-a-neon.mk, on the bottom, it says:

-mfpu=neon

However, our Krait can do better and this can be replaced with mfpu=neon-vfpv4.

HOWEVER, while GCC is OK with that, clang is not. So, let's hack it and use just 'neon' for clang:

In the file ~/android/system/build/core/clang/TARGET_arm.mk

(line 15) CLANG_CONFIG_arm_TARGET_EXTRA_CFLAGS := -mfpu=neon \

and

(line 22) CLANG_CONFIG_arm_TARGET_EXTRA_CPPFLAGS := -mfpu=neon \
[Galaxy S 4 Mini Android Development] happyta5:
Follow your instructions and it all went well. Thanks
[Galaxy S 4 Mini Android Development] ivankolev:
build/core/binary.mk:617: recipe for target '/home/ivankolev/CM12/out/target/product/klte/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/AudioMixer.o' failed

make: *** [/home/ivankolev/CM12/out/target/product/klte/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/AudioMixer.o] Error 1

Any ideas?

EDIT: For changing to -O3, I used:

find . -type f -name "*.mk" -exec grep -q "\-g\ " {} \; -print > out_g.txt; find . -type f -name "*.mk" -exec grep -q "\-O2\ " {} \; -print > out_o2.txt; find . -type f -name "*.mk" -exec grep -q "\-Os\ " {} \; -print > out_os.txt

for i in `cat out_g.txt`; do cp $i $i.bak; sed -i 's/-g //g' $i; done

for i in `cat out_o2.txt`; do sed -i 's/-O2 /-O3 /g' $i; done

for i in `cat out_os.txt`; do sed -i 's/-Os /-O3 /g' $i; done

found in http://xdaforums.com/showthread.php?t=2732298

And actually my error was: Using plain -O3 causes compilation error.

The solution: https://github.com/temasek/android_frameworks_av/commit/292d4e2c74d07287b7dc3b366e031f235e136fc8
[Galaxy S 4 Mini Android Development] saintxseiya:
Hi mates,

i am stuck, i can build builds for several other devices, but the I9195 just drives me crazy, it compiles fine though, but then it just does not boot, it hangs on the very first samsung splash screen, any ideas?

i am using the standard gcc 4.8 toolchain from cm and this is my local_manifest.xml for the device.

<manifest>
<!-- add github as a remote source -->
<!-- <remote name="github" fetch="git://github.com" /> -->

<!-- Main CM based Forks -->

<!-- <remove-project name="CyanogenMod/android_frameworks_base" /> -->
<!-- <project path="frameworks/base" name="Team-Hydra/android_frameworks_base" remote="github" revision="cm-12.0" /> -->

<!-- <remove-project name="CyanogenMod/android_packages_apps_Settings" />
<project path="packages/apps/Settings" name="Team-Hydra/android_packages_apps_Settings" remote="github" revision="cm-12.0" /> -->

<!-- add my device trees -->
<project path="device/samsung/serranoltexx" name="CyanogenMod/android_device_samsung_serranoltexx" remote="github" revision="cm-12.0" />
<project path="kernel/samsung/msm8930-common" name="CyanogenMod/android_kernel_samsung_msm8930-common" remote="github" revision="cm-12.0" />
<project path="device/samsung/serrano-common" name="CyanogenMod/android_device_samsung_serrano-common" remote="github" revision="cm-12.0" />
<project path="device/samsung/msm8930-common" name="CyanogenMod/android_device_samsung_msm8930-common" remote="github" revision="cm-12.0" />
<project path="vendor/samsung/serrano-common" name="TheMuppets/proprietary_vendor_samsung" remote="github" revision="cm-12.0" />
<project path="device/samsung/qcom-common" name="CyanogenMod/android_device_samsung_qcom-common" remote="github" revision="cm-12.0" />
<project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" name="arter97/arm-linux-androideabi-4.9" remote="github" revision="cm-12.0" />
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" name="arter97/arm-linux-androideabi-4.9" remote="github" revision="cm-12.0" />

<!-- <project path="kernel/samsung/msm8930-common" name="CyanogenMod/android_kernel_samsung_msm8930-common" remote="github" revision="cm-12.0" /> -->
</manifest>

Any ideas? Really would appreciate it!

Cheers

Saint.
[Galaxy S 4 Mini Android Development] jgcaap:
Try go to the kernel directory on terminal, and make definitions of your device. Perhaps when syncing is getting the wrong device.

Are you making any edits on build? Thanks
[Galaxy S 4 Mini Android Development] saintxseiya:
Hey,

naaa just the normal things, also tried not to use any local_manifest etc. still stuck, strange thing, as it happens only wikth this device.

Cheers.

saint
[Galaxy S 4 Mini Android Development] Miccia:
3g works?
[Galaxy S 4 Mini Android Development] saintxseiya:
no problem with jfltexx and klte, just this device is not booting up, tried to flash kernel afterwards, no chance.
[Galaxy S 4 Mini Android Development] Miccia:
Is possible that u messed up with the kernel or device tree

Delete the kernel/samsung and device/samsung directory and vendor too

Then source ./build/envsetup, repo sync and brunch serranoltexx
[Galaxy S 4 Mini Android Development] Cilenco:
I'm also really new to Android ROM development. Instead to the thread starter I want to build a pure AOSP ROM but I thought that it is very related to this topic so I post my question here. I also opened a thread at StackOverflow but the answer there is not really helpful for me. Can I build pure AOSP with the device and vendor files from CM and TheMuppets or maybe even a 5.1 build?

All other things should be clear so far (the CM tutorial is really great) but at the moment I only have a Windows machine and before I install Linux and so on it would be nice to know whether the whole effort worthwhile at all...

At last I really want to say thank you to [MENTION=5431488]sysKin[/MENTION] who had this great idea to start this thread. I'm sure that this can help a lot of people here and provide other searching people with information about compiler errors and so even if they do not have a S4 Mini.
[Galaxy S 4 Mini Android Development] sysKin:
In case someone wonders, branch 12.1 builds just fine these days. You can use the same SaberMod toolchain manifest as on page 3, it works perfectly.

SaberMod moved from GitHub to Gitlab, but I have yet to successfully clone anything from Gitlab (on any OS - it either closes the connection during fetching, or just never starts fetching), something's seriously wrong with it

I updated some recommendations on page to make them nicer/cleaner/less hacky.
[Galaxy S 4 Mini Android Development] sysKin:
Heyhey ~

I had more fun over the weekend and I FINALLY managed to build with GCC 4.9.

The good news is: no further code changes or fixes were needed. No more internal compiler errors or things like that.

The bad news is: it's still not perfectly clean.

So, here's what I did. First, I used the local manifest capability to bring Linaro 4.9 toolchain for arm-androideabi. I kept SaberMod's arm-eabi toolchain because I don't care about kernel all the much (I use F4k's) and also because, for some reason, Linaro git is not showing arm-eabi-4.9 of any kind.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="gitlab" fetch="https://gitlab.com/"/>
<remote name="linaro" fetch="https://android.git.linaro.org/git-ro/"/>

<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" />

<project name="SaberMod/arm-eabi-4.8" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" remote="github" revision="master"/>
<project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9-linaro.git" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" remote="linaro" revision="master"/>
</manifest>

As you can see, I'm using the manifest to drop Linaro's prebuilts into the "standard" unmodified arm-linux-androideabi-4.8 folder. Then I can just start a build without ever modifying any variables that select gcc version (I'm baffled as to why gcc selection is not made this way in the first place).

Now, for the funny bit: when trying to build, when it got to the kernel part, arm-eabi-gcc fails (!).

I poked it until I understood why: Linaro's toolchain is an arm-linux-androideabi toolchain (ie thumb and not kernel) BUT it seems to contain arm-eabi prebuilts too. Those arm-eabi binaries don't work (at least in this setup; their cc1 is not found) but the build setup is not smart enough and uses them instead of perfectly good SaberMod's arm-eabi.

So, here's a follow-up fix: go to prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin and delete all the files with name starting with arm-eabi.

Then, it builds!

Looking at Linaro repository, if I cloned "arm-linux-androideabi-4.9.git" (no -linaro suffix) I wouldn't have the arm-eabi files. Maybe it's the way to go, but I haven't tried.

Next thing to play with: newer clang prebuilts. Linaro has both 3.4 and 3.5, while we're building with 3.3.
[JASJAR, XDA Exec, MDA Pro ROM Development] moh6299:
hi hope someone can help ive installed the new rom on my xda JASJAR_WWE_20200_20305_11300 ubt voice command does not work for calling out incoming calls and reading tex mes.ive played round with the settigs but still can't get it to work. thanks in advance
[JASJAR, XDA Exec, MDA Pro ROM Development] gingerchristopher:
voice command

Hi I also had the same problems.

I ended up flashing back to Midgets v1 vanilla to solve the problem.

I like the voice command function its quite a nice feature on crossbow,

I have just flashed upto darkforces 2.10.02wwe radio 1.15 its fantasticly fast

but sadly no VC.

I have tried putting on CyberonVoiceCommand and MSVoiceCommand as

cab's but to no joy they still wont work.

Does anyone have a cab file that works on Darkforces 2.10.02 with 1.15

radio.?? or can point me in the right direction.

Thanks gingerchristopher
[JASJAR, XDA Exec, MDA Pro ROM Development] gingerchristopher:
voice command .cab

Ok after a bit of hunting around this weekend I found this CAB.

it is 1.6 ms voice command. I have popped it in om uni's sd card and loaded it up to the device and not the sd card. All is working fine it reads texts and transmits to my bluetooth headset ok. hope this is of help.

gingerchristopher

Edit: I can't attatch the cab file. pm me if you would like it. or gingerchristopher@hotmail.com
[XDA Assist] XDA Visitor:
Hi,

i am developing desktop application using kony framework.

1)when click refresh button in browser while working in the application, the page automatically navigate into login page.

2) when reduce the window size, it dynamically resize the text size.how it possible in kony.

3) When i am login loader is not appear in center.

4)I have changed arabic fonts, now new fonts appear in chrome, but not appear in IE.

please help me.
[Xperia Z3 Q&A, Help & Troubleshooting] Ertishop:
I was updateing my apps trough Aptoide, when it tired to update the Stock camera app it said "app installation failed" and my Stock camera app was gone, cant find it in the app store and the one in aptoide wont work says failed to install. It's a Rooted z3, can anyone help?
[Xperia Z3 Q&A, Help & Troubleshooting] Geeks Empire:
Info

the system app are inside stock firmware and u can just reinstall it by flash through recovery (it means system apps are not available on Play Store)

so u should search for flashable .zip of camera or Repair ur firmware by PC companion

:good:
[Xperia Z3 Q&A, Help & Troubleshooting] Ertishop:
When I do that flash trough recovery does my phone get reseted and loose everything? And if possible could you maybe give me a link to a flashable zip file
[Nexus 6 Q&A, Help & Troubleshooting] Williamsss:
I am trying to port a AOSP rom named optipop that is awesome from the nexus 5 to nexus 6 I have got the vendor/optipop setup and I have forked a couple tree device trees and kernel trees from other roms but I can't really find anything that compiles :/ I would love any advice or help! Thanks a bunch

https://github.com/OptiPop

https://plus.google.com/u/0/+WilliamCaseySedlacek/posts

I have read

http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code

and still no luck. Thanks a ton guys. Have a great Christmas
[Nexus 6 Q&A, Help & Troubleshooting] DespairFactor:
Are you still looking for help?
[Nexus 6 Q&A, Help & Troubleshooting] Williamsss:
I would love some help. I have a work around which is using host gcc at 4.6 rather than 4.8 however I would like an actual fix rather than a work around.
[Nexus 6 Q&A, Help & Troubleshooting] DespairFactor:
Sorry, I didn't get notified of your response, you can hit me up on hangouts, matthewdalex92@gmail.com
[Android Q&A, Help & Troubleshooting] android-volca:
I have Chinese a13 tablet

model t730

original firmware : nuclear_evb-eng 4.0.4 (ice cream sandwich )

but I want to upgrade it to jelly bean

so I try many flashes

one of them is fastjb 2.5

but the problem always was that the touch screen not working

so I try many t.s module and nothing help:(

... my question is : can I take the original T.s module from my original flash to faastjb ? and how ????:confused:

by the way my lsmod is

" dmard06 11314 0 - Live 0xbf10f000

rtl8150 10305 0 - Live 0xbf108000

mcs7830 7581 0 - Live 0xbf102000

qf9700 9152 0 - Live 0xbf0fb000

asix 24601 0 - Live 0xbf0ef000

sun5i_csi0 33255 0 - Live 0xbf0e1000

sp0838 19043 0 - Live 0xbf0d8000

sp0a19 20147 0 - Live 0xbf0cf000

ov2655 16871 0 - Live 0xbf0c6000

gc2015 19711 0 - Live 0xbf0bd000

hm2057 26251 0 - Live 0xbf0b1000

gt2005 20632 0 - Live 0xbf0a7000

sp2518 17349 0 - Live 0xbf095000

gc0308 19198 1 - Live 0xbf08c000

cedarx 9351 0 - Live 0xbf06f000

mali 150844 12 - Live 0xbf03d000

ump 49202 21 mali, Live 0xbf029000

gc0329 19530 1 - Live 0xbf020000

videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf

videobuf_core 20242 2 sun5i_csi0,videobuf_dma_co

ft5x_ts 45969 0 - Live 0xbf000000 "

please help me !!
[Android Q&A, Help & Troubleshooting] android-volca:
help
[MDA II, XDA II, 2060 General] dove_fohls:
helo, can u please help me with this BT problem, i can send files via Bluetooth but i can't receive any files in return although i have already checked the box "receive all incoming beams" and putting my BT status to discoverable.. please help.. i have already formatted my phone but still can't receive any files thru this.. please.. please.. this is somehow OK before but now.. it seems its useless to receive files. i am using xda2 unit with 1.66 ROM.. i am too afraid to upgrade my ROM since i have already read some problems about that.. . i hope there is still other way...thanks
[MDA II, XDA II, 2060 General] c_shekhar:
It is a known issue. The ftp modules in the otiginal ROMs are missing. please install broadcomm BT stack on your device and things shalll be much better....
[MDA II, XDA II, 2060 General] dove_fohls:
thanks!

thanks for your response...will try to search for that stack and i'll keep you posted.. thanks..
[MDA II, XDA II, 2060 General] dove_fohls:
broadcomm BT stack

can't find the file to download the broadcomm BT stack.. can u please send me the direct link or if possible the file itself for me to install it on my unit.. hoping for your response.. thank you very much..
[MDA II, XDA II, 2060 General] Rudegar:
search for widcomm then
[Galaxy Note 3 Neo General] wingedpanther:
Hello Guys,

We've created a dedicated Website for UNIKAT ROM

www.unikat.comxa.com​

Please do visit and give some suggestions :)
[Galaxy Note 3 Neo General] ersink:
You'd better if you include the root process, so the visitors can obtain all sources to install your rom by this site!
[Android Apps and Games] Medicina:
It takes all sorts of games to clear your mind and relax from the daily hustle and bustle. We're glad to offer one option you might've never tried before - instead of taking it out on innocent mooks, confront the root of problem directly! Well... as directly as mobile games allow. Here he is, your tyrant boss sitting right in front of you, ready for a death match. Take on him with any office supplies you find on hand, just like you so often had been tempted to! This amusing and peculiar timekiller is perfect for catching a quick and rewarding break at work. Try it and let us know what you think!

DOWNLOAD
[Android Apps and Games] Guypwnz:
Kind of game you need on your work:D
[Android Apps and Games] WazzApps:
Haha! It's an amazing game! Thanks! :)
[Android Apps and Games] Freddy_Five:
Cool game :) However, am I blind or is this app really not available on Google Play?
[Android Apps and Games] Vanel_Lion:
Wow! Awesome!
[Sprint HTC One (M8)] johnequickiii:
I was just wondering if anyone else noticed this. I used to be able to share a photo via long tap to multiple things, (Bluetooth, email, messenger...), but now I can only share to Scribble.

Any ideas? Kinda sucks they'd remove such a useful functionality and replace it with only Scribble.
[Sprint HTC One (M8)] johnequickiii:
Is there any way to change this at all? It really makes the process more complicated having to download something I only want to share, then having to go delete the download.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] 52yt:
If I am in 3.2.6， is that still OK？
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] EncryptedCurse:
No. You need to downgrade.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] 52yt:
how can I download？
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] 52yt:
downgrade
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] dr3yec:
So if I have TWRP 2.8.1.0 installed i should use thor-nexus-rom-v2.0.2_boot.zip ? If I want Nexus rom on the new bootloader?