• Pranshu

    • Post #5
    • (Edited)

    @adbo Hey so there are multiple things I want to talk about

    1. I have raised this issue multiple times even before Android 14, yet nothing is done to solve it. When you use Smallest Font Size and Smallest Display Size the network signals like 4G, 4G+, 5G, 5G+ does not change the size to smallest like you can see the difference when Font Size is One and Display Size is Smallest. The battery percentage and the clock size changes to smallest size but the network signal (4G, 4G+, 5G, 5G+) does not change even a bit. And when you open the control centre the fonts size are different. Like I don’t understand how can this be missed. I have the proof/screenshots as well so if you want I can share, now even I am tired sharing this.
    2. The New Inter Font does not apply to network signals(4G, 4G+, 5G, 5G+) you can see this clearly when you are using 4G. There are 2 different fonts for 4, 4 is different in battery or clock and 4 is different in network signal. I don’t understand how these small and visual things are missed. I feel the testing is not being done properly. Also if you need I can share the proof/screenshots for this as well.
    3. The New Inter Font does not support some text like example in X ‘Trolling is an Art’ is an account if you see it won’t be visible using Inter Font.
    4. Also the New Inter Font does not work with some Google Apps like Gmail, Google, Play Store, etc. Even X does not have support for Inter Font properly. I feel these small things make the UX more better. Since it’s directly visible to the naked eye.
    5. Why are the features still in Beta, even though Stable Release was released with half cooked features(sorry but not trying to be rude). Like what is going?

    I feel Nothing’s most unique part is Software but if these small things are being left out, I don’t know what to expect because even though these are very small things but once it is noticed it cannot be unseen🙂, all these small things makes the UX better.

    Also if you can let us know when Nothing Gallery will be fully released (not the early access one).

    Thank you for your time.

    Related discussions

    I got to know that you are launching the phone 3 in last of month of March so I would like to tell the launch date so it can be a successful product.

    I think your product should launch in Auspicious Time so your product can get a successful product.

    The date is 30/03/25 as it comes on Sunday many people will see the launch event ! As it is a free time on that day .

    Because it shows the relation between Nothing phone 3

    3+0=3

    0+3=3

    2-5=3

    Your well wisher❤️‍🩹

      Im very much satisfied with the phone, however with os 3.0 there some issues and inconsistencies with the font, QS and launcher icons

      1. QS Lag and stutters on Phone 2, also wifi bluetooth and mobile data tiles take long to respond, also no animations while opening them

      2. Change of font and display size doesn’t apply to the QS panel.

      3. Inter font has issues in certain situations, will display blank characters.

      4. Volume panel doens’t sync in with android 15 design langauge.

      5. Third party QS tiles will show as inactive after few hours of non usage.

        Most of the issue are already mentioned by user PulkitGhorse post I’m attaching link for it https://nothing.community/d/22864-nothing-os-wishlist-megathread-session-2025/37

      I’m very satisfied with my Nothing Phone 2. I have highlighted some key areas which I feel still could be improved.

      1. Digital Wellbeing- One of nothings key goals was to find a balance between good phone use and prevention of doom scrolling. What wellbeing innovations are nothing considering that can continue to bridge this gap further and make the use of tech more purposeful rather than following trend. (More use of glyphs, wellbeing modes, work modes etc)
      2. OS performance- In recent updates nothing os has become more readable and minimalist. However, in terms of performance, it doesn’t feel as smooth as it should do, for a minimal os you would expect ram usage to be low unless heavy tasks were being performed. I’d like to know more about how nothing aims to bridge this gap to make the experience feel fluid and responsive on lower hardware resources.
      3. Consistent font use would be greatly appreciated, such as using Inter across the entire UI rather than hybrid mix of different fonts. Sticking to one font, and then gradually increasing the font pool, would mean the use of fonts could be applied cohesively and consistently.

        The software has been a joy to use but I have felt that the Glyphs seem to be stalling now and there have been no significant updates to the Glyphs since the 2.5 update, almost a year ago.

        Also, the camera performance is not that bad in most scenarios but one thing I really do not enjoy is that different photo modes are not performing similarly. The Portrait mode has significantly lower quality images and does not implement the Ultra XDR feature. The consistency in camera performance needs to be addressed.

        I would say since its your first meeting, take it smooth. Other than that, I would be very interested to find out if any more widgets are coming from the community as well as any future guidelines, tips and collabs. But good luck!

        adbo 1. secure folder is must needed one. Oneplus hides there apps inside Google dialer. Nothing os “uses same fingerprint and password as lock screen”.

        1. Volume slider in notification shade(if possible) I’m worried of button wearing off.

        Please shed some light onto this

          adbo please add more games like floppy bird and block puzzle games in community widgets and mainly depth effect clocks in lockscreen and music always on display

            • LEPE

              • Post #16

              I would love to know how Nothing enables widgets to be swiped left and right as android, as far as i know, does not allow this function because it´s restricted to changing screens!
              So try and give your best to release this info to the community so that more beloved widgets can use this functionality.

              I´m not seeing any other Android OS doing this so im assuming only Nothing has this knowledge? If not then whoever has it pls share it 😅RapidZapper

              Cheers

                  Let me share some concerns from the Japanese community.

                  First, we’d like to understand why every Nothing OS release tends to arrive later in Japan compared to other countries.

                  Japanese users and the community strongly wish to receive OTA updates simultaneously with other regions.

                  What can we do to make this happen? We are willing to cooperate in any way we can.

                  There’s also the issue of Japanese font design in Nothing OS 3.0.

                  The Nothing design team is incredible, but are there any Japanese designers on the team?

                  If not, the community could strengthen its activities to help fill this gap.

                  We also ask for a Japanese topic section on the web version of the Nothing community.

                  Currently, most users rely on Discord, but this year, we’d like to increase traffic to the web version as well.

                  The Japanese community is full of supportive members.

                  This year, we aim to be more active and make a greater impact on the global stage.

                  Let me know if you’d like any adjustments or further assistance☺

                  congratulations on your new role! It’s inspiring to see how actively you’re engaging with the community and making an effort to represent our voices.

                  LEPE well, no, it’s just a custom view inside the nothing launcher, they’re not real widgets (I mean, they’re not remoteViews, like android original widgets).

                  • LEPE replied to this.

                      Hi, I would like to voice concerns from a developer perspective on the Glyph Developer Kit that I’ll just call SDK from now on and in combination with that, my support team experience:

                      I feel like that the recent support for this novel idea has died down. The state of the GitHub page was left to rot, the new Phone (2a) Plus did NOT have any support even if the README said so and after contacting the Nothing Support via the Settings > System > Feedback option (support id: 746325, 21st of October 2024) I was asked to provide all kinds of information (Phone system version, demo video, full phone logs encrypted with an unknown password?!?) that did not change a thing about fixing the problem.

                      The problem was really easy to fix in my opinion: Uploading the new SDK and updating the README.
                      And yea it should be that easy because I found a workaround that just worked by pretending that the 2a Plus is a 2a.

                      After trying to explain to the support team that nothing of that is needed to fix the issue and sending them a demo application and video that clearly demonstrates the issue at hand, I was ensured that they have forwarded this to the relevant team and that they will keep me updated.

                      After not hearing from them for a week I decided to check in and was assured that the team is working on it.
                      Then a month passed since first contact and I reached out again and it seemed like my original ticket was just closed - either by an automatic system or deliberately - since my mail was marked as a follow up inquiry.

                      What I learned later is that there was a silent update to the SDK GitHub repository (13th of November 2024) that actually added the new updated java file with compatibility for the 2a Plus. The support team also told me that the team has updated the SDK and the README on the 16th of December (more than a month since the actual SDK update) and wanted to closed the follow up support ticket (id: 805719).

                      After waiting for 57 days for this confirmation it turned out that the README was not updated and did not match with the actual logic of the SDK. I went ahead and submitted a pull request to fix the broken README and wrote that to the support team.

                      This fix of mine was promptly merged on the 18th of December (58 days in total).

                      I also want to raise the issue of the current state of the GitHub repository of the SDK:

                      This repo does not seem maintained except for the occasional update of the README and SDK itself. Many people have raised issues that are still open and not addressed. Why suggest that this SDK is open and made for collaboration by hosting it on GitHub and then not using the features and feedback provided over GitHub? Why not use the community to contribute to the SDK and make it open source? Let the community add convenience functions and help find bugs. Most of the actual led logic is hidden behind a service on the phone anyways so there is not that much that can go wrong.

                      Another thing that bummed me is that the usage of the SDK in the background is officially not possible. This may have stopped many developers in their tracks to utilize the SDK to its full potential. It is still possible though with some clever background code.

                      So just to summarize:

                      • The support team seems to not have enough time/resources to fully read the replies and just seems to follow a list with things they should do without actually looking at the problem at hand.
                      • The communication between the teams and the support team seems non optimal.
                      • The SDK should be open source and actively maintained to at least update it when a new phone releases.
                      • Consider adding proper background usage support for the SDK.

                      Thank you for your time 🙂

                        SebiAi Applause for 90 minutes! One thing I disagree is the background usage of the GDK because it is not documented how the system could handle concurrent usage of the glyphs from different apps. I would also abort the “activation key” concept and feature the apps that take advantage of this SDK to let the community know about it.

                          adbo my CMF phone 1 camera issue (dirt on the lens for both camera rare as well as selfie most of the time) still not solved