Database Info

[Q] Camera Swap on rooted TF101

Hi - NaN (not a noob) to software and hacking but new to this device.
I have a rooted TF101 and wonder if anyone's hacked the device so that the front camera becomes the rear and the rear camera becomes the front.
Really just curious before I go ahead and brick my device. I'm thinking about mv /dev/ov5640 and /dev/tegra_camera but that sounds far too easy (and dangerous)...

Why would You be interested in swapping the cameras anyways? Seems to be a biit pointless to me as every app ive used with cameras it had support to use front or back.
Sent from my Transformer TF101 using xda premium

I agree
kenshin1388 said:
Why would You be interested in swapping the cameras anyways? Seems to be a biit pointless to me as every app ive used with cameras it had support to use front or back.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I agree to this, there is no point to make the change.

Well for starters Opera 12, which includes support for getUserMedia() WebRTC extensions uses the first webcam it comes across, the rear. If I wanted to even make a mock up of a video call I would need the front camera (granted this is only good for the lab, not production).
But really I was trying to understand how the underlying media device capability works. If you simply exchange using mv /dev/mi1040 (the front camera device) and /dev/ov5640 (back camera) then it goofs the images to any app that uses cameras.
There must therefore be other layer(s) determining device capabilities, codecs, etc.
There's a file /etc/nvcamera.conf but that only seems to affect the main camera app. I swapped 1 and 0 and front and back tags, although admittedly haven't yet swapped the device ID whilst leaving the front/back tags the same.
And there's a whopping /etc/media_profiles.xml defining all the camera capabilities.
Do I need a reason? Isn't anyone even just curious doing something to push the device and learn more about the platform???

There was a point where Yahoo IM would use the back camera (when it was avaiable native to the TF). There was a member "droidx" he modified some files and got the front camera working with it. You're better off looking at modifying files as oppose to rewiring cameras.
More info here
http://forum.xda-developers.com/showthread.php?t=1087769

How to swap the cameras so Opera 12 uses front camera for getUserMedia()
Ok, here's how I did it.
Essentially you only need to swap the tags 'front' and 'back' in the file /etc/nvcamera.conf
The change is permanent across reboots, but messes the orientation/mirror image of the cameras, so the rear camera becomes a mirror image, not the front. This messes all portrait shots as the camera pic becomes upside down.
Device needs to be rooted.
Need to make /system directory read/write:
# mount -o rw,remount /system
# vi /etc/nvcamera.conf# format, cameraName=device,direction,orientation,type
This is the file before mods
# type can be 'stereo' for stereo capable, 'mono' for not stereo capable,
# 'usb' to enable searching for a usb device and where to put it in the list
# if found. Lines must be shorter then 256 characters
version=1
camera0=/dev/ov5640,back,0,mono
#camera1=/dev/ov5650,back,0,mono // 2nd camera for stereo once supported
camera1=/dev/mi1040,front,0,mono
#camera4=/dev/ov5650,back,0,stereo // virtual stereo device once supported
Change this line:
camera0=/dev/ov5640,back,0,mono
to:
camera0=/dev/ov5640,front,0,mono
And this line:
camera1=/dev/mi1040,front,0,mono
to:
camera1=/dev/mi1040,back,0,mono
Save and it works.

Please remove :/

No keep it, that's a good thing to have available to see or as a project. I love to learn things like this.

Thing O Doom said:
No keep it, that's a good thing to have available to see or as a project. I love to learn things like this.
Click to expand...
Click to collapse
I second doom. It's about pushing the limits of the device.
Good on ya for doing this.
Sent from my SCH-I500 using Tapatalk 2

I also agree. as some may not understand the reasoning, obviously oblonsky has a reason for doing this, just because everyone doesnt understand or agree with him is no reason to cut him off and remove his post... anything anyone learns or attempts to learn about android or the transformers code will progress understanding of the platform and the device. I vote let it stay and continue your endeavor fellow androidian.....

Yes, thanks guys. I'm already wondering now whether it may be possible to add new cameras, or disable cameras - do more useful stuff than swap cameras. Also I took the time to post the answer to my own question just in case it was useful to anyone else - so it would seem odd to want to remove the information that just *might* be useful to others at some point.

will this work on nougat......if not how to do it on nougat

Here is a reason to make the front camera the default camera: After getting in a terrible rain, my main camera on the back is not working anymore.
When starting a camera apps, it just quits with kind of a "connection to camera no possible" message.

Here's another reason to make the front camera as the default
I have a phone that's about 5 years old. It's been through heavy and rough usage. Hence, the connection between the motherboard and camera module are fried.
Now, when I have to login into WhatsApp Web or the WhatsApp App for Windows, I cannot because it needs a QR code scanned - which triggers the back camera.
So, I'm going to go ahead and try this, kudos!

Thanks for posting!
This was useful. Thanks. Please keep experimenting for no reasons.

