yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] pkelly517:
Okay, last time I'll ask. I promise.

In between family/daughter time over the weekend, I tried everything I could to figure this out.

When I tap on a number in the call log that's NOT part of my Contacts (just a number), I get this screen.

Then I hit Add to Contacts, and I get this

I don't want to Copy to My Contacts. I want to have Contacts come up, and I choose which Contact needs the number.

Here's the logcat (XDA Upload handling it). The Dialer/Contact stuff is right about in the middle.

Clean flash? yes. no. Doesn't really matter.

Slim AIO Gapps? You bet.

Slim Minimal Gapps? A few times.

Built from scratch at home? sometimes

Downloaded both beta 2.1 and 2.3 to make sure nothing wrong in my build? Uh huh.

Contacts are only synced on one of three Google accounts on phone.

Everything works as hoped on another ROM (AOKP)? Surprisingly, yes. First time, every time.

I'd hate to move on to another ROM over this smallish issue, but it's driving me nuts. And it shouldn't be that hard to find the problem. But I can't find it. And I need help.

Thanks
[Nexus 5 Original Android Development] Jubakuba:
Idk man, sorry.

I click a call from call log.

Click blank photo of popup...

And get a contact list.
[Nexus 5 Original Android Development] pkelly517:
The comments in Contacts/res/values (from memory) points to my phone thinking I'm adding a number to a corporate account. Maybe T-Mobile prepaid has it confused?

I'll grab a logcat from another ROM later this week, just to compare the two.
[Nexus 5 Original Android Development] kufikugel:
well I can reproduce it. Although I wonder why this should work on other roms. This is normal AOSP behaviour I think at least we did not change anything ther. But I agree a bit dumb

whatever to workaround this for you press on the unknown contact image in the history log on the left...this opens a popup with an icon on the right to add the contact....this is doing what you want

In the meantime I will add the same shortcut to the screenshot you posted.
[Nexus 5 Original Android Development] pkelly517:
Yay!

Workaround works. I wonder why you are the only one who has been able to reproduce it?
[Nexus 5 Original Android Development] kufikugel:
no idea lol.....I will start to figure out now why :D
[Nexus 5 Original Android Development] pkelly517:
Thanks.

I guess the next best thing to fixing a bug is pointing out a reproducible bug. Even if Jubakuba can't make it happen :p
[Nexus 5 Original Android Development] TJKV:
Okay I've added two videos in my post above.

Yeah...I hope it's possible to maybe straight-in replace the relevant bits of code from the older implementation :p
[Nexus 5 Original Android Development] Yank555:
Maybe because that code was still stock ? :D

I'll have a look, but atm fighting another battle, against those crappy lags we're getting after longer uptimes...

JP.
[Nexus 5 Original Android Development] TJKV:
No hurry, although let me know when you've seen those videos, I'd want to remove the links after you are done watching them :p
[Nexus 5 Original Android Development] Mikulec:
Maybe. lol :laugh:
[Nexus 5 Original Android Development] Yank555:
Done ;)

And confirm, that's what I managed to reproduce.

If you don't see me move on that topic by a week's time or so, please do remind me to have a look, I'm getting forgetful at my age, and threads just move so fast :D

JP.
[Nexus 5 Original Android Development] TJKV:
Alright, will do :good:

*Goes to set a reminder for this in Google now*

"Argh, damn thing won't launch!"

:D
[Nexus 5 Original Android Development] luisangel89:
Thank you! Sorry for the late reply. I'm in an area with really bad signal. Sacramento. T mobile has really bad reception here.
[Nexus 5 Original Android Development] Yank555:
Haven't tested yet (need to recompile, it's complicated on my buildbox atm :silly:), but the newest patchset (PS9) should bring assist back :

https://review.slimroms.eu/#/c/6555/9

No change in fwb should be needed.

JP.

---------- Post added at 09:52 PM ---------- Previous post was at 09:48 PM ----------

