yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Boss442:
This is amazing man!

Enviado desde mi Moto G mediante Tapatalk
[Android Software/Hacking General [Developers Only]] DexedrineXR:
Damn... Wish I had an international gs3. I'd be on SlimKat, find your thread and be like:

I'm gonna be 20 years old in about an hour... Should I ask?
[Android Software/Hacking General [Developers Only]] marcomarinho:
Great work :highfive:

I saw you had already a custom 4.10 linaro. If I use it, do I need to change anything on your commit?
[Android Software/Hacking General [Developers Only]] JustArchi:
It won't boot, stl port has segfaults when using GCC 4.9+. If you want to use it, sure, change TARGET_GCC_VERSION and include proper toolchain.
[Android Software/Hacking General [Developers Only]] marcomarinho:
Is this the best toolchain [stability/performance] to compile a ROM?

https://github.com/JustArchi/Linaro/tree/4.8-androideabi
[Android Software/Hacking General [Developers Only]] JustArchi:
Yes.
[Android Software/Hacking General [Developers Only]] marcomarinho:
Just one last question. Do I need to configure envsetup.sh to the custom toolchain directory?
[Android Software/Hacking General [Developers Only]] JustArchi:
No, but you need to add Linaro entries to your local_manifest.

https://github.com/JustArchi/ArchiDroid/blob/2.X-EXPERIMENTAL/__dont_include/roomservice.xml#L3
[Android Software/Hacking General [Developers Only]] micr0g:
Thank you [MENTION=5161352]JustArchi[/MENTION]

i make a build for Slimkat (nexus 5)

Everything is fine but just a noobish question,

I have to enable "TARGET_USE_O3=true" in BoardConfig.mk ?
[Android Software/Hacking General [Developers Only]] JustArchi:
No, you shouldn't have any commits apart from mine. It already specifies O3 for everything.
[Android Software/Hacking General [Developers Only]] Codename13:
Can I use a 4.7 toolchain with the ArchiDroid optimizations? I've tried compiling my kernel with different 4.8 toolchains before, and it's always resulted in boot loops.
[Android Software/Hacking General [Developers Only]] JustArchi:
Actually you can. Just change TARGET_GCC_VERSION back to 4.7.
[Android Software/Hacking General [Developers Only]] DeveDroid:
Well done mate, I'll try contributing from my side to this project :)
[Android Software/Hacking General [Developers Only]] ayoubij:
great work archi !! also after porting a fully working 4.4.2 touchwiz to i9300 is it possible to make aosp for i9300 more stable now? :)
[Android Software/Hacking General [Developers Only]] dragonnn:
@JustArchi which flags could be used for kernel compiling? And where should I put it in in the Makefile? I don't compile the complete ROM because I have to low machine for that, but I am developing a custom kernel for my Xperia Z. BTW Fajnie trafić na innych Polaków ;)
[Android Software/Hacking General [Developers Only]] pianistaPL:
Ktoś tu mówił o Polakach? :D

Świetna robota [MENTION=5161352]JustArchi[/MENTION] :highfive:
[Android Software/Hacking General [Developers Only]] JustArchi:
If you have whole ROM tree then you cherry-pick this commit, lunch your target and make bootimage. This is enough.

If you have standalone kernel, take a look at main Makefile :).
[Android Software/Hacking General [Developers Only]] JustArchi:
So it looks like Linaro bug. Nice to know. I'll just update my repos with daily snapshots and hope for the best then.
[Android Software/Hacking General [Developers Only]] Codename13:
****, just updated my Play Store to the latest version - and the corrupted app icons bug happens to me on my GCC Linaro 4.8 compiled CM10.2. Also, it seems like the screenshots for apps are corrupted too.

EDIT - Someone two posts up reported no issues when compiled with SaberMod 4.8. I'll try that later then.
[Android Software/Hacking General [Developers Only]] JustArchi:
Better try with Google's GCC, as I'm curious if it works fine.
[Android Software/Hacking General [Developers Only]] kenzolo:
[MENTION=5161352]JustArchi[/MENTION]

this commit is necessary only for GCC 4.8? or Linaro 4.7 , 4.8 sabermod..

"ART doesn't work in Android KitKat 4.4.2 with GCC 4.8. This can be fixed with this commit"

https://github.com/JustArchi/android_art/commit/8354d2d
[Android Software/Hacking General [Developers Only]] JustArchi:
Everything based on GCC 4.8+. Linaro 4.8, Google's 4.8, SaberMod's 4.8 probably as well.
[Android Software/Hacking General [Developers Only]] F4k:
No graphical glitch using Google's 4.8 toolchain, I have it with Linaro 4.8
[Android Software/Hacking General [Developers Only]] JustArchi:
Good. So graphical glitches are caused only by Linaro 4.8, Google's GCC 4.8 or SaberMod work properly. Nice to know that. Adding to the OP.

