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

[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.

Related

[ROM][GT-S8000] Android for non-android phone [JétDROID] CyanogenMod 7.1 unofficial

Jét-Droid project
This mind-blowing development project has successfully ported Android to the non-android smartphones by Samsung S8000 and S8003
Dual boot (JetQi bootloader) preserves stock OS on the internal memory and boots into Android from the external micro SD card
Altough JetDroid project was done also for Samsung S8003, I will refer here only to S8000 as I couldn't test any of this with the S8003
NEW DEVELOPERS ARE WELCOME
Click to expand...
Click to collapse
INDEX:
This post includes:"JétDroid" project introduction / S8000 hardware info / development info
Post #2: Install guide for users / download links / attached files
Post #3: ROM CyanogenMod 7.1 (State-of-the-Art ROM to 2013/2014)
Post #4: Older ROMs and CyanogenMod 9 experimental
CREDITS:
All the credits and respect goes to the guys who have grounded, carried and brought to us this project, its developers and contributors:
dopi
KB-JetDroid
Carlos_Manuel
aleksey.4erepanov
and many others: please post here and I will update the list
The project home was not on the XDA but here:
External links (old):
Development homepage of JétDroid project
Forum of the JétDroid project
Click to expand...
Click to collapse
Guys from JetDroid project are most welcome to join this thread, I'm sure some of them are here on the XDA forum
HARDWARE INFO
SAMSUNG Jét S8000
"Smarter than smartphone"
With this enormous fanfare worldwide, (with the General Manager for the UK who tought that the Samsung Jet S8000 is better than the Apple iPhone 3GS) Samsung's flagship handset as of 2009, Samsung Jet S8000 was released with this not really modest marketing tag that can be found still nowadays on internet.
Yet, altough released back in 2009, the hardware of the S8000 is even as of beginning 2014 still better than many modern low-end android phones and throughout interesting target for the android porting development:
{
"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"
}
Technical information:
Manufacturer: Samsung Mobile
Availability by country: June 2009
Compatible networks: GSM 850/900/1800/1900 MHz
UMTS (3G): 900/2100 MHz
HSDPA: 3.6Mbps
Form factor: Touchscreen bar
Dimensions: 108.8(H) x 53.5(W) x 11.9 mm(D)
Weight: 110 g
CPU: 800 MHz processor
Display: 3.1" (79mm) 16M color WVGA AMOLED touchscreen, 480 x 800 pixels
Platform: Latest TouchWiz 2.0 UI with Motion UI, Media Gate 3D and Smart unlock
Data inputs: T9, Abc
Memory: 2GB internal / removable storage: microSD up to 16 GB (microSDHC compatible)
Rear camera: 5MP (2,592×1,944 pixels) auto-focus, with dual LED flash, geo-tagging, image stabilization, face detection, Smile Shot, Wide Dynamic Range (WDR) and D1 video recording at 30 fps
Connectivity: Wi-Fi, Bluetooth 2.1 with A2DP, standard microUSB port, GPS receiver with A-GPS, 3.5mm audio jack, TV out
Media: MP3, AAC, AAC+, e-AAC+, WMA, AMR, WAV, MP4, MPEG4, H.263, H.264, WMV, DivX, and XviD
Connectivity: Wi-Fi (802.11b/g), AGPS, Bluetooth 2.1 with A2DP, and USB 2.0 (microUSB)
Other: Accelerometer for screen auto rotate and turn-to-mute, electronic compass, FM radio with RDS, DNSe and SRS sound effect, Touchscreen, full web browser (Dolfin), and haptic touch feedback
Battery: 1100 mAh Li-ion
Battery Talk Time: up to 8.2 hours
Standby: up to 442 hours
CONS of Samsung's OS:
The hardware of this nice looking handset is excellent but crippled by its poor operating system and even poorer support from Samsung
No additional widgets / applications to download
Official firmware support is non existent
The Exchange sync software doesn't work with gmail
No text smiley's
Can't copy/paste text
GPS drains the battery (Wi-Fi also)
Java support is poor
Motion gate is useless
Memo's limited to 100 characters
The phone with Samsung's OS is laggy
Click to expand...
Click to collapse
GET A JETDROID DEVELOPER !!
DEVELOPMENT INFO: about "JETDROID"
Target: porting Android OS to non-android devices Samsung Jét GT-S8000 (and GT-S8003)
"JETDROID": HOW DOES IT WORK?
Linux-based hardware of Samsung Jét is in general capable of booting into Android OS
Boot into Android OS is done here directly from external SD card, not from internal memory
JetDroid partition of the external (removable) SD card is formatted with Linux OS to ext2 or ext3
JetQi bootloader must be flashed on the S8000, boot into Android is possible with 2-buttons-combo
Original Samsung's firmware remains unmodified and the S8000 can also boot normally into stock OS
JETDROID DEVELOPMENT SOURCES:
JetDroid development: open source info is HERE
JetQi bootloader (how-to-build) source: GitHub
Jet-Kernel: GitHub
Jet-Kernel_3.0: GitHub
Jet-Platform: GitHub
BUILD A ROM - DEVICE REPOSITORY SOURCES:
How to build a Jét ROM: CLICK HERE
How to build a Jét kernel: CLICK HERE
DEVELOPMENT STATUS (to early 2014):
modification of the JetQi bootloader is possible for succesful porting of the CWM recovery
drivers development necessary for enabling SIM card functions (calls, SMS)
State-of-the-Art ROM: CyanogenMod 7.1 (build 20130603 by Carlos_Manuel: DOWNLOAD IT HERE)
JETDROID project / external links:
Development homepage of JétDroid project
Forum of the JétDroid project
Click to expand...
Click to collapse
Flashing guide
FLASHING GUIDE
DISCLAIMER:
Code:
* [i]i am not responsible for any bricked devices, marriage crisis,[/i]
* [i]sleeples nights, termonuclear wars, electricity blackouts, short[/i]
* [i]circuits, or for bad weather in your region that will brick your phone.[/i]
* [i]this thread is for an older device, download links may dissapear by time[/i]
* [i][b]warning:[/b] bootloader flashing is just always risky proceeding that[/i]
* [i]could hard-brick any device. Everybody is flashing on his own wish- and risk[/i]
Click to expand...
Click to collapse
INSTALL CHECKLIST:
S8000 must be unlocked (both sim and network) otherwise hard-brick by flashing of the bootloader is possible
Samsung mobile usb driver must be installed on your pc and device recognized by the pc
Compatible original firmware (list in the guide) must be flashed with multiloader v.5.62 (attached)
After that, the JetQi dual-boot bootloader must be flashed with multiloader v.5.62
External SDHC card must be inserted in the phone (the faster SDHC card is, the better)
Card gets formatted by running Samsung OS with Ubuntu/Linux OS (running Ubuntu in the Virtual box or as "Test Ubuntu" (live CD) is also possible)
Unmount TFLASH volume (careful here, as MFLASH is internal partition of the stock fw of your phone!!!!)
Better use "Disk Utility" than "Gparted" to format the SDHC card and format first partition as "Master-Boot-Record" (ext2) for JetDroid ROM
JetDroid partition size for JetDroid can be between 1550-1950mb, create another partition (rest) as FAT
Mount both volumes/partitions (ext and FAT)
Extract in Ubuntu downloaded ROM and paste all files on the JetDroid partition
In "Terminal" (Ubuntu) set permissions: (sudo chmod -R 777 /media/yournameforjetdroidpartition(withoutspaces)
Now "Safely remove parent drive" (phone) and switch off the phone
Boot with 2-buttons-combo into Android OS (call&power buttons)
Click to expand...
Click to collapse
GUIDE:
here is an old JétDroid installation guide
you can use also this guide
and here is the same installation guide in german language
DOWNLOADS: (all links are still working)
download here the files for the old Eclair 2.1 build
this JetQi bootloader works on my s8000 (also attached on the bottom of this post)
another JetQi bootloader links: jacquesjk-bootloader or this one here (both untested by me)
multiloader v.5.62 (flashing software for compatible stock rom) is attached on the bottom of this post
Buttons on the s8000:
functions of the buttons:
View attachment 2508844
(click to enlarge)
Click to expand...
Click to collapse
download files:
State-of-the-Art ROM for JETDROID
NOTE: my own reccomendation is to use only the very fastest SDHC cards you can get. Don't even consider anything beyond Class 10, otherwise you will face unstable and laggy performance. Sandisk extreme 80Mbps will work the best.
Click to expand...
Click to collapse
CyanogenMod 7.1
by Carlos_Manuel
DOWNLOADS: CyanogenMod 7.1 (build 20130603): DOWNLOAD IT HERE
(Carlos_Manuel's site)
WHAT IS WORKING:
ADB (everything works: push/pull, installing apps, logcat, permissions changing etc)
WiFi
Root (I did it with the SuperOneclick 2.3.3 root tool by Shortfuse)
Touchscreen fully working
Bluetooth (send & receive)
Play Store / Google account sync
Apps (all works: root & no-root)
CM7.x features: like multi-languages support etc
WHAT IS NOT WORKING:
(as in other JetDroid ROMs):
SIM card: no connection
none of the SIM functions (calls, SMS, mobile data)
battery status displays always 70% (charging works normally)
Click to expand...
Click to collapse
All credits for this ROM to dopi, KB-JetDroid and @Carlos_Manuel
SCREENSHOTS:
Click to expand...
Click to collapse
JétDroid: ROMs overview / earliest to latest
JétDroid and me: pros & cons
At this point, I will just report my own experience with all other ROMs that I was able to try so far on my S8000
* * * * * * * this comparison is therefore just subjective and by no mean a fair or complete overview * * * * * * * *
Click to expand...
Click to collapse
Out of my own experience, I can report here only of four ROMs that I was able to boot on my S8000. Regrettably, I have missed whole this exciting development project although I own this phone since 2009: I simply never browsed in internet, couldn't even imagine to boot into Android OS with it. If you ask me "is it worth it"? I will say: yes, definitely! One can use Samsung's TW2.0 for calls, SMS and mobile internet and Android with WLAN. It is matter of taste, I really enjoy to use Android with my Jét, especially my favorite ROM, the CM7.1 by Carlos_Manuel
VIDEO COMPARISON:
**** TouchWiz **** Eclair (2.1) **** CyanogenMod 9 (4.0.4) **** CyanogenMod 7.1 ****
For watching in 1920x1080 HD, please CLICK HERE to watch it directly on YouTube
Click to expand...
Click to collapse
JETDROID ROMs - functionality comparison:
Eclair 2.1 (JetPlatform0.2 and 0.3)
ADB: NO
WiFi: NO
Bluetooth: (send & receive) NO
Root: NO
Touchscreen: YES (fully working)
Google (Play Store / account sync etc): NO
Apps: YES, at least all of those you can install
Android version features: YES (languages, etc)
Functionality: unstable, laggy, freezes often, no tone (indication works)
Comment: despite just few working functions, developing of this ROM was simply the revolution in person and excellent base for further development. A key-feature (JetQi bootloader) was invented short before this stage. Reportedly, Wi-Fi was working on 0.3 platform, however I wasn't able to turn it on, or I have used wrong files on my SDHC card.
CyanogenMod 6 (Froyo 2.2)
Unfortunatelly, I wasn't able to boot this ROM. I've tried all tricks but the ROM I found and downloaded simply didn't boot. I am grateful if anybody gives me a hint where to download working one.
CyanogenMod 7.1 (Gingerbread 2.3.7)
ADB: YES (everything works: push/pull, installing apps, logcat, permissions changing etc)
WiFi: YES (fully working)
Bluetooth: YES (fully working: send & receive)
Root: YES (I've gained root access it with the SuperOneclick 2.3.3 root tool by Shortfuse, that uses ADB to install Superuser and busybox)
Touchscreen: YES fully working
Google (Play Store / account sync etc): YES (all working)
Apps: YES (all apps work here: no matter if root or no-root ones)
Android version features: YES (all working)
Functionality: altough slow compared to modern devices, with fastest SDHC cards it is stable and not too laggy, it makes definitely fun to use it. Not so with slower SDHC cards: unstable und laggy, CPU gets warmer then.
Comment: overall best ROM that I could try. If some day a Jét-driver for the SIM card get succesfully developed and some recent Linaro codes implemented in the kernel to boost its performance, this ROM would be just perfect for the S8000
CyanogenMod 9 (Ice Cream Sandwich 4.0.4)
ADB: YES... (not fully, installing Apps via ADB works, read comment)
WiFi: NO (freezes)
Bluetooth: YES (I didn't try data transfer)
Root: ALMOST (read comment)
Touchscreen: ALMOST (cursor circle works, also click, but not "hold" click, therefore difficult scrolling)
Google (Play Store / account sync etc): NO (no Wi-Fi, no SIM card, so no connectivity)
Apps: YES
Android version features: YES (multi-languages, time zones, correct time displaying)
Functionality: early development stage, tough obviously great potential for the S8000 in ICS, hopefully it will be developed further
Comment: with this ROM as-is, ADB was working, but it wasn't able to install apps. After just a simple experiment of copy&paste of few files from the CM7.1 ROM (cat, getprop, sh) I was already able to install the Apps and nearly gained root access. Some basic files are missing in this ROM that is bit left alone in its early stage of development (ADB reports: rm not found so it can not delete the files). This ROM has potential to be great and should definitely be developed further, the device benefits of ICS codes, feels smoother and fast.... you can see that it boots into OS about 7sec faster that CM7.1, altough it has a slower SDHC card (about 20% slower). So ICS could likely be "The One" ROM for S8000, by gaining all functions that CM7.1 already has working. I didn't try to create logcat for Wi-Fi enabling, maybe it would give an answer what to do, it is anyway nearly working....
Click to expand...
Click to collapse
WHAT IS NOT WORKING (in all JétDroid ROMs):
SIM card: no connection
none of the SIM functions (calls, SMS, mobile data)
Click to expand...
Click to collapse
Nice!
But credits goes to Dopi and KB-JetDroid from jetdroid.org / Github.
My built ROM is optimized and includes some other stuff like librsjni file for live wallpapers, etc.
Hopefully someday Dopi and KB-JetDroid starts working on ICS, because it's fast on Jét.
@Carlos_Manuel
OK, I will update the OP under "credits" altough you definitely deserve them as well: I couldn't even find anywhere GB roms by dopi and KB-JetDroid and some of which I found and downloaded didn't boot
tetakpatak said:
@Carlos_Manuel
OK, I will update the OP under "credits" altough you definitely deserve them as well: I couldn't even find anywhere GB roms by dopi and KB-JetDroid and some of which I found and downloaded didn't boot
Click to expand...
Click to collapse
Check out Dopi's JetPlatform 0.5 thread, it's a CM7.
Carlos_Manuel said:
Nice!
But credits goes to Dopi and KB-JetDroid from jetdroid.org / Github.
My built ROM is optimized and includes some other stuff like librsjni file for live wallpapers, etc.
Hopefully someday Dopi and KB-JetDroid starts working on ICS, because it's fast on Jét.
Click to expand...
Click to collapse
Kudos mate
---------- Post added at 06:04 PM ---------- Previous post was at 06:02 PM ----------
tetakpatak said:
@Carlos_Manuel
OK, I will update the OP under "credits" altough you definitely deserve them as well: I couldn't even find anywhere GB roms by dopi and KB-JetDroid and some of which I found and downloaded didn't boot
Click to expand...
Click to collapse
Thks for opening this new thread Tetakpatak
I think i'm going to dust off my jet again.
My resistive touchscreen just died on me... cant play with my jet anymore...
Will remember this one as one of the best cellphones i had... shame that samy did.not used android on it.
Sent from Asus MemoPad FHD ME302C
Oh, pity..... I'm sorry mate
I also really like my S8000. It runs whole day long as radio (app Live365) on Carlos_Manuel's CM7 Android.
tetakpatak said:
Oh, pity..... I'm sorry mate
I also really like my S8000. It runs whole day long as radio (app Live365) on Carlos_Manuel's CM7 Android.
Click to expand...
Click to collapse
I'm trying to get one 2nd hand on Ebay... but since the touchscreen is resistive i'm kinda reluctant...
I was able to remove the "digitizer" from the phone (not glued to the screen) but replace part are way too expensive for me to just tinker with the Jét...
I really liked my jét even if was just to tinker with... One of the best buys i did.
Your phone didn't get broken because of flashing a JétDroid I hope?
The back part gets quite warm, reading a SDHC card costs CPU hard work , it seems.
tetakpatak said:
Your phone didn't get broken because of flashing a JétDroid I hope?
The back part gets quite warm, reading a SDHC card costs CPU hard work , it seems.
Click to expand...
Click to collapse
No of course not.
The digitizer just stop working on most parts of the screen... and its the resistive layer fault because if i press it really hard sometimes it works... its was to expect after all resistive tech like this have a limited number of uses until it "breaks".
2nd hand models are quite cheap on eBay but i wonder if the digitizer is in good condition, since i only need that part to reassemble my good old jét...
Good luck
tetakpatak said:
Out of my own experience, I can report here only of four ROMs that I was able to boot on my S8000. Regrettably, I have missed whole this exciting development project although I own this phone since 2009: I simply never browsed in internet, couldn't even imagine to boot into Android OS with it. If you ask me "is it worth it"? I will say: yes, definitely! One can use Samsung's TW2.0 for calls,and SMS and mobile internet and Android with WLAN. It is matter of taste, I really enjoy to use Android with my Jét, especially my favorite ROM, the CM7.1 by Carlos_Manuel[/COLOR]
Click to expand...
Click to collapse
This phone is fantastic, I have one that is indistinguishable from brand new hardly used, it's a new replacement for a digitizer problem , I have never stopped hoping this push would come, there are millions of us who still have this phone, I hope what your doing is advertised widely. Pity samsung didn't release the source code they've missed a massive chance to increase their Street cred with the whole tech buying public and change public perception of their support. Might not be allowed, but I bet many would give a small donation for a fully completed modern rom. Best wishes from me and from many.
samsungwarrior said:
This phone is fantastic, I have one that is indistinguishable from brand new hardly used, it's a new replacement for a digitizer problem , I have never stopped hoping this push would come, there are millions of us who still have this phone, I hope what your doing is advertised widely. Pity samsung didn't release the source code they've missed a massive chance to increase their Street cred with the whole tech buying public and change public perception of their support. Might not be allowed, but I bet many would give a small donation for a fully completed modern rom. Best wishes from me and from many.
Click to expand...
Click to collapse
I totally agree. The hardware is really good and sturdy, so with the source code, dopi & co would probably easily port ICS similar way like in Badadroid project (with Samsung S8500 and S8530 with Bada OS, last model between S8000 and the revolutional Galaxy S1, i9000) instead of taking the hard road of hardware hacking.
Boot of Android OS from the external SD card slows the phone massively down, as the card slot is a bottleneck.
tetakpatalked from N7100
Disculpa se que el articulo es viejo pero me gustaría saber si después de instalar android en mi jet puedo hacer llamadas usar las conexiones de red ?
yohanab said:
Disculpa se que el articulo es viejo pero me gustaría saber si después de instalar android en mi jet puedo hacer llamadas usar las conexiones de red ?
Click to expand...
Click to collapse
Ola. Mi Castellano es muy limitado. Lo espero que entiendas Inglés.
This project, as far as i know, was abandoned years ago :/ ... as i recall it does not the cell network chipset (i might be wrong here, i was a few years ago) but i think WiFi was ok and working.
The resistive part of my Jet unit died last year and i just trashed the unit so i cant really test it now. Hope the info helps.
Yes, exactly. Wifi works, not so the mobile network in Android. One needs to reboot to the stock UI to use mobile networks. I still have my S8000 and both android and stock UI are working.
Sent from my GT-N7100 using Tapatalk
Hi there, I know this is an old thread, but I'm planning on installing it to my hibernative Jét S8000, and was wondering myself if there is a way to extract Sim relative stuffs from Stock Samsung OS and implement it to JétDroid Rom? A question just like this cause, I saw that pretty all of the JétDroid Roms have a problem with Sim, so, is there any way of doing so??
Anyway, thanks for any revelant- or normal- answers,
See ya
Oxydeme said:
Hi there, I know this is an old thread, but I'm planning on installing it to my hibernative Jét S8000, and was wondering myself if there is a way to extract Sim relative stuffs from Stock Samsung OS and implement it to JétDroid Rom? A question just like this cause, I saw that pretty all of the JétDroid Roms have a problem with Sim, so, is there any way of doing so??
Anyway, thanks for any revelant- or normal- answers,
See ya
Click to expand...
Click to collapse
Well, AMAIK, the development project described in this thread was the only succesful porting of the Android to the S8000, running it from the external memory card.
None of the ROM versions has ever made it to work with the SIM card if the S8000 was booted in Android.
Sent from my GT-N7100 using Tapatalk

Kitkat 4.4 update is now available for Jiayu G4S

* Source - bbs.ejiayu.com
Jiayu officially Rollout Kitkat 4.4 (Trial ver. / Beta ) for Jiayu G4S .
New Rom is available on Needrom.com. & bbs.ejiayu.com
Whats new :-
New and smart dialing Caller First, the new dialer will recommend common contacts based on your usage habits, automatic intelligent, easy Speed ​​Dial; Meanwhile, some well-known companies or service numbers of calls, using Google's online database to match automatically displays the name, even if your phone does not store them .
Optimized for RAM. KitKat Android 4.4 has been optimized for the RAM occupied even fluent only 512MB RAM on some older phones to run. It also further optimized the system is running low with hardware, seems to be better in many smart wearing running on the device.
New icon, lock screen, start the animation and color scheme before the blue-green color design is changed into white / gray, more minimalist, another style icon further flattening, also built some new animations, the whole interface more beautiful, less resource-intensive. In addition, also joined the translucent style interface to ensure that the status bar and the navigation bar to play better results in the application.
Fullscreen mode :
now, whether you are looking at books, or use any application that can easily enter into full-screen mode, hide the virtual keys to bring more investment experience. Simply slide the screen edge, you can retrieve the keys, but also very convenient.
Wireless printing :
Photos you can use Google Cloud Print wireless printing your phone, documents or web pages, other printer manufacturers will quickly follow, publish related applications.
Screen recording feature :
Android 4.4 adds screen recording function, you can record all operations on the device for a period of MP4 video, and choose the aspect ratio or bit rate, and even add a watermark.
Low power audio and positioning modes :
Android 4.4 added a low-power audio and positioning mode to further reduce power consumption of the device.
New Bluetooth profile and infrared compatibility :
Android 4.4 built two new Bluetooth profile, you can support more devices, lower power consumption, including the mouse, keyboard and handle, but also be able to exchange with Bluetooth Map . In addition, the new infrared remote control interface can support more devices, including TVs, switches and so on.
Note :-
1, the upgrade to Android 4.4 version of Android 4.2 version must use the wire brush way to be, does not support the card brush approach. Please note before upgrading users to back up important data on the phone's original, to prevent loss.
2, released the first edition preferred domain version of Android 4.4 experience, there may be some BUG, yet to be discovered and perfect for user testing and experience to use.
3, for the Google Android 4.4 system software version newer, popular applications APK software may have some compatibility issues with pending application developers update the software version.
Awesome! I will try it as soon as i have time, someone antutued it??

[RESEARCH][ANT+][CM12.1/CM13.0][HLTE]How to implement ANT+ on AOSP Roms 5.1.1+

Hello community,
after many hours of research and different attempts to get ANT+ working with CM12.1 on my N9005 I want to start some kind of information exchange on XDA to bundle all previous experiences.
ANT+ is a low power bluetooth mode, which is used to connect professional sports/outdoor equipment like heart rate belts, speed or cadence sensors, powermeters and so on. BTLE (bluetooth low energy) mode is provided as an alternative, but most equipment manufacturers do no support BTLE because ANT+ is optimized for stability and durabiltiy and has some advantages over BTLE (i.e. optimized device protocols for lower energy expenditure).
There are two smartphone manufacturers out there which support ANT+ natively (depending on the built-in hardware) since some generations - Samsung and Sony. (I read about the OPO (One Plus One) got native ANT+ support in the meantime.)
The qualcomm edition of the Note 3 (N9005) uses a broadcom 4335 wifi/bluetooth chip which is capabable of ANT+. Samsung stock roms provide native ANT+ support but if you switch to a newer CM12.1 or CM13 rom (maybe because of the great performance or KNOX and other bloatware issues), you will unfortunately loose the native ANT+ support. The same goes for the S4 and S4 active too like mentioned in several threads and communities.
There were several attempts to get ANT+ working on CM12.1. One of te most important attempts was made by @christer12 which seemed to be successful:
http://review.cyanogenmod.org/#/c/110547/
http://review.cyanogenmod.org/#/c/110396/
Some days later he stated on his twitter page "ANT+ on hlte don't work properly, because ANT+ in cm-12.1 is not properly integrated for bcm4335.. =(".
ANT-wireless provides a kind of "reference architecture" for the inclusion of ANT+ in Android roms:
https://github.com/ant-wireless/ANT_in_Android
But when comparing this approach with the one used in Samsung stock roms there are some differences. Samsung does not use a native library called "libantradio.so". Their AntHALService (interface between vendor hardware drivers and common ANT+ software) is built on the broadcom SDK which uses the class package com.broadcom.bt (with it's own radio manager implementation). This package is integrated in the Samsung stock rom /system/framework folder as java archive (JAR).
So my intention was to switch to the samsung aproach and use the broadcom libraries (in combination with Samsung vendor libs) for a "custom" AntHalService. That worked out ok, but at the moment I'm experiencing some difficulties in testing. The virtual machine of my android studio does not support bluetooth out of the box and my device (CM12.1) show a runtime reference error (NoClassDefFoundError) while accessing the broadcom classes. All classes are in the APK/classpath but CM12.1 seems to behave differently.
As I'm interested in other experiences and new ideas I just wanted to start this thread.
Thanks in advance and regards,
B
Reserved
I found this very interesting thread of xda-user @iRant which shows neccesary changes in the CM mainline code and seems to be the base for the ANT+ support in CM11:
http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990
https://android-review.googlesource.com/#/q/owner:"James+Bootsma"+status:open
This solutions implements - amongst others - some vendor specific functions/commands (*VS) in the Bluetooth stack which were missing in the mainline code.
https://play.google.com/store/apps/details?id=com.z2software.antplus
Wasn't it working ?
newintage said:
https://play.google.com/store/apps/details?id=com.z2software.antplus
Wasn't it working ?
Click to expand...
Click to collapse
Sorry for the late reply. I messed up my phones CSC and had to reflash my phone several times. ?
Thanks for the link. ? I found some posts concerning ANT+ enabler but they did contain inconsistent results. So I did a little research and recognized that the last update from 2015/12/20 seems to fix some CM problems. Reading that I bought the app to try it out myself.
Results:
In general it seems to be working, but not really reliable yet. I got some "adapter not detected" messages and had to reboot my phone two times to reactivate bluetooth again. I will send an e-mail to the developer to analyze the problems.
As CM is open source a "commit solution" should be more "integrated" but I could live with a workaround if it's really reliable.
I am very interested in this as I was using my tablet (Samsung tab pro 10.1) to connect to my Garmin via ANT+. Since using a CM based custom ROM there is no longer any support. I was using a custom ROM on my Note 3 that was based upon a stock samsung one that included support for ANT+. If it can be included there then why not on CM ROMS?
ANT+ enabler used to work for CM 12.1 , but then it stopped working , i just tried it again and not working. if you flash Teamsek V17 , it starts working, but anything after 17.2 and things stop working. I have NOT tried CM13. (I assume the result is the same)

[APP][4.0.3+]Device Info HW

Device Info HW
version: 5.8.3
Device Info HW is a hardware and software information app for Android devices.
App trying detect components of your smartphone to provide complete information about device's hardware.
Now detection is supported for lcd, touchscreen, cameras, sensors, memory, flash, audio, nfc, charger, wi-fi and battery; if that possible for your device.
I think app is interesting and useful for users and developers who build kernels or android.
App has a quick navigation, fresh design. Also supports dark, black theme (in PRO version or 2 week in free)
You can switch by tab or use navigation panel. Many items are clickable and you can go to another tab or menu.
On recent devices reading some information is blocked.
App trying provide maximum information as possible. If you have root, app can read more (switch in settings)
Components
LCD - model. For recent android detection require root.
Also you can check the colors in lcd test.
Touchscreen - show model, also you can check how much fingers are supported in multi-touch test.
Camera - hardware info (model, vendor, resolution) and software info by API.
If can't detect camera model, sometimes available a list of supported cameras.
Detailed info about SoC in you device
CPU : model, cores, clusters, family, abi, governor, frequency
GPU : model, vendor, opengl, frequency, list of extensions
Click on the clock speed to open CPU monitor
System: complete info about your firmware build.
Memory: type lpddr and for some devices operating frequency.
Flash: chip and vendor emmc or ufs (scsi).
You can go to the memory tab and see usage of memory and storage.
Battery: base info and for some devices available extra info:
- Discharging speed is current consumption
- Charging speed is charge current minus current consumption
- Power profile - encoded by manufacturer for calculate consumption
* Kernel profile
* Model
Thermal: temperatures by thermal sensors
Sensors: availability of basic sensors and tests for them
Applications: you can quickly find apps and see info about it, also provided system apps
Drivers: you can find other chips used in your device.
Partitions: list of partition and their sizes.
PMIC: list of power regulator voltages which applied to the components.
Wi-Fi: info about connection
Bluetooth: supported features
Input devices: list of input devices.
Codecs: decoders and encoders, drm info
USB: connected devices by otg
Extra options:
- Show i2c address of the chip
- Open engineering menu for mtk and xiaomi
- List of CPU codenames for Qualcomm, mtk, HiSilicon
Devices database
You can find info for other devices, compare and check similar drivers. It available on web page: deviceinfohw.ru
Also you can upload your device info. See to the Info Center.
PRO VERSION
• Theme
Supports all a light, dark and black theme, choose what you like.
In the free version, black available 2 weeks for the test.
• Report
You can create a report with information about the device.
It will be saved in file HTML or PDF format.
You can open it or send to email by share button.
See example:
deviceinfohw.ru/data/report_example.html
• Copy text
Copy text by long press in info lists.
• New design of battery tab with charge / discharge chart
• Device list
List of i2c, spi devices.
It's useful when available many chips or they uncategorized.
Also this supports development to improve app.
Note:
Not for all devices can read drivers info, it's depend on soc, vendor. If you want help, then upload your device info.
If you want translate app for your language or have interesting ideas or found bugs, write me to email or forum.
Requirements :
- Android 4.0.3 and above
Permissions :
- INTERNET is required for upload device info. It's use only for manual upload.
- CAMERA is required for getting camera software characteristics for old camera api.
- ACCESS_WIFI_STATE is required for info about wi-fi connection.
Google Play:
https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw
{
"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"
}
Awesome App. Well Done!
Tested on more than 10 Mediatek Devices, no issues found. I'll start to upload all my device's hardware info to your database as soon as possible.
Nice App Sir Keep Up The Good Work! :highfive:
Hey OP! Thank you very much for this app :good:
Version 3.0.5. Now we see in the Camera tab
I would like to that looked so
Please, if possible....
Good work bro
New version 3.3.1 released.
- Support samsung exynos platform: detect cameras, wi-fi (tested on galaxy s7)
- Improved cluster detection.
- Added audio chips and nfc detection.
- Improved components detection.
- Added Net tab with wi-fi info.
- Fixed crash on some 7.0 devices.
- Bugs fixes.
good app
New version 3.5.0 released.
- Begin support Huawei HiSilicon platfrom. Display detection (need root).
On some devices available all supported cameras.
- Improved components detection.
Fixed display detection on some devices samsung, htc (qcom).
Improved sensor detection for 2 in 1 chips (acc + gyro) .
Improved components detection for samsung devices.
- Added new tab Input devices
On mtk available touchscreen model and fw version (tested on goodix).
- New app icon.
* Who has samsung with 4.2.2 with crash or bug write to me for test. (Navigation View class not found on this devices)
New version 4.0.0 released.
1) Added battery charge / discharge speed.
a) For 5.0+ via Android API
b) For mtk special variant. Tested on mt6752, mt6589.
Discharging speed is current consumption. Ids = Ic
Charging speed is charge current - current consumption. Ics = Icc - Ic
2) New navigation panel.
3) Battery experimental.
mtk
Added battery profile from kernel. According to my data, in most cases it differs on +-5% from real capacity of the factory battery.
qcom
Added battery profile from kernel and battery model. Tested on msm8992.
4) Improved components detection.
5) Spreadtrum
Added detecting lcd id (need enable root in settings)
Exmple: ID066108 it means id 0x066108, found name is s6d77a1a01.
In camera tab added list of supported camera models.
6) Samsung
Exynos
Added detecting lcd id (need enable root in settings)
Exmple: ID_0x404024 it means id 0x066108, found name is S6E3FA0.
Detect camera models for spreadtrum, qcom, marvell pxa, broadcom. (need test)
7) Qualcomm
Added list of supported camera models.
8) List of system apps. Open from apps tab from last item.
List of OpenGL ES extensions.
9) Fix codepages in some lang.
10) Fix bugs and crash on some devices.
11) Device Info HW+ (PRO)
You can create a report with device information.
Saving in html file format. See example:
http://www.deviceinfohw.ru/data/report_example.html
4.2.1
- Huawei on qcom: improved support.
- List of supported cameras with vendor and resolution.
- Samsung on exynos: added gpu freq.
- Qualcomm: added lcd panel without root from sysfs.
- Engineering menu moved to navigation panel + miui cit.
- Updated components detection and fixed errors.
- Updated sensors tab (using Sensor Test 1.4+).
- Build with new sdk.
- Begin spanish and polish localization by Radek Strycharz.
- i2c device list groupped by bus [PRO]
ANDR7E said:
4.2.1
:
:
Click to expand...
Click to collapse
Awesome...
Can you add switch to show free RAM from /proc/meminfo?
hyperion70 said:
Awesome...
Can you add switch to show free RAM from /proc/meminfo?
Click to expand...
Click to collapse
Added it and swap/zram size too.
Maybe total ram will be correct for phones with fake ram size.
ANDR7E said:
Added it and swap/zram size too.
Maybe total ram will be correct for phones with fake ram size.
Click to expand...
Click to collapse
OP, thank you very much for the update 4.5.0.
New version 4.6.3
Version 4.5.0
- New material tab bar.
- Screen Test (lcd color, multi-touch, touch drawing)
- Cpu Monitor (press on clock speed)
- Dark theme support (2 week or PRO)
- Updated components detection.
- Optimizations.
- RAM from kernel (meminfo) + swap
- Some fixes for HiSilicon cpu detection.
Version 4.6.3
- Added partition info for some platforms.
- Added new lcd color tests.
- Added tab with USB devices
- Updated components detection.
- Asus qcom: try detect cameras.
- HiSilicon: added gpu freq.
- HiSilicon: try detect cameras (with root).
- CPU operating time (click to core count item)
- System: device features: list of the features enabled in firmware.
- System: extra sys info (click to system build fingerprint item)
(modem mtk, vm mem size, some vendor info)
- Try fix opengl bug for some devices.
- Try deep detect mt6757 P20 series => P20 / P20 series / P25 / P25 series
P.S.
Who want help translate app to own language, I provide strings resources https://github.com/andr7e/DeviceInfoHW_translations/
Partitions + Project (Nvidia Tegra 4)
ANDR7E said:
New version 4.6.3
Version 4.6.3
- Added partition info for some platforms.
Click to expand...
Click to collapse
I have just downloaded version 4.6.4.
Thank you very much for the partition info on Nvidia Tegra 4 (Toshiba Excite Pro AT10LE-A-). Can you improve it with names (like on MTK) and a switch to enable the traditional view too, please?
The information below will help you doing that. There is a link to two partition screenshots of this tablet in our XDA thread.
[Q] How Root Toshiba Excite Pro AT10LE-A-108
https://forum.xda-developers.com/showpost.php?p=74227484&postcount=39
So, here is partitions info of this tablet (attached file in black)
And their names (attached file in black)
According to Nexus 7 development thread, these are common names on Tegra tablets:
APP -> system
CAC -> cache
LNX -> boot
MDA -> encrypted userdata
MSC -> misc
PER -> per device calibration
SOS -> recovery
UDA -> userdata
USP -> bootloader
We are trying to unlock the bootloader of Toshiba Excite Pro AT10LE-A (Nvidia Tegra 4 device). There is a protection by the sealime.ko security module blocking some partitions. To defeat sealime.ko we need all the information available on partitions.
Another request is the Project information that is missing on Nvidia Tegra 4 devices. It has valuable information on LCM, modem, etc. Can you include it, please?
Thanks and best regards!
YuriRM said:
I have just downloaded version 4.6.4.
Thank you very much for the partition info on Nvidia Tegra 4 (Toshiba Excite Pro AT10LE-A-). Can you improve it with names (like on MTK) and a switch to enable the traditional view too, please?
Click to expand...
Click to collapse
Partition names are also supported. How it works:
1) Get partition block path from /proc/mounts by key system or cache
If finded it printed in log
2) Get mapping list like on your screenshots (some devices need root)
I see on toshiba tegra3 source, tegra4 didn't find.
LCM can't detect, in driver only set settings and init work.
https://github.com/pio-masaki/kerne.../arch/arm/mach-tegra/board-tostab12AL-panel.c
great.
add a option to show some sensor info on notification/notification icon may be useful
Tegra 4 Technical Reference Manual
ANDR7E said:
Partition names are also supported. How it works:
1) Get partition block path from /proc/mounts by key system or cache
If finded it printed in log
2) Get mapping list like on your screenshots (some devices need root)
I see on toshiba tegra3 source, tegra4 didn't find.
LCM can't detect, in driver only set settings and init work.
https://github.com/pio-masaki/kerne.../arch/arm/mach-tegra/board-tostab12AL-panel.c
Click to expand...
Click to collapse
I hope this helps!
Regards
Tegra 4 Technical Reference Manual
https://developer.nvidia.com/embedded/tegra-4-reference
The Tegra 4 Technical Reference Manual ("TRM") is a technical document of over 2,600 pages targeted at those working on open source or other low level software projects that use or target the Tegra 4 processor. The TRM focuses on the logical organization and control of Tegra 4 Series devices. It provides information for those modules that interface to external devices, or those that control fundamental chip operations. The modules detailed in this document provide an overview, any necessary programming guidelines, and a register listing for that module. Internal functional units such as video and graphics hardware acceleration are controlled by NVIDIA provided software and not documented.
NVIDIA provides access to the Tegra 4 Technical Reference Manual to registered developers only. To become a registered developer, please sign up for our Embedded Registered Developer Program.
If you are already a Registered Developer, you can download the TRM from our Download Center.
Table of Contents
Introduction
Address and Interrupt Map
Interrupt Controller
Arbitration Semaphores
Atomics
Clock and Reset Controller
CL-DVFS
Timers
Multi-Purpose I/O Pins and Pin Multiplexing (Pinmuxing)
Power Management Controller
Real-Time Clock
Boot Process
Host Subsystem
GR2D
GR3D
Encoder Pre-Processor (EPP)
Keyboard Controller
CPU
Flow Controller
Memory Controller
AHB
APB
USB Complex
Audio Hub (AHUB)
Display Controller
MIPI-DSI (Display Serial Interface)
Serial Transport Stream DTV Controller
High-Definition Multimedia Interface HDMI CEC MIPI-CSI (Camera Serial Interface) MIPI D-PHY Calibration for CSI and DSI Video Input (VI) SD/MMC Controller MIPI-HSI (High Speed Synchronous Serial Interface) I2C Controller UART and VFIR Controller Serial Peripheral Interface (SPI) Controller
One Wire Battery Controller
PWM Controller
Thermal Sensor and Thermal Throttling Controller
ANDR7E said:
tegra4 didn't find.
Click to expand...
Click to collapse
Tegra 4 device - Tegra Note 7
https://github.com/Shaky156/Tegra-Note-7/blob/master/arch/arm/mach-tegra/board-aruba-panel.c
https://github.com/Tegra4
Tegra 4 Device tree, kernel and vendor binaries for Gigaset QV1030 aka. Quanta FG6Q
https://fg6q-dev.github.io/
https://www.notebookcheck.net/Gigaset-QV1030.114384.0.html
https://www.notebookcheck.net/NVIDIA-Tegra-4-SoC.87052.0.html
Sent from my takee 1 using XDA Labs
YuriRM said:
Tegra 4
Click to expand...
Click to collapse
I wrote about your toshiba device, tegra 4 source is available. LCD model name is not set, only lcd params.

