yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] dankoman:
Re: app incompatibility, if it's any consolation, here's proof that an app showing as incompatible will still successfully update regardless...
[Nexus 5 Original Android Development] Garrykd:
Yup, I'm just as fed up as probably everyone is about this, it's been quite frustrating. I don't think it's really about those 2 apps though. They were just the ones [MENTION=2495716]chikimonke[/MENTION] (bright weather) and I (rr3) used as a reference to indicate that there was incompatibility....I'm sure there are other apps that are the same. I personally think that it really should be up to the developers to make more inclusive apps. In the case of real racing, Electronic Arts maintains very strict control over what devices the game is compatible with. It actually runs fine at 420dpi and 370dpi It's almost an arbitrary choice so they can limit the support they need to do. I've emailed them about this very issue and have had no response (not surprising with such a large company).

Anyway, the real reason I asked for an unhacked play store is because I was not getting play store notifications and have not been for a couple of months. I had read that it might have been associated with the changes made to the play store to allow multi dpi. Turns out that it might be more complex than that or the 2 issues might not be related at all.

If I can get update notifications again I'll be pleased as punch, I can deal with the incompatibility issue, that's secondary.

I am overjoyed that you took time out of your life to try and accommodate some of the users here and appreciate it immensely.

So thanks and don't sweat it. Now, I've pinned a Google poster and EA poster to the wall.....darts anyone?

Candy Crush Saga ?? Eeeeeeeww
[Nexus 5 Original Android Development] phin586:
Latest google+ keeps crashing on me while on 5.4
[Nexus 5 Original Android Development] dankoman:
oh come on now, i haven't played it in ages...

---------- Post added at 06:21 PM ---------- Previous post was at 06:20 PM ----------

don't get me started on g+. i can't even get it to decompile so i can theme it.
[Nexus 5 Original Android Development] pkelly517:
I broke down and downloaded the PA micro gapps today. GPS at -52. Immediate Nova update notification. No trds, but no fight either. And, to be honest, if I don't have to update manually, I never go into Play Store, so I won't notice.

Maybe tomorrow the whole thing collapses like everyone else has seen. We'll see.
[Nexus 5 Original Android Development] Garrykd:
When I was using the PA gapps I received notifications. It wasn't until I switched to the slim gapps that the notifications stopped.

I just haven't been able to bring myself to go back....I like the slim trds package and the folks responsible for them. :)

