[ROM] [4.1.2] [P311X] MicroDelta Stock Based ROM (XXDME3)

Search This thread
By:
Advanced…
F

filipepferraz

Member
Oct 17, 2010
33
44
Tsjoklat said:
I think only one version was ever posted. But, I still think the problem is with xposed. It is almost as if xposed doesn't function properly unless there is the right cache available to it. Maybe that is why it started working about a week after I had reinstalled my ROM.
Click to expand...

I make some changes, my tablet was with a 0 named folder with the same structure of root directory. I deleted this 0 folder and started to reinstall everything from zero. I installed the Xposed framework, restarted, installed app settings, activate and restarted and it's ok. Later I will try to install and activate the ThemeUI again.

Thank you very much for the help.

One question, is possible to port the IR functionality from 4.1.2 to 4.2.2 ROMs?
 
Skazzy3

Skazzy3

Senior Member
Jan 9, 2012
2,271
1,050
filipepferraz said:
I make some changes, my tablet was with a 0 named folder with the same structure of root directory. I deleted this 0 folder and started to reinstall everything from zero. I installed the Xposed framework, restarted, installed app settings, activate and restarted and it's ok. Later I will try to install and activate the ThemeUI again.

Thank you very much for the help.

One question, is possible to port the IR functionality from 4.1.2 to 4.2.2 ROMs?
Click to expand...
The 0 folder is needed for 4.2.x ROMS only.
Also no IR.
 
Tsjoklat

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,385
filipepferraz said:
One question, is possible to port the IR functionality from 4.1.2 to 4.2.2 ROMs?
Click to expand...

The IR functionality works with this ROM because this is based off of Samsung's stock images. The 4.2.2 Roms are based off of other sources (which do not support Samsung's custom framework). But, I read that Samsung is going to release a stock 4.2.2 image before September.
 
F

filipepferraz

Member
Oct 17, 2010
33
44
Tsjoklat said:
The IR functionality works with this ROM because this is based off of Samsung's stock images. The 4.2.2 Roms are based off of other sources (which do not support Samsung's custom framework). But, I read that Samsung is going to release a stock 4.2.2 image before September.
Click to expand...

In 4.2.2 exists the hardware module of IR to make a custom app to use the IR without the samsung framework and peel app? Direct hardware access.
 
F

filipepferraz

Member
Oct 17, 2010
33
44
Luigi2012SM64DS said:
But who's gonna make an app?

Sent from my GT-P3113 using Tapatalk HD
Click to expand...

I want to start making the app, but first I want to know if the hardware is available to use from Android.
I have the IOIO developer board and find some example projects of using IR:
http://courses.cs.tau.ac.il/embedded/projects/fall2011/IR_on_IOIO/IR_on_IOIO.htm
https://github.com/lanthaler/ioio/

There is a lib to use IR with IOIO, maybe if the hardware module exists in 4.2.2 version can be possible do send IR signals from the app without the IOIO, using the IR module presents in p3113.
 
Tsjoklat

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,385
After further thought about why the TabletUI module does not work on a new setup, I think I just realized what made the problem go away. I had mentioned a few posts back that I had experienced the same issue but when a new version of Xposed was posted, the problem went away. But, now that I think back, right before I tried the new version of Xposed, I had manually edited my build.prop to a dpi of 133 to force the UI into tablet mode. This action must have created some cached configurations for the TabletUI. After booting into tablet mode, I then edited the build.prop back to dpi 160 and booted back into PhabletUI. Finally, I then enabled the XPosed TabletUI module and it worked as expected from then on. So, I think the issue is with the module, not XPosed itself.
 
  • Like
Reactions: filipepferraz
F

filipepferraz

Member
Oct 17, 2010
33
44
Tsjoklat said:
After further thought about why the TabletUI module does not work on a new setup, I think I just realized what made the problem go away. I had mentioned a few posts back that I had experienced the same issue but when a new version of Xposed was posted, the problem went away. But, now that I think back, right before I tried the new version of Xposed, I had manually edited my build.prop to a dpi of 133 to force the UI into tablet mode. This action must have created some cached configurations for the TabletUI. After booting into tablet mode, I then edited the build.prop back to dpi 160 and booted back into PhabletUI. Finally, I then enabled the XPosed TabletUI module and it worked as expected from then on. So, I think the issue is with the module, not XPosed itself.
Click to expand...

I will try to make what you have described to see if works and confirm the issue with the module.
Thank you very much for the information
 
Skazzy3

Skazzy3

