https://telemetry.clashprojects.qd.je/ Its really cool btw , u guys can check telemetry too . Daily , Weekly , Monthly stats too , just from link.
❤24
Which of these addition , we should consider first ?
Anonymous Poll
37%
Podcast + Video 🗿🗿
63%
Spookipie Integration + Listen Togethe🤒
❤5⚡1
LET ME SOLO HER
Which of these addition , we should consider first ?
Why u guys aren't voting for podcast + video , Imagine listening "Aaj ki RAAT" at loseless quality with 4K video , Just Epic.
😭31❤3
LastWave-v4.3.1-release.apk
24.9 MB
LastWave
What's New in v4.3.1
- Reworked Audio Output Indicator: Redesigned signal path screen with live Fidelity & DSP scores, stream health, clock drift, and latency stats.
- Smoother Playback: Optimized audio buffering and frame delivery for faster, glitch-free track playback.
- Better Algorithms: Upgraded core audio processing and track-matching logic for improved accuracy.
- Playback, Bit-Perfect & DAC Fixes: Resolved playback bugs, stabilized bit-perfect USB DAC routing, and fixed Exclusive Mode handshakes.
Github -: https://github.com/Clash-Projects/LastWave-Native/releases/tag/4.3.1
What's New in v4.3.1
- Reworked Audio Output Indicator: Redesigned signal path screen with live Fidelity & DSP scores, stream health, clock drift, and latency stats.
- Smoother Playback: Optimized audio buffering and frame delivery for faster, glitch-free track playback.
- Better Algorithms: Upgraded core audio processing and track-matching logic for improved accuracy.
- Playback, Bit-Perfect & DAC Fixes: Resolved playback bugs, stabilized bit-perfect USB DAC routing, and fixed Exclusive Mode handshakes.
Github -: https://github.com/Clash-Projects/LastWave-Native/releases/tag/4.3.1
❤39🔥10⚡2❤🔥1
Maintaining the desktop app is tough. It is not a port of the Kotlin app [KMP] ; rather, it is a full Flutter app built from scratch. There are many bugs, so let's switch to the website instead of fixing it. 🤒
🤣32👏6😁3🗿2
We're now on Reddit!
Join and follow our official subreddit community here:
👉 https://www.reddit.com/r/LastWave/
Join and follow our official subreddit community here:
👉 https://www.reddit.com/r/LastWave/
Reddit
r/LastWave
Unofficial LastWave discussion sub.
⚡16❤4👍3
LET ME SOLO HER
Maintaining the desktop app is tough. It is not a port of the Kotlin app [KMP] ; rather, it is a full Flutter app built from scratch. There are many bugs, so let's switch to the website instead of fixing it. 🤒
Desktop Beta 1.3.0 is coming soon. By the way, how many of you fell for this ragebait?
❤20
LastWave
What's New in v1.3.0 (Beta)
- 17 Lyrics Providers: Upgraded from 5 to 17 synced lyrics sources running together, with word-by-word sync and quick source switching right from Now Playing.
- Dolby Atmos Support: Added native Dolby Atmos streaming and tagged .m4a downloads, plus Atmos badges on the player and track cards.
- YouTube Music Login & Sync: Added cookie login support so your liked and unliked songs sync directly with your YouTube Music account.
- Faster Engine & 144Hz UI: Smoother 144Hz scrolling, instant app startup, and zero background CPU usage when minimized.
- Live Map, Matching & UI Updates: Added an optional global live listening map, better multi-artist and accent matching, a cleaner Discord status card, and deeper AMOLED black themes.
Downloads -: https://github.com/Clash-Projects/LastWave-Desktop/releases/tag/v1.3.0
What's New in v1.3.0 (Beta)
- 17 Lyrics Providers: Upgraded from 5 to 17 synced lyrics sources running together, with word-by-word sync and quick source switching right from Now Playing.
- Dolby Atmos Support: Added native Dolby Atmos streaming and tagged .m4a downloads, plus Atmos badges on the player and track cards.
- YouTube Music Login & Sync: Added cookie login support so your liked and unliked songs sync directly with your YouTube Music account.
- Faster Engine & 144Hz UI: Smoother 144Hz scrolling, instant app startup, and zero background CPU usage when minimized.
- Live Map, Matching & UI Updates: Added an optional global live listening map, better multi-artist and accent matching, a cleaner Discord status card, and deeper AMOLED black themes.
Downloads -: https://github.com/Clash-Projects/LastWave-Desktop/releases/tag/v1.3.0
❤22🔥2
When we first planned the desktop app, I initially went with a KMP (Kotlin Multiplatform) port of our Android app. While it was easy to port over, it simply couldn't hit the lightweight performance we wanted so we shifted to Flutter.
A few days later, Kehan and Mrinmoy joined the team. When we first launched LastWave Desktop, it was honestly pretty heavy: sitting at around 10–15% idle CPU usage (on an Intel Core Ultra 7 155H) and eating 800 MB–1 GB of RAM.
Since then, we’ve slowly added new lyric providers, fixed track-mismatch issues, and poured our energy into pure stability, speed, and low-level optimization.
Where we are today:
RAM Usage: ~150 MB (down from ~1 GB)
CPU Usage: ~1% while actively playing Hi-Res Lossless FLAC (down from 10–15% idle)
Yes, there are still features missing, and we haven't focused purely on feature-stacking yet. Our goal was never cheap Apple-like translucency or flashy animations that eat up system resources we just wanted to build a simple, minimalistic, and genuinely lightweight music client.
Updates might be slow for a while because life is busy right now: Kehan is in his final year of B.Tech with his own workload, Mrinmoy is in his JEE drop year, and I have my own Boards and JEE prep going on.
That said, much more is coming to the desktop app soon! Even with the quiet update schedule, looking at how cleanly and efficiently it runs right now, I can confidently say LastWave is if not the best easily one of the best desktop and Android music clients out there. Thank you all for sticking with us! ❤️
A few days later, Kehan and Mrinmoy joined the team. When we first launched LastWave Desktop, it was honestly pretty heavy: sitting at around 10–15% idle CPU usage (on an Intel Core Ultra 7 155H) and eating 800 MB–1 GB of RAM.
Since then, we’ve slowly added new lyric providers, fixed track-mismatch issues, and poured our energy into pure stability, speed, and low-level optimization.
Where we are today:
RAM Usage: ~150 MB (down from ~1 GB)
CPU Usage: ~1% while actively playing Hi-Res Lossless FLAC (down from 10–15% idle)
Yes, there are still features missing, and we haven't focused purely on feature-stacking yet. Our goal was never cheap Apple-like translucency or flashy animations that eat up system resources we just wanted to build a simple, minimalistic, and genuinely lightweight music client.
Updates might be slow for a while because life is busy right now: Kehan is in his final year of B.Tech with his own workload, Mrinmoy is in his JEE drop year, and I have my own Boards and JEE prep going on.
That said, much more is coming to the desktop app soon! Even with the quiet update schedule, looking at how cleanly and efficiently it runs right now, I can confidently say LastWave is if not the best easily one of the best desktop and Android music clients out there. Thank you all for sticking with us! ❤️
❤41👍6
Forwarded from Samaksh
Hello everyone, I am Samaksh creator and maintainer of OriginSU,
Regarding this blog post: https://spacealtctrl.net/blog/standing-on-the-shoulder-of-giants
I want to share my side of this situation because I feel like the blog doesn't tell the whole story.
The issue is about Sentinel and Zygisk-Ultima from ReSukiSU Ultima and the related implementations in OriginSU. The author has raised concerns about attribution and is now threatening to send me a DMCA notice.
For context, here's my commit regarding Origin Veil:
https://github.com/samakshkambxj/OriginSU/commit/8a163023e
My work and commit history are public. I'm not trying to hide the development process or where the work came from. Open-source development involves building on existing projects, and I believe these situations should be handled by looking at the actual code, licences, and contributions rather than jumping straight to accusations.
When he first confronted me about the credits, I added attribution to my repository. I also asked him to take down the blog post in return, because I wanted to settle things privately and move on. He didn't respond to that request and blocked me.
Now, after some time, he's back with threats of a DMCA notice.
I'm happy to discuss legitimate concerns about attribution or licensing, and I'll address any specific issues that are actually identified. But I don't think it's fair to ignore my attempt to resolve the matter and continue escalating things publicly.
Honestly, this whole situation has started to feel like harassment. There's a difference between protecting your work and repeatedly targeting another developer after they've made an effort to address your concerns.
I'm not here to attack anyone or start drama. I just want people to hear both sides before forming an opinion. My repository, commits, and subsequent changes are public, so anyone interested can examine the actual history for themselves.
I'm open to resolving genuine technical or licensing concerns, but I also expect the discussion to remain respectful.
Regarding this blog post: https://spacealtctrl.net/blog/standing-on-the-shoulder-of-giants
I want to share my side of this situation because I feel like the blog doesn't tell the whole story.
The issue is about Sentinel and Zygisk-Ultima from ReSukiSU Ultima and the related implementations in OriginSU. The author has raised concerns about attribution and is now threatening to send me a DMCA notice.
For context, here's my commit regarding Origin Veil:
https://github.com/samakshkambxj/OriginSU/commit/8a163023e
My work and commit history are public. I'm not trying to hide the development process or where the work came from. Open-source development involves building on existing projects, and I believe these situations should be handled by looking at the actual code, licences, and contributions rather than jumping straight to accusations.
When he first confronted me about the credits, I added attribution to my repository. I also asked him to take down the blog post in return, because I wanted to settle things privately and move on. He didn't respond to that request and blocked me.
Now, after some time, he's back with threats of a DMCA notice.
I'm happy to discuss legitimate concerns about attribution or licensing, and I'll address any specific issues that are actually identified. But I don't think it's fair to ignore my attempt to resolve the matter and continue escalating things publicly.
Honestly, this whole situation has started to feel like harassment. There's a difference between protecting your work and repeatedly targeting another developer after they've made an effort to address your concerns.
I'm not here to attack anyone or start drama. I just want people to hear both sides before forming an opinion. My repository, commits, and subsequent changes are public, so anyone interested can examine the actual history for themselves.
I'm open to resolving genuine technical or licensing concerns, but I also expect the discussion to remain respectful.
GitHub
GitHub - samakshkambxj/OriginSU: A fork of ReSukiSU, designed specifically for the Origin Kernel, with additional features and…
A fork of ReSukiSU, designed specifically for the Origin Kernel, with additional features and cosmetics - samakshkambxj/OriginSU
❤12
LET ME SOLO HER
Hello everyone, I am Samaksh creator and maintainer of OriginSU, Regarding this blog post: https://spacealtctrl.net/blog/standing-on-the-shoulder-of-giants I want to share my side of this situation because I feel like the blog doesn't tell the whole story.…
Throwing around threats of bogus DMCA takedowns and shouting about filing actual legal cases while straight-up blocking my friend from communicating is just pure, childish intimidation.
Under GNU GPLv3 Section 8, a first-time attribution oversight is explicitly a legally curable offense: once you add the credit, the license is permanently reinstated, and any legal standing to claim copyright infringement or force a takedown completely vanishes. If @spacebarred refuses to talk, hides behind legal threats, and blocks good-faith attempts to resolve it, they're just posturing and completely ignoring how the open-source license they chose to use actually works.
Under GNU GPLv3 Section 8, a first-time attribution oversight is explicitly a legally curable offense: once you add the credit, the license is permanently reinstated, and any legal standing to claim copyright infringement or force a takedown completely vanishes. If @spacebarred refuses to talk, hides behind legal threats, and blocks good-faith attempts to resolve it, they're just posturing and completely ignoring how the open-source license they chose to use actually works.
💯13❤8
Looking for Reddit moderators to join the team! Must have solid Reddit reach and engagement history ,DM me if you're interested. Also, something special for active Reddit posters is dropping very soon, so stay tuned! https://www.reddit.com/r/LastWave/
❤20
Sorry, but there is no new patch for Android. It is all done. Now, for nearly one month, we have just been running on patches.
It's time for a big update.
🗿29❤6
KR$NA's "Boom Shaka" is currently sitting at #7 on the LastWave charts. Let's push it to #1 as the most-listened track on LastWave , Let's listen it on Repeat 🎶🎵
#communitydare
#communitydare
🗿16❤4🤣4⚡2🤔1😭1
LET ME SOLO HER
Introducing the L-Bitches Addon for unlimited lossless streaming and downloads! It uses a different source, so when used together with the regular addon, it'll give you an extra library and higher quality. Just Unlimited Streaming and Unlimited Downloads…
The L-Bitches Addon was supposed to be dead, but honestly, what a joke it’s still working completely fine. They can't even patch a reverse-engineered community addon, so we’re just out here abusing it at fullest capacity anyway.
Stability is never guaranteed since it was never mine to begin with, but since their devs are clearly asleep, just ride it out. If anyone runs into lossless stuttering or playback issues, just uninstall it. Otherwise, enjoy milking it while it lasts.
Stability is never guaranteed since it was never mine to begin with, but since their devs are clearly asleep, just ride it out. If anyone runs into lossless stuttering or playback issues, just uninstall it. Otherwise, enjoy milking it while it lasts.
🤣21❤2
LET ME SOLO HER
The L-Bitches Addon was supposed to be dead, but honestly, what a joke it’s still working completely fine. They can't even patch a reverse-engineered community addon, so we’re just out here abusing it at fullest capacity anyway. Stability is never guaranteed…
The addon owner saw this and panicked, deleting his instance. WTF, it was fine 5 minutes ago , now its DEAD ☠️.
🤣17