|
I had been using the store version, looking forward to the release. My Xbox music mysteriously started working and playing the files it wouldn't play earlier, so that's good.... until I try to add more music probably.
|
#
?
Apr 22, 2015 14:28
|
|
|
|
| # ? May 15, 2024 00:05 |
|
|
Drastic Actions posted:Okay, so I just submitted a new release for the regular Awful.appx app that changes the database to my new one. Hopefully once it's approved and installed it should fix the lovely database bugs that were causing all those issues for everyone not in the beta. Good news: V6.5.4.1 is already available in the phone store, and it fixed randomly crashing to the start screen while reading a thread! Bad news: It fixes randomly crashing while reading a thread by crashing automatically on startup. Every time. Even after a phone reboot and a delete/reinstall cycle. Never even got to the point of logging in after reinstalling it, just crashed immediately. Phone info: International Lumia 1520 with 8.1.1. Wizard of the Deep fucked around with this message at 14:58 on Apr 22, 2015 |
|
#
?
Apr 22, 2015 14:44
|
|
|
Wizard of the Deep posted:Bad news: It fixes randomly crashing while reading a thread by crashing automatically on startup. Every time. Even after a phone reboot and a delete/reinstall cycle. Never even got to the point of logging in after reinstalling it, just crashed immediately. Good news: If uninstalling does not work, reformat your device.  The app might be trying to read the old database file (which it will blow up on, because they are totally different) and uninstalling it might not actually be deleting it (which makes no loving sense to me, considering it's in storage on the app, but that's windows phone for ya). So you might have to reformat to fully get rid of that lovely database file. Also if it's blowing up at startup on the new version I just released, it will blow up in the beta too. Again, it's probably the database file. So yeah, reformat. EDIT: And I just reproduced it in the simulator. Installing the old version (with the crappy database) and installing the new version on top of it will cause it to blow up. And uninstalling it won't help, even though I'm storing them in ApplicationData.Current.LocalFolder it's still there, so it tries to load it. What the gently caress, this is lame :\. So yeah, I guess you do have to reformat and try again. gently caress this poo poo  .
Drastic Actions fucked around with this message at 15:17 on Apr 22, 2015 |
|
#
?
Apr 22, 2015 15:03
|
|
|
Drastic Actions posted:Good news: If uninstalling does not work, reformat your device. I think we have very different definitions of the term "good news", Professor. God, I wish there was some method of managing poo poo in these godforsaken devices.
|
|
#
?
Apr 22, 2015 15:18
|
|
|
Uh. The app was not crashing for me before, ever, but now post-update it is crashing on load, even post-reinstall, and I guess reformatting my device is the only way to fix it? Guess I'm done reading the forums on my phone then, I had a good run Seriously though if an update will make the app permanently crash on load for a subset of users maybe don't push it? Just spitballing here e: not even trying to be snarky, please rollback to old version loquacius fucked around with this message at 15:34 on Apr 22, 2015 |
|
#
?
Apr 22, 2015 15:32
|
|
|
loquacius posted:Uh. The app was not crashing for me before, ever, but now post-update it is crashing on load, even post-reinstall, and I guess reformatting my device is the only way to fix it? Gonna throw this out there: I didn't loving know it was an issue, or I would not have released it  EDIT: Also, can't roll back, because then the original people who had issues are still hosed, and people who did update fine will likewise also be hosed. So really, it's totally hosed .So I pushed a new version that changes the file name, and also puts in protections so the stupid thing will be deleted if you uninstall the app. So that should hopefully fix it. It upgraded fine on the simulator anyway. Drastic Actions fucked around with this message at 15:48 on Apr 22, 2015 |
|
#
?
Apr 22, 2015 15:34
|
|
|
Drastic Actions posted:Good news: If uninstalling does not work, reformat your device. Really glad I got an HTC M8 Windows instead of the Android version. FYI if you have an M8 windows, don't update the dot view update as it will screw up your dot view case and make it worthless! I'm holding on to the dumb platform only because of Windows 10, which my phone may not get anyway, in hopes that *this* update will fix WP.
|
|
#
?
Apr 22, 2015 15:52
|
|
|
loquacius posted:Guess I'm done reading the forums on my phone then, I had a good run I'm not trying to poo on the guys making forum reader apps, but the forums are perfectly readable in the IE browser. I personally haven't ever understood the need for an app.
|
|
#
?
Apr 22, 2015 15:55
|
|
|
The apps make it a lot faster and cleaner overall. In IE, the quotes are huge, but still readable. Where I edited my above post, the strikeout is fine, but the line after is unreadable. I'm at the point where, unless Windows 10 blows me away, I'll get the iPhone 6s or maybe the iPhone 6s+. I'll wait the next five months or so for the next release. Hopefully Apple will switch to a USB-C interface now rather than later.
|
|
#
?
Apr 22, 2015 16:00
|
|
|
Another update submitted and approved, check shortly and see if that fixes the issue. I tried upgrading it on the simulator and it worked fine. I tried on my person devices and it worked fine. I'm not saying there are no issues. Worst case scenario is to reformat and try again, but (and this is going to shock people here) I'm trying to avoid that. Sorry for loving up your morning. I don't have a QA team that can check every possible test case for bugs and regressions. It worked for me and for the windows tester (who, I'm going to assume, had a fresh device and did not run into this issue), so I didn't catch it. It happens. You deal with it and move on. But to the person who found my work email to tell me the app broke: don't do that. Thanks .
Drastic Actions fucked around with this message at 16:21 on Apr 22, 2015 |
|
#
?
Apr 22, 2015 16:19
|
|
|
There was a small update to the music app: - You can now delete items from the recently played section, which is helpful as most every update has hosed this up and made a mess of it IME. - In settings, there is a "Sync Now" option, so you can finally force a sync of your music and playlists as opposed to XM updating it whenever the gently caress it wants. So 2% less lovely now, woop
|
|
#
?
Apr 22, 2015 16:19
|
|
|
MobMentality posted:So if I had to move to an OS to wait out the fuckery of W10s release would it be easiest to go to ios or Android from Windows?
|
|
#
?
Apr 22, 2015 16:21
|
|
|
Drastic Actions posted:Another update submitted and approved, check shortly and see if that fixes the issue. I tried upgrading it on the simulator and it worked fine. I tried on my person devices and it worked fine. I'm not saying there are no issues. Worst case scenario is to reformat and try again, but (and this is going to shock people here) I'm trying to avoid that. Awesome, thanks! I apologize if my first post on the issue was lovely. It wasn't meant as a personal attack or anything, I guess the sarcasm wasn't as obvious as I wanted it to be. poo poo happens, we all move on. I really appreciate your efforts in bailing out this burning, sinking platform, so thanks!
|
|
#
?
Apr 22, 2015 16:28
|
|
|
I finally found how to make a playlist using Windows Explorer and jesus christ what the hell this is hosed up. Right-click on any song, select Create Playlist. This creates a new .pla file which is just a dummy placeholder. Right-click on the file, select Properties, go to the References tag, and delete that song and drag more on it. I now wish I never knew. This UI is the worst.
|
|
#
?
Apr 22, 2015 16:49
|
|
|
Suspicious Dish posted:I finally found how to make a playlist using Windows Explorer and jesus christ what the hell this is hosed up. 
|
|
#
?
Apr 22, 2015 17:34
|
|
|
Even if you have an Xbox music pass and can sync playlists from the Music app, it's still a clusterfuck (even aside from having to use the 8.1 music app). One of the problems that's always existed with the XB Music app on 8.1 is that it would try and 'match' the music from your collection with what exists in XB Music, except that it usually did a horrible job. You would frequently have completely mismatched albums/album art, duplicate tracks and albums , and for the tracks that it coudl match, some had licensing restrictions such as they couldn't be downloaded to be played offline, or their license would suddenly be revoked. This is even separate from the 'other' duplicate track problem with Windows Phone 8.0 - that was a constant music DB corruption issue that took about a year to fix (for most). This was compounded by the fact that the Music app would prioritize the Xbox Music version of your collection (even if you didn't have an active XB Music pass subscription), so say if you viewed a particular artist, the only version of the album you would see was what Xbox Music could find its licensed DB - so you might see your album with identical album cover art (maybe) as the ripped version in your collection, but would only see the tracks that the (meagre) Xbox Music service had licensed, so invariably you might be missing tracks. Only by going into the Album view and searching for that album would you find that you had 2 copies, and of course they look identical until you go into each version and see which has the lesser # of tracks or has the small streaming icon beside it, indicating it's from the XB music catalog and not your local. Of course when you attempt to remove those duplicate tracks, you would get an identical question (Do you want to remove this from your collection?) as you would if you were actually deleting songs from your local storage as opposed to just removing the title name from your collection - all for naught regardless, as when you restarted Xbox music it would try to match tracks again as well and just gently caress up your collection again. Over time there were small obvious should-have-been-at-launch improvements with icon clarity designating which tracks were streaming/downloaded/local, and matching improved - a bit. But really, the only way to avoid this crap with your local collection was to got into settings and just disable Xbox Music from trying to automatch your album data. You could still access your streaming/downloading abilities, but at least it would stop loving with your collection and present only what you actually had. The problem is that if you want to utilize playlist syncing from desktop->phone, you don't have that option to just skip Xbox Music's attempt to 'organize' your locally stored copy on your phone, you have only one option - to 'sync my online collection'. It's bad enough that you ever need a paid subscription (to one of the most sparsely populated online music catalogs to boot) just to sync playlists, but because you will invariably end up with duplicate tracks/albums on your phone, that will often screw up the playlist syncing. For example, just recently I had a playlist synced from my PC to my 635 a while ago, the PC's playlist was compromised entirely of local songs from my collection and it was seemingly finding the local tracks just fine on my phone's SD card when it synced. Invariably after an update to the phone app, suddenly I'm walking about and I notice some songs are being skipped - what happened was that the playlist was automatically 're-created' after the update, and despite having perfectly legitimate local copies on the phone, it went out to the Xbox Music service and found identically named tracks - except the license agreements for those tracks had expired, so it starts skipping them on my playlist. It replaced the tracks in my playlist that had legitimate copies from the local source with tracks that were removed from the service - holy poo poo. Only by completely wiping and re-creating the playlist on both my PC and phone did I eventually get it to pick the right tracks - for now at least. gently caress you could have a blog with weekly updates on how useless the music experience has been from MS. tl/dr: XBox music is bad and always will be
|
|
#
?
Apr 22, 2015 18:01
|
|
|
Drastic Actions posted:Another update submitted and approved, check shortly and see if that fixes the issue. I tried upgrading it on the simulator and it worked fine. I tried on my person devices and it worked fine. I'm not saying there are no issues. Worst case scenario is to reformat and try again, but (and this is going to shock people here) I'm trying to avoid that. What's the new version number? The store says 2015.422.1442.4741 but it's still crashing on startup for me even after uninstalling and reinstalling the app. I had installed the bum update if that matters.
|
|
#
?
Apr 22, 2015 18:25
|
|
|
Edward IV posted:What's the new version number? The store says 2015.422.1442.4741 but it's still crashing on startup for me even after uninstalling and reinstalling the app. I had installed the bum update if that matters. That is the newest version, which means you should probably reformat and reinstall. It sucks, I know it does, but that's the only thing I can think of at this point that should take care of it. Every new device I install it to (include QA devices I swiped at work  ) all work with the newest version, but none of them had the previous one on there. So...
|
|
#
?
Apr 22, 2015 18:46
|
|
|
Edward IV posted:What's the new version number? The store says 2015.422.1442.4741 but it's still crashing on startup for me even after uninstalling and reinstalling the app. I had installed the bum update if that matters. Both devices are Win10. I'll try and get some crash logs if it's possible.
|
|
#
?
Apr 22, 2015 19:06
|
|
|
I went to the Microsoft store over the weekend and picked up a 635 for $49 to replace my 520 until flagships arrive. Anyone have an idea why they phased out the 1520 so soon without a successor? It seemed a bit..early. Not that I was going to buy one but I would have liked to look at that big ol screen one more time  I wasn't expecting the 635 to run a whole lot better than the 520 but I've been pleasantly surprised. I guess a boost in processing power goes a long way.
|
|
#
?
Apr 22, 2015 19:16
|
|
|
bushes posted:I went to the Microsoft store over the weekend and picked up a 635 for $49 to replace my 520 until flagships arrive. Anyone have an idea why they phased out the 1520 so soon without a successor? It seemed a bit..early. Not that I was going to buy one but I would have liked to look at that big ol screen one more time In this same vein, all the positive discussion of the 925 a few pages ago inspired me to buy a used one for $70 on ebay to replace my 520. I know it's a pretty old phone but it has LTE, a camera, and that wonderful OLED display with glance. I probably would have bought a 640 otherwise.
|
|
#
?
Apr 22, 2015 19:29
|
|
|
bushes posted:I went to the Microsoft store over the weekend and picked up a 635 for $49 to replace my 520 until flagships arrive. Anyone have an idea why they phased out the 1520 so soon without a successor? It seemed a bit..early. Not that I was going to buy one but I would have liked to look at that big ol screen one more time The lumia 1520 is a 2013 phone comparable to the Galaxy note 3. Neither ATT or Verizon still sells new Galaxy note 3s although you can get refurbs. It wasn't so much retired early as Microsoft just hasn't bothered releasing new flagships in the US since it came out.
|
|
#
?
Apr 22, 2015 19:35
|
|
|
xylo posted:Same. My retail device that has the old database still blows up. I also have a brand new device that I got yesterday that is blowing up. I did notice that I saw some "restoring data" during the store install so I'm wondering if you hooked into application backup and the data was coming from that? I'm not. It should all be local. I formatted all my devices now and installed it from the store. It worked. I deployed directly to my device. it worked I have no idea what could be screwing it up, because it is seriously working just fine when I try it.
|
|
#
?
Apr 22, 2015 19:37
|
|
|
bushes posted:I went to the Microsoft store over the weekend and picked up a 635 for $49 to replace my 520 until flagships arrive. Anyone have an idea why they phased out the 1520 so soon without a successor? It seemed a bit..early. Not that I was going to buy one but I would have liked to look at that big ol screen one more time Honestly it's a combo of things. I really didn't like the drive to push to just lower the BOM in any way possible and optimized software -- the always seemed to result in cheaper/less parts, rather then creative ways to keep a better part and lower the BOM elsewhere (either design or volume). I love to never see another sub 615/805 or whatever (8916/8909 etc) phone again Drastic Actions posted:I'm not. It should all be local. I formatted all my devices now and installed it from the store. It worked. I deployed directly to my device. it worked xylo fucked around with this message at 20:00 on Apr 22, 2015 |
|
#
?
Apr 22, 2015 19:56
|
|
|
xylo posted:Windows Phone - go slam your dick into a car door a few hundred times before you do so it seems like a less painful experience
|
|
#
?
Apr 22, 2015 20:07
|
|
|
CalvinandHobbes posted:The lumia 1520 is a 2013 phone comparable to the Galaxy note 3. Neither ATT or Verizon still sells new Galaxy note 3s although you can get refurbs. xylo posted:Same. My retail device that has the old database still blows up. I also have a brand new device that I got yesterday that is blowing up. I did notice that I saw some "restoring data" during the store install so I'm wondering if you hooked into application backup and the data was coming from that? xylo posted:Should have waited for the 640 that should be in any day now Meh. If I'm going to get into a contract or at&t next or whatever I want it to be a phone that'll last me a looong time. My iphone 4s that I still have lying around still works great and I figure if I splurge as much on a WP as I did on that I can get the same kind of results (hopefully). A $200+ phone is a little bit too steep for a stopgap measure 
|
|
#
?
Apr 22, 2015 21:05
|
|
|
Drastic Actions posted:I'm not. It should all be local. I formatted all my devices now and installed it from the store. It worked. I deployed directly to my device. it worked I'm having the same issue here, but maybe a weekend project of reformatting the device is in order. There's no way to navigate to the folder the database file is in that's screwing things up and manually delete it, is there? Whether using an app on the phone or just going through a computer? Edit: Speaking of reformatting, since I've never done that before does anyone have a rough idea of how long that takes to reformat and install the backup? Ev fucked around with this message at 22:38 on Apr 22, 2015 |
|
#
?
Apr 22, 2015 22:35
|
|
|
Ev posted:I'm having the same issue here, but maybe a weekend project of reformatting the device is in order. There's no way to navigate to the folder the database file is in that's screwing things up and manually delete it, is there? Whether using an app on the phone or just going through a computer? It should be in the app folder, which you don't have access to. What I want is if someone is having the issue is to reformat, reinstall, and see if that does fix it. If not, then at least one person bit the bullet rather than everyone. I should be getting crash logs in a few days hopefully, but that's too long. If someone could check, that would be cool. If only I could reproduce this 
|
|
#
?
Apr 22, 2015 22:47
|
|
|
Drastic Actions posted:It should be in the app folder, which you don't have access to. What I want is if someone is having the issue is to reformat, reinstall, and see if that does fix it. If not, then at least one person bit the bullet rather than everyone. I'm resetting my phone now so we'll see if that helps in a few hours.
|
|
#
?
Apr 22, 2015 22:58
|
|
|
Edward IV posted:I'm resetting my phone now so we'll see if that helps in a few hours. Hold off on it. I'm debugging it now and it might be something really weird.
|
|
#
?
Apr 22, 2015 23:17
|
|
|
Too late. It's only a factory reset rather than rolling back with the recovery tool so I don't have to go through the trouble of resigning up for the developer preview, installing the preview updates, and reorganizing my start screen. Right now, it's restoring from a backup.
|
|
#
?
Apr 22, 2015 23:26
|
|
|
Edward IV posted:Too late. It's only a factory reset rather than rolling back with the recovery tool so I don't have to go through the trouble of resigning up for the developer preview, installing the preview updates, and reorganizing my start screen. Right now, it's restoring from a backup. I'm saying that because I'm about 99% sure now it will still fail, because I finally got it reproducing on device. And if it's the issue I think it is, it's a subtle as all gently caress bug to catch. EDIT: Okay people, submitted yet another package, and this time I'm really sure it should at least not crash at start up .So here's what I found for those playing along at home (who care about this programming sort of thing). Basically, some old database code I had that did some jank as gently caress reflection was still being called deep inside the startup method. Now, in the main WP program I still had the libraries that required that reflection (which were no longer being used anyway, it was for the old database) but there was no actual code being called for those libraries, they were just referenced. Now, when the reflection call was made in my release build APPX, it ran fine because the libraries were still there. But in the STORE release (IE: What you all have) it failed, because the libraries were being stripped from that appx. I only saw that by loving running WinDbg on the store release, which took a good hour to set up, and saw that it was trying to reference something that was not there. So in the end:  Also note that the old database file was still an issue, just a separate and also stupid one. So there was a multitude of things that hosed up. This new build should work, because now everything database related it called after startup is fully done, and if it fails, it should give a message. I'm guessing it will still fail, but now I can get a nice stack trace rather than a crash on start up. Sorry everyone. Again,
Drastic Actions fucked around with this message at 00:10 on Apr 23, 2015 |
|
#
?
Apr 22, 2015 23:35
|
|
|
Whelp, the app is STILL somehow broken after a factory reset. Does a factory reset not scrub everything clean? Or is it that screwy of a bug? Hopefully, this next update will work or I might have to use the recovery tool.
|
|
#
?
Apr 23, 2015 01:53
|
|
|
Edward IV posted:Whelp, the app is STILL somehow broken after a factory reset. If you read what I had above, it's probably not just the database file issue, it's another one. The newest newest update was submitted and approved a few hours ago, but it's still not live in the store yet. When it is it should hopefully fix the issue right this time. EDIT: The newest store release is 2015.422.2259.4971 : 6.5.6.3 So it should have updated. The good news is that it should not crash on start up (as long as you didn't have bookmarks as your launch page). The bad news is bookmarks and SAclopedia is borked. The database files are not being created now for them. This, despite the fact that it totally does do it on my debug and release builds if I deploy them directly to me device .I'm working on it. I'm updating my desktop and laptop Windows 10 builds so it may not be tonight but I'll try to get another build fixing that too. I will figure this out. It's so stupid. Drastic Actions fucked around with this message at 02:21 on Apr 23, 2015 |
|
#
?
Apr 23, 2015 02:00
|
|
|
Drastic Actions posted:If you read what I had above, it's probably not just the database file issue, it's another one. The newest newest update was submitted and approved a few hours ago, but it's still not live in the store yet. When it is it should hopefully fix the issue right this time. I can confirm the .3 version is up in the store now. Of course, my start page for the app is the bookmarks Thanks again for your support and patience with dumb things! ETA: Confirmed, it's more working than it was this morning! Wizard of the Deep fucked around with this message at 02:40 on Apr 23, 2015 |
|
#
?
Apr 23, 2015 02:35
|
|
|
Newest version of the app works, thanks for all your hard work!
|
|
#
?
Apr 23, 2015 03:08
|
|
|
So now when I open the app it says:code:
|
|
#
?
Apr 23, 2015 03:21
|
|
|
Ev posted:So now when I open the app it says: quote:So it should have updated. The good news is that it should not crash on start up (as long as you didn't have bookmarks as your launch page). The bad news is bookmarks and SAclopedia is borked. The database files are not being created now for them. This, despite the fact that it totally does do it on my debug and release builds if I deploy them directly to me device Yep, that's what I expected. Funny enough, I think I figured that out, pushed ANOTHER update and hopefully that gets accepted and fixes bookmarks and SAclopedia.
|
|
#
?
Apr 23, 2015 03:25
|
|
|
Drastic Actions posted:Yep, that's what I expected. Funny enough, I think I figured that out, pushed ANOTHER update and hopefully that gets accepted and fixes bookmarks and SAclopedia. That's my bad, I missed where you said that. But serious thanks for all the work you're putting into this!
|
|
#
?
Apr 23, 2015 03:30
|
|
|
|
| # ? May 15, 2024 00:05 |
|
|
Yes, thank you for your hard work as always, Drastic Actions. The app hasn't crashed on me all day, which is a good sign.
|
|
#
?
Apr 23, 2015 03:41
|
|
