[Magisk Rom][T83x] WETA 7.0 [SG4][Sep.11]
- Thread starter Mentalmuso
- Start date
Yeah it's normal, it's just the way I've done the mods, they need to be switched off which is done by default, but on first boot there is no data built for wetamod at that stage.
[emoji450]
It is, until I get my device back from warranty.
Be aware though, 1.1.1 is built off T835 firmware, and it doesn't connect with Samsung account very well. I think you need to be pre connected or something and not wipe data. I won't be basing off t835 in the future because of this.
V1.0 is based off t830 and is missing some UI WETA features.
[emoji450]
Cool. It's running fine on my 830. Don't use Samsung crap so that doesn't matter to me.
Installed v1.0. Aside from a little hiccups on first boot everything been smooth so far. I hope you get your tab back soon and update to the right base 
Are you able to compile from source? A thing that've driven crazy in the last few days is the latency problems with bluetooth controller (namely my Switch Pro Controller but it also might have to do with audio device latency, too). It seems that the cause is most likely stemming from bluetooth SSR_MAX_LATENCY value, default to 800ms which is too high and causes the lag. The value resides within' system/bt/bta/include/bta_hh_api.h and the name is BTA_HH_SSR_MAX_LATENCY_DEF 800. Based on what I've been reading around the minimal value which can be used is 24.
I managed to find the hex value in bluetooth.default.so and changed it to 24ms and it has eliminated the latency problem all together. It would be nicer if this can be done from source.
(src: https://www.reddit.com/r/EmulationO...ing_joycon_bluetooth_lag_fix_on_android_play/).
Are you able to compile from source? A thing that've driven crazy in the last few days is the latency problems with bluetooth controller (namely my Switch Pro Controller but it also might have to do with audio device latency, too). It seems that the cause is most likely stemming from bluetooth SSR_MAX_LATENCY value, default to 800ms which is too high and causes the lag. The value resides within' system/bt/bta/include/bta_hh_api.h and the name is BTA_HH_SSR_MAX_LATENCY_DEF 800. Based on what I've been reading around the minimal value which can be used is 24.
I managed to find the hex value in bluetooth.default.so and changed it to 24ms and it has eliminated the latency problem all together. It would be nicer if this can be done from source.
(src: https://www.reddit.com/r/EmulationO...ing_joycon_bluetooth_lag_fix_on_android_play/).
Last edited:
Oh really? Good stuff! I have a kernel I built from source if that's what you're meaning. I can't remember whether I included it in the rom or not, I think I was on the verge of including it but stuff cane up..Installed v1.0. Aside from a little hiccups on first boot everything been smooth so far. I hope you get your tab back soon and update to the right base
Are you able to compile from source? A thing that've driven crazy in the last few days is the latency problems with bluetooth controller (namely my Switch Pro Controller but it also might have to do with audio device latency, too). It seems that the cause is most likely stemming from bluetooth SSR_MAX_LATENCY value, default to 800ms which is too high and causes the lag. The value resides within' system/bt/bta/include/bta_hh_api.h and the name is BTA_HH_SSR_MAX_LATENCY_DEF 800. Based on what I've been reading around the minimal value which can be used is 24.
I managed to find the hex value in bluetooth.default.so and changed it to 24ms and it has eliminated the latency problem all together. It would be nicer if this can be done from source.
(src: https://www.reddit.com/r/EmulationO...ing_joycon_bluetooth_lag_fix_on_android_play/).
I don't see anything wrong with simply hex editing to fix the Bluetooth though, building a rom from aosp source would just lose too many Samsung features, including the spen pressure sensitivity
Sent from my SM-N9600 using Tapatalk
My device is back from warranty. I'll be updating this weekend I think.
[emoji450]
[emoji450]
Just out of curiosity, didn't they refuse your warranty after triggering the Knox counter?
Nope. Cool huh.
It also had a different CSC on it to stock USA. They replaced the whole motherboard to fix it.
[emoji450]
Last edited:
Sorry I’ve always rooted my devices never ever once have i flashed a Rom (Sorry I’m a bit confused) I’ve got two files t835_vendor.img and WETA_T83x_1.1.1 as my model is T835 do i flash both files ? Which one do i flash first ? Also I’m on stock Android Oreo 8.1 i am rooted can someone please let me know ? Thanks
WETA 2.0
Updated base to SA3 (T830)(Jan sec)
All mods from the t835 based 1.1 rom included in 2.0.
Samsung account works.
WETA custom kernel.
Magisk 18.1
Download page
[emoji450]
Updated base to SA3 (T830)(Jan sec)
All mods from the t835 based 1.1 rom included in 2.0.
Samsung account works.
WETA custom kernel.
Magisk 18.1
Download page
[emoji450]
Hello Mentalmuso,
Thank you for your work. I use version 1.1
I would like to know if dolby atmos works with this version ?
Thank you for your work. I use version 1.1
I would like to know if dolby atmos works with this version ?
I keep getting the acore process has stopped responding error
I dirty flashed and did the following:
1. rebooted to recovery
2. flashed boot img
3. flashed vendor img
4. rebooted recovery
5. flashed rom
6. flashed magisk
7. cleared caches
8. rebooted to system
As soon as I rebooted to system i started to get that error
Thoughts?
I dirty flashed and did the following:
1. rebooted to recovery
2. flashed boot img
3. flashed vendor img
4. rebooted recovery
5. flashed rom
6. flashed magisk
7. cleared caches
8. rebooted to system
As soon as I rebooted to system i started to get that error
Thoughts?
Why did you flash boot.img?
Also what device? If it's T835 that may be the problem
[emoji450]
Because you said to
Edit 2
Looks like you were quoting someone's else to flash boot. I didn't seem you quoting him. That's why I flashed it
And no I'm running a 830
Edit
It seems to have stopped now. On the first boot after flashing it was constantly coming up. But after it settled and a reboot. I haven't seen it since. Will report back if it happens again
Last edited:
Can we dirty flash the latest update? If so, is it as done at booting to recovery, flashing rom, then magisk?
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