New Android Headunit A007_C56 2.2Ghz Octa 128GB+8GB

New Android Headunit A007_C56 2.2Ghz Octa 128GB+8GB - Android Head-Units

ANDROID:202211081700 (4G) 12 (fake 10)
MCU:MLO-mtk_C56_whe02d-aAaAaA_473X-CC568091-8A 20221221
Model: A007_C56_HA11_U859-EN-D_2022-11-08-1652
Octo 2.2Ghz 128GB+8GB 4G LTE on board.
Recently bought this headunit from Alli. It is a very quick unit although it comes with a lot of behind the scenes bloat and I have so far been unable to root and ADB does not work.
My main problem is an app called TXZ VOICE. It is interfering with android assistant. It is installed as a system app and I am unable to remove or disable it. As is the case with many of the other bloat apps.
I guess I'll have to wait for the community to pick it up. But what little information I have learned is the factory code 99992. A testing mode that appears to have an ADB shell, however it will not remove or disable apps.
Any insight would be greatly appreciated

If an ADB shell is provided, then check device's system file build.prop for the follwing entries
ro.build.type=userdebug
ro.debuggable=1
ro.secure=0
Click to expand...
Click to collapse
to check whether you can debloat Android or not.

jwoegerbauer said:
If an ADB shell is provided, then check device's system file build.prop for the follwing entries
to check whether you can debloat Android or not.
Click to expand...
Click to collapse
Thank you for the reply.
ro.build.type=userdebug
ro.debuggable=1
ro.secure=1
So I guess there's the answer.
The bootloader does seem to be unlocked however. I think there is a custom bootloader installed but I can't access it.

A device's bootloader ( Linux kernel ) and device's Android OS are totally different things.
If I understood it well then you want to debloat Android OS: this gets done via ADB ( read: Android Debug Bridge ).

Yeah. I was just adding any information I know about this headunit. My hope is perhaps it may be possible to flash new firmware in the future.

Related

[unofficial][linux3.4][native][tarchive][multirom]ArchLinuxARM release for N7 2013

This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483

looks interesting will give it a crack and see how it goes

thanks for the work. it boots impressingly fast.
castrwilliam said:
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Click to expand...
Click to collapse
if I activate the onboard keyboard ist shows at the bottom of the login screen. login works without password. when beeing logged in the keyboard is gone. I can see the keyboard symbol on the left besinde the speaker symbol but tapping on it doesn't trigger anything. also changing any options in the control center -> onboard settings have no effects. logging in without keyboard activated and then control center -> onboard settings has no effects either.
I cannot "adb shell" due to lack of permissions
Code:
# adb devices
List of devices attached
???????????? no permissions
and I'm not owning a bluetooth keyboard. so right now I can only play minesweeper - oh wait, it's not installed...

is there any way to rotate the screen as its really annoying having it in portrait all the time

Toby0897 said:
is there any way to rotate the screen as its really annoying having it in portrait all the time
Click to expand...
Click to collapse
Yeah it is in the monitor options but it's worthless since Xorg crashes when changing the rotation

Great stuff!
I would remove the KDE plasma etc packages as that desktop seemed to unusable. (Due to broken hw acceleration?).
what's next?

Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!

hugomc92 said:
Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!
Click to expand...
Click to collapse
You will need to install busybox for tar to work

daringblaze said:
You will need to install busybox for tar to work
Click to expand...
Click to collapse
Thank you very much!! That make tar to work!!
Gonna try archLinux ASAP!!
Thanks!

updates
Hi, great stuff!
After installing it, I tried to update arch (
Code:
sudo pacman -Syu
) but this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!

computer-whisperer said:
this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!
Click to expand...
Click to collapse
Make sure you ignore xorg and mesa stuff. Add
Code:
IgnorePkg = glu mesa mesa-dri mesa-libgl xorg-server-common xorg-server-devel xorg-fonts-misc xproto libdrm
IgnoreGroup = xorg
to /etc/pacman.conf.
The list probably contains some extra entries, but works for me

It took xda 2 years, but they finally did it.
In all seriousness, props to you. I've been waiting for this for along time.

castrwilliam said:
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/......
Click to expand...
Click to collapse
Hi castrwilliam, would you mind sharing what step you went through to create arch_flo_20141210_multirom.tar.gz ?

