Database Develop

[Q] Adding Touchwiz Framework to AOSP Roms Inquiry

Hi Guys,
I just want to check if is there a way to flash touchwiz framework to an AOSP ROM for some samsung applications to work? In my SGS2 before, there is a Touchwiz.zip that can be flashed to MIUI ROM to have Touchwiz added to the actual ROM.
Thank you

I would really like to know that too.. Im really interested to try aosp rom (becouse tablet UI), but I personally doen't like aosp calendar and clock apps..

Open the ROM.zip
go to /system/apps/
insert the TouchWiz.apk in apps folder *MIND IT dont give spaces btween app names as Touch Wiz.apk it will give FC Error alwayz*
no need to remove any other launcher included over there
JUST flash this rom and BINGO.....................
Ive no idea of whether we need to fix permissions on new inserted .apk files
Take that risk PLEASE and LEMME noe if u get any errors

Is there any updates with this?
Sent from my GT-N7000 using Tapatalk

Put the TouchWiz30Launcher.apk in /system/app and other two in /system/framework and reboot and you will have touchwiz...
Important: Donot rename the files....

vijai2011 said:
Put the TouchWiz30Launcher.apk in /system/app and other two in /system/framework and reboot and you will have touchwiz...
Important: Donot rename the files....
Click to expand...
Click to collapse
Any idea if S-Apps will work when I put the TW framework on an AOSP ROM or are they dependent on something else?

codewisp said:
Any idea if S-Apps will work when I put the TW framework on an AOSP ROM or are they dependent on something else?
Click to expand...
Click to collapse
They are different apps dependent on touchwiz....

vijai2011 said:
They are different apps dependent on touchwiz....
Click to expand...
Click to collapse
So S apps will work then?
Sent from my GT-N7000 using Tapatalk

nicholadia said:
So S apps will work then?
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
It should work i guess

vijai2011 said:
It should work i guess
Click to expand...
Click to collapse
Hi
1°) Could I use the same files on a GN7100 (GN2) ?
2°) would I be able to use this framework to make the TW keyboard work on ProBAM ROM?
Thanks
Nico

nicopilami said:
Hi
1°) Could I use the same files on a GN7100 (GN2) ?
2°) would I be able to use this framework to make the TW keyboard work on ProBAM ROM?
Thanks
Nico
Click to expand...
Click to collapse
To make it work, you need all tw framework and its not only in those tw-framework-res but in almost all bits. And so it makes it extremely difficult to port and easy task would be to flash a tw based rom. Much easier

vijai2011 said:
To make it work, you need all tw framework and its not only in those tw-framework-res but in almost all bits. And so it makes it extremely difficult to port and easy task would be to flash a tw based rom. Much easier
Click to expand...
Click to collapse
Hi
Thanks for the answer. What I understand is it is not impossible, just maybe not trivial.
Then I take the challenge, I'm downloading the stock rom right now to extract the same three files from it, and put them into the ProBAM ROM... we'll see :laugh:

nicopilami said:
Hi
Thanks for the answer. What I understand is it is not impossible, just maybe not trivial.
Then I take the challenge, I'm downloading the stock rom right now to extract the same three files from it, and put them into the ProBAM ROM... we'll see :laugh:
Click to expand...
Click to collapse
It gonna bootloop. So be sure to take a nandroid

@vijai2011,
bump.....
Sorry I know its a older post, but need information about porting touch wiz frame work so as I can make splanner.apk to work with nexus 7, moto razr etc. so far its the best calendar app I have come across. After trying all available calendar in google store.
So question to you is from where you copied the attached touch wiz files....

. Not sure if anyone has had success since.
Sent from my Nexus 5 using Tapatalk

didn't work at s4mini gti9195
vijai2011 said:
Put the TouchWiz30Launcher.apk in /system/app and other two in /system/framework and reboot and you will have touchwiz...
Important: Donot rename the files....
Click to expand...
Click to collapse
android version 4.4.2
kernel reserraction remix
didn't work for me tried many times. luncher don't work. please help me

