Profile cover photo
Profile photo
Björn Lundén (blunden)
722 followers
722 followers
About
Posts

Post has attachment
Do Not Disturb Sync for Wear

In an attempt to "fix" the Do Not Disturb behaviour in Android Wear 2.0, I built an app that brings back the AW 1.5 style syncing of the Do Not Disturb state.

It shouldn't affect battery life noticably since it doesn't run anything in the background except when sending the state change.
Add a comment...

Post has attachment
This community will not be renamed

I know people were wondering this and I have just gotten confirmation that this community won't become an official LineageOS community and therefore won't be renamed.

Thank you for all the participation and feel free to communicate with us on
https://www.reddit.com/r/LineageOS/ or other official channels.

Post has attachment
WD Purple™ - Now with backdoored firmware preinstalled!


Photo
Add a comment...

Post has attachment
I felt like trying the new Shazam Lite app out so I modified it to bypass the region restriction. Basically it always reports the user to be from India which is enough to complete the setup process.

http://www.mediafire.com/file/scdp0tn5z5tt3r8/com.shazam.android.lite_1.0.0-161005-100005_no-region-restriction.apk

If people would prefer to use the official apk they can instead use an intercepting proxy to modify the login-request sent to the shazam servers. The parameters to modify should be fairly obvious. That should allow you to use it until they force the app to login again. The modified app has no such restrictions of course.
Add a comment...

Post has attachment

Post has attachment
Damn it! Now I have to wait until December. :(

On the other hand, it looks great.

https://www.youtube.com/watch?v=Wji-BZ0oCwg
Add a comment...

Post has shared content
Add a comment...

Post has attachment
Add a comment...

Having seen Star Wars: The Force Awakens I can now rejoin the internet, knowing that I'm basically impervious to spoilers.

Yesterday I was basically living in internet "radio silence".
Add a comment...

Post has shared content
We've said this many times before but it bears repeating.
Upgrading CyanogenMod versions

This is something that drives me absolutely nuts. People run around telling users that they should be wiping data between rom upgrades. I'm not talking about between nightlies, although I've even seen that recommended before which is insane, but between major version upgrades. There is no reason you should have to wipe your data when going from cm-12.1 to cm-13.0. Database migrations are built in to the rom. It handles the upgrade for you. People like +Adnan Begovic spend a bunch of time making sure this sort of stuff works.

99% of the time if someone is having issues after a major release upgrade, its because they didn't flash an updated gapps package along with the rom (not something CM really has any control over) or they went backwards (cm-13.0->cm12.1 for example) as migrations don't handle a downgrade.

On several occasions I've seen +Abhisek Devkota mention that if we do something that forces a user to wipe their data, we've done something wrong. That couldn't be more true.

Now, if you're lucky enough, you may be able to get your hands on an early unofficial build of cm 13 for your device. These most likely will require a wipe at this time, as the database migrations are still in development. But by the time official nightlies start, they will be working.

This is on par with the "wipe your data 3 times in recovery to make sure you get it all" rumor.

tl;dr You don't need to wipe your data when you upgrade to an official cm-13.0 build and anyone that tells you different is misinformed, ignorant or just plain lying to you.
Add a comment...
Wait while more posts are being loaded