yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] HamsterHam:
There was a separate thread though. Maybe it got deleted. I can see why it is on the back burner with L coming up :)
[Nexus 5 Original Android Development] danarama:
Thread? No but:

There's a recent official statement from [MENTION=5047159]Tylog[/MENTION] on this subject.

http://xdaforums.com/showthread.php?p=53976107
[Nexus 5 Original Android Development] HamsterHam:
Must be losing my marbles! Cheers guys.
[Nexus 5 Original Android Development] Natakranta:
Thanks! You helped me find what was wrong and it was my understanding of app services. Apparently maps on it's own doesn't have a service running in background preventing Tasker from executing exit task.

But when I start navigation on maps, this is a service running even when I switch to other app. Tasker is seeing maps service and is not executing the exit task (GPS off). Perfect!

Your exit task seams to me an overkill. I have just GPS disable by Secure Settings and it's working fine going from GPS being on during maps and navigation to GPS off with location off. Location off is my initial default status.

I used to keep location on with WiFi only which is supposed to be the battery saver mode but I noticed Google Search/Now was abusing it causing plenty of short wake locks at the times I was totally not interested in it waking my device.

I read that using GPS only mode would help to keep Google Search/Now on short leash, but I'm mostly inside buildings where GPS can't fix position and drains battery pointlessly.

So I did what Google tries so hard to prevent me from doing. I switched location off. Indefinitely. And I enable GPS only for navigation when I actually need it.

This is just another example of how forcing people to do one thing usually causes the opposite ;)

I'm looking at you location prompt pop-up.
[Nexus 5 Original Android Development] JaylanPHNX:
With TRDS chrome, I think that's sort of a bug that it asks over and over at first. You can see some discussion of that in the official Gapps thread.
[Nexus 5 Original Android Development] danarama:
Can anyone please tell me where the code is for the double tap status bar to sleep?
[Nexus 5 Original Android Development] Andromendous:
Isnt there a on off switch for that? Or am i mistaken. Sometimes ill swipe the status bar down and the screen will turn off. Kinds annoying
[Nexus 5 Original Android Development] danarama:
No theres no switch. I will start compiling my own build if I can figure out what to remove. Its constantly turning my screen off when I swipe my notification area down. Its actually got to the point where I need to do something about it.
[Nexus 5 Original Android Development] chikimonke:
I don't think I've ever once accidently turned off the screen while swiping down the status bar. I have my status bar hidden in extended desktop mode though, so I wonder if that helps keep it from happening? Or maybe some of the digitizers are more sensitive on some phones than others? I'm honestly not sure why it's a feature (I mean, I know it's a feature because Slim team wants it) or at least one that's not able to be switched off in settings. I'm pretty sure the only time I've seen it mentioned, is when people are complaining about accidentally activating it, never a "does this ROM have this feature? it's a must for me" or "OMG this feature is great"

Again, I don't ever encounter the accidental activation, and honestly don't care one way or the other, but it's been brought up enough in here that I think it should at least be brought to the table to discuss. Informal poll incoming:

Didn't know this feature existed

Knew it existed, never used it, doesn't bother me.

Use it all the time, love it.

Is that why my screen turns off all the time !?!?!

I'm so frustrated with the feature that I will compile my own build to remove it.

I think that about covers it. And if the team ( [MENTION=5047159]Tylog[/MENTION], [MENTION=4790322]kufikugel[/MENTION], [MENTION=3087740]Jubakuba[/MENTION], [MENTION=1277872]dankoman[/MENTION], [MENTION=3877985]prbassplayer[/MENTION] et al) don't want this poll/discussion, just say so and I'll edit my post, but I do think it's worth talking about.
[Nexus 5 Original Android Development] ralpheboyo:
Well count me in for option 2.... Never used it.. Never will... Got nova and slim actions for that nonsense.....
[Nexus 5 Original Android Development] CaspaTheGhost:
I'm sure I noticed an open commit allowing it to be toggled with CoS, can't remember when though!

Sent from my Slim N5
[Nexus 5 Original Android Development] danarama:
It happens to me a lot. Even when I know I'm being careful not to double tap it. But its worse for me. I live in the Yorkshire countryside and get a bus to work and back. I spend 2.5 hours a day on a really bumpy bus with nothing but my phone so in these cases, actual double taps are inevitable.
[Nexus 5 Original Android Development] tcowl:
I would love to just be able to disable this feature. I tend to accidentaly turn off my screen when just pulling down the notification drawer. It's not enough to make me build my own build lol but damn i'd flash a tweaked build to get rid of it.
[Nexus 5 Original Android Development] danarama:
Depends on the code and where it is. Maybe I could just build systemui or even just flash an updated xml file.

A switch in display would be preferable though
[Nexus 5 Original Android Development] Jubakuba:
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBarView.java

Remove lines 69-81.
[Nexus 5 Original Android Development] danarama:
Nice one. Thanks for that.
[Nexus 5 Original Android Development] Andromendous:
Well it happens alot, not too much on my n5 but all the time on my n72013, witch is amazing cus my n5's screen is so sensitive i can just hover my finger over a button to press it. But ya, i think its a good feature, would just be nice to be able to switch it off

---------- Post added at 12:20 PM ---------- Previous post was at 12:18 PM ----------

Not trying to ask too much, but would you happen to know how to make a build with sabormod 4.10 toolchain?
[Nexus 5 Original Android Development] danarama:
No. I haven't compiled a ROM for a while. I last compiled slimbean on my s3 last year and that was the first time I compiled since gingerbread. Only really compile reecovery.
[Nexus 5 Original Android Development] DroidIt!:
Same here (for the N7). It's usually only in landscape mode for me though. Seems like if you touch the status bar outside of the notif panel it triggers it without the double tap. I just move my finger a little further into the screen in landscape to pull down the notif bar and it doesn't happen then. ;)

