yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Yank555:
On the WiFi not connecting front, I'm having this as well, have the WiFi with exclamation mark in notification shade.

When I go to the WiFi settings, I see the WiFi with an authentification error. I the just tap on it, tap 'connect'mand it connects just fine, no password prompt or thelike.

Strange, though, even if not a dealbreaker for me, and I can't remember having this or not on AOSP, switched to Slim too quickly ;)

This is here at work, but I have the same at home. I've noticed this lately, so might not really have any link to 0.7.

WiFi looks 'connected' in battery settings.

JP.
[Nexus 5 Original Android Development] peikojose:
If you install elemental X 2.04 using AromaInstaller over SlimLP 0.7 DT2W doesn't work. Don't know if it is ROM or kernel derp.
[Nexus 5 Original Android Development] danarama:
I don't use DT2W at all. But I have 2.04 plus SLimLP 0.7. I turned it on in ElementalX app and it worked. Obviously I don't use Aroma to turn this on since I don't use the function. So are you saying it isn't enabled by default if you select it in Aroma? And that it only works if you manually enable it in the app?
[Nexus 5 Original Android Development] csolanol:
Hi all, sharing this project from AnderWeb, the guy who created ADW Launcher. Maybe the SlimTeam is interested.

https://github.com/AnderWeb/discreteSeekBar
[Nexus 5 Original Android Development] VictorLapin:
After reading this line:

android.util.Log.wtf("WARNING!! HACKERY-DRAGONS!!");

I doubt that the team will be interested :)
[Nexus 5 Original Android Development] chykal:
Yes. I clean flashed it and have dirty flashed the latest slim gapps.
[Nexus 5 Original Android Development] peikojose:
Thanks form your answer. Yes, enabling it using aroma installer doesn't do anything. But using Kernel Tweaker to enable it works, problem is that I cannot control the timeout, haptic feedback and so on. Worked fine using 0.6 alpha. Tried clean flash.

BTW: what is the elemental x app?
[Nexus 5 Original Android Development] NovaSlim:
When in doubt, Google.

http://elementalx.org/elementalx-app/
[Nexus 5 Original Android Development] mendozaram:
Can't delete tones from /system/media/audio/... (0.7 - Supersu - Es File Explorer) anybody else with this?
[Nexus 5 Original Android Development] danarama:
ES file explorer doesnt work properly without PIE patch
[Nexus 5 Original Android Development] mendozaram:
Thanks, i try with Root Explorer and everything went fine :good:
[Nexus 5 Original Android Development] Chitown021:
Looks like my lag issues on my games were a dirty flash problem. I uninstalled and reinstalled the games and now they work much better.
[Nexus 5 Original Android Development] kufikugel:
For you :) https://gerrit.slimroms.net/19608

Backported to slimkat as well.

And no overlapping statusbaricons on center clock I fixed last night. The solutions which floated arounf in the past where just vague assumptions on the measurement. This is now pretty exact.

https://gerrit.slimroms.net/19580

Whatever just that you guys see it is still rolling and fixes for lp we backport to slim kat of course as well.

Lets see maybe I do today a new build :)

Again a ton off stuff new and fixed.
[Nexus 5 Original Android Development] danarama:
[MENTION=4790322]kufikugel[/MENTION], did you have any more thoughts about potentially enabling statusbar brightness on lockscreen?
[Nexus 5 Original Android Development] kufikugel:
[MENTION=2872010]rootSU[/MENTION] yeah noted it and will do during the week. Want to finalize headsup and navbar and always small things came in between lmao :D
[Nexus 5 Original Android Development] danarama:
Ah no problem. Just wasnt sure you saw it as it was in the same post as secure pull down, which was much more important :)
[Nexus 5 Original Android Development] :
I'm having the strangest issue right now and hope someone can help me out or tell me whats going on.

I updated TWRP from version 2.8.0.1 to 2.8.1.0 then 2.8.2.0. That's when everything went downhill. I was stuck in a bootloop, so I reflashed LP and got everything to boot up fine with the exception of my data being gone (except sd). I thought to myself, alright, ill downgrade to TWRP 2.8.1.0 to be safe and wipe everything. So, I tried starting fresh, with the latest alpha of LP, gapps and SU. Phone boots up, go through setup...no nav bar and bar at the top. I don't know what the heck I did wrong. I tried starting fresh twice. Same crap. No bar top or bottom.
[Nexus 5 Original Android Development] Yank555:
Wow, I feel honored, thanks a lot for all the work done, I couldn't enjoy LP if it wasn't for Slim-Team ! :D

