[OMNI] [4.4.4] [SM-T31X] Omni Rom (Unofficial) - DISCONTINUED

[ketut.kumajaya]

Please download and flash philz_touch_6.00.8-t310-blackhawk-next.zip in your current recovery.
Reboot Recovery.
Try again to flash the Rom.

I have to update it, using non SELinux kernel for now

I just committed lt01wifi update + libsensorservice.so fix for all variant, sync your source and rebuild Omni :good: My next job:
1. Update Omni lt01lte
2. Update PhilZ Touch kernel for all lt01 variant
3. Update NEXT kernel for CM 11 for p31xx and all lt01 variant

 

[Android-Andi]

I rebuild as fast as i can but i can not acces to my build-pc for next 4 days...
Thanks for all your work on it

 

[manup456]

I posted about issue flashing this and never got a response is everyone getting a status 7 error when flashing?

Sent from my SM-T310 using XDA Premium 4 mobile app

 

[Moa1480]

Omnirom 4.4.2

I posted about issue flashing this and never got a response is everyone getting a status 7 error when flashing?

Sent from my SM-T310 using XDA Premium 4 mobile app

Me too..

 

[manup456]

Me too..

Yeah not sure what's going on I tried a few times and nothing. So I doubt its on our end guess we have to wait until we can get some KitKat in our life.

Sent from my SM-T310 using XDA Premium 4 mobile app

 

[fjsferreira]

Yeah not sure what's going on I tried a few times and nothing. So I doubt its on our end guess we have to wait until we can get some KitKat in our life.

Sent from my SM-T310 using XDA Premium 4 mobile app

Getting error 7 too.

 

[Android-Andi]

Sorry together... it is because of the recovery...

Please replace the update-binary inside the rom.zip with the one from here (inside the zip) http://forum.xda-developers.com/showthread.php?t=2532300
and try again if you want.

maybe CWM 6.0.4.5 from @gr8nole will work without changeing the update-binary...
For T310: T310_CWM6.0.4.5.recovery.img ..

It is because there have been some changes since kitkat... ketut will repack his PhilZ Touch to make it KitKat compatible... give him some time.


This Project is still WIP... maybe you will get a Bootloop, i dont know

Ketut added a lot of commits to Omni for Tab 3 in the last days.
i will run next build on 31th dez. or in january.

 

[fjsferreira]

Sorry together... it is because of the recovery...

Please replace the update-binary inside the rom.zip with the one from here (inside the zip) http://forum.xda-developers.com/showthread.php?t=2532300
and try again if you want.

maybe CWM 6.0.4.5 from @gr8nole will work without changeing the update-binary...
For T310: T310_CWM6.0.4.5.recovery.img ..

It is because there have been some changes since kitkat... ketut will repack his PhilZ Touch to make it KitKat compatible... give him some time.


This Project is still WIP... maybe you will get a Bootloop, i dont know

Ketut added a lot of commits to Omni for Tab 3 in the last days.
i will run next build on 31th dez. or in january.

It's givin status 4 error now

 

[Android-Andi]

mh... ok.. idk... sorry

let´s wait for next 4.4.2 Test-Build...

 

[fjsferreira]

mh... ok.. idk... sorry

let´s wait for next 4.4.2 Test-Build...

Sounds good man. Looking forward to it.

 

[ketut.kumajaya]

mh... ok.. idk... sorry

let´s wait for next 4.4.2 Test-Build...

Please sync your source, just merged my cm-11.0 commit to android-4.4 :good:

 

[souleater11]

hi everyone,
this may sound stupid but is this rom compatible for Galaxy tab 3 7 inch version?

I notice that the difference between 7 and 8 inches Galaxy tab 3 are their resolution sizes so I would assume that this omni rom is safe to flash in 7 inch variant galaxy tab 3

Sent from my SM-T210R using xda app-developers app

 

[ketut.kumajaya]

hi everyone,
this may sound stupid but is this rom compatible for Galaxy tab 3 7 inch version?

I notice that the difference between 7 and 8 inches Galaxy tab 3 are their resolution sizes so I would assume that this omni rom is safe to flash in 7 inch variant galaxy tab 3

Sent from my SM-T210R using xda app-developers app

Don't do it! There a lot of different behind the screen :laugh:

 

[Android-Andi]

2 / 3 days left... i have no access to my pc ... can not rebuild at the moment

 

[ketut.kumajaya]

No problem, may also better after CM 11 managed to boot. But I'll always try to sync my work on CM to Omni.

 

[Android-Andi]

If CM not boot... omni won´t boot too i think.
I have seen all your changes to omni thanks a lot for that! and please keep it up until you managed cm to boot

 

[ketut.kumajaya]

Go Omni go, go :laugh: @Android-Andi Don't pull my cm-11.0 lt013g audio commit for now, it's an experimental codes :good:

 

[Android-Andi]

it itches in my fingers to run it.... i will run my build-bot in ~ 21 hours when i get access back to it
it will do the tab 3 builds after Omni for P31XX and P51XX but before CM11 for P51XX ... so it should be up this year if everything went well

 

[Android-Andi]

@ketut.kumajaya maybe you want to add those commit´s to your android-4.4 tree:
https://github.com/andi34/android_d...mmit/91a25a80347e82969501a17323dbb86cc41d5b3a
https://github.com/andi34/android_d...mmit/fe389ae98dcaccc118a1a8c3704cc783dd82a466
https://github.com/andi34/android_d...mmit/ccc5e908e0fe1e98cf8002fe1ca1cf6909b407bf


@iofthestorm told me to cherry-pick this commit: https://gerrit.omnirom.org/#/c/3011
to fix the Keyboard-Issue.

He also told me as another workaround

"...If you want you can probably actually just disable the sec_keyboard driver in your kernel defconfig, since that's the source of the false hardware keyboard...."

 

[ketut.kumajaya]

@ketut.kumajaya maybe you want to add those commit´s to your android-4.4 tree:
https://github.com/andi34/android_d...mmit/91a25a80347e82969501a17323dbb86cc41d5b3a
https://github.com/andi34/android_d...mmit/fe389ae98dcaccc118a1a8c3704cc783dd82a466
https://github.com/andi34/android_d...mmit/ccc5e908e0fe1e98cf8002fe1ca1cf6909b407bf


@iofthestorm told me to cherry-pick this commit: https://gerrit.omnirom.org/#/c/3011
to fix the Keyboard-Issue.

He also told me as another workaround

But we don't have hardware keyboard:

Not sure, I skip the initial setup wizard for a different reason and my soft keyboard always work after then.