What do you expect with such old files from 2012?

where could touwchwiz-based custom roms be found?

frac82 said:
where could touwchwiz-based custom roms be found?
Click to expand...
Click to collapse
in the N7000 forum on xda-developers...

I didn't see anything about changing the permissions. I'm adding this currently to my tablet. I'll let you know

[Q]Framework-res.apk

Hi everyone. I have this problem: When I change system apps (SystemUI, SecSettungs, LegacyInCallUI and others) on my G800H 5.1.1 Lollipop framework, system works properly. But when I change framework-res, system starts up and goes to reboot. Any ideas?
P.S. Sorry for my English

Can anyone help me please?

Hello, I have a question and I think it can remove it here. When a ROM is installed, whichever it is absolutely supersedes all? That is, it replaces all that can be seen from the TWRP?

rodrycapo07 said:
Hello, I have a question and I think it can remove it here. When a ROM is installed, whichever it is absolutely supersedes all? That is, it replaces all that can be seen from the TWRP?
Click to expand...
Click to collapse
ROM installed in September 2015 (when it's realised). Rooted, TWPR 2.8

Hello, I am not referring to when (date) to install the ROM. I meant when installing a ROM, replaced everything that can be seen in the recovery?
I will not give a solution. I'm with a doubt and I think you can help

OK, problem solved. I deodexed my firmware, and now it runs normal with edited framework-res

rodrycapo07 said:
replaced everything that can be seen in the recovery?
Click to expand...
Click to collapse
I don't understand you man, what do you mean?

Led control on Android M ....it is possible?

Hello.
i have a question if there is possible to enable led control on Nexus stock M 6.01 MMB29V without TWRP and root.
Thanks and rgds.

semail00 said:
Hello.
i have a question if there is possible to enable led control on Nexus stock M 6.01 MMB29V without TWRP and root.
Thanks and rgds.
Click to expand...
Click to collapse
Without Root - yes (you can use this > http://forum.xda-developers.com/nexus-6/general/led-control-stock-xposed-t3146814
Without TWRP - no

cam30era said:
Without Root - yes (you can use this > http://forum.xda-developers.com/nexus-6/general/led-control-stock-xposed-t3146814
Without TWRP - no
Click to expand...
Click to collapse
I would not advise doing that. As the file is from 5.1.1 there is no telling what changes to the system that has been done.

zelendel said:
I would not advise doing that. As the file is from 5.1.1 there is no telling what changes to the system that has been done.
Click to expand...
Click to collapse
You are correct. I should have been more specific. Post #95 includes file download from CM13 (Android 6.0). Working fine for me on MMB29V.

cam30era said:
You are correct. I should have been more specific. Post #95 includes file download from CM13 (Android 6.0). Working fine for me on MMB29V.
Click to expand...
Click to collapse
Even then that is for that build. It may cause other issues on different builds.

zelendel said:
Even then that is for that build. It may cause other issues on different builds.
Click to expand...
Click to collapse
I agree. It could. But isn't that what we all do here about that? Modifications that are not necessarily 100% bullet proof? And looking for feedback from others who are using it..?

semail00 said:
... possible to enable led control on Nexus stock M 6.01 MMB29V without TWRP and root....
Click to expand...
Click to collapse
It seems to me that you already know the answer. You are familiar with the terms TWRP and root.
Beside the question you need to give a motive.

NLBeev said:
It seems to me that you already know the answer. You are familiar with the terms TWRP and root.
Beside the question you need to give a motive.
Click to expand...
Click to collapse
Hello,
I just wanted to see if it was possible activate led notification without changing the original system, even with some apks ( I do not know but that someone could know ). This was the meaning of my request ..... I apologize if I have not been able to explain.
rgds.

semail00 said:
Hello,
I just wanted to see if it was possible activate led notification without changing the original system, even with some apks ( I do not know but that someone could know ). This was the meaning of my request ..... I apologize if I have not been able to explain.
rgds.
Click to expand...
Click to collapse
Understood. It is nice to know the 'why' behind questions.
On my N6 I've LED control, but with a Lite rom of Danvdh and the cataclysm mod. Works good, but .......root and TWRP.

Extremely DeBloated DeOdexed Patch for Z5 E6683 DSDS 32.3.A.0.376 MY Nougat Firmware

Here is the Extremely DeBloated DeOdexed Patch for Z5 E6683 DSDS 32.3.A.0.376 MY Nougat Firmware with Patched SERVICES.JAR [superuser MOD]
Downloads :
Extremely De-Bloated DeOdexed Patch [Flashable] for Z5 E6683 DSDS v32.3.A.0.376 MY: HERE
Patched Rooted Stock Kernel for Z5 Series .376 Nougat Firmware : HERE
Stock FTF Firmware for Z5 E6683 DSDS v32.3.A.0.376 MY : HERE
Please HIT Thanks if this post helped you in any way.

reserved

reserved for second post

@chinmoy32 bro first thanks a lot . i will try at 6633 but it would be great , if you add list of app was removed from deodex.zip

hello,
what is actually inside the patched kernel ?
is it with drm fix ?
---edit
just read ur other thread about ur kernel, nvm

@chinmoy32 dear i flashed you deodex.zip.all thing is ok except my display and font or all apk ia very small.
what did change you in deodex.zip?
i want to revert to stock size.
would you please help me here?
wait for it
thanks

Hamidreza2010 said:
@chinmoy32 dear i flashed you deodex.zip.all thing is ok except my display and font or all apk ia very small.
what did change you in deodex.zip?
i want to revert to stock size.
would you please help me here?
wait for it
thanks
Click to expand...
Click to collapse
Thats nothing to worry about.................... my friend
I personally use lcd density = 320 , so it is set to 320 in build.prop
just change it back to 480 which is default size and your phone will be back to its normal stock PPI

Hey chinmoy, I've tried many times to flash this patch, but errors occurred every time the phone starts up:
"org.codeaurora.ims has stopped"
"Bluetooth Share has stopped"
Click to expand...
Click to collapse
I don't know what is wrong, and here's my steps:
1. flash stock firmware via flashtool, wipe all.
2. flash kernel via fastboot ( fastboot flash boot 376_NO_SU.img ).
3. flash SuperSU via twrp, wipe cache/dalvik, and reboot.
4. flash deodexed patch via twrp, wipe cache/dalvik, and reboot.
Click to expand...
Click to collapse
step 3 and 4 got a error:
e: legacy property environment did not initialize successfully, properties may not be detected.
Click to expand...
Click to collapse
However nothing is wrong until the patch installed, errors pop up after system starts up, and bluetooth cannot be switched on.
All of the staffs downloaded from your thread.
And one more question, what is the path of the stock camera apk?

chinmoy32 said:
reserved
Click to expand...
Click to collapse
Bro seems Bluetooth not work and get FC
did you saw this issue?

Hamidreza2010 said:
Bro seems Bluetooth not work and get FC
did you saw this issue?
Click to expand...
Click to collapse
yes,
now that you mentioned it , I checked and found the same issue !!
Maybe something to do with deodexing--
need to check

chinmoy32 said:
yes,
now that you mentioned it , I checked and found the same issue !!
Maybe something to do with deodexing--
need to check
Click to expand...
Click to collapse
Ok bro if fix that please put here just fix.zip
thanks a lot

@chinmoy32 Will you have any further development for this ROM rather than just stock. I mean will you mod it further (add XZ features, other great stuffs...) to make it a true ROM, not just a debloated TFT?

Yes I'm also having issue with org.codeaurora.ims not working and Bluetooth share too.

sirdoha said:
@chinmoy32 Will you have any further development for this ROM rather than just stock. I mean will you mod it further (add XZ features, other great stuffs...) to make it a true ROM, not just a debloated TFT?
Click to expand...
Click to collapse
No, I have no plan to do anything else , neither do I have that amount of time.

I found out I cant use WhatsApp video call too

Chrome is having problem too sir.

Because I wanna use Bluetooth , I restore a backup using twrp to go back to without patch, and now I'm stuck in recovery , keep looping back to twrp even though I tried to boot system

sorry for asking, but can you provide list which apps that removed? I'm just wanna debloat everything as much as I can
thanks

ryandxter said:
sorry for asking, but can you provide list which apps that removed? I'm just wanna debloat everything as much as I can
thanks
Click to expand...
Click to collapse
+1
https://forum.xda-developers.com/showpost.php?p=71010120&postcount=4

chinmoy32 said:
yes,
now that you mentioned it , I checked and found the same issue !!
Maybe something to do with deodexing--
need to check
Click to expand...
Click to collapse
Hi
this is fix for bluetooth
just flash via recovery
you can add to the first post:

[8.1] [Magisk Module] Multi-Touch Fix for 8.1 Devices running LOS/AOSP

Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
1a. It works only for AOSP/LOS based roms on the essential phone. It seems like stock isn´t close enough to aosp.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07

this was confirmed working on the xda portal post by @crixley for the essential phone running a custom aosp/los based rom.
Big thanks to you!

Freak07 said:
this was confirmed working on the xda portal post by @crixley for the essential phone.
Big thanks to you!
Click to expand...
Click to collapse
Huge difference, including touch latency! I'm super pumped about it.

Work perfectly!!! Thank you so much!

Guys, does it work? For me I ended up in bootloop

xorwin said:
Guys, does it work? For me I ended up in bootloop
Click to expand...
Click to collapse
Omg you're right it actually causes my phone to not boot. I wiped my entire phone thinking it was some kind of module conflict and now it still wont boot.

xorwin said:
Guys, does it work? For me I ended up in bootloop
Click to expand...
Click to collapse
wind711 said:
Omg you're right it actually causes my phone to not boot. I wiped my entire phone thinking it was some kind of module conflict and now it still wont boot.
Click to expand...
Click to collapse
I bootlooped too. Flashing the stock boot image fixed it and my phone booted right to Android.

Jank4AU said:
I bootlooped too. Flashing the stock boot image fixed it and my phone booted right to Android.
Click to expand...
Click to collapse
Once I flashed the stock boot image I lost magisk so that wouldn't work.

wind711 said:
Once I flashed the stock boot image I lost magisk so that wouldn't work.
Click to expand...
Click to collapse
I wasn't worried about losing Magisk. I was trying to get my phone to boot.
@crixley what did you do to get it to work? For three of us it results in a bootloop.

Jank4AU said:
I wasn't worried about losing Magisk. I was trying to get my phone to boot.
@crixley what did you do to get it to work? For three of us it results in a bootloop.
Click to expand...
Click to collapse
I'm not on stock rom, that might be it. Should have been clear on that

crixley said:
I'm not on stock rom, that might be it. Should have been clear on that
Click to expand...
Click to collapse
Yeah, I'm on stock so you're probably right, that might be it.

Thank you soo much @Freak07 !

I installed with with magisk app as a module. Booted perfect

tomzefi said:
I installed with with magisk app as a module. Booted perfect
Click to expand...
Click to collapse
Are you on stock or custom ROM?

Jank4AU said:
Are you on stock or custom ROM?
Click to expand...
Click to collapse
Should have mentioned that. I am on resurrection remix and rooted.

Confirmed that it also bootloops on stock ROM, if you have ElementalX Kernel installed.

It seems that the stock rom isn’t close enough to aosp so this fix will only work on custom roms!

I edited the OP accordingly to the stock rom issue.
In the meantime can one of you guys on the stock rom do me a favour and check if you have libinputflinger.so and libinput.so located in system/lib and system/lib64 or if the libs are somewhere in vendor for you?

They exist both files.

hypnz said:
They exist both files.
Click to expand...
Click to collapse
It should be 4 files overall. libinput.so and libinputflinger.so have to be in system/lib and additionally in system/lib64.
but if they are in system and not in system/vendor then I have no way of fixing it atm I fear.