yashsingh1/xdaforums huggingface dataset:
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Full Screen Caller ID with Opal Dailer

This is just a suggestion, and I am sure you are busy with other things but this is a nice visual improvement.

I don't know if you would be interested in building in this App into your ROM to replace the current dailer. Its also simular to what the Touch HD uses for incoming calls.

The only down fall is you would lose Video Calling funtion. For now I am just using the CAB on top of the ROM.

Here is the link to the CAB and OEM package.

http://xdaforums.com/showthread.php?t=430354

Again thanks for your great ROM, it currently is my favorite and I don't see switching for a while.

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] vcdwelt:
Thanks for new Rom.

Installing now :D
[Touch Dual, MDA Touch Plus ROM Development] shark147:
I just some time and there are serious bugs in this ROM, I promise you that I am doing with the DIALPAD OPAL :)

@EDIT:

almost, almost do you do now so you happy :p
[Touch Dual, MDA Touch Plus ROM Development] ironman76:
Hello, what does it mean? OEMDRIVER from opal? Could we use radio 1.71..? Thanks
[Touch Dual, MDA Touch Plus ROM Development] shark147:
Hi,

The OEMDRIVER OPAL is the new HTC Touch Viva (Code Name: HTC Opal 100)

Jerpelea have export the driver.

No you can not even the Radio 1.71, because, the camera don't work, no ring etc...

The next version of the ROM LILLY, will have the new Nike driver, and the version of RADIO will be 1.71

i'm wait Jerpelea correct a problem with the messages in the new driver.

OEMDRIVER from OPAL is supplementing the HTCCA D3D Driver.
[Touch Dual, MDA Touch Plus ROM Development] ironman76:
Ah, ok, i see. Thank you very much for your fast answer:)
[Touch Dual, MDA Touch Plus ROM Development] Zumbi:
I did a bitmap rendering benchmark with SK Tools (still LILLY v1.2.5) and it's exactly as fast as a Touch Diamond! Performance was my argument to update with your ROM, because the poor out-of-the-box performance of the Niki sucked and the new gui/visuals are a great give-away. ;)

I'm afraid your new ROMs will run faster than my PC. :D
[Touch Dual, MDA Touch Plus ROM Development] Pinotage:
Hello Shark,

my question just again. What are the differences between version 1.2.5 and 1.3 of your manila 2D rom without cube? Ok, i can read the changelog, but perhaps you can describe the difference? Is ist faster?More stable?

Thanks for your answer (and your good work).

Greets
[Touch Dual, MDA Touch Plus ROM Development] shark147:
Hi :)

Yes more stable and fast, thanks for driver OPAL
[Touch Dual, MDA Touch Plus ROM Development] Zumbi:
Hi,

I didn't test 1.3 yet!!

Found no bugs in 1.2.5 (I don't wanna change the M2D theme because I like Sharks composition) and installed all my applications...it takes hours :rolleyes: ...so I'm still happy with it.

But with the OPAL driver and a new dailer I'll test performance again. :p
[Touch Dual, MDA Touch Plus ROM Development] Parg:
Here two "bugs" I noticed in the "1.2.5 20 keys" version:

- The is no dot in the soft keyboard

- The hard keyboard doesn't work the way it should do
[Touch Dual, MDA Touch Plus ROM Development] vcdwelt:
You should update, new rom is realy fast :D

No problems so far on my 16key nike. Only the Manila2D Skin is nothing for me, but with integrated M2D Customizer no problem :)

And again a great Rom from Shark
[Touch Dual, MDA Touch Plus ROM Development] Zumbi:
Hi,

had trouble with finding the dot the first time, too. Don't search for a dot, it looks like a hyphen, like this "-" but at the bottom ;)

Layout/language and appropriate button:

Italian/English -> :

German -> @

Spanish -> ñ

French -> ;

Hope it helps :rolleyes:

I feel pressurized. MUST...UPDATE...ROM! ^^
[Touch Dual, MDA Touch Plus ROM Development] Pinotage:
You guys drive me crazy :D

I have done all my settings with version 1.2.5, and its good for me.

I was sure nothin to change any more.

And now you tell us to change. Could become a long night, once again...;)

