Profile cover photo
Profile photo
Aaron “aaronpoweruser” Gascoigne
1,656 followers -
its me
its me

1,656 followers
About
Aaron's posts

Post has attachment
I made a thing.

I'm in Barcelona for #Mwc15... Come hang out with me for some drinks tonight! Ping me for details 

Post has attachment
Nexus 6

"shamu_defconfig: Remove ROW, set CFQ default

IO patterns seen with ROW IO scheduler can expose bugs in eMMC
firmware.  Avoid these by using CFQ scheduler."

Sure this is a proper fix

https://android.googlesource.com/kernel/msm/+/7c8728821feb440886a6afa4da511afcbfa345d3"

Post has shared content
Many are wondering why we implemented the cm theme engine instead implementing our own.

We opted for the cm theme engine to maintain compatibility with all the theme existing themes and to make the lives of androids wonderful designers easier. We are here to advanced android for the community not to fragment it.

P.S this is by far one of our most stable releases a lot of work went in to it and I'm truly proud of it.
4.4 BETA1

On this week’s dose of awesome sauce from PA Headquarters. We are proud to bring you Theme Engine, a stable Hover and a bunch of fixes. Hats off to CM, Clark Scheff, Andrew Mast and Sony mobile, for their work on Theme engine Truly outstanding work. Porting it to an AOSP base was a massive effort, lead by +Carlo Savignano. We tried to do it in a way so that it can be easily ported to other AOSP based ROMs for the benefit of the entire community. We are also proud to mark Hover stable, after many betas and three rewrites. We apologize for all the betas, but we really wanted to try to get this right, we encourage you to compare this build to beta 1, some major improvements have been made. The lessons learned here means more/quicker awesomeness in the future.

With Google IO only a month away we are nearing the end of Kitkat, but that doesn't mean development is slowing down. Our team is comprised of numerous students and with school ending we are now doubling down on making PA awesome, we plan to finish strong and have a few Major projects to release that we have been working on internally for quite some time. Awesomeness is coming :)  

P.S. This is still 4.4.2. We have merged and are testing 4.4.3 internally but it was released too close to our release to allow enough time for adequate testing. 

P.S 2 Like the Themes shown off in the image below they were made by our own +Matt Flaming  and  +Lo Huot  and are available on the play store (PiazzA will be available soon). Show them some love.

General
- Translated into over 30 languages!
- Backported numerous fixes from AOSP master.
- Improved quicksettings.
- Removed lockscreen blur feature in favour of custom lockscreen background from Theme Engine (it will come back as a component of theme engine in the future).

Theme Engine
- Bring full CM11 theme engine. (First AOSP based ROM!!)
- WARNING: Home button gets refreshed only after reboot or by force killing SystemUI  if you want to  a avoid reboot. Will be fixed in next build.

Hover
- Stable status!!
- Removed Jank (its a technical term)
- Fixed remaining bugs, including spam and invisible notifications.
- Fully working and improved inCallUi.
- Restored default swipe to dismiss behavior. An upcoming swipe up gesture will let you dismiss hover as was replacing the old behavior.

Pie/Immersive
- Fixed immersive API Thanks for the developers who helped diagnose the issue
- Vastly improved triggering, and allow you to trigger from any area on the edge on tablets.
- Pie now rotates like the navBar (will appear on short edge).
- Enabled pie only on immersive mode enabled by quick settings tlie (not in app immersive).
- Fixed AOSP immersive bug issue where apps would register a touch when swiping statusBar and/or navBar.
- Fixed numerous freezes.

WARNING: We recommend a clean flash this time due to massive changes

Builds: http://paranoidandroid.co/roms

Bugs: https://paranoidandroid.atlassian.net

Kraken Icon Pack: https://play.google.com/store/apps/details?id=com.jmftech.kraken.icons

#StayParanoid  
Photo

Post has attachment
This release has me all. #stayparanoid  
Animated Photo

Post has shared content
Nice to see people take notice 
Initial thoughts on Hover:
If you actually had the epiphany from the release of Hover that I did then quit reading now, if now... continue, please continue:


