Profile

Cover photo
Guillaume Lesniak
6,767 followers|4,540,885 views
AboutPostsPhotosYouTubeReviews

Stream

 
Find the cause of a glitch after 3 months of intense tracking: check. #achievementunlocked  
56
Max Weninger's profile photoAlex Cruz (Mazda)'s profile photoCorey M (EnemyofGLaDOS)'s profile photo
3 comments
 
💪👍🎉🎊🍻
Add a comment...
 
Android 5.1 rollout

I've started merging Android 5.1. I'm going to edit and update this post as the progress goes.

Update 1: Started merging a few repos. Merge result will appear in a new set of android-5.1 branches. Manifest is up.

Update 2: Halfway there! (fw/base, fw/native and fw/av excluded :P)

Update 3: Everything but fw/base merged! Almost there :)

Update 4: Merge is done, however it's not guaranteed to be building atm

Update 5: Build fixes are ready. Make sure you apply https://gerrit.omnirom.org/#/c/12501/ and you should be set!
49
2
Andrew Dodd's profile photoStephen Reddish's profile photoTamás Nagy's profile photoKevin Minions's profile photo
10 comments
 
fantastic news, synching atm. Where is best place to put feedback?
Add a comment...

Guillaume Lesniak

Shared publicly  - 
 
When I'm scrolling through my Google+ stream, and someone asks if Camera2 will be ported to the Galaxy S2 because "It's something ROM developers can easily do", and some random indian "coder" says "I will", I'm all like...
77
6
Alex Cruz (Mazda)'s profile photoRyan Cavitt (Kira)'s profile photoAlex Mendonca (Rektroid)'s profile photoCorey M (EnemyofGLaDOS)'s profile photo
18 comments
 
+Andrew Dodd When I see "Camera2", I immediately think "manual shutter time", which is supported in very few blob camera drivers. It's probably possible to wrap the current blob to proxy the Camera2 API calls, but you won't get much new features.
Add a comment...

Guillaume Lesniak

Feature Discussion  - 
 
Lollipop means security to us! :D
44
Max Weninger's profile photoYanuar Harry's profile photoGran PC's profile photoPrzemek Gedek's profile photo
4 comments
 
This is interesting, do explain the nature of this prompt.
Add a comment...
 
Testing Lollipop messenger... 
65
3
Shaunak Guharay's profile photoKowalski OmniROM's profile photoPraveen K's profile photoJaime López's profile photo
34 comments
 
Honestly didn't like it. I like hangouts more
Add a comment...
Have them in circles
6,767 people
Jean Roth's profile photo
Michael Stevens's profile photo
Russell Stewart's profile photo
Irfan Bakri's profile photo
Troy Miller's profile photo
Ludovic Clement's profile photo
Ahmed1 Baali's profile photo
Ashley Vercammen's profile photo
Matt Hallam's profile photo

Guillaume Lesniak

General Discussion  - 
 
And we're up! #5.1
70
2
Andrew Dodd's profile photoEric McGuire's profile photoCorey M (EnemyofGLaDOS)'s profile photoAlessandro Di Giacomantonio's profile photo
11 comments
 
I did read. Didn't know what Caf devices were until now, so now I know.
Add a comment...
 
Google: Hey, please use our new APIs in Lollipop, don't use the deprecated ones.
Me: Okay, let's do it.
Google: Awesome!
Me: Hey, but using this new API broke AVRCP metadata
Google: Oh right, we haven't updated the Bluetooth system yet, it's still using the old API.
Me: Then why use the new API?
Google: ...I'm feeling lucky.
78
3
Max Weninger's profile photoBhargz Shukla's profile photoKevin Minions's profile photoMarco Foggiato's profile photo
6 comments
 
Well - all I know is that I have all kind of weired issues even with a nearly unchanged bluedroid as we use in Omni
Add a comment...
 
I want to react to some of the comments on the XDA article about Google's QA on AOSP (read: http://www.xda-developers.com/android/google-aosp-qa-team-lollipop/), from a custom ROM developer point of view.

While custom ROMs users is a minority (though, a majority on XDA I suppose), a bad support of AOSP is a bad thing for all custom ROMs.
By "bad support", I mean both the lack of tests (resulting in crashes in AOSP apps), as well as the closing down of more and more previously AOSP apps (Calendar is now left out, along with Mms, Music, Browser, ...).

It has multiple implications:
- We're left with a broken system even before any kind of change the team might make, leaving you users unhappy because "it's unstable!!11!!".
- We cannot do ANY enhancement on top of Google's changes for the closed apps. If you want us to add a feature on the new Calendar app, we can't. If you want us to add a new feature on the new "Messenger" app, we can't.

That means even more work for us. We have to fix what's broken, and we have to either Reverse Engineer or re-code from the ground up new apps to replace Google Apps so that we can add new features to them.
This means one more thing:
- Our versions of the apps will clash against Google versions. They will make changes, we will make changes, but we will have to copy their changes (ie. RE or code them, once again) to keep things up-to-date, instead of just having to merge both repositories like we could do so far.

