Search results

Looks good now :). Regarding -S 512M - probably older fastboot versions don't detect properly device properties, it should be auto-detected in all latest versions. Personally I use fastboot on my Debian in latest 6.0.1 version, and it worked for me without -S switch (but of course image was...

Spannaa - flashing your fastboot versions will break OTA updates in future if any of core low-level partitions such as bootloader differs from bak partition on the device. Official update firstly flashes new partitions, then updates backup partitions (this is to prevent hard-bricks if primary...

Sorry for late reply. I'm not quite sure how to help you because if device is not recognized even in fastboot mode then you most likely bricked it, although I don't know how you managed to do that, as I did the switch over dozen of times already and everything works as supposed to, other users...

Will be possible with new version I'm finishing right now, but without any support (aka not tested, use at your own risk).

At the moment we have rather dfficult situation because custom ROMs based on AOSP (such as my AD which is not yet public) require previous OOS LP firmware, while OOS 3.0 includes new MM firmware which breaks both older recoveries and custom ROMs. As I need to switch between OOS 3.0 and my AD...

# Device should define their GAPPS_VARIANT in device/manufacturer/product/BoardConfig.mk ifeq ($(GAPPS_VARIANT),) $(error GAPPS_VARIANT must be configured) endif I can work it around by specifying minimum required package and adding everything I want though, thanks :).

I'll switch to 6.0 for kernel later as well, but I'm testing things before doing so.

Sorry for double post, is there any way to exclude given packages from given variant? For example, I can notice here that packages are added to PRODUCT_PACKAGES. How about specifying extra variable, such as TARGET_GAPPS_EXCLUDED_PACKAGES, which would have to be defined in board config, and if...

This is exactly what I need. Thanks!

I'm currently testing my build for OP2 and I can't notice any need of extra -Os hacks or cherry-picks for any other repos apart from android_bionic fixes for GCC 5.3.1, if somebody wants to compile androideabi with something newer than 4.9. Any symptoms I should be aware of & check before...

Are there any plans on perhaps releasing odexed versions of GAPPS? I'm having fun with my AD and base system launches in 10 seconds after full wipe with my optimizations, I'm wondering if it's possible to ship GAPPS also in odexed versions. For non-being-updated core GAPPS taken from Nexus...

Booted for me :). And I confirmed that it's all that is needed.

I don't, I managed to do it by myself ;).

Yeah, although I don't agree with everything they're doing regarding optimizations. More is not better, tests, benchmarks and regressions should be done. I already spotted things that are not good. Anyway, the line I added to my board config seems to work. I'll see if it boots once whole ROM...

Nobody was born with AOSP Makefiles knowledge. I still have a lot to learn myself. I'm currently testing how aarch64 kernel toolchain works with my setup. If I succeed, even better, because I might be able to enable even more flags in final commit :).

Doesn't work for me as my device kernel seems to be using the same toolchain as the ROM (only one aarch64), and that one causes non-booting behaviour. Could you provide me with your local manifest, or all lines that redefine your used toolchains?

I don't know because I didn't even test that build when I heard that I can compile it with UBER 5.3. But I can say that no such issue happens on my latest working build with my optimizations and custom toolchains. I'm nearly done with my optimizations. I'm just sad that custom aarch64...

Just wait for the release as my current repo is one giant mess for testing everything I can for M release, so there's really no point in squashing it or even worse - merging, before I'm done.

Only those two? Plain easy then, haha. Thanks for fix for recovery size, I was wondering why my old ifneq resulted in syntax error. I'm pretty much done with 4.9 tests, but if only those two commits are needed for GCC 5.3 support then I'll be happy to test it too before a release. Some things...

Yes, as long as you resolve possible conflcits and other issues yourself.

You have many duplicated flags already defined by given optimization levels. Also are you really sure that you can build your ROM with UBERTC 5.3? It gives me many errors related to broken types such as char16_t. Probably because of default standard change between 4.9 and 5.0+.

