Skip to main content

Galaxy Tab 2 7.0" P3100 upgrade from 4.0.4 to Jellybean 4.2.2 with CyanogenMod 10.1 M3

After reading some reviews, I decided to brave the rooting experience and upgrade my shiny new Tab 2 to Android 4.2.2 using the instructions on the CyanogenMod wiki.

While it was fairly straight forward, I did run into a couple of snags namely;

  1. The Download Mode initiation for the P3100 is incorrect. Hold the Volume Down and Power Button simultaneously.
  2. The Recovery Mode button sequence was not identified. Hold down the Volume Up and Power Button simultaneously.
  3. As the P3100 has an External SD Card slot, this is the easiest way to get the new CyanogenMod firmware onto your device. It also avoids the need for the Android SDK and getting your head around sending command line instructions which were not spelled out in the guide. I'd also had no previous experience with the Android Debug Bridge (adb) mentioned in the Wiki.
  4. After copying the CyanogenMod firmware and Google Apps package to the SD card, koush's ClockworkMod Recovery software could not find any files on the card. I navigated through the extensive menu using the Volume Up and Down buttons with Power button to enter and unmounted the External SD card and then mounted it again. The zip files were now visible.
The upgrade is absolutely fantastic and I can't believe how much better 4.2.2 is over 4.0.4. The only thing I'm missing is the Clipboard history paste function that was in my stock 4.0.4 firmware and I haven't found a clipboard manager that allows me to access the clipboard history when using the paste feature yet.

Other than that, the cm-10.1-20130411-EXPERIMENTAL-p3100-M3 seems extremely stable and fast and has given my Tab 2 a whole new life. Well worth the upgrade!

P.S I had problems with very high battery drain with Exchange services under 4.0.4 which drove me to despair and after not finding a solution online, I was keen to see if it was related to the actual Android firmware. Seems it was as my Exchange services battery drain has gone from 60~86% (yes, 86%!) to <5% when syncing and nothing when the Exchange mail is idle!

Labels:

Comments

Post a Comment

Popular posts from this blog

Using ESPEasy with Home Assistant via MQTT

Preface: I've just started playing around with Home Assistant on a Raspberry Pi and exploring the world of MQTT to control devices on the network. Learning curve is a bit steep but worth the effort as MQTT is very fast. The hardware and software tools I'm using are as follows: 2 x Sonoff relay units 2 x NodeMCU Boards ESPEasy firmware (must be version 121 or above as that contains the MQTT 'retain' flag option. Home Assistant software on Raspberry Pi2 MQTT Test Software: PC: MQTT.fx Android: MQTT Dashboard
17 comments
Read more

My Notepad++ tricks when editing YAML files in Home Assistant

To comment out a whole section in one go: Highlight the text you want to comment out and use CTRL + Q. If you do this at the start of a line, it will only comment that line. CTRL + Q is toggle mode (comment on/off). CTRL + K will allow you to add multiple comments one after the other.
2 comments
Read more

How to check what entities are filling up your Home Assistant database

If you use the Home Assistant MariaDB add-on, this tip will show you how to query the database so see what Home Assistant entity states are triggering the most, filling up your database. What were going to do: Install the phMyAdmin add-on for MariaDB. Query the MariaDB database. See what entity state changes have the most action. Paste the code below into the SQL query box:  select entity_id,count( * ) from states group by entity_id order by count ( * ) desc; And if you're using the internal home-assistant_v2.db instead, you can use the SQLite Web add-on to achieve the same thing.
Post a Comment
Read more