from my N5
[Nexus 5 Original Android Development] Andromendous:
I think, the touch screen on that tab has issues, i think it registers your touch, then loses it, then registers it again. Thinking you double tapped
[Nexus 5 Original Android Development] reinert012:
me too!!
[Nexus 5 Original Android Development] Joshmccullough:
Is that a 'Car Stereo One' reference from the Toledo, OH, area???? If so: it's a small world indeed.
[Nexus 5 Original Android Development] chikimonke:
Not sure if it is or not, but [MENTION=5047159]Tylog[/MENTION] is from/in Germany. :)
[Nexus 5 Original Android Development] Grondinm:
so back from my little "vacation" had lots of fun now time to get back to android. For those of us like me that enjoy LSN I have finally figured out how to fix LSN pocket detection. thanx to [MENTION=3087740]Jubakuba[/MENTION] for the point at where i needed to look. Now i'm having trouble submiting this change to the original change in gerrit. I had no problems pushing the changes required for the second part of LSN but the framework part just won't go i get this error:

To ssh://grondinm@gerrit.slimroms.net:29418/SlimRoms/frameworks_base
! [remote rejected] HEAD -> refs/for/kk4.4-caf (duplicate request)
error: failed to push some refs to 'ssh://grondinm@gerrit.slimroms.net:29418/SlimRoms/frameworks_base'

it's almost like git/repo do not realize that this should be part of the original change...not sure where to go from here. Either way build for hammerhead is uploading as i type this and flo and mako builds will be up after work. Enjoy :o

Edit:

This is the script i use to submit things to gerrit:

#!/bin/bash
EXPECTED_ARGS=1
E_BADARGS=42

if [ $# -ne $EXPECTED_ARGS ]
then
echo "Usage `basename $0` project_name"
exit $E_BADARGS
fi

PROJECT=$1
BRANCH=kk4.4-caf
git push ssh://grondinm@gerrit.slimroms.net:29418/SlimRoms/$PROJECT HEAD:refs/for/$BRANCH

i changed the branch to kk4.4-caf since this is where the original change is submitted to
[Nexus 5 Original Android Development] JaylanPHNX:
I'm casting my ballot for #3. Love it. My N5 must have a crappier touch sensor than everyone else's, though, cause I find myself sometimes jabbing away at the status bar yelling, "Sleep, damn you!"

From my Tab Pro 8.4
[Nexus 5 Original Android Development] Tylog:
Hm? I don't understand what you mean

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Grondinm:
Regarding the double tap notification bar to sleep my vote goes to Number 2. Mind you my status bar is always hidden(expanded desktop) and i use slimpie to bring down notifications when i need them but still knew about it and never caused problems even before i started running in expanded 100%
[Nexus 5 Original Android Development] DroidIt!:
Personally, I honestly never use it, just always use the power button myself or let the screen time out. Besides if I started yelling at my phone, I might get the wife ban hammer :)