[MENTION=2332422]temasek[/MENTION]

(I update my 4.8 Linaro branch from time to time using daily snapshots so it's possible that Linaro team will deal with this problem soon)
[Android Software/Hacking General [Developers Only]] Orphee:
I guess I'm missing something but when I want to replace linaro with google in roomservices.xml :

I have this error while doing repo sync :

fatal: remote error:

platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8 is not a valid repository name

Email support@github.com for help

fatal: remote error:

platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8 is not a valid repository name

Email support@github.com for help
[Android Software/Hacking General [Developers Only]] kantjer:
I use that commit in my SaberMod 4.8.3 build and ART is confirmed to be working.
[Android Software/Hacking General [Developers Only]] JustArchi:
It depends on ROM you're compiling. CM uses strange policy and decided that they don't want AOSP repos at all.

Check your main manifest for proper reference to AOSP. It may be something like AOSP/platform_prebuilts... I'm not using CM so I don't know what they have.
[Android Software/Hacking General [Developers Only]] F4k:
I fixed that adding:

<project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" [B][COLOR="Red"]remote="aosp"[/COLOR][/B] revision="master" />
[Android Software/Hacking General [Developers Only]] JustArchi:
Nice!
[Android Software/Hacking General [Developers Only]] Orphee:
Thank you !
[Android Software/Hacking General [Developers Only]] Fred6681:
I can tell you that Within 2 or 3 hours!

It works on s3 mini although some apps not work .

Edit:

No problem app icons on playstore with linaro 4.9
[Android Software/Hacking General [Developers Only]] judas1977:
Thanks archi, I'm running omni (linaro) now, nothing spectacular though:), need some hours to judge...

No issues with Google play, maybe it depends on some factor (resolution?)

Now I'm compiling with sabermod..

Wysłane z mojego Blade przy użyciu Tapatalka
[Android Software/Hacking General [Developers Only]] ne0zone75:
Linaro GCC feedback...

Good afternoon ;)

[MENTION=5161352]JustArchi[/MENTION], just reporting back about your Linaro GCC toolchains with v2 optimizations applied on both CyanogenMod 11.0 and SlimKAT 5.2 source code :

ROM :

-> 4.7 : everything is working as smooth as possible... :good:

-> 4.8 : 'Play Store' bug ! Everything else is great... :highfive:

-> 4.9 : ROM is not booting ! :crying:

... kernel has always been compiled with 4.7 and the target device is a GT-I9195.

Best regards :D
[Android Software/Hacking General [Developers Only]] Codename13:
My Play Store updated some time earlier today or yesterday, and it looks like the corrupted icons/screens for apps in the Play Store have been fixed. I'm still running CM10.2 built with Linaro 4.8, so I guess the image corruption was some sort of problem on Google's end?? Why else would it be fixed after having updated to 4.8.19?
[Android Software/Hacking General [Developers Only]] Orphee:
I don't find update for play store, I'm on 4.8.19 with corrupted icons, could you check your version ?
[Android Software/Hacking General [Developers Only]] Codename13:
That's quite strange... My Play Store is 4.8.19, I'm running a build of CM10.2 built with Linaro 4.8, and there are no corrupted icons... The only resolution I can think of is that the corrupted icons are a fault on Google's end, the server side, and they're in the midst of pushing everyone onto the fixed server? Or something like that. Just to see if we have the same Play Store, do you have the new, more user-friendly permissions pop-up when trying to install an app?
[Android Software/Hacking General [Developers Only]] Orphee:
Yes, I downloaded the apk and pushed it with adb.

It didn't update itself to 4.8.19... the last automatic update is 4.6.17
[Android Software/Hacking General [Developers Only]] sidneyk:
OK, just did another clean build for Asus tf101. I grabbed linaro 4.8.3 prebuilt tool chain directly from linaro pages and built with your flags. Play store still showing corrupted icons. Other things seem fine. Antutu scores 10000+, better than normal. It's not the Play store because everything is fine when ROM built with standard flags and standard GCC 4.7. It's got to be either the particular linaro version or one or more of the flags used. Again, I'm on a Tegra 2 device. Gonna try a standard GCC 4.7 build with the flags and see what happens.
[Android Software/Hacking General [Developers Only]] sidneyk:
Build with standard GCC 4.7 and your flags on Omnirom, the Playstore is fine.
[Android Software/Hacking General [Developers Only]] Orphee:
When I try to compile with JustArchi's Linaro GCC 4.9 the compilation fails at net module...
[Android Software/Hacking General [Developers Only]] Cashreedhar:
I did my homework and searched everywhere and finally posting. This post is amazing and I want to try this. Myself not a developer, but want to know if " JustArchi's ArchiDroid Optimizations" have been implemented in any of the HTC One X or ASUS Nexus 7(2013) ROMs. Please let me know for any way to try this on my device
[Android Software/Hacking General [Developers Only]] Codename13:
What error do you get?
[Android Software/Hacking General [Developers Only]] Silesh.Nair:
I made a test build of AICP for endeavoru with the optimizations. Check here.
[Android Software/Hacking General [Developers Only]] shoey63:
Please use

