Fr4nKB silver0346 apparently it has some problems with Phone(2a)s, I’m uploading a fix as I write this and it will be out tomorrow around 1PM CET Sticky_PRP thank you, just fixed that
Hardik Fr4nKB no the lines are not fixed and with the latest general release of nothing os 2.0 in phone 2 extential notification aren’t working.
Fr4nKB Hardik the lines will be fixed with tomorrow’s update, the message before was just acknowledging the bug. Have you tried rebooting? I remember all glyph apps being broken for a week when they released 3.0 beta, I hope this is not the case again as I didn’t have any power in fixing that.
Fr4nKB Hardik report this to Nothing’s team via settings -> system -> feedback, you can turn on glyph debug mode as a temporary solution @Rob ⚡️ @RapidZapper do you have any reports about 3.0 stable messing up with GDK like last time? @JayKay135 has the same problem with his app
Hardik Fr4nKB i an just waiting for todays update maybe it could make any change, even after the update it didn’t get fixed I will surelyy report this.
Fr4nKB Hardik hardly doubt that, it doesn’t depend on me. It’s really frustrating since many people have bought the app and now cannot use it. muhkuhaushonolulu only affects Phone(2)s, just like last time, which is also the most used device by Glyphify’s users
muhkuhaushonolulu @Fr4nKB after the latest stable 3.0 update for (2a) extential and battery indicator are working without problems for me
Hardik Fr4nKB These shady moves by Nothing are making it worse Updates the app and provided the feedback to nothing. How much time do you think they will take? Guys is it only me or everyone with phone 2 is encountering the issue.
ThanosB Hardik yeah something is off. And the light torch widget doesn’t seem to be working or I miss something and the charging indicator doesn’t work for me
Fr4nKB ThanosB Bubi Hardik last time this happened it took them about a week to fix (6 Nov - 14 Nov), a week is also the time most EU countries have to wait to get updates after they are announced. I think the two things are connected.
Hardik @Fr4nKB buddy what we had to last timw for fixing this on phone 2? Because this sucks right now, I have reported it, but idk how and when it’ll be fixed, what all happend during the previous beta period?
Bubi Fr4nKB thanks for the continuous support and all the effort you’re putting into this. I have faith that the issue will end up being solved, because if glyphify worked on the beta version, ir should work fine on the stable version. Keep up the good work and Merry Christmas!
ThanosB Fr4nKB Yep I can confirm, my Glyph debug was off, I eneble the dev mode and turned it on, restarted the device, and now the App is working properly, you can turned the glyph debug off again after the restart (Phone 2)
Fr4nKB deLight_ Unfortunately it’s not possible, I’m sorry MarkFrancis I’m glad Glyphify is your favorite app, really honored🤩 Yes, you can go into developer options, activate glyph debug mode and restart the app (force stop). Hopefully Nothing will have this problem fixed by next week…
MarkFrancis Just updated to Android 15/3.0 and my favourite app has stopped working. @Fr4nKB - Wasn’t there something in developer mode that we had to do in the early days of Glyphify? Would that help?
JayKay135 Fr4nKB Nothing was able to resolve this issue yesterday. At least my app is working again. And I’ve also tested another app from the Play Store. I assume there was an issue with their firebase integration. Probably some messed up database rules. I’ve additionally messaged them via email which for the future is probably the best way to get a quick response. I just hope that we don’t have to experience something like this ever again. I was forced to code, test, translate and publish a developer message for my app in no time to avoid further 1 star reviews. Still, there were several people complaining about my app not working in the Play Store. At least the issue got resolved in a somewhat resonable amount of time. I’ve screwed up my SHA1 key in the past and had to wait two weeks for a reply.