from my N5
[Nexus 5 Original Android Development] chikimonke:
So it seems it's a very mixed lot on liking, not liking, not caring. It seems to me, that if possible, a toggle switch should be added into display or statusbar settings and then everyone SHOULD be happy (though we know there's always one...)
[Nexus 5 Original Android Development] graffix31:
im between 2 and 3. for the longest time it was the only way i shut my screen off. i have a nav ring setting for it now but i like it as a feature. im ok with a toggle to turn it off but i dont want to see it go away though.
[Nexus 5 Original Android Development] JaylanPHNX:
I only yell at my phone when I'm alone in my car, like all the other perfectly sane people. [emoji12]

From my Tab Pro 8.4
[Nexus 5 Original Android Development] Andromendous:
I have another bug to report, for some reason, i cant seem to get my battery to die. Im approaching 15hrs and im at 87%. Its like the phone just cant die. I dunno if this is a feature, or maybe a bug. BUT IT JUST WONT DIE!!.

Ill post bettery results at the end of the day :)
[Nexus 5 Original Android Development] Tylog:
We will fix it in the next five years, so long you must life with it xD

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Andromendous:
Noooooo!....... I mean....

Yeeeeesssssss!!!!!!!
[Nexus 5 Original Android Development] Jax Teller:
My vote is on #3. I use it all the time and I love the double tap to sleep on status bar.

Also I have never activated it by accident.
[Nexus 5 Original Android Development] Aerowinder:
I personally find the feature to be pointless. I've never hit it on purpose, only on accident. It doesn't bother me enough to compile my own version.
[Nexus 5 Original Android Development] ryukiri:
My vote is on 3. I use it all the time and I usually don't last long on a rom without it.
[Nexus 5 Original Android Development] danarama:
I don't see why we're voting. It isnt going to change.
[Nexus 5 Original Android Development] chikimonke:
There hasn't been much to discuss that is on topic lately (damn you you stable ROM) so I figured now was as good a time as any to discuss it. As I've said before, I don't use it, nor have problems with it, but it seems there's enough people on both sides that it would make sense and please the whole user base, if a switch was implemented. Use it and love it, great, nothing changes. Find it a nuisance or don't use it, great, you can disable it. Not talking removal, just allow the user to turn it off if they want. Aside from [MENTION=3087740]Jubakuba[/MENTION] showing you where the code is, none of the Team members have commented though. [MENTION=5047159]Tylog[/MENTION], [MENTION=4790322]kufikugel[/MENTION], [MENTION=3877985]prbassplayer[/MENTION], any thoughts/comments?
[Nexus 5 Original Android Development] danarama:
Ok fair enough. A switch would be lovely but it has been requested before. I understand not allowing things like recents to be changed. Its a great feature , better than the default and its in line with the teams vision of their ROM. Unfortunately though, this other feature can cause real usability issues. Unlike recents, its just not suitable for everyone. Like my bouncy bus ride or the fact that it regularly seems to false positive double taps.
[Nexus 5 Original Android Development] mendozaram:
Im using the latest beta gapps .155 and there is no trds gmail... Or its just me?
[Nexus 5 Original Android Development] kufikugel:
Sorry a bit busy to bring up 1+1 on a non cm base lol. Good thing it is running...most things figured out just bt and camera is broken....second is easy...for bt I need to bring up a slim config. Our and cms bt has nothing in common lol.

Whatever about the double tap to sleep....I will make another suggestion

What about to reduce the activation area....let's say like quick pulldown for qs it is activated by default on the left side....with a width of 25% of the statusbar....so left corner you can use it....of course if the user setuped qs quick pulldown on the left it automatically switches to the right corner.

This way you still have 25% of the statusbar where you can activate it....it does not disturb normal pulldown which is mostly done on the middle of the statusbar neither does it conflict with qs quick pulldown due of the automatic switch
[Nexus 5 Original Android Development] NovaSlim:
Dankoman never said there is a TRDS gmail in 155, it is just a Gmail version update because Google pushed one out today. Gmail is one of the harder apps to TRDS and Dankoman is still working on it.
[Nexus 5 Original Android Development] chikimonke:
Current versions of gmail and G+ don't play nice with the TRDS process. [MENTION=1277872]dankoman[/MENTION] has been working on it.
[Nexus 5 Original Android Development] JaylanPHNX:
That's music to my ears, because the unofficial SlimKat for the Galaxy Tab Pro 8.4 doesn't have working Bluetooth and the guy making it cited this BT difference as why.

