[ROM/A1/Recovery][Wifi+3G+TMobile][4.4.4/2.8][Oct 27]Omni Based Rom and TWRP

Summarized Standard Disclaimer: use at your own risk. I use it at mine.
*Full wipe recommended if coming from another kitkat rom*
MAKE SURE TO HAVE A BROWSER APK. THERE IS NO MORE STOCK BROWSER. For firefox see below.

My personal build "Diamond Rom 4.4" is based on omnirom with the following additions:

• CM Calculator (the newly redone one they're proud of)
• CM File Manager
• CM Wallpapers
• Bash shell
• Nano text editor
• Powertop
• Koush's full featured open source superuser (and it's INTEGRATED into settings :cyclops: )
• Carbon rom blue balls wallpaper
• Cyanogenmod port of 2 column settings adapted to Omni rom.
• Omni floating window

I've added a few of my personal touches which include

• Batter circle color changing: green 100%-51% yellow 50%-16% red 15%-0% This was my favorite I9000M framework-res mod that I've missed since switching to CM7.2 way back.
• Killed lock screen music full screen (personal privacy thing when riding public transportation)
• Disable android external storage management: messes with ext4 formatted hard drives or multi partitioned hard drives. Use the unix style mount command
• Disable hardware keyboard on boot: disabled but not removed. You'll have to manually turn it on
• Removed camera sounds
• Disable SELinux at the kernel level. It's even disabled on my laptop/desktop at the kernel because it seems like it's more trouble than it's worth.
• Put the dalvik cache in the cache partition. Don't waste the data partition for it. :cyclops:
• And of course, comes bundled with my A1 kernel :cyclops:

Every thing I've tested: camera, youtube hd, sound, gps, usb otg(use manual mount command) etc work.

