{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Leagoo M8 is an entry level 5.7" Smartphone running on the MT6580A SOC with 2GB of RAM. Like many budget devices, the Leagoo M8 has decent hardware for the money, but suffers from a poor software experience and too much bloat. I created this project to share a more lightweight and clean software experience so we can get the most out of our device without too much effort
Important note! I am NOT a developer. Don't expect me to know how to recompile a kernel or anything. I'm just a lazy user who has been using Android for a while and much prefers a clean, AOSP-style look and feel There are a few technical issues which are outside of my reach, so if anyone is able to help, please feel free to reach out.
Disclaimer! I am not responsible for any damages you may do to yourself or your device by modifying your device!
What's Working:
- Everything, except some silly Leagoo features which I removed (eg. Supershot, screen recording).
Known issues:
Same issues as stock Freeme OS. Nothing serious and definitely OK as a daily driver, but the following annoy me the most. If anyone is able to suggest fixes, please comment below!
1. Onscreen Softkeys are misconfigured. I'd like to at least re-map the recents button back to recents, and change the long press of recents to menu. Recents should not be a menu button.... this may require recompiling SystemUI.apk (I think) which is out of my depth
2. The fingerprint sensor is silly. Sometimes it won't recognise my finger, despite me adding the same finger three times, and other times the fingerprint sensor is active when using it, and it will trigger some actions if I touch it by accident (eg. when using Chrome it will open the menu, and other time it will just vibrate the phone - strange).
3. Wi-Fi performance and 3G performance are low compared to other devices. Not sure if this can be fixed by software.
4. There are limited language options. I would like to see English (Australia) for example, but this is not a big deal
5. Considering replacing stock Phone and Contacts apps with Google equivalent from Play Store. Will test first.
6. At 10% battery a prompt will appear which asks whether you want to enable "superPowerSave mode" which is a really badly done version of Samsung's Ultra Power Saver mode, which I removed, so clicking OK does nothing. Would be nice to remove this prompt somehow.
Install Instructions:
Since I am lazy, I have just packaged it as a TWRP backup. Root is not included by default, but you can flash SuperSU in TWRP if you like.
1. Install TWRP 3.0.2 on your device via SPFlashTools (If you haven't done so already, download link provided)
2. Download ROM package, unpack archive, and copy contents to /sdcard of the device internal storage
3. Restore the TWRP backup. This will wipe /system, /data and /boot for you, so there is no need to factory reset.
4. Flash SuperSU package from "Extras" folder for Root access (optional)
5. Wipe internal storage to clear up internal storage (optional)
6. Reboot, wait at least 10 minutes for first boot - it takes a while
Downloads:
LM Debloated ROM Backup & Root Package: https://mega.nz/#!SR8iwByZ!k0w4nKzsQp0l02vuIWVIRsgIQGohC7Fvt5v99EriOiU
TWRP Recovery Install Package (if not already installed): https://mega.nz/#!7NlmVCrR!tR2NCZVFHJVueGCwWQvkHsfQxAiYLI4-SZRSngM0Lcc
Credits:
Leagoo for building FreemeOS for this device
XDA:DevDB Information
LM Debloated for Leagoo M8, ROM for all devices (see above for details)
Contributors
stephendt0
ROM OS Version: 6.0.x Marshmallow
Based On: FreemeOS
Version Information
Status: Testing
Created 2017-03-18
Last Updated 2017-03-18
Tips:
- You can enable hotspot tile in quick settings by toggling hotspot on and off once
- You can remove the non-functional tiles from quick settings by enabling SystemUI Tuner (hold settings button)
Changelog:
Version 1.0 (Based on 20161213 ROM)
Installed the following apps as system apps:
Nano OpenGapps (update all core Gapps packages)
Nova Launcher
Android Messages
Google Clock
Google Calculator
GBoard (Replacing Google Keyboard)
MK Explorer
Removed the following apps:
App Store (Not Play Store)
Bookmark Provider
Browser
Calculator
Calendar
Child Mode
com.freeme.theme.Lineart
com.freeme.theem.theme_colourful
Concentric circles
Clock
Dual Tag
Kika for LEAGOO
File Manager
Email
Music
Videos
Weather
Google Pinyin Input
Talkback
Locknow
Power Saver
FreeMe OS Lite
Com.freeme.motionrecognition
Com.freeme.theme.qindefault
Messages
Sound Recorded
GHBL 1.0 (Lock)
Cleantask 3.0.7
Search
Supershot
Screen Recorder
I was able to flash TWRP using the files you uploaded. Now I'm rooted. Thank you so much. More grease to your elbow.
donshady28 said:
I was able to flash TWRP using the files you uploaded. Now I'm rooted. Thank you so much. More grease to your elbow.
Click to expand...
Click to collapse
Glad to hear it, first time I've ever uploaded a ROM. :good: Feel free to use the thanks button and let me know how it goes for you!
Edit: If anyone is able to help out with the wish list, I'd be very appreciative!
Great work and congratulations on your first rom.
Did you run any benchmarks before and after? And how is ram consumption vs. stock?
Palm Trees said:
Great work and congratulations on your first rom.
Did you run any benchmarks before and after? And how is ram consumption vs. stock?
Click to expand...
Click to collapse
I can't say I tested much before and after (I couldn't stand the bloat lol), but it definitely feels a lot more responsive, and I am getting good battery life now - around 6hrs SOT today, few phone calls, but mostly messaging and reddit/facebook and a bit of book reading. I'm very happy so far. There are reviews where people were saying they were getting a lot less SOT than that, so I think it's an improvement.
Next thing I'll add to my wish list is to integrate the Google Dialer and Google Contacts app from the play store to replace the stock Android 6.0 apps, assuming that they work well during my testing on this device. They have a couple more features and being linked to the play store means that as Google adds more features and improves functionality, the ROM will automatically get those updates.
Thank you so much for your effort. You help many others
Update: Xposed works fine, and once I installed gravitybox I was able to remap the buttons with relative ease. More info here: https://forum.xda-developers.com/showthread.php?t=3034811
Edit: was getting some strange issues with Xposed so uninstalled it. For example, my recents key disappeared randomly after a reboot :/
I enjoy this lazy man ROM alot. I have enough juice to make my day. Thank you stephend. I'll advise you a to switch to this ROM.
Greetings.
SP Flash tool returns error 5054
galensbane said:
Greetings.
SP Flash tool returns error 5054
Click to expand...
Click to collapse
You need to retry. There's nothing wrong with the files.
donshady28 said:
You need to retry. There's nothing wrong with the files.
Click to expand...
Click to collapse
I've try many times, with or without battery, after plug in the status bar goes 100% red downloading and after 5 seconds gives the error.
In the proccess from scatter file i've checked only the recovery file is that correct?
Do you have your drivers properly installed??? If not, follow this link and download mtk driver
https://uploads.to/xfwv5rrz2zsx
donshady28 said:
Do you have your drivers properly installed??? If not, follow this link and download mtk driver
https://uploads.to/xfwv5rrz2zsx
Click to expand...
Click to collapse
Thanks for the link.
I've install the driver (both on x86 and x64 windows system).
Same error.
Do i have to check anything else except the recovery?
maybe preloader or dsp_bl??
Just the recovery.
You don't have to check any thing just the recovery okay. I don't understand what's going on with your phone. Use another computer.
donshady28 said:
You don't have to check any thing just the recovery okay. I don't understand what's going on with your phone. Use another computer.
Click to expand...
Click to collapse
Actually i did.
I've tried on win 10 x64 and win 7 x86 provided the drivers you gave me, same thing :S
Reinstall
Reinstall the driver. I used a Windows 7 to flash the recovery.
Try a Windows 7 pc okay
donshady28 said:
Reinstall the driver. I used a Windows 7 to flash the recovery.
Try a Windows 7 pc okay
Click to expand...
Click to collapse
I actually did it!
The problem was in the "how to" engage the process.
I was pressing both volume buttons and then plug in the phone in the computer.
It worked with just plug in the phone!
I did it on windows 10 x64
Thanks for all the help.
Phone is smooth, great work.
Enjoy.
Yes, mediatek phones are a bit funny, all you have to do is click download and then connect the device whilst it is powered off and it will just flash away, no button pressing needed.
I really would like to re-arrange these on-screen buttons though. Preferably on a system level by editing an XML file. Anyone know how to do this?
Edit: Also, has anyone lost vibration after flashing my deblotated ROM? I've just noticed my phone doesn't vibrate, but I think it might be hardware.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is free, community built, the distribution of aftermarket firmware Android 4.0 (Ice cream), which is designed to increase performance and reliability in the stock Android for your device.
Code:
# include <std_disclaimer.h>
/ *
*
* Not responsible for bricks devices, SD cards dead
* Thermonuclear war, or be fired because of the alarm application failed. Please
* Do some research, if you have any questions about the features included in this ROM
* Before flashing it! You are choosing to make these changes, and if
* You point the finger at me for spoiling the device, I will laugh at you.
* /
CyanogenMod is based on the Android Open Source Project with additional contributions from many people within the Android community. Can be used without any need for any Google software installed. Linked below is a package that has come from another Android project to restore parts of Google. CyanogenMod are still included various hardware-specific code, which is also gradually open source anyway.
All source code is available CyanogenMod Github repository CyanogenMod. And if you would like to contribute to CyanogenMod, please visit our Gerrit code review. You can also see the Changelog for a complete list of updates and features.
Instructions:
The first time you use CyanogenMod 9 on the device or from another ROM?
1-Install ClockworkMod recovery. The instructions are available in the second post .
2-Make a backup nandroid your current ROM. (in the Backup and recovery >> restore >> backup)
3-Format the partition of data and cache device. (in the recovery >> Wipe data / factory reset
4-CyanogenMod to flash (Install zip from sdcard, CM9-(fversion)-UNOFICIAL-pascal2.zip)
5-Optional: Install the Google Apps package addon. (Install zip from sdcard gapps-ics-20120429-signed.zip)
Upgrading from an earlier version of CyanogenMod 9
Make a backup nandroid your current ROM.
CyanogenMod flash (Google Apps will be a backup and restore automatically).
problems
Experience issues? Please provide the following information to our bug tracker:
If the device was difficult to start the system, please provide the file "/ proc / last_kmsg".
If the device was a soft reset, or "bootlooping", please run a Logcat and provide maximum power.
Please use Pastebin when possible.
Download Links:
CyanogenMod 9:
Latest version: 9_alpha [30/09]
Download: http://d-h.st/3Di/
GoogleApps (supplement):
*Version: gapps-ics-20120429
Mirror: http://goo.im/gapps/gapps-ics-20120429-signed.zip
Moldels tested:
Bq Pascal 2 (rk2918 7", 1gb ram)
Bq Kepler 2 (rk2918 8", 1gb ram)
Not working:
Minor faults:
Problems with overlay (wallpapper aspect, laucher, dimensions ...)
Not tested (HMDI)
Sensor work bad.
Changelog:
30/09/2012
-fix orientation camera
-Update sources
13/09/2012
-Fix vpu/ion
-fix camera
10/09/2012
-Fix rendering webgl (thanks to christiantroy)
30/06/2012
-Add recovery
-Remove incompatibility with install(ro.product)
-Add usb storage support.
-Rendering(Faults in web browser).
-Add own recovery in installer(non touch).
Installation Instructions for vurrut ClockworkMod recovery(non touch):
For Rktools (windows):
1-Download and extract the file on the desktop recovery_RKtool_winV2.zip.
2-Turn the tablet in any way jtag, (-) and insert the usb.
3-Run the RK29update.exe (should appear under "device connected", if not, repeat step 2)
4-Turn the tablet and turn into recovery mode ((-) and (power)).
Restore to the previous ROM:
1-Reboot in the Recovery.
2-Backup and Restore >> Restore.
3-You choose the date of restoration (if you miss several).
I need help from other developers
To build:
repo init -u git://github.com/CM9-Pascal2/android.git -b ics-release
repo sync
./builder.sh pascal2 img.
Things that has been made.
-Gpu
-Sensors.
-Audio.
-Custom releasedtools to build a package
-Create a builder to create custom img. How to use??--->README
Hi,
I have tried twice to make a CM9-build for my Newsmy P9 but none of my builds were succesful so i'am very glad that you succeeded. I'll help you developping the ROM (for Newsmy P9).
Nice to know: One member of our community ported the CWM-recovery to the RK2918 (gathering.tweakers.net/forum/list_messages/1475526) it's in dutch...
Biohax17
Finally!
Finally there is someone who tries to cover our "forgotten" RK2918 Tablets. When I bought my Onda vi30 RK2918 Tablet last November I was certain to get the option to upgrade to ICS sooner or later...but neither "sooner" nor "later" came along...
But I tried your instruction and get stuck at the screen for CWM. I shows up quiet nicely but the touchscreen isn't recognized properly. Here's what happens:
When I tap on the UP or DOWN or any other Softkey on the screen nothing happens. The keys are just not "pressed". HOWEVER: Once (in landscape orientation) I put my fingers on the upper left corner the small lines above the keys flicker. To make it clearer: the area of the key recognition is way off!
Is there a way to flash the CWM Recovery using my stock rom kernel so that the touchscreen is calibrated accordingly?
Thanks for your help, let me know if I can help with some Try-and-Error
Hello, i have a problem, i try this rom on my tablet rk 29
http://www.danew.com/fiche-produits-dslide-701r.php?spage=specification
But, when i apply the recovery, i can't launch the rom, i have bootloop to recovery.
I tryed to install the cm9.ZIP
But i'm blocked at " install cyanogenMod9 " since 20 minutes.
Need help to install please ^^
Sorry for my bad english !
Edit : When i try to backup i have :
E: Can't mount /cache/recovery/log
E : Can't open /cache/recovery/log
E: Can't mount /cache recovery/last_log
E: Can't open /cache/recovery/last_log
and can't mount system !
And i can't send the last lmsg , it's impossible to mount sd card, sd card ext, nothing
Could not merge - no boot
Hi,
I have tried to merge the recovery image with the official Cube u18gt elite but no luck. Unpacked with RK Tools, replaced recovery.img with the modified one, packed, flash, no boot. Could you please help a noob and point me in the right direction? Thank you.
I was doing some searches this week and came across a post about having to turn the screen to the right or left to go up or down. I don't think it was XDA, was just a general google search on RK 2918 or RockChip 2918. My wife has a Mediacom smartpad 850i.
New version released.30/06
Please post the logcat, dmesg in pastebin to evaluate the errors.
BQ Kepler 2
Is this compatible with BQ Kepler 2?
edgardurao said:
Is this compatible with BQ Kepler 2?
Click to expand...
Click to collapse
Yes. If you have problems in installation delete meta-inf /updater-script delete 1º line.
Tested on Cube U9GT-2 9.7"
All is ok, but not working: G-sensor and Camera.
Hey,
I do not have a hardware button/volume rocker like other tablets, I only have three buttons (Menu/Home/Back), a little reset button and the on/off button. I usually flash firmwares by holding the Home Button (the middle one) and plugging the tablet in afterwards.
I have an Onda vi30 Rk2918 (not the A10-Allwinner)
Could I still use this firmware?
I have a question. Is it CM9 with original stock kernel for each tablet, or is there a new kernel included in this CM9 ROM?
also
@eugene_sm Hi, could you tell me how it performs when you tested it? Is it the same as stock/Evolution? Or is it similar? Or is it better? Or is it much better?
Thanks!
sw6lee said:
@eugene_sm Hi, could you tell me how it performs when you tested it? Is it the same as stock/Evolution? Or is it similar? Or is it better? Or is it much better?
Thanks!
Click to expand...
Click to collapse
Hi, my feeling is that this firmware is much faster and better than stock/Evolution.
eugene_sm said:
Hi, my feeling is that this firmware is much faster and better than stock/Evolution.
Click to expand...
Click to collapse
Wow, that's a good news!! I hope I will feel the same way when I try it later. Do you know if it's a different kernel? Or is it the same kernel as usual u9gt2 one, but just the rom is CM9?
Thanks.
I just tried this ROM, and I think it's much faster and smoother than stock based cube roms! I have a huge problem though.. I think google play downloads apps, but it doesn't let me open any downloaded apps. If I open an app, it just takes me to the app page in the google play. I THINK it's related to the LCD density that they changed? Everything's tiny. Some people like that, but it causes some problems. So I can't download a file manager (actually can't open it, along with anything I download), so I have to disable my volume buttons because they are broken and acting weird if I don't disable them. Also, I tried downloading all these free apps I need from computer and tried moving to the tablet, and they were moved successfully, BUT I realized..without a file manager, I can't install any apks..damn!
I don't know what to do??
EDIT: NVM after rebooted, every app I downloaded appeared!
BTW, any U9GT2 users who wants to try this rom, DO NOT use the CWM recovery posted in this thread. It bricked my tablet, then I recovered it luckly, and now everything's fine. Use the CWM posted on FlashMyAndroid forum in the recovery section of U9GT2 forum.
---------- Post added at 01:29 AM ---------- Previous post was at 01:19 AM ----------
OMFG.. Today is THE day I started to actually like my tablet...since like February??
Just changed the LCD density to 160 (original), and even the home screen is super smooth! Before, at density of 120, the home screen was kind of laggy, but all other system was smooth, but now everything is perfect! If you are an U9gt2 owner, and are somewhat frustrated with the ICS performance, DO TRY THIS, and do all the stuff that I stated above, including POST above! Oh and I changed to Apex Launcher btw.
Cheers!!
Hi eugene! Can u tell me if flash is workibg anybetter with this rom. I know itsa long shot but thought it wasworthasking. Currently on gingerbread for flash but a lot of games dont appear to work for some reason. Also is the gsensor working and do uknow if many games are working. Very tempted to try this!
ark2010 said:
Hi eugene! Can u tell me if flash is workibg anybetter with this rom. I know itsa long shot but thought it wasworthasking. Currently on gingerbread for flash but a lot of games dont appear to work for some reason. Also is the gsensor working and do uknow if many games are working. Very tempted to try this!
Click to expand...
Click to collapse
This firmware is still very raw and I do not recommend it for everyday use. Try Evolution 2.3.
eugene_sm said:
This firmware is still very raw and I do not recommend it for everyday use. Try Evolution 2.3.
Click to expand...
Click to collapse
Thanks for the reply mate. I tried evo but too annoying iplayer n stuff doesnt work. Kinda want my cake and eat it too. Is it easy enuf tobsort out the pixel density? Neone else reviewed it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KatKiss ROM
MarshMallow 6.0.1 ReleaseAsus TF101
Please note that this version is made for and tested on the TF101 model.
This rom is an aosp based rom with my own additions on top of it.
The main motto of the rom being Kiss. Even though the Meerkat could give you a kiss, it stands for Keeps it Sweet and Simple too
Which means that just like the other K.A.T stuff, the rom's main goal is efficiency, speed/res ponsiveness,
while not adding bloated features that will slow things down
DOWNLOADS:
Latest Rom Version: KatKiss-6.0_034.zip | Mirror
[*] Gapps: opengapps pico
SuperSU: SuperSU BETA 2.52
Sound improvements & gps quick fix : K.A.T App
SL101 Compatibility Pack: KatKiss-6.0-sl101-compat-V5.zip (To flash after the rom for the Asus Slider SL101 only, DO NOT flash for the TF101 model)
Install Instructions:
These builds are designed to be installed with a recent recovery.
TWRP 2.8.1 is recommended: available here
Older versions of TWRP like 2.3.x won't work.
Backup everything !
Go to recovery
[*]The first time you install: Format /data (full wipe doesn't format)
(you can skip this step if you're already on the same main version of KatKiss, if ever you encounter a problem redo a full clean install and format /data and try again before reporting )
Then *EVERYTIME* flash (all together):
rom zip
SuperSU zip
[*]gapps zip
Wipe cache/dalvik
Reboot
Rom Main Features:
MultiWindow Support with 2, 3 or 4 panes setup
High speed and responsive oriented
High performance and overclocked KatKernel included
Dock keyboard Support with full special/function keys support
Global Keyboard Shortcuts / KeyOverride Macro association (See post #2 for more info)
HDMI Support
Battery Level Indicator & Dock Battery support + Mods (icon/Text/%)
CIFS, ext4, NTFS, ExFat support
RRO Theme Engine - Themes & more info
Native Android FSTRIM + Manual scripts for Database optimization and fstrim (see post #2)
Media Scanner Filters
Navbar with left, balanced (PixelC like) or middle aligned buttons.
All Wifi channels support
Integrated cpu & io performance settings panel
Custom Navbars buttons long press actions
Advanced power menu with reboot options.
User Immersive mode and actions with automode when docked setting
Advanced per application permission management (AppOps)
Ethernet-auto support
Misc utils Busybox, rsync...
Custom Quick Settings tiles
ChangeLog: http://public.timduru.org/Android/KatKiss/6.0/ChangeLog.html
Rom Source: https://github.com/timduru (branch katkiss-6.0)
Credits:
Original banner concept by i9apps, Bootanimation by mgeniusm, original drawing by BBF
Chainfire for SuperSU
WebPage
How to report
What to include in the report
Disclaimer: The usual
Use at your own risk, I won't be responsible for any damages caused to your Transformer or to yourself.
In most cases if something breaks, flashing a rom on top should fix it.
XDA:DevDB Information
KatKiss-MarshMallow, ROM for the Asus Eee Pad Transformer
Contributors
timduru
Source Code: https://github.com/timduru
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 2.6.x
Based On: AOSP
Version Information
Status: Stable
Created 2016-02-19
Last Updated 2018-10-19
Tips
First Install
Make sure you do a format /data the first time you install the rom
(backup your internal storage first if you want to keep something)
The first boot after a rom flash can take a few minutes as ART is slower than dalvik to optimize the applications, but is faster after the 1st time.
(First boot takes ~4-5 minutes without gapps and 10+ minutes with gapps)
Also keep in mind that after a fresh install, it might take a bit of time to get up to full speed as media scanner & google are checking/scanning and restoring stuff.
Bluetooth
Bluetooth might require to be turned on twice before it scans and displays the available devices.
Wallpaper Modes
Different Wallpaper modes have been added in Settings => Display
** Normal (regular android mode)
** Disable System Wallpaper rendering (set as default)
** Disable Wallpaper service
2nd setting will prevent the wallpaper being rendered by the system making things faster and also freeing resources
That's the recommended setting you want to use if you are using a launcher that has internal wallpaper rendering
The Default included Launcher3 has internal rendering
For Nova: Go to its Settings => Desktop => Wallpaper Scrolling => Force, then set a wallpaper.
(You will see a black wallpaper if you're not using a launcher that can do internal rendering, If wallpaper is important and that you want to keep your current launcher, then switch back to the 1st setting)
Youtube
Depending on your network and tablet load, 720p videos might not play or take longer to buffer.
Switch to 480p in that case.
Some videos are also 720p60fps so you might need to switch back to 480p for these too.
You can also try an older youtube version and disable auto updates: youtube-v5.0.21
Google Play Movies
Our current Widevine DRM libs are not compatible in MM.
So you can't play a movie on the tablet with Google Play Movies as it requires that.
Starting a movie to play on chromecast should be fine as the drm will be the chromecast one in that case.
Now On Tap
Now On Tap requires the nano opengapps version, however our default /system partition is too small to accommodate them.
So if you want to install the nano or bigger opengapps version, you'll need to repartition the storage space first using Bigwheelie for extended partitions
Then activate Now on Tap from google now settings
Hardware keyboard layouts
More languages have been added in the default asusec keyboard
Set the keyboard layout through Settings => Language & Input => asusec => setup keyboard layouts
These also allow live switching without reboot with ctrl + space
Global Key Override/Shorcut Mecanism
Available in Settings => Dock => Add Key Override Actions
This will allow you not only to redefine function keys assignment, and other special keys actions,
but you'll also be able to assign global macro actions / app launch to any key + Meta key combination (shift Left or Right , ctrl..)
You can also add multiple actions to one key combination, simply click again on the "+" button for the same key combination.
For example if you want to assign to one key combination a list of action to run before going to bed for example, like: turn wifi off, Bluetooth off, mute sound, and turn screen off, you can do that
Note that starting multiple applications with one key is kinda a miss and hit for the moment due to some mecanism in android that seems to prevent applications to start too close to each others.
Storage (fstrim) and Database optimization:
Fstrim is native since 4.3 and will happen in the background if your tablet is idle / sleeping and that your battery is > 70%
There is also a script to run it manually in the rom: /etc/kat/optimizestorage
To optimize the Database: /etc/kat/optimizedb
To run both, open a terminal and run:
su
/etc/kat/optimize
MultiWindow
Multiwindow allows you to split the screen in 2, 3 or 4 panes
you can switch an app back and forth between multiwindow mode and regular mode while it's running
NavBar:
- To switch between full screen and split View you can use the
NavBar Buttons
The app that currently has the focus (or the latest used app if you're on the Desktop) will be used for the main pane (left and/or top depending on the mode and rotation)
And it will lay the remaining most recently used apps in the rest of the available 1-2-3 panes depending on the icon you click
- If you press a multiwindow icon again when in splitview mode, it'll bring the focused app back to fullscreen mode.
- To swap the 2 latest focused apps location / pane , long press on the
NavBar Button
- To change focus simply Tap on the app or use the
NavBar Button
That button can also be used in non multiwindow mode to switch quickly between the 2 most recent apps.
Global Actions:
Actions to switch the app between fullscreen / splitview 2-3-4 panes, swap, or switch between the 2 most recent apps have been added
so you can bind them to a key / key combination with the Global KeyOverride or long press on navbar button too.
Note: Most apps works ok in splitview mode, but some of them might crash or not refresh correctly sometime.
To manually position an app in one of the pane:
For the moment either reorder your apps before clicking on an auto mode icon,
or you can also activate the default Marshmallow Multiwindow mode to get extra icons to positions an app in a specific pane (activate it in developer options )
Then position the apps with the icons from the Recents screen. (default MM recents icons are for 2 or 4 panes)
Banners
First
Many thanks, Tim, for keeping the Tf101 alive!
I'm a little afraid to try, but I know I will
Officially my Transformer is one of the oldest devices I own and should really show its age.
But it just doesn't, it sets itself apart from the two other Tegra 2 devices (Notion Ink Adam and Acer Iconia) by being a thoroughly enjoyable device, which reacts very promptly to all input and still is mechanically perfect with great battery life.
Some hardware ingredients like DRAM and Flash seem to be made of better stuff (some benchmark show twice the memory bandwidth than Acer Iconia and NI Adam and the eMMC is lots better than Acer (Adam is notoriously terrible)), but mostly it must be the constant tweaking you (and Google?) have put in, because the performance only got better and better, even if the applications typically got fatter and fatter and 1GB of DRAM is no longer as plenty as it used to be with Android 2.2.
I surely can't say the same for my Nexus 7, which started being somewhat snappier than the Transformer and turned out pretty bad with LP even after turning off the journalling on ext4.
Marshmallow has disappointed me so far (only Nexus 10 migrated yet), mostly because my standard launcher SPB shell 3D no longer works on it and I just like it better than stock or any other.
And then I just don't see any significant improvements beyond Lollipop or rather CM 12 with all the privacy stuff already included. And I just love the fast task switching, which is part of the multiwindow support and which I have on a keyboard shortcut (hope it comes soon).
Somehow I also doubt that Nougat will be better in any sense except "better" Google integration.
But since I'm very much afraid of operating anything without the latest security patches, I'll just have to make the switch.
And I'm sure it will be as perfect as the current LP by the time Nougat comes out.
Thanks Timduru for making it possible
Link is ready, downloading :good:
Thank you. what I've failed to understand, do you need to install a separate root tool? Or is it included in the recommended recovery tool? It's still as i bought it in 2011... Thanks!
Thanks so much Tim gonna test this out
cwouter said:
Thank you. what I've failed to understand, do you need to install a separate root tool? Or is it included in the recommended recovery tool? It's still as i bought it in 2011... Thanks!
Click to expand...
Click to collapse
Just follow the procedure from the 1st post:
once you have the recovery installed:
the first time: format /data
then install all 3 zips at once: rom + supersu + gapps
then reboot.
Thank you Tim! Awesome as always. Gonna try ASAP.
One question...
What is the downside of not having omx codecs working?
xbs said:
Thank you Tim! Awesome as always. Gonna try ASAP.
One question...
What is the downside of not having omx codecs working?
Click to expand...
Click to collapse
No omx codecs means no gpu video acceleration, so it'll use cpu to decode instead.
Wait a bit before trying, 019b is coming fixing the reboots with some apps
New Version #019b
New rom version available: KatKiss-6.0_019b.zip
ChangeLog:
TF101:
- Fix reboots caused by some apps(ES file explorer, play music, youtube...)
- Fix ExFat support
TF101 KatKernel 122:
- net: Handle 'sk' being NULL in UID-based routing
- add native ExFat FS support
timduru said:
Just follow the procedure from the 1st post:
once you have the recovery installed:
the first time: format /data
then install all 3 zips at once: rom + supersu + gapps
then reboot.
Click to expand...
Click to collapse
It sounds so easy... First I don't really know how to install the recovery (hence, i have been spending 'only' app 7 hours on topic by now). I would assume from PWR+VOL- then Vol+ goes to recovery mode, but the device gets stuck with a android red expression mark. I then tried to install the Easyflasher 0.8.3 and managed to first delete the drivers and installed new universal ones. Rebooted and continue to follow the procedure and the Easyflasher on my Windows tells me i have successfully unbricked my Asus Stock. However, when i reboot, it looks all exactly the same, no data lost, no new installation. Then I could, or should?, flash a recovery. However, if i try to do it from the Easyflasher there is only the old TWRP 2.2.1. available and i fail to make use of the downloaded TWRP 2.8.1.1. CLick the Root, doesn't work either.
Then, the frustration goes up and the progress goes down... please advise and push me in the right direction! MUch appreciated!
cwouter said:
It sounds so easy... First I don't really know how to install the recovery (hence, i have been spending 'only' app 7 hours on topic by now). I would assume from PWR+VOL- then Vol+ goes to recovery mode, but the device gets stuck with a android red expression mark. I then tried to install the Easyflasher 0.8.3 and managed to first delete the drivers and installed new universal ones. Rebooted and continue to follow the procedure and the Easyflasher on my Windows tells me i have successfully unbricked my Asus Stock. However, when i reboot, it looks all exactly the same, no data lost, no new installation. Then I could, or should?, flash a recovery. However, if i try to do it from the Easyflasher there is only the old TWRP 2.2.1. available and i fail to make use of the downloaded TWRP 2.8.1.1. CLick the Root, doesn't work either.
Then, the frustration goes up and the progress goes down... please advise and push me in the right direction! MUch appreciated!
Click to expand...
Click to collapse
Installing the recovery is not really the focus of this thread, and it has been a really long time since I installed on mine
But what I would do, since you seem to have easyflasher and drivers working:
- Install TWRP 2.2.1 from easyflasher
- reboot to that TWRP 2.2.1
- Install the TWRP 2.8.1.1 flashable zip from TWRP 2.2.1
- reboot to the recovery and it should now be TWRP 2.8.1.1
Flashed all 3 zip ROM+su+pico but can't boot to Android.
After the Asus logo screen turns black and nothing happens.
Any ideas?
xbs said:
Flashed all 3 zip ROM+su+pico but can't boot to Android.
After the Asus logo screen turns black and nothing happens.
Any ideas?
Click to expand...
Click to collapse
sounds as if the new kernel didn't flash or something.
What recovery are you using ?
Even if the screen goes black you should get adb working after a few minutes, it's still doing things in the background normally.
Try to grab me a logcat + dmesg at that point.
EDIT: Found the problem, yeah kernel not flashing:
Flash it separatly for the moment: Tim_KatKernel_122_MM6.0.zip
that will be fixed in the next version.
xbs said:
Flashed all 3 zip ROM+su+pico but can't boot to Android.
After the Asus logo screen turns black and nothing happens.
Any ideas?
Click to expand...
Click to collapse
Unfortunately me too.
The only step from install note was the "Format" because of lack of time and data cable to copy everything from internal sd to my pc (only way for me is over the air with My Phone Explorer right now).
Tried 19 & 19b together with SuperSu 2.52 and gapps-arm-pico in one flash.
Backlight of screen is on, but then nothing happens over an hour.
---------- Post added at 13:46 ---------- Previous post was at 13:45 ----------
timduru said:
sounds as if the new kernel didn't flash or something.
What recovery are you using ?
Even if the screen goes black you should get adb working after a few minutes, it's still doing things in the background normally.
Try to grab me a logcat + dmesg at that point.
EDIT: Found the problem, yeah kernel not flashing:
Flash it separated for the moment: Tim_KatKernel_122_MM6.0.zip
that will be fixed in the next version.
Click to expand...
Click to collapse
Will do immediately!
---------- Post added at 14:00 ---------- Previous post was at 13:46 ----------
Just booted fine, into MM
New Version #019c
New rom version available: KatKiss-6.0_019c.zip
ChangeLog:
TF101:
- Fix Kernel not being installed
timduru said:
Installing the recovery is not really the focus of this thread, and it has been a really long time since I installed on mine
But what I would do, since you seem to have easyflasher and drivers working:
- Install TWRP 2.2.1 from easyflasher
- reboot to that TWRP 2.2.1
- Install the TWRP 2.8.1.1 flashable zip from TWRP 2.2.1
- reboot to the recovery and it should now be TWRP 2.8.1.1
Click to expand...
Click to collapse
Sounds like a plan, i tried and Easyflasher tells me it runs Wheelie,NV Flash then 'finished new reboot into recovery'. I do so, but android gets stuck in the recovery with an red expression mark, then it'll boot normal again.
Might it be that root access is blocking it? The Easyflasher root access tells me to first falsh recovery and put the superuser on sd.
I have installed both TWRP and SuperSu but both run into issues: the first tells me 'root is required' then closes, the second tells me 'no SU binary installed' then closes.
I then decided to go for a very crappy 1-click root access, see http://forum.xda-developers.com/showthread.php?t=1689193, with an even worse http://www.4shared.com/postDownload/ja5cFLAL/1-Click_Transformer_Root_11.html. This seems to have succeeded and i got root access (!) and the above described issues on TWRP and SuperSu were not gone.
Then in TWRP i couldn't select the zipfile TWRP 2.8.1, and after telling TWRP i had a TF101 i could select an older version like 2.3, which he was going to download. I had to confirm a path but decided to abort. I then tried to boot recovery but unfortunately, and not as i expected, it run into the same red expression mark. I then decided to run APX mode again and see if easyflasher could access root now. Also negative. Then run normal ABD mode and checked if i could do something with SuperSu, also negative.
So it seems my problem is that TWRP doesn't allow me to select the right zip file and as a result i can't run any recovery... any idea?
UPDATE: going back to apx flash the default TWRP2.2.1 then reboot to recovery succeeds in Easyflasher but the same red expression mark with Android. so also negative
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To God be the glory, my Slim7 Nougat project finally works on the Note Edge!
This is a very slimmed down version of Android Nougat, almost a "vanilla" experience with a few tasteful perks! By design, this ROM comes without root for those who wish to have a "pure" version without the entanglements that come with root, but it can also be easily rooted by using chainfire's SuperSU (see below for instructions and downloads). In it's default form, it is perfect for those banking apps, workplaces, and games that require you to have a phone without root. No need for tricks or hacks, all while having the latest and greatest Android on your Samsung Galaxy Note Edge.
If you do decide to use root, then you will be pleasently surprised to know that Substratum and layering works with this ROM. While not perfect, for the most part it functions well in my initial testing. However, if you find problems arise after installing a theme, please remove the theme to make sure it is not a substratum related issue.
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
This SlimRoms Nougat ROM was built for the TBLTETMO/TBLTECAN using modified LineageOS TBLTEXX trees. I have not tried this on any other device, but you are welcome to try it AT YOUR OWN RISK. The updater script would need to be edited. Chime in if it worked on your device.
A huge thanks to the SlimRoms Project team!
Disclaimer: SlimRoms is not responsible for any damages to your device.
All of my work is completely available for any who wish to use or modify it. I didn't make SlimRoms, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
Click to expand...
Click to collapse
A huge thanks to the SlimRoms team!
Another huge thanks goes to mickey387 for pioneering Nougat on the Note Edge!
Downloads:
Rom Download link:
http://www.mediafire.com/file/varcd...-7.1.1.build.0.7-UNOFFICIAL-20170223-0838.zip
SuperSU download: (There may be other versions, 2.79 is the only version I personally tested.)
http://www.supersu.com/download
Gapps link:
http://opengapps.org/
-Which I personally only tested Nano. Be sure to choose "Arm" and "7.1".
If you want the AKLU kernel - Better performance and battery life:
https://forum.xda-developers.com/no...droid-development/kernel-aklu-kernel-t3558419
Be sure to only choose the SLIM 7 version.
This Rom has been stable for me, however, Nougat is new, so be prepared for some little hic-ups here and there. Be sure to follow these installation steps very carefully, as they may be different then what you are used to.
!!!FIRST BOOT TAKES LONGER THAN 5 EARTH MINUTES TO COMPLETE!!!
!!!IF YOU FLASH SUPERSU, IT WILL REBOOT SEVERAL TIMES DURING INSTALL, THAT IS OKAY!!!
Installation instructions ( TO BE NON-ROOTED ) :
-YOU MUST BE ON THE 6.0.1 MODEM and BOOTLOADER!
-Download ROM, and if desired, AKLU kernel, and gapps, and put them on your phone's external storage.
-Reboot into recovery mode - TWRP (I personally installed this using 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install Gapps. - Optional
--> OPTIONAL - After first boot, then go back to recovery and install the AKLU kernel.
Installation instructions ( TO BE ROOTED ) :
-YOU MUST BE ON THE 6.0.1 MODEM and BOOTLOADER!
-Download ROM, and SuperSU, AKLU kernel, and gapps, and put them on your phone's external storage.
-Reboot into recovery mode - TWRP (I personally installed this using 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install Gapps -- Optional.
-Let the system boot up.
-Go back to TWRP.
-Install AKLU kernel. - Optional
-Reboot to system.
-Go back to TWRP.
-Install SuperSU.
-Let the system boot up. Note that it may reboot a couple times during the boot animation, that is okay.
-Enjoy!
Code:
What works:
So far everything that I have tried works, such as
- Camera for video and pictures (use orange camera app, not traditional blue camera app.)
- Phone calls/receiving
- Data 2g/3g/LTE
- Bluetooth
- WiFi
- PTP/MTP
- GPS
- WiFi hotspot
- Multi-Window
- Fingerprint sensor* See notes.
etc....
What doesn't:
- Notification LED only shows RED and YELLOW. To show YELLOW, choose CYAN as the notification color, and it will show up YELLOW. All other color choices appear RED.
- The automatic time zone function forgets where you are alot. Use the manual time zone instead.
- Choosing to reboot the phone sometimes takes a loooong time. It may be better to Power off and then start the phone, which is faster for some reason.
- Built in blue camera app sometimes gets "stuck" or freezes or crashes, I tested several other camera apps, and all worked fine, including the orange camera app and opencamera from the fdroid repository.
- There is no "edge" feature at this time.
- Let me know in the forums if you find other issues.
Main Features:
- Merged with android-7.1.1_r13
- SlimDim, now with 100% more dimming
- SlimAction, Splits screen action (long press app in slim recent)
- SlimRecents, an alternative recents
- Notification log (long press statusbar header)
- Kill app from notification (long pres app notification)
- Substratum support (if rooted)
- OmniSwitcher built in so the kill function works with or without root.
- Advanced reboot (found under security settings).
SlimRoms XDA Forum: http://forum.xda-developers.com/slimroms
Source Code: http://github.com/SlimRoms/
Official websites: http://www.slimroms.net/ or http://slimroms.org/
ROM OS Version: 7.1.1 Nougat
ROM Kernel: Linux 3.10.40
Based On: AOSP and LineageOS.
My device trees: https://github.com/alaskalinuxuser/
Created 2017-02-23
Last Updated 2017-02-23
Change log:
Code:
20170223
-Fixed home button screen wake.
-Fixed WiFi hotspot.
-Added texting app.
-Added OmniSwitcher as optional switcher/tasker (makes a good "edge bar" since you can pin apps).
-Initial release!
Notes about the rom:
Notes about the rom:
Fingerprint sensor:
I have successfuly used the fingerprint sensor, but it is a bit sketchy. To make it work:
- Go to register your fingerprint under security settings.
- I registered all 5 of my fingertips all at once, by clicking add another, and only 2 of them "stuck" when I clicked done. I redid it registering one finger over and over again several times, and it eventually registered and stuck.
- If after clicking done, the fingerprint settings says x-number of fingerprints registered, then those fingerprints are working. Once registered, then you can use it in apps, and for the lockscreen, which did work about 1/2 of the time for me.
- If the lockscreen does not show the "fingerprint" icon, reboot to make it appear.
Open Source apps:
There are quite a few really good open source apps included in this build, such as:
Browser app
Amaze file manager app
SatStat GPS app
Camera app (orange one)
All of these great apps and more can be found at https://f-droid.org/repository/browse/. You can also download other great apps there like music players, games, and everything else you might need. The Fdroid app allows you to maintain up to date version control and simple downloading and installation of these apps and is a lightweight alternative to the Google Play Store. that is certainly worth taking a look.
Running smooth as butter. Thanks man!
JeremySS said:
Running smooth as butter. Thanks man!
Click to expand...
Click to collapse
Thanks for the kind words! I also use Slim as my dd on the note edge. Simply elegant. Thanks to the slim team.
I do find the led color for notifications to be an interesting problem.
When setting notifications: If I choose red, it shows up greenish. If I choose yellow, it shows up red. If I choose cyan, it shows up yellow.
But the first flash is always red.
I'll have to work on that.
Does it work with tbltexx
It says it is not compatible with tbltexx.
Thanks
Tunc
eresen said:
It says it is not compatible with tbltexx.
Thanks
Tunc
Click to expand...
Click to collapse
Correct, this is the tbltetmo version. You need this version, which is compatible with your phone:
https://forum.xda-developers.com/note-edge/development/rom-slimroms-n-t3562516
Im having a problem with ir. Sure remote control worked before i changed rom to this one and now it doesnt. Any ideas?
Other than that its top work fella.
any reason why certain applications force close? Like skype for example. Starts, loads for a brief second and force closes
Hi,
I flashed this rom on N915W8 through TWRP. All went well but no sim card was detected. I am very new to this stuff and this is my first post. I really like the rom so would like to know should I do to make it right.
Thanks.
blue_waturz said:
Hi,
I flashed this rom on N915W8 through TWRP. All went well but no sim card was detected. I am very new to this stuff and this is my first post. I really like the rom so would like to know should I do to make it right.
Thanks.
Click to expand...
Click to collapse
Sorry, I no longer have my note edge. However, you could try flashing these data zips: https://forum.xda-developers.com/showthread.php?t=3546110
Hope that helps!
Sent from my LG-H811 using XDA-Developers Legacy app
AlaskaLinuxUser said:
Sorry, I no longer have my note edge. However, you could try flashing these data zips: https://forum.xda-developers.com/showthread.php?t=3546110
Hope that helps!
Sent from my LG-H811 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I reverted back to stock rogers rom to save time and phone. I will need to try again.
Can't install it ..keeps saying E: unknown
Sent from my SM-N930F using XDA-Developers Legacy app
kachhh said:
Can't install it ..keeps saying E: unknown
Sent from my SM-N930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Are you installing this on a 930F? This is for a N915 T.
Sent from my LG-H811 using XDA-Developers Legacy app
No sorry I figured out...I'm on 915T is just my browser was downloading it incomplete.. I just changed the browser and is working
Sent from my SM-N915T using XDA-Developers Legacy app
I flashed the rom but when I connect to beats earphones the mic doesn't work..... Is there a fix for this issue? Besides that it looks good so far, thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is PAX?
Our release of Android 10, titled CR-8.0, is codenamed PAX after the latin word for peace and Pax, the roman godess for peace.
PAX provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. PAX delivers a set of unique features, like a systemwide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z3 Compact
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Nightly
Created 2020-02-08
Last Updated 2020-05-06
My feedback about CR8.0 (weekly build 20200513-0206) with gapps pico, magisk 20.4 and ~75 user apps.
Using TWRP 3.3.1-z3c-20191212-sar from here
Xposed (RiRu 20.2 from magisk repo, EdXposed-YAHFA-v0.4.6.2.4529 from here) works without problems (1st screenshot).
I'm not using internal data encryption because of compatibility problems between ROMs/versions, tired to restore backups each time I flash new ROM.
About 700MB of RAM free just after boot, with stock launcher.
Battery drain fast, but my battery is very old, no complain.
Pros:
+ reliably fast
+ everything works including GPS, BT, calls/data, hotspot and all my apps
+ no problems with audio routing and mic sensitivity
+ camera is ok but I use OpenCamera anyway
Cons/bugs:
- still no 5ghz wifi in Russia (I use my magisk-patch to fix this, may also help with other regions, try if you meet this bug)
- ongoing call can be hanged accidentally by double-tap in any place of turned off display (e.g. by cheek) if tap-to-wake feature is active (here is my workaround using Automate tool, works like a charm). I'm not sure if this bug belongs only to my phone or to any z3c, but it was like forever on any AOSP-based ROM, starting with Android 7.
- broken size for "Aeroplane mode" button/icon in power menu (see 2nd screenshot)
- ringtone sound become a bit quieter after half a second from start of incoming call
- overall loudspeakers volume is not loud enough
Features I'd like to have in this ROM:
1) choose clock position in statusbar (only at left in CR8.0)
2) brightness control by sliding in statusbar without opening it
3) mess up digits on the PIN unlock screen [Carbone Fibers > Buttons > Scramble PIN]
4) unlock instantly when entering last digit without confirmation
5) long press power button to turn on/off torch while display turned off [Carbone Fibers > Buttons > Toggle torch]
6) restrict/disable power menu while phone locked
7) disable notification panel while phone locked
8) set minimal time between notifications on per app basis
9) wake by volume rocker buttons
10) increasing ringing volume
11) debugging over network (settings in devs options, absent in CR)
Most of this stuff available in LOS and AEX roms, but also all (except: 7,10,11, with bugs: 6) can be achieved in CR by using GravityBox xposed module.
Thank you @Myself5 for continue work with our lovely z3c.
Thank you very much for supporting our cute device
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?
Found a BUG: can't set PIN/pattern to lock screen, getting bootloop after try to set it and reboot.
I use z3c as my daily driver, so I need screen lock, can't use this ROM until fixed. Hope I'm not only one who faces this bug.
BigBrother84 said:
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?
Click to expand...
Click to collapse
Not sure about these apps, but at least GravityBox[Q] and App Locale 2 I can NOT get working on this ROM with EdXposed v0.4.6.0_beta(4471) (YAHFA). As well as on latest february build of LOS 17.1 (but worked fine on january build). May be I should try some newer versions of EdXposed (like ones from "canary" repo or something), but I need screenlock bug fixed first to use this ROM and more of free time. Btw, everything works perfect on LOS16.
Hooin Kyoma said:
Wiped all except micro sd. Stuck at "Setup wizard keeps stopping", system unusable. With and without gapps.
Ok I just clean-reinstalled ROM and made first boot WITHOUT SIM CARD INSERTED and it's boot fine. Btw my SIM card PIN-locked (if it's important) and it never caused any problems in LOS17.
Also I reserve this post for my review.
Thank you @Myself5 for continue work with our lovely z3c.
Click to expand...
Click to collapse
The Setup Wizard is still work in progress, and we just discovered nobody tested it with a SIM so far. We'll take care of it, thanks.
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?
Myself5 said:
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?
Click to expand...
Click to collapse
Tried with and without encryption. With and without Gapps. With and without SIM card. Always same result. Everytrhing fine until you set screen lock PIN either from Setup Wizard or from Security settings. First of, unlock method stays "Swipe" after set PIN. And if you reboot, system's boot to desktop and auto-soft-reboot (without sony logo) after few seconds. And yes, this not happening on LOS17.1
Installation immediately fails for me.
Code:
Patching system image unconditionally...
E1001: Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/sdcard/CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200208-1428.zip'[/COLOR]
Updating partition details...
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
Failed to mount '/appslog' (Invalid argument)[/COLOR]
...done
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
E:Error creating fstab[/COLOR]
Tried to update from your previous CR7 build (CARBON-CR-7.0-OPAL-UNOFFICIAL-z3c-20190819-2110), using TWRP 3.2.1 from here. Nothing actually got written, so previous installation is fine.
yxagasasgas said:
using TWRP 3.2.1
Click to expand...
Click to collapse
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.
Hooin Kyoma said:
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.
Click to expand...
Click to collapse
Doesn't work for me, just blackscreens and reboots. Tried installing it both via TWRP app and fastboot (although strangely enough, even though adb worked, fastboot didn't in Windows, had to boot to Linux), no dice, so went back to my previous TWRP for now.
Would be nice to know what's up with that, but I haven't fiddled with any of this in a long time. Ever since CarbonROM appeared, my Z3C pretty much "just worked" and I never had to do much of any fiddling.
New build uploaded just now has the SetupWizard fixed. The lockscreen bug is getting looked into right now.
Uploaded a new build. Contains some additional lockscreen clocks but more importantly, the PIN issue is fixed.
Code:
f8d3b9c5519b91baba7a917d99b7f09e CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200225-1530.zip
Myself5 said:
PIN issue is fixed
Click to expand...
Click to collapse
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Hooin Kyoma said:
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
the camera was not working for me as well, but after some restarts it fixed itself. i dont know how that happened (even tried the xperia camera port from magisc) but i cannot confirm weather that did the trick..
Hooin Kyoma said:
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.
okij said:
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.
Click to expand...
Click to collapse
Thanks for the tip mate. But it didn't help in this case.
Btw, today I installed (again) latest LOS17, tuned it, rebooted many times, played with microG/magisk/xposed modules - camera worked fine all the time.
Next (steps to reproduce): wiped cache, dalvik, data and system, installed only CR-8.0 (20200225), rebooted to system, skip anything, camera WORKS! Did nothing, just rebooted again, and got "Can't connect to the camera"! I think this is a BUG and hope I'm not the only one who faces it.
I still have a question about Carbon Fibers menu, why it lack items/options? I can't even reposition statusbar clock to right without using "third-party" apps like GravityBox xposed module.
Also, kind of "feature request": time to time I use adb from PC (we all do i think), and I hate to connect cable to micro-USB port, cuz it's weak and can break soon if use freqently. I use magnetic port/cable for charging and "ADB over network" toggle in Developer Options for ADB operations. One of the reasons why I prefer LOS is because of this "must have" thing, they even have tile in QS for toggle it quickly! Can it be added to CR?
the "cant connect to the camera" returned unexpectedly..
Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?
Thank you for your hard work!
Does encryption work properly?
What works
Viper4android works
Sony Device Dummy works with official Sony apps
Spotify works
Myself5 said:
Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?
Click to expand...
Click to collapse
Great, this looks interesting indeed!
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1 (because everything is working well and rock stable on this older version and thankfully you still release monthly security patches for it.)
Have you done some thorough testing of cr-8.0 on the Z3/Z3c devices before making it now official and is everything working (e.g. full camera support and proper in-call audio, which had problems on shinano devices on Android 9 and 10 before)?
If so, I might give it a try this weekend.
Thank you and keep up the great work! :good:
okij said:
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1
Click to expand...
Click to collapse
I tried dirty-flash on my cr-6.1, but without success - I can't boot my phone because it stuck in boot animation.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/mantinan/android_kernel_google_msm
Device: https://github.com/LineageOS/android_device_asus_flox
Download:
ROM
Known issues:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
bestiatester said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
ROM (Download from here)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Download:
ROM
Known issues:
Battery is shown as charging at 0 mA.
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!
Mr.Conkel said:
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!
Click to expand...
Click to collapse
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!
GeekyTanuj said:
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!
Click to expand...
Click to collapse
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
Mr.Conkel said:
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
Click to expand...
Click to collapse
Thanks for this guide! Really helped me get things going smoothly! Love this ROM.
Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you
jojo33680 said:
Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you
Click to expand...
Click to collapse
you need to use the Exkernel to enable dt2w. Here's the latest one: Link.
I am running an old 7.0 Resurrection ROM on my N7.
TWRP is installed & bootloader unlocked so I suspect I would just need to repartition & install?
No clue why ADBgives me these errors in powershell.
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
For those who have partition with a different method like me that is NOT flox so they can flash other ROMs, replace this in the ROM zip. All I did was remove assert get prop that checks to make sure your tablet is the right one for the ROM. It won't flash if you're not using flox repartition so I changed it to allow it to flash. I have 1.6gb of system space and am able to flash this ROM, opengapps pico, magisk and custom kernel with no issues running a non flox repartition.
updater-script
drive.google.com
Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.
bestiatester said:
Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.
Click to expand...
Click to collapse
I confirm I have the same problem
Hello all,
I follow the guides and the installation went smoothly, thanks for the really good job you've done.
I'm new in the crDroid world so sorry if the question seems stupid: As the power button of the Nexus 7 is not easy to access, how can I activate the double tap to wakeup ?
Some years ago the tablet was installed with aicp, and the DT2W was working. So I'm a little bit disappointed if it is not working now.
Thanks.
Davidtre07 said:
DT2W
Click to expand...
Click to collapse
This material will help you: 01 ... 02 ... 03 ... 04
lyushiK said:
This material will help you: 01 ... 02 ... 03 ... 04
Click to expand...
Click to collapse
With Anykernel installed works like a charm !
Thanks.
Davidtre07 said:
With Anykernel installed works like a charm !
Thanks.
Click to expand...
Click to collapse
If you have a patch or pointer to the code that makes it work... just let me know and I'll try to add it.
I'm testing a patch for the charge current to be shown ok, seems to work, if all the tests are ok I'll ship it in with the next release.
No I don't have any patch to propose, I just followed the links provided by @lyushiK.
As far I understood, to work you have to recompile a kernel with DT2W hability and you have to activate it with the right flag in the kernel.
From my side what I've done:
Installed Magisk (patched boot.img)
Installed this kernel: https://androidfilehost.com/?fid=7161016148664820402
And to finish added to magisk this module: https://github.com/ipdev99/mModule_dt2w
Reboot and it works !
In Magisk I see the module is looking in /sys/ for "doubletap*" or "dt2w*" or "wake_gesture".
If it found one of the files then activate it (echo 1 in the file)
But still, you have to have the right kernel !
Thanks very much, this Rom is so smooth and running great. The only thing I've noticed is that the icon size and text is very small when using the tablet in landscape mode but fine in portrait mode. Any changes I make to the icon size from the settings apply in portrait but when switched to landscape stay as really small, is there any setting I have missed to enlarge them?
Thank you for the great work!
Just for feedback: I can confirm the camera issue, too, though it doesn't bother me.
Another small thing I noticed: during the initial setup my device was called Pixel 6 Pro (first I thought, I chose the wrong image) but in the settings it says correctly "Nexus 7".