Great work guys! I was looking for this for a really long time and i am writing this on my n7 with linux but i have a few questions:
1. is it possible to overclock(and how) because my n7 runs on 1.89ghz and 477mhz gpu in android with elementalx kernel and it would be nice to have some more power
2. can the screen be rotated so the hardware buttons are on top (i saw a post saying it chrashes but i cant even find the setting xD) because it would be alot easier to use the OTG cable
And thank you guys for making this happen, i love linux on the note 10.1 and im so glad to have this run it too(would be maaad if it can be overclocked )

Thank you for this wonderful package!
I recently updated all packages ) and iam trying to fix the issue without reinstall (challenge accepted)
It seems that the xorg-server 1.17 is the problem. I compiled. Freedreno and the freedreno mesa 10.3 and libdrn packages without success. The xserver is segfaulting when it loads libexa.so.
Now i try to downgrade to 1.16 . ive read that the xf86-video-freedreno-git package is not working with flo. Is that correct? Did youbuild this packages with modificationa?
I believe this is why i love arch. Its like lego for nerds or something

castrwilliam said:
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Click to expand...
Click to collapse
What's NOT working

Hello, is there some instruction howto run (native) arch on nexus 4? I see only for n7, n10...

Hello, I have some trouble when I boot.
config: rastapop 5.1.1 (AOSP based) + last multirom v32A + Kernel w/ kexec-hardboot patch (Stock 5.1.1)
Installing archlinux correctly from the terminal emulator. Load it --> black screen (about 6seconds) --> Google Logo forever
Someone know what I can do for make it work ?

Cool I will give it a try.

Help- split screen Android 7.1.2!!

Hey folks!
I just bought 10.1 Android screen with GPS running Android version 7.1.2, processor type: Ultra Octa-T8
my question is:
How to split the screen (running two apps simultaneously )? Is there any app can do the split?
Thanks in advance,

Android7 supports split screen by default, so no special application is needed.
BUT Since T8's firmware has freeform mode enabled, you can not use split screen unless it is invalidated.
If you can use ADB, you can override freeform mode with the following syntax
adb shell delete global enable_freeform_support
But stock firmware will not be able to use ADB.
I would like to know if there is a good way...

warata said:
Android7 supports split screen by default, so no special application is needed.
BUT Since T8's firmware has freeform mode enabled, you can not use split screen unless it is invalidated.
If you can use ADB, you can override freeform mode with the following syntax
adb shell delete global enable_freeform_support
But stock firmware will not be able to use ADB.
I would like to know if there is a good way...
Click to expand...
Click to collapse
thanks for the reply,
How can I override freeform mode with the following syntax
adb shell delete global enable_freeform_support
Do you mean I have to root the screen?
would you please give more details I am new this world

MoMo131 said:
thanks for the reply,
How can I override freeform mode with the following syntax
adb shell delete global enable_freeform_support
Do you mean I have to root the screen?
would you please give more details I am new this world
Click to expand...
Click to collapse
Is this what you mean??:
https://www.youtube.com/watch?v=MRHyH9anr4c

MoMo131 said:
Is this what you mean??:
https://www.youtube.com/watch?v=MRHyH9anr4c
Click to expand...
Click to collapse
That's right buddy.In freeform mode you can use it immediately in stock ROM.
But its function is not quite useful in car stereos.
If you can disable free form mode it should be possible to use split mode.
But I am not a developer, nor is it familiar to Android.
I think that it is better for you to come to this thread for better advice.
https://forum.xda-developers.com/an...ecity-vw-allwinner-t8-2gb-32gb-7-1-2-t3704290

[Guide] How to Enable Miracast for Pixel

Introduction
Few weeks ago, I got a Pixel 1 as my backup phone, when I try to connect it to the Microsoft Wireless Display Adapter, it couldn't find the Adapter.
I haven't used Android phones for a long time. In my mind, Android natively supports Miracast. After some searching, I was frightened to find that Google has removed Miracast from Android.
I was really disappointed because I often cast my Windows devices easily by using Miracast. My Projector has only two HDMI ports, one for HDMI cable, and one for Wireless Display Adapter. I can't add a Chromecast unless a HDMI switch is used.
One possible solution is to add a line "persist.debug.wfd.enable=1" in "build.prop" to enable WiFi-Display, but many people say that it doesn't work since Android N, the phone can discover WiFi-Displays but unable to cast.
Since Android framework is open source, I did some searching and found that some WiFi-Display related code still exists. Android 9 still keeps the WifiDisplayAdapter in DisplayManagerService, but removed WifiDisplay from MediaPlayerService, that's why we can discover WiFi-Displays but can't cast.
I recovered some code from AOSP history commits, fixed the build errors, and debugged on my Pixel, finally the Miracast can work on my Pixel.
If you also want Miracast to work on your Google phones, you can follow my steps, but first make sure your ROM is open source so that you can change and rebuild it.
If you have a Pixel 1 running the same version of system, you can simply replace some files in your system with the files I built.
If you have other Google phones or running different versions, you can apply my patch to AOSP, and build it by yourself. I have built the latest version for all Google Pixel phones, but I haven't tested except Pixel 1.
If your ROM is not open source, I will no longer be able to help, since MediaPlayerService may have been changed by your ROM, you may can't replace it with the AOSP version.
Prerequisites
Pixel running Android 9.0.0 build number PQ1A.181205.002.A1 or PQ1A.190105.004.
Bootloader unlocked.
adb and fastboot tools and drivers are working for your device.
Note & Disclaimer
These steps will change files in your system, your Pixel should run the exact same version of system. Pushing files to different versions of system may cause unknown problems.
Please check carefully before running each command, a mistaken operation may result in unable to boot up, or destroy your data, or even damage your phone.
If you are not sure about what these steps are doing, but still want to go ahead, please backup your phone firstly, you may not be able to recover your phone to its original state.
I have only tested on Pixel 1 with build number PQ1A.181205.002.A1 and PQ1A.190105.004, for other phones or versions, you should build and test on your own.
Basic Steps
Flash the same version of factory image for your phone.
Download the prebuilt files from https://github.com/sbjbs/android-wfd-patch
Add this line into "build.prop", without it, we will not be able to enable WiFi-Display:
Code:
persist.debug.wfd.enable=1
Replace some files in system:
Code:
system/lib/libaudioflinger.so
system/lib64/libaudioflinger.so
system/lib/libserviceutility.so
system/lib64/libserviceutility.so
system/lib/libmedia.so
system/lib64/libmedia.so
system/lib/libwilhelm.so
system/lib64/libwilhelm.so
system/lib/libandroid_runtime.so
system/lib64/libandroid_runtime.so
system/lib/libstagefright.so
system/lib64/libstagefright.so
system/lib/libstagefright_wfd.so
system/lib64/libstagefright_wfd.so
system/lib/libmediaplayerservice.so
If you have magisk installed, you can refer to Phoenix Wright's post:
Phoenix Wright said:
using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent.
using magisk to overlay them on /system
Click to expand...
Click to collapse
Some extra steps that you may need
Remove dm-verity metadata of system.img
The dm-verity can prevent us from changing the system, and what's more it has a forward-error-correction(FEC) feature, which can detect and correct some corrupted data.
I spend a lot of time on attempting to change the build.prop but fail again and again, it just always correct the file, and I can't enable wifi-display.
I don't know how to disable it. Since the error-correcting info should be stored in the dm-verity metadata, I just removed the dm-verity metadata from the stock system.img, and flash the system.img.
I will list the steps to remove dm-verity metadata, but if you can disable dm-verity entirely, that should work too.
For phones that have a vbmeta partition (like Pixel 2), seems you can flash an special vbmeta.img to disable AVB. You can build the empty vbmeta image by this command, but I don't have a device to test if it works:
Code:
avbtool make_vbmeta_image --flag 2 --padding_size 4096 --output vbmeta.img
For Pixel 1, we need to remove dm-verity metadata that attached to system.img, first convert the sparse system.img to an ext4 image:
Code:
simg2img system.img system.ext4.img
read the block count to calculate the system size:
Code:
od -j 1028 -An -N4 -tu system.ext4.img
for Pixel 1, it should be 516099. You also can read it by a Hex Editor, e.g., WinHEX in Windows, read 4 bytes starting from 1028 bytes, as a little-endian hex value.
so the real system partition size is 516099 * 4096 = 2113941504 bytes.
we need to set the data to zero after that position. It's important to do this, since we need to overwrite the metadata in that area, rather than just truncate the size of system.img.
next get the ext4 image size, for Pixel PQ1A.181205.002.A1, it should be 2147483648.
so we need to write 2147483648 - 2113941504 = 33542144 bytes：
Code:
dd if=/dev/zero of=system.ext4.img seek=2113941504 count=33542144 oflag=seek_bytes iflag=count_bytes
we also can use some other tools to do this, e.g., WinHEX in Windows. Open the file in in-place mode, and jump to 2113941504, and select it as the begin, and jump to the end, and select as the end, and fill the selection with all zero.
after that, flash the changed system.ext4.img to Pixel:
Code:
fastboot flash system system.ext4.img
Test that you can boot up normally. If not, check what's wrong and fix it.
Temporary boot up by TWRP image
We don't have to install TWRP, but just use it to temporary boot up, so that we can mount the system partition for writing. If you have TWRP installed, you can just boot to TWRP.
Download TWRP image for pixel, just need the twrp.img, we won't install the zip file.
boot your device to bootloader:
Code:
adb reboot bootloader
and boot by the twrp.img
Code:
fastboot boot twrp.img
after TWRP booted up, just leave it there, no need to unlock or input password, we will change the system by adb.
Mount system partition for writing.
In the current version of TWRP for Pixel (twrp-3.2.3-1-sailfish.img), its fstab has an entry for system partition, we can directly mount it.
Code:
adb shell mount /system
run mount to check if successfully mounted:
Code:
adb shell mount
you should see an entry like this:
Code:
/dev/block/sda34 on /system type ext4 (rw,seclabel,relatime)
If not, you should stop now, and check the above steps.
after mount, we can use adb to push files into system.

Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel

jean_michmich said:
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
Click to expand...
Click to collapse
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.

sbjbs said:
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
Click to expand...
Click to collapse
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).

jean_michmich said:
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
Click to expand...
Click to collapse
I used to be a ‘latest official ROM’ user
For custom ROMs, since they may have changed the framework, we can't replace files with AOSP version, but as long as they're open source, we can try to contribute to it.
Adding Miracast support in Android is not difficult, and many manufactures have their own support.
I hope your custom ROM will support Miracast for Pie in the near future.

Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.

Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs

spezi77 said:
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
Click to expand...
Click to collapse
There's a link in the OP: https://github.com/sbjbs/android-wfd-patch/tree/master/patches/android-9.0.0

Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Great to hear that!
You method is simpler and more elegant, that's awesome!

Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin

nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.

nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.

Phoenix Wright said:
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
Click to expand...
Click to collapse
Thanks!
sbjbs said:
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Click to expand...
Click to collapse
I tried building with my ROM but I got build errors related to OMX.h, I need to find a solution for them. Thanks anyways!
Nitin

Someone tries on Pixel 3? Thanks

It works perfectly ! I used the prebuilt files on the march build.
Do you know if we can force the 16/9 ratio ?
Thanks
edit : I will try with second screens !

this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....

marshyrob said:
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
Click to expand...
Click to collapse
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?

EMJI79 said:
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
Click to expand...
Click to collapse
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.

marshyrob said:
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
Click to expand...
Click to collapse
It did work today with my Sony television.
Thanks!

OMG!!! You made my week. Few hiccups tho....
Can anyone else confirm that Hulu and HBO go and Amazon prime . YouTube works.
Hulu and amazon I can log on but when it plays all you get is audio. Haven't tried Netflix I don't sub them.
HBO go as soon as I try to play a video it says this video cannot be played. If I disable the mirror it plays perfectly. Same thing with Hulu and prime. Disable the mirror an it works perfectly on my phone.

[Guide] How to enable wifi tethering