Greets
[Touch Dual, MDA Touch Plus ROM Development] shark147:
The new version has improved graphics, you will be disappointed not. :)
[Touch Dual, MDA Touch Plus ROM Development] vcdwelt:
I know this problem very good, but i wasn't able to resist the new Rom (as always) :D
[Touch Dual, MDA Touch Plus ROM Development] Pinotage:
I have read that in 1.3 a new manila skin is used. What skin is this (could you post a screen shot)?

In 1.2.5. with the blue skin everything fit very well (blue splash scren, blue manila with blue settings, and blue home screen).

What about the new ROM?

Thanks
[Touch Dual, MDA Touch Plus ROM Development] Parg:
It seems to be the same skin. Only the scrollbar on the bottom is white. Looks good
[Touch Dual, MDA Touch Plus ROM Development] Zumbi:
I think the skin is the same.

"Manilla2D Update18 (Change Skin Only)" and "Manilla2D Configuration v0.10.130 (THEME CHANGE)" means, that you now can customize the skin without getting errors on M2D. In the versions released before TouchFlo wasn't working with custom skins.

If I'm not right, plz post some screenshots of the pink M2D skin :D Just jokin'.

The black bar was the only thing that distracted me. In some apps you didn't see any buttons. You had to blind-tap it. Good to hear it's fixed now.

Great work again Shark!
[Touch Dual, MDA Touch Plus ROM Development] Parg:
@Shark:

Are you going to to fix the "Audio Manager doesnt work in Standy by" Problem or is it on purpose?
[Touch Dual, MDA Touch Plus ROM Development] damir4ever:
I'm upgrading 1.3 LILLY tomorow! Still on 1.2.4 version.. Can't wait to see how fast it will go whit this upgrade:)
[Touch Dual, MDA Touch Plus ROM Development] Pinotage:
After flashing my hardware keyboard didn´t work. I have installed the software keyboard and the german files. But hardware keyboard only writes numbers, no letters. What did I wrong?
[Touch Dual, MDA Touch Plus ROM Development] windin:
bit of an issue and I have reflashed 3 times now to make sure but I dont have any weather icons, in the last version I did but no while it will allow me to set my city there is nothing displayed

any ideas?
[Touch Dual, MDA Touch Plus ROM Development] Zumbi:
Did you hard-reset after flashing? Anyone else got this problem?

I won't flash from 1.2.5 to 1.3 until the next couple of days so i can't help atm.
[Touch Dual, MDA Touch Plus ROM Development] sergiuh:
same here..............
[Touch Dual, MDA Touch Plus ROM Development] Zumbi:
I bet you got the PocketCM keyboard...uninstall and try again (got this problem with the numbers before and solved it). Do you have the 16 or 20 keys version?
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
Has anyone tested to see if the new version has the swipe gesture fixed when trying to move between email accounts and SMS?? In the LILLY version I'm running the screen turns black when I swipe between the different messaging accounts.
[Touch Dual, MDA Touch Plus ROM Development] dadme:
Version 1.3 works nice by now for me. Can i use this with new Nike Radio 1.71.09.01K?
[Touch Dual, MDA Touch Plus ROM Development] shark147:
Hi

you remove all City and try again, also happened to me, but after I removed the city, and I added city, the icons have appeared.
[Touch Dual, MDA Touch Plus ROM Development] shark147:
Hi,

No you can not even the Radio 1.71, because, the camera don't work, no ring etc...

The next version of the ROM LILLY, will have the new Nike driver, and the version of RADIO will be 1.71

I'm wait Jerpelea correct a problem with the messages in the new driver.
[Touch Dual, MDA Touch Plus ROM Development] shark147:
Yes, the problem fix. :)
[Touch Dual, MDA Touch Plus ROM Development] shark147:
Hi at all,

Today i have release the same LILLY ROM v1.3 with DIALPAD 2G OPAL, download POST#3

:)
[Touch Dual, MDA Touch Plus ROM Development] LockeDeAvrim:
Feeback on Lilly 1.3

Firstly a codo's to Shark147 for the Rom, been testing 1.3 No Keyboard for the last 3 days and these are the only problems I've found so far.

1. Enabling "MyFavesWidget" in M2DC cause M2D To go into start loop (tap to start >> Starting >> tap to start).

2. Video's don't play (In HTC Album or M2 Photo Widget)

I believe radio issues has already been covered, but I'm listing them for reference.

3. Camera Not working with Radio 1.65.28.25. fixed by flashing Radio 1.58.21.23_25.65.30.04S_Modded, but causes bad signal. Ended up using Radio 1.58.25.14_25.69.30.05P