Keep us updated ....it might be of help in the long run. ;)
[Nexus 5 Original Android Development] raycaster3:
I use team blackout clear/black (depending on the day) playstore (.20 version is still in testing but I'm using it) and though it isn't trds compatible I've never had compatibility or notification issues with it. Strange.

Sent from my Nexus 5
[Nexus 5 Original Android Development] dankoman:
Guys the play store I posted last night updates, promise! I messed up the last one I did, but this one updates - try it!

http://d-h.st/rUQ

to reiterate, this is identical to the one I posted last night. It definitely updates.
[Nexus 5 Original Android Development] efan3719:
We can just rename to phonesky and push to system right?
[Nexus 5 Original Android Development] the.emilio:
Delete it using slim sizer and install from play store. Its named plusone.apk I think in slim sizer
[Nexus 5 Original Android Development] pkelly517:
Will do, although I may not have even done it right.

Reboot to recovery, flash micro gapps. An hour later, I cleared cache/data for both Play store and gps. I saw that the BW wasn't compatible. Now it is.

Edit: was. Maybe I get updates manana, maybe not.

---------- Post added at 06:45 PM ---------- Previous post was at 06:44 PM ----------
[Nexus 5 Original Android Development] Grondinm:
so maybe no one will be interested in this but here is a small crude script i made to build slimkat. it can be executed like so:

./build.sh <devicename> fetch clean

or replace fetch with anything else if you only wish to clean or just omit both to just build...i know it's not written the best but my skills are limited and it works...

#!/bin/bash
export USE_CCACHE=1
export CCACHE_DIR=/home/marcg/.andccache
export device="$1"
source build/envsetup.sh
sleep 2
if [ "$2" == "fetch" ]
then
echo "Get new source"
repo sync
if [ "$?" != "0" ]
then
exit $?
else
echo "Source synced"
fi
fi
if [ "$3" == "clean" ]
then
echo "Clearing old build"
sleep 2
make clean
fi
echo "Building for $device"
sleep 2
brunch $device

it is setup to enable and use ccache so if you don't wish to use that just comment out those lines or modify the path to the ccache dir and make sure to create that dir first and install ccahce if you wish to use it...

EDIT:Updated script to use make clean instead of clobber

EDIT2: i should mention this script should be placed in the root of your android source tree.
[Nexus 5 Original Android Development] dankoman:
Yes, make sure permissions are rw-r--r--.

And make sure it's in priv-app
[Nexus 5 Original Android Development] Garrykd:
.....maybe clear data for play store as well
[Nexus 5 Original Android Development] Poser:
Sensei: Given that it is was one of the most abhorrently coded pieces of dung for a long time (though much better now), I am not holding my breath. Not a biggie.

Well played sir.
[Nexus 5 Original Android Development] efan3719:
As soon as I did that I got two updates. So looks like that portion is working as it should.

Edit...... And now app compatibility seems to be fixed. Real Racing 3 and Bright Weather both show up fine. Wonder how long that'll last...
[Nexus 5 Original Android Development] RobbieL811:
Maybe you should change "make clobber" to "make clean". Doesn't "make clobber" delete your ccache when it is run? If you change it to make clean, it will keep your ccache and build alot faster instead of recompiling all of the cache. I'm not positive but this is what I think.
[Nexus 5 Original Android Development] Grondinm:
i don't think it does...but now i will have to check for sure...
[Nexus 5 Original Android Development] RobbieL811:
I know that when I run "make clobber" on my machine instead of "make clean", it takes WAY longer to complete the build. Like it is recompiling the ccache. Try it one time. I may have just been on drugs at the time and been imagining things!!!
[Nexus 5 Original Android Development] Garrykd:
Ccache isn't in the build directory, is it?
[Nexus 5 Original Android Development] RobbieL811:
/prebuilts/misc/linux-x86/ccache?
[Nexus 5 Original Android Development] Grondinm:
that's the executable....the actual cache dir has to be specified...i don't think that gets cleaned by make clobber...also ignore what i said about having to install ccache as it does come as part of the tool chain...
[Nexus 5 Original Android Development] prbassplayer:
Ccache isn't enables by default you need to specify the path, size and else it. If your machine uses ccache and you make clobber builds will take longer because it no longer has the ccache which needs to be rebuilt. That doesn't mean the act of "rebuilding" it makes it slower it just means the compiler doesn't have it to be faster. Remember ccache just stores bits of previous compiles to reuse later on.
[Nexus 5 Original Android Development] RobbieL811:
Like I said. It just takes me a lot longer to build when I run make clobber. Probably about 10 minutes with make clean, probably about 30 with make clobber. Thanks for the script though!

Sent from my Nexus 5
[Nexus 5 Original Android Development] Grondinm:
so make clobber does clean the ccache...thank you for that info
[Nexus 5 Original Android Development] RobbieL811:
That's what i thought. I knew I wasn't going crazy!

---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------

This is what I meant. I guess I just worded it wrong. Thanks.
[Nexus 5 Original Android Development] Garrykd:
What he said ^^^^^ :)
[Nexus 5 Original Android Development] crford:
Not true. make clean and make clobber do the exact same thing. Here are their references from the build/core/main.mk