[Discussion] DeX : too good to be true ?

The DeX concept looks great: http://www.samsung.com/global/galaxy/apps/samsung-dex/ (but...)
http://www.gsmarena.com/samsung_galaxy_s8-review-1603p10.php
I already read multiple reviews on DeX and could not find answers to basic interrogations :
-will DeX-use shorten the total number of discharge/charge cycles of the battery, by simultaneous charging/OS powerhouse ?
-is there any wireless connections between s8 and DeX ?
-are they any broken s8' functionalities when plugged ?
-...
(There is no teardown yet.) https://forum.xda-developers.com/album.php?albumid=14179 shows DeX using a Parade
PS176 DisplayPort-> hdmi 2.0b
On software side, I also noticed reviewers warning that Microsoft is a kind of fake on desktop/1080, without additional licenses (Office 365 subscription) : what else ?
The DeX' Virtual Desktop Infrastructure presentation is real appetizing ( even more with the s8 & s8+ 4.4.x kernel/"linux"), hope some owners will discuss and reveal the future-proof "truth" of that puck.
"Hazy specs" :
If you look into s8+ attached defconfig, apparently "regular" vdi config are not set in this (very) NEW 4.4 kernel:
Code:
# CONFIG_USERFAULTFD is not set
# CONFIG_VIRTIO_PCI is not set
# CONFIG_VIRTIO_MMIO is not set
# CONFIG_XEN is not set
# CONFIG_VIRTUALIZATION is not set
Maybe the advertised VDI for "Enterprise Mobility Management" (EMM) will use a different kernel (or the future Note 8 only)?
DeX is a sophisticated cradle/hub only, fully compatible with Knox (fingerprint & iris scan) that relies on Samsung original charger.
For now, DeX is still working after Knox tripped or even twrp/su-"ified".
Following Note7 fiasco and with a non-removable battery , it would be reassuring to know if DeX-use is powered/charged by the puck :
-via the embedded s8' battery while already in (slow) charging (electric "zugzwang"?=> destructive degradation & overheat)
-via an embedded independent s8' circuitry different from the one which is already (cool) charging the battery
I remember you, that (conversely to laptops), with almost all android devices, we are not supposed to use a device when on charge, and to charge before capacity under 50%.
Edit : related critics
http://www.vdcresearch.com/News-events/emob-blog/Samsung-DeX-The-Future-of-Enterprise-Computing.html
https://www.xda-developers.com/sams...m-revolution-but-aimed-at-the-wrong-audience/
[Samsung Galaxy S8+ Accessories > Samsung Dex by @SmilerOnline ]
One thing I think I discovered is that not just any Android app will work, only Dex-compatible ones (which seems like a really good way fro Samsung to screw themselves on the Dex concept right out of the door). I don't want to use Msoft Office - I want to get on Facebook, use a Reddit client and play Hearthstone.
I hope I'm wrong. I bought the phone almost entirely for Dex. I originally intended to get a Remix device when it launched for the desktop-docking experience but figured it'd be smarter to give my money to a bigger company that can really support the concept well. In a worst case scenario maybe I'll have to flash a Remix rom to the device to get the experience that Samsung promised (or hinted at, I guess).
All Android apps will work just not in "dex mode"
My understanding is that all of the apps (on the phone) will work, but ones that don't support "dex" mode will only run in full screen "phone" mode, so you can't tile/resize/etc the windows or anything special.
NicksOnTheWing said:
One thing I think I discovered is that not just any Android app will work, only Dex-compatible ones (which seems like a really good way fro Samsung to screw themselves on the Dex concept right out of the door). I don't want to use Msoft Office - I want to get on Facebook, use a Reddit client and play Hearthstone.
I hope I'm wrong. I bought the phone almost entirely for Dex. I originally intended to get a Remix device when it launched for the desktop-docking experience but figured it'd be smarter to give my money to a bigger company that can really support the concept well. In a worst case scenario maybe I'll have to flash a Remix rom to the device to get the experience that Samsung promised (or hinted at, I guess).
Click to expand...
Click to collapse
Source? From what I understand normal android Apps work they just aren't optimize for resizing like Dex apps.
YellowGTO said:
Source? From what I understand normal android Apps work they just aren't optimize for resizing like Dex apps.
Click to expand...
Click to collapse
From Google's and Samsung's documentation, apps do need to be compiled to support resizable windows in dex (an additional property in the manifest).
However if the app is designed to support Android windowed mode the app should work just with a fixed window size. I've already updated one of the apps I support to be resizable, just waiting for my dex dock to actually see if it works correctly.
Sorry for spreading misinformation - I'm happy to say I was wrong in what I thought earlier! I reached out to a fella on Twitter that had one and he happily showed me:
{
"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"
}
thelestat said:
From Google's and Samsung's documentation, apps do need to be compiled to support resizable windows in dex (an additional property in the manifest).
However if the app is designed to support Android windowed mode the app should work just with a fixed window size. I've already updated one of the apps I support to be resizable, just waiting for my dex dock to actually see if it works correctly.
Click to expand...
Click to collapse
From what I read, SamsungBrowser, Office365 (check attached/'PhoneArena') and Adobe are compatible; Chrome is next app to provide superposable graphics on DeX UI/1080.
Following the end of UbuntuTouch development, and with Microsoft VDI support, via certified corporate collaborators (Citrix Receiver, VMware Horizon Client and Amazon WorkSpaces), it looks like the first winning android move against iPhone' success (since soc64 appearance)...
On geek side, it's unclear if DeX is Knox (un-tripped) dependant: apparently it's just a hollow charging hub that takes advantage of s8[usb3.1DisplayPort +soc64 +4.4kernel] ?
The Knox bonus, in DeX, is largely targeted as the un-hackable final solution for hybrid outdoor/office agents, without the need of shared & unsecured PCs in buildings.
Definitively, there is just zero assertion on gaming (dynamics) or education (durability >2years).
(I will update 1st post when teardown clarify the inside of the cradle.)
[Samsung Galaxy S8+ Accessories > Samsung Dex by @SmilerOnline ]
Could somebody tell me how multiple languages work with Dex?
I have a physical keyboard with English and Russian letters on the keys. Is there a keyboard switching shortcut just like in Windows or is there some other solution?
oF2pks said:
-will DeX-use shorten the total number of discharge/charge cycles of the battery, by simultaneous charging/OS powerhouse ?
Click to expand...
Click to collapse
This is my biggest concern. I play Bleach: Brave souls a lot on my S6, and thus had to charge it quite often, 3-4 times a day leaving it plugged in. After one year I'm lucky to get 1.5 hour SoT and 7 hours standby. I know they said the S8 is supposed to be really good in that department, not losing a lot of it's initial capacity after the first year.
Hi! I'm currently planning to buy S8 mainly because of dex.
If there are anyone who is already used dex, I want to ask whether it is possible to use an usb c extension on dex station to our S8?
I need it because I want to have a good protection on my S8 (planning on buying otterbox defender or love mei), but I also plan to use dex quite intensively.
Also, when using it with a game open, can we still multitask?
I mean like auto-ing a game, when we write on MS word in the same time.
Another question is : Can Dex desktop mode can be ported on the Note 4 and work with the older samsung dock...It has also hdmi output and usb ports so it is similar to Dex stand?
Or Enable Dex mod wirelessly using miracast technology that works generally fine.
I have the dex still unopened as my gear I think I buy way too much stuff I don't use...still haven't found a situation where id say this is where the dex can be useful
Sent from my SM-G950F using Tapatalk
Isn't this sort of thing already possible with DriveDroid and Linux already? Plus, I don't see this anywhere useful as that, and I don't see a use for this. Android is never meant to be the equivalent of a desktop OS in the first place.
Anyone know what I'm not allowed to disable for Dex? Mine is coming this week. I've disabled Touchwiz Launcher as I use nova, that's the only app I can think off if they're in the same app
Anyone else getting can't start Dex error? I've renabled everything and still the same problem
DeX teardown / twrp-su / s8:defconfig
I have updated 1st post with more info : teardown / twrp-su_OK / s8:defconfig attached
Thx to @Sv3nDV (imgur) you can look at teardown :
Sv3nDV said:
From what I gather, there is a realtek 8152 10/100 controller. Next to that is a cy7c656 USB 2.0 hub. A PS176 DP-HDMI converter is by the HDMI port. Near the USB-C port there is a chip I cannot read, I will get a better shot of that. Looks like its by a lot of power converter/regulation stuff. Its odd to me the base of the Dex says it is rated [email protected] amp but the included USB power brick is max 9v.
The other side of the board has 3 Cypress Semi chips. One is a cy 65210 which says USB billboard? Would that be the chip that determines what USB-C features are available during handshake? (again, not an expert at all lol). Then the Ethernet phy chip and some others.
I will open the Dex again when I get home from work and document how to do it, and take better shots on each chip for better ID.
Click to expand...
Click to collapse
DeX is using a Parade PS176 DisplayPort-> hdmi 2.0b
+ https://www.paradetech.com/parades-ps176-displayport-hdmi-2-0-converter-adopted-samsung-dex/
Thx to @zulu99 , for now, DeX ok with twrp/su .
You can follow THE "realtime" DeX guide with app compatibility: @SmilerOnline thread https://forum.xda-developers.com/galaxy-s8+/accessories/samsung-dex-t3593828/page999
Don't forget to vote !
DeX owner question
Has anyone tried attaching a mass storage device to a DeX to see if it will work as a substitute media player?
I have a WD Live and if I can connect my 4tb it might make file transfer easier...
Jca1982 said:
Has anyone tried attaching a mass storage device to a DeX to see if it will work as a substitute media player?
I have a WD Live and if I can connect my 4tb it might make file transfer easier...
Click to expand...
Click to collapse
I had tested a mouse and keyboard Bluetooth in just 1 port, I mean: mouse and keyboard have 1 Bluetooth receiver so in 1 Dec usb port can use keyboard and mouse :silly:
And what about battery? Dex is a battery destructor?
Conito11 said:
I had tested a mouse and keyboard Bluetooth in just 1 port, I mean: mouse and keyboard have 1 Bluetooth receiver so in 1 Dec usb port can use keyboard and mouse :silly:
And what about battery? Dex is a battery destructor?
Click to expand...
Click to collapse
Why use Bluetooth in usb, just start it on phone and connect you bt unit's.. and then you 2 free usb ports..
Skickat från min SM-G950F via Tapatalk

Categories

Resources