Hi!
It has come to my attention that videos played in this ROM (VGA+) are getting less stuttter / lag. Even without the modified libraries.
As I have checked the date when the libraries (OMX) were created, it was way back 2008.
if I applied the updated libs of the Adreno 200 for ICS ARMv6, the lag is getting obvious, its like there is a sudden freeze in frames.
I don't know for now what's going on here (libstagefright, OpenMAX, and the Adreno 200 drivers) in the cm9.1 alpha 9 rom itself.
Has anyone tried this ROM? (This came from google)
https://code.google.com/p/cm9-wildfire-s/downloads/list
maybe there is a way on putting JDroid's and Gangster41's modified files here, but for now, I don't know what files to put and what's not, coz I'm no good at modifying the libraries. (No knowledge about linux / android programming)
Everytime I put the modified OMX libs, video acceleration gets worse.
Even the Adreno 200 Lib updates for ICS! :/
hope this info somehow helps the issue on the HW acceleration for ARMv6.
I hope the solution will be found soon, so we will have a fully functional cm9!
Where did you find adreno200 libs for armv6 ics?
thepastormarty said:
Hi!
Has anyone tried this ROM? (This came from google)
https://code.google.com/p/cm9-wildfire-s/downloads/list
Click to expand...
Click to collapse
ummmm... it's our CM 9.1 from modpunk, it's core of all (almost) ICS ROMs in dev thread. I think you just don't understood something.
EdikNeznanov said:
ummmm... it's our CM 9.1 from modpunk, it's core of all (almost) ICS ROMs in dev thread. I think you just don't undertood something.
Click to expand...
Click to collapse
yeah you're right. Thanks anyway. I'll try to look deeper into the files then.
polfrank said:
Where did you find adreno200 libs for armv6 ics?
Click to expand...
Click to collapse
sorry for not replying.
somewhere in the xda afaik.
I have attached the necessary files for the ICS. (The adreno 200 drivers, dont forget to delete the libGLES_android.so.. they said, deleting that file will increase performace, as it now relies on hardware, and the OMX libraries done by gangster41)
As far from what I have read from the android devs on ics armv6, video recording was somehow possible, but in h263, ammb (vid/audio) format.
see here (http://forum.xda-developers.com/showthread.php?t=1860561&page=5)
Hello! Has there been any progress concerning this matter? I tried modifying things some time ago but I failed..
As I saw, thehacka1 has released a rom(icysnap) with better video playback(i hope it s not my idea).
Furthermore I thought that the owl project team could give a little help here, although they re focused on cm10.1 doing a good job...
Are there any chances of improvement or should I abandon hope...? :/
I copied system/lib folder from MIUI v4 by Henry_01 (which has working video playback) into SlimSandwich and video was working correctly. I just thought I should share. So, we have working video playback on ics!
I've been working on getting Ubuntu running on my Sprint Galaxy S3 using the same method I used on my Epic 4G - kexec from recovery loading the root filesystem off a partition on an SD card.
What I've done so far:
* Found a kexec loader to boot into a custom kernel, which is required for booting off an SD card, among other things;
* Compiled a custom kernel with KGSL DRM support enabled for Freedreno;
* Built a minimal Ubuntu 13.10 armhf rootfs and compiled the Freedreno DRM/DDX/Mesa Gallium driver with changes to support the Adreno 225 and stub occlusion query (possibility of full dekstop OpenGL 2.1 support!);
* Got X11 working with USB keyboard, touchscreen, and fbdev. Still working on getting the Freedreno DDX to load.
I still get a kernel oops with the camera driver (http://pastebin.com/egZbxsED), but it apparently doesn't affect stability or cause reboots anymore.
Working so far:
* USB Host - only tested with a keyboard, but other input/storage/audio/video devices should also work.
* Framebuffer console - thanks castrwilliam!
* Touchscreen works with X.org fbdev driver and the following added to /usr/share/X11/xorg.conf.d/11-evdev-quirks.conf:
Code:
Section InputClass
Identifier "Touchscreen"
Driver "evdev"
MatchProduct "sec_touchscreen"
EndSection
* Power and volume buttons
Untested:
* Bluetooth - might need firmware
* Sensors - should work just fine
* Home, menu and back buttons should work but probably need mapping
Unlikely to work due to proprietary Android-only blobs:
* Camera
Kernel config changes:
# IMPORTANT: remove the line that says "depends on !MSM_KGSL_DRM" from drivers/gpu/msm/Kconfig:70
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_VT_CONSOLE=y
CONFIG_DRM=y
CONFIG_MSM_KGSL_DRM=y
I may eventually post a pre-built kernel, but if you don't know how to compile a kernel from source, this guide is not for you.
Likewise, if you don't know how to prepare an armhf Ubuntu root filesystem, this guide won't help much.
After building the kernel, copy arch/arm/boot/zImage to your SD card along with the attached zImage.zip (CWM-flashable kexec loader).
It might need modifications (META-INF/com/google/android/updater-script) depending on how you have your card set up.
UPDATE: Unfortunately, this phone hasn't been a good fit for me. I never got very far booting Ubuntu or Freedreno, so I decided to sell it.
For anyone still interested in this project, I believe castrwilliam has the required patches.
When I get my next Snapdragon device (either the new Nexus 7, a Nexus 4, a Galaxy S4, or another phone with Adreno 320 graphics), I will post the Mesa patches for occlusion query support. Sorry I wasn't more helpful with this device.
Added to favourites, I'll see what I can do with it over the weekend
Sent from my SPH-L710 using Tapatalk 4 Beta
Great work. Good luck debugging.
Sent from my SPH-L710 using xda app-developers app
Maybe taking a look at how Motorola worked Ubuntu, in a way, with Webtop that came on the Photon. The Photon has the integrated Ubuntu-based 'Webtop' application from Motorola. The Webtop application is launched when the phone is connnected to the external display through Laptop dock or HD multimedia dock. In Webtop mode, offering similar user interface of typical Ubuntu desktop, the phone can run several applications on external display such as Firefox web browser, SNS clients and 'mobile view' application enabling total access of the Photon and its screen. In September 2011, Motorola released the source code of Webtop application at SourceForge.
I know it's not an app you're trying to use but it may help in finding how to work some of the kinks you have. I hope that helps
Hi, I'm the person maintaining Ubuntu currently for HP Touchpad (http://forum.xda-developers.com/showthread.php?t=2225462) (which also uses an MSM SOC.) It's starting to show its age... I'm trying to get this to where you have it currently on a Verizon S3 / d2vzw (obviously, kexec'ing into a Verizon kernel instead.) Maybe we could collaborate?
Currently I have the KT747 kernel (kexec host support as well as guest) (compiled as a zImage. If you can provide me with access to the patches you have for freedreno and hopefully also an initramfs image (I'm going to mod the HPTP rootfs, so no need there)... I'd love it.
My only modifications to the kernel so far are the ones I mentioned in the OP and three of Rob Clark's Freedreno commits from the mako-kernel branch of kernel-msm on his GitHub - namely, "kgsl: drm: remove checking on 'active'", "video/msm: add true ARGB", and "kgsl: fix null ptr on cache flush".
At one point I had X11 working with freedreno displaying the GNOME background, but the screen blanked after 10 seconds and I couldn't recover from that. Unfortunately, after experimenting with different kernel config options, I lost that semi-working configuration and the GPU started to page fault, sometimes displaying a corrupted screen and sometimes rebooting before displaying anything.
Believe me, I've been working on this for weeks, and it's very frustrating that it doesn't even sort of work. My minimal modifications to Mesa to get it to recognize the Adreno 225 are highly unlikely to be the cause of the problems, and I highly doubt the differences between the 220 and 225 are to blame since it was working at one point. It's a one liner, figured out from from freedreno/mesa issue #2.
Castrwilliam, the initramfs is the least of your worries. I don't use one, since its only function is to display the Plymouth splash, which doesn't work anyway.
gTan64 said:
...
Castrwilliam, the initramfs is the least of your worries. I don't use one, since its only function is to display the Plymouth splash, which doesn't work anyway.
Click to expand...
Click to collapse
Yeah, I realized how you were doing this after looking at the kexec script. I was trying to boot from Android, not recovery, and was under the impression you had put a disk image on external SD, and then made the initramfs loop-mount that and boot from it... but now I see you partitioned it.
It's a shame you don't have your original config, I'll try to get it booting again on my end. I remember doing something like this a while back, where I made like 10 differently configured kernels at once, and tested them each in turn. I imagine the ramconsole would help a good bit so that I could look a how far we're getting. (The touchpad has its own version of that, which you can read directly from the bootloader (bootie.) Then again, it also has LVM volumes for storage instead of actual partitions (except for boot) - which makes it uber easy to boot lots of OSes.)
Currently I'm not doing too well. I remember that kexec did work at one point on d2vzw hardware but I'm assuming that it still does now (new bootloaders, 3.4 kernels, ...) I do kexec -e, the reboot happens, I see the Samsung bootloader screen, then the screen blanks for like 5 seconds and it reboots again - back into android.
castrwilliam said:
I imagine the ramconsole would help a good bit so that I could look a how far we're getting...
the screen blanks for like 5 seconds and it reboots again - back into android.
Click to expand...
Click to collapse
The RAM console should be enabled by default, so check /proc/last_kmsg once Android boots back up.
It could be something simple like the root filesystem not mounting, either due to how you partitioned the card or not having time to settle, hence rootwait. Or it could be something else. I haven't gotten any useful output in /proc/last_kmsg with the framebuffer console enabled, so make sure that's disabled unless you want a headache and a psychiatrist visit.
Unfortunately, I've spent way too much energy trying to debug the GPU page fault, and I probably won't have much time to work on it after next month. I want this bug dead and forgotten, so more eyes would be great!
X11 works (shows something on screen) with the X.org "fbdev" driver. I can't reproduce anything with "freedreno" (or "modesetting", which I accidentally loaded at one point...)
The touch screen doesn't respond, but the power key works and brings up a shutdown dialog.
Screenshot attached. I used the 13.04 Touchpad rootfs with some modifications...
Okay, you can get the fbcon working by either loading it as a module during boot OR changing its "module_init" macro in drivers/video/console/fbcon.c to "late_initcall".
Picture attached. Sorry for blurriness, I don't have an actual digital camera, only what's on my sig. This should make debugging a bit easier.
Nice to see some more freedreno development on android phones
I'm using freedreno with a slightly different approach, starting it directly from android on a chrooted shell, which is a lot more easier to debug.
The kernel needs some fixes from the mako branch and the following configs:
Code:
CONFIG_DEVTMPFS=y
CONFIG_VT=y
CONFIG_DRM=y
CONFIG_MSM_KGSL_2D=y
CONFIG_MSM_KGSL_DRM=y
Rob Clark (the maintainer of freedreno) has been working on his own kernel driver for adreno gpu:
https://github.com/freedreno/kernel-msm/commits/ifc6410-drm
This would be a nice addition/replacement for the current qualcomm gpu driver.
Wootever said:
Nice to see some more freedreno development on android phones
I'm using freedreno with a slightly different approach, starting it directly from android on a chrooted shell, which is a lot more easier to debug.
The kernel needs some fixes from the mako branch and the following configs:
Code:
CONFIG_DEVTMPFS=y
CONFIG_VT=y
CONFIG_DRM=y
CONFIG_MSM_KGSL_2D=y
CONFIG_MSM_KGSL_DRM=y
Rob Clark (the maintainer of freedreno) has been working on his own kernel driver for adreno gpu:
https://github.com/freedreno/kernel-msm/commits/ifc6410-drm
This would be a nice addition/replacement for the current qualcomm gpu driver.
Click to expand...
Click to collapse
How do you stop the SurfaceFlinger (I think that's proper terminology) from hogging the framebuffer?
Semi Working Freedreno/X11
castrwilliam said:
How do you stop the SurfaceFlinger (I think that's proper terminology) from hogging the framebuffer?
Click to expand...
Click to collapse
HEY, look what I did?!
(There are a lot of patches req'd to get this far. Even at this point, there's a weird bug where the cursor loops across the edge of the screen and windows overlap themselves. If you want to know, I'll elaborate in a further post, otherwise, let's get that touchscreen working for release!)
Thanks to Rob Clark (again, the author of freedreno) who helped me get this far on his IRC channel at Freenode.
castrwilliam said:
HEY, look what I did?!
(There are a lot of patches req'd to get this far. Even at this point, there's a weird bug where the cursor loops across the edge of the screen and windows overlap themselves. If you want to know, I'll elaborate in a further post, otherwise, let's get that touchscreen working for release!)
Thanks to Rob Clark (again, the author of freedreno) who helped me get this far on his IRC channel at Freenode.
Click to expand...
Click to collapse
Are we keeping track of all the necessary patches? I'm on https://github.com/CyanogenMod/android_kernel_samsung_d2, branch cm-10.2_kgsl, with the per-process pagetable hack, the "active" kgsl_drm fix, Adreno 225 case in Mesa (freedreno_screen.c), and my stub occlusion query hack. I wasn't on #freedreno when Rob Clark pointed out the libdrm bug I heard about from the Wiki - did you fix that? I'm still getting the assert crashes.
I'll be on #freedreno at some point tomorrow.
gTan64 said:
Are we keeping track of all the necessary patches? I'm on https://github.com/CyanogenMod/android_kernel_samsung_d2, branch cm-10.2_kgsl, with the per-process pagetable hack, the "active" kgsl_drm fix, Adreno 225 case in Mesa (freedreno_screen.c), and my stub occlusion query hack. I wasn't on #freedreno when Rob Clark pointed out the libdrm bug I heard about from the Wiki - did you fix that? I'm still getting the assert crashes.
I'll be on #freedreno at some point tomorrow.
Click to expand...
Click to collapse
I got this to work by using a fairly old libdrm, but a new DDX (xf86-video-freedreno). I haven't fixed the assert bug on the newer ones.
You need to patch the DDX's msm-device.c to set the width to 736 (has to be a multiple of 32), and then disable/comment out/delete where it calls the mode-set function (there's a comment about making xrandr happy in the right place.) I can make a patch soon, but I have a feeling that this is what made the other bug happen with the looping cursor.
edit -- I fixed the looping cursor. A patch is attached...
Youtube video of it working: http://www.youtube.com/watch?v=rh9wmmYuKxY
Tips:
Set the firnware path for the dhd (wi-fi) driver to /system/etc/wifi/bcmdhd_sta.bin (WITHOUT the _b2 buffix, it will be added by the module). Set the nvram file to /system/etc/wifi/nvram_net.txt. Then, add the Android partitions to the /etc/fstab (mmcblk0p14 is system.)
apt-get install xserver-xorg-input-multitouch and then add a config file under /usr/share/X11/xorg.conf.d/ to get the touchscreen working. It will act like a laptop trackpad. You MUST use the multitouch driver. "evdev" will segfault the server on any touch. Note that you can match the TS in an InputClass with its udev name, "sec_touchscreen".
The date that I compiled the working Freedreno libdrm was the date that Ubuntu 13.04 was released. I'm working on narrowing it down to a Git SHA1 revision. I used Rob Clark's repository, not the freedesktop one.
Use the master branch of the DDX, sorry for the earlier confusion.
For battery savings, you might want to cherry pick the DPMS commit from the a3xx branch of the DDX.
castrwilliam said:
How do you stop the SurfaceFlinger (I think that's proper terminology) from hogging the framebuffer?
Click to expand...
Click to collapse
There are two binaries you can execute with adb shell stop/start that kills and restart the android proccesses, allowing access to the framebuffer.
Okay, so 2-D does work with my mods, but I just tried 3-D last night (ran es2gears with the Adreno 225 mod in place on mesa) and the pagefaults returned.
I did notice something about your pagefault reboots, though: they shouldn't necessarily be happening, it's a NULL pointer dereference that can be fixed in the handler by doing this in drivers/gpu/msm/kgsl_iommu.c (function is kgsl_iommu_fault_handler):
Change
Code:
curr_context->pagefault = 1;
curr_context->pagefault_ts = curr_global_ts;
To:
Code:
if (curr_context) {
curr_context->pagefault = 1;
curr_context->pagefault_ts = curr_global_ts;
}
So anyone got any updates for this if not i will start building upon what is there if it is ok
Sent from my SCH-S960L using xda premium
allenjthomsen said:
So anyone got any updates for this if not i will start building upon what is there if it is ok
Sent from my SCH-S960L using xda premium
Click to expand...
Click to collapse
I guess it is OK. Hopefully you can make a dent in this development. Keeping my eye on this thread.
No longer developing for this phone
Unfortunately, this phone hasn't been a good fit for me. I never got very far booting Ubuntu or Freedreno, so I decided to sell it.
For anyone still interested in this project, I believe castrwilliam has the required patches.
When I get my next Snapdragon device (either the new Nexus 7, a Nexus 4, a Galaxy S4, or another phone with Adreno 320 graphics), I will post the Mesa patches for occlusion query support.
I've been trying to update the kernel version on the HD 10 Suez 2017. I am using the sources from this link https://github.com/chaosmaster/android_kernel_amazon_suez/tree/lineage-16.0 on the master Branch I cannot get the the device to boot when building a kernel. However if I use the Android 16 branch, I can get the device to boot but I have an irregularity that I cannot seem to figure out. The screen will go black. It doesn't turn off it just goes black that's if you stop touching the screen or you stop moving the device. aside from that I have not been able to see if anything else is affected but I can get the kernel versions updated at least two 3.18.22 but I haven't continue further because of this the weirdness. I have not tried any other sources as of the moment but was wondering if anybody is run into this problem.
Would this help at all? It’s the googlesource for MTK kernel 3.18
Have you tried building lineage 17 or 18 yet?
https://android.googlesource.com/kernel/mediatek/
https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Mt8176 running Oreo 8.1. Supposedly project treble compatable too. Could this mean 8.1 for the HD10 and/or treble support too?
Fix MediaTek no display bug
MediaTek has a family of SoCs that are used in (among other devices) several Chromebooks, such as the MT8173 used in the Lenovo N23 Chromebook and Acer Chromebook R13, plus the MT8183 in the Lenovo IdeaPad Duet Chromebook. We are working hard to have better upstream support for these devices, especially Enric Balletbo, who has been involved in kernel and Chromebook upstream support for a long time. The displays on MT8173 based devices were not functional when using the mainline kernel, this has been rectified with this kernel release.
The cause of this defect was a conflict between the clock and DRM drivers. He found that two different drivers - the MT8173 clocks controller driver, and the MT8173 DRM driver were using the same compatible string mediatek,mt8173-mmsys. This is a problem since in such cases only the first matched driver will be probed. The other one, in this case the DRM driver, never gets probed and so the display was not made available for use. In a collaborative effort between Enric Balletbo and the MediaTek SoC maintainer Matthias Brugger, a top level mmsys driver (Multi-Media subsystem) was introduced to register the clock and DRM drivers. See 1, 2.
Linux 5.8 probably fixed your display bug. What is the chance of moving this tablet up to android 10/11?
source:
https://www.collabora.com/news-and-blog/news-and-events/kernel-5.8.html
*shouldn't start this way but this first paragraph is for the SAVY Rooted SURFACE DUO USERS whom understand drivers and this whole comcept of the ability to upgrade Adreno drivers, LOOKNG TO SKIP THE FLUFF AND CUT THE CHASE *expedited summary*
You can see your current Display/graphics driver via an app like AIDA64 via the play store (for reference my up to date Android 12 Duo had v502 drivers).... The installation is like any standard magisk module. Simply flash a suitable SM8150(aka snapdragon 855/Andreno 640) driver via magisks/Fox's MMM obtained from this link:
adreno driver for sm8xxx/sm7xxx/sm6xxx
adreno driver magisk module for sm8150 or sm8xxx/sm7xxx/sm6xxx family running on R or newertested on sm8150 and sm8250WARNING : [email protected] has known crash issues when used with magiskWARNING: BLOBS HAS...
www.pling.com
be sure to read the details of the different varients... I recocommend starting with the stock 530. Use at your own risk,.. I recommend the 530 edition, as they have reported no known issues, after install you can verify the current driver version via an app like AIDA64...
Ps.. I used fox's MMM to install the magisk module for the stock 530 first, and after verifyimg all was well, I was able to revert to v502 simply by uninstalling via Foxs MMM & rebooting... so that gave me confidence to install the version I am using currently which ist The December 2022 530 release posted, that also emulates being an ADRENO 730...it's actually as smooth as butter, past first 24hrs & benchmark tests etc (no battery studies by me tho so you'll have to explore that yourself as all I can say is that my temps were much more stable in AnTuTu enroute to higher scores.. also I have not tried the later drivers, opting to stay bug free with the v530 for now, since performance is already top tier imo, playing all games I have at max even prior, but the UI/UX is noticably more responsive and smooth which makes me eager for my pen to arrive as I'm certain these improvements will also translate there as well as the UX for me now has literally zero input/update delay)
**************************
FULL Post below
**************************
Here goes a full post....I am not good at this but yeah..lemme drop something useful relevant and compatible to our devices I'm thanks *this is not any of my work nor is it specifically designed for Surface Duo users yet it works perfectly considering it's targeted for our same underlyimg hardware
------UPDATED/MODIFIED ADRENO 640 GRAPHICS DRIVERS TO BOOST OVERALL PERFORMANCE
...We all know Microsoft is historically behind when it comes to providing users with the latest hardware drivers and the situation is no different here....
Vroom, hello I've been super busy absolutely renovating my Surface Duo and I'm just felt this particular discovery of a mod would be a great one to highlight. Essentially, you more than likely are running outdated drivers for our Andreno 640, to identify exactly what version your drivers are, you can use the 'AIDA64' application to identify which drivers you are running (I'll guess v 502 if your surface is up to date on Android 12 like minea).. nevertheless we all know how important drivers can be to increased performance and implementation of various codimg advancements to enhance existing hardware. Your display drivers are oh so critical to your entire experience while using your device for absolutely any visible task, and especially are the backbone of gaming performance... So because this is such a useful all around mod for all of us looking to stay on the bleeding edge of things, I feel it would be unjust to not share such a useful thing that most Duo users may not otherwise sought out.
This is not my own tweak nor creation, so use this at your own risk. In which case, I will recommend that if your set-up is like mines, in that your Surface is running driver version 502 and is up to date with either Android 12, you should feel pretty safe to install this mod via FOXES MMM... However if you typically flash magisks mods in other fashions, well proceed with caution (only because I just don't know, however it is my belief that if you flash version 530 which has been determined stable and don't touch anything that isn't designed exclusively for OUR SURFACE DUO MODEL SM8150, that you should be safe..
Sorry i am not in the business of posts like these so let me just tell you my process of which I feel safe, however I am not suggesting there is any one correct way as I'm theory ,it's simply a matter of flashing the correct files to magisk..
But because I have to explain something without just assuming you're a modded that's already ready for the links
***********UPDATED AND MODIFIED GRAPHICS DRIVERS FOR SM8150 (SNAP855,A640)*****
Requirements (for SURFACE DUO, SNAPDRAGON 855 (aka **SM8150**), ADRENO 640)
Android 11/12
Rooted
Magisk installed
Fox's MMM (at least that's what I use to flash magisk files)
Optional (Aida64) this app is one of such that will display your driver version in the display tab
*****Step 1
So essentially after verifying with the Aida64 app that you have a Duo with an 855, and ADRENO 640...
************Step to 2
You simply need to head over to this site download the desired drivers
Click files and select an SM8150 driver*
adreno driver for sm8xxx/sm7xxx/sm6xxx
adreno driver magisk module for sm8150 or sm8xxx/sm7xxx/sm6xxx family running on R or newertested on sm8150 and sm8250WARNING : [email protected] has known crash issues when used with magiskWARNING: BLOBS HAS...
www.pling.com
Personal advice/info
*(I person highly recommended 530 as they have been reported essentially flawless and I can testify that even the very latest 530 mod posted that reports itself as being a fake Andreno 730 (this allowing more freedom in certain games that limit options based on hardware) nevertheless I am but a user who hasn't tried everything however I did beginning installing the stock v530 and confirming that after uninstalling with Foxs MMM that!y original 502; drivers safely returned prior to reaching for the recent December 530 fake a730 running ever so beautifully on my device currently *
*********Step 3
After downloading the desired SM8150 driver, use Fox's MMM and select install module from storage then reboot and confirm the updated driver version via AIDA64, that it!
**********DOME!
For more detail here are the original Sources I followed
Honestly this is the key source, where I obtained all the important stuff...which is a telegram channel
Adreno | Konabess support
You can view and join @adreno_konabess right away.
t.me
And I got them telegram link from this thread (of which has information I found ultimately irrelevant in the end but hey..)
Update Adreno GPU drivers Vulkan to latest v615 any Device: Drastically improve performance gaming.
4utech85.blogspot.com
Ummm here are some screenshots of my Duo getting a boost in score (feels bigger than that tho) and now reporting my Duo has a 730 in it lol ps no the drivers doesn't make the display small like mines I change the dpi myself via developer options to make use of the screen lol
@cqqx2
Hello. I have noticed that you created some duplicates of this thread. I'm sure there was a glitch in the matrix
So is this thread your go-to thread now?
Be so kind to let me know.
Cheers,
mrjuniork (Forum Mod)
mrjuniork said:
@cqqx2
Hello. I have noticed that you created some duplicates of this thread. I'm sure there was a glitch in the matrix
So is this thread your go-to thread now?
Be so kind to let me know.
Cheers,
mrjuniork (Forum Mod)
Click to expand...
Click to collapse
Yes this is the correct one
cqqx2 said:
Yes this is the correct one
Click to expand...
Click to collapse
Perfect. Thx for getting back to me.
Cheers