.PHONY: clean
clean:
@rm -rf $(OUT_DIR)/*
@echo -e ${CL_GRN}"Entire build directory removed."${CL_RST}

.PHONY: clobber
clobber: clean
[Nexus 5 Original Android Development] RobbieL811:
Like I said. All I know is that it takes me 3 times as long to build after a make clobber. Prbassplayer confirmed my suspicion too.

Sent from my Nexus 5
[Nexus 5 Original Android Development] crford:
It's totally placebo. Neither one touches CCACHE

http://wiki.cyanogenmod.org/w/Doc:_make_clean_vs_make_clobber

make clean does the same thing as make clobber, which is removing all generated files ($OUT_DIR).
[Nexus 5 Original Android Development] efan3719:
has anyone experienced an issue with Hangouts and MMS recently? havent been able to receive them. it says it's sending one when it should be receiving one. using [MENTION=1277872]dankoman[/MENTION]'s latest inverted Hangouts apk.
[Nexus 5 Original Android Development] tracerit:
anyone able to make nandroid backups using Online Nandroid Backup app? For me it just keeps backing up /data forever. Been waiting at least an hour before I quit the operation.
[Nexus 5 Original Android Development] efan3719:
i use it. has always worked just fine. might wanna ask in the app thread for help.
[Nexus 5 Original Android Development] tracerit:
how long does it take for you to make a nandroid through the app? whats your final size?

when i make nanddroids through recovery, they're 3.8GB uncompressed and it usually takes 3-4 minutes.
[Nexus 5 Original Android Development] efan3719:
mine is 1.54 GB, but i dont backup /cache and a few other things. and my install might be a different size than yours. and i'm not sure how long it takes as i run it on a schedule at night but i dont remember it taking very long. it'll probably not be as fast as when you're in recovery though. i know the app developer is back from a bit of break and i working on fixing some of the issues and has requested people with problems to notify him in the thread of via PM. so if you are experiencing issues now would be the time to bring it to his attention. he just recently posted a changelog for the app that already has some fixes.
[Nexus 5 Original Android Development] the.emilio:
Off topic... GO SPURS GO!!!!!
[Nexus 5 Original Android Development] rockknee:
Is there a way to get rid of that stupid "space left xx GB" thing that appears always when new app is installed or updated. No brainer feature really. I didn't find anything from settings and I searched this thread and slimroms FAQ. ?
[Nexus 5 Original Android Development] pseudoheld:
i dont have that message...im guessing its a "feature" of some app you have installed.

install "burnt toast" xposed module to see which app posted that message!
[Nexus 5 Original Android Development] rockknee:
Ok. Thanks for pointing me that it's not ROM related.

---------- Post added at 01:15 PM ---------- Previous post was at 01:02 PM ----------

I take my words back. Burn toast didn't indicate that as related to any app and it has not happened before with these same apps. So it must be ROM feature. Using latest "official" build
[Nexus 5 Original Android Development] Natakranta:
Yes it does. I've just got notification in the morning.

Though compatibility is lost on 420 and doesn't seem to come back.
[Nexus 5 Original Android Development] lets_zock:
Do you have ES File Explorer? I think I read about this before and it was the fault of ES. I'm sure it's 100% related to an app.

EDIT: Jep, I just installed ES to test it out. Instantly got this notification. It's the one regarding low space here:
[Nexus 5 Original Android Development] rockknee:
Yes confirming this.
[Nexus 5 Original Android Development] dark_ente:
Please check the link again, it leads to my folder, not yours
[Nexus 5 Original Android Development] Garrykd:
notifications yay

I'm so excited I had to send this from on the river

I have play store notifications!! Thanks Dan!
[Nexus 5 Original Android Development] chikimonke:
Yeah, I posted about the same thing a couple days ago. Do you happen to be connected to wifi when the issues are happening? I've found that if I turn off wifi, everything goes through as it should. I'm on T-Mobile in the US. I've been experiencing it for much longer though, well before [MENTION=1277872]dankoman[/MENTION] 's first TRDS version.
[Nexus 5 Original Android Development] dankoman:
Is anybody using a play store version that makes compatibility stick permanently? If so, tell me which version and I'll try to see what they're doing and port it over to our version.
[Nexus 5 Original Android Development] csolanol:
I am not having compatibility issues but i don't get play store notifications.

Edit: Using 410 dpi
[Nexus 5 Original Android Development] efan3719:
Yeah that usually works for me to but now it isn't working. Must be something on my networks end

Sent from my Nexus 7
[Nexus 5 Original Android Development] Anthonok:
Edit

Sorry wrong thread. Never did that before
[Nexus 5 Original Android Development] AvRS:
Have you tried the latest version shared by Dankoman a few pages back?
[Nexus 5 Original Android Development] csolanol:
I was just answering Danko, not complainning ?
[Nexus 5 Original Android Development] DrunkFuX666:
Guys is there a way to get a "clear all" button in the Slim Recents bar, or any option to clear all for that matter...?

Sent from my Nexus 5
[Nexus 5 Original Android Development] EQ811977:
No! But keep the accidental thanks!
[Nexus 5 Original Android Development] Anrikus:
From the Slim FAQ (http://www.slimroms.net/index.php/faq/slimbean/436-how-do-i-close-all-apps-in-the-new-slimrecents)

About the button:

Again from the Slim FAQ (http://www.slimroms.net/index.php/faq/slimbean/414-will-you-add-the-kill-all-in-recents)
[Nexus 5 Original Android Development] micr0g:
No it doesn't.

The link lead to personal folder account (it was mistake) that's why you see your folder when you click on it.

Working links

https://www.mediafire.com/folder/mjtldd7vaw2eb/Linaro_4.10_ROM._4.8_KERNEL.

https://www.mediafire.com/folder/czfrz62mch10u/Sabermod_4.10_ROM._4.8_KERNEL.
[Nexus 5 Original Android Development] Natakranta:
Dan's hacked, TRDSed Play Store 4.8.20 and GPS 4.4.52 (1174655-038). There was Shuttle+ update since about noon, but I got notification only after a reboot. After second reboot notification did not appear. It looks like notification appears only once and then an update is labeled as "notified".
[Nexus 5 Original Android Development] pseudoheld:
just noticed that the "OK Google" hot word detection seems broken for me.

when i launch google now it doesn't react to "ok google" (the hotword detection is set to "ON")

anyone else have this?
[Nexus 5 Original Android Development] AvRS:
I was only asking if you've tried as that's what was being asked about as he said he fixed things in the latest that he forgot about in the previous.
[Nexus 5 Original Android Development] csolanol:
Oh ok, thanks but as i don't have compatibility issues i will wait until next weekly to update to latest dankoman gapps
[Nexus 5 Original Android Development] dankoman:
Spoke to soon :(
[Nexus 5 Original Android Development] yaatzek:
Ok, I will give it a go. Will report tomorrow.
[Nexus 5 Original Android Development] Garrykd:
[MENTION=1277872]dankoman[/MENTION]'s day today ;) :
[Nexus 5 Original Android Development] yaatzek:
Answered to soon...
[Nexus 5 Original Android Development] dankoman:
In case anyone is wondering, the next upcoming official gapps will have play store version 4.8.20, but the smali hacks from the old version have been brought over to the new version. This means that once again, auto updates will not work, and Google will think you're using a 240 dpi device. I have reverted all of my modifications except TRDS for this version because nothing seems to help compatibility issues in the long run.

When you update tomorrow, I suggest you wipe system manually and if you're gonna dirty flash, remove any updates for play store, Google play services, and Google services framework from /data/app/. This way we can all be on the same page and using the same versions next week.
[Nexus 5 Original Android Development] chikimonke:
Alright so I've been running at stock DPI for the day and everything has been running quite well. I'm not sure if it's placebo or what, but the interface actually seems snappier. Less lag in the UI as a whole. I'm not sure if there's any correlation there or if it's the mushrooms again, but it's not something I was looking for but started to notice.

[MENTION=1277872]dankoman[/MENTION], has there been any discussion amongst the team of sticking with stock DPI for the time being, since none of the old hacks seem to work fully right now? I know that's blasphemous talk in these parts, but it could alleviate these problems for now, while a solution is figured out. Then, the folks that still want the smaller DPI can edit it themselves, knowing that it will at least partially break things for now. Just thinking out loud here.
[Nexus 5 Original Android Development] Grondinm:
good stuff. care to share the new package for us selfbuilders....
[Nexus 5 Original Android Development] ralpheboyo:
Concur..... Additional benefit as well is that applying themes is so much easier and problem free....

Seriously have you checked slim FAQ:

http://www.slimroms.net/index.php/faq
[Nexus 5 Original Android Development] Tylog:
No, we don't plan to change the Base DPI to Stock.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] RobbieL811:
Good deal! Nobody wants that 480 crap! Looks like an 8 year olds phone.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Grondinm:
a bit OT but can i just mention that if you are going to use ccache to build android make sure to increase the size of the cache to something bigger than 1G
[Nexus 5 Original Android Development] dankoman:
i'm not sure how much of the rest of the team is even aware of these issues. in no way do i speak for the rest of the team, but i don't foresee them changing to 480 dpi (yuck!) by default though. hypothetically, i think the consensus would most likely be to figure out the issue and nail it rather than make sacrifices like that.
[Nexus 5 Original Android Development] chikimonke:
Makes sense. Just figured I'd throw it out there for discussion. So that being the case, will you guys hurry up and fix it already :D
[Nexus 5 Original Android Development] prbassplayer:
No it doesn't. I don't have the resources right now to grep where else it's handled but clobber deletes ccache and out. Clean just does out. Proof of concept set up a ccache for elsewhere compile a few times and it gets filled. Make clean and it almost doesn't change. Make closer pretty much deletes almost all of the stuff in ccache. It makes a HUGE difference, trust me we do this a bit lol. Same as to minimize compiling times having your source and ccache on different drives greatly decreases compile times, and ssd's doesn't decrease compile times that much compared to a 7200rpm disk drive (as in it isn't worth the investment) ;)
[Nexus 5 Original Android Development] RobbieL811:
Having my coached setup on my other drive will make my compile times faster? I have it setup on my ssd along with my source. How can I put it on my HDD?

Sent from my Nexus 5
[Nexus 5 Original Android Development] dankoman:
oh come on, 10 mins isn't fast enough for you? :p
[Nexus 5 Original Android Development] RobbieL811:
Lol. Just trying to learn my man. I can definitely handle it at 10 minutes. Lol.

Sent from my Nexus 5
[Nexus 5 Original Android Development] aow1980:
Talk Nerdy To Me http://youtu.be/JO6eydRPpyU

Sorry it's ot but every time I see this I think of the Slim team.
[Nexus 5 Original Android Development] dankoman:
weekly 5.6 incoming :D

https://gerrit.slimroms.net/#/c/8570/

new 5.6 official gapps are up too:

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4
[Nexus 5 Original Android Development] prbassplayer:
During testing on decent desktop (Sandy bridge quad 3.6 ghz, 16Gb ram with j9) the difference between having ccache on same drive vs different drive was I believe about 20 mins. Using ssd was maybe 5 mins. His very fastest speed was with source on ssd and ccache on 7200rpm drive.

As to how to do that you need to export

export CCACHE_DIR=

And

export CCACHE_BASEDIR=

To the correct paths

Edit: like to point out that those where tests doesn't mean it will be the same for everyone all the time, but logically HDD and SSD have a r/w queue time, if both source and ccache are on the same drive they compete for that queue vs having there own on different drives.
[Nexus 5 Original Android Development] Aerowinder:
And... it's out.
[Nexus 5 Original Android Development] RobbieL811:
So the Play Store in this Gapps should update but not have all apps compatible? Should I do a clean wipe? Or just delete my prebuilt gms core and google play service update apks?
[Nexus 5 Original Android Development] prbassplayer:
Should all be compatible mate.
[Nexus 5 Original Android Development] dankoman:
delete those apks in data/app if dirty. best bet is a clean wipe, yes.

play store in this gapps will NOT update.
[Nexus 5 Original Android Development] crford:
I'm not trying to be a prick, but I've been doing this a long time. Unless you're setting something somewhere else, or you're thinking of another ROM, you're mistaken. Straight from the repo, the Slim Makefile sets an alias for clobber to clean. They are one and the same.

cford@endor:~$ export USE_CCACHE=1
cford@endor:~$ export CCACHE_DIR=/media/cford/e7fc0fd1-024d-432f-9fcc-2b382864191c/ccache-slim/
cford@endor:~$ cd Slim
cford@endor:~/Slim$ set |grep CCACHE
CCACHE_DIR=/media/cford/e7fc0fd1-024d-432f-9fcc-2b382864191c/ccache-slim/
USE_CCACHE=1
cford@endor:~/Slim$ cd $CCACHE_DIR
cford@endor:/media/cford/e7fc0fd1-024d-432f-9fcc-2b382864191c/ccache-slim$ du -sh .
23G	.
cford@endor:/media/cford/e7fc0fd1-024d-432f-9fcc-2b382864191c/ccache-slim$ set -o
allexport	off
braceexpand	on
emacs	on
errexit	off
errtrace	off
functrace	off
hashall	on
histexpand	on
history	on
ignoreeof	off
interactive-comments	on
keyword	off
monitor	on
noclobber	off
noexec	off
noglob	off
nolog	off
notify	off
nounset	off
onecmd	off
physical	off
pipefail	off
posix	off
privileged	off
verbose	off
vi	off
xtrace	off
cford@endor:/media/cford/e7fc0fd1-024d-432f-9fcc-2b382864191c/ccache-slim$ cd ~/Slim
cford@endor:~/Slim$ make clobber
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
SLIM_VERSION=
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
TARGET_GCC_VERSION=4.7
TARGET_GCC_VERSION_EXP=
TARGET_USE_O3=
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.11.0-12-generic-x86_64-with-LinuxMint-16-petra
HOST_BUILD_TYPE=release
BUILD_ID=KVT49L
OUT_DIR=/media/cford/e7fc0fd1-024d-432f-9fcc-2b382864191c/android/Slim/out
============================================
Checking build tools versions...
Entire build directory removed.
cford@endor:~/Slim$ cd -
/media/cford/e7fc0fd1-024d-432f-9fcc-2b382864191c/ccache-slim
cford@endor:/media/cford/e7fc0fd1-024d-432f-9fcc-2b382864191c/ccache-slim$ du -sh .
23G	.
cford@endor:/media/cford/e7fc0fd1-024d-432f-9fcc-2b382864191c/ccache-slim$ cd -
/home/cford/Slim
cford@endor:~/Slim$ cat Makefile
### DO NOT EDIT THIS FILE ###
include build/core/main.mk
### DO NOT EDIT THIS FILE ###
cford@endor:~/Slim$ grep clobber build/core/main.mk
dont_bother_goals := clean clobber dataclean installclean \
.PHONY: clobber
clobber: clean
cford@endor:~/Slim$
[Nexus 5 Original Android Development] RobbieL811:
Anybody gotta mirror to the new Gapps? Slim site must be getting slammed.
[Nexus 5 Original Android Development] dankoman:
pm