Senior Member
Jan 9, 2012
2,271
1,050
I wonder if it is possible to "squish" the nav bar buttons in tablet ui. Like in ICS. Cuz the button would overlap the mini apps thing.
 
Tsjoklat

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,385
Luigi2012SM64DS said:
I wonder if it is possible to "squish" the nav bar buttons in tablet ui. Like in ICS. Cuz the button would overlap the mini apps thing.
Click to expand...

Yes, install the "App Settings" Xposed module also and change the DPI of the SystemUI.apk to a range between 134 - 160. I recommend setting DPI to 145 (for the SystemUI.apk) because this is as low as it can go before the long press on the home button stops working with Google Now.

Note: The TabletUI module should also be enabled.
 
Last edited:
enzo319

enzo319

Senior Member
Dec 24, 2010
293
126
I'm gonna flash this tonight on my p3113. Anyone have issues with the physical keyboard dock?

Clapping is giving yourself a high-five for something someone else did.
 
jakelights

jakelights

Senior Member
Jul 29, 2010
133
22
Sir I tried this rom for my hong kong stock rom but the video player seems have a black backgroud, ive attached an image that the original rom appear. But if i flash this rom, as i said theres a black backround apoears on control. Is this normal for non hong kong rom?

Sent from my GT-P3110 using xda app-developers app
 

Attachments

  • uploadfromtaptalk1370771990094.jpg
    uploadfromtaptalk1370771990094.jpg
    35.7 KB · Views: 278
Tsjoklat

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,385
jakelights said:
Sir I tried this rom for my hong kong stock rom but the video player seems have a black backgroud, ive attached an image that the original rom appear. But if i flash this rom, as i said theres a black backround apoears on control. Is this normal for non hong kong rom?

Sent from my GT-P3110 using xda app-developers app
Click to expand...

The video player should have a black background. Attached is a screenshot of how it looks on my device using this ROM.

edit: I see what you mean. It does look like your ROM has slightly different shading behind some of the buttons and the pause, fast forward, and rewind have a completely transparent background. I think these are regional differences.
 
Last edited:
jakelights

jakelights

Senior Member
Jul 29, 2010
133
22
Thank you for reply sir. I tried to replace the apk in the system, fix permission. But its not working. Any help sir? I really like to make this rom my main.
Sent from my GT-P3110 using xda app-developers app
 
enzo319

enzo319

Senior Member
Dec 24, 2010
293
126
odd

My P3113 was just hanging on the 'Samsung' logo. Tired numerous times with all the addons, in the end i just flashed the p3110 ROM then flashed each add on afterwards. so far so good.
 
enzo319

enzo319

Senior Member
Dec 24, 2010
293
126
Yes. Yea wound up doing a factory reset and after installing the main ROM I flashed each mod individually. ROM runs smoother than stock

Clapping is giving yourself a high-five for something someone else did.
 
Tsjoklat

Tsjoklat

Senior Member
Apr 5, 2010
1,705
2,385
Last edited:
  • Like
Reactions: jakelights
jakelights

jakelights

Senior Member
Jul 29, 2010
133
22
Tsjoklat said:
I have used your suggestion and added the stock video player with transparent controls to the OP.

MicroDelta-JB-4.1.2-transparent-videoplayer-signed.zip

Thanks!
Click to expand...

Thank you sir. I'll flash this ROM as soon as i arrive home. Thanks again sir

Update: This works sir. thanks so much. anyway, i'm using stock rom before flashing this rom and the patch. do you recomen i wipe before flashing this rom?
 
Last edited:
You must log in or register to reply here.

Similar threads