From my Tab Pro 8.4
[Nexus 5 Original Android Development] Natakranta:
[MENTION=4790322]kufikugel[/MENTION], what are the times for TRDS switching on and off with on day time mode?

It would be cool if user could set on and off time :)
[Nexus 5 Original Android Development] efan3719:
This may be totally wrong as the cause but I think its so hot here that my phone rebooted while using GPS in my car on my magnetic dock. Black phone and a metal thingy to help it stick to the dock. Almost too hot to touch. It's about 105 here. Record breaking temp. :(
[Nexus 5 Original Android Development] damngood98:
Personally the only time I use it is by accident. I would think if you were going to make a change and play with the coding it, an on/off switch would sufficient. I don't think I've seen a single comment asking for reduction......just my humble opinion :o
[Nexus 5 Original Android Development] NovaSlim:
Try to use a lower brightness setting? I found that reduced my in car on GPS temp a lot.
[Nexus 5 Original Android Development] chikimonke:
I know you like a challenge and all Kufi, but wouldn't it be easier to just make a switch? I think it would be easier for the user too. Don't have to worry about where the sweet spot is or anything. Could also make it so the first time it is activated, it doesn't actually turn the screen off, but rather, pops up a window telling the user that the double tap they just performed will turn the screen off next time. And then letting them choose to keep that enabled, or disable it. Then still have a switch elsewhere if the user ever changes their mind. The pop-up is by no means necessary, but it seemed like you wanted something a little more challenging than just a switch :D
[Nexus 5 Original Android Development] plaseo:
I have been lurking here for a couple months now after my s2 shattered and I picked up a n5 and promptly flashed slim. I gotta say this is by far the best thread on xda and most likely the best ROM as well. I have been trying to build slim on my desktop and since this is such a helpful great thread was wondering if someone could give a little advice. I can't get past repo sync. (I may be a noob :)) It starts and runs fine for a while but always fails when trying to download something from android.googlesource.com. Either I get unable to access or could not resolve host. I have been banging my head against the wall for 2 days trying to get this to work. I'm not sure if it is my network or something else. I have tried all sorts of network troubleshooting,wired,wireless. My internet is usually rock solid so I'm leaning towards something else. Any ideas?

:P
[Nexus 5 Original Android Development] Joshmccullough:
There's a chain of car stereo sellers in the Toledo, Ohio, area and at the end of every radio/TV commercial their owner says "Car Stereo One....Turtle!" I have no idea where that comes from, but I thought maybe you were referencing that until this post and the other fellow saying that you're from Germany, so not likely :)
[Nexus 5 Original Android Development] RobbieL811:
If you are using Ubuntu, follow

THIS GUIDE

step by step.
[Nexus 5 Original Android Development] plaseo:
This looks nearly identical to what I'm following. Yours is a bit more helpful though thanks!
[Nexus 5 Original Android Development] RobbieL811:
It's probably the same one that was on XDA. A few things were changed to make it specific to Slim.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Andromendous:
Will your guide be the same for xubuntu 14?
[Nexus 5 Original Android Development] plaseo:
AFAIK yes. I'm using Lubuntu 14. The Ubuntu flavors use the same base its just different desktop environments and programs.
[Nexus 5 Original Android Development] RobbieL811:
I'm not sure. I think so though. I've never used Xubuntu. Isn't it based on Ubuntu though? If so, I would think it would be very similar if not exactly the same.
[Nexus 5 Original Android Development] efan3719:
Yeah just about any that are based on Ubuntu will work with that guide. Maybe some very minor differences. I used that guide with Mint and it worked out fine.
[Nexus 5 Original Android Development] Andromendous:
Cool, I ask just because I remember there were some differences between ubuntu 12 and ubuntu 13. And Im pretty sure xubuntu is just a stripped down version of ubuntu with a xfc desktop instead of unity. I think the only problem i might run into is lacking some packages that ubuntu would already have. Gonna try a build this weekend. Im gonna wipe my laptop and start over, Id really like to make a build with sabermod 4.10, toolchain, but i dont know how to, would anyone with that kinda knowledge care to help a feller learn something?
[Nexus 5 Original Android Development] aow1980:
I've been trying to find out how for awhile and no progress so far. I think [MENTION=4911350]RobbieL811[/MENTION] is working on it too.
[Nexus 5 Original Android Development] Andromendous:
Ok, Ive looked for guides on google and youtube but ive found nothing. I pmed a dev, hope to hear from him soon.
[Nexus 5 Original Android Development] RobbieL811:
Lol. Damn that's weird! I'm building right now with it. First time in a month or so.