Any idea on the WiFi thing ? If I can help in some way, provide more info, test out stuff, let me know !

JP.
[Nexus 5 Original Android Development] pulak861:
i am having the same issue... downloaded everything twice... sometimes it works(rarely).... sometimes it doesnt... flashed the phone 7 times.. worked for 2 times only... dont know what is happening . im pn twrp 2.8.1.0

and what is the actual step for clean flash???
[Nexus 5 Original Android Development] d88naimi:
Under settings my media control is turned on but doesn't skip songs via volume rocker is that feature not implemented yet? Thank you slim team for this absolutely amazing ROM.

Nexus 5 alpha 0.7 cleaned flashed
[Nexus 5 Original Android Development] danarama:
Read the description written underneath "media control" ;)
[Nexus 5 Original Android Development] :
I just flashed back to 4.4.4 without any issues. This was my last resort as I need a working phone, especially today lol. Would be nice to find out how to get back on lollipop.
[Nexus 5 Original Android Development] Moh Kohn:
Have you tried using the Google image using the fastboot method? If not I would give that a go including the userdata, then once you can boot into stock lollipop install recovery and flash away.
[Nexus 5 Original Android Development] d88naimi:
So in other words not implemented yet?
[Nexus 5 Original Android Development] danarama:
Not exactly. The setting you have set has been implemented but the setting you're talking about is not the setting you have set and has not been implemented

---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------

[MENTION=4790322]kufikugel[/MENTION] another one for ya should you choose to accept it :)

App picker (open with) - could you create the ability to just press the app once to open and act like the "just once action" instead of having to make 2 presses (select app and then either "just once" or "always") please :p

Edit well actually it works differently anyway. Just don't like the "just once" instead of pressing app name.

First screen shot, the alternative apps in the bottom pane are click app to open. The suggested app in top pane, you press "just once"

So I mean can we get rid of "just once" and press app instead in top pane?

Also if no suggested app, you have to select app (one press) then "just once". Again, is it possible to remove just once?

Inconsistencies driving me crazy haha
[Nexus 5 Original Android Development] d88naimi:
Thank you kind sir your a true gent and a scholar.
[Nexus 5 Original Android Development] Mikulec:
If you would remove the Always/Just once buttons, how would you then select the app that you want to always open the selected "link"?
[Nexus 5 Original Android Development] danarama:
I didn't say to remove "always". You'd need that to set apps as default. However, it would look better as a switch.
[Nexus 5 Original Android Development] DroidIt!:
A post for anybody having problems...well with anything :) When I initially went from kk to LP, ALL of my sensors quit working. Then when I went to update from slim .6 (5.0 base) to .7 (5.0.1 base) I couldn't get it to boot for anything. I let it sit on the boot screen for 20 minutes, redownloaded it about 3 different times and flashed probably about 7 times and no luck. I did quite a bit of research and in the official google issue reports there are pages of people having problems with the 5.0 update on not only the N5 but also the 2012 N7 and the N4. Seems those are the 3 big devices having problems. Everything from WiFi, to various google apps crashing, to sensors not working. Seems the most troublesome sensors are the proximity and light sensors. In some rare cases people have experienced what I have, no sensors at all working which just also happens to be worst case scenario. Some people in those cases have called google or an official LG repair and been told they need to have their mother boards replaced.

So if you're simply having WiFi problems or a sensor or two not working you'll probably be able to wait for another update from google and be fine. In my case I'm going to give updating to .7 one more try and if that doesn't work then I think I'll be phone hunting. I know I want to stay nexus, but if I could ask for some opinions, do you guys think I should get another N5 or should I go for the N6. Really kind of bummed about my N5 apparently taking a nose dive simply from a google update and I know kufi's on the N5, but if I can't get my N5 working what would you guys do?
[Nexus 5 Original Android Development] Mikulec:
[MENTION=5193466]DroidIt![/MENTION] - if you are comfortable with the size of Nexus6, go for it. For me the size is too much and I would probably stay with Nexus5.
[Nexus 5 Original Android Development] ANDROIDRAZRM:
I have a hard time believing that a software update can cause permanent hardware malfunctions. Have you tried a real factory flash using an md5 verified file? Have you updated your adb/fastboot tools to the lollipop versions?
[Nexus 5 Original Android Development] AndrasLOHF:
[MENTION=5193466]DroidIt![/MENTION] I'd probably flash the full 4.4.4 image and see if that helps to save some money first. Then try 5.x.x when it gets updated.
[Nexus 5 Original Android Development] DroidIt!:
Yeas and yes :) Multiple times actually with both 5.0 and 4.4.4. Funny thing is, when I went back to stock 4.4.4, sensor box said all my sensors were working, but they weren't actually doing anything. Then I went all official and from stock 4.4.4 I did like anybody would do and took the 5.0 upgrade from google right on my phone, so regular system upgrade. I went back into sensor box after that and it said all of my sensors are dead. I tried quite a few different tests to see if any of them would work and they'd definitely dead. So, like I said gonna try one more slim update and see if that works, but if not then a new phone it is. It'll hurt a bit needing to buy a new phone, but I HAVE to have something reliable for work. It is possible my N5 would keep working, but no sensors + no updates is too much for me.

