[NDK & VNC] VNC server on Android - Android Apps and Games

I am currently working on VNC server that can run in android native environment (AOSP).
With help from libvncserver and droid-vnc-server, I could load VNC server daemon running on the android.
So far, I tried in Nexus 7, Galaxy Tab 3 (10.1 x86), Galaxy prevail, Nexus 4, Galaxy S3.
Only in galaxy prevail returns a screen installed by libvncserver. I think libvncserver does not deal with 32 bpp.
Whereas droid-vnc-server runs fine in Nexus 7 and Galaxy Tab 3 but once I try to connect to VNC server, the server returns only black screen.
It looks like the problem is that rfb is not correctly getting framebuffer.
Nexus 7 has Tigra and Galaxy tab 3 uses raw fb0 (YAY x86!!)
Did anyone successfully run droid-vnc-server ????

3120
As of now, I was able to:
* make it run on Samsung Galaxy S3 i9300 without code change
* make it run on Samsung Galaxy Tab 3 10.1 with code change:
- using fb method, mmap() call succeed but it appears that the virtual memory is never updated (a black screen if displayed on vnc cleint side) => so I have "simulated" the mmap() behavior by re-readingfb0 again and again (for sure it is not effeicient but it is functional)
However, I cannot make it run on Samsung Galaxy S3 i9305.
=> mmap() fails everytimes on fb0
=> ioctl always reports a bad height of ...50px => it corresponds to the android banner....
=> if I replace mmap() by the looping read algorithm, I could see the 720x50px windows reported on the VNC client side....so not the full screen....
=> using ioctl -rl 28 /dev/graphics/fb0 17920, I confirm that height is well seen at 50px .... so, again, seems to be a wrong value
Pierre

Hi Pierre, could you pls provide the apk? I'd like to test it on my Samsung Galaxy S4 (GT-I-9505).

Related

[Q] MT6516 ciphone a3 touchscreen sensitivity tweak

Hello. My screen bounces when I hold my finger onscreen.
I want to increase amount of filtering of touches.
The closest I got was here: android.modaco.com/content/acer-liquid-liquid-modaco-com/309503/increase-touch-screen-sensitivity-only-tested-on-liquide-1-100-05-based-roms/
----> /sys/devices/platform/i2c-adapter/i2c-0/0-005c/noise
but on my MT6516 based ciphone a3 (iphone 4 clone running android 2.2.1) I have only /sys/devices/platform/mt6516-i2c.0/i2c-0 and no 0-005c
in /i2c-0 there are:
0-0018
0-00aa
0-00fe
but they all contain items with the following names:
/driver
/power
/subsystem
modalias
name
uevent
Help me please
P.S. I can list all the directory containts if that would help?

[concept] Samsung Galaxy NxT a​nd other stuff​

Hi,
In 2012, I was using my Galaxy Note and I imagined my dream version of this great Android device. Having done a lot of sketches, I started to make them more concrete.
You can see these concepts on my website (higher resolution 950x490). Ask me if you need higher resolution (1600x825) :
pubble.com
My projects :
Galaxy NxT (Note and type) ;
MyStuff (for tracking and checking my stuff near me) ;
Beam Station ;
SPEN ;
Music kit ;
UM^2.
Have a nice day,
Christophe SIMÉON from France

[Q] Android (root phone) + debian + asterisk

Hi this is my first time in the forum, thanks for make a excellent Android community.. Ok my question is..
I setup a Galaxy note n7000 rooted phone install debian and asterisk server to use extension for call another android phones in local mode using a wifi tethering of the note and configuring other android phones (galaxy s2 AT&T & Galaxy s3 I9300 native sip client) like extensions inside the asterisk config...
This is the escenario:
Galaxy Note N7000 (root & debian installed) - - - > Asterisk PBX server.
Extension 1 - - - > Galaxy S2 AT&T (root & native sip client)
Extension 2 - - - > Galaxy S3 I9300 (root & native sip client)
The thinks is, i set the asterisk server and test it extension 1 to call extension 2 and everything ia smooth.. But i really need to know if can a gsm radio module be used to make and receive calls for the extensions configured in the asterisk server, for use the galaxy note n7000 like a gsm gateway?
Thanks for your support..

Overflow Property is creating issues on some android devices?? Need Help