As a Google Fanboy, as a Android Geek, as a CrackFlasher, I am always looking for the abundance of features. If not to show off to my friends but, out of curiosity for what the future actually holds as software and hardware merge into something incredibly useful; in my hands, on my wrist or strapped to my head like Giordi Laforge's visor - I am sincerely in love with concepts that float around the topic of futurism.

Google's Ceo has said numerous times that he believes technology should show up in life when you need it, and then vanish out of the way when you are done with it. Google's Googliness shines bright in this way throughout their UI/UX in all their projects and today, the Paranoid Android Team have done the same. 

The previous Halo feature has been enhanced in a way that requires less thumb-work. No more chat-head like bubble to swipe on and off the screen clumsily. This feature has been so polarizing, the halo-haters, the lovers and, the indifferent. 

Hover is a landmark for the PA Team
Though the previous builds have expressed their desire to not only focus on cramming features into a ROM, they also realize the importance of negative space; whats left out is just as important.

Hover allows the user to see and take action on a notification like Halo but, in a way that keeps the mess and frustration out of it. There is no selling the idea to your wife or friend anymore... Now FLOATING ALL THE NOTIFICATIONS above your primary task at hand is simple. No ninja-mode, no bubble with a mind of its own. NO MORE LEARNING CURVE. 

IT JUST WORKS, INTUITIVELY.

My applause to you +Paranoid Android 
Animated Photo

Post has shared content
I completely agree Qualcomm and thus arm is the incumbent in the mobile world. An OEM isn't going to want to have to go through the cost of switching architectures. 
"It is not enough for Intel to offer an Atom chip that merely breaks even with Snapdragon — it must blow Qualcomm completely out of the water."

THIS

I have gotten into several heated discussions here on G+ about Qualcomm vs. <whoever> and I pretty much universally side with Qualcomm.  Whoever I am debating with always likes to throw out 'but what about X' and back it up with some stats from somewhere.  'But the Exynos Octa (barely) out benchmarks the comparable Snapdragon.'  'But the Intel chip is going to node-drop faster.'  'But Marvel is building their own integrated baseband chips now too.'

It's not that the naysayers' points don't have merit.  It's that none of those points matter in the least.  Qualcomm is the dominant player in the SoC market right now.  Supplanting that does not require building a product that can evenly compete with a Snapdragon chip or even one that can narrowly outperform that Snapdragon chip.  It requires building a product that destroys the Snapdragon on multiple fronts.  And nobody can do that right now.

On that front, people like to talk about what these other companies will be doing soon.  But that is really not good enough either.  The fact that Samsung or Intel plans to release a product 6-months from now that actually can significantly outmatch the Snapdragon chips that are in devices right now is only relevant if you assume that Qualcomm has no plans to continue innovating in the future.  Obviously that is not going to happen.

And the biggest problem at this point is not just the ability to produce a product that is better performing than a Snapdragon.  I mean, that has proven to be a problem in that nobody can do so, but even if they could, the bigger problem is simple inertia.  If you want a smartphone OEM to chose your SoC instead of Qualcomm's, not only do you need yours to outperform the Snapdragon in every way, but you need to have it do so by such a margin as to make it worth the OEM's time (and money) to throw away their institutional knowledge of integrating their devices with Snapdragon chips and start from scratch with your new product.  And no company can come even remotely close to that bar right now.

Post has attachment
When I see a new android studio update and think its a good idea to update and all the gradle files in my mult-library project decide they don't like the idea.   #pixelpushing  
Animated Photo

Post has attachment
How I feel trying to code right now 

#pixelpushing  
Animated Photo

Post has shared content
A view from the other side. All roms should be working at this level. We are at the point were roms are not for the power user. We are establishing identities. We are on the verge of another computing revolution.

We have our Microsoft, who will be our apple? 
This week I decided to try something new. I went to the +CyanogenMod offices in Seattle and spent some time with the Oppo N1 CM Edition, and learned about the development and support process from the guys who have been working on it. 

Even if you're not interested in the N1 as your personal phone, I think you should take a look at what these guys are doing because they are not slowing down even a little bit after this is officially released. 
Wait while more posts are being loaded