Affichage des articles dont le libellé est picking. Afficher tous les articles
Affichage des articles dont le libellé est picking. Afficher tous les articles

dimanche 21 décembre 2014

Help Picking A Highly Protective Case topic






I currently own the S5 G900F with the Official S-View Cover, due to the case becoming unpleasantly dirty (White to black) and the realization that the phone might not last me very long with this level of protection, Im in the search for a new case.

I need this case to be a bull coverage case, which means that it will have to have a inbuilt screen protector, for I can not apply one to save my life. It must also be as compact as possible, while offering great levels of protection, as I have small hands.

Cases I have been looking at are the Otterbox Defender Series (S5), and the i-Blason ArmourBox

OtterBox - My concerns about this case, is the 'Echo' that certain members of the community suffer, although someone has 'found a cure' for this, which is to find and peel away hidden stickers inside the case, I am not sure, as I have only heard of it once. This is a very popular case and seams to offer the most protection. It also adds quite some size to the phone, which may become annoying.

i-Blason - This is not a very popular case, but seams to be thinner and smaller than the OtterBox. It is cheaper, but price does not really matter as both cases are competitively price in the UK. It seams to offer good protection.

One of my biggest worries with both cases is the functionality of the FingerPrint Unlock, this is something I use and take pride of on my mobile, and would hate to have to use it, would these cases allow for the use?

Secondly, the inbuilt screen protectors, is there any 'give' as in, does it feel like you are not touching the screen?

Any opinions and suggestions would be greatly appreciated, thanks






samedi 13 décembre 2014

[GUIDE][CM12] Compiling CM12 for Moto G and cherry picking features. topic






Here's a little something for the guys (and flashaholics) who don't like to wait for devs to release new CM12 builds.

AFAIK ROMS CAN'T BE COMPILED ON 32 BIT SYSTEMS. ONLY 64 BIT.

We start with setting up the build environment:
First, start with installing this:

Code:


sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

Once that is done, we go about installing JDK-7 since that's the one that works for lollipop :p


Code:


sudo apt-get install openjdk-7-jdk

Then we install the Android SDK for some useful stuff:


Code:


sudo apt-get install android androidsdk-uiautomatorviewer android-copyright android-src-vendor android-emulator android-tools-adb android-headers android-tools-adbd androidsdk-ddms  android-tools-fastboot androidsdk-hierarchyviewer android-tools-fsutils androidsdk-traceview

Once all that is dealt with, we can move on to the repo tool. That's what will get your CM repos syncing:


Code:


mkdir -p ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo


and then, reboot to apply the changes.

Now for the interesting part
Not really, actually.

Time to yank the CM source code.

Create a working directory where you're going to sync all the sources and do the dirty stuff.
For this guide, we'll call the working directory "cm12"

Create the directory by running

Code:


mkdir cm12

enter your working directory by typing

Code:


cd cm12

Inititialize the repo by throwing in:


Code:


repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0

Wait for all the activity in the terminal to cease. And then type in:


Code:


repo sync

while the stuff is downloading, grab a ginger ale, or a cup of coffee and admire your handiwork. If you're the impatient type, find a generous dose of your favourite sedative, and knock yourself out for a few hours. When you're up again, you'll be faced with one of two things. Either your repos have synced successfully (yay!), or you get some nasty fetch errors. If it's the latter, then, Voila! You've just faced your first ever compiling frustration. Take some time out and break a few things, drive the neighbours crazy and then return to the PC and knock in:


Code:


repo sync -j1

This should (hopefully) work perfectly as long as you have an internet connection worth paying for. If not, then compiling probably isn't for you anyway.

Once all the repos have been synced, you need the device specific sh*t. To do that, run:


Code:


. build/envsetup.sh && breakfast falcon

It will create the falcon local manifest. Once all the stuff has been downloaded, and the terminal returns to normal, you still have one more modification to make. You need the proprietary stuffs.

Go to the working directory, and press ctrl+h this should reveal the secret land of the .repo folder.

Double click on the folder, and you will find more folders. Go to the one named local_manifests and you'll find something called "roomservice.xml" right click on it and open it with gedit.

There, right at the bottom, before the <manifest/> past this in:


Code:


  <project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" />

save the file and return to the terminal.

run another repo sync and then get the prebuilts by typing in:

Code:


repo sync
cd vendor/cm
./get-prebuilts


Then cd back to your working directory

Code:


cd ~/cm12

YOU'RE READY TO ROLL!

Finally, to build, type in:


Code:



. build/envsetup.sh && brunch falcon


If you have a really powerful PC, then use:


Code:


. build/envsetup.sh && brunch cm_falcon-userdebug -j8

And if you have a really really powerful PC, then use:

Code:


. build/envsetup.sh && brunch cm_falcon-userdebug -j16

Wait for the build to compile. Usually takes about 2-3 hours on an okay PC. You'll find your completed build in cm12/out/target/product/falcon.

The next time you want to build, run:


Code:


make clean
repo sync
. build/envsetup.sh
brunch falcon
.. and so on.


Happy Building!






 

© 2013 Mobile Probleme. All rights resevered. Designed by Templateism

Back To Top