4. Video Not working with Radio 1.65.28.25 fixed by flashing Radio 1.58.21.23_25.65.30.04S_Modded, but causes bad signal. Ended up using Radio 1.58.25.14_25.69.30.05P

5. Phone Mic & Speaker does not work Radio 1.65.28.25 fixed by flashing Radio 1.58.21.23_25.65.30.04S_Modded, but causes bad signal. Ended up using Radio 1.58.25.14_25.69.30.05P

6. Audio Manager stops playing when phone power button is pressed for sleep mode. Workaround is to use the "Display Switch" appliaction included.

7. Sliding open phone does not launch "Quick Tasks" or phone. Installed SlideActions 1.91, Phone App now closes when sliding "close", but sliding open still doesn't work. Starts working when M2D is disabled in today menu.

8. Weather tab's images don't display. I resolved this by removing all locations and re-adding them.

I Have not yet tested the Google Maps (Need to install google), but all other functions are working well.

Also I have an idea for a Windows (tsk) theme with your rom which might fit betten that pure_black. Attached is an image of the general idea. Will try to get the top bar to be white as well, but of course I want the "dirty" white look of M2D's widget bar.
[Touch Dual, MDA Touch Plus ROM Development] shark147:
Hi, Thanks for your feedback.

what you've written is all right

In this Version ROM the RADIO ROM, can not be longer than the RUU Nike Radio 1.64.08.21K otherwise the camera and ring, etc don't work.

For QuickTask must hold the button "Volume Controll DOWN"

Thanks :)
[Touch Dual, MDA Touch Plus ROM Development] Parg:
Is that problem in purpose or a bug?
[Touch Dual, MDA Touch Plus ROM Development] cpt.bert:
I cant install the parvello digital clock... manilla 2d then goes into loop
[Samsung Galaxy Note 10 Questions & Answers] DesperateScorpion:
View attachment 5357605
[Samsung Galaxy Note 10 Questions & Answers] blackhawk:
Back button?🤣

Maybe something you disabled... dependencies, dependencies, dependencies.

Guess on the next factory reset keep an eye on it... or go witch hunting now for disabled Samsung apks/services.
[Samsung Galaxy Note 10 Questions & Answers] blackhawk:
Is Samsung Cloud or Pass disabled?

Just a guess I don't use either my Samsung account is disable.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Awesometic:
## Changelogs

2023. 9. 20

Change the default download link of this thread to version 3.5.2 for the best stabiliy

Somewhen

Updated TWRP version to 3.7.0

2021. 11. 30

Updated TWRP version to 3.6.0

Started to use my custom kernel

Set the kernel to "awesometic-kernel-v0.3"

Merged CAF tag LA.UM.7.6.r1-07800-89xx.0

Now it supports F2FS file system

Improved performance

And some more but not related to the recovery

2021. 7. 9

Initial release
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Awesometic:
**TWRP 3.5.2 is highly recommended**

On the collected data so far, TWRP 3.6.0 and 3.7.0 are somewhat unstable for some conditions.

So I decided to change the download link of this thread to 3.5.2 to prevent from making users from avoiding the unstable version.

But I didn't remove the files on the drive, so if you want to try the newer versions please visit here and download the archived files.

- Google Drive - Galaxy Tab S3 TWRP
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] elchmartin:
Nice to see TWRP for the sm820...

Cannot really test since my tabs3 is needed as a daily, but that might just change soon...
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] samsuffit:
Flashed with an old TWRP. It works. Can't test with stock rom either... Strange bug with the shell:

libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 635 (ls), pid 635 (ls) Segmentation fault

It happens only when trying to access /external_sd/ (ls, find, etc.) no problem at / or /sdcard/ /external_sd/ is accessible with the internal file browser. Portrait orientation? Why not.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] XolYnrac:
I have flashed with tweaked ROM https://xdaforums.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/ via adb shell. It work right
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] XolYnrac:
I would like to help to add dualboot for sm-t820, is there some project in this direction ?

Thanks, Good job!!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Awesometic:
Actually, on my side, I have no issue when accessing the SD card, /external_sd. I'm usually putting a file into that directory through ADB. Sorry, don't know why that happens..

If there's no problem when you use another TWRP, can you tell me which one?