I have built a mobile app (a website for mobile users) using Javascript, Xamarin and Asp.net MVC. I have used multiple tools to make sure the app run on multiple platforms. And regardless, what browser visitors are using.
I have tested the application on multiple devices and works fine:-
iOS 7 - Apple iPad Mini 3,Apple iPad Air 2, iPhone 5
Android 5.0 -
Mobile
Samsung Galaxy A8, HTC One E8, Huawei Honor 3X G750, Lenovo A7010
Tablet
Samsung Galaxy Tab A P555, , Huawei Media Pad T1 7.0 U-701 3G
Android 5.1.1 -
HTC One E8, Google Nexus 9
But, when the app was tested with Samsung Galaxy A9, Samsung Galaxy Tab S 10.5 and Tab 4 7.0 with operating system Android 5.0. I got some weird error. If 'overflow:auto' property is assigned to a div, the touch event is disable, scroll is present on the div . The parent div of the problematic div has a property of absolute position.
While using google, I found that you can't use the auto overflow with absolute position attribute. Right now, this issue is only visible with few pages as overflow property is only assigned to pages that describe North-East region of the USA. Please have a look at this page: http://militarybases.co/directory/tobyhanna-army-depot-base-in-tobyhanna-pa/. Right now, I have removed the 'overflow:auto', you can see scrolling is working perfectly(But it is a must requirement).
Right now, I can't remove the absolute position attribute(no way), as I have spent 1 month on the design and can't redesign the whole app. But I also needed the overflow property for ^^ pages.
Failed Solutions I have Tried:
I have used overflow with :scroll instead of :auto.
I also have tried webkit-backface-visibility:hidden.
In Javascript, I have tried 'iScroll'.
I have only 10 days in release and stuck in this mess.

[Beta][ROM] OXI - turn your smartphone into a computer (oneplus3/t nexus 5x and more)

