Device and Project Presentation
In 2015 the Chinese company EStar launches on the market the Takee 1. An octa-core smartphone with an astonishing Holographic 3D technology developed by the german Seereal.
Despite the cutting-edge hardware, a low price and the big innovations in the field of 3D and AirTouch... the phone does not receive the big success it deserved, Estar closes down and the last official software update dates back to 2015, leaving the whole system stuck to Android 4.2.
But today, 5 years after the last update and the closure of the company, I continue what the far-sighted EStar was doing, studying 3D technologies and releasing a new Android 7 Software Update.
I had to face many difficulties but...
making an Android 7 ROM from just an Android 4.2 base is now possible!
Let's go guys!
Presentation Image
https://imgur.com/Be7YKsg
Other screenshots
https://imgur.com/a/RRyUNL7
Youtube video
The last ROM is v. 3.0
Everything works except the Cameras. 3D partially works.
Changelog (click to show history of working/not working components)
v2.0
Magisk improvements
v1.2
Bluetooth Now Working
Full Holographic 3D and AirTouch support - in Development
v1.1
Usability
WiFi module - Working
Phone module - Working
Audio - Working
Camera - Working (you have to apply a fix)
Fm radio - Working
USB debugging - Working
Bluetooth - Not working but I'm working on a fix!
v1.0
First release that can boot, no need to download it.
Theming
Transition from RidonOS to Mik-el Android:
Removed most of the references to RidonOS and Micromax 311
Mik-el bootscreen (boots faster)
Mik-el wallpaper
Apps
Replaced Ridon launcher with a lighweight Open Source Pixel Launcher
Removed Old Google apps, size of the Rom reduced
Added F-Droid, Open Source alternative to Google play store
Added an Open Source alternative to Youtube
Added 52kb app to exchange files on wifi between smartphone and PC
Added OpenCamera, best android camera app (and it's Open Source)
Added High-quality Audio recorder with noise reduction
System and Performance
Enabled USB Debugging by default
Adjusted dpi value: screen is more readable and system is more reactive!
First step to port the Bit Cauldron 3D Audio Technology included in the Takee stock Rom: Removed loudsound patch to avoid possible future conflicts
Mik-el fixes to extend the life of your device
system warns you when you reach high temperatures
system doesn't write on the phone memory over and over again (The original Takee 1 stock rom is based on Android 4.2 and trimming was introduced starting from Android 4.3 only)
you can install apps directly on external SD card - starting from v. 1.2
Support me:
Telegram Channel here
Instagram here
Youtube here
Paypal here
XDA:DevDB Information
Mik-el Android 7 for EStar Takee 1
Contributors
Mik-el
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4.67
Version Information
Status: Stable with some bugs
Created 2019-11-02
Last Updated 2021-10-16
TWRP by Mik-el - Download and Instructions
To flash an Android 7 Rom You must use an updated TWRP custom recovery!
I made a new TWRP for Takee 1 and I released 2 versions
TWRP 3.1.1. here
TWRP 3.1.1 with OTG support here
Instructions and Screenshots are included in the previous links.
Rom Download
Free Download, Virus Free (just use "slow download")
v 1.1-------------> here
v 1.2-------------> here
v 2.0-------------> here (10th March 2021)
v 2.0.1 Bundle*---> here (9th April 2021)
v 3.0 (3D) and Bundle*--->here (16th October 2021)
* = Bundle includes= ROM + Optional Stuff among: Google Apps, SuperSU root and Magisk!
Google Apps
Google Apps 2021. Most lightweight version possible. We love privacy, so they're optional.
I made a flashable .zip to install them from TWRP recovery but it seems not working for me, you can test it and let me know.
Magisk or Root? What do you want?
I want Magisk = Rom 2.0.1 is pre-patched for Magisk (boot.img). After booting the ROM just install the Magisk Canary apk. (Apk included in the 2.0.1 bundle you have just downloaded).
I want Root =before installing the 2.0.1 ROM, take the "boot_unrooted.img" file inside the 2.0.1 Bundle you just downloaded. rename this file in "boot.img" and replace it inside the .zip file of the ROM. Now you can flash the ROM and then flash SuperSU through recovery
Rom Integrity Infos
Code:
Name: Mik-el_Android_for_Takee_v1.1.zip
Date: 27/12/2020
Size: 602 MB (631,352,946 bytes)
--------
SHA-1: 260999abe54d3ae473272a4002cc9cef2ea93e60
MD5: c2fb20469f11a2f6c16c0479a8c157f6
CRC32: 8436c496
General Advices about Takee 1
Don't use the original charger, probably you have a good one but it gave problems to most of the users
Don't try to flash this rom with SP Flash tool, you can't, follow the instruction I'm providing here
Instructions to flash the ROM:
Backup 3D calibration files or you'll lose the 3D effect forever. Internal and External storage -> "Android" folder -> "HolographyProfile" file and "matrix" file. To know more about 3D calibration, read this! Also, backup your important data, as always;
Boot your Stock Rom and check if you still have these (or other) Air Touch games in your phone storage.
Fruit Ninja (it looks like this)
Sector Strike (it looks like this)
This game (it looks like this)
This other game (it looks like this)
Shadow Snake (it looks like this)
Tunnel Trouble (it looks like this)
If the answer is YES, go to step 3. Otherwise, go to step 4.
Spoiler: YES, I still have Air Touch Games
These Air Touch games can't be downloaded anymore! The Takee 1 3D store is offline! Now you can help the Takee community preserving these games for the future. You just need 1 minute. Download the ApkExtractor app (2.4 MB), save the games on your external SD card and upload them somewhere on the web! Then, you can flash the new Rom.
Download and Install the updated TWRP custom recovery made by me, if you haven't done it yet:
TWRP 3.1.1. here
TWRP 3.1.1 with OTG support here
Download my Rom, it's a .zip file;
Copy the Rom file on your MicroSD;
Once you have installed the recovery you can boot into it;
"Wipe" -> "Swipe to Factory Reset";
"Install" -> select the .zip file for the Rom -> "Swipe to flash"
"Reboot" -> "System"
A tip to Improve Rom Performance
Use the Rom for a few minutes and see how it performs. After that, open the fstrim app included in the Rom and use it to trim the internal storage of you device. This will be the first trim you'll phone has received in 6 years, since 2015 ! It took me 3 trims in a row to fully trim my /data partition. Now see how much more responsive the phone has become!
How to solve Camera Bug for ROM version 1.1
Open the "Reboot Manager" app and do a quick/warm reboot, now your cameras work!
Spoiler: Click here for an Alternative Method
Go to Settings
Go to developer options
Activate "extended reboot menu"
When you want to use the camera:
Long press power button and select "reboot" - you will be asked, which type of reboot you want to do
Select "warm reboot"
Camera is now working!
Definitive solution
Will be solved in the next release.
Help me with testing and support me to get an invincible Rom!
Next updates
Full 3D and Airtouch Support
Camera ready at boot without warm reboot
"Mik-el Rom Updater" to update the system with one touch
Bluetooth Fix
whatever you want!
Support me
Leave a 5 stars review and a positive review using the panel on XDA.
Use these links to support me:
Telegram Channel here
Instagram here
Youtube here
Paypal here
Credits
Mik-el
a big hug to @io2345 for:
helping me with testing and fixes
donating 10 euros for the development
for exchanging almost 150 mails with me to bring this project to life!
@YuriRM
for having collected information and having made a detailed list of Hardware specs from phones similar to the Takee 1
for his continuous effort to bring back interest in this device on XDA and Telegram
@kano3d
for donating 4 euros for generic 3D development
other members of the Takee 1 community (@giotogo, @Talwarmirza, @snapss , @Hunter_07)
an unknown artist for the Mik-el Android wallpaper
Reserved for future Updates.
P.S. Ignore the very next posts below: intially the community and I were talking about other things (problems faced during development), and NOW that the Rom is ready I updated this same thread, to don't make a new one. Now, Enjoy
ROM for Holographic 3D smartphone
Thanks! This ROM will bring a fresh air and new lease of life to EStar TAKEE 1, the first ever Holographic 3D smartphone launched in 2015 at an affordable price ($100-150). Nobody will need to buy an extremely expensive RED Hydrogen One at $1200.
The 3D community will rejoice!
The amazing resources of PHEREO are available to all lovers of 3D Stereo Images and Photos.
http://phereo.com/
Select an image and click Wiggle... if you do not have a smartphone with 3D display.
My advice is to install the PhereoRoll3D app too!
https://github.com/JackDesBwa/PhereoRoll3D
NewPipe - to download 3D videos from YouTube
https://github.com/TeamNewPipe/NewPipe/
INVIDIOUS - to download 3D videos from YouTube, VEVO, etc.
https://www.invidio.us/
Plenty of resources for 3D lovers that justify buying a device with 3D display.
interesting. this phone is still good.....
Anyone with ViperOS development experience?
io2345 said:
Anyone with ViperOS development experience?
Click to expand...
Click to collapse
More than ViperOS developers we need someone that has experience with rom porting.
I made more than 7 releases for this ROM and @io2345 tested them all!
We solved the failed installation problem, now we just need to solve the bootloop.
The porting process is OK, the updater-script file is OK, file permissions are OK...
I don't know where the problem could be!
Next time I'll use another porting guide. (there are only 2 guides and one didn't work since now)
Instead of ViperOS I'll also use a LineageOS rom as port rom.
Let's see what I can get.
(Stay tuned subscribing to this thread and collaborating with us, cheers)
Greek & Indian ROM ports by Jpower7 (A310 kernel) and blacklisted.rock (A311 kernel)
My suggestion is to try other 3.4.67 ports for EStar Takee 1.
ROM ports by Jpower73 (A310 kernel) - Greece
He maintains working links for his ROMs. Therefore, you can also ask his help.
(Android Ice Cold Project) for Coolpad F1/MmxA310-Α311/Himax Polymer Octa by Jpower73
https://forum.xda-developers.com/a310/development/android-ice-cold-project-coolpad-f1-t3802656
HTC SENSE 10 for Coolpad F1-A310-Himax Polymer Octa by Jpower73
https://forum.xda-developers.com/a310/development/htc-sense-10-coolpad-f1-a310-canvas-t3952369
Poly Os for Coolpad F1/Micromax Canvas Nitro A310/Himax Polymer Octa by Jpower73
https://forum.xda-developers.com/a310/development/poly-os-coolpad-f1-micromax-canvas-t3801223
ROM ports by blacklisted.rock (A311 kernel) - India
The developer does not use his device anymore. His phone is over 5 years old and the battery is malfunctioning.
[BUGLESS][7.1.2]Ridon OS for A310/A311/Coolpad F1/Himax Polymer by blacklisted.rock
https://forum.xda-developers.com/a310/development/bugless-ridon-os-a310-a311-coolpad-f1-t3779279
[ROM][FINAL]Resurrection Remix OS 5.8.5 V4.0 for A311/A310/Coolpad F1/Himax Polymer by blacklisted.rock
https://forum.xda-developers.com/a310/development/rom-resurrection-remix-os-5-8-5-v4-0-t3786640
But you can look for other ROMs here
https://forum.xda-developers.com/a310/development
List of TAKEE 1 clones for parts by YuriRM
https://forum.xda-developers.com/showpost.php?p=74386084&postcount=1199
EStar Takee 1 - list of components
http://deviceinfohw.ru/devices/inde...=cpu0&brand=brand0&filter=takee&submit=Search
HIMAX POLYMER - 10 shared components with EStar Takee 1
Back CAMERA and Front CAMERA (sunny_imx135_mipi_raw and ov5648_mipi_raw), LENS, ALSPS, one part in two of CHARGER (fan5405), PMIC, WIFI and two parts in four of OTHERS (kd_camera_hw and dummy_eeprom) and RAM.
http://deviceinfohw.ru/devices/item.php?item=1083
Micromax A311 \ A315 \ A316 - just 1 shared component with EStar Takee 1
Back CAMERA
http://deviceinfohw.ru/devices/item.php?item=4999 (A315)
http://deviceinfohw.ru/devices/item.php?item=3526 (A316)
There is no data for Micromax A311 and A310
http://deviceinfohw.ru/devices/inde...m0&brand=brand0&filter=Micromax&submit=Search
I have requested to upload the list of components of Micromax A311 and A310 to the Device Info HW database
Android 4.4.2 KitKat kernel - BQ Aquaris E5 FHD
Official source code for BQ Aquaris E5 FHD
https://github.com/bq/aquaris-E5FHD
Have you acquired knowledge enough for including specific drivers of EStar Takee 1 into this Android 4.4.2 KitKat kernel of BQ Aquaris E5 FHD?
You will get a much better kernel (3.4.67) than luckasfb.
Instructions
Building custom kernels for Android devices
https://source.android.com/setup/build/building-kernels
SavageMessiahZine - Russian forum of Android kernels and assembly instructions
Development of kernels and firmware for devices on the MTK platform � | Self-compiled kernel from source � | Instructions for building ANDROID from sources. � | Theme on assembling the source code MTK on china-iphone | Build TWRP for Qualcomm platform �
https://www.savagemessiahzine.com/forum/index.php?showtopic=583114
Guidance from LordArcadius (GitHub and Telegram) and nathanchance (XDA)
Compiling Android Kernel for your own device #67
https://github.com/ILUGD/talks/issues/67
XDA Reference guide:- https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
Help and support Telegram group:- http://t.me/LinuxKernelChat
Upstreaming guide:- https://forum.xda-developers.com/an...rence-how-to-upstream-android-kernel-t3626913
Toolchain:-
GCC 4.9 for 64 bit:- https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/
GCC 4.9 for 32 bit:- https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/
My Telegram username:- @LordArcadius
GPIO pin numbers in the Circuit Board of EStar Takee 1
I hope there is a solution for camera bugs introduced by luckasfb in his latest kernel of EStar Takee 1.
Some KitKat kernels share both cameras (Sony imx135_mipi_raw and OmniVision ov5645_mipi_yuv) with EStar Takee 1.
However, it may be down to GPIO pin numbers in the Circuit Board. That is why I want to know the Circuit Board ID number, the physical address number of each component and GPIO pin numbers of camera sensors of those devices.
That info is included in the kernel source code of BQ Aquaris E5 FHD.
@giotogo can you find this information inside your EStar Takee 1 device, please?
Circuit Board ID number
GPIO pin numbers of camera sensors in the Circuit Board
Take detailed photos of internal components
Take detailed photos of internal numbers printed in the motherboard.
This information may help find other devices that share an identical Circuit Board ID number. This list of most compatible devices is useful. Hopefully, It will enable to choose the easiest Android 7.1.2 Nougat ROM to port into EStar Takee 1.
It also provides crucial information for changing the GPIO pin numbers of both cameras in the KitKat kernel source code of EStar Takee 1.
Bug in power for cameras GPIO pins in codegen - EStar Takee 1
https://forum.xda-developers.com/showpost.php?p=79024675&postcount=1361
The video below shows how to open a device and find the Circuit Board ID number.
However, my guess is that it boils down to the physical address number of each component and GPIO pin numbers in the motherboard. This enables to direct each camera driver (front and back cameras) to a specific address in the Circuit Board (GPIO pin number). This is the info that luckasfb tried so hard to find, trying by hand hundreds of combinations for GPIO pins. He did not open the case of his EStar Takee 1 device.
How to Find and download Firmware file for chinese tablets
https://www.youtube.com/watch?v=XZqLoxpbUSA
How to fix a bootloop after installing a Custom ROM like Viper OS
io2345 said:
Anyone with ViperOS development experience?
Click to expand...
Click to collapse
@io2345 how are you doing? It has been a long time since we last talked.
I may have found a solution for the bootloop of the Viper ROM ported by @Mik-el.
Can you test this method, please?
Have you watched this video by the clever german guy, Christoph Zahradnik ?
His Viper ROM is used in this explanation... Viper SC2_5.2.1.zip ?
How to fix a bootloop after installing a Custom ROM like Viper OS (07/03/2015)
By Christoph Zahradnik
https://www.youtube.com/watch?v=cgYXy2XC1SM
Below find what happened on the previous day.
HTC Sensation (Snapdragon S3) and Viper ROM - installing a Custom ROM and entering a bootloop (06/03/2015)
By Christoph Zahradnik
https://www.youtube.com/watch?v=-Snab4bsnzQ
YuriRM said:
I hope there is a solution for camera bugs introduced by luckasfb in his latest kernel of EStar Takee 1.
Some KitKat kernels share both cameras (Sony imx135_mipi_raw and OmniVision ov5645_mipi_yuv) with EStar Takee 1.
However, it may be down to GPIO pin numbers in the Circuit Board. That is why I want to know the Circuit Board ID number, the physical address number of each component and GPIO pin numbers of camera sensors of those devices.
That info is included in the kernel source code of BQ Aquaris E5 FHD.
@giotogo can you find this information inside your EStar Takee 1 device, please?
Circuit Board ID number
GPIO pin numbers of camera sensors in the Circuit Board
Take detailed photos of internal components
Take detailed photos of internal numbers printed in the motherboard.
This information may help find other devices that share an identical Circuit Board ID number. This list of most compatible devices is useful. Hopefully, It will enable to choose the easiest Android 7.1.2 Nougat ROM to port into EStar Takee 1.
It also provides crucial information for changing the GPIO pin numbers of both cameras in the KitKat kernel source code of EStar Takee 1.
Bug in power for cameras GPIO pins in codegen - EStar Takee 1
https://forum.xda-developers.com/showpost.php?p=79024675&postcount=1361
The video below shows how to open a device and find the Circuit Board ID number.
However, my guess is that it boils down to the physical address number of each component and GPIO pin numbers in the motherboard. This enables to direct each camera driver (front and back cameras) to a specific address in the Circuit Board (GPIO pin number). This is the info that luckasfb tried so hard to find, trying by hand hundreds of combinations for GPIO pins. He did not open the case of his EStar Takee 1 device.
How to Find and download Firmware file for chinese tablets
https://www.youtube.com/watch?v=XZqLoxpbUSA
Click to expand...
Click to collapse
Here is photos. i hope, you find what you want
https://ibb.co/3Nc72LG
https://ibb.co/NZpGbPm
https://ibb.co/Sf2bnL6
https://ibb.co/ygg1jWq
https://ibb.co/0sRmXKy
https://ibb.co/vqRcg8P
YuriRM said:
@io2345 how are you doing? It has been a long time since we last talked.
I may have found a solution for the bootloop of the Viper ROM ported by @Mik-el.
Can you test this method, please?
Yurim, I'll try my best to get it done the next weeks. Currently time is a rare factor...
As far as I know, the device of Mik-el is working now (more or less). So it might be a good idea to let him try this method himself.
Click to expand...
Click to collapse
Found the time today and tried the method via fastboot. Sadly to say, it doesn't change anything. Phone keeps bootlooping.
@io2345 @giotogo
I'm chatting with @blacklisted.rock on telegram. He said he'll send me a better porting guide.
Me and @YuriRM have already chosen a new and better rom to use as port rom.
The failed installation/ updater-binary errors were already solved in my last viperOS port.
Hopefully this time we'll get a booting Android 7 rom.
Regards
@io2345 @giotogo
I'm chatting with @blacklisted.rock on telegram. He said he'll send me a better porting guide.
Me and @YuriRM have already chosen a new and better rom to use as port rom.
The failed installation/ updater-binary errors were already solved in my last viperOS port.
Hopefully this time we'll get a booting Android 7 rom.
Regards
{Mod edit: Quoted post has been deleted}
why you need this damned phone?
Hi everyone, I am also the owner of takee1.
I haven't used it for a long time, but when I saw that someone was doing something to bring it back to life, it gave me hope.
I would be interested in updating it with a more current rom, since 4.2 is no longer compatible with anything!
I hope it will be possible soon.
These Chinese continually churn out new models, but never firmware updates!....shamefull!
June 2020 Updates: Rom ported! Now we need a recovery!
June 2020 Updates: Rom ported! Now we need a recovery!
Guys, I've really faced a lot of problems when trying to port this rom:
1) I had to wait 5 months to receive a working battery from China, thank you Corona Virus...
2) university... XD
3) porting guides on the web suck, I had to contact many people and study many articles and video guides... until I had to make my own porting guide...
4) some tools to extract boot.img files extract .img files, but with a wrong structure!! (and I discovered this just recently!)
5) I had to change the port rom, now I'm not using a ViperOS rom, but a RidonOS rom from a Micromax device much more similar to Takee 1 (more than 90%of the hardware is identical)
6) I want to thank you @io2345 for helping me to test over 10 roms!! We had to exchange almost 100 mails to bring you a new and updated Rom!!
Anyway after all this FREE effort I think that I finally got a working Rom !! (correctly ported!!)
But we dhave another problem now...
We discovered that the custom recovery we use on Takee 1 (twrp 2.8.0.0. developed by @luckasfb ) is too old to support Android 7! We need a new custom recovery, probably a twrp 3.0 or above.
I've already researched new material and guides on the web. I found a guide that seems to clearly explain how to port a custom recovery to any device.
The process is simple, it consist in the extraction of the recovery from an Android kitchen in Linux, the rest is about replacing files.
Is this the end, or not?
Anyway the process is long and boring...
I'm quite busy with exams, life a few other projects...
I don't know if continuing this project is convenient for me at this point...
If someone wants to help me and @io2345 please leave a message hereunder, I'll leave you links and infos about the recovery porting.
Cheers!
A reward of 20 euro is awaiting your delivery of a fully working Android 7 ROM + custom recovery.
I expect @io2345 to reward you as well:
Regarding TWRP-3.1 custom recoveries for EStar Takee 1, I did some porting attemps from 5-19 November 2017.
https://forum.xda-developers.com/showpost.php?p=74410087&postcount=1201
https://forum.xda-developers.com/showpost.php?p=74434705&postcount=1202
https://forum.xda-developers.com/showpost.php?p=74482513&postcount=1203
https://forum.xda-developers.com/showpost.php?p=74488944&postcount=1205
https://forum.xda-developers.com/showpost.php?p=74540282&postcount=1206
https://forum.xda-developers.com/showpost.php?p=74564282&postcount=1207
TWRP for BQ Aquaris E5FHD
https://twrp.me/bq/bqaquarise5fhd.html
Current version
twrp-3.4.0-0-vegetafhd.img
Related
{
"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"
}
DEPRECATED, NO MORE UP-TO-DATE, ONLY KEPT FOR ARCHIVE
Technical Specifications -
Model Number(s) -
XT1031: Boost Mobile8GB
XT1032: This Model Number is shared by International GSM Version and the Google Play Edition 8 GB/16 GB (Single SIM) EU & International GSM - 8GB/16GB. (Does not Support 1700 MHz AWS)
XT1033 : Brazil, India, Malaysia (BrightStar) - 8GB & 16GB(Brazil Colors Edition) (Both are Dual Sim) and also for Moto G (Music edition) (Dual Sim) (16GB Only), Malaysia 8GB & 16 GB are Dual Sim
XT1034: AT&T and T-Mobile - 8GB/16GB.
Frequencies / Bands:
AT&T and T-Mobile - HSDPA 850, 900, 1900, 2100 MHz; GSM 850, 900, 1800, 1900 MHz
Verizon and Sprint - CDMA:800, 1900 MHz, CDMA2000 1xEV-DO
Display Resolution: 720 x 1280 pixels Corning Gorilla Glass 3 (IPS LCD capacitive)
Screen Size: 4.5" 16 M Colors (329 PPi)
Bluetooth Enabled: Yes
Wi-Fi Enabled: Yes
Internal Memory: 8 GB (Actual Space for user data ~6 GB)
16 GB (Actual Space for user data ~12 GB)
External Memory: None
Size / Dimensions: 5.11 x 2.59 x 0.46 inches (129.9 x 65.9 x 11.6 mm)
Weight: 5.04 oz (143 g)
Battery Capacity: 2070 mAh (Not User Replaceable)
Camera: 5 MP (2592х1944 pixels) Camcorder: 720p (30fps), stereo sound rec., HDR Front-facing camera: 1.3 megapixels
Operating System: Android 4.4, 4.3
Keyboard: Touch Screen
GPS: Yes
Click to expand...
Click to collapse
Unique Features -
Motorola Assist
50 GB Google Drive Space Free
Dual Sim
FM Receiver
Click to expand...
Click to collapse
Moto G Review -
Moto G Review - Here's great thread with collated Reviews of this device. Thanks to @matmutant
Click to expand...
Click to collapse
List of Commonly used Terms -
All that is fine, but I don't know what this rooting, flashing, nandroid, Modding etc. mean? Yelp ?
Fear Not! Here's a little Cheat Sheet for you. Please thank @benjamingwynn for this. I took his original list for HTC and extended it for here. Given bellow is a Glossary of sorts for commonly used terms. Please let me know if I missed any and I will add it. Also please visit this Q & A thread. Its more than likely to answer most of your questions.
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AFAIK - "As far as I know"
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free (see open-source)
APK - "Android Package" an Android application
Binary - (sometimes called bin's) a group of executable files.
Brick - When the device refuses to boot at all, despite having a full battery is termed as Bricking. Most of the times, the devices gives some indication of problems such as blinking Red Led, but no other signs of life. It is also called Hard Brick. Also see Soft Brick.
Bootloader - Its a small piece of code that's embedded in the device. Its the first to be executed when the device is turned on.
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
CM - See CyanogenMod
CM10 - Cyanogenmod 10. A modified version of Jelly Bean release of Android 4.2.x as well as 4.3.x (see CynogenMod)
CM11 - Cyanogenmod 11. A modified version of Kitkat release of Android 4.4.x. (see CynogenMod)
Custom recovery - An unofficial recovery developed by other developers for your device. Its typically used to install unoffical ROMs. See CWM and TWRP.
CWM - ClockWorkMod, a project that makes Custom Recovery.
Cyanogenmod - A free open-source project based on the AOSP. It is a modded (see modded) version of the Android firmware
Dev - See developer.
Developer - A man or woman who has created (developed) software.
Deodexed - Where the two part ODEX files (see Odex) are moved into the actual APK (apk), thus making it one.
Execute - To "run" or "start" a binary
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM. (See ROM)
Flash - The process of installing a software on your device.
Flashing - See Flash.
FOTA - "Firmware over the air" this normally refers to ROM's but can refer to radio firmware (see OTA)
Froyo - Android 2.2
GB - Could mean one of two things. 1. Gingerbread or 2. Great Britain
Gingerbread - Android 2.3
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop bellow the (just as easily configurable) minimum frequency.
Honeycomb - Android 3.x. it was never released or ported to the wildfire s because it was built for tablets.
Ice cream sandwich/ICS - Android 4.0. The latest version of Android.
JDK - "Java Development Kit" an SDK for the java platform. It is needed to run the Android SDK.
JRE - "Java Runtime Environment" a collection of binarys and files to allow java software to execute.
KANG - The process of creating a code based of someone else's code.
Kernel - This is another term brought over from Linux World. A Kernel is a piece of software, that takes over from the Bootloader and then completes the booting of the device. It handles the CPU and other vital components. A modded kernel may be used for overclocking.
Library's/Libs - a set of instructions for applications to use to function. A functioning camera lib would allow the camera to be used.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
Modding - To perform a mod
Modded - to have included mods or condition after applying a mod.
Modification - see mod
Open-Source - (not to be confused with free) A piece of software that is free to edit, use, distribute and share with no charge.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
Radio Firmware - (see firmware) a type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Overclock - (not to be confused with underclock) to exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Nandroid - Its a process of taking a backup of most of the partitions in Android. This is usually performed in Recovery Console when OS is not running.
Partition - Similar to Linux, Android storage is divided into Partitions. These are akin to compartments that house specific part of the OS boot and operation.
RAM - Could be one of three meanings: 1. Memory for the CPU to process processes. 2. Random Access Memory, a place where information can be used, executed from, modified, or deleted. 3. A type of sheep.
Recovery - Its a dedicated Android partition, that has Recovery console installed. This is invisible during normal operation of the android device.
ROM - 1. A modified version of the Android operating system operating system. 2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
RUU - "ROM Update Utility" An automatic installer for Radio Firmware, ROM and HBOOT. (Predominantly used on HTC).
SD - Short term for MicroSD
SDK - "Software Development Kit" a set of tools used for software development.
Soft Brick - When the device refuses to boot despite a full battery, but shows some other signs of life, its considered as soft Bricked. Also see Brick
Stock - An unchanged version of something. Example: I just flashed stock Rom. Typically this term may be used to refer to Official firmware. But this is not the case always.
TWRP - Team Win Recovery Project. This also has a newer edition called TWRP 2.
Underclock - to change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WFS - "Wildfire S" an armv6 device made by HTC in 2011.
WIP - "Work In Progress"
Zipalligned - This is something that makes a ROM faster. Best see this link for more.
Click to expand...
Click to collapse
Ok Now that you have a hang of your device, you probably want to explore your options and maybe install a Custom Rom. Well, the first thing you will need is to Root the Device.
So what really is a Root ? Why should I do it ? Would it break my Phone ? How about my Warranty ? All legitimate questions. To start off, here's an easy guide by Lifehacker. This whole concept may seem mystical to some of us. Let me try to make it pretty straightforward. Rooting is a process on Android that effectively grants you superuser access. Think of it as Administrator access on Windows. Android is a derivative of Linux. So those from Linux should have no difficulty with this concept.
There are certain operations that only a Superuser can do. Hence you'd want to root in order to so. For ex, remove any application that is installed as System application. Just like on on Windows, Root access does come with risk, so you need to use it with care. Just because you have Root access, does not mean your phone is broken. Typically making wrong changes to system with Root access, will result in affecting smooth operation of your phone. In extreme cases, the device may be Bricked if incorrect software (Rom, Mod or others) is flashed.
When it comes to Warranty, typically Root as such does not void your warranty. But if you end up flashing anything with a custom Recovery, then your Warranty may be voided.
Rooting -
Ok so, I got what Root is and I need to be responsible in what I do. How do I get the root ? Well the first and basic thing would be to install appropriate drivers for Windows.
Next in order to Root, please follow this thread by @paulobrien . As you will see, there are two ways to go about it. Both do require your Bootloader to be unlocked. However, neither method, applies to the Google Play Edition (XT1032) as there is no supporting Custom Recovery for this variant.
If you do not have or do not wish to unlock your bootloader then you can opt for @oasoas014 's method of bootloader downgrade. You may also visit @Cooptx's more detailed guide. Note, with the most recent recoveries, you do not need to downgrade your bootloader.
Note - Flashing a bootloader is inherently dangerous. You can possibly hardbrick your device if you flash incorrect bootloader. Always check the MD5 value of downloaded file.
Only In Case of Moto G Google Play Edition (XT1032), it is possible to unlock the Bootloader on your own. You do not need to pay to get an Unlock Code from Motorola. Instead, you can follow the same method as Nexus or other Google Play Devices. Here's a nice tutorial. For those technically minded, here's Android Source Documentation of the same process. Once unlocked, the bootloader cannot be re-locked unless you flash a signed system image, (which Motorola has not made available as of 01-22-2014).
One of the first things you should do upon Rooting is to backup your PDS Partition.
[SIZE=+1]How to backup / restore PDS partition and why?[/SIZE]On Motorola devices the 'pds' partition contains information specific to your machine: IMEI, MAC address, serial number, etc. This partition can be lost by accidental format or over time due to filesystem corruption. If you have made a backup, there is a good chance you can bring your handset back to life.
==> PDS backup will help to restore lost IMEI. It is a situation when the phone reports that the IMEI is unknown. ; This works like a vaccine, apply before having issue with IMEI, after it will be too late !
Instructions:
**Root Required**
Using ADB you can make a copy of the partition and move it to a safe place (Google Drive?):adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/pds of=/sdcard/pds.imgTo restore in the event of corruption or loss:adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds(assuming you've pushed pds.img to internal SDcard storage first)
Click to expand...
Click to collapse
Once rooted, some of you may wish to stick with that and not proceed any further. With root, you will want to remove some of the apps that you don't need. I wish to suggest that you take a complete backup with a tool such as Titanium Backup. That way if you accidentally uninstall/remove something that's critical to android's operation, then you can restore it. For those of you, who wish to install custom Rom, read on.
The first step towards installing a custom Rom is to install a custom Recovery.
Please note, In order to flash any custom Recoveries, you need to have unlocked Bootloader. The viable options are either follow this guide or get an unlock code from Motorola.
Custom Recoveries -
A Custom Recovery is a unofficial Recovery Console that can be flashed to your device's Recovery Partition.
Typically unofficial recoveries offer several advantages over Stock or Official Recovery. Hence the unofficial recoveries are necessary in order to flash a Custom Rom. Apart from flashing a Rom, Kernel or any other firmware, unofficial Recoveries can also take Nandroids.
An unofficial Recovery is also commonly referred to as Custom Recovery. There are two major projects that contribute Custom recoveries. One is called CWM. The other is called TWRP. Given bellow is a list of Custom Recoveries available for your device.
Note - CWM and TWRP recoveries do not support the Google Play Edition variant (XT1032). You will need to wait for Motorola to release the Kernel source code before @a1Pha can support. However Philz Touch does support Google Play Edition.
CWM Recovery v 6.0.4.5 by @a1Pha -
This is the ClockWorkMod Recovery for the Moto G. Head over to the thread for more details.
(Thread as of 12-15-2013)
CWM 6.0.4.7 Swipe Recovery from CM11 thread
CWM 6.0.4.7 Swipe Recovery
TWRP Recovery v2.6.3.0 by @a1Pha -
This is TWRP 2 project brought over to Moto G by @a1Pha. Keeping with TWRP 2, its a Touch Recovery. Head over to the thread for more details.
(Thread updated as of 12-09-13)
Philz's Touch Recovery v2.6.3.0 by @Phil3759 -
This is CWM Advanced Edition Recovery for the Moto G. Head over to the Thread for more details. Other members have reported that this is compatible with the Google Play Edition of this phone.
ROMs for Moto G
ROMs -
Given bellow is a list of known Roms for Moto G. Most of the Custom Roms for Moto G require Unlocked Bootloader in order to flash via custom Recovery. Only in the case of Stock firmware or Stock based firmware, it will be possible to flash without unlocked bootloader.
If I miss on a Great Rom, let me know.
AOSP ROMs - [KITKAT 4.4.x]
Android Open Source Project, commonly known as AOSP is a repository of Official Google Codebase for Android. Any Rom built from this code will provide a true Android Experience.
CM 11 (Unofficial) - by @Dhacker29
Unofficial release of CynogenMod 11 (4.4.2) for the Moto G. It is released only for GSM variants only. International GSM and US domestic (AT&T and T-Mobile) are supported. Please head over to the thread for details.
Nexus G - by @xmattjus
This Rom offers a pure vanilla Nexus experience on your Moto G. As of 13-01014, Modem does not work for dual sim models. Please see the thread for details.
SlimKat Unofficial - by @SpaceKiller
Following on the Traditions of Slim Rom, this unofficial port provides the same experience on Motorola G. As of 01-18-14, the rom supports only GSM Variants for EU, International and US. Please see the thread for more details.
Paranoid Android Unofficial - by @Vocoderism
Unofficial Port of the Paranoid Android Rom for Moto G. This rom is intended only for EU and international GSM variants. Please see the thread for more details.
Beanstalk Unofficial - by @Cameron581
This Rom is based on the CM codebase as well as Slim Code. It has a lot of nice features. Please see the thread for more details.
AOSP ROMs - [JB 4.3]
None Listed as of 12-31-2013.
Stock based ROMs - [Kitkat 4.4]
Stock Firmware - [KITKAT 4.4.2] by @antiquezip
The OTA Update to Kitkat 4.4.2 is posted for the U. S. GSM version of this device. It is dubbed as U.S. GSM (UMTS Version with AWS)
Please see this thread for more details.
This note, it is possible to apply this update to other Non-US GSM Devices successfully. Please look for a Guide in Post 4.
Kitkat+ Rom - [Kitkat 4.4.2] by @anerik
This is a stock based Kitkat rom. It enhances the stock Kitkat firmware and hence the name. Please head over to the thread for details.
OTA Firmware (All variants) - [Kitkat 4.4.2] by @josalaito
The original 4.4.2 release for GSM version has been re-packed for all variants of this device. It now applies to US as well as international versions of the Moto G. Head over to the thread for details.
(Rom Thread as of 12-23-2013.)
Stock based ROMs - [JB 4.3]
List of Stock Firmwares by @Skrilax_CZ -
All the Stock unrooted firmwares are available over here. The process to flash this, has been linked in the Post 3.
INFUSION B2 Rom by @tillaz -
This is a modified stock based Rom. Please head over to the thread for more details. Or you could also visit Modaco Thread for Screenshots and more details.
(Rom Thread as of 12-23-2013)
KERNELS -
Given bellow is a list of kernels for Moto G. Please let me know if there's one I have missed.
AOSP Kernels -
Hybrid Kernel by @faux123 - [for JB 4.2]
Although based on Linux 3.4, this kernel incorporates some of the advanced features of Linux 3.8+. Head over to the thread for more details.
[ANYKERNEL] pink Kernel by @pinkflozd
This kernel offers a host of features. It does support ExFAT and NTFS. It is based on Linux 3.4.x. It is not Compatible with Stock Rom. Head over to the thread for more details.
Furnace Kernel by @Savoca
This Kernel offers a host of features and includes good collection of Governers and Schedulers. It is based on Linux 3.4.x. It is not Compatible with Stock Rom. Head over to the thread for more details.
Baseband/Modems -
We have a list of possible Modems / Basebands for the Moto G. Please see the thread by @lost101 for details. The thread is Work in progress as of 04-16-2014.
Guides, Tutorials, How To -
Streamlined Rooting International Variants - [Kitkat 4.4.2] by @nupi
This thread has a nice Guide for Non-US versions the Moto G. by This only applies to those who have updated to Kitkat. See the thread for details.
How to Flash OTA Update to Non-US GSM Devices - by @darkeingel
For the Stock OTA updates that are being rolled out, here is a nice Guide by @darkeingel.
GUIDE : APK Parsing Errors -
When uninstalling an app, you got an error message "APK not found" or something to that effect, you may want to follow this Guide.
Mods and Apps -
Calendar Mod - by @Shaftenberg
This mod lets you see Text view in the Calendar when looking at Month as a whole. Head over to the thread for more details.
Status Bar Mod - Remove Carrier Label - by @Shaftenberg
This mod helps you to remove the Carrier's name from the phone's status bar. See the thread for details.
Volume Button Mod - by @Shaftenberg
This mod allows you to long press volume button to skip to the next Track or to the previous track. See the thread for details.
[Xposed] Framework Mods for Moto G -
Xposed Framework is a new framework introduced to the AOSP world. It helps access and modify system settings on the fly that would have otherwise taken a lot of steps.
MotoGuide collection of Tweaks -
@Kameo has created MotoGuide, a collection of assorted appearance tweaks to modify Status bar and other changes. Please see the thread for more details.
Wakeup on Volume Up -
@dubidu has written a module to the framework that allows you to wake the phone by pressing the Volume Up button. See the thread for details. You do need the Framework installed as basic requirement. You may wish to also visit a list of all Xposed modules written. Note, not all of them will work with Moto G.
Modified Phone Apk displaying Caller photo - by @shaftenberg
This mod shows the full picture of the caller from your contacts instead of being cut off at top. See the thread for the screeshot and details.
Customizations - Themes, Bootanimations, Media -
Boot Animation - by@Cooptx
There's a great bootanimation created from one of the Moto G animation video files. Please see the thread for details.
Font Pack for Motorola G- by @gianton
We have universal Font Packs that are compatible with Moto G. These can be flashed from Custom Recovery. Please see the thread for details.
Specific to International Variants -
Thanks for this!
Enviado de meu XT1033 usando Tapatalk
leonardoroza said:
Thanks for this!
Click to expand...
Click to collapse
I am still building this. Presently working on my Moto X thread.
Update this with a new faux Kernel
This summary is very helpful thank you.
Sent from my XT1034 using XDA Premium 4 mobile app
root problem
Hello!
I have a Moto G with android 4.3, and I want to root, but I can't.
Can you help me please?
I installed the moto driver, the java jdk, and I not find the android jdk.
What I find 480 Mb and there is no install file. /on windows 7 X84/ :silly: :crying:
It would be great if you could add a link to the stock ROM images
robagp said:
Hello!
I have a Moto G with android 4.3, and I want to root, but I can't.
Can you help me please?
I installed the moto driver, the java jdk, and I not find the android jdk.
What I find 480 Mb and there is no install file. /on windows 7 X84/ :silly: :crying:
Click to expand...
Click to collapse
Please follow this thread.
Cooptx said:
It would be great if you could add a link to the stock ROM images
Click to expand...
Click to collapse
I intend to. I am working on building up. Its a work in progress.
Hello!
I have a new problem /the jdk is ok now/
I want to open the bootloader, and they write me the email is sent, but nothing. I not get email, not in spam too.
I used my gmail email, when I login the motorola site.
I made again, but same, no email.
robagp said:
Hello!
I have a new problem /the jdk is ok now/
I want to open the bootloader, and they write me the email is sent, but nothing. I not get email, not in spam too.
I used my gmail email, when I login the motorola site.
I made again, but same, no email.
Click to expand...
Click to collapse
It may take a day or so. Please wait 24 to 48 hours.
Hello!
I have again a problem.
I unlocked the bootloader, when it start shows the screen.
I want to root but nothing.
I downloaded the Superboot, and I do this:
OSs-MacBook-Pro:r2sr maverick$ chmod +x superboot-mac.sh
OSs-MacBook-Pro:r2sr maverick$ sudo ./superboot-mac.sh
Password:
downloading 'boot.img'...
OKAY [ 0.356s]
booting...
OKAY [ 0.251s]
finished. total time: 0.607s
OSs-MacBook-Pro:r2sr maverick$
But when restart nothing. I downloaded googleplay store the superSU , but it shows:
There is no SU binary installed, and SuperSU cannot install it.
:crying:
I do it with windows but not rooted too...
robagp said:
Hello!
I have again a problem.
I unlocked the bootloader, when it start shows the screen.
I want to root but nothing.
I downloaded the Superboot, and I do this:
OSs-MacBook-Pro:r2sr maverick$ chmod +x superboot-mac.sh
OSs-MacBook-Pro:r2sr maverick$ sudo ./superboot-mac.sh
Password:
downloading 'boot.img'...
OKAY [ 0.356s]
booting...
OKAY [ 0.251s]
finished. total time: 0.607s
OSs-MacBook-Pro:r2sr maverick$
But when restart nothing. I downloaded googleplay store the superSU , but it shows:
There is no SU binary installed, and SuperSU cannot install it.
:crying:
I do it with windows but not rooted too...
Click to expand...
Click to collapse
Please note that this is a resource guide, not a Q&A thread. I have written a guide that I think may help you. http://forum.xda-developers.com/showthread.php?t=2585755
Disregard, already corrected.
AFAIK touchless control and active notifications are for the X only, please correct the first post(or me if I'm wrong)
Sent from my phone
miklosbard said:
AFAIK touchless control and active notifications are for the X only, please correct the first post(or me if I'm wrong)
Sent from my phone
Click to expand...
Click to collapse
You are correct.
Edit: Moto Maker is also not available for the Moto G
More OP edits
CM9 - Cyanogenmod 9. A modified version of ICS. (see CynogenMod)
CM10 - Cyanogenmod 10. A modified version of ICS. (see CynogenMod)
Should be JB
CM11 - Cyanogenmod 11. A modified version of ICS. (see CynogenMod)
Should be KK
Not that it matters right now, because we don't have any CM
Also, CyanogenMod is spelt wrong at the end. And I am pretty sure that you can remove all preJB words
INFUSION B2 Rom by @tillaz -
This is a JB ROM
And there is no need to label JB as 4.1, 4.2 and 4.3 because we only have 4.3
Also, you should add the two root methods for KK
http://forum.xda-developers.com/showthread.php?t=2583652
http://forum.xda-developers.com/showthread.php?t=2585755
In OP special features have listed Active noti and Touchless controls ....
both are not features of G(they are of moto x)
Cooptx said:
You are correct.
Edit: Moto Maker is also not available for the Moto G
More OP edits
CM9 - Cyanogenmod 9. A modified version of ICS. (see CynogenMod)
CM10 - Cyanogenmod 10. A modified version of ICS. (see CynogenMod)
Should be JB
CM11 - Cyanogenmod 11. A modified version of ICS. (see CynogenMod)
Should be KK
Not that it matters right now, because we don't have any CM
Also, CyanogenMod is spelt wrong at the end. And I am pretty sure that you can remove all preJB words
INFUSION B2 Rom by @tillaz -
This is a JB ROM
And there is no need to label JB as 4.1, 4.2 and 4.3 because we only have 4.3
Also, you should add the two root methods for KK
http://forum.xda-developers.com/showthread.php?t=2583652
http://forum.xda-developers.com/showthread.php?t=2585755
Click to expand...
Click to collapse
Thanks for mentioning. I have made rest of the changes except for the 2 Root methods. Will add them to the Op. All changes are done.
Between the two methods you have mentioned, the basic premise of bootloader downgrade is pretty much the same right ? Your's seems more elaborate list of steps. Or am I missing something ?
Ankush menat said:
In OP special features have listed Active noti and Touchless controls ....
both are not features of G(they are of moto x)
Click to expand...
Click to collapse
Thanks for mentioning. This has been corrected.
All developments are carried out thanks to donations on Purchase of these or other devices
thank
Please do not copy files to other file shares
the project is under constant development and refinement
Project name [ROM] Moto X L!te FW LPA23.12-15.5.EU.ML
Tagline Faster Lighter Economical
for XT1052/1053/1058 - 2G/3G/LTE
and only GSM XT1049/1050/1056/1060/ - 2G/3G/LTE (for CDMA use menu *#*#4636#*#*)
SYSTEM Firmware LPA23.12-15.5.EU.ML Multilingual
- firmware Deodex - allowing resources using modifiers such GravityBox apply all when firmware odex, it sometimes limited customization or going awry
- Launcher -4*5, no searche bar
- tzdata 2015f
- icudt53l last
- return "the gesture of the Jedi" (after installing the firmware of the old sensor /*** it does not threaten the phone)
- delete more apps FaceLock, MotoServices, Google Drive & Docs, Permissions and etc
- replaced by sound WirelessChargingStarted
- uppdate apps LatinIME, Migrate, Calendar, AudioMonitor, Moto, MotCamera, MotGallery
- Stagefright Fix
- removed a lot of the background services collect and send data on the type of phone DropBox, MotoCare, MotoConntect, Drive, FaceLock ... etc.
- add apps VendorApp ESFileManager, CCleaner
- added Russian, Ukrainian language
for Unloked Device
Install for Custom Recovery
Root not PreInstalled
Download there https://yadi.sk/d/jp8ykQqFindY8/MotoX/5.1.0
for Loked Device
5.1.0 for locked phones ready to be sewn LONG !!! 5.1.0 1.5 GB used by all, no matter what the new system weighs only 900MB ... the old system to be erased
Install for QDLoad9008
Root, BusyBox is PreInstalled
- Root SuperSU v2.46
- BusyBox v1.32.2
DISCLAIMER
Author is not responsible for totally bricked devices, broken arms, legs, plane crashes and your wife's cheating.
All actions taken is your own risk.
Instructions to install
You:
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
- unzipp _Rus_5_1_0_LPA23_12.XX.7_BL_V30.BE.rar to Cython27;
Method is dangerous, however gives results.
you must have firmware SU6-7 receiving is not in the form of an update (OTA) and stitched through the RSD Lite.
00 Flash *******_5.1.0-LPA23.12-XX.7_CFC.xml firmware
01 Unzipp everything to Cython27.
02 Run BLBROKE.bat.
03 After you got Qualcomm HS-USB QDLoader 9008, install drivers manually
04 Run RUN_Rus_Part**.bat. Parts 250 of system.
*** You can also run a file if you are sure that your phone can work 6-7 hours with the screen RUN_Rus_***_Full.bat
then repeat this step X times (the number of times equal to 6)
while (found next part) do
***
>> fastboot to hold 10 minutes that would have been charged a little phone
>> Run BLBROKE.bat.
>> Run RUN_Rus_***_Part**.bat. Parts 250 of system.
***
end
99 Turn device on. Now you have SU DEODEX PreRooted
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC
Scripts, ROM there -> https://yadi.sk/d/kxbxpTnziSg35/Moto X/5.1.0
Please do not copy files to other file shares
the project is under constant development and refinement
XDA:DevDB Information
[ROM] Moto X L!te FW LPA23.12-15.5.EU.ML, ROM for the Moto X
Contributors
CrashXXL
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: Android 5.1.0 LPA23.12-15.5
Version Information
Status: Stable
Current Stable Version: 1.00
Stable Release Date: 2015-10-19
Current Beta Version: 0.01
Beta Release Date: 2015-09-28
Created 2015-10-12
Last Updated 2015-10-21
So can I assume this is a stock based rom that has been debloated, optimized, and such but is fully functional as a stock Rom? I've been waiting to update the wife's X on account of all the reported troubles with the official lollipop update.
This firmware is the most clean and fast
It based on the stock, and includes all updates and patches
Hi!
First of all, thank you very much for your rom, the "jedi" gesture is back!
I checked the stagefright detector and it seems to be vulnereble to the "CVE-2015-6602" I asume is a new vulnerability and motorola haven´t patched yet.
I have installed the rom an hour ago and everything works as expected, so nothing else to report, if I find anything strange i will tell you.
Thanks again!
Iktor said:
Hi!
First of all, thank you very much for your rom, the "jedi" gesture is back!
I checked the stagefright detector and it seems to be vulnereble to the "CVE-2015-6602" I asume is a new vulnerability and motorola haven´t patched yet.
I have installed the rom an hour ago and everything works as expected, so nothing else to report, if I find anything strange i will tell you.
Thanks again!
Click to expand...
Click to collapse
stagefright was fixed in last update, so I would certainly expect this ROM to have that patch. also, I believe that this thread should be moved to the Development section, not in general. you may need a mod to help out.
"and only GSM XT1049/1050/1056/1060/ - 2G/3G/LTE (for CDMA use menu *#*#4636#*#*)"
So this could work on the Sprint network with a 1056?
please link to another server
Enviado desde mi Moto X mediante Tapatalk
May I know how often will you update?
What about the very serious glitch-bug on YouTube ? Is it fixed ?
Sent from my XT1052 using Tapatalk
the project will be updated as long as I have moto phone x1
applications such as YouTube, Chrome, and others I can not fix, maybe, I do not have the source code of the product
YES 1056 will work
Xposed?
wildblade64 said:
Xposed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed
CrashXXL said:
the project will be updated as long as I have moto phone x1
applications such as YouTube, Chrome, and others I can not fix, maybe, I do not have the source code of the product
Click to expand...
Click to collapse
Thank you for reply.
jco23 said:
stagefright was fixed in last update, so I would certainly expect this ROM to have that patch. also, I believe that this thread should be moved to the Development section, not in general. you may need a mod to help out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ota-xt1052-firmware-update-5-1-10-10-t3221898
Above thread has screenshots of XT1052 with update and shows that the above vulnerability is not fixed yet. It's the only one thats not fixed.
---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------
CrashXXL said:
the project will be updated as long as I have moto phone x1
applications such as YouTube, Chrome, and others I can not fix, maybe, I do not have the source code of the product
Click to expand...
Click to collapse
I'm sorry... I dont understand... Do these apps not work right now???
I want to try this ROM to get back to stock... I do not have a system to flash the stock files...
Please help me understand.
XT1049 on C Spire?
Do you think this ROM will work on XT1049 from C Spire? I also would like to use a stock based ROM.
I do not change third-party applications, such as YouTube, Chrome, and other Google search, wait for the update application from the developers (Google)
Sorry, I meant to say if this rom will have xposed built in. Thank you so much crash by the way, I'm assuming this will eventually work for xt1058 with locked bootloaders?
what is that?
the gesture of the Jedi
what is that?
On kitkat you could have your hand in front of the screen and it would display moto display, since the lolipop update, you have to hold your hand directly over the light sensor for a few seconds.
Hi,
So as many of you already knew - I'm working on porting CM13 onto my NU3001.
I has it on my desk table, so I could work on it during my days. (I have another NR3001 installed in my car)
I already made some work for our unit SW. This is quick screenshots. Sources based on xdAuto and CM13. This is a very BETA and many things not working for now.on.
Why? : When I realize than CyanogenMod 13 (6.0.1) works on my Motorola XT1080 better than stock - I start thinking of porting CM13 to our device. And when I have spare set - I start porting.
How? : I took easiest way - try to do not modify kernel a lot, instead adopt bionic and other libraries for out 3.0.36+ kernel.
Currently working staff (it is very beginning):
1. Recovery TWRP 3.0.2
2. CM13 (LineAge OS) booting.
3. Graphics working (there is some blinking present).
4. Wifi working
5. Android audio working
6. Bonovo Radio working
4. Most of the rest is on the way (GPS, BT, rest of Bonovo apps)
UPDATE_1:
I decide to do not stuck with CM 13 and switch to AOSP N release (7.0) (mostly because on my daily job - we also going to Android N, so it should be more familiar to me now)
Currently working staff:
1. Recovery TWRP 3.0.2
2. SELinux needs to be carefully ported (kernel part), cause starting from 7.0 is can not be disabled (as I did for CM13 to easy port)
During this port I will try to minimize inpact to AOSP release, so any future updates should be much more easier.
For you to understanding of amount of needed work - kernel already has 100+ patches on top of xdauto release. Approximate left about 250-300 patches to revise/port.
Android 7.0 port abandoned because of bigger and bigger amount of work need to be done to port SELinux on top of our outdated kernel.
UPDATE2:
I setup review build environment, so who want to look at NOT-FULLY-WORKING CM13 could download sources and binaries. I do not provide instructions how to flash it, because who wants to look and contribute already know hot to flash, and who doesn't probably don't really want this NOT-FULLY-WORKING CM13
UPDATE3:
So I finally managed to get functional networking. So now Wifi working, internet working, display working.
I starting to port all necessary items. No more 'hard' showstoppers so far.
New build (I believe it is build number 5) should be ready in an our on build server, so I could test it more fully.
UPDATE4:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8
UPDATE5:
Build number 15 has working audio + radio
UPDATE6:
Most of Bonovo changes ported, new build 20 ready.
This build contains zip file which should be flashable via twrp, but I not test it this way.
Issues remaining so far(most noticeable to me):
1. Display flickering (my suspect is to vsync/fence mechanism slightly changed in Android 6.0, need to investigate)
2. HW Volume buttons not working on device
3. No audio In
UPDATE 7:
Starting from build 23 following images available:
cm_rk3188-ota-XX.zip - update to use via TWRP
nu3001-la-cm13-XX-userdebug.tar.gz - build image for flash via command line rkflashtool under linux (full or partial flash)
rkflash_nu3001-la-cm13-XX-userdebug.zip - Full image to be flashed via PC GUI RK Batch Tool.
kernel_nu3001-la-cm13-XX-userdebug.tar.gz - just kernel with debug symbols for debugging purposes.
To just download sources:
repo init -u https://gerrit.nc.org.ua/manifest -b nu3001_cm13
If you plan to contribute - login to Gerrit with GMail, push your SSH public key, choose login name and then do:
repo init -u ssh://<user>@gerrit.nc.org.ua:29418/manifest -b nu3001_cm13
Builds will be available on Jenkins build server (login also via GMail, PM for access grant on current project stage):
https://jenkins.nc.org.ua/
1.5 GB folder on MEGA
4 files
mega.nz
Please do not spoof this thread with questions like "When?", I will try to post updates regularly in this message.
This thread created is mostly to exchange experience with this build once it is published (issues, TODOs, etc)
**Reserved **
First!
Second! Lol
I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.
At the very least I can beta test when its a little more complete.
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
Black're a legend !!
Your project is great !!! see Android 6.0 on Carpad would be great.
Thanks for the great effort you make for all
Woooow great !!
Good luck
nice one, i hope a very important feature:
"that can be use apps, which require android +4.4.4, like lollipop"
I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.
keep up work!
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
I want to buy NU3001 now, is there any way to get it?
vivacious said:
I want to buy NU3001 now, is there any way to get it?
Click to expand...
Click to collapse
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
vivacious said:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
Click to expand...
Click to collapse
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
Hi VBlack,
it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!
I have only one question:
With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.
When the power back very often the Carpad car remains with black screen until i touch it with my finger.
I think the problem is somehow related to the USB ports.
Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??
Thank you!!
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
Nice to hear from you. Sure I will share. Current situation is next:
CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.
AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...
So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
Sent from my DROID MAXX using Tapatalk
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
I update first post with sources and build information
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
shatteredsilicon said:
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
Click to expand...
Click to collapse
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
shatteredsilicon said:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
Click to expand...
Click to collapse
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.
So generally for what I have in mind:
1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.
2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.
So in any case it is very nice to have.
Flyme 6 Rom For Samsung T705 & T700Version information:
-By Cyborg (Chinese developer);
-Applicable Samsung T705 (klimtlte);
-ROM version:Flyme 6 beta version;
-Based on LineageOS 13.0. (Thank you for the work done by Exynos5420 team!)
Introduction to the note:
-Please line based on lineageos 13.0.
Notice:
-For T705/T705M/T705Y and T700!, not for T705C;
-About T700: After a lot of user testing, Flyme6 rom can be applied directly to the T700, without any modification (of course,
T700 does not use the call function)! The specific installation is as same as the T705).
-Please brush machine under twrp recovery;
How to install it?
step1: Download lineageos 13.0 installation package :
T705: https://www.androidfilehost.com/?fid=817550096634787685
T700: https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-13-0-sm-t700-t3554485
(Thanks @deadman96385 build lineageos13.0 rom for T700.)
step2: Flashing lineageos 13.0 use TWRP recovery 3.0+;
step3: Download the flyme6 installation package ;
step4: Flashingflyme6 use TWRP recovery 3.0+;
step5: reboot system
Don't forget to Wipes data,cache,and dalvik before you swipe rom!
Flyme 6 Introduction:
-Depth customization based on Andrews 6.0.1;
-To the content of the axis of the system design more primary and secondary, full of immersion, delicate Smart animation to make browsing the page becomes fun and fun;
-Innovation to join the intelligent thinking engine, can learn the user operating habits, according to the use of scenarios to provide intelligent solutions to create mobile phone light intelligence;
-More powerful parallel space security model allows users to multi-identity scenes can also switch freely.
Flyme 6 Highlights:
-Content Design;
-New word reread; intelligent thinking engine;
-Game mode; night self repair; process reaper; lightning start;
-Informed management of intelligent storage; notification fast management; new multi-task management;
-More features can go to Flyme official website to understand
Description:
-This ROM is based on Flyme open source project Pile fit, thanks Flyme development team, LineageOS development team;
-Use a third party Rec brush into the first brush into Flyme be sure to double clear, double before the data backup;
-Flyme6 first brush to start slowly, need to wait about 15 minutes, please be patient waiting to enter the system;
-If you need to double clear, please brush ROM before the double clear; brush ROM after the double will not be able to start the system;
-This ROM is a personal patch patch, non-Flyme co-development group ROM!
Disclaimer:
-1. The ROM has passed my test! As a result of improper operation of the consequences, I and the forum will not bear any responsibility;
-2. Brush before the phone to ensure that at least 50% or more of the power, and to ensure that the brush machine during the mobile phone and computer without any exception;
-3. Brush a risk, the first brush machine friends, be sure to carefully study the forum brush machine tutorial, otherwise the consequences of their own;
-4. I do not own ROM and the copyright of the program, please study and study for the purpose of legitimate use;
-5. It is forbidden to make your own ROM second tampering published! In particular, no technical content of the second package integration promotion software, offenders must study!
-6. If you brush into the ROM, it means that the above agreement has been accepted by default.
Root Support:
-Magisk Manager
Xposed Support:
-Link: https://www.androidfilehost.com/?fid=745425885120750151
Bugs:
-Fingerprint function can not be used;
-Call function has been tested, basically no problem. But the Mms function may have some problems, such as: when you send information to others, the other party will receive your information, but your tablet shows "send failed", there is no solution, if you know how to do ,please tell me. Thanks @acui @mac231us before doing feedback.
-This is based on Flyme experience version of the adapter, there should be some can not repair the "flyme error". If any, please feedback, maybe in the next version to solve!
Changelog:
---------------------------------------------------------------------------------------------------------------------------------------------------------
[2017.07.20]:
-First beta;
-Added magisk root
-Update the release files for version Flyme 6.7.7.14R;
---------------------------------------------------------------------------------------------------------------------------------------------------------
[2017.07.21]:
-Change version: Flyme 6.7.7.14R Cyborg-build-v2.0;
-Update magisk root version:
-Latest Stable Magisk Version: v13.3;
-Latest Magisk Manager Version: v5.1.1;
-Optimize the brush machine script, brush machine humanization process.
---------------------------------------------------------------------------------------------------------------------------------------------------------
[2017.07.28]:
-Change version: Flyme 6.7.7.21R Cyborg-build-v3.0;
-Update the release files for version Flyme 6.7.7.21R;
-Add xposed support,you have to install this zip by recovery : https://www.androidfilehost.com/?fid=745425885120750151
-Change the DPI-320 to DPI-420;
-Optimize the brush machine script, brush machine humanization process.
--------------------------------------------------------------------------------------------------------------------------------------------------------
[2017.08.18]:
-Change version: Flyme 6.7.8.11IR Cyborg-build-v4.0;
-Update the release files for version Flyme 6.7.8.11IR;
>> function adjustment
• System
Clearly tell you that the lock on the page that thing, waiting for the next time you will be locked when you know
Charm blue 5 / charm blue 3 / charm blue U10 / charm blue U20 replacement for the bottom of the Android, charm blue metal / charm blue 2 / charm blue 2 telecommunications version of the follow-up adjustment
• Calendar
Birthday / Anniversary / Countdown Day, Female Ticket Rhapsody Hurry to record it so as not to kneel the keyboard
Path: Calendar - New event - more options
>> Problem improvement
• phone Guardian
Repair the virus killing into the scanning state did not stop after the phenomenon
Repair mobile phone thin with the virus killing the same after the start also stopped the phenomenon
Repair the use of security scanning scan ticket two-dimensional code after the phenomenon of garbled
Other
Repair in the "reading" in a section of the text after clicking to share to the QQ will prompt the picture does not exist
Repair long press the home key or by language to wake up the "voice assistant" can not be recorded after the phenomenon
--------------------------------------------------------------------------------------------------------------------------------------------------------
[2017.10.01]:
-Change version: Flyme 6.7.9.22R Cyborg-build-v5.0;
-Update the release files for version Flyme 6.7.9.22R;
>> function adjustment
Function adjustment
Focus on optimizing the system resource allocation strategy, and comprehensively enhance the system stability and fluency
For the game scene for resource tilt, improve the game frame rate and performance during the game more fun
High frame rate mode automatically tighten the strategy to reduce the power consumption of mobile phones, reduce heat and so on
>> Problem improvement
• Camera
Repair open slow, open when the phenomenon of short black screen
• Video
Repair play local video and online video, there are Caton phenomenon
Resolve the problem that the video is still pushed after the push is pushed
--------------------------------------------------------------------------------------------------------------------------------------------------------
Download link:
---------------------------------------------------------------------------------------------------------------------------------------------------------
-[2017.07.20]: https://www.androidfilehost.com/?fid=961840155545583261
---------------------------------------------------------------------------------------------------------------------------------------------------------
-[2017.07.21]: https://www.adroidfilehost.com/?fid=817550096634787379
---------------------------------------------------------------------------------------------------------------------------------------------------------
-[2017.07.28]: https://www.androidfilehost.com/?fid=817550096634788959
---------------------------------------------------------------------------------------------------------------------------------------------------------
-[2017.08.18]: https://www.androidfilehost.com/?fid=889764386195923711
---------------------------------------------------------------------------------------------------------------------------------------------------------
NEW-[2017.10.01]: https://androidfilehost.com/?fid=817906626617934764
Thanks:
-Flyme group: https://github.com/FlymeOS/flyme-release
-Lineageos group: https://github.com/LineageOS
-Magisk group: https://forum.xda-developers.com/apps/magisk
-Exynos 5420 Team: https://github.com/exynos5420
-Other people who are not listed but who make efforts.
Wow, amazing. Thanks for sharing.Could it be installed on T700??
Enviado desde mi Redmi Note 3 mediante Tapatalk
alberbrando said:
Wow, amazing. Thanks for sharing.Could it be installed on T700??
Enviado desde mi Redmi Note 3 mediante Tapatalk
Click to expand...
Click to collapse
After a lot of user testing, Flyme6 rom can be applied directly to the T700, without any modification (of course,
T700 does not use the call function)! The specific installation is as same as the T705).
Telephone is good, data is good, can accept text message but cannot send text message
i will try to port it for t700 shouldnt be hard as i have ported a lot of roms from other devices to t700 but it will be online quite late cuz i have 0.1mbit upload
TimurAlaskara_TR said:
i will try to port it for t700 shouldnt be hard but it will be online quite late cuz i have 0.1mbit upload
Click to expand...
Click to collapse
Great,Timur.
Enviado desde mi Redmi Note 3 mediante Tapatalk
Is this rom based tw or aosp ?
Envoyé de mon SM-T705 en utilisant Tapatalk
aumast said:
Is this rom based tw or aosp ?
Envoyé de mon SM-T705 en utilisant Tapatalk
Click to expand...
Click to collapse
Based on lineageos 13.0
acui said:
Telephone is good, data is good, can accept text message but cannot send text message
Click to expand...
Click to collapse
Yes, but the message is not to send a failure, only to show "send failure" on T705, in fact the other person has received your message.
TimurAlaskara_TR said:
i will try to port it for t700 shouldnt be hard as i have ported a lot of roms from other devices to t700 but it will be online quite late cuz i have 0.1mbit upload
Click to expand...
Click to collapse
It's nice to see that you can prot it to T700, but you have to be aware that some bugs might not be fixed, because this flyme version is a beta version ！
Good luck!
yang_w said:
It's nice to see that you can prot it to T700, but you have to be aware that some bugs might not be fixed, because this flyme version is a beta version ！
Good luck!
Click to expand...
Click to collapse
yep i have used flyme os 6 on s7edge and s3 noth were crap
we need to wait for future builds
fixed flashing error...
that was fast!...wow (understand was under development already) thanks...downloading now
---------- Post added at 08:16 PM ---------- Previous post was at 07:44 PM ----------
getting some symlinks faliked error 7 in updater process (error installation) - this is for twrp 3.1.1 and did full wipe (system, cache, data, dalvik/art cache before flashing.
fixed flashing error 7
reboot recovery
go to mount panel and uncheck cache
then full wipe (if not done already) then flash the zip
booting now...
---------- Post added at 08:56 PM ---------- Previous post was at 08:16 PM ----------
yang_w said:
Sorry, it does not work with T700 because I only have T705. But I believe flyme6 can be used on the T700, provided that there is a developer to adapt it
Click to expand...
Click to collapse
tried v2 on my T705M (705 Latin American version) ..calls work (no reboots no sound issues-except other caller/person at other end of line can hear his sound (slight)..common issue on many CM/AOSP in my experience for some of these tablet phone devices (not the pure smartphone devices - think something to do with mic and internal speaker arrangement)...however tab A 7.0 T285 CM 13/14 has no such issues not sure why (is a 7 inch tablet phone device) so not sure
anyway you have my report on the calling function-maybe someone else has some more ideas/insight or different experience..thanks
Thank you for some feedback on the call function, which will give some reference to other users. In fact, after the test, in my T705 (TGY Hongkong, China) on the call function is very perfect, but the Mms function will be some problems, I have not found a solution to the problem.In fact I have only one Nano Sim card, but it is applied to my Iphone 7plus, so testing these features will be more difficult.
--About Flash this flyme6 rom:
This Flyme6 is based on lineageos13 production, so it is best to flash los13 / cm13 first, and then flash flyme6, this Introduction may avoid some mistakes. If you did not flash los13 / cm13 before, you may need to FULL WIPE, and then brush into flyme6, of course, I did not test this operation.
i can confirm that this rom is also working verrrryyy well on t700 without any extra bugs. i flashed this rom over full aosp 7.1.2. it has still got all these stabdard flYme os bugs on board. another thing is that it is based on a phone ui and it needs some optimization for tablets just like i did on my old sucuk rom for tab s.
future builds without flyme os bugs would make it possible to use this as a daily driver
yang_w said:
Thank you for some feedback on the call function, which will give some reference to other users. In fact, after the test, in my T705 (TGY Hongkong, China) on the call function is very perfect, but the Mms function will be some problems, I have not found a solution to the problem.In fact I have only one Nano Sim card, but it is applied to my Iphone 7plus, so testing these features will be more difficult.
--About Flash this flyme6 rom:
This Flyme6 is based on lineageos13 production, so it is best to flash los13 / cm13 first, and then flash flyme6, this Introduction may avoid some mistakes. If you did not flash los13 / cm13 before, you may need to FULL WIPE, and then brush into flyme6, of course, I did not test this operation.
Click to expand...
Click to collapse
yes just noticed today that the lineage 13 is needed to flash first (I did not do this-had a custom MM stock-based rom before this, then did the full wipe and directly went to the flyme package) Will do the stated method in the original post OP thanks
TimurAlaskara_TR said:
i can confirm that this rom is also working verrrryyy well on t700 without any extra bugs. i flashed this rom over full aosp 7.1.2. it has still got all these stabdard flYme os bugs on board. another thing is that it is based on a phone ui and it needs some optimization for tablets just like i did on my old sucuk rom for tab s.
future builds without flyme os bugs would make it possible to use this as a daily driver
Click to expand...
Click to collapse
Please share your build for t700
U don't need to port t705 ROMs to t700 .. They usually work without any edit.
U can also flash it without flashing lineage before
Linage (cm) has hardware issues with the t705 requiring some rewrite of the device tree, since the devs are busy with N this most likely will not be solved at all. These issues effect fingerprint sensor, mic, and battery drain ( in some cases a rouge process clocks the processor at 40% continuously ).
All ROMs using Lin/cm codebase ( and the deathly kernel obviously ) will share the same probs in part or in whole ( exception to this is vanir who do a lot of their own work on top of the cm codebase ).
This ROM is the same, a bunch of commits put on top of a very shaky base.
I am working on a solution but it will be aosp based since they have the only fully operational ( as regards to hardware ) implementation (have reposted it ), some mild kangs on top of the already working code.
PS. The unofficial cm13 build at XDA has solved some of the bugs ,being outside of the official cm13 branch, fingerprint and others still there.
TimurAlaskara_TR said:
yep i have used flyme os 6 on s7edge and s3 noth were crap
we need to wait for future builds
Click to expand...
Click to collapse
Hello, TimurAlaskara_TR. Can you tell me how to port it to the T700? There are already many people who need T700 flyme6. If you tell me the way, I will modify and upload to AFH.
To port it too t700. A t700 will be required. Thats all. Although the t705 version may flash as is to t700
{
"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"
}
team bliss is pleased to present to you
bliss rom based on Android 9 Pie
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Notice
- READ: The OP and most recent discussions will generally help to answer any questions you will encounter. If not, we will do our best to answer your questions & concerns as soon as possible. We will also simply direct you to the OP if the answer is contained there. We encourage community minded interactions: users helping fellow users allows Team Bliss to focus on the work involved to make things Blissful.
- Please do not ask for ETA's;
- We will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts;
- We encourage users to contribute towards this project, and we're openly accepting applications for others to join Team Bliss
First, a little bit about this project...
Starting in Android Pie, Bliss OS will be taking a different approach to building Android for PC's. Taking inspiration from @phhusson 's Treble methods, and Intel's Project Celadon, we have reworked a good majority of the commits from Android-x86 Project and Bliss OS's Oreo release, and packaged it up so that it can work a bit more dynamically. The result was something we could integrate into a single source, along side normal device builds. This is much like our Treble builds that use PHH's Treble methods, and Intel's Project Celadon's EFI builds. Both of which are also buildable directly from the BlissRoms-x86 source: https://github.com/BlissRoms-x86/manifest
These Bliss OS releases will be considered the Bleeding Edge of development for Android on x86, and we will be marking most of our additions to be sent down the ladder to our Android-PC project & hopefully Android-x86 Project as well. For now though, you can stay tuned to this thread for updates on all that.
ROM Porting Details:
Like we mentioned already, things this round will be done a bit differently using the patching system to build for x86 devices, making updating and maintaining far easier than before, and even lowers the bar for understanding how it all works. But things were still complicated enough for us to see room for improvement. So we have also packaged up all the x86 bits we add to Bliss OS, minus a few goodies and are making them available to the entire community to add to their ROM projects. You can find the basics on GitHub already, https://github.com/Android-PC and for those interested in adding x86 support to your own ROM, I was able to squash things down to a single commit in build/make in order to help get the ball rolling. This will also be the source we are helping out Android-x86 Project with, so don't be surprised if things change a bit to reflect that projects branding more.
https://github.com/Android-PC/platform_build/commit/eda2e16b0018c5554f98acaa708f8200a171f206
I'm always open to suggestions on how we can improve upon things too, so don't be afraid to speak up, just remember to be considerate upon doing so
We will be updating our website also over the next few weeks to feature a new downloads section, as well as further information about using our source for commercial projects.
AIO Thread
Bliss Source
https://github.com/BlissRoms
BlissRoms Devices Source
https://github.com/BlissRoms-Devices
BlissRoms Kernel Source
https://github.com/BlissRoms-Kernels
BlissRoms Vendor Source
https://github.com/BlissRoms-Vendor
BlissRoms-x86
https://github.com/BlissRoms-x86
Bliss' Android-PC Project
https://github.com/Android-PC
Open Gapps Project
!!CONSIDER THESE AS DEVELOPMENT BUILDS FOR NOW!!
These are not to be considered stable in any way shape or form. Please continue at your own risk. Developers and experienced users suggested
This release is a work in progress, and will take community effort in order to iron out all the bugs.
There are no IPTS builds for the Surface devices yet, and there won't be until I am able to fix my SurfaceBook. Sorry :'(
Read the documentation first:
https://docs.blissos.org
Team Bliss is not responsible in any way for anything that happens to your device in the process of installing
Please familiarize yourself with available installation options before attempting to install the OS.
Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
Download the ISO file
Use Rufus or similar to burn to USB drive
Disable Secure Boot, Bitlocker, and any other boot security
Boot into the USB drive.
Run Bliss OS in Live mode to test things out, if all is well, continue to next step
Boot into the USB drive, and choose Bliss OS Install
Pick your poison, but please do this with caution, making sure to fully understand what you are doing.
These are beta builds, so please take that into consideration when reporting issues. We want all the info possible
Packages Manager sometimes crashes the system. This will require you to wait, then open a terminal and use $ su && svc wifi disable , and when it comes back, $ su && svc wifi enable
Screenshots aren't working yet
Video playback does not work right as of yet
Sound issues on many machines still
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
-Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
-After downloading the Catlog app, go to the app settings, and change the log level to Debug.
-Clear all previous logs and take the exact steps to produce the error you are receiving.
-As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
-Copy and paste the entire log either to Hastebin or Pastebin
-Save the log, and copy and paste the link into the forum with a brief description of the error.
-You can also open trouble tickets on our website for bugs.
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
If someone takes it upon themselves to donate to us, of course it will be appreciated, and all funds will be used to pay our server and upkeep fees.
If someone wants to donate, our PayPal link is below.
PayPal Link
Very Important Information
Team Bliss will allow some minor off-topic comments in our development threads.
Please post in the general forums for off-topic comments and/or questions.
Overall, please keep comments relevant to development, as this better helps you and our team
when trying to determine problems that users are having.
We appreciate all levels of knowledge in our threads, and therefore we ask that
the seasoned members be helpful to those with less knowledge.
Most importantly, do NOT troll those with less knowledge than yourself.
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts.
We thank you for adhering to our thread rules.
Thank you for using Bliss! And have as always: #StayBlissful
XDA:DevDB Information
Bliss OS - Pie for PCs (development Beta Preview), ROM for the ROM Central
Contributors
electrikjesus, ElfinJNoty
Source Code: https://github.com/BlissRoms
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: x86 Arch
Version Information
Status: Beta
Current Beta Version: 20181018
Beta Release Date: 2018-10-18
Created 2018-10-19
Last Updated 2019-07-23
The Instructions
We have moved the instructions to be a part of our docs site
For the main instructions to get going with Bliss OS, you can check out our Installation Guide
If you get into a bind with your install, you should see our Troubleshooting section
For the few addons and other info we have for Bliss OS installs, you can check out our Extras section
And if you're ready to start building and testing new things, you can check out the Bliss OS Build Guide.
Thanks, and keep scrolling for FAQ & Updates
Build Types Explained:
Q: Bliss builds come with funny names. Why?
A: Because we felt the need to include the various branches for Kernel, Mesa, & Firmware in the build name.
So, when you see a name like this:
Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso
It can be broken into 3-4 parts.
Build ID: "Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457"
Kernel Branch: "_kernel-4.9"
Mesa Branch: "_m18.3.0-devel_w40_LLVM70"
Firmware Branch: "_dev-kernel.org"
Q: What do the parts of the kernel names mean?
A: When we add a batch of commits to the kernels, we like to save that version with an identifier. So the most common parts to the kernel names are as follows:
-ax86 : Means that this kernel started off from the Android-x86 repo, or has the majority of Chih Wei's commits for that kernel
-ma : Means this started out from Maurossi's repo. (https://github.com/maurossi/linux)
-gal : Means that this kernel also includes compatibility with Chromebook devices, from the peeps at Gallium OS (https://github.com/GalliumOS/linux)
-ipts : Means that we are including some specific commits for the Intel IPTS touchscreens (mostly in the Surface line of devices) These builds likely won't run well on most other devices.
Q: OK, So I have a BlahBlah CPU, with a Such'n'such GPU, what builds are right for me?
A: Well, we have a method to all our madness there. We build Bliss OS with different kernels that work as a way to make it more compatible with different types of devices. Here is the breakdown on those:
Kernel-4.9 These are considered the most "Stable" builds, they will work across most older and recent devices.
Kernel-4.12-14 builds will be hard to come by, but seem to work great for some newer Atom based devices.
Kernel 4.15+ builds will not work on some older devices, so consider these to be a little less "All-In-One"
Kernel 4.18+ Intended for newer devices. adds some newer touchscreen support and added AMDGPU support
kernel 4.19+ Intended for newer devices. Even more touchscreen support and ACPI support
Kernel 4.20+ Intended for newer devices. Even more touchscreen support and added ARM/ATOM support and Vega GPU support
Kernel 5.0+ This is where things will start getting tricky. Even more touchscreen support, and added support for ARM/ARM64/ATOM etc, but also a ton of Android kernel commits start making their way into things.
For all other FAQ's, please check the Wiki or our Telegram Chat
Recent Update Posts:
Updates, Round 1 - 2018.10.28
https://forum.xda-developers.com/showpost.php?p=77999419&postcount=55
Updates, Round 2 - 2018.11.07
https://forum.xda-developers.com/showpost.php?p=78092995&postcount=112
Forgotten Kernel-4.18 build - 2018.11.01
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=175
Christmas Build - 2018.12.25
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=238
Fist Release of 2019!! - 2019.01.16
https://forum.xda-developers.com/showpost.php?p=78691527&postcount=337
Second Release of 2019!! - 2019.01.21
https://forum.xda-developers.com/showpost.php?p=78730287&postcount=363
Updates to kernel-4.20 - 2019.01.26
https://forum.xda-developers.com/showpost.php?p=78768409&postcount=378
Surface IPTS build updates - 2019.01.30
https://forum.xda-developers.com/showpost.php?p=78796749&postcount=396
Update for Bliss OS - 2019.02.05
https://forum.xda-developers.com/showpost.php?p=78841065&postcount=412
Bliss OS Updates - 2019.02.23
https://forum.xda-developers.com/showpost.php?p=78973810&postcount=500
Bliss OS Updates - 2019.03.10
https://forum.xda-developers.com/showpost.php?p=79083283&postcount=549
Bliss OS 11.6 Updates - 2019.03.24
https://forum.xda-developers.com/showpost.php?p=79188758&postcount=576
Bliss OS 11.7 Updates - 2019.04.03
https://forum.xda-developers.com/showpost.php?p=79265706&postcount=616
Bliss OS 11.8 Updates (with GMS) - 2019.04.23
https://forum.xda-developers.com/showpost.php?p=79397531&postcount=676
Bliss OS 11.9 Release (with GMS) - 2019.05.26
https://forum.xda-developers.com/showpost.php?p=79607423&postcount=827
Bliss OS 11.9 (with GMS) -EXPERIMENTAL x86 (32 bit) builds - Build Date 2019-08-01
https://forum.xda-developers.com/showpost.php?p=80044597&postcount=1039
Bliss OS 11.10 x86_64 Generic Vulkan Build - EXPERIMENTAL - Build Date 2019-09-01
https://forum.xda-developers.com/showpost.php?p=80172193&postcount=1130
Announcement - Community Builds
https://forum.xda-developers.com/showpost.php?p=80672909&postcount=1268
Bliss OS 11.10 x86_64 Generic & IPTS Builds - With Vulkan - Build Date 2019-12-14/15
https://forum.xda-developers.com/showpost.php?p=81209911&postcount=1396
Bliss OS 11.10 x86_64 Generic - With Vulkan - Build Date 2020-04-11
https://forum.xda-developers.com/showpost.php?p=82275141&postcount=1675
Bliss OS 11.11 x86_64 Generic - With Vulkan and other graphics options - Build Date 2020-06-24
https://forum.xda-developers.com/showpost.php?p=82967929&postcount=1796
Bliss OS 11.11 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-08-03
https://forum.xda-developers.com/showpost.php?p=83214267&postcount=1841
Bliss OS 11.12 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-09-25
https://forum.xda-developers.com/showpost.php?p=83661769&postcount=1916
Bliss OS 11.12/13 x86_64 Generic - Kernel 4.19.122/5.8 - Mesa-19.3.5/20.1.0 - Release Date 2020-11-14
https://forum.xda-developers.com/showpost.php?p=83919621&postcount=1947
Bliss OS 11.14 x86_64 Generic - Kernel 4.19.122/5.10 - Mesa-19.3.5/20.1.10 - Release Date 2021-05-09
Bliss OS - Pie for PCs (LTS)
team bliss is pleased to present to you bliss rom based on Android 9 Pie Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all...
forum.xda-developers.com
Downloads
Downloads has been moved for now. Please use the latest link from our website:
http://blissos.org
or
http://blissroms-x86.github.io
Contributing to the project
Bliss OS is in need of contributors. People to help squash some bugs, forward port features and support, and others to help with answering the common questions here in the XDA threads, or on our Telegram chat.
Pull requests are going to be spread out a little. All the commits for the build script will go through http://review.blissroms.com While everything else will have to be in the form of pull requests from https://github.com/BlissRoms-x86 or https://github.com/Android-PC
For anyone interested in joining our team, please visit the Bliss Family page of our site for more information on how to do that
https://blissroms.com/bfor.html
For those with even a little experience, but a lot of drive to learn more, we also offer our services to help people learn the ropes. https://t.me/Team_Bliss_Build_Support
Or for those a little more committed, look into the Bliss Family page of our site and join from there.
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
AllanJacques said:
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
Click to expand...
Click to collapse
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Does not work on Asus t101ha (cherrytrail)
wenna.speedy said:
Does not work on Asus t101ha (cherrytrail)
Click to expand...
Click to collapse
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
vEEGAZ said:
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Click to expand...
Click to collapse
Also for your case, can you try booting up with the old modprobe method mentioned in the second post? It may handle that wifi chipset a bit differently.
Another thing to try is to disable and then re-enable wifi service:
$ su
$ svc wifi disable && svc wifi enable
electrikjesus said:
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Click to expand...
Click to collapse
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
AllanJacques said:
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Instead, how about I tell you about this update Microsoft pushed to the surface book that made it to where I can't test my IPTS, or any kernel currently...
So to help with quality assurance, I would rather wait until I can test a build to make sure it works as expected before passing it off to the public.
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
mickey36736 said:
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
Click to expand...
Click to collapse
You got that result when using the easy installer? Did you try using the bootable USB install?
electrikjesus said:
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
Click to expand...
Click to collapse
I tried all boot options - stucked on boot everytime.
electrikjesus said:
You got that result when using the easy installer? Did you try using the bootable USB install?
Click to expand...
Click to collapse
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
mickey36736 said:
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
Click to expand...
Click to collapse
The symptoms suggest that some of your hardware isn't being detected right on install
Surface pro 2017 touch screen
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
I'm just gonna ignore this and ask you to read the OP again, but slower
Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
You shall wait until we release a build that supports your ipts display, and then rejoice!
Pie is "beta preview" and we build BlissOS to run on 1000's of potential HW configurations. Then we test with the devices we possess. When deemed ready, we share. A build which supports your device specific issue: not ready yet.
The info you requested to do this manually can be found using the search function of XDA(visit the website instead of app and look in a thread for "search this thread" then type: manual driver
.....or just read the OP ?