There's no plan for something related to the dual-boot. :)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] samsuffit:
I tried again, before I messed it up https://xdaforums.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/post-85316477 and had the same error. Before I was using TWRP 3.2.1-1 and I never had any error with adb shell. The error wasn't with adb push, but adb shell.

I'm a bit tired of this damned tablet, I don't know, it was a bit expensive for a Digital Photo Frame.

---

Interesting. So, I succesfully "unbrick" this doomed tablet with the method of the seven days, then I flashed your TWRP with Heimdall, with the option '--no-reboot' and pressed Home/Vol+/Power to reboot immediately in recovery. The splash screen appear and nothing. I flashed TWRP 3.2.1-1 wich can be find in this forum, reboot in recovery, I had this new red message "RECOVERY IS NOT SEANANDROID ENFORCED" and... it worked. Format Data, wipe everything, flash Lineage, Magisk, as usual, reboot in recovery. Inside TWRP 3.2.1-1 I flashed your TWRP 3.5.2_9-0 and... it worked!

From Stock Rom:

- Flash with Heimdall/Odin -> NOT OK

- Flash with TWRP -> OK

Still, I have the error.

sam@suffit $ adb shell
gts3lwifi:/ # ls /external_sd/
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 4616 (ls), pid 4616 (ls)
Segmentation fault
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Awesometic:
I haven't faced that issue so far. Actually I use only one kind of SD card so probably I couldn't find that issue.

Could you attach the logcat when the error occurs?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] samsuffit:
Unfortunately there isn't logcat in recovery and the recovery.log dump doesn't show anything. /external_sd is mounted correctly, that's why I can access it with the internal file browser or choose it to pick up a file to flash. kernel.log (dmesg) doesn't show anything either. The problem is with the shell, busybox. I can't help you more, I'll think to an other way to find where's the error come from.

Reading the logs, I've found where the date and time are, for my other problem in the other thread.

I:Created '/persist' folder.
I:TWFunc::Fixup_Time: Pre-fix date and time: 2017-01-01--09-56-37
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /persist/time/ats_2, offset 1592833667239
I:TWFunc::Fixup_Time: Date and time corrected: 2020-06-22--23-44-25
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Awesometic:
Oh okay, thank you for the report anyway.

And the date/time issue, I didn't know that the time data is stored into the /persist directory. :oops:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] LedgendaryEpics:
twrp seems very stable, however incredibly slow to start. it takes 30 to 40 seconds ro get the twrp boot screen for me (t820) other thsn that it works well, I also tested this out by not flashing the kg/rmm state patch, as well the the encryption disabler and was able to boot back to this recovery without my data getting absolutely wiped. before with asyx twrp, twrp would delete all system files and data if those two zip files werent flashed, especially when updating the rom or dirty flashing. so far so good keep it up.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Awesometic:
Yeah I'm using my TWRP and I agree that there's a performance issue. 😅 Will look into this problem.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bmwdroid:
I'd love to see camera first, cause that's what I need much more, than a fast booting TWRP. ;)

That I'm using only once a month or less and if it needs 40"' or 5' to start doesn't bother me.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] hinghing1113:
I have 2 questions. Do I need to install the patch, Tab3 oreo forced encryption disabler??

Second, do i need to uncheck auto reboot after install this twrp version?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bmwdroid:
1. Well I never installed so it seems not necessary

2. If you mean Odin flashing the TWRP, surely.

Otherwise the old stock recovery gets revived when auto rebooting and not into TWRP directly.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] fulleden:
Does this require root?

I can successfully get into TWRP and format Data but rebooting makes my T820 act as it were factory reset (boots up to setup wizard) and replaces TWRP with stock recovery. I'm not selecting read only mode when first opening TWRP. I'm not latest stock firmware
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Awesometic:
Hello.

Strange. Once you have installed TWRP recovery on your tablet then it should not be turned into the stock recovery again automatically. I believe.

Have you checked OEM unlock option in the Developer options menu? I don' know it is possible to enter the custom recovery without checking that option..
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] fulleden:
I agree. I didn't realize the stock recover could overwrite TWRP once you were able to boot into it. Yes, I did have the bootloader unlocked (by OEM unlock in Dev Options, not sure there's another way). I was using Odin to flash and even tried a few different versions. The tablet originally had the latest Oreo Rom. I tried downgrading it to an older Oreo and also tried a Nougant rom. I had to do a "Format Data", otherwise I would get a boot loop and it seems to me that this then forced a "factory reset" on the next restart where it would sit on the Samsung logo for a very long time. I tried several different angles. I could reboot from TWRP back into TWRP. I even tried flashing TWRP on top of TWRP. Every time I went to boot into Android, it would take forever while it was apparently performing a rebuild of something. I was trying to avoid root to avoid tripping Knox. My ultimate goal was to systemize an app using TWRP which I've done on several older Samsung tablets.