<humongous log here>

when posting massive logs

;)
[Android Software/Hacking General [Developers Only]] sparksco:
If you've never compiled the kernel with a custom toolchain before you probably need some modifications to Makefile to make it compile.

Like this one should be able to cherry-pick or port easily.. Just make sure you have a GPL kernel source if you release something to the public.

https://github.com/AOSPAL/android_k...mmit/946fba66cc3c8d4d6052151fefb5650eab62df7a
[Android Software/Hacking General [Developers Only]] prstorero:
I'm working on implementing these commits on my own build of Slim for the Nexus 5 (last night was the first time I've ever compiled). At first I had a 10k drop in antutu and was told to do a make clean, so I'm in the process of doing that now. My main question now is how can i confirm that my build is using the gcc 4.8 toolchain? I followed this post by [MENTION=5161352]JustArchi[/MENTION] and it shows the correct gcc when the build starts, but that's just displaying it and would like to know if there's a way to confirm which one it's really using to build.
[Android Software/Hacking General [Developers Only]] JustArchi:
Add to your local manifest (if using 4.8):

Resync, after resync you should notice that your old 4.7 toolchain is gone.

If you did everything OK, you won't need it and your build will compile using only 4.8.
[Android Software/Hacking General [Developers Only]] prstorero:
I'm going to try that when i can get it to build again. For whatever reason i keep getting the error "make: *** [/home/scott/Slim/out/target/product/hammerhead/obj/SHARED_LIBRARIES/libdvm_intermediates/interp/Interp.o] Error 1" then the build stops. I think it started after doing the make clean.
[Android Software/Hacking General [Developers Only]] JustArchi:
In a few following days I'll make some experiments with new flags and some additional fixes. Big kudos to [MENTION=4328678]metalspring[/MENTION] for most of the tips.
[Android Software/Hacking General [Developers Only]] prstorero:
I got that done and did a repo sync, but the two folders were still there. So i just moved them out manually. Should i also get rid of the 4.6 one that's sitting in there? Also one more thing, in terms of the 4.8 toolchain I have the "arm-linux-androideabi-4.8" folder but not the "arm-eabi-4.8" one in prebuilts/gcc/linux-x86/arm/. I have a "gcc-4.8.0" on my desktop, but that doesn't contain the same stuff as the ones that came when i synced the repo. I got it from the official download, but maybe there is some different thing I'm supposed to use (Should i just get rid of that?). Aside from these questions, I did get a build going with your commits and thing seem to run nicely :)

Edit: I got the code right for removing the 4.7 chains now. I was led to believe that the local manifest was in platform_manifest so that's where I had them haha. Once i moved those lines to the proper file i saw them get deleted and the other 4.8 folder that was missing is now there.

Edit2: [MENTION=5161352]JustArchi[/MENTION] could you take a quick look at the files that are supposed to be modified according to your github? My files were a little different compared to the ones you show'd both in terms of line numbers and the lines to remove were slightly different. I just want to make sure things look like they should. If so then I'm all set. LINK
[Android Software/Hacking General [Developers Only]] Silesh.Nair:
I am compiling cm with the new flags. Lets see how it goes.
[Android Software/Hacking General [Developers Only]] JustArchi:
You applied some third-party magic O3 optimizations before mine, this will conflict and result in some flags being ignored.
[Android Software/Hacking General [Developers Only]] prstorero:
[MENTION=5161352]JustArchi[/MENTION] Dang it must be slims stuff. Could you tell me what they are so I can delete them (or is it just any line that has O3 in it before your code)? Also after doing so would i need to do a make clean again?
[Android Software/Hacking General [Developers Only]] shoey63:
You will have to browse the code, and manually apply changes. Obviously cherry picking won't work if lines have already been altered.

