My Daily QA - 2020-08-28
#1
Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results: mobian/08-28-2020-Verizon.html
               mobian/08-28-2020-TMobile.html

[b]Conclusion: [/b]OS is not Ready for pinephone to be daily driver.

[b]Notes:
[/b]The Microphone is getting really sensitive. The audio out quality is suffering because of it.


I started a longevity test thanks to a comment from @ragreenburg

I set the phone down and let it go to sleep. After about an hour i send a text to my pinephone. I never received it. I called the pinephone. It never rang. I unlocked the phone to see if it would reconnect. It didnt.

Connection to the cell towers broke and the phone had to be rebooted to reconnect. Connection to my wifi broke and had to be rebooted to reconnect.

I dont have a section on my test sheets for this longevity test yet.
#2
(08-28-2020, 02:57 PM)AmazingNutria Wrote: Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results: mobian/08-28-2020-Verizon.html
               mobian/08-28-2020-TMobile.html

[b]Conclusion: [/b]OS is not Ready for pinephone to be daily driver.

[b]Notes:
[/b]The Microphone is getting really sensitive. The audio out quality is suffering because of it.


I started a longevity test thanks to a comment from @ragreenburg

I set the phone down and let it go to sleep. After about an hour i send a text to my pinephone. I never received it. I called the pinephone. It never rang. I unlocked the phone to see if it would reconnect. It didnt.

Connection to the cell towers broke and the phone had to be rebooted to reconnect. Connection to my wifi broke and had to be rebooted to reconnect.

I dont have a section on my test sheets for this longevity test yet.

Thanks for adding this,
   I found the same problems,
 since I am using this sim card to hopefully receive an important text from DHL,
I put the August 26 release back on my Brave Heart for continued use.
   ( I really hope that important text does not come while I am testing new releases ! )

Notes:
  I really think just adjusting the 'microphone input' down a little bit in 'settings' would correct
the 'sensitivity issue'  (under 'sound').
  You must set some settings anyway, such as 'region & language' when you run the first time.

Also :  I have found when setting the region & language that a full shutdown works better than
a 'restart' ( for me )
#3
(08-28-2020, 02:57 PM)AmazingNutria Wrote: Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results: mobian/08-28-2020-Verizon.html
               mobian/08-28-2020-TMobile.html

[b]Conclusion: [/b]OS is not Ready for pinephone to be daily driver.

[b]Notes:
[/b]The Microphone is getting really sensitive. The audio out quality is suffering because of it.


I started a longevity test thanks to a comment from @ragreenburg

I set the phone down and let it go to sleep. After about an hour i send a text to my pinephone. I never received it. I called the pinephone. It never rang. I unlocked the phone to see if it would reconnect. It didnt.

Connection to the cell towers broke and the phone had to be rebooted to reconnect. Connection to my wifi broke and had to be rebooted to reconnect.

I dont have a section on my test sheets for this longevity test yet.
Just saw this and I tried a similar longevity test last night with the August 29th nightly build and it seemed to work though I noticed that sending texts to myself always resulted in me getting a response saying this function isn't available so I texted my roommate and they said they got it.
#4
I know you already have a long list of testing items.
At some point, it might be also useful to see how long it takes for certain apps to be launched.
For a daily driver, this should be quicker. The camera took me between 5 -10 seconds, firefox took 10-15 seconds to appear... Is this a ram issue? any clue why it takes so long?

I mean we can get used to that, for sure. But if it can be improved, we should...


Possibly Related Threads…
Thread Author Replies Views Last Post
  2020-11-13 Image status. Gribouille 38 8,011 07-10-2021, 05:43 AM
Last Post: Gribouille
  Status update 2020-12-15 a-wai 34 13,423 01-13-2021, 07:14 AM
Last Post: scott_VYuCAbn3k1NFK
  My Daily QA - 2020-10-06 AmazingNutria 6 2,501 01-05-2021, 10:08 PM
Last Post: daniel
  Why the 12/15/2020 build is no where near a daily driver yet TheLastDon 24 5,511 12-31-2020, 09:51 AM
Last Post: HLing
  Status update 2020-11-15 a-wai 17 7,613 12-05-2020, 05:58 PM
Last Post: bcnaz
  Status update 2020-09-05 a-wai 26 10,692 10-12-2020, 01:50 PM
Last Post: dukla2000
  Status update 2020-10-05 a-wai 8 3,001 10-08-2020, 03:20 AM
Last Post: dukla2000
  My Daily QA - 2020-09-22 AmazingNutria 4 1,806 09-25-2020, 08:33 AM
Last Post: bcnaz
  My Daily QA - 2020-09-11 AmazingNutria 2 1,319 09-20-2020, 09:17 PM
Last Post: daniel
  My Daily QA - 2020-09-10 AmazingNutria 1 1,074 09-11-2020, 08:30 AM
Last Post: daniel

Forum Jump:


Users browsing this thread: 1 Guest(s)