SHUR1KEN said:
I have a phone that's about 5 years old. It's been through heavy and rough usage. Hence, the connection between the motherboard and camera module are fried.
Now, when I have to login into WhatsApp Web or the WhatsApp App for Windows, I cannot because it needs a QR code scanned - which triggers the back camera.
So, I'm going to go ahead and try this, kudos!
Click to expand...
Click to collapse
Uhm did it work?

Unfortunately, no, it didn't. Apparently, WhatsApp has gotten rid of the gate that used to allow for the "exploit" to happen before. I have heard of users doing it 2 years ago.
Anyway, what I had to do in my case was, I had to maintain pressure at the point on the camera module where it connects to the motherboard, while navigating to WhatsApp Web and scanning the QR code, all without even the most minute of movements. Otherwise the phone would fail to detect the camera module all over again, demanding me to repeat the whole thing again + a manual camera driver reset from my ROM settings.
Tried it like 20+ times. Succeeded in 1/20 of them... **** was tough, bro.

I finally managed to do this on my Redmi Note 5. This is probably applicable to most other devices as well.
Remount the system partition as writable:
Code:
$ su -c mount -o rw,remount /system
Edit /system/vendor/etc/camera/camera_config.xml and swap all
Code:
<Position>BACK</Position>
to
Code:
<Position>FRONT</Position>
and vice versa.
Reboot.

Do you think this will still work?
If I unroot after modifying the file, will the change persist?
Many thanks for your excellent work.

TheSnowpup said:
Do you think this will still work?
If I unroot after modifying the file, will the change persist?
Many thanks for your excellent work.
Click to expand...
Click to collapse
It still works for me at least. I think it will persist after unrooting, but I don't know how rooting works under the hood right now, so this may be incorrect.
If you try it, please report back your results!

[Kernel][GPL] Development 3.0 Kernel

Current state of 3.0 Kernel
WiFi/Thether/p2p - 100%
TouchScreen - 100%
Video Codec/hw 720p/ION stuff - 100%
Display/DSS - 100%
Phone/3G data - 100%
Sound/FM-Radio - 100%
F2FS support - 100%
GPU OC 266mhz - 100%
Bluetooth - 95%
USB - 98%, otg bugged.
Sensors - 98%, Need test all sensors, looks like all sensors works
Camera - 85%, Preview/Photo(Red have random problem)/Panorama works for both lenses. Video rec not work yet.
Overclock CPU- 0%, not implemented.
For CM10,10.1,10.2 < 07.11.13 users:
To install KitKat, need update recovery. Do not forget reboot, after install recovery.
http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
Tips:
Do not format System and Cache to F2FS!!!
1. To use f2fsl "/system/bin/mkfs.f2fs /dev/block/mmcblk1p25" or format via TWRP (Advanced wipe menu).
2. To restore ext4, in recovery unmount data, mount system, and do via adb shell /system/bin/make_ext4fs /dev/block/mmcblk1p25 or format via TWRP (Advanced wipe menu).
3. If you have 0 bytes free bug, reformat data to f2fs or ext3/4.
4. 1.1 Ghz can be enabled in performance settings.
Click to expand...
Click to collapse
If you liked this project, you can donate
Donate to Quarx
PayPal: [email protected]
---------------------------------------
Donate to Blechd0se
PayPal: [email protected]
Click to expand...
Click to collapse
Download: http://quarx2k.ru/index2.php?dir=buildbot/roms/defy-cm11.0-3.0
Sources of kernel availabe here(branch p-android-omap3-3.0): https://github.com/Quarx2k/jordan-kernel/tree/p-android-omap3-3.0