timmytim
[ROM][P311X] (4.1.2) XXDME3 | Stock | Odexed | For Devs & ROM Cooks
Replies
2
Views
3K
rod555
rod555
Tsjoklat
[ROM] [4.2.2] [P311X] MicroDelta Stock Based ROM (UEUCMK3)
Replies
344
Views
78K
Tsjoklat
Tsjoklat
K
[ROM] [4.1.2] [P31xx] Stock Based ROM Powered by NEXT
Replies
697
Views
130K
Z
ze7zez
CM-PRo
[ROM][GT-P3100][4.0.4] -Stock - Base: IMM76D.P3100DDBLF3
Replies
33
Views
140K
eryfilho
eryfilho
RomsWell
[ROM][7/26][GT-P3113][4.0.4] - Stock Rooted De-Odexed -Base: IMM76D.P3113UEBLG5
Replies
140
Views
44K
Gizmo
Gizmo

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 16
    Tsjoklat
    Tsjoklat
    Presenting, MicroDelta stock based JB 4.1.2 ROM (P3110XXDME3) for the Samsung Galaxy Tab 2 P3110 and P3113 (see addons for more information on P3113 infrared support). There are no performance enhancing init.d scripts or system tweaks applied to this ROM. Everything should be as close to stock as possible. All customizations for this ROM will be provided below as independent addons.

    • JB 4.1.2
    • Deodexed
    • Zipaligned
    • Busybox 1.20.2r2 with statically linked binary (Resource: https://code.google.com/p/yangapp/downloads/detail?name=busybox-1.20.2r2)
    • Superuser 1.0.1.8 by ClockworkMod is now default superuser application. This version is chosen because it is fully working, free, and open source. Resource: https://play.google.com/store/apps/details?id=com.koushikdutta.superuser ** Note** XXDMA2 release uses SuperSU 1.25 (Resource: http://forum.xda-developers.com/showthread.php?t=1538053)
    • Kernel init.d support added to stock ramdisk. Note: The init.d support in this ROM is triggered by a patch to init.rc in the ramdisk (instead of the alternate "install-recovery.sh" init.d trigger method). The alternate "install-recovery.sh" init.d trigger method is not used in this ROM because it can conflict with the init.d support provided by other custom kernels and cause the init.d scripts to be executed twice.
    • Note: The modified version of Google Play Store is now supplied separately with latest release (XXDME3). See attachments below for flashable zip to install this version of the modified Play Store. Google Play Store 3.4.7 (/system/app/Phonesky.apk) added and modified to skip automatic internal self update (Google has permanently disabled Ti Backup's ability to attach and detach applications in the Play Store after version 3.4.7, so the Google Play Store has been modified to not internally update itself automatically without notification or permission). Resource: http://forum.xda-developers.com/showthread.php?t=1580827
    • Startup and Shutdown sound files renamed with "bak" extension to prevent execution (these two sound files can be changed back to their original names to enable the default startup and shutdown sounds again).
      1. /system/media/audio/ui/PowerOff.ogg
      2. /system/media/audio/ui/PowerOn.ogg
    • Sysro and sysrw scripts added to /system/xbin for easy command line interface.

    No default applications have been removed from this ROM. I find it safer to use Ti Backup and freeze the applications that I do not want to use, instead of removing them. Here is a list of the applications that I recommend freezing with Ti Backup in this ROM:

    • AllShare Play
    • AllShare Service
    • ChatON
    • Game Hub
    • Google Play Magazines
    • Google Play Music
    • Kobo
    • Music Hub
    • PressReader
    • Readers Hub
    • S Suggest
    • Samsung Apps
    • Samsung Push Service
    • Software update
    • Video Hub
    • Zinio

    Notes on Tablet UI:

    For the "Tablet UI", I recommend using Xposed Framework. Resource: http://forum.xda-developers.com/showthread.php?p=24267797

    After setting up Xposed framework, install the "TabletUI" and "App Settings" Xposed modules. Activate both Xposed modules and use the App Settings Xposed module to control the DPI of the SystemUI (with a range of 134 to 160 DPI). Any DPI setting for the SystemUI that is lower than 134, while the TabletUI Xposed module is also activated, will cause the SystemUI to report an error. DPI 145 seems to be optimal size because this is as low as it can go before the long press on the home button works with Google Now.

    Tablet UI Xposed module: http://www.villainrom.co.uk/forum/threads/tabletui-trigger.5527/ or http://forum.xda-developers.com/showpost.php?p=41583916&postcount=84
    App Settings Xposed module: http://www.villainrom.co.uk/forum/threads/app-settings.5486/ or http://forum.xda-developers.com/showpost.php?p=41891726&postcount=116
    Xposed Module Homepage: http://www.villainrom.co.uk/forum/forums/xposed_framework_mods/

    You must use Xposed Framework >= v2.1.4 (along with the TabletUI module) for this to work properly with this ROM.

    Notes on custom kernels:

    This ROM should work as a good base for testing custom kernels. There are many to choose from, but the KK Boot image works very well (thanks ketut.kumajaya). Reference: http://forum.xda-developers.com/showthread.php?t=1855700

    Recommended Installation:

    ** If you are already running a stock 4.1.x ROM, then there is no need to wipe the data/cache. Just flash over the top of the previous installation without wiping.

    ** If you are currently using an AOKP or CM based ROM, then a wipe of the data/cache after installation is required.

    Thanks:

    Special thanks to everyone here on XDA that helped me put this together. Attached below is a text file (MicroDelta-P3110-JB-4.1.2-P3110XXDME3.txt) with the MD5 and link to the ROM. I have also attached a few custom MicroDelta (and alternate Deltadroid) bootanimations and wallpapers for your Home and lock screen. Enjoy.

    Additional Addons:

    Attached below is also a ClockworkMod flashable zip (MicroDelta-JB-4.1.2-P3110XXDME3-stock-kernel-init.d-bootanimation-signed.zip) of the stock kernel with init.d support plus additional custom bootanimation support. The kernel package also comes with a custom MicroDelta bootanimation which is installed to /system/media/bootanimation.zip. Note: This kernel package with bootanimation support will also work with a P3113. Edit: Added alternate bootanimation with kernel called Deltadroid.

    Additionally, attached below is a text file (MicroDelta-P3113-JB-4.1.2-P3113XXDME3.txt) that contains the MD5 and link to a ClockworkMod flashable zip for P3113 support. The flashable zip will modify build.prop on the MicroDelta ROM so that Settings->About will display the correct P3113 model number. Also, this flashable zip will install the Peel Infrared support for the P3113. Flash the zip over the top of the P3110 MicroDelta ROM to install.

    The extended 4-Way Reboot menu modification has been added below as a flashable ClockworkMod zip. This modification alters android.policy.jar and integrates the extended reboot menu into the system. Credits to kahvitahra for posting a howto.

    In addition to the 4-Way Reboot menu modification, the Back2Kill mod is also available for android.policy.jar (allows you to long press the back key to kill current running applications). This modification is combined with the 4-Way Reboot Modification because both of these modifications are changing the same file. Credits to Mirko ddd for posting a howto.

    The Ripple lockscreen has been added below as a flashable ClockworkMod zip. This modification alters framework-res.apk and services.jar to integrate the Ripple lockscreen. Credits to txr33 for posting a howto.

    The stock video player also comes as an addon with transparent control buttons (play,ff,rw) and support for bluetooth control (pause,ff,rw,next track,previous track).

    Provided below are three different options for altering the user interface (for both p3110 and p3113):

    1) JB-black-statusbar-icons: change the Touchwiz status bar to black and the status bar icons to the default Jelly Bean icon set for the wifi, battery, and bluetooth. Also, change the notification panel to a black background with Jelly Bean blue accents. Works in PhabletUI and TabletUI.

    2) JB-nominiapps-black-statusbar-icons: Same as option #1 plus removes the mini applications "arrow" that exists in the middle of the navigation bar (so that the TabletUI modification has more room for the soft keys). Works in PhabletUI and TableUI.

    3) JB-nominiapps: Keep the default Touchwiz status bar and icon set. Only remove the mini applications "arrow".

    All MicroDelta 4.1.2 Roms and modifications can be found here:
    MicroDelta 4.1.2 File Repository
    View
    6
    Tsjoklat
    Tsjoklat
    Richcar said:
    Hi Tsjoklat would we be getting any update base on the p3110 , 4.2.2 .
    http://www.sammobile.com/2013/08/13...t-p3110-receiving-android-4-2-2-update-in-uk/
    Click to expand...

    Yes, I'm in the final testing stages now. I will start uploading in about 10 minutes and create a new MicroDelta 4.2.2 thread.
    View
    4
    Tsjoklat
    Tsjoklat
    Remove Miniapps

    I have figured out how to remove the miniapps arrow on the navigation bar without causing any problems with the video player and other system applications. I posted the following file which will work in both TabletUI and PhabletUI and it will make the status bar black and also install the default Jelly Bean status bar icons for the wifi, battery, and bluetooth.

    Link to flashable zip for no miniapps and jelly bean status bar icons

    Code: 
    diff -ru SystemUI.orig/res/layout/tw_system_bar.xml SystemUI/res/layout/tw_system_bar.xml