So, think I might head to my local T-Mobile store, see how big shamu really is and make a decision.

But yep, I'm all out of ideas. I think she's dead Jim! :(
[Nexus 5 Original Android Development] roboots21:
[MENTION=4790322]kufikugel[/MENTION]

For self builders, I am having an issue with building. Something is messed up in my current build from this morning. The last build I did (and looking inside the latest alpha), the system folder is fully populated with the correct folders, and the upper level directory contains the following:

META-INF, system, boot.img, and file_contexts

Looking at the build I just did, the system folder only contains the bin directory, but the upper level directory contains the following:

META-INF, system, boot.img, file_contexts, system.new.dat, system.patch.dat, system.transfer.list

Something is messed up with the build process itself. I just did a build right before alpha 7 that I was running on my N5. I did a full clean build this last time so something is up with the build.
[Nexus 5 Original Android Development] DroidIt!:
Yeah I was thinking maybe I'll try the full 5.0.1 factory image whenever that comes in. Really only got a couple more things I can think to try. I did read a couple users reported letting their phone sit on the boot up screen for about an hour and that seemed to work for some. So I'm gonna try that too. Really love my N5, it's been my favorite phone yet, so I'm trying EVERYTHING I've learned over the last 4 or 5 years. I'll keep at it. Well, either way I'm still going to have a nexus, but if I can't get this one working again, torn about whether it'll be a N5 or N6 :)
[Nexus 5 Original Android Development] Silentbob999:
[MENTION=4790322]kufikugel[/MENTION] : LogCat

LogCat1 / Pastebin

LogCat2 / Pastebin

LogCat3 / Pastebin

basicly, me leaving home, getting in the subway (no service zone), try to read offline news = it doesnt work , turn off mobile data = it work
[Nexus 5 Original Android Development] leafs44:
i got the same thing as you, except i was building for shamu
[Nexus 5 Original Android Development] arifqur:
Feel sorry for you brother.

Hope it works out for you.
[Nexus 5 Original Android Development] ANDROIDRAZRM:
Yeah, this bug is killing my battery life on all the aosp/cm builds, so back to a modified factory image for me.
[Nexus 5 Original Android Development] AndrasLOHF:
Same here. I placed an order with T-Mobile last week when the order page went from saying Out of Stock to Buy Now on 64gb blue Nexus 6. I love my Nexus 5 but on every single build from the final dev preview onwards my battery life has been utter poo poo. Fortunately that Buy Now button was actually a backorder 6-8 weeks button so I canceled my order and am keeping the Nexus 5. I just have to keep a charger handy until a fix gets out lol.
[Nexus 5 Original Android Development] DroidIt!:
Yep. Like I said, it seems like most problems are fixable with an update. That's the impression I was getting from my readings. But by far the WiFi was the most prominent one. I have faith though, google really likes to update, so it should get fixed rather sooner than later I think :)
[Nexus 5 Original Android Development] Phazmos:
Could it just be a bad battery?

First few L previews were a tad worse on battery for me, but since about 210o it's been noticeably better than kk.

It was tough for me to hit 7hrs sot on kk, now it's more like 8 easy.

With my usage of course.
[Nexus 5 Original Android Development] Kurre:
Why you'd assume that it's messed up? [emoji6] yesterday I flashed similar build and these changes made install process very quick.

So we're talking about something like this in the updater script, I presume:

block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");

(I haven't done build after yesterday morning so I haven't tested latest changes..)

Afaik, this is something Google brought up with lollipop..and it's ought to be a good thing. Google probably will tell you more [emoji2]

Edit: ah, you already got some answers in another thread too.

Sent from my Nexus 4
[Nexus 5 Original Android Development] roboots21:
You're correct. Something is just up with my build and I don't know what.
[Nexus 5 Original Android Development] snwahs:
I have an odd issue with the 0.7 build related to read / write access when connecting my phone to my computer via USB. In 0.7 there are no folders shown. Checking with ES File Explorer and Root Explorer the same is true. When looking at the file explorer in TWRP I can see all of the files as well as folders. I can confirm that I do have MTP set and all the drivers installed. In addition when trying to copy files from my desktop I continously receive cannot copy file errors.

When reverting back to 4.4.4 8.18, this issue does not occur. I can see all files when connecting via USB. I can then transfer files from my desktop, etc.

I have done full system wipes in all cases (clean flashes) but still no joy on the 0.7 build. I went further and did a repair on the system from recovery as well. Anyone else experiencing this?
[Nexus 5 Original Android Development] :
This has been answered multiple times. Download terminal emulator from the play store.

Type in the following:

su

restorecon -FR /data/media/0
[Nexus 5 Original Android Development] snwahs:
What I get for not paying attention. Thanks and my apology...
[Nexus 5 Original Android Development] justmpm:
I remembered that there was a previous issue with the sensors and I found this guide: http://zidroid.com/how-to-fix-google-nexus-5-sensors-android-4-4-2-kitkat/

I am not sure if it will help but it is worth a go...
[Nexus 5 Original Android Development] DroidIt!:
:) Yep, tried that one too. Think I'm going to nand and then flash the .7 update and let it sit on the boot screen for about an hour and see if anything happens...maybe, if not, eh I'll probably get a new nexus tomorrow. Kind of leaning towards the 6 as long as it's not TOO huge. Well, here I go :fingers-crossed:
[Nexus 5 Original Android Development] randman2011:
My personal opinion, but while I was at a T Mobile store I figured I'd play with the N6. I asked a worker where it was because the only thing under the Nexus sign was a tablet. Turns out it was the N6. I just laughed and walked out. It dwarfed the G3 next to it, and I always considered that to be pushing it. If it were me, I'd definitely stick with the N5.
[Nexus 5 Original Android Development] theesotericone:
Did flashing an old KK nand do anything with the sensor issue? There's got a be a way to recover them. We talked about it upthread but the chances of them all failing at once is pretty low. Plus I'd hate to see you leave this tight knit group and head over to the 6 side. lol That might be jealousy talking though.:cool:
[Nexus 5 Original Android Development] DroidIt!:
Well, going the flashing the .7 and letting it sit route. So far it's been on the boot screen for about 15 minutes. I'm still hoping. :) I looked at my local T-Mobile web site and I could have an N6 in about 10 days. Plus they'd take an N5 for about $185 in trade. Even if this thing doesn't boot doesn't mean I'm going anywhere. I post occasionally useless posts in most threads, so don't worry. ?
[Nexus 5 Original Android Development] DrunkFuX666:
I think the main reason to upgrade to the N6 was the huge battery... But since all reviews thus far say it STILL has terrible battery, definitely not worth the upgrade to me... Will have to carry on with the N5 and the external battery packs...