Wanna laugh :(

I can't reproduce it AT ALL on shamu ?! That's bad :rolleyes:

JP.
[Nexus 5 Original Android Development] JayDream:
The incoming call volume isn't working for me. Rocking the latest build 7/21
[Nexus 5 Original Android Development] kagwind:
Didn't think you removed assist from the list. :silly:
[Nexus 5 Original Android Development] perrocaliente:
Regarding the navring swipe issue that was just discussed I have noticed this as well and you're only gonna notice it if you use your phone quickly like I do. On kitkat you could just swipe it as fast as you wanted and it would activate. On here you have to hold for a second and swipe and make sure you get it perfect. If you swipe too fast it fails and if you don't hold for a second it fails. Anybody who's used slimkat navring shortcuts should understand. Slimkat's navring was lightning quick and worked every time. Lollipop's navring sucks in that regard.
[Nexus 5 Original Android Development] RobbieL811:
You are definitely right about the nav ring. There is a difference. But, I think that there is a reason that it is much slower in lollipop. Idk what that reason is though lol. Personally, I could deal with the slower response. I just want my five targets back instead of 3 lol.
[Nexus 5 Original Android Development] pseudoheld:
I have a different lollipop room on my second multirom system (cataclysm) and it doesn't have the aforementioned delay when swiping up. (just FYI)
[Nexus 5 Original Android Development] Mikulec:
Funny thing is that I can reproduce the navbar swipe just like on a stock rom, but the swipe needs to be more precise upward motion.
[Nexus 5 Original Android Development] Yank555:
The funny thing, no matter how fast I try, on shamu it works fine !? That's seriously a bloody issue :(

[MENTION=4911350]RobbieL811[/MENTION] : 5 ? Ain't that crowded ?? ;)

OK, I'll have a look what I can do about that...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
[Nexus 5 Original Android Development] pseudoheld:
[MENTION=2033478]Yank555[/MENTION] [MENTION=4911350]RobbieL811[/MENTION] here is another log of my system going nuts.

Phone becomes unresponsive, screen just turns of, can't be turned on, flashes on and off, system UI seems to crash.

https://www.dropbox.com/s/pe6n9erxg69l3vf/2015-07-22-09-21-51.txt?dl=0

should I continue to post these logs ?
[Nexus 5 Original Android Development] Yank555:
Yep, more logs is always better than less ;)

JP.

EDIT :

This explains screen on delays :

07-22 08:13:34.894 I/DisplayPowerController(735): Blocking screen on until initial contents have been drawn.
07-22 08:13:35.028 I/DisplayPowerController(735): Unblocked screen on after 135 ms

And obviously it's the drawing that takes a hit, as if GPU wasn't working fast enough, but GPU raw speed is handled by the kernel, and there's been no change on that end, so it has to be somewhere higher in the chain. Or it's totally unrelated and drawing just doesn't get a chance to do it work because of sth else.

But it's hard to conclude anything, this log seems to be the end of the battle, I don't see what could have triggered the kill-storm.

On the other hand, when is ground 0 happening, right before the kill-storm, or a lot earlier and it builds up. Hard to catch on a log except if the log runs from system start.

JP.

EDIT 2:

What gapps are you running (exact name of the zip you flash) ?
[Nexus 5 Original Android Development] Mikulec:
Could you launch it also by slightly diagonal swipe?
[Nexus 5 Original Android Development] Yank555:
Yep, but then it launches the right action (in my test). And I did it like really fast, starting off of the touch area and I lifted the finger on 1/3, half and 2/3 of the screen hight and even just went further and out of the touch area on top.

JP.
[Nexus 5 Original Android Development] Mikulec:
[MENTION=5605731]perrocaliente[/MENTION] [MENTION=4911350]RobbieL811[/MENTION] [MENTION=1757430]pseudoheld[/MENTION] [MENTION=2033478]Yank555[/MENTION] How many navbar buttons do you all have on screen? Could it be connected with the number of buttons you have?
[Nexus 5 Original Android Development] pseudoheld:
Slim_mini_gapps.BETA.5.1.build.0.x-20150717.zip

i have stock navbar buttons and just the one (stock) navbar swipe button
[Nexus 5 Original Android Development] Yank555:
I have 5, always have had. And 3 ring targets.

JP.
[Nexus 5 Original Android Development] Mikulec:
So its not dependant on number of buttons and neither on navbar height (I just tested it with different heights).

But I have learned how to swipe it quickly and launch the ring target. I can successfully launch it in 7 out of 10 tries. :D

BTW any new build coming in near future?
[Nexus 5 Original Android Development] perrocaliente:
I have 3 total. But it doesn't seem to be connected to that. Like robbie said lollipops navring is just different from kitkat. The animation design and speed are all different.
[Nexus 5 Original Android Development] Mikulec:
Yes, as I said in previous post. But its not about kitkat vs lollipop, more like SlimLP with navbar rings vs SlimLP w/o navbar rings.
[Nexus 5 Original Android Development] Phazmos:
Navring - stock lp is just fine, well, a smidge slow than kk, maybe. But I just run a finger up from nav bar as fast as I can and search comes right up.