--- SystemUI.orig/res/layout/tw_system_bar.xml	2013-04-27 04:03:05.814778319 +0200
+++ SystemUI/res/layout/tw_system_bar.xml	2013-04-27 04:25:05.858777314 +0200
@@ -13,7 +13,6 @@
                     <com.android.systemui.statusbar.policy.QuickLaunchKeyButtonView android:id="@id/quick_launch" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/tw_ic_sysbar_capture" android:contentDescription="@string/accessibility_capture" />
                     <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/menu" android:visibility="invisible" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/tw_ic_sysbar_menu" android:contentDescription="@string/accessibility_menu" systemui:keyCode="82" />
                 </LinearLayout>
-                <ImageView android:id="@id/traybar_handler" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/traybar_handler" android:layout_centerInParent="true" android:contentDescription="@string/accessibility_open_traybar" />
                 <com.android.systemui.statusbar.policy.EventHole android:id="@id/fake_space_bar" android:paddingLeft="8.0dip" android:paddingRight="8.0dip" android:visibility="gone" android:layout_width="0.0dip" android:layout_height="fill_parent" android:layout_toLeftOf="@id/notificationArea" android:layout_toRightOf="@id/navigationArea" />
             </RelativeLayout>
         </FrameLayout>
diff -ru SystemUI.orig/res/layout-sw600dp/tw_navi_bar.xml SystemUI/res/layout-sw600dp/tw_navi_bar.xml
--- SystemUI.orig/res/layout-sw600dp/tw_navi_bar.xml	2013-04-27 04:03:06.330778319 +0200
+++ SystemUI/res/layout-sw600dp/tw_navi_bar.xml	2013-04-27 04:27:50.670777163 +0200
@@ -9,7 +9,6 @@
                 <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/recent_apps" android:layout_width="wrap_content" android:layout_height="fill_parent" android:layout_marginLeft="50.0dip" android:src="@drawable/tw_navigationbar_recent" android:contentDescription="@string/accessibility_recent" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
                 <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/home" android:layout_width="wrap_content" android:layout_height="fill_parent" android:layout_marginLeft="50.0dip" android:src="@drawable/tw_navigationbar_home" android:contentDescription="@string/accessibility_home" systemui:keyCode="3" systemui:keyRepeat="true" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
                 <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/back" android:layout_width="wrap_content" android:layout_height="fill_parent" android:layout_marginLeft="50.0dip" android:src="@drawable/tw_navigationbar_back" android:contentDescription="@string/accessibility_back" systemui:keyCode="4" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