[For moderators : As there is no "General" forum on the "Custom Roms" section, I hope I'm not wrong posting it here. Feel free to move it where it should be!]
OXI - Beta version​Hi everyone!
I would like to present something we have been working on for some time now !
For those who thinks their smartphone can perform the same tasks that a computer can, we would like to allow you to replace your computer with your smartphone, using it on any screen, TV, projector. Basically, it's like Microsoft Continuum but better with Android
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OXI working on NexDock​
What is OXI ?​We're developing a desktop-like environment for Android, implying multitasking, resizing, notification support.
You can use it directly on your main screen but the most interesting is to use a second screen (with MHL/DP or Miracast for instance) to get a desktop environment on it and still use your phone meanwhile.
It might be more clear with some videos : https://goo.gl/6R6rcZ
Our code is now based on LineageOS 14.1, and we're ready to follow the next Android evolutions. We're using LineageOS for compatibility reasons, because we want to be able to try with multiple phones without spending much time on porting.
We're currently in a buiding process, and you can already download the A.2.3 (Nougat) OXI versions for :
- OnePlus 3 / 3T
- OnePlus 2
- OnePlus One
- Huawei Nexus 6P
- LG Nexus 5X
- LG G5 (we have issues with DisplayPort, let us know how is it working for you)
- Samsung Galaxy S7 (Exynos - herolte)
- Samsung Galaxy S7 Edge (Exynos - hero2lte)
- Samsung Galaxy Tab S2 LTE (gts210ltexx)
- Samsung Galaxy Tab S2 wifi (gts210wifi)
- Lenovo Zuk Z1 (ham)
- Xiaomi Redmi Note 3 Pro (kenzo)
- LeEco Le Max 2 (x2)
- ZTE Axon 7
Old versions, we still keep it here for the record
Our code is based on CyanogenMod 13, and I'm currently switching the dev branches to LineageOS 14.1. We're using CM/LOS for compatibility reasons, because we want to be able to try with multiple phones without spending much time on porting.
Right now we have several alpha versions
-> OnePlus 3 (oneplus3)
-> Samsung Galaxy S4 LTE Advance (ks01lte)
-> LG Nexus 5X (bullhead)
-> Galaxy tab S2 9.7 lte (gts210ltexx)
Next alpha-releases are going to be Galaxy Note4 (trltexx) and probably Redmi Note 3 pro (kenzo). Not sure right now. In our wishlist (from our french community), are also S6, S7, LG h850, angler, some Asus...
Click to expand...
Click to collapse
If you want OXI to be on your smartphone, tablet or other device, please tell us! If it's supported by LineageOS, it would be even easier for us .
To have a comfortable experience on OXI, you need to have a mid-range around (from experience, 40-50k score at Antutu is enough). But you need at least 2GB memory, 3GB is better. Basically : more RAM => more apps that can be opened simultaneously without slowing down the system. With 3GB, you can easily open 15 apps. We didn't had enough applications installed to crash our OnePlus 3 .
Usage​I'm going to describe really quickly the basics of OXI. You'll find multiple apps preinstalled in the ROM :
OXI : Launch OXI on main display (phone)
OXI Remote : Launch OXI on the external display (Miracast, DisplayLink, DisplayPort, MHL, HDMI, Chromecast or other...)
For wireless, we recommand the Miracast adapters from Microsoft (Wireless Display v2) or from ActionTech. These adapters are fully compatible with OXI and eliminate completely the mouse lag that you might experience with other wireless adapters (such as Chromecast). Give us feedback, we didn't try everything !
OXI Control : A basic tool replacing keyboard and mouse. Two modes, "Keypad" is a simple touchpad/keyboard, moving the mouse from the phone, and the "Pad" mode is a mirrored touchscreen surface. Very cool to play multitouch games in OXI.
OXI Overscan tool : If you are using OXI on some TV you might notice a part of app missing. You can use this tool to crop the visible surface, adjust until you can see a red rectangle around the blue one.
How to launch an app in OXI :
Start OXI from launcher
Put the mouse in the bottom left part to see the menu button an click on it
Start your favorite apps !
How to connect in Miracast
In the notifications zone, select "Cast" and choose your miracast adapter.
If it's working, you should see your phone mirrored on the screen.
Launch OXI on a second screen :
Be sure you are already connected to another screen and mirroring.
Launch OXI Remote.
If needed, enable permissions
Location permission is just used to show the wifi networks
Overlay permission is mandatory for OXI remote, as we're drawing over a different surface than the main screen.
Click on start
OXI should appear on the other screen and your device should have a new notification with "OXI running". You can tap on this notification to shut down OXI.
Control tool usage
The control tool features two modes :
"Keypad" mode is a remote keyboard and mouse/touchpad
"Pad" mode allows you to interact with the active window (the touch surface is mapped to the active window)
Interface quick-guide
NOTE : this is not updated, the new interface is looking way better (check the videos ! https://goo.gl/6R6rcZ
Roadmap​Please tell us your remarks and wishes for next versions, so we can adjust our roadmap by most-wanted features.
​Short-term
Screenshot tool
Full shutdown of the main screen when using OXI in remote (to save battery)
Customization options (font size, background...)
Medium/long-term
Inbuilt file manager
Multiple instance launching (ex : two Word instances)
Multiscreen support
Disclaimer​
This is an alpha, quite stable but it's not 100% stable or secured.
Installing it is your choice and we're not responsible for any damage or loss of data.
However there's no difference between this and a CyanogenMod ROM for the installation, if you are confident all should be okay. We're using those devices for a long time now, and it works great.
Never forget the golden rule : ALWAY SAVE YOUR DATA, and do nandroid backup before any operation on your phone.
This is an alpha (again), so we might fix a lot of things between releases, so check regularly for updates
Installation/Download :​Installation procedure : It's like LineageOS 14.1 nightlies. You might find better tutorial for your particular phone here . Basically, the way to do is :
1. (If not done yet) : Unlock bootloader
2. (If not done yet) : Flash custom recovery (TWRP or cyanogenmod classic recovery), with fastboot, odin/heimdall, spflashtool...
3. (If not done yet) : In recovery, remember to do a backup !
4. Wipe all the phone (Might not be mandatory if you're already running LineageOS 14.1 nightly)
5. Install the zip file
6. (Optional) Install Google Apps (Open GApps, android 7.1)
7. Restart the phone
That might sounds stupid but with my brand new account on XDA, right now I can't post ROMs in each device forum... I will do that as soon as I can...
For latest releases, check https://getoxi.com/download !
OXI A.2.3 (2017/06/22) - Nougat version !
OnePlus3/3T: https://www.androidfilehost.com/?fid=817550096634781196 - md5 14e3d2b8339820e67bf8d40d89906da4
Nexus 6P (angler) : https://www.androidfilehost.com/?fid=673368273298969591 - md5 77a06b7e67028281c1efa14f73d39d61
Nexus 5X (bullhead) : https://www.androidfilehost.com/?fid=817550096634781195 - md5 631f4ad7e0c9dbccb3217bfe3b672d94
LG G5 (h850) : https://www.androidfilehost.com/?fid=817550096634781193 - md5 91253ff89726aaa50a8f28b280884934
OnePlus 2 : https://www.androidfilehost.com/?fid=961840155545576971 - md5 8d8610d5efa789905bbc0d1997047b5c
OnePlus One : https://www.androidfilehost.com/?fid=889764386195911027 - md5 e27152738b4de60fca08e280049eb48e
Samsung Galaxy S7 (exynos - herolte) : https://www.androidfilehost.com/?fid=745425885120744840- md5 d78b9a7ac25b99615a8b7d0c9c242f15
Samsung Galaxy S7 Edge (exynos - hero2lte) : https://www.androidfilehost.com/?fid=817550096634782269 - md5 f9b8afb0681d1e12ac7bb4b97a061a00
Samsung Galaxy Tab S2 LTE (gts210ltexx) : https://www.androidfilehost.com/?fid=889764386195912098 - md5 eac4e7f670858c383e224bf0187f2b97
Samsung Galaxy Tab S2 wifi (gts210wifi) : https://www.androidfilehost.com/?fid=961840155545578097 - md5 ec9addd2e34503c4878bd2ba90c23c2e
Lenovo Zuk Z1 (ham) : https://www.androidfilehost.com/?fid=817550096634782293 - md5 a9944f74678f6224b7610c8a46325533
Xiaomi Redmi Note 3 Pro (kenzo) https://www.androidfilehost.com/?fid=745425885120744839 - md5 614ea7b4119ee4771d1d98bea7d050d8
LeEco Le Max 2 (x2) https://www.androidfilehost.com/?fid=889764386195913394 - md5 8ec7f1ff0a8bde53fcb5c902690968f1
ZTE Axon 7 (axon7) https://www.androidfilehost.com/?fid=961840155545579364 - md5 bb9a4f6173281fe0f2ab049405f4d411
OXI A.1.9 (2017/02/08) :
OnePlus3 : https://www.androidfilehost.com/?fid=817550096634745003 - md5 463000a46067233f352fe24c4f3002ab
Nexus 5X (bullhead) : https://www.androidfilehost.com/?fid=673368273298929998 - md5 8f1bc2d74d0d3daccd8dab0e00a90d5c
Samsung S4 Advance LTE (ks01lte, I9506) : https://www.androidfilehost.com/?fid=817550096634745004 - md5 65f29339e55df4379d2c0e2ead029dfb
Samsung Galaxy Tab (gts210ltexx, SM-T815) : https://www.androidfilehost.com/?fid=817550096634745005 - md5 ff6ba0d94e4463c33467c71aeee53025
Known issues/Limitations​- Chromecast is supported but won't have any optimization for the latency
- Google Play might be unstable on the desktop environment – the list of apps is not updated (will be fixed soon)
- Authorizing permissions might be difficult in some case. We advice that you also start your apps at least one on your phone screen before launching them in OXI
- You might experience some issues non-related to OXI, it might be related to CyanogenMod 13 :/
- Shortcuts on desktop are saved when exiting
- Bluetooth management inside OXI won't work (yet)
- Some applications (especially some games) won't resize properly. Unity-based games might crash if resized, we're working on it.
- Best experience is with 1920x1080 resolution on an external screen (TV or computer screen).
- Some TV screen won't report the correct real size, so the "size" inside the application might be larger than expected. We're working on allowing you to choose the dpi of each window
- Miracast is enabled up to 1920x1080 resolution and won't support 4K
- Only one instance of each application can be started on desktop mode.
- One application can be started on the phone OR on the screen but not both simultaneously.
- The overscan tool might need to be force-closed its overlay is shown above OXI.
- The ROM does NOT include any Google apps, so you should install them manually (We're usually using Open GApps).
FAQ​- I'm an app developer and my app is not resizing correctly, why ?
-> That's a good question . Contact us and we'll see why !
- Are you using the Android Nougat multitasking/resizing ?
-> No, we are based on Android 6 Marshmallow. Our method is a bit different.
- Why do I need a special ROM for that?
-> We added and modified some parts of the Android system, to high and lower levels, to make OXI work.
- That's cool ! Can I use it everyday?
-> Sure, but keep in mind it's a beta right now, with stability and possibly security issues (still dev-code)
- Did you put any spy or anything ad inside the app or ROM?
-> No. Only love and required modifications for OXI to work. And for the app, we just added a crash-reporting library (Firebase).
- Can you make it compatible with [Phone/tablet model]?
-> We would like to make OXI available to the maximum of devices. Just keep in mind 2GB of memory is a minimum and 3GB is recommended. Let us know and we'll try to make it compatible if we can!
- Can you make it compatible with [application] that currently didn't work in OXI?
-> Give us information about the issue, we will investigate it asap.
- Can I install it with a multi-rom loader?
-> Probably... We actually haven't tried it yet. Let us know
- Who are you?
-> We're a small company called Auxens and we are in France (that's also why this text is probably full of mistakes, please put down the forks!). You can check our website, http://www.auxens.com
Sources:
​Our code is currently based on CyanogenMod 13 (Apache 2) https://github.com/CyanogenMod and http://cyanogenmod.org (sadly down)
We're using kernels and device trees from official CyanogenMod repositories for ks01lte, bullhead, oneplus3 and gts210ltexx.
Kernels (GPL) are available here :
https://github.com/CyanogenMod/android_kernel_samsung_ks01lte
https://github.com/CyanogenMod/android_kernel_lge_bullhead
https://github.com/CyanogenMod/android_kernel_oneplus_msm8996
https://github.com/CyanogenMod/android_kernel_samsung_gts2
Very excited to see multiscreen support as a mid term goal.
Switching to Lineage OS could be a good thing. In particular Lineage OS x86 https://forum.xda-developers.com/lineage/general/unofficial-linage-os-pc-based-android-t3531145
Would allow for PC with multiscreen - great for app developers and app research.
Can you help me compile a lineage is x86 version with OXI for display link external screen?
Does it work OK on [email protected] displaylink DL6950 chipset(such as targus 160 dock)?
xda_nikita said:
Very excited to see multiscreen support as a mid term goal.
Switching to Lineage OS could be a good thing. In particular Lineage OS x86 https://forum.xda-developers.com/lineage/general/unofficial-linage-os-pc-based-android-t3531145
Would allow for PC with multiscreen - great for app developers and app research.
Can you help me compile a lineage is x86 version with OXI for display link external screen?
Does it work OK on [email protected] displaylink DL6950 chipset(such as targus 160 dock)?
Click to expand...
Click to collapse
Hi !
I like the idea of having a vbox x86 OXI available for testing, we'll try to compile an OXI version on this platform
Then some test would be required but if the displaylink driver is enabled in the kernel, it should work for external screen (with USB bus capture by vbox).
For the [email protected] we don't have this kind of hardware here, but if Android supports it, OXI should also work (backgrounds might be slightly pixelated due to their lower resolution). Best would be to ask DisplayLink if they tested the DL6950 chipset on Android devices. And with a android-x86/LineageOS based OXI, it will also depend of the GPU capabilities of the virtual driver.
Its a shame about the 2GB ram Requirement
I would like to run this on my Motorola Razr Maxx XT912 (1GB) as it would allow me to used the laptop dock it was designed to originally use (I actually used the atrix dock as it was easier to get hold of) phone has both micro USB and micro HDMI ports.
I am running LineageOS 13 UTMS_ Spyder on mine and its great waiting for stable LineageOS 14 UTMS_ Spyder and then i will consider an update.
I dont need to run multiple apps at once but will allow me to get mail, open a web browser or an RDP session
So... Is OXI going commercial route?
Or did I read it wrong?
Bb
Hey. Would you add the op3t too? There are enoguh unified Roms, i think its not too hard to add like a New phone? U added the op3 already.
Really woule like to test this with my op3t, thanks!
Great work guys and good luck!
0x4A4A said:
Hi !
I like the idea of having a vbox x86 OXI available for testing, we'll try to compile an OXI version on this platform
Then some test would be required but if the displaylink driver is enabled in the kernel, it should work for external screen (with USB bus capture by vbox).
For the [email protected] we don't have this kind of hardware here, but if Android supports it, OXI should also work (backgrounds might be slightly pixelated due to their lower resolution). Best would be to ask DisplayLink if they tested the DL6950 chipset on Android devices. And with a android-x86/LineageOS based OXI, it will also depend of the GPU capabilities of the virtual driver.
Click to expand...
Click to collapse
Brilliant. Can't wait to test the vbox image with display link via USB bus capture.
The overall direction I would like to see OXI going is
An android version of https://youtu.be/KpYgOQekstQ
Scalable Adaptive Graphics Environment - SAGE SAGE2.
P.S. [email protected] works OK on Remix OS(android x86 based) but no multi monitor support or plans announced for it. The display link website has android drivers although I only managed mirroring vs the way more useful continuum that oxi provides. If I get my hands on the DL6950 based docks that can be daisy chained to 6 independent [email protected] external monitors I will post back results here or other auxens forums. :svetius
0x4A4A said:
Hi !
I like the idea of having a vbox x86 OXI available for testing, we'll try to compile an OXI version on this platform
Then some test would be required but if the displaylink driver is enabled in the kernel, it should work for external screen (with USB bus capture by vbox).
For the [email protected] we don't have this kind of hardware here, but if Android supports it, OXI should also work (backgrounds might be slightly pixelated due to their lower resolution). Best would be to ask DisplayLink if they tested the DL6950 chipset on Android devices. And with a android-x86/LineageOS based OXI, it will also depend of the GPU capabilities of the virtual driver.
Click to expand...
Click to collapse
Just to check if you guys are still commited to a vbox x86 image ? Is this still on
xda_nikita said:
Just to check if you guys are still commited to a vbox x86 image ? Is this still on
Click to expand...
Click to collapse
No news from them even on french forums (they are french)... Don't know what's going on. They've been pretty quiet.
Work on rr latest build?
Hi everyone! Sorry for the lack of news. We've been mega-busy after the MWC...
We've been working on a new UI, on the Nougat port (the confectionery was harder than expected ), on a Miracast fix for Nougat/LineageOS, on bugfixes and security improvements.
We will try to share soon some other CM13-based (with new UI) OXI rom, while we are still working on Nougat .
For Android X86-port, it's not done yet, but we're working on it too (would be also very useful for debugging).
Any news for oneplus 3T?
I noticed there is a download for the Note 4 N910F on your website. Has that been confirmed working on a Note 4?
What devises would you like to see?
Hey dev team,
Could we possibly see versions for the nexus 6 and Samsung Galaxy tab 10.1 2014 edition(WiFi)?
Appreciate all of your hard work!!! ?
So, we have been working hard, and finally we can provide you a beta version of OXI on several devices !
We're now based on LineageOS 14.1 (finally, nougat !) and we are currently building OXI with multiple devices. We'll add soon others devices officially supported by LineageOS.
The new version, A.2.3, is now available for Nexus 5X, OnePlus 3 & 3T (same package), OnePlus 2, OnePlus One, LG G5 (however we have issue with DisplayPort right know). Miracast should work.
You can watch new demos on our new youtube channel https://goo.gl/6R6rcZ and check our website https://getoxi.com which is the most up-to-date place to look up on OXI (but also our Facebook page and Twitter account )
His is awesome news. Im downloading it for try in my OnePlus One.
Do you have plans to add a range of cheap and mid level devices? Lets say, Doogee Mix for example. It has a good potential (it seems) but it's not a flagship. This would be nice for emergent countries.
Also, there's anyway to contribute for you guys? like a patron or something?
I have tried to install in my opo and Ive got error: 7 in twrp.
Wanted devices: Doogee MIX as soon it be launched.
ogabriel said:
I have tried to install in my opo and Ive got error: 7 in twrp.
Wanted devices: Doogee MIX as soon it be launched.
Click to expand...
Click to collapse
Try with another twrp version and check the md5 of your download as well.
@Ox4A4A team,
Will try as soon as I can. But I have no more Chromecast.... It had a little "accident".
Looking forward to the Note 4 port.

Categories

Resources