Related
Introduction:
Please read and try to do some research instead of bombarding the developers with the same questions over and over, cluttering the threads with useless and recursive information. I will try to include terms for all the ROMs and Kernels in the Development Section, and remove the obvious things as much as possible. That doesn’t mean it will be perfect! I hope this will be useful for beginners, because it provides most of the basic information you need to get started. From now on, it’s up to you what you do.
I am fully aware that the information included here is for one time use, enough to get you started. Some of these things ARE well known by many of you, but they are still useful for others that are just beginning to learn about their NS. Besides definitions and explanations, I’ll also link to useful posts around xda and other sites, which provide further information on the respective subject.
ROMs(ROM: a firmware that contains the Android operating system, and at least critical apps necessary for running your phone (but usually more apps than just those); can be stock or custom, and comes packaged in a *.zip file, flashable under recovery)
AOSP-built ROMs
Features: these are built from source code, from the Android Open Source Project, delivered free of bloatware and with rich customizations.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyanogenMod 9 (still in alpha stages for now)
IML74K Android 4.0.3 Build 4 - Quad Lockscreen + More MODS (1/15/12)
nuhetri- v1.0.0
Slim ICS
AOSP+ V2.3|ICS 4.0.3|Source Built|Status Bar Widgets + Nice Mods
4G VERSION
vhgomez36-ICS-NXS-4G-4.0.3 r2.0
IML74K Android 4.0.3 Build 3 - Quad Lockscreen+More MODS
Crossbones v0.1.3
CyanogenMod 9 v4.0.3 - Alpha 20
Click to expand...
Click to collapse
Moddified ROMs
Features: these are modified versions of stock/AOSP ROMs/other custom ROMs, that keep the look of the base ROM up to a certain point. Also generally free of bloatware and with some additional modifications.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
CyberGR-MOD|NS.NGN ver. 4.0 Ultimate
NSCollab 1.0.60
Ultimate ICS v4.0
-=Nexus MV 1.12.09=-
KANGY6 | ICS | AOKP |
NexusBeam 4.2.3
CyberGR-MOD|NS.NGN ver. 3.0 Hybrid ICS
Click to expand...
Click to collapse
MIUI-style ROMs
Features: unique type of ROM, developed by the Chinese. Has a strong iOS feel, highly customizable.
Some of the most popular (at the moment):
GSM VERSION: i9023/i9020A/i9020T
◄ ▌ [09.Jan.12] [ROM] Brainmaster's MIUI 2.1.6 ICS | Stable 2.3.7b v2 GB ▌►
DianXin OS (DX ROM) ICS | GB ROM
4G VERSION
◄ ▌ [28.Nov.11] [ROM] brainmaster's MIUI NS4G 1.11.25 | OTA ▌►
Click to expand...
Click to collapse
Stock ROM
Official releases from Google. The reasons most people here flash a stock ROM are: they want to update/ are bored of custom ROMs/ want to start over with their phone/ warranty reasons.
If you want to go back to stock for some reason, check this thread and read carefully, so you get the correct version for you.
Click to expand...
Click to collapse
Once we decide for a type or ROM (except stock), we head over to the ROMs thread and begin reading the list of features. Now would be a good time to PANIC! No, no, just kidding Those words do exist in some kind of language (not necessarily English). So here’s a very basic list of the most common terms found in our ROM threads:
Code:
[B]AOSP[/B]
[quote]Short for [url=http://source.android.com/]Android Open Source Project[/url]. Its purpose is to maintain the development
of the Android platform. Anyone can use the Android source code for
any purpose, and this is when custom ROMs come in. The [AOSP]
tag is used here to signal a ROM built from Google’s source, a pure
ROM, free of bloatware, with very good performance (generally)
and a very extended degree of customization. [/quote]
[B]Build.prop[/B]
[quote]This file is located in /system/build.prop. It holds the majority
of the runtime flags that are used when Android boots. Basically, it
lists specific information about your device, for applications to use.
You can also edit lines, with a file manager that has access to
/system, in order to change LCD density, build number, device
model and many more. [/quote]
[B]Busybox(ed)[/B]
[quote]Busybox is a collection of simple, but powerful Linux
utilities, that Android doesn't come with by default. It is used
by applications like MetaMorph and Titanium backup in order
to do special operations. You can manage ther version installed
on your phone with various apps from the [url=https://market.android.com/search?q=busybox&c=apps]market[/url] [/quote]
[B]/boot partition[/B]
[quote]This partition includes the bootloader and kernel, and
it enables the phone to boot. Wiping it must be done only if
requested, and the phone must not be rebooted after this operation.
Instalation of a new one is done by flashing a ROM that includes
the /boot partition. [/quote]
[B]/cache partition[/B]
[quote]Inside this partition, Android stores frequently accessed
data and app components. Performing a wipe of the /cache does
not affect personal settings or files, but simply gets rid of existing
data there, which gets automatically rebuilt in time. [/quote]
[B]Dalvik cache[/B]
[quote]Dalvik cache collects the information about the installed
applications and frameworks, and organizes them into a writeable
cache. Under this writeable cache, it stores the “optimized”
bytecode of the applications which is used by the applications
themselves later for a smoother operation. This dalvik cache can
grow as more applications are installed on your phone. It is safe
to wipe dalvik-cache. It will be rebuilt again when the phone
boots. This also explains why your phone takes ages to start up
for the first time. [/quote]
[B]/data partition[/B]
[quote]Also called userdata, the data partition contains the user’s
data – this is where your contacts, messages, settings and apps
that you have installed go. Wiping this partition essentially performs
a factory reset on your device, restoring it to the way it was
when you first booted it, or the way it was after the last official
or custom ROM installation. When you perform a wipe data/factory
reset from recovery, it is this partition that you are wiping. [/quote]
[B]Deodex(ed)[/B]
[quote]In Android file system, applications come in packages with
the extension .apk. These application packages, or APKs contain
certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application
that are optimized before booting. Doing so speeds up the boot
process, as it preloads part of an application. Deodexing is basically
repackaging of these APKs in a certain way, such that they are
reassembled into classes.dex files. By doing that, all pieces of an
application package are put together back in one place, thus
eliminating the worry of a modified APK conflicting with some
separate odexed parts. The advantage of deodexing is in modification possibilities. On the other hand, since the .odex files were supposed
to quickly build the dalvik cache, removing them would mean
longer initial boot times. However, this is true only for the first
ever boot after deodexing, since the cache would still get built
over time as applications are used. [/quote]
[B]EFS folder[/B]
[quote]This is a VERY important folder. It contains phone-specific
information, like IMEI (encrypted in the nv_data.bin), wireless
devices MAC addresses, product code (also in the nv_data.bin)
and more. I advise you to make a backup of this folder, and keep
it safe. Remember, backup BEFORE flashing anything. Use [url=http://forum.xda-developers.com/showthread.php?t=1138873]this tool from forum member Borky_16[/url]. [/quote]
[B]Init.d[/B]
[quote]Init.d is very useful because it runs scripts that you can
just delete or replace in the /system/etc/init.d folder. The scripts
are also very flexible and can be used to call other scripts or set
a variety of system settings. [/quote]
[B]G-apps/Gapps[/B]
[quote]A long time ago, in a galaxy far far away, there was a
developer. And he used the Force for developing something called
CyanogenMod. For the happiness of the other folks in the galaxy,
he included some applications from Google. But the Emperor…
oh, sorry… But Google didn’t agree with him including these
proprietary apps, so they sent him a cease and desist letter.
Long story short, the Google Applications are provided separately
via a flashable .zip file. This is the case for pure AOSP ROMs,
and theoretically this is how it should be done. Theoretically. [/quote]
[B]Host File[/B]
[quote]Located in the /etc/ folder, it is used to block ads.
Most ROMs come with a “blocks ~95% of ads” statement. You
can also manage it with apps from the [url=https://market.android.com/search?q=ad+block&c=apps]market[/url]. [/quote]
[B]Logcat[/B]
[quote]The Android logging system provides a mechanism for
collecting and viewing system debug output. Logs from various
applications and portions of the system are collected in a series
of circular buffers, which then can be viewed and filtered by
the logcat command. You can use logcat from an ADB shell to view
the log messages.[/quote]
[B]NANDroid[/B]
[quote]When you take NANDroid backup, it means you are
backing up entire ROM. It’s basically a picture of the ROMs’
state . So when something goes wrong, you have the
chance to restore your phone to the backup state using the NANDroid. [/quote]
[B]NSTools[/B]
[quote]An essential tool that manages tweaks like BLN,
BLD, BLX, Liveoc, OC, CPU Governor, Deep idle and so on.
Written by arifhn, available in the [url=https://market.android.com/details?id=mobi.cyann.nstools&feature=search_result#?t=W251bGwsMSwyLDEsIm1vYmkuY3lhbm4ubnN0b29scyJd]market[/url] and on [url=http://forum.xda-developers.com/showthread.php?t=1333696]xda[/url],
this is a must have application for managing these various options. [/quote]
[B]Odex[/B]
[quote]These ‘odex’ files are actually collections of parts
of an application that are optimized before booting. Also explained at deodex(ed). [/quote]
[B]Power Menu[/B]
[quote]A multiple choice menu that appears when long pressing
the power button. In stock, these are critical options,
such as powering down the device. Developers have also
added options for taking snapshots,
rebooting normally/into bootloader/into recovery and so on. [/quote]
[B]Radio[/B]
[quote]The radio controls basic low-level functions like
network connectivity, Wi-Fi, and GPS. It comes as a radio.img file,
and generally, developers try to leave this out of their
ROMs because different areas require different radios. Pay attention
to this when choosing to flash a new ROM. There is a reference
thread with all the radios [url=http://forum.xda-developers.com/showthread.php?t=1116884]HERE[/url]. [/quote]
[B]Ramdisk[/B]
[quote]Ramdisk.img is a small partition image that is mounted
read-only by the kernel at boot time. It only contains /init
and a few config files. It is used to start init, which will
mount the rest of the system images properly and run the
init procedure. A Ramdisk is a standard Linux feature. [/quote]
[B]Recovery[/B]
[quote]Recovery mode in Android provides an environment for
users to wipe cache, data, factory reset the phone or update
it with a .zip file. There are custom recoveries like [url=http://www.clockworkmod.com/rommanager]ClockworkMod[/url] or [url=http://forum.xda-developers.com/showthread.php?t=1399565]TWRP[/url], which provide additional functionality,
and are very popular for this reason. [/quote]
[B]RTL[/B]
[quote]Short for Right-to-Left and refers to support for languages requiring this type of writing. [/quote]
[B]SetCPU[/B]
[quote]An application built by coolbho3000, which allows CPU speed tweaking and management, allows overclocking, and sets CPU governors. Available on [url=http://forum.xda-developers.com/showthread.php?t=505419]xda[/url] and the [url=https://market.android.com/details?id=com.mhuang.overclocking&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5taHVhbmcub3ZlcmNsb2NraW5nIl0.]market[/url] (try to buy from the market if you want to support his work). [/quote]
[B]SIM Toolkit (STK)[/B]
[quote]Now if you live in the States, you might not even know what
the STK is, so a bit of explaining is in order. Put simply, the STK
allows carriers to load a simple set of menus and 'applications' on
your SIM card. Earlier versions of Android, up to 1.6, actually
included a rather rough, but functional Sim Toolkit application, but
at some point it was dropped. [/quote]
[B]/system Partition[/B]
[quote]This partition basically contains the entire operating system,
except the kernel and the bootloader. This includes the Android
user interface as well as all the system applications that come
pre-installed on the device. Wiping this partition will remove Android
from the device without rendering it unbootable, and you will
still be able to put the phone into recovery or bootloader mode
to install a new ROM. [/quote]
[B]Unsecured Boot.img[/B]
[quote]Used for adb remount, gets you root by default on a shell. (ro.secure=0) [/quote]
[B]V6 Supercharger Script[/B]
[quote]A more technical explanation could be done here, but
the bottom line is that this is used to make your phone run
faster, by better management of memory. [/quote]
[B]Zipaling[/B]
[quote]Zipalign is an archive alignment tool introduced first
time with 1.6 Android SDK (software development kit). It
optimizes the way an Android application package (APK) is
packaged. Doing so enables the Android operating system to
interact with the application more efficiently, and hence has
the potential to make the application and overall the whole
system much faster. Execution time is minimized for zipaligned
applications, resulting is lesser amount of RAM consumption
when running the APK. [/quote]
Kernels
(Kernel: provides the most basic level of control over all of the phone's hardware; consider them a link between the hardware components and the ROM)
With kernels it’s a little bit easier. At least this is how it may seem. Right after rooting the device, many choose to first flash a kernel (including me) mostly because it gives the opportunity to flash something while not modifying the appearance of the phone. Furthermore, it gives you the ability to change things like CPU clock speed, internal and ARM voltages, and also have different patches and mods designed to prolong battery life/improve speed/provide stability.
Kernels are abundant for the NS, so I’ll be naming the most popular:
GLaDOS
ICUP Kernel Edition
*Matr1x*
SG-NS-ICS - 14-01-2012 - 11UV|Voodoo|BFQ|BIGMEM|BLN|BLD|BLX|TW|Lazy|3.0.15
Netarchy Nexus
NS+4G Trinity (E)UV and OC CM9 + m(any) roms
Click to expand...
Click to collapse
Many users ask around about which could be the best kernel. For this, xda member bedalus decided to set up a thread where he benchmarked ICS kernels (accurately enough). This should give you an idea where to start from.
Also, there are terms which appear frequently in the features list of kernels, so here’s a very basic list of the most common terms found in our kernel threads:
Code:
[B]BFS[/B]
[quote]A Brain F**ked Scheduler will perform better on CPU intensive
process, which usually cause them to get higher benchmark scores.
However because it only dedicates minimal CPU to background
processes you may experience lag when switching quickly between
different tasks. [/quote]
[B]BLD[/B]
[quote]Backlight Dimmer provides an option for the lights of the
touchkeys to be turned off after a certain period. This can be
tweaked from NStools. [/quote]
[B]BLN[/B]
[quote]Backlight Notification is a mod developed by neldar,
which converts the touchkey backlights into a notification led. [/quote]
[B]BLX[/B]
[quote]Battery Life eXtender, from Ezekeel, manages the maximum
percentage to which the battery is being charged. By default,
the Nexus S is charged to about 95% capacity. [/quote]
[B]CFS[/B]
[quote]A Completely Fair Scheduler is more suited for multitasking.
You may notice performance issues when using CPU heavy
activities like HD games because it is trying to keep the other
processes in the background equal to the one that is hogging the
CPU. It should also be noted that, as designed, this type of
kernel should handle going from listening to music to sending a
text to surfing the web with minimal lag. [/quote]
[B]Deep IDLE[/B]
[quote]Another mod by Ezekeel, which allows the phone to
enter a “deep idle” state while performing tasks when the screen is
off. For example, listening to music with the screen off and
Deep Idle turned on, you should get better battery life than
without Deep Idle. [/quote]
[B]Governors [/B]
[quote]There is a much to be said here, and this would stretch
this dictionary too much. I recommend reading [url=https://github.com/CyanogenMod/cm-kernel/blob/android-msm-2.6.37/Documentation/cpu-freq/governors.txt]THIS[/url], a very good explanation of
governors—from CyanogenMod. [/quote]
[B]OC (Overclock)[/B]
[quote]An overclock is usually one of the first things users
figure out after gaining root access on a new phone. If you
want to push your smartphone's CPU to run more clock cycles,
you have to know that extra power isn't coming from nowhere.
However, it is generally considered good practice, but it
depends on your handset. Some phones may be able to support
overclocking to 1.4 GHz, while others may never get past
1.2 GHz. Just proceed with caution. [/quote]
[B]Touch Wake[/B]
[quote]Yes, yes, Ezekeel again. This mod allows the user to
wake the device after a set amount of time, just by touching
the screen or the capacitive buttons. The time after which the
screen no longer responds to a touch is set with NStools. [/quote]
[B]UV (Undervolt)[/B]
[quote]This refers to lowering the voltage to conserve power while
still achieving the same performance, assuming your settings
remain stable. Both SetCPU and NStools allow the user to change
voltages. Like overclocking, this is also a trial and error process,
because each phone is different. The benefits are low energy
consumption and less thermal output. [/quote]
Tools & Mods
So you have a rooted phone. Maybe even a custom Kernel or ROM, whatever works for you. But you still want to be a tad different from the other guys using the same configuration as yours. So here's a small selection of mods and apps developed by members of the community, enough to get you started. Feel free to experiment, and remember: read before flashing, search before asking and you should be alright!
Mods for AOSP+ Rom
[BOOTANIMATION] Plain, Simple & Colorful + color variants
Nova Launcher
Flavours for stock OTA ICS 4.0.3
Search key to ICS recent apps [add CM9 version]
[NS][NS4G]FaceLock for ICS 4.0.3
Enable on-screen buttons in ICS roms
Click to expand...
Click to collapse
NOTES:
I am hoping this little survival guide is useful FOR BEGINNERS in understanding the basic terminology used here in the Nexus S sections. As the title suggests, it was made with beginners in mind, so I don’t want posts of so called “experts” saying how they already knew this.
IMPORTANT: I do NOT guarantee the explanations written here are completely accurate or complete, FOR NOW. I will keep working on this, correcting mistakes as I continue to read.
If you find something that you think is not correct, or consider something must be added, please post here, together with a link to a credible source.
All of this came from sources off the internet, so please bear with me. Also, sorry for any typing mistakes. If you see any, please be sure to signal them
If I have helped you in any way, or if you appreciate the work invested in this (now and for the future), press the THANKS button.
Thank you! (Hoping to see this stick) And many thanks to all the great devs working on ROMs and Kernels for us. Keep up the great work!
W O R K - I N - P R O G R E S S
(I will be sure to notify you when I believe this is complete)
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
ljordan2 said:
Wow this is a very good idea. Thanks!
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Thank you! I'm just worried it is a little bit long... but in the next couple of days I will be making it more reader friendly
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
nice thread! thanks
Hey great post, i still haven't rooted my nexus s but you just made me flash a kernal. I was tkinking about it but never too serious.
thanks!
Love it!!! Cleared so much up (you recieved my first Thanks button click!)
Just wanted to clarify something about the Kernel. My Rom is stock 2.3.6 that was received OTA when I unboxed the phone (Nexus S GSM i9020A, I'm in Canada). The bootloader is unlocked, phone rooted with CWM recovery via one click (QBKing's Video). Am I able to flash a custom Kernel to a stock Rom? Reading the above seems to lean towards the "yes", but wanted to make sure first.
Also, do not use the one click method on the Nexus S GSM if you want to easily return to stock. The one click stock only supports the 4G, which is extremely silly and inconvenient IMO. I'm currently still trying to figure out how to return to stock, incase something does happen and the phone needs warranty work. Let's just say, I'm not making much progress and this is extremely uncomfortable ATM..
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Thanks so much for taking the time to do this
Sent from my Nexus S using XDA App
Harbb said:
Great thread and idea, all seems spot on. I vote for sticky.
Also, heX, you can flash a custom kernel on a stock rom as long as you have an unlocked bootloader and custom recovery. I'd recommend you backup all you need with TB or similar, then do unlock your bootloader if you havn't already (search around for how to do this, described in rooting guides). Just remember this will delete -ALL- user data, including sdcard. After this you can flash a su.zip to have proper root access, and you can easily install a stock image with a custom bootloader then lock the bootloader afterward for pure stocky goodness.
Click to expand...
Click to collapse
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
very useful for us newbie, thanks for sharing
heX79 said:
TYVM Harbb!
Yes, currently the bootloader is unlocked, phone rooted and CWM installed. I did a TB backup prior so I could quickly restore my apps and settings. All is running well.
I tried to flash a full stock Rom back to the phone, but have run into an issue in doing so, posted here
I'm still awaiting some help with regards to that one, hopefully all will be well soon.
I'm not sure why I got spooked in doing this. I'd like to try the Matrix kernel and there are various Roms that definitely sound fantastic, but part of me just wants it back to stock so warranty and OTA are restored as the phone is only a few weeks old.
Click to expand...
Click to collapse
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
great post OP
Nice thread! Great Work ,Thanks
Hey thanks! Happy to see good feedback on this.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
Great beginners guide, and thanks for the link!
For kernel benchmarks and more, see here: http://goo.gl/mpeHI
Thanks very much! I will give it a try shortly, just to confirm if I recieve any issues. I've also installed the recommended CWM version for my model, not sure if it makes a difference, but I flashed 5.0.2.0 anyway as the version I was getting an error with had a higher build number.
Right now I'm enjoying AndroidME 1.2.3 with Speedy 6 kernel and have no complaints so far! (Kernel updated this morning from Speedy 5)
I will report back with any issues once I have some time to do a Nandroid backup and test the stock Rom.
Thanks for your help!
It's nice to know there's a way to revert back to stock, should anything need servicing! I've also started reading up on Odin
flodb113 said:
Ok I see you have the att version, so i9020A. When android 4.0.3 came out, I wanted to go back to stock 2.3.6 so that I could update officially. Anyway, I downloaded a full stock ROM, flashable via recovery, from HERE and all went smooth for me. (the link is to the i9020A version, of course I used the i9023 version). Try the stock posted there, and see if you get any error. I think you should be ok now, if not, post back. Remember, this takes you fully back to stock, no cwm, no nothing custom.
I am glad to see that I helped somenone, I will make some modifications this afternoon, still 9am here (maybe add stuff to the dictionary and post it to google docs or something like that, just to make it easier to scroll through and more). Any suggestions or critics are welcome!
EDIT: Guide updated:
-better arrangement of the dictionary (will be adding new terms tomorrow, had to study for an exam today)
-added Tools & Mods section (will build on that later on)
-more to come...
Click to expand...
Click to collapse
You're welcome! Looking forward to an update with your stock flashing situation. I also used ClockworkMod 5.0.2.0 a long time. I'm now on 5.0.2.3 only for the better menu layout.
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
just one question...
can i install more than one kernel at a time...
for eg.like one i installed for battery usage and othr for sound..
can i do tht
Since I am not allowed to post in the developer thread, I want to thank this way for the great gift Omnirom 4.4.
You have breathed new life into my n7000. :crying:
Thanks to chasmodo, herna, AA1973 and all the developers involved in the project for the hard work, patience and humor.
I hope the error report in the new version today (omni-4.4.1-20131208-NIGHTLY-n7000) can help the project to continuously improve.
Awesome ROM indeed
Sent from my GT-N7000 using xda app-developers app
can you show how smooth its running with a video or so?
Same here.. Even I can't post in that thread.
Its a awesome rom, smooth, new features etc. But I have to share some bugs which I thought may be shared here:
1. Can't move apps to sd card.
2. Bluetooth when connected through car (for phone and audio), disconnects and reconnect in every 11-12 mins.
3. Google search and google play services are consuming too much of battery. I guess its a Kitkat issue.
I am currently on 8th Dec rom. Rest is pretty good. No problem at all.
You can't post in a development thread until you reach the number of 10 posts... But you can search the thread without posting..
If you use hot word recognition in GLE, then it will drain battery.
Kernel > herna posted a Kernel which enables apps to be moved. Although Google deprecated this AFAIK.
Last, but not least, thanks for being mentioned, flatters me - but I am *not* a developer!
GALAXY NOTE N7000 // KITKAT 4.4.1 // OMNI
AA1973 said:
You can't post in a development thread until you reach the number of 10 posts... But you can search the thread without posting..
If you use hot word recognition in GLE, then it will drain battery.
Kernel > herna posted a Kernel which enables apps to be moved. Although Google deprecated this AFAIK.
Last, but not least, thanks for being mentioned, flatters me - but I am *not* a developer!
GALAXY NOTE N7000 // KITKAT 4.4.1 // OMNI
Click to expand...
Click to collapse
Even when I switched off the hot word recognition in GLE, location services off, no auto sync, etc still Google search or google play services is the most battery drainer when the phone is not used overnight.
OmniROM is really a real gift for the N7000. It's much better than Cyanogemod for me, because the performance is better. But i also had some trouble and i'm not able to post in the developers thread. Here are my problems:
- external SD card isn't mounted properly, so i have to take some detours to open it with ES explorer
- when i enable ART i can't lock the screen anymore (omni-4.4.1-20131208-NIGHTLY-n7000)
- OpenDelta is able to reduce the update size, but when it boots into TWRP the update fails because the script is searching /sdcard which is the external SD, but the update.zip is stored in the internal SD which is mounted as /emmc, so you have to update manually
Do you have the same issues ?
G4liant said:
OmniROM is really a real gift for the N7000. It's much better than Cyanogemod for me, because the performance is better. But i also had some trouble and i'm not able to post in the developers thread. Here are my problems:
- external SD card isn't mounted properly, so i have to take some detours to open it with ES explorer
- when i enable ART i can't lock the screen anymore (omni-4.4.1-20131208-NIGHTLY-n7000)
- OpenDelta is able to reduce the update size, but when it boots into TWRP the update fails because the script is searching /sdcard which is the external SD, but the update.zip is stored in the internal SD which is mounted as /emmc, so you have to update manually
Do you have the same issues ?
Click to expand...
Click to collapse
No issues with me as you have mentioned. All three options are available to me.
Saurabh4255 said:
Same here.. Even I can't post in that thread.
3. Google search and google play services are consuming too much of battery. I guess its a Kitkat issue.
Click to expand...
Click to collapse
in expanded wifi settings disable "google search if wifi is deaktivated"
updater worked for me today
prinzkazimir said:
in expanded wifi settings disable "google search if wifi is deaktivated"
updater worked for me today
Click to expand...
Click to collapse
Have done that but no success. But yes.. Bcoz of disabling this the footprint of google search on battery consumption is less as compare to previous settings. But other culprit Google play services remains the same.
Just to update on continuous bluetooth disconnection, I unpaired my car connection and also deleted the phone from car and reconnect it. As for now it is paring up nicely for more than 20 mins. Lets see how it reacts if connected for more than this.
My battery is doing fine now, btw.
G4liant said:
- external SD card isn't mounted properly, so i have to take some detours to open it with ES explorer
- when i enable ART i can't lock the screen anymore (omni-4.4.1-20131208-NIGHTLY-n7000)
- OpenDelta is able to reduce the update size, but when it boots into TWRP the update fails because the script is searching /sdcard which is the external SD, but the update.zip is stored in the internal SD which is mounted as /emmc, so you have to update manually
Do you have the same issues ?
Click to expand...
Click to collapse
Use another file explorer. Might be also an issue of es file explorer. Or a mixture of both, as es expects the external in mnt/media_rw
Don't enable ART. It is experimental and has to be treated as such. Hence it is hidden in developer options.
Didn't have such an issue with OpenDelta. In any case. Please remember that
A) Omni is a very "young" firmware
B) OpenDelta has been introduced 2 nightlies ago. Be gentle and patient
For me, OpenDelta worked this morning.
Did you enable SuperSU backup script within SuperSU app, too?
GALAXY NOTE N7000 // KITKAT 4.4.1 // OMNI
AA1973 said:
For me, OpenDelta worked this morning.
Click to expand...
Click to collapse
I will find it out tomorrow.
AA1973 said:
Did you enable SuperSU backup script within SuperSU app, too?
Click to expand...
Click to collapse
For now i haven't activated the backup script. EDIT: It's activated now.
Then do it.
GALAXY NOTE N7000 // KITKAT 4.4.1 // OMNI
Update: Regarding the google search and play service battery consumption, I tried cache and dalvik cache wipe through recovery mode and now batery is giving good backup.
OpenDelta worked good for me! Also running ART! Thanks!
Wonder what boot shows on asylum
prinzkazimir said:
OpenDelta worked good for me! Also running ART! Thanks!
Wonder what boot shows on asylum
Click to expand...
Click to collapse
Well, there is only one way to find out.
But be careful, don't do it if you have a hearth condition or are prone to epilepsy.
Azeazezar said:
Well, there is only one way to find out.
But be careful, don't do it if you have a hearth condition or are prone to epilepsy.
Click to expand...
Click to collapse
Had I listened to you!
As a precaution I have taken the 9/12. I look in here again when I'm back from the sanatorium.
Thank you so much Omni team. I was waiting this ROM. It’s really great user friendly and smooth.
Query: Do the active display in display setting uses the moto x like feature of only activating the pixels where the display is required and not the whole screen?
AOSP - Android Nougat - 7.1.2 - NZH54D
This is a pure build of AOSP Android 7.1 Nougat, the goal is to have a pure AOSP rom for Samsung T705, so it is not the objective of this project to include any functionality that is not native to Android AOSP.
Download:
ROM: Mega, AndroidFileHost
Modem(OJ1): Mega, AndroidFileHost
Gapps:
OpenGapps: http://opengapps.org/
Choose ARM platform
Root:
SuperSU: http://www.supersu.com/download
Credits:
Kernel is based on LineageOS's Exynos5420 kernel, device tree is based on @Schischu, @deadman96385 and his Exynos5420 team's marvelous works.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Code:
2017-09-12
- Latest AOSP (NZH54D) Android 7.1.2_r33
- Screen rotating glitches fixed
- New Bluetooth HAL, distortion fixed
- Rework RIL, more stable phone calling and receiving
- IR blaster fixed with new IR HAL
- This might well be the last Nougat release, I will work on Oreo from now on
2017-06-19
- Latest AOSP (NJH47B) Android 7.1.2_r17
- Some kernel tweaks
2017-06-14
- AOSP (N2G47O) Android 7.1.2_r8
- Kernel 3.4.113
- Baseband version OJ1 (see download link above for modem file)
- Fingerprint disabled, everything else work, [B]including mobile data[/B]
Flashing instructions:
Flash TWRP 3.0.2 or higher
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
and wipe them. Don't reboot just yet.
Go into install menu
Select and flash rom file aosp-XXX.zip
Select and flash SM-T705_OJ1_MODEM.zip if needed. You might need to change the file name to modem.zip
Wipe cache/dalvik cache and reboot to system. Due to some bugs, we can't flash opengapps alone with this rom
After the successful first boot, boot back into recovery and flash gapps and supersu.
Reboot to system
Contributors:
@scubajeff
Source Code: https://github.com/scubajeff/
ROM OS Version: 7.1.2 Nougat NZH54D
ROM Kernel: Linux 3.4.113
Based On: AOSP
Status: Stable
Created: 2017-06-14
Last Updated: 2017-09-12
Reserved.
UI Screenshot please
Waaaaww.. Another klimtlte AOSP.. Really amazing works.. Could you give us partial screnshoot please..
And do you have a plan to continue to maintain this build..?
Thankssss in advance :good::good:
maz izaackovich said:
Waaaaww.. Another klimtlte AOSP.. Really amazing works.. Could you give us partial screnshoot please..
And do you have a plan to continue to maintain this build..?
Thankssss in advance :good::good:
Click to expand...
Click to collapse
Of course I will maintain this build and I'm planing for a Android O update in the near future.
scubajeff said:
Of course I will maintain this build and I'm planing for a Android O update in the near future.
Click to expand...
Click to collapse
Nice..!! Android O . Glad to see another dev like you maintain this AOSP, since schisu and maloshasa has stopped their project, in AOSP based on MM os. Downloading now, I'll report back if there's some bug..
Currently using latest RR Nougat
Thankssss sir..
___________________________________________________________________
hy sir.. come again to report some issues
1. there's glitches in every opening apps or recent apps, ie. : i opened browser and then i opened COC or others, so i found there was glitches between switching that apps, and nearly happened in every swtching or opening apps ( i guess this aint my screen problem, never have been happened before)
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
3. in owner user setting: i got my picture placing upside down than it supposed to be.
over all it works smooth and light. i hope i dont bother you with my issues report
thaannnnkkss..
Sorry, I'm english short.
When I'm calling with bluetooth, voice distorted. Please fix this problem. Thank you.
Ssanmai man said:
Sorry, I'm english short.
When I'm calling with bluetooth, voice distorted. Please fix this problem. Thank you.
Click to expand...
Click to collapse
Distortion happen on your side or the other side can't hear your voice clear enough?
Sent from my Samsung SM-T705 using XDA Labs
maz izaackovich said:
Nice..!! Android O . Glad to see another dev like you maintain this AOSP, since schisu and maloshasa has stopped their project, in AOSP based on MM os. Downloading now, I'll report back if there's some bug..
Currently using latest RR Nougat
Thankssss sir..
___________________________________________________________________
hy sir.. come again to report some issues
1. there's glitches in every opening apps or recent apps, ie. : i opened browser and then i opened COC or others, so i found there was glitches between switching that apps, and nearly happened in every swtching or opening apps ( i guess this aint my screen problem, never have been happened before)
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
3. in owner user setting: i got my picture placing upside down than it supposed to be.
over all it works smooth and light. i hope i dont bother you with my issues report
thaannnnkkss..
Click to expand...
Click to collapse
1. I have glitches when rotating the screen, but never see them when switching apps, even when using double tapping of recent app button to fast switch between 2 most recent apps.
2. I will look into this one, however could you kindly be more elaborate that during all those steps, was your t705 mounted to you laptop thru. MTP ?
3. I could not reproduct this one neither, my avatar in owner profile now is clearly showing that the nose is below the eyes.
Thx for reporting. Keep them coming.
Sent from my Samsung SM-T705 using XDA Labs
scubajeff said:
1. I have glitches when rotating the screen, but never see them when switching apps, even when using double tapping of recent app button to fast switch between 2 most recent apps.
2. I will look into this one, however could you kindly be more elaborate that during all those steps, was your t705 mounted to you laptop thru. MTP ?
3. I could not reproduct this one neither, my avatar in owner profile now is clearly showing that the nose is below the eyes.
Thx for reporting. Keep them coming.
Sent from my Samsung SM-T705 using XDA Labs
Click to expand...
Click to collapse
1 yes.. . Glitches in opening apps, and rotating it.
2. Yah, thru MTP. I can't see my file, but ext sdcard is accesible thru my laptop, but not a copied file. When i look for it into "file explorer" in my tablet, it's there. So I have to unmount-remount my ext sdcard, and even worst i have to restart my tablet then i plug in back thru my laptop to get "my copied file" accessible..
Thaannkksss...
maz izaackovich said:
1 yes.. . Glitches in opening apps, and rotating it.
2. Yah, thru MTP. I can't see my file, but ext sdcard is accesible thru my laptop, but not a copied file. When i look for it into "file explorer" in my tablet, it's there. So I have to unmount-remount my ext sdcard, and even worst i have to restart my tablet then i plug in back thru my laptop to get "my copied file" accessible..
Thaannkksss...
Click to expand...
Click to collapse
Do you mean that the list of file is not refreshed on the laptop side?
Sent from my Samsung SM-T705 using XDA Labs
scubajeff said:
Do you mean that the list of file is not refreshed on the laptop side?
Sent from my Samsung SM-T705 using XDA Labs
Click to expand...
Click to collapse
Yeessss.. Thats right.. Sorry for my bad english
maz izaackovich said:
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
Click to expand...
Click to collapse
I can reproduct this one, seems to me it's an long overdue bug of Google's implementation of MTP, related to media rescan. It happened under many circumstances, see this bug report --> https://issuetracker.google.com/issues/37071807
Sadly, Google refuse to acknowledge it as a bug.
Hi Scubajeff
I am experiencing an issue with com.android.phone and android.process.acore keeps failing to respond and its having a detremental effect on the battery life.
Any ideas how to fix this ?
ypmud said:
Hi Scubajeff
I am experiencing an issue with com.android.phone and android.process.acore keeps failing to respond and its having a detremental effect on the battery life.
Any ideas how to fix this ?
Click to expand...
Click to collapse
I ever had that issue, when i unisntalled google stock contact "Contacts.apk and ContactsProvider.apk" to replace with "zenui dialer and contact"
I guessed your issue it's related with, that your stock contact isnt installed properly
Try to flash these two .apks (Contacts.apk and ContactsProvider.apk) taken from your rom thru trwp or cwm recovery . It's solved my problem.
is there a way i can disable both phone and contacts ?
I am not on a rooted device
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Its ok I have figured it out that I needed to wipe the device due to it using my previous apk's
ypmud said:
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Its ok I have figured it out that I needed to wipe the device due to it using my previous apk's
Click to expand...
Click to collapse
Yes, if you are coming from other ROM, it's really, truly, absolutely important to WIPE ALL before flashing.
scubajeff said:
Distortion happen on your side or the other side can't hear your voice clear enough?
Click to expand...
Click to collapse
First, I confirm that my side distorted.
So far not bad. Both my 3G and LTE data are working fine, not sure about calls yet as I haven't tried. I do get those weird artifacts when I rotate the screen, but I've seen that on most of the Nougat 7.1 based ROMs. Nice work with the Kernel. It seems to be VERY customisable in Deathly Adiutor which is great for me. As with all Nougat based ROMs, the audio input latency is the best it's ever been. I would like the ability to enable software keys and to be able to bypass the hardware keys because as you most certainly know they have a strong tendency to interfere with this device (I keep catching them with my hand). Also, the IR blaster doesn't work AT ALL. I would like that to be fixed as Peel Smart Remote is an everyday app for me and I can't use it with this ROM.
simonjonnemeth said:
So far not bad. Both my 3G and LTE data are working fine, not sure about calls yet as I haven't tried. I do get those weird artifacts when I rotate the screen, but I've seen that on most of the Nougat 7.1 based ROMs. Nice work with the Kernel. It seems to be VERY customisable in Deathly Adiutor which is great for me. As with all Nougat based ROMs, the audio input latency is the best it's ever been. I would like the ability to enable software keys and to be able to bypass the hardware keys because as you most certainly know they have a strong tendency to interfere with this device (I keep catching them with my hand). Also, the IR blaster doesn't work AT ALL. I would like that to be fixed as Peel Smart Remote is an everyday app for me and I can't use it with this ROM.
Click to expand...
Click to collapse
I have to admitted that I didn't test the IR at all. Will give it a run asap. Sorry.
Sent from my Samsung SM-T705 using XDA Labs
I can now say I can only just make a phone call with this ROM. It's echoey and almost unmanageable when it does work, but it doesn't always work (no sound, normally causes the phone to lock up and force reset upon hanging up). I really want a non-stock ROM that works, preferably Android Nougat 7.1.2 but everyone seems to get the half finished, get fed up and leave us in the dark, and then finally after 6 months mark it as discontinued (cough cough LiquidDeath). I hope you don't do that because this ROM is promising.
Edit: The locking up may have been my fault for overclocking too high.
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
AFAIK these roms cover other Moto G3 versions but investigate more for yourself.
Always keep Nandroid backups using TWRP of your running Rom. I keep copies of my latest Android 10 Chli360/Lineage running Roms on my Phone's portable SD card in the phone and also on my Laptop.
https://twrp.me
Warning!
I've never bothered with any Android 8 Oreo roms on my G3 2015 Osprey. I went straight to Android 9(PIE).
https://chil360.github.io
I've tried most and now I'm only interested in the Lineage versions and the Havoc versions of Android 10 as these keep the Hardware FM radio that I like to use.
Havoc version,
Havoc-OS-v3.3-20200306-osprey-Unofficial.zip
Working fine and
Lineage,
ineage-17.1-20200308-UNOFFICIAL-osprey.zip
Working fine.
Note: If I recall correctly Chil360 Havoc Android 10 Rom does not need Gapps installing. If Lineage does I use Arm_10_Pico,
Note:
When setting up the phone I never let the phone install backups automatically I have my apps backed up on my SD card and re-install them from there. Google photos will not not clone-Install and a few others so I just re-download those.
Contacts:
Although Google backs up contacts lists to be safe I keep an,"Old School" backup using the Contact's apps Import/Export option and save them to a .vcf file. This will look like contacts.vcf or 000001.vcf on the phone wherever you have chosen to save it. This can be imported into any contacts app,Even on APPLE phones!
I send a copy of this .vcf file to myself attached to an Email. This means I can download my contacts to any phone anywhere in the World if I ever need to.
Note:
I never encrypt my phones so cannot answer any questions on this subject.
If you want to,"Root" the phone then install the .zip version of Magisk from your phone's Internal Memory and keep it on your phone's Internal memory. You install the .zip using TWRP's install option and always take it's advice on clearing Dalvik Cache and Cache.
Then once the phone is booted update both it and it's manager via an Internet connection.
Note: Some,"Pay/Money" apps will detect that you are running a non-stock rom. You can hide these apps using,"Magisk Hide" and in some cases you need to Hide the app AND then use Magisk option to rename itself. You can call it anything you like but keep it simple like Osprey.
HTH
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
Chil360 has updated the April 2020 Havoc 3.4 and it now installs on the Above phone. I am testing it as I post.
Havoc-OS-v3.4-20200417-osprey-Unofficial.zip. Does not require Gapps installing.
BTW I do like the AOSP_Pizza Android 9 rom for Chil360 as well(Still has FM RAdio).
https://www.androidfilehost.com/?fid=4349826312261742008
I go back to it sometimes as it has some features others don't have like showing local temp on the Lockscreen and also allows me to install a Custom boot animation logo. I like the old,"Stitch" Moto Logo
The Android 10 roms won't let me change the animated loading logos(They will let me change the static boot logo) or I need to find versions that will work with Android 10
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
Just thought I'd update.
Started to install Chil's latest Paranoid Android and it installed fine but stopped as I realized it doesn't have as many tweaks as Havoc 3.4.
Things I like about Havoc 3 series.
I can have,
Date and time in the notification bar.
Battery percentage next to Battery icon and time left when Notification bar is swiped down.
Easy to swap software buttons(I'm right handed so like my Back button on the right).
It still lets me use my old version of Holo Launcher.
You can assign functions to the Software buttons like Long press to Lockscreen. Can't seem to get Long press to enable the Flashlight tho
Advanced Restart on Power button.
Loads more tweaks to explore.
One thing I would like but I'm not sure if the Motos are capable but I have a cheap China phone that lets me double tap the screen to wake it up and I don't mean just at the Top of the phone I mean anywhere on the screen.
I can't see myself using any other version except as stated AOSP Pizza for a bit of a change now and then
PS
Continued thanks to CHIL his work is much appreciated keeping these Classic little phones going
Latest Chil360 roms are out. I'm running Havoc(May Security updated) but FM radio not working
Has anybody else had issues with the FM radio not working after upgrading to v3.5-20200508 version of Havoc Android 10 for Moto G3 2015? I found after upgrading to this version, the FM radio would no longer work, it would just freeze. Downgrading to v3.4-20200417, it would work perfectly again. Upgrading again to v3.5-20200508, it no longer would work. Has anything been changed that would cause this? Other than this issue, I believe that the ROM is excellent.
Gord
Glad you found this. Checking the FM radio is usually one of the first things I do but didn't this time
Yes you are right it's not working for me as well in Havoc 3.5.
Gone back to 3.4 with no problems :good:
Gordster
Thank you for responding to my reply and addressing the FM radio issue. I have found one other ongoing problem with the camera app. This has been occurring with all custom roms that I have tried whether Android 9 or 10. When photos or videos are saved to the internal phone, they go to the "main storage\DCIM\Camera" directory. I however like to save my photos and videos directly to the SD card.
With Android 6 they could be directed to "sdcard\DCIM\Camera" directory but with all custom roms I've tried when directed to the SD card, they wind up in "sdcard\Android\data\org.lineageos.snap\files" directory. Can this be changed so they go directly to the default location "sdcard\DCIM\Camera" directory?
Thanks
Gord
Gordster said:
Thank you for responding to my reply and addressing the FM radio issue. I have found one other ongoing problem with the camera app. This has been occurring with all custom roms that I have tried whether Android 9 or 10. When photos or videos are saved to the internal phone, they go to the "main storage\DCIM\Camera" directory. I however like to save my photos and videos directly to the SD card.
With Android 6 they could be directed to "sdcard\DCIM\Camera" directory but with all custom roms I've tried when directed to the SD card, they wind up in "sdcard\Android\data\org.lineageos.snap\files" directory. Can this be changed so they go directly to the default location "sdcard\DCIM\Camera" directory?
Thanks
Gord
Click to expand...
Click to collapse
I haven't used a Stock android Camera for years. I use the way better,"Open Camera" .You can set it to save to the SD card by enabling it's framework option and then pointing it to the SD card. It now says it contains ads but It used to be ad-free but I haven't seen any ads even in the latest version.
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_GB
Open Camera > Gear icon(settings) More Camera controls and Use Storage Access Framework and then Save location and say yes to permissions asked
R1ffR4ff said:
I haven't used a Stock android Camera for years. I use the way better,"Open Camera" .You can set it to save to the SD card by enabling it's framework option and then pointing it to the SD card. It now says it contains ads but It used to be ad-free but I haven't seen any ads even in the latest version.
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_GB
Open Camera > Gear icon(settings) More Camera controls and Use Storage Access Framework and then Save location and say yes to permissions asked
Click to expand...
Click to collapse
How can you use the OpenCamera? I try that but the photo with flash are blur, only Moto Camera can do photo with flash without the blur effect.
stukdev said:
How can you use the OpenCamera? I try that but the photo with flash are blur, only Moto Camera can do photo with flash without the blur effect.
Click to expand...
Click to collapse
Open camera has worked on all the roms I've tested.
Try another Camera app and if it does it with that you may have a hardware fault
Make a Nandroid backup and then do a Factory reset from Recovery mode but when setting up the phone don't let Google auto install any apps and just get to the Stock camera as soon as you can and see if it works. There may be an app you install that is causing the problem.
BTW.
Check back through this thread on how I install custom roms. I do it clean and add my apps back after I've got into the phone from .apk backups.
R1ffR4ff said:
Open camera has worked on all the roms I've tested.
Try another Camera app and if it does it with that you may have a hardware fault
Make a Nandroid backup and then do a Factory reset from Recovery mode but when setting up the phone don't let Google auto install any apps and just get to the Stock camera as soon as you can and see if it works. There may be an app you install that is causing the problem.
BTW.
Check back through this thread on how I install custom roms. I do it clean and add my apps back after I've got into the phone from .apk backups.
Click to expand...
Click to collapse
Maybe its an hardware fault, but with the Moto App i haven't any problem
stukdev said:
Maybe its an hardware fault, but with the Moto App i haven't any problem
Click to expand...
Click to collapse
See previous reply and also I don't know if you know the,"Soft Reset" trick on Moto phones that can clear some problems.
Press and hold the Power button in for around 10/15 seconds until the phone restarts. This emulates taking the Battery out and can clear clogged RAM of old data that can prevent correct operation
I've been running the latest May AOSP PIZZA
AOSiP-9.0-Pizza-osprey-20200517.zip
Since yesterday and all seems fine so far. Only thing missing is the local Temp on the lock screen unless I'm missing a setting. This was the same with the last version
Not a deal breaker
Installed Chil360's latest AOSP_QUICHE Android 10 June updates(Clean install).
AOSiP-10-Quiche-osprey-20200605.zip
All working well including FM Radio. Updated TWRP using the APP to 3.3.1 as the TWRP clock and date went funky but may not be related.
Phone is still rooted with Magisk and Root removed before installing clean and then re-rooted and Magisk updated.
Nice editing option to move Software buttons around in the AOSP roms. When texting I have a habit of hitting the Home button making my SMS app disappear. I've moved my Home button a little off-centre more to the right(I'm right handed) and this has cured that
Update. The Rom is working well but it's doesn't feel as slick as the AOSP_PIZZA version(May version) so I've gone back to that for now just out of personal preference.
So presently my faves are Havoc 3.4 and Havoc 3.6(Android 10) 2020 and AOSP_PIZZA Android 9 May 2020 version(Moto Stitch Boot animation).
Again my ongoing thanks for CHIL360's work in keeping these great little phones updated
Latest Android 10 Havoc 3.6 released by Chil360 with June 2020 updates,
https://chil360.github.io/ten.html
Gapps included.
Installed and all working e.g Text/Calls/GPS/FM Radio/ WiFi/WiFi Hotspot/Camera/Bluetooth etc.
Very fast booting and really slick
One possible glitch is the Stock Camera has the option to Save to SD but it doesn't seem to work. As I rarely use the Stock Camera preferring the much better,"Open Camera" from the Playstore this is not an issue for me
PS
Because of the dedication of the Android Developers on here we have an old 2015 Phone/s with more up-to-date software than many brand new phones
Chil360 has released a first and new Rom to his collection. Android 10 PixelExperience Plus 10.0,
https://chil360.github.io
If you like Google I think you will like this
I wonder if he might be looking to work on the new Android 11 if it can be used on the Moto G3
Then install Gapps if required.
Then do another Factory reset for good measure.
If ever there's a problem when first setting up after the first boot-up has loaded just press and hold the Power Button in for around 10/15 seconds and the phone will reboot(Soft Reset) which emulates taking the Battery out. [/B]
Chil360 has released a new Rom,
potato_osprey-10-20200619-croquette.v3.2.0+15.Community.zip
Unfortunately I cannot test it as it boot-loops.
Tried all my tricks but no good
Gone back to Havoc 3.6
Latest POSP Croquette v3.2.0-hotfix+16 loads but no FM radio so no good to me
Back to Havoc 3.6(Android 10)/ AOSP_PIZZA Android 9 May version
July 2020 Havoc 3.7 released by Chil360.
Installed clean and running well
The Havoc 3.7 July 2020 release by Chil360 IMO is the best and most stable custom rom I've tested for Moto g3 2015 (osprey) and is highly customizable. I especially like the "smart battery charger" feature which allows the charger to be set at a maximum percentage in my case 92%. I have not found any other custom rom with this feature. This will help prolong the battery life by not charging it to 100% every time. The July 2020 release installed fine and is running with no apparent problems. I tried the latest "official" lineageos version July 3 2020 but had problems with random spontaneous reboots.
THESE COOKED ROMS ASSUME YOU HAVE ALREADY AN UNLOCKED BOOTLOADER AND TWRP AS RECOVERY SYSTEM. You can flash them using TWRP, after wiping ART, cache, data, boot and system partitions.
FINAL RELEASE: Well... this is the final release from me and it is specifically for the WiFi model. I hope it is worth it for you. It is more stable and somewhat updated, anyway, if you use a X90F (wifi model) you will probably like it. The other versions are still up for whatever reason. Here's the link. Follow this guide by @Quardah if you are coming from a factory ROM. Go to post 46 if you can't get past the setup wizard. A barely tested (by @Nuihc88) version for the 3G (X90L) model can be found here.
NOTICE: If you find this work useful, mirror it. I won't be hosting it for free forever and it is becoming a burden to my Nextcloud installation. One would say this is a pretty much forgotten thread, but I'm seeing almost daily download activity. I'm putting the ROM files offline now and getting away from XDA for a while. Please don't DM me for the files. If you are looking for them, ask others in this thread. Good bye.
||||||||||||||||||| FROM HERE IS JUST INFORMATION YOU PROBABLY DON'T NEED |||||||||||||||||||
Spoiler: NEWS THAT ARE NOT ANYMORE.
APRIL 9, 2021: You can find in these links a new version of the cooked ROM.
The link for the updated cooked ROM is: https://centsoarer.ddns.net/s/Y8o3eoBK4Ryx5RP. This is a version with GAPPS updated: https://centsoarer.ddns.net/s/FPKjgQcmW3CHZCw. Feel free to mirror, unless you are afraid of Lenovo's lawyers, but don't forget to share the link.
My personal version... even more debloated (if you don't need chinese, japanese, korean, or russian input support/apps) and with CPU tweaks for my own usage: https://centsoarer.ddns.net/s/jcCDAgNedryGRjo
KNOWN ISSUES AND SOLUTIONS:
1) One random reboot after the first boot will happen and it is normal.
2) I'd reccommend to stay with Magisk 21.4 for a while, Magisk Manager >21.4 won't manage your extensions.
3) If you can't get past the initial Setup Wizard check post 46. Basically you have to boot into bootloader, erase the config partition and format it again.
4) Needs confirmation, but versions with signature spoofing patches seem to break Lenovo's SmartSide Bar.
JUNE 12: Fast update on the Cooked ROM and TWRP and KERNEL. They are not as universal as I implied before. Proceed carefully since they may not work four your device/firmware. Make a Nandroid backup and only flash with testing purposes.
JUNE 5: So, I know this is not what everybody who owns this tablet wants to have (that is Android 9 or 10 of course) but, in recent weeks Lenovo updated the firmware of this tablets. It still is a Marshmallow one and it still sucks big time but I took it as a base and cooked it to deliver a newer TWRP recovery with compression, a flashable modified kernel and a cooked flashable stock ROM to free the owners of this tablets from the treacherous path of making this hardware to work properly. If you want a better overall experience and are in stock firmware you just need to Unlock your bootloader, flash TWRP, Format data partition (not only wipe), Wipe Cache, Dalvik/ART, System and DATA and flash the Cooked ROM to put this tablet in a sweeter spot. For details go to post #2!
JUNE 3: Been trying to get to know some of the source code available for Cherry Trail devices and I am fairly lost at building TWRP from source. Anyway, I ported a newer TWRP recovery IMG file for the YT3-X90F (maybe L, X, Y and Z) from the TWRP image for the Chuwi Hi10 Pro tablet from here, using AIK-Linux. The result is in the second post labeled as beta, since I only tested in the YT3-X90F model, running lollipop firmware. So far, it works fine flashing ZIP archives, backing up and restoring backups. Advantages? Well, backups are way lighter if you enable compression (like half the size), higher resolution, twrp turns off the screen with a timeout and whatever made them bump from version 2 to 3. While I could port a newer TWRP version, I just wanted to have lighter backups with compression... so maybe it is what it is .
ORIGINAL POST STARTS HERE. This is general information that I collected for geeks or desperate users that bricked their tablets. When I started this post it wasn't intended to produce a cooked ROM that would include most of these hacks. You don't need this if your tablet boots to Android or TWRP. You also don't need this if you are ready to flash the cooked ROM.
(This is a lenghty post. I suggest you to navigate by section header and find the one you might need.)
There are several Lenovo Yoga 3 tablet models out there and, while some of them enjoy of prime community support as the Yoga Tab 3 Plus, this Intel Atom powered tablet is pretty much forgotten and, at the same time, users were recently buying this tablet, which is a great piece of hardware but has the most terrible support by Lenovo.
Spoiler: WHAT LENOVO TABLET(S) IS THIS GUIDE FOR?
Basically, this is that Lenovo tablet with an attached projector and an Intel Atom Cherry Trail x5 Z8500. There are several models, though, to my knowledge they vary in their code names in the last letter, the two most basic ones (2GB RAM, 32 GB ROM) are the YT3-X90F and the YT3-X90L, the former connects to the internet by WiFi and the latter being the one with LTE/Phone capabilities. There are other models, though, and they vary on the amount of RAM and internal storage. Apparently, the YT3-X90[YX] models (the 4/64 GB refresh) have some use for these firmwares we describe, but in a very specific way, if you own a Y or X model, keep reading, especially the next section.
Spoiler: EXPLAINING HOW TO FIND THE RIGHT STOCK FIRMWARE
Lenovo support has been terrible (there are no words to describe it, really), so they launched this tablet with Android 5.1 Lollipop and they maintained it for a while but were very slow to deliver Android 6.0 Marshmallow. In fact, there was already Android Nougat, when they sent the Marshmallow update. Nevertheless, the update was bad. Performance issues were always a thing and some functionality went lost in the update (less intuitive multiple windows, a crippled recents activity/screen, and a laggy overall experience). Bottom line, they launched a curated Android Lollipop 5.1 firmware with security updates until March 2016 (striked because the last lollipop update f*cks up my sensors, except the light one) and a half-assed Android Marshmallow 6.0.1 firmware.
Of course, at the time, I'm guessing most of us upgraded to Android Marshmallow 6.0.1, hoping the upgrade would fix the issues in Lollipop or with security patches in mind. The reality was that Android 6.0.1 wasn't nearly as maintained as 5.1 and security ambitions went nowhere. So, we got the upgrade all right, but at this point, both Android versions can be considered inherently insecure and we really shouldn't be using it for sensitive work.
OK, there are several Android 5.1 and 6.0 firmwares, you can recognize them because they are all over the internet typically in a compressed format. For example, this firmware hosted in androidhost.ru named:
YT3-X90F_ENG_S100265_1601281130_WW24_ROW
Is a firmware for the Lenovo Yoga Tab 3 (YT3) Pro (X90) Wifi Version (F). The ENG part is an indication of the build type, ENG is an engineer build while USR is probably a firmware for the end user (this is common now that I know a bit more about AOSP source code), it is a Lollipop firmware (S1, Marshmallow would be a S2) with update version (00265), date of compilation and a good estimate of its security patch (1601281130), the WW24 is the weekly release version of the Android kernel for Intel devices (the latest, in May 2020, being WW31 which is exactly the same as WW28 and not updated since 2016), the final part means it is the global ROM version (ROW, opossed to the Chinese version CN). This is the latest Lollipop firmware I am aware of, so, as an example, an imaginary Android Marshmallow Chinese firmware for the LTE version of the Yoga Tab 3 would look like:
YT3-X90L_USR_S200013_1610141535_WW24_CN
As an additional note the Chinese ROMS, I presume, are not trusty but they are also Google-free for what it's worth. On the other hand, they ship with a "Lenovo Services Framework" that should be as intrusive as the Google Play Services. Oh, also, baidu and yandex, and, really, any less traditional search engine can help you find a fitting firmware.
Spoiler: EXPLAINING HOW TO FLASH A STOCK FIRMWARE (DOWNGRADE TO LOLLIPOP AND UNBRICK)
I did test several firmwares, chinese and global, lollipop and marshmallow and the safest and easiest way to flash them is by using the Intel Platform Flash Tool Lite . I can't say I trust in this site, but it hosts a handy tutorial on how to use it, though, is pretty intuitive. The software exists for Mac, Windows and Linux, be sure you are in, at least, the 5.8.x version, this is important to avoid the need to install some special drivers separately as a pre-requisite. Grossly, Intel Flash Tool Lite works like this:
0) Turn off your tablet if it is on.
1) Launch Intel Platform Flash Tool Lite.
2) If your downloaded firmware is in zip format load it with the blue "Browse..." button.
2 bis) OR, if your firmware is in other compressed formats, uncompress it first. After this use the "Browse..." button to load the "flash.json" file.
3) In Configuration option select "blank" if it isn't set already. Optionally, un-tick the "On-demand flash" option to have more control of this process. Also, maybe you can use the "erase" configuration here.
4) Start your tablet in DNX mode. To do this, press Vol- and hold it, then Vol+ and keep holding both, then press the Power button until it turns on and you see the Lenovo logo and some text indicating you are in said mode.
5) Connect your Yoga Tablet with a USB cable and your Intel Platform Flash Tool Lite windows should show it as detected. Now you can proceed using the blue "Start to flash" button.
6) Keep an eye on your tablet, since some firmwares will prompt to set some more options. Unless you know what you are doing, answer "Yes" to any question.
7) Reboot and wait.
If a couple hours have passed and the tablet hasn't booted, maybe you should try another firmware.
IMPORTANT NOTE AND INSTRUCTIONS FOR YT3-X90Y AND POTENTIALLY YT3-X90X USERS: I don't know the rules in xda about linking to other forums but in certain forum there is an answered question about the Y model (the 4/64 GB WiFi only refresh) on how to flash a firmware. Instructions are the same as I gave in this section, except, apparently, you need to do it twice, first with the ENG version and the second time with the USR version except you are not using the flash.json file, this time you'll browse for the flash_factory_1st_stage.json one and the factory1st configuration in fastboot. It is not clear what are the consequences of not doing it this way or what if you combine different firmware versions (it would be interesting to have a tester here). Notice please, these firmwares are marked for the YT3-X90F model. So, clarifying:
1) Follow the instructions above to flash the YT3-X90F_ENG firmware.
2) Power off your tablet.
3) Boot into bootloader (not in DNX, you need to boot into bootloader by powering on while holding Vol+).
4) From the YT3-X90F_USR firmware folder use Intel Platform Flashing Tool Lite to load the flash_factory_1st_stage.json and select the factory1st configuration.
5) After flashing the USR firmware, reboot and you should be good to go.
METANOTE: This wasn't tested by me, please do this only when you are hopeless with your hardware. This is just an educated guess but I bet it works the same with the YT3-X90L (the LTE version 2/32 GB Yoga Tab 3 Pro) and the YT3-X90X (the 4/64 GB refresh).
ALTERNATIVE WAY TO FLASH A STOCK FIRMWARE (ADVANCED USERS, requires fastboot)
Well, there is no need, really, to use that Intel tool. In my search for a lollipop firmware (I wanted to downgrade from Marshmallow) I found the firmware YT3-X90F_USR_S100195_1512052308_WW24_ROW in www.firmware247.com or www.androidfilehost.com (IMPORTANT: please read the note on downgrading to Android 5.1 Lollipop in the note at the end of this section). This firmware was special since, if you are in Windows and have fastboot executable ready and in place, you can run a script (run_me.bat) in the Windows terminal (CMD) or Powershell to flash the firmware semi-automatically. I think this firmware was modified, though, since I found differences in the boot.img when compared with stock firmwares. This script is credited to XDA members @ionioni and @joesnose and you can replicate its steps if you:
0) Turn off your tablet if it is on.
1) Start your tablet in DNX mode. To do this, press Vol- and hold it, then Vol+ and keep holding both, then press the Power button until it turns on and you see the Lenovo logo and some text indicating you are in said mode.
2) Connect your tablet to your fastboot enabled PC using a USB cable.
3) Input "fastboot flash osloader loader.efi"
4) Wait 5 seconds to be sure the loader flash finishes.
5) Reboot into Bootloader. If you don't know how, one way is to hold Vol+ and Power on your tablet.
6) Input "fastboot oem unlock" and confirm using Vol keys to select the right option and the Power button to enter it.
7) Input "fastboot flash system system.img"
8) Input "fastboot flash boot boot.img"
9) Input "fastboot flash recovery recovery.img"
10) Input "fastboot flash bootloader bootloader.img"
Follow your instincts, since I don't know if these IMG files are always named the same. You can get these IMG files from downloaded sources or dump them yourself using dd command.
NOTE ON DOWNGRADING TO ANDROID LOLLIPOP 5.1: So, one of my main concerns has been to go back to Android Lollipop. There is a last version of Lollipop from where you can upgrade to Marshmallow with a security patch from March 2016. Nevertheless, you MAY end up loosing other sensors except the light one. If this happens, you need to use a complete firmware flash using Intel Platform Flash Tool Lite. In my experience, some boot images are not compatible with other weird partitions like country or misc.
Spoiler: TWEAKS ALREADY IN THE COOKED ROM
The first boot takes some time even amounting for the time of the setup itself. By the time you are in the launcher tapping on app's icons you think there's nothing wrong with our device, but after some apps are in memory, you notice some lag. You think "OK, it is updating, but soon it'll settle", but it does not. So, you reboot again after updates and fire up a terminal emulator and connect to your tablet using a USB cable with USB debugging turned on and issue a free command to find something like this:
Code:
total used free shared buffers
Mem: 1950372 1820964 129408 0 7756
Swap: 524284 10740 513544
Total: 2474656 1831704 642952
Which means you have a total of ~2.5 GB (this is the 2 GB model). So, did I download that extra half GB of RAM or Lenovo was feeling generous? Well, no. The issue here is Lenovo built the kernel with zRAM support which is a technology included in Linux that reserves space in RAM to quickly compress and uncompress pages of data exceeding our physical amount of RAM installed (2 GB). This is not Virtual Memory as in a swap file/partition or Windows' Page File inside storage media. zRAM literally reserves a fixed amount of physical RAM space (blocks) to expand it by compressing data. The consequence is you loose "fast RAM" (THE RAM) and gain some "slow RAM" (the zRAM). You also sacrifice some CPU power to compress/decompress data and, with this, some battery juice is also lost.
That does not sound like a terrible trade-off for a RAM-limited device, one would think. Another interesting thing would be WHEN to send this piling data in "fast RAM" to the compressed space and WHEN to get it back. Two parameters control the WHENS, one is called "swappiness" (when to send it to the compressed space, the "slow RAM") and the other may be the "vfs_cache_pressure" (when to uncompress it and send it back to the "fast RAM"). And this is where the main problem is, really, because the kernel, Linux, is pressing the RAM constantly to send some less prioritary data to "slow RAM" and, at the same time, is trying constantly to send compressed data back to the "fast RAM". Summarizing, this kernel behavior is practically minimizing the fast RAM amount and usage while maximizing the "slow RAM" usage. This is nuts, by default a swappiness and a vfs_cache_pressure of 100 are not even default for servers, these parameters extremely prioritize that processes can get done no matter how slow they get, and they are even more nuts when Android is designed to work without swap space.
What that free command is telling us is the tablet is using the "slow RAM" even when we only just turned it on. Fortunately there are two ways to fix this problem: one is to completely disable zRAM, the other one is to use ZRAM a whole lot less by tweaking the swappiness and vfs_cache_pressure parameters. This can be easily done with the following sentences in a rooted tablet:
Code:
# echo 5 > /proc/sys/vm/swappiness
# echo 50 > echo 5 > /proc/sys/vm/vfs_cache_pressure
Or, to regain the whole fast RAM:
Code:
# swapoff /dev/block/zram*
One caveat of the first method, reducing swappiness, is there is still a lot of RAM (one quarter of the whole RAM in a 2 GB device) reserved as "slow RAM".
SOME ROMS DID NOT ENABLE KERNEL SAMEPAGE MERGING, UNFORTUNATELY
Additional to the sorry implementation of zRAM, some firmwares support a fabulous Linux tool to reduce RAM usage called Kernel Samepage Merging (KSM) but they don't use it by default. This software runs at kernel level, so, it really is CPU-wise inexpensive and, opposite to zRAM it can actually recover some RAM usage by reducing the amount of data flagged as redundant in physical RAM by merging it. KSM is good for you and you should have it always enabled by issuing the following command as root:
Code:
# echo 1 > /sys/kernel/mm/ksm/run
STOP WRITING AND FIX MY RAM! PLEASE!
Well... are there any people interested on this? With the above information you can write a script to execute at boot. Something like this should work in any version of the firmware:
Code:
#!/system/bin/sh
# Mount system as rw
busybox mount -o remount,rw -t auto /system
# Tweaking swappiness in zram
echo "5" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
# Activating Kernel Samepage Merging
echo 1 > /sys/kernel/mm/ksm/run
# Remount system as ro. noatime option for faster and volatile system
# busybox mount -o ro,remount,noatime /system
busybox mount -o ro,remount /system
exit 1
Or, you can unpack the boot.img and modify the init.cht_ffd.rc (lollipop) or the init.r2_cht_ffd.rc (marshmallow) files to write these values as default... or, if there is interest for something easier, I can produce this boot.img files for you to flash using fastboot.
ROOTING THE LENOVO YOGA TAB 3 PRO (YT3-X90[FL])
Here I am not gonna write a lot. Instructions were given in this thread. I'd only recommend to put vm.targetutilization at 0.8 top 0.85 in system/build.prop
After rooting, debloat your firmware. I use the app "/system/app mover" from Fdroid to convert to user apps and uninstall them. Also, if rooting is not your cup of tea, you can install AppOps software to freeze all those apps that you don't use regularly. Also, I couldn't patch my services.jar for Signature Spoofing with Nanodroid patcher in the most recent lollipop firmware, but it did work in Marshmallow... anyway I'll do it manually.
ARE YT3-X90F AND YT3-X90L FIRMWARES INTERCHANGEABLE?
I own a WiFi only device (YT3-X90F) so I can't assert they are interchangeable. If I owned the LTE version and use a WiFi firmware I would expect to loose LTE functionality. Now, on the other direction is more interesting because I've been using a LTE firmware version for weeks (as a matter of fact, the one joesnose linked in his How-To debrick this tablet, flashed with the instructions I posted for advanced users it even updated to recent 2020 firmwares). The only tweak you need for this to work well is to add "ro.ril.disable=1" in the build.prop file. So, yes, firmware for the LTE version work in the WiFi version but kind of not vice versa.
Spoiler: YT3-X90(FL) UN-DEVELOPMENT
No news here. All capable people interested on developing for this device are all done with Lenovo and their attitude against Open Source. Don't expect your situation to change.
I'm happy to know there are still a couple of developers interested on this device. I won't cite them by linking their names but they are OOEvil and alquez, the first guy is trying to make a Generic System Image (GSI) ROM compatible with our tablet, I don't know the details so I wouldn't go further. Alquez has been active in this thread and, while he is trying to figure out how to build a kernel, he believes the best way to start having some alternative to official Lenovo firmware is by using a firmware kernel (a prebuilt kernel) to, first, build a more up-to-date TWRP recovery.img and from there try to build CyanogenMod 13, which was based on Android Marshmallow 6.0.1. My guess is newer Android versions wouldn't work if we can't build the kernel from source.
PHOTO ALBUM OF YT3/X90Y BIOS
This photo album documenting every screen option in the BIOS of the Yoga Tab 3 Pro may or may not help someone, but it contains a lot of useful hardware information and guidance for those attempting to boot something else than the original Android 5 or 6 firmware. Using this options, that are accessible through F2 at boot with an attached USB keyboard, you could try Linux distributions on the tablet or even attempt to run Windows, @alquez informs it works fine with a recent distro but the mainline kernel is lacking touchscreen and battery support. This is absolutely his work and he asked me to share it. I hope it serves someone. It is hosted in a rather obscure website but it was the only reasonable placeholder I could find for the 321 photos.
Hope this helps someone, I just didn't want to keep it to myself. Have a nice day!
Just remember, if your tablet is 3G capable I strongly suggest that you modify the line "ro.lenovo.tablet=wifi" to "ro.lenovo.tablet=3gdata" and remove the line "ro.radio.noril=true" to your build.prop file in /system. To do this you can use the section Build.prop Editor of the Kernel Adiutor app or you can do it manually if you have already a method to modify system files. If you do not use mobile data at all, you may leave the build.prop as it is, you'll save a lot of battery by using only wifi.
Spoiler: Some old info here, but maybe useful
ONLY FOR TESTING: Cooked ROM, newer TWRP and tweaked kernel
ONLY TRY THESE FOR TESTING PURPOSES, THE TWEAKS ARE ALL SAFE TO USE BUT ONLY FLASH FOR TESTING PURPOSES, PLEASE. FIRST, TRY TO USE FASTBOOT TO BOOT THE boot.img FILE WITHOUT FLASHING: IF IT BOOTS GO AHEAD AND TRY THE OTHER FILES (fastboot boot boot.img). THE TWRP IS NOT AS STABLE AS THE OTHER ONE HERE AT XDA BUT ALLOWS TO USE ZIP COMPRESSION IN BACKUPS. I AM NOT GONNA BE AROUND. IF YOU TRY SOMETHING MAKE A BACKUP FIRST. THIS DEVICE IS MESSY AS F*CK.
Spoiler: Some old info here, but maybe useful
I wrote a very detailed guide about these files I uploaded to my Nextcloud that include the newer TWRP-3.0.2, a TWRP flashable Cooked ROM and a separate kernel (boot.img) in case your system is already setup, but the post went to some XDA void and didn't upload. These are based on the YT3-X90L latest firmware, but they work on the X90F model too. The TWRP should work with Lollipop and Marshmallow firmwares.
I can't write everything again, so, the kernel contains better management of RAM and emmc (internal) memory, a 256 MB zRAM space instead of 512 and a more conservative approach to LowMemoryKiller.
The cooked ROM includes the described kernel and debloated apps, it's already rooted with Magisk (you can unroot with Magisk Uninstaller), an updated Busybox build, su.d support (I plan to use it with AFWall+), zipaligned apps, etc. It is for the X90L but possibly works for the other Yoga Tab 3 Pro models. It works for the X90F but it will reboot once after the first boot because the RIL configuration times out. To install the cooked ROM you need to:
0) Know that by doing this you will loose pretty much everything in your tablet. You start from scratch if everything goes smooth, if not you could possibly end up with a system without an OS. The usual stuff when you are customizing your system.
1) Boot into TWRP and make a Nandroid backup. IT IS IMPORTANT because @joesnose had problems with a "random reboot" and lost Bluetooth/WiFi after it. I am trying to look into this. The only difference is his tablet has 4 GB RAM and probably a different firmware.
2) Wipe cache, Dalvik/ART, System and Data in TWRP - Wipe, Advanced Wipe menu. If your tablet is encrypted, or in factory firmware you also need to explicitly use the button "Format Data partition" and confirm writing "yes" in the format procedure prompt. You will loose any configuration made to your tablet.
3) Install the superr_stockMM.zip wich is flashable by selecting the file from your Internal tablet memory, using the Install button in the main TWRP interface.
FOUR IMPORTANT NOTES TO COMMON ISSUES:
If you come from a stock firmware your data partition is encrypted. You need to pass a blank password in TWRP to continue to use the custom recovery. You also need to format data partition before flashing the cooked ROM.
If your tablet is WiFi-only I strongly suggest that you modify the line "ro.lenovo.tablet=3gdata" to "ro.lenovo.tablet=wifi" and add the line "ro.radio.noril=true" to your build.prop file in /system. To do this you can use the section Build.prop Editor of the Kernel Adiutor app or you can do it manually if you have already a method to modify system files. In Lollipop firmware you use "ro.ril.disable=1" instead of "ro.radio.noril=true" to get the same effect: sort of a conversion to WIFI-only tablet from LTE models. I'd argue this is useful to do if you are gonna be without LTE connection/service for long periods of time and I can think a couple of other uses.
Do not use stock Lenovo launcher unless you uninstall Magisk... they are incompatible for reasons I don't care to know and the Launcher will constantly FC (it is a pain in the arse).
If you are still expecting better performance I am sure there are some tweaks left in RAM management but it wont go too much further in 2 GB devices. Instead, you may consider to lower your display resolution and pixel density to something reasonable as 1400x2240 or even 1200x1920 maintaining the same aspect ratio. To do this you do not need to have root but you need to interact with the tablet using ADB. First change the size of your display:
Code:
adb shell wm size 1400x2240
Then adjust your density:
Code:
adb shell wm density 260
If still is not enough you can go even further with 1200x1920 and 224, use the same method to go back to stock with 1600x2560 and 300 to 302. This won't need a reboot but will probably cause an inconsistent UI that will lead to FCs and random reboot. You can just reboot after applying these tweaks. Unless you are really sight-gifted you won't notice a lot has changed but you will be dealing with 2.x Mpixels instead of 4.x Mpixels and that will help with your overall performance as well as your battery life sacrificing a pixel count that most of the people wouldn't even notice. If you did this correctly, in the next boot sequences you'll notice an offset on the Lenovo orange logo.
It is important to say that your display supports 1600x2560 pixels physically, but I'm assuming the GPU has no dedicated RAM and uses the device's, so, by reducing the quantity of pixels the GPU needs to deal with, the pressure on the device's RAM is also reduced.
EXTRA TIP: If boot annoys you just delete /system/media/boot.wav, bootanimation.zip and shutdownanimation.zip and you'll get a silent boot and the generic android boot animation.
Hope you enjoy your tablet!
TWRP-3.0.2.0- BETA: Again, this is not a flashable zip. Uncompress first and test the recovery system using "fastboot boot twrp_yt3-x90f_beta.img". If everything works for you, you may want to flash it permanently rebooting to bootloader and flashing with "fastboot flash recovery twrp_yt3-x90f_beta.img". Remember I did not test this in Marshmallow yet.
FEATURES:
- Fixed RAM issues (swapiness 10, vfs_cache_size 50 and disabled dynamic low memory killer tweaks and minfree values).
- Reduced zRAM size to only 256 MB.
- Tweaked interactive CPU scheduler to use other than min and max frequencies (but still responsive). The tweaks are based on the Advanced Interactive Governor Tweaks Guide. This may save battery life.
- Max frequency capped to 2.08 GHz (this is not great if you are a gamer). This tablet throttles when using max frequency for a long time, so, to save battery and keep it cooler I tweaked the CPU to run slower.
- Tweaked I/O schedulers to use deadline governor and read ahead cache to 640 kb (used benchmarks to get to this value).
- Force encryption disabled (to avoid applying ionioni script after flashing). Still needs to format data partition. You can encrypt your data partition later through Configuration -> Security user interface.
- Implemented native init.d support (not su.d anymore and no need to root the main OS).
- Busybox updated.
- Rooted with Magisk by default ( you can use Magisk uninstaller to unroot).
- Debloated apps. I also deleted Lenovo User Experience Program which was asking for root privileges even when you don't opt in to the Lenovo UE Program at setup wizard. I find this behavior shady.
-Multi-window mode is available in Developer Options and needs to be activated by you. In this mode if an app is compatible with multi-window mode you can double-tap on its title bar to enable Window mode. This function was more transparent in Lollipop firmware but it is still there in Marshmallow firmware if you change the build type to userdebug instead of user in build.prop (that's how I enabled it in the Cooked ROM).
- There are also other tweaks in VM and KSM.
And that's it, I'm not trying to change a lot, only the fundamental issues. But I suggest some other tweaks up there.
Such a shame. I love my Yoga Tab 3 Pro. Great hardware. But the software. Thanx anyway for your work.
Very nice write up. Thanks.
joesnose said:
Very nice write up. Thanks.
Click to expand...
Click to collapse
You're welcome. Thanks to you, while learning about this hardware your username pops everywhere.
jahfaby said:
Such a shame. I love my Yoga Tab 3 Pro. Great hardware. But the software. Thanx anyway for your work.
Click to expand...
Click to collapse
It really, really sucks. Let's hope something interesting happens after these strange and recent updates.
CENTSOARER said:
V1: The zip name boot_mod_mm.zip is based on the latest boot IMG provided by Lenovo. You need to first uncompress and flash it using fastboot (this is not a TWRP flshable zip). If you are uncomfortable flashing, you can test it only by issuing "fastboot boot boot_mm_march20_mod.img" once uncompressed, or, if you feel fine using it you can flash it permanently by using the command "fastboot flash boot boot_mm_march20_mod.img". This boot IMG will only work with Marshmallow firmwares in both YT3-X90(FL).
FEATURES:
- Fixed RAM issues (swapiness, vfs_cache_size and low memory killer tweaks).
- Reduced zRAM size to only 128 MB.
- Tweaked interactive CPU scheduler to use other than min and max frequencies (but still responsive). This saves battery life.
- Max frequency capped to 2.08 GHz (this is not great if you are a gamer). This tablet throttles when using max frequency for a long time, so, to save battery and keep it cooler I tweaked the CPU to run slower.
- Tweaked I/O schedulers to use deadline governor.
- Force encryption disabled (it's unnecesary to apply ionioni script now). Still needs to format data partition. You can encrypt your data partition later through Configuration->Security user interface.
Click to expand...
Click to collapse
Thanks for this. Going to take it for a spin.
joesnose said:
Thanks for this. Going to take it for a spin.
Click to expand...
Click to collapse
Please, please provide feedback and don't forget to wipe caches.
alquez said:
"No news here. All capable people interested on developing for this device are all done with Lenovo and their attitude against Open Source. Don't expect your situation to change."
https://github.com/intel/ProductionKernelQuilts this repository containts patches necessary to create base 3.14.55 and 3.14.64 uefi/cht-m1stable kernel tree. The same tree that was butchered by Lenovo in their OPEN_SOURCE "release".
Check this file https://github.com/intel/ProductionKernelQuilts/blob/master/uefi/cht-m1stable/ChangeReport.md and the WW24 part in the "YT3-X90F_ENG_S100265_1601281130_WW24_ROW" will become more clear
Quilt manual: https://elinux.org/images/7/74/Maintaining_Multiple_Android_Linux_Kernels_at_Intel.pdf
If someone would be looking for a good piece to start: the best would be to recreate 3.14.55 or 3.14.64 from the quilts, use the x86_64 defconfig and build a kernel which can be booted. In order to test this, the best solution is to repack TWRP with the new kernel and do "fastboot boot" without flashing, until it boots and the touch screen is working. There's no other way i'm afraid.
I have prepared complete photo documentation of UEFI Bios, i can share, currently moving to different google photos account. Its over 300 photos.
Please, set up a Discord channel if you want to proceed. The first month will be quite boring and daunting because it's going to be build -> repack -> boot -> rant
Click to expand...
Click to collapse
In my defense, when I wrote that sentence was after taking a peek on your github profile, I figured you were just done with the Yoga Tab 3 Pro. I am really, really glad you're still trying and I recognize you are very capable of changing things for this device. I appreciate the sources you link but I am afraid I am useless as a developer, partly because of a lack of time and partly because of a lack of adequate training. I will try to help as much as I can, though. Thanks for the post.
alquez said:
No worries, however if anyone is interested how to actually crunch this one: we have a working prebuild kernel which can be pulled of boot image, and we have a working TWRP, however it looks like TWRP wasn't actually built from source, but cooked using android kitchen so we're still missing a device tree, which in my opinion is a good place to start, because you can use prebuilt kernel to build recovery and lineageos/aosp (it's deprecated but we're talking about android 6 aka cm-13.0/lineage 13.0). If I can create a most basic device tree which is capable of building recovery from scratch useing binary kernel and modules, i'd say were' good, because the next part would be adding more binary blobs from the official software, and we can skip the kernel source part for now until we have lineageos build 13 working). I started experimenting on xiaomi latte tree because it wasnt split like Z00A. It's not gonna be a proper port but it should work from now (i think)
@joesnose did you cook or compile TWRP? It's important
Ok, I'm at the stage i have two folders. The one is unpacked working TWRP, the other one is unpacked compilation i'm building, which means im able to build TWRP from source with binary kernel, but it's not working yet. The goal is make the left one look like the right one by adjusting various parts in BoardConfig.mk and copying files.. If someone has right partition sizes for BoardConfig.mk that would be really helpful, the values i calculated suck and don'y boot yet
Click to expand...
Click to collapse
Uhmmm, I've been there and took some notes with some "GNU shell Fu". What sizes are you using right now?
And regarding the WW part of the name I've noticed the recent updates are marked as WW17 opposed to WW28 which was the latest stable with any changes. Any idea why Lenovo used WW17 to update the Yoga Tab 3 Pro recently?
alquez said:
update, ive managed to boot vanilla android-x86 x64 6.0.1 build without touching the kernel yet and different TWRP (3.1.1.0) with kernel swap
Click to expand...
Click to collapse
Geez, I was excited because I read Ubuntu booted on this hardware but then I realized it was the Yoga 3 tablet but not the Yoga Tab 3, goddamnit. Keep up the good work!
alquez said:
Um Ubuntu 20.04 boots with working accelerometer so the screen rotation works + wifi, and probably audio i forgot to play youtube video, the stuff missing is battery, touchscreen and projector.
To test it you need to connect a usb hub using usb otg, put ubuntu and a keyboard in the hub, boot, and press f2 really fast if you haven't enabled slow boot yet. You can even boot
Xubuntu to ram and remove flash drive. It's a pc architecture after all and most of the processor related stuff is in the linux mainline since 4.11
Recently i was checking why the Windows 10 installer crashes on ACPI Error.
Click to expand...
Click to collapse
Oh, I will have fun doing this kind of stuff at the end of the year. It must run swiftly with i3, provided you won't get touchscreen support.
alquez said:
Geting TS and a battery running is a mandatory, the next is the projector. The rest is pretty much working. I'm building generic celadon x86 atm and the beast is huge it's like 18% now after two hours on -j8 on i7. Maybe we can give this old monster a new life
edit:
And i need to add 480gb drive ;/
Code:
/dev/sdc1 229G 210G 6,7G 97% /home/android
Click to expand...
Click to collapse
I am afraid those are the peripherals that will keep you in 3.14.55/64 Linux, at least for a while , unless you know something more (wouldn't be surprised).
Are those GB for source code or for cache? Both? Jesus... the thing is huge but reading the unpacked boot.img makes much more sense now.
It was ionioni who made the twrp for the device. I dont have the foggiest how he did it.
---------- Post added at 01:23 AM ---------- Previous post was at 01:18 AM ----------
Wow! I missed lot, looks like you have made some serious progress here. very well done.
alquez said:
I contacted my friend and he told me to compare these two folders:
https://github.com/alquez/lenovo_yt...l/cht/arch/x86/platform/intel-mid/device_libs
https://github.com/torvalds/linux/tree/master/arch/x86/platform/intel-mid/device_libs
the new files in "lenovo tree" are the modules we're after, mostly and it's a place to start
I need to ask inioni about twrp.
Click to expand...
Click to collapse
I will guess it was ported from the Yoga Tab 2. I will edit this post soon.
alquez said:
Nice! There's big chance the modules are reused somewhere. We can compare these. I think the two folders in
https://github.com/alquez/lenovo_yt3_x90_osc/tree/master/kernel/cht/drivers/input/touchscreen
which are missing from vanilla tree are two separate drivers and one is for "any pen" driver. Can you ask someone porting modules recently
to help us refresh my memory
[edit]
I've got in touch with TeamBliss of BlissRoms , they are working on cherrytrail tree
Click to expand...
Click to collapse
Nah, I couldn't confirm it was ported. A lot of posts were removed when XDA enforced the GPL measures to its developers.
About BlissRoms, it just makes sense they are working on Cherry trail. I hope you and those guys can achieve something soon. I mean, it's a 2 GB RAM device but the display, projector and dolby audio system are worth for a better fate than Lenovo's plans.
alquez said:
4GB of ram 4 cpu cores, Hardware virtualization support, fast gpu and fast emmc memory. It's a beast, way ahead of it's time.
Click to expand...
Click to collapse
Well, I have the 2 GB RAM model, so my expectations are conservative. Anyway, don't believe I'm a hardcore user, so it's plenty enough for me, considering I won't even flash Google apps. I am now settled with Lollipop, since I need apps not getting killed by damn Doze. It is a shame how OEMs can limit a device like this one. Crond, init.d, bad zRAM, shell, even busybox... frequently the OS is crippled. I read somewhere Doze can be disabled in build.prop or something but one thing I just hate is the recents screen in Marshmallow firmware (my God, is terrible!) and can't be easily changed for something like OmniSwitch. I mean, for a mobile device you have an unusual architecture, why limit it further? Damn, I wish BlissRoms come up with a working build.
Hey, @alquez, have you tried Linux 5.7 on the tablet? I saw this article and seems like the touchscreen may work with the next mainline kernel release. I mean, right now is on RC7, should be stable enough to compile and try (I'd try it, but can't get to my workstations thanks to the virus).
EDIT: Ah... I was looking into my device and it comes with a HiDeep touchscreen (cat /dev/input/event3), the linked news is for the Goodix driver / devices. At least, I guess, it will attract others to this platform... anyway, I was wondering and also confused, shouldn't touch screen work with the hideep driver using this config already?
Thanks for the new feel.
This is great, glad to see a developer picking up this tablet. It's a fine machine with an unfortunately small user base and has never really seen any development apart from ionioni s efforts and he didn't even own one, lol.
Edit: *Thank for the new twrp * auto correct!
I love this device! For me it's the perfect device for vacation just because of the projector!
I am so happy that you guys are working on it again. the ram and display tweak works like a charme for me. Had to reset my background screen though
thx for all your help. As soon as you guys have light rom, i'll install it on my 2GB device.
hello how to flash your twrp please ?
can someone upload adb drivers for the yt3-x90f please ? because i try to flash in dnx fastboot mode but commands don't work, even "fastboot devices" don't show me the yoga tab 3 pro