Tho on a side note... Iv been looking but can't seem to find the option... Is it possible to display battery percentage WHILE charging?? It just shows the power bolt... And since I'm using knock display, it doesn't show me the charging % on lock screen. Suggestions?

Sent from my Nexus 5
[Nexus 5 Original Android Development] DroidIt!:
Well it's official. Can't get the sensors fixed and can't update to 5.0.1....soooo, decided to join Juba on the N6 scene. I'll still be in here, but didn't want to get the exact same phone again even though it IS a really good phone. Figure as long as I'm going to spend the money, might as well get google's newest. It shows up on the 15th. Not too bad considering some of the delays I've seen. I just must be lucky with my local T-Mobile :)
[Nexus 5 Original Android Development] efan3719:
don't be a stranger around here ;) still on the fence about getting a N6. be sure to give us your thoughts on the device when you get it. :good:
[Nexus 5 Original Android Development] DroidIt!:
Definitely, and nope won't be a stranger at all. I had been planning on keeping my N5 for quite a while longer, but such is life sometimes. I'll let ya definitely know how the new phone works out ?
[Nexus 5 Original Android Development] VictorLapin:
Guys, about that screen off animation. I have noticed that it is shown only with ambient display disabled. Maybe that's why some of you have it and some not.

Tapatalked from Slim Nexus 7
[Nexus 5 Original Android Development] kufikugel:
New build up guys,

