[RECOVERY][OFFICIAL] TWRP 3.5.0_9-0 [T710][T715][T715Y][T810][T815][T815Y]

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
Tweak to T710 and T715 only!

I seemed to have overlooked one last screen orientation-related flag in the BoardConfig.mk file that decides the orientation of the UI regardless of the X-Y axes flags. I copied over "TW_THEME := landscape_hdpi" line from the gts210 device trees when it should really be "TW_THEME := portrait_hdpi". Below are the updated builds, the aim of whichis for the interface to look like it does on phones:

Links moved to the OP.
 
Last edited:
  • Like
Reactions: mac231us and tripLr

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
Ok, the T710 and T715 builds in portrait orientation have been confirmed to work as intended. I have requested that the official builds be updated, but in the meantime you can find them linked in my signature under TWRP.
 
Last edited:

NeWONEx

Senior Member
Sep 29, 2014
697
163
73
Is Aroma displaying in portrait orientation while TWRP is in landscape? Which exact Aroma build are you trying to flash? Did this also occur on older versions of TWRP? Are you able to tap on Aroma's menus properly, or does the tap location not correspond to the place that Aroma thinks you tapped? I need more details to be able to help.

There is a chance that Aroma needs to be updated to TWRP 3.2.
I used lastest update for Open Gapps aroma but still it is in wrong orientation. See the video below. And thanks for your time.

https://photos.app.goo.gl/3MMIVtSo1nEPFzhD3
 

NeWONEx