*Instructions*
First time flashing omni:
-Read second post FAQ and other important information.
-Flash TWRP (you can flash twrp over cwm from cwm if you're in that situation)
-Reboot into new recovery
-Make recovery backup (optional)
-Run Titanium Backup (highly recommended)
-Full wipe
-Format system partition
-Install ROM
-Install gapps
-Reboot :cyclops:

Subsequent flashes:
-Install ROM

Downloads
Mediafire Wifi download folder with md5sum file
Mediafire 3G download folder with md5sum file
Mediafire TMobile download folder with md5sum file
*Authorization to download is just a captcha. Simply enter the text in the picture or name the item being advertised in the picture.* Mediafire sure beats sh***y sites like uploaded.net or rapidgator

A1 Kernel (as its own download)
V1.9.2: Security fix made aware by cyanogenmod, specifically this. The commit message on my github has a copy and paste mistake. It should list both of those security flaws as patched instead of the same one twice. Oops :cyclops: Security fix comes with ALL roms June 28 and onwards.
3G/Wifi 6ff199d6c9037d222a70ec0c561c8028
TMobile a675fd353ad3ad7dbf8e6bf2109fa360

TWRP Recovery
2.7.1.0 Wifi 6c995325e749e7561893e398847b09a0
2.7.1.0 3G 8fa04be69d0faf3d9a134e829ddff680
2.7.1.0 Wifi July 8 a8d12c13aac7430a319369069d814e72
2.7.1.0 3G July 8 dc1c50622c29c621f29b95f4c53734ea
2.7.1.0 Wifi August 11 b2c21e8fd58dc38a9c8b7669031b84b1
2.7.1.0 3G August 11 9f48defe78391e63a9053cbd281f738f
2.7.1.0 TMobile August 11 87fb29c803a2e3a56d98a1475c5fce8f
2.8.0.0 Wifi cfdac70d0ccac34cf220887eab72f8b0
2.8.0.0 3G d7918eb397f54c484e04a6d5cb07945c
2.8.0.0 TMobile aaf7c6d2455ca32178ec846f5186c774

Newer versions of firefox explicitly disable flash on tegra2. Use my firefox mod which is just normal firefox with a hacked tegra2 blacklisting mechanism. Don't use the old firefox apk. It has unpatched security holes.

Changelog: omnirom gerrit

Sources: https://github.com/AAccount?tab=repositories Has my device trees as well as all the omni repos I forked with my additions.

Credits:
Kasper_h: helping to make 4.4 possible
pershoot: original device tree from CM10.1
Omni team: providing great starter rom and keeping it TF101 compatible
fred6681: original gapps package. I just removed the 4.4.2 check
Cyanogenmod team: rom extras like calculator, superuser, to fill in Omni's missing holes and 2 panel settings template.

XDA:DevDB Information
Omnirom+ 4.4 for Galaxy Tab 10.1, ROM for the Samsung Galaxy Tab 10.1

Contributors
AAccount
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
Based On: Omni

Version Information
Status: Stable

Created 2014-10-12
Last Updated 2014-10-11

Known Issues:

• Wifi signal indicator and speed indicator don't show up
• No list of 3G APN. Write down your settings first
• Bluetooth audio issues
• Recovery adb doesn't start automatically. In recovery, go to Advanced --> ADB Sideload and start it. You can then cancel it if you don't want to use that. It just starts the recovery adb and will continue to run until you reboot. fixed thanks to twa_priv
• Use another recovery for TMobile. Apparently the twrps I make can't boot on TMobile hardware even though it boots on my Wifi only.

FAQ

• How do I get multi window: Settings-->(second) More --> App circle bar (check box) && --> Included apps (choose what you want available in multi window)
• Yes you can flash TWRP over CWM
• Random flickering: Try Settings-->Developer options -->Disable HW Overlays.
• Can't install a very large quantity of apps: fix
• Can't mount ext4 media: kill the e2fsck process assuming you safely removed the media before sticking into the tablet.

(Below this is optional)
(Android device manager does have legitimate uses. However, please read and consider the following paranoid but realistic fantasy:)
Completely disable android device manager: By only going to Settings->Security->Device administrators and un checking "Android Device Manager" this doesn't completely remove the ability for google to send in commands to your device. Go to the google play store through a web browser, choose android device manager, and try "ringing" your device. To my horror, my tablet started to ring as if it got a phone call. I don't find it acceptable that gapps gives google a way to setup a remote command and control operation. In any other operating system this is considered a back door or virus.

To close this back door install Xprivacy. Enable system apps to be modified. Look for the entry (should be highlghted in red to indicate a system app) "Google Account Manager, Google Backup Transport... (lots of items here) ...Google Services Framework". Check mark Notifications and open its menu. Check mark the items in red. These are cloud to device (c2d) permissions which do exactly what you think. While not necessary, disable identification too for good measure. This disabled the ring feature on my tablet which means android device manager should no longer be able to send in commands. I don't have the guts to try the device wipe feature but it should work too. Do not disable location otherwise google maps won't be able to find you which means no gps car navigation.

See this post about building from source. I use a different, simpler trick for prebuilt chromium binaries. Fear not, they are source built but only when there are real source changes. They're just recycled in between to save 90mins/build of time.

What graphical glitches do you mean? I think ever since omni fixed the screenshot way back most graphical bugs have been ironed out. By youtube hd do you mean it doesn't play or can be laggy? If you mean laggy I read on wikipedia the GPU video decoding on the tegra2 sucks. That's a hardware problem.

3G build and new recovery coming later today. I cheated the chrome renderer build process by copying all the freshly done ones from the wifi only output folder.

My github is now fully up to date with all the appropriate omni repos forked with my personal touches whether it be the audio blob fixes or little things I like.

Sent from my GT-P7510

lancem71 said:

What are the flashing instructions? Is there a preferred gapps package?

Sent from my GT-P7510 using Tapatalk

Click to expand...

Click to collapse

I added instructions. There's no really preferred gapps package. I just like that one because it's the smallest one that gets the job done. There are some gapps packages that are bigger than the rom which I consider bloated.

mistersixt said:

With all ROMs starting with 4.3 it looks like if a flash of lightning goes from one corner to the other (my wife is saying it looks more like a scratch) for maybe 100 ms, this happens quite constantly though, every minute or something. Also, in some games like flappy bird the application gets stuck for maybe 100 to 200 ms completely (every 5 to 10 seconds maybe) before it continues, this makes playing games unpossible (temple run is another good example).

With 10.2/SGT7 this does not happen ... for whatever reason.

Regards, mistersixt.

Click to expand...

Click to collapse

I get these randomly sometimes but not often enough that I would consider it an issue. In angry birds it's an issue but if you go to Settings-->Developer Options check mark "Force GPU rendering" and "Disable HW overlays". Then you can play angry birds at least without the lightning.

And now for an important question
I have a script that puts /data/dalvik-cache on /cache/dalvik-cache as it was way back in android 2.2 froyo. Even though our tablet shipped with android 3.0 and my I9300 S3 shipped with android 4.0, Samsung seems to have been very sloppy and left the /cache partition huge to accomodate the froyo standard. This is a waste of space that will never be used. The cache paritition is 0.5GB. Is it OK if I include this script as a boot script? Is 0.5GB/500MB enough for most peoples' dalvik-cache? This will free up that space and add it to the internal sd card.

jaibar said:

Regarding the Dalvik cache, is there a way to know how much space all my installed apps + system are currently using?

Click to expand...

Click to collapse

Go to the CM File Manager --> Settings --> General Settings -> Compute folder statistics and check mark that box. Also in the same area be sure to set access mode to prompt user mode or root access mode. Then, go to /data and hold dalvik-cache folder until get a menu and choose properties. The size will show up under "Size: ". Mine is 208mb.