Mastodon IzzyOnDroid


Say thanks!
↓ Your product here? ↓
Das Inoffizielle Android-HandbuchAndroid kennenlernen, Tipps & TricksDas Inoffizielle Android-Handbuch
Android kennenlernen, Tipps & Tricks
Buy at Amazon for EUR 16,99
Das Inoffizielle Android SystemhandbuchTiefer ins System einsteigenDas Inoffizielle Android Systemhandbuch
Tiefer ins System einsteigen
Buy at Amazon for EUR 7,00
Die besten Android-AppsDen Androiden austattenDie besten Android-Apps
Den Androiden austatten
Buy at Amazon for EUR 5,00
 
dehelp

Android without Google 6: Self-Experiment

It’s certainly a nice thing to write a tutorial for others – but I also did that for myself. And now that all facts seem to be together, it was time to put the theory into deeds: a self-experiment. I followed my own advice, and freed my first Droid. A second one is awaiting its freedom once I’m done with the first1. As I did with my tutorial, I will also share my experiences with you. And while I usually “publish” posts only when they’re finished, this one will be an exception: From time to time I will update it with „new findings“.

Btw: Being in the middle of my self experiment, it was nice to see I’m not the only one  :D

Android without Google:

Started before this series, but clearly belonging here:

Installation

MapsApi
MapsApi working

This went as described in Android without Google 5: Free your Droid! (and Android without Google 2: ownCloud). Like I already indicated with the NOGAPPS instruction, there was a little trouble flashing the MapsApi, which just gave me an E:Error in /sdcard/Update/mapsapi.flashable.zip (Status 0) Installation aborted. The described “manual alternative” however worked fine: maps are shown in apps accessing it, tested e.g. with RF Signal Tracker (see screenshot to the right).

But though no errors were indicated on install, NetworkLocation based on OpenCellID seems not to work2: apps either say they won’t work without GPS, or claim an “unsupported location service”. I’ve posted that to the NOGAPPS thread at XDA, but no solution so far. Still hoping for the dev to turn up with some ideas. There seem to be a few alternative projects on this, though – but they all require Android 4.1 or 4.2 and higher, while the little Wildfire is running 4.0.

Baseline I

Battery Rundown
Battery Rundown: 25h+

Following the mostly successfull install, I ran a first „initial baseline“:

Comparing with my other two devices: the Milestone² (comparable configuration but with SIM) went to the charger daily with ~75% battery left, my LG Optimus 4X with ~50% (the latter had even to be charged twice on the third day, as something3 was going mad again, draining the battery to 30% in just 5 hours. Though charged up to 96% after this, the device was down to 50% again in the evening).

Interim

Following the first baseline, a little testing and analysis:

Baseline II

Battery Rundown
Battery Rundown: 4,5d+

Now for the „real-life baseline“ (using a SIM of the provider „Base“ even  :D ) – put in the SIM, switch off mobile data (as that SIM has no data plan associated). Now the battery usage should be well comparable with that of my Motorola Milestone 2, which is configured the same way (SIM, no data) – but has the full load of Google bloat installed. Thrilling. My expectation: Instead of ending up with 75% at bedtime (like the Milestone), it will have 90% battery left.

Only 10 hours later it seems my expectations are more than met: Milestone at ~85%, Wildfire still ~99% (and the LG Optimus 4X already down to ~80%). Screen-On times of Wildfire and Milestone are pretty much comparable: the latter runs my work-time recorder, the former mainly the calendar (but today I also ran some location tests on it, so it was even „busier“). Altogether, estimated Screen-On time per device ~30min (LG ~1h).

Rundown without charging: 97% - 75% - 55% - 35% - 5% Had to put it to the charger before five days were full this time. Remember the times a phones battery lasted two weeks?

Preliminary results

Additional install recommendations

So apart from the „basic installation“ described in parts 2 and 5, are there any recommendations on what might be generally required on the device? That very much depends on what ships with the ROM used. Moreover, your mileage might vary from mine. But yes, there are some things Id recommend. Simply skip areas irrelevant to you ;)

You might also wish to take a look at part 4 of this series for other recommendations. As it’s not really fun testing apps on the small 240x320px screen of the Wildfire (how did I stand that back then?), you will forgive me not going to full length with it here. I might check some more once the Milestone 2 gets its time ;)


Battery Rundown
Battery Rundown: 17d+

Update 2014-11:

Baseline III

Just to be able to provide you some „shocking facts”, I’ve left the device in flight-mode – not using it more than once a day to check the battery stats. For results of this experiment, take a look at the corresponding screenshot to the right, giving proof to the fact that an Android phone indeed can run not only for more than two days, but even for more than two weeks without being charged  :D

Real-life test

And so it came to pass that my main device, being the only one left running with Google Apps, had to be sent to service due to several hardware-related issues. To be able to communicate, I had to switch over to one of my backups. My choice fell on the Motorola Milestone 2 (aka „Droid 2“), which I meanwhile also had „freed from Google“: I’d flashed it with CM10 (Android 4.1) and installed the NOGAPPS components as described in part 5 (of course using a different image file in #4; while I again had to install MapsAPI „manually“, this time all components seem to be working fine). Following that (and preceding the factory-reset of the device-to-be-repaired) I used Adebar to back-up the latter, then transferred all the apps I’ve used to the Milestone-2. So basically, the Milestone² now has all the apps I’ve had installed before on the LG Optimus 4X5, minus the GAPPS, plus the NOGAPPS.

Battery Rundown
Battery at the last third of a normal day

That was a week ago. Since then, the Milestone² was to be my „main device“. So how did I survive that „first week“? I have to admit, I’m only missing little:

Temporary conclusion

Except for things requiring Cloud Messaging (in my case, Stack Exchange notifications), I didn’t find anything missing (YMMV). Everything seems to run smoothly, and all functionality needed was given – including markets, location, and maps.


Battery Rundown
Battery Rundown: 6d+

Update 2014-11-18:

Final words

Now Im running this self-experiment for more than two months. And during the past two-and-a-half weeks, I had to absolve a real-life test – as my only device left with Google apps on had to be sent to service. Time to finalize this report.

It were two devices with two purposes during this „final run“: The Wildfire served as „secondary“, for personal use. About 3-5 phone calls a day, plus one app Im currently testing (an "electronic worksheet", so not too much time spent on). No mobile data, so Id locked it down to GSM (aka „2G“). Like back in the old dumb-phone times, battery made it throughout the entire week, though I had WiFi permanently turned on. See screenshot to the right for „detailed stats“.

The other one was the Milestone, used for „business“: Mobile data on, let the device chose whether 2G or 3G. Mixed number of calls, another work-punch-clock (my main one), lots of reading (RSS Feeds, Twitter), Mail checking. Went to its dock each night with more than 70% juice left. Still missing my Stack Exchange notifications, but not much more.

Now, my Optimus has returned from service. So what will I do? Free it as well? Every thing has its time: I will first check how it behaves with the updates applied. And I need some device to „check against“ – plus, as Android book author, must be able to „check things Google”. So probably not that soon. But eventually, that might happen: My over-all experiences were pretty encouraging.

For you who reads this: As I wrote above, YMMV. But maybe you will decide to free some device(s) and, like me, keep one in „temporary slavery“. Until the last gaps might be closed (like GCM in my case). Or you don’t need any of the missing things, and straightly go ahead. Whatever your choice: I hope my articles here proved helpful!

appsprivacyreview


  1. The second one already has followed suit and, while my Optimus P880 is away for service, acting as my „temporary main-device” – see the real-life test↩︎

  2. This seems either to be specific to the device, or to the Android version: No such issues on the Milestone 2 running 4.1 (CM10). ↩︎

  3. Initially I suspected Google Services being the culprit, but meanwhile I’m not that sure it’s always them. The O4X seems to have a serious baseband issue (showing up in other places as well), so it might also be connected to that – which is why it’s currently sent-in for service. ↩︎

  4. As with the CellID-stuff, this again seems to be device or ROM specific: no such issue on the Milestone². ↩︎

  5. With a few exceptions of apps I’d once tried but stopped using. ↩︎

  6. Turned out it seems to heavily rely on Google Services – so on the "Google-free device" it does nothing but listing your installed apps and when you’ve updated them last – no changelog details, no update notifications. I’ve contacted the dev in the hope for a fix. ↩︎

  7. Though I still wonder about Phone Idle and Cell Standby being at positions 2 and 3 with around 20% each. Something strange specific to my carrier? One statement by LG Support might suggest as much, as changes in the routers of that carrier a few months ago also triggered their baseband-big-trouble on their P880 and P990 devices. ↩︎

2014-09-07 (2014-11-18)