Anything with nav ring customizations exhibit the odd behavior.

Reasons for that I'd have to leave for the coders out there, which I am not.
[Nexus 5 Original Android Development] RobbieL811:
Lol. Idk if I would call it an issue...It's just how we had the nav ring in Kitkat and I loved it. It didn't seem too crowded then, but then again, the targets seem to be a little bigger in Lollipop.
[Nexus 5 Original Android Development] effraie:
I also can't make a quick swipe from the home button to trigger search. But, as far as I remember, I had the same behaviour in slimkat... Small pause on home button for the ring to show, and then swipe to the target.

IMHO, that's a good behaviour : it allow me to use target for search and quick swipe (via launcher) to trigger an other action
[Nexus 5 Original Android Development] Yank555:
To get that on shamu, I have to be insanely quick, and only possible with two hands, not because of device size, but my thumb just isn't fast enough :silly:

I think the problem is the animation is more complex as in KK (can't remember to be honest), and the listener only starts listening after the animation is done, or mostly done.

JP.

---------- Post added at 03:46 PM ---------- Previous post was at 03:43 PM ----------

Indeed, sth that works isn't really an issue :) But when the same code works on one and not on another device, it's not helping either :p

I think indeed they are bigger than they were in KK, but again, I just can't remember KK anymore...

JP.
[Nexus 5 Original Android Development] TJKV:
If that is the issue, where animation hasn't completed before we have swiped and let go of the screen, then I just remembered something:

Back when SlimRecents first came out for SlimKat, there was a similar issue to do with animation. I noticed that if we tap recents button and very quickly tap on an app on the recents drawer, the app we tap on will come up but the recents drawer won't close. Apparently the opening animation wasn't done when tapped on quickly, so the closing of the drawer and the associated animation is never triggered. I told kufi about it and he just made a small fix for it. Basically he made sure that the closing of the app drawer didn't depend on whether the opening animation was done or not. That helped speed up the process of switching apps using slimrecents just a little bit, at least for those of us with lightning fast fingers :p

So in a similar concept, is it not possible to enable the actuation trigger(s) on the navring before animation is started/completed? Assuming that is the problem, that is :p
[Nexus 5 Original Android Development] Yank555:
To reply as an IT consultant would :

Everything is possible, it all depends on the time it takes, thus the price you're willing to pay for it :D

On a serious note, of course a lot is possible, I need to see what can be done and what can't, but won't get to it before the WE unfortunately, I'm taken the 3 evenings the week has left :cowboy:

But there is a big difference between SlimRecents and the NavRing stuff...

The apps are already spawned and visible while the drawer is sliding out, thus they exist and are touchable.

In this case I believe the targets only get spawned after the animation is done, thus likely don't exist yet and can't be touchable.

But only the code will tell ;)

JP.
[Nexus 5 Original Android Development] TJKV:
Good, cheap, fast. Choose any two :D

Of course, I just remembered that slimrecents thing when you mentioned animation, is all [emoji14]
[Nexus 5 Original Android Development] Phazmos:
That size was the only thing holding me back from the 6, but price is coming down. Getting more and more tempting.
[Nexus 5 Original Android Development] pseudoheld:
Here is a logcat with more errors than you can shake a stick at:

https://www.dropbox.com/s/nhul6lp16k30uyh/2015-07-23-00-01-33.txt?dl=0

Phone generally unresponsive and locking up every now and again :(
[Nexus 5 Original Android Development] effraie:
Small bug, only cosmetically annoying : on lockscreen, there is "aucun service" (french for "no service" instead of provider name, even if I'm correctly connected
[Nexus 5 Original Android Development] RobbieL811:
It's an issue across all ROMs right now.
[Nexus 5 Original Android Development] effraie:
So I guess I'm too much loyal to slim to know that!
[Nexus 5 Original Android Development] puldag:
Also got the unresponsive lock screen. Last build (21.7.), clean flash (data, system, cache).

Edit: testing with elementalX kernel, so far so good (for couple of hours).

Edit2: unresponsiveness still appears, so not kernel related. Maybe stock kernel? :)
[Nexus 5 Original Android Development] pseudoheld:
I also did a completely clean reflash just to be able to exclude all other possibilities and my issues still persist. :(

Unresponsive, ui crashes, etc

Here's once again a log :

https://www.dropbox.com/s/5md3c0anw3c5c1m/2015-07-23-23-52-03.txt?dl=0
[Nexus 5 Original Android Development] prbassplayer:
I'm no where near a pc right now but this clean means your not restoring apps right?

Edit: What [MENTION=2033478]Yank555[/MENTION] said might be a good idea
[Nexus 5 Original Android Development] Yank555:
Did you consider a complete wipe (including internal memory = you will lose EVERYTHING, so backup to external USB-OTG memory !) ? Looks like you're having tons of IO issues...

JP.
[Nexus 5 Original Android Development] kirmr:
Just one question, are you planning to add in the future the Shake Listener? Really liked that feature back in the SlimKat days:)
[Nexus 5 Original Android Development] pseudoheld:
I did a factory reset. Didn't do a complete wipe and to be honest I would like to avoid it aswell.

I might just switch roms again and see if it all goes away...

What are IO issues?

I didn't restore any apps via tibu. (tô exclude that as an error source)

Fun new problem: the lag is now so bad, that when rotating from portrait to landscape it literally takes a few seconds for the image to adjust meaning at first the portrait image is shown rotated on the half of the landscape...
[Nexus 5 Original Android Development] Yank555:
IO issues are issue reading / writing to the filesystems. If you have a corrupted filesystem, there is NO way around a complete wipe, the data partition is on the internal 'sdcard' (it's a bit more complicated than that), but if that filesystem is wonky, you'll never get out of this.

Easiest way would be fastboot factory flash stock images, that will wipe EVERYTHING and put your device in a real factory state.

After that, I'd suggest you run stock for a few days (you can root it), to validate you don't have a hardware issue.

After that, if all is fine, try flashing a custom ROM again (Slim or whatever you want to look into).

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1a kernel.
[Nexus 5 Original Android Development] pseudoheld:
thanks for clearing that up.

I do have multirom installed. maybe thats a culprit? but slim is running on the main system so I don't think its the cause.

Before going down the extreme route and wiping the phone completely i guess i will switch to a different custom rom for a day or two just to see if the issues persist (will report back here) if thats the case i guess i will have to go with the wipe.

are there any tests i can run (maybe some smart terminal code) to check the filesystem for errors/problems?
[Nexus 5 Original Android Development] Yank555:
Well if you use multi-rom, a lot can be the issue, that makes the situation rather more than less complex. I've never used multi-rom, I have no need for it.

In all cases, if a ROM misbehaves with multi-rom, only way to know for sure is to test it clean as intended, else we'll potentially be chasing ghosts.

Filesystem checks is possible (command is fsck, or a derivative thereof), never needed to run one on a smartphone, only on "real" Linux boxes so far. But that never will be a valid durable solution in any way, if a fsck has work to do, I'll always start fresh, be it a smartphone, PC or server partition.

You can only build a stable "thing" on a good foundation ;)

And experience in my many years of IT has taught me, that starting fresh and clean takes less time than trying to fix "such issues", it's just a matter of return on effort calculation, ethics would tell me otherwise :D

JP.

EDIT: Just checked, don't seem to find an fsck.ext4 on my phone, only exfat and msdos.
[Nexus 5 Original Android Development] Phazmos:
First rule of dirty flashing - if trouble, clean flash, actually, first rule should be - dirty flash, don't post issues.

Oh well.
[Nexus 5 Original Android Development] pseudoheld:
it was a clean flash.

my definition of dirty flash is just installing one rom ontop of another, no wipe whatsoever. (all apps etc are untouched and still present after the flash)

clean flash for me is wipe data and cache (factory reset) anything else is a complete erasing of the system as yank suggested.
[Nexus 5 Original Android Development] Yank555:
Well by clean I mean really clean, no multi-rom no xposed etc. ;)

JP.
[Nexus 5 Original Android Development] pseudoheld:
no exposed, no apps restored no nothing. only thing was multirom, but it doesn't really effect the main system afaik. it injects a preboot option to boot from another rom if installed. i didn't even have another rom installed so basically it was/is completely stock.
[Nexus 5 Original Android Development] Yank555:
Well, I will have to disagree on this, MultiROM is

a major "non-stock" thing

and it does certainly add potential problems which would not be present otherwise ;)