Ultimately, if every stock app is closed down, custom ROMs will become either just slightly changed stock AOSP running Google Apps, or will turn into OEM skins with all stock apps (can we still define what are stock apps?) replaced.

Don't get me wrong, I do use Google Apps and Google Services, and I'm not against having some Google-proprietary apps (Gmail, Drive, etc). But not updating MMS app in favor of Hangouts/Bugle, not updating Email app in favor of Gmail, not updating Calendar in favor of Google Calendar, not updating Music, Gallery, ... is more a bad thing than a good thing if you're using custom ROMs, because then you won't be tied to your OEM apps, but to Google apps. And if you don't like a particular aspect of an app, well, too bad.

This also opens up new opportunities of bringing open source alternative to proprietary apps (one of the things Omni is committed to), but re-doing all the base apps and updating them to match the design of the current Google-version of the apps is a gigantic task.
Sure, there are many alternatives already on the Play Store or other marketplaces, but IMHO people trying out custom ROMs expect an enhanced AOSP experience - ie. enhanced stock apps, not other apps.

We'll see how the music rolls.
Let's take a look at some of the fairly major bugs and inconsistencies in the latest AOSP 5.0 release of Android Lollipop.
143
19
Ron Amescua's profile photoAndreas Adam (AA1973)'s profile photoJoel Tomfohr's profile photoGabriel Luchijan's profile photo
31 comments
 
+Rushabh Kothari no. It's illegal to decompile their code and use it. Even gapps is a grey area.. This isn't a solution. 
Add a comment...
 
Lollipop Merge

Lollipop has arrived! We're already hard at work merging changes and bringing you your favorite new flavor of candy.
You can follow the progress here: https://docs.google.com/spreadsheets/d/1WzqI3qCuAbG9MYsN89rcbae_JT4_LM0YUvIx3y-Glro/edit#gid=0

Branch is android-5.0 in the repositories and will appear as they are merged. The code isn't guaranteed to be buildable/usable until we tell you so.

It is also worth noticing that once Lollipop will be usable to the point nightlies can start, Kitkat nightlies will either be stopped or switched to a weekly/monthly status.

Happy 4th November!
145
14
Luca Zaninello's profile photoStefan Mayrhofer's profile photoStefano Belli's profile photoSylvain CORTET's profile photo
35 comments
 
+Andrew Dodd many tanks man, yes, based on my experiences first usable build takes at least 2 weeks from the release of the images, so nothing on the orizons untile december ;)

Good work to anyone and thanks for Your work guys!
Add a comment...
 
#lollipop   #transitions  
Whenever I have an exit transition with the content being a little too big, I end up with this warning:
W/OpenGLRenderer﹕ Layer exceeds max. dimensions supported by the GPU (1080x5190, max=4096x4096)
causing then an IllegalArgumentException in nativePollOnce crashing my app and I can't do anything about it.
AFAIK this error didn't happen with the previous L Preview APIs.
+Android Developers 
1
Add a comment...
 
It's funny to see devices "24 bits / 48 KHz audio blahblah" - when OpenSL fails to create a 24 bits, 48 KHz context on those devices.

#Iwantfloatingpointaudiobackcompat   #didyousettle  
20
1
Kowalski OmniROM's profile photo
Add a comment...

Guillaume Lesniak

Shared publicly  - 
 
Guess it's time to look at other app stores. I don't want someone showing up at my doorstep just because I have one paid app that nobody buys on the Play Store. Heck, even Apple do better!
 
Google is now requiring app developers to add their physical address which will be shown on the app details page. This is a huge deal for indie app developers.

Just by having an email address on the app detail page I get spammed with about 20-40 emails a day (with filters). This week someone emailed me and threatened my life (he was crazy and thought I worked for the government and stole his information). Just think if he had my physical address and lived near by.

Yes, I could go get a P.O. box but can Google pay for it? They already take 30%. None of which has ever been used to advertise my apps. 

#rant   #google   #android   #androiddev  
59
3
Chad Cormier Roussel's profile photoTomasz Roszko's profile photoRoman Hošek's profile photoMichael Limb (something15525)'s profile photo
28 comments
 
I feel like a lot of developers will work at google's address
Add a comment...
People
Have them in circles
6,767 people
Jean Roth's profile photo
Michael Stevens's profile photo
Russell Stewart's profile photo
Irfan Bakri's profile photo
Troy Miller's profile photo
Ludovic Clement's profile photo
Ahmed1 Baali's profile photo
Ashley Vercammen's profile photo
Matt Hallam's profile photo
Links
Story
Tagline
Hey, is that a bird?
Bragging rights
Focal Camera app, OmniROM developer, legacy Team Hacksung Developer, 2ème place du concours Innov'Game 2010
J'y étais deux fois, malade deux fois. L'hygiène est très douteuse et la cuisine en général très industrielle.
Public - a year ago
reviewed a year ago
1 review
Map
Map
Map