Sent from my Nexus 5
[Nexus 5 Original Android Development] aow1980:
Can you link the build when done? Wife is already in bed so no more computer for me tonight. Lol
[Nexus 5 Original Android Development] bikeryder007:
Good. Minux's 4.10 sabermod slim builds are the greatest things since boobs. Same great slim, just perkier.
[Nexus 5 Original Android Development] Garrykd:
Responding from the wilds of northern Ontario, standing on a hill to get reception..... what version of java do you have? If it's openJDK you will get that error with chromium. Change to the oracle version of JDK

You are missing proprietary binaries, send me a pm and I'll get back to you tomorrow.

Sent from my office:
[Nexus 5 Original Android Development] RobbieL811:
Yeah. I'll upload it for you. Give me a little bit for the build to finish. I can't remember exactly what I did in the past to build Slim with SM. I think I just edited .envsetup.sh and let it build. Somebody that knows a little more than me correct me if I am doing it incorrectly. Target GCC Version at the beginning of the build still says 4.7?

Sent from my Nexus 5
[Nexus 5 Original Android Development] aow1980:
That is what I was doing but I removed the other toolchain from the folder and it failed. It was trying to use the 4.7. [MENTION=5161352]JustArchi[/MENTION] had a post in the linaro compiler thread about the correct way to do it. Tried that and it still failed. After more research it looks like some things need changed to allow for it built with 4.8 and above.
[Nexus 5 Original Android Development] RobbieL811:
Well, we're about to find out! My build is almost done.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Riddlah:
I have read conflicting reports about using the envsetup not being the correct way to build with 4.8 or newer. I've tried going through and grabbing the strict aliasing fixes along with changing to 4.8 but can't get it to build. Actually in the process of redoing my sync folder to try again.
[Nexus 5 Original Android Development] RobbieL811:
Well, definitely let me know if you figure it out the proper way.
[Nexus 5 Original Android Development] Riddlah:
will do. one thing I did notice was changing from 4.8 to 4.9 or 4.10 seem to produce different error messages for me. For now I'm trying with 4.8. If that works I'll try for the other two.
[Nexus 5 Original Android Development] RobbieL811:
OK. My build compiled w/ the envsetup changes but it looks like it was still compiled with Linaro by looking at the kernel name in Kcontrol. I wonder if I need to change boardconfig too?

Sent from my Nexus 5
[Nexus 5 Original Android Development] Riddlah:
I have seen some use the boardconfig and some use the Target_ARM. I thought kernel apps only showed the toolchain used by the kernel?
[Nexus 5 Original Android Development] RobbieL811:
I will PM you. Don't wanna be cluttering up the thread with stuff people don't feel like reading.
[Nexus 5 Original Android Development] CaspaTheGhost:
Unofficial build posted a few pages back.

Not all the TRDS commits have been merged so its still a WIP.

Sent from my Slim N5
[Nexus 5 Original Android Development] aashgaur:
hey .. if someone is using that unofficial build.. and i think everyone is :P

are you guys having that when someone calls.. you see behind that the image when you answer the call !! i think its a gapps issue because i am using p.a gapps but can someone +1 that ? thanks.
[Nexus 5 Original Android Development] coolek33:
Keep using those gapps and don't post any issues. Use only official builds and gapps if U want to post bugs in this thread. Keep it clean ;)
[Nexus 5 Original Android Development] AndrasLOHF:
You'd have to do everything manually but from this site you can blackout to your hearts content. ;)

http://www.designrifts.com/teamblackedoutapp/category/blacked-out-apps/google-apps-black/
[Nexus 5 Original Android Development] dankoman:
delete
[Nexus 5 Original Android Development] rxmxsh:
What is TDRS?