In the end, I flashed Magisk then everything worked on the first try. Booting into Android went quick and I still had TWRP. I tripped Knox but in the end I was able to get what I needed onto the tablet. All is fine now.

Thanks for your work on this TWRP recovery and for sticking around to help support it.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] fulleden:
For those having trouble exiting download mode and hitting volume up quickly enough to boot into recovery:

Before flashing TWRP, check the Odin options and make sure the Auto Restart flag is set. Hit the Start button to flash TWRP then within a few second, press and hold Volume-Up & Home. Do not touch the power button. As soon as TWRP is flashed, the tablet will restart and boot into recovery.

I've installed TWRP on many devices but never had a device where it was so difficult to go from volume down to exit download mode to volume up for recovery quick enough. Both buttons seem responsive so I don't know what the deal was.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Awesometic:
News on TWRP. :)

Firstly, I set my custom kernel to my TWRP before setting that to my ROM.

The new kernel has LA.UM.7.6.r1-07800-89xx.0 CAF tag merged.

So there's a performance improvement and so on but we can't feel that much on the recovery.

Above all, I am very satisfied with the faster recovery boot speed.

Will write the details on the ROM release later.

And I enabled F2FS file system successfully, so we can use F2FS file system on Galaxy Tab S3 from now on. I have been using this few days and it seems working well.

Before you switch to F2FS, please make sure you have a backup of the current partitions.

edit) And the following LineageOS will have the F2FS ready kernel too.

Enjoy, and let me know if you face any issues.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bmwdroid:
@Awesometic thx again very much.

Flashed it today via old TWRP.

Starting much faster. Brilliant work.

Switching fs I'll do when your next LOS update is published.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Awesometic:
Glad to hear it's working :)

Yeah after some tests I will upload the new ROM that has the new kernel soon.

I forgot that, the past ROMs can recognize F2FS but its built-in kernel is not prepared for F2FS 😅
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] kitty035:
Can this be flashed through the TWRP APP or does it have to be done by root adb shell command if I have ashyx TWRP already installed?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bmwdroid:
@kitty035 I did it my way.

Others Idk.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Dantzy:
When will there be an update?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bmwdroid:
When the dev tells us.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] enriquejones666:
Yes, I just did it and it worked fine.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] etere:
I begin to think that my problems depend on the twrp and not on the Roms: spontaneous reboots (only with the tablet in standby) until the device is completely locked... solve with the combination of the three keys and I start it again to find the battery on the ground... All this happens with the HevocOS 4.16, lineageOS 18.1 and 19.1.... I also reinstalled the twrp 3.6.0_09 via odin... Same behavior in all three android versions.

Please Awesometic, do the miracle!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bmwdroid:
Did you try another TWRP?

Mine is now on 3.6.... but with all the others I never had the problem you've got.

Although with Havoc 4.16 and LOS18.1 I encountered sudden reboots and freezings as well.

LOS19.1 is miles better regarding that.

Did you try to tweak CPU frequency 2 klicks down?

Improved mine a lot.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] etere:
No, nothing other awesometic twrp.....some indication about a specific twrp to try? I see tath a new one 3.6.1 is out....!

Wath can i do to try your CPU frequency?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bmwdroid:
Have root and use Kernel Adiutor from F-Droid.

3.6.1. out is just a general notification by TWRP team but doesn't mean this device specifically for which they made none.

Atm all for T825 are made by devs separately.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] etere:
Hello everyone. With Odin I uploaded the original Pie (the last official). Then I loaded the twrp again and on the next reboot always with twrp I deleted everything and installed at once lineage 19.1 + nikgpps+magisk. Never a reboot, consumed 14% in 30 hours with the screen off! Wonderful!!!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] wakka1:
Can someone help me please.i unlocked bootloader in developer option, flashed twrp using odin, tried to install lineageos rom, but it froze for 2 seconds before rebooting to twrp again..did the wipe and now my tablet is into infinite bootloop.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bmwdroid:
Answered here already.

Please try to avoid double posts (same question in different threads).