Senior Member
Sep 29, 2014
697
163
73
Is Aroma displaying in portrait orientation while TWRP is in landscape?
No, both of them in landscape
Which exact Aroma build are you trying to flash? Did this also occur on older versions of TWRP?
I tried lastest Aroma Open Gapps which is AROMA (I'll look into it and update)
Are you able to tap on Aroma's menus properly, or does the tap location not correspond to the place that Aroma thinks you tapped?
I can tap but it is not corresponding to the right place.

Sent from my SM-T815 using Tapatalk
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
No, both of them in landscape

I tried lastest Aroma Open Gapps which is AROMA (I'll look into it and update)

I can tap but it is not corresponding to the right place.

Sent from my SM-T815 using Tapatalk
Just as I suspected, Aroma is oriented in landscape but it's receiving touch input as if it were in portrait. This problem isn't new: 3119 I just tried Aroma build 20171230 and I can confirm this problem on my T810 as well. Has any version of Aroma every worked for you on any version of TWRP? If yes please specify which version of each. It could be a bug in either Aroma or TWRP, I'll look into it deeper.

Edit: there's a developer who figured this out for an older Galaxy tablet almost a year ago. I'll see if he can help me, but if this is a problem on Aroma's end, its developer has stopped working on it around 6 months ago.
 
Last edited:

NeWONEx

Senior Member
Sep 29, 2014
697
163
73
Has any version of Aroma every worked for you on any version of TWRP? If yes please specify which version of each.

Edit: there's a developer who figured this out for an older Galaxy tablet almost a year ago. I'll see if he can help me, but if this is a problem on Aroma's end, its developer has stopped working on it around 6 months ago.
Aroma never work in the right orientation. I always use script to skip aroma GUI as it give me headache. and ashyx said it is related to Samsung end not aroma or TWRP. and he said he has nothing to do with it. btw it wont make a big deal if you change orientation, make it portrait, why not ? :eek:

Here is the bug:
MTP doesn't work while I'm running TWRP. it was work in ashyx build.(there is sign of connection but actually nothing appear)
 
Last edited:

msprenger

Senior Member
Aug 5, 2014
395
195
73
[email protected],

Got a question, when i try to perform a nandbackup via twrp, i always get an error when backing up System.
I do not know Now to solve that issue, because i do not want to install a new Rom without being able to create a Backup.

Any Solutions?

Thanks msprenger
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
[email protected],

Got a question, when i try to perform a nandbackup via twrp, i always get an error when backing up System.
I do not know Now to solve that issue, because i do not want to install a new Rom without being able to create a Backup.

Any Solutions?

Thanks msprenger
I need more details to be able to help: which variant do you have? what's the exact error? did the backup finish by itself or did the error stop the backup from continuing? Please post a log and screenshot if possible.
 

msprenger

Senior Member
Aug 5, 2014
395
195
73
I need more details to be able to help: which variant do you have? what's the exact error? did the backup finish by itself or did the error stop the backup from continuing? Please post a log and screenshot if possible.
Backup did not Stop, runs through but starting with backing up System...E: error...
I have 810 Variant..2015...
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
Backup did not Stop, runs through but starting with backing up System...E: error...
I have 810 Variant..2015...
In that case, please if you don't feel comfortable with this backup that you made with 3.2.1-0, flash an older version of TWRP that didn't encounter an error when backing up, make a separate backup with it, re-flash 3.2.1-0 and see if you can restore the backup you made with 3.2.1-0. That way you will still have the backup made with the older TWRP in case the backup with 3.2.1-0 fails to restore properly.
 
  • Like
Reactions: msprenger

msprenger

Senior Member
Aug 5, 2014
395
195
73
In that case, please if you don't feel comfortable with this backup that you made with 3.2.1-0, flash an older version of TWRP that didn't encounter an error when backing up, make a separate backup with it, re-flash 3.2.1-0 and see if you can restore the backup you made with 3.2.1-0. That way you will still have the backup made with the older TWRP in case the backup with 3.2.1-0 fails to restore properly.
Thank you I'll give it a shot ?
 
G

GuestD0747

Guest
I tried to flash it several times using ODIN on my T815, but every single time the device reboots, with an " <ID:0/005> RQT_CLOSE !!". I've enabled the developer options and USB debugging, but i cannot find the "OEM Unlock" slider, it's missing. I've also tried rebooting it into fast boot in order to send a "fastboot oem unlock" command but it boots normally. Tried on several computers.

UPDATE: Flashing back from Nougat to Marshmallow Stock didn't help.

Do i have to wait 7 days for the option to appear like with the Note 8/ S8?
 
Last edited:

ubergeek77

Senior Member
Oct 30, 2015
233
77
0
Did we really never resolve the landscape/portrait touchscreen issue with Aroma on the T810? It's driving me insane. OP mentioned that there was a portrait fix for T710 and T715. Will that fix really not work for the T810? I'm trying to build TWRP from source with this fix applied myself, but I've never built Android from source, and it's incredibly complex (not to mention cloning repositories and building stuff is going to take an obscene amount of time for new environments).

While waiting on that (though I have zero confidence in it working), I also tried a custom theme. But when I tried changing the rotation, I ended up cutting off the bottom half of the screen and had to revert the theme.

I'm really just looking for any solution here. Any solution at all. Even if it requires a custom TWRP theme of some sort, compiling from source, trying an experimental build, you name it.
 
Last edited:

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
Did we really never resolve the landscape/portrait touchscreen issue with Aroma on the T810? It's driving me insane. OP mentioned that there was a portrait fix for T710 and T715. Will that fix really not work for the T810? I'm trying to build TWRP from source with this fix applied myself, but I've never built Android from source, and it's incredibly complex (not to mention cloning repositories and building stuff is going to take an obscene amount of time for new environments).

While waiting on that (though I have zero confidence in it working), I also tried a custom theme. But when I tried changing the rotation, I ended up cutting off the bottom half of the screen and had to revert the theme.

I'm really just looking for any solution here. Any solution at all. Even if it requires a custom TWRP theme of some sort, compiling from source, trying an experimental build, you name it.
This has long been fixed when I bumped the version to 3.2.1-1.
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,322
6,211
263
tiny.cc
Great! Thank you for your dedication to keeping this tablet alive.

Where can I get a copy of the 3.2.1-1 build? As I said, I have a T810 (gts210wifi). I see you're the maintainer for the official TWRP builds, but I only see downloads for 3.2.1-0 for this device.
My mistake, I bumped it to 3.2.1-1 for T710 and T715 to avoid the landscape inconsistency. T810 and T815 are at 3.2.1-0 because they work as expected in landscape orientation.
 

ubergeek77

Senior Member
Oct 30, 2015
233
77
0
My mistake, I bumped it to 3.2.1-1 for T710 and T715 to avoid the landscape inconsistency. T810 and T815 are at 3.2.1-0 because they work as expected in landscape orientation.
Ok, I don't have the other versions of this tablet, so I'm assuming that means they were broken to some extent in landscape mode. But as I'm sure you're aware, flashable zips that use AROMA don't behave correctly with the touch screen. The UI elements are displayed as landscape, and stretch appropriately, but the touch inputs behave as though they're being displayed in portrait.

In my case, this is happening with this version of TWRP (3.2.1-0), on the T810, when flashing open_gapps-arm-8.1-aroma-20180527.zip, which uses AROMA version 2.70RC2.

Is there a workaround for this touchscreen issue that you know of?

By the way, I completely forgot to mention - adb and MTP in recovery does not work at all in this build of TWRP. I've tried across both Windows and Linux machines, and nothing I do works, even after enabling USB debugging and accepting my computer's fingerprint. It doesn't even show up as "offline" under "adb devices." It's as though the tablet isn't connected via USB at all, like the USB port is disabled. In another modified version of TWRP I used, MTP worked, but adb still didn't (and admittedly that build was a bit buggy).