Changelog:
17.11:
Added timer slack controller
Added dynamic fsync
Added proportional rate reduction for TCP
Added opensource camera driver (mt9p012)
Added syspanic driver for panic_daemon
Added sync framework (together with ION its part of androids graphical "project butter")
Switched to SLUB allocator
Enabled ram console Support
Synced binder to mainline version (~3.10)
Fixed reboot while incoming or outcoming call (fix proximity sensor in general)
Many small performance patches and fixes for better android support all over the place
Logs or it didn't happen! If you want to report a problem, be sure to post a log file!
Here is a small guide when we need which log file and how to get it.
Old Changelog;
Added new extra_free_kbytes tuable (4.4 compatibility)
Added our Interactive Governor from 2.6.32 for additional performance
Added a basic display control driver
Added a dynamic writeback control interface
Enabled cgroups for memory (4.4 compatibility)
Enabled deadline and changed tunables to the same as on 2.6.32
Enabled xattr and fs security for ext3/4
Patched up trim (ext3/4) to the latest mainline version
Switched to XZ compression for a smaller kernel image
Reclaimed some RAM from logger and vram
*Fixed the wakeup delay and the "funny" screen on resume
TODO:
Add Overclock driver
Fix kpanic with pvr and dss (solved?)
Fix sleep problem
How To Build
Code:
git clone https://github.com/Quarx2k/jordan-kernel.git
cd jordan-kernel
git checkout --orphan p-android-omap3-3.0
git pull https://github.com/Quarx2k/jordan-kernel.git p-android-omap3-3.0
export CROSS_COMPILE=/path/to/your/toolchains/arm-eabi-4.6/bin/arm-eabi-
export ARCH=arm
make mapphone_defconfig
make -j12
Sys-Values explanation;
Let me explain some of this features a little bit. 3.0.8 offers completely new opportunities to do some magic stuff.
One thing i developed a while back ago is a dynamic writeback driver with a sys-interface. It uses the earlysuspend kernel api
to flush dirty pages more frequent when in suspend, while display is on it avoids it to give a more fluid user interface.
Can be controlled via the following command;
echo 1 > /sys/devices/virtual/misc/writeback/writeback_enabled
(1 for enabled = default, 0 for disabled)
Click to expand...
Click to collapse
Also new; a basic display driver! As i tried to fix some things in our dss driver i noticed that we have different panel configurations.One is for all defy green and one for defy red lense users. I exposed those values to user space so that they can be changed. The
new default one are those, which are used on the red lense defy. In theory there could be 256 values (0-255), however could only find the
following as useful. This is not the final gamma control i wanted to have, but at least it gives some control. If someone knows the proper
addresses for gamma values, i can add them too
echo xx > /sys/class/misc/display_control/display_brightness_value
(0 will set the screen to almost 0,
9 will set the screen to some kind of blue-washed colors,
31 will set the screen to more warmer colors = default)
Click to expand...
Click to collapse
In order to run 4.4 more fluid, google made a guide and also published some recommended patches. One of them let you change
the VM's behavior to have a minimum amount of free memory. Also controllable over a interface;
echo 8192 > /proc/sys/vm/extra_free_kbytes
Click to expand...
Click to collapse
8192 means 8 MB of free ram (in any case).

Thanks for this information
Gesendet von meinem Nexus 4 mit Tapatalk 2

If I may ask, @Quarx and @Blechdose: which one of these items are the hardest to solve at the moment?

a separate thread was really needed for 3.0.8 kernel.
thank u quarx and Blechd0se

matiasrey said:
If I may ask, @Quarx and @Blechdose: which one of these items are the hardest to solve at the moment?
Click to expand...
Click to collapse
I am guessing it's the Camera?

Honestly, i think its time to stop working on the 2.6.32 kernel and focus on 3.0.x, looking as an atrix user, its definetly the best choice devs could do. Hehe
Sent from my LG-E975 using Tapatalk

Once again, thanks!!!

@Quarx @Blechd0se About the camera... Quarx, you asked in a post somewhere about our opinions on whether you guys should try to set it up with an open-source driver or with the old Moto driver. Maybe you could tell us what would be the advantages and disadvantages of which one and we could even vote if you want us to?
I'm guessing that we could get more out of the camera with an open-source driver, but it would be harder to set-up than the Moto driver?

niksy+ said:
@Quarx @Blechd0se About the camera... Quarx, you asked in a post somewhere about our opinions on whether you guys should try to set it up with an open-source driver or with the old Moto driver. Maybe you could tell us what would be the advantages and disadvantages of which one and we could even vote if you want us to?
I'm guessing that we could get more out of the camera with an open-source driver, but it would be harder to set-up than the Moto driver?
Click to expand...
Click to collapse
its a 5mp camera, so we should go for the old moto drivers, easiest stuff to do right?

Once it works with open source driver for camera, free forever...
Sent from my Nexus 7 using xda app-developers app

I shouted "YES!!" out loud when I saw the commit about headset and microphone fixes! *edit* But the call speaker maybe isn't fixed just yet :/ Still, gotta try the new build when it shows up ^_^
(that's this one - https://github.com/Quarx2k/android_...mmit/8f5a44ca04ba1c005cb1ac2409639b62f6260d4e )
Combined with Blechd0se's stability fixes (especially this one that fixes the "deep sleep death" - https://github.com/Quarx2k/jordan-kernel/commit/f6b6de228a09f46ab7d6eff70f9225f88e7d3515 ) the next build is going to be very usable imho

niksy+ said:
I shouted "YES!!" out loud when I saw the commit about headset and microphone fixes! *edit* But the call speaker maybe isn't fixed just yet :/ Still, gotta try the new build when it shows up ^_^
(that's this one - https://github.com/Quarx2k/android_...mmit/8f5a44ca04ba1c005cb1ac2409639b62f6260d4e )
Combined with Blechd0se's stability fixes (especially this one that fixes the "deep sleep death" - https://github.com/Quarx2k/jordan-kernel/commit/f6b6de228a09f46ab7d6eff70f9225f88e7d3515 ) the next build is going to be very usable imho
Click to expand...
Click to collapse
Yes Quarx is doing a very good job here, still struggling with a last few bugs. Anyway, its progress! Also the huge battery drain should be fixed,
i disabled kmemleak. 3.0 is such a nice base to work with, no need to do hacky things, it just works out of the box.
Next version will have timer_slack controller (its working perfectly). Also many fixes for crashes and memory leaks.
One big thing is still the display. Although wakeup delay is gone for me, dss/pvr crashes sometimes. Its very random.
Also overclocking has two sides; on the one side its much easier to understand, on the other side it doesn't work as expected (can't overclock
to 1200mhz for example). But we have finally a nice voltage/frequency table.

Glad to read the good news, doesn´t seem too far from a usable kernel!
Have you decided what camera drivers you´ll go for?

F* yeah! "isl29030: fix reboot of proximity sensor" commit signed off by Blechd0se
Quarx has been focusing on the in-call sound issue today, so things are looking brighter by the day
*edit* I'm guessing more and more people use the thanks button as the like button

When I wake up in the morning and read Quarx github , appear "Add Micron MT9P012 sensor driver" , so I think we can hope at an camera soon...

OTG!!
In the description it says USB: 98%, "OTG" bugged. Does this mean we can connect pen drives, mouse and keyboards to our defy with this kernel?

mayur2j said:
In the description it says USB: 98%, "OTG" bugged. Does this mean we can connect pen drives, mouse and keyboards to our defy with this kernel?
Click to expand...
Click to collapse
Yes, but with external power.

major9 said:
Yes, but with external power.
Click to expand...
Click to collapse
So it's of almost no use then..

External power? I can conenct mouse/keyboard or flash drives, no need external power.

Trimmer vs lagfix

Other than Trimmer supporting lollipop is there any difference between the effect of using Trimmer or lagfix?

Anderson2 said:
Other than Trimmer supporting lollipop is there any difference between the effect of using Trimmer or lagfix?
Click to expand...
Click to collapse
Nope, except for that Trimmer's functions are free and they aren't lagfix

Thanks for the thread. This is how I found this app) Just downloaded it.
SENT BY ENTANGLEMENT

TRIM is supported since Android 4.3, so it would be stupid to use fstrim apps like Trimmer.

alexiuss said:
TRIM is supported since Android 4.3, so it would be stupid to use fstrim apps like Trimmer.
Click to expand...
Click to collapse
No it isn't. Some devices need to trim more regularly (Like N7 2012)

Sent by entanglement
Seems to work on mine

GtrCraft said:
No it isn't. Some devices need to trim more regularly (Like N7 2012)
Click to expand...
Click to collapse
Android automatically TRIM filesystems once every 24 hours, so, having external apps doing the same thing is dumb.
"The Android framework will send out a “start idle maintenance window” event that the MountService listens for, and then invokes vold to fstrim filesystems when a few conditions have been met – the device hasn’t been touched for over an hour, no idle maintenance window event has been sent in 24 hours, and the device is either off-charger with 80% battery or on-charger with 30% battery. The goal is to have fstrim run roughly once every 24 hours if you’re in the habit of plugging the device in to charge every night."

alexiuss said:
Android automatically TRIM filesystems once every 24 hours, so, having external apps doing the same thing is dumb.
"The Android framework will send out a “start idle maintenance window” event that the MountService listens for, and then invokes vold to fstrim filesystems when a few conditions have been met – the device hasn’t been touched for over an hour, no idle maintenance window event has been sent in 24 hours, and the device is either off-charger with 80% battery or on-charger with 30% battery. The goal is to have fstrim run roughly once every 24 hours if you’re in the habit of plugging the device in to charge every night."
Click to expand...
Click to collapse
And what if those conditions aren't met, nobody is forcing you to use it

EVR_AL00 – light review and heavy customization

I got the Mate 20 X from Italy, delivered two weeks after order on November 12 for € 829, VAT and 2-years warranty included. It is a nice silver device 6/128 (don’t need more memory). My first hands-on impression? I was shocked.
I had pure Chinese phones before (Huawei and Lenovo) and I know how to deal with them. That wasn’t what upset me. And it wasn’t EMUI either, I like some of its functionality and I know how to customize it.
But my previous phone was Mate 10 pro (international, not Chinese), which really works well and comparison with a newcomer is what really shocked me. The EVR_AL00 came slow and clumsy with those big fat letters and ugly ios-like icons on the screen. I tried to improve the look with increasing the smallest width in the developer options, but original resolution came back with every reset.
So what I did first, is factory reset (I usually perform it on every new phone). I lost Google Play but I didn’t care, I intended to install and adjust Google apps anyway.
And then I started to customize the phone. Basically, it means “dechinezed” and “deiosinezed” it and make it usable for my purposes as the daily driver. Eventually, I succeeded and like before I don’t regret that I bought the Chinese phone as I never regretted before. I believe that my customization demands would request almost the same amount of work and effort with the “international” version.
And with “dechinezed” I don’t mean to be impolite, actually, I like some of the features of China phones, some of them after years comes to western phones as well (night sight, close all apps etc). I just prefer the more Android look of the phone (even more than currently, Google delivers).
The actual status of my phone is as follows:
In the beginning, when I started phone manager, the performance never exceeded 69%. It seems that later it adapted and healed itself (maybe with help of AI) and now performance is usually over 90, close to 100% and the phone suddenly becomes snappy and smooth, slightly better than Mate 10 pro. As expected, the battery life is due to its capacity and with my way of use it could easily survive two days. I don’t have exact data on SOT and other parameters of the battery performance yet. By adjusting the text and display size (both too small) under settings/display the phone gets a nicer look and more usable size of applications.
I had decided to keep EMUI launcher before I learned that the phone has a hard time with other launchers. I bought Nova Prime once, I consider it a great launcher, maybe the best, but even on my previous phone I used EMUI. The reason is in its features that I don’t want to sacrifice: dedicated Accuweather, swype gestures (now with 9), dark mode. I was never a fan of ios-like white themes, I always considered that Android’s color is black. Besides, what even Google admits now (and started to return black mode into its apps accordingly), the white mode consumes a lot more energy (especially with AMOLED). What is yet to admit is that it burns your eyes.
So, what I have now, is a fully customized EVR_AL00 that perfectly suits my needs. That means that it looks like Android, works like Android and behaves like Android. I replaced most Chinese apps with Google’s ones, installed additional that I use and tune the system. With tuning the system I mean screen adjustment and customization. Under Settings/Display/text and display size, I changed both values to small and thus converted ugly appearance of the display into something that suits size and purpose of the phone. I replaced IOS icons with the Android ones. Adjusted notifications and permissions for each application.
First I was thinking about keeping some Chinese apps that I considered useful, like Sky Mobile and a few others. But trying them I found out that all of them are more or less connected either with Chinese environment or payment system and therefore eventually I removed them all. After I had to perform the factory reset I was only got more careful with apps that I disabled. And according to my orientation, I kept Email, at least until Google implements dark color in Gmail. And kept useful utilities: (Manager, Gallery, Remote…).
Otherwise, I use Google Phone (the amazing last beta from: https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218, thank you Martin), Messages, Translate (removed nonfunctional MS Translate), Auto, Duo, Voice, Photos, Trips, Pay, Assistant, Lens, Google, Chrome, and of course all Google system apps. I also use third-party apps like VLC, Xiaomi calculator and YouTube vanced. Pretty much everything works as expected, including notifications to the extent that suits my way of use. After I erased Hivoice, Assistant works together with the hot word, if the screen is turned on (never wished to use it from turned off screen). The red mic on notification bar of the attached picture shows that assistant is active.
All banks application work. Google Play is not working at the moment but I expect that it will eventually. Currently, failure is the result of poor synchronization between Chinese EMUI and Google Android. No point to call the bank, it is the last one to solve the problem. The problem will be solved with the new EMUI or Play Services, because there is no material obstacle for G Play (SafetyNet passed and bank card is recognized and could be used online). I have another identical payment system installed (Inteso SP) and it works flawlessly.
CUSTOMIZATION
In order to adapt the phone to my needs, I had to deal with existing Chinese application first. I had to either: 1) remove them, 2) hide them, or 3) disable (erase) them.
Removing apps
Removing apps was easy. Just uninstall Chinese in Settings/Apps. As I said, I did it thoroughly and indiscriminately.
Hiding apps
My overall objective is to have only one home screen page. I’m fed up with slippery pages interfering with gestures. And besides, I decided to use gestures (swype) as system navigation and therefore swyping between homepages could be annoying even more.
In order to have only one home page, I have to use folders and hide auxiliary functional apps (like download, OTA, backup, clock..etc).
Surprisingly I found that Tweaker for Huawei works pretty well with EMUI9, although it is an old application: https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.emuitweaker&hl=en. One of its functions is triggering the abandoned EMUI gesture that enables hiding any application and thus removing it from the home screen without affecting its functionality.
Disabling (erasing) apps
To “remove” any nonremovable application without root you need a computer with the adb command-line tool. In fact, this method never removes any application, rather disables and hides it for the current user. So it doesn’t affect OTA and it doesn’t revert after reset either. It does come back after factory reset though.
The method of erasing an app works through adb (so adb must be installed on the computer – either Windows or Linux) and it requests the following syntax in command line:
1. adb devices (and after that setting permission on the phone)
2. adb shell
3. pm unistall -k --user 0 <package name>
where <package name> is not the name of the application as it shows but the name of the installed package, which must be discovered and one of the apps which could do that effectively could be found here: https://play.google.com/store/apps/details?id=pl.itto.packageinspector&hl=en.
(for example: pm uninstall -k --user 0 com.huawei.wallet)
A basic idea what to disable could be found here: https://forum.xda-developers.com/note-10/how-to/guide-to-remove-apps-root-t3828324. Of course, what to disable always depends on personal preferences and therefore this list should be taken with a grain of salt.
So, after arranging applications there comes the final stage of making the phone Android again. EMUI makeover. For that, we need this EMUI editor: https://play.google.com/store/apps/details?id=com.mixapplications.themeeditor.
But there is a bad news. It doesn’t work with EMUI 9 (yet). What now? There are two possibilities: either finding a good theme and simply installing it (there are plenty of them, only I didn’t test if they are working with EMUI 9 (some of the android likes are to be found in the Playstore under Hamzio7 or here: https://forum.xda-developers.com/mate-10/themes/pure-black-theme-emui-8-t3719904.
The other possibility is to find a phone with EMUI 8 and compile the hwt file there and transfer it to Mate 20 X. That is what I did. The system will warn you that it is an old version of the theme and it might not work well but skip that. It works just fine.
Don’t judge the solution by my design. I’m a modest guy, more practically oriented. You may have almost any design that you wish.
And of course, if you decide to experiment with this stuff yourself, you should be aware that you are the only one taking the risk. I honestly believe that you can’t, if you are not extremely innovative, irretrievably destroy anything, but even factory reset might be sometimes really annoying.
Good luck with your brand new Chinese Mate 20 X.

Great post Just a couple of questions:
1) Are your notifications working perfectly? By that, I mean without delay under both wi-fi and mobile networks, with screen on and screen off? If so, what did you do to achieve this?
2) Do you mind sharing where did you buy the device from?

Nice job! Looking even more forward to the arrival of my Mate 20 X!

@piskr
Would you mind give some steps to get google phone and Messages to work properly. When phone call comes in, my phone call screen does not come on. Messages only works sometime and sometime message does not send. Thanks.

Genoveffo said:
Great post Just a couple of questions:
1) Are your notifications working perfectly? By that, I mean without delay under both wi-fi and mobile networks, with screen on and screen off? If so, what did you do to achieve this?
2) Do you mind sharing where did you buy the device from?
Click to expand...
Click to collapse
1) Yes, notifications work flawlessly in my extent of use, both with the screen on and off. I don't use exotics like telegram or whatsapp though. It's a matter of permissions and notification settings. Be aware that each notification had to be set separately and checked under application and under notification sector under settings. And also have in mind that if you install the third party phone, it is just addition of original phone (under app/system processes), and the later must remain active and has its own permissions and notification as well. Phone app has different system structure than SMS. You can simply erase Huawei messaging and replace it with the Google one (haven't tried others).
2) You can find here both color and memory variants: https://www.ilmultistoredelzazza.eu...l_Sim_EMUI_9_Android_9/p1748191_19236868.aspx

wingzero said:
@piskr
Would you mind give some steps to get google phone and Messages to work properly. When phone call comes in, my phone call screen does not come on. Messages only works sometime and sometime message does not send. Thanks.
Click to expand...
Click to collapse
You should really carefully check and set both permissions and notifications for each application. And remember that you mustn't neglect the system phone app.

piskr said:
You should really carefully check and set both permissions and notifications for each application. And remember that you mustn't neglect the system phone app.
Click to expand...
Click to collapse
I checked all the settings and seem to be correct unless I missed some steps.

wingzero said:
I checked all the settings and seem to be correct unless I missed some steps.
Click to expand...
Click to collapse
OK. Here are my settings.

You do know there's an EVR-L international models, right? Why not just get that instead? That's what I have.

piskr said:
OK. Here are my settings.
Click to expand...
Click to collapse
Thanks for taking the time to post the screen shots. All my the settings are the same except I don't the phone app on your last screen shot. Did you download it or it's a stock app?
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
MishaalRahman said:
You do know there's an EVR-L international models, right? Why not just get that instead? That's what I have.
Click to expand...
Click to collapse
It's too late. I already bought the China version. It's too much hassle try to sell it.

wingzero said:
Thanks for taking the time to post the screen shots. All my the settings are the same except I don't the phone app on your last screen shot. Did you download it or it's a stock app?
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
It's too late. I already bought the China version. It's too much hassle try to sell it.
Click to expand...
Click to collapse
That's right, the last one is Google phone from the link I published and it works just fine (I really recommend it, it has so many opportunities). But you have managed to get notifications neither on the home screen nor on the lock screen? Neither for messages nor for the phone? If I were you I would go from setting to setting for this two apps and inspect every item very carefully. It is possible in this early stage of EMUI9 that it has some weird glitches occurring randomly on some phones but it is not very likely. A small overlooked detail in settings could mean everything.
Otherwise, I don't regret that I bought the Chinese version. Now I've got everything that I would have with the international variant. Only I don't have working Google pay yet, but so far I haven't seen a clear statement that it really works on international Mate 20x either. To work means to be able pay with the phone not only loading a card, that's what I did too. Otherwise, I got a good price (€660 before VAT), integrated call recorder and rooting opportunity.
And regarding crap, international one has it too. I've got international Mate 10 pro and I know it. Besides Chinese one additional western, baked in (MS, Facebook, Google's and third party's).

@piskr
The phone will ring on the google phone app but the screen does not come. I will play with the settings and figure it out. Thanks for all the help.

Thank you. This helped get me to a non-Chinese specifc phone.
Attachin my ADB run.
UPDATE: Please check out AJ's great thread https://forum.xda-developers.com/mate-20-x/how-to/guide-remove-apps-adb-t3870727
I mistakenly removed one item (com.huawei.android.hwouc) I shouldn't have and I amnot getting OTAs (which I also turn off automatic ones in dev options, but if I want one, I lost it them).