Changes see gerrit please :)

Just woke up lol
[Nexus 5 Original Android Development] jtwlbz:
Kufi.. Quick pin unlock would be really useful feature for those of users using exchange emails.. Thanks
[Nexus 5 Original Android Development] Juzman:
New build flashed and working. :)
[Nexus 5 Original Android Development] yaatzek:
Thank you Santa :)
[Nexus 5 Original Android Development] :
Sorry to submit this again but I think it was overlooked. I've had this error since KitKat. With my carrier, whenever I miss a call I receive a text but it goes straight to my SIM. So now, every time I miss that call I get a "Sim card is full" message. My problem is deleting these messages. Every time I attempt to delete them I get a force close. I've tried deleting them in cm11 months back and had no issues but with slimkat or slimlp I get this error. Also using third party apps to delete them does not work.

I've never submitted a logcat before so hopefully I did it correctly. I replicated the issue three times which should appear in the log attached.

Thanks for the hard work so far guys!
[Nexus 5 Original Android Development] kufikugel:
Can you do a longer logcat? The short snippet does not show the crash.

Thanks :)
[Nexus 5 Original Android Development] :
Which app would you recommend? I used catlog, not sure if it's the standard app.
[Nexus 5 Original Android Development] oSandmaNo:
http://xdaforums.com/google-nexus-5/general/sensors-fix-nexus-5-t2704915

Might help you out. Same thing happened to me after flashing a sense port :p
[Nexus 5 Original Android Development] beaver2233:
if you mean the launcher, you need to change the dpi to stock, so, 480.
[Nexus 5 Original Android Development] SwayART:
Could you tell me how to do that? If you don't mind. ☺
[Nexus 5 Original Android Development] rpmfc36:
Download this app:

https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi

Change DPI to 480, reboot and you're good to go.
[Nexus 5 Original Android Development] TJKV:
[MENTION=4790322]kufikugel[/MENTION] [MENTION=3087740]Jubakuba[/MENTION]

Feature request:

In slimbean, long pressing the notifications button in the quicksettings drawer (top right icon) used to open quicksettings configuration page. It's not in slimkat yet but if/when it is added back, maybe long pressing that button when in the notification drawer could be made to open the notification station? Right now notification station can only be accessed by adding a shortcut to that activity somewhere (.Settings$NotificationStationActivity). I know it is probably a niche activity but some people might like it :)
[Nexus 5 Original Android Development] Jubakuba:
Bah! I never knew that existed, lol.

Personally...yeah, I'd say it's pretty niche.

BUT...what the heck else would you put there?!

So, yeah...makes sense to me when that comes around.
[Nexus 5 Original Android Development] TJKV:
Exactly my thoughts, so this could be the long press function at least till somone thinks of something better that could go there :P
[Nexus 5 Original Android Development] c@p:
Is the patch for battery light the same as CM has done?

Tapatalked by neXus 5
[Nexus 5 Original Android Development] LorD ClockaN:
Yes afaik

~~ Flowed from my Nexus 5 ~~
[Nexus 5 Original Android Development] c@p:
Seems so, new ElementalX Kernel is working perfect with the new charching light.

Thanks Slim team ?

Tapatalked by neXus 5
[Nexus 5 Original Android Development] mike2587:
Hey all, this weekly is awesome, I wanna ask if someone tried to enable s2s/s2w/dt2w?! I can't enable them with Trickster mod...Are these functions enabled in this weekly's kernel already?
[Nexus 5 Original Android Development] LorD ClockaN:
even if you manage to enable them with some other kernel, those functions are draining battery like mad..
[Nexus 5 Original Android Development] mike2587:
I tried 'em with bricked kernel and stock rom and yes, the battery draining is a problem, but I wanna try with this rom...So they have not been implemented in slimkat kernel yet? A friend of mine with last slimkat weekly on a mako device (nexus 4) has enabled s2s and dt2w easily...
[Nexus 5 Original Android Development] Craxx:
what about gesture unlock in lockscreen will this be included? :D

Best regards ;)

Craxx

Send from my Nexus 5 with Tapatalk
[Nexus 5 Original Android Development] LorD ClockaN:
don't know, I always use my own kernel, but what I do know is that unlock implementations are from showp so from bricked kernel and it acts the same as there