Testing Samsung A3 (2016) a3xelte January 2021 Oreo "dev" build

Image tested: e-0.14-o-2021012798648-dev-a3xeltexx.zip
TWRP on phone: twrp-3.5.0_9-0-a3xelte

Tested over a period of about 12 hours today. The image installed ok, /e/ starts fine initially, as soon wifi is connected the expected bootloop started.
https://gitlab.e.foundation/e/backlog/-/issues/943. I tested secure wifi and unsecured, apparent same dropout with either.

I since found I could connect the phone to wifi by

  • disconnect router from outside line,
  • connect phone by wifi to local network,
  • reconnect router to outside line.

Now I can hold a connection for several hours, install apps by wifi, do useful online work, make and receive calls and SMS.

I can get adb logcats but https://haste.tchncs.de/ says all are “too big to post”. I will continue to experiment to get a shorter, more specific log.

Thank you very much for the work that has been done for this fine phone.

If any of this is news to devs I would be very happy to provide more feedback.

1 Like

Did you format /data ?
Backup your things, before doing it,
I am afraid it is needed for a system upgrade.

I did format data and more, a number of times, as it happens, due to initially having a “Zip signature verification failed!” issue. Just to be more clear, the phone was previously nicely running e-0.10-p-2020081067156-test-a3xelte which I had successfully updated with an update containing date 20200813.

Im waiting till the Q build comes out next week !

This is an age-old /e/ problem that has not been fixed for almost two years. Test ROM /e/OS ‘9-Pie’ ran much better. If an /e/ OS ‘Q’ should come, it can only get better.

1 Like

Update: In that test I had an uptime of 30 hours, using the phone well on wifi, calls and SMS. I lost the uptime due to coming indoors without switching wifi off, so I failed to do my “soft wifi connect”.

I did just note this post where an A310F… is reported running

I add this comment as I wonder if something in the Stock ROM still lingers from the phone previously locked to carrier O2?

I have searched for stock ROMs for this device, the carrier is still mentioned. I wonder if the same apples to SM-J700F j7eltexx which shares this issue #263.

(Meanwhile e-0.10-p-2020081067156-test-a3xelte updated with an update containing date 20200813 has run nicely for over a month and 24 hour test of lineage-17.1-20210103-recovery-a3xelte.img - no issues found.)