Recent content by demlak

if you use "Greenify" and updated it.. maybe you get bootloop because of this.. when this is the case.. just uninstall greenify via adb in twrp.. if not.. i can't help

as described.. rom doesn't matter.. it's a bootloader-based problem on another partition.. just follow instructions

read the postings after this.. and use baord-search.. if you got question after this.. ask again

you have to use google to understand what fastbootmode, recoverymode and those commands are.. this thread is not for explaining basics, that are explained all over the internet...

maybe i should make a donate button, hrhr =)

as far as i know, it is compatible.. but i'm not 100% sure.. i did not test.. and i'm not involved into it... i would think that it is compatible, because it was made for 12.1 and was then made compatible for 13.. so why don't you just test it?

update... here is the working CameraBQ App für CM13 as attachment.. (just added file libarcsoft_panorama_burstcapture.so, as mentioned in here: http://www.android-hilfe.de/thema/rom-offiziell-cyanogenmod-13-fuer-das-bq-aquaris-x5-paella-nightlies.794870/#post-10052562) updated version of the...

Found a Solution.. just Download Camera App from here: https://s.basketbuild.com/devs/eloimuns/bq/piccolo/ (file: CameraBQ_signed_v4.1.0.zip) Unpack zip file.. go into folder: META-INF/com/google/android/ open file with texteditor: updater-script Replace every "piccolo" by "paella" "M5" by...

crash report on CM13: and logcat output: maybe this helps to get it working on CM13? seems to be a write-permission problem on dalvik?

does this fix your loop more then one time?

hehe.. you are all welcome.... should i make a donate button? *g*

and the world doesn't care about that you don't care... but remember: we are on a forum/board with many alternative firmwares and apps that mostly are developed/modified because of privacy concerns.. so, this is an essential topic on this forum/board... despite from your personal view

no change.. still tries to connect to *.1e100.net hosts (and for sure to some adblock.org hosts to update lists) after allowing to connect to adblock hosts.. gello also still wants to connect to 151.101.12.133

as i wrote a few pages before.. i use "firewall without root" to monitor which app is connecting to which host... i start gello-mod and for sure there is a google searchpage as startpage (why not blank page as default?).. then i go through every setting to get my privacy whishes reflected.. also...

startpage is set to blank a browser that is starting and that has not given any address nor any information is connecting to several hosts.. without information why it is connecting.. this let.me think about privacy problems