Home Artists Posts Import Register

Content

Back to the "old" release schedule!

With the last newsletter I've announced that CleanROM will be seeing a bunch of new features as part of a bigger feature update sometime in the future.

The original plan was to bundle all of said planned features into one big release and thus cut down on consecutive releases as much as possible to save you guys time you'd otherwise spend repeatedly installing smaller updates as they get released.

I gave this approach a long hard thought this weekend.

It was a long (overtime-heavy) week. So far I haven't had a single hour to myself yet, and it made me wonder... if time is such a rare commodity for me, just how long would it take me to reliable deliver such a "big" feature update next to my regular job and daily life?

And most importantly, what are you, my patrons, to gain from me stacking and delaying updates in such a way?

After I started thinking about it this way I quickly realized that my original way of doing things around here yielded way more benefits.

By getting newly implemented features out of the door as soon as they pass internal testing not only gives you, my community, access to it, but it will also give me faster user feedback which can then be put to use in future updates.

As such, I'll be going back to my regular "get it out once its done" release schedule.

Now that this is out of the way, let me explain what the new "A2DP keep alive" feature can do for you.

A2DP KeepAlive

If you are anything like me, then you have cut the wire in pretty much everything tech, including headphones & speakers.

As such, I've been through countless Bluetooth headsets, earphones and speakers, trying to find my personal favorite in each category.

There's something for everyone here, these devices come in all sizes (and prices) and all do pretty much the same thing. They beam sound from your device's into your ear.

But sometimes OEM-implemented power-saving functions can interfere with this.

If you've ever experienced awkward pauses in your audio during silent segments of a movie or a device fully disconnected on you after prolonged periods of silence then this feature might be for you.

When this feature is enabled, it will keep the Bluetooth transport open by injecting a small silent audio sample into the stream periodically, essentially circumventing all of the aforementioned power-saving related audio issues.

Downloads

Files

Comments

Anonymous

Definitely better idea, we'd be waiting months for a cumulative patch, seeing as you work alone on this plus there are these things like life and responsibilities, I wish we all could do without those.

Anonymous

Great! Thank you so much!

Anonymous

Nice - THX!

Anonymous

I dont know if it was the recent firmware update or the recent Dolphin update but Vulcan does not work on GPD XD Plus again and had to revert back to open GL for it unfortunetly.

blackseraph

The graphics stack hasn't been touched in forever. I'd be surprised to see a regression without any actual changes that could cause it. I'll look into it though once I have some time at hand.

Anonymous

Well I had revearted back to the previous cleanrom from last month and it isn't the clean rom that's making vulcan not work on Dolphin for us. So they had to have had done some changes themselves and once again GPD XD Plus owners are back openGL. :(

blackseraph

I can only take a look at stuff on the weekend, so I haven't had the chance to debug this yet, but I will.

Anonymous

Hello! I cant even play dolphin un this versión. After playing for 1 minute the gpd just freeze and i need to rebbot the system

Anonymous

Apartently, there is a problem with the latests dolphin versions. It doesnt seems tl work on any versión of the ROM

Anonymous

This A2DP thing seems very broken. I get a lot of spam in the Android logcat logs that says it's trying to invoke things on a null object about the media player. It also breaks games that use Unity game engine. Had to turn off the "fix" for it to restore sound.

blackseraph

I might have to pin the BG service via a framework exclusion. Is there anything else to the log? A stack trace maybe?