Rudolpht said:
Thank you. This helped get me to a non-Chinese specifc phone.
Attachin my ADB run.
Click to expand...
Click to collapse
As I'm not well schooled on ADB. How would you apply this? And why 2 Zips? Gracias

See beginning of the thread and other threads on ADB. Same list, mine in txt or zip, same file, not necessarily good for everyone.
Sent from my HWEVR using XDA Labs

def-g said:
As I'm not well schooled on ADB. How would you apply this? And why 2 Zips? Gracias
Click to expand...
Click to collapse
Here's my Spreadsheet with a quick guide in it along with the adb files you'll need.
https://forum.xda-developers.com/mate-20-x/how-to/guide-remove-apps-adb-t3870727
Once you get the list of packages on your AL00 just run the fastboot command to remove each one.

wingzero said:
@piskr
The phone will ring on the google phone app but the screen does not come. I will play with the settings and figure it out. Thanks for all the help.
Click to expand...
Click to collapse
Wondering if you had any luck. Some people actually use a phone as a phone
Sent from my HWEVR using XDA Labs

Rudolpht said:
Wondering if you had any luck. Some people actually use a phone as a phone
Sent from my HWEVR using XDA Labs
Click to expand...
Click to collapse
I got it working. I am using the stable v.25 version. What I did was after selected the google phone as default dialing app, I go back to default apps and click the stock phone and then click the google phone again. I did this by chance and luck. Hope this will solve your issue. The stock phone app is horrible. Make sure you use the stable version. Good luck.

wingzero said:
I got it working. I am using the stable v.25 version. What I did was after selected the google phone as default dialing app, I go back to default apps and click the stock phone and then click the google phone again. I did this by chance and luck. Hope this will solve your issue. The stock phone app is horrible. Make sure you use the stable version. Good luck.
Click to expand...
Click to collapse
Thanks man.
Sent from my HWEVR using XDA Labs

Now it's 27. And so far everything work. Regarding comments on the forum we are on the privileged side. Just be sure to set notifications and permissions right.

NO MORE SLOW.

For the few who remain using these tablets (and the even fewer who bought a 2015 shield controller like me) I have the final nail in the coffin for performance. Without custom OS. Allowing you to use your very specific (criminally underused) 2015 Shield controller wirelessly. Welcome to the end of your woes (performance not guaranteed, this crap worked for me though). I still haven't checked if battery usage has improved, but it has certainly let me depend on this and use my controller again as opposed to using a CustomOS (previously used AEX 6.7, good performance, but bad video playback and lack of wifi controller support).
Required thingys:
TWRP
This awesome script (JournalingDisabler.zip) (thnx very much skynet28): https://forum.xda-developers.com/t/...urnaling-in-internal-ext4-partitions.1252028/
Developer Options
Snacks? Drinks? This is gonna take some time, don't pass out halfway through lol
Boost 1: DISABLE JOURNALING.
Y'all. This is the good stuff. the nitro. This will make your tablet feel new (again, if everything goes right and I'm not some insane fluke). I only got the idea from an offhand comment from m0nt3s. I thought they were talking about one of the writing apps at first, but once I learned what it was, my brain imploded. Did a quick google search, and found skynet28's solution right away. It's a script designed to disable an ext4 logging service that eats up memory and processing power. I didn't think it would be compatible (but my chaotic neutral mind said why not), but it works:
1. Install TWRP using adb and prayer (that's what it feels like the first time around lol)
2. Download the zip (JournalingDisabler.zip) to your tablet.
3. Use the install button in TWRP, navigate to the zip, and install away.
It should show text saying journaling is disabled if all went well. The gains should be immediately noticeable on your next boot. I didn't notice any issues or side effects, but I also have the benefit of not having important/sensitive data on it, so just to play it safe, back up your data in case issues crop up later.
Boost 2: BACKGROUND PROCESSES
This one will be a touch more noticeable, especially if you multitask on this tablet, but it can definitely stop a lot of the hitching. This one will be in the bottom of the developer options. If you don't have dev options, go into the about tablet section and tap the build number until you become a dev. Setting it to 1 or 2 is decent, but setting it to none will have the biggest impact.
Boost 3: DON'T USE APP OPTIMIZATION
Seriously. Don't know who dropped the ball. But just turn it all off. It's not even a boost, it's just a negative having it on.
Boost 4: SYNCING
If anything is syncing, be it Gmail, your YouTube notifications, or a news feed, turn it off. Any time apps struggle and fight for WIFI, your experience sucks. If you aren't using it as a main (i'm using it in my car as a head unit)
Boost 5: Color Correction
Must have been the same peeps who dropped the ball on app optimization. With the gains you get above, you might not need to, but if you're trying to max it out this will do it.
That's it for me! This is what I've done to get my tablet feeling smooth again. Let me know how it goes?

I can attest that a lot of the above is what needs to be done to save the last days of this tablet. I did not now about the journal part- will have to try this. Related, I just flashed the original OTA's for the Wifi edition on my Shield LTE. By doing this I got a insane boost in battery life. The LTE (H+) does not work but I don't need it and there are other devices that have much better connectivity .

BLKMN said:
For the few who remain using these tablets (and the even fewer who bought a 2015 shield controller like me) I have the final nail in the coffin for performance. Without custom OS. Allowing you to use your very specific (criminally underused) 2015 Shield controller wirelessly. Welcome to the end of your woes (performance not guaranteed, this crap worked for me though). I still haven't checked if battery usage has improved, but it has certainly let me depend on this and use my controller again as opposed to using a CustomOS (previously used AEX 6.7, good performance, but bad video playback and lack of wifi controller support).
Required thingys:
TWRP
This awesome script (JournalingDisabler.zip) (thnx very much skynet28): https://forum.xda-developers.com/t/...urnaling-in-internal-ext4-partitions.1252028/
Developer Options
Snacks? Drinks? This is gonna take some time, don't pass out halfway through lol
Boost 1: DISABLE JOURNALING.
Y'all. This is the good stuff. the nitro. This will make your tablet feel new (again, if everything goes right and I'm not some insane fluke). I only got the idea from an offhand comment from m0nt3s. I thought they were talking about one of the writing apps at first, but once I learned what it was, my brain imploded. Did a quick google search, and found skynet28's solution right away. It's a script designed to disable an ext4 logging service that eats up memory and processing power. I didn't think it would be compatible (but my chaotic neutral mind said why not), but it works:
1. Install TWRP using adb and prayer (that's what it feels like the first time around lol)
2. Download the zip (JournalingDisabler.zip) to your tablet.
3. Use the install button in TWRP, navigate to the zip, and install away.
It should show text saying journaling is disabled if all went well. The gains should be immediately noticeable on your next boot. I didn't notice any issues or side effects, but I also have the benefit of not having important/sensitive data on it, so just to play it safe, back up your data in case issues crop up later.
Boost 2: BACKGROUND PROCESSES
This one will be a touch more noticeable, especially if you multitask on this tablet, but it can definitely stop a lot of the hitching. This one will be in the bottom of the developer options. If you don't have dev options, go into the about tablet section and tap the build number until you become a dev. Setting it to 1 or 2 is decent, but setting it to none will have the biggest impact.
Boost 3: DON'T USE APP OPTIMIZATION
Seriously. Don't know who dropped the ball. But just turn it all off. It's not even a boost, it's just a negative having it on.
Boost 4: SYNCING
If anything is syncing, be it Gmail, your YouTube notifications, or a news feed, turn it off. Any time apps struggle and fight for WIFI, your experience sucks. If you aren't using it as a main (i'm using it in my car as a head unit)
Boost 5: Color Correction
Must have been the same peeps who dropped the ball on app optimization. With the gains you get above, you might not need to, but if you're trying to max it out this will do it.
That's it for me! This is what I've done to get my tablet feeling smooth again. Let me know how it goes?
Click to expand...
Click to collapse
This works! Every bit of OP is legit.
I used current TWRP as of today, twrp-3.6.1_9-0-shieldtablet.img, from https://twrp.me/nvidia/nvidiahshieldtablet.html using fastboot install method on a fully updated Android 7 Nvidia Shield Tablet model p1761w.
Thanks, much respect!

It is important that those who still do not install TWRP should know that to enter fastboot, they must use the official nvidia drivers "SHIELD_Family_WHQL_USB_driver_201801"
This method helped me to lighten but it becomes impossible to install applications, the google services together with those of nvidia cause the ram to collapse and the system cannot manage correctly.
I strongly recommend you to change to a custom rom, you will finally feel the fluidity of the system
At this moment I use lineage 15.1 (android 8.1) + google services minimum (pico)
No chrome app - no Gmail app + facebook and instagram full app. and the system remains light.

nunitofiman said:
It is important that those who still do not install TWRP should know that to enter fastboot, they must use the official nvidia drivers "SHIELD_Family_WHQL_USB_driver_201801"
This method helped me to lighten but it becomes impossible to install applications, the google services together with those of nvidia cause the ram to collapse and the system cannot manage correctly.
I strongly recommend you to change to a custom rom, you will finally feel the fluidity of the system
At this moment I use lineage 15.1 (android 8.1) + google services minimum (pico)
No chrome app - no Gmail app + facebook and instagram full app. and the system remains light.
Click to expand...
Click to collapse
I really wish a developer(s) would take one more look at this device. If there was way to bump up the android version but retain the NVIDIA features it would breath a few more years into these . These tablets are still pretty good for mid range emulation and now that everything has changed with cloud gaming, they are not as irrelevant as it would seem . I've been having pretty good performance on my LTE 32GB that I flashed the original "WiFi edition " stock ROM on. I get great battery life now and use the tablet almost daily for gaming and light use. The sound is also still pretty impressive and I like the stylus functionality as I can't really afford a Samsung device.

What is "journaling"? Is it the same as the logging by logcat? You can set the buffer size to 0K or 64K (setting it to 0 still logs at 64K).