{
"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!
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 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.
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP, for Android Pie we based on the "Ground Zero Open Source Project" (GZOSP), and now for Android 10 we are fully based on AOSP.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
Download link: https://dwnld.aicp-rom.com/
Test builds: https://www.androidfilehost.com/?w=files&flid=302281
NOTE: Test builds are often those builds that I use personally. They tend to include open patches from our gerrit, and some additional changes documented here.
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
- Generating QR Codes for wifi sharing is broken (AOSP bug for devices without biometric sensors)
- You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android 10. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
0. Real recovery is recommended, it has been reported though that FOTA recovery might work too. There are issues with reboot to recovery with some recoveries (the TWRP linked here seems to work fine for me)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Flash the root solution of your choice (optional).
7. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
Currently supported Root Solution:
Magisk stable
Magisk versions >= 17.2 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/AICP/kernel_sony_msm8974/tree/q10.0
Device tree source:
https://github.com/AICP/device_sony_amami/tree/q10.0
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
NeoArian
rcstar6696
SuperLamic
AdrianDC
115ek
drakonizer
HazouPH
All the other contributors to sony msm8974 platform
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
Android Ice Cold Project (AICP) 15.0 (q10.0) amami (Sony Z1 Compact), ROM for the Sony Xperia Z1 Compact
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader
Version Information
Status: Stable
Created 2019-11-18
Last Updated 2020-10-18
Reserved
Thank for this new ROM.
My remarks are ofc no complaints, only hints for other testers
Today I flashed AICP-q10.0_amami_20191118_1126.zip.
1. At every boot I get an error window:
"Android System: There is an internal problem with your phone."
2. With Magisk 20.1 I have root but the SafetyNet state is red
3. I flashed magisk-riru-core-v19.5.zip, but after flashing magisk-EdXposed-YAHFA-v0.4.5.1_beta.4463.-release.zip the phone does
no longer boot I had no time to search for a solution.
4. ExSDCard Access Enabler v3.5 is working, BusyBox for Android NDK v1.31.1 too.
5. I flashed a GAPPS (I found no other version) from here
https://www.cyanogenmods.org/downloads/nano-opengapps-for-android-10-arm32/
I could login at Google but I cannot download/sync my contacts or app updates.
The Playstore shows that the device is not certificated.
6: Camera is working but I found no possibility to store the pictures to the extSDCard.
Thank you very much for your work. It's excellent.
3. I flashed magisk-riru-core-v19.5.zip, but after flashing magisk-EdXposed-YAHFA-v0.4.5.1_beta.4463.-release.zip the phone does
no longer boot I had no time to search for a solution.
Click to expand...
Click to collapse
This is not the place for (ed)xposed related issues. See here for a solution:
https://forum.xda-developers.com/xposed/android-9-0-xposed-solutions-t3889513
hi
Camera button wake device not working.
Bluetooth find other phone but can't connected.
problem when I want to unlock the screen.
magisk 20.1 good worked.
gapp beta good worked.
Thank you for your work.
I pushed a new build since it's been some time since the last one (I've been quite busy with other things recently...).
There shouldn't be many changes from the device side, but there should be some updates and fixes to the framework which some of you might be interested in.
wi-fi does not work, without a SIM card can not connect to update over wi-fi.
sibor55 said:
wi-fi does not work, without a SIM card can not connect to update over wi-fi.
Click to expand...
Click to collapse
No, WiFi is fine here (2.4 and 5 GHz).
---------- Post added at 01:44 PM ---------- Previous post was at 01:34 PM ----------
SpiritCroc said:
I pushed a new build
Click to expand...
Click to collapse
Thank you very much.
1. Magisk SafetyNet-status is red
2. Google Play store: play protect-certificate is not certified.
I flashed ROM, GAPPS and Magisk several times (wiped all ofc).
The rest seams to be ok but I will continue only if these two problems are solved.
New build is up.
- Sony logo fixed
- enforcing sepolicy
- Fix for TWRP time included
SpiritCroc said:
New build is up.
Click to expand...
Click to collapse
Thank you.
SafetyNet in Magisk is green again
But the UI is very slow like in the last build too.
tramp20 said:
But the UI is very slow like in the last build too.
Click to expand...
Click to collapse
Sorry, problem was homemade
After a fresh installation (wipe all) it looks very good until now.
awesome
you keep this nice little phone alive
I've upgraded to AICP 15 and it's very stable, no problem until now, everything is working fine.
I think the battery is eaten a slighter more quickly than with AICP 14, but maybe I've not done a full setup of all the settings as it was in the previous version.
I just noticed a very very very small issue : the battery status of the BT device isn't shown (the parameter is correctly set).
Thanks a lot for all the work! :good:
Hi there, 2 questions if you dont mind hehe
1- About battery, which one has better performance, aicp android 7, 9 or 10 ?
2- Does anybody have the aicp android 7 ROM ?
Hy!
Wou, excelent work, it is great! Battery live in my Z1C is more better then Android 9, about 35 - 40 % better.
Official builds have started
Since I forgot to write here and some might have missed it: official AICP 15.0 builds have started for amami
(thanks to @tramp20 for reminding me)
SpiritCroc said:
official AICP 15.0 builds have started for amami
Click to expand...
Click to collapse
I assume I have to wipe all coming from AICP-q10.0_amami_20200226_0853?
tramp20 said:
I assume I have to wipe all coming from AICP-q10.0_amami_20200226_0853?
Click to expand...
Click to collapse
I think dirty flash should work, please report if it doesn't
SpiritCroc said:
I think dirty flash should work, please report if it doesn't
Click to expand...
Click to collapse
It worked but every app (incl. system ) needed 2-3 sec to start
So I did a full wipe and installed all again (ROM, Gapps, Magisk, Edxposed etc).
{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), 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 repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
NFC
Flashlight
Mobicore keystore
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Download the latest build.
Reboot to recovery
Flash the latest build.
Optional: Flash GApps for Google Services and Magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Common Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][10] LineageOS 17.1 for Galaxy J4+ [j4primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: OneUI, U2
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.1
Beta Release Date: 2020-02-25
Created 2020-02-25
Last Updated 2020-03-10
Changelogs :
Public Beta 3 - 18/03/2020 :
Fixed a issue which some users have broken ril.
Fixed a issue which some users have broken nfc.
Public Beta 2 - 10/03/2020 :
Merge Security Patch: 5 March 2020
Fix audio on second sim: @Geckyn
Fix HDR on Camera.
Fix FM Radio.
Fix torch releated issues.
Fix Mac Adress releated issues.
LineageOS Source Upstream.
Public Beta 1 - 26/02/2020 :
First public release.
Special Thanks :
@BarryBlackCat for non-stop, day and night testing builds.
@Geckyn for pointing out some stuff. Thanks man.
I will NOT accept your bug report if you are using a custom kernel.
I will NOT accept your bug report if you are using a modification (Like some magisk modules etc.).
I will NOT check your bug report if you didn't provide any logs (Some bugs may will be checked).
Camera doesn't take HDR photo (or hang when switching between HDR and non HDR mode), it also happened on other custom ROM as well.
No magisk module or custom kernel installed.
Here is the logcat with "camera" keyword as filter: https://pastebin.com/RrDvAtjw
Andhika24kd said:
Camera doesn't take HDR photo (or hang when switching between HDR and non HDR mode), it also happened on other custom ROM as well.
No magisk module or custom kernel installed.
Here is the logcat with "camera" keyword as filter: https://pastebin.com/RrDvAtjw
Click to expand...
Click to collapse
Thanks.
KotaMangga said:
Ashyx kernel sir?
Click to expand...
Click to collapse
Let me make the steps clear for you:
1) You must be on Android Pie (custom or stock ROM doesn't matter). If you're on Samsung Oreo (U2), upgrade to Samsung Pie first so the device bootloader will be upgraded to U4 or newer.
2) If you're on Samsung Pie, flash TWRP and do all the required steps (this includes flashing RMM bypass, flashing encryption disabler, and formatting your data). If you're already using custom ROM, just skip this step.
3) Go to TWRP. As far as I remember, you can boot directly to TWRP by pressing POWER + VOL UP when the device is off.
4) In TWRP, swipe to allow modifications. Go to wipe - advanced wipe - and select dalvik/ART, system, data, and cache - swipe to wipe. You may also want to wipe your internal/external storage to avoid dirty data from previous ROM and apps.
5) Go to install - select your ROM zip and flash it - also flash Magisk and GApps after that (if needed)
6) Reboot system. If asked to install TWRP system app, just unselect all checkboxes and press do not install.
7) You're done. First boot will take a while, be patient.
No, kernel is already shipped within the ROM itself. No ROM comes with no kernel (lol). Moreover, most custom kernels on the J4+ forum may not be compatible for Android 10 yet. The OP also stated do not flash custom kernel if you want to get his support. However, if you insisted, make sure to reflash Magisk (if installed before) after flashing custom kernel. Alternatively, flash the custom kernel first before flashing Magisk.
No, OrangeFox recovery is not tested. If you're having trouble flashing the ROM using OrangeFox, unpack TWRP tar file and flash the recovery.img as recovery inside OrangeFox. After reboot, you will have TWRP again as your recovery (press POWER + VOL UP, as stated earlier).
ROM screenshot: (Stock apps are actually there and just like in LOS 16, sorry I already uninstalled most of them)
Andhika24kd said:
Let me make the steps clear for you:
1) You must be on Android Pie (custom or stock ROM doesn't matter). If you're on Samsung Oreo (U2), upgrade to Samsung Pie first so the device bootloader will be upgraded to U4 or newer.
2) If you're on Samsung Pie, flash TWRP and do all the required steps (this includes flashing RMM bypass, flashing encryption disabler, and formatting your data). If you're already using custom ROM, just skip this step.
3) Go to TWRP. As far as I remember, you can boot directly to TWRP by pressing POWER + VOL UP when the device is off.
4) In TWRP, swipe to allow modifications. Go to wipe - advanced wipe - and select dalvik/ART, system, data, and cache - swipe to wipe. You may also want to wipe your internal/external storage to avoid dirty data from previous ROM and apps.
5) Go to install - select your ROM zip and flash it - also flash Magisk and GApps after that (if needed)
6) Reboot system. If asked to install TWRP system app, just unselect all checkboxes and press do not install.
7) You're done. First boot will take a while, be patient.
No, kernel is already shipped within the ROM itself. No ROM comes with no kernel (lol). Moreover, most custom kernels on the J4+ forum may not be compatible for Android 10 yet. The OP also stated do not flash custom kernel if you want to get his support. However, if you insisted, make sure to reflash Magisk (if installed before) after flashing custom kernel. Alternatively, flash the custom kernel first before flashing Magisk.
No, OrangeFox recovery is not tested. If you're having trouble flashing the ROM using OrangeFox, unpack TWRP tar file and flash the recovery.img as recovery inside OrangeFox. After reboot, you will have TWRP again as your recovery (press POWER + VOL UP, as stated earlier).
Click to expand...
Click to collapse
OK , thanks for the tutorial also the full explanation
Can we get some screenshots?
any temp fix for VoLTE and sec sim voice
swarupgolui said:
any temp fix for VoLTE and sec sim voice
Click to expand...
Click to collapse
Maybe you could try sending logcat when attempting voice (call?) on SIM 2. There is a handy app on Play Store called "Logcat Reader" to catch & filter logs easily, just press to round button to record the logs.
I currently can't do it since I don't have someone important to call.
swarupgolui said:
any temp fix for VoLTE and sec sim voice
Click to expand...
Click to collapse
Samsung's ims is heavily OneUI framework dependent. Fixing it is kinda miracle. I don't think it will be ever fixed. But if you contact me on telegram, we might try to fix it. Also trying to fix voice of second sim.
This rom for j6+ sir? , I cant flash it .
KotaMangga said:
This rom for j6+ sir? , I cant flash it .
Click to expand...
Click to collapse
Check the thread on j6+ forum.
ataberkozen said:
Samsung's ims is heavily OneUI framework dependent. Fixing it is kinda miracle. I don't think it will be ever fixed. But if you contact me on telegram, we might try to fix it. Also trying to fix voice of second sim.
Click to expand...
Click to collapse
telegram link?
swarupgolui said:
telegram link?
Click to expand...
Click to collapse
MacTavishAO
ataberkozen said:
MacTavishAO
Click to expand...
Click to collapse
already send the msg reply plz
my id @metalgod_IN
ataberkozen said:
Check the thread on j6+ forum.
Click to expand...
Click to collapse
no, I mean it's for j4+?
E3004 : This package is for j6primelte ; your device is j4primelte.
KotaMangga said:
no, I mean it's for j4+?
E3004 : This package is for j6primelte ; your device is j4primelte.
Click to expand...
Click to collapse
Don't click on "Download Latest Version", click on zip name with j4primelte.
I has installed the rom sir , this rom more faster.
I see little problem :
1. when i change to power saver , battery indicator going red . but after switch mode , its back normal
{
"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.