{
"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 a free, community built, aftermarket firmware distribution of Android 5 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
These unofficial builds are based on the CM t30 Kernel available at https://github.com/CyanogenMod/android_kernel_acer_t30
All my specific device tree can be integrated in the CyanogenMod project.
https://github.com/Shr3ps/device_acer_a510
https://github.com/picasso-m-mf-dev/android_device_acer_a510
These builds are based on some Graphic Legacy code, thanks to pawitp for his patches : https://gist.github.com/pawitp/c8a4b32ecd838146192b
Downloads
cm-12-20150409-UNOFFICIAL-a510_lvm (9f521876a716178e8b5711afb53a8d22)
cm-12-20150201-UNOFFICIAL-a510-exp_lvm (c1e94281ae53ff70852e40312d7e07f0)
http://acer.shreps.fr
Requirement
An unlocked Bootloader - JB Version
CWM recovery or TWRP recovery
version 6.0.5.0+ with LVM Support (Look at the CWM thread) or TWRP with LVM Support (called bigsystem by Elibl)
Installation
Do a Nandroid Backup!
Wipe data/factory reset if coming from another ROM or version of CM. If you are already on CM11 or CM12, just make Wipe Cache & Wipe Dalvick-Cache for a proper upgrade.
Install the ROM using Recovery
Install the adapated Google Apps (I recommend minimal Gapps 5 on my website gapps-lp-20141109-signed.zip but you can use Latest Paranoid Gapps for 5.0.x
Note: The partition layout of CM12 is identical to that of CM11 with LVM and thus you may use CWM with LVM to backup/restore.
Bugs & FAQ
Known Issues:
RIL not compatible with A511
Flashing L might take a while in recovery (please be patient)
First boot might take a while too !
Frequent random crashes
Bootanimation crashes after a while (but the boot process continues normally)
Setting brightness to minimum while on auto brightness may cause the screen to go completely dark with no way to set it back except for guessing where the brightness setting is or using adb to force set a higher brightness.
If you have a black screen at first boot or after bad settings manipulation, use this commande in adb :
Code:
adb shell "echo 255 > /sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness"
If it doesn't work, push power to enable your screen and try the command again.
If the bug comes with auto-brightness enabled, you can put your sensor on a light to force it to level up the brightness.
SELinux not in enforcing mode
Bluetooth may not work properly
XDA:DevDB Information
[ROM][5.0.2] CyanogenMod 12 for Acer A510[UNOFFICIAL], ROM for the Acer Iconia A700 and A510
Contributors
Shreps
Source Code: https://github.com/picasso-m-mf-dev/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: JB Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Beta
Stable Release Date: 2015-04-09
Beta Release Date: 2015-02-01
Created 2015-02-03
Last Updated 2015-04-10
Here we go with the first public build !
cm-12-20150201-UNOFFICIAL-a510-exp_lvm (c1e94281ae53ff70852e40312d7e07f0)
Bravo shreps
Nice to see pawtip works used.
is there another tegra3 with lollipop , to mutually work ?
BENETNATH said:
Bravo shreps
Nice to see pawtip works used.
is there another tegra3 with lollipop , to mutually work ?
Click to expand...
Click to collapse
I'm not sure, the t30 kernel is very Acer specific on many driver part.
We need a good Kernel dev to manage to make it "clean" and remove all the Acer specific code, that would be great in order to properly upgrade the Kernel next.
Actually, we're stuck on 3.1 Kernel version because of these Acer code.
But I'm not this person, I'm lacking kernel skills (and also free time) to do this.
Unfortunately we had only one kernel dev.
But we lost him, because he has no tab anymore.
CM12 ist running on my A510 since 0:45 (in germany) without any problems, except brightness minimum.
I wiped system, cache, dalvik and internal memory (to delete all data from older installations)
Than I flashed CM12 and Gapps with TWRP.
I didn't tested Bluetooth.
Acer Iconia A510 | CM12 | Android 5.0.2
HornetRider said:
Unfortunately we had only one kernel dev.
But we lost him, because he has no tab anymore.
CM12 ist running on my A510 since 0:45 (in germany) without any problems, except brightness minimum.
I wiped system, cache, dalvik and internal memory (to delete all data from older installations)
Than I flashed CM12 and Gapps with TWRP.
I didn't tested Bluetooth.
Acer Iconia A510 | CM12 | Android 5.0.2
Click to expand...
Click to collapse
Yes, it's bad news for Zyian ?
But thx for your feedback on the build !
Envoyé de mon One+
kernel work is really a pain, i agree.
It requires a lot of time to get something working..
CM12 isn't rooted?
It's no problem, I flashed SuperSU 2.45 to get root.
Acer Iconia A510 | CM12 | Android 5.0.2
I have a bug in gallery app
https://docs.google.com/file/d/0B_Ls_Pd3r1HIR0s0UlhGUlpUbE0/edit?usp=docslist_api
There are grey fields between my pictures.
All real existing pictures are shown, but between them are this grey fields.
Cyanogen Gallery shows all pictures correct.
When I try to use G+ Foto App, Android media server crashes.
HornetRider said:
I have a bug in gallery app
https://docs.google.com/file/d/0B_Ls_Pd3r1HIR0s0UlhGUlpUbE0/edit?usp=docslist_api
There are grey fields between my pictures.
All real existing pictures are shown, but between them are this grey fields.
Cyanogen Gallery shows all pictures correct.
When I try to use G+ Foto App, Android media server crashes.
Click to expand...
Click to collapse
Gallery and Photos G+ app working fine on My tab.
Try to clear cache and remove thumbnail dir on your memory
Envoyé de mon One+
Didn't work for me.
This grey fields are no missing pictures or missing thumbnails.
All real existing pictures have thumbnails.
Acer Iconia A510 | CM12 | Android 5.0.2
Me too, I can't open Photo app. It will be force closed after I ignore first cloud backup prompt.
Sent from my A510 using XDA Free mobile app
Did both of you made a wipe data ? Did you upgrade G+ via play store ?
Envoyé de mon One+
Yes for both.
It's OK for build in gallery but FC happens in Google Photo.
I have wiped both cache and delete cache.
After upgrade process finished, I can't go into desktop. So I wiped data as well.
Finally I read install instructions again and figure out that the problem is caused by backlight setting.
Then I install gaaps again.
Sent from my A510 using XDA Free mobile app
About the Gallery app issue, @HornetRider I think you should try to format your internal memory an push back cleaned photos
About the Photos issue from G+, it could be a gapps issue, you can try to flash another gapps package. On my tab, I upgrade Google+ from the play store, and no problem using the Photos app.
First thanks to Shreps for his great work.
For myself I found a solution of this Brightness-Gate.
I played a little bit in the configuration settings.
and then I turned off a funtion, called "Adaptive Brightness".
Look at my picture.
Since then, I have no more issues with calibrating brightness
Shreps said:
About the Gallery app issue, @HornetRider I think you should try to format your internal memory an push back cleaned photos
About the Photos issue from G+, it could be a gapps issue, you can try to flash another gapps package. On my tab, I upgrade Google+ from the play store, and no problem using the Photos app.
Click to expand...
Click to collapse
I suspect the missing thumbnails caused by the scan media process.
Coz I can't run build in Music app as well but I have a solution.
I tried to eject SD card and rebooted my tablet.
While system is running in second boot, insert the SD card again.
Now I ve got most of the thumbnails but still some missing.
Moreover, I can run Google photo now but it shows many missing media icons.
Music app now is running in perfect status. It show all songs and covers.
No more force closed happen.
I'll try to backup all data in SD card and format it.
Sent from my A510 using XDA Free mobile app
Hi,
First of great work Shreps and thank you for continued support.
i have a problem. Made the install (full wipe cache, dalvik, data) after install and first reboot the black screen (tried several clean installs with and without apps). problem is that i cant make connection with ADB to send command. The computer (windows 8.1) recognizes the tablet connection when connecting usb, but adb can't find the device.
any solution for that?
I use twrp recovery and in the recovery mode adb is finding my phone.
i'm kind a noob here
Fixed: use windows 7 for debugging
Shreps said:
About the Gallery app issue, @HornetRider I think you should try to format your internal memory an push back cleaned photos
About the Photos issue from G+, it could be a gapps issue, you can try to flash another gapps package. On my tab, I upgrade Google+ from the play store, and no problem using the Photos app.
Click to expand...
Click to collapse
I wiped the internal storage together with system, cache and dalvik , before I flashed CM12.
But all my photo folders are on my external SD-Card. Maybe I should wipe the card (after backup all important data)?
wallacefung said:
I'll try to backup all data in SD card and format it.
Click to expand...
Click to collapse
Did this solve your problem?
Than I'll try it also.
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 a free, community built, aftermarket firmware distribution of Android 4.4 (Kit Kat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
These unofficial builds are based on the CM t30 Kernel available at https://github.com/CyanogenMod/android_kernel_acer_t30
Big thanks to pawitp and his great work on A700.
All my specific device tree can be integrated in the CyanogenMod project.
https://github.com/Shr3ps/device_acer_a510
https://github.com/picasso-m-mf-dev/android_device_acer_a510
Downloads
cm-11-20160109-STABLE_UNOFFICIAL-a510_a511_lvm (815f962d58d4c146e2510d71db4f65c2) [Includes all security patch from January 1st 2016]
cm-11-20150629-UNOFFICIAL-a510-a511_lvm Stable - Final Build (9270a16291245e98b704d12e4db9d6f2)
cm-11-20150113-UNOFFICIAL-a510-a511_lvm (66675eb46ca7a7cae3b98debaa960ff4)
cm-11-M11-20141018-UNOFFICIAL-a510-a511_lvm (6aeea1c6427e4f3620b66a81c6ad255f)
cm-11-M10-20140920-UNOFFICIAL-a510-a511_lvm [1afa7b99ba78f22f030b78c7c563ba0c]
cm-11-M9-20140805-UNOFFICIAL-a510-a511_lvm [30ec5acc0a9b53b3ed65f8bc426ec7c6]
cm-11-20140711-UNOFFICIAL-a510-a511_lvm
cm-11-20140625-UNOFFICIAL-a510-a511_lvm (Android 4.4.4 + LVM Support)
cm-11-20140609-UNOFFICIAL-a510-a511 (Android 4.4.3)
cm-11-20140430-UNOFFICIAL-a510-a511 (Latest 4.4.2 Stable)
cm-11-20140407-UNOFFICIAL-a510-a511 M5 Tag
cm-11-20140325-UNOFFICIAL-a510-a511
cm-11-20140311-UNOFFICIAL-a510-a511 M4 Tag
cm-11-20140303-UNOFFICIAL-a510-a511
cm-11-20140224-UNOFFICIAL-a510-a511
cm-11-20140214-UNOFFICIAL-a510-a511
cm-11-20140129-UNOFFICIAL-a510
cm-11-20140121-UNOFFICIAL-a510
cm-11-20140115-UNOFFICIAL-a510
cm-11-20140111-UNOFFICIAL-a510
cm-11-20140103-UNOFFICIAL-a510
cm-11-20131230-UNOFFICIAL-a510
http://acer.shreps.fr
Requirement
An unlocked Bootloader - JB Version
CWM recovery or TWRP recovery
version 6.0.4.x+ for 4.4.2/4.4.3 (You can flash my CWM 6.0.4.5 build or the latest 6.0.4.7) or an updated TWRP
version 6.0.4.9+ with LVM Support for 4.4.4 (Look at the CWM thread) or TWRP with LVM Support (called bigsystem by Elibl)
Installation
Do a Nandroid Backup!
Wipe data/factory reset if coming from another ROM or version of CM. If you are already on CM11, just make Wipe Cache & Wipe Dalvick-Cache for a proper upgrade.
Install the ROM using appropriate ClockworkMod Recovery
Install the adapated Google Apps (I recommend Gapps 4.4.2 Core on my website [12-14_GApps_Core_4.4.2_signed.zip] for 4.4.2 & 4.4.3)
Use Official CM Gapps or Latest Paranoid Gapps for 4.4.4
Note: The partition layout of CM11 is identical to that of CM10.x and thus you may use CWM to backup/restore.
CyanogenMod Changelog
http://changelog.bbqdroid.org/
Bugs & FAQ
If the Tablet has some rendering problem in Portrait Mode (some margin with the status bar)
You can use the "Immersive Mode" by CM or "Disable HW overlays" in the developer options
[Should be Fixed in the latest version]
If you have some wallpaper resizing bugs
Try another Launcher like Nova Launcher, we have to wait for a CM Fix
[Should be Fixed in the latest version]
If you can't take a photo with the camera app
You need to use an external SDCard
No Data location (GPS Ok, but Wifi location KO)
Fixed with 4.4.4 !
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
XDA:DevDB Information
CyanogenMod 11 for Acer A510/A511, ROM for the Acer Iconia A700 and A510
Contributors
Shreps
Source Code: https://github.com/Shr3ps/device_acer_a510
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: JB Unlocked Bootloader
Version Information
Status: Stable
Current Stable Version: Final Build
Stable Release Date: 2015-06-29
Created 2014-07-01
Last Updated 2015-06-29
And Happy new year
Hey
thank you so much Shreps.
If anyone is experiencing problems... Try to flash the pa_gapps-modular-mini-4.4.2-20131230-signed.zip Gapps. The other ones didnt work for me.
Happy new year.
davze said:
Hey
thank you so much Shreps.
If anyone is experiencing problems... Try to flash the pa_gapps-modular-mini-4.4.2-20131230-signed.zip Gapps. The other ones didnt work for me.
Happy new year.
Click to expand...
Click to collapse
12-14_GApps_Core_4.4.2_signed.zip didn't work well ? What are the problems ?
Shreps said:
And Happy new year
Click to expand...
Click to collapse
Happy new year to you too and to all people on xda, bonne annnnéééeeeeee 2014... :laugh:
recovery install
Shreps said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (Kit Kat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
These unofficial builds are based on the CM t30 Kernel available at https://github.com/CyanogenMod/android_kernel_acer_t30
All my specific device tree can be integrated in the CyanogenMod project.
https://github.com/Shr3ps/device_acer_a510
Downloads
cm-11-20131230-UNOFFICIAL-a510
http://acer.shreps.fr
Requirement
An unlocked Bootloader
CWM recovery version 6.0.4.x+ (You can flash my CWM 6.0.4.5 build)
Installation
Do a Nandroid Backup!
Wipe data/factory reset if coming from another ROM or version of CM
Install the ROM using ClockworkMod Recovery 6.0.4+
Install the Google Apps for KK (I recommend Gapps 4.4.2 Core on my website, but you can use CM Gapps : http://wiki.cyanogenmod.org/w/Gapps or PA Gapps : http://forum.xda-developers.com/showthread.php?t=2397942)
Note: The partition layout of CM11 is identical to that of CM10.x and thus you may use CWM to backup/restore.
CyanogenMod Changelog
http://changelog.bbqdroid.org/
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Click to expand...
Click to collapse
Hi,
How to install "shreps" recovery?
with adb sheel?
fastboot flash recovery recoveryshreps.img
and that is all?
ACER 510
bootloader: unlock
recovery: cwm 6.0.1.3 nothrills
rom: 10.2-20131203 Cyanogenmod
I got problems with the Gapps. Either nothing works (PA Gapps Full) or the system boots but Gapps are not showing up in the app drawer. Any recomodations which gapps package i should flash?
palotex said:
Hi,
How to install "shreps" recovery?
with adb sheel?
fastboot flash recovery recoveryshreps.img
and that is all?
ACER 510
bootloader: unlock
recovery: cwm 6.0.1.3 nothrills
rom: 10.2-20131203 Cyanogenmod
Click to expand...
Click to collapse
Yes, via Fastboot like the NoThrills version, you just have to follow the instructions : http://forum.xda-developers.com/showthread.php?t=1866378
using my IMG file.
fastboot flash recovery recovery-cwm-shreps-6.0.4.5-a510.img
davze said:
I got problems with the Gapps. Either nothing works (PA Gapps Full) or the system boots but Gapps are not showing up in the app drawer. Any recomodations which gapps package i should flash?
Click to expand...
Click to collapse
Use 12-14_GApps_Core_4.4.2_signed.zip in order to have the minimal core Google Services (Play Store & Google Account Sync)
Then, install all your needed Google Apps from the Store (Gmail, Maps, Keyboard, Hangout, G+, etc.)
It works now. Have a nice evening!
Just flashed the Rom.
Working great so far.
Thanks for this port!
Shreps said:
Yes, via Fastboot like the NoThrills version, you just have to follow the instructions : http://forum.xda-developers.com/showthread.php?t=1866378
using my IMG file.
fastboot flash recovery recovery-cwm-shreps-6.0.4.5-a510.img
Click to expand...
Click to collapse
I've been trying this, following the instructions, but when I type in adb reboot-bootloader the tablet just reboots normally and doesn't stop at the bootloader. Entering fastboot flash recovery recovery-cwm-shreps-6.0.4.5-a510.img when at the bootloader just gives <waiting for device>
Thank you very much Shreps! Will give it a try tonight and post back
ok... I seem to be stuck, as I can't get adb to see my device online (always appears offline and I've tried different solutions listed on the web) to reboot on bootloader mode to install CWM 6.0.4.5, I have CM 10.2 right now; any help?
EDIT: OK, I updated ADB to the latest version, as the one I was using on older version that came with an AIO toolkit for rooting ICS version of the tab, but I can't get it to reboot in either bootloader or recovery mode; the tabs reboots, but gous straight into CM boot :S
mossief1965 said:
I've been trying this, following the instructions, but when I type in adb reboot-bootloader the tablet just reboots normally and doesn't stop at the bootloader. Entering fastboot flash recovery recovery-cwm-shreps-6.0.4.5-a510.img when at the bootloader just gives <waiting for device>
Click to expand...
Click to collapse
I got there in the end. Downloaded flashify from store and used that. ROM is working perfectly so far, very stable and smooth.
Sent from my A510 using Tapatalk 4
Lusanagi said:
ok... I seem to be stuck, as I can't get adb to see my device online (always appears offline and I've tried different solutions listed on the web) to reboot on bootloader mode to install CWM 6.0.4.5, I have CM 10.2 right now; any help?
EDIT: OK, I updated ADB to the latest version, as the one I was using on older version that came with an AIO toolkit for rooting ICS version of the tab, but I can't get it to reboot in either bootloader or recovery mode; the tabs reboots, but gous straight into CM boot :S
Click to expand...
Click to collapse
Hello, if you are on CM 10.2, you can go in the developer options, activate advanced reboot and press power : reboot in bootloader.
And from there you will be able to flash the new recovery
Good luck
Envoyé de mon S510 en utilisant Tapatalk
You can also use Flashify app from google play to flash CWM, it works well for me
Shreps said:
Hello, if you are on CM 10.2, you can go in the developer options, activate advanced reboot and press power : reboot in bootloader.
And from there you will be able to flash the new recovery
Good luck
Envoyé de mon S510 en utilisant Tapatalk
Click to expand...
Click to collapse
Already tried that and quick boot, still boots back to cm
I'll try flashify and see how it goes
Nice work.
Every thing is running well.
Only bookmark sync is missing. But this look's like a common CM11 issue.
Thanks for your work.
Gesendet von meinem A510 mit Tapatalk
Thank your for your post first.
I got a problem while flashing the ROM. I used the Recovery by NoThrills, v6.0.1.9 to flash your 4.4 ROM and it fails...of course. Sorry I missed the part about the version of the Recovery... and I can't enter the old system (which is your post of CM10, 4.3) now. Every time the tab starts, it will fail to load the system, and restarts automatically to Recovery Mode...
I don't know how to flash a Recovery in this situation... and ADB or FASTBOOT doesn't work when the tab is in Recovery mode...
Please give me some suggestion, 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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
These unofficial builds are based on the CM t30 Kernel available at https://github.com/CyanogenMod/android_kernel_acer_t30
All my specific device tree can be integrated in the CyanogenMod project.
https://github.com/Shr3ps/device_acer_a510
https://github.com/picasso-m-mf-dev/android_device_acer_a510
These builds are based on some Graphic Legacy code, thanks to pawitp for his patches : https://gist.github.com/pawitp/c8a4b32ecd838146192b
Downloads
cm-12.1-20150722-UNOFFICIAL-a510 (bdfe1fd99d3637b44e8da82f1ac6c60c)
cm-12.1-20150707-UNOFFICIAL-a510 (1b5e7892bd3cf88f8d7d56489c5b6413) [android-5.1.1_r6]
cm-12.1-20150615-UNOFFICIAL-a510 ( 766c865f922802997324591b66a272d9) [Using Z-Kernel][android-5.1.1_r4]
cm-12.1-20150606-UNOFFICIAL-a510 (ab5b04a18af6923dc8d388bdfd837702) [Using Z-Kernel]
cm-12.1-20150605-UNOFFICIAL-a510a (161b2a5cceb8619bb8943bb4c7c23368) [Using Grouper HWcomposer Blob 5.1 - LMY47D]
cm-12.1-20150523-UNOFFICIAL-a510 (3746f125544f196747fd3578f7decd0b) [android-5.1.1_r3]
cm-12.1-20150514-UNOFFICIAL-a510 (2309701493fed98a40ce431252dc81cc) [android-5.1.1_r1]
cm-12.1-20150417-UNOFFICIAL-a510 (1999f944a548b6d88143f8083c84a66d) [android-5.1.0_r5]
cm-12.1-20150409-UNOFFICIAL-a510 (fbf1de716605dd31ade9666cab3f8ad0) [android-5.1.0_r3]
http://acer.shreps.fr
Requirement
An unlocked Bootloader - JB Version
CWM recovery or TWRP recovery
version 6.0.5.0+ with LVM Support (Look at the CWM thread) or TWRP with LVM Support (called bigsystem by Elibl)
Installation
Do a Nandroid Backup!
Wipe data/factory reset if coming from another ROM or version of CM. If you are already on CM12 or a previous build of CM12.1, just make Wipe Cache & Wipe Dalvick-Cache for a proper upgrade.
Install the ROM using Recovery
Install the adapated Google Apps (Latest Paranoid Gapps for 5.1)
Note: The partition layout of CM12 is identical to that of CM11 with LVM and thus you may use CWM with LVM to backup/restore.
Bugs & FAQ
Known Issues:
RIL not compatible with A511
Flashing L might take a while in recovery (please be patient)
First boot might take a while too !
Setting brightness to minimum while on auto brightness may cause the screen to go completely dark with no way to set it back except for guessing where the brightness setting is or using adb to force set a higher brightness. (should be fixed)
If you have a black screen at first boot or after bad settings manipulation, use this commande in adb :
Code:
adb shell "echo 255 > /sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness"
If it doesn't work, push power to enable your screen and try the command again.
If the bug comes with auto-brightness enabled, you can put your sensor on a light to force it to level up the brightness.
SELinux not in enforcing mode
GPU HWComposer & HDMI, please check this post
XDA:DevDB Information
[ROM][5.1] CyanogenMod 12.1 for Acer A510[UNOFFICIAL], ROM for the Acer Iconia A700 and A510
Contributors
Shreps
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: JB Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Beta
Beta Release Date: 2015-04-09
Created 2015-04-09
Last Updated 2015-04-10
Hello , i have flashed with TWRP 2.7.1 and I'm stuck at first reboot on acer logo , how long must I wait ?
funregis said:
Hello , i have flashed with TWRP 2.7.1 and I'm stuck at first reboot on acer logo , how long must I wait ?
Click to expand...
Click to collapse
Weird, it should boot with the cm bootanim. Are you sure you're using a LVM recovery ?
Only tried with My CWM on my tab.
Shreps said:
Weird, it should boot with the cm bootanim. Are you sure you're using a LVM recovery ?
Only tried with My CWM on my tab.
Click to expand...
Click to collapse
Ok I will try with CWM
mmmm A have a ICS bootloader , strange I cant flash jelly bean bootloader to get LVM. My fast boot mode is not working anymore .
I flashed my pad to 5.1. It suddenly reboot in first hour. I keep it in suspend status for a whole night then I reboot manually. After rebooting, it runs system optimizing process again. What's wrong with the dalvik cache partition? But it seems the system is very statble and smooth now.
Sent from my A510 using XDA Free mobile app
wallacefung said:
I flashed my pad to 5.1. It suddenly reboot in first hour. I keep it in suspend status for a whole night then I reboot manually. After rebooting, it runs system optimizing process again. What's wrong with the dalvik cache partition? But it seems the system is very statble and smooth now.
Sent from my A510 using XDA Free mobile app
Click to expand...
Click to collapse
Cool if it's now stable
cm-12.1-20150410-UNOFFICIAL-a700 beta
@Sterist and all A700 users
Can some of you try this : cm-12.1-20150410-UNOFFICIAL-a700 (0503e7cf1944abe38f1d7a1065d08c73)
+cc @Ziyan @nchc @farris @kraoc @Moscow Desire (don't remember who has an A700 )
Shreps said:
@Sterist and all A700 users
Can some of you try this : cm-12.1-20150410-UNOFFICIAL-a700 (0503e7cf1944abe38f1d7a1065d08c73)
+cc @Ziyan @nchc @farris @kraoc (don't remember who has an A700 )
Click to expand...
Click to collapse
Sure, but I have an A510
Struggling here to install the gapps, as "insufficient space" - error 70. Moved from CWM to TWRP but still not luck with stock and full. Without the gapps, CM 12.1 looks fine though.
LATER EDIT: mini flashed successfully. So my \system is too small, huh?
sstanescu said:
Struggling here to install the gapps, as "insufficient space" - error 70. Moved from CWM to TWRP but still not luck with stock and full. Without the gapps, CM 12.1 looks fine though.
LATER EDIT: mini flashed successfully. So my \system is too small, huh?
Click to expand...
Click to collapse
Yes, /system partition is very small on A510, CM12.1 is possible thanks to LVM.
Envoyé de mon One+
Hello Shreps,
I try to install your rom on my A700 with twrp and the install never really start. It stop with some commandline then it freeze.
I install lots of rom with different device and it never happen.
What I'm doing wrong?
Thks for the rom.
marsulio said:
Hello Shreps,
I try to install your rom on my A700 with twrp and the install never really start. It stop with some commandline then it freeze.
I install lots of rom with different device and it never happen.
What I'm doing wrong?
Thks for the rom.
Click to expand...
Click to collapse
I thought i had the same problem while flashing: twrp seemed to freeze, but after a about 15 minutes the rom was flashed (along with PA Gapps Pico).
First impressions: the initial setup (WLAN, google account) was extremly laggy and after each step the tablet rebooted.
After enabling Developer mode the A700 crashed and rebooted but they were enabled afterwards.
Unfortunatly a message that the storage space is running out popped up.
Next reboot after enabling expanded desktop.
WLAN, expanded desktop and camera work, bluetooth and GPS couldn't be tested at the moment.
This was the second lollipop build I have tested on the A700 and like on the other build the screen turns completly black on minimal brightness - I hope this helps.
I will test it now for a while before reverting to PacRom RC3.
Un grand merci à Shreps for his awesome work kepping the A700 alive!
amazing!
this rom works perfectly good, many thanks for your efforts dude! ( je t'aime @Shreps )
Shreps said:
@Sterist and all A700 users
Can some of you try this : cm-12.1-20150410-UNOFFICIAL-a700 (0503e7cf1944abe38f1d7a1065d08c73)
+cc @Ziyan @nchc @farris @kraoc (don't remember who has an A700 )
Click to expand...
Click to collapse
I have a 510
CAn´t install CM 12.1.....
Hi,
Need help to install CM 12.1.
I tried to install recovery 6.0.5.0 LVM using fastboot ( i have TWRP recovery), but doesn´t boot. Say error and reboot.
I tried install CM12.1 with TWRP , but after flashing, and reboot tablet, the acer logo stay on screen........ I wait about 20 minutes... and tablet didn´t boot to system. Did all wipes......
Can anyone help me to install CM12.1?
Step by step..
Thank you :angel:
test on A700
Thanks Shreps, I´ve tried to test your rom on my A700. Flashed it with TWRP 2.7.1.0 and after reboot, I got the brightness problem and cant fix it.
Can´t connect through ADB cause of "device unauthorized". And I can´t accept incomming connection on screen, cause i cant see the dialog.
I´ve tried to enable adb via the shell in TWRP but it didn´t work at all.
Code:
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
If you can fix it, i will like to test your roms. :good:
Flippo24 said:
Thanks Shreps, I´ve tried to test your rom on my A700. Flashed it with TWRP 2.7.1.0 and after reboot, I got the brightness problem and cant fix it.
Can´t connect through ADB cause of "device unauthorized". And I can´t accept incomming connection on screen, cause i cant see the dialog.
Click to expand...
Click to collapse
After a long install I have the same problem that Flippo24 got.
If you find where could be the problem, I'd like to test your rom too.
For sure you can open an extra Thread for your Rom in A700 section so some more people can find it.
Shreps said:
@Sterist and all A700 users
Can some of you try this : cm-12.1-20150410-UNOFFICIAL-a700 (0503e7cf1944abe38f1d7a1065d08c73)
+cc @Ziyan @nchc @farris @kraoc @Moscow Desire (don't remember who has an A700 )
Click to expand...
Click to collapse
downloading now, but getting ready for work.
Will report back soon
edit: I see now I'm the last to get the memo lol anticipating the same issue as the prior feedback, I'll wait for the next
{
"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"
}
OmniROM is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance, reliability and features over stock Android for your device. It's also about options, which is the beauty of Android.
Code:
#include <std_disclaimer.h>
/*
* 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. Hard. A lot.
*/
OmniROM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts.
All the source code for OmniROM is available in the OmniROM Github repo.
Homepage:
=================
http://omnirom.org/
Wiki:
=================
http://docs.omnirom.org/Main_Page
Gerrit:
=================
https://gerrit.omnirom.org/
Bugtracker:
=================
http://jira.omnirom.org
Use this thread to report bugs as this is UNOFFICIAL
IRC:
=================
irc.freenode.net #omnirom
Be Advised:
=================
Root access is not included by default. Please flash SuperSU for root (See below).
If problems arise from your use of custom kernels, "performance scripts", etc. etc., we can't be responsible.
Screenshots:
=================
http://abload.de/img/screenshot_20170814-2qlsi5.png
http://abload.de/img/screenshot_20170814-2mssai.png
Installation Instructions:
=================
First time installing OmniROM to your Shield Tablet or coming from another ROM:
- Read known issues and FAQs
- Make sure you're running a proper working Team Win Recovery Project (TWRP) - https://twrp.me/devices/nvidiahshieldtablet.html
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Don't restore system data using Titanium Backup!
Upgrading from earlier version of OmniROM:
- Copy the OmniROM zip to your SDCard
- Boot into Recovery
- Flash the OmniROM zip from SDCard
- Reboot
Downloads:
=================
UNOFFICIAL builds
omni-7.1.2-20171110-shieldtablet-HOMEMADE.zip md5:196df454441117da0962015063573a95
omni-7.1.2-20170901-shieldtablet-HOMEMADE.zip md5:02b22807016a3e39d0b0e46986fb24d9
omni-7.1.2-20170818-shieldtablet-HOMEMADE.zip md5:1ebc771fa3626a2a2bd7e68d72df9f7b
omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip md5:4710c3ec9347e1c9ca7dc4013fde0bbf
MIRROR: omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip
Gapps: Open Gapps
http://opengapps.org/
SuperSU:
http://www.supersu.com/download
Device Source Code:
=================
Device trees:
https://github.com/Lolzen/android_device_nvidia_shieldtablet
https://github.com/Lolzen/android_device_nvidia_shield-common
Kernel:
https://github.com/Lolzen/android_kernel_nvidia_shield
Nvidia hardware:
https://github.com/Lolzen/android_hardware_nvidia_power
https://github.com/Lolzen/android_hardware_nvidia_thermal
https://github.com/Lolzen/android_hardware_nvidia_libstagefrighthw
Vendor blobs:
https://github.com/Lolzen/proprietary_vendor_nvidia
Credits:
=================
Steel01 for providing device trees and blob sources and doing an excellent job maintaining them
BitOBSessiOn and OmniROM folks for pointing me in the right direction getting past the Black Screen
OmniROM Project for code base and being #swag in General
Thanks ! The only problem is that the video is not working
marcostesvk said:
Thanks ! The only problem is that the video is not working
Click to expand...
Click to collapse
Thanks for reporting! Could you specify which app? I do have mixed results on this, on one hand YT / MX Player are working on the other one Clover can't play webM's.
I'll certainly look into it.
The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?
marcostesvk said:
The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?
Click to expand...
Click to collapse
I'd advice against that, personally.
However, i have a workaround for the videos. There's some problem with the hardware decoding, i still have to figure out why.
For now i simply disabled hardware decoders, the software decoding seems to work fine, but this isn't a fix by any means.
I'll add the link to the download once the upload finished.
added to OP
Another bug i've encountered is that the Shield Camera's pictures are distorted, however when you activate HDR everything is fine. Again, just a workaround for now. The alternative is to use AOSP Camera.
Charging issue fix available?
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.
fmcgregor said:
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.
Click to expand...
Click to collapse
Seems weird.
Does anybody else have this issue?
klo_lol said:
Seems weird.
Does anybody else have this issue?
Click to expand...
Click to collapse
Thanks for trying. And thanks to anyone for replying. In terms of self help, I downloaded some battery apps to see if they can re-align the battery so it can charge up to 100%. Still only charging up to 89%. Tried cleaning the input ports and the chargers. I have wiped cache partitions. I have the latest TWRP. I'm scared to try to re-flash because it was so difficult - "setup wizard keeps stopping."
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!
fmcgregor said:
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!
Click to expand...
Click to collapse
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?
klo_lol said:
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?
Click to expand...
Click to collapse
Yes TWRP 3.1.1-1. Thx very much for the OTA link. Just fyi, the battery zip link was dead. But I'll find a working link now that I know the general name..
klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
Hi, just an update. I re-flashed and used bean gapps this time. No problems this time, but the battery still won't charge above 89%. Just as a by the way, the clock and date start up at factory until I get it on the wifi and it syncs. Every time. If there's no wifi, it's set to Dec. 31, 2012. Anyone else with this?
uploaded a new build. Link in OP.
No major changes, just up2date with omni source as of today
new build in OP.
*updated with latest omni 7.1 changes
*updated with some device changes from Aaron Kling
*updated kernel with latest nvidia kernel sources
i'm still bumping my head against a wall why hwencoders seem to have some sort of problems. You can play media, it's just not working with the configs it's supposed to.
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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 us for messing up your device, we will laugh at you.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: Whenever I try flashing any lineage-16.0 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: I am seeing Error 7 when trying to flash a GApps package.
A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: How often will new builds be released?
A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed.
[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]
ROMs
pitrus-
- LTE: deb
- Wi-Fi: flo
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
Open GApps
How to flash LineageOS and Open GApps1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
5. Swipe to Wipe at Bottom of Screen,
6. Back to Main start screen,
7. Wipe > Format Data,
8. Type 'Yes' and press blue checkmark at the bottom-right corner,
9. Go Back to Main Start Screen,
10. Move your LineageOS Rom and GApps Package to the internal storage,
11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- Encryption does not work at all. Upon encrypting your tablet, you will be unable to reboot into System. This is a bug in all AOSP-based custom Pie roms for deb and flo.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.
Sources
- deb device tree
- flo device tree
- kernel
- blobs
XDA:DevDB Information
LineageOS 16.0, ROM for the Nexus 7 (2013)
Contributors
ripee, followmsi, pitrus-, flex1911, Clamor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: System partition large enough to accommodate the rom and GApps.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-08-11
Created 2019-02-22
Last Updated 2019-11-10
Reserved
Reserved
Awesome! Keep up the great work and thank you for keeping this devices development alive
JT1510365 said:
Awesome! Keep up the great work and thank you for keeping this devices development alive
Click to expand...
Click to collapse
All credit to followmsi and flex1911
oh yeah maga
make android great again
Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?
DaCl88 said:
Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?
Click to expand...
Click to collapse
Since the sources I linked are followmsi's, yes this is the same rom, but built more recently to take advantage of the lineage commits added since followmsi's last build. Because of this, it will have the same h.264 bug in Kodi.
Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !
gaja22 said:
Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !
Click to expand...
Click to collapse
Did you re-partition the memory, as described in the FAQ's in the OP?
ripee said:
All credit to followmsi and flex1911
Click to expand...
Click to collapse
Of course
To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.
Thx!
Will test this ROM!
yourrealking said:
To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.
Click to expand...
Click to collapse
Hello, my lock screen will be temporarily displayed in portrait then rotates to landscape.
Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?
hlxanthus said:
Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?
Click to expand...
Click to collapse
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.
ripee said:
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.
Click to expand...
Click to collapse
Read the OP's instructions again. It clearly says to wipe data and internal storage.
Hi and thanks for (the) pie. It works great for the main user but i have a strange problem with a secondary (or guest) user:
Whenever i switch to the secondary user the navigation bar (three buttons) disappears. The bar is not just hidden but seems to be really gone/killed. When switching back to the main user the bar is still missing and i need to restart to get it back. Any ideas?
The pie ROM works great on my Nexus. Thank you so much. It's amazing. I hope you plan to add the security patches every month. Thx.
hlxanthus said:
Read the OP's instructions again. It clearly says to wipe data and internal storage.
Click to expand...
Click to collapse
Yes, I have read the OP. Wiping both data and internal storage is for the sake of less experienced users who should be starting fresh no matter what rom they're coming from. As you have more experience, please use your judgment to wipe whatever you know needs to be wiped.
{
"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:
#include <std_disclaimer.h>
/*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.All the source code for LineageOS is available in the LineageOS GitHub organization.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.You can also view the changelog for a full list of changes & features.Official LineageOS website : http://lineageos.orgAbout LineageOS Legal : http://lineageos.org/legal
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.2. This ROM does not intended to support Google Camera, but you can try to play with some mods.
About FDE and FBEFull-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.To make it a bit clear:- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the sameMoreover, to work with new encryption you need a recovery with appropriate support.Downloads Links
LineageOS 20:Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/kugoGoogle Applications (optional):MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)XDA post about GApps: https://xda-developers.com/download-google-apps-gappsRecommended Recovery (optional):TWRP 3.x: https://forum.xda-developers.com/-/-t3793837
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta
FEATURES AND ISSUES
Boot: Ok
Bluetooth: Unknown
WiFi: Ok
WiFi Hotspot: Unknown
RIL - Phone - Data: Ok
GPS: Ok
Camera: Unknown
Camcorder: Unknown
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok (WIP)
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Unknown
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing
It's amazing bro, i can't bealive my device got A13
It seems the device is working again - post removed
soomon said:
I installed this system, and at the 2nd reboot my phone is dead. completely dead. seems it has been bricked before I even could log into my google account.
It doesnt even react to power any more.
Of course the phone is old and wasnt used for a long time, so I dont know if it got bricked by the OS or the hardware.
but it's dead.
be careful people!
Click to expand...
Click to collapse
It's almost impossible to brick this device completely just by ROM, unless you're doing something very unusual or developer-related.
This ROM has been tested by user for more than two weeks and everything was fine. It also been tested by Xperia X users since March, there was nothing like that either... and there never was actually.
Anyway, there is no specific in your message, except "It doesnt even react to power any more". Try to get adb/fastboot modes, charge or flash stock firmware. If no luck, I'm pretty sure it's a hardware issue, probably battery or something else.
I was also thinking about this and it was hard for me to believe the custom OS could actually damage the hardware.
I am happy to report it seems to be the device itself that caused the issue and not the rom. Today it was working Since it is an old device I'm assuming it was a hardware issue, so I deleted my old post.
It's working perfectly now. thank you so much!
I'll install this asap. Cant belive that this device is live again. Im using it as main phone. Gonna post my experience with rom here. Cheers
Edit: Cant seems to make it work . i was on latest stock, did full wipe , installed clean los20 , no gapps no additional zipps . it goes past sony logo shows black screen and immediately restarts on that black screen . Any suggestions ?
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?
After install this rom i found bugs on this rom A13 LOS 20:
-WIFI
-HOTSPOT
-TAP TO WAKE NOT WORK
- GPS can't lock
- NFC
Edit : after reinstall from Lineage 19 to Lineage 20 , Wifi , hotspot , Gps , working fine
Thanks for @Chippa_a and team , share and build rom for x compact
Deep sleep pretty good , keep it up
shandu98 said:
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?
Click to expand...
Click to collapse
Do you have the latest TWRP offered on the other thread? If you get a boot loop back into TWRP you can try tapping restart to system which is an option within TWRP. If you still have problems after with a boot loop try a clean install by wiping dalvik, cache, system, internal storage, followed by formatting data, then reboot to TWRP flash the build and tap restart to system when finished.
my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo
Tri Akbar Fitriana said:
my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo
Click to expand...
Click to collapse
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.
Asta01 said:
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.
Click to expand...
Click to collapse
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
I flash Stockrom with flashtool. I dont need TA file.
Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
No.
Try lineage recovery it works for me, with twrp i get black screen
Chippa_a said:
Moreover, to work with new encryption you need a recovery with appropriate support.
Click to expand...
Click to collapse
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!
Chippa_a said:
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!
Click to expand...
Click to collapse
Thanks,with twrp 3.7.0_12 is twrp working.
Thank you chippa _a. The rom is amazing. I haven't found any bugs so far, and it's incredibly fast. A new life for the Xperia x compact. Thanks alot.
Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because my phone is rooted, is there a solution for that?
SietZ said:
Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because NY phone is rooted, is there a solution for that?
Click to expand...
Click to collapse
For me is Google cam port "MGC_8.2.204_Parrot043_V1" working perfect.