This guide is for academic and development purposes only and should not be used to circumvent any contracts you have with you cell carrier.
You need to be rooted in order to enable wifi tethering.
Rooting and editing your stock image voids most warranties.
Follow this guide at your own risk. (I can't take responsibility for you braking your phone)
1. Install a Build.prop editor(this isn't mandatory but I find it makes things easier) I use this one: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_US
2. add the following line to the build prop: net.tethering.noprovisioning=true
3. Reboot your phone
4. Profit

SAVED

dtb1987 said:
2. add the following line to the build prop: net.tethering.noprovisioning=true
Click to expand...
Click to collapse
Which section of the build prop did you put it in?

gargleblarg said:
Which section of the build prop did you put it in?
Click to expand...
Click to collapse
I normally put it at the end

dtb1987 said:
I normally put it at the end
Click to expand...
Click to collapse
Thanks, it works like a charm .

Note, if you are running Magisk, you shouldn't update the build prop directly, which modifies the system partition so you can no longer use an OTA update.
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true
Added to this directory...
/data/adb/service.d/
or if it doesn't work there, move to this directory...
/data/adb/post-fs-data.d/
I have not tested this myself, but it is how you are supposed to change build prop when using Magisk. Do your own research to make this work properly...

duh1 said:
Note, if you are running Magisk, you shouldn't update the build prop directly, which modifies the system partition so you can no longer use an OTA update.
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true
Added to this directory...
/data/adb/service.d/
or if it doesn't work there, move to this directory...
/data/adb/post-fs-data.d/
I have not tested this myself, but it is how you are supposed to change build prop when using Magisk. Do your own research to make this work properly...
Click to expand...
Click to collapse
You shouldn't OTA update a rooted phone to begin with because those updates don't account for changes you may have made. you should be downloading the updates from here: https://developers.google.com/android/images and flashing them manually

dtb1987 said:
You shouldn't OTA update a rooted phone to begin with because those updates don't account for changes you may have made. you should be downloading the updates from here: https://developers.google.com/android/images and flashing them manually
Click to expand...
Click to collapse
You can't run an OTA update on a modified boot image. You use Magisk to revert the boot image back to stock, run the update and re-root. Since it's a systemless root and you don't modify anything directly in the system image, therefore you don't have to revert back to stock system.
I was just offering a quick heads up for those who may be rooted with Magisk, on how to properly modify the build prop without modifying system directly. It's a good thing to learn since many times you'll have to modify those init scripts anyway.

How do I add it to magisk, I'm totally new to it.

Question: I currently have AT&T's (really lame) tethering plan, and my data plan is capped at 5GB data (for my business, AT&T does not offer an unlimited data plan with tethering). So I currently have the ability to turn on/off the Wifi hotspot setting in the phone Settings.
I just rooted the phone and did your update. To test success, I now have to change my plan to unlimited data (no tethering). When I do this, I should be able to still turn on/off the Wifi hotspot via the phone Settings (even though I no longer have the plan with the tethering feature)? Thank you.

issues with Android 10?
Hi, I followed these instructions and all is good.... But I'm stuck on Android 9, holding off on moving to Android 10 due to what I've read in other posts about this technique no longer working. Thought I'd check back to see if anyone has had success upgrading to Android 10 - and enabling wifi tethering via the technique mentioned above. Thanks.

Tethering on Android 10
This works for me on Android 10. It systemless-ly adds the
Code:
net.tethering.noprovisioning=true
line using the resetprop command, and it also runs
Code:
settings put global tether_dun_required 0
which prevents your phone from marking tethered data as such. This makes it harder for your carrier to throttle or block tethered data.
Just keep in mind that if your carrier really cares about tethering, they can still tell through TTL (for IPv4) or Hop Limit (for IPv6) whether or not the traffic is coming from your phone or an attached device. This can be circumvented by setting TTL/Hop Limit on the client devices to 65 before connecting to the hotspot.

DaBigGoog said:
This works for me on Android 10. It systemless-ly adds the
Code:
net.tethering.noprovisioning=true
line using the resetprop command, and it also runs
Code:
settings put global tether_dun_required 0
which prevents your phone from marking tethered data as such. This makes it harder for your carrier to throttle or block tethered data.
Just keep in mind that if your carrier really cares about tethering, they can still tell through TTL (for IPv4) or Hop Limit (for IPv6) whether or not the traffic is coming from your phone or an attached device. This can be circumvented by setting TTL/Hop Limit on the client devices to 65 before connecting to the hotspot.
Click to expand...
Click to collapse
Awesome - thank you!

saved

duh1 said:
Note, if you are running Magisk, you shouldn't update the build prop directly, which modifies the system partition so you can no longer use an OTA update.
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true
Added to this directory...
/data/adb/service.d/
or if it doesn't work there, move to this directory...
/data/adb/post-fs-data.d/
I have not tested this myself, but it is how you are supposed to change build prop when using Magisk. Do your own research to make this work properly...
Click to expand...
Click to collapse
I don't understand how to do this or what it means. I have root magisk on sm-a235f
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true

Eonon GA2175

Hello everyone.
For my first post here I'd like to share and learn more about rooting the EONON GA2175. This Android HU currently operating with Oreo on a RK3326_mid chipset. So after an exhaustive search, there is not much information available in rooting this system. It seems that's this HU seems to be almost completely locked down. For starters, I wasn't able to even access developer mode through the build number as usual. I was finally able to get through by installing a developer access app called "Developer Options Shortcut & Device Info" on the app store.
Using one click apps like Kingo Root, Root Master or Towel Root are completely ineffective. As a matter of fact, Root Master says my "phone is too strong"
I tried connecting the unit to a laptop by using a male to male USB cable. But both my laptop of the HU do not recognize each other. Maybe some drivers may help but none are available.
I've watched you tube videos that demonstrating other people rooting similar units by accessing the safe boot option then loading TWRP on a SD card. I believe this is the only way to root these units. However, for this unit I am unable to access safe mode. I've discovered that holding the "Vol/PWR" knob for approximately 10 sec will cause it to start blinking but combinations with the "RST" button, home or quick pressing the "PWR" doesn't work. That's as far as I got.
I hope this helps anyone with the same unit but any help with my roadblock will be greatly appreciated.
Thanx!

UPDATE
So I finally managed to get to recovery mode on this device.
1. With a tooth pick, quick press the "RST" button.
2. Long press the "PWR/VOL" knob for approximately 10secs until the lights blink.
3. Then immediately quick press the "PWR/VOL"
You may need to do it more than once but it'll work.
Well.... now what TWRP version should I use?
I didn't see my HU listed.
Or should I use a different program?

did you end up getting something to work?
Mark

Not yet.
I did manage to find some unit specifics. I'll post them shortly. Maybe some coder can do something with that info. Where I run into a roadblock is that I cannot find a suitable ROM and MCU.

If this help to figure things out.
BOARD : rk30sdk
SERIAL : 77A6117127A8F7B2
eng.hct.20181229.163118
eng.hct.20181229.163118
DEVICE: rk3326_mid
HOST : r930
MODEL : rk3326_mid
RELEASE : 8.1.0
MANUFACTURER: rockchip
USER : hct
BUILD NUMBER: PX30 8.1.0 OPM8.181105.002 eng.hct.20181229.163118
CPU_ABI: arm64-v8a ; Quad-Core [email protected]
MEMORY: 1960MB
BRAND : rockchip
SDK_INT: 27
DISPLAY : rk3326_mid-userdebug 8.1.0 OPM8.181105.002 eng.hct.20181229.163118 test-keys
FINGERPRINT: rockchip/rk3326_mid/rk3326_mid:8.1.0/OPM8.181105.002/hct12291631:userdebug/test-keys
HARDWARE: rk30board
PRODUCT : rk3326_mid
BOOTLOADER : unknown
REL: REL
ID: OPM8.181105.002
UNKNOWN: unknown
TYPE : userdebug
TAGS : test-keys
MCU VERSION: MTCE_HT_V2.99_1
November 18, 2018 19:03:43

Root Path info
Root Access:
No Access
SU:
su found
UID/GID:
uid=10105(u0_a105) gid=10105(u0_a105) groups=10105(u0_a105),3003(inet),9997(everybody),20105(u0_a105_cache),50105(all_a105) context=u:r:untrusted_app:s0:c512,c768
Utils:
busybox
toybox
toolbox
Path:
/sbin
/system/sbin
/system/bin
/system/xbin
/vendor/bin
/vendor/xbin
Path:
[/system/xbin/su]
Version:
/system/bin/sh: <stdin>[16]: /system/xbin/su: can't execute: Permission denied
Permissions:
rwsr-x---
Owner:
root:shell
SELinux:
Permissive
Path:
[/system/bin/busybox]
Permissions:
rwxr-xr-x
Owner:
root:shell

Get any further with this, wouldn't mind a custom ROM for mine although i'm pretty happy how it works now.

Actually yes!! Type "ADBON" in factory setting password to access developer options. It works. Thanks Ric69!

Database Users

welcome