And yes, make clean + wipe. /..cache
[Android Software/Hacking General [Developers Only]] prstorero:
Alright dang. I'm not even sure of what to delete; only been compiling for a couple days now so i obviously don't have much experience. I assume it's anything that has O3 in it but I could be entirely wrong.
[Android Software/Hacking General [Developers Only]] kantjer:
Look here, al the repo's starting with SlimSaberKat contain the necessary commits to build Slim for the S4, should get you started for the Nexus 5 also.

That in combination with the local_manifest sugested by [MENTION=5161352]JustArchi[/MENTION] should be sufficient.

My local_manifest looks like this (I'm building with SaberMod)

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<remote name="SaberMod"
fetch="https://bitbucket.org/Cl3Kener/" />

<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" />
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" name="sm-arm-eabi-4.8" remote="SaberMod" revision="master" />
<project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" name="sm-arm-androideabi-4.8" remote="SaberMod" revision="master" />
</manifest>
[Android Software/Hacking General [Developers Only]] prstorero:
Alright cool but I don't think that addresses the problem of having some of Slims stuff in there that causes [MENTION=5161352]JustArchi[/MENTION]'s flags to be skipped. These are the two files in question where I added his commits. In regards to toolchains, I'm using just the standard gcc 4.8, so no sabormod, but my local manifest does look like yours for getting rid of the old and setting the new one, so I think that is taken care of.
[Android Software/Hacking General [Developers Only]] kantjer:
These commits are all based on the Slim source,so conflicts, and all I need to built with all optimizations. Building using Linaro 4.8 isn't a problem I also tried that.
[Android Software/Hacking General [Developers Only]] prstorero:
So because I'm building from Slim's source, there will be conflicts? If so how do i get rid of them? I'm not sure if that's what you meant, if it wasn't then I apologize.
[Android Software/Hacking General [Developers Only]] kantjer:
No the opposite. The commits on my repo are based on the Slim source so I expect you can cherry pick them without any problems.

Just sync with the Slim source

apply these commits (modify the ~/SlimSaberKat path to match your system)

cd ~/SlimSaberKat/build/core/combo/
git fetch https://github.com/kantjer/SlimSaberKat-android_build/ && git cherry-pick 416bcf71cf684b33f34e39d0afd2a8652e0960ab

cd ~/SlimSaberKat/hardware/qcom/display-caf/
git fetch https://github.com/kantjer/SlimSaberKat-android_build/ && git cherry-pick 3be332c5d349de1c49d5450199c37cf5d18d4a8a

cd ~/SlimSaberKat/frameworks/rs/
git fetch https://github.com/kantjer/SlimSaberKat-frameworks_rs/
git cherry-pick d18fd8f97765759b2604ba0bc1df836db97bd25b
git cherry-pick 439b96cb6c88a6f968fde1d83c86043fa8afa6d2

cd ~/SlimSaberKat/art/runtime/
git fetch https://github.com/kantjer/SlimSaberKat-android_art/ && git cherry-pick ee63c833fcb08c24506dcb9e01810fe03055f5ea

. build/envsetup.sh

lunch slim .......

make clean

make -j4 bacon
[Android Software/Hacking General [Developers Only]] prstorero:
Alright all but 3 of those worked without an error. Below i put which commits caused which error. I used the curly braces to encase the corresponding error to the git fetch.

git fetch https://github.com/kantjer/SlimSaberKat-android_build/ && git cherry-pick 3be332c5d349de1c49d5450199c37cf5d18d4a8a

{

fatal: bad object 3be332c5d349de1c49d5450199c37cf5d18d4a8a

}

git cherry-pick d18fd8f97765759b2604ba0bc1df836db97bd25b

{

error: Your local changes to the following files would be overwritten by merge:

Android.mk

Please, commit your changes or stash them before you can merge.

Aborting

}

git cherry-pick 439b96cb6c88a6f968fde1d83c86043fa8afa6d2

{

error: Your local changes to the following files would be overwritten by merge:

cpu_ref/Android.mk

Please, commit your changes or stash them before you can merge.

Aborting

}
[Android Software/Hacking General [Developers Only]] kantjer:
I thinks those are the result of your earlier tries. Perhaps it's best to start again with a clean repo.

Delete all the files creating errors from your local source and sync again.
[Android Software/Hacking General [Developers Only]] prstorero:
Alright it worked after deleting the folders and doing a fresh sync, so I'm compiling a build now. Can i ask why you suggested make bacon? From my understanding that's more of a CM thing. I've been compiling with "make -j4 -o3 otapackage"
[Android Software/Hacking General [Developers Only]] kantjer:
"make bacon" will give you a zip like the stock version, otapackage will be much larger with a lot off overhead.
[Android Software/Hacking General [Developers Only]] prstorero:
Ah the overhead would probably explain why it takes longer than it should to compile. I'll probably switch to bacon then. Is the -o3 fine to leave in there as well?
[Android Software/Hacking General [Developers Only]] kantjer:
just use "make -j4 bacon" or what jx you want to use.

All optimization like O3 are set in TARGET_linux-arm.mk
[Android Software/Hacking General [Developers Only]] prstorero:
Ah alright awesome. I'll be sure to let you know how things go after (hopefully) my build finishes with no errors and i get it flashed. Thanks for all the help, i really appreciate it.

Edit: The build failed. I think Slims source had something change because it didn't seem linked to any changes I made from your commits. Guess I gotta wait and try again.

Edit2: I did a new repo sync and re-did the commits and all but one work. The one regarding the display-caf refuses to work even after deleting the folder and a fresh repo. So i left that one off for now and am trying a new build with bacon.
[Android Software/Hacking General [Developers Only]] sidneyk:
Did a build for Asus tf101 on omni with your flags and linaro-4.7. It builds and boots and play store is fine but my internal /sdcard shows empty and external formatted as ext4 shows but won't let me do anything with files. Normal android gcc 4.7 all is fine, without the flags.
[Android Software/Hacking General [Developers Only]] kantjer:
sounds a bit like an issue I was having after building with SaberMod 4.8 and all optimizations set.
[Android Software/Hacking General [Developers Only]] judas1977:
@up

Try to make clear/clobber

Edit: i think i saw commit fixing that error, but don't remember exactly
[Android Software/Hacking General [Developers Only]] prstorero:
Started getting the same error consistently when building whether I did a make clean or not. Switched my toolchain back to 4.7 and it passed the error no problem. For what ever reason 4.8 just stopped working. I've had a successful build with it before so I'm not sure what happened with it. Guess I'm stuck with 4.7 lol.
[Android Software/Hacking General [Developers Only]] sidneyk:
That could be it, that some optimization just isn't compiling something right. I'm trying another build now on Omnirom with linaro-4.7 tool chain and the only flags I'm changing are -O3 for the first part and -O2 for the thumb parts. We'll see what that does. If I get the same issue then I'll try a build with linaro-4.7 and leave all the flags at the standard settings and see if it even builds. I am cleaning .ccache and doing 'make clean' AND 'make clobber' before each build, just to be sure. I'm doing user debug builds, though, with '. build/envsetup.sh' then 'brunch tf101'. Easier for my testing because the other way takes too much space and forces me to use the PA micro gapps package, meaning I have to find some of the gapps pieces on Play store, that I normally use to test things, which are already in the PA mini gapps package.
[Android Software/Hacking General [Developers Only]] irocevo:
Can anyone help me fix a couple errors I keep getting or at least point me in the right direction.

http://paste.ubuntu.com/7545749/

edit: New Build gives me these errors. Help Please.

/media/iroc/storage500/cm11/kernel/htc/msm8960/net/bluetooth/hci_conn.c: In function 'hci_le_ltk_reply':
/media/iroc/storage500/cm11/kernel/htc/msm8960/net/bluetooth/hci_conn.c:407:28: warning: argument to 'sizeof'
in 'memcpy' call is the same pointer type '__u8 *' as the destination; expected '__u8' or
an explicit length [-Wsizeof-pointer-memaccess]
error, forbidden warning: hci_conn.c:407
make[4]: *** [net/bluetooth/hci_conn.o] Error 1

.............................................................................

In file included from /media/iroc/storage500/cm11/kernel/htc/msm8960/drivers/usb/gadget/android.c:50:0:
/media/iroc/storage500/cm11/kernel/htc/msm8960/drivers/usb/gadget/f_qdss.c: In function 'qdss_bind_config':
/media/iroc/storage500/cm11/kernel/htc/msm8960/drivers/usb/gadget/f_qdss.c:586:38: warning: argument to
'sizeof' in 'strncmp' call is the same expression as the second source; did you mean to provide an explicit
length? [-Wsizeof-pointer-memaccess]
error, forbidden warning: f_qdss.c:586
make[5]: *** [drivers/usb/gadget/android.o] Error 1
make[4]: *** [drivers/usb/gadget] Error 2
make[3]: *** [drivers/usb] Error 2
make[3]: *** Waiting for unfinished jobs....
[Android Software/Hacking General [Developers Only]] :
how do i clear CCACHE ?
[Android Software/Hacking General [Developers Only]] JustArchi:
rm -rf ~/.ccache
[Android Software/Hacking General [Developers Only]] irocevo:
rm -rf /home/username/.ccache

edit:

JustArchi you are quick. either way will work