Size of the build? No. Since when size of the build has any outcome on the performance that optimizations bring? Bigger is not faster - bigger is not slower either. Question is what you want to measure. Performance? It's enough to write 20 lines in C that will use internal binaries to do a...

... :cool:

Actually I might consider it, because I plan on testing my optimizations back on ARM as well, but I don't promise anything. "Maybe".

Just because some of you are wondering. Yes, I'm testing how M works with my optimizations, with UBERTC toolchains, and testing which newly introduced or previously disabled (for compatibility reasons) flags may work again. If you need simple copy-pasta that should work properly, you can find...

Yes, because root is enabled only on userdebug builds.

Out of scope of this thread, my optimizations to do not alter root inclusion. I've just started checking what can be adapted from old commit to M, so thanks for the heads up, I'll need to test another dozen of builds and devices to find optimal solution :).

No, I ended supporting SGS3.

Just wanted to stop by to say that I'm very glad somebody picked it up and fixed everything what was broken. Cheers.

I'll start working on it around end of the January, as I'm now pretty busy with my diploma project and everything next to it. It will come out, eventually.

Then you should know answer already.

2 toolchains are used, androideabi for ROM, and eabi for kernel. If you flash custom kernel, obviously kernel compiled with eabi toolchain is not being used anymore. So it depends to which TC you're referring to.

It should work if CM13 has working SELinux. If it doesn't, sorry, I do not plan on adding anything here anymore.

No, last version is running good for now, and I'll be busy for next month or so with my diploma project. If you have an urge to update to M as soon as possible, AD is not for you. If you don't have an urge, M will be released after I'm done with my things, with usual quality that all AD users know.

Yes, but it will take time. This is not a simple copy & paste, but actual hours spent on compiling and testing regressions. If I was about to put my optimizations in one image, it would be this:

Not sure if you're being serious or not.

Disable saving bandwidth in chrome, as that option causes proxying through google servers, and adblock can't work with that.

EOL means End Of Life, and end of life means that AD officially ended it's life, including everything connected with it such as my support, new releases, bugfixing, bug reports, and everything else. I don't want to close the thread because it may still be useful for people such as you, who are...

Yes to all.

ArchiDroid 3.1.5 Changelog ArchiDroid 3.1.5 - Newest ArchiKernel snapshot - Updated GAPPS, sources and other common things Download All Files XDA Stable: ArchiDroid 3.1.5 GitHub | XDA Direct | XDA Torrent Remember that you don't need anything else to flash. Google Apps are included already...

There's no commit. https://github.com/ArchiDroid/ArchiDroid/blob/i9300-cm-experimental/_archidroid/tweaks/build.prop/navibarON.sh

Nothing changed so there is no reason to release new version.

You don't need a reply from me. You just need to go to the recovery, install the AD ZIP you downloaded, and follow the instructions on screen. When AD wizard asks if you want to wipe your data, you should tell yes. If you want to be double-sure that everything is done properly, you can prior to...

ArchiDroid 3.1.5 Changelog ArchiDroid 3.1.5 - Newest ArchiKernel snapshot - Updated GAPPS, sources and other common things Important notes ArchiDroid 3.1 is major new release based on CyanogenMod 12.1 (Android 5.1.1 Lollipop). There are too many changes compared to previous release of AD...

ArchiKernel is now in official EOL state. You should not expect support or new releases anymore. As my kernel uses my own AnyKernel method, there's a high chance that it will remain compatible also with many ROMs released in a future. If you want to thank me for what you received, consider...

This ROM is in true EOL state and there won't be any build more, as I moved to OnePlus Two myself. Last build was here just to patch you for known security holes, and as I still had S3 around when I did build it. (Which doesn't mean that you can't fork my repos and build yourself)

CM12+ doesn't need any ART fixes.

AD can currently be installed only on i9300 and nicki (xperia m). However as I received brand new OnePlus Two, I do plan releasing AD for that device too.

How do you do fellow kids? :cool: I'm glad somebody is trying to make CM usable on OP2, most likely I'll help and contribute something too later, as I just got a device myself. Cheers Grarak for what you're doing!

Much appreciated :). Thank you!