I guess [MENTION=3276129]Phazmos[/MENTION] pretty much summed it up, but let me be more exhaustive :

1) dirty-flash in your config should be the rule

2) run into problems, cleanflash (keep multiROM and other mods if you want)

3) still run into problems, really cleanflash (no multiROM etc., just plain wipe and install ROM as intended)

4) still run into problems, ask for help, if possible provide logs or how to reproduce your issues etc. leaving device in state 3 (no mods)

5) last step, which you could test, too, is to really wipe everything (or fastboot flash factory images if you prefer)

Step 5 being if you feel like it before asking for help, but it's totally understandable you'd want to explore other options first, 5 is really a last resort kind of thing.

And important, if you nevertheless decide to report problems in 1,2,3, then also do provide infos such as that you have multiROM, Xposed and whatnot right away.

This will speed up help, or maybe you'll get turned down because of the mods, but that's still better than to "loose" time yourself / of others trying to help until you say that you have those "mods" installed.

Now that being said, I'd recommend you go to step 3 and we get you going :)

JP.
[Nexus 5 Original Android Development] pseudoheld:
would be interesting to know if the other people experiencing issues are running multirom or are at "stock"

---------- Post added at 11:40 AM ---------- Previous post was at 11:36 AM ----------

i have already removed multirom (as you can do it with the system running) as issues still persist i guess i will reflash the rom now without multirom and see where we go.

its just that up till the recent issues with slim i never had a problem so i highly doubted that multirom was/is the culprit, but as I currently dont need it / use it i will try and reflash without multirom present.
[Nexus 5 Original Android Development] pseudoheld:
Ok clean install without multirom, no restores and no xposed...

Lets see how it goes...

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] DroidIt!:
To add to all the good advice Yank gave :) Typically if you're the only one having a particular type of issue, it's something in your setup. If it were me, if it weren't solved by the end of the day, I'd just do like yank suggested and transfer everything to PC and flash a factory image and see if all goes away. 95% chance it does, but if it doesn't then it's probably hardware. You can either transfer everything by USB, putting it in google drive like I tend to do or transfer to PC with this app https://play.google.com/store/apps/details?id=com.majedev.superbeam Sometimes for whatever reason, TiBu backups have problems completely transferring via USB to PC so I'll use that app to do the transfer. Takes a little more time but can actually be more reliable.

But to save time, I would say if not solved by the end of the day I would do as Yank and I are suggesting. You'll end up saving a lot of time I think ;)
[Nexus 5 Original Android Development] Mikulec:
This is the first time I see someone else is having problems transfering TIBU backup from phone to PC. I found a solution, I am copying the backup while in TWRP recovery, works everytime without problem.
[Nexus 5 Original Android Development] pseudoheld:
aaand im still having problems.

guess its the complete wipe then.

fastboot here i come...
[Nexus 5 Original Android Development] DroidIt!:
Good idea ;)

---------- Post added at 10:27 AM ---------- Previous post was at 10:25 AM ----------

Yep, just transfer all like stated, flash the factory image and go on stock rooted for a bit to see if you still see the same issues. If not then flash away, if you do then maybe a phone swap out :)

---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------

Yep, just transfer all like stated, flash the factory image and go on stock rooted for a bit to see if you still see the same issues. If not then flash away, if you do then maybe a phone swap out :)
[Nexus 5 Original Android Development] pseudoheld:
Installed slim already after the clean flash. Thought I'd go straight to slim to see how it goes.

So far so good.

Will report back with anything new
[Nexus 5 Original Android Development] pseudoheld:
Overall it's working better however the screen now has a delay when turning it on.

Here's a log. Any idea what's happening? It's nearly right at the end.

https://www.dropbox.com/s/nfuzx33merpuroq/2015-07-24-23-27-35.txt?dl=0
[Nexus 5 Original Android Development] Yank555:
That's most likely the lag that's been discussed, here and/or builders collective thread.

So far all I can say about it, and ezio can confirm, using older gapps is fine, recent produce those delays.

But so far no idea what exactly causes them.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1b kernel.
[Nexus 5 Original Android Development] pseudoheld:
Ok good to know ;)

Thanks
[Nexus 5 Original Android Development] stricker49:
ETA on when site will be back?

http://www.slimdevs.com/
[Nexus 5 Original Android Development] prbassplayer:
SlimDevs is permanently down
[Nexus 5 Original Android Development] derschnelle:
Do we know a reason for that?