Within 30-40 seconds after opening any application (including the android system ones that auto-load @ boot), they crash ; promting: "__ has stopped unexpectedly. please try again."
Recent changes:
installed avast! (recently uninstalled)
set up swift key X
any ideas/fixes?
on cm7 btw.
As a last resort, if nobody is able to come up with a specific fix for you, I would suggest reflashing the ROM or restoring to factory settings within the ROM. It can be a pain in the butt, but if nothing else works, it's like starting from scratch in the ROM. That tends to be what i do when i have problems that are widespread like that and it always fixes it for me.
Out of curiousity which build of CM7 are you using? I have the latest nightly (420) of 7.2 and it is the most stable and customizable DInc ROM I've tried.
EDIT: I am flashing CM 7.2 RC2 right now, I didn't realize it came out a few days ago. Until further notice though, I still would recommend the nightly just because I haven't really tried this yet, knowing CM though they wouldn't release an RC if it wasn't ready. Hopefully they will start work on CM9 for dinc soon if we cross our fingers.
of course >.<
i believe its a standard build of 7.0.2, i cant check though because settings crashes immediately
ugh.. now its bootlooping.
flashed to 7.2 RC2;
please lock.
vassskk said:
flashed to 7.2 RC2;
please lock.
Click to expand...
Click to collapse
I hope it works out for you!! if you have anymore problems, come on back and someone will try to help you out.
I have a Verizon GNEX, been running an older version of PA for quite a while, went to update to the newest version and on first boot during the initial setup it would freeze and reboot. I have tried everything i can think of, different roms, ODIN, different kernels, but it still will freeze and reboot after a couple taps, TWRP and the bootloader work fine and havent frozen once, I'm doing most of this through the Nexus Toolkit but I just cant get it to work at all.
Ive seen some people have had similar issues and they seems to be hardware related I'm really hoping thats not the case and its just an obscure issue that I cant seem to pin down
Any help would be greatly appreciated.
Most likely is the new CM theme engine bug included in most of the KitKat custom ROMs out there including PA. I found SlimKat to be stable because they're building their own theme engine instead.
Until the maintainers (see Lineage Info/Maintainers at http://wiki.lineageos.org/d2att_info.html)
have a chance to create a thread, let's share our experiences with the LineageOS 14 Nightlies here
Latest LineageOS 14 Nightlies
https://download.lineageos.org/d2att
i am just a novice but.......I did a clean install of the 1/23 rom with the mini gapps and everything went well as expected. Wifi, calls/data, bluetooth, battery life, camera all work perfectly for my limited needs.
The only hiccup I had was in doing the the 1/30 update. When doing the update using settings, Lineage will download the update and boot to TWRP, but will not automatically install the update. Easy enough though, as I performed the update manually.
I can't complain. I have a five year old device with up to date software and security patch. All I can say is thanks to these amazing developers.
yoshkapundrick said:
i am just a novice but.......I did a clean install of the 1/23 rom with the mini gapps and everything went well as expected. Wifi, calls/data, bluetooth, battery life, camera all work perfectly for my limited needs.
The only hiccup I had was in doing the the 1/30 update. When doing the update using settings, Lineage will download the update and boot to TWRP, but will not automatically install the update. Easy enough though, as I performed the update manually.
I can't complain. I have a five year old device with up to date software and security patch. All I can say is thanks to these amazing developers.
Click to expand...
Click to collapse
Did you use the addonsu*.zip file (https://download.lineageos.org/extras) to root the device. If so, did you have any problems?
No I didn't. I was only changing roms from cyanogenmod to lineage.
With 2017-02-13 nightly installed, I was able to finally performed a successful backup and restore in TWRP 3.0.2-0.
Phone was setup with a clean install using the following:
lineage-14.1-20170213-nightly-d2att-signed.zip
addonsu-arm-signed.zip
open_gapps-arm-7.1-nano-20170213.zip
Automatic syncing of date and time with network does not work all the time on 2017-02-13 nightly.
If you set the date and time to use network provided time (Settings\Date & Time\Automated date & time) it uses the correct time for a while but then switches to some random time.
Other people I know have had this problem and some of them are on different cell providers.
I had to turn off the automatic settings and set the date and time manually.
tjensen said:
Automatic syncing of date and time with network does not work all the time on 2017-02-13 nightly.
If you set the date and time to use network provided time (Settings\Date & Time\Automated date & time) it uses the correct time for a while but then switches to some random time.
Other people I know have had this problem and some of them are on different cell providers.
I had to turn off the automatic settings and set the date and time manually.
Click to expand...
Click to collapse
Same problem here. Also home button wake the device regardless of the setting under buttons sub menu and a very erratic compass after several attempts to calibrate.
Anyone getting "Updater process ended with ERROR 7" error with installing 20170220 update?
yoshkapundrick said:
Anyone getting "Updater process ended with ERROR 7" error with installing 20170220 update?
Click to expand...
Click to collapse
I did, so downloaded again and still the same... Wiped everything and flashed it anew; working great.... simply can't update existing rom... or so it seems...
nextmouk said:
I did, so downloaded again and still the same... Wiped everything and flashed it anew; working great.... simply can't update existing rom... or so it seems...
Click to expand...
Click to collapse
Yep, previous nightlies I could dirty flash. However, 2017-02-20 nightly I could only clean flash to install.
In TWRP:
Dalvik/ART Cache - Wipe
System - Wipe
Data - Leave
Internal Storage - Leave
Cache - Wipe
Micro SDCard - Leave
USB OTG - Leave
Dirty flash produces error
Dalvik/ART Cache - Wipe
System - Wipe
Data - Wipe
Internal Storage - Leave
Cache - Wipe
Micro SDCard - Leave
USB OTG - Leave
Clean flash produces no error
UPDATE: 2017-02-21 nightly can be dirty flashed
20170221 update works nicely in updating previous versions.
tjensen said:
Automatic syncing of date and time with network does not work all the time on 2017-02-13 nightly.
If you set the date and time to use network provided time (Settings\Date & Time\Automated date & time) it uses the correct time for a while but then switches to some random time.
Click to expand...
Click to collapse
This is still problematic int the 2017-02-27 nightly. At least on my device, it's a time zone issue. That is, the automatic time zone setting isn't working. So, the minutes are right, but the device shows GMT instead of CST/CDT.
Everything else seems to be working, and I find Lineage OS a bit "snappier" than Oct-OS - probably because of the absence of add-ons. But, hey, it's a 4.5-year-old phone.
New TWRP version 3.1.0-0 released!
https://dl.twrp.me/d2att/
Anyone notice a moderate improvement of the compass (I had not checked in months since cm). My readings used to be wildly variable, however now it seems to be consistently off 20 degrees.
FYI: After encrypting the phone with 20170320 nightly installed, the sim card is not recognized.
First I did a CLEAN install of 20170320 nightly; sim recognized.
Next I did not make any changes except encrypted the phone; sim NOT recognized.
SIM not recognized
After the first boot on 20170328 the SIM card is recognized but once the device is rebooted the SIM card is not recognized anymore, the same with 20170320.
FYI: Posted over on reddit an inquiry on the status of the compass accuracy on our D2att LineageOS device.
https://www.reddit.com/r/LineageOS/comments/64v74o/d2att_compass_accuracy/
The d2att does not appear to be supported anymore by LineageOS.
There are no maintainers listed at https://wiki.lineageos.org/devices/d2att anymore.
And then there is this in blazing red on the page:
"The Samsung Galaxy S III (AT&T) is either unmaintained or does not meet the criteria needed for official LineageOS support status. A build guide is available for developers that would like to make private builds, or even restart official support."
If anyone has any news it would be appreciated.
tjensen said:
The d2att does not appear to be supported anymore by LineageOS.
There are no maintainers listed at https://wiki.lineageos.org/devices/d2att anymore.
And then there is this in blazing red on the page:
"The Samsung Galaxy S III (AT&T) is either unmaintained or does not meet the criteria needed for official LineageOS support status. A build guide is available for developers that would like to make private builds, or even restart official support."
If anyone has any news it would be appreciated.
Click to expand...
Click to collapse
Thanks to tjensen For posting this.
For those wondering, Yesterday (04/14/2017), I posted the following on reddit:
Samsung Galaxy S3 not supported anymore?
https://www.lineageoslog.com/14.1/d2att Unless I'm incorrect Lineage 14.1 support for d2att, d2spr, d2tmo and d2vzw has been discontinued. Can anyone confirm this?
Link to reddit post: https://www.reddit.com/r/LineageOS/comments/65diqo/samsung_galaxy_s3_not_supported_anymore/
Chuckles5150 said:
Thanks to tjensen For posting this.
For those wondering, Yesterday (04/14/2017), I posted the following on reddit:
Samsung Galaxy S3 not supported anymore?
https://www.lineageoslog.com/14.1/d2att Unless I'm incorrect Lineage 14.1 support for d2att, d2spr, d2tmo and d2vzw has been discontinued. Can anyone confirm this?
Link to reddit post: https://www.reddit.com/r/LineageOS/comments/65diqo/samsung_galaxy_s3_not_supported_anymore/
Click to expand...
Click to collapse
Just last week the d2att was ranked 89th out of 1,254 devices for the most installs of the LinageOS (according to LinageOS stats page).
With that kind of popularity and interest I thought it was safe and would always have maintainers wanting to continue the builds. :crying:
I am trying to flash CM 12.1 on a GT6810P. I followed instructions from the 1st post of the thread and everything works fine up to the point of flashing the zipfile of CM12.1. It progresses to "Patching system image unconditionally" and then nothing happens anymore. I tried both CMWR 6.0.5.1 as the latest TWRP. In CMWR the wire frame keeps rotating, but the process never finishes. I let it run for 1 hour and 45 minutes, but still no end.
Does anybody have any clue what is wrong or what I am doing wrong?
I discovered that above problem is only with the most recent release of the 8th of June '16. I was able to flash the second last release of the 18th of januari '16 without a problem. Pretty strange. Did anybody had the same problem as me?
I had the same problem with cm-12.1-20160608-UNOFFICIAL-nevisp and after reading through the forums, I discovered that others did too.
I'm also using cm-12.1-20160118-UNOFFICIAL-nevisp, but I can't seem to use WhatsApp without the phone crashing every few hours.
CM11 had trouble playing videos in WhatsApp, so I moved to CM12. I still have not found a stable build that can do just Youtube, Whatsapp, and basic calls without crashing or poor performance. Have you tried the CM13 release by faizauthar12?
eximiusnl said:
I discovered that above problem is only with the most recent release of the 8th of June '16. I was able to flash the second last release of the 18th of januari '16 without a problem. Pretty strange. Did anybody had the same problem as me?
Click to expand...
Click to collapse
orangematter said:
Have you tried the CM13 release by faizauthar12?
Click to expand...
Click to collapse
Yes, I tried that one after I could not get cm-12.1-20160608-UNOFFICIAL-nevisp to work. But CM 13 is so slow that it is not usable and hangs on the Google login, so Play store does not work.
cm-12.1-20160118-UNOFFICIAL-nevisp seems to complain about the SIM and seems to expect a dual SIM phone. The last posts in the CM12.1 thread are related to this issue.
I recently upgraded the Motorola One Action LOS4M to the latest 4-7-2022 build and, after the typical LineageOS loading screen (which lingered an abnormal amount of time), it shut off on its own and was sent to the LineageOS Recovery saying the ROM was "corrupt," and to do a factory reset to possibly fix it. After trying that a few times (including a TWRP advanced wipe), I get the same result of being sent back to the recovery with the same message installing the Official ROM from LOS4M official site. Anyone else having this problem with this build, and any of the recent Official LineageOS builds (not the 'for MicroG' builds) so we can tell where the issue is? The previous build (3-21-2022) still works fine so had to downgrade to get the phone to work.
You should try the new 19.1 build and see if it works.
From reading the wiki, you should use "MindTheGapps".
If you're not looking to do that, isn't a way to use MicroG "rootless" (without flashing it)?
This could be a bug, as none of the builds are stable (nightly).