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!

Related discussions

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

                      How to achieve a perfect OS? What do we need more, what could we expect?

                      Im enjoying my Phone (2), i wish you all have a great meeting!

                      • LEPE

                        • Post #28

                        Mirko_ddd

                        Oh I see, thx for the info. So I think they are gonna keep that for themself 🙁

                          1. I want to know whether the Nothing team is aware of the Inconsistent performance of the camera. if yes, what are the measures they have taken?
                          2. Last year when @RohitPakalapati was there, we raised concerns regarding support for cmf watch pro 1. But there were no improvements made till date
                          3. And there are so much bugs in the OS 3.0 and also the features they showed in Nothing OS 3.0 video are not yet fully released. Why should they hurry and release the OS half baked?

                          Thx for asking, not sure this has been done previously, can consider pitching an idea to showcase Nothing’s work process behind a software update, e.g.

                          • how does the team decide on which bug/problem to focus on, i.e. is there a decision matrix used?
                          • how is the update tested prior to release?
                          • is there already a rough roadmap of what features to add in the next few updates?
                          • how does the software update process affect decision-making for future new models? e.g. software team tries hard to improve camera software, but there is a limit to what software can do, leading to decision making to use a larger camera sensor for future models

                          personally think this will help fans understand the difficulties of a software update, that not all bugs can be solved at the same time, etc.

                          Phone 2 users have been raising this issue ever since the phone is out. Please improve the CAMERA. The performance is inconsistent.