-                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/traybar_handler0" android:visibility="gone" android:layout_width="80.0dip" android:layout_height="fill_parent" android:layout_marginLeft="50.0dip" android:layout_marginRight="0.0dip" android:src="@drawable/traybar_handler" android:layout_centerInParent="true" android:contentDescription="@string/accessibility_open_traybar" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
             </LinearLayout>
             <LinearLayout android:gravity="right" android:orientation="horizontal" android:id="@id/lights_out" android:background="@drawable/tw_navigationbar_bg" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="fill_parent">
                 <ImageView android:visibility="gone" android:layout_width="80.0dip" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_lights_out_dot_large" android:scaleType="center" />
@@ -26,7 +25,6 @@
                 <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/recent_apps" android:layout_width="wrap_content" android:layout_height="fill_parent" android:layout_marginLeft="262.0dip" android:src="@drawable/tw_navigationbar_recent" android:contentDescription="@string/accessibility_recent" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
                 <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/home" android:layout_width="wrap_content" android:layout_height="fill_parent" android:layout_marginLeft="50.0dip" android:src="@drawable/tw_navigationbar_home" android:contentDescription="@string/accessibility_home" systemui:keyCode="3" systemui:keyRepeat="true" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
                 <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/back" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginLeft="50.0dip" android:src="@drawable/tw_navigationbar_back" android:contentDescription="@string/accessibility_back" systemui:keyCode="4" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
-                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/traybar_handler90" android:visibility="gone" android:layout_width="80.0dip" android:layout_height="fill_parent" android:layout_marginLeft="262.0dip" android:layout_marginRight="0.0dip" android:src="@drawable/traybar_handler" android:contentDescription="@string/accessibility_open_traybar" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
             </LinearLayout>
             <LinearLayout android:gravity="right" android:orientation="horizontal" android:id="@id/lights_out" android:background="@drawable/tw_navigationbar_bg" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="fill_parent">
                 <ImageView android:visibility="gone" android:layout_width="80.0dip" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_lights_out_dot_large" android:scaleType="center" />

    TabletUI is much nicer now that all the buttons fit in portrait mode. Those miniapps were in the way. I recommend this modification with just the TabletUI Xposed framework. Attached is a screenshot.

    Edit: see http://forum.xda-developers.com/showpost.php?p=41045560&postcount=62 for new patch that fixes softkey alignment in PhabletUI.
    View
    3
    Tsjoklat
    Tsjoklat
    Screenshots of PhabletUI and TabletUI:
    View
    3
    Tsjoklat
    Tsjoklat
    I have just added XXDME3 ROM to the 2nd post. This is the latest release from sammobile.com. Enjoy.

    Upgrade instructions: Just install on top of previous MicroDelta release to upgrade. No need to clear data or cache.
    View

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone