Hi,
to find your Panel manufaturer ID do the following via ADB or Terminal (Note: enter it after fresh boot, the kernel log gets flooded with useless stuff very quick):
Code:
dmesg | grep -i mdss_dsi_panel_init
The output will be something like:
Code:
mdss_dsi_panel_init: Panel Name = 9
Available Panel Types
jdi_novatek_hd_cmd_panel (Panel Name = 9)
lgd_novatek_hd_cmd_panel (Panel Name = 8)
somc,default_panel_0 (Panel Name = default)
somc,default_panel_1 (Panel Name = default)
Without root permission denied?
Sent from my iPad using Tapatalk
@Tommy-Geenexus
Cool Bro!
JDI = JVC
LGD = LG display
And default is... "default"?
Lol how do we know what's the "default" manufacturer?
Regards
mele80 said:
Without root permission denied?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Try via adb shell (adb shell dmesg). This works fine for me without root.
langeveld024 said:
@Tommy-Geenexus
Cool Bro!
JDI = JVC
LGD = LG display
And default is... "default"?
Lol how do we know what's the "default" manufacturer?
Regards
Click to expand...
Click to collapse
Nope, JDI = Japan Display Inc, but LGD is LG (don't know for sure).
The default one is prob. not used in shipping units
Tommy-Geenexus said:
Nope, JDI = Japan Display Inc, but LGD is LG (don't know for sure).
The default one is prob. not used in shipping units
Click to expand...
Click to collapse
Thanks!
Is it possible related to colour and/or buying location and such? (as I've read everyone is talking about)
langeveld024 said:
Thanks!
Is it possible related to colour and/or buying location and such? (as I've read everyone is talking about)
Click to expand...
Click to collapse
I honestly can't tell, but it may or may not be, only a Sony representative can answer that
Returns nothing here when used via ADB. A manual dmesg check also gives nothing.
I got number 9. Do they differ in quality?
Random Username said:
I got number 9. Do they differ in quality?
Click to expand...
Click to collapse
Can't tell so far. People who returned their Z5C to get a new one could check which Panel they got and report any differences.
Im kinda noob when it comes to ADB controles, so any ''detailed'' step by step guide for entering commands to check this thing? I ender adb shell and when i enter the command from the OP i get nada. Help?
Tommy-Geenexus said:
Hi,
to find your Panel manufaturer ID do the following via ADB or Terminal:
Code:
dmesg | grep -i mdss_dsi_panel_init
Click to expand...
Click to collapse
You should probably mention that this will work quite early after system start.
dmesg log is cluttered rather quickly and shows only recent records. That's why some people report nothing in the output.
Back to the topic, I have 9 for the phone bought in central Europe. So, this will be probably most dominant display for EU region.
bubimir13 said:
Im kinda noob when it comes to ADB controles, so any ''detailed'' step by step guide for entering commands to check this thing? I ender adb shell and when i enter the command from the OP i get nada. Help?
Click to expand...
Click to collapse
Turn on usb-debugging, enter adb shell and the command above. Thats it.
OtaruM said:
You should probably mention that this will work quite early after system start.
dmesg log is cluttered rather quickly and shows only recent records. That's why some people report nothing in the output.
Back to the topic, I have 9 for the phone bought in central Europe. So, this will be probably most dominant display for EU region.
Click to expand...
Click to collapse
Yeah you're right, the log get's cluttered pretty easy, working on that already on my Kernel.
Added it to the OP.
also got 9. And also an CE1 version (Croatia). Guess this is going to be a standard for most of Europe.
panel 9 here as well, anyone actually gotten the LG panel? Might just be testing hardware or similar?
Panel 9 here as well...
mdss_dsi_panel_init: Panel Name = 8
report by my Xperia Z5 Compact White
bought in 2015/10/3 in Taipei, Taiwan
mdss_dsi_panel_init: Panel Name = 9
z5c black Germany.
Display has a slight shadow topside that is most noticeable during boot when the white animation is playing.
Panel 9
E5823 Black Italy Rev3
Related
Hi, I am thinking of buying Nexus 7, but I would really like to have some way to stream it's display to at least computer. That can be most easily (well, more like the most primitive way) by sending content of framebuffer via wifi. That however requires the framebuffer to be accessible and reasonably big (eg. small).
Now, I do not have it yet, and I do not know anybody who has it, so I am asking you to get some info about framebuffer for me. It will not take more than 5 minutes and only things you need is ADB and root.
So, if you decided to help me, thank you, and let's get started.
I want you to just run several commands on your device under root and then send me the result files.
1. Device permissions
Code:
ls -l /dev > /sdcard/xda_tass.txt
ls -l /dev/graphics >> /sdcard/xda_tass.txt
These two commands will tell me what device files are available on N7 and their permissions. The output is saved to file on sdcard (well, I hope the memory in N7 is called /sdcard. If not, just change it to some existing path).
2. Testing the framebuffer
Code:
time (cat /dev/graphics/fb0 > /dev/null) >> /sdcard/xda_tass.txt 2>&1
This command will tell me how long does it take to read framebuffer. Run it 3-5 times, so that I have some average values. If "/dev/graphics/fb0" does not exist, try "/dev/fb0".
Code:
cat /dev/graphics/fb0 > /sdcard/xda_tass.dat
Copies the framebuffer into file, so that I know how big it is and which format does it have. This is like taking screenshot, so make sure there is not something embarrassing on your display
3. Send me the files
Take files "xda_tass.txt" and "xda_tass.dat", ZIP em' up and put it somewhere. That is all.
I would be really glad if somebody could do that for me, thanks
Here you go
http://db.tt/3WBr5BWK
Also the sdcard is now /storage/sdcard0, yeah idk why
Sent from my Nexus 7 using Tapatalk 2
Thank you
Looks okay, even though the framebuffer is huge. Well, I suppose it is not a problem to compress it on that quad-core craziness. And, it has two framebuffers (fb0 and fb1) - I wonder why.
Also, I cannot decode data from that framebuffer. Could you please get me also the second framebuffer?
Code:
cat /dev/graphics/fb1 > /storage/sdcard0/xda_tass_fb1.dat
Tasssadar said:
Thank you
Looks okay, even though the framebuffer is huge. Well, I suppose it is not a problem to compress it on that quad-core craziness. And, it has two framebuffers (fb0 and fb1) - I wonder why.
Also, I cannot decode data from that framebuffer. Could you please get me also the second framebuffer?
Code:
cat /dev/graphics/fb1 > /storage/sdcard0/xda_tass_fb1.dat
Click to expand...
Click to collapse
Here you go
http://db.tt/Nt6kBM83
Sent from my Nexus 7 using Tapatalk 2
Data from fb1 look about as random as those from fb0 to me. Gonna need some more samples, but I can do that by myself once I'll have my own N7.
Thanks for helping me
Tasssadar said:
Data from fb1 look about as random as those from fb0 to me. Gonna need some more samples, but I can do that by myself once I'll have my own N7.
Thanks for helping me
Click to expand...
Click to collapse
No problem lol
Sent from my Jelly Nexus S
@Tasssadar how did you decode the framebuffer? I'm actually trying to get a screenshot of MultiROM, but I can't figure out how to decode it. I'm trying to open it with GIMP by changing the settings and moving the width value, but I can't get a clear image.
Your signature says you have the 2013 Nexus 7. MultiROM doesn't use framebuffer on that device because of severe kernel driver bug. You can still take screenshots though - tap on the screen with four fingers at once. The screen should flash and screenshot will be saved to /sdcard/multirom/ (accessible in Android only with root in /data/media/0/multirom).
The format should be RGB Alpha and the dimensions should be 1200x1920.
Tasssadar said:
Your signature says you have the 2013 Nexus 7. MultiROM doesn't use framebuffer on that device because of severe kernel driver bug. You can still take screenshots though - tap on the screen with four fingers at once. The screen should flash and screenshot will be saved to /sdcard/multirom/ (accessible in Android only with root in /data/media/0/multirom).
The format should be RGB Alpha and the dimensions should be 1200x1920.
Click to expand...
Click to collapse
Damn, you put so many easter eggs in MultiROM
That's interesting though... That's why when pulling the framebuffer I only got a black screen. In the recovery, instead, I could get something "visible" (still not the actuall image, though).
@Tasssadar Is it still possible to take screenshots on the new multirom for flo? When I tap with four fingers nothing happens.
Since v27, screenshots are taken with power+volume down combo like in Android ( you have to press power button first though, cause I'm lazy). They are also saved as PNG instead of raw data, and they are in folder /sdcard/Pictures/Screenshots like Android screenshots. I mentioned it in the changelog
Protip :
tutorial on howto increase Nook's "resolution" by changing /system/build.prop
http://forum.xda-developers.com/showthread.php?t=823522
Can someone do a compare?
I scanned the thread and performed the following actions:
First I used the "test" commands to experiment with settings. I discovered that I liked a density setting of 133 best.
# setprop qemu.sf.lcd_density 133
# busybox killall system_server
So I modified my /system/build.prop by changing the line
#ro.sf.lcd_density=240
to
ro.sf.lcd_density=133
and rebooted.
So, everything is certainly smaller, but as I have only one NST, I cannot determine if I think the text is sharper because I can't do a side-by-side comparison. So, is there somebody out there with two NSTs who is willing to make this change to one of them and then do a side-by-side comparison and report back?
David0226 said:
So, everything is certainly smaller, but as I have only one NST, I cannot determine if I think the text is sharper because I can't do a side-by-side comparison. So, is there somebody out there with two NSTs who is willing to make this change to one of them and then do a side-by-side comparison and report back?
Click to expand...
Click to collapse
You can do few screenshots and compare them side-by-side.
screenshots?
how do you do a screnshot on nook? , ( for those of us that don't know) , thanks
steelworker said:
how do you do a screnshot on nook? , ( for those of us that don't know) , thanks
Click to expand...
Click to collapse
dude...wtf?
Just type "screenshot android" into your search engine.
I use 'ddms' via adb.
http://www.makeuseof.com/tag/how-to-capture-screenshots-with-your-android-mobile-phone/
No real difference
Here are two screen shots I took. (Thanks for the link osowiecki). The first was taken with the density set to 160 (standard) and the second with it set to 120. There is some difference in the size of the header and footer lines, but I see no real difference in the size of the book text. Setting the density to 120 does allow the standard B&N library app to display nine titles on one screen instead of six. Otherwise I see no difference when using the standard B&N reader.
I did these tests using the LCDDensity app.
Here are screenshots of the library app in each density ...
I can't confirm any changes for text based books, but it definitely helps with converted comics. No idea why the screenshots are green, used "screenshot" tool from within adb shell. Tried with default DPI, 133, 120, and also pulled the image from the unconverted CBR for comparison.
neoman4426 said:
No idea why the screenshots are green ...
Click to expand...
Click to collapse
My screenshots taken with the screenshot tool in ADB shell were green also. You will get better results by following the procedure outlined in the link in osowiecki's post.
Was the first thing I tried, couldn't get it to recognize my device. I'm not sure if it's a wired ADB only thing, or a "doesn't work on Linux for some reason" thing or what. ah well, I kind of like the green look
Hello,
I have galaxy note 2 (n7100) international version and im running OmniRom 4.4.2 (31-3-2014)
the rom is great but charging the battery takes alot of time( way too long than normal ),i have flashed several stock /costumed rom and i didnt encounter this problem......
if im writing in the wrong section please provide me with a link so i can report my problem
Thanks in advance
If your device is rooted try to manually apply the charging currency using terminal emulator, adb shell, or so:
Code:
echo "1800" > /sys/devices/platform/samsung-battery/dcp_ac_input_curr
echo "1700" > /sys/devices/platform/samsung-battery/dcp_ac_chrg_curr
dcp_ac_input_curr defines the maximum input, dcp_ac_chrg_curr defines the currency at which your battery will be loaded. If this loads your device faster, some app or OmniROM sets lower values for those variables. If not, I don't know. Make sure you are executing these commands as root.
klenamenis said:
If your device is rooted try to manually apply the charging currency using terminal emulator, adb shell, or so:
Code:
echo "1800" > /sys/devices/platform/samsung-battery/dcp_ac_input_curr
echo "1700" > /sys/devices/platform/samsung-battery/dcp_ac_chrg_curr
dcp_ac_input_curr defines the maximum input, dcp_ac_chrg_curr defines the currency at which your battery will be loaded. If this loads your device faster, some app or OmniROM sets lower values for those variables. If not, I don't know. Make sure you are executing these commands as root.
Click to expand...
Click to collapse
Hey klenamenis, thanks for that. Is there a noob way to check whatever you mentioned here? I have the same problem and i can't really understand what is it i could do.
Sent from my GT-N7000 using Tapatalk
nihilist_bloke said:
Hey klenamenis, thanks for that. Is there a noob way to check whatever you mentioned here? I have the same problem and i can't really understand what is it i could do.
Click to expand...
Click to collapse
Install this app, open it and type in the following commands and post both outputs here:
PHP:
echo /sys/devices/platform/samsung-battery/dcp_ac_input_curr
echo /sys/devices/platform/samsung-battery/dcp_ac_chrg_curr
Just out of curiosity I enter the commands in a Android terminal emulator ,
su -
echo /sys/devices/platform/samsung-battery/dcp_ac_input_curr
and got nothing in return... no value only the echo...
When i do the echo "1800" > /sys/....
command
I get a file not found error.
what's doing this noob wrong?
Sent from my GT-N7100 using xda app-developers app
I'm also having this issue, very frustrating. I recently bought two new Galaxy Note 2 charge at a rate of anywhere from 200-800 mAh, when the amount they should be charging is 1800 mAh. Looking for a fix.
When entering the above command, I also get an error.
CyD13 said:
I'm also having this issue, very frustrating. I recently bought two new Galaxy Note 2 charge at a rate of anywhere from 200-800 mAh, when the amount they should be charging is 1800 mAh. Looking for a fix.
When entering the above command, I also get an error.
Click to expand...
Click to collapse
Sorry to hear that, Mine works fine,
Hi all, I bought an m3 a couple of weeks ago and the interface for all my apps show up as they would on a phone display rather than on a tablet.
My question is, if I root the device and just put straight android on, would I be able to specify that this is a tablet device rather than a phone? Or even, are there 2 versions available to install? Or is all this built into the hardware?
I know you can shrink the size of text and the general look within settings but that's not the issue. it's how the apps function .e.g. on some apps if I click on a link it takes me to another page rather than just popping up on a side bar. I had a Samsung previously, identical screen size and I can see the difference.
Any help is much appreciated
Thanks
Dig around on this forum, there are a few threads. If you are rooted there are ways to change the DPI which will trigger the apps to correctly display tablet mode. Less severe than loading a ROM.
Here is one of them:
https://forum.xda-developers.com/mediapad-m3/help/huawei-mediapad-m3-chrome-running-phone-t3487236
portisgreg said:
Hi all, I bought an m3 a couple of weeks ago and the interface for all my apps show up as they would on a phone display rather than on a tablet.
My question is, if I root the device and just put straight android on, would I be able to specify that this is a tablet device rather than a phone? Or even, are there 2 versions available to install? Or is all this built into the hardware?
I know you can shrink the size of text and the general look within settings but that's not the issue. it's how the apps function .e.g. on some apps if I click on a link it takes me to another page rather than just popping up on a side bar. I had a Samsung previously, identical screen size and I can see the difference.
Any help is much appreciated
Thanks
Click to expand...
Click to collapse
Hi!
Unlikely it is a known issue. Nothing you can do except changing the dpi to 325. If you do that all apps run in tablet mode but if you restart the tab it goes back over 400 dpi so it's not a perfect solution.
Thanks for the replies I've managed to root it and I got a really terrible rom (the only one I could find in the forums)
A couple more questions:
1. the density settings don't stay even if you root - it there any way to keep them?
2. are there any better ROMs than this?
Thanks
Greg
Ok!
So here's the latest build from Huawei with Android 7.0.
I accept no liability as it's clearly a pre-release with glitches etc but I've not found any issues yet
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1224/g490/v80058/f2/full/update.zip
I used the Huawei Firmware Finder Team Tool to find it.
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
portisgreg said:
Thanks for the replies I've managed to root it and I got a really terrible rom (the only one I could find in the forums)
A couple more questions:
1. the density settings don't stay even if you root - it there any way to keep them?
2. are there any better ROMs than this?
Thanks
Greg
Click to expand...
Click to collapse
adb.exe shell wm density 330 && adb reboot
https://forum.xda-developers.com/me...chrome-running-phone-t3487236/page3?nocache=1
famedoro said:
adb.exe shell wm density 330 && adb reboot
https://forum.xda-developers.com/me...chrome-running-phone-t3487236/page3?nocache=1
Click to expand...
Click to collapse
thanks but it doesn't retain the settings after reboot still
Nougat doesn't solve this problem.
Sent from my BTV-W09 using Tapatalk
Android 6 update is available below...
PLEASE NOTE: This is a one way street, no downgrading to android 5.
https://www.carjoying.com/Joying-blog/59.html
Jeep and TL123 (toyota) model are the only ones which use the low resolution ROM
Considering this was released today please be careful what risk you are taking.
I will be doing some tests and will report if I find any issue.. please send your bug reports to carjoying so they can be fixed.
Also we need an INTEL subcategory in the forum under Android Auto
--- updates---
Passwords:
3368 for settings
8086 launchers
5768 menu backlight
Root and debug on
https://forum.xda-developers.com/showpost.php?p=72057022&postcount=12
- method 2 still work for root and SU
Google voice response works without hacking.
audio_policy.conf now supports usb dacs without modification
TomTom GO works without risky bootloader mod.
Viper4Android installs correctly
-with removal of deep buffer section in /system/etc/audio_policy.conf as per https://forum.xda-developers.com/showpost.php?p=72060811&postcount=35
- https://forum.xda-developers.com/showpost.php?p=72064749&postcount=41
The pull down white text color issue is fixed with play music and other apps
New Recovery
If you need to RE-FLASH the 6.0 firmware, you MUST rename 5009_20.zip to 5009_60.zip , otherwise the firmware will throw an error! yay! I just tested it and it WORKS!
Enable wireless adb https://forum.xda-developers.com/showpost.php?p=71616884&postcount=273
Enable split screen settings in debugging mode then you can split the screens from the task manager (post #84 & #103)
updated "no-kill" https://forum.xda-developers.com/showpost.php?p=72102580&postcount=87
task killer removed and will call the google voice search from the 'SRC' button https://forum.xda-developers.com/showpost.php?p=72153510&postcount=159
ADB enable easier way post #160: in the downloaded ROM zip,
"config.txt" inside the root firmware directory , just add "service.adb.tcp.port=5555" to the last line.
Spotify notifications work
google from any screen by velvet apk post #206 https://forum.xda-developers.com/showpost.php?p=72179874&postcount=206
the CPU works a lot nicer, spending a lot of time at lower freqs when power is not needed
.when you get out of sleep the selected apps are no longer in split screen
you can't read the PMIC temperature anymore
when you set the DPI to 240 the upper bar gets huge and the apps still don't scale well
the bar gets white on Deezer, annoying at night,ugly looking (bug) picture attached
the iGO/Waze bug that makes the unit sleep after 5 minutes (instead of the normal 1 minute) from the moment the engine is off is still present. drawing .01-.05amp for that 5min.
MAY 8 2017 UPDATE
BUG Fixes , Bluetooth Issues solved and working well
========
Steering wheel key customization
https://forum.xda-developers.com/an...-units/joying-2gb-steering-wheel-key-t3543390
Tips and Tricks link:
https://forum.xda-developers.com/an...roll-joying-2gb-sofia-mtcb-mtcd-tips-t3555249
tomtom go
doctorman said:
Android 6 update is available below...
PLEASE NOTE: This is a one way street, no downgrading to android 5.
https://www.carjoying.com/Joying-blog/59.html
Considering this was released today please be careful what risk you are taking.
I will be doing some tests and will report if I find any issue.. please send your bug reports to carjoying so they can be fixed.
Also we need an INTEL subcategory in the forum under Android Auto
Click to expand...
Click to collapse
It works tomtom go?
Again no detailed change log. Incredible.
I'd keep away until a few people have tried this.....
Beta release? Don't think I'd risk this on the head unit and end up without a working unit until they actually fix it.... "Fix some bugs" seems to be the extent of most of their change logs... hehe
someone guinea pig it
Looking forward to someone having the balls to flash this.
As a side note...why is everyone so excited about Android 6 on this unit...I don't see any features that would even make me update.
CadillacMike said:
someone guinea pig it
Click to expand...
Click to collapse
Install went very quick, it wipes all applications and data.
I have not yet been able to access via wifi / ADB, so no rooting or mods as of now
> adb connect 10.0.0.26
unable to connect to 10.0.0.26:5555: Connection refused
gustden said:
Install went very quick, it wipes all applications and data.
I have not yet been able to access via wifi / ADB, so no rooting or mods as of now
> adb connect 10.0.0.26
unable to connect to 10.0.0.26:5555: Connection refused
Click to expand...
Click to collapse
That would be simply terrible if it can't be bypassed.
CadillacMike said:
someone guinea pig it
Click to expand...
Click to collapse
doitright4 said:
Since it wiped everything, did you remember to enable usb debugging? (which really means adbd)
Click to expand...
Click to collapse
KamaL said:
That would be simply terrible if it can't be bypassed.
Click to expand...
Click to collapse
USB debugging was enabled.
It looks like they missed persist.adb.tcp.port=5555 in the properties. It can be enabled by the following:
1) download a terminal program ( Terminal Emulator for Android )
2) enter the following command: setprop persist.adb.tcp.port 5555
3) reboot
I just, installed supersu and seems to be working
doitright4 said:
That's a great point, and it is really... sad? stupid? FREAKING RETARDED!!!! that they would bother wasting time to build 6.0 so long after 7.0 (and 7.1 even!!!) are already available.
7.x of course, adds in split screen mode, which would be a GREAT benefit to car radios.
There is one thing, however, that could make the 6.0 build good, especially an early or beta build... they've had less time to destroy it than they've had to destroy 5.x. So its probably a faster, more stable, and more respectful build than what we've previously seen.
Click to expand...
Click to collapse
Yeah split screen might be useful...otherwise it just runs navigation/music/videos in cars mostly...which any version of Android can do.
mirror up for 1024x600 version:
pending
extracted files here
pending
gustden said:
USB debugging was enabled.
It looks like they missed persist.adb.tcp.port=5555 in the properties. It can be enabled by the following:
1) download a terminal program ( Terminal Emulator for Android )
2) enter the following command: setprop persist.adb.tcp.port 5555
3) reboot
I just, installed supersu and seems to be working
Click to expand...
Click to collapse
Great to hear that.
Are there any noticeable changes so far?
So how's the update?
Is it faster/slower than android 5?
Did you find some bugs?
@gustden mind checking if the apps are still the same as in 5.1.1? Especially around the server app if the kill switch is still present
bogdi1988 said:
@gustden mind checking if the apps are still the same as in 5.1.1? Especially around the server app if the kill switch is still present
Click to expand...
Click to collapse
All the apps are still the same. Not seeing much difference, other than in the settings. So far, it seems fast and stable.
Sofia-1-C9-Server-V1.0.apk looks the same ( and still kills everything on standby). Hope to have time to remove the app killer and add the other mods over the weekend.
gustden said:
All the apps are still the same. Not seeing much difference, other than in the settings. So far, it seems fast and stable.
Sofia-1-C9-Server-V1.0.apk looks the same ( and still kills everything on standby). Hope to have time to remove the app killer and add the other mods over the weekend.
Click to expand...
Click to collapse
Thanks! I'd love to see an updated Server with the standby-kill removed, the source button -> google search hack and the mute-alarms feature removed so we can have the voice output for Google searches - if possible please?
gustden said:
I just, installed supersu and seems to be working
Click to expand...
Click to collapse
Way to go man !
Thank you !
---------- Post added at 05:24 PM ---------- Previous post was at 05:22 PM ----------
bogdi1988 said:
@gustden mind checking if the apps are still the same as in 5.1.1? Especially around the server app if the kill switch is still present
Click to expand...
Click to collapse
Good point ! It would be nice to be able to use the mods from 5.0.1 ... or at least some of them....
---------- Post added at 05:26 PM ---------- Previous post was at 05:24 PM ----------
gustden said:
All the apps are still the same. Not seeing much difference, other than in the settings. So far, it seems fast and stable.
Sofia-1-C9-Server-V1.0.apk looks the same ( and still kills everything on standby). Hope to have time to remove the app killer and add the other mods over the weekend.
Click to expand...
Click to collapse
Is the notifications bar still broken ? (white text and buttions on white bar)
And the most important question, any changes regarding the Bluetooth module? Does it still cover the screen during calls without the ability to minimize?
KamaL said:
And the most important question, any changes regarding the Bluetooth module? Does it still cover the screen during calls without the ability to minimize?
Click to expand...
Click to collapse
Based on what @gustden said, it looks